BE6K on UCS220 and CUPS IM Compliance Co-Residency

[jason.henderson]

Hi all,

Can anyone confirm whether co-residency between CUCM/CUC/CUPS, and a PostgreSQL server (on a Windows or Linux VM) on a BE6K (on UCS220) is supported?  I can't find anything on the DocWiki that says no, but then I can't find anything that says yes either.

Thanks in advance,

Jason

[Manish Gogna]

Hi Jason,

As per the following link it should be supported subject to the conditions outlined below

http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/BE6000/Coresidency/9_x/BE6K_coRes.html

* One vCPU should be reserved for ESXi scheduler if Cisco Unity Connection is deployed in a VM.

Up to three third-party applications may run on each BE 6000 host in a  deployment. Where two or more BE 6000 ESXi hosts are present in a  deployment, a maximum of six third-party applications may be installed.

The coresidency policy that is defined in this document applies for  deployments on any Business Edition 6000 Server running Virtualization  Hypervisor version 5.x.

Not all UC applications support coresidency, or they may have limited support of coresidency. See http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines#Application_Co-residency_Support_Policy for details.

All other general UC virtualization rules apply—for example, VMware feature support and supported ESXi versions. See www.cisco.com/go/uc-virtualized.

All non-BE 6000 UC applications must be VMware certified or supported  and must not require anything beyond the vSphere ESXi requirements that  is outlined at http://docwiki.cisco.com/wiki/Unified_Communications_VMware_Requirements.

All applications must support ESXi 5.0 as a minimum and align with supported versions of the other BE 6000 UC applications.

Customers that run a coresident deployment must agree to temporarily  reduce the number of virtual machines that are running on a host if  Cisco deems it necessary for debugging purposes.

Customers must permanently reduce the number of virtual machines that  are running on a host if Cisco determines that the host is overloaded.

If a customer is unwilling to agree to these requirements, Cisco TAC will not support the coresident deployment.

Support for third-party applications is provided by the vendor of the individual application.

When planning a coresident deployment, you must consider four areas: CPU, RAM, storage and network.

For details on virtual to physical sizing rules in a coresidency context, see http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Sizing_Guidelines.

The sizing rules refer to the "Tested Reference Configuration" hardware support approach, described here: http://docwiki.cisco.com/wiki/UC_Virtualization_Supported_Hardware.

HTH

Manish

[Jaime Valencia]

The most important bit is missing, only a small subset of apps can be installed:

•Non-BE 6000 UC means any of the following:

–Other Cisco UC applications (such as MediaSense) that are not explicitly part of the BE 6000 solution.

–Virtualized third-party UC applications that are included in the Cisco Developer Network, Marketplace Solutions Catalog for Collaboration. List of all permitted third-party UC applications can be found here. (Note:- Third-party applications that are not part of CDN may not be used with the BE 6000).

–Virtualized third-party applications that are offered through the Cisco SolutionsPlus Program described athttp://www.cisco.com/web/partners/pr46/solutions_plus/index.html.

HTH

java

if this helps, please rate

www.cisco.com/go/pdihelpdesk