Cisco WebEx Meetings Server Administration Guide Release 2.0
Upgrading the System
Downloads: This chapterpdf (PDF - 1.3MB) The complete bookPDF (PDF - 3.89MB) | The complete bookePub (ePub - 1.48MB) | Feedback

Upgrading the System

Upgrading the System

Preparing for an Upgrade

Your system can be upgraded by redeploying it with an upgraded OVA (Virtual Server Template) file. The upgrade procedure creates a parallel system and the data from the original system is transferred to the upgraded system as part of the upgrade process. If the upgraded system fails testing, you can restart the original system to restore service, fix any errors, and redeploy an upgraded system.

An upgrade is defined as a replacement of the system to deploy major modifications that we made to the system. For example replacing a system currently running version 1.0 to run version 2.0 that includes support for a new operating system. An update is defined as overwriting an existing (original) system to take advantage of modifications that we made to improve the system. For example, you might update a system from version 1.5 to 1.5MR by using the Updating the System procedure. Check the release notes for the correct procedure to use. In both cases, all of the data from the original system is transferred to the updated or upgraded system.

The system can be upgraded automatically or manually. We recommend that you upgrade the system by using the automatic process.

When upgrading:

  • Do not attempt to upgrade a system to an incremental release; upgrade to the next full version of the application. For example, upgrade your system from 1.5 to 2.0. Update your system from 1.1 to 1.5.
  • Verify that the time settings for all VMs match:
    • Ensure time is correct and that Network Time Protocol (NTP) is running. (See Configuring the ESXi Host to Use an NTP Server.)
    • Confirm the NTP configuration on each ESXi host is configured to start and stop with the host.
    • If it is necessary to modify the configuration to correct any of these issues, verify that all VMs on the hosts are gracefully powered OFF.
  • When you upgrade a Cisco WebEx Meeting Server, the log captures saved on the original system are not transferred to the updated Cisco WebEx Meeting Server system. Therefore, you should capture and download any logs and log captures that you need from the original system before you start the upgrade.
  • The 2.0 Admin VM must be on the same ESXi host as the 1.x Admin VM.
  • For new installations of Cisco WebEx Meetings Server Release 2.0, the storage requirements are:
    • Disk space can be local (DAS) or external (SAN or NAS).
    • ESXi hosts (Cisco UCS server) with the Admin virtual machine require 1.5 TB of disk space.
    • ESXi hosts (Cisco UCS server) without an Admin virtual machine require 1 TB of disk space.
    • When upgrading to Cisco WebEx Meetings Server Release 2.0 from Release 1.x by using existing Cisco UCS servers, the ESXi hosts requires 1118 GB of free disk space if the UCS server has only the Admin virtual machine (primary or HA system) or 990 GB of free disk space if the UCS server has one Admin and one Media virtual machine (primary or HA system).
    For complete details, see the Resources Consumed by Cisco WebEx Meetings Server and the ESXi Host section in the http:/​/​www.cisco.com/​c/​en/​us/​support/​conferencing/​webex-meetings-server/​products-installation-and-configuration-guides-list.html.

Note


We refer to the system in place before initiating the upgrade as the original system. The system in place following upgrade is referred to as the upgraded system.

Before You Begin an Automatic or Manual Upgrade

Before upgrading a system automatically or manually, the following issues should be addressed:

  • Obtain the OVA file required for the upgrade.
  • Remove all VMware snapshots of the original (existing) system. Do not take any snapshots during the upgrade process.
  • Create a backup for each virtual machine in your original (existing) system. (See Creating a Backup by using VMware vCenter.)
  • Plan a maintenance outage. During the upgrade process the original system is placed into maintenance mode and requires exclusive access to the system; users cannot access the system for meetings during this time. Schedule this portion of the upgrade for a time that is the least disruptive to your users.
  • Plan for the increased size of the data stores, as the original system and the upgraded system share data stores until testing of the upgraded system is complete and the original system is removed.
  • Verify that the original system hostnames and IP addresses are reused in the upgraded system. Also that the internal virtual machines for both systems are on the same subnet. If you have added public access, the Internet Reverse Proxy virtual machines for the original system and the upgraded system should be on the same subnet.
  • Verify that the vCenter hostname can be resolved by the DNS server. Test the link by pinging the hostname.

