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 System Size
|
4
|
Using the VMware vSphere client, select
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 Your Internet Reverse Proxy
|
20
|
Enter the hostname and
networking information for the Internet Reverse Proxy.
|
Entering the 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 Your 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 Your
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.
|
Testing the
System
|
30 |
Re-host the licenses as
appropriate for the expanded system.
|
About
Licenses
Re-hosting
Licenses after an Upgrade
|