Service Profiles and Cisco Unified Communications

[Darren Lynn]

Hi All,

I need some information on Service Profile configuration for ESXi hosts that will be running Cisco Unified Communications Manager and associated applications (Unity Connections and Presence)

The B-Series Chassis will initially host 2 B200M2 blades for this purpose and I'm after best practice for the Service Profiles. The blades are running the M81KR Virtual Interface Card.

Any help is appreciated, or if someone can point me in the direction of the documentation that would also be appreciated.

Cheers

Darren

[cpaggen]

It's quite straightforward:

- you must boot from local disk

- bundle your local drives in a RAID-1 group

- assign a pair of vHBAs to your profile for connectivity to your FC SAN (one to SAN "A", one to SAN "B")

- as far as networking in concerned, you have "carte blanche" (UC VMs use a single nic and Nexus 1000V is optional)

--> you could for instance create 6 vnics: 2 for service console, 2 for vmotion, 2 for vmdata. Or just 2 vnics and have Nexus 1000V "own" them. Any other scheme you find suitable is ok.

Most restrictions aren't on the UCS side but rather on specific VMware features currently supported by the solution.

See

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html

http://docwiki.cisco.com/wiki/Unified_Communications_VMWare_Requirements

The OVA templates for the UC VMs are at http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization_Downloads_%28including_OVA/OVF_Templates%29 --> you'll get an idea of storage capacity and vCPU requirements