MediaCentral ® Platform Services Version 2.2 Installation and Configuration Guide MCS Version: 2.2 Document Version: 1.1.1 Important Information This document provides instructions to install and configure Avid MediaCentral Platform Services (MCS) V2.2 for use with MediaCentral | UX 2.2. For a complete list of qualified products, see the Avid MediaCentral V2.2 ReadMe.
MCS 2.2 Installation and Configuration Guide Date Revised Version Changes Made - Updated “Installing RHEL and the MCS Software” on page 76 to include Gen9 driver installation. Corrected PostgreSQL port number. April 16, 2015 1.1.1 Updated “Setting Up the RAID Level 1 Mirrored System Drives (Gen9)” on page 66. Updated “Setting Up the RAID Level 5 Cache Drives (Gen9)” on page 68. About MCS 2.2 Please see the MediaCentral Platform 2.
MCS 2.2 Installation and Configuration Guide Contents Important Information ....................................................................................................................... 1 Revision History .................................................................................................................................. 1 PART I: INTRODUCTION & OVERVIEW ........................................................................................................... 11 Welcome ............
MCS 2.2 Installation and Configuration Guide The Dedicated Caching Volume ........................................................................................................... 29 Caching for Interplay | MAM ............................................................................................................... 30 Caching for iOS Devices in MediaCentral ............................................................................................. 30 Caching for MediaCentral | Cloud..............
MCS 2.2 Installation and Configuration Guide Obtaining Gluster ................................................................................................................................. 53 Obtaining Additional Packages ............................................................................................................. 53 Preparing the MCS Installation USB Key ..................................................................................................
MCS 2.2 Installation and Configuration Guide Synching the System Clock....................................................................................................................... 94 Creating the File Cache on the RAID ........................................................................................................ 96 Partitioning the RAID ............................................................................................................................
MCS 2.2 Installation and Configuration Guide Joining the Cluster.................................................................................................................................. 139 Replicating the Cluster File Caches using Gluster .................................................................................. 140 Gluster Workflow ............................................................................................................................... 140 Before You Begin .........
MCS 2.2 Installation and Configuration Guide Failed to Resolve Zone URL ............................................................................................................ 173 Errors in Zone Configuration .......................................................................................................... 173 Errors During Setup ........................................................................................................................ 174 Dismantling a Multi-Zone Environment ....
MCS 2.2 Installation and Configuration Guide Backing up and Restoring the MCS Database ........................................................................................ 208 Reconfiguring the ISIS Connection(s) ..................................................................................................... 209 Appendix A: Installing MCS on Non-HP Hardware ................................................................................. 211 Non-HP Installation Notes ..............................
MCS 2.2 Installation and Configuration Guide iNEWS Configuration for iPad and iPhone Integration ...................................................................... 239 Editing SYSTEM.CLIENT.VERSIONS ..................................................................................................... 240 Adding iPad and iPhone Devices to the iNEWS Configuration File .................................................... 241 Installing Avid Central on the iPad or iPhone ....................................
MCS 2.
MCS 2.2 Installation and Configuration Guide Welcome Welcome to the MCS Installation and Configuration Guide. This document will guide you through the installation and set up of the MediaCentral Services (MCS) software components. It provides step by step instructions to visually verify the hardware setup, install Linux and the MCS software, and configure the software systems that will make use of MCS.
MCS 2.2 Installation and Configuration Guide Note: Clock setting and synchronization play an important role in some MCS deployments. For a discussion of the issues associated with clock synchronization and using a time server to set the system clock, see “Clock Synchronization in Linux” on page 37. About this Guide This guide provides all the instructions you need to set up MCS 2.2. The installation and configuration is complex and can be difficult, particularly if you are unfamiliar with Linux.
MCS 2.2 Installation and Configuration Guide Delivery of Licenses on Back-End Systems An iNEWS client license or an MediaCentral mobile license for a specified number of clients is sent to the customer through email along with specific installation instructions. However, to ensure proper licensed integration between MediaCentral and iNEWS, additional modification to system files in the iNEWS database is also required.
MCS 2.2 Installation and Configuration Guide • Linux (general): Work with Linux directories (cd, mkdir, ls), create volumes, mount/unmount directories, volumes and devices (e.g. USB key), verify the status of a Linux service. • Linux (file editing): Use the Linux text editor (vi) to open/create files, add/delete text, save/close files, etc. • Networking: An understanding of network topologies and Ethernet protocols (TCP/IP), using ping command, verify/change a NIC card Ethernet interface (i.e. eth0).
MCS 2.2 Installation and Configuration Guide access to your station’s iNEWS system. The iPad and iPhone apps additionally provide access to your Interplay | Production databases. For iOS installation information, see “Appendix I: Installing and Configuring the Avid MediaCentral | UX Mobile Application for iPad or iPhone” on page 239. For Android installation information, see the “MediaCentral | UX User’s Guide”, or the Android app help. The Android app can be downloaded here: https://play.google.
MCS 2.2 Installation and Configuration Guide MCS Connectivity Before examining specific deployment options it can be helpful to have an understanding of where MCS sits in terms of connectivity to other Avid components.
MCS 2.2 Installation and Configuration Guide Multi-Zone By default, MCS operates within a single environment such as a particular facility, or department within a facility. A single facility may in fact house numerous MCS systems, each of which, by default, operates independently. In a multi-zone configuration, two or more single-zone systems are joined together. These can even be separated geographically — for example, one server or cluster could be located in Toronto and another in Munich.
MCS 2.2 Installation and Configuration Guide • Interplay Media Services Automation • Interplay Consolidate • Interplay Delivery • Production Engine Bus Connector (PEBCo) For more information, see the Avid Media | Index Configuration Guide. Deployment Options MCS is a collection of software services designed to support a number of Avid enterprise solutions and deployment options.
MCS 2.2 Installation and Configuration Guide MediaCentral – iNEWS Only One of the most straightforward deployments is MCS for MediaCentral in an iNEWS-only environment; that is, with connections to iNEWS but no connection to Interplay | Production. In this deployment MCS provides the ability to browse and edit iNEWS content (queues, stories) from a remote web client. The ability to browse, play and edit associated video requires Interplay | Production and is not provided by the iNEWS-only deployment.
MCS 2.2 Installation and Configuration Guide MediaCentral – Interplay | Production Only MCS for MediaCentral with Interplay | Production has connections to Interplay | Production only. In this deployment MCS serves layouts for applications, provides user authentication, manages system configuration settings, and provides proxy-based playback of video assets over the network to web-based and mobile clients.
MCS 2.2 Installation and Configuration Guide MediaCentral – iNEWS and Interplay | Production MCS for MediaCentral with iNEWS and Interplay | Production has both iNEWS connectivity and Interplay | Production connectivity. Similarly to the iNEWS-only deployment, this provides the ability to browse and edit iNEWS content (queues, stories) from a remote web client. Interplay | Production connectivity provides the ability to browse, play and edit associated video.
MCS 2.2 Installation and Configuration Guide Media Composer | Cloud Only MCS for Media Composer | Cloud provides playback of different format video assets registered by Interplay | Production and residing on an ISIS. MCS decodes the source format and streams images and sound to the remote Media Composer | Cloud enabled Media Composer or NewsCutter. This deployment typically requires two HDs configured as a RAID 1 (mirrored RAID) for the Linux operating system. A media cache is also required.
MCS 2.2 Installation and Configuration Guide Both MediaCentral and Media Composer | Cloud (Shared MCS) MediaCentral and Media Composer | Cloud can easily share the same MCS server(s). In this deployment, MCS serves layouts for applications, provides user authentication, and manages system configuration settings. MCS also provides proxy-base playback over the network of different format video assets registered by Interplay | Production and residing on an ISIS.
MCS 2.2 Installation and Configuration Guide o • Single HD Clustering yields high-availability and load-balancing Interplay | MAM In an Interplay | MAM deployment, MCS provides playback of video assets registered as a browse proxies by Interplay | MAM. The registered browse proxies can reside on standard filesystem storage, or proprietary storage that provides a standard system gateway.
MCS 2.2 Installation and Configuration Guide Port Bonding in Interplay | MAM Port bonding (also called link aggregation) is an OS-level technique for combining multiple Ethernet ports into a group, making them appear and behave as a single port. Ethernet ports correspond to the physical connectors in a NIC card where network cables are plugged in. Bonded ports retain their individual cable connections to the network router or switch. However, they are seen by the network as a single port.
MCS 2.2 Installation and Configuration Guide The following table lists the server-side port requirements. For more information see the MCS Security Architecture and Analysis document.
MCS 2.2 Installation and Configuration Guide However, outside the corporate firewall (not shown) the private-range IP address (e.g. 192.XXX.XXX.XXX.XXX) supplied by the load-balancing algorithm is not accessible. Thus, if the MediaCentral client is to connect from outside the corporate firewall, the FQDN must also be resolvable from outside the firewall. For VPN connections this is a non-issue. In the NAT deployment model, NAT must be configured to resolve the FQDN.
MCS 2.2 Installation and Configuration Guide Note: This document provides instructions for creating a media cache volume as a RAID 5 using multiple disks in the server enclosure. However, other configurations are possible, including two drives in a RAID 1 configuration, or a single drive. For details, see the “MediaCentral Platform Services Hardware Guide”. The Dedicated Caching Volume All MCS servers require a RAID 1 that mirrors the operating system across two HD drives.
MCS 2.2 Installation and Configuration Guide Caching for Interplay | MAM For caching, it is important to understand how MAM browse proxies get from proxy storage to the MAM desktop. For each playback request, MCS does one of the following: • File-based playback (native): When MAM proxies are in a format that an Adobe Flashbased player can play natively, MCS serves the proxy file as-is to the remote web-based client. Adobe Flash-based players natively play MP4-wrapped h.264/aac or FLV.
MCS 2.2 Installation and Configuration Guide Note: RHEL is not free, and Avid does not redistribute it or include it as part of the MCS installation. RHEL licensing and support options are covered in the “MediaCentral Platform Services Hardware Guide”. Installing Linux Installations on qualified HP servers can use an express process involving a USB key and the Avid-supplied kickstart (ks.cfg) file. Kickstart files are commonly used in Linux installs to automate the OS installation.
MCS 2.2 Installation and Configuration Guide Directory Description /etc Contains Linux system configuration files, including the filesystem table, fstab, which tells the operating system what volumes to mount at mount at boot-time. /etc/udev/rules.d Contains rules used by the Linux device manager, including network script files where persistent names are assigned to network interfaces. In Linux, every network interface has a unique name.
MCS 2.2 Installation and Configuration Guide The following table presents a few of the more commonly used Linux commands. Command Description ls Lists directory contents. Use the –l option (hyphen lower-case L) for a detailed listing. cd Changes directories. cat Outputs the contents of the named file to the screen. clear Clears screen. cp Copies files and directories. Auto-completes the command based on contents of the command line and directory contents.
MCS 2.2 Installation and Configuration Guide Command Description scp Securely copies files between machines (across an ssh connection). service Runs an initialization script. e.g. service avid-all Shows you the last 10 (or n) lines in a file. tail e.g. tail tail -50 tail –f The “-f” option keeps the tail command outputting appended data as the file grows. Useful for monitoring log files. udevadm Requests device events from the Linux kernel.
MCS 2.2 Installation and Configuration Guide Key Press Description I a A Insert text at beginning of current line Insert text after the cursor Insert text at end of current line w b Shift-g D x dd yy p Turn off Insert mode and switch to command mode. Next word Previous word Move cursor to last line of the file Delete remainder of line Delete character under the cursor Delete current line “Yank” (copy) a whole line in command mode. Paste the yanked line in command mode.
MCS 2.2 Installation and Configuration Guide Linux Usage Tips The following table presents tips that will make it easier to work in RHEL. Tip Description Getting Help For help with Linux commands, the Linux System Manual (“man” pages) are easily available by typing the man command followed by the item of interest.
MCS 2.2 Installation and Configuration Guide Volumes in Linux For those more familiar with Windows, the steps to creating usable volume in Linux are similar to preparing a new HD for use in Windows. In Windows, you initialize the disk, create a partition, and assign it a drive letter. You must then format the disk, specify its file system, its allocation unit size, and assign it a volume label. In Linux, you must also initialize the disk (this takes place during RHEL installation) and create a partition.
MCS 2.2 Installation and Configuration Guide RAIDs in MCS RAID stands for redundant array of inexpensive (or independent) disks. RAIDs are used in MCS to provide data redundancy and for efficiency in caching large amounts of data across multiple disks. On supported HP servers, you implement these RAIDs at the level of the HP disk controller, using the HP RAID configuration BIOS utility.
MCS 2.2 Installation and Configuration Guide Introduction to Clustering Redundancy and scale for MCS is obtained by setting up a cluster of two or more servers. Within the cluster, requests for media are automatically distributed to the available servers. An MCS server cluster provides the following: • Redundancy/High-availability. If any node in the cluster fails, connections to that node will automatically be redirected to another node. • Scale/Load balancing.
MCS 2.2 Installation and Configuration Guide Cluster Deployment In a cluster deployment, there is one master-slave pair of nodes (providing high-availability and failover), and additional nodes supporting transcoding (for scale and load-balancing). In a cluster, all MCS traffic is routed to the master node. Player requests, handled by the MCPS playback service, are distributed by the master to all available nodes.
MCS 2.2 Installation and Configuration Guide Working with Gluster Recall that the MCS server transcodes media from the format in which it is stored on the ISIS (or standard filesystem storage) into an alternate delivery format, such as an FLV or MPEG-2 Transport Stream. In a deployment with a single MCS server, the MCS server maintains a cache where it keeps recently-transcoded media.
MCS 2.
MCS 2.2 Installation and Configuration Guide Installation Workflow The following table describes each of the main installation steps. If you are setting up a server cluster, be sure to read “Clustering Workflow” on page 129 too. Step Task Time Est. 1 Appendix J: Installation Pre-Flight Checklist 1–2 hr varies Make sure you have all the information related to the server hardware (including disk drives and NIC cards in the enclosure), network topography, IP addresses, etc.
MCS 2.2 Installation and Configuration Guide Step Task Time Est. 9 Installing RHEL and the MCS Software 20 min In this step you install RHEL and MCS on the RAID 1 disk array. 10 Booting RHEL for the First Time 10 min Like most operating systems, the first time you boot RHEL you need to set some system information. It is minimal, in the case of RHEL.
MCS 2.2 Installation and Configuration Guide Step Task Time Est. 18 Replicating the Cluster File Caches 30 min If you are creating a cluster of MCS nodes, we recommend that you replicate (mirror) the RAID 5 file cache volume across each server in the cluster. Note: This step is required only if your Interplay | MAM deployment requires a file cache, or you are deploying iOS devices in MediaCentral.
MCS 2.2 Installation and Configuration Guide Before You Begin Make sure you have everything in place to ensure an efficient and successful installation. Do not proceed with the installation if something is missing. Security Updates Important: Red Hat has issued security advisories for RHEL 6.5. Once you have installed the operating system, please take a moment to resolve the security vulnerabilities. For instructions, see the “Security Updates” section in the MediaCentral Platform 2.2 ReadMe.
MCS 2.2 Installation and Configuration Guide If you are missing software, please see “Obtaining the Software” on page 50. Note: It is particularly important that the server(s) on which you are installing the MCS software should be physically installed in the engineering environment, and the appropriate ISIS and/or the house network connection(s) should be known to you.
MCS 2.2 Installation and Configuration Guide ¨ Do I need a RAID 1? Yes. Yes. All MCS servers require a RAID 1 that mirrors the operating system across two HD drives. ¨ Do I need a dedicated media cache volume (e.g. RAID 5)? Yes or No. Almost all MediaCentral deployments require a dedicated media cache volume, for the multicam caching requirements. This includes MediaCentral | Cloud deployments. The single exception is the iNEWS-only deployment.
MCS 2.2 Installation and Configuration Guide An MCS server or cluster can serve MediaCentral and Media Composer | Cloud simultaneously. In this case, simply install an MCS server or MCS server cluster as indicated in this document. ¨ A Multicast or Unicast Network? (Clustering only) MCS clusters support both unicast and multicast network communication. This body of this guide provides instructions for configuring a cluster in a multicast environment. However, multicast requires multicast enabled routers.
MCS 2.2 Installation and Configuration Guide • MediaCentral: Change the Administrator default password the first time you log in to the MediaCentral | UX (the MediaCentral UI). Before you begin obtain the new passwords from the customer where the system is being installed. Obtaining the Software Note: For version information see the MediaCentral Platform 2.2 ReadMe.
MCS 2.2 Installation and Configuration Guide For the precise installation package name, see the MediaCentral Platform 2.2 ReadMe. Note: If the MCS installation package is not available via the DLC, please contact your Avid representative to obtain it. The ZIP file contains the following: Item Description MediaCentral_Services __Linux.tar.gz The MCS Server Installation package. This compressed tar file contains numerous files, including the following useful shell script: ics_version.
MCS 2.2 Installation and Configuration Guide Item Description system-backup.sh Prepares for an upgrade by backing up important data, including system settings, network settings, the Jetty keystore and application.properties file, and the UMS database. Obtaining Red Hat Enterprise Linux Log in to your Red Hat Network account and download the DVD image (.iso) file or purchase a DVD. Either format can be used for the MCS installation. Note: At the time of this document’s publication, the RHEL 6.
MCS 2.2 Installation and Configuration Guide 4. Log in to your Red Hat Network account. 5. On the Download Red Hat Enterprise Linux page, locate the driver update disk (.iso): dd-hpsa-18216-x86_64.iso 6. Click the Download Now button and save the ISO file to your computer. You will use this driver update disk ISO file later when you create the MCS Installation USB key. Obtaining Gluster Navigate to the download directory at gluster.org containing the GlusterFS version supported by MCS: http://download.
MCS 2.2 Installation and Configuration Guide • Interplay Transcode Provider: The Interplay Transcode Provider installer is supplied as part of the Interplay | Production installer package. • Interplay Transcode Provider patch: The Transcode patch is found in the list of Avid Interplay patches: http://esd.avid.com/ProductInformation.aspx?id=76. As noted, the above software is required for MediaCentral deployments only (excluding iNEWSonly MediaCentral deployments).
MCS 2.2 Installation and Configuration Guide Preparing the HP ProLiant Gen9 Server Installation USB Key Due to licensing restrictions, Avid is not able to redistribute the RHEL installation media. You must download the RHEL installation image (.iso) file from Red Hat directly—or get it from the RHEL Installation DVD that came with your MCS server. Follow this procedure only if you are installing MCS software components on a supported HP Gen9 server. Note: Make sure the RHEL image (.
MCS 2.2 Installation and Configuration Guide 6. Choose the Diskimage radio button then browse to the RHEL image (.iso) file (named rhel-server-6.5-x86_64-dvd.iso or similar). 7. Verify the Hard Disk Name and USB Device Name are correct for your deployment.
MCS 2.2 Installation and Configuration Guide The process takes 10-20 minutes. Once complete, the USB key has everything it needs for a complete RHEL and MCS installation. Note: Copying the RHEL image (.iso) file to the USB key is a one-time process. To install MCS to more than one server, or to re-install MCS, you do not need to repeat these steps. To edit the kickstart file: 1. With the Installation USB key still plugged in to the Windows laptop or desktop, open the kickstart (ks.cfg) file for editing.
MCS 2.2 Installation and Configuration Guide Otherwise, proceed to “Installing the Network Interface Cards” on page 60. Preparing the HP ProLiant Gen8 (or Other ) Server Installation USB Key Follow this procedure only if you are installing MCS software components on a supported HP Gen8 server. Due to licensing restrictions, Avid is not able to redistribute the RHEL installation media. You must download the RHEL installation image (.
MCS 2.2 Installation and Configuration Guide Note: These values have changed since RHEL 6.0, where the hard disk name was sda and the USB device name was sdb. 12. In the “Additional Files” field browse to the MediaCentral_Services__Linux folder on the desktop (or wherever you expanded it to) and then select the directory name. 13. Click OK in the main dialog. 14. A process begins to copy the RHEL image (.iso) file and the MCS installation files to the USB key. The process takes 10-20 minutes.
MCS 2.2 Installation and Configuration Guide ¨ glusterfs‐geo‐replication‐3.4.0‐8.el6.x86_64.rpm ¨ glusterfs‐libs‐3.4.0‐8.el6.x86_64.rpm ¨ glusterfs‐server‐3.4.0‐8.el6.x86_64.rpm ¨ A Windows XP/Vista/7 laptop or desktop computer It is recommended that you copy the files to the MCS installation USB key. (Advanced Linux users may wish to create a network share to install these components instead.) To add GlusterFS to the MCS Installation USB key: 1.
MCS 2.2 Installation and Configuration Guide Connecting to ISIS Proxy Storage The HP DL360 G8 has a full height PCI slot in the upper left corner. Use this slot for either the Myricom 10GigE or the HP NC365T 4-port GigE NIC. The “built-in” Ethernet ports can also be used, if the server is provisioned with the HP 366FLR 4-port GigE NIC.
MCS 2.2 Installation and Configuration Guide Connecting to non-ISIS Proxy Storage Interplay | MAM deployments where browse proxies reside on non-ISIS storage do not require additional NIC cards. They make use of the Ethernet ports built in to the HP server. Visually verify that one of the built-in ports is connected to the network. For a 10GigE connection to non-ISIS storage, use a 10GigE NIC of your choosing.
MCS 2.2 Installation and Configuration Guide HP servers are frequently shipped with BIOS settings set to Power-Saving mode. MCS is makes intensive use of the server’s CPUs and memory, especially when under heavy load. You will get much better performance by ensuring that the server is set to operate at Maximum Performance. Note: While setting the system clock and power saving mode can be done after the installation process, we recommend making the change immediately.
MCS 2.2 Installation and Configuration Guide 4. Press Enter to select “BIOS/Platform Configuration (RBSU)”. 5. Arrow down and select “Boot Options”, press the Enter key. 6. Press Enter to select “Boot Mode”, press the Enter key. 7. Arrow down and select “Legacy BIOS Mode”, press the Enter key.
MCS 2.2 Installation and Configuration Guide 8. Press ESC to go back to BIOS/Platform Configuration (RBSU)”. 9. Arrow down and select “Power Management”. 10. Press Enter to select “HP Power Profile”. 11. Arrow down and select “Maximum Performance”, press the Enter key. 12. Press ESC to go back to BIOS/Platform Configuration (RBSU)”. 13. Arrow down and select “Date and Time”, press Enter key. 14. Set the date (mm-dd-yyyy) and time (hh:mm:ss).
MCS 2.2 Installation and Configuration Guide 15. Press ESC to go back to “BIOS/Platform Configuration (RBSU)”. 16. Press F10 to save . 17. Press ESC to go back to “System Configuration”. If prompted, select “Y” to save changes and exit. 18. Press ESC to go back to “System Configuration”. 19. Press ESC to go back to “System Utilities”. 20. Arrow down and select “Reboot the System”. The server reboots with new options. Proceed to “Setting Up the RAID Level 1 Mirrored System Drives (Gen9)” on page 66.
MCS 2.2 Installation and Configuration Guide 3. Select “HP Smart Storage Administrator” 4. Select “Smart Array P840” from left side menu. 5. Select “Create Array” under “Actions”. 6. Select both 500 GB Drives then select “Create Array”. 7. Verify “RAID 1”, 256 KiB / 256 KiB Stripe Size, 32 Sectors, Maximum Size, Caching Enabled, then select “Create Logical Drive”.
MCS 2.2 Installation and Configuration Guide 8. Press the “Finish” button to complete. Proceed to “Setting Up the RAID Level 1 Mirrored System Drives (Gen9)” on page 66. Setting Up the RAID Level 5 Cache Drives (Gen9) In this step you configure the remaining HD drives in the server enclosure as a RAID Level 5. In a RAID 5 data is automatically distributed across all the disks in the RAID for increased performance and redundancy.
MCS 2.2 Installation and Configuration Guide 3. Verify “RAID 5”, 256 KiB / 1.7 MiB Stripe Size, 32 Sectors, Maximum Size, Caching Enabled, and then select “Create Logical Drive”. 4. Press “Finish” button to complete. 5. Press “X” (top right) to exit. Confirm the exit by clicking “OK” when prompted. 6. Press “Power” button (top right) to exit. Select “Reboot” when prompted.
MCS 2.2 Installation and Configuration Guide Proceed to “Installing RHEL and the MCS Software” on page 76. Changing BIOS Settings and Creating RAIDs on the HP ProLiant Gen8 This section presents the BIOS procedures you must perform when installing MCS on an HP Proliant Gen8 server. Setting the System Clock and Disabling HP Power Saving Mode (Gen8) To ensure the smooth installation of RHEL and MCS, the system clock must be set.
MCS 2.2 Installation and Configuration Guide The ROM-Based Setup Utility appears after a few moments. 3. Choose Date and Time and press Enter. Date and Time options appear. Set the date (mm-dd-yyyy) and time (hh:mm:ss). 4. Press Enter to save the changes and return to the Setup Utility menu. 5. Choose Power Management Options. Power Management options appear. 6. Choose HP Power Profile. Power Profile options appear. 7. Choose Maximum Performance. You are returned to the HP Power Management options menu.
MCS 2.2 Installation and Configuration Guide Setting Up the RAID Level 1 Mirrored System Drives (Gen8) In this step you configure two of the HD drives in the server enclosure as a RAID Level 1 – a mirrored RAID – where the RHEL and MCS software will be installed. This is done using the Option ROM Configuration for Arrays utility, in the HP server’s BIOS. Note: If the list of available disks does not appear as expected, it may be that a RAID has already been created.
MCS 2.2 Installation and Configuration Guide Note: The prompt to press F8 can flash by quite quickly. If you miss it, reboot and try again. 11. From the Main Menu, select Create Logical Drive. 12. Select the following two HD drives in Available Physical Drives: • Box 1 Bay 1 • Box 1 Bay 2 13. Deselect all the other available HD drives (if any). 14. Ensure RAID 1 is selected in RAID Configurations.
MCS 2.2 Installation and Configuration Guide Note: In older firmware versions, the choice presented may be RAID 1+0. Since you are only using two HD drives, this is identical to a RAID 1. 15. Ensure Disable (4GB maximum) is selected in Maximum Boot partition: 16. Ensure nothing is selected in Parity Group Count. 17. Ensure nothing is selected in Spare. 18. Press Enter to create the logical drive. A message appears summarizing the RAID 1 setup. 19. Press F8 to save the configuration.
MCS 2.2 Installation and Configuration Guide 2. As soon as you see the prompt to enter the Option ROM Configuration for Arrays utility, press F8. Note: The prompt to press F8 can flash by very quickly. If you miss it, reboot and try again. 3. From the Main Menu, select Create Logical Drive. 4. Ensure the HD drives to be included in the RAID 5 are selected in Available Physical Drives: • Box 2 Bays 3-8 (typical configuration) 5. Ensure RAID 5 is selected in RAID Configurations. 6.
MCS 2.2 Installation and Configuration Guide 9. Press Enter to create the logical drive. A message appears summarizing the RAID 5 setup. 10. Press F8 to save the configuration. A message appears confirming the configuration has been saved. 11. Press Enter to finalize the RAID 5. Note: Do not press the Escape key to exit, since this reboots the server. Proceed to “Installing RHEL and the MCS Software” on page 76.
MCS 2.2 Installation and Configuration Guide overwrites this file. To preserve your changes, back up the file before beginning the upgrade, and restore it after. Note: For workflow details on upgrading to MCS 2.2 from an earlier release, see the MCS 2.2 Upgrading Guide, available from the Avid Knowledge Base MCS 2.2 web page. To boot the server from the USB key and run the installer: 1. Before rebooting the server ensure the USB key is inserted.
MCS 2.2 Installation and Configuration Guide linux dd c. In the dialog that appears, confirm that you have a driver disk. d. The installer may prompt you to specify the location of the update. Select the device name indicating the MCS Installation USB key (e.g sdc). Similarly specify the partition on the device (e.g. sdc1). e. Select the driver and select OK: z_dd-hpsa-18216-x86_64.iso f. When prompted for more drivers, select No.
MCS 2.2 Installation and Configuration Guide 6. The RHEL installation proceeds. When you see the “Post-Installation” message, it indicates the MCS installation scripts are being executed. 7. When the installation process is complete, you are prompted to reboot. DO NOT REBOOT before removing the USB key.
MCS 2.2 Installation and Configuration Guide If you reboot without removing the USB key the server will reboot from the USB key again and re-launch the installer. Note: If you pressed Enter by mistake, remove the USB key as quickly as possible (before the system boots up again). If this is not possible, you need to perform the installation again. Proceed to “Booting RHEL for the First Time” on page 80.
MCS 2.2 Installation and Configuration Guide Booting from the System Drive When installing RHEL and MCS you booted from the MCS Installation USB key. This time you boot from the system drive where the OS and software were installed. To boot the server from the system drive for the first time: Note: If the USB key is still in the server, remove it. 1. Press Enter in the post-installation dialog. Rebooting the server triggers a first-time boot up from the system drive. The RHEL Configuration screen appears.
MCS 2.2 Installation and Configuration Guide 3. Choose the Language option for your keyboard. 4. Focus the OK button. Press Enter. 5. From the Choose a Tool menu, select Quit. Press Enter. 6. Log in a the Linux prompt Default user name: root default password: _ Note: Please contact your Avid representative for the default root password. You can re-enter the first boot set-up menus at any time by typing “setup” (without quotes) at the Linux command prompt. Proceed to “Security Updates” below.
MCS 2.2 Installation and Configuration Guide Note: Please contact your Avid representative for the default root password. 2. To check the date type date and press enter. The date is displayed. 3. If the date is incorrect, change it. For example, for September 2nd, 2012, at 11:03 a.m. enter: date 090211032012 The required format is MMDDHHmmYYYY. (Month-Date-Hour-Minute-Year) 4. When you press enter the reset date is displayed: Sun Sep 2 11:03:00 EDT 2012 Proceed to “Setting the Time Zone” below.
MCS 2.2 Installation and Configuration Guide 6. Locate the ZONE information, and replace “America/New_York” with the appropriate information, for example: ZONE="America/Los_Angeles" Navigate using the arrow keys, then press A (append) and replace the information. 7. Save and exit the clock file by typing the following command from within the vi editing session: :wq 8. That is, tap the Escape key, then the colon, then type wq and press Return.
MCS 2.2 Installation and Configuration Guide ¨ Whether you are setting up a cluster of MCS server nodes ¨ Facility network settings (static IP address, netmask, default gateway IP, etc., as applicable) ¨ Server name Note: You collected the above information in “Appendix J: Installation Pre-Flight Checklist” on page 244. Identifying NIC Interfaces by Sight RHEL provides a simple means for visually identifying the NIC ports on a server, whether they are active or not.
MCS 2.2 Installation and Configuration Guide 3. From the Network Configuration menu, select Device Configuration. Press Enter. A list of NIC cards contained in the server enclosure appears. 4. Use the arrow keys to locate the NIC card used to connect to the network. Press Enter to view its details. 5. Note the name assigned to the NIC card interface of interest (e.g.
MCS 2.2 Installation and Configuration Guide 6. Perform the action required at each menu (Quit, Exit, etc.) to return to the Linux prompt. If the selected NIC card interface is named eth0 proceed to “Ensuring the NIC Interface Comes Up at System Startup” on page 89. If the selected NIC card’s interface is not named eth0, proceed to “Swapping NIC Interface Names” below.
MCS 2.2 Installation and Configuration Guide 9. Save and exit the 70-persistent-net.rules file by typing the following command from within the vi editing session: :wq That is, tap the Escape key, then the colon, then type wq and press Return. You are returned to the Linux prompt. Proceed to “Removing the MAC Address Hardware References” below.
MCS 2.2 Installation and Configuration Guide 5. Position the cursor on the HWADDR line and press “dd” to remove it. That is tap the lower case letter D twice. 6. Save and exit the file by typing the following command from within the vi editing session: :wq That is, tap the Escape key, then the colon, then type wq and press Return. You are returned to the Linux prompt. 7. Repeat the above steps for the other NIC interface you renamed (e.g. ethX). 8.
MCS 2.2 Installation and Configuration Guide :wq That is, tap the Escape key, then the colon, then type wq and press Return. You are returned to the Linux prompt. Proceed to “Configuring the Hostname and Static Network Route” below. Configuring the Hostname and Static Network Route Now that the NIC interface you will use to connect the MCS server to the network has been named eth0, you are ready to configure the server to make the connection. This is done using the RHEL configuration facility.
MCS 2.2 Installation and Configuration Guide A list of NIC cards contained in the server enclosure appears. 4. Use the arrow keys to locate the NIC card and interface named eth0. Press Enter to view its details 5. Ensure the following information is correctly set: ¨ Default name: eth0 ¨ Default device: eth0 ¨ DHCP is disabled (Spacebar to disable) 6.
MCS 2.2 Installation and Configuration Guide Note: The host name indicated above is the host name only (e.g. ics-dl360-1),that is, the name of the machine. Do not use the fully qualified domain name (e.g. ics-dl3601.mydomain.com or ics-dl360-1.mydomain.local). 11. Select Save & Quit. Press Enter. 12. Select Quit. Press Enter. You may be prompted to login to the server. 13. Verify the DNS Server information has been stored in the RHEL resolver configuration (resolv.conf) file: cat /etc/resolv.
MCS 2.2 Installation and Configuration Guide Note: You can edit the file /etc/hosts while the system is up and running without disrupting user activity. To verify the hosts file: 1. Open the active hosts (/etc/hosts) file for editing. vi /etc/hosts It should look similar to the following: 127.0.0.1 ::1 localhost localhost.localdomain localhost4 localhost4.localdomain4 localhost localhost.localdomain localhost6 localhost6.localdomain6 The entries shown above map the default localhost IP address (127.0.0.
MCS 2.2 Installation and Configuration Guide Verifying Network and DNS Connectivity Before continuing, take a moment to verify that network connectivity is now established. To verify network connectivity: On any other network connected machine, use the Linux ping command to reach the host in question: ping –c 4 For example: ping –c 4 ics-dl360-1 The system responds by outputting its efforts to reach the specified host, and the results.
MCS 2.2 Installation and Configuration Guide ntpdate -q 2. Edit the NTP configuration (ntp.conf) file using a text editor (such as vi): vi /etc/ntp.conf 3. Add a line for the NTP server. For example, if the address of the NTP server is ntp.myhost.com, add the following line: server ntp.myhost.com You can supply the IP address instead (e.g. 192.XXX.XXX.XXX) 4. Comment out any out-of-house servers that may already be present, for security. For example: # server 0.rhel.pool.ntp.
MCS 2.2 Installation and Configuration Guide ntpd: time set +9.677029s The NTP daemon sets the time when there are large changes, and slews (slowly adjusts) the time for small changes (significantly less than a second). There may be no output for a slew. 10. Verify the system time and date: date The system responds with a message similar to the following: Wed Jul 23 12:41:54 EDT 2014 Proceed to “Creating the File Cache on the RAID” below.
MCS 2.2 Installation and Configuration Guide parted /dev/sdb p free Information similar to the following is displayed: Model: HP LOGICAL VOLUME (scsi) Disk /dev/sdb: 2500GB Sector size (logical/physical): 512B/512B Partition Table: gpt Number Start 17.4kB End 2500GB Size 2500GB File system Free Space Name Flags 3.
MCS 2.2 Installation and Configuration Guide Note the name of the physical volume (/dev/sdb1) takes a 1 (one). LVM feedback indicates the successful creation of the physical volume. 2. Create a volume group, vg_ics_cache, containing the physical volume /dev/sdb1: vgcreate -s 256k -M 2 vg_ics_cache /dev/sdb1 LVM feedback indicates the successful creation of the volume group. 3.
MCS 2.2 Installation and Configuration Guide LVM feedback indicates the successful creation of the logical volume. Note that Linux may override the sector size you specified. That is OK. 5. Create a filesystem on the logical volume (i.e. format it): mkfs.ext4 /dev/vg_ics_cache/lv_ics_cache Note in the above command you specify logical volume by its Linux block device name (/dev//). As in other operating systems, formatting in RHEL is a slow operation. Please be patient.
MCS 2.2 Installation and Configuration Guide 7. Verify that /cache has been mounted correctly: df –h The following information is displayed about the cache: size, used, available, user % and mount point (mounted on), similar to the following: Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_ics_cache-lv_ics_cache 29G 585M 27G 3% /cache 8.
MCS 2.2 Installation and Configuration Guide Proceed to one of the following: • “Appendix B: Configuring Port Bonding for Interplay | MAM (Optional)” on page 221. • “Installing the MediaCentral Distribution Service” on page 101. • “Configuring MCS for Interplay | MAM” on page 103. • “Configuring MCS for MediaCentral and/or Media Composer | Cloud” on page 105.
MCS 2.2 Installation and Configuration Guide The following illustration shows MCDS installed on a server running Media Services Transcode and another instance installed on a server running STP Encode. The MCS server communicates with one instance of MCDS, in this case the one running on the Media Services Transcode server. In case this server goes down, the MCS server can communicate with the MCDS instance on the STP Encode server.
MCS 2.2 Installation and Configuration Guide The welcome screen of the installer is displayed. 4. Click Next. 5. Accept the license agreement and click Next. 6. Accept the default installation location, or click Change to install to a different folder. 7. Click Next. 8. Click Install to begin the installation. The installation should take only a few minutes. 9. When the installation is completed, click Finish. The MediaCentral Distribution Service is automatically started as a Windows service.
MCS 2.2 Installation and Configuration Guide To create an MediaCentral user for Interplay | MAM: 1. With the server up and running, log in to MediaCentral as an administrator level-user. See “Logging into MediaCentral” on page 109. 2. Select Users from the Layout selector. 3. Create a special role for the MAM user by clicking on the Create Role button in the Roles pane. 4. Click the Create Role button. 5. In the Details pane, type the properties for the new role: • • • Role name (e.g.
MCS 2.2 Installation and Configuration Guide 2. Select System Settings from the Layout selector. 3. In the Settings pane, click Player. 4. Enter the MCS server hostname (e.g. ics-dl360-1). 5. Click Apply to save your changes. Now you can monitor load balancing on the Load Balancer page. For more information, see “Monitoring Load Balancing” on page 197. Proceed to “Clustering Workflow” on page 129 (optional).
MCS 2.2 Installation and Configuration Guide Step Task Time Est. 5 Configuring Interplay | Production Settings 1 min In this step you tell MCS where it can find the Interplay | Production server, and the MediaCentral Distribution Service. 6 Configuring MCPS for Interplay 1 min MCPS communicates directly with Interplay | Production. In this step you provide the user name and password used by MCPS for Interplay | Production, and other information it needs.
MCS 2.2 Installation and Configuration Guide ¨ Web browser supported by MediaCentral. The procedures in this section make use of the following information: ¨ Host name of the MCS server (e.g. ics-dl360-1)) or Static IP address of the MCS cluster (e.g.: 192.XXX.XXX.XXX) ¨ New MediaCentral Administrator password. ¨ Knowledge of whether or not MOS plug-ins are used (iNEWS workflows) ¨ Knowledge of whether the facility routers support multicast.
MCS 2.2 Installation and Configuration Guide Configuring the MediaCentral UI By default, the MediaCentral UI contains functionality for all the IME solutions it supports. You can easily remove support for functions that are not needed. To configure the MediaCentral UI: 1. Start the configurator by typing the following at the Linux prompt: /opt/avid/avid-interplay-central/configurator The configuration UI appears.
MCS 2.2 Installation and Configuration Guide • Interplay | Production: Toggles the Interplay | Production settings group. • iNEWS: Toggles the iNEWS settings group. • Media | Distribute: Toggles the Interplay Media | Distribute layout. 3. Use the Up and Down arrow keys to move between the options, Left and Right arrow keys to move between OK and Cancel, SPACEBAR to toggle the asterisks, and press Enter to confirm.
MCS 2.2 Installation and Configuration Guide 2. Enter the URL of the MCS server In the address bar: • https:// where is the host name of the MCS server The Interplay Central sign-in screen appears. In place of the sign-in screen, you might see a warning indicating the connection is not private. The warning relates to SSL certificates.
MCS 2.2 Installation and Configuration Guide In the above case, click Proceed Anyway. Note: For information on configuring a trusted certificate, see the Avid KB: http://avid.force.com/pkb/articles/en_US/how_to/SSL-Certificates-for-server-to-browserconnections. 3. Sign in using the default administrator credentials (case-sensitive): • User name: Administrator Signing in takes you to an MediaCentral layout. 4. The first time any user signs in, the Avid Software License Agreement is presented.
MCS 2.2 Installation and Configuration Guide If you created iNEWS and Interplay | Production users called Administrator with the default MediaCentral Administrator password, you can check “Use my MediaCentral Credentials”. Otherwise, enter the user names and passwords for the iNEWS system, and the Interplay | Production system.
MCS 2.2 Installation and Configuration Guide Setting the System ID and Changing the Administrator Password In this step you enter the System ID into MediaCentral. The System ID is a unique identifier that is used for support. For reasons of security it is strongly suggested that you change the password for the Administrator user. This procedure makes use of the following information: ¨ The System ID (an 11-digit number used in support calls). ¨ MediaCentral Administrator password.
MCS 2.2 Installation and Configuration Guide 5. Expand the list of administrators in the User Tree and locate the Administrator user. 6. Double-click the Administrator user to view its details. 7. Click the Change Password button in the Details pane, and enter a new password for the Administrator user. Use a strong password that is in accordance with the client’s password enforcement policies. 8. Click OK update the password information.
MCS 2.2 Installation and Configuration Guide systemID-b, and if present, systemID-c. Address resolution can be through DNS or hosts file. 4. Configure the additional iNEWS settings: Setting Description Timing Field The value used to specify how the iNEWS timing field is updated when you associate a sequence with a story. Tape ID When you associate a sequence with a story, the iNEWS field name you want to update the sequence Tape-ID with — for example, video-id.
MCS 2.2 Installation and Configuration Guide 3. Configure Interplay | Production credentials: a. Enter the Interplay | Production server (the Interplay engine) hostname or IP address. If you have an Interplay Engine cluster, specify the virtual server, not an individual server. b. Enter the Service URL of the MediaCentral Distribution Service (e.g. https://:). You can enter a hostname or IP address for the server.
MCS 2.2 Installation and Configuration Guide ¨ Lookup server hostname(s) ¨ Knowledge of whether multi-resolution workflows are being used Note: The host names indicated above is the host name only (e.g. mi-mtl-1),that is, it is the name of the machine. Do not use the fully qualified domain name (e.g. mi-mtl-1.mydomain.com or mi-mtl-1.mydomain.local). It can also be the IP address. To configure MCPS for Interplay: 1. Select System Settings from the Layout selector. 2.
MCS 2.2 Installation and Configuration Guide Proceed to “Configuring the MCPS Player” below. Configuring the MCPS Player The MCPS Player communicates directly with the MCS server to obtain media for playback, using the credentials of the logged-in user for validation. In this step you tell the MCPS Player where to find the MCS server. This procedure makes use of the following information: ¨ MCS server hostname (e.g. ics-dl360-1) ¨ MCS cluster static IP address (e.g. 192.XXX.XXX.XXX) or host name (e.g.
MCS 2.2 Installation and Configuration Guide Configuring the MCPS Player for Media Composer | Cloud In this step you provide user credentials for Media Composer | Cloud. This procedure makes use of the following information: ¨ User name and password reserved for the Media Composer | Cloud user (e.g.
MCS 2.2 Installation and Configuration Guide • Communication with the ISIS • Playback of compressed media generated on the MCS server over the network Multiple connections are possible. When you maintain other active connections on the MCS server, you must indicate which network connections are reserved for ISIS, and which are used for other network activity.
MCS 2.2 Installation and Configuration Guide Mounting the ISIS System(s) Now that you have specified what NIC interface connection(s) are used to reach the ISIS, you can mount the ISIS system(s). MCS communicates with ISIS storage directly. It uses a separate set of ISIS credentials from the end-user to read media assets for playback and to write audio assets for voice-over recorded by Interplay Central end-users.
MCS 2.2 Installation and Configuration Guide c. Password Note: The host name indicated above is the host name only (e.g. isis-mtl-1),that is, it is the name of the machine. Do not use the fully qualified domain name (e.g. isis-mtl-1.mydomain.com or isis-mtl-1.mydomain.local). It can also be the IP address. 6. For a Zone 3 connection, enter list of IP addresses for the ISIS System Director. Separate each entry by a semi-colon, no spaces. 7. Click Apply. The status changes to Connected. 8.
MCS 2.2 Installation and Configuration Guide The output above indicates an ISIS called morphisis1 mounted at /isis/morphisis1. “Fuse” is the RHEL filesystem type reserved for third-party filesystems. 3. The Linux df command displays disk usage information for all the mounted filesystems: df -h The system responds with output similar to the following: Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg_icps-lv_cache 527G 6.
MCS 2.2 Installation and Configuration Guide To disable 3G and Edge streams: 1. Log in as root and edit the following file using a text editor (such as vi): /usr/maxt/maxedit/share/MPEGPresets/MPEG2TS.mpegpreset 2. In each of the [Edge] and [3G] areas, set the active parameter to active=0. 3. Save and close the file. Proceed to “Clustering Workflow” on page 129 (optional). Or, proceed to “PART V: POST-INSTALLATION” on page 177.
MCS 2.2 Installation and Configuration Guide PART III: CLUSTERING Note: For detailed information on how MCS servers operate in a cluster, see the “MCS 2.2 Clustering Guide”.
MCS 2.2 Installation and Configuration Guide Setting up the Server Cluster Clustering adds high-availability, load-balancing and scale to MCS. To set up a cluster, each server in the cluster must have RHEL and MCS installed. One server must also be fully configured for the deployment of interest. The other servers need only RHEL and MCS installed.
MCS 2.2 Installation and Configuration Guide Note the following: • RabbitMQ, the message broker/queue used by ACS, maintains its own clustering system. It is not managed by Pacemaker • GlusterFS mirrors media cached on an individual RAID 5 drive to all other RAID 5 drives in the cluster. • DRBD mirrors the MCS databases on two servers in a master-slave configuration. This provides redundancy in case of a server failure • Pacemaker is the cluster resource manager.
MCS 2.2 Installation and Configuration Guide The following table lists the bus-dependent services: Node 1 (master) Node 2 (slave) Node 3 Node n AAF Generator† (avid-aaf-gen) ON ON ON ON MCS Messaging (avid-acs-messenger & avid-acs-mail) ON ON ON ON ON ON ON ON Service Name (Linux) MCS Media | Distribute (avid-mpd) †The AAF Generator runs on all nodes, but it is only made use of on the master and slave nodes, since it is used by the MCS Core Service (“the middleware”).
MCS 2.2 Installation and Configuration Guide Clustering Workflow Clustering requires that you set up one server completely before creating a cluster. That is, set up MCS on a server as if you were performing a non-clustered installation. Once that is done, you can set up the other MCS servers and add them to the cluster. The following table outlines the clustering installation workflow: Note: If you are setting up a cluster, only the master node requires configuring.
MCS 2.2 Installation and Configuration Guide Step Task Time Est. other MCS nodes. 7 Replicating the Cluster File Caches 20 min Set up Gluster to mirror the caches, so each server in the cluster can easily use material transcoded by the others. This step is only required if your MCS nodes make use of a dedicated media cache volume (e.g. RAID 5).
MCS 2.2 Installation and Configuration Guide /etc/hosts You also edit the default hosts file, at the following location: /etc/sysconfig/networking/profiles/default/hosts In addition, you optimize the lookup service order by editing the Name Service Switch file in this location: /etc/nsswitch.conf Adding Host Names and IP Addresses to the hosts file In this step you add entries to the hosts file so Linux can quickly resolve host names to IP addresses, for all nodes in the cluster.
MCS 2.2 Installation and Configuration Guide 3. Save and exit the file. Note: It is a good idea to declare the nodes in the hosts file in order of latency, ascending. Run a ping command to each node and add the lines to the file in order of the ping return. For example, if node-2 returns a ping after 30ms and node-3 after 20ms, put in the line for node-3 before node-2. 4.
MCS 2.2 Installation and Configuration Guide Setting Up DRBD In a clustered configuration, MCS uses the open source Distributed Replicated Block Device (DRBD) storage system software to replicate its PostgreSQL database across all nodes in the cluster. In this step, you set up DRBD and initialize the replication using the command provided. Note: DRBD runs on a master node and a non-master node only, even in a cluster with more than two nodes.
MCS 2.2 Installation and Configuration Guide To set up DRBD: Note: Before beginning this procedure, please note the following: • The DRBD setup script is case-sensitive. The host names you enter must exactly match those defined for the master and non-master. • To check the spelling and capitalization of a host, use the Linux hostname command. • In addition, make sure the host name returned by the hostname command is not a “fully qualified domain name” (FQDN).
MCS 2.2 Installation and Configuration Guide Do you want to proceed? [need to type 'yes' to confirm] This indicates the DRBD setup script has found the 20GB partition set aside for it and is about to take ownership of it. 6. Type “yes” at the prompt to continue with the setup. The system responds, and waits for the other DRBD node, with output similar to the following: Writing meta data... initializing activity log NOT initializing bitmap New drbd meta data block successfully created.
MCS 2.2 Installation and Configuration Guide 5% synchronized … 55% synchronized 97% synchronized Node synchronization finished 8. Wait until node synchronization is completed before proceeding to the next step. Proceed to “Starting the Cluster Services” below. Starting the Cluster Services Now that you have set up DRBD, you are ready to start and configure the cluster services. Scripts have been provided that simplify this process.
MCS 2.2 Installation and Configuration Guide --corosync-mcast-addr="" --rabbitmq_master= • is the multicast address that IT provided for the cluster (e.g. 239.XXX.XXX.XXX). Note: The “default” multicast address used for MCS clustering is 239.192.1.1. This is set by the setup-corosync script, if you do not specify one.
MCS 2.2 Installation and Configuration Guide Note: The comma-separated list of non-DRBD nodes must not contain any spaces between each entry, only a comma. 3.
MCS 2.2 Installation and Configuration Guide Proceed to “Joining the Cluster” below. Joining the Cluster With the clustering services up and running on the master node – the fully configured MCS server – add the other servers to the cluster. To add other servers to the cluster: 1.
MCS 2.2 Installation and Configuration Guide service avid-mpd restart Note: Restarting the Media | Distribute (avid-mpd) service is only needed if Media | Distribute (separate installer) is installed on the system. Proceed to “Replicating the Cluster File Caches using Gluster” on page 140. Replicating the Cluster File Caches using Gluster Before you set up a server cluster you should enable the automatic replication of cluster file caches between all servers.
MCS 2.2 Installation and Configuration Guide Step Task Time Est. A “utility” procedure repeated here for convenience. 3 Installing Gluster 2 min/server Install the Gluster RPMs and start the Gluster service. 4 Unmounting and Removing the USB Key 2 min/server Remove the USB key to prevent accidental rebooting and reimaging of the disk. 5 Creating the Trusted Storage Pool 5 min In this step, you tell Gluster which servers will be involved in cache replication.
MCS 2.2 Installation and Configuration Guide Step Task Time Est. In this final step you use the Linux chkconfig utility to ensure the Gluster daemon starts and system startup. The following illustration summarizes the filesystem operations: For a description of the purpose and contents of each cache subdirectory, see “Caching in MCS” on page 28.
MCS 2.2 Installation and Configuration Guide Note: The host name indicated above is the host name only (e.g. ics-dl360-1),that is, it is the name of the machine. Do not use the fully qualified domain name (e.g. ics-dl360-1.mydomain.com or ics-dl360-1.mydomain.local). It can also be the IP address. Proceed to “Mounting the USB Key” below.
MCS 2.2 Installation and Configuration Guide Filesystem /dev/sdc1 Size 7.5G Used Avail Use% Mounted on 4.5G 3.0G 61% /media/usb Proceed to “Installing Gluster” below. Installing Gluster Once the MCS Installation USB key is mounted on the Linux server, you can install Gluster. In this step, you both install the Gluster RPMs and create the folders where the caches will be located.
MCS 2.2 Installation and Configuration Guide Unmounting and Removing the USB Key As a safety precaution, once you have installed Gluster, unmount and remove the USB key from the server before proceeding. If you re-boot with the server with the USB key still in place, RHEL will be re-installed and all your work will be lost. To unmount the USB key: 1.
MCS 2.2 Installation and Configuration Guide Example (do not type this example) To illustrate the command, consider an MCS server cluster consisting of three servers, ics-dl360-1, icsdl360-2 and ics-dl360-3. To create the GlusterFS trusted storage pool from ics-dl360-1, you would issue the following commands: gluster gluster peer peer probe probe ics-dl360-2 ics-dl360-3 This procedure requires the following information: • Machine name (host name) of each server in the cluster (e.g.
MCS 2.2 Installation and Configuration Guide Configuring the GlusterFS Volumes Gluster uses its own file system, GlusterFS, which includes its own notion of volumes. GlusterFS volumes consist of underlying directories from the trusted storage pools. When you create a GlusterFS volume, you also configure its behavior. In MCS we make use of Gluster’s ability to automatically distribute and replicate data (mirror) across the trusted storage.
MCS 2.2 Installation and Configuration Guide To create and start the GlusterFS volumes: Note: Perform this procedure just once, on any server in the cluster. It doesn’t matter which one. 1.
MCS 2.2 Installation and Configuration Guide Setting Gluster Volume Ownership The following two directories must be owned by user maxmin and have group id set to maxmin: cache/gluster/gluster_data_download cache/gluster/gluster_data_fl_cache The directories above are associated with RHEL directories (/cache/fl_cache and /cache/download) used to store files for http-based streaming, such as media converted to FLV for file-based playback.
MCS 2.2 Installation and Configuration Guide 7. Verify the success of the ownership changes: ls –la /cache/gluster Should return: drwxrwsrwx 3 maxmin maxmin 4096 Jan 12 09:51 gluster_data_download drwxrwsrwx 5 maxmin maxmin 4096 Jan 12 09:51 gluster_data_fl_cache drwxr-xr-x 3 root root 4096 Feb 5 08:33 gluster_data_multicam 8. Restart the GlusterFS service: service glusterd restart 9.
MCS 2.2 Installation and Configuration Guide mkdir mkdir mkdir mkdir /cache/fl_cache /cache/mob-fetch /cache/render /cache/spooler Note: You created /cache/download and /cache/fl_cache earlier when setting up the RAID (see “Partitioning the RAID” on page 96). Moreover, if you are creating a cluster for a system that has already been set up and run, the above folders already exist.
MCS 2.2 Installation and Configuration Guide The above lines mount the cache at the end of the boot cycle, when the network services are up. Restarting the avid-all service ensures the backend services have access to the newly mounted caches. 8. Save and exit the file: :wq Proceed to “Changing Ownership and Mounting the GlusterFS Volumes in Linux” below.
MCS 2.2 Installation and Configuration Guide drwxrwsrwx drwxrwsrwx 2 maxmin maxmin 4096 Nov 4 10:15 gluster_data_download 2 maxmin maxmin 4096 Nov 4 10:15 gluster_data_fl_cache The “s” in the group position indicates a special permission has been applied. 4.
MCS 2.2 Installation and Configuration Guide Test the cache setup by writing a file to one of the GlusterFS cache folders (e.g. /cache/download) on one server and verify it appears on the other servers. For example, the following Linux commands create two files: 1) toto.txt in /cache/download and 2) sample.txt in /cache/render: touch touch /cache/download/toto.txt /cache/render/sample.txt Proceed to “Ensuring Gluster is On at Boot” on page 154.
MCS 2.2 Installation and Configuration Guide In a cluster setup, you must point the MCPS player to the cluster IP address (e.g. 192.XXX.XXX.XXX) or host name (e.g. ics-cluster). If not, video will be served by the server named earlier, and only that server. In a cluster, you want the master node to determine which node serves the video. In a cluster, the master node holds the cluster host name and IP address. In this step you change configuration settings to tell the MCPS player where to find the cluster.
MCS 2.
MCS 2.2 Installation and Configuration Guide Overview The MAM connector enables all Interplay | MAM workflows in MediaCentral UX. The supported configuration for the MAM connector requires you to install the connector on the MCS server, which is part of your MediaCentral configuration. Before you install the MAM connector, you must install and configure the MCS server. The MAM connector installation procedures assume you have installed Avid MediaCentral Platform Services (MCS).
MCS 2.2 Installation and Configuration Guide Step Task Time Est. and slave nodes. It is not installed on load-balancing nodes. See “Identifying the Master, Slave and Load-Balancing Nodes” on page 186. 5 Bringing the Cluster Offline 5 min To prevent unnecessary failovers, bring the cluster offline before installing the MAM connector 6 Installing the MAM Connector 5 min Insert the USB key with the MAM connector RPMs on it, and install the packages.
MCS 2.2 Installation and Configuration Guide If the file is in the ZIP format, unzip it and transfer the compressed tar (.tar.gz) file. Bringing the Cluster Offline Pacemaker tracks failure counts for various services in a cluster, and a failover from master to slave will automatically take place when a service’s threshold is reached. To prevent unintended failovers during installation of the MAM connector, bring the cluster offline first. To bring the cluster off-line: 1.
MCS 2.2 Installation and Configuration Guide 9. If there are fail counts listed, run the cluster resource manager cleanup command to reset them: crm resource cleanup [] is the resource name of interest: AvidIPC, AvidUMS, AvidACS, pgsqlDB (or another) (optional) is the node of interest. Note: If you receive an “object/attribute does not exist” error message, it indicates the resource is active on more than one node.
MCS 2.2 Installation and Configuration Guide 5. Run the MAM Connector installation script: /media/usb/connector/MediaCentral_MAM_Connector_/install.sh 6. Verify the success of the installation using rpm command: rpm -qa | grep mam The output should include the following line: avid-interplay-central-mam-2.1.0..noarch.rpm 7.
MCS 2.2 Installation and Configuration Guide In a single-node deployment restart the following service instead: service avid-interplay-central restart 6. Unmount the MAM Connector Installation USB key and remove it from the server. See “Unmounting and Removing the USB Key” on page 145. 7. Repeat the process for the slave server. 8. Bring the cluster back online. See “Bringing the Cluster Offline” on page 159.
MCS 2.
MCS 2.2 Installation and Configuration Guide Overview This section provides instructions on setting up a multi-zone environment. This can be done as part of an initial installation, or for systems that are already established. The procedures in this section cover single MCS nodes and MCS clusters that are already established.
MCS 2.2 Installation and Configuration Guide Multi-Zone Workflow The following table describes each of the main multi-zone configuration steps: Step Task Time Est. 1 Setting up and Configuring an MCS Server or Server Cluster in Each Zone 2–3 hr per zone If you have not already done so, set up a fully operational MCS server (or cluster) in each zone. See “Installation Workflow” on page 43 and/or “Clustering Workflow” on page 129.
MCS 2.2 Installation and Configuration Guide ¨ Slave node Install the generated RSA keys in the slave zone on the following nodes: ¨ Master node ¨ Slave zone This procedure makes use of the following information: ¨ Linux root password To generate and Install RSA Keys: 1. Log in (at the Linux prompt) to the master node in the master zone as the root user user. 2.
MCS 2.2 Installation and Configuration Guide Creating the Master Zone and Initiating Multi-Zone Environment This procedure makes use of the following information: ¨ The master zone name (e.g. master_zone) ¨ The master zone root user credentials ¨ The UMS administrator password (e.g. Avid123) To create the master zone and initiate the multi-zone: 1. Log in as the Administrator user to the MediaCentral UX instance located in the master zone, and select System Settings from the Layout selector. 2.
MCS 2.2 Installation and Configuration Guide Note that if the local zone is a cluster this is indicated in the UI: 3. Click the Activate Multi-Zone button. In the confirmation dialog that appears, click Proceed. A Zone Details dialog appears. 4. In the Zone Details dialog that appears, enter the following information: • Root Username and Root Password: The root user credentials for the master zone MCS server. • Zone Name: Name of the master zone (e.g. Master_Zone).
MCS 2.2 Installation and Configuration Guide Once registration of the master zone is complete, a dialog appears indicating success of the operations. 6. Click OK to close the dialog and complete the process. MediaCentral is automatically restarted. 7. Once restarted, log back in to MediaCentral UX. The Zones Details area now shows the newly created zone (e.g. Master_Zone): Proceed to “Adding Slave Zone(s) to the Multi-Zone Environment”, below.
MCS 2.2 Installation and Configuration Guide 3. Click the Add Slave Zone button. In the confirmation dialog that appears, click Proceed. The Zone Details dialog appears. If the master zone is a cluster, the following Zone Details dialog appears instead: 4. In the Zone Details dialog, enter the following information. Master Zone Access (only appears if master zone is a cluster): • Root Username and Root Password: The root user credentials for the master zone MCS server.
MCS 2.2 Installation and Configuration Guide 5. Click Register. A dialog appears showing progress of the operations related to slave zone registration. Once the slave zone registration is complete, a dialog appears indicating success of the operations. 6. Click OK to close the dialog and complete the process. 7. The Zones Details page is refreshed with the new slave zone. Note that the master zone is now identified with the letter “M” and the current zone is bolded.
MCS 2.2 Installation and Configuration Guide 1. Log in to MediaCentral UX as an administrator-level user in either the master zone or one of the slave zones. 2. Select Users from the Layout selector. 3. Observe that the Users layout now has an additional tab named MediaCentral Zones, where all the linked zones are displayed. 4. To validate that a user added to one zone can log in from another, begin by clicking the Create User button.
MCS 2.2 Installation and Configuration Guide Failed to Resolve Zone URL When registering the slave zone the following message indicates the zone is unreachable. Verify that the zone is online and the URL you entered is correct. The master zone URL is passed into the zone configuration processes automatically, based on the current URL as shown in the browser. If you receive the following error, it may indicated the browser is using a form that is unreachable to the backend services (e.g. a hostname).
MCS 2.2 Installation and Configuration Guide The following table presents typical configuration error messages: Message Explanation The zone does not exist in the UMS. Zone is present in the BUS, but not in the UMS. The zone exists in UMS but is not linked. Zone is present in the UMS, but not in the BUS. Some links are missing The zone is missing one or more links to other zones. Errors During Setup If any stage of the setup fails, all the subsequent steps are skipped.
MCS 2.2 Installation and Configuration Guide 1. Log in to MediaCentral UX in the master zone as the Administrator user. 2. Select System Settings from the Layout selector and Zones in the Settings pane. 3. For each slave zone, select the zone and click the Remove Zone button. The Zone Details dialog appears for the slave zone. 4. In the Zone Details dialog, enter the following information: Master Zone Access: • Root Username and Root Password: The root user credentials for the master zone MCS server.
MCS 2.2 Installation and Configuration Guide 6. Repeat for any other slave zones you wish to add. 7. Once deregistration of the slave zone(s) is complete, select the master zone and click the Remove Zone button. The Zone Details dialog appears for the master zone. 8. Enter the master zone UMS administrator password (e.g. Avid123), then click the Unregister button. A dialog appears showing progress of the operations related to slave zone deregistration.
MCS 2.
MCS 2.2 Installation and Configuration Guide Determining the Installed MCS Version You can verify the version/build numbers of the MCS installed services. To verify the version numbers, connect to the MCS server console as the root user and type: ics_version …then press Enter. Service version numbers are returned as follows: UMS Version: 2.2.x.x ICPS Version: 2.2.x.x ICPS manager Version: 2.2.x.x ACS Version: 2.2.x.x System ID: "xxxxxxxxxxx" ICS installer: 2.
MCS 2.2 Installation and Configuration Guide Verifying Cache Directory Permissions As part of the installation (or upgrading) process, you created a number of cache directories, changing ownership and setting their permissions. In this section, you verify the permissions are set correctly. Note: This procedure is only necessary for a cluster deployment.
MCS 2.2 Installation and Configuration Guide 4. If the ownership and permissions are not set correctly, refer to the instructions in “Making the RHEL Cache Directories” on page 150. Validating the FQDN for External Access As noted in “DNS Requirements” on page 27, it is vital that the fully qualified domain name (FQDN) for each node in the cluster is resolvable by the DNS name server tasked with doing so.
MCS 2.2 Installation and Configuration Guide If MediaCentral will be accessed from outside the corporate firewall via NAT, ensure that this server is accessible. In particular, ensure the FQDN returned by the query is associated with a public address. 3. Refresh the browser to establish a new session. For completeness, keep refreshing the browser until you have seen all nodes in the cluster.
MCS 2.2 Installation and Configuration Guide Recall that tapping the tab key invokes the Linux autocomplete functionality and ensures accuracy when typing long file names. Some feedback appears indicating the success of the installation. 4. To verify the package has been installed: rpm -qa | grep max 5. Log in to the slave node as root and repeat the process. 6. To launch the player demo web page by opening a browser and navigating to the following URL: http:///player/index.
MCS 2.2 Installation and Configuration Guide The following table lists the files and directories backed up and restored by the system-backup script. Note: RHEL user names and passwords (such as the root user) are not backed up or restored by the system-backup script. After an upgrade, for example, logging in as “root” requires the default password. For the default root user password, contact your Avid representative.
MCS 2.2 Installation and Configuration Guide 2. Change to the mount point. For example: cd /media/usb 3. Back up the MCS settings and database using the backup script. ./system-backup.sh –b A backup file is written to the USB key: /media/usb/sys-backup/ics_setup_files.tar.
MCS 2.2 Installation and Configuration Guide mv sys-backup- sys-backup 4. Restore the MCS settings and database using the backup script. ./system-backup.sh –r You are asked to confirm the restoration of the MCS database: Would you like to restore the database now? (y/n) 5. Type “y” (without the quotes) to confirm the action. You are asked to confirm the shutting down of the Avid services: All Avid services will be shut down before performing a database restore operation.
MCS 2.2 Installation and Configuration Guide As noted, resources are collections of services grouped together for oversight by Pacemaker. Pacemaker sees and manages resources, not individual services. For a list of service that need to be running, see “Tables of Services, Resources and Utilities” on page 187.
MCS 2.2 Installation and Configuration Guide Tables of Services, Resources and Utilities The tables in this section provide lists of essential services that need to be running in a clustered configuration. It includes three tables: • Single Node Deployment: The services that must be running for a single node deployment. • Cluster — All Nodes: The services that must be running on all nodes, in a cluster deployment. • Cluster — Master Node: The services that must be running on the master node only.
MCS 2.2 Installation and Configuration Guide Single Node Deployment Service Description avid-aaf-gen AAF Generator service, the service responsible for saving sequences. To reduce bottlenecks when the system is under heavy load, five instances of this service run concurrently, by default. Installed on all nodes but only used on the master or slave node, depending on where the IPC Core service (avidinterplay-central) is running.
MCS 2.2 Installation and Configuration Guide Single Node Deployment Service Description avid-ics A utility script (not a service) that can be used to verify the status of all the major MCS services that must be running on the node.
MCS 2.2 Installation and Configuration Guide All Nodes Service Description avid-all Encapsulates all MCPS back-end services: - avid-config avid-isis avid-fps avid-jips avid-spooler avid-edit pacemaker Cluster Management and Service Failover Management corosync Cluster Engine Data Bus glusterd GlusterFS daemon responsible for cache replication rabbitmq-server Messaging broker/queue for ACS (the message bus). Maintains its own cluster functionality to deliver highavailability.
MCS 2.2 Installation and Configuration Guide All Nodes Service Description avid-mpd Media | Distribute services. Operates similarly to the avid-acs-messenger service described above. This service is only available when Media | Distribute (separate installer) is installed on the system. avid-ics A utility script (not a service) that can be used to verify the status of all the major MCS services.
MCS 2.2 Installation and Configuration Guide Cluster — Master Node Only The following table presents the services that must be running on the master node. Note: These services must also be running on a single-node deployment. Master Node Service Description avid-interplay-central MediaCentral Core services (“the middleware”) avid-acs-ctrl-core Avid Common Services bus (“the bus”) Essential bus services needed for the overall platform to operate: • “avid.acs.
MCS 2.2 Installation and Configuration Guide Master Node Service Description postgresql-9.
MCS 2.2 Installation and Configuration Guide Managed by Pacemaker/Corosync Service Description MongoDB Encapsulates: - AvidAll mongod Encapsulates: - AvidICPS Encapsulates: - Redis avid-all avid-icps-manager Encapsulates: - redis Note: Pacemaker and Corosync manage numerous other cluster resources. The table lists the most important ones.
MCS 2.2 Installation and Configuration Guide Though the AAF Generator service is active in saving sequences only on the master node, you should verify its status on the slave node too, to prepare for any failover. 2.
MCS 2.2 Installation and Configuration Guide This returns the status of services on all nodes. Error messages may appear.
MCS 2.2 Installation and Configuration Guide Note: The prefix lsb shown in the cluster resource monitor indicates the named service conforms to the Linux Standard Base project, meaning these services support standard Linux commands for scripts (e.g. start, stop, restart).
MCS 2.2 Installation and Configuration Guide Service Description Session Start The time (MM.DD.YYYY HH:SS) at which the player embedded in the browser connected to the MCS server. Session End The time at which the session was terminated. IP The node’s IP address (e.g. XXX.XX.XX.XXX/32) Note that a /32 netmask indicates that point-to-point communication is used by the load balancing service. It does not reflect the facility netmask in use across the facility network. Added The time (MM.DD.
MCS 2.2 Installation and Configuration Guide This returns the status of all cluster-related services on all nodes, with output similar to the following example using two nodes (e.g. burl-ics1 & burl-ics2).
MCS 2.2 Installation and Configuration Guide 3. In a separate terminal session log in to any node as root and bring the master node into standby mode: crm node standby In the above command, replace with the name of the master node (e.g. morpheus-hp1). 4. Observe the failover in the crm_mon utility within the other terminal session as the master node is reassigned to one of the remaining nodes and the associated services are brought up on the new master.
MCS 2.2 Installation and Configuration Guide for the resource (the “everywhere” form). For example, for the AvidAll resource, use AvidAllEverywhere. For AvidConnectivityMon, use AvidConnectivityMonEverywhere. Note: You can address the services contained in the postgres resource group (postgres_fs, AvidClusterIP and pgsqlDB) individually, or as a group. For example, to reset the fail count for AvidALL resource, issue the following command: crm resource cleanup AvidAllEverywhere 3.
MCS 2.2 Installation and Configuration Guide The system responds by opening an email shell and prompting your for a subject line: Subject: 5. Enter a subject line and press Return: The system responds by moving the cursor into the body of the email. Type a line or two of text, as desired. Note: If the Backspace key types “^H” rather than deleting, exit the email shell by typing Ctrl-c (twice).
MCS 2.2 Installation and Configuration Guide admin-email="email_A@temp.net,email_B@temp.net" 5. Save and exit the file ( :wq). The system responds by writing the updated configuration file to a temporary location and outputting an error message similar to the following: "/tmp/tmpjve4D9" 72L, 3258C written ERROR: rsc-options: attribute admin-email does not exist Do you still want to commit? 6. Type yes to commit your changes. 7.
MCS 2.2 Installation and Configuration Guide 2. Unmounting the GlusterFS volumes 3. Recreating the GlusterFS volumes, without the eliminated node 4. Reconfigure the cluster, and bring the cluster back up. For guidelines, see “Adding a New Node to a Cluster” below. Note: Even after performing the above steps, a “node offline” message may remain in the cluster monitoring tool (crm_mon).
MCS 2.2 Installation and Configuration Guide 2. One any server in the cluster, stop the GlusterFS volumes: gluster volume stop gl-cache-dl gluster volume stop gl-cache-fl 3. One any server in the cluster, delete the GlusterFS volumes: gluster volume delete gl-cache-dl gluster volume delete gl-cache-fl 4. On each server in the cluster, remove the Linux extended attributes for the /cache directories: setfattr setfattr setfattr setfattr -x -x -x -x trusted.glusterfs.
MCS 2.2 Installation and Configuration Guide To bring the cluster back up with the new node: In this step, you run the setup-cluster script on an existing master or slave node, as you did when originally setting up the cluster, excluding the new node from DRBD. Next, you join the new node to the cluster. 1. On either the master or slave node, run the setup-cluster script. For details on the form of the command, see “Starting the Cluster Services” on page 136.
MCS 2.2 Installation and Configuration Guide • Hostname: http:// where is either the MCS host name (if you only have a single server) Or, http:// where is the IP address you provisioned for the MCS cluster • User name: root • Password: _ Note: Note that you changed the root password during the installation process. Note: Please contact your Avid representative for the default root password. 2.
MCS 2.2 Installation and Configuration Guide • Average CPU load • Number of CPU interrupts per second • System uptime • Swap space (disk space reserved for memory when RAM is fully loaded) • System memory usage • CPU usage Contact your Avid representative for information about Avid System Monitor. A qualified Avid support representative can upgrade an Avid System Monitor system to work with MCS.
MCS 2.2 Installation and Configuration Guide 4. Make the master node the DRBD primary (on the master node): drbdadm primary r0 5. Mount the DRBD drive on the master node: mount /dev/drbd1 /mnt/drbd 6. Start the PostgreSQL database on the master node: service postgresql-9.1 start 7. Restore the MCS database on the master node: /opt/avid/bin/avid-db --drop-db="no" restoreall Once the MCS database has been restored you can begin handing control back to pacemaker in the steps below. 8.
MCS 2.2 Installation and Configuration Guide 3. Swap the NIC interface names so the new card owns port eth0 by editing the 70-persistent-net.rules file. See “Editing the Network Connections” on page 84. 4. Remove the MAC address hardware references for the swapped ports from the corresponding ifcfg-ethX files and reboot. See “Editing the Network Connections” on page 84. 5. Log in to MediaCentral UX with administrator privileges and update the ISIS connection mode to match the new connection speed.
MCS 2.2 Installation and Configuration Guide Appendix A: Installing MCS on Non-HP Hardware For the most part the steps provided in the main body of this guide for installing and configuring MCS on supported HP hardware are easily generalized to non-HP hardware. There are two main differences. Note: This section provides tips for installing RHEL and MCS for Interplay | MAM on non-HP hardware. MCS supports MediaCentral and MediaCentral | Cloud on HP and Dell Hardware only.
MCS 2.2 Installation and Configuration Guide Note: Some MCS software components depend on the language for RHEL being set to English. Please select English as the language of installation. Do not change the input language afterwards. 3. Install MCS. ¨ Mount the RHEL DVD under /sysinstall (this is where the install script looks for it): mount /dev/sdX /sysinstall In the above command, substitute the optical drive device name for sdX (e.g.
MCS 2.2 Installation and Configuration Guide Appendix B: Installing MCS on Dell Hardware This appendix presents the main differences when installing MSC on a supported Dell server. Note: This section provides tips for installing RHEL and MCS for MediaCentral UX on supported Dell hardware. MCS supports MediaCentral and MediaCentral | Cloud on HP and Dell Hardware only. MCS supports Interplay | MAM on both HP and non-HP hardware. Setting Performance Profile 1. 2. 3. 4. 5.
MCS 2.2 Installation and Configuration Guide 2. From the Create Virtual Disk page select Select Physical Disks. 3. Put check marks in the appropriate Physical Disk boxes. a. For the RAID1 (the system disk) this should be 00:01:00 and 00:01:01 b. For the RAID5 (the optional cache disk) this should be 00:01:02 through and 00:01:07. 4. Select Apply Changes. A confirmation screen indicates success. 5. From the Create Virtual Disk Page, select Create Virtual Disk.
MCS 2.2 Installation and Configuration Guide • • • sda: The USB key itself. sdb: The system drive. sdc: The cache volume. To delete the system disk partition table on a preconfigured system: 1. Boot from the USB key. See “Editing the Kickstart File The prepared MCS Installation USB key includes an kickstart (ks.cfg) file supplied by Avid that accelerates the RHEL installation by automatically providing answers to common setup questions for hardware known in advance.
MCS 2.2 Installation and Configuration Guide 5. Select the “/dev/sda1” partition (the USB key). Leave the “Directory holding image” field blank. 6. At the networking prompt, do not set up networking, since it is not needed.
MCS 2.2 Installation and Configuration Guide 7. At the prompt to rescue an existing installation, choose Skip. 8. At the next screen, choose Start shell. RHEL presents the RHEL system prompt: 9. At the system prompt, use the RHEL fdisk utility to examine the current partitions: fdisk -cul Use Shift-Pg Up and Shift-Pg Dn to view the entire output, since scroll bars will not be present in the rescue shell.
MCS 2.2 Installation and Configuration Guide The desired output is similar to the following. That is, there should be three partitions on the system disk (sdb): Disk /dev/sdb: 500.
MCS 2.2 Installation and Configuration Guide w 15. Verify the partitions on sdb were successfully removed using the RHEL fdisk utility: fdisk -cul 16. Proceed with the RHEL and MCS installation by booting from the USB key and installing RHEL and MCS. The correct partitions and filesystems will be created automatically during the installation. Editing the Kickstart File The prepared MCS Installation USB key includes an kickstart (ks.
MCS 2.2 Installation and Configuration Guide The server will discover the USB key when it scans for devices, but it will not boot from it by default. 3. From the Boot Manager Main Menu, choose BIOS Boot Menu. 4. From the BIOS Boot Manager (a text screen), highlight the “Hard drive C:” choice. 5. From the popup menu that appears, select “Front USB” and press Enter.
MCS 2.2 Installation and Configuration Guide The server continues the boot from the USB key and the “Welcome to Red Hat Enterprise Linux” screen appears. 6. From the “Welcome to Red Hat Enterprise Linux” screen, choose “Install Red Hat 6.5 with ICS”. 7. Refer to the “MCS 2.0 installation and Configuration Guide” for the remaining installation instructions. Additional Notes - - Set the system clock at the command line after the first boot, not in BIOS.
MCS 2.2 Installation and Configuration Guide Port bonding is only possible for Interplay | MAM deployments. It does not apply to MediaCentral and/or Media Composer | Cloud deployments. MediaCentral and Media Composer | Cloud cannot make use of port bonding. The procedures in this section make use of information you entered in “Appendix J: Installation Pre-Flight Checklist” on page 244: ¨ Device name for each NIC Ethernet port used in port bonding (e.g. eth0, eth1, etc.
MCS 2.2 Installation and Configuration Guide 3. Using the Linux editor vi, open the interface configuration file for the first interface to be included in the port bond (e.g. ifcfg-eth0): vi ifcfg-eth0 4. When you open it for editing, the file should look something like this: DEVICE=eth0 NM_CONTROLLED=yes ONBOOT=yes DHCP_HOSTNAME=$HOSTNAME BOOTPROTO=static TYPE=Ethernet USERCTL=no PEERDNS=yes IPV6INIT=no 5.
MCS 2.2 Installation and Configuration Guide ifcfg-bond0 is the name of the port-bonding group (e.g. ifcfg-bond0). 9. Add the following lines to the newly created file: DEVICE=bond0 ONBOOT=yes BOOTPROTO=static USERCTL=no BONDING_OPTS="mode=0" • DEVICE=bond0 specifies the name of the port bonding group interface. It must correspond to the name of the file itself.
MCS 2.2 Installation and Configuration Guide Appendix C: Migrating the UMS Database with the User Management Utilities Tool Some MCS upgrade paths require that you migrate your existing Windows-based User Management Services (UMS) database to the new Linux-based MCS server. For example, updating from Interplay Central 1.2.x to Interplay Central 1.3 (or higher) involves the decommissioning and/or repurposing of the Windows server where middleware and UMS ran under Interplay Central 1.2.x.
MCS 2.2 Installation and Configuration Guide C:\ProgramData\Avid\Avid Interplay Central User Management Service\db If the database lock file is present, wait for the UMS to stop completely and for the lock file to be removed. Note: Attempting to migrate a locked database can result in data corruption. 5. Copy the UMS database (database.h2.db) file from the Windows server to an available directory on the new RHEL server (e.g. /tmp). The Windows database file is located here: C:\ProgramData\Avid\Avid Inte
MCS 2.2 Installation and Configuration Guide • Type the following command at the Linux command prompt: avid-ums-admin-tool -ms [acs-bus-url] [ums-admin-password] For example: avid-ums-admin-tool -ms localhost:61616 xxxxx In the above example, the default ACS bus URL and port is used (localhost:61616). A message informs you when the settings migration completes: Migration completed successfully.
MCS 2.2 Installation and Configuration Guide Appendix D: Installing the Chrome Extension for MediaCentral MOS Plug-Ins MediaCentral provides support for MOS Active-X plug-ins. For example, Deko Select is a plug-in for a newsroom computer system’s interface that allows a user, such as a reporter, to drag and drop graphic templates directly into the story, as well as alter replaceable text or graphics in the selected template.
MCS 2.2 Installation and Configuration Guide Uninstalling the Chrome Extension If you need to uninstall the Chrome Extension, use the Windows Control Panel. Do not use the Chrome Extensions page. 1. Click Start and select Control Panel. 2. Click Programs and Features. 3. Right-click Avid MediaCentral MOS plugin and select Uninstall. Click Yes and follow the prompts. For more information about MOS plug-ins, see the Avid MediaCentral User’s Guide or the Avid MediaCentral Help.
MCS 2.2 Installation and Configuration Guide 4. Navigate once again to MCS server or cluster (e.g. https://) and log in as a user for whom MOS plug-ins are enabled. Note: To enable MOS for the logged in user, in MediaCentral, select Home -> User Settings -> MOS and then select “MOS enabled” 5. Download and run setup.exe as prompted. If your receive a "This webpage is not available" message, refresh with F5, and then say Yes to proceed.
MCS 2.2 Installation and Configuration Guide "description": "Avid MOS ActiveX Chrome Extension", "key": "MIGfMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCa6DtGBLy26p0nWU7mfBTutgDZpGZw0t a30LRo1Av6J1LUgL3AxJu5BP4TJxlXXbIKd0H2X6oLgKU3GIw5+r1YKK8BKVfgjpSanEWzg vWsbjXcnH4XVF8thXYvutkTj5telkhFmOba1UG0zauqMqpnWus9ADGyMGBUIPsTlLhXDwID AQAB", "manifest_version": 2, "name": "Avid MOS ActiveX hosting plugin", "plugins": [ { "path": "npchmos.dll", "public": true } ], "version": "1.0.1.
MCS 2.2 Installation and Configuration Guide } ringnumber: 0 bindnetaddr: 10.16.35.0 mcastport: 5405 } transport: udpu } As illustrated by the example above, the following configuration changes are required: 1. Remove mcastaddr from the file (leave mcastport). 2. Add the new transport (that indicates unicast): udpu. 3. Create a member{} section for each node in the cluster, following the example, but replacing the values for memberaddr with the IP address of your own cluster nodes.
MCS 2.2 Installation and Configuration Guide 4. Edit the corosync configuration file: vi /etc/corosync/corosync.conf • Remove mcastaddr from the file (leave mcastport). • Add the new transport (that indicates unicast): udpu. • Create a member{} section for each node in the cluster, following the example, but replacing the values for memberaddr with the IP addresses of your own cluster nodes. 5. Restart corosync on the node: service corosync start 6.
MCS 2.2 Installation and Configuration Guide Appendix G: Installing the Interplay | Production License for MediaCentral The Avid Interplay Administrator is a client application that can be installed on any computer in your network and then used to manage either the Interplay Engine or the Interplay Archive Engine. You can use the Licenses view of the Interplay Administrator to install the Interplay | Production license needed for integration with MediaCentral.
MCS 2.2 Installation and Configuration Guide Appendix H: Configuring iNEWS for Integration with MediaCentral Before you can connect to an iNEWS newsroom computer system from an MediaCentral workstation, you must edit two system files in iNEWS so that iNEWS recognizes MediaCentral as a properly licensed device. The files to edit are: • SYSTEM.CLIENT.VERSIONS • SYSTEM.CLIENT.
MCS 2.2 Installation and Configuration Guide database if Workstation addresses shows a “site” license and IP-specific restriction is not wanted. • Workstation resources—the number of clients that can simultaneously connect to iNEWS, including iNEWS workstations, MediaCentral workstations, Apple iPad tablets, and Apple iPhone devices. • Mobile devices allowed—the number of mobile devices that can simultaneously connect to iNEWS.
MCS 2.2 Installation and Configuration Guide 4. Save the story. 5. Reconfigure the system. From the iNEWS console: a. Select the master computer, which is typically server A. b. Enter superuser mode, using the correct password. The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#). c. Take the system offline by typing: NRCS-A# offline d. Reconfigure the system by typing: NRCS-A# configure -n The above command must be run on the master computer. e.
MCS 2.2 Installation and Configuration Guide Note: You do not need to add to SYSTEM.CLIENT.WINDOWS the IP addresses of any MediaCentral client computers or devices. 4. Save the story. 5. Reconfigure the system. From the iNEWS console: a. Select the master computer, which is typically server A. b. Enter superuser mode, using the correct password. The dollar sign ($) at the end of the console’s server prompt will change to a pound sign (#). c. Take the system offline by typing: NRCS-A# offline d.
MCS 2.2 Installation and Configuration Guide Appendix I: Installing and Configuring the Avid MediaCentral | UX Mobile Application for iPad or iPhone The Avid MediaCentral | UX mobile application is a native user interface designed to run on the Apple iPad touch-screen tablet and the Apple iPhone touch-screen phone, and enable direct, secure access to your station’s iNEWS newsroom computer system.
MCS 2.2 Installation and Configuration Guide Editing SYSTEM.CLIENT.VERSIONS You use the iNEWS console in superuser mode, for some steps in the following procedure. For more information, see “The iNEWS Console” chapter in the “iNEWS Installation and Configuration Guide”. 1. Sign in to an iNEWS workstation as a system administrator, or any user account with write access to the System directory. 2. Navigate to SYSTEM.CLIENT.VERSIONS and open the first story in that queue. 3.
MCS 2.2 Installation and Configuration Guide f. Press Ctrl+D to leave superuser mode. The pound sign (#) at the end of the console’s server prompt will change back to a dollar sign ($). Adding iPad and iPhone Devices to the iNEWS Configuration File The configuration file (/site/config) lists all devices, servers, and resources configured to run on your iNEWS newsroom computer system and how they are connected.
MCS 2.2 Installation and Configuration Guide Note: For dual or triple server systems, the configuration file has multiple host sections to define which server handles which devices under various circumstances. You should add resource list entries to each host section. 4. In the INWS sessions section, add a resource line for the devices, using the following format: inws - gnews ; For example: inws 2001:2005 - gnews – 5.
MCS 2.2 Installation and Configuration Guide Installing Avid Central on the iPad or iPhone The following procedure assumes licensing, setup, and configuration of the MediaCentral and iNEWS servers have already been completed. To install Avid Central on the iPad or iPhone: 1. Open iTunes (the Apple market). 2. Locate the Avid Central mobile application. 3. Tap Download.
MCS 2.2 Installation and Configuration Guide Appendix J: Installation Pre-Flight Checklist This section lists all the information needed to perform the installation. Please gather the information from the customer before beginning the installation process. Take care to collect all the information relevant to the MCS deployment you are undertaking. System ID and Default Password Information The installation scripts establish login credentials for RHEL and MediaCentral at the administrator level.
MCS 2.2 Installation and Configuration Guide In-House IT Specialist: Phone Number: Email: Network Administrator: Phone Number: Email: Pre-Flight Product Team Contact: Phone Number: Email: Interplay | MAM Administrator: Phone Number: Email: Interplay | MAM Configuration Specialist: Phone Number: Email: Hardware ¨ Windows Machine (32-bit or 64-bit) (e.g. Window XP/Vista/7 laptop or desktop computer): Used to download software from the Internet and prepare the USB key.
MCS 2.2 Installation and Configuration Guide Network Settings Obtain the following information from your network administrator and enter it in the spaces provided. These items are needed by Linux. ¨ Facility Static IP address: ¨ Facility Netmask: ¨ Default Gateway IP: ¨ Primary DNS server: ¨ Secondary DNS server: ¨ DNS Search Path Domain: NTP Time Server Record the Network Time Protocol (NTP) time server address, for use in synchronizing the system clock.
MCS 2.2 Installation and Configuration Guide Hard Drives1: Number of Hard Drives Used for the OS (e.g. 2): Number of Hard Drives Reserved for the Cache (e.g. 6): System Drives Bay and Slots (e.g. Bay 1 Slots 1 &2): Cache Drives Bay and Slots (e.g.
MCS 2.2 Installation and Configuration Guide • If your network already uses multicasting, obtain a distinct multicast address for use by MCS. If there is no other multicast activity on the network, write “use default multicast address”: Note: The “default” multicast address used for MCS clustering is 239.192.1.1. This is set by the setup-corosync script, if you do not specify one.
MCS 2.2 Installation and Configuration Guide • The credentials should not be shared with any human users • Permission to read all folders in the workgroup • We recommend using a name that indicates the purpose of the user credentials (e.g. ics-interplay) ¨ Media Composer | Cloud Playback User Media Composer | Cloud requires a unique user name and password reserved for it. They are used to enable MediaCentral | Cloud playback.
MCS 2.2 Installation and Configuration Guide ¨ MediaCentral Distribution Service – Service URL (e.g. https://:): ¨ Media Indexer host name: Note: If the Interplay media indexer is connected to a High Availability Group (HAG), enter the host name of the active Media Indexer.
MCS 2.2 Installation and Configuration Guide • The credentials should not be shared with any human users • Permission to read all workspaces, and to write to the workspace flagged as VO (voiceover) workspace • We recommend using a name that indicates the purpose of the user credentials (e.g. icsisis) • In multi-ISIS setups, create the same user credentials across all ISIS storage systems.
MCS 2.2 Installation and Configuration Guide Copyright and Disclaimer Product specifications are subject to change without notice and do not represent a commitment on the part of Avid Technology, Inc. The software described in this document is furnished under a license agreement. You can obtain a copy of that license by visiting the Avid Web site at www.avid.com. The terms of that license are also available in the product in the same directory as the software.