'''"UC on UCS"''' used by itself refers to both UC on UCS TRC and UC on UCS Specs-based.<br>

+

-

'''"Specs-based"''' used by itself refers to the common rules of UC on UCS Specs-based and Third-party Server Specs-based.&nbsp; <br><br>

+

-

Below is a comparison of the hardware support options. Note that the following are identical regardless of the support model chosen:

+

'''"TRC"''' used by itself means "UC on UCS Tested Reference Configuration (TRC)". '''"UC on UCS"''' used by itself refers to both UC on UCS TRC and UC on UCS Specs-based.<br> '''"Specs-based"''' used by itself refers to the common rules of UC on UCS Specs-based and Third-party Server Specs-based.&nbsp; <br><br>

-

* Virtual machine (OVA) definitions<br>

+

-

* VMware product, version and feature support<br>

+

Below is a comparison of the hardware support options. Note that the following are identical regardless of the support model chosen:

* See the [[#Introduction | Introduction]] for basic virtualization software requirements, including what is optional and what is mandatory.

+

-

* For Cisco UCS, no UC applications run or install directly on the server hardware; all applications run only as virtual machines. Cisco UC does not support a physical, bare-metal, or nonvirtualized installation on Cisco UCS server hardware.

+

*See the [[#Introduction|Introduction]] for basic virtualization software requirements, including what is optional and what is mandatory.

+

*For Cisco UCS, no UC applications run or install directly on the server hardware; all applications run only as virtual machines. Cisco UC does not support a physical, bare-metal, or nonvirtualized installation on Cisco UCS server hardware.

{{ note | For '''UC on UCS Specs-based''' and '''Third-party Server Specs-based''', use of VMware vCenter is mandatory, and Statistics Level 4 logging is mandatory. [[Troubleshooting and Performance Monitoring Virtualized Environments#vCenter Settings| Click here]] for how to configure VMware vCenter to capture these logs. If not configured by default, Cisco TAC may request enabling these settings in order to troubleshoot problems. }}

+

{{ note | For '''UC on UCS Specs-based''' and '''Third-party Server Specs-based''', use of VMware vCenter is mandatory, and Statistics Level 4 logging is mandatory. [[Troubleshooting and Performance Monitoring Virtualized Environments#vCenter Settings| Click here]] for how to configure VMware vCenter to capture these logs. If not configured by default, Cisco TAC may request enabling these settings in order to troubleshoot problems. }} <br> <br>

-

<br>

+

-

<br>

+

= "Can I use this server?" =

= "Can I use this server?" =

Line 492:

Line 555:

<br> The server model only matters in the context of:

<br> The server model only matters in the context of:

+

*whether or not it is on the [http://www.vmware.com/go/hcl VMware HCL]

*whether or not it is on the [http://www.vmware.com/go/hcl VMware HCL]

*what Intel CPU models does it carry (and are those CPU models allowed for UC virtualization)

*what Intel CPU models does it carry (and are those CPU models allowed for UC virtualization)

-

*can its hardware component options satisfy all other requirements of this policy

+

*can its hardware component options satisfy all other requirements of this policy

UC apps will specify [[Unified Communications VMWare Requirements|the required version of VMware vSphere ESXi]]. Customers should follow server vendor guidelines for what to use with this VMware version.

+

*BIOS

+

*Firmware

+

*Drivers

-

For Cisco UCS:

+

| colspan="3" |

-

* UCS Software or UCS Manager Software in UCS 6x00 hardware: use the latest recommended version for the VMware vSphere ESXi version

+

There are no UC-specific requirements.

-

* Other B-Series / C-Series BIOS, firmware, drivers: use the latest recommended version for the VMware vSphere ESXi version

** Note that the resultant "Logical Cores" do not factor into [[Unified Communications Virtualization Sizing Guidelines#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing| UC sizing rules for co-residency]]. UC still requires mapping one physical core to one vcpu core (not to one "Logical Core").

+

+

UC apps will specify [[Unified Communications VMWare Requirements|the required version of VMware vSphere ESXi]]. Customers should follow server vendor guidelines for what to use with this VMware version.

+

+

For Cisco UCS:

+

+

*UCS Software or UCS Manager Software in UCS 6x00 hardware: use the latest recommended version for the VMware vSphere ESXi version

+

*Other B-Series / C-Series BIOS, firmware, drivers: use the latest recommended version for the VMware vSphere ESXi version

**Note that the resultant "Logical Cores" do not factor into [[Unified Communications Virtualization Sizing Guidelines#General_Rules_for_Co-residency_and_Physical.2FVirtual_Hardware_Sizing|UC sizing rules for co-residency]]. UC still requires mapping one physical core to one vcpu core (not to one "Logical Core").

+

+

<br>

|-

|-

-

! Mechanical and Environmental<br>

+

! Mechanical and Environmental<br>

-

| colspan="3" |

+

| colspan="3" |

{{ note | Energy-saving features that cause reduction in CPU performance or real-time relocation/powering-down of virtual machines (such as '''CPU throttling''' or '''VMware Dynamic Power Management''') '''are not supported'''.

{{ note | Energy-saving features that cause reduction in CPU performance or real-time relocation/powering-down of virtual machines (such as '''CPU throttling''' or '''VMware Dynamic Power Management''') '''are not supported'''.

-

}}

+

}}

-

Otherwise, there are no UC-specific requirements for form factor, rack mounting hardware, cable management hardware, power supplies, fans or cooling systems. Follow server vendor guidelines for these components.

+

Otherwise, there are no UC-specific requirements for form factor, rack mounting hardware, cable management hardware, power supplies, fans or cooling systems. Follow server vendor guidelines for these components.

If you use a Cisco UCS bundle SKU, note that the rail kit, cable management and power supply options may not match what is available with non-bundled Cisco UCS.

If you use a Cisco UCS bundle SKU, note that the rail kit, cable management and power supply options may not match what is available with non-bundled Cisco UCS.

-

Redundant power supplies are highly recommended, particularly for '''UC on UCS'''.

+

Redundant power supplies are highly recommended, particularly for '''UC on UCS'''.

-

For Cisco UCS, it is strongly recommended to use the Cisco default rail kit, unless you have different rack types such as telco racks or racks proprietary to another server vendor. Cisco does not sell any other types of rack-mounting hardware; you must purchase such hardware from a third party.

+

For Cisco UCS, it is strongly recommended to use the Cisco default rail kit, unless you have different rack types such as telco racks or racks proprietary to another server vendor. Cisco does not sell any other types of rack-mounting hardware; you must purchase such hardware from a third party.

|}

|}

+

<br> <br>

<br>

<br>

-

<br>

+

= Processors / CPUs =

-

= Processors / CPUs =

+

Cisco Collaboration is a set of mission-critical, "Tier 0" applications, where customer expectations for availability, stability and predictable performance are higher than for traditional business applications. Cisco Collaboration apps are real-time and latency-sensitive, with extremely different resource footprints and operational characteristics than traditional business applications. Therefore note the following:

* Explicit qualification of new or existing CPU architectures is required.

-

* within a supported CPU architecture, not every CPU model will be supported

+

* Until qualification occurs, new CPU architectures are not allowed or supported, even if they are believed to be "better" than currently supported CPU models.

-

* UC support of new CPU architectures/models may lag the release date from Intel and/or server vendors.

+

* Some CPU architectures may never be allowed or supported by Cisco Collaboration (e.g. Intel desktop architecture or Xeon 65xx). Within an allowed or supported CPU architecture, some CPU models may never be supported (e.g. due to insufficient physical core speed).

-

<br>

+

* Collaboration application support for new CPU architectures/models may lag the release date from Intel and/or server vendors.

-

{{ note | Until UC qualification occurs, new CPU models are not supported, even if they are believed to be "better" than currently supported models. }}

:*CPU&nbsp;rules for UC&nbsp;on UCS&nbsp;Specs-based and 3rd-party Specs-based (described in second table below).&nbsp; CPU must also be allowed for the specific Cisco Collaboration app (see links for each app on www.cisco.com/go/uc-virtualized). <br>

+

:*UC on&nbsp;UCS Tested Reference Configurations have additional restrictions on CPU choice (described in second table below).&nbsp; The&nbsp;TRC and its CPU must also be allowed for the specific&nbsp;Cisco Collaboration app (see links for each app on www.cisco.com/go/uc-virtualized).<br>

+

+

<br>

+

+

{{ note | Only certain VM configurations of certain Collaboration apps are allowed to run on a "Restricted UC Performance" CPU. See the application pages on www.cisco.com/go/uc-virtualized.}}

For purposes of [[Unified Communications Virtualization Sizing Guidelines|sizing rules and co-residency]], virtualized UC apps see equivalent performance from one physical CPU core on any of the above architectures. E.g. UC apps perform eqiuvalently on 1 physical core of 5600 at 2.53+&nbsp;GHz or 1 physical core of E5-2600 at 2.50+ GHz or 1 physical core of E7-2800 at 2.40+&nbsp;GHz.<br>

*Physical CPU core speed same or higher than that of the TRC BOM's CPU model in [[#UC_on_UCS_Tested_Reference_Configurations|Table 1]].

+

+

E.g. if the TRC BOM was tested with 2-socket Intel Xeon E5-2680 (Romley/SandyBridge-EP, 8-core, 2.7 GHz), then 2-sockets of any 8-core CPU of 2.7 GHz or higher with the E5-26xx/46xx (Intel&nbsp;Xeon Romley/SandyBridge-EP architecture) may be substituted.

+

| colspan="2" |

| colspan="2" |

-

The following "Full UC Performance" models:

+

See app links in table on http://www.cisco.com/go/uc-virtualized or [[Unified Communications Virtualization Supported Applications|Supported Applications]] for which CPU Types are allowed for a given VM configuration of a UC app. E.g. the Unified Communications Manager 7500 user VM configuration is only allowed on a Full UC Performance CPU. <br>

* Hyper-threading on the CPU should be enabled when available, but the resulting Logical Cores do not change UC app rules. UC rules are based on 1:1 mapping of physical cores to virtual cores, not Logical Cores to virtual cores.

+

-

<br> Cisco TAC is not obligated to troubleshoot UC app issues in deployments with insufficient physical processor cores or speed.

+

Per these policies, recall that '''physical CPU cores may not be over-subscribed for UC VMs'''

+

+

*I.e. '''one physical CPU core must equal one VM vCPU core'''.

+

*Hyper-threading on the CPU should be enabled when available, but the resulting Logical Cores do not change UC app rules. UC rules are based on 1:1 mapping of physical cores to vcpu, not Logical Cores to vcpu.

+

+

<br> Cisco TAC is not obligated to troubleshoot UC app issues in deployments with insufficient physical processor cores or speed.

|}

|}

-

<br><br>

-

= Memory / RAM =

+

<br><br>

+

+

= Memory / RAM =

{{ note | Virtualization software licenses such as Cisco UC Virtualization Foundation or VMware vSphere limit the amount of total vRAM that can be used (and therefore the amount of physical RAM that can be used for UC VMs, due to UC sizing rules). See [[Unified Communications VMware Requirements]] for these limits. In general larger deployments, or deployments with high VM counts, will require very high vRAM totals and will therefore need to use VMware vSphere instead of Cisco UC Virtualization Foundation.

{{ note | Virtualization software licenses such as Cisco UC Virtualization Foundation or VMware vSphere limit the amount of total vRAM that can be used (and therefore the amount of physical RAM that can be used for UC VMs, due to UC sizing rules). See [[Unified Communications VMware Requirements]] for these limits. In general larger deployments, or deployments with high VM counts, will require very high vRAM totals and will therefore need to use VMware vSphere instead of Cisco UC Virtualization Foundation.

-

If using high-memory-capacity servers, use VMware vSphere instead to ensure use of all physical memory. }}

+

If using high-memory-capacity servers, use VMware vSphere instead to ensure use of all physical memory. }}

{| width="1200" style="" class="wikitable FCK__ShowTableBorders"

{| width="1200" style="" class="wikitable FCK__ShowTableBorders"

|-

|-

-

!

+

! <br>

-

! UC on UCS TRC

+

! UC on UCS TRC

! Specs-based (UCS or 3rd-party Server)

! Specs-based (UCS or 3rd-party Server)

-

|-

|-

! rowspan="2" | Physical RAM

! rowspan="2" | Physical RAM

-

| Total ''available'' is listed in [[#UC on UCS Tested Reference Configurations | Table 1]]. Additional memory may be added.

+

| Total ''available'' is listed in [[#UC_on_UCS_Tested_Reference_Configurations|Table 1]]. Additional memory may be added.

| Total ''available'' depends on the server chosen.

| Total ''available'' depends on the server chosen.

-

|-

|-

| colspan="2" |

| colspan="2" |

-

Total ''required'' is dependent on the virtual machine quantity/size mix deployed on the hardware:

+

Total ''required'' is dependent on the virtual machine quantity/size mix deployed on the hardware:

*2-4 GB required for virtualization software, depending on version.&nbsp; See [[Unified_Communications_Virtualization_Sizing_Guidelines|Memory/RAM section of General sizing rules]].

-

* while following [[Unified Communications Virtualization Sizing Guidelines|co-residency support policy rules]]. Per these rules, recall that '''UC does not support physical memory oversubscription''' (1 GB of vRAM must equal 1 GB of physical RAM). Cisco TAC is not obligated to troubleshoot UC app issues if the deployment has insufficient physical RAM.

*while following [[Unified Communications Virtualization Sizing Guidelines|co-residency support policy rules]]. Per these rules, recall that '''UC does not support physical memory oversubscription''' (1 GB of vRAM must equal 1 GB of physical RAM). Cisco TAC is not obligated to troubleshoot UC app issues if the deployment has insufficient physical RAM.

|-

|-

-

! Memory Module/DIMM Speed and Population

+

! Memory Module/DIMM Speed and Population

-

| colspan="2" |

+

| colspan="2" |

-

For what was tested in a TRC, see [[#UC on UCS Tested Reference Configurations | Table 1]].<br>

+

For what was tested in a TRC, see [[#UC_on_UCS_Tested_Reference_Configurations|Table 1]].<br>

+

+

Follow server vendor guidelines for optimum memory population for the memory capacity required by UC.

+

+

*For Cisco UCS, use the Specs Sheets at [https://apps.cisco.com/QuickCatalog/home.do UCS Quick Catalog]. E.g. for a UCS B200 M3 with 96GB total RAM, optimal is 4x8GB DIMM + 4x4GB DIMM. Using 6x16GB DIMM is not optimal.<br>

-

Follow server vendor guidelines for optimum memory population for the memory capacity required by UC.

+

Otherwise, there are no UC-specific requirements (primarily because UC does not support memory oversubscription).<br>

-

* For Cisco UCS, use the Specs Sheets at [https://apps.cisco.com/QuickCatalog/home.do UCS Quick Catalog]. E.g. for a UCS B200 M3 with 96GB total RAM, optimal is 4x8GB DIMM + 4x4GB DIMM. Using 6x16GB DIMM is not optimal.<br>

+

-

Otherwise, there are no UC-specific requirements (primarily because UC does not support memory oversubscription).<br>

+

*UC allows any DIMM speed (e.g. 1333 MHz, 1600 MHz, etc.).<br>

-

* UC allows any DIMM speed (e.g. 1333 MHz, 1600 MHz, etc.).<br>

+

*UC allows any memory hardware module size, density and quantity (including changing the DIMM population on a Tested Reference Configuration) as long as UC-required RAM capacity is met, and the server vendor supports the intended memory configuration.<br>

-

* UC allows any memory hardware module size, density and quantity as long as UC-required RAM capacity is met, and the server vendor supports it.

+

|}

|}

Line 688:

Line 844:

*Compatible with the VMware HCL and compatible with the supported server model used

*Compatible with the VMware HCL and compatible with the supported server model used

*[[Unified Communications Virtualization Downloads (including OVA/OVF Templates)|Published '''vDisk''' capacity requirements of UC VMs ]]. Disk space must be available to the VM as needed. If thin provisioned, running out of disk space due to thin provisioning will crash the application and corrupt the virtual disk (which may also prevent restore from backup on the virtual disk).

:*For diskless TRCs and any Specs-based server, thin provisioning (either from VMware or from storage array) is allowed with the caveat that disk space must be available to the VM as needed. Running out of disk space due to thin provisioning will crash the application and corrupt the virtual disk (which may also prevent restore from backup on the virtual disk).

<br> {{ note | '''UC on UCS TRCs''' using only DAS storage (such as C220 M3S TRC#1) have been pre-designed and tested to meet the above requirements for any UC with UC co-residency scenario that will fit on the TRC. Detailed capacity planning is not required unless deploying

<br> {{ note | '''UC on UCS TRCs''' using only DAS storage (such as C220 M3S TRC#1) have been pre-designed and tested to meet the above requirements for any UC with UC co-residency scenario that will fit on the TRC. Detailed capacity planning is not required unless deploying

Line 700:

Line 860:

<br> See below for supported storage hardware options.

<br> See below for supported storage hardware options.

-

{| width="770" class="wikitable FCK__ShowTableBorders" style=""

+

{| width="770" style="" class="wikitable FCK__ShowTableBorders"

|-

|-

-

! <br>

+

! <br>

! UC on UCS TRC

! UC on UCS TRC

! Specs-based (UCS or 3rd-party Server)

! Specs-based (UCS or 3rd-party Server)

Line 723:

Line 883:

<br> '''DAS Support Details'''

<br> '''DAS Support Details'''

-

{| width="1200" class="wikitable FCK__ShowTableBorders" style=""

+

{| width="1200" style="" class="wikitable FCK__ShowTableBorders"

|-

|-

-

! <br>

+

! <br>

! UC on UCS TRC

! UC on UCS TRC

! Specs-based (UCS or 3rd-party Server)

! Specs-based (UCS or 3rd-party Server)

Line 743:

Line 903:

*compatible with the VMware HCL and compatible with the server model used

*compatible with the VMware HCL and compatible with the server model used

*The storage solution must be compatible with the VMware HCL. For example, refer to the “SAN/Storage” tab at http://www.vmware.com/resources/compatibility/search.php?sourceid=ie7&amp;rls=com.microsoft:en-us:IE-SearchBox&amp;ie=&amp;oe=

*The storage solution must be compatible with the VMware HCL. For example, refer to the “SAN/Storage” tab at http://www.vmware.com/resources/compatibility/search.php?sourceid=ie7&amp;rls=com.microsoft:en-us:IE-SearchBox&amp;ie=&amp;oe=

*No UC requirements on disk size, speed, technology (SAS, SATA, FC disk), form factor or RAID configuration as long as requirements for compatibility, latency, performance and capacity are met. "Tier 1 Storage" is generally recommended for UC deployments. See the [[UC Virtualization Storage System Design Requirements]] for an illustration of a best practices storage array configuration for UC.

*No UC requirements on disk size, speed, technology (SAS, SATA, FC disk), form factor or RAID configuration as long as requirements for compatibility, latency, performance and capacity are met. "Tier 1 Storage" is generally recommended for UC deployments. See the [[UC Virtualization Storage System Design Requirements]] for an illustration of a best practices storage array configuration for UC.

Line 769:

Line 929:

<br>

<br>

-

<br> <br> '''Removable Media'''<br>Booting from USB devices or SD cards is not supported with UC apps at this time.<br>

+

<br> <br> '''Removable Media'''

+

+

{| width="770" style="" class="wikitable FCK__ShowTableBorders"

+

|-

+

! <br>

+

! UC on UCS TRC

+

! Specs-based (UCS or 3rd-party Server)

+

|-

+

! Boot from SD cards, USB flash or other

+

|

+

*Not allowed or supported by Cisco for apps or VMware vSphere ESXi. TRCs are only validated as either boot from DAS or diskless boot from FC SAN depending on Table 1.

+

*Note all current TRCs are either diskless blades or C-Series DAS/HDD. SD cards in C-Series TRCs are used for convenience to get the UCS utilities (like SCU and HUU), in lieu of a DVD drive.

+

+

|

+

*Not allowed or supported by Cisco for apps. Must boot from DAS, SAN or NAS per Specs-based Storage requirements.

+

*Allowed for VMware vSphere ESXi as long as supported by server vendor.&nbsp; Cisco&nbsp;Collaboration apps do not test, validate or troubleshoot these boot methods - work with server vendor if boot issues.

+

+

|}

Otherwise, there are no UC-specific requirements or restrictions. The different methods of [[Implementing Virtualization Deployments#Installing_UC_Applications_in_the_VM|installing UC apps into VMs]] can leverage the following distribution types of Cisco UC software:

Otherwise, there are no UC-specific requirements or restrictions. The different methods of [[Implementing Virtualization Deployments#Installing_UC_Applications_in_the_VM|installing UC apps into VMs]] can leverage the following distribution types of Cisco UC software:

{{ note | Do not assume that every UCS bundle part number on [https://apps.cisco.com/QuickCatalog/home.do UCS Quick Catalog] can be used with UC on UCS. Before quoting one of these bundles, identify the BOM that it ships and see below:

+

{{ note | Bundle SKUs for UC on UCS TRCs are listed in the [http://apps.cisco.com/ccw/cpc/offers/uconucs UC on UCS section of Cisco Commerce Build and Price tool].

-

* If the bundle meets TRC requirements, it may be quoted for UC on UCS TRC.

+

+

Do not assume that other UCS bundle SKUs on [http://apps.cisco.com/ccw/cpc/home.do Cisco Commerce Build and Price] can be used with UC on UCS. Before quoting one of these bundles, identify the BOM that it ships and see below:

+

* If the bundle meets TRC requirements on this page, it may be quoted for UC on UCS TRC.

* If the bundle does NOT meet TRC requirements but DOES meet Specs-based requirements, then it may be quoted for UC on UCS Specs-based only.

* If the bundle does NOT meet TRC requirements but DOES meet Specs-based requirements, then it may be quoted for UC on UCS Specs-based only.

-

* If the bundle does NOT meet TRC requirements and also does NOT meet Specs-based requirements, then it may NOT be quoted for UC on UCS at all without modification. }} <br>

+

* If the bundle does NOT meet TRC requirements and also does NOT meet Specs-based requirements, then it may NOT be quoted for UC on UCS at all without modification. }} <br>

-

=== B440 M2 TRC#1 ===

+

=== B440 M2 TRC#1 ===

-

This BOM was also quotable via fixed-configuration bundle UCS-B440M2-VCDL1.

+

2X-Large blade&nbsp;TRC.<br>

+

+

This BOM was also quotable via fixed-configuration bundle UCS-B440M2-VCDL1.

This configuration is also quotable as either UCUCS-EZ-B200M3 (single blade) or UCSB-EZ-UC-B200M3 (multiple blades with chassis and switching).

{| class="prettytable"

{| class="prettytable"

|-

|-

-

|

+

|

-

'''Quantity'''

+

'''Quantity'''

-

|

+

|

-

'''Cisco Part Number'''

+

'''Cisco Part Number'''

-

|

+

|

-

'''Description'''

+

'''Description'''

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''UCSB-B200-M3-U'''

+

'''UCSB-B200-M3-U'''

+

+

|

+

UCS B200 M3 Blade Server w/o CPU, mem, HDD, mLOM/mezz (UPG)

-

|

-

UCS B200 M3 Blade Server w/o CPU, mem, HDD, mLOM/mezz (UPG)

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCS-CPU-E5-2680'''

+

'''UCS-CPU-E5-2680'''

-

|

+

|

-

2.70 GHz E5-2680 130W 8C/20MB Cache/DDR3 1600MHz

+

2.70 GHz E5-2680 130W 8C/20MB Cache/DDR3 1600MHz

|-

|-

-

|'''8'''

+

| '''8'''

-

|'''UCS-MR-1X082RY-A'''

+

| '''UCS-MR-1X082RY-A'''

-

|8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

+

| 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

-

+

|-

|-

-

|'''8'''

+

| '''8'''

-

|'''UCS-MR-1X041RY-A'''

+

| '''UCS-MR-1X041RY-A'''

-

|4GB DDR3-1600-MHz RDIMM/PC3-12800/single rank/1.35v

+

| 4GB DDR3-1600-MHz RDIMM/PC3-12800/single rank/1.35v

-

+

|-

|-

-

|

+

| <br>

-

|

+

| <br>

-

|Diskless

+

| Diskless

-

+

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''UCSB-MLOM-40G-01'''

+

'''UCSB-MLOM-40G-01'''

-

|

+

|

-

VIC 1240 modular LOM for M3 blade servers

+

VIC 1240 modular LOM for M3 blade servers

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''N20-BBLKD'''

+

'''N20-BBLKD'''

-

+

-

|

+

-

Auto-included: UCS 2.5 inch HDD blanking panel

+

+

|

+

Auto-included: UCS 2.5 inch HDD blanking panel

+

<br>

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSB-HS-01-EP'''

+

'''UCSB-HS-01-EP'''

-

|

+

|

-

Auto-included: Heat Sink for UCS B200 M3 server

+

Auto-included: Heat Sink for UCS B200 M3 server

|}

|}

+

<br>

+

<br>

-

<br>

+

=== C260 M2 TRC#1 ===

+

Extra-Large&nbsp;TRC.<br>

-

<br>

+

This configuration was also quotable as UCS-C260M2-VCD2.

-

+

-

+

-

+

-

<br>

+

-

+

-

=== C260 M2 TRC#1 ===

+

-

+

-

This configuration was also quotable as UCS-C260M2-VCD2.

+

{| class="prettytable"

{| class="prettytable"

|-

|-

-

|

+

|

-

'''Quantity'''

+

'''Quantity'''

-

|

+

|

-

'''Cisco Part Number'''

+

'''Cisco Part Number'''

-

|

+

|

-

'''Description'''

+

'''Description'''

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''C260-BASE-2646'''

+

'''C260-BASE-2646'''

-

|

+

|

-

UCS C260 M2 Rack Server (w/o CPU, MRB, PSU)

+

UCS C260 M2 Rack Server (w/o CPU, MRB, PSU)

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCS-CPU-E72870'''

+

'''UCS-CPU-E72870'''

-

|

+

|

-

2.4 GHz E7-2870 130W 10C/30M Cache

+

2.4 GHz E7-2870 130W 10C/30M Cache

|-

|-

-

|

+

|

-

'''16'''

+

'''16'''

-

|

+

|

-

'''C260-MRBD-002'''

+

'''C260-MRBD-002'''

-

|

+

|

-

2 DIMM Memory Riser Board For C260

+

2 DIMM Memory Riser Board For C260

|-

|-

-

|

+

|

-

'''16'''

+

'''16'''

-

|

+

|

-

'''UCS-MR-2X041RX-C'''

+

'''UCS-MR-2X041RX-C'''

-

|

+

|

-

2X4GB DDR3-1333-MHz RDIMM/PC3-10600/single rank/x1/1.35v

+

2X4GB DDR3-1333-MHz RDIMM/PC3-10600/single rank/x1/1.35v

|-

|-

-

|

+

|

-

'''16'''

+

'''16'''

-

|

+

|

-

'''A03-D300GA2'''

+

'''A03-D300GA2'''

-

|

+

|

-

300GB 6Gb SAS 10K RPM SFF HDD/hot plug/drive sled mounted

+

300GB 6Gb SAS 10K RPM SFF HDD/hot plug/drive sled mounted

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSC-DBKP-08E'''

+

'''UCSC-DBKP-08E'''

-

|

+

|

-

8 Drive Backplane W/Expander For C-Series

+

8 Drive Backplane W/Expander For C-Series

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''R2XX-PL003'''

+

'''R2XX-PL003'''

-

|

+

|

-

LSI 6G MegaRAID 9261-8i card (RAID 0,1,5,6,10,60) - 512WC

+

LSI 6G MegaRAID 9261-8i card (RAID 0,1,5,6,10,60) - 512WC

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''UCSC-BBU-11-C260'''

+

'''UCSC-BBU-11-C260'''

-

|

+

|

-

RAID battery backup for LSI Electr controller for C260

+

RAID battery backup for LSI Electr controller for C260

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

| One of:<br>

-

'''N2XX-AIPCI02'''

+

*'''N2XX-AIPCI02'''

+

*'''UCSC-PCIE-IRJ45'''

-

|

+

| <br>

-

Intel Quad port GbE Controller (E1G44ETG1P20)

+

*Intel Quad port GbE Controller (E1G44ETG1P20)

+

*Intel i350 Quad Port 1Gb Adapter

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSC-PSU2-1200'''

+

'''UCSC-PSU2-1200'''

-

|

+

|

-

1200W 2u Power Supply For UCS

+

1200W 2u Power Supply For UCS

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''UCSC-RAIL-2U'''

+

'''UCSC-RAIL-2U'''

-

|

+

|

-

2U Rail Kit for UCS C-Series servers

+

2U Rail Kit for UCS C-Series servers

|-

|-

-

|

+

|

+

<br>

+

|

+

<br>

-

|

+

|

-

+

DVD drive not provided nor supported on this model

-

+

-

|

+

-

DVD drive not provided nor supported on this model

+

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''UCS-SD-16G'''

+

'''UCS-SD-16G'''

-

|

+

|

-

16GB SD Card module for UCS Servers

+

16GB SD Card module for UCS Servers

|-

|-

-

|

+

|

-

'''1'''

+

'''1'''

-

|

+

|

-

'''UCSX-MLOM-001'''

+

'''UCSX-MLOM-001'''

-

|

+

|

-

Modular LOM For UCS

+

Modular LOM For UCS

|-

|-

-

|

+

|

-

'''32'''

+

'''32'''

-

|

+

|

-

'''UCS-MKIT-041RX-C'''

+

'''UCS-MKIT-041RX-C'''

-

|

+

|

-

Auto-Included: Mem kit for UCS-MR-2X041RX-C

+

Auto-Included: Mem kit for UCS-MR-2X041RX-C

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSC-HS-01-C260'''

+

'''UCSC-HS-01-C260'''

-

|

+

|

-

Auto-Included: CPU HEAT SINK for UCS C260 M2 RACK SERVER

+

Auto-Included: CPU HEAT SINK for UCS C260 M2 RACK SERVER

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSC-PCIF-01F'''

+

'''UCSC-PCIF-01F'''

-

|

+

|

-

Auto-Included: Full height PCIe filler for C-Series

+

Auto-Included: Full height PCIe filler for C-Series

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSC-PCIF-01H'''

+

'''UCSC-PCIF-01H'''

-

|

+

|

-

Auto-Included: Half height PCIe filler for UCS

+

Auto-Included: Half height PCIe filler for UCS

|-

|-

-

|

+

|

-

'''2'''

+

'''2'''

-

|

+

|

-

'''UCSC-RC-P8M-C260'''

+

'''UCSC-RC-P8M-C260'''

-

|

+

|

-

Auto-Included: .79m SAS RAID Cable for C260

+

Auto-Included: .79m SAS RAID Cable for C260

|}

|}

+

<br>

+

<br>

-

<br>

+

=== C240 M3S (SFF) TRC#1 ===

-

=== C240 M3S (SFF) TRC#1 ===

+

{{ note | The C240 M3L (LFF) is only supported under UC on UCS Specs-based. }} This configuration is also available via bundle UCUCS-EZ-C240M3S. Note that the RAID controller shipped with this bundle depends on date of purchase. <br>

-

{{ note | The C240 M3L (LFF) is only supported under UC on UCS Specs-based. }}

+

Large&nbsp;TRC.<br>

-

This configuration is also available via bundle UCUCS-EZ-C240M3S.

+

+

<br>

{| class="prettytable"

{| class="prettytable"

|-

|-

-

|'''Quantity'''

+

| '''Quantity'''

-

+

| '''Cisco Part Number'''

-

|'''Cisco Part Number'''

+

| '''Description'''

-

+

-

|'''Description'''

+

-

+

|-

|-

-

|'''1'''

+

| '''1'''

-

|'''UCSC-C240-M3S

+

| '''UCSC-C240-M3S'''

-

|UCS C240 M3 SFF w/o CPU, mem, HD, PCIe, w/ rail kit

+

| UCS C240 M3 SFF w/o CPU, mem, HD, PCIe, w/ rail kit

-

+

|-

|-

-

|'''2

+

| '''2'''

-

|'''UCS-CPU-E5-2680

+

| '''UCS-CPU-E5-2680'''

-

|2.70 GHz E5-2680 130W 8C/20MB Cache/DDR3 1600MHz

+

| 2.70 GHz E5-2680 130W 8C/20MB Cache/DDR3 1600MHz

-

+

|-

|-

-

|'''8'''

+

| '''8'''

-

|'''UCS-MR-1X082RY-A'''

+

| '''UCS-MR-1X082RY-A'''

-

|8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

+

| 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

-

+

|-

|-

-

|'''8'''

+

| '''8'''

-

|'''UCS-MR-1X041RY-A'''

+

| '''UCS-MR-1X041RY-A'''

-

|4GB DDR3-1600-MHz RDIMM/PC3-12800/single rank/1.35v

+

| 4GB DDR3-1600-MHz RDIMM/PC3-12800/single rank/1.35v

-

+

|-

|-

-

|'''16

+

| '''16'''

-

|'''UCS-HDD300GI2F105

+

| '''UCS-HDD300GI2F105'''

-

|300GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted

+

| 300GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted

-

+

|-

|-

-

|'''1

+

| '''1'''

-

|'''UCSC-SD-16G-C240

+

| '''UCSC-SD-16G-C240'''

-

|16GB SD Card Module for C240 Servers

+

| 16GB SD Card Module for C240 Servers

-

+

|-

|-

-

|'''1

+

| '''1'''

-

|'''One of:

+

| '''One of:'''

*UCS-RAID-9266

*UCS-RAID-9266

-

*UCS-RAID-9266CV

+

*UCS-RAID-9266CV

-

|<br>

+

*UCS-RAID9271CV-8I

-

*MegaRAID 9266-8i + battery backup for C240 and C220

+

-

*MegaRAID 9266CV-8i w/TFM + Super Cap

+

-

|-

+

| <br>

-

|'''

+

*MegaRAID 9266-8i + battery backup for C240 and C220

-

|'''

+

*MegaRAID 9266CV-8i w/TFM + Super Cap

-

|DVD drive not offered with C240 M3.

+

*MegaRAID 9271CV Raid card with 8 internal SAS/SATA parts, S

|-

|-

-

|'''2

+

| <br>

-

|'''UCSC-PCIE-IRJ45

+

| <br>

-

|Intel i350 Quad Port 1Gb Adapter

+

| DVD drive not offered with C240 M3.

-

+

|-

|-

-

|'''2

+

| '''2'''

-

|'''UCSC-PSU2-1200

+

| '''UCSC-PCIE-IRJ45'''

-

|1200W 2u Power Supply For UCS

+

| Intel i350 Quad Port 1Gb Adapter

-

+

|-

|-

-

|'''2

+

| '''2'''

-

|'''UCSC-HS-C240M3

+

| '''UCSC-PSU2-1200'''

-

|Auto-included: Heat Sink for UCS C240 M3 Rack Server

+

| 1200W 2u Power Supply For UCS

-

+

|-

|-

-

|'''1

+

| '''2'''

-

|'''UCSC-RAIL-2U

+

| '''UCSC-HS-C240M3'''

-

|Auto-included: 2U Rail Kit for UCS C-Series servers

+

| Auto-included: Heat Sink for UCS C240 M3 Rack Server

-

+

|-

|-

-

|'''8

+

| '''1'''

-

|'''N20-BBLKD

+

| '''UCSC-RAIL-2U'''

-

|Auto-included: UCS 2.5 inch HDD blanking panel

+

| Auto-included: 2U Rail Kit for UCS C-Series servers

-

+

|-

|-

-

|'''2

+

| '''8'''

-

|'''UCSC-PCIF-01F

+

| '''N20-BBLKD'''

-

|Auto-included:Full height PCIe filler for C-Series

+

| Auto-included: UCS 2.5 inch HDD blanking panel

-

+

|-

+

| '''2'''

+

| '''UCSC-PCIF-01F'''

+

| Auto-included:Full height PCIe filler for C-Series

|}

|}

+

<br> <br>

-

<br>

+

=== C240 M3S (SFF) TRC#2 ===

-

=== C220 M3S (SFF) TRC#1 ===

+

{{ note | The C240 M3L (LFF) is only supported under UC on UCS Specs-based. }} This configuration is also available as part of a Cisco Business&nbsp;Edition 7000 bundle BE7K-K9 or BE7K-K9-XU. <br>

-

{{ note | This TRC is NOT supported for use with Cisco Business Edition 6000. }}

+

-

+

-

{{ note | The C220 M3L (LFF) is only supported under UC on UCS Specs-based. }}

+

-

This configuration is also available as bundle UCUCS-EZ-C220M3S.

+

+

Medium TRC.<br>

{| class="prettytable"

{| class="prettytable"

|-

|-

-

|'''Quantity'''

+

| '''Quantity'''

+

| '''Cisco Part Number'''

+

| '''Description'''

+

|-

+

| '''1'''

+

| '''UCSC-C240-M3S'''

+

| UCS C240 M3 SFF w/o CPU, mem, HD, PCIe, w/ rail kit

+

|-

+

| '''2'''

+

| '''UCS-CPU-E5-2640'''

+

| 2.50 GHz E5-2640/95W 6C/15MB Cache/DDR3 1333MHz

+

|-

+

| '''8'''

+

| '''UCS-MR-1X082RY-A'''

+

| 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

+

|-

+

| '''12'''

+

| '''A03-D300GA2 '''<br>

+

| 300GB 6Gb SAS 10K RPM SFF HDD/hot plug/drive sled mounted<br>

+

|-

+

| '''1'''

+

|

+

'''UCS-RAID9271CV-8I'''

-

|'''Cisco Part Number'''

+

|

-

+

MegaRAID 9271CV Raid card with 8 internal SAS/SATA parts, S

-

|'''Description'''

+

|-

|-

-

|'''1'''

+

| '''1<br>'''

-

|'''UCSC-C220-M3S

+

| '''R2XX-RAID5<br>'''

-

|UCS C220 M3 SFF w/o CPU, mem, HDD, PCIe, w/ rail kit

+

| Enable RAID 5 Setting<br>

-

+

|-

|-

-

|'''2

+

| <br>

-

|'''UCS-CPU-E5-2643

+

| <br>

-

|3.30 GHz E5-2643/130W 4C/10MB Cache/DDR3 1600MHz

+

| DVD drive not offered with C240 M3.

-

+

|-

|-

-

|'''8

+

| '''2'''

-

|'''UCS-MR-1X082RY-A

+

| '''UCSC-PCIE-IRJ45'''

-

|8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

+

| Intel i350 Quad Port 1Gb Adapter

-

+

|-

|-

-

|'''8

+

| '''2'''

-

|'''UCS-HDD300GI2F105

+

| '''UCSC-PSU2-1200'''

-

|300GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted

+

| 1200W 2u Power Supply For UCS

+

|-

+

| '''2'''

+

| '''UCSC-HS-C240M3'''

+

| Auto-included: Heat Sink for UCS C240 M3 Rack Server

+

|-

+

| '''1'''

+

| '''UCSC-RAIL-2U'''

+

| Auto-included: 2U Rail Kit for UCS C-Series servers

+

|-

+

| '''12'''

+

| '''N20-BBLKD'''

+

| Auto-included: UCS 2.5 inch HDD blanking panel

+

|-

+

| '''2'''

+

| '''UCSC-PCIF-01F'''

+

| Auto-included:Full height PCIe filler for C-Series

+

|}

+

<br> <br>

+

+

=== C220 M3S (SFF) TRC#1 ===

+

+

{{ note | This TRC is NOT supported for use with [[Cisco Business Edition 6000]]. }}

+

+

{{ note | The C220 M3L (LFF) is only supported under UC on UCS Specs-based. }} This configuration is also available as bundle UCUCS-EZ-C220M3S. Note that the RAID controller shipped with this bundle depends on date of purchase.

+

+

Medium TRC.<br>

+

+

{| class="prettytable"

+

|-

+

| '''Quantity'''

+

| '''Cisco Part Number'''

+

| '''Description'''

+

|-

+

| '''1'''

+

| '''UCSC-C220-M3S'''

+

| UCS C220 M3 SFF w/o CPU, mem, HDD, PCIe, w/ rail kit

+

|-

+

| '''2'''

+

| '''UCS-CPU-E5-2643'''

+

| 3.30 GHz E5-2643/130W 4C/10MB Cache/DDR3 1600MHz

+

|-

+

| '''8'''

+

| '''UCS-MR-1X082RY-A'''

+

| 8GB DDR3-1600-MHz RDIMM/PC3-12800/dual rank/1.35v

+

|-

+

| '''8'''

+

| '''UCS-HDD300GI2F105'''

+

| 300GB 6Gb SAS 15K RPM SFF HDD/hot plug/drive sled mounted

|-

|-

-

|'''1

+

| '''1'''

-

|'''One of:

+

| '''One of:'''

*UCS-RAID-9266

*UCS-RAID-9266

*UCS-RAID-9266CV

*UCS-RAID-9266CV

-

|<br>

+

*UCS-RAID9271CV-8I

-

*MegaRAID 9266-8i + battery backup for C240 and C220

+

-

*MegaRAID 9266CV-8i w/TFM + Super Cap

+

-

|-

+

| <br>

-

|'''1

+

*MegaRAID 9266-8i + battery backup for C240 and C220

-

|'''UCSC-SD-16G-C220

+

*MegaRAID 9266CV-8i w/TFM + Super Cap

-

|16GB SD Card Module for C220 Servers

+

*MegaRAID 9271CV Raid card with 8 internal SAS/SATA parts, S

|-

|-

-

|'''

+

| '''1'''

-

|'''

+

| '''UCSC-SD-16G-C220'''

-

|DVD drive not offered with C220 M3.

+

| 16GB SD Card Module for C220 Servers

-

+

|-

|-

-

|'''1

+

| <br>

-

|'''UCSC-PCIE-IRJ45

+

| <br>

-

|Intel i350 Quad Port 1Gb Adapter

+

| DVD drive not offered with C220 M3.

-

+

|-

|-

-

|'''2

+

| '''1'''

-

|'''UCSC-PSU-650W

+

| '''UCSC-PCIE-IRJ45'''

-

|650W power supply for C-series rack servers

+

| Intel i350 Quad Port 1Gb Adapter

-

+

|-

|-

-

|'''2

+

| '''2'''

-

|'''UCSC-HS-C220M3

+

| '''UCSC-PSU-650W'''

-

|Auto-included: Heat Sink for UCS C220 M3 Rack Server

+

| 650W power supply for C-series rack servers

-

+

|-

+

| '''2'''

+

| '''UCSC-HS-C220M3'''

+

| Auto-included: Heat Sink for UCS C220 M3 Rack Server

|-

|-

-

|'''1

+

| '''1'''

-

|'''UCSC-RAIL1

+

| '''UCSC-RAIL1'''

-

|Auto-included: 2U Rail Kit for C220 servers

+

| Auto-included: 2U Rail Kit for C220 servers

-

+

|}

|}

+

<br>

+

<br>

-

<br>

+

=== C220 M3S (SFF) TRC#2 ===

-

=== C220 M3S (SFF) TRC#2 ===

{{ note |

{{ note |

-

*This TRC is supported for use with:

+

*This hardware configuration is supported for use as:

-

** Cisco Business Edition 6000 (where it is quoted as an auto-included option in BE6K bundle, UCSC-C220-M3SBE)

"TRC" used by itself means "UC on UCS Tested Reference Configuration (TRC)". "UC on UCS" used by itself refers to both UC on UCS TRC and UC on UCS Specs-based."Specs-based" used by itself refers to the common rules of UC on UCS Specs-based and Third-party Server Specs-based.

Below is a comparison of the hardware support options. Note that the following are identical regardless of the support model chosen:

VMware Requirements

VMware virtualization software is required for Cisco TAC support.

See the Introduction for basic virtualization software requirements, including what is optional and what is mandatory.

For Cisco UCS, no UC applications run or install directly on the server hardware; all applications run only as virtual machines. Cisco UC does not support a physical, bare-metal, or nonvirtualized installation on Cisco UCS server hardware.

All UC virtualization deployments must follow UC rules for supported VMware products, versions, editions and features as described here.

Note:

For UC on UCS Specs-based and Third-party Server Specs-based, use of VMware vCenter is mandatory, and Statistics Level 4 logging is mandatory. Click here for how to configure VMware vCenter to capture these logs. If not configured by default, Cisco TAC may request enabling these settings in order to troubleshoot problems.

Note that the resultant "Logical Cores" do not factor into UC sizing rules for co-residency. UC still requires mapping one physical core to one vcpu core (not to one "Logical Core").

Mechanical and Environmental

Note:

Energy-saving features that cause reduction in CPU performance or real-time relocation/powering-down of virtual machines (such as CPU throttling or VMware Dynamic Power Management) are not supported.

Otherwise, there are no UC-specific requirements for form factor, rack mounting hardware, cable management hardware, power supplies, fans or cooling systems. Follow server vendor guidelines for these components.

If you use a Cisco UCS bundle SKU, note that the rail kit, cable management and power supply options may not match what is available with non-bundled Cisco UCS.

Redundant power supplies are highly recommended, particularly for UC on UCS.

For Cisco UCS, it is strongly recommended to use the Cisco default rail kit, unless you have different rack types such as telco racks or racks proprietary to another server vendor. Cisco does not sell any other types of rack-mounting hardware; you must purchase such hardware from a third party.

Processors / CPUs

Cisco Collaboration is a set of mission-critical, "Tier 0" applications, where customer expectations for availability, stability and predictable performance are higher than for traditional business applications. Cisco Collaboration apps are real-time and latency-sensitive, with extremely different resource footprints and operational characteristics than traditional business applications. Therefore note the following:

Note:

Explicit qualification of new or existing CPU architectures is required.

Until qualification occurs, new CPU architectures are not allowed or supported, even if they are believed to be "better" than currently supported CPU models.

Some CPU architectures may never be allowed or supported by Cisco Collaboration (e.g. Intel desktop architecture or Xeon 65xx). Within an allowed or supported CPU architecture, some CPU models may never be supported (e.g. due to insufficient physical core speed).

Collaboration application support for new CPU architectures/models may lag the release date from Intel and/or server vendors.

CPU rules for UC on UCS Specs-based and 3rd-party Specs-based (described in second table below). CPU must also be allowed for the specific Cisco Collaboration app (see links for each app on www.cisco.com/go/uc-virtualized).

UC on UCS Tested Reference Configurations have additional restrictions on CPU choice (described in second table below). The TRC and its CPU must also be allowed for the specific Cisco Collaboration app (see links for each app on www.cisco.com/go/uc-virtualized).

Note:

Only certain VM configurations of certain Collaboration apps are allowed to run on a "Restricted UC Performance" CPU. See the application pages on www.cisco.com/go/uc-virtualized.

CPU Architecture & Models

Full UC Performance CPUs

Restricted UC Performance CPUsMay not be supported for your UC app - see links at www.cisco.com/go/uc-virtualized

For purposes of sizing rules and co-residency, virtualized UC apps see equivalent performance from one physical CPU core on any of the above architectures. E.g. UC apps perform eqiuvalently on 1 physical core of 5600 at 2.53+ GHz or 1 physical core of E5-2600 at 2.50+ GHz or 1 physical core of E7-2800 at 2.40+ GHz.

Physical CPU core speed same or higher than that of the TRC BOM's CPU model in Table 1.

E.g. if the TRC BOM was tested with 2-socket Intel Xeon E5-2680 (Romley/SandyBridge-EP, 8-core, 2.7 GHz), then 2-sockets of any 8-core CPU of 2.7 GHz or higher with the E5-26xx/46xx (Intel Xeon Romley/SandyBridge-EP architecture) may be substituted.

Per these policies, recall that physical CPU cores may not be over-subscribed for UC VMs

I.e. one physical CPU core must equal one VM vCPU core.

Hyper-threading on the CPU should be enabled when available, but the resulting Logical Cores do not change UC app rules. UC rules are based on 1:1 mapping of physical cores to vcpu, not Logical Cores to vcpu.

Cisco TAC is not obligated to troubleshoot UC app issues in deployments with insufficient physical processor cores or speed.

Memory / RAM

Note:

Virtualization software licenses such as Cisco UC Virtualization Foundation or VMware vSphere limit the amount of total vRAM that can be used (and therefore the amount of physical RAM that can be used for UC VMs, due to UC sizing rules). See Unified Communications VMware Requirements for these limits. In general larger deployments, or deployments with high VM counts, will require very high vRAM totals and will therefore need to use VMware vSphere instead of Cisco UC Virtualization Foundation.
If using high-memory-capacity servers, use VMware vSphere instead to ensure use of all physical memory.

while following co-residency support policy rules. Per these rules, recall that UC does not support physical memory oversubscription (1 GB of vRAM must equal 1 GB of physical RAM). Cisco TAC is not obligated to troubleshoot UC app issues if the deployment has insufficient physical RAM.

Follow server vendor guidelines for optimum memory population for the memory capacity required by UC.

For Cisco UCS, use the Specs Sheets at UCS Quick Catalog. E.g. for a UCS B200 M3 with 96GB total RAM, optimal is 4x8GB DIMM + 4x4GB DIMM. Using 6x16GB DIMM is not optimal.

Otherwise, there are no UC-specific requirements (primarily because UC does not support memory oversubscription).

UC allows any DIMM speed (e.g. 1333 MHz, 1600 MHz, etc.).

UC allows any memory hardware module size, density and quantity (including changing the DIMM population on a Tested Reference Configuration) as long as UC-required RAM capacity is met, and the server vendor supports the intended memory configuration.

Storage

To be supported for UC, all storage systems - whether TRC or specs-based - must meet the following requirements:

Compatible with the VMware HCL and compatible with the supported server model used

For DAS-only TRCs (including Cisco Business Edition 6000, Thin Provisioning (either from VMware or from storage array) is not supported. Thick provisioning must be used.

For diskless TRCs and any Specs-based server, thin provisioning (either from VMware or from storage array) is allowed with the caveat that disk space must be available to the VM as needed. Running out of disk space due to thin provisioning will crash the application and corrupt the virtual disk (which may also prevent restore from backup on the virtual disk).

UC on UCS TRCs using only DAS storage (such as C220 M3S TRC#1) have been pre-designed and tested to meet the above requirements for any UC with UC co-residency scenario that will fit on the TRC. Detailed capacity planning is not required unless deploying

non-UC/3rd-party apps

VM OVA templates created later than the TRC

VM OVA templates with very large vDisks (300GB+).

Note:

All of the above requirements must be met for Cisco UC to function properly. Except for UC on UCS TRCs using DAS only, it is the customer's responsibility to design a storage system that meets the above requirements. Cisco TAC is not obligated to troubleshoot UC app issues when customer-provided storage is insufficient, overloaded or otherwise not meeting the above requirements.

B-Series TRC may use the disk size/speed listed in Table 1 BOMs, or any other orderable size/speed for the blade server (since local disks are only used to boot VMware).

C-Series TRC Both must be same or higher than specs listed in Table 1. E.g. for a TRC tested with 300 GB 10K rpm disks, then:

300GB 15K rpm is supported (faster)

146GB 10K rpm not supported (too small)

7.2K rpm disk of any size not supported (too slow)

DAS is supported with customer-determined disk size, speed, quantity, technology, form factor and RAID configuration as long as:

compatible with the VMware HCL and compatible with the server model used

all UC latency, performance and capacity requirements are met. To ensure optimum UC app performance, be sure to use Battery Backup cache or SuperCap on RAID controllers for DAS.

TRC BOMs are updated as orderable disk drive options change. E.g. UCS C210 M2 TRC#1 was tested with 146GB 15K rpm disks, but due to 146GB disk EOL, the BOM now specifies 300GB 15K rpm disks (still supported as TRC since both size and speed are "same or higher" than what was tested).

Disk Quantity, Technology, Form Factor

Must exactly match what is listed in Table 1. E.g. if the TRC was tested with ten 2.5" SAS drives, then that must be used regardless of disk size or speed.

No UC requirements on disk size, speed, technology (SAS, SATA, FC disk), form factor or RAID configuration as long as requirements for compatibility, latency, performance and capacity are met. "Tier 1 Storage" is generally recommended for UC deployments. See the UC Virtualization Storage System Design Requirements for an illustration of a best practices storage array configuration for UC.

There is no UC-specific requirement for NFS version. Use what VMware and the server vendor recommend for the vSphere ESXi version required by UC.

Use of storage network and array "features" (such as thin provisioning or EMC Powerpath) is allowed.

Otherwise any shared storage configuration is allowed as long as UC requirements for VMware HCL, server compatibility, latency, capacity and performance are met.

Removable Media

UC on UCS TRC

Specs-based (UCS or 3rd-party Server)

Boot from SD cards, USB flash or other

Not allowed or supported by Cisco for apps or VMware vSphere ESXi. TRCs are only validated as either boot from DAS or diskless boot from FC SAN depending on Table 1.

Note all current TRCs are either diskless blades or C-Series DAS/HDD. SD cards in C-Series TRCs are used for convenience to get the UCS utilities (like SCU and HUU), in lieu of a DVD drive.

Not allowed or supported by Cisco for apps. Must boot from DAS, SAN or NAS per Specs-based Storage requirements.

Allowed for VMware vSphere ESXi as long as supported by server vendor. Cisco Collaboration apps do not test, validate or troubleshoot these boot methods - work with server vendor if boot issues.

Otherwise, there are no UC-specific requirements or restrictions. The different methods of installing UC apps into VMs can leverage the following distribution types of Cisco UC software:

UCS B-Series TRC may use either the adapters listed in Table 1 BOMs or substitute with any other supported adapter for the blade server model. Which adapter "should" be used is dependent on deployment, design and UC apps.

The customer is also responsible for configuring redundant devices on the server (e.g. redundant NIC, HBA, VIA or CNA adapters).

There are no UC restrictions on hardware vendors for I/O Devices other than that VMware HCL and the server vendor/model must be compatible with them and support them.

IO Capacity and Performance

In most cases detailed capacity planning is not required for LAN IO or storage access IO. TRC adapter choices have been made to accommodate the IO of all UC on UCS app co-residency scenarios that will fit on the TRC. For guidance on active vs. standby network ports, see the Cisco UC Design Guide] and QoS Design Considerations for Virtual UC with UCS It is the customer's responsibility to ensure the external LAN and storage access meet UC app design requirements.

LAN access adapters must be able to accommodate the LAN usage of UC VMs (described in UC app design guides).

Storage access adapters must be able to accommodate the storage IOPS (described in the Storage section of this policy).

Cisco TAC is not obligated troubleshoot UC apps issues in a deployment with insufficient or overloaded I/O devices.