Cisco Unified MeetingPlace, Release 7.1 -- How to Upgrade the Application Server

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Procedure)
m (1 revision)

Revision as of 15:23, 4 April 2011


Cisco Unified MeetingPlace, Release 7.1 > Installation > How to Upgrade to Cisco Unified MeetingPlace Release 7.1 > How to Upgrade the Application Server > How to Upgrade the Web Server > Upgrading the Cisco Unified MeetingPlace 3500 Series Media Server Software > Upgrading Microsoft Outlook for Cisco Unified MeetingPlace



Note: You can upgrade to Release 7.1 from Release 7.0.2 (MR1) or Release 7.0.3 (MR2). If you are at Release 7.0.1, then you must first upgrade to Release 7.0.2. See How to Upgrade to Cisco Unified MeetingPlace Release 7.0.2.


When you upgrade the Application Server, the system 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.

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



Contents

Preparing to Upgrade the Application Server

Before You Begin

  • Make sure that you have the Release 7.0 software available in case you need to restore your data.
  • Confirm that files can be transferred to and from the Application Server using SCP utilities or an FTP server. This can help when completing or troubleshooting the upgrade.


Tip: You do not need to uninstall the operating system or Application Server software before you upgrade.


Procedure

Task Description and Related Topics

1. Make sure that the system is running. Do not turn off the Cisco Unified MeetingPlace services.

--

2. Verify that there is sufficient free disk space in the partitions.

Verifying Available Disk Space Before Upgrading the Application Server

3. (Optional) If you have a segmented meeting access (SMA) configuration, disable SMA on your system.

"How to Disable SMA" module in the Cisco Unified MeetingPlace Release 7.1 Configuration Guide at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/products_installation_and_configuration_guides_list.html.

4. During the upgrade, 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.<version> /mail/res/email_templates. It also backs up the back-end notification templates and copies them to the same directory.

Upgrades and Notification Templates

What to Do Next

Proceed to Upgrading the Application Server.


Related Topics


Upgrading the Application Server

Before You Begin

Complete the tasks described in Preparing to Upgrade the Application Server.

Procedure

Task Description and Related Topics

Determine which upgrade procedure to follow:

a. If your Application Server is in a failover deployment...

Follow the procedure in Upgrading Application Servers that are Used in a Failover Deployment.

b. If your Application Server uses database replication for Directory Service with RSNA...

Follow the procedure in Upgrading Application Servers that are Used in a Directory Service Deployment for RSNA.

c. If your Application Server does not meet either of the above conditions...

Follow the procedure in either Upgrading the Application Server by Using the Console or Upgrading the Application Server Remotely.


Note: The log file for the upgrade is located in the /tmp directory.

Related Topics


Upgrades and Notification Templates

When you upgrade the Application Server from an earlier release, the system does the following with notification templates:

  • Overwrites all custom e-mail notification templates and replaces them with the standard e-mail notification templates for the later release.
  • Copies all of the notification templates for the Microsoft Outlook front-end deployment to a backup directory, /opt/cisco/meetingplace/var.<version> /mail/res/email_templates.
  • Copies all of the notification templates for the Microsoft Outlook back-end deployment to a backup directory, /opt/cisco/meetingplace/var.<version> /mail/res/email_templates.


See "About Customizing E-Mail Notification Templates" in the "Integrating with Microsoft Outlook" module in the Cisco Unified MeetingPlace 7.1 Integration Guide at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_installation_guides_list.html for complete information on customizing your e-mail notification templates.


Related Topics

Verifying Available Disk Space Before Upgrading the Application Server

The upgrade installer automatically removes files and folders that are safe to remove during the upgrade. At the end of the pre-installation, the summary page will display how much space is required on the /opt folder for the upgrade.


Before You Begin

The size of the upgrade bin file is indicated on the Cisco Software Download page.

Note: The upgrade file requires at least 100 MB of free space in the / and /tmp partitions.