Upgrading the System Automatically

Before You Begin an Automatic Upgrade

Before upgrading a system by using the automatic upgrade process, the following issues should be addressed:

  • Notify other system administrators that they should not access or make changes to the original system during the upgrade, as their changes might yield unpredictable results.
  • Provide and configure one additional IP address and hostname that will be used temporarily for the administration virtual machine on the upgraded system. This can be any available IP address in the VLAN. The hostname can be anything you want, as this IP address and hostname will be released at the end of the upgrade process. The original system and the upgraded system are both powered up during the upgrade process. The temporary IP address and hostname prevents IP conflicts during this part of the procedure. After the data is transferred from the original system to the upgraded system, the original system is powered down. At the end of the automatic upgrade, the upgraded system is taken out of maintenance mode and reboots. During the reboot, the temporary IP address and hostname are released and the upgraded system uses the original administration virtual machine IP address and hostname. If there is a firewall between the administration virtual machines and the IRP virtual machines, the temporary IP address must be allowed through the firewall.
  • Do not manually power on or shut down either system.
  • Verify that vSwitch is not used on ESXi hosts as a distributed switch. The automatic upgrade process does not support vSwitch Distributed Switch on CWMS ESXi hosts. Change to a standard switch or use theUpgrading the System Manually process.

Using Automatic Upgrade

This table lists the high-level tasks needed to complete an automatic upgrade. It includes links to sections of the Cisco WebEx Meetings Server Administration Guide that provide the detailed steps necessary to complete each task. (To move easily between this table and the individual task in Adobe Acrobat, select Previous View or Next View.)

Task Description For Details, See
1 Go to the license manager on the original system and generate a license request by selecting System > View more > Manage Licenses. License manager opens in a new tab.

Select Generate License Request. A pop-up appears with the license request text. Copy the text and save the license request in a convenient location as it might be necessary to use the manual re-host procedure to reclaim your licenses. This information can also help Cisco to find your licenses.

Fulfilling Licenses by using the License Manager
2 Using the vSphere client, deploy the Admin virtual machine (by using the temporary IP address) for the upgraded system by selecting the configuration with the Auto-upgrade suffix, for example 250 Users Admin Auto-upgrade.
3

Verify that the 2.0 Admin VM can reach the 1.X disks.

The Admin VMs are on the same ESXi host and have access to the same data stores, therefore they should be able to view both sets of disks.

The datastore used by the 1.x Admin VM datastore (vmdk) files should be visible through the vCenter (by using the same vCenter credentials that the automatic upgrade process uses).

 
4 Power on the Administration virtual machine for the upgraded system and write down the deployment URL displayed on the virtual machine console.  
5 Enter the deployment URL into a web browser URL field.  
6 Enter the Administration and vCenter URLs and credentials, so we can deploy the virtual machines for you. Providing VMware vCenter Credentials
7 To deploy any additional virtual machines, select Continue. (Until you begin the setup of the upgraded system and the original system is placed in maintenance mode, users can hold meetings, but administrators should not modify the original system virtual machines.)

The progress of the upgrade is displayed on the deployment URL of the upgraded system and on the VMware console connected to the primary system Admin virtual machine.

The VMware console provides the deployment URL to use in case the browser window inadvertently closes during the upgrade process.

8

Note the names of the automatically-created virtual machines listed in vCenter. The format for virtual machine names is:

CWMS_hostname_MMDDHHmm

where mm=minute

When the upgrade is complete, the virtual machines do not display. To find the virtual machines that were created as part of the CWMS upgrade, you can search based on this format.

