Systems are identified by the number of concurrent users supported:

• 50 concurrent users (also known as a micro system)

  • Typically supports a company between 500 and 1000 employees

  • Primary system [(without High Availability (HA)] comprises an Admin virtual machine, and an optional Internet Reverse Proxy (IRP) machine.

• 250 concurrent users (also known as a small system)

  • Typically supports a company between 2500 and 5000 employees

  • Primary system (without HA) comprises an Admin virtual machine, a Media virtual machine, and an optional Internet Reverse Proxy (IRP) machine.

• 800 concurrent users (also known as a medium system)

  • Typically supports a company between 8000 and 16,000 employees.

  • Primary system (without HA) comprises an Admin virtual machine, a Media virtual machine, and an optional Internet Reverse Proxy (IRP) machine.

• 2000 concurrent users (also known as a large system)

  • Typically supports a company between 20,000 and 40,000 employees.

  • Primary system (without HA) comprises an Admin virtual machine, three Media virtual machines, two Web machines, and an optional Internet Reverse Proxy (IRP) machine.

• 4000 concurrent users (also known as an extra large (XL) system

  • Typically supports a company with more than 50000 employees.

  • Primary system (without HA) comprises an Admin virtual machine, four Media virtual machines, three Web machines, and two optional Internet Reverse Proxy (IRP) machines.

    You can extend a primary XL system to comprise an Admin virtual machine, six media virtual machines, five web virtual machines and four optional IRP machines. Each extension unit consists of one media, one web and one optional IRP VM.

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.

Networking Changes

• 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.

Required Information

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:

• Required Information for an Automatic Deployment

• Required Information for a Manual Deployment

This is the information required for your system, in order.

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 lookup IP addresses for you during the deployment. To avoid 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.)

What to do Next

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.

What to do Next

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.