Procedure
  1. Open an SSH to the Application Server.
  2. Enter su- to switch to the root login.
  3. Use the CLI command df –h to list the used and free space for all disk partitions.
  4. Confirm that the free space available for each meets the requirements before proceeding. If they do not meet the requirements, delete files and folders to make the free space available.
    WARNING! Do not try to remove or rename any files under /opt/cisco/meetingplace. If you still do not have enough free disk space after completing this procedure and removing unnecessary files, contact Cisco TAC to find out what can be removed.
  5. Transfer the upgrade files to the /partB folder.


Related Topics

Upgrading the Application Server by Using the Console

Before You Begin

Procedure

  1. If you have not already done so, download the Application Server upgrade files.
    1. Go to the Cisco software download page at Version/Option&treeName=Voice%20and%20Unified%20Communications&modelName=Cisco%20Unified%20MeetingPlace%207.0&treeMdfId=278875240
      If the link in Step 1 does not work, go to http://www.cisco.com/cisco/web/download/index.html then navigate to the software by selecting Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 7.1 > Unified MeetingPlace Application Server.
    2. Select your software release.
    3. Click Add to Cart next to the item you want to download, then click the Download Cart link in the upper right corner.
    4. Expand the item for details including the file checksum.
    5. When ready, click Proceed with Download and save the file to a convenient location.
  2. From the console, go to the Cisco Unified MeetingPlace operating system login page and log in as the user called root.
  3. Right-click on the desktop and select New Terminal.
    The system displays the command line.
  4. Enter whoami to verify that you are the root user.
  5. Navigate to the directory where you saved the upgrade file. Use the command md5sum <filename> to compute the MD5 checksum of the uploaded file to confirm the integrity of the upgrade file.
  6. Ensure that the .bin image is executable:
    Example:
    chmod u+x CUMP_AppServerUpgrade_7_1.bin
  7. Enter sh upgrade_mp_<version>.bin & to execute the program.
    The Install GUI displays the Introduction page.
  8. Click Next.
    The system checks to see if a previous version of the Application Server is installed. If there is a previous version, the system displays a message.
  9. Click Next to begin the upgrade.
  10. Review the pre-installation summary. If all of the values are correct, click Install.
  11. When the upgrade is complete, click Done to reboot the system.

What to Do Next

See Upgrading to Release 7.1: Overview.

Related Topics


Upgrading the Application Server Remotely

Before You Begin

  • Make sure that you have the Release 7.0 software available in case you need to restore your data.

Procedure

  1. If you have not already done so, download the Application Server upgrade files.
    1. Go to the Cisco software download page at Version/Option&treeName=Voice%20and%20Unified%20Communications&modelName=Cisco%20Unified%20MeetingPlace%207.0&treeMdfId=278875240
      If the link in Step 1 does not work, go to http://www.cisco.com/cisco/web/download/index.html then navigate to the software by selecting Voice and Unified Communications > Unified Communications Applications > Conferencing > Cisco Unified MeetingPlace > Cisco Unified MeetingPlace 7.1 > Unified MeetingPlace Application Server.
    2. Select your software release.
    3. Click Add to Cart next to the item you want to download, then click the Download Cart link in the upper right corner.
    4. Expand the item for details including the file checksum.
    5. When ready, click Proceed with Download and save the file to a convenient location.
  2. Use a utility to verify that the file checksum matches the download details.
  3. Transfer the upgrade or patch file to Cisco Unified MeetingPlace using SCP file transfer.
  4. Using an SSH client, log in as the user called mpxadmin.
  5. Enter screen -S mp_upgrade to create and attach to a screen named mp_upgrade.
    Note: 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:
    1. Using an SSH client, log in as the user called mpxadmin.
    2. Enter screen -ls to find out the full name of the screen created in Step 5. The full name of the screen consists of an identifier followed by a dot and then the name that you used in Step 5. For example, the full screen name might be 1665.mp_upgrade.
    3. Enter screen -rD <full_screen_name> to reattach to the installation screen.
  6. Change to the root user by entering su - and enter the root password.
  7. From the CLI, navigate to the directory where you saved the upgrade file. Use the command md5sum <filename> to compute the MD5 checksum of the uploaded file to confirm integrity of the upgrade file.
  8. Ensure that the .bin image is executable:
    Example:
    chmod u+x CUMP_AppServerUpgrade_7_1.bin
  9. Enter sh ./upgrade_mp_<version>.bin -i console to execute the program.
  10. Follow the screens, continuing to press Enter to advance.
  11. When the upgrade is complete, press Enter to restart the system.
    Note: When you restart the system, all existing screens are removed.

