The Cisco Unified MeetingPlace Release 7.0 system had two options for web conferencing: using the Cisco Unified MeetingPlace meeting room and using the Cisco WebEx meeting room. In Release 8.0, Cisco Unified MeetingPlace only offers the Cisco WebEx meeting room.

For systems that are upgraded, the software that ran the Cisco Unified MeetingPlace meeting room will remain on the upgraded system in order to allow users to play back meetings that were recorded in Release 7.0. The old software cannot be used for scheduling or attending meetings.

In upgraded systems, the SSL/TLS page in the Administration Center shows two SSL configuration fields. The second SSL configuration field is required to play back meeting recordings from Cisco Unified MeetingPlace Release 7.0.

Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0 will continue to use two NICs (IP addresses); however, new Cisco Unified MeetingPlace Release 8.0 systems only use one NIC.

In Cisco Unified MeetingPlace Release 7.0, there were two fields to describe licensed capacity: Use licensed audio capacity and Use licensed video capacity. In Cisco Unified MeetingPlace Release 8.0, these two fields are combined into one field called Use licensed capacity. The value of the new field in Cisco Unified MeetingPlace Release 8.0 is set to the value of the Use licensed audio capacity in Cisco Unified MeetingPlace Release 7.0.

For Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0, you must ensure that the remote storage location is accessible; otherwise, some of the web master services may fail to start properly which can cause the system to try to restart all the services.

Cisco Unified MeetingPlace Release 7.0 meetings describe meeting attendees using the terms moderators, presenters, and audience. Cisco Unified MeetingPlace Release 8.0 meetings use the terms host, alternate host, and attendee. See the Completing the Upgrade for more information about how user types in Release 7.0 are converted for Release 8.0.

Cisco Unified MeetingPlace Release 8.0 does not have lecture-style meetings.

Cisco Unified MeetingPlace Release 8.0 systems that are upgraded from Release 7.0 will keep the current setting for the "Dial-out calls enabled via guest profile" parameter; however, new Cisco Unified MeetingPlace Release 8.0 systems will set the default value for that parameter to Yes. This means that systems that are upgraded to Release 8.0 may not allow guest users to dial out from the meeting room automatically even though new installations will allow this.

Recommendations

We recommend that you upgrade your Cisco Unified MeetingPlace system during a time when there is not much meeting traffic, for example, over a weekend or a period of extended downtime.

Note: Technically, installing the Cisco WebEx Node for MCS is optional. It is not required if your system is audio only. However, if your system will include web functionality, you must install the Cisco WebEx Node for MCS.

About Upgrading the Application Server Software

To upgrade the Application Server software, you must already have an existing version of the Application Server software installed on your server.

When you upgrade the Application Server software, the upgrade program moves the existing files to a backup directory and installs the new files in the current directory. This allows you to uninstall the upgrade if you need to.

A fresh installation of the Application Server software erases the database that holds the Hardware Media Server configuration information; however, upgrading the Application Server software does not erase the database.

The upgrade program backs up any Microsoft Outlook notification templates and copies them to /opt/cisco/meetingplace/var.

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

Preparing to Upgrade the Application Server Software

Do not uninstall the Application Server software before you upgrade.

The Cisco Unified MeetingPlace system must be running when you perform an upgrade. Do not turn off the Cisco Unified MeetingPlace services.

Restrictions and Recommendations for Upgrading the Application Server Software

(Upgrading to Release 8.0 from Release 7.0.1.4 FCS or from Release 7.0.2.14 MR1 version only.) If your Application Server is on a Cisco MCS 7835-I2 or a Cisco MCS 7835-H2, then we recommend you run the upgrade script from the /mpx-record directory. Enter df -h to determine the amount of available space. There should be a minimum of 6 GB available in the /mpx-record directory, when you run the upgrade script here. If you prefer to run the upgrade script from the /tmp directory, then there must be a minimum of 8 GB available in the /mpx-record directory.

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 Application Server. Without this, your upgrade 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.

