Installation, Upgrade, and Migration Guide for Cisco Unified MeetingPlace Release 8.6
Migrating from Cisco Unified MeetingPlace Release 7.1 or 8.0
Downloads: This chapterpdf (PDF - 530.0KB) The complete bookPDF (PDF - 5.68MB) | Feedback

Migrating from Cisco Unified MeetingPlace Release 7.1 or 8.0

Table Of Contents

Migrating from Cisco Unified MeetingPlace Release 7.1 or 8.0

About Migration

Changes between Release 8.5 and Release 8.6

Migration Process

Hardware Considerations for Migrating to Cisco Unified MeetingPlace Release 8.6

Application Server

Web Server

Hardware Media Server

Cisco WebEx Site

Changing the NBR Dial-Out Sequence

Migrating to a Virtual Machine

Preserved Data

Retaining Recordings

How To Prepare for a Migration

Migration Best Practices

Migration Considerations

Updating User Management

Migration Prerequisites

Using Rsync to Transfer Your Migration Data

How to Migrate the Application Server Software

About Migrating the Application Server Software

Preparing to Migrate the Application Server Software

Gathering Migration Values

Determining Which Procedure to Follow

Migrating the Application Server by Using the Console

Migrating the Application Server Remotely

Migrating Application Servers that are Used in a Failover Deployment

Migrating a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling

Migrating a Failover Deployment in a System with WebEx Scheduling

Migrating Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment

Completing the Application Server Software Migration

Updating Email Notifications

How to Test the Application Server Software Migration

Troubleshooting the Application Server Software Migration

How to Migrate the Web Server

Preparing to Migrate the Web Server

Backing Up the Web Conferencing Data Before a Migration

Cisco Unified MeetingPlace Web Conferencing Backup Utility

Specifying a Different Backup Destination Folder

Backing Up Data from the Source Web Server

Restoring the Web Server Data

Cisco Security Agent (CSA)

Installing the Web Server Software

Reconfiguring the Application Server Connection in the Gateway SIM

Connecting the Application Server to the Web Server

Allowing Guest Users to Dial Out

Troubleshooting the Web Server Migration

How To Install the Cisco WebEx Node for MCS for a Migrated System

How to Upgrade the Software for the Hardware Media Server

Hardware Media Server Software Upgrade Utility

Upgrading the Software for the Hardware Media Server

Restrictions for Upgrading the Software for the Hardware Media Server

Launching the Upgrade Utility

Upgrading the Software for Audio Blades

Upgrading the Software for Video Blades

Troubleshooting Errors When Upgrading the Software for the Hardware Media Server

Recommendations for Moving an Audio Blade to a Different Hardware Media Server

How to Change from a Hardware Media Server to an Express Media Server

About the Media Server

Changing the Type of Media Server that Your System Uses

How to Migrate Microsoft Outlook for Cisco Unified MeetingPlace

Upgrading the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook

Testing that the Migrated System Works Correctly

Configuring Your System After Migration

Completing the Migration


Migrating from Cisco Unified MeetingPlace Release 7.1 or 8.0


Release 8.6
Revised: 10/29/13

Complete the migration procedure in this module if you have an existing Cisco Unified MeetingPlace Release 7.x or 8.0 system, and you are migrating from an existing:

Audio-only deployment to a Release 8.6 audio-only deployment (retains MeetingPlace scheduling)

Cisco Unified MeetingPlace system with MeetingPlace scheduling to a Release 8.6 system with MeetingPlace scheduling

Cisco Unified MeetingPlace system with MeetingPlace scheduling to a Release 8.6 system with an audio-only deployment

Cisco Unified MeetingPlace system with Webex scheduling to a Release 8.6 system with Webex scheduling


Caution For complete details, see the Migration Overview module and use the Migration Matrix to determine your specific migration procedure.


Note If you are on a Release 7.x system, and have Adobe Connect (Adobe Breeze) meetings, then only audio and video recordings are migrated. Web recordings and attachments are not migrated. We recommend you keep your legacy Cisco Unified MeetingPlace system intact (to access legacy Web recordings and attachments), and install a new Release 8.6 system. For more information on supported migrations, see Migration Matrix.



Note Reservationless Single Number Access (RSNA) functionality is replaced with the multinode configuration in Release 8.6. If you currently have a RSNA system, see Migrating Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment.



Note This migration module covers the migration or installation of the following Release 8.6 components (Application Server, Web Server, Cisco WebEx Node for MCS, Hardware Media Server, and Microsoft Outlook plug-in). If your system includes any Cisco Unified MeetingPlace integration, then refer to the specific integration module for your release. See the Configuration Guide for Cisco Unified MeetingPlace Release 8.6.


This migration procedures comprises the following

About Migration

How To Prepare for a Migration

How to Migrate the Application Server Software

How to Migrate the Web Server

How To Install the Cisco WebEx Node for MCS for a Migrated System

How to Upgrade the Software for the Hardware Media Server

How to Change from a Hardware Media Server to an Express Media Server

How to Migrate Microsoft Outlook for Cisco Unified MeetingPlace

Testing that the Migrated System Works Correctly

Configuring Your System After Migration

Completing the Migration

About Migration

Changes between Release 8.5 and Release 8.6

Migration Process

Hardware Considerations for Migrating to Cisco Unified MeetingPlace Release 8.6

Migrating to a Virtual Machine

Preserved Data

Changes between Release 8.5 and Release 8.6

These are the some of the feature changes between Cisco Unified MeetingPlace Release 8.5 and Release 8.6:

For a complete list, see http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_release_notes_list.html.

Support for Windows 8 Operating System, Microsoft Outlook 2013, Microsoft Exchange 2013

Tested browsers:

Internet Explorer: 10

Mozilla Firefox: 22, see the Firefox release schedule at https://wiki.mozilla.org/RapidRelease/Calendar

Google Chrome: 28, see the Chrome release schedule at http://www.chromium.org/developers/calendar

Apple Safari: 5.1.7

Support for IBM Domino server: 8.5.3 (x86 and x64)

Support for IBM Lotus Notes:

Lotus Notes client 8.5.3

Lotus Notes template 8.5.3

Support for Cisco Unified Communications Manager: 10.0

VMware ESXi 5.1

Migration Process

Follow these steps to migrate to Cisco Unified MeetingPlace Release 8.6 from Cisco Unified MeetingPlace Release 7.0 or later.


Note If you have not done so already, review the migration matrix for Release 8.6 and ensure that your migration is supported. See Migration Overview.


Procedure

Step #
Step Description
Related Topics

Step 1 

Notify end users of the planned migration and system downtime.

 

Step 2 

Migrate your existing Application Server data and install the Release 8.6 Application Server software.

How to Migrate the Application Server Software

Step 3 

As needed, install the Release 8.6 Web Server software.

How to Migrate the Web Server

Step 4 

As needed, upgrade Cisco WebEx.

Cisco WebEx Site

Step 5 

As needed, upgrade the Hardware Media Server software to Release 8.6.

How to Upgrade the Software for the Hardware Media Server

Step 6 

If desired, convert the Hardware Media Server to an Express Media Server.

How to Change from a Hardware Media Server to an Express Media Server

Step 7 

As needed, reinstall the Cisco WebEx Node for MCS.

Note The Cisco WebEx Node for MCS is optional.


Note You may choose to install the Cisco WebEx Node on a virtual machine.


How To Install the Cisco WebEx Node for MCS for a Migrated System

Step 8 

As needed, configure your system to use Cisco WebEx.

"About Integrating with Cisco WebEx in the Configuration Guide for Cisco Unified MeetingPlace

 

Step 9 

As needed, migrate the Microsoft Outlook for Cisco Unified MeetingPlace integration.

How to Migrate Microsoft Outlook for Cisco Unified MeetingPlace

Step 10 

Test that the migrated system works correctly.


Caution Be sure to read and complete the post-migration procedures in Testing that the Migrated System Works Correctly, before using your system.

Step 11 

Inform end users that the system has been successfully migrated.

Completing the Migration


Hardware Considerations for Migrating to Cisco Unified MeetingPlace Release 8.6


Caution If you choose to continue using the same hardware for your Release 8.6 system, then make sure that it meets the minimum requirements for the Cisco Unified MeetingPlace Release 8.6. See http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html.


Note If you plan to use new hardware, then you can either shut down the old hardware during the migration or leave it running. If you decide to keep the old hardware, then any changes (including user changes, scheduled meetings, new recordings, and so on), made after the archive of your existing data, will not be copied to the new servers.


Application Server

You can install the Release 8.6 Application Server on a Cisco MCS or on a virtual machine with a VMware ESXi 4.1 (or later) host on a UCS B-Series or UCS C-Series Server.


Note Refer to the "Hardware Requirements" section of the System Requirements document for information about which release of ESXi to use with your system. See System Requirements at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html


Web Server

The Release 8.6 Web Server is installed on a Cisco MCS running the Cisco Unified MeetingPlace Windows operating system. In Release 8.5.2 and higher, you may install the Web Server on a virtual machine (with a VMware ESXi 4.1(or later) host on Cisco UCS B-Series Blade Servers and UCS C-Series Rack-Mount Servers).

You can either reuse an existing Cisco MCS for the Web Server or you can install a newer Cisco MCS. We recommend using new hardware for the Release 8.6 Web Server and keeping the old Web Server as a contingency until the Release 8.6 deployment is complete and operational.


Caution If you choose to continue using the same hardware for your Web Server, make sure that it meets the minimum requirements for theCisco Unified MeetingPlace 8.6 Web Server. Release 8.6 requires installation on a Cisco MCS with the Cisco Unified MeetingPlace Windows operating system. For more information, see the System Requirements for Cisco Unified MeetingPlace Release 8.6 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html.


Note If you are installing on an Cisco MCS 7835-I2 or 7845-I2, then you may need to upgrade or downgrade the firmware before installing the Cisco Unified MeetingPlace Windows operating system. For the steps to correct this problem, see Updating the Firmware on a Cisco MCS 7835-I2 or 7845-I2. For background information about the problem, see http://www.cisco.com/en/US/products/ps6509/products_tech_note09186a008059a81d.shtml.


Hardware Media Server

There have not been any significant changes in the Hardware Media Server.

Cisco WebEx Site


Note This section only applies to deployments that utilize Cisco WebEx.


When you migrate to Cisco Unified MeetingPlace Release 8.6, you must use the Cisco WebEx WBS27 SP27 or later Release. If you are using an earlier release, then you must upgrade to this release or later.

Notify the Cisco WebEx Client Success Manager (CSM) that you plan to migrate to Cisco Unified MeetingPlace Release 8.6. Ask the CSM to schedule and plan an upgrade of your Cisco WebEx site, as needed. Be sure to communicate any language requirements, as well.


Note In order to avoid a delay in implementing your migration, we recommend that you schedule the Cisco WebEx upgrade as far in advance as possible of your Cisco Unified MeetingPlace migration.



Caution (This only applies to deployments with WebEx scheduling, where you are upgrading an existing Cisco WebEx site.) If you are planning to use a different name for your Release 8.6 Application Server, then ask your CSM to update the Application Server hostname in the tele-domain (TD) during the time you are migrating your system to Release 8.6. If the hostname is prematurely changed in the TD before synchronizing the Release 8.6 Application Server, then some meetings (scheduled before the migration with the old hostname) may fail. By discussing this in advance with your CSM, the CSM can schedule a change to happen during the Cisco WebEx site's maintenance window.

Changing the NBR Dial-Out Sequence


Note This section only applies to deployments with MeetingPlace scheduling. A Cisco WebEx super administrator must complete this procedure.