9 To automatically put the system in maintenance mode and begin the setup of the upgraded system, select Continue. A message displays when Maintenance Mode is enabled, which might take up to 30 minutes.
10 To launch the upgraded Cisco WebEx Administration site, select Sign In to Administration Site.
11

Turn off maintenance mode on the upgraded system. The system reboots.

It might take a few minutes for the meeting service to become available. Your system is ready for users to start meetings when all the virtual machines listed on the System Properties page display a status of Good (green). See Turning Maintenance Mode On or Off for more information.

12 Test the upgraded system. If the upgrade is unsuccessful, power off the upgraded system, power on the original system, and contact Cisco TAC. About System Testing
13 Re-host and update the license version as appropriate for the upgraded system. Within 180 days or less the license-free grace period shall expire. If the original system had valid licenses, those licenses must be re-hosted in 180 days or less. If the original system was operating in the license-free grace period, the remaining unexpired days are transferred to the upgraded system. About Licenses Re-hosting Licenses after a Major System Modification
14 If the previously deployed Cisco WebEx Meetings Application or Productivity Tools are different versions or build numbers from a newly deployed version of the application and the upgrade is not blocked, you are notified by an upgrade warning dialog box. It might be necessary to push the Cisco WebEx Meetings Application or Productivity Tools to the users.

See the Cisco WebEx Meetings Application and Productivity Tools Compatibility Matrix section of the Cisco WebEx Meetings Server Planning Guide and System Requirements, found at http:/​/​www.cisco.com/​c/​en/​us/​support/​conferencing/​webex-meetings-server/​products-installation-and-configuration-guides-list.html.

Upgrading the System Manually

Before You Begin a Manual Upgrade

Verify that the upgraded system can access the disks for the original system Admin virtual machine. (Hard disk 4 will be copied from the original system to the upgraded system.)

Do not power on and run both systems at the same time, because the hostnames and IP addresses from the original virtual machines are used in the upgraded system.

Upgrading the System Manually

Some of the tasks in this table include links to other sections of the Cisco WebEx Meetings Server Administration Guide. These sections provide detailed information on that task. (To move easily between this table and the individual task in Adobe Acrobat, select Previous View or Next View.)

Task Description For Details, See
1 Go to the license manager on the original system and generate a license request by selecting System > View more > Manage Licenses. License manager opens in a new tab.

Select Generate License Request. A pop-up appears with the license request text. Copy the text and save it the license request in a convenient location as it might be necessary to use the manual re-host procedure to reclaim your licenses. This information can also help Cisco to find your licenses.

About Licenses
2 Login to the Administration site of the original system.
3 Go to the System tab and select Upgrade.
4

Select Major Upgrade.

5

Select Continue to archive the original system data and put the system into maintenance mode.

6 Using the VMware vSphere client, select Power > Shut Down Guest on the virtual machines for the original system.  
7 Deploy all of the upgraded system virtual machines, including the HA and IRP virtual machines.

During deployment there is an option to Power on VM after deployment. Verify that this is not checked or that the VMs have been started manually before the next step is complete; otherwise, it will cause the VMs to deploy as a new system and create a new deployment instead of migrating the data. If the VMs are powered on, they must be deleted and redeployed before proceeding.

Deploying the OVA File From the VMware vSphere Client
8 Copy the data from your original system to the Admin virtual machine for the upgraded system. Attaching an Existing VMDK File to a New Virtual Machine
9 Power on the upgraded Admin virtual machine and write down the deployment URL displayed on the virtual machine console. If the system will include high availability (HA), do not setup the HA virtual machines from HA Admin Deployment; allow the upgrade script to discover the HA virtual machines. (See Configuring a High Availability System.)  
10 Power on the other upgraded virtual machines.
11 Enter the deployment URL into a web browser.  
12 Select Continue to launch the system setup.

The progress of the upgrade is displayed on the deployment URL of the upgraded system and on the VMware console connected to the primary system Admin virtual machine.

