• What kind of install? Interplay Central or Interplay MAM.
While the installation steps are very similar for Interplay Central and Interplay MAM support, the configuration steps are different. Instructions for configuring Interplay Central for ICPS are provided in this document. For Interplay MAM, obtain the MAM configuration instructions before proceeding.
• What kind of server setup? Single or Cluster.
A server cluster provides high-availability and load-balancing. The OS and ICPS install identically on each server in the cluster, but additional steps are required to configure the servers as a cluster.
• Is this a dual setup? Interplay MAM and Interplay Central?
ICPS can serve both Interplay MAM and Interplay Central simultaneously. In this case, install an ICPS server cluster as indicated in this document. Then, perform both configuration operations.
Before You Begin
Before you begin, make sure you have the following:
• The ICPS server(s)
• RHEL 6.0 installation installation .iso file or DVD media
• The ICPS installation package (USB_v1.2.zip)
• An 8GB USB key (HP DL380/DL360 installations only; optional for non-HP installations)
• A Windows XP/Vista/7 laptop or desktop computer
Note: The server(s) on which you are installing the ICPS software should be physically installed in your engineering environment, and the appropriate network connection(s) to ISIS and/or the house network should already be made.
You also require access to the server’s console:
• Directly by connecting a monitor and keyboard to the server
• Remotely via KVM or comparable solution
Intended Audiences and Prerequisites
This guide is for the person responsible for performing a fresh install of ICPS, or upgrading or maintaining an existing ICPS installation.
• Professional Services: Avid personnel whose responsibilities include installing and upgrading the ICPS system, on-site at a client’s facility.
• In-House Installers: Clients with an in-house IT department that has expertise in systems integration, Linux (including port-bonding), networking, etc. This kind of person might be called on to add a new ICPS node to an already established ICPS cluster, for example.
Upgrading Instructions
To upgrade from an earlier version of ICPS, mount the USB key and run the installation script.
PART II: Installing ICPS on HP DL380/DL360 Hardware
The following table provides time estimates for each of the main installation steps.
Task Approximate
Time Needed
Step #1 Setting Up the HP Server Hardware 1 hr
Step #2 Installing the RHEL and ICPS Software Components 40 min Step #3 Set up the High-Availability and Load-Balanced Server Cluster 20 min Step #4 Create the Interplay MAM Cache Volume 10min
Step #5 Create the Cluster Cache 20 min
Step #6a Configure ICPS for Interplay MAM 20 min
Step #6b Configure ICPS for Interplay Central 10 min
Step #7 Post-Installation Steps 10 min
Total: 3 hr 10 min
Step #1 Setting Up the HP Server Hardware
In this procedure, you connect the HP DL380/DL360 server to your network, set up its hard disk drives, set the system clock, and disable power saving mode (often enabled, by default).
Connect the ICPS Server to the ISIS and Network
The physical servers must be installed and connected to the ISIS via a Zone 1 (direct) or Zone 2 (through a switch) connection.
Note: This procedure applies to Interplay Central deployments only.
1. For 10GigE connections, use the Myricom 10GigE NIC in PCI slot 4 (see diagram below).
2. For GigE connections, do not use the on-board Broadcom GigE ports. You should have an Intel PROset quad-port GigE NIC in PCI slot 2 (see the diagram below). Connect to the left-most port on that NIC.
Note: For a specific NIC manufacturer and model, please consult and Avid representative.
Connect the ICPS Server to MAM Proxy Storage and Network
In an Interplay MAM deployment, you can use the on-board Broadcomm GigE port to connect to the “house” network. For a 10GigE connection, use a 10GigE NIC of your choosing.
Setting Up the DL380 System Drive Volume
ICPS installs onto the system drive along with the RHEL OS. The DL380 server has a drive cage for up to 16 drives, of which only 2 are currently occupied.
We recommend that you set up a RAID 1 (mirror) volume, using both drives for the system disk, one drive mirroring the other, for redundancy.
Setting Up the DL360 System Drive Volume
ICPS installs onto the system drive along with the RHEL OS. The DL360 server has a drive cage for up to 16 drives, of which 8 are occupied.
The following setup is recommended:
• Set up 2 drives as a RAID 1 (mirror) volume for use as the system disk.
• Set up the remaining 6 drives in a RAID 5 configuration, for use as the ICPS cache.
Setting the System Clock
To ensure the smooth installation of the RHEL OS and ICPS in a later step, set the system clock.
To start the server and access the BIOS to set the system clock:
1. Power up the server.
2. When the console displays the option to enter the Setup menu, press F9.
The Setup utility appears.
3. Choose Date and Time.
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 main menu.
5. Exit the Setup utility (F10) and save.
The server reboots with new options.
Disabling HP DL380/DL360 Power Saving Mode
The HP DL380 is frequently shipped with BIOS settings set to Power-Saving mode. ICPS is CPU and memory intensive processes, especially when under heavy load—you will get much better performance by ensuring that your server is set to operate at Maximum Performance.
Note: You can do this before or after the installation process. We recommend making the change immediately.
To start the server and access the BIOS to check settings:
1. Power up the server.
2. When the console displays the option to enter the Setup menu, press F9.
The Setup utility appears.
3. Choose Power Management Options.
Power Management options appear.
4. Choose HP Power Profile.
Power Profile options appear.
5. Choose Maximum Performance.
You are returned to the HP Power Profile options.
6. Press Esc to return to main menu.
7. Exit the Setup utility (F10) and save.
The server reboots with new options.
Step #2 Installing the RHEL and ICPS Software Components
In this procedure, you copy the RHEL OS installation media to the ICPS installation USB key, and then install both the RHEL OS and the ICPS software components in one continuous step.
Preparing the ICPS USB Key
Installing ICPS requires a bootable USB key with all the files required for installing ICPS.
If instead of an ICPS installation USB key you only have the ICPS installation ZIP file, prepare a USB key using the following steps.
To prepare the ICPS USB key:
1. Procure an 8GB USB key.
2. Format the USB key as a FAT32 volume.
3. Get the ICPS software installation package file, USB_v1.2.zip.
4. Unzip the file into a unique directory.
Copying Red Hat Enterprise Linux OS Media to the ICPS USB Key
Follow this procedure only if you are installing ICPS software components on an HP DL380/DL360 server. To complete this procedure, make sure you have:
• A Windows computer
• RHEL 6.0 OS installation DVD or .iso
Avid does not redistribute the RHEL system media on the ICPS installation USB key. You must download the installation .iso file from Red Hat directly—or get it from the RHEL Installation DVD that comes with your server—then copy the .iso file to the USB key Avid provides for ICPS installation.
Note: Only RHEL 6.0 OS is supported. Do not install patches, updates, or upgrade to RHEL 6.1.
To copy the RHEL OS .iso file to the USB key:
1. Log into a Windows laptop or desktop.
2. Make sure the RHEL 6.0 .iso file is accessible locally (preferable) or over the network from your computer
Note: If you don’t have the RHEL 6.0 installation .iso or a RHEL installation DVD from which to create one, log into rhn.redhat.com using your account credentials and
download the .iso. Remember to download the 6.0 version—6.1 or later is not supported.
3. Browse Windows Explorer to the USB key volume.
4. Double-click iso2usb.exe to launch the application.
5. Choose the Diskimage radio button then browse to the .iso file.
6. Verify the Hard Disk Name and USB Device Name are correct:
• Hard Disk Name: sda
• USB Device Name: sdb
Note: If you will be configuring the DL360/DL380 with a separate cache volume, the USB device name will be sdc instead.
7. In the “Additional Files” field browse to the directory where you unzipped the USB_v1.2.zip file.
8. Click OK.
9. A process begins to copy the .iso file to the USB key. This process will take 5-10 minutes.
Once it is complete, the USB key has everything it needs for a complete RHEL and ICPS installation process.
Note: Copying the RHEL 6.0 OS .iso file to the USB key is a one-time process. If you ever have to re-install ICPS, you do not need to repeat these steps.
Booting the Server from the USB Key and Running the Installer
If you are installing ICPS on an HP DL360/DL360, the installation process installs RHEL and ICPS software components.
To boot the server from the USB key and run the installer:
1. Before powering on the server, insert the USB key.
2. Power on the server.
3. Wait for the Welcome screen to appear.
The first option in the list, Install and upgrade an existing system, is selected.
4. Press Enter.
The option is used automatically if you do nothing and wait 60 sections. The RHEL packages are installed—this takes 5-10 minutes.
When the process is complete, you are prompted to reboot.
5. Do not press Enter! Remove the USB key from the server.
If you reboot without removing the USB key the server will reboot from the USB key again. If you pressed Enter by mistake, remove the USB key as quickly as possible (before the system boots up again).
To reboot the server for the first time:
1. Press Enter.
Rebooting the server at this time triggers the first time boot up on the system drive. The
“first boot” screen appears.
2. From the Choose a Tool menu, select Keyboard Configuration. Press Enter.
Choose the Language option for your keyboard.
3. Focus the OK button. Press Enter.
4. Choose the Network Configuration option. Press Enter.
5. If you are setting up a cluster of ICPS servers or if you want to set up a static IP, choose the Device Configuration option.
Static IP is required when setting up a load balanced cluster of servers. Press Enter.
A list of network interface ports appears.
6. Choose the device option corresponding to eth0. Press Enter.
7. Enter network device information:
• Keep the default name: eth0
• Keep the default device: eth0
• Disable DHCP (Spacebar)
• Enter the static IP, network, default gateway IP, and DNS servers 8. Select OK. Press Enter.
You are returned to the list of network interface ports.
9. Select Save. Press Enter.
10. Choose the DNS Configuration option. Press Enter.
11. Enter DNS information:
• Enter the hostname: <machine name>
• DNS entries should be carried over from step 7 (if you specified static addresses).
• If you did not enable DHCP, enter the DNS search path domain 12. Select Save & Quit. Press Enter.
13. Select Quit. Press Enter.
You are prompted to login to the server.
To check the date and time:
1. Login as root (i.e. user name = root).
Note: The default root password is Avid123
2. Check the date on the server. Type date and press enter.
The date is displayed, for example: Sun Apr 1 11:03:04 EDT 2012 3. If the date is incorrect, change the date. For example, enter:
date 040211032012
The required format is MMDDHHmmYYYY. (Month-Date-Hour-Minute-Year) 4. When you press enter the reset date is displayed:
Mon Apr 2 11:03:00 EDT 2012
To manually edit the network configuration file:
Due to an artifact of the RHEL 6.0 installation process, “backticks” (`) are often added around entries in the network configuration file. Before leaving network configuration, remove the backticks from around any effected entries.
1. Manually edit the network configuration file in /etc/sysconfig/network-scripts/ifcfg-eth0
The first time you edit the file, it may have duplicate entries and backticks similar to the following example:
DEVICE=eth0
HWADDR=00:26:55:e6:83:e1 NM_CONTROLLED=yes
ONBOOT=yes
DHCP_HOSTNAME=`$HOSTNAME`
ONBOOT=yes
DHCP_HOSTNAME=`$HOSTNAME`
2. Remove the duplicate entries and backticks (e.g. from around the host name).
3. Restart the network service (as root):
/etc/init.d/network restart
Step #3 Set up the High-Availability and Load-Balanced Server Cluster
Redundancy and scale for ICPS can be obtained by setting up a cluster of two or more servers. In a high-availability and load-balanced setup, multiple ICPS servers are exposed using a single IP address. In essence, Interplay Production and Interplay MAM see the cluster as a single machine. Within the cluster, requests for media are automatically distributed to the available nodes.
Properly configured, an ICPS server cluster provides the following:
• Load balancing. All incoming playback connections are routed to a cluster IP address, and are subsequently distributed evenly to the nodes in the cluster.
• High-availability. If any node in the cluster fails, connections to that node will automatically be redirected to another node.
• Shared Cache: The media transcoded by one node in the cluster is immediately available for use by the other nodes.
• Cluster monitoring. You can monitor the status of the cluster by entering a command. If a node fails (or if any other serious problem is detected by the cluster monitoring service), an e-mail is sent to one or more e-mail addresses.
Before you begin, make sure of the following:
• ICPS software components are installed on all servers in the cluster
• All servers are on the network and are assigned IP addresses
• You have an assigned cluster IP address (distinct from the servers in the cluster)
• If your network already uses multicast, IT must issue you a multicast address to avoid potential conflicts. If your network does not use multicast, the cluster can safely use a default multicast address.
Note: Unicast is not supported.
On All Servers in the Cluster
All servers in the cluster must be connected to an Ethernet interface having the same name (eth0 recommended). This may not be the case, by default, for a number of reasons, including systems with multiple network interface cards, re-assignment due to matches in network rules files, or explicit settings in the NIC’s configuration file. Follow these steps to verify the Ethernet interface is correctly named.
1. Ensure the Ethernet NIC device has been assigned to the correct physical port by examining the content of the following rules file:
/etc/udev/rules.d/70-persistent-net.rules
2. Locate the entry for the NIC of interest (the physical card used for clustering), and verify it is assigned to the correct physical port (eth0 recommended):
# PCI device 0x14e4:0x1639 (model) (custom name provided by external tool)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="9c:8e:99:1b:31:d4", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
• model is the NIC model name provided by the manufacturer.
• NAME="eth0" assigns the named (i.e. matched) NIC to the physical port eth0. This same port must be used for each NIC in the cluster.
Note: If you will be making use of port bonding, assign the value of the port bonding interface (e.gbond0) instead. For a discussion of port bonding, see “Configure Port Bonding for Interplay MAM (Optional)” on page 23.
3. Verify that configuration information for the NIC cluster is correct. Examine the contents of the NIC device’s ifcfg-<device> file (e.g. ifcfg-eth0) in the
/etc/sysconfig/network-scripts directory.
The file should look something like this:
DEVICE=eth0
HWADDR=9c:8e:99:1b:31:d4
NM_CONTROLLED=yes
• DEVICE=eth0 specifies the name of the physical Ethernet interface device.
• ONBOOT=yes instructs the OS to bring up the device at boot time. Must be yes.
• BOOTPROTO=static lets you assign IP address of the device explicitly (recommended), or allow the OS to assign of the IP address device dynamically. Can be static
(recommended) or dhcp (system assigned).
If you assign the IP addresses statically you are also required to have IPADDR and NETMASK entries.
4. If there are other NIC devices installed on the server, verify their configuration files to ensure there are no naming conflicts. For example, verify that the value assigned to DEVICE is different for each one.
On One Server in the Cluster
These steps must be completed (as root) on one server in the cluster. It doesn’t matter which server.
1. Do one of the following commands (as root):
• If your network has no other Multicast activity, you can use the default Multicast address with the following command:
/usr/maxt/maxedit/cluster/resources/cluster setup-corosync --setup-corosync-bind-iface=eth0
• If IT issued you a different Multicast address, use the following command:
/usr/maxt/maxedit/cluster/resources/cluster setup-corosync --corosync-bind-iface=eth0 --corosync-mcast-addr="<multicast address>"
• <multicast address> is the multicast address that IT provided for the cluster Note: If you will be making use of port bonding, assign the value of the port bonding interface (e.gbond0) instead. For a discussion of port bonding, see “Configure Port Bonding for Interplay MAM (Optional)” on page 23.
Enter the following command:
/usr/maxt/maxedit/cluster/resources/cluster setup-cluster --cluster-ip="<cluster IP address>" --pingable_ip="<router IP address>" --admin_email="<comma separated e-mail list>"
• <cluster IP address> is the IP address that IT provided for the cluster
• <router IP address> is an IP address that will always be available on the network, for example, a network router’s IP address
• <comma separated e-mail list> is a comma separated list of e-mail addresses to which to send cluster status notifications
On All Other Servers in the Cluster
On all other servers in the cluster, do one of the following commands (as root):
• If your network has no other multicast activity, you can use the default Multicast address with the following command:
/usr/maxt/maxedit/cluster/resources/cluster setup-corosync --corosync-bind-iface=eth0
• If IT issued you a different multicast address, use the following command:
/usr/maxt/maxedit/cluster/resources/cluster setup-corosync --corosync-bind-iface=eth0
--corosync-mcast-addr="<multicast address>"
<multicast address> is the multicast address that IT provided for the cluster.
Note: If you will be making use of port bonding, assign the value of the port bonding interface (e.gbond0) instead. For a discussion of port bonding, see “Configure Port Bonding for Interplay MAM (Optional)” on page 23.
Step #4 Create the Interplay MAM Cache Volume
In this step you create the RAID 5 cache volume for ICPS deployed for Interplay MAM on HP DL360 hardware.
1. Create a disk partition:
fdisk /dev/sdb 2. Create a Physical Disk:
pvcreate --metadatasize=64k /dev/sdb1 3. Create a Volume group
vgcreate -s 256K -M 2 vg_icps_cache /dev/sdb1 4. Obtain the a value for the number of Physical Extents:
vgdisplay vg_icps_cache
A list of properties for the volume groups appear, including the physical extents (PE).
Use this value to create the logical volume (below).
5. Create the Logical Volume
lvcreate -l <available_PEs> -r 1024 -n lv_icps_cache vg_icps_cache
• <available_PEs> is the value obtained above.
6. Format the volume
mkfs.ext4 /dev/vg_icps_cache/lv_icps_cache 7. Add the entry into /etc/fstab:
/dev/mapper/vg_icps_cache-lv_icps_cache /cache ext4 rw 0 0
/dev/mapper/vg_icps_cache-lv_icps_cache /cache ext4 rw 0 0