! colspan="7" | <center>'''[[UC Virtualization Supported Hardware#UC_on_UCS_Tested_Reference_Configurations|UCS Tested Reference Configurations]]'''<br>S is same as BE6000 MD<br>S+ is same as BE6000&nbsp;HD<br>M includes BE7000<br></center>

*For other third-party software requirements and for a list of approved UCS servers, see the server requirements and version compatibility with Unified CM sections in the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense]. <br>

{{note| Cisco MediaSense has stringent requirements for the media disk size for any deployment. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html Solution Reference Network Design for Cisco MediaSense, Release 8.5(3)] for more information.}}

*[[#IOPS_and_Storage_System_Performance_Requirements|Click for "IOPS"]]

-

Up to 60 terabytes of media storage is supported per cluster, divided into up to six 2TB virtual disks in each of five servers. This assumes that all nodes are B-series servers, for which Cisco MediaSense supports SAN storage. C-series servers, for which only direct attached drives are currently supported, are limited to two 2TB media storage partitions each. Also, no single media partition may be smaller than 200GB.

+

<br>

-

See the following links for more information:

+

|-

+

| 7vCPU Config<br>[[#Notes_on_7_vCPU_VM_configuration|See notes]]

+

| bgcolor="pink" | No

+

| 7<br>

+

| 8 GB<br>

+

| [[#Notes_on_7_vCPU_VM_configuration|See notes]]

+

| 1

+

| align="center" | <br>

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

| bgcolor="lawngreen" align="center" | Yes

+

| bgcolor="pink" align="center" | No

+

| bgcolor="pink" align="center" | No

+

|}

-

*See the [[IO Operations Per Second (IOPS)#Cisco_MediaSense]] section for the IOPS specifications

If your partitions (VM&nbsp;disk configuration) are not aligned, your data replication between the primary and secondary servers may get congested and result in your data being out of sync. To avoid these problems, only use the VM&nbsp;templates provided by Cisco MediaSense.<br>

+

The 2 vCPU VM configuration can be used for a Primary or a Secondary Cisco MediaSense node. <br> Expansion nodes are not supported with this configuration. This configuration is available for deployment on the UCS-E servers. Look for details here [[Cisco MediaSense on UCSE|Cisco_MediaSense_on_UCSE]]

{{caution| If your VM template or VM configuration does not meet the Cisco MediaSense requirements, it is possible for your installation to halt due to an unrecoverable error. See [[Installation: Installation halts with an unrecoverable error]].}}

+

Expansion Nodes are not supported with this virtual machine configuration.

-

<br>

+

=== Supported Capabilities ===

-

{{note| Configure the primary server and secondary server in your Cisco MediaSense deployment to have identical hardware in terms of CPU configuration (number of CPUs and speed of the CPU), storage configuration (number of disks, speed of disk, and RAID setup), and memory. Be sure to keep both servers in the same network and run the same version of VMWare Hypervisor on both servers.}}

The VM-specific sizing informaton required for Cisco MediaSense is additional virtual disks for media storage. See the [http://www.cisco.com/en/US/products/ps11389/products_implementation_design_guides_list.html SRND for Cisco MediaSense] for further information.

+

+ A audio call between two end points equals two Audio-Weight Media Streams. <br> ++ Max recording storage per node on UCS E140S blades is 400GB when using 600GB SED drives, or 700GB when using 900GB 15K RPM drives.

-

= How to Dump Install Logs to the VM Serial Port<br> =

+

<br>

-

See [[How to Dump Install Logs to the Serial Port of the Virtual Machine]].

+

== Notes on 4 vCPU VM configuration ==

-

<br>

+

The 2 vCPU VM configuration can be used for a Primary or a Secondary Cisco MediaSense node. <br> Expansion nodes are not supported with this configuration. This configuration is available for deployment on the UCS-E servers. Look for details here [[Cisco MediaSense on UCSE|Cisco_MediaSense_on_UCSE]]

+ A audio call between two end points equals two Audio-Weight Media Streams. <br> ++ Max recording storage per node on UCS E140S blades is 400GB when using 600GB SED drives, or 700GB when using 900GB 15K RPM drives.

+

+

<br>

+

+

== Notes on 7 vCPU VM configuration ==

+

+

The 7 vCPU VM configuration can be used for a Primary, Secondary or an Expansion Cisco MediaSense node.

Notes on 2 vCPU VM configuration

The 2 vCPU VM configuration can be used for a Primary or a Secondary Cisco MediaSense node. Expansion nodes are not supported with this configuration. This configuration is available for deployment on the UCS-E servers. Look for details here Cisco_MediaSense_on_UCSE

+ A audio call between two end points equals two Audio-Weight Media Streams. ++ Max recording storage per node on UCS E140S blades is 400GB when using 600GB SED drives, or 700GB when using 900GB 15K RPM drives.

Notes on 4 vCPU VM configuration

The 2 vCPU VM configuration can be used for a Primary or a Secondary Cisco MediaSense node. Expansion nodes are not supported with this configuration. This configuration is available for deployment on the UCS-E servers. Look for details here Cisco_MediaSense_on_UCSE

+ A audio call between two end points equals two Audio-Weight Media Streams. ++ Max recording storage per node on UCS E140S blades is 400GB when using 600GB SED drives, or 700GB when using 900GB 15K RPM drives.

Notes on 7 vCPU VM configuration

The 7 vCPU VM configuration can be used for a Primary, Secondary or an Expansion Cisco MediaSense node.