Cisco WebEx Meetings Server Administration Guide Release 2.0
Expanding Your System to a Larger System Size
Downloads: This chapterpdf (PDF - 1.23MB) The complete bookPDF (PDF - 3.89MB) | 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. This section describes the prerequisites necessary for a system expansion.


Note


Expansion of a system requires that your existing system licenses be re-hosted on the expanded system. (See Re-hosting Licenses after a Major System Modification.)


Determining the Size of the New System

Consider the following:
  • Budgeting for any additional hardware.
  • Anticipating the number of concurrent meetings and their average size over the next few months.

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 by using Automatic Deployment

Before You Begin


Note


The system before expansion is referred to as the original system. The system following expansion is the expanded system.

Schedule a time that is least disruptive to your users to do the system expansion.

Put the primary system in maintenance mode before starting the system expansion.


Caution


Because this procedure requires exclusive access to the system, users cannot access the system for meetings. Be sure to schedule this procedure during a time that will be least disruptive to your users.

Coordinate with other system administrators before starting a system-altering procedure. Other system administrators should not access the system during this procedure. If they do so, their changes are not saved, and the result can be unpredictable.

Considerations Before Expanding the System

  • Be sure to remove all VMware snapshots of your original system before starting the expansion procedure.
  • You can reuse the same hostnames and IP addresses for the original virtual machines in the expanded system. However, only the original system or the expanded system can be powered on; both systems cannot be powered on and running at the same time.
  • If you had HA on the your original system, then after the deployment of the expanded system you must add HA to the expanded system. You cannot reuse the HA system, as it is not retained after an expansion.
  • You can keep the original system until you have finished testing the expanded system. Once testing is complete and you are satisfied with the expanded system, you can remove the original (pre-expansion) system.
  • The internal virtual machines for the original system and the expanded system must be on the same subnet.
  • If you have added public access, the Internet Reverse Proxy virtual machines for the original system and the expanded system must be on the same subnet.
  • When you add a new virtual machine to the system, your current security certificate and public and private keys become invalid and require an update, unless you are using a self-signed certificate. Certificates include hostnames and URLs. The certificate and keys become invalid because they do not include the new virtual machine. For complete information on certificates and keys, see Managing Certificates.
  • Be sure the expanded system can access the disks for the original system Admin virtual machine. You will be copying Hard disk 4 to the expanded system.
  • Be sure your expanded system is up and running while removing or deleting your original system. This prevents accidental removal of the Hard disk 4 base VMDK file that might be accessed by the expanded system.

Expanding the System

The overall tasks to expand the system are:

  1. Create a backup of the original system.
  2. Use the same OVA file you used to deploy your original system and deploy the Admin virtual machine for the new system size.
  3. Copy the data from your original system to the Admin virtual machine for the expanded system.
  4. Deploy any additional virtual machines for the new system size.
  5. Test the expanded system.
  6. Re-host the licenses.

Summary of Tasks to Expand the System by using Automatic Deployment


Note


This table includes links to other sections of the Cisco WebEx Meetings Server Administration Guide. Each of these sections provides detailed information on the specific task. After you complete each task, return to this table to complete the next task. (Use Previous View and Next View in Adobe Acrobat to move easily between this table and the individual task procedures.)