Change the NBR Dial-Out Sequence by completing the following procedure. Otherwise, NBR recordings will not work in Release 8.6.

Procedure


Step 1 As the Cisco WebEx super administrator, find the telephony domain being used by the Cisco WebEx site.

Step 2 Edit the telephony domain.

Step 3 Find the section titled, Audio Broadcast/NBR Dial-Out Sequence, and change the dial sequence to the following:

Label
Pause Before
Value Entry
Require#

Enter 3#

2 Seconds

3

Y

Enter Profile #

1 Second

[Profile Number]

Y

Enter Profile Password

1 Second

[Profile Password]

Y

Enter Meeting ID

1 Second

[Meeting ID]

Y

Press 1 to enter meeting

1 Second

1

N


Step 4 Save your changes.


Migrating to a Virtual Machine

You can migrate your Application Server or your Cisco WebEx Node for MCS for MCS to a virtual machine, from a physical machine, with the following considerations:

The virtual machine must have the following requirements:

Application Server and Cisco WebEx Node for MCS: 8 vCPU, 8 GB RAM, and a 300GB hard drive.

Web Server: 4 vCPU, 4 GB RAM, and a 250GB hard drive.

Install one virtual machine, per blade, on a Cisco UCS B-Series or C-Series Server.

When installing the Cisco Unified MeetingPlace system remotely, be sure your LAN connection supports at least 1 Gb/s (gigabits per second).

The virtual machine must be on a VMware ESXi 4.1 (or later) host.


Note Refer to the "Hardware Requirements" section of the System Requirements document for information about which release of ESXi to use with your system. See System Requirements at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html.


For more information about installing Cisco Unified MeetingPlace components on a virtual machine, see Installing on a Virtual Machine.


Note The Cisco Unified MeetingPlace system does not support snapshots on virtual machines.


Preserved Data

The migration process presented in this module preserves the following data for the preceding 38 days or the number of days until the meeting statistics are purged, whichever number is lower:

Future meetings, including invited participants

History of past meetings and meeting participants (only for deployments with MeetingPlace Scheduling or audio-only deployments)

Continuous meetings that are still active (ongoing)


Note Continuous meetings are not supported in Release 8.6 for deployments with WebEx scheduling.


Recorded user names

Recorded meetings (for both voice and web) and attachments (these can only be accessed from the web) for completed meetings

You may be able to access older recordings. See Retaining Recordings for more information.

Future meetings

Recurring meeting instances (for audio deployments and deployments with MeetingPlace scheduling)

For deployments with WebEx scheduling, all past meetings are not retained in Cisco Unified MeetingPlace (because the meetings are retained in Cisco WebEx)

Users and groups

User language settings

Web customizations through the Cisco Unified MeetingPlace web user portal (Admin)

Cisco WebEx configurations

Directory Service configuration

SIP configuration

SMTP and Microsoft Exchange Server configuration

Click-to-attend links in previous e-mail notifications (only if the Cisco Unified MeetingPlace Release 8.6 Web Server has the same hostname (FQDN) as the legacy Web Server). If the hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Old Microsoft Outlook notifications

Old IBM Lotus Notes notifications

Old e-mail notifications

Retaining Recordings

If you want to retain historical recordings, you may chose one of the following options.

You can keep the legacy Cisco Unified MeetingPlace system for historical data.

We recommend you restrict users from starting new meetings on the legacy system. You can rename the legacy Cisco Unified MeetingPlace system with a new name, and retain the existing name on the new Cisco Unified MeetingPlace 8.6 system for an easier transition.

Retain the existing Cisco Unified MeetingPlace system for a specified period, and ask meeting hosts and participants to download historical meetings and attachments on to their own machine.

After the specified time, you can bring down the legacy system.

How To Prepare for a Migration

Migration Best Practices

Migration Considerations

Migration Prerequisites

Migration Best Practices

We recommend that you schedule to start and finish the migration of your Cisco Unified MeetingPlace system during a time when there is low activity and not much meeting traffic; for example, over a weekend or a period of extended downtime.

During the migration, you will need to transfer files between servers. Be sure to have a file transfer application, such as WinSCP, available to transfer these files.

Be sure that your archive directory has "write" permission so that the migration program can write your archive data.

Be sure the usernames have the necessary access permissions to perform the various procedures in this module.

When installing the Cisco Unified MeetingPlace system remotely, be sure your LAN connection supports at least 1 Gb/s (gigabits per second).

If you are using existing hardware, we highly recommend creating both a backup and archive, in case you need to revert to your legacy system. Sign in to the Cisco Unified MeetingPlace Administration Center and select Maintenance > Backup and Archive.

If you are planning to change the name of your Application Server or Web Server following migration, then consider the following:

If the Web Server hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Update the DNS server with the information for your new Release 8.6 Web Server and Application Server

(Only deployments with WebEx scheduling) If you are planning to use a different name for your Release 8.6 Application Server, and are upgrading an existing Cisco WebEx site, then ask your CSM to update the Application Server hostname in the tele-domain (TD) during the time you are migrating your system to Release 8.6. See Cisco WebEx Site.

Have a valid DNS service configuration. This is mandatory for correct operation of the Cisco Unified MeetingPlace system.

You need to enter a valid IP address for a DNS service during the installation of the Release 8.6 Application Server. Without this, your migration may fail.

You can test your DNS service by entering on the command-line interface, ping <DNS_IP_Address>. You should get a response in under 200 milliseconds.

Migration Considerations

The migration program retains the following information:

Cisco Unified MeetingPlace database

$MP_ROOT/licenses

$MP_ROOT/afs/custom

$MP_ROOT/afs/conf/ContinuouseMtg.list

/usr/local/enrollment

/opt/cisco/meetingplace/web/current/bases/main/conf/server.xml

/opt/cisco/meetingplace/web/current/etc/conf

/var/mp/ciscowebexadaptor/webex

/var/mp/ciscowebexadaptor/proxy

/opt/cisco/meetingplace/var/outlook/ResourcesCustom.properties

The migration program retains the Microsoft Exchange and SMTP configuration information in property files, as well as email templates, in the /mpx-record/migrateBackup directory:

/opt/cisco/meetingplace/var/mail/conf

/opt/cisco/meetingplace/var/mail/res

/opt/cisco/meetingplace/var/mail/res/rcms-res.ver

/opt/cisco/meetingplace/var/mail/conf/rcms-config.ver

/opt/cisco/meetingplace/var/mail/conf/rcms-config.xml


Note The version and content of these property files may change from release to release. The migration program checks and upgrades these files, if the versions are the same. If the versions of the property files are not the same, the program warns you to reset the configuration settings manually.


Release 8.6 system with WebEx scheduling—All future audio/video only meetings, that are scheduled from Conference Manager, are not migrated. Users cannot see, and will not be able to attend these future or recurring meetings, that were scheduled with Conference Manager prior to the migration.

Release 8.0 to Release 8.6 migration of a system with WebEx scheduling, MeetingPlace-driven User Management, and SSO integration—Following a migration, your Release 8.6 system will not support custom session types. If you attempt to use custom session types after migration, then non-default configurations will reset.

Release 8.0 to Release 8.6 migration of a system with MeetingPlace-managed profiles with Directory Integration—For proper profile creation with your WebEx integration, select only the five default values (First name, Last name, User name, Password and Email) on the WebEx Site Administration> WebEx Site Settings> Account Management Settings> Require for account signup in the Administration Center.

Release 8.6 system with MeetingPlace scheduling or audio deployments—All future audio/video only meetings, that are scheduled from Conference Manager, are migrated.

Release 8.6 system with WebEx scheduling—Does not support Delegate users. Following a migration, Delegate users are converted to "End users".

Cisco WebEx Node for MCS—Requires a fresh install on a MCS or on a virtual machine, as the underlying operating system has changed.

Web Server—Requires a fresh install, on a Cisco MCS with the Cisco Unified MeetingPlace Windows operating system. However, your Web Server data is migrated.

User profile numbers must be 8 digits or fewer in Release 8.6. Correct any user profiles longer than 8 digits by editing User Configuration > User Profiles in the Administration Center.

Updating User Management

Cisco Unified MeetingPlace Release 8.6 has two types of User Management: Cisco WebEx-driven User Management and Cisco Unified MeetingPlace-driven User Management.

Cisco WebEx-driven User Management—User profiles are copied to Cisco Unified MeetingPlace, as needed, to run meetings

We recommend Webex-driven User Management for all customers that integrate Cisco WebEx with Cisco Unified MeetingPlace Audio, starting with Release 8.6.

Cisco Unified MeetingPlace-driven User Management—User profiles are added locally to the Cisco Unified MeetingPlace system, or are synchronized from Directory Services.

The migration process retains profiles for MeetingPlace-driven User Management, if the existing system has MeetingPlace scheduling, or if Directory Services were used in the legacy system (AXL authentication).


Note If you had a Release 7.x or Release 8.0 deployment with WebEx scheduling, and without directory services, then you will have Webex-driven User Management following the migration. However, individual user profiles will still state MeetingPlace-driven User Management, until the user logs in to Cisco WebEx and the profile is sychronized.


Following the migration, you may sign in to the Administration Center and select User Configuration > User Profiles. Select Edit by the username to determine the User Management.

If your migrated Release 8.6 system has MeetingPlace-driven User Management, then you can always use the MPtoWebEx CSV Converter tool to change to Webex-driven User Management. However, if you decide to change to Webex-driven User Management after migration, then you will need to reinstall a new Release 8.6 Application Server and provision a new Cisco WebEx site compatible with a Release 8.6 system with Cisco WebEx-driven User Management. See Migrating Using the MPtoWebEx CSV Converter.


Note If you use the MPtoWebEx CSV Converter tool, then all data, other than user profiles, are lost. Be sure to keep your existing system to play existing recordings.


During the next user profile synchronization, Cisco WebEx will populate the WebExhostID field for each synchronized user profile.


Note Once you convert to Webex-driven User Management, you cannot change back to Cisco Unified MeetingPlace-driven User Management.


Migration Prerequisites

Obtain the Cisco Unified MeetingPlace Release 8.6 software DVDs from the Cisco Global Price List (GPL) or with a valid Cisco Unified Communications Software Subscription (UCSS). You will use the DVDs during the migration. Contact Cisco customer support for additional information.

Obtain the binaries for Cisco Unified MeetingPlace Release 8.6 or later from http://www.cisco.com/cisco/software/navigator.html. Select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6.

If you have a profile with a username of appuser-internal, then change that username. Otherwise, the migration program displays a message that this user profile is reserved for Release 8.6. The profile is removed and you are asked to confirm this removal before continuing with the migration.

If your deployment includes Hardware Media Servers, then be sure to write down the IP address for each MCU before you start the migration. You will need to configure your audio and video blades on the Cisco Unified MeetingPlace Release 8.6 Hardware Media Servers, following the migration.

Write down your SNMP configuration. You will need to configure it, following the migration.

Prepare a different archive server, for archiving your migration data. We recommend you use a different archive server than the one you use for regular backups, to avoid overwriting your existing backup data.


Note The migration program uses SSH/rsync to connect to the archive server used for the migration data. Be sure to select an archive server that supports this method of archiving.


Using Rsync to Transfer Your Migration Data

The remote server to which you archive files must support rsync and SSH connections.

You can set up rsync on a Linux or Windows machine, or a Mac. However, you may prefer to use a Linux machine or a Mac, as rsync may already have been installed as part of your operating system. If you prefer to install rsync on a Windows machine, there are various applications that provide this functionality.


