Notes:

• * vRAM requirements are 1GB per vCPU with a minimum of 4GB of RAM, but recommended minimum of 8GB. A Combined VM (Edge + Callbridge + DB + Scheduler) only supports 1000 cospaces as a base opposed to the 75k of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100k cospaces is required across all CMS VMs using the Callbridge or Database components. For example, a separate Callbridge VM and Database VM deployment to support 20HD ports and 275k cospaces would be required. Additionally, running a Scheduler requires an additional 4GB of RAM.
  • Callbridge VM: 16vCPU with 18GB RAM (16vCPU to give 20HD ports. 16GB RAM to support the HD ports plus 2GB of RAM for 200k co-spaces in excess of 75k).
  • Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200k additional cospaces in excess of 75k).
• This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
• For more details, see Notes for VM Configurations
• For all other details on hardware and VMware support, refer to Cisco Collaboration Infrastructure.
• Refer to Quote Collab for modeling VM placement on a user defined hardware configuration.

Notes:

• * vRAM requirements are 1GB per vCPU with a minimum of 4GB of RAM, but recommended minimum of 8GB. A Combined VM (Edge + Callbridge + DB + Scheduler) only supports 1000 cospaces as a base opposed to the 75k of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100k cospaces is required across all CMS VMs using the Callbridge or Database components. For example, a separate Callbridge VM and Database VM deployment to support 20HD ports and 275k cospaces would be required. Additionally, running a Scheduler requires an additional 4GB of RAM.
  • Callbridge VM: 16vCPU with 18GB RAM (16vCPU to give 20HD ports. 16GB RAM to support the HD ports plus 2GB of RAM for 200k co-spaces in excess of 75k).
  • Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200k additional cospaces in excess of 75k).
• This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
• For more details, see Notes for VM Configurations
• For all other details on hardware and VMware support, refer to Cisco Collaboration Infrastructure.
• Refer to Quote Collab for modeling VM placement on a user defined hardware configuration.

Notes:

• * vRAM requirements are 1GB per vCPU with a minimum of 4GB of RAM, but recommended minimum of 8GB. A Combined VM (Edge + Callbridge + DB) only supports 1000 cospaces as a base opposed to the 75k of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100k cospaces is required across all CMS VMs using the Callbridge or Database components. For example a separate Callbridge VM and Database VM deployment to support 20HD ports and 275k cospaces would required.
  • Callbridge VM: 16vCPU with 18GB RAM (16vCPU to give 20HD ports. 16GB RAM to support the HD ports plus 2GB of RAM for 200k co-spaces in excess of 75k
  • Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200k additional cospaces in excess of 75k.
• This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
• For more details, see Notes for VM Configurations
• For all other details on hardware and VMware support, refer to Cisco Collaboration Infrastructure.
• Refer to Quote Collab for modeling VM placement on a user defined hardware configuration.

Notes:

• This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
• For more details, see Notes for VM Configurations
• For all other details on hardware and VMware support, refer to Cisco Collaboration Infrastructure.
• Refer to Quote Collab for modeling VM placement on a user defined hardware configuration.

Notes:

• This information listed here for convenience. For latest information, when in doubt, conflict, review the Cisco Meeting Server documentation.
• For more details, see Notes for VM Configurations
• For all other details on hardware and VMware support, refer to Cisco Collaboration Infrastructure.
• Refer to Quote Collab for modeling VM placement on a user defined hardware configuration.