Unified Computing System Hardware

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(→Hardware Requirements)
 
(14 intermediate revisions not shown)
Line 1: Line 1:
-
<html>
+
'''Go to: [[Guidelines to Edit UC Virtualization Pages|Guidelines to Edit UC Virtualization Pages]]'''<br>  
-
<head>
+
-
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+
-
<!-- TemplateBeginEditable name="doctitle" -->
+
-
<title>Custom Search</title>
+
-
<!-- TemplateEndEditable -->
+
-
<!-- TemplateBeginEditable name="head" -->
+
-
<!-- TemplateEndEditable -->
+
-
<style type="text/css">
+
-
<!--
+
-
.style1 {
+
-
font-family: Arial, Helvetica, sans-serif;
+
-
font-weight: bold;
+
-
color: #990000;
+
-
}
+
-
-->
+
-
</style>
+
-
</head>
+
-
<body>
+
-
<table width="850" border="0">
+
-
  <tr>
+
-
    <td>&nbsp;</td>
+
-
    <td>&nbsp;</td>
+
-
    <td><span class="style1">Custom Search:</span></td>
+
-
  </tr>
+
-
  <tr>
+
-
    <td>&nbsp;</td>
+
-
    <td>&nbsp;</td>
+
-
    <td><form action="http://vtg-india/search/search-results.htm" id="cse-search-box">
+
-
  <div>
+
-
    <input type="hidden" name="cx"  />
+
-
    <input type="hidden" name="cof" />
+
-
    <input type="hidden" name="ie" value="UTF-8" />
+
-
    <input type="text" name="q" size="31"  />
+
-
    <select name="sysversion" id="sysversion" onchange="ValueAssign()">
+
-
      <option value="000" selected="selected">All</option>
+
-
      <option value="001">System DocWiki</option>
+
-
      <option value="701">Release 7.0(1)</option>
+
-
      <option value="611">Release 6.1(1)</option>
+
-
      <option value="601">Release 6.0(1)</option>
+
-
      <option value="513">Release 5.1(3)</option>
+
-
      <option value="512">Release 5.1(2)</option>
+
-
      <option value="511">Release 5.1(1)</option>
+
-
      <option value="502">Release 5.0(2)</option>
+
-
      <option value="501">Release 5.0(1)</option>
+
-
        </select>
+
-
      <input type="submit" name="sa" value="Search" />
+
-
  </div>
+
-
</form>
+
-
<script type="text/javascript" src="http://www.google.com/coop/cse/brand?form=cse-search-box&lang=en">
+
-
</script>
+
-
</tr>
+
-
</table>
+
-
</body>
+
-
<script>
+
-
function ValueAssign()
+
-
{
+
-
//var 7VersionValue='006593089695086678066:0kl2h5qj840';
+
-
if(document.getElementById("sysversion").value=="000")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:0kl2h5qj840';
+
-
document.forms[0].cof.value='FORID:9';
+
-
}
+
-
if(document.getElementById("sysversion").value=="001")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:lzag0lfme8o';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="701")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:kfddvkpdjrs';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
 
+
-
if(document.getElementById("sysversion").value=="611")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:nqrs5zeblvi';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="601")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:kwqrd9thjqm';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="513")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:aepwjocyk7k';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="512")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:4zzx60m1sqa';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="511")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:nuz7v4v8vyy';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="502")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:uwk4-ptfgxe';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
if(document.getElementById("sysversion").value=="501")
+
-
{
+
-
document.forms[0].cx.value='006593089695086678066:pphx2va8kka';
+
-
document.forms[0].cof.value='FORID:10';
+
-
}
+
-
}
+
-
</script>
+
-
</html>
+
-
 
+
----
----
-
== Introduction ==
+
<br>
-
 
+
-
Virtualization has emerged as a leading trend in the data center. Organizations are embracing the virtualized data center for a variety of reasons, including total cost of ownership (TCO), consolidation, operational efficiency and flexibility, disaster recovery and business continuity, security, and reduced carbon footprint.
+
-
Cisco is committed to leading the transition toward the virtualized data center through innovative products and solutions, including support for Cisco Unity messaging on the VMware ESXi platform, part of the VMware Infrastructure suite.
+
-
 