Caution If you are using an Application Server as your rsync server and you are using the mpxadmin user for authentication, then be sure the mpxadmin password does not contain the @ special character. This special character may cause authentication to fail, and the migration process to exit.
If your mpxadmin password contains a special character, we recommend that you temporarily change the password to one without special characters, to ensure the rsync authentication does not fail. For more information on changing your password, see "Changing the Password for root or mpxadmin on the Application Server" or "Changing System Administration Passwords for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.


Caution These procedures are intended to provide you with a guideline for setting up a rsync server for Linux, Windows, or Mac operating systems. The exact commands and steps may differ for your particular environment.

Transferring Your Data to a Rsync Server With a Linux or Mac Operating System in the "Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server" section of the Configuration Guide for Cisco Unified MeetingPlace

Transferring Your Data to a Rsync Server With a Windows Operating System in the "Backing Up, Archiving, and Restoring Data on the Cisco Unified MeetingPlace Application Server" section of the Configuration Guide for Cisco Unified MeetingPlace

How to Migrate the Application Server Software

About Migrating the Application Server Software

Preparing to Migrate the Application Server Software

Gathering Migration Values

Determining Which Procedure to Follow

Migrating the Application Server by Using the Console

Migrating the Application Server Remotely

Migrating Application Servers that are Used in a Failover Deployment

Migrating Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment

Completing the Application Server Software Migration

How to Test the Application Server Software Migration

Troubleshooting the Application Server Software Migration

About Migrating the Application Server Software

Ensure the checksum program, sha1sum, is installed in the archive server. As the archive user, enter which sha1sum on the CLI of the archive server. If you see a response similar to "usr/bin/sha1sum", then the program is available and you are good to create the archive. If you don't have this program, then download and install it.

To migrate the Application Server software, you must already have an existing version of the Application Server software installed on your legacy Application Server or the migration program will fail.

Before running the migration, we highly recommend you backup and archive your existing data. If the migration fails, then you can use this data to set up your legacy Application Server. See Determining Which Procedure to Follow.

When you migrate the Application Server data, the migration program moves the existing Cisco Unified MeetingPlace data files to a remote backup directory.

A fresh installation of the Cisco Unified MeetingPlace 8.6 Application Server is required. The fresh installation reformats the hard disk, and erases all existing information on the hardware. The migration restore program will restore the legacy Cisco Unified MeetingPlace data files from the remote backup directory.

The migration program backs up any Microsoft Outlook notification templates and copies them to the /mpx-record/migrateBackup/opt/cisco/meetingplace/var/mail/ directory.

We support using Integrated Lights-Out (iLO) to install the Application Server software. This standard only applies to the Cisco MCS 7845-H2. For information about installing, configuring, and using iLO, see http://h18000.www1.hp.com/products/servers/management/ilo/.

The migration program retains the same deployment that you currently have on your existing Cisco Unified MeetingPlace system, regardless of the selection you choose during the installation of the Application Server. For example, a Release 7 or 8 system with WebEx scheduling, retains WebEx scheduling, following migration.

The migration program completes the following tasks

1. Creates an archive of Cisco Unified MeetingPlace data and transfers the data to an archive location.

2. Retrieves the migration archive data and uses it to restore the Cisco Unified MeetingPlace database and configuration data.

3. Updates the database schema to Cisco Unified MeetingPlace Release 8.6.

4. Depending on your deployment, it sets the User Management (of user profiles) and generates a report if any user profiles have profile numbers longer than 8 digits.

For more information on User Management, see "Configuring User Profiles and User Groups for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.

Preparing to Migrate the Application Server Software


Caution Do not run any other processes or tasks on your systems during a migration.

Do not uninstall the Application Server software before migration.

If your deployment includes Hardware Media Servers, then be sure to write down the IP address for each MCU before you start the migration. You will need to configure your audio and video blades on the Cisco Unified MeetingPlace Release 8.6 Hardware Media Servers, following the migration.

We recommend that the server that you are migrating have at least 4 GB of memory. See the System Requirements for Cisco Unified MeetingPlace Release 8.6 Release 8.6 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html

If you have automatic backups/archives enabled, then turn this off when you migrate the Application Server software.

Check the status of the Cisco Unified MeetingPlace system. Go to the Command-Line Interface and as root, enter the mpx_sys status command. Ensure that the database services are up and running. See "Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server" in the Configuration Guide for Cisco Unified MeetingPlace.

Gathering Migration Values

We recommend you fill in this table, then print it out and keep it with you during the migration.

Table 1 Migration Values

Field
Format

Remote Archive server hostname

 

Username to access remote archive server

 

Password for username to access remote archive server

 

Pathname location of archive

 

SNMP configuration

 

MCU IP Address

 

MCU IP Address

 

MCU IP Address

 

MCU IP Address

 

MCU IP Address

 

Determining Which Procedure to Follow

Depending on the configuration of your Application Server, follow one of these steps:

If your Application Server is in a failover deployment:

and you want to continue MeetingPlace scheduling—follow the procedure in the Migrating a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling. After the migration, reconfigure the system for database replication.

and you want to continue Cisco WebEx scheduling—follow the procedure in Migrating a Failover Deployment in a System with WebEx Scheduling.

If your Application Server is in a Reservationless Single Number Access (RSNA) deployment, then see Migrating Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment. In Release 8.6, RSNA functionality is replaced with the multinode configuration.

If your Application Server does not meet either of the above conditions, follow the procedure in either the Migrating the Application Server by Using the Console or the Migrating the Application Server Remotely.

Migrating the Application Server by Using the Console

Before You Begin

Complete Determining Which Procedure to Follow.

Take the Audio Blade offline.

Procedure


Step 1 Go to Cisco.com and find the migration binary: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6 > Unified MeetingPlace Application Server. The naming convention will be similar to CUMP_AppServerUpgrade_<version>.bin, where <version> is the version number to which you are migrating.


Note Be sure to use the exact CUMP_AppServerUpgrade_<version>.bin file for the version to which you are migrating. For example, if you are migrating to Release 8.6, then use the upgrade file for Release 8.6. If you are migrating to Release 8.5.3, then use the upgrade file for Release 8.5.3, and so on.


Step 2 Save the file to a convenient location.

Step 3 Enter md5sum CUMP_AppServerUpgrade_<version>.bin to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.

Step 4 Sign in to the Application Server command-line interface as the root user.

Step 5 Transfer the CUMP_AppServerUpgrade_<version>.bin file to the Application Server.

We recommend saving the file to the /partB directory, as it has a lot of free space.

Step 6 Enter sh ./CUMP_AppServerUpgrade_<version>.bin to execute the file.

The migration program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the migration program displays a message listing the previous version found on the system.


Note If the migration program does not find any previous versions of the Application Server software, the migration program displays an error message and you must quit the migration.


Step 7 Select Next after reading the Introduction.

Step 8 Select Yes to confirm the migration.

Step 9 Enter the information for your remote migration archive server and select Next.


Note For the migration, we suggest you use a different archive server than what you configured for your legacy system.



Note Be sure the user selected below has the appropriate permission to write the migration data to the archive server.


Hostname of the migration archive server

Pathname to the directory where the data archive is written

Username to connect to the migration archive server

Password for the user to connect to the migration archive server


Note If you do not have a remote migration server available, you can use a local Cisco Unified MeetingPlace Application Server as a migration point. To use the Application Server, enter localhost as a hostname, /home/mpxadmin/ as a pathname, and the mpxadmin credentials for authentication. Once the script is finished, retrieve the migration file from the /home/mpxadmin/ directory of the application server and store it on a remote location.


The migration program runs a validation check and archives and transfers the Application Server data, required for migration, to the archive server. This process takes a half hour to two hours to complete. A migrateBackup.tar.gz file is created at the archive location.


Note If you get an error message during the migration archive creation, see MeetingPlaceUpgradeLog.txt in the /tmp directory.


Step 10 You see an error message stating that the profile, with a username of appuser-internal, will be removed. Select Yes to remove this profile, or select No to cancel the migration and rename your existing appuser-internal profile.

Step 11 Select OK to acknowledge the message about writing down the IP addresses for each MCU.

Step 12 Select OK to acknowledge the message about writing down the SNMP configuration.

You will need to configure SNMP following the migration.

Step 13 Select OK when the migration archive is complete.

The migration program terminates.

Step 14 Install the Cisco Unified MeetingPlace 8.6 Application Server on your existing hardware, or on a virtual machine on a Cisco UCS B-Series or C-Series Server, or a new Cisco MCS. (You may also install it on the exact equivalent server from a different manufacturer.) See the Installing the Application Server Software module.


Caution If you want to migrate to Release 8.6, then you must first install the Release 8.5.5 FCS Application Server. Secondly, upgrade the Application Server to Release 8.6, by following the instructions in Upgrading to Cisco Unified MeetingPlace Release 8.6. You cannot install the Release 8.5.3 or later Application Server without first installing the Release 8.5.2 Application Server.


Note The Cisco Unified MeetingPlace version on your Release 8.6 Application Server must match the version of the upgrade file you used in Step 1 of this procedure.



Note If you plan to use new hardware and retain your existing hostname/IP address for the Application Server, then be sure to power off your legacy Application Server before installing the 8.6 Application Server.


Step 15 If you installed the Application Server on a new machine, then use the net command to continue to use the same hostname and IP address as your legacy Application Server. If, however, your new machine has a different IP address, then add the IP address of the new machine to the DNS server (so the new IP address is also mapped to the hostname of the legacy Application Server machine).

By making the change on the DNS server, all requests to this hostname is directed to the new IP address on the Release 8.6 Application Server. No change is required in the Microsoft Outlook plug-in on the client, and users can access both legacy and new meetings.

Step 16 Sign in to the Application Server CLI as the root user.

Step 17 Navigate to the $MP_DATABASE/db-maintenance directory.

Step 18 Enter ./install_migration.bin to start the migration restore process.

The migration program displays a migration restore data screen.

Step 19 Select Enter to begin the migration restore process or select 2 to cancel the migration.

Step 20 Enter the following or select Enter to use the default:

Remote migration archive server hostname or IP address

Username to connect to the remote migration archive server host

Password to connect to the remote migration archive server host

Pathname to the migration archive

Step 21 Select Enter to acknowledge the message about adding the blades to the HMS after migration.

Step 22 Select Enter to acknowledge the message about manually adding the SNMP configuration, following migration.

The migration program confirms the archive server setting which has the migration data file, migrateBackup.tar.gz. The process then migrates the data from the archive server to Release 8.6 system. It may take half an hour to two hours.

When this process is done, a completed message is displayed. (An error message is displayed if the migration restore process fails.)

Step 23 Select Enter to acknowledge the message about email templates.

Your existing templates have been copied to the /mpx-record/migrateBackup directory.

Step 24 Select Enter to terminate the installer program.

Step 25 Put the Audio Blade back online.

Step 26 Sign in to the Cisco Unified MeetingPlace Administration Center page on the Cisco Unified MeetingPlace 8.6 Application Server as a system administrator.

Step 27 Select Maintenance > Backup and Archive.

Step 28 Verify your routine backup and archive configuration. Turn on automatic backups and archiving.


Note We recommend you select a different archive location for your Release 8.6 system, to avoid overwriting your legacy system archive and backup data.



Note Release 8.6 only supports SSH/rsync archiving. Be sure to set up an archive server that supports this archiving method.


Choose Yes in the Enable automatic backup field.

Choose Yes in the Enable automatic archiving field.