The VMware console provides the deployment URL to use in case the browser window inadvertently closes during the upgrade process.

13 Select Turn Off Maintenance Mode and Continue to confirm.

It might take a few minutes for the meeting service to become available. Your system is ready for users to start meetings when all the virtual machines listed on the System Properties page display a status of Good (green). See Turning Maintenance Mode On or Off for more information.

14 When the system setup is complete, select Sign in to Administration site.  
15 Test the upgraded system.

When your upgraded system is running satisfactorily, you can delete your original system to free the original system resources. Keep the upgraded system running while deleting the original system to prevent the accidental removal of the Hard disk 4 base VMDK file that might be accessed by the upgraded system.

If the upgrade is unsuccessful, contact Cisco TAC and power off the upgraded system and power on the original system.

About System Testing
16 Re-host and update the license version as appropriate for the upgraded system. Within 180 days or less the free trial period shall expire. If the original system had valid licenses, those licenses must be re-hosted in 180 days or less. If the original system was operating in the license-free grace period, the remaining unexpired days are transferred to the upgraded system. About Licenses Re-hosting Licenses after a Major System Modification
17 If the previously deployed Cisco WebEx Meetings Application or Productivity Tools are different versions or build numbers from a newly deployed version of the application and the upgrade is not blocked, you are notified by an upgrade warning dialog box. It might be necessary to push the Cisco WebEx Meetings Application or Productivity Tools to the users.

See the Cisco WebEx Meetings Application and Productivity Tools Compatibility Matrix section of the Cisco WebEx Meetings Server Planning Guide and System Requirements, found at http:/​/​www.cisco.com/​c/​en/​us/​support/​conferencing/​webex-meetings-server/​products-installation-and-configuration-guides-list.html.

License Re-host and Upgrade

Re-hosting allows the original system licenses to be used on the upgraded system for a limited period of time. If the licenses are not re-hosted, they cannot be fully upgraded. Within 180 days or less the grace period shall expire. Following a software upgrade:

  • If the original system was operating without licenses and within the free-trial period, the remaining number of license-free days is transferred to the upgraded system.
  • If the original system had valid licenses, those licenses are valid for up to 180 days before they must be re-hosted (see Re-hosting Licenses after a Major System Modification) and updated.

Accessing the GLO Request Form

To display the Global Licensing Operations (GLO) request form, select Contact Us on the Product License Registration page (https:/​/​tools.cisco.com/​SWIFT/​LicensingUI/​Quickstart). On the GLO Support Contact Information page, select request.

Before You Begin

Be prepared to provide the following information:

  • Contact information
  • Problem description
  • Product name and licensing activity (such as resend license information or upgrade license)
  • Entitlement information (such as a product serial number)

Re-hosting Licenses after a Major System Modification

After a system has been modified as the result of an action such as an upgrade or expansion, and testing is complete, the next step is to re-host your Permanent licenses. Re-hosted licenses are automatically invalidated on the original system. Before you begin the re-host, preserve a license request from the original system in case it is needed to re-host the licenses.

When re-hosting licenses, the number of licenses that you can re-host is limited to the number of licenses on the original system. The preferred method of re-hosting licenses is through the Product License Registration portal.

