Cisco Expands UC Virtualization Support to add HP and IBM Platforms

William Bell
Vice President, Solutions and Products

Before going into the new support model, let’s define the Trusted Reference Configuration (TRC). TRCs are configuration “bundles” defined and supported by Cisco. These configurations outline platform hardware specifications that have been tested by Cisco for guaranteed performance for real-time applications in a virtual environment. TRCs are further defined to include specific capacity and application co-residency scenarios.

Three key benefits to the TRC approach is that:

  • A simplified platform selection process
  • Installation and maintenance documentation supporting the TRC models
  • Cisco TAC directly supports the TRC models.

On June 7th, Cisco added an alternative to the TRC model called: “Specifications Based Hardware Support“.  That is a mouth full, so I’ll refer to it as the “Specs-Based” model. Anyway, customers now have three deployment options:

  1. TRC: UC on UCS
  2. Specs-Based Model: UC on UCS
  3. Specs-Based Model: HP and IBM*
* The HP and IBM servers supported are listed on the VMware Hardware Compatibility List.
* Supported servers must use Intel Xeon 5600 or 7500 series processors

Not all UC applications are supported with the Specs-based model. Apparently, support will be phased in. As of June 7, the following products and versions are supported with the Specs-based model:

  • CUCM 8.0(2)+ and 8.5(1)+
  • CUCM – Session Manager Edition 8.5(1)
  • Cisco UC Management Suite 7.1+
  • Unity Connection 8.0(2)+ and 8.5(1)+
  • Unity 7.0(2)+
  • UCCX and IP IVR 8.5(1)+

Support for additional UC products is expected over the rest of CY2011.

This announcement isn’t limited to simply stating one can use HP and IBM compute services. The Specs-based model also adds support for the following:

  • Storage support for DAS, SAN (Fibre Channel, iSCSI, FCoE), and NAS (NFS)
  • More co-resident UC VMs per physical server as long as:
    • CPU physical core count is equal to the sum of UC VM core requirements and co-residency support policies
    • Minimum RAM is 2GB (for hypervisor) plus the sum of UC VM vRAM requirements
NOTE: Cisco UC applications and 3rd party or non-UC co-residency is still not supported

Whereas the TRC model is meant to simplify platform selection, the Specs-based model is intended to provide more flexibility.  Cisco has laid out requirements and considerations for the Specs-based model on the Cisco UC Virtualization DocWiki.  I highly recommend taking the time to read through the DocWiki.

Leave a Reply


Nick Kelly

Cybersecurity Engineer, Cisco

Nick has over 20 years of experience in Security Operations and Security Sales. He is an avid student of cybersecurity and regularly engages with the Infosec community at events like BSides, RVASec, Derbycon and more. The son of an FBI forensics director, Nick holds a B.S. in Criminal Justice and is one of Cisco’s Fire Jumper Elite members. When he’s not working, he writes cyberpunk and punches aliens on his Playstation.


Virgilio “BONG” dela Cruz Jr.

CCDP, CCNA V, CCNP, Cisco IPS Express Security for AM/EE
Field Solutions Architect, Tech Data

Virgilio “Bong” has sixteen years of professional experience in IT industry from academe, technical and customer support, pre-sales, post sales, project management, training and enablement. He has worked in Cisco Technical Assistance Center (TAC) as a member of the WAN and LAN Switching team. Bong now works for Tech Data as the Field Solutions Architect with a focus on Cisco Security and holds a few Cisco certifications including Fire Jumper Elite.


John Cavanaugh

CCIE #1066, CCDE #20070002, CCAr
Chief Technology Officer, Practice Lead Security Services, NetCraftsmen

John is our CTO and the practice lead for a talented team of consultants focused on designing and delivering scalable and secure infrastructure solutions to customers across multiple industry verticals and technologies. Previously he has held several positions including Executive Director/Chief Architect for Global Network Services at JPMorgan Chase. In that capacity, he led a team managing network architecture and services.  Prior to his role at JPMorgan Chase, John was a Distinguished Engineer at Cisco working across a number of verticals including Higher Education, Finance, Retail, Government, and Health Care.

He is an expert in working with groups to identify business needs, and align technology strategies to enable business strategies, building in agility and scalability to allow for future changes. John is experienced in the architecture and design of highly available, secure, network infrastructure and data centers, and has worked on projects worldwide. He has worked in both the business and regulatory environments for the design and deployment of complex IT infrastructures.