Step 29 On the Cisco Unified MeetingPlace Administration Center page, select Cisco WebEx Configuration. Then select Configure WebEx.


Troubleshooting Tips

See Troubleshooting the Application Server Software Migration.

Related Topics

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

Synchronizing Audio Blade Meeting Types with the Template Audio Blade in the Changing Values for the Hardware Media Server module

Application Commands for the Application Server in the "Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server" section of the Configuration Guide for Cisco Unified MeetingPlace.

Cisco supports single-node deployments with WebEx scheduling in Release 8.6. For additional benefits, including RSNA functionality, and increased meetings capacity, you may choose to install a multinode deployment. For more information, see "Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace..

What To Do Next

1. If you are migrating to Release 8.6, then skip to the next step. If you are remaining at Release 8.5.2, then install any applicable patches. Go to Cisco.com: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6 > Unified MeetingPlace Application Server-8.6.

Be sure to read the README for information about the patch, and instructions for installing the patch.

2. Completing the Application Server Software Migration

Migrating the Application Server Remotely

When you migrate the Application Server software remotely, the migration status is limited. We recommend that you migrate the Application Server at the console if possible.

Restrictions

You must use the screen to perform a remote migration.

Before You Begin

Complete Determining Which Procedure to Follow.

Take the Audio Blade offline.

Procedure


Step 1 Go to Cisco.com and find the migration binary: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6 > Unified MeetingPlace Application Server. The naming convention will be similar to CUMP_AppServerUpgrade_<version>.bin, where <version> is the version number to which you are migrating.


Note Be sure to use the exact CUMP_AppServerUpgrade_<version>.bin file for the version to which you are migrating. For example, if you are migrating to Release 8.6, then use the upgrade file for Release 8.6. If you are migrating to Release 8.5.3, then use the upgrade file for Release 8.5.3, and so on.


Step 2 Save the file to a convenient, local location.

Step 3 Enter md5sum CUMP_AppServerUpgrade_<version>.bin to determine the checksum of the file that you downloaded. Compare this value to the checksum value of the file that is posted on the download page on Cisco.com.

Step 4 Transfer the CUMP_AppServerUpgrade_<version>.bin file to the Cisco Unified MeetingPlace Application Server using SCP file transfer.

We recommend saving the file to the /partB directory, as it has a lot of free space.

Step 5 Using an SSH client, sign in as the user called mpxadmin.

Step 6 Enter screen -S mp_migrate to create and attach to a screen named mp_migrate.

Step 7 Change to the root user by entering su - and enter the root password.

Step 8 From the CLI, navigate to the directory where you saved the /partB/CUMP_AppServerUpgrade_<version>.bin file.

Step 9 Enter sh /partB/CUMP_AppServerUpgrade_<version>.bin to execute the file.

The migration program checks to see if there are any previous versions of the Application Server software installed. If there is at least one previous version, the migration program displays a message listing the previous version found on the system.


Note If the migration program does not find any previous versions of the Application Server software, the migration program displays an error message and you must quit the migration.


Step 10 Select Next after reading the Introduction.

Step 11 Select Yes to confirm the migration.

Step 12 Enter the information for your remote migration archive server and select Next.


Note For the migration, we suggest you use a different archive server than what you configured for your legacy system.



Note Be sure the user selected below has the appropriate permission to write the migration data to the archive server.


Hostname of the migration archive server

Pathname to the directory where the data archive is written

Username to connect to the migration archive server

Password for the user to connect to the migration archive server


Note If you do not have a remote migration server available, you can use the local Cisco Unified MeetingPlace Application Server as a migration point. To use the Application Server, enter localhost as a hostname, /home/mpxadmin/ as a pathname and the mpxadmin credentials for authentication. Once the script is finished, retrieve the migration file from the /home/mpxadmin/ directory of the application server and store it on a remote location.


The migration program runs a validation check and archives and transfers the Application Server data to the archive server. This process takes one to two hours to complete. A migrateBackup.tar.gz file is created at the archive location.


Note If you get an error message during the migration archive creation, see MeetingPlaceUpgradeLog.txt in the /tmp directory.


Step 13 You see an error message stating that the profile, with a username of appuser-internal, will be removed. Select Yes to remove this profile, or select No to cancel the migration and rename your existing appuser-internal profile.

Step 14 Select OK to acknowledge the message about writing down the IP addresses for each MCU.

Step 15 Select OK to acknowledge the message about writing down the SNMP configuration.

You will need to configure SNMP following the migration.

Step 16 Select OK when the migration archive is complete.

The migration program terminates.

Step 17 Install the Cisco Unified MeetingPlace 8.6 Application Server on your existing hardware, or on a virtual machine on a Cisco UCS B-Series or C-Series Server, or a new Cisco MCS. (You may also install it on the exact equivalent server from a different manufacturer.) See the Installing the Application Server Software module.


Caution If you want to migrate to Release 8.6, then you must first install the Release 8.6 FCS Application Server. Secondly, upgrade the Application Server to Release 8.6, by following the instructions in Upgrading to Cisco Unified MeetingPlace Release 8.6. You cannot install the Release 8.5.3 or later Application Server without first installing the Release 8.5.2 Application Server.


Note The Cisco Unified MeetingPlace version on your Release 8.6 Application Server must match the version of the upgrade file you used in Step 1 of this procedure.



Note If you plan to use new hardware and retain your existing hostname/IP address for the Application Server, then be sure to power off your legacy Application Server before installing the 8.6 Application Server.


Step 18 If you installed the Application Server on a new machine, then use the net command to continue to use the same hostname and IP address as your legacy Application Server. If, however, your new machine has a different hostname and IP address, then add the IP address of the new machine to the DNS server (so the new IP address is also mapped to the hostname of the legacy Application Server machine).

By making the change on the DNS server, all requests to this hostname is directed to the new IP address on the Release 8.6 Application Server. No change is required in the Microsoft Outlook plug-in on the client, and users can access both legacy and new meetings.

Step 19 Open a separate SSH session to the Application Server as the mpxadmin user.

Step 20 Enter screen -S mp_migrate to create and attach to a screen named mp_migrate.

Step 21 Change to the root user by entering su - and enter the root password.

Step 22 Navigate to the $MP_DATABASE/db-maintenance directory.

Step 23 Enter ./install_migration.bin to start the migration restore process.

The migration program displays a migration restore data screen. You see intermittent prompts, showing the progress. Depending on the size of your database, this can take up to several hours to complete.

Step 24 Select Enter to begin the migration restore process or select 2 to cancel the migration.

Step 25 Enter the following or select Enter to use the default.

Remote migration archive server hostname or IP address

Username to connect to the remote migration archive server host

Password to connect to the remote migration archive server host

Pathname to the migration archive

Step 26 Select Enter to acknowledge the message about adding the blades to the HMS after migration.

Step 27 Select Enter to acknowledge the message about manually adding the SNMP configuration, following migration.

The migration program confirms the archive server setting which has migration data file, migrateBackup.tar.gz. The process then migrates the data from the archive server to Release 8.6 system. It may take half an hour to two hours.

When this process is done, a completed message is displayed. (An error message is displayed if the migration restore process fails.)

Step 28 Select Enter to acknowledge the message about email templates.

Your existing templates have been copied to the /mpx-record/migrateBackup directory.

Step 29 Select Enter to terminate the installer program.

Step 30 Put the Audio Blade back online.

Step 31 Sign in to the Cisco Unified MeetingPlace Administration Center page on the Cisco Unified MeetingPlace 8.6 Application Server as a system administrator.

Step 32 Select Maintenance > Backup and Archive.

Step 33 Verify your routine backup and archive configuration. Turn on automatic backups and archiving.


Note We recommend you select a different archive location for your Release 8.6 system, to avoid overwriting your legacy system archive and backup data.



Note Release 8.6 only supports SSH/rsync archiving. Be sure to set up an archive server that supports this archiving method.


Choose Yes in the Enable automatic backup field.

Choose Yes in the Enable automatic archiving field.


Troubleshooting

If the SSH remote session disconnects while you are migrating the Application Server, follow these steps to reattach to the installation screen and continue the migration:

1. Using an SSH client, sign in as the user called mpxadmin.

2. Enter screen -ls to find out the full name of the screen created in the preceding procedure. The full name of the screen consists of an identifier followed by a dot and then the name that you used. For example, the full screen name might be 1665.mp_migrate.

3. Enter screen -rD full_screen_name to reattach to the installation screen.

Related Topics

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

Synchronizing Audio Blade Meeting Types with the Template Audio Blade in the Changing Values for the Hardware Media Server module

Application Commands for the Application Server in the Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server

Cisco supports single-node deployments with WebEx scheduling in Release 8.6. For additional benefits, including RSNA functionality, and increased meetings capacity, you may choose to install a multinode deployment. For more information, see "Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.

What To Do Next

1. If you are migrating to Release 8.6, then skip to the next step. If you are remaining at Release 8.5.2, then install any applicable patches. Go to Cisco.com: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6 > Unified MeetingPlace Application Server-8.6.

Be sure to read the README for information about the patch, and instructions for installing the patch.

2. Completing the Application Server Software Migration

Migrating Application Servers that are Used in a Failover Deployment

Pick the procedure appropriate for your existing deployment:

Migrating a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling

Migrating a Failover Deployment in a System with WebEx Scheduling

Migrating a Failover Deployment in an Audio-Only System or a System with MeetingPlace Scheduling

Follow this procedure if you are migrating a failover deployment with:

Cisco Unified MeetingPlace scheduling to a Release 8.6 system with Cisco Unified MeetingPlace scheduling

Audio-only system to a Release 8.6 audio-only system

Before You Begin

Complete Determining Which Procedure to Follow for the active Application Server.


Note The following nomenclature is used for clarity in the procedure below: we assume node 1 is the active Application Server in the existing system and node 2 is the standby Application Server. If this is not the case, then refer to your existing documentation and use the mp_replication status command to determine which server is node 1 and which server is node 2. The node number is indicated in the output in the Node column.


The overall procedure is described in the summary steps. The detailed procedure follows, with step-by-step instruction.

Summary Steps

1. Turn off and tear down replication between the active and standby Application Servers.

2. Convert the active server to single server mode and migrate it to Release 8.6.

3. Convert the newly migrated Release 8.6 Application Server to failover (standby) mode.

4. Convert the remaining legacy Application Server to active, then convert it to single server mode and migrate it to Release 8.6.

5. Set up replication between the two Release 8.6 Application Servers.

Procedure


Step 1 Sign in to the CLI of node 1 (active server) as the mpxadmin user. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 2 Enter su - to switch to the root user.

Step 3 Enter mp_replication status on node 1 (active server) to ensure that all database changes have been synchronized.

The system displays the queue column as zeroes.

Host Name

Host IP Address

Replication Type

Site

Node

State

Status

Queue

ServerA

<Server_A_IP>

Local

1

1

Active

Local

0

ServerB

<Server_B_IP>

Intra-Site

1

2

Active

Connected

0


Step 4 On node 1, switch off replication between the two Application Servers, where node_2_eth0:0 is the eth0:0 address for node 2.

Release 7.1 or Release 8.0 MR1—Enter mp_replication switchOFF [-v] on node 1

All other releases—Enter mp_replication switchOFF -r node_2_eth0:0 on node 1

Step 5 On node 1 (active server), tear down the replication setup with the remote Application Server, where node_2_eth0:0 is the eth0:0 address for node 2.

Release 7.1 or Release 8.0 MR1—Enter mp_replication teardown [-v] on node 1

All other releases—Enter mp_replication teardown -r node_2_eth0:0 on node 1

