Talk:Unified Communications Virtualization Sizing Guidelines

From DocWiki

Jump to: navigation, search

This page references a TAC Technote Document ID: 113520, which I believe is also EDCS document EDCS-1153298. The link to that document is broken. Is there a way to get to that document? Or is it an obsolete document and is there a replacement. Customer is asking to get that document, as it is referenced in several places.

VMware: CPU affinity and Memory reservation support: Is This statement is true for all UC&C applications ? (UCCE included ?) "All applications require a 1:1 mapping of VM vCPU cores to physical CPU cores. Cisco Unity VMs also require VMware CPU Affinity. " It seems to be opposite to these informations: "VM CPU affinity is not supported. You don't need to set CPU affinity for the VMs that are running Unified CCE applications on the VMware ESXi on UCS platform" => And also this page: "VM CPU affinity is not supported. You do not need to set CPU affinity for the VMs that are running Unified CVP applications on the VMware ESXi on UCS platform" => I am also pretty sure that I read that latest ova/ovf will include cpu affinity and memory affinity. Can you please confirm the support of CPU affinity and memory reservation for UCCE/CUCVP. Thanks. Lotfi AMARI.

Cisco Configuration Tool (need link here)

Where is the link to Cisco Configuration Tool?

All VMs require a one to one mapping between virtual hardware and physical hardware - is this correct

Under the No Hardware Oversubscription section with regards to CPU it states CPU reservations on the VMs are not required, allowed or supported. Use of CPU reservations in lieu of one-vcpu-to-one-physical-CPU-core mapping is not supported. Even if some of the virtual machines have a reservation, the above one-to-one vCPU to physical core rule still applies – it overrides the reservation. For example, if you have a host with a total of 4 physical cores, and you want to run the CUCM 2500 user OVA (which has 800 MHz reservation and requires 1 vCPU) along with other virtual machines, you still must deploy the VMs with a one to one mapping of vCPU to physical core. If you do not follow this rule, your deployment is unsupported. However in the Cisco-HCS-Compatibility-Matrix [1] it clearly states CPU oversubscription is only allowed for specific VMs where reservations are identified within the Compatibility Matrix for Cisco Hosted Collaboration Solution. Otherwise all VMs must map 1 VM vCPU core to 1 physical CPU core. and that the CUCM 2500 user OVA 1x800 MHz is highlighted as CPU oversubscription being allowed.

Personal tools