Determining Which Procedure to Follow

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

Enter md5sum upgrade_mp_<'version_number>'.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.

From the console, go to the Cisco Unified MeetingPlace operating system sign-in page and sign in as the user called root.

The upgrade 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 upgrade program displays a message listing the previous versions found on the system.

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

Select Next to begin the upgrade.

The upgrade program displays a pre-installation summary.

Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.

Select Install if all the values are correct.

The upgrade program upgrades all the required components associated with the Application Server software.

The upgrade program displays a message stating that the upgrade is complete.

Enter md5sum upgrade_mp_<'version_number'>.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.

The upgrade 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 upgrade program displays a message listing the previous versions found on the system.

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

Press Enter to continue.

Review the pre-installation summary. Values include the product name, install folder, and the amount of disk space required and available for the installation target.

Press Enter to begin the upgrade.

The upgrade program installs the Application Server upgrade.

When the upgrade is complete, the upgrade program displays the Install Complete page and a message stating that the upgrade is complete.

Press Enter to restart the system.

Note: When you restart the system, all existing screens are removed.

Synchronize the Hardware Media Server and meeting types.

Put the Audio Blade back online.

Troubleshooting

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

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

Enter screen -ls to find out the full name of the screen created in Step 6 of the "Upgrading the Application Server Remotely" procedure. The full name of the screen consists of an identifier followed by a dot and then the name that you used in Step 6 of the "Upgrading the Application Server Remotely" procedure. For example, the full screen name might be 1665.mp_upgrade.

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

Upgrading Application Servers that are Used in a Failover Deployment

Before You Begin

Note the following nomenclature that is used for clarity: node 1 is the server that originally is the active Application Server and node 2 is the server that originally is the standby Application Server.

Turn off failover before you begin.

Procedure

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

Enter su - to switch to the root user.

Enter mp_replication status on node 1 to ensure that all database changes have been synchronized.

The system displays the queue column as zeroes.

Enter mp_replication switchOFF -r 'node_2_eth0:0' on node 1, to switch off replication between the two Application Servers, where node_2_eth0:0is the eth0:0 address for node 2.

Enter 'mp_replication teardown -r 'node_2_eth0:0 on node 1, to tear down the replication setup with the remote Application Server, where node_2_eth0:0is the eth0:0 address for node 2.

Archive and save the configuration data on node 1.

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

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

RSNA is typically used with Directory Service, which uses user database replication to enable two Cisco Unified MeetingPlace Application Servers in different sites to have synchronized user profiles and user groups.

Restriction

During the upgrade process, do not make any user or group configuration changes on any of the Application Servers. If you make configuration changes on one Application Server, they will not be ported to the other Application Server, because you turned off database replication.

If you do make any user or group configuration changes, follow the procedure below and then perform the initial setup procedures to synchronize the data between the two Application Servers. To synchronize the data, you will need to erase the database from one server and synchronize the data from the other server.

Before You Begin

The instructions for upgrading Application Servers that are used in an RSNA deployment include the following prerequisite actions, which avoids the creation of duplicate or unsynchronized user profiles of type delegate, attendant, or system administrator on the Application Servers.

If you created any identical user profiles of type delegate, attendant, or system administrator on both Application Servers, then delete those user profiles from one of the servers.

For example, if you created a system administrator profile A1 in each of the two servers S1 and S2, then delete A1 from either S1 or S2.

Synchronize the user data in both Application Servers by using one of the following methods:

For each user profile you deleted from one Application Server, update the identical user profile on the other Application Server.

Updating a user profile automatically causes the profile record to be replicated to the other Application Server.

Enter the following command in the Application Server CLI, specifying the hostnames of the Application Servers:

mp_replication switchON -rhostname-remote-S -Fhostname-local

This process may take a long time, depending on the total number of user profiles on the Application Servers and the network bandwidth between them.

