Technical information

Ordering Guide

b. These approvals are granted by VCE Platform Engineering and Support. A vArchitect on the

worldwide channel team must be engaged to package these exception requirements to VCE

Platform Engineering & Support.

Follow this checklist to quote a UC on UCS solution. You will need assistance from your Data-Center account team

for many of these elements.

1. Gather information required to quote.

2. Determine UC Virtual Machine quantity, and UCS server quantity

3. Quote UCS servers and any other required UCS components

4. Quote “Readiness” requirements (VMware, network, storage)

5. Quote UC, UCSS, and Services

Each step will be further detailed below.

1. Gather information required to quote

UC on UCS quotes are easiest if you have already done a design based on a Cisco MCS 7800 quote and you are

converting it to UC on UCS. The following information is required to successfully quote a solution:

●

Which applications will be included in the proposal?

◦ Check server compatibility resources to ensure the target applications (and versions) are supported for the

UCS models you want to quote. For example, Cisco UCM compatibility starts with Version 8.0(2), requires

use of VMware ESXi 4, and is detailed at http://www.cisco.com/go/swonly and

http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/prod_brochure0900aecd8062a4

f9.html.

◦ UC Applications: See http://www.cisco.com/go/uc-virtualized for a list of applications and versions that

support Cisco UCS, and links to product-specific support information.

◦ Other Cisco Applications: For example, Network Management, Security, Wireless, etc. This software may

run on a different blade in the same chassis as UC, but may not be co-resident on the same server with

UC.

◦ Third-party Applications: For example, OEM software, Solutions Plus, Cisco Technology Developer

Program, or customer-provided applications such as Directory, File/Print, Customer Relationship

Management, Human Resources Information System, Enterprise Resource Planning, etc. Check with the

vendor’s server support policy for whether the applications can run on Cisco UCS. This software may run

on a different blade in the same chassis as UC, but may not be co-resident on the same server with UC.

●

Sites that will host the applications, and which servers/applications will live at each site. Most customers either

have everything at a single site or split across a primary and redundant site.

●

Total number of software application instances, and what application and “role”.

◦ E.g., instance count for a Cisco MCS 7800 solution is equal to the number of MCS servers.

◦ E.g., Application and “role” could be Cisco UCM Publisher, Cisco UCM Subscriber, Cisco Unified CCE

Router, Cisco Unified Intelligence Suite Archiver, Nuance server, etc.

●

Identify customer’s “Placement Logic” and business criteria for the design.

◦ Will all servers and software live at a single site or at multiple sites? How are they split?

◦ Does the customer want to minimize server footprint and maximize server usage, or instead spread apps

across multiple servers, chassis, and sites?

◦ Identify “anticonsolidation” business requirements such as high-availability concerns, service-level

agreements, change management effect, IT organization, assessed criticality of the apps, and security