For the latest information on MediaCentral Platform Services, see the documentation available from the
MediaCentral Services page of the Avid Knowledge Base. Updates are occasionally issued after initial
release.
Note: For information on the supported RHEL version see the MediaCentral Platform 2.3 ReadMe.
This document is intended for people who either need to advise on or directly make purchase decisions
for hardware on which MediaCentral Platform Services (MCS) will be installed and configured.
A basic understanding of server components (CPU, RAM, network cards) is required, but this document
does not go into technical depth in this respect.
Note: This document provides HP and Dell part numbers for each item as a reference. Prices are no
longer provided, and may differ, depending on your geography and the customer’s relationship with
HP or Dell. Part numbers may change without notification. Consult with the manufacturer directly
for updated information.
Updates from the 2.2 Installation Guide include:
June 25, 2015
• Clarification on qualified number of video analysis requests in section 15.
• Minor style changes.
Please see the MediaCentral Platform 2.3 ReadMe and any ReadMe documents pertaining to the
solution(s) by which MCS is used.
15 Appendix A: HP DL360p Gen8 Hardware Requirements .......................................................... 38
15.1 Complete List of Supported CPUs ................................................................................................ 40
16 Copyright and Disclaimer ...................................................................................................... 41
3
1
Additional Resources
1.1 Red Hat Enterprise Linux (RHEL)
1.2 Hewlett-Packard (HP) and Dell
1.2.1 HP ProLiant DL360 Gen9
The following section provides useful links for vendors discussed in this guide.
•Red Hat RHEL support options:
https://www.redhat.com/wapps/store/catalog.html
Consult the manufacturer’s web site for the most up-to-date for resources for researching and
configuring the servers supported for MediaCentral Platform Services.
Note: The Dell PowerEdge R620 server is supported but unavailable for purchase at time of
publication. Only part numbers for the Dell R630 are provided.
5
2
Overview
2.1 What is MCS?
2.2 Buying Hardware for MCS
Before getting into the details of buying hardware for MCS, take a moment to understand what
MCS is, and why it is important to make the right hardware purchase decisions.
MCS is a set of software services that serve application layouts for applications, provide user
authentication, manage system configuration settings, and deliver video playback over the
network to web-based and mobile clients used with the following Avid solutions:
• MediaCentral | UX
• Media Composer | Cloud
• Interplay | MAM
• Media | Distribute
MCS consists of:
• MediaCentral Middleware Services
• MediaCentral User Management Services
• MediaCentral Playback Services
• MediaCentral Configuration Service
• MediaCentral Messaging Service
• MediaCentral AAF Generator Service
MediaCentral Platform Services 2.3 Hardware Guide
MCS installs all services on the same server, and multiple servers can be clustered together to
obtain high-availability and horizontal scale.
For the most part, provisioning hardware is straightforward in that it is easy to configure a basic
supported server. However, due to the different and optional video playback methods and
features determining exactly what to provision can be complex. Take the time needed to
determine the number of servers required, and the options with which the servers may need to
be provisioned.
This document aims to facilitate the process of determining how many servers are needed, and
which, if any, options are required.
• MCS supports MediaCentral and Media Composer | Cloud on HP and Dell hardware
only.
• MCS supports Interplay | MAM on HP, Dell and other hardware.
• MCS supports deployments that do not require video playback on HP, Dell and other
hardware. An iNEWS-only deployment with connections to iNEWS but no connection to
Interplay | Production is a non-video deployment.
6
2.3 Server Requirements at a Glance
In all cases, it is recommended that you review hardware purchase assessments with a qualified
Avid representative before purchasing any servers. Reviewing this document is an essential first
step prior to consultation that will accelerate the process.
After reading this document you should be able to:
Clearly identify the solution for which you are buying MCS hardware
Determine the general hardware platform you need to buy
Choose the Red Hat Enterprise Linux (RHEL) support subscription option that best
meets your needs
Determine which, if any, specific network interface cards (NICs) are required
Determine whether or not you require additional hard drives for media caching
Collect data that will allow you to determine how many MCS servers are required
In the case of provisioning hardware from Avid, HP, or Dell, provide valid part numbers
for everything you need to offer
If applicable, explain all hardware purchases to your customer
The number of servers needed depends on a number of factors that can be determined in
advance of hardware procurement:
MediaCentral Platform Services 2.3 Hardware Guide
1. Deployment Type: This type of deployment has a primary influence on server
requirements. An iNEWS only deployment without video playback has the lowest
processing needs. MediaCentral UX and Interplay MAM deployments require more CPU
resources, due to the media transcoding requirements.
2. Media Formats: The next biggest consideration is the media storage format. For
example, DNxHD is a resource-intensive media format. Avid JFIF is lightweight, in
comparison. Thus for the same number of users, fewer servers are needed for a site
where media is stored as Avid JFIF.
3. Frame-based vs File-based Playback: In frame-based playback, MCS decodes the stored
proxies and streams images and audio to the remote client as individual frames. In filebased playback, MCS transcodes to FLV and caches the results. Both MediaCentral UX
and Interplay MAM can be set (by the end-user) for either frame-based or file-based
playback. Frame-based playback is the more CPU-intensive. As above, for the same
number of users, fewer servers will be needed for a site favoring file-based playback.
4. Number of Users: The number of servers deployed must match peak usage
requirements. For example, if a single server can simultaneously transcode 15 streams
of the proxy storage format, but 25 users are expected, two servers will be needed.
The following table summarizes the basic cases for one, two and three or more servers. For a
detailed discussion see “Deploying Multiple Servers” on page 21
.
7
MediaCentral Platform Services 2.3 Hardware Guide
Number
Deployment
Description
1
Single Server
The minimum deployment model, suitable for environments
2
Master + Slave
Adds automatic failover safety to the basic single-server
3+
Master + Slave
Adds increased peak-usage and media transcoding capacity.
of
Servers
Model
+ Load Balancing
with few users and/or undemanding transcoding requirements.
For example, suitable for MediaCentral for iNEWS-only
deployment; that is, to browse and edit iNEWS content with no
connection to Interplay | Production (hence no video
browse/edit/playback).
deployment, plus increased peak-usage and transcoding
capacity.
This is the minimum recommended deployment for most
scenarios.
Deploying multiple servers in a cluster is particularly important
for sites with many users and/or resource-hungry media
formats.
For example, a single server can support the simultaneous
playback of over 100 Avid JFIF media streams, but only 15
streams of AVC Intra 50 to MediaCentral UX.
8
3
Qualified Servers
3.1 HP ProLiant DL360 Gen9
The following servers are qualified for use with MCS 2.3:
HP ProLiant DL360 Gen9
HP ProLiant DL360p Gen8
Dell PowerEdge R630
We currently qualify the HP DL360 Gen9 server. This 1U form factor server provides enough
expansion for NICs and drives to suit all MCS deployments.
DL360 Gen9 - Front
MediaCentral Platform Services 2.3 Hardware Guide
1. Access Panel
2. Serial Label Pull Tab
3. HP Universal Media Bay
4. Power On/Standby button and system power LED button
5. Health LED
6. NIC Status LED
7. USB 3.0 Connector
8. Unit Identification Button & LED
9. SAS/SATA/SSD Drive Bays
9
MediaCentral Platform Services 2.3 Hardware Guide
DL360 Gen9 - Back
1. PCIe 3.0 Slots 1-3
2. HP Flexible Slot Power Supply Bay 2
3. Power Supply 2 Status LED
4. Power Supply 2 C13 Connection
5. HP Flexible Slot Power Supply Bay 1
6. Power Supply 1 Status LED
7. Power Supply 1 C13 Connection
8. Video Connector
9. Embedded 4x1GbE Network Adapter
10. Dedicated iLO 4 connector
11. Serial Port Connector (Optional)
12. USB 3.0 Connectors (2)
13. Unit Identification LED
14. FlexibleLOM bay (Optional)
NOTE: Shown: 4x1Gbe.
10
DL360 Gen9 - Top
MediaCentral Platform Services 2.3 Hardware Guide
1. 5 Standard Fans Ship for 1P and 7 Standard Fans Ship for 2P
NOTE: High Performance Fans also available as an option.
2. 2 Processors with HP Smart Socket Guide
3. HP Smart Storage Battery
4. 24 DDR4 DIMM slots (12 per processor)
5. MicroSD card slot
6. Dual Internal USB 3.0 connector
7. HP Flexible Smart Array or Smart HBA
8. 2 HP Flexible Slot Power supplies
9. Secondary PCIe 3.0 riser for PCIe slot 3 (requires CPU 2)
10. Embedded 4x1Gbe NIC
11. Primary PCIe 3.0 riser for PCIe slots 1 & 2
12. FlexibleLOM Bay
13. Embedded SATA Controller ports
11
3.2 HP ProLiant DL360p Gen8
We currently qualify the HP DL360P Gen8 server; however, this server is no longer available for
purchase in some regions. This 1U form factor server provides enough expansion for NICs and
drives to suit all MCS deployments.
DL360p Gen8 - Overview
MediaCentral Platform Services 2.3 Hardware Guide
1. Hood cover
2. Up to two Intel® E5-2600 Series processors
3. Optical Disk Drive Bay
4. Active Health and Network Status LEDs
5. Video connector (requires Front Video Adapter Kit)
6. Slide-out System Insight Display (SID)
7. Hard Drive Bays
8. Removable hot-plug fan modules for easy serviceability
9. 24 DIMM slots
10. Redundant Hot Plug Power Supplies (upgradeable option)
11. Removable Riser Cage assembly for 2 x PCIe 3.0