Design and Implementation Checklist

From DocWiki

Revision as of 21:54, 15 December 2010 by Wamaxwel (Talk | contribs)
Jump to: navigation, search

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

Contents

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


Purchasing Information

Cisco UCS servers may be purchased either as a single Cisco Collaboration SKU or a set of Cisco Data Center SKUs. See UCS page at http://www.cisco.com/go/swonly for details.

  • Cisco field and channel partners may also consult the "UC on UCS" chapter of the User Connect Licensing Ordering Guide.

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 VMware Requirements link.

  • Cisco field and channel partners may also consult the "UC on UCS" chapter of the User Connect Licensing Ordering Guide.

There is no change to how UC applications are purchased. User Connect Licensing, Unified Workspace Licensing and UC Software Subscription are all the same for both virtualized (UC on UCS) and non-virtualized (MCS 7800) deployments.


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

UC app media are obtained at Product Upgrade Tool for both virtualized (UC on UCS) and non-virtualized (MCS 7800) deployments.

UC app licenses are obtained at http://www.cisco.com/go/license for both virtualized (UC on UCS) and non-virtualized (MCS 7800) deployments. Each Virtual Machine running a UC app requires licensing.

  • Note that non-virtualized (MCS 7800) deployments require submission of a Product Authorization Key (PAK) derived from the MCS 7800 physical MAC address.
  • Note that virtualized (UC on UCS) deployments require submission of a Product Authorization Key (PAK) derived from a "licensing MAC". For CUCM, you can generate a "licensing MAC" at http://www.cisco.com/web/cuc_afg/index.html.

Majority of UC app documents are posted online to http://www.cisco.com.

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

Server shipments are managed the same for both UCS and MCS 7800 servers.


Implementation

Operations

Virtualized deployments (UC on UCS) are not an appliance, and the user experience for management and serviceability are slightly different.

  • Each solution component (server/storage, 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