+
-
Deploying Cisco Unified Communications on VMware ESXi delivers the following advantages:
+
-
:* Allows customers to extend the benefits of their virtualization and storage data center investments to Cisco Unified Communications.
+
-
:* Maintains the same predictable scalability provided by running the Cisco Unified Communication applications on a physical server.
+
-
 
+
-
Cisco Unified Communications are real-time application, which makes it more difficult to virtualize than traditional data-centric applications, such as database and email servers. Delivering this level of performance in a reliable, predictable, and serviceable manner requires some concessions, primarily around not oversubscribing the CPU, RAM and other resources.
+
-
You can virtualize many of the Cisco Unified Communication applications, such as Cisco Unified Communication Manager, Cisco Unity Connection, Cisco Unified Presence Server, Cisco Unified Contact Center Express and other Contact Center applications
+
== Introduction  ==
-
You can also run a mix of virtual and nonvirtual machines, including the servers in a backup or failover pair.
+
This web page describes supported compute, storage and network hardware for virtualized Cisco Unified Communications on Cisco Unified Computing System (UC on UCS).  
-
Also note that to virtualize Cisco Unified Communications applications, there is an additional support burden. Customers provide the hardware, VMware ESXi software, and are responsible for coordinating support for these components, including provisioning and performance troubleshooting.
+
-
Customers who are unwilling to take on such support may be better candidates for deploying Cisco Unified Communication applications on physical servers.
+
 +
