[cisco-voip] Add new vCPU of CUCM server

[Ryan Ratliff (rratliff)]

Don’t confuse the Unity Connection and UCM specs.

http://www.cisco.com/web/software/283088407/108296/cucm_10.0_vmv8_v1.7.ova.README.txt

The 2500-user 1 vCPU spec is for the non-“Restricted Perf CPUs” (http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware#Processors_.2F_CPUs) only usesa n 800MHz reservation.
If you are adding another vCPU I’d have no qualms doubling that reservation.  Note that the 7500-user spec uses 2 vCPUs with a 3600 MHz reservation.

-Ryan

On Feb 24, 2015, at 11:54 AM, Anthony Holloway <avholloway+cisco-voip at gmail.com<mailto:avholloway+cisco-voip at gmail.com>> wrote:

Great technical point there Dan. I did mean cores and not sockets.  This conversation has me now wondering about the need to adjust the CPU reservation in MHz under Resources > CPU.

In the 10.5 OVA it lists the following for the 5000 device option:

The 5000 user node
        Cisco Unity Connection (CUC) configuration that supports up to
        5000 users per node.
        Details:
        - Number of virtual CPUs: 2
           - For Xeon 5600 and 7500 processors - minimum of 2.53 GHz each (5.06 GHz reserved or
           - For Xeon E7 processors - minimum of 2.4 GHz each (4.8 GHz reserved)
        - Amount of RAM: 6 GB
        - Hard disks: 1 x 200 GB (contains aligned partitions for CUC application)
        - OS support: Red Hat Enterprise Linux 6 (64-bit)

Source: http://www.cisco.com/web/software/282074348/113178/CUC_10.5_vmv8_v1.5.ova.README.txt

So, would one be expected to adjust the following setting to 5.06GHz or 4.8GHz?  Or simply leave it be?

<image.png>


On Tue Feb 24 2015 at 10:23:48 AM Daniel Pagan <dpagan at fidelus.com<mailto:dpagan at fidelus.com>> wrote:
Just to add to Anthony’s email, I suggest making sure to add to the vCPU socket count, not number of vCPU cores per socket. Also note that you can increase your vCPU socket count but should *not* decrease it – this is not supported.

- Dan

From: cisco-voip [mailto:cisco-voip-bounces at puck.nether.net<mailto:cisco-voip-bounces at puck.nether.net>] On Behalf Of Anthony Holloway
Sent: Monday, February 23, 2015 6:51 PM
To: Claiton Campos; cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
Subject: Re: [cisco-voip] Add new vCPU of CUCM server

Yes.  You would need to shutdown the VM first, and then just add the new vCPU count under Edit Settings of the VM.  It's the disks which you cannot simply increase from within VMWare.

This is something I did recently during an upgrade of CUCM from 8x to 10x on a C210M2 which was using the 2500 user OVA.

This is what I read which prompted me to change mine:

“The 2500 user VM configuration with one vcpu may exhibit performance issues during CPU/IO-intensive operations (such as installs, upgrades, backups and CDR writes), or if your deployment has certain characteristics such as a large quantity of TFTP files. Changing the VM config to 2 vcpu is recommended as a prevention strategy.”

Source: http://docwiki.cisco.com/wiki/Virtualization_for_Cisco_Unified_Communications_Manager_(CUCM)#Notes_on_2500_user_VM_configurations

On Mon Feb 23 2015 at 5:42:14 PM Claiton Campos <claitoncampos at gmail.com<mailto:claitoncampos at gmail.com>> wrote:

Hello , someone has come to change the amount of vCPU a CUCM server in production? Recently 'm having problems with high throughput publisher server and as directed by the TAC is suggested to add a new vCPU to the server. My question is whether the server recognizes this new vCPU .
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20150224/1e114feb/attachment.html>