Step 1
|
Sign in to Webex Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the
data centers in this system.
|
Step 2
|
If you are expanding an MDC system, remove the secondary datab center, leaving only the primary data center.
|
Step 3
|
If you are expanding an MDC system, create a new data center running Cisco Webex Meeting Server to be joined after the primary
system is expanded.
|
Step 4
|
Create a backup of the original system. ()
|
Step 5
|
Turn on Maintenance Mode. See Turning Maintenance Mode On or Off.
If the data center is part of a Multidata Center (MDC) system, in-progress meetings fail over to an active data center. The
failover can cause a brief interruption in active meetings. See About Maintenance Mode for information. Turning on Maintenance Mode for all active data centers shuts down all conference functionality. No one
can sign in to the Webex site, schedule meetings, join meetings, or play meeting recordings.
|
Step 6
|
Select
Continue.
|
Step 7
|
Select
.
The
Manage
System Specifications page appears.
|
Step 8
|
Select
Expand
System Size.
|
Step 9
|
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. When the backup is complete, you are notified that you can
proceed with your expansion.
|
Step 10
|
Using the VMware
vSphere client, select
on the virtual machines for the original
system.
|
Step 11
|
Using the
vSphere client, deploy the Admin virtual machine for the new system size.
|
Step 12
|
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 13
|
Power on the
Admin virtual machine for the expanded system and write down the deployment
URL. If you are performing an automatic expansion, we 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 14
|
Enter the
deployment URL into a web browser and continue the deployment of your expanded
system.
|
Step 15
|
Select your
preferred language for the deployment of the expanded system. (See
Selecting Your Language for Setup.)
|
Step 16
|
Select
.
|
Step 17
|
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 18
|
Select
Install a primary system.
|
Step 19
|
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:
-
Enter your
vCenter credentials so that we can deploy the virtual machines for you. (See
Providing VMware vCenter Credentials.)
-
Select the
ESXi host, data store, and virtual machine port group for the Media virtual
machine. (See
Choosing vCenter Settings for Your Media and Web Virtual Machines.)
-
Enter the
fully qualified domain name of the Media virtual machine.
Use the same
OVA file you first used to install the system. Deploy an Admin virtual machine
for the new system size.
Your system
notifies you when the expansion is complete.
|
Step 20
|
If you want
public access for your expanded system, then verify that 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:
-
Select
the ESXi host, data store, and virtual machine port group for the Internet
Reverse Proxy (IRP) virtual machine.
-
Enter the
hostname and networking information for the IRP virtual machine.
|
Step 21
|
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 22
|
Enter the private VIP address for the Webex site URL. (See Entering the Private VIP Address.)
You can 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 23
|
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 can enter the same Webex Common site URL that you used for your original system, or change to a new one. If you do change
it, then make the necessary updates in the DNS server.
Note
|
If users attempt to use the original URL, those users cannot: After this change is made, system traffic coming from hostnames,
other than the ones currently configured, is dropped.
|
|
Step 24
|
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 Administration site URL that you use for the original system, or change to a new one. If you
do change it, then make the necessary updates in the DNS server.
|
Step 25
|
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 26
|
After your
virtual machines have deployed successfully, select
Next to continue to the system check. (See
Deploying Virtual Machines Manually.)
Along
with the system check, we update the expanded system with any required
maintenance release updates to match the software version of the original
system. (These updates might take up to an hour.) When complete, the system
restarts. (See
Checking the System.)
|
Step 27
|
Select
Restart.
|
Step 28
|
Sign in to Webex Site Administration.
In a Multidata Center system, the DNS determines which data center Dashboard appears. Use this Dashboard to manage all the
data centers in this system.
|
Step 29
|
If you are
expanding an MDC system, join it to the MDC system. (See
Joining a Data Center to a Multi-Data Center System.)
|
Step 30
|
Turn off Maintenance Mode.
When you turn off Maintenance Mode, the system determines whether a restart or a reboot is required, and displays the appropriate
message. A restart takes approximated 3 to 5 minutes and a reboot takes approximately 30 minutes. If the data center is part
of a Multidata Center (MDC) system, you are redirected to the global admin URL. The DNS resolution policy determines which
data center you see. If Key Regeneration is enabled, taking one data center out of Maintenance Mode automatically takes all
data centers in the system out of Maintenance Mode.
See Turning Maintenance Mode On or Off.
Meeting service on the data center is restored.
|
Step 31
|
Select
Continue.
The system restarts. You can sign into Webex Site Administration when the restart is completed.
|
Step 32
|
Test the expanded system.
See About System Testing. If the expansion is unsuccessful, power off the expanded system and power on the original system. If necessary, contact
Cisco TAC for further assistance.
|