Task Description For Details, See
1 Prepare the original system for expansion. You completed this task earlier in this chapter. It is included in this table for completeness.
2 Prepare for a system-altering procedure. You completed this task earlier in this chapter. It is included in this table for completeness.
3 Initiate the expansion procedure from the Administration site of the original system. Expanding the System Size
4 Using the VMware vSphere client, select Power > Shut Down Guest on the virtual machines for the original system.  
5 Using the vSphere client, deploy the Admin virtual machine for the new system size. Deploying the OVA File From the VMware vSphere Client
6 Attach Hard disk 4 from the original system's Admin virtual machine to the Admin virtual machine for the expanded system. Attaching an Existing VMDK File to a New Virtual Machine
7 Power on the Admin virtual machine for the expanded system and write down the deployment URL.  
9 Enter the deployment URL into a web browser and continue the deployment of your expanded system.  
10 Select your preferred language for the deployment of the expanded system. Selecting Your Language for Setup
11 Confirm the system size. (This system size must be larger than or equal to the original system.) Confirming the Size of Your System
13 Select Install a primary system. Choosing What System to Install
14 Select an automatic deployment. Choosing the Type of System Deployment
15 Enter your vCenter credentials so that we may deploy the virtual machines for you. Providing VMware vCenter Credentials
16 Select the ESXi host, datastore, and virtual machine port group for the media virtual machine. Choosing vCenter Settings for your Media Virtual Machine
17 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.) Entering Networking Information for the Media Virtual Machine
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.
Note   

If you have not enabled public access, skip to Task 19.

Adding Public Access
19 If you have added public access, then select the ESXi host, data store, and virtual machine port group for the Internet Reverse Proxy virtual machine. Choosing vCenter Settings for Internet Reverse Proxy
20 Enter the hostname and networking information for the Internet Reverse Proxy. Entering Networking Information for the Internet Reverse Proxy
21 Enter the public VIP address for the WebEx site URL.
Note   

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

Entering the Public VIP Address
22 Enter the private VIP address for the WebEx Administration URL.
Note   

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

Entering the Private VIP Address
23 Enter the WebEx site URL. 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.)
Note   

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.

Make sure you 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.

Entering the WebEx Site and Administration URLs
24 Enter the WebEx Administration URL for administrators to access Cisco WebEx Administration and internal participants to host or attend meetings (only with a split-horizon DNS). (This URL resolves to the Private VIP address.)
Note   

You can enter the same WebEx Administration 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.

Entering the WebEx Site and Administration URLs
25 Check that you have made all the networking, DNS server, and firewall configuration changes required for your system. Confirming that the Network is Configured Correctly
26 Once your virtual machines have deployed successfully, then select Next to continue to the system check. Deploying the Virtual Machines
27 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. Checking the System
28 Sign in to Cisco WebEx Administration.  
29 Test the expanded system. If the expansion is unsuccessful, then power off the expanded system and power on the original system. Contact Cisco TAC for further assistance. About System Testing
30 Re-host the licenses as appropriate for the expanded system. About Licenses Re-hosting Licenses after a Major System Modification

Expanding the System by using Manual Deployment

Before You Begin


Note


The system before expansion is referred to as the original system. The system following expansion is the expanded system.

Schedule a time that is least disruptive to your users to do the system expansion.

Put the primary system in maintenance mode before starting the system expansion.


Caution


Because this procedure requires exclusive access to the system, users cannot access the system for meetings. Be sure to schedule this procedure during a time that will be least disruptive to your users.

Coordinate with other system administrators before starting a system-altering procedure. Other system administrators should not access the system during this procedure. If they do so, their changes are not saved, and the result can be unpredictable.

Considerations Before Expanding the System

  • Be sure to remove all VMware snapshots of your original system before starting the expansion procedure.
  • You can reuse the same hostnames and IP addresses for the original virtual machines in the expanded system. However, only the original system, or the expanded system, can be powered on at any given time. Both systems cannot be powered on and running at the same time.
  • If you have already added a HA system to your original system, then following deployment of the expanded system, you must add a new HA system. You cannot reuse the original HA system as it is not retained, following the expansion.
  • You might want to keep the original system until you have finished testing the expanded system. Once testing is complete and you are satisfied with the expanded system, you can remove the original (pre-expansion) system.
  • The internal virtual machines for the original system and the expanded system must be on the same subnet.
  • If you have added public access, then the Internet Reverse Proxy virtual machines for the original system and the expanded system must be on the same subnet.
  • When you add a new virtual machine to the system, your current security certificate and public and private keys become invalid and require an update, unless you are using a self-signed certificate. Certificates include hostnames and URLs. The certificate and keys become invalid because they do not include the new virtual machine. For complete information on certificates and keys, see Managing Certificates.
  • Be sure the expanded system can access the disks for the original system's Admin virtual machine. You will be copying over Hard disk 4 to the expanded system.
  • Be sure your expanded system is up and running while removing or deleting your original system. This prevents accidental removal of Hard disk 4 's base VMDK file, which may be accessed by the expanded system.

