Design and Implementation Checklist

From DocWiki

Jump to: navigation, search

This page provides a high level checklist for design and implementation of the Unified CMBE 6000 solution.


Design Information

UC Applications

UC application design is largely the same as on MCS 7800 and uses the same design guides. Please refer to the tested system capacities at Supported System Capacities.

Unified CMBE 6000 supports full feature redundancy. You can configure hardware redundancy for all the applications by deploying a secondary UCS C200 server and turning on high availability feature supported by each one of the applications. If a customer is migrating from MCS based Unified CMBE 5000 or Unified CM and would like to configure redundancy only for call processing they can do so by configuring the instance of Unified CM running on the MCS78XX as a secondary/subscriber node.

Virtualization Design

Unified CMBE 6000 uses virtualization technology to acheive multiple application co-residency on the UCS server. Each one of the applications is placed on a virtual machine with pre-defined configuration that has been tested and rated for the capacities specified in the Supported System Capacities page.

Purchasing Information

Please refer to the Unified CMBE ordering guide for more details on how to order the Unified CMBE 6000.

Cisco Unified Communications Manager Business Edition 6000 offers a starter bundle that includes the following

  • 100 Basic Unfiied Communications Manager UCL
  • 100 Unity Connection Voicemail Licenses
  • UCS C200 M2 server

For ordering additional users, high availability and other feature options use the standard Unified Cmmunication manager and Cisco Unity Connection add-on part numbers.

Cisco Unified Presence and Contact Center application software and user licenses can also be optionally added using standard part numbers available for ordering the applications.

For more details please refer to the ordering guides of the individual applications.

Required VMware may be purchased either as a single Cisco Collaboration SKU, a set of Cisco Data Center SKUs or from VMware or other 3rd-party (including leveraging an existing customer site license or enteprise license). For details, see Unified Communications VMWare Requirements

To order Unified CMBE 6000 suite of applications using Cisco Unified Workspace Licensing refer to the CUWL ordering guide

Fulfillment of Software Licenses, Software Media and Server/Storage Hardware

UC app media are obtained by ordering appropriate part numbers defined in the application ordering guides.

UC app licenses are obtained at Each Virtual Machine running a UC app requires licensing.

  • Note that virtualized (UC on UCS) deployments require submission of a Product Authorization Key (PAK) derived from a "licensing MAC". For Unified Communications Manager, you can generate a "licensing MAC" at

Majority of UC app documents are posted online to

If VMware is purchased from Cisco, the only that is shipped is a paper licensing agreement containing a Product Activation Code (PAC) and a link with instructions on how to submit the PAC and receive a VMware license file. All VMware media and docs are posted online at - these are not physicall shipped.



Unified CMBE 6000 is not an appliance, and the user experience for management and serviceability are slightly different from appliances supported by the component applications.

  • Each application component (server, VMware, UC app) has its own set of management layers and tools. For management tasks that involve native hardware, all three will need to be touched. For tasks that only involve the UC app and do not involve native hardware, existing UC app tools and interfaces suffice.
  • For UC on UCS, certain kinds of hardware alerts are only available via CIM format - see Supported Hardware link for more details.

Back to Unified CMBE 6000

Rating: 0.0/5 (0 votes cast)

Personal tools