If the original system had licenses, the upgraded system allows you a 180-day free trial period before licenses are required, allowing you time to test the upgraded system before re-hosting the original licenses on the upgraded system. Once the licenses are re-hosted, the free trial period ends. Re-hosting can be done by using the Product License Registration Portal at http:/​/​tools.cisco.com/​SWIFT/​LicensingUI/​Home (see Accessing the GLO Request Form. If the original system was already operating on a free trial period, the upgraded system free trial period is equal to that amount of free trial period that was on the original system when it was updated. If the original system was locked due to an expiration of the free trial period or a lack of Installed licenses, the upgraded system will also be locked.

Generate a License Request

To acquire a license request for the original system:

Procedure
    Step 1   From the original system Admin window, select the System window.
    Step 2   Select (under Licenses) view more > Manage Licenses.
    Step 3   Select Other Fulfillment Options > Generate License Request.
    Step 4   Copy the content and save the license request in a file on the PC.

    What to Do Next

    Register the licenses. See Register Licenses to be Re-hosted for instructions.

    Register Licenses to be Re-hosted

    To use the Product License Registration portal:

    Procedure
      Step 1   Log in to the Product License Registration portal at https:/​/​tools.cisco.com/​SWIFT/​LicensingUI/​Quickstart.
      Step 2   Log in to the cisco.com account that was used to fulfil licenses for your original system.

      If this account is not available or if you login and do not find licenses associated with this account, open a case with Cisco (see Accessing the GLO Request Form).

      Step 3   Select Transfer > License for transfer - Initiate. The Specify License Source tab appears.
      Step 4   Select the checkbox beside the UUID of the 1.X system from where you want to re-host licenses. If you have multiple systems and you do not know the UUID of the one you want to re-host, go back to the original system and launch the license manager. In the Licenses window look in the File Name column for a license string, for example c8be79aeecaba5922955b53679527463_201311182150051080. The string of characters from the beginning of the string to the underscore (_) delimiter is the UUID.
      Step 5   Go to the Product License Registration portal.
      Step 6   Select the licenses you want to re-host and select Next. The Specify Target & Options window displays.
      Step 7   Paste the license request in the target system License Request field and select Next. The target system is the system to where you are moving licenses. If this is a software upgrade, the target is the upgraded system. If this is a system expansion, the target is the larger system. If this is a disaster recovery, the target is the post-recovery system. The Review window appears.
      Step 8   Select the I agree to the terms of the license agreement checkbox and click Submit. You are sent an email containing your re-hosted licenses. Note that if you are doing the re-host as part of a software upgrade, you must re-host (see Re-hosting Licenses after a Major System Modification) and update the 1.0 licenses on your 2.0 system. An error message, such as You are using an invalid license file with your current deployment might display on the administration site of your upgraded system. This is expected. An expiration date indicating when your system will be disabled, is included in the message. Upgrade your licenses before the expiration date or your system will be disabled.

      What to Do Next

      After re-hosting the licenses, complete the license upgrade before the date shown to assure the uninterrupted use of the system. See Fulfilling Licenses by using the License Manager for more information.

      Upgrading Licenses after a Software Upgrade

      After a software upgrade, Installed licenses are re-hosted from the original system on the upgraded system. (See Re-hosting Licenses after a Major System Modification for more information.) After the licenses have been re-hosted, they can be upgraded for use on the upgraded system.

      The association of users to licenses is deleted. Users are associated with licenses the first time they host a meeting.

      To upgrade your Installed licenses by using eFulfilment:

      1. Obtain a Product Authorization Key (PAK) code from your vendor.
      2. From the System window select (under Licenses) view more>Manage Licenses> Licenses> Fulfil Licenses from PAK. The Fulfil Licenses from PAK window is shown.
      3. Enter the PAK code and select Next.
      4. Log in by using your cisco.com account credentials. The Fulfill Licenses from PAK window is shown.
      5. Click the Install column to select the number of licenses you want to install.
      6. Indicate the number of licenses to be installed and select Save. The licenses are installed on the system as part of the eFulfillment from the PAK.

        Note


        The number of licenses that you can install is limited to the number of licenses available from the upgrade PAK and cannot exceed the number of licenses that were re-hosted from the original system.

      To upgrade the version of your Installed licenses from a license file:

      1. Obtain a license file from your vendor by using cisco.com/go/license.
      2. From the System window select (under Licenses) view more>Manage Licenses> Licenses> Fulfil licenses from file. The Install Licenses File window is shown.
      3. Browse in the license file. The file is shown on the Licenses window.

      The licenses are updated.