Tested Reference Configurations (TRC)

From DocWiki

Revision as of 21:00, 7 June 2011 by Cchetty (Talk | contribs)
Jump to: navigation, search

Go to: Guidelines to Edit UC Virtualization Pages



Contents

Introduction

This web page describes supported compute, storage and network hardware for Virtualization of Cisco Unified Communications using Tested Reference Configurations.

For more details on Cisco UCS servers in general, see the Related Hardware Documentation section below.

Ensure your deployment follows all the design and procurement rules here.

See procurement considerations here for hardware purchase options. Cisco part numbers are described here

Hardware Requirements for Tested Reference Configurations


To be considered a Tested Reference Configuration (TRC) for support purposes, follow the policy below. NOTE: any deviation from policy below is no longer a Tested Reference Configuration and you must follow the "Specs-based VMware Support" Policy here.

  • Server model and generation must exactly match table below.
  • Physical CPU quantity, CPU model and physical cores per CPU must exactly match table below.
  • Total physical Memory/RAM must be same or higher than in table below. Must follow Cisco UCS best practices for memory module density, quantity and speed - no UC-specific requirements on memory configuration other than total RAM.
  • Physical/Local/DAS Storage
    • Disk quantity must exactly match table below.
    • Disk size (e.g. 146GB) must be same or higher than table below for UCS C-Series. For UCS B-series, any disk size may be used.
    • Disk speed (e.g. 10k RPM vs. 15k RPM) must be same or higher than table below for UCS C-Series. For UCS B-Series, any disk speed may be used.
    • Disk technology (e.g. SAS) must exactly match table below.
    • RAID Controller Card and battery backup must exactly match table below and parts lists here.
    • RAID configuration, including physical-to-logical volume mapping, must exactly match table below and RAID instructions in the document Installing CUCM on Virtual Servers here.
  • Shared Storage (SAN)
    • SAN transport must be Fibre Channel. Other shared storage options (iSCSI, FCoE, NFS) are not included in Tested Reference Configurations - follow "Specs-based VMware Support" Policy here.
    • Local disks on UCS B-Series are only used to host/boot VMware. UC apps must host/boot from Fibre Channel SAN. Certain UC apps also support diskless servers for boot from FC SAN.
    • Local disks on UCS C-Series DAS-only TRCs are used to host/boot VMware and UC apps.
    • Local disks on UCS C-Series TRCs with HBA are only used to host/boot VMware. UC apps must host/boot from Fibre Channel SAN. Certain UC apps also support diskless servers for boot from FC SAN.
  • Adapters for network and storage access (NIC, HBA, CNA, VIC)
    • UCS B-Series may use the mezzanine adapter in table below, or any other supported mezzanine adapter. Which adapter "should" be used is dependent on deployment, design and UC apps.
    • UCS C-Series NIC and HBA must exactly match adapters in table below. Other NIC, HBA, CNA or VIC options are not included in Tested Reference Configurations - follow "Specs-based VMware Support" Policy here.
  • Redundant Power supplies on UCS C210 are highly recommended.
  • Rack-mounting hardware on UCS C-Series: It is strongly recommended that you keep the Cisco default rail kit, unless you have different rack types such as telco racks or racks proprietary to another server vendor. You can optionally include the Cisco default cable management hardware. Cisco does not sell any other types of rack-mounting hardware; you must purchase such hardware from a third party.
  • Local DVD drive on UCS C-Series: It is strongly recommended that you keep a local DVD drive; otherwise certain customer procedures for installation and upgrading cannot be supported.


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 <span id="fck_dom_range_temp_1307473674591_228" /> 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

BIOS, Firmware, Drivers and UCS Software versions

There are no direct support requirements for particular versions of any of these items for Cisco UC apps.

Cisco UC apps will specify supported VMware versions and supported server models. Customers should use latest recommended BIOS, firmware, drivers and UCS / UCS Manager Software versions that are compatible with the UC-supported VMware version on the server model being used.


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 TRCs or UCS specs-based hardware, 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.

Related Hardware Documentation

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 in a Virtualized Environment

Rating: 3.6/5 (10 votes cast)

Personal tools