Step 6 Sign in to the Cisco Unified MeetingPlace Administration Center and select Maintenance > Backup and Archive. Create a backup and archive and save the configuration data on node 1 (active server).

We recommend creating a backup and archive in case you need to revert to your legacy system. If you are using new hardware, then disregard this step.

Step 7 Enter failoverUtil setDeployment singleServer to change the mode of node 1 to SingleServer.

Step 8 Install the Application Server on node 1. See Migrating the Application Server by Using the Console.


Note At this time, we strongly recommend you validate the migration of the Application Server on node 1. See Testing that the Migrated System Works Correctly.


Step 9 Enter failoverUtil setDeployment failover on node 1 to change the mode of node 1 to failover.


Note This disables the eth0 interface of node 1, so that node 2 can become active.


Step 10 Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 11 Enter su - to switch to the root user.

Step 12 Enter failoverUtil setServer active on node 2 to change its mode from standby to active.

Step 13 On node 2, tear down the replication setup with the remote Application Server, where node_1_eth0:0 is the eth0:0 address for node 1.

Release 7.1 or Release 8.0 MR1—Enter mp_replication teardown [-v] on node 2

All other releases—Enter mp_replication teardown -r node_1_eth0:0 on node 2

Step 14 Enter failoverUtil setDeployment singleServer on node 2 to change its mode to SingleServer.

Step 15 Install the Application Server on node 2. See the Migrating the Application Server by Using the Console.

Step 16 Enter failoverUtil setDeployment failover on node 2 to change its mode to failover (standby).

At this point, both Application Servers are in standby mode.

Step 17 Sign in to the CLI of node 2. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 18 Enter mp_replication init -n 2 -r <node1-eth0:0-hostname> [-v] to initialize database replication.

Step 19 Sign in to the CLI of node 1. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 20 Enter the following to initialize and start database replication:

mp_replication init -n 1 -r <node2-eth0:0-hostname> [-v]

mp_replication switchON

Step 21 Enter failoverUtil setServer active on node 1 to change its mode to active.

Node 1 is the active Application Server and node 2 is the standby Application Server.


Related Topics

Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module

Backing Up, Archiving, and Restoring Data on the Application Server module

Migrating the Application Server by Using the Console

Migrating the Application Server Remotely

What To Do Next

Completing the Application Server Software Migration

Migrating a Failover Deployment in a System with WebEx Scheduling

Follow this procedure if you are migrating a failover deployment with Cisco WebEx scheduling to a Release 8.6 system with Cisco WebEx scheduling. You will migrate your existing system, then create a multinode deployment, enabling active/active resiliency.

Before You Begin

Complete Determining Which Procedure to Follow for the active Application Server.


Note The following nomenclature is used for clarity in the procedure below: we assume node 1 is the active Application Server in the existing system and node 2 is the standby Application Server. If this is not the case, then refer to your existing documentation and use the mp_replication status command to determine which server is node 1 and which server is node 2. The node number is indicated in the output in the Node column.


The overall procedure is described in the summary steps. The detailed procedure follows, with step-by-step instruction.

Summary Steps

1. Turn off and tear down replication between the active and standby Application Servers.

2. Convert the active server to single server mode and migrate it to Release 8.6.

3. Install the Release 8.6 Application Server on node 2 and configure a multinode system.

Procedure


Step 1 Sign in to the CLI of node 1 (active server) as the mpxadmin user. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 2 Enter su - to switch to the root user.

Step 3 Enter mp_replication status on node 1 (active server) to ensure that all database changes have been synchronized.

The system displays the queue column as zeroes.

Host Name

Host IP Address

Replication Type

Site

Node

State

Status

Queue

ServerA

<Server_A_IP>

Local

1

1

Active

Local

0

ServerB

<Server_B_IP>

Intra-Site

1

2

Active

Connected

0


Step 4 On node 1, switch off replication between the two Application Servers, where node_2_eth0:0 is the eth0:0 address for node 2.

Release 7.1 or Release 8.0 MR1—Enter mp_replication switchOFF [-v] on node 1

All other releases—Enter mp_replication switchOFF -r node_2_eth0:0 on node 1

Step 5 On node 1, tear down the replication setup with the remote Application Server, where node_2_eth0:0 is the eth0:0 address for node 2.

Release 7.1 or Release 8.0 MR1—Enter mp_replication teardown [-v] on node 1

All other releases—Enter mp_replication teardown -r node_2_eth0:0 on node 1

Step 6 Sign in to the Cisco Unified MeetingPlace Administration Center and select Maintenance > Backup and Archive. Create a backup and archive and save the configuration data on node 1 (active server).

We recommend creating a backup and archive in case you need to revert to your legacy system. If you are using new hardware, then disregard this step.

Step 7 Enter failoverUtil setDeployment singleServer to change the mode of node 1 to SingleServer.

Step 8 Install the Application Server on node 1. See Migrating the Application Server by Using the Console.


Note At this time, we strongly recommend you validate the migration of the Application Server on node 1. See Testing that the Migrated System Works Correctly.


Step 9 Install the Application Server on node 2. See Installing the Application Server Software.


Note If you are planning to install Cisco Unified MeetingPlace Release 8.6 or later, then first install Release 8.6 on the Application Server, by following the instructions in this module. Then, upgrade your Release 8.5.2 Application Server to Release 8.5.x, by following the instructions in Upgrading to Cisco Unified MeetingPlace Release 8.6.



Related Topics

Using the Command-Line Interface (CLI) on the Cisco Unified MeetingPlace Application Server module

Backing Up, Archiving, and Restoring Data on the Application Server module

Migrating the Application Server by Using the Console

Migrating the Application Server Remotely

What To Do Next

1. Completing the Application Server Software Migration

2. Configure your system in a multinode deployment. See "Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.

Migrating Application Servers that are Used in a Reservationless Single Number Access (RSNA) Deployment

RSNA functionality is replaced with the multinode configuration in Release 8.6. If you have an audio-only system, or have a deployment with Cisco Unified MeetingPlace scheduling and want this functionality, then complete the following procedure.

Before You Begin

Complete Determining Which Procedure to Follow for the Application Server that you will migrate.


Note The following nomenclature is used for clarity in the procedure below: site1 is the server in site 1 and site 2 is the server in site 2. In this procedure, we will migrate the server in site 1, though you can choose to migrate the server in site 2 instead.


Procedure


Step 1 Sign in to the CLI of the server in site 1 as the mpxadmin user. If you are signing in remotely, use the eth0:0 IP address or hostname.

Step 2 Enter su - to switch to the root user.

Step 3 Enter mp_replication status on the site 1 server to ensure that all database changes have been synchronized.

The system displays the queue column as zeroes.

Host Name

Host IP Address

Replication Type

Site

Node

State

Status

Queue

ServerA

<Server_A_IP>

Local

1

1

Active

Local

0

ServerB

<Server_B_IP>

Inter-Site

2

1

Active

Connected

0


Step 4 On the server in site 1, switch off replication between the two Application Servers, where site_2_eth0:0 is the eth0:0 address for the server in site 2.

Release 7.1 or Release 8.0 MR1—Enter mp_replication switchOFF [-v] on the server in site 1

All other releases—Enter mp_replication switchOFF -r site_2_eth0:0 on the server in site 1

Step 5 On the server in site 1, tear down the replication setup with the remote Application Server, where site_2_eth0:0 is the eth0:0 address for the server in site 2.

Release 7.1 or Release 8.0 MR1—Enter mp_replication teardown [-v] on the server in site 1

All other releases—Enter mp_replication teardown -r site_2_eth0:0 on the server in site 1

Step 6 Sign in to the Cisco Unified MeetingPlace Administration Center and select Maintenance > Backup and Archive. Create a backup and archive and save the configuration data on the server in site 1.

We recommend creating a backup and archive in case you need to revert to your legacy system. If you are using new hardware, then disregard this step.

Step 7 Complete the migration procedure in the Migrating Using the MPtoWebEx CSV Converter module for the server in site 1.

Step 8 Install a new Release 8.6 Application Server and configure it with a newly provisioned Cisco WebEx site.

Step 9 Add at least one additional node and configure a multinode system.


"Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace

What to Do Next

Completing the Application Server Software Migration

Completing the Application Server Software Migration

Updating Email Notifications

Only complete this section if you are migrating a Cisco Unified MeetingPlace system with MeetingPlace scheduling. If you migrated a Cisco Unified MeetingPlace system with WebEx scheduling, then go to How to Test the Application Server Software Migration.

Merging Email Notification Templates

Restoring Email Server Configuration

Merging Email Notification Templates

The migration program checks the version of the email templates when migrating to Release 8.6. If the version is same, then the migration programs restore the email template from the prior release. If the version is different, the migration program does not restore those email templates. Instead, it restores the email template to a back up directory, /mpx-record/migrateBackup/opt/cisco/meetingplace/var.<previous_version_number>. Then, it displays a message asking you to customize the email templates manually.

See "Customizing Email Notifications for Cisco Unified MeetingPlaceon MeetingPlace-Scheduled and Audio-Only Deployments" in the Configuration Guide for Cisco Unified MeetingPlace"for complete information on customizing your email notification templates.

Restoring Email Server Configuration

The migration program checks the version of SMTP/Exchange server configuration, when migrating to Release 8.6. If the version is same, then the migration programs restores the SMTP/Exchange server configuration from the prior release. If the version is different, the migration program does not restore the SMTP/Exchange server configuration. Instead, it restores the SMTP/Exchange server configuration to a back up directory, /mpx-record/migrateBackup.

If a message is displayed, asking you to customize SMTP/Exchange server manually, then complete the following procedure.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select System Configuration > Email Notifications > SMTP Server Configuration.

Step 3 Enter values in all fields.

Step 4 Select Save.

Step 5 Select System Configuration > Email Notifications > Exchange Server Configuration.

Step 6 Enter values in all fields.

Step 7 Select Save.


Related Topics

SMTP Server Configuration Page in the "Administration Center Page References for Cisco Unified MeetingPlace" section of the Configuration Guide for Cisco Unified MeetingPlace

Exchange Server Configuration Page in the "Administration Center Page References for Cisco Unified MeetingPlace" section of the Configuration Guide for Cisco Unified MeetingPlace

How to Test the Application Server Software Migration

After migrating the Application Server software, perform these tests to ensure that the migration was successful.

Checking the System Status in the Installing the Application Server Software module

Testing the Basic Installation in the Installing the Application Server Software module

Troubleshooting the Application Server Software Installation in the Installing the Application Server Software module

Troubleshooting the Application Server Software Migration

Error Message    There is not enough disk space to update the Application Server 
software.

Recommended Action    Contact Cisco TAC, who can help you identify and remove unnecessary files from the relevant partitions.

Problem   The migration installer does not have enough space in the / directory.

Explanation    You downloaded the migration binary onto your desktop, which stores it in the /home/user_name/Desktop directory. That directory uses the space from the / directory.

Solution   Remove the downloaded file from the /home/user_name/Desktop directory to free up space.

Error Message    There is not enough space to extract the upgrade installer file.

Recommended Action    Ensure that there are no large, extraneous files in the /opt partition.

Error Message    Cannot upgrade the Application Server software because there is no 
earlier version already installed on the server.

Explanation    You must have at least one previous version on your system before you can migrate.

Recommended Action    Install the Application Server software.

Related Topics

Installing the Application Server Software module

Error Message    The installer has found an equal or newer version this update.

Explanation    You must have at least one older version of the Application Server software on your system before you can migrate.

Recommended Action    Install a newer version of the Application Server software.

Related Topics