What to Do Next

See Upgrading to Release 7.1: Overview.

Related Topics

Upgrading Application Servers that are Used in a Failover Deployment

Tip: This task is documented as five separate steps. We recommend that you review all of the steps before attempting the configuration.



Before You Begin

  • Make sure of the following:
    • You have already downloaded the Release 7.1 Application Server upgrade files.
      For details, see Application Server Upgrade.
    • You have the Release 7.0 software available in case you need to restore your data.
  • Note the following nomenclature:
    • Node 1 is the original active Application Server.
    • Node 2 is the original standby Application Server.


Note: Do not leave a standby server out of production for an extended period of time. Doing so may cause the primary server to fail. If you must bring the standby server down for days or weeks at a time, disable replication before you do so.

Step 1: Prepare Node 1 for Upgrade

Procedure

  1. Log in to the CLI of Node 1. If you are logging in remotely, use the hostname (FQDN).
  2. Enter su- to switch to the root login.
  3. Enter mp_replication status on Node 1 to ensure that all database changes have been synchronized.
    The system displays the queue column as zeroes.
  4. Enter mp_replication switchOFF -r <Node 2 eth0:0-hostname> where <Node 2 eth0:0-hostname> is the eth0:0 FQDN for Node 2. This switches off replication between the two Application Servers.
  5. Enter mp_replication teardown -r <Node 2 eth0:0-hostname> where <Node 2 eth0:0-hostname> is the eth0:0 FQDN for Node 2. This tears down the replication setup with the remote Application Server.
  6. Enter failoverUtil setDeployment singleServer to change the mode of Node 1 to SingleServer.
  7. Proceed to Step 2: Back Up and Upgrade Node 1.

Step 2: Back Up and Upgrade Node 1

Before You Begin

Note: This backup/archive set is taken when the primary server is a Single Server/Standalone configuration, and can only be restored to the same server when it is in a Single Server configuration. The backup/archive cannot be used to restore to the same server when it is configured as Failover node.


Procedure

  1. Log in to the Administration Center.
  2. Click Maintenance > Backup and Archive.
  3. Set up the archiving method if your system is not already set up.
    1. Select SSH/rsync as your archiving method.
    2. Set Pathname location of archive to the directory on the remote server.
    3. Set Remote archive host to the hostname (FQDN) of the remote server.
    4. Set Remote host username and Remote host password.
    5. Set Notification email to a valid email address.
  4. From an SSH session on the Release 7.0 Application Server, make sure that you can successfully SCP a dummy file using the server/username/password path parameters you set up in this procedure.
  5. Click Save and Run Backup.
    A backup of the database is created in /db/backup/compressed_backup on the Release 7.0 Application Server.
  6. Return to the Administration Center page and click Save and Run Archiving.
    The backup files and other important files are copied to the remote server.
  7. Complete a selective check to verify that the backup and files were copied over.
  8. Navigate to the directory where you installed the Application Server upgrade files and upgrade Node 1.
  9. Reboot Node 1.
  10. Enter failoverUtil setDeployment failover 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.
  11. Proceed to Step 3: Prepare Node 2 for Upgrade.


Related Topics

Step 3: Prepare Node 2 for Upgrade

Before You Begin


Procedure

  1. Log in to the CLI of Node 2. If you are logging in remotely, use the hostname (FQDN).
  2. Enter su- to switch to the root login.
  3. Enter failoverUtil setServer active on Node 2 to change its mode from standby to active.
  4. Enter mp_replication teardown -r <Node 1 eth0:0-hostname> where <Node 1 eth0:0-hostname> is the eth0:0 FQDN for Node 1. This tears down the replication setup with the remote Application Server.
  5. Enter failoverUtil setDeployment singleServer on Node 2 to change its mode to SingleServer.
  6. Proceed to Step 4: Backup and Upgrade Node 2.