Expanding the System

The overall tasks to expand the system are:

  1. Create a backup of your original system.
  2. Use the same OVA file you used to deploy your original system and deploy the Admin virtual machine for the new system size.
  3. Copy the data from your original system to the Admin virtual machine for the expanded system.
  4. Using the OVA, deploy any additional virtual machines for the new system size.
  5. Test the expanded system.
  6. Re-host the licenses.

Summary of Tasks to Expand the System Using a Manual Deployment


Note


This table includes links to other sections of the Cisco WebEx Meetings Server Administration Guide. Each of these sections provides detailed information on the specific task. After you complete each task, return to this table to complete the next task. (Use Previous View and Next View in Adobe Acrobat to move easily between this table and the individual task procedures.)


Task Description For Details, See
1 Prepare the original system for expansion. You completed this task earlier in this chapter. It is included in this table for completeness.
2 Prepare for a system-altering procedure. You completed this task earlier in this chapter. It is included in this table for completeness.
3 Initiate the expansion procedure from the Administration site of the original system. Expanding the System Size
4 Using the VMware vSphere client, select Power > Shut Down Guest on the virtual machines for the original system.  
5 Using the vSphere client, deploy the Admin virtual machine for the new system size.
Note   

At this time, you may also create the other virtual machines for your system.

Deploying the OVA File From the VMware vSphere Client
6 Attach Hard disk 4 from the original system's Admin virtual machine to the Admin virtual machine for the expanded system. Attaching an Existing VMDK File to a New Virtual Machine
7 Power on the Admin virtual machine for the expanded system and write down the deployment URL.
Note   

At this time, you may also power on the other virtual machines in your system. Be sure all the virtual machines power on successfully.

 
9 Enter the deployment URL into a web browser and continue the deployment of your expanded system.  
10 Select your preferred language for the deployment of the expanded system. Selecting Your Language for Setup
11 Confirm the system size. (This system size must be larger than or equal to the original system.) Confirming the Size of Your System
12 Select Install a primary system. Choosing What System to Install
13 Select a manual deployment. Choosing the Type of System Deployment
14 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. Adding Public Access
15 Enter the public VIP address for the WebEx site URL.
Note   

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

Entering the Public VIP Address
16 Enter the private VIP address for the WebEx Administration URL.
Note   

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

Entering the Private VIP Address
17 Enter the WebEx site URL. 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.)
Note   

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.

Make sure you 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.

Entering the WebEx Site and Administration URLs
18 Enter the WebEx Administration URL for administrators to access Cisco WebEx Administration and internal participants to host or attend meetings (only with a split-horizon DNS). (This URL resolves to the Private VIP address.)
Note   

You may enter the same WebEx Administration 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.

Entering the WebEx Site and Administration URLs
19 Check that you have made all the networking, DNS server, and firewall configuration changes required for your system. Confirming that the Network is Configured Correctly
20 Once your virtual machines have deployed successfully, then select Next to continue to the system check. Deploying Virtual Machines
21 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 may take up to an hour.) When complete, the system restarts. Checking the System
22 Sign in to Cisco WebEx Administration.  
23 Test the expanded system. If the expansion is unsuccessful, then power off the expanded system and power on the original system. Contact Cisco TAC for further assistance. About System Testing
24 Re-host the licenses as appropriate for the expanded system. About Licenses Re-hosting Licenses after a Major System Modification