Installing the Application Server Software module

Error Message    Warning - Not enough memory. If you continue, system performance may 
be impacted. It is highly recommended that you exit the installation and install 
more memory.

Explanation    We recommend that the server that you migrate have the amount of memory mentioned for that server in the system requirements.

Recommended Action    Install more memory.

Related Topics

System Requirements for Cisco Unified MeetingPlace Release 8.6 at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html

Problem   The migration program says that the database is corrupted.

Solution   Run the /etc/init.d/mpx_db status command to check the status of the database.

Related Topics

How to Migrate the Application Server Software

How to Migrate the Web Server


Note Do not complete this section if you have an existing deployment with WebEx scheduling and MeetingPlace-driven User Management. Go to the next section, How To Install the Cisco WebEx Node for MCS for a Migrated System.


To migrate the Web Server, perform the following tasks in this order:

1. Read the migration prerequisites. See Preparing to Migrate the Web Server.

2. Back up your Web Server data. See Backing Up the Web Conferencing Data Before a Migration.


Note If you are installing a new Web Server, then complete your data back up and the Cisco Unified MeetingPlace Windows operating system installation (Step 3) in parallel, to save some time.


3. Install the Cisco Unified MeetingPlace Windows operating system on your Release 8.6 Web Server MCS or on a virtual machine on a Cisco UCS B-Series or UCS C-Series Server.

For more information on creating a virtual machine, see the Installing on a Virtual Machine module.

4. Restore the Web Server data on your new machine. See Restoring the Web Server Data.

5. Install the Cisco Unified MeetingPlace 8.6 Web Server on the new machine. See Installing the Web Server Software.

6. See Reconfiguring the Application Server Connection in the Gateway SIM.

7. See Connecting the Application Server to the Web Server.

8. If you want to allow guests to be able to dial out to other users, set the parameters for the guest profile. See Allowing Guest Users to Dial Out.

Preparing to Migrate the Web Server


Caution Do not run any other processes or tasks on your systems during a migration.

Migrate the Application Server before you install the Web Server software.

Obtain the Cisco Unified MeetingPlace Release 8.6 web conferencing backup utility to back up and restore your Web Server data.


Note Be sure to use the Release 8.6 web conferencing backup utility to migrate your Web Server data; not the backup utility with your existing Cisco Unified MeetingPlace system.


Do not interrupt the installation during the automatic system shutdown or reboot.

If your system has multiple Web Servers, you must migrate them all to the same version. You can migrate them in any order.

We recommend that you only install the Web Server software after hours. To avoid losing recordings, do not install the Web Server database if there are any meetings that are currently in session that have recordings or if any meetings with recordings have recently ended, because the system may not have posted the recording yet posted to the attachment and recording page.

Backing Up the Web Conferencing Data Before a Migration

The Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard generates an executable that migrates configuration settings and meeting information from one Web Server to another. If you have a load-balancing cluster of Web Servers, complete the following procedures on each server in the cluster.


Note The restore file generated by the Cisco Unified MeetingPlace Web Conferencing Backup or Restore Wizard cannot be used to revert to your existing release if the migration fails. You will need to have a manual backup created if you need to revert to the original release. For more information, see module How to Back Up and Restore MPWEB SQL Database in the Configuring the SQL Server for the Cisco Unified MeetingPlace Web Server module.



Note If you are planning to install the Cisco Unified MeetingPlace Release 8.6 Web Server on the same hardware as the legacy Cisco Unified MeetingPlace Web Server, then back up your Web conferencing data on a different server.


Cisco Unified MeetingPlace Web Conferencing Backup Utility

Specifying a Different Backup Destination Folder

Backing Up Data from the Source Web Server

Cisco Unified MeetingPlace Web Conferencing Backup Utility


Note The Cisco Unified MeetingPlace web conferencing backup utility is included in the Cisco Unified MeetingPlace 8.6 Web Conferencing DVD. Copy it to your existing Cisco Unified MeetingPlace Web Server to execute your backup.



Note If you are installing Release 8.6, go to http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6. Obtain CiscoUnifiedMeetingPlaceWebConferencingBackup.exe for your release.


The Web Conferencing backup utility uses the Microsoft Windows backup tool as its underlying backup engine. Since the Windows backup tool does not perform any compression, the total size of your projected backup equals the total data size of the files and folders that you want to back up. You may use the Properties function in Windows Explorer to get the size of each folder and add them together to get the total size of back up data.

By default, the backup utility backs up data from the following folders:

C:\Program Files\Microsoft SQL Server\MSSQL\Data

C:\Program Files\Cisco Systems\MPWeb\Meetings

C:\Program Files\Cisco Systems\MPWeb\WebConf\content\7

The \MPWeb\WebConf\content\7 folder contains an extremely large number of folders and files.

These folders are based on the default set up of the local SQL Server database on the Cisco MCS server and on the lack of a shared storage location.


Note The Web Conferencing backup utility cannot back up data from a shared storage location. To back up such data, manually navigate to the location of your shared storage location, copy the contents of the entire folder, then paste them into another location.


The utility then stores the backed up data in the following folder by default:

C:\Program Files\Cisco Systems\MPWeb\MPBackup

If you run the backup utility in command line mode, you can specify a different location. See Specifying a Different Backup Destination Folder.

Specifying a Different Backup Destination Folder

Complete this procedure if you want to set up your own destination backup folder, where your backed up data will be stored. If you do not do this procedure, the Web Conferencing backup utility will store its backed up data in C:\Program Files\Cisco Systems\MPWeb\MPBackup by default.

If you choose to use the default destination folder, go to Backing Up Data from the Source Web Server.

Procedure


Step 1 Open a DOS command window.

a. Select Start > Run.

b. Enter cmd.

Step 2 Navigate to the folder where the Release 8.6 backup utility is located. Example: C:\Temp\mpweb_software>

Step 3 Enter the location of your backup destination folder by reviewing the following examples:

Example 1: 

If you enter ciscounifiedmeetingplacewebconferencingbackup.exe f:

the backup utility will create a folder called f:\MPBackup and use it as the destination folder for your backed up data.

Example 2: 