Note: Note the following nomenclature that is used for clarity: node 1 is the server that is in site 1 and node 2 is the server that is in site 2.

Procedure

Sign in to the CLI of node 1.

Enter su - to switch to the root user.

Enter mp_replication status on node 1 to ensure that all database changes have been synchronized.

The system displays the queue column as zeroes.

Enter 'mp_replication switchOFF -r 'node_2_IP_address on node 1, to switch off replication between the two Application Servers, where node_2_IP_addressis the IP address for node 2.

Enter 'mp_replication teardown -r 'node_2_IP_address on node 1, to tear down the replication setup with the remote Application Server, where node_2_IP_addressis the IP address for node 2.

Completing the Application Server Software Upgrade

Merging Email Notification Templates

When you upgrade the Application Server software from an earlier release, the upgrade program overwrites all custom email notification templates and replaces them with the standard email notification templates for the release to which you are upgrading. However, before the upgrade process begins, the upgrade program moves all of the email notification templates for the original release to a backup directory under /opt/cisco/meetingplace/var.

Restoring Email Notification Values

The upgrade process also overwrites all the configuration values for the SMTP and Exchange servers. After upgrading the Application Server software, you must manually restore the SMTP and Exchange server values.

Enter mpx_version and verify that the Application Server version on your system matches the version to which you upgraded.

Note: To ensure that your server has adequate disk space, the upgrade program removes many of the older versions of the Application Server software that are on your system. Therefore, when you run the mpx_version command, you may not see every version that you have ever installed.

Enter mpx_sys status and ensure that most services are running:

The license service will not be running.

If you chose to install an Express Media Server, the video administration and SIP server services will not be running.

Restrictions for Upgrading the Web Server Software

Upgrade the Application Server before you upgrade the web server software.

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

If your system has multiple web servers, you must upgrade them all to the same version. You can upgrade them in any order.

Recommendations for Upgrading the Web Server Software

We recommend that you only upgrade the Web Server software after hours. To avoid losing recordings, do not upgrade the Web Server software 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.

We do not support upgrading the Cisco Unified MeetingPlace Web Server software by using Terminal Services.

Manually back up the notification templates for the Microsoft Outlook back-end deployment; however, you do not have to back up the notification templates for SMTP and the Microsoft Outlook front-end deployment because the system copies all of the notification templates for SMTP and the Microsoft Outlook front-end deployment to a backup directory under /opt/cisco/meetingplace/var.

Working with the Cisco Security Agent (CSA)

If the Cisco Security Agent (CSA) is installed on your system, before you upgrade the web server, you must stop CSA, uninstall it, and install the version of CSA that is on the Cisco Unified MeetingPlace Web Server DVD.

Reinstalling the Cisco Security Agent (CSA)

Troubleshooting

If you run into problems while installing the CSA, contact Cisco TAC. Examples of problems include if you are installing the CSA and the system aborts the installation or if the system does not let you reinstall or uninstall the CSA.

About Upgrading Cisco WebEx

This section only applies to Cisco Unified MeetingPlace Release 7.0 systems that use Cisco WebEx.

Upgrading the Cisco WebEx Release

When you upgrade from Cisco Unified MeetingPlace Release 7.0 to Cisco Unified MeetingPlace Release 8.0, you must also upgrade from the Cisco WebEx WBS26 Release to the Cisco WebEx WBS27 Release.

You cannot upgrade Cisco WebEx yourself. To upgrade to the Cisco WebEx WBS27 Release, you must notify the Cisco WebEx Customer Support Engineer (CSE) that you plan to upgrade Cisco Unified MeetingPlace from Release 7.0 to Release 8.0 and then ask the CSE to upgrade your release of Cisco WebEx. In order to avoid a delay in implementing your upgrade, we recommend that you schedule the Cisco WebEx upgrade as far in advance as possible of your Cisco Unified MeetingPlace upgrade.

Making Recordings Accessible to Users

