|
| Version 2.8 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.7 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.6 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.5 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.4 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.3 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.2 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
|
|
| Version 2.1 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware. |
|
|
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
* See mouse-over column heading for details
|
|
| Version 2.0 |
(top) |
| ALERT! This page has been updated to reflect compatibility with the latest M5 hardware. Click here to download support for M4 and older hardware.
This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
If you want to run Meeting Server on hardware that is not listed below (e.g. Cisco Multiparty Media 400v/ 410v Server/ 410v Blade Server or CMS1000) then see Cisco Meeting Server documentation.
* See mouse-over column heading for details
|
|
|
Notes |
(top) |
| |
|
Review the Cisco Meeting Server documentation for more information
Call Bridge VM or Combined VM (Edge + Call Bridge):
The Call Bridge supports Intel Xeon E5 2600 series (or later) processors and requires a minimum quantity of 4 vCPU. Where the clock speed is 2.5GHz or above each vCPU provides 1.25 HD ports. Where the clock speed is less than 2.5GHz, the 4 vCPU minimum still applies but each vCPU provides less than 1.25 HD ports. To calculate the capacity of each vCPU, divide the clock speed by 2.5 and multiply that by 1.25, for example a processor with 2.0GHz provides (2.0/ 2.5) x 1.25 = 1 HD port per vCPU. Capacity scales linearly with number of vCPUs so a system with 40 vCPUs allocated to CMS, with a clock speed of 2.5GHz can handle 50 concurrent 720p30 H.264 call legs.
Running a single VM
When running a single virtual machine on a host, one physical core per host must be left unused by apps for ESXi scheduler. With a single VM, it is possible to use hyper-threading to increase the available capacity. In this case the number of available vCPUs is double the number of physical cores in use. So a two socket system which has 20 physical cores will have 19 available to the application. With hyper-threading enabled, 38vCPUs can be used, which should be allocated to the CMS VM, and the other 2 left unused. If an option is available to choose both number of sockets and number of cores per socket, then these should mirror the underlying hardware.
Running multiple VMs co-resident on a single host
When running multiple virtual machine on a single host, at most one vCPU per physical core should be allocated regardless of the hyper-threading mode. If an option is available to choose both number of sockets and number of cores per socket for a VM, a single socket should be configured with all the virtual CPU cores.
When using VMware 5.5+ with multiple VMs and the Latency Sensitivity feature, one vCPUs per physical core can be assigned to applications. This requires the Cisco Meeting Server Core / Combined VM's Latency Sensitivity to be set to 'High' with one or more other VMs set to 'Normal'. So a two socket system which has 20 physical cores will have 20 vCPU available for the co-resident applications. If no other VMs can be set to 'Normal' then one physical core must be left unused. When using VMware release 5.1, or VMware 5.5+ without Latency Sensitivity, one physical core per physical server must be left unused by apps for ESXi scheduler. So a two socket system which has 20 physical cores will have 19 vCPU available for the co-resident applications. Use Collaboration Virtual Machine Placement Tool (VMPT) for assistance.
Over subscription of the host, either by incorrectly setting the number of Cisco Meeting Server VM virtual CPUs or by contention for CPU resources amongst VMs, causes scheduling delays and results in degraded media quality. A Cisco Meeting Server VM, correctly configured according to the recommendations above, will degrade gracefully by dropping frame rate and/or resolution if pushed over capacity.
Edged VM:
Edge VMs that connect to a single Meeting Server Call Bridge use 4 vCPUs and 4 GB vRAM. In other cases use 8vCPU and 8 GB vRAM.
Recording VM:
One recording per vcpu.
The recommended deployment for production usage of Recording is to run it on a separate VM.
This VM should be sized with 1 vCPU and 0.5GB of memory per 1 recording.
For co-residency with other VMs on shared hardware, 1vcpu per 1 physical CPU core (no Logical Cores/hyper-threading) for max 1 recording per physical CPU core.
If higher density required, see CMS 1000 deployment models on www.cisco.com/go/meetingserver.
Can scale-out up to 8 Recorder VMs. If seeking >8, review by Cisco video team required (see your Cisco account team for process).
See www.cisco.com/go/meetingserver for all other details.
Streaming VM:
Six streams per vcpu.
The recommended deployment for production usage of the Streamer is to run it on a separate VM.
This VM should be sized with 1 vCPU and 1GB of memory per 6 concurrent streams.
For co-residency with other VMs on shared hardware, 1vcpu per 1 physical CPU core (no Logical Cores/hyper-threading) for max 6 streams per physical CPU core.
If higher density required, see CMS 1000 deployment models on www.cisco.com/go/meetingserver.
Can scale-out up to 6 Streaming VMs. If seeking >6, review by Cisco video team required (see your Cisco account team for process).
See www.cisco.com/go/meetingserver for all other details.
|
|
|
IOPS and Storage System Performance Requirements |
(top) |
| |
| Coming soon.
|
|
|
|
|
|