`If you enter ciscounifiedmeetingplacewebconferencingbackup.exe f:\backup

the backup utility will create a folder called f:\backup\MPBackup and use it as the destination folder for your backed up data.


Note If you specify f:\ instead of f:, or f:\backup\ instead of f:\backup, the backup utility will fail and abort. In other words, do not include the \ as the last character in your path specification.


Example 3: 

Specify your destination backup folder by using a UNC path:

Enter ciscounifiedmeetingplacewebconferencingbackup.exe \\hostname\temp


Backing Up Data from the Source Web Server

As a precaution, complete this procedure even if you will be using the same hardware for the Cisco Unified MeetingPlace 8.6 Web Server.

Before You Begin

Manually estimate the total data size of your backup operation to ensure that your destination has enough disk space to hold the backed up data files.

Manually stop the MSSQLSERVER service and disable the service until the backup is done.


Note This backup takes 15-30 minutes, depending on the number of users, meetings, attachments, and recordings. For example, the backup takes about 10 minutes for a system with about 300,000 profile users and 400,000 meetings, with a small number of attachments and recordings.


Procedure


Step 1 On your existing Cisco Unified MeetingPlace Web Server, exit any open applications.

Step 2 Copy CiscoUnifiedMeetingPlaceWebConferencingBackup.exe from the Cisco Unified MeetingPlace 8.6 Web Conferencing DVD and copy it to the existing Cisco Unified MeetingPlace Web Server.


Note Be sure to use CiscoUnifiedMeetingPlaceWebConferencingBackup.exe for the release to which you are migrating. If you are installing Release 8.6 go to http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6. Obtain CiscoUnifiedMeetingPlaceWebConferencingBackup.exe for your release.


Step 3 Double-click CiscoUnifiedMeetingPlaceWebConferencingBackup.exe.


Note To store the backup data in a different location, run the following from the command prompt: CiscoUnifiedMeetingPlaceWebConferencingBackup <location>


Step 4 Click Next in the first dialog box of the Backup or Restore Wizard and follow the prompts.

The Backup or Restore Wizard creates a restore file called CiscoUnifiedMeetingPlaceWebConferencingRestore.exe that you can use on a separate Web Server.

Step 5 Set the MSSQLSERVER service back to its original settings.



Note You do not need to back up any notification templates. The system copies all of these notification templates to a backup directory under /opt/cisco/meetingplace/var<legacy_release_number>.


Restoring the Web Server Data

Restrictions

Do not run any other processes or tasks on your systems during a migration. This can potentially affect the data that is being transferred from one system to another.

You cannot migrate the Cisco Unified MeetingPlace Web Server when the Application Server is being rebooted. The Application Server must be running before you can migrate the Web Server.

To ensure that the Application Server is running, sign in to the CLI as mpxadmin and enter swstatus. For more information about using the CLI, see the Configuration Guide for Cisco Unified MeetingPlace Release 8.6 or the online help in the administrator interface.

Click-to-attend links in previous e-mail notifications (only if the Cisco Unified MeetingPlace Release 8.6 Web Server has the same hostname (FQDN) as the legacy Web Server). If the hostname is changed, then a CNAME with the old FQDN can be added in DNS to point to the new primary Web Server. This enables CTA links to function correctly when the hostname is changed.

Before You Begin

Ensure that you completed Backing Up Data from the Source Web Server.

Copy the backup directory from the source web server to the destination web server where you want to restore the data.

This backup directory includes MeetingPlacebackup.bkf and CiscoUnifiedMeetingPlaceWebConferencingRestore.exe.

Ensure that the migration to the new 8.6 Application Server has already been completed.

(Release 8.5.1 only) Ensure that the Microsoft SQL Server account on the new Web Server uses the same username and password as the SQL Server account on the source Web Conferencing Server

Install the Cisco Unified MeetingPlace Windows operating system on the Release 8.6 Web Server.


Note If you are installing on an Cisco MCS 7835-I2 or 7845-I2 then you may need to upgrade or downgrade the firmware before installing the MP Windows OS. For the steps to correct this problem, see Updating the Firmware on a Cisco MCS 7835-I2 or 7845-I2. For background information about the problem, see http://www.cisco.com/en/US/products/ps6509/products_tech_note09186a008059a81d.shtml.



Note This restore process takes approximately the same amount of time as the backup.


Procedure


Step 1 Copy CiscoUnifiedMeetingPlaceWebConferencingRestore.exe to the destination computer.

Step 2 Double-click this file.

The Backup or Restore Wizard window displays.

Step 3 Click Next.

Step 4 Select Restore files and settings. Click Next.

Step 5 Click Browse and navigate to your MeetingPlacebackup.bkf file. Click Next.

Step 6 Double-click an item in the left pane to see its contents.

Step 7 Check the items you want to restore. Click Next.

Ensure that all drives and multiple folder options are checked.

Step 8 Click Finish to close the Wizard.

The restore operation proceeds.

Step 9 Click Close to close the Cisco Unified MeetingPlace Restore window.


Cisco Security Agent (CSA)

If you want the Cisco Security Agent (CSA) installed on your Release 8.6 system, then you must install the version of CSA that is on the Cisco Unified MeetingPlace Release 8.6 Web Server DVD. Follow the instructions in the Installing the Cisco Unified MeetingPlace Web Server Software module.

Installing the Web Server Software

To migrate your Cisco Unified MeetingPlace Web Server to Release 8.6, do a fresh install of the 8.6 Web Server. See How to Install the Cisco Unified MeetingPlace Web Server Software, in the Installing the Cisco Unified MeetingPlace Web Server Software module.


Note If you are planning to install Cisco Unified MeetingPlace Release 8.6 then go to http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6. Obtain the CiscoUnifiedMeetingPlaceWebServer.exe file for your release.


Related Topics

For information about configuring the Web Server to synchronize with an NTP server, see Configuring the Time for the Web Server in the "Configuring Time and Time Zones for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.

Reconfiguring the Application Server Connection in the Gateway SIM

Following the migration, the connection between the Application Server and the Web Server is broken. Complete the following procedure to redo the connection.

Procedure


Step 1 Stop the web services and the Gateway SIM service.

Step 2 Open the Gateway SIM Agent.

a. Open the MeetingPlace Gateways Configuration utility.

b. Select the Gateway SIM tab.

Step 3 Delete this unit from the active Application Server.

a. Go to the lower-left pane of the Gateway SIM tab.

b. Select the name of the Application Server that you want to disconnect from.

c. Select Delete.

Step 4 Add this unit to a new Application Server.

a. Open the Gateway SIM Agent.

b. Select Add.

The MeetingPlace Server Entry window displays.

c. Enter the new configuration information as follows:

Parameter
Action

Server Name

Enter the hostname of the Release 8.6 Cisco Unified MeetingPlace Application Server.

Note If you use an IP address instead of a hostname for the Application Server, you will have to update the IP address on the Web Server whenever you change the IP address on the Application Server.

Shadow Server

Leave this field as is.

Client IP Address

Enter the IP address of the computer on which the Gateway SIM is installed.

Transfer Destination

Leave this field as is.

Link Encryption Disabled

Leave this box unchecked to maintain encrypted communications between the Gateway SIM and the Application Server.

Encryption uses a 56-bit DES algorithm with a secret key.


d. Select OK.

e. Select OK again.

Step 5 Restart the Gateway SIM service and the Cisco Unified MeetingPlace Web Master Service.

If other Web Servers share the database with this server, restart the services on those servers as well.


Connecting the Application Server to the Web Server

Following the migration, both your legacy Web Server and the Release 8.6 Web Server may both be connected to the Release 8.6 Application Server. Complete the following procedure to disable your legacy Web Server connection.

Procedure


Step 1 Sign in to the Administration Center for the Release 8.6 Application Server.

Step 2 Select System Configuration > Web Servers.

Step 3 Find the Unit number of the legacy Web Server and confirm that Enabled is set to No.

Step 4 Find the Unit number of the Release 8.6 Web Server and confirm that Enabled is set to Yes.


Note If you do not see the Release 8.6 Web server in this list (for example, when the unit numbers from the legacy Web Server and the 8.6 Web Server are the same), then add the new 8.6 Web Server in the list and set Enabled to Yes.



Allowing Guest Users to Dial Out

After you have migrated the Web Server on your system, if you want to allow guests to be able to dial out to other users, set the following parameters for the guest profile. Sign in to the Cisco Unified MeetingPlace Administration Center and select User Configuration > User Profiles. Select Edit for the guest user to change the Can dial out parameter.

To find the Call-in teleconferencing check box parameter in Cisco WebEx, go to Site Administration > Manage Site > Site Settings > Default Scheduler Options > Default site audio options.

Can dial out parameter in the Administration Center
Call-in teleconferencing checkbox in Cisco WebEx
Result

Yes

checked

Guests can dial out from the telephone

Guests cannot dial out from the meeting room

Yes

not checked

Guests can dial out from the telephone

Guests can dial out from the meeting room

No

checked

Guests cannot dial out from the telephone

Guests cannot dial out from the meeting room

No

not checked

Not recommended.


Related Topics

Restricting Dial-Out Privileges for Guest Users in the "Securing the Cisco Unified MeetingPlace System" section of Configuration Guide for Cisco Unified MeetingPlace

Overview of Security Tasks in the "Securing the Cisco Unified MeetingPlace System" section of the Configuration Guide for Cisco Unified MeetingPlace

Troubleshooting the Web Server Migration

Error Message    You cannot run this software on a server that already has Cisco Unified 
MeetingPlace Web Conferencing.

Recommended Action    Remove the existing Web Server software. You must install Cisco Unified MeetingPlace Web Conferencing on a clean machine.

Problem   The Web Server does not boot after the migration.

Solution   When the Web Server boots up, it compares the Application Server hostname that it has stored in the SQL database with that configured in the Gateway SIM. If the names do not match, the Web Server fails to boot. If this is the cause, complete the procedure in "Restoring the Cisco Unified MeetingPlace Web Server After Boot Failure" in the Configuration Guide for Cisco Unified MeetingPlace

How To Install the Cisco WebEx Node for MCS for a Migrated System

The Cisco WebEx Node for MCS (on a MCS or on a virtual machine) is an optional component in Release 8.6, used for internal meetings, where all the audio, video, and content sharing remains on-premises. Due to a change in the operating system, you cannot upgrade or migrate a Cisco WebEx Node for MCS from Release 8.0 to Release 8.5. Instead, you must install a new Release 8.5 Cisco WebEx Node for MCS.

If you do not have a Cisco WebEx Node for MCS and do not plan to add one, then go to How to Upgrade the Software for the Hardware Media Server. If you are using Express Media Server, then go to How to Migrate Microsoft Outlook for Cisco Unified MeetingPlace.


Note Be sure to write down all your Cisco WebEx Node for MCS configuration information so that you can reenter the information during the installation of your new Cisco WebEx Node for MCS (on a MCS or on a virtual machine). Sign in to the Cisco WebEx Node for MCS CLI as wbxadmin, enter show webex config, and write down all the information.


You may continue to use the same hardware for the Release 8.5 Cisco WebEx Node for MCS, as long as the hardware meets the minimum requirements in Release 8.5. (See http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_device_support_tables_list.html.)

You may also choose to install the Cisco WebEx Node for MCS on a virtual machine with a VMware ESXi 4.1 host on a Cisco UCS B-Series or C-Series Server, or on a new Cisco MCS.

How to Upgrade the Software for the Hardware Media Server

Ensure that you have the latest software for your audio and video blades.

Hardware Media Server Software Upgrade Utility

Upgrading the Software for the Hardware Media Server

Troubleshooting Errors When Upgrading the Software for the Hardware Media Server

Recommendations for Moving an Audio Blade to a Different Hardware Media Server

Hardware Media Server Software Upgrade Utility

If you are using a Express Media Server, go to How to Migrate Microsoft Outlook for Cisco Unified MeetingPlace.

Use the Hardware Media Server Software upgrade utilities to upgrade the Hardware Media Server software. The utilities upload files via a network connection to the Hardware Media Server. You can choose to perform a typical upgrade (which includes all the new files) or a customized upgrade (which enables you to select which files to upload). You can upgrade either the Audio Blade software or the Video Blade software depending on your deployment. You may need both the Audio Blade and Video Blade upgrade utilities.

The software upgrade utility resets the Audio Blade password and SNMP community names back to the factory default settings. To restore the previous Audio Blade password and SNMP community names, either put the Audio Blade online or synchronize the Audio Blade. Note that the synchronization process will not overwrite a set password; it will only overwrite a factory default password.

Information for any other administrative users in the Media Server Administration for the Hardware Media Server is lost during an upgrade.


Note During the migration, the system does not retain the names and IP addresses of the audio and video blades comprising the Hardware Media Server. Be sure to add them once your migration is complete. See Adding an Audio Blade to Cisco Unified MeetingPlace in the Changing Values for the Hardware Media Server module.



Note Following the migration, be sure to configure your SNMP configuration with the information you wrote down earlier.



Note If you used a new machine for your Release 8.6 Application Server, then be sure to disconnect the MCU from the legacy Application Server following the migration.


Upgrading the Software for the Hardware Media Server

Restrictions for Upgrading the Software for the Hardware Media Server

Launching the Upgrade Utility

Upgrading the Software for Audio Blades

Upgrading the Software for Video Blades

Restrictions for Upgrading the Software for the Hardware Media Server

Migrate the Application Server before you upgrade the Hardware Media Server.

When you upgrade the Hardware Media Server software, the system resets all of the Audio Blade configuration settings (except for the network interface configuration). You must reapply any custom settings that you have previously made to the Audio and Video Blades after the upgrade procedure is complete.

Launching the Upgrade Utility

Procedure


Step 1 Download the executable file from the Cisco Unified MeetingPlace 3500 Series Media Server Software CD-ROM or from the Cisco web site:

Obtain the Cisco Unified MeetingPlace Release 8.6 Prerequisite Package: http://www.cisco.com/cisco/software/navigator.html and select Products > Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 8.6. Select Unified MeetingPlace Audio Blade and Unified MeetingPlace Video Blade, respectively.

To upgrade the software for Audio Blades, the file is called AudioBlade_Upgrade_xx.exe.

To upgrade the software for Video Blades, the file is called VideoBlade_Upgrade_xx.exe.

Step 2 Double-click the file to run the upgrade utility.

The system extracts the upgrade files and displays the Upgrade Utility dialog box.


What To Do Next

To upgrade the software for the Audio Blades, go to Upgrading the Software for Audio Blades.

To upgrade the software for the Video Blades, go to Upgrading the Software for Video Blades.

Upgrading the Software for Audio Blades

Before You Begin

Make sure that no meetings are active.

Procedure


Step 1 Sign in as an administrator to the Media Server Administration for the Hardware Media Server.

Step 2 Take the Audio Blade offline.


Note Failure to take the Audio Blade offline before the upgrade can result in an inconsistent state, with a variety of possible symptoms including dead air when dialing into the system.


Step 3 Enter the IP address of the Audio Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.

Step 4 Enter the administrator user name and password for the Audio Blade, as configured in the device network configuration settings, in the Login Information section.

Step 5 (Optional) Modify the read and write community settings for the Audio Blade as follows:

a. Select Customize SNMP Settings....

b. Enter the required read community and write community values.


Note We recommend that you modify the default settings for security purposes.


c. Select OK to return to the Upgrade Utility dialog box.

Step 6 (Optional) Select the components of the Audio Blade that you want to upgrade as follows:

a. Select Customize... in the Upgrade Information section.

b. Check the components that you want to upgrade.


Note The components displayed vary according to the hardware that is upgraded.


c. Select OK to return to the Upgrade Utility dialog box.

Step 7 Select Upgrade to upgrade all components of the software (or only those components you manually selected via the Customize option).

The upgrade utility informs you whether the upgrade is successful.


Note When the upgrade is complete, the Audio Blade automatically resets itself and starts operation with the new software version.


Step 8 Upgrading the Audio Blades resets the user credentials. Sign in to the Media Server Administration for the Hardware Media Server by using the user name of "admin" and the password of "password".

Step 9 To improve security, we recommend that you change the user name and password.

Step 10 Repeat Step 3 to Step 7 for any other Audio Blades that need to be upgraded.

Step 11 Put the Audio Blade online.


Note Putting the Audio Blade online restores the password and SNMP community names that were in effect before the upgrade. It also synchronizes the Application Server with the Audio Blade except for the meeting types.


Step 12 Repeat Step 2 to Step 11 for each blade that was upgraded.

Step 13 Go to Resource Management > Meeting Types.

Step 14 Select Synchronize.


Related Topics

Signing in to the Media Server Administration for the Hardware Media Server in the Changing Values for the Hardware Media Server module

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

Changing the Media Server Administration Password for the Hardware Media Server in the Changing Values for the Hardware Media Server module

What To Do Next

If you previously customized your Audio Blades, manually reapply those customizations.

Upgrading the Software for Video Blades

Before You Begin

Make sure that no meetings are active.

Procedure


Step 1 Sign in as an administrator to the Media Server Administration for the Hardware Media Server.

Step 2 Enter the IP address of the Video Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.

Step 3 Enter the administrator user name and password for the Video Blade, as configured in the device network configuration settings, in the Login Information section.

Step 4 (Optional) Select the components of the Video Blade that you want to upgrade as follows:

a. Select Customize... in the Upgrade Information section.

b. Check the components that you want to upgrade.


Note The components displayed vary according to the hardware that is upgraded.


c. Select OK to return to the Upgrade Utility dialog box.

Step 5 Select Upgrade to upgrade all components of the software (or only those components you manually selected via the Customize option).

The software upgrade utility informs you whether the upgrade is successful.


Note When the upgrade is complete, the Video Blade automatically resets itself and starts operation with the new software version.


Step 6 Repeat Step 2 to Step 5 for any other Video Blades that need to be upgraded.

Step 7 Put the Video Blade online.

Step 8 Repeat Step 2 to Step 7 for each blade that was upgraded.

Step 9 Go to Resource Management > Meeting Types.

Step 10 Select Synchronize.

Step 11 Upgrading the Video Blades resets the user credentials. Sign in to the Media Server Administration for the Hardware Media Server by using the user name of "admin" and the password of "password".

Step 12 To improve security, we recommend that you change the user name and password.


Related Topics

Signing in to the Media Server Administration for the Hardware Media Server in the Changing Values for the Hardware Media Server module

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

How to Configure Administrators for the Hardware Media Server in the Configuring the Audio and Video Blades for the Hardware Media Server module

What To Do Next

If you are using a Hardware Media Server in your deployment, then you need to configure your audio and video blades on the Cisco Unified MeetingPlace Release 8.6 Hardware Media Server. Select the same IP address, as before the migration, for each MCU. See Adding an Audio Blade to Cisco Unified MeetingPlace in the Changing Values for the Hardware Media Server module.


Note If you used a new machine for your Release 8.6 Application Server, then be sure to disconnect the MCU from the legacy Application Server following the migration.


If you previously customized your Video Blades, manually reapply those customizations.

Troubleshooting Errors When Upgrading the Software for the Hardware Media Server

Use the following recovery procedure if the Hardware Media Server upgrade procedure fails and any further attempts to upgrade it are blocked by the following three error messages:

Could not retrieve the target information. Your SNMP community settings might be incorrect. Click OK to continue the upgrade, or Cancel to review your SNMP community settings.

If you press OK, you see this error message:

Setup cannot continue without obtaining target information through SNMP. Please reset the target manually or contact customer support for more help.

After that message, the system displays this error message:

Upgrade process failed.

Procedure


Step 1 Sign in as an administrator to the Media Server Administration for the Hardware Media Server.

Step 2 Take the Audio Blade offline.


Note Failure to take the Audio Blade offline before the upgrade can result in an inconsistent state, with a variety of possible symptoms including dead air when dialing into the system.


Step 3 Enter the IP address of the Audio Blade that you want to upgrade in the General Information section of the Upgrade Utility dialog box.

Step 4 Enter the administrator user name and password for the Audio Blade, as configured in the device network configuration settings, in the Login Information section.

Step 5 Select Customize from inside the Upgrade Information section.

The system displays the following message:

The SNMP community settings do not match the target community. Press Retry to change the Read Community name.

Step 6 Select Ignore.

Step 7 In the Customize dialog box, ensure that only the following boxes are checked: MCU WEB Interface, MCU Config File, and MCU Factory Default Config File.

Step 8 Select OK.

Step 9 Select Upgrade.

Step 10 Select OK when the system displays the error message.

The system begins updating the three processes that you checked in Step 7.

Step 11 When the upgrade is complete, run the upgrade utility again, without the customized settings.


Related Topics

Signing in to the Media Server Administration for the Hardware Media Server in the Changing Values for the Hardware Media Server module

Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module

Recommendations for Moving an Audio Blade to a Different Hardware Media Server

When moving an Audio Blade from one Hardware Media Server to another (except when doing so for failover), we recommend the following best practices:

Use different Audio Blade passwords and SNMP community names for each Hardware Media Server.

Set the Audio Blade to permanently offline on the Hardware Media Server from which you are moving the Audio Blade. See Changing the Online and Offline Status of an Audio Blade in the Changing Values for the Hardware Media Server module.

How to Change from a Hardware Media Server to an Express Media Server

About the Media Server

Changing the Type of Media Server that Your System Uses

About the Media Server

All systems that will use audio or video need a media server and the media server can be either a Hardware Media Server or an Express Media Server.

The Express Media Server is a set of software modules, including an audio mixer and a video switcher, that resides on the Application Server. The Express Media Server creates a single box, software-only solution for Cisco Unified MeetingPlace.

The Hardware Media Server is comprised of Audio and Video Blades.

All Cisco Unified MeetingPlace Release 8.6 systems automatically come with an Express Media Server.

Changing the Type of Media Server that Your System Uses

Follow these steps to change the type of media server that your system uses from a Hardware Media Server to an Express Media Server.

Procedure


Step 1 Sign in to the Administration Center.

Step 2 Select System Configuration > Media Resource Configuration.

Step 3 Select Express Media Server for the Type of media server field.

Step 4 Select Save.

The system reboots.


What To Do Next

Configure the system for the Express Media Server. See "Configuring Meetings for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.

How to Migrate Microsoft Outlook for Cisco Unified MeetingPlace


Note The Microsoft Outlook for Cisco Unified MeetingPlace integration is the same for Cisco Unified MeetingPlace Release 7.0 MR 2 and Cisco Unified MeetingPlace Release 8.0. Therefore, if you have already upgraded your Microsoft Outlook for Cisco Unified MeetingPlace integration to Release 7.0 MR 2 or later, then you do not need to follow this procedure. Your integration is already upgraded. Tell your users to upgrade their Outlook plug-in. See Upgrading the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook.



Note You do not need to back up any notification templates. The system copies all of these notification templates to a backup directory under /opt/cisco/meetingplace/var<legacy_release_number>.


To migrate from Cisco Unified MeetingPlace Release 7.0 to Cisco Unified MeetingPlace Release 8.6, follow these steps:

Step #
Step Description
For more information, see

Step 1 

Migrate your Cisco Unified MeetingPlace Release 7.0 system to Cisco Unified MeetingPlace Release 8.6

How to Migrate the Application Server Software

How to Migrate the Web Server

How to Upgrade the Software for the Hardware Media Server

Step 2 

Uninstall the Microsoft Outlook for Cisco Unified MeetingPlace integration Release 7.0 from the Web Server.

Uninstalling Cisco Unified MeetingPlace for Microsoft Outlook Gateway From the Web Server in the "Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the MeetingPlace Web Scheduling Interface" section of the Configuration Guide for Cisco Unified MeetingPlace

 

Step 3 

Configure the Microsoft Exchange Server.

Configuring the Cisco Unified MeetingPlace Connection to the Microsoft Exchange Server in the "Enabling Microsoft Outlook Calendar Notifications for Meetings Scheduled from the MeetingPlace Web Scheduling Interface" section of the Configuration Guide for Cisco Unified MeetingPlace

 

Step 4 

Sign in to the Release 8.6 Application Server as the root user.

 

Step 5 

From the Release 8.6 Application Server, run the following Cisco Unified MeetingPlace-Microsoft Exchange migration script: /opt/cisco/meetingplace/migrationtools/current/notifications/migrateExchangeForICAL.sh.

 


Note The migration process may take a long time if many meetings need to be migrated. To speed up the migration, purge old meetings from the Cisco Unified MeetingPlace-dedicated mailbox and empty the Deleted Items folder. We recommend that the mailbox have fewer than 1360 appointment items or 32 KB of appointment data before you run the migration script.


Upgrading the Cisco Unified MeetingPlace Plug-In for Microsoft Outlook

After you complete the migration process, have your users upgrade the Cisco Unified MeetingPlace plug-in for Microsoft Outlook on their PCs. They can do this themselves by doing one of the following:

Select Download Outlook Plug-In from the Cisco Unified MeetingPlace web user portal.

Select Upgrade to newer version from the MeetingPlace tab in a Microsoft Outlook calendar appointment.


Note After upgrading the plug-in, instruct your users to clear the cookies in Internet Explorer, and restart Microsoft Outlook, before using Cisco Unified MeetingPlace for Microsoft Outlook meetings. If the user does not clear the cookies, then the user name is garbled in the login window.


Testing that the Migrated System Works Correctly

Verify the following after you migrate and configure the entire Cisco Unified MeetingPlace system:

Licenses

Your system has all the necessary licenses installed. See the Planning Guide for Cisco Unified MeetingPlace Release 8.6 at: http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_implementation_design_guides_list.html for information about Cisco Unified MeetingPlace Release 8.6 licenses.

"Obtaining Your License After Migration" in the Configuration Guide for Cisco Unified MeetingPlace for the exact procedure.

Database Import

Ensure that the following information imported correctly: user groups, user profiles, video terminal profiles, video types, video usage assignments, meeting categories, and password expirations.

Before turning off maintenance mode on your Release 8.6 Application Server, ensure that all recorded names for user profiles were imported correctly.

Confirm that all the users' recorded names have been copied into their respective user profile subdirectories. There must be no wav or refcnt files in the /opt/cisco/meetingplace/afs/custom/userprofile directory.


Caution If a user attempts to start a meeting before the user's recorded name has been copied to the subdirectory, than the user profile becomes unusable, and cannot be repaired.

Ensure that all scheduled meetings, both past and recurring, imported correctly.

Ensure that the default video mode assigned to user profiles matches the global video mode that was previously assigned to the user profile.

Scheduling

Ensure that you can schedule a meeting.

Ensure that the system sends an email notification for the meeting that you scheduled.

Ensure that you can join and attend the meeting via audio, video, and web.

Test that the dial in and dial out features work.

System Access

Ensure that you have access to all of the Administration Center pages, including Conference Manager. To access the Administration Center, go to a web browser and enter http://<your-app-server>.

Recordings

Ensure that you can record a meeting.

Ensure that you can play back the meeting recording.

Configuring Your System After Migration

Release 8.6 systems with WebEx scheduling:

From the Administration Center, select Cisco WebEx Site Configuration and enter the appropriate phone numbers in Access Information. For more information, see the "About Integrating with Cisco WebEx" section in the Configuration Guide for Cisco Unified MeetingPlace.

Completing the Migration

To complete the migration, follow these steps.

Inform end users that the system has been successfully migrated.

Changes in user roles.

Cisco Unified MeetingPlace Release 7.x—Users who were meeting moderators are converted to alternate hosts in Cisco Unified MeetingPlace Release 8.6. Meeting attendees or presenters are converted to meeting attendees.

In Cisco Unified MeetingPlace Release 8.0 and 8.6, only a host or an alternate host can start a meeting.

We recommend that after you migrate your system, you inform users about this restriction and suggest that meeting owners designate alternate hosts before their meetings begin. Only the meeting owner or an alternate host can modify a meeting.

Cisco Unified MeetingPlace Release 8.0—No changes in user roles.

Changes in licensing.

Starting with Cisco Unified MeetingPlace Release 8.6, licensing has changed from a user-based model to a meeting host-based model. Meeting hosts can schedule audio meetings, video meetings, or both. For more information, see "Installing and Managing Licenses for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.

If you want to create a multinode deployment, then see "Configuring your Multinode Topology for Cisco Unified MeetingPlace" in the Configuration Guide for Cisco Unified MeetingPlace.