Step 4: Backup and Upgrade Node 2

Before You Begin


Note: This backup/archive set is taken when the secondary server is in a Single Server/Standalone configuration, and can only be restored to the same server when it is in a Single Server configuration. The backup/archive cannot be used to restore to the same server when it is configured as Failover node.


Procedure

  1. Log in to the Administration Center.
  2. Click Maintenance > Backup and Archive.
  3. Set up the archiving method if your system is not already set up.
    1. Select SSH/rsync as your archiving method.
    2. Set Pathname location of archive to the directory on the remote server.
      Make sure that the pathname is distinct from the one you used for storing archives in Node 1.
    3. Set Remote archive host to the hostname (FQDN) of the remote server.
    4. Set Remote host username and Remote host password.
    5. Set Notification email to a valid email address.
  4. From an SSH session on the Release 7.0 Application Server, make sure that you can successfully SCP a dummy file using the server/username/path parameters you set up in this procedure.
  5. Click Save and Run Backup.
    A backup of the database is created in /db/backup/compressed_backup on the Release 7.0 Application Server.
  6. Return to the Administration Center page and click Save and Run Archiving.
    The backup files and other important files are copied to the remote server.
  7. Complete a selective check to verify that the backup and files were copied over.
  8. Navigate to the directory where you installed the Release 7.1 Application Server upgrade files and upgrade Node 2.
  9. Reboot Node 2.
  10. Enter failoverUtil setDeployment failover to change the mode of Node 2 to failover.
    At this point, both Application Servers are in standby mode.
  11. Enter the following command to initialize database replication on Node 2:
    mp_replication init -n 2 -r <node1-eth0:0-hostname> [-v]
  12. Proceed to Step 5: Configure Failover Mode.


Related Topics

Step 5: Configure Failover Mode

Before You Begin

Complete Step 4: Backup and Upgrade Node 2.


  1. Log in to the CLI of Node 1.
    If you are logging in remotely, use the hostname (FQDN).
  2. Enter the following commands to initialize and start database replication:
    mp_replication init -n 1 -r <node2-eth0:0-hostname> [-v]
    mp_replication switchON
  3. Enter failoverUtil setServer active on Node 1 to change its mode to active.
    Both servers are now in failover mode. Node 1 is the active Application Server and Node 2 is the standby Application Server.

What to Do Next

Related Topics

Upgrading Application Servers that are Used in a Directory Service Deployment for RSNA

Tip: This task is documented as three separate steps. We recommend that you review each step before attempting the configuration.


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 any changes are made, initial setup procedures may have to be followed to synchronize the data between the two Application Servers, depending on the type of changes made on the two servers.


Before You Begin

  • Note the following nomenclature:
    • Node 1 is the server that is in site 1.
    • Node 2 is the server that is in site 2.

Step 1: Upgrade Node 1 in a Directory Service Deployment

Before You Begin


Procedure

  1. Log in to the CLI of Node 1.
  2. Enter su to switch to the root login.
  3. Enter mp_replication status on Node 1 to ensure that all database changes have been synchronized.
    The system displays the queue column as zeroes.
  4. Enter mp_replication switchOFF -r <node2-hostname>
    where <node2-hostname> is the FQDN for Node 2. This switches off replication between the two Application Servers.
  5. Enter mp_replication teardown -r <node2-hostname>
    where <node2-hostname> is the FQDN for Node 2. This tears down the replication setup with the remote Application Server.
  6. Archive and save the configuration data on Node 1.
  7. Upgrade Node 1.
  8. Proceed to Step 2: Upgrade Node 2 in a Directory Service Deployment.

Step 2: Upgrade Node 2 in a Directory Service Deployment

Before You Begin


Procedure

  1. Log in to the CLI of Node 2.
  2. Enter su to switch to the root login.
  3. Enter mp_replication teardown -r <node1-hostname>
    where <node1-hostname> is the FQDN for Node 1. This tears down the replication setup with the remote Application Server.
  4. Upgrade Node 2.
    Both Application Servers are now upgraded.
  5. Proceed to Step 3: Turn on Replication Between the Two Servers.