Note that because Cisco Unified Communications is composed of real-time media applications, there are certain support requirements that must be followed.
-
== Hardware Requirements ==
+
Mixed deployments of virtualized, non-virtual MCS and non-virtual "bare-metal Software-only" servers are supported, see http://www.cisco.com/go/ucsrnd .
-
The currently-available Unified Communications System Hardware are:
+
-
:* Unified Computing System B-200 M1
+
UC on UCS hardware supports servers purchased as Collaboration SKUs or as Data Center SKUs, provided they meet the support policies described below.
-
:* Unified Computing System C-210 M1
+
-
::* Reference Configuration 1
+
-
::* Reference Configuration 2
+
-
::* Reference Configuration 3
+
-
Refer to [http://www.cisco.com/go/swonly the supported specifications page] and the section on Related Hardware Documentation for details on these models.
+
== Hardware Requirements  ==
-
=== B-200 M1 Requirements ===
+
For more details on Cisco UCS servers in general, please see http://www.cisco.com/go/ucs , http://www.cisco.com/go/uconucs and the Related Hardware Documentation section below.
-
The following hardware requirements apply to the currently-supported Unified Communications applications when using the B-200 M1 hardware:
+
-
:* The hardware must be the half-width B-200 blade, with the Intel E5540 CPU or greater.
+
UC on UCS uses "Tested Reference Configurations" to describe supported configurations of compute, storage and network hardware. The table below contains a high-level summary of Tested Reference Configurations.  
-
:* SAN storage must be used.  
+
-
:* The SAN array must on the VMware list of supported SANs.
+
-
:* SAN connectivity must be fiber channel.
+
-
:* SAN array disks must be fiber channel or SAS with 10k or 15k spindle speed.
+
-
:* No over subscription of of any resource is allowed.
+
-
A complete list of requirements is located [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html here].
+
Please see the "UC on UCS" link at http://www.cisco.com/go/swonly, or [http://www.cisco.com/en/US/prod/collateral/voicesw/ps6790/ps5748/ps378/solution_overview_c22-597556.html here] for the following:
-
=== C-210 M1 Requirements ===
+
*Complete list of hardware requirements  
-
The following hardware requirements apply to the currently-supported Unified Communications applications when using the C-210 M1 hardware:
+
*Alternative configurations that are also supported  
 +
*Mapping of Cisco Collaboration SKUs to equivalent Cisco Data Center SKUs
 +
*Details on DAS and SAN storage requirements
-
:* The hardware must be the C-210 server.
+
Tested Reference Configurations for UC on UCS are supported whether purchased as Cisco Collaboration SKUs or Cisco Data Center SKUs.  
-
:* The local disks (DAS) must be used for both VMware and any Unified Communications applications when deployed using Reference Configuration 1 and Reference Configuration 2. For Reference Configuration 3, VMware must be installed on local disks (DAS) but Unified Communications applications can be installed on either DAS or SAN.  The SAN requirements for Reference Configuration 3 are the same as for the B-200 M1. 
+
-
:* No over subscription of any resource is allowed.
+
-
A complete list of requirements is located [http://cisco.com/go/swonly here].
+
<br>
-
==== Monitoring and Alarming for the the C210M1 ====
+
{| border="1"
-
Local alarming of hardware is not supported on the C210M1. Remote monitoring and alarming of hardware using CIM is recommended. Refer to the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/utilities/raid/reference/guide/ucs_raid_smis_reference.html ''UCS RAID Controller SMI-S Reference Guide''] for detailed information on this topic.
+
|-
 +
! Base Server Model and Generation
 +
! Tested Reference Configuration (TRC)
 +
! CPU
 +
! RAM
 +
! Storage
 +
! Adapters
 +
! Notes
 +
|-
 +
! UCS B200 M2 Blade Server
 +
| TRC #1
 +
| Dual E5640 (8 physical cores total)
 +
| 48GB (12x4GB)
 +
| DAS (RAID1) for VMware, FC SAN for UC apps
 +
| Cisco VIC
 +
| UCS-B200M2-VCS1
 +
|-
 +
!
 +
| TRC #2
 +
| Dual E5640 (8 physical cores total)
 +
| 48GB (12x4GB)
 +
| Diskless - FC SAN for VMware and UC apps
 +
| Cisco VIC
 +
| Sold as Cisco Data Center SKUs only
 +
|-
 +
! UCS B200 M1 Blade Server
 +
| TRC #1
 +
| Dual E5540 (8 physical cores total)
 +
| 36GB (6x2GB+6x4GB)
 +
| DAS (RAID1) for VMware, FC SAN for UC apps
 +
| 3rd-party CNA
 +
| UCS-B200M1-VCS1
 +
|-
 +
!
 +
| TRC #2
 +
| Dual E5540 (8 physical cores total)
 +
| 36GB (6x2GB+6x4GB)
 +
| Diskless - FC SAN for VMware and UC apps
 +
| 3rd-party CNA
 +
| Sold as Cisco Data Center SKUs only
 +
|-
 +
! UCS C210 M2 General-Purpose Rack-Mount Server
 +
| TRC #1
 +
| Dual E5640 (8 physical cores total)
 +
| 48GB (12x4GB)
 +
| DAS (2 disks RAID1) for VMware + DAS (8 disks RAID5) for UC apps
 +
| 1GbE NIC
 +
| UCS-C210M2-VCD2
 +
|-
 +
! <br>
 +
| TRC #2
 +
| Dual E5640 (8 physical cores total)
 +
| 48GB (12x4GB)
 +
| DAS (2 disks RAID1) for VMware, FC SAN for UC apps
 +
| 1GbE NIC and 4G FC HBA
 +
| Sold as Cisco Data Center SKUs only
 +
|-
 +
! <br>
 +
| TRC #3
 +
| Dual E5640 (8 physical cores total)
 +
| 48GB (12x4GB)
 +
| Diskless - FC SAN for VMware and UC apps
 +
| 1GbE NIC and 4G FC HBA
 +
| Sold as Cisco Data Center SKUs only
 +
|-
 +
! UCS C210 M1 General-Purpose Rack-Mount Server
 +
| TRC #1
 +
| Dual E5540 (8 physical cores total)
 +
| 12GB (6x2GB)
 +
| DAS (2 disks RAID1) for VMware + DAS (4 disks RAID5) for UC apps
 +
| 1GbE NIC
 +
| UCS-C210M1-VCD1 (note: only supports a single Virtual Machine)
 +
|-
 +
! <br>
 +
| TRC #2
 +
| Dual E5540 (8 physical cores total)
 +
| 36GB (6x2GB+6x4GB)
 +
| DAS (2 disks RAID1) for VMware + DAS (8 disks RAID5) for UC apps
 +
| 1GbE NIC
 +
| UCS-C210M1-VCD2
 +
|-
 +
! <br>
 +
| TRC #3
 +
| Dual E5540 (8 physical cores total)
 +
| 36GB (6x2GB+6x4GB)
 +
| DAS (2 disks RAID1) for VMware, FC SAN for UC apps
 +
| 1GbE NIC and 4G FC HBA
 +
| Sold as Cisco Data Center SKUs only
 +
|-
 +
! <br>
 +
| TRC #4
 +
| Dual E5540 (8 physical cores total)
 +
| 36GB (6x2GB+6x4GB)
 +
| Diskless - FC SAN for VMware and UC apps
 +
| 1GbE NIC and 4G FC HBA
 +
| Sold as Cisco Data Center SKUs only
 +
|-
 +
! UCS C200 M2 General-Purpose Rack-Mount Server
 +
| TRC #1
 +
| Dual E5506 (8 physical cores total)
 +
| 24GB (6x4GB)
 +
| DAS (4 disks RAID10) for VMware + UC apps
 +
| 1GbE NIC
 +
| UCS-C200M2-VCD2 (note: only scaled for &lt;1K users depending on UC app)
 +
|}
-
== Related Hardware Documentation ==
+
== Related Hardware Documentation ==
-
[http://www.cisco.com/en/US/products/ps10280/prod_installation_guides_list.html Unified Computing System B-Series Servers]
+
==== Monitoring and Alarming for Cisco UCS  ====
-
[http://www.cisco.com/en/US/products/ps10493/prod_installation_guides_list.html Unified Computing System C-Series Servers ]
+
At this time on Cisco UCS, certain types of serviceability monitoring and alarming (such as hard drive failure) are only available via OS instrumentation. For UC on UCS this means alerts are generated by VMware in CIM format, and require VMware vCenter or equivalent CIM-compliant console. Refer to the [http://www.cisco.com/en/US/docs/unified_computing/ucs/sw/utilities/raid/reference/guide/ucs_raid_smis_reference.html ''UCS RAID Controller SMI-S Reference Guide''] for detailed information on this topic.
-
[http://www.cisco.com/en/US/products/ps10279/prod_installation_guides_list.html Unified Computing System 5100 Series Blade Server Chassis]
+
=== Other Key Cisco UCS Documents  ===
-
[http://www.cisco.com/en/US/products/ps10276/prod_installation_guides_list.html Unified Computing System 6100 Series Fabric Interconnects]
+
For installation and configuration information on UCS servers, refer to the documentation roadmap for either the B-Series or C-Series servers:
-
[http://www.cisco.com/en/US/products/ps10278/index.html Unified Computing System 2100 Series Fabric Extenders]
+
*[http://www.cisco.com/go/unifiedcomputing/b-series-doc Cisco UCS B-Series Servers Documentation Roadmap]
 +
*[http://www.cisco.com/go/unifiedcomputing/c-series-doc Cisco UCS C-Series Servers Documentation Roadmap]
 +
*[http://www.cisco.com/en/US/products/ps10739/tsd_products_support_series_home.html Cisco UCS C-Series Integrated Management Controller Documentation]
 +
*[http://www.cisco.com/en/US/products/ps10281/tsd_products_support_series_home.html Cisco UCS Manager Documentation]
-
[http://www.cisco.com/en/US/products/ps10281/tsd_products_support_series_home.html Unified Computing System Manager]
+
<br>
----
----
-
Back to [http://docwiki.cisco.com/wiki/Unified_Communications_Virtualization Unified Communications Virtualization main page]
+
Back to [[Unified Communications Virtualization|Unified Communications Virtualization main page]]

Latest revision as of 21:15, 25 April 2011

Go to: Guidelines to Edit UC Virtualization Pages


Contents

Introduction

This web page describes supported compute, storage and network hardware for virtualized Cisco Unified Communications on Cisco Unified Computing System (UC on UCS).

Note that because Cisco Unified Communications is composed of real-time media applications, there are certain support requirements that must be followed.

Mixed deployments of virtualized, non-virtual MCS and non-virtual "bare-metal Software-only" servers are supported, see http://www.cisco.com/go/ucsrnd .

UC on UCS hardware supports servers purchased as Collaboration SKUs or as Data Center SKUs, provided they meet the support policies described below.

Hardware Requirements

For more details on Cisco UCS servers in general, please see http://www.cisco.com/go/ucs , http://www.cisco.com/go/uconucs and the Related Hardware Documentation section below.

UC on UCS uses "Tested Reference Configurations" to describe supported configurations of compute, storage and network hardware. The table below contains a high-level summary of Tested Reference Configurations.

Please see the "UC on UCS" link at http://www.cisco.com/go/swonly, or here for the following:

  • Complete list of hardware requirements
  • Alternative configurations that are also supported
  • Mapping of Cisco Collaboration SKUs to equivalent Cisco Data Center SKUs
  • Details on DAS and SAN storage requirements

Tested Reference Configurations for UC on UCS are supported whether purchased as Cisco Collaboration SKUs or Cisco Data Center SKUs.


Base Server Model and Generation Tested Reference Configuration (TRC) CPU RAM Storage Adapters Notes
UCS B200 M2 Blade Server TRC #1 Dual E5640 (8 physical cores total) 48GB (12x4GB) DAS (RAID1) for VMware, FC SAN for UC apps Cisco VIC UCS-B200M2-VCS1
TRC #2 Dual E5640 (8 physical cores total) 48GB (12x4GB) Diskless - FC SAN for VMware and UC apps Cisco VIC Sold as Cisco Data Center SKUs only
UCS B200 M1 Blade Server TRC #1 Dual E5540 (8 physical cores total) 36GB (6x2GB+6x4GB) DAS (RAID1) for VMware, FC SAN for UC apps 3rd-party CNA UCS-B200M1-VCS1
TRC #2 Dual E5540 (8 physical cores total) 36GB (6x2GB+6x4GB) Diskless - FC SAN for VMware and UC apps 3rd-party CNA Sold as Cisco Data Center SKUs only
UCS C210 M2 General-Purpose Rack-Mount Server TRC #1 Dual E5640 (8 physical cores total) 48GB (12x4GB) DAS (2 disks RAID1) for VMware + DAS (8 disks RAID5) for UC apps 1GbE NIC UCS-C210M2-VCD2

TRC #2 Dual E5640 (8 physical cores total) 48GB (12x4GB) DAS (2 disks RAID1) for VMware, FC SAN for UC apps 1GbE NIC and 4G FC HBA Sold as Cisco Data Center SKUs only

TRC #3 Dual E5640 (8 physical cores total) 48GB (12x4GB) Diskless - FC SAN for VMware and UC apps 1GbE NIC and 4G FC HBA Sold as Cisco Data Center SKUs only
UCS C210 M1 General-Purpose Rack-Mount Server TRC #1 Dual E5540 (8 physical cores total) 12GB (6x2GB) DAS (2 disks RAID1) for VMware + DAS (4 disks RAID5) for UC apps 1GbE NIC UCS-C210M1-VCD1 (note: only supports a single Virtual Machine)

TRC #2 Dual E5540 (8 physical cores total) 36GB (6x2GB+6x4GB) DAS (2 disks RAID1) for VMware + DAS (8 disks RAID5) for UC apps 1GbE NIC UCS-C210M1-VCD2

TRC #3 Dual E5540 (8 physical cores total) 36GB (6x2GB+6x4GB) DAS (2 disks RAID1) for VMware, FC SAN for UC apps 1GbE NIC and 4G FC HBA Sold as Cisco Data Center SKUs only

TRC #4 Dual E5540 (8 physical cores total) 36GB (6x2GB+6x4GB) Diskless - FC SAN for VMware and UC apps 1GbE NIC and 4G FC HBA Sold as Cisco Data Center SKUs only
UCS C200 M2 General-Purpose Rack-Mount Server TRC #1 Dual E5506 (8 physical cores total) 24GB (6x4GB) DAS (4 disks RAID10) for VMware + UC apps 1GbE NIC UCS-C200M2-VCD2 (note: only scaled for <1K users depending on UC app)

Related Hardware Documentation

Monitoring and Alarming for Cisco UCS

At this time on Cisco UCS, certain types of serviceability monitoring and alarming (such as hard drive failure) are only available via OS instrumentation. For UC on UCS this means alerts are generated by VMware in CIM format, and require VMware vCenter or equivalent CIM-compliant console. Refer to the UCS RAID Controller SMI-S Reference Guide for detailed information on this topic.

Other Key Cisco UCS Documents

For installation and configuration information on UCS servers, refer to the documentation roadmap for either the B-Series or C-Series servers:


Back to Unified Communications Virtualization main page

Rating: 2.3/5 (10 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Unified_Computing_System_Hardware"
Personal tools