Version 3.9

Supported Versions of VMware vSphere ESXi: 7.0 Update 3o

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 75,000 of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.8

Supported Versions of VMware vSphere ESXi: 7.0 Update 3n

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 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.7

Supported Versions of VMware vSphere ESXi: 6.5 P09, 6.7 P08, 7.0 U3j

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 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.6

Supported Versions of VMware vSphere ESXi: 6.5 EP 26, 6.7 EP 23, 7.0 U3d

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 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.5

Supported Versions of VMware vSphere ESXi: 6.5 P07, 6.7 EP 23, 7.0 U3d

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 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.4

Supported Versions of VMware vSphere ESXi: 6.5 P07, 6.7 P05, 7.0 U2a

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 75,000 of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.3

Supported Versions of VMware vSphere ESXi: 6.5 U3, 6.7 U3, 7.0 U2a

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 75,000 of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.2

Supported Versions of VMware vSphere ESXi: 6.5 U2, 6.7, 7.0 U1c

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 75,000 of a dedicated Callbridge VM. To support additonal cospaces in a deployment an additional 1GB per 100,000 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 275,000 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 200,000 co-spaces in excess of 75,000).
• Database VM: 8vCPU with 10GB RAM (8vCPU with 8GB RAM base Database VM with 2GB addition RAM for 200,000 additional cospaces in excess of 75,000).
• 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.

Version 3.1

Supported Versions of VMware vSphere ESXi: 6.5 U2, 6.7, 7.0

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.

Version 3.0 (with ESXi 7.0)

Supported Versions of VMware vSphere ESXi: 7.0

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.

Contacts | Feedback | Help | Sitemap | Terms & conditions | Privacy Statement | Cookie Policy | Trademarks