Cisco WebEx Meetings Server Administration Guide Release 2.0
Expanding Your System to a Larger System Size
Downloads: This chapterpdf (PDF - 1.19MB) The complete bookPDF (PDF - 3.85MB) | The complete bookePub (ePub - 1.48MB) | Feedback

Expanding Your System to a Larger System Size

Expanding Your System to a Larger System Size

Preparing for System Expansion

System expansion requires the deployment of a new primary system, and the transfer of the system data from the original system to the expanded system. Expansion of a system requires that your existing Host licenses be re-hosted on the expanded system. (See Re-hosting Licenses after a Major System Modification.)

Considerations for an Expanded System

Consider the following:
  • Budgeting for any additional hardware.

  • Anticipating the number of concurrent meetings and their average size over the next few months.

  • When an original system is upgraded or expanded, a parallel system is created. If there is time left in the trial period of the original system, that time is transferred to the upgraded or expanded system. Valid Permanent Host licenses on the original system can be transferred to an upgraded or expanded system by re-hosting the licenses.

Obtaining the Information Required For System Expansion

Obtain the OVA file used to install the existing system version and complete the expansion checklist:

Field Name Current Value For Your System
WebEx Site URL  
Administration Site URL  
Private VIP Address  
Public VIP Address  

Expanding the System Size