Step 3: Turn on Replication Between the Two Servers

Before You Begin

Complete Step 2: Upgrade Node 2 in a Directory Service Deployment.


Procedure

  1. Log in to the CLI of Node 2.
  2. Enter su to switch to the root login.
  3. Enter the following command using the FQDN of Node 1:
    mp_replication init -s 2 -r <node1-hostname > [-v]
  4. Log in to the CLI of Node 1.
  5. Enter su to switch to the root login.
  6. Enter the following commands using the FQDN of Node 2:
    mp_replication init -n 1 -r <node2-hostname> [-v]
    mp_replication switchON [-v]
  7. (Optional) Synchronize Node 1 and Node 2.
    • Database replication is not active during the upgrade so if any User/Group configuration changes are made on either server, they will not propagate to the other server. To see how many Users and Groups are present in a server, run the dbsize command as root. If there is a difference and configuration changes were only made on one server, synchronize the differences by using the following command on Node 1:
    mp_replication switchON -S -F <hostname to sync from>
    • Depending on the number of Users/Groups and the network bandwidth between the two servers, the sync may take several hours.


Note: If configuration changes for users or groups were made on both servers, automatic sync may not be possible. In such a scenario, the options are as follows:

  • Restore the servers from the backups that were taken just before tearing down replication. Setup replication again.
  • Clear the data of one server and follow the initial instructions of adding an empty server to an existing server in a directory services setup.

Related Topics

Troubleshooting the Application Server Upgrade

Problem: There is an issue with the 7.1 upgrade and I want to restore my Cisco Unified MeetingPlace system back to Release 7.0.

Solution: It is possible to restore your system back to Release 7.0 as long as you completed the following prior to the upgrade attempt:

  • Backed up the 7.0 system.


If you have satisfied these requirements, proceed to:


Note: You must have your original Release 7.0 installation DVD.

Note: Since you are restoring from the latest Release 7.0 backup, you will lose any data added after you upgraded your system to Release 7.1.




Problem: The system displayed a message stating that it does not have enough disk space to install the upgrade.

Possible Cause: This may be caused by having too many earlier releases on the server.

Solution: Ensure that you have enough disk space on your system to install an upgrade. Previous releases on the system take up disk space. If the previous releases are not needed, delete them by using the mpx_cleanup command in the Command Line Interface (CLI). See the following process.

Restrictions: This command removes the previous releases that you select. However, it will not remove the first or last release on the system. Therefore, you must have at least three releases of Cisco Unified MeetingPlace installed on your system to successfully run this command.

Procedure:

  1. Log in to the CLI.
    See the "Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace" module in the ''Cisco Unified MeetingPlace Release 7.1 Reference Guide at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_technical_reference_list.html.
  2. Enter su - to switch to the root login.
  3. Enter mpx_cleanup to determine the release numbers installed on the system.
  4. Enter mpx_cleanup <release number>, where <release number> is the release number displayed in the CLI of the release you want to delete.
  5. Enter y to confirm that you really want to remove this version.
  6. Enter mpx_cleanup again to verify that the release that you just removed is gone.



Problem: The system displayed a message stating that it still does not have enough disk space to install the upgrade, even after removing previous releases.

Solution: Free up enough disk space on your system to install an upgrade by using the Command Line Interface (CLI). See the following procedure.

Procedure:

  1. Log in to the CLI.
    See the "Using the Command-Line Interface (CLI) in Cisco Unified MeetingPlace" module in the ''Cisco Unified MeetingPlace Release 7.1 Reference Guide at http://www.cisco.com/en/US/products/sw/ps5664/ps5669/prod_technical_reference_list.html.
  2. Enter su - to switch to the root login.
  3. Enter IATEMPDIR=/partB. You can replace partB with any directory that has sufficient space.
  4. Enter export IATEMPDIR.

Rating: 0.0/5 (0 votes cast)

Personal tools