High-level Checklist for Design and Implementation

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Protected "High-level Checklist for Design and Implementation" [edit=sysop:move=sysop] [cascading])
m (1 revision)
 
(3 intermediate revisions not shown)
Line 1: Line 1:
-
This page provides "source of the source" information for assistance with the lifecycle of a Cisco Unified Communications Virtualization solution, including "UC on UCS".
+
'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''<br>
-
= Design Information =
+
----
-
== UC Applications ==
+
<br>
-
UC application design is largely the same as on MCS 7800 and uses [http://www.cisco.com/go/ucsrnd the same design guides].  The main change with virtualization is how to interpret the design output of "Server" count and size. 
+
-
* With non-virtualized designs the "Server" is an MCS 7800 or software-only equivalent.  One physical server runs only one application instance.
+
-
* With virtualized designs the "Server" is a [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|Virtual Machine in "OVA" format]].  One physical server runs multiple application instances.
+
 +
This page provides "source of the source" information for assistance with the lifecycle of a Cisco Unified Communications Virtualization solution, including "UC on UCS".
-
== Virtualization Design ==
+
= Design Information  =
-
After designing the UC application itself, for each "Server" required, you must select an appropriate [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|virtual machine template in OVA format]].  
+
== UC Applications ==
-
Then you must determine what physical servers/storage you need taking into account:
+
UC application design is largely the same as on MCS 7800 and uses [http://www.cisco.com/go/ucsrnd the same design guides]. The main change with virtualization is how to interpret the design output of "Server" count and size.  
-
* [[Unified Communications VMWare Requirements|VMware requirements]]
+
-
* [[Unified Communications Virtualization Supported Applications|Application support]]
+
-
* [[Unified Communications Virtualization Sizing Guidelines|Co-residency support, server selection, redundancy, and storage design]]
+
-
* Supported server/storage configurations - summary [[Unified Computing System Hardware|here]], full details [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html here].
+
 +
*With non-virtualized designs the "Server" is an MCS 7800 or software-only equivalent. One physical server runs only one application instance.
 +
*With virtualized designs the "Server" is a [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|Virtual Machine in "OVA" format]]. One physical server runs multiple application instances.
-
= Purchasing Information =
+
<br>
-
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.
+
== Virtualization Design ==
-
* 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.
+
After designing the UC application itself, for each "Server" required, you must select an appropriate [[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|virtual machine template in OVA format]].  
 +
Then you must determine what physical servers/storage you need taking into account:
-
= Fulfillment of Software Licenses, Software Media and Server/Storage Hardware =
+
*[[Unified Communications VMWare Requirements|VMware requirements]]
 +
*[[Unified Communications Virtualization Supported Applications|Application support]]
 +
*[[Unified Communications Virtualization Sizing Guidelines|Co-residency support, server selection, redundancy, and storage design]]
 +
*Supported server/storage configurations - summary [[Unified Computing System Hardware|here]], full details [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html here].
-
'''UC app media''' are obtained at Product Upgrade Tool for both virtualized (UC on UCS) and non-virtualized (MCS 7800) deployments.
+
<br>
-
'''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.
+
= Purchasing Information =
-
* 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.
+
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.  
-
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.
+
*Cisco field and channel partners may also consult the "UC on UCS" chapter of the User Connect Licensing Ordering Guide.
-
'''Server shipments''' are managed the same for both UCS and MCS 7800 servers.
+
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.
-
= Implementation =
+
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.
-
The [http://www.cisco.com/web/cuc_afg/index.html Answer File Generator] utility creates answer files for unattended Cisco Unified Communications installations. If your primary node will be installed on a virtual machine, this utility will also generate a virtual License MAC to be used when you request licenses.
+
<br>
 +
= Fulfillment of Software Licenses, Software Media and Server/Storage Hardware  =
-
= Operations =
+
'''UC app media''' are obtained at Product Upgrade Tool for both virtualized (UC on UCS) and non-virtualized (MCS 7800) deployments.
-
Virtualized deployments (UC on UCS) are not an appliance, and the user experience for management and serviceability are slightly different.
+
'''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.
-
* 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.
+
*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.
 +
 
 +
<br>
 +
 
 +
= Implementation  =
 +
 
 +
The [http://www.cisco.com/web/cuc_afg/index.html Answer File Generator] utility creates answer files for unattended Cisco Unified Communications installations. If your primary node will be installed on a virtual machine, this utility will also generate a virtual License MAC to be used when you request licenses.
 +
 
 +
<br>
 +
 
 +
= 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 Communications Virtualization|Unified Communications Virtualization main page]]
Back to [[Unified Communications Virtualization|Unified Communications Virtualization main page]]

Latest revision as of 17:03, 7 March 2011

Go to: Guidelines to Edit UC Virtualization Pages



This page provides "source of the source" information for assistance with the lifecycle of a Cisco Unified Communications Virtualization solution, including "UC on UCS".

Contents

Design Information

UC Applications

UC application design is largely the same as on MCS 7800 and uses the same design guides. The main change with virtualization is how to interpret the design output of "Server" count and size.

  • With non-virtualized designs the "Server" is an MCS 7800 or software-only equivalent. One physical server runs only one application instance.
  • With virtualized designs the "Server" is a Virtual Machine in "OVA" format. One physical server runs multiple application instances.


Virtualization Design

After designing the UC application itself, for each "Server" required, you must select an appropriate virtual machine template in OVA format.

Then you must determine what physical servers/storage you need taking into account:


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

The Answer File Generator utility creates answer files for unattended Cisco Unified Communications installations. If your primary node will be installed on a virtual machine, this utility will also generate a virtual License MAC to be used when you request licenses.


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 Communications Virtualization main page

Rating: 5.0/5 (1 vote cast)

Personal tools