Procedure


    Step 1   Sign in to the Administration site.
    Step 2   Create a backup of the original system.
    Step 3   Turn on Maintenance Mode. See Turning Maintenance Mode On or Off for Version 2.0 and Before.

    We recommend that you take a snapshot of each virtual machine. (See Taking a Snapshot by using VMware vCenter.)

    Turning on Maintenance Mode on all active data centers shuts down conferencing activity and prevents users from signing in to the WebEx site, scheduling meetings, joining meetings, or playing meeting recordings. See About Maintenance Mode for information about which system tasks require Maintenance Mode to be turned on.

    Step 4   Select Continue.
    Step 5   Select System > View More.
    Step 6   Select Expand System Size.
    Step 7   Select Continue.

    Your system checks connectivity to the virtual machines. If there are connectivity problems with one or more virtual machines, you must fix the problems before you can continue. If there are no connectivity problems, your system performs an automatic backup. After the backup is complete, you are notified that you can proceed with your expansion.

    Step 8   Using the VMware vSphere client, select Power > Shut Down Guest on the virtual machines for the original system. (See Deploying the OVA File From the VMware vSphere Client.)
    Step 9   Using the vSphere client, deploy the Admin virtual machine for the new system size.

    If you are performing an automatic expansion, we will create the other virtual machines for your system. If you are performing a manual expansion, you can create the other virtual machines for your system.

    Step 10   Attach Hard disk 4 from the original system Admin virtual machine to the Admin virtual machine for the expanded system. (See Attaching an Existing VMDK File to a New Virtual Machine.)
    Step 11   Power on the Admin virtual machine for the expanded system and write down the deployment URL.

    If you are performing an automatic expansion, we will power on the other virtual machines for your system. If you are performing a manual expansion, power on the other virtual machines for your system.

    Step 12   Enter the deployment URL into a web browser and continue the deployment of your expanded system.
    Step 13   Select your preferred language for the deployment of the expanded system. (See Selecting Your Language for Setup.)
    Step 14   Select Expand the capacity of existing system > Next.
    Step 15   Confirm the system size. (See Confirming the Size of Your System.)

    This system size must be larger than or equal to the original system.

    Step 16   Select Install a primary system.
    Step 17   Select automatic or manual deployment. (See Choosing the Type of Deployment.)

    If you chose manual deployment, continue to the next step. If you chose automatic deployment:

    1. Enter your vCenter credentials so that we can deploy the virtual machines for you. (See Providing VMware vCenter Credentials.)
    2. Select the ESXi host, datastore, and virtual machine port group for the Media virtual machine. (See Choosing vCenter Settings for your Media Virtual Machine.)
    3. Enter the fully qualified domain name of the Media virtual machine.

      If you have already updated your DNS server with entries for the expanded system, then we will look up the IP address for you. (See Entering Networking Information for the Media Virtual Machine.)

    Use the same OVA file you used to deploy your original system and deploy the Admin virtual machine for the new system size.

    Your system notifies you once the expansion is complete.

    Step 18   If you want public access for your expanded system, then ensure there is a check in the Create an Internet Reverse Proxy virtual machine check box. Otherwise, uncheck this check box. (See Adding Public Access to Your System by using IRP.)

    If you have chosen to add public access:

    1. Select the ESXi host, data store, and virtual machine port group for the Internet Reverse Proxy (IRP) virtual machine.
    2. Enter the hostname and networking information for the IRP virtual machine.
    Step 19   Enter the public VIP address for the WebEx site URL. (See Entering the Public VIP Address.)

    You can enter the same public VIP address that you use for your original system, or change it to a new IP address. If you change it, then make the necessary updates in the DNS server.

    Step 20   Enter the private VIP address for the WebEx site URL. (See Entering the Private VIP Address.)

    You may enter the same private VIP address that you use for your original system, or change it to a new IP address. If you change it, then make the necessary updates in the DNS server.

    Step 21   Enter the WebEx Common site URL. (See Entering the WebEx Common Site and Administration Site URLs.)

    Participants access this URL to host and attend meetings. This URL resolves to the private VIP address or the public VIP address, depending on whether or not you are using a split-horizon DNS.

    You may enter the same WebEx site URL that you use for your original system, or change to a new one. If you do change it, then make the necessary updates in the DNS server.

    Retain your original site URL on the DNS server. Redirect your original site URL to the new site URL. If users attempt to use the original URL and you have not redirected it to the new URL, they will not be able to host or join meetings.

    Step 22   Enter the WebEx Administration site URL for administrators to access the Cisco WebEx Administration site. (See Entering the WebEx Common Site and Administration Site URLs.)

    This URL resolves to the private VIP address.

    You can enter the same WebEx site URL that you use for your original system, or change to a new one. If you do change it, then make the necessary updates in the DNS server.

    Retain your original site URL on the DNS server. Redirect your original site URL to the new site URL. If users attempt to use the original URL and you have not redirected it to the new URL, they will not be able to host or join meetings.

    Step 23   Verify that you have made all the networking, DNS server, and firewall configuration changes required for your system. (See Confirming that the Network is Configured Correctly.)
    Step 24   After your virtual machines have deployed successfully, select Next to continue to the system check. (See Deploying Virtual Machines.) Along with the system check, we update the expanded system with any required updates to match the software version of the original system, before expansion. (These updates might take up to an hour.) When complete, the system restarts. (See Checking the System.)
    Step 25   Select Restart.
    Step 26   Sign into the Administration site.
    Step 27   Turn off Maintenance Mode. See Turning Maintenance Mode On or Off for Version 2.0 and Before.

    When you turn off Maintenance Mode, the system determines if a restart (takes approximately 3 - 5 minutes) or a reboot (takes approximately 30 minutes) is required and displays the appropriate message.

    Meeting service for users on this data center is restored.
    Step 28   Select Continue. The system restarts. You can sign into the Administration site when the restart is completed.
    Note   

    If you originally created the virtual machines by using the Cisco WebEx Meetings Server 2.0 OVA file, then you might see a "Cannot access server" error message. If this happens, then use the VMware vSphere client and "Restart Guest" for all the virtual machines in the system.

    Step 29   Test the expanded system. (See About System Testing.)

    If the expansion is unsuccessful, then power off the expanded system and power on the original system. If necessary, contact Cisco TAC for further assistance.

    Step 30   Re-host the Host licenses as appropriate for the expanded system. (See About Host Licenses and Re-hosting Licenses after a Major System Modification .)