Recordings that were created using Cisco Unified MeetingPlace Release 7.0 must be moved to a location where they can be accessed by Cisco Unified MeetingPlace Release 8.0 users.

This procedure only applies if both the following are true:

You are upgrading your system from Release 7.0 to Release 8.0

The Cisco WebEx site name for your Release 8.0 system is different from the Cisco WebEx site name for your Release 7.0 system.

Procedure

Navigate to the Cisco WebEx Site Administration page for the Release 7.0 system.

Sign in with the credentials that you use to sign into the Application Server.

Navigate to the user page for the admin user.

Select My WebEx.

Select My Files on the left.

Select the My Recordings tab.

If there are any recordings, delete them by doing the following:

On the line with the recording name, click the down arrow on the right.

Select Delete.

Select OK in the confirmation dialog box.

Continue until you have deleted all the recordings.

Select Site Administration.

Select Edit User List on the left.

In the User name field, enter the user name for the user who has recordings that need to be moved to the new server.

Select Search.

Select the name of the user to go to the account for this user on the Release 7.0 system.

Select Re-assign NBR Recordings.

The system displays a dialog box where you can reassign the recordings for the user.

In the Search field, enter admin.

Select Search.

Select Yes in the confirmation dialog box.

The system moves all the recordings for that user to the admin user's account.

Continue Step 9 to Step 16 for all users on the Release 7.0 system who have recordings.

Navigate to the user page for the admin user.

Select My WebEx.

Select My Files on the left.

Select the My Recordings tab.

For each meeting, select the name of the meeting, which is displayed under the "Topic" header.

Download the recording by doing the following:

On the line with the recording name, click the down arrow on the right.

Hardware Media Server Software Upgrade Utility

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.

How to Upgrade the Software for the Hardware Media Server

Restrictions for Upgrading the Software for the Hardware Media Server

Upgrade 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.

Upgrading the Software for Audio Blades

Before You Begin

Procedure

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

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.

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

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

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

Select Customize SNMP Settings....

Enter the required read community and write community values.

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

Select OKto return to the Upgrade Utility dialog box.

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

Select Customize... in the Upgrade Information section.

Check the components that you want to upgrade.

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

Select OKto return to the Upgrade Utility dialog box.

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.

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".

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

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

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.

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

About the Express Media Server

Cisco Unified MeetingPlace Release 8.0 introduces an Express Media Server, a software version of the Hardware Media Server that was used in previous releases of Cisco Unified MeetingPlace. 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.

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

Note: The upgrade process may take a long time if many meetings need to be migrated. To speed up the upgrade, 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 upgrade script.

What To Do Next

After you complete the upgrade 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:

Database Import

Ensure that all recorded names for user profiles were imported correctly.

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.

Completing the Upgrade

Inform end users that the system has been successfully upgraded.

During the upgrade process, only users who were moderators for a Cisco Unified MeetingPlace Release 7.0 meeting are converted to alternate hosts in Cisco Unified MeetingPlace Release 8.0. Meeting attendees or presenters for Cisco Unified MeetingPlace Release 7.0 meetings are only converted to meeting attendees in Cisco Unified MeetingPlace Release 8.0.

In Cisco Unified MeetingPlace Release 8.0, only a host or an alternate host can start a meeting. After an upgrade, users may find that meetings only have one host and no alternate host and may experience not being able to start a meeting.

We recommend that after you upgrade your system, you inform end user about this restriction and suggest that meeting owners designate alternate hosts for their meetings. This must be done before the meeting begins and only the meeting owner or delegate can modify a meeting.

If you have upgraded your system to a Release 8.0 system with Cisco WebEx scheduling and without directory services integration, then the user passwords are not recognized after you import your user profiles into Cisco WebEx. (Cisco Unified MeetingPlace passwords are encrypted whereas Cisco WebEx uses plain text passwords.)

When they next log in to Cisco WebEx, ask your users to select Forgot your password and have them reset their password.