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.
Systems are identified by the number of concurrent users supported:
WebEx Site URL—Secure HTTP URL for users to host and attend meetings in a single-data center environment.
WebEx Administration URL—Secure HTTP URL for administrators to configure, monitor, and manage the system in a single-data center environment.
Public VIP—virtual IP address for the WebEx site URL.
Private VIP—virtual IP address for the Administration site URL or the virtual IP address for the WebEx site URL (for internal users only, if you have a split-horizon DNS).
WebEx Common URL—used by the DNS to redirect the user to the data center where the user performs meeting-related tasks, such as scheduling or hosting meetings. Which data center DNS chooses is transparent to the user. The WebEx Common URL is simply a convenient location for a user to enter the system. If a data center goes down, nothing changes for the user, including the URL used to access meetings, because the DNS redirects the user to the surviving data center.
Administration Common URL—is often referenced as simply the Administration URL. It is used by the DNS to redirect an administrator to the management data center to where the administrator logs into the system. Which data center the DNS chooses is transparent to the administrator (however, the string in the URL bar changes depending on which data center the administrator is using to access the system). The Administration Common URL is simply a convenient target an administrator uses to enter the system.
Administration Local URLs—are specific to each data center in a Multi-data Center (MDC) system. When signing in through the Administration Common URL, the DNS redirects the administrator to the Administration Local URL for the management data center. Any system modifications, such as assigning a license to a user, are performed on the management data center and replicated to all data centers in the MDC system.
An administrator can choose a specific data center to modify from within the CWMS application, but selecting another data center to modify does not change the Administration Local URL, because the administrator's access to the system remains with the data center chosen by the DNS when the administrator logged into the system. The administrator's modifications to another data center in the MDC system pass through the management data center chosen by the DNS to the target data center.
An MDC system has a minimum of two Administration Local URLs, one for every data center in the system.
Local URLs that are specific to each data center.
Common Site URL |
||
Common Administration URL |
|
|
DC1 and DC2 Virtual IP addresses |
||
Data Center 1 |
Data Center 2 |
|
Local Site URLs |
||
Local Administrator URLs |
||
Public Virtual IP Addresses |
||
Private Virtual IP Addresses |
||
DNS Server |
||
Administration Virtual Machine IP Address |
||
Media Virtual Machine IP Address 1 |
||
Media Virtual Machine IP Address 2 |
||
Media Virtual Machine IP Address 3 |
||
Web Virtual Machine IP Address 1 |
||
Web Virtual Machine IP Address 2 |
||
DMZ Virtual Machine IP Address (optional) |
||
CWMS Administrator Email Addresses |
||
Administrator Password |
||
Remote Access1 |
||
Remote Access Password |
||
Call Manager IP Address |
||
Cisco Call Manager Administrator ID |
||
Cisco Call Manager Password |
||
CWMS Dial-in Numbers |
||
Phone Numbers |
You must use VMware vCenter to manage the ESXi hosts on which the Cisco WebEx Meetings Server system is deployed.
Public access: whether users external to your firewall can host and access meetings from the Internet or mobile devices. We recommend allowing public access, because it provides a better user experience for your mobile workforce.
Type of DNS setup at your company: split-horizon DNS or a non-split horizon DNS (most common DNS configuration). For more information about DNS setup, see the Cisco WebEx Meetings Server Planning Guide.
Open port 10200 from the administrator desktop to the Admin virtual machine. Port 10200 is used by the web browser during the deployment.
The required information varies if you are doing an automatic deployment (supported for 50 concurrent users, 250 concurrent users, and 800 concurrent users) systems or manual deployment (supported for all system sizes). We recommend that you select an automatic deployment unless you are deploying a 2000-user system that always requires a manual deployment.
Choose the appropriate checklist for your deployment type:
This is the information required for your system, in order.
With this information, start the system deployment by entering the deployment URL in a browser window. (The deployment URL is displayed in the console window for the Admin virtual machine.)
Note | If the system is rebooted before the configuration is complete, a new passcode is generated and you must use the deployment URL with the new passcode. |
In a manual deployment, you create all the virtual machines for your system by using the OVA wizard from your vSphere client. You then install your system by using manual deployment.
When deploying a 2000-user system, you must deploy the system manually.
Note | Add the virtual machine FQDNs, IP addresses, WebEx and Administration site URLs, and VIP addresses to your DNS servers before you start the system deployment. We use this information to check network connectivity at the end of the deployment. To avoid any DNS issues, test these URLs and IP addresses before you start the OVA deployment. Otherwise, the system deployment might fail until you correct these errors. The Fully Qualified Domain Name (FQDN) of the Primary System must be 50 characters or less to have all components up on primary system. If the FQDN is longer than 50 characters, MZM, CB, and WWP components will be in a DOWN state. (FQDN=Primary System name including the domain.) |
This is the information required for your system, in order.
Field Name | Description | Value For Your System |
---|---|---|
Public VIP |
IP address for the WebEx site URL (site users access to host and attend meetings) |
|
Private VIP |
||
WebEx Site URL |
Secure HTTP URL (all lowercase characters) for users to host and attend meetings. |
|
WebEx Administration URL |
Secure HTTP URL (all lowercase characters) for administrators to configure, monitor, and manage the system. |
|
FQDN for the internal virtual machines |
Depending on the system size, this is the FQDN (all lowercase characters) of the media and web virtual machines. |
|
(Public access only) FQDN of the Internet Reverse Proxy |
To add public access, enter the FQDN (all lowercase characters) of the Internet Reverse Proxy virtual machine. |
With this information, start the system deployment by entering the deployment URL in a browser window. (The deployment URL is written in the console window for the Admin virtual machine.)
Note | If the system is rebooted before the configuration is complete, a new passcode is generated and you must use the deployment URL with the new passcode. |