The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The OVA template creates two virtual NICs for each virtual machine. However, only the Administration virtual machines uses both virtual NICs. All other Cisco WebEx Meetings Server (CWMS) virtual machines, only one virtual NIC is used and the other one is disconnected.
This procedure is provided as a general guidance. The screens you see during the OVA deployment depends upon your vCenter, storage, and networking configuration, and might be different from what is described in this procedure. See your VMware vSphere documentation for complete information on the OVA wizard.
Obtain the Cisco WebEx Meetings Server OVA file for your system and place it in a location that is accessible from VMware vSphere. Use the VMware vSphere client to deploy the Administration virtual machine for your system.
You must use VMware vCenter to manage the ESXi hosts on which the Cisco WebEx Meetings Server system is deployed. Using the vSphere client, sign in to vCenter and deploy the OVA file for the Admin virtual machine.
Step 1 | Sign in to your
VMware vSphere client.
Be sure to sign in as a user that includes administrator privileges: to deploy, configure, power on or off, and delete virtual machines. | ||
Step 2 | Select | ||
Step 3 | Select
Browse to navigate to the location of the OVA file.
Select
Next.
You can select the Cisco WebEx Meetings Server link to go to a Web page with detailed information about this system. | ||
Step 4 | Read the End User License Agreement and select Accept, then select Next. | ||
Step 5 | Navigate to and select the location in the vCenter inventory where you want to place the Admin virtual machine. | ||
Step 6 | Enter the name of the virtual machine for your system size and select Next. For more information on selecting the correct size for your company, see General Information for System Deployment.
You must deploy the Admin virtual machine before deploying any other virtual machines. If you select automatic deployment (recommended), we deploy the other virtual machines for you. If you choose manual deployment (required for a 2000 concurrent users system), then after deploying the Admin virtual machine, you must deploy the other virtual machines by using this same wizard. Cisco recommends you include the type in the virtual machine name; for example, include "Admin" in your Admin virtual machine name to easily identify it in your vCenter inventory. All the internal virtual machines for your system must be in the same subnet as the Admin virtual machine. (Depending on the system size you select, you might need one or more media and web internal virtual machines.) | ||
Step 7 | From the drop-down
list, select the virtual machine for your system size and select
Next.
Be sure to deploy the Admin virtual machine before any other virtual machines in your system. | ||
Step 8 | Navigate through the vCenter inventory and select the ESXi host or cluster where you want to deploy the virtual machines for your system. Select Next. | ||
Step 9 | If the cluster
contains a resource pool, select the resource pool where you want to deploy the
OVA template and select
Next.
Resource pools share CPU and memory resources working with VMware features such as DRS or vMotion. Resource pools must be dedicated to a single ESXi Host. VMware resource pools are not recommended for use with Cisco WebEx Meetings Server. | ||
Step 10 | Select the
datastore for your virtual machine and the kind of provisioning for your
virtual machine.
You must select Thick Provisioning and create the maximum virtual disk space required for your system. With Thin Provisioning, VMware allocates the file system space on an as-needed basis that can result in poor performance. Lazy zero is sufficient and eager zero is acceptable, but eager zero will take more time to complete. | ||
Step 11 | Set up network
mapping. For each source network, select a destination network from the
drop-down list in the
Destination Networks column. Select
Next.
| ||
Step 12 | Enter the
following information for the virtual machine, then select
Next:
| ||
Step 13 | Confirm the information that you have entered. If there are any mistakes, select Back and change the values. | ||
Step 14 | If you are manually upgrading a system, select Finish, skip the balance of this procedure and continue with the next step in Upgrading Your System Manually. (Copying data from the original system to the upgrade system by using manual deployment should be performed after the upgraded system is deployed, but not yet powered on.) Otherwise, check Power on after deployment and select Finish. | ||
Step 15 | If you are
deploying an Admin virtual machine, go to vCenter and open a console window for
the virtual machine. Once it powers on, we will check the networking
information you entered during the OVA deployment.
If we are able to confirm connectivity, a green checkmark appears. If there is a problem, a red X appears. Fix the error and re-attempt the OVA deployment. | ||
Step 16 | Write down the
case-sensitive URL displayed in the console window.
An administrator uses this URL to continue the system deployment. If the system is re-booted before the configuration is complete, a new passcode is generated and you must use the URL with the new passcode. |
If you are performing a manual deployment, we recommend that you deploy the rest of the virtual machines for your system at this time. This avoids any issues such as time outs when powering on virtual machines.
If the deployment is successful, continue with system deployment in a browser window.
If the deployment failed, see Checking Your Networking Configuration After a Failed OVA Deployment.
Confirm the networking entries for the virtual machine.
Do not use Edit Settings... for any of the virtual machines in your system, other than after a failed deployment. Once the system is up and running, you must use the WebEx Administration site to make any further edits to virtual machine settings. If you use your vSphere client, those changes will not be accepted by the system.
Note | For detailed steps, see your VMware vSphere documentation. |
Determine your preferred language for setting up the system.
Note | Do not close this browser window until the system deployment is complete. If you close the browser early, it might be necessary to restart the deployment. CWMS System is the default name of the data center after an upgrade; it is not translated from English in any of the other languages. |
Be sure you have deployed the Admin virtual machine from VMware vCenter. See Deploying the OVA File From the VMware vSphere Client
Step 1 | Specify whether you are deploying a new system, or expanding an existing system. |
Step 2 | Click Next. |
You selected the size of your system when you deployed the Admin virtual machine by using the OVA file.
Step 1 | To confirm that the system size you selected during the OVA deployment is correct, click Next. |
Step 2 | If the system size is incorrect, click I want to change System Size. |
Step 3 | Using your VMware vSphere client, locate the Admin virtual machine with the incorrect system size. |
Step 4 | Click for the virtual machine. |
Step 5 | Right-click the virtual machine and click Delete from Disk. |
Step 6 | Redeploy the OVA file and select the Admin virtual machine for the correct system size. |
You can choose automatic or manual deployment of the system virtual machines. Your choice of automatic or manual deployment depends on the following considerations:
If you have time constraints, an automatic deployment is faster than a manual deployment.
If you prefer step-by-step guidance, this guidance is provided during an automatic deployment.
If you are familiar with VMware vCenter and do not want to provide us your vCenter credentials, select manual deployment.
We recommend that you select Automatic unless you are deploying a 2000-user system, which always requires a manual deployment.
If you select an automatic deployment, Cisco WebEx Meetings Server requires your vCenter credentials to deploy the virtual machines for you.
All the ESXi hosts for your system must belong to the same VMware vCenter.
The media virtual machine is required for small, medium, and large systems. The web virtual machine is required for large systems.
After you enter the fully qualified domain name of the media and web virtual machines, Cisco WebEx Meetings Server populates the networking information.
Note | The media and web virtual machines must be on the same subnet as the Admin virtual machine. Do not edit the domain, IPv4 gateway, subnet mask, or DNS servers for the media or web virtual machines. |
If you add public access by using IRP, users outside the firewall can host or attend meetings from the Internet or mobile devices. IRP virtual machines can be added to a system at any time on a per-data center basis. Adding IRP to one data center in a Multi-data Center (MDC) environment gives users outside the firewall access to the entire system. To prevent external access, all IRP virtual machines must be removed from a system.
For security reasons, we recommend that you locate the Internet Reverse Proxy on a subnet different from the subnet occupied by the Administration virtual machine. This ensures network level isolation between the Internet Reverse Proxy and your internal (Admin and media, if applicable) virtual machines.
In a Multi-data Center (MDC) environment, the data centers cannot be expanded or upgraded. Secondary data centers must be removed from the MDC, making it a Single-data Center (SDC) environment. The MDC environment can be restored after the data centers are modified and it is verified that the data center sizes and versions match.
It is not necessary to connect your storage server to an Internet Reverse Proxy (IRP) server.
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.
With public access: Choosing vCenter Settings for Internet Reverse Proxy (IRP)
Without public access: Entering the Private VIP Address
For IPv6 client connections: Configuring IPv6 for Client Connections
Verify that the firewall ports required by VMware vCenter are open so that vCenter can deploy the Internet Reverse Proxy (IRP) virtual machine. For more information on the required firewall ports, see the Cisco WebEx Meetings Server Planning Guide.
Add the hostnames and IP addresses of Internet Reverse Proxy (IRP) servers in your DNS servers, to enable lookup from an external network.
If you have DNS servers to support lookup from internal networks, add the information to these servers too. This configuration enables a secure connection between your internal virtual machines and the IRP servers.
This public VIP address must be visible from both the Internet and the internal network (split-horizon DNS only).
This public VIP address must be on the same subnet as the Internet Reverse proxy.
If you do not have a split-horizon DNS, then all users use the Public VIP address to host and attend meetings.
If you have a split-horizon DNS, and added public access, then external users use the Public VIP address to host and attend meetings.
For more information on non-split horizon and split-horizon DNS, and public access, see the Cisco WebEx Meetings Server Planning Guide.
Note | If you are creating a High Availability (HA) system, you do not need to reenter this information, as we will use the information you entered for the primary system. |
Enter the public VIP IPv4 address and select Next.
Administrators configure, monitor, and maintain the system from the Administration site URL that maps to the private VIP address.
If you have a split-horizon DNS, then internal users also use the Private VIP address to host and attend meetings.
If you are adding a High Availability (HA) system, you do not need to reenter this information; we will use the information you entered for the primary system.
The private virtual IP (VIP) address must be on the same subnet as your internal (Admin and Media, if applicable) virtual machines.
Enter the IPv4 private VIP address and select Next.
The Common Site URL allows users to schedule and host meetings, and access meeting recordings. The Administration Site URL provides management of the system. If you are adding a High Availability (HA) system, it is not necessary to reenter this information; the primary system URLs should match the HA system URLs.
Users access the WebEx site URL to schedule, host, or attend meetings. This URL resolves to either the private VIP address or the public VIP address, depending on whether or not you are using a split-horizon DNS.
Resolves to the public VIP address for all users, when you do not have split-horizon DNS.
Resolves to the public VIP address for external users when you have split-horizon DNS.
Resolves to the private VIP address for internal users when you have split-horizon DNS.
Note | Ports 80 and 443 must be open for the WebEx site URL. |
Administrators access the WebEx Administration URL to configure, manage, and monitor the system. This URL resolves to the private VIP address.
Note | Ports 80 and 443 must be open for the WebEx Administration URL. |
You may choose almost any names for these URLs, comprising all lowercase characters. However, you cannot use the following as the hostname in the URLs:
the same name as the hostnames for any of the virtual machines in the system
authentication
client
companylogo
dispatcher
docs
elm-admin
elm-client-services
emails
maintenance
manager
orion
oriondata
oriontemp
nbr
npp
probe
reminder
ROOT
solr
TomcatROOT
upgradeserver
url0107ld
version
WBXService
webex
This screen provides links to online help for the networking changes required for your system. The online help provides details on DNS server changes as well as firewall settings.
You must make the DNS server and firewall changes that allow us to test network connectivity.
If you have not done so already, complete the networking configuration and select Next.
If you are testing an automatic deployment, we deploy the virtual machines required for your system when you select Next.
If you are testing a manual deployment, enter the hostnames for your virtual machines and deploy them (if you have not deployed them already).
When the deployment is complete, test them by powering them on and verifying that all the virtual machines powered on successfully.
Based on the information that you entered earlier, we deploy the virtual machines required for your system.
The deployment requires several minutes to complete. Do not leave this page until all the virtual machines have deployed and are powered on, unless error messages appear.
When the status column shows all green checks, the deployment is complete with no errors. You can change the FQDNs for the virtual machines by clicking Detect virtual machines.
1. (Optional) After the status column shows all green checks, click Next.
2. If errors are indicated, fix the errors.
3. Power off and delete the virtual machines involved with the errors.
4. Click Next to redeploy the system.
Step 1 | (Optional) After the status column shows all green checks, click Next. |
Step 2 | If errors are indicated, fix the errors.
You can click Download log file to obtain the log file for the deployment. The log provides information that you can use to troubleshoot a failed deployment. |
Step 3 | Power off and delete the virtual machines involved with the errors. |
Step 4 | Click Next to redeploy the system. |
After providing information about the virtual machines in the system, connect to each of the virtual machines. Virtual machines for extension units appear in this list.
Note | Do not leave this browser page until the system is connected to all of the virtual machines, unless a connection fails with an error message to indicate the problem. |
The system check verifies the configuration parameters of your system. This includes confirming that the virtual machines have the required minimum configuration, and validating the WebEx site and WebEx Administration URLs.
The system check takes several minutes to complete. Do not leave this page until all the checks have been completed successfully, or the system check fails and shows error messages indicating the problem.
If you reload the page before the checks are complete, you are returned to the first page of this system deployment. When the checks are completed successfully, the first page of configuration utility appears.
The Administration site URL used during the deployment process is the Administration virtual machine hostname. During basic configuration, the hostname is replaced with the Administration site URL. As a result, the first time you sign in to the Administration site, the system might prompt you to accept the certificate exception.
Complete one of the following:
Power down all the virtual machines from VMware vCenter and manually delete them. Then retry the system deployment on a system with resources that meet or exceed the minimum requirements.
Proceed with your current installation. If you do, you must acknowledge that you forgo the right to request technical support from Cisco. Confirm by checking the error message check box and select Next.
Select Continue to go to the basic configuration where you begin by setting up the mail server (Configuring an Email (SMTP) Server) and identifying an administrator (Creating Administrator Accounts). If another administrator will complete the basic configuration, send this URL to that administrator.