Pinnacle Systems MediaCentral Platform Services - 2.6 Upgrading Guide

Download

Important Information

Revision History

Date Revised

Changes Made

•

April 19, 2016

• Corrected information related to upgrades involving Media Index.

•

Avid MediaCentral

Platform Services

Upgrading Guide Version 2.6.0

This document is a guide to upgrading to MediaCentral Platform Services (MCS) 2.6.0 from a previous version of MCS or Interplay Central Services (ICS).

Avid recommends that you read all the information in this upgrade guide thoroughly before installing or using the corresponding software release.

Important: Check the Avid Knowledge Base for the latest updates to this guide and all

related documentation for Avid MediaCentral Platform Services.

http://avid.force.com/pkb/articles/en_US/readme/Avid-MediaCentral-Version-2-6-xDocumentation

Note: For a list products qualified for use with MCS 2.6, and the supported RHEL operating system, see the Software Compatibility Matrix on the Avid Knowledge Base

April 25, 2016

March 31, 2016

Added information related to Media Index upgrades.

Added process for Upgrading the ISIS Client Software

• Updates for MCS v2.6 implementation of sharded MongoDB

MediaCentral Services 2.6 Upgrading Guide

Important Information ....................................................................................................................... 1

Revision History .................................................................................................................................. 1

Contents ..................................................................................................................................................... 2

Overview .................................................................................................................................................... 4

How to Use this Guide ............................................................................................................................... 4

Obtaining the Software Packages .............................................................................................................. 4

Operating System ....................................................................................................................................... 5

Upgrading Multi-Zone Deployments ......................................................................................................... 5

Upgrading Media | Index Deployments .................................................................................................... 6

Upgrading the iNEWS Client Version ......................................................................................................... 6

Upgrading the ISIS Client Software ............................................................................................................ 7

Installing or Upgrading the Closed Captioning Service .............................................................................. 8

Upgrading the MediaCentral Distribution Service (MCDS) ........................................................................ 8

An Important Note on SSL Certificates ...................................................................................................... 9

Backing Up and Restoring SSL Private Keys ............................................................................................... 9

Migrating User Settings from UMS to USS During an Upgrade ............................................................... 10

Upgrade Prerequisites ............................................................................................................................. 10

Update Installation versus Full Installation .............................................................................................. 11

Upgrade Paths .......................................................................................................................................... 11

Upgrades for systems already running RHEL 6.5 ................................................................................. 11

Upgrades for systems running RHEL 6.3 .............................................................................................. 11

Upgrades from 1.2.x or 1.3.x to MCS 2.6 ............................................................................................. 11

Upgrading a Single Server RHEL 6.5 System to MCS 2.6 .......................................................................... 12

Installing MediaCentral Platform Services 2.6 ..................................................................................... 12

Upgrading a Cluster RHEL 6.5 System to MCS 2.6 ................................................................................... 16

Identifying the Master, Slave and Load-Balancing Nodes .................................................................... 16

Backing-up the User Database and System Settings ............................................................................ 17

Updating the Media Index Database .................................................................................................... 17

Taking the Cluster Offline ..................................................................................................................... 17

Updating the Cluster ............................................................................................................................ 18

Stopping the RabbitMQ Service and Rebooting the Cluster ................................................................ 20

Verifying the RabbitMQ Cluster ........................................................................................................... 20

Bringing the Corosync Cluster Online ................................................................................................... 21

MediaCentral Services 2.6 Upgrading Guide

Verifying Gluster Volume Permissions ................................................................................................. 24

Removing the Gluster Metadata Cache Replication Volume ............................................................... 25

Upgrading a Single Server RHEL 6.3 System to MCS 2.6 .......................................................................... 26

Backing-up System Settings.................................................................................................................. 26

Installing RHEL 6.5 and MCS 2.6 ........................................................................................................... 26

Restoring System Settings and Migrating the User Database .............................................................. 27

Additional Upgrade Procedures ........................................................................................................... 28

Upgrading a Cluster RHEL 6.3 System to MCS 2.6 ................................................................................... 30

Identifying the Master, Slave and Load-Balancing Nodes .................................................................... 30

Backing Up the System Settings ........................................................................................................... 31

Taking the Cluster Offline ..................................................................................................................... 32

Upgrading the Software ....................................................................................................................... 32

Restoring System Settings and Migrating the User Database .............................................................. 33

Additional Upgrade Procedures ........................................................................................................... 34

Appendix A: Post Upgrade Notes ............................................................................................................. 37

Reconfiguring MCS for Upgrades from ICS 1.7 or Earlier ..................................................................... 37

Reconfiguring MCS for Use with Media Composer | Cloud ............................................................. 37

Reconfiguring MCS for Use with Interplay | MAM ........................................................................... 38

Resetting Layouts After Upgrading from V2.0 to V2.6 ......................................................................... 39

Resetting Layouts After Upgrading from ICS V1.6 or Earlier ................................................................ 39

Appendix B: Mounting and Unmounting a USB Drive ............................................................................. 40

Appendix C: Copying Software to the MCS Server .................................................................................. 42

Copying Software Using WinSCP .......................................................................................................... 42

Copying Software Using a USB Drive .................................................................................................... 43

Appendix D: Deleting the RAID 5 ............................................................................................................. 45

Deleting the RAID 5 on an HP Gen9 ..................................................................................................... 45

Deleting the RAID 5 on an HP Gen8 ..................................................................................................... 46

Deleting the RAID 5 on an Dell Server .................................................................................................. 49

Appendix E: Verifying the Media Index Status ......................................................................................... 53

Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database .............................. 54

Copyright and Disclaimer ......................................................................................................................... 58

Overview

How to Use this Guide

Obtaining the Software Packages

Upgrading to MediaCentral Platform Services (MCS) 2.6 for MediaCentral UX, Media Composer | Cloud, and Interplay | MAM, involves the migration of settings and data along with the software upgrade. Depending on the upgrade path you are faced with, the migration of settings and data is either manual or automated.

Note: Beginning with version 2.0, the term “MediaCentral Platform Services” replaces “Interplay Central Services.”

There are two main upgrade paths to MCS 2.6, depending on the currently installed operating system:

MediaCentral Services 2.6 Upgrading Guide

• RHEL 6.5 – If this is the currently installed OS, the upgrade is non-destructive and

largely automated. Manual back-up of the MCS database and system settings is not required, but recommended.

• RHEL 6.3 and earlier – This upgrade involves a clean installation of RHEL 6.5 and

MCS. Manually backing up the MCS database and system settings before the upgrade and restoring them after the upgrade is complete is mandatory.

When the upgrade path involves a RHEL version change, you must also manually back up any private keys associated with SSL certificates received from a Certificate Authority, if CA-signed certificates are in use. In the case of a cluster, you must manually re-create the cluster and reconfigure Gluster cache replication (if used).

This guide documents the overall upgrade process for the supported upgrade scenarios. It must be used in conjunction with the MediaCentral Platform Services Installation and

Configuration Guide. For clustering, the MediaCentral Platform Services Concepts and Clustering Guide provides valuable information regarding cluster operations and post-

upgrade verification procedures.

For each step in the overall upgrade process, this document offers the following guidance:

• Includes step-by-step instructions for a procedure

- or -

• Cross-references a section in an separate document such as the MediaCentral

Platform Services Installation and Configuration Guide

In the second case, the heading of the relevant section of the document is provided. Since direct page references are unreliable, you must scan the table of contents in that guide to find the heading and page.

Multiple software packages are required to properly install and configure MediaCentral Platform Services. For more information on downloading these packages, see “Obtaining the Software” in the MediaCentral Platform Services Installation and Configuration Guide.

Operating System

Upgrading Multi-Zone Deployments

MCS 2.6 requires Red Hat Enterprise Linux (RHEL) v6.5. In addition, whether performing an upgrade or a full installation, the MCS installer requires the RHEL v6.5 ISO to be mounted, so you must obtain the RHEL 6.5 ISO. This is true, even when performing an upgrade where the operating system does not change.

MediaCentral Services 2.6 Upgrading Guide

For more information on MCS and RHEL version compatibility, see the “

Matrix: Interplay Production and MediaCentral” on the Avid Knowledge Base.

If your deployment is configured for multi-zone, note the following:

• As multi-zone configurations often span WAN (wide area network) environments,

special attention should be paid to ensure that the correct network ports are open between the zones. Review the Avid Networking Port Usage Guide on the

Knowledge Base for more information on the ports required for multi-zone.

• If you are upgrading from MCS v2.3.x or earlier, after the master zone has been

updated, the /opt/avid/cluster/bin/pgpool_remote_start script needs to be run to enable the proper syncing of the user databases between all zones again. Please be aware that the script will restart some services on the systems in the remote zones. After the services are restarted, users will need to sign back into MediaCentral.

• If you are upgrading from MCS v2.3.x or earlier, upgrade slave zones first. If you cannot

bring all zones offline at once, upgrade the slave zone(s) before the master zone.

An upgraded slave zone no longer has access to the centralized user management service (UMS), which is owned by the master zone. Users in the upgraded slave zone can continue to log in using the local, read-only copy of the UMS database. However, new users cannot be added through the slave zone.

Compatibility

Avid

• If you are upgrading from MCS v2.4.0, the master zone must be upgraded first. Once the

master zone has been upgraded, you can upgrade the slave zones in any order. Slave zones running MCS 2.4.0 will continue to be able to access the master zone’s user database and will not be limited to read-only mode as in previous releases.

• If you are upgrading from MCS v2.4.1 or higher, you can upgrade the zones in any order.

Master and slave zones running MCS v2.4.1 and v2.5.x are fully compatible with zones running MCS 2.6.

• If you are upgrading a zone to MCS v2.6 and your multi-zone configuration contains

zones that have already been upgrade to v2.6 and have already been configured for sharded Mongo, make sure to add the new zone to sharded Mongo.

For details, see “Adding a Zone to a Sharded Mongo Multi-Zone Environment” in the MediaCentral Platform Services Installation and Configuration Guide.

Upgrading Media | Index Deployments

Upgrading the iNEWS Client Version

If your deployment is configured for Media Index, note the following:

• If your upgrade includes an index schema migration, note that the process can take

multiple hours to complete on large systems. During this time, indexed searching (with the exception of marker searches) is functional, but slow. Additionally, systems cannot add data to the index through the indexing agents while the migration occurs. Administrators might consider stopping the indexing agents during this period.

• If you are upgrading from MediaCentral v2.1.x or earlier, the indexes are incompatible

with MediaCentral v2.6. Before upgrading to MCS v2.6, you must reset the Media Index configuration and delete the indexes in all zones. Deleting the indexes reverts the index table to a clean (empty) state.

For instructions, see “Upgrading Media Index from v2.0.x or v2.1.x” the Avid Media | Index Configuration Guide.

• If you are upgrading from MediaCentral v2.2.x or v2.3.x, the indexes are compatible

with MediaCentral v2.6 and do not need to be deleted. However, a migration script (

media-index-upgrade.sh) must be run before upgrading to v2.6 to update the

schema to include new features associated with MCS v2.6. Once the system is upgraded to v2.6, a second script ( to complete the process.

avid-acs-mediaindex-indices-migration) must be run

MediaCentral Services 2.6 Upgrading Guide

Details for running the migration scripts are contained in the body of this document.

• If you are upgrading from MediaCentral v2.4.0 or later, the indexes are compatible with

MediaCentral v2.6 and do not need to be deleted. However, a migration script must be run after upgrading to v2.6. The script updates the schema to include new features associated with MCS v2.6.

Details for running the migration script are contained in the body of this document.

• To configure the Production Engine Bus Connector (PEBCo) for Media Index with MCS

v2.6, you must use the Interplay Administrator tool v3.5 or higher.

If your workflow includes integration with Avid iNEWS, ensure your iNEWS system is updated with the iNEWS client version for this release of MCS. See the Avid MediaCentral Platform Services ReadMe for iNEWS client version information. See “Editing SYSTEM.CLIENT.VERSIONS” in the MediaCentral Platform Services Installation and Configuration Guide for instructions on adding the client version to the iNEWS server.

Upgrading the ISIS Client Software

During the MediaCentral Platform Services installation process, a version of the Avid ISIS Client software is automatically installed. However, other versions of the ISIS Client may also be bundled with the installation package. For example, MediaCentral v2.6 pre-installs the ISIS Client v4.7.7 and bundles ISIS Client v5.1.0.

Once the MediaCentral Platform Services upgrade is complete, verify the version of the ISIS Client required for your configuration and upgrade the client if necessary.

MediaCentral Services 2.6 Upgrading Guide

For more information on client version compatibility, see the “

Compatibility Matrix:

Interplay Production and MediaCentral” on the Avid Knowledge Base.

To upgrade the ISIS Client:

1. Navigate to the location of the bundled ISIS Client software:

cd /opt/avid/<path>

For example:

cd /opt/avid/Packages_ISIS51/

2. Use the following command to upgrade the ISIS Client:

rpm -ivh AvidISISClient-<version>.el6.x86_64.rpm

You are not required to uninstall any previous version of the client software. The installer automatically replaces version of the client already installed on the system.

3. Once the ISIS Client is installed, restart the ISIS service:

For a single server:

service avid-isis restart

For a cluster configuration the avid-isis service is restarted through the cluster resource:

crm resource restart AvidAllEverywhere

Note: Upgrading the ISIS client on a cluster might introduce resource fail-counts. Once

the upgrade is complete on all nodes, clear the fail-counts with the crm resource

cleanup <rsc> [<node>]

command.

4. Verify that the installed version of the ISIS Client reports the updated version number:

rpm –qa | grep ISIS

MediaCentral Services 2.6 Upgrading Guide

Installing or Upgrading the Closed Captioning Service

Upgrading the MediaCentral Distribution Service (MCDS)

MCS v2.3 introduced a Closed Captioning Service for use with MediaCentral UX. This service is not included in the MCS software package and requires a separate installation. Follow the steps in this guide to complete the upgrade to MCS v2.6. Once the upgrade is complete, the Closed Captioning Service can be installed or upgraded.

See “PART VIII: INSTALLING THE CLOSED CAPTIONING SERVICE” in the MediaCentral Platform Services Installation and Configuration Guide for upgrade instructions.

Note: If you are upgrading a system that has the Closed Captioning Service (CCS) installed, complete the MCS upgrade and the CCS upgrade before testing the system. Older versions of the CCS might not be compatible with the newer version of MCS and the version mismatch could present issues during testing.

MCDS is used in MediaCentral UX configurations which employ a Send To Playback (STP) workflow. Consult the version compatibility chart on the Avid Knowledge Base for the correct version of MCDS for your installation and upgrade the software if necessary.

http://avid.force.com/pkb/articles/en_US/compatibility/Avid-Video-Compatibility-Charts

To upgrade the MediaCentral Distribution Service:

1. MCDS could be in one or more locations within your environment. Use the following

process to verify where MCDS is installed:

a. Log into MediaCentral UX as a user with Administrator privileges.

See “Logging into MediaCentral” in the MediaCentral Platform Services Installation and Configuration Guide for additional information.

b. Select System Settings from the Layout selector. c. In the Settings pane, select Interplay | Production. d. Make note of the MCDS Service URL. This field lists the location or locations

where MCDS has been installed.

e. Log out of MediaCentral UX and close the browser.

2. On the system or systems where MCDS has been installed, use the “Programs and

Features” Control Panel to uninstall MCDS.

Note: MCDS v3.3 and higher are 64 bit applications. Prior 32 bit versions of MCDS must be manually removed to avoid the installation of multiple versions on the same system.

3. If upgrading from a 32 bit version of MCDS, navigate to C:\Program Files (x86)\Avid\ and

delete the residual “MediaCentral Distribution Service” folder.

4. Install the updated version of MCDS.

5. Repeat this process if you need to upgrade MCDS on a second host system.

MediaCentral Services 2.6 Upgrading Guide

An Important Note on SSL Certificates

Backing Up and Restoring SSL Private Keys

MediaCentral uses the Secure Sockets Layer (SSL) for its server to browser connections.

MediaCentral Platform Services v2.5 uses a different SSL certificate format than found in previous releases. If you are upgrading to MCS v2.5 or later and using a Self-Signed or Trusted-CA certificate, refer to the following article on the Avid Knowledge Base to create or in some cases upgrade your SSL certificate:

http://avid.force.com/pkb/articles/en_US/how_to/SSL-Certificates-for-server-to-browserconnections

Note: Changes to the application.properties file (/opt/avid/etc/avid/avid-interplaycentral/config/application.properties) required for Jetty certificates in MCS 2.4 and earlier are no longer required. If desired, the changes can be reverted after the upgrade to MCS 2.5 or higher. Alternatively, the application.properties file can remain unaltered and the Jetty certificate information will be ignored.

Upgrading can be a “true” (non-destructive) upgrade, or can involve a fresh install of RHEL. For fresh installs, the system-backup script has been provided to back up and restore system settings related to MCS, including SSL data (the certificate and associated private key).

However, if you are using a Trusted CA-signed Certificate, a private key (site.key or jettyPrivateKey.key) file was created during the certificate creation process. The procedure suggests that you back up this file in a safe place, such as the root user home directory (

/root) directory. If you are performing a fresh install of RHEL, be sure to back up this

private key to an external location before performing the upgrade. Backing up private key files is good practice, whatever the type of upgrade being performed.

Note: If the private key was not backed up elsewhere, it is doubly important to back up the file before performing the upgrade. The private key is used to generate Certificate Signing Requests (CSRs).

For instructions on creating and installing SSL certificates see the following article:

http://avid.force.com/pkb/articles/en_US/how_to/SSL-Certificates-for-server-to-browserconnections

To back up and restore the private key file:

1. Locate the private key file used to generate the Certificate Signing Request (if any).

The default name is site.key for MCS 2.5 and later or jettyPrivateKey.key for MCS 2.4 and earlier. During its creation, it was suggested you store it in the following directory:

/root

2. Copy the private key to a safe location (off the MCS server).

3. If applicable, restore the key at the appropriate step in the upgrade.

MediaCentral Services 2.6 Upgrading Guide

Migrating User Settings from UMS to USS During an Upgrade

Upgrade Prerequisites

MediaCentral 2.0 introduced a new user database scheme. Upgrades of systems prior to 2.0 need to complete a user database migration using the supplied avid-uss-import script.

• For upgrades from 1.8.0 (RedHat 6.3) or earlier, a backup and restore of the MCS

database is required. The user database migration must be completed after restoring the MCS database, but before logging in via the MediaCentral | UX user interface.

• For upgrades from 1.8.1 (RedHat 6.5), a backup and restore of the MCS database is

not required. However, the avid-uss-import script must still be run before logging in via the MediaCentral | UX user interface.

Note: In a cluster, the user database migration script must be run once on the master node only.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details on the backup and restore procedure. Procedures for using the avid-uss-import script are covered in

Upgrades for systems running RHEL 6.3.

Before starting any MCS upgrade, it is important to ensure you have a healthy environment. Verify the following as appropriate:

 (All configurations) Ensure you can log into MediaCentral UX via a web browser and

verify basic functionality.

 (Cluster configurations) Verify the status of RabbitMQ and the ACS Bus.

See “Verifying the Status of RabbitMQ” in the MediaCentral Platform Services Installation and Configuration Guide for details.

See “Verifying ACS Bus Functionality” in the MediaCentral Platform Services Installation and Configuration Guide for details.

 (Cluster configurations) Verify the status of the Corosync cluster. Ensure there are no

errors.

See “Cluster Resource Monitor” in the MediaCentral Platform Services Concepts and Clustering Guide for details.

 (Multi-zone configurations) Verify that the “Zones” section of the MediaCentral UX

System Settings layout displays all expected zones with no errors.

See “Troubleshooting the Multi-Zone Setup” in the MediaCentral Platform Services Installation and Configuration Guide for details.

MediaCentral Services 2.6 Upgrading Guide

Update Installation versus Full Installation

Upgrade Paths

Upgrades for systems already running RHEL 6.5

Upgrades for systems running RHEL 6.3

Upgrades from 1.2.x or 1.3.x to MCS 2.6

For MCS systems already operating under RHEL v6.5, the upgrade process is fairly straight forward and requires a minimal amount of time to complete.

For older versions of ICS or MCS operating under RHEL v6.3, the upgrade to MCS 2.6 is closer to a new installation than it is to an upgrade. The process involves using the MCS Installation USB Drive to reimage the server and complete a fresh installation of MCS. Because of this, extra care must be taken to ensure the MCS system settings and user database are preserved.

This section presents the upgrade paths for specific deployment options.

For upgrading instructions:

• Upgrading a Single Server RHEL 6.5 System to MCS 2.6 on page 12

• Upgrading a Cluster RHEL 6.5 System to MCS 2.6 on page 16.

For upgrading instructions:

• Upgrading a Single Server RHEL 6.3 System to MCS 2.6 on page 26

• Upgrading a Cluster RHEL 6.3 System to MCS 2.6 on page 30.

For Interplay Central and / or ICPS 1.2.x and 1.3.x upgrade options, please consult your Avid representative.

MediaCentral Services 2.6 Upgrading Guide

Upgrading a Single Server RHEL 6.5 System to MCS 2.6

Installing MediaCentral Platform Services 2.6

Installing MCS v2.6 on a single server already operating under RHEL 6.5 is a simple automated update of the affected packages. All MCS system settings are preserved.

Expected downtime: 30 min.

Note: Prior to upgrading, ensure you have verified the

Upgrade Prerequisites on page 10.

1. Prepare the v2.6 MCS Installation USB Drive and connect it to your MCS server.

It is necessary to upgrade the system using the MCS Installation USB Drive as it contains the RHEL 6.5 ISO required for the upgrade process.

See “Creating the MCS Installation USB Drive” in the MediaCentral Platform Services Installation and Configuration Guide for details.

2. Mount the USB drive and change to the USB mount point.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

3. Although the upgrade is non-destructive, it is a good idea to back-up the MCS database.

This is an optional, but recommended step.

Back up the MCS settings and database using the backup script:

./system-backup.sh –b

” for details.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for additional details.

4. (Media Index configurations only) If you are upgrading from MCS v2.2.x or v2.3.x and

Media Index has been configured on your system, you need to run a schema migration script before upgrading the MCS software.

a. Prior to running the migration script, review the information in

Appendix E:

Verifying the Media Index Status to verify that no active schema migration is

currently affecting Media Index.

b. Once you have verified the status, run the migration script from the root of the

MCS Installation USB Drive:

./media-index-upgrade.sh

This script will update the indexes to be compatible with the MCS v2.6 index structure.

Note: The elasticsearch service must be running for this script to complete the migration tasks.

MediaCentral Services 2.6 Upgrading Guide

5. Start the installation script:

./install.sh

Note: Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the installation script in the current directory. Otherwise you will receive the following error message:

-bash: install.sh: command not found

If you are upgrading from MCS v2.2.x or v2.3.x and your system is configured for Media Index, you will receive a message indicating that “A Media | Index configuration has been detected on this system”. Select one of the following options:

• Type

IGNORE if you have already upgraded your Media | Index data or want to

upgrade your system without completing the migration.

• Type

QUIT if you have not yet upgraded your Media | Index data and need to exit

the installer.

During the installation process, progress is displayed. The update completes with an indication of success:

INSTALLATION FINISHED

If any errors were encountered during the upgrade, you can obtain more information in the installation log at:

/var/log/MediaCentral_Services_<version>_Build_<number>_Linux.log

6. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.6.x.x ICPS Version: 2.6.x.x ICPS manager Version: 2.6.x.x ACS Version: 2.6.x.x System ID: "xxxxxxxxxxx"

ICS installer: 2.6 (Build xx) Created on <installer creation date>

Note: Starting with MediaCentral v2.6, the ics_version command includes additional information on multi-zone, Media Index, MAM Connector and other components. For precise version numbers, see the Avid MediaCentral Platform Services 2.6 ReadMe.

Note: If you receive a “command not found” error, logout and log back into the server or SSH

session (PuTTY). This will refresh the login for the upgraded system and should allow the command to run properly.

7. Unmount the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

MediaCentral Services 2.6 Upgrading Guide

8. (Multi-Zone configurations only) If you are upgrading from MCS v2.3.x or earlier, once

the master zone has been updated, run the following script from the master zone to reenable the database syncing between all zones:

/opt/avid/cluster/bin/pgpool_remote_start

This step is not required and should not be completed if upgrading from MCS 2.4 or higher.

9. The MediaCentral v2.6 upgrade process installs ISIS Client v4.7.7 by default. However,

ISIS Client v5.1 is bundled with the release for sites that need to connect to ISIS 1000 systems. If your system requires a connection to ISIS 1000, follow the instructions for

Upgrading the ISIS Client Software on page 7

10. If additional components (e.g. Closed Captioning Service, MAM Connector, Media

Distribute, etc.) require updating, complete those upgrades at this time. Failure to upgrade previously installed components may result in unexpected errors when testing the system.

11. (Media Index configurations only) Depending upon your upgrade path, additional steps

are required to complete the installation. Review the following:

• If you upgraded from MCS v2.4.x or v2.5.x, a migration script must be run to update

the schema to include new features associated with MCS v2.6.

a. Review the information in Appendix E: Verifying the Media Index Status

verify that no active schema migration is currently affecting Media Index.

b. Once you have verified the status, type the following to run the migration

script:

/opt/avid/media-index/avid-acs-media-indexmigration/avid-acs-mediaindex-indices-migration

• If you upgraded from MCS v2.2.x or v2.3.x, a migration script (media-index-

upgrade.sh

(

avid-acs-mediaindex-indices-migration) must now be run to complete

) was run prior to the upgrade. However, a second migration script

the process.

a. Review the information in Appendix E: Verifying the Media Index Status

verify that no active schema migration is currently affecting Media Index.

b. Once you have verified the status, type the following to run the migration

script:

/opt/avid/media-index/avid-acs-media-indexmigration/avid-acs-mediaindex-indices-migration

• If you upgraded from MCS v2.1.x or earlier, the Media Index configuration was reset

and a data migration is not required. However, the Media Index configuration must be reconfigured at this time.

For instructions on reconfiguring Media Index, see “Upgrading Media Index from v2.0.x or v2.1.x” the Avid Media | Index Configuration Guide.

MediaCentral Services 2.6 Upgrading Guide

12. (Media Index configurations only) Systems configured with Media Index for MAM that

have upgraded from MCS v2.4.x or v2.5.x must re-sync the legal list using the MAM CentralSyncAgent to resend dictionary data to the Media Index.

For more information on using the Interplay MAM Sync Service Administrator, see “Setting Up Interplay | MAM Sync Service” the Avid Media | Index Configuration Guide or reference the Interplay | MAM Sync Service Administrator User’s Guide.

13. Once the upgrade is complete, you should verify basic functionality. For more

information, see “PART VII: VERIFYING THE INSTALLATION” of the MediaCentral Platform Services Installation and Configuration Guide.

14. (Multi-Zone configurations only) Once the system has been fully upgraded and tested,

reconfigure the multi-zone configuration for the MCS v2.6 implementation of Mongo.

If you are running a multi-zone configuration consisting of zones with mixed software versions, only zones that have been upgraded to MCS 2.6 can exist in a sharded Mongo configuration. Any zones that are not upgraded at this time, can be added to the Mongo configuration after they have been upgraded to v2.6 at a later date.

For more information, see “PART VI: SHARDED MONGO” in the MediaCentral Platform Services Installation and Configuration Guide.

MediaCentral Services 2.6 Upgrading Guide

Upgrading a Cluster RHEL 6.5 System to MCS 2.6

Identifying the Master, Slave and Load-Balancing Nodes

Installing MCS 2.6 on a cluster already operating under RHEL 6.5 involves an automated update of the affected packages. All MCS system settings are preserved. All nodes must be taken offline to perform the update.

The cluster upgrade involves the following steps:

 Identifying the Master, Slave and Load-Balancing Nodes  (optional) Backing-up the User Database and System Settings  (Media Index only) Updating the Media Index Database  Taking the Cluster Offline  Updating the Cluster  Stopping the RabbitMQ Service and Rebooting the Cluster  Verifying the RabbitMQ Cluster  Bringing the Corosync Cluster Online  (if applicable) Verifying Gluster Volume Permissions  (if applicable) Removing the Gluster Metadata Cache Replication Volume

Expected downtime: 1 hr. for 2 servers, + 30 min. for each additional server.

Note: Prior to upgrading, ensure you have verified the

Upgrade Prerequisites on page 10.

There are three types of nodes in a cluster: master, slave, and load-balancing. The master “owns” multiple resources such as the cluster IP address. The slave assumes the role of master in the event of a failover. Additional nodes play a load-balancing role, but can never take on the role of master.

To identify the master, slave, and load-balancing nodes:

1. Verify the current role of each node in the cluster through the Cluster Resource

Monitor. Log in to any machine in the cluster as the root user and type:

crm_mon

2. To identify the master and slave nodes, look for the line containing “Master/Slave Set”.

For example:

Master/Slave Set: ms_drbd_postgres [drbd_postgres] Masters: [ wavd-mcs01 ] Slaves: [ wavd-mcs02 ]

In this example, the master node is wavd-mcs01 and the slave node is wavd-mcs02.

3. To identify the load-balancing nodes, look for the line containing “Clone Set”.

For example:

Clone Set: AvidAllEverywhere [AvidAll] Started: [ wavd-mcs01 wavd-mcs02 wavd-mcs0 wavd-mcs04]

In this example, the load-balancing nodes are wavd-mcs03 and wavd-mcs04.

4. Exit crm_mon by pressing CTRL-C on the keyboard.

MediaCentral Services 2.6 Upgrading Guide

Backing-up the User Database and System Settings

Updating the Media Index Database

Taking the Cluster Offline

Although the upgrade is non-destructive, it is a good idea to back-up the MCS database. This is an optional, but recommended step.

To back up the database and settings:

1. Prepare the v2.6 MCS Installation USB Drive and connect it to the cluster master node.

See “Creating the MCS Installation USB Drive” in the MediaCentral Platform Services Installation and Configuration Guide for details.

2. Mount the USB drive and change to the mount point.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

3. Back up the current system settings and MCS database using the backup script.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for additional details.

4. Repeat this process for the slave node and all load balancing nodes.

” for details.

(Media Index configurations only) If you are upgrading from MCS v2.2.x or v2.3.x and Media Index has been configured on your system, you need to run a schema migration script prior to upgrading the MCS software. The script can be run from any cluster node and must be run while the cluster is online.

To run the Media Index migration script:

1. Review the information in Appendix E: Verifying the Media Index Status

no active schema migration is currently affecting Media Index

2. Once you have verified the status, run the migration script from the root of the MCS

Installation USB Drive:

to verify that

./media-index-upgrade.sh

This script will update the indexes to be compatible with the MCS v2.6 index structure.

Note: The elasticsearchEverywhere cluster resource must be running for this script to complete the migration tasks.

Corosync and RabbitMQ maintain independent clustering mechanisms. Corosync clusters operate in a master/slave relationship whereas RabbitMQ clusters run in an Active/Active state where any node in the cluster could be the owner of a RabbitMQ “queue”. This means that the order in which the nodes disconnect and reconnect to the RabbitMQ cluster is particularly important.

Note: Take care to note the order in which nodes are taken offline. The node that is “last down” must be the node that is “first up”. Failure to do so may break the RabbitMQ cluster.

MediaCentral Services 2.6 Upgrading Guide

Updating the Cluster

Note: If you are upgrading from MCS v2.2.x or v2.3.x and Media Index has been configured on your system, complete the schema migration prior to taking the cluster offline. See

Upgrading Media | Index Deployments

for details.

In the following process, you will put each node of the Corosync cluster into “standby” and you will stop the RabbitMQ service to pause its clustering functionality. Complete this process one node at a time, waiting 30 seconds between each node. Avid recommends starting with the final node first.

To bring the cluster into standby mode:

1. Begin by putting the Corosync load-balancing nodes into standby mode and stopping

the rabbitmq service. Complete this process one node at a time, waiting 30 seconds between each node:

crm node standby <node name> service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

2. Wait 30 seconds and put the Corosync slave node into standby:

crm node standby <node name> service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

3. Wait 30 seconds and put the Corosync master node into standby:

crm node standby <node name> service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

Upgrade the nodes in the reverse order that you stopped the services. Start with the Corosync master node, followed by the slave node and finally the load balancing nodes.

To update the cluster:

1. If you have not already done so, prepare the v2.6 MCS Installation USB Drive and

connect it to your first MCS server.

It is necessary to upgrade the system using the MCS Installation USB Drive as it contains the RHEL 6.5 ISO required for the upgrade process.

See “Creating the MCS Installation USB Drive” in the MediaCentral Platform Services Installation and Configuration Guide for details.

2. Mount the USB drive and change to the mount point.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

” for details.

MediaCentral Services 2.6 Upgrading Guide

3. Start the installation script.

./install.sh

Note: Be sure to use the dot-slash (“./”) notation, which tells Linux to look for the installation script in the current directory. Otherwise you will receive the following error message:

-bash: install.sh: command not found

If you are upgrading from MCS v2.2 or v2.3 and your system is configured for Media Index, you will receive a message indicating that “A Media | Index configuration has been detected on this system”. Select one of the following options:

• Type

IGNORE if you have already upgraded your Media | Index data or want to

upgrade your system without completing the migration.

• Type

QUIT if you have not yet upgraded your Media | Index data and need to exit

the installer.

During the installation process, progress is displayed. The update completes with an indication of success:

INSTALLATION FINISHED

If any errors were encountered during the upgrade, you can obtain more information in the installation log at:

/var/log/MediaCentral_Services_<version>_Build_<number>_Linux.log

4. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.6.x.x ICPS Version: 2.6.x.x ICPS manager Version: 2.6.x.x ACS Version: 2.6.x.x System ID: "xxxxxxxxxxx"

ICS installer: 2.6 (Build xx) Created on <installer creation date>

Note: Starting with MediaCentral v2.6, the ics_version command includes additional information on multi-zone, Media Index, MAM Connector and other components.

For

precise version numbers, see the Avid MediaCentral Platform Services 2.6 ReadMe.

Note: If you receive a “command not found” error, logout and log back into the server or SSH

session (PuTTY). This will refresh the login for the upgraded system and should allow the command to run properly.

5. Unmount the USB drive, proceed to the next node, and follow the same pattern: a. Mount the MCS 2.6 Installation USB drive b. Run the update script c. Verify the ics_version output d. Unmount the USB drive

MediaCentral Services 2.6 Upgrading Guide

Stopping the RabbitMQ Service and Rebooting the Cluster

Verifying the RabbitMQ Cluster

6. If additional components (e.g. Closed Captioning Service, MAM Connector, Media

Distribute, etc.) require updating, complete those upgrades at this time. Failure to upgrade previously installed components may result in unexpected errors when testing the system.

Installing the software update restarted the RabbitMQ service. The services need to be stopped again before rebooting the cluster.

Prior to completing this process, note the following:

• If you are upgrading from MCS v2.2.3 or earlier, this process is required.

• If you are upgrading from MCS v2.2.4 or later, this process can be skipped.

To stop RabbitMQ and reboot the cluster:

1. Stop the RabbitMQ services on the final load-balancing node:

service rabbitmq-server stop

Example: If you have four cluster nodes, number 4 is the “final” load-balancing node.

2. Waiting 30 seconds between each node, stop the RabbitMQ services on the next load-

balancing node, then the slave node and finally the master node.

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

3. Once the RabbitMQ services have been stopped on each node, all nodes in the cluster

must be rebooted. The order in which the nodes are rebooted is important to ensure RabbitMQ starts successfully. Begin by rebooting the master node:

reboot <master node name>

4. Waiting 30 seconds between each node, reboot the slave node and each load-balancing

node.

reboot <node name>

5. Once all nodes have been rebooted and RabbitMQ has been started on each node,

verify the status of the RabbitMQ cluster.

Prior to restoring the Cosrosync cluster, you should first verify that the RabbitMQ cluster is functioning normally. Complete the following two steps on each cluster node.

Note: The RabbitMQ cluster must be healthy prior to bringing the Corosync cluster back online. If you suspect there is a problem, see the following Avid Knowledge Base article for assistance:

http://avid.force.com/pkb/articles/en_US/troubleshooting/RabbitMQ-cluster-troubleshooting

MediaCentral Services 2.6 Upgrading Guide

Bringing the Corosync Cluster Online

To verify the status of RabbitMQ:

1. Verify the status of the RabbitMQ service:

service rabbitmq-server status

The command will return a detailed string of data regarding the service. Example (partial only):

[root@mcs-1 ~]# service rabbitmq-server status Status of node 'rabbit@mcs-1' ... [{pid,2064}, {running_applications, [{rabbitmq_federation_management,"RabbitMQ Federation

Management","3.3.5"},

{rabbitmq_management,"RabbitMQ Management Console","3.3.5"},

Review the output of the command and verify there are no obvious error messages such as “

service is dead but pid (xxxxx) is running”.

2. Check the RabbitMQ cluster with the “rabbitmqctl cluster_status” command:

rabbitmqctl cluster_status

The following is an example of a 2-node cluster:

Cluster status of node 'rabbit@node-n1’ ... [{nodes,[{disc,['rabbit@node-n1','rabbit@node-n2']}]}, {running_nodes,[ 'rabbit@node-n1','rabbit@node-n2']}, {cluster_name,<<"rabbit@node-n1">>}, {partitions,[]}]

The command should return information about each of the RabbitMQ cluster nodes. All available nodes should appear on both the “nodes” and “running_nodes” lines.

Verify that each node reports the same information about the RabbitMQ cluster (all nodes are known and running).

Note:

The RabbitMQ cluster must be healthy prior to bringing the Corosync cluster back online. If you suspect there is a problem, see the following Avid Knowledge Base article for assistance:

http://avid.force.com/pkb/articles/en_US/troubleshooting/RabbitMQ-cluster-troubleshooting

The final step in the process is to bring the Cosrosync cluster back online and verify that the cluster is functioning normally.

To bring the cluster back online:

1. Reactivate the cluster by running the following command on the master node only:

/opt/avid/cluster/bin/reactivate-cluster

The script will begin collecting information about your system.

MediaCentral Services 2.6 Upgrading Guide

2. The script creates a backup copy of the cluster configuration file. If you have previously

upgraded your MCS server, a configuration backup file already exists. You are asked to confirm that you want to overwrite this backup file:

File /root/ics_cluster_config_reinit.bak exists. Do you want to overwrite it (y/n)?

Enter “y” to proceed.

3. A list of configuration settings will appear on the screen. You are asked to confirm these

settings:

Do you wish to apply these settings? y/n

Enter “y” to proceed.

Be patient as the script brings all nodes back online.

Note: If after running the reactivate-cluster script you observe that a node is the state of “Offline - Unclean Node”, restart Pacemaker on that node.

If the reactivate-cluster command does not bring all nodes back online, you can complete the process manually. For example, to bring the master node back online:

crm node online <node name>

Wait 30 seconds and bring the slave node back online:

crm node online <node name>

If applicable, bring the load-balancing nodes back online:

crm node online <node name>

4. Start the Cluster Resource Monitor to verify the cluster status:

crm_mon -f

• Verify the master, slave, and load-balancing nodes have rejoined the cluster, as

expected.

• Review the fail counts for the following resources (at a minimum): AvidIPC,

AvidUMS, AvidACS, pgsqlDB.

5. If failures are listed, run the cluster resource manager cleanup command to reset them:

crm resource cleanup <rsc> [<node>]

<rsc> is the resource name of interest: AvidIPC, AvidUMS, AvidACS, pgsqlDB (or another)

<node> (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. Repeat the command using the group name 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

MediaCentral Services 2.6 Upgrading Guide

6. (Media Index configurations only) If you are upgrading from MCS v2.2 or higher, you

must run the following script to restart the appropriate services:

/opt/avid/cluster/bin/search-cluster rsc-start

This command only needs to be run once on any node in the cluster.

7. (Multi-Zone configurations only) If you are upgrading from MCS v2.3.x or earlier, once

the master zone has been updated, run the following script from the Master node of the cluster in the Master zone to re-enable the database syncing between all zones.

/opt/avid/cluster/bin/pgpool_remote_start

This step is not required and should not be completed if upgrading from MCS 2.4 or higher.

8. The MediaCentral v2.6 upgrade process installs ISIS Client v4.7.7 by default. However,

ISIS Client v5.1 is bundled with the release for sites that need to connect to ISIS 1000 systems. If your system requires a connection to ISIS 1000, follow the instructions for

Upgrading the ISIS Client Software on page 7

9. (Media Index configurations only) Depending upon your upgrade path, additional steps

are required to complete the installation. Review the following:

• If you upgraded from MCS v2.4.x or v2.5.x, a migration script must be run to update

the schema to include new features associated with MCS v2.6.

a. Review the information in Appendix E: Verifying the Media Index Status to

verify that no active schema migration is currently affecting Media Index.

b. Once you have verified the status, type the following to run the migration script:

/opt/avid/media-index/avid-acs-media-index-migration/avidacs-mediaindex-indices-migration

• If you upgraded from MCS v2.2.x or v2.3.x, a migration script (media-index-

upgrade.sh

(

avid-acs-mediaindex-indices-migration) must now be run to complete

) was run prior to the upgrade. However, a second migration script

the process.

a. Review the information in Appendix E: Verifying the Media Index Status

verify that no active schema migration is currently affecting Media Index.

b. Once you have verified the status, type the following to run the migration script:

/opt/avid/media-index/avid-acs-media-index-migration/avidacs-mediaindex-indices-migration

• If you upgraded from MCS v2.1.x or earlier, the Media Index configuration was reset

and a data migration is not required. However, the Media Index configuration must be reconfigured at this time.

For instructions on reconfiguring Media Index, see “Upgrading Media Index from v2.0.x or v2.1.x” the Avid Media | Index Configuration Guide.

10. (Media Index configurations only) Systems configured with Media Index for MAM that

have upgraded from MCS v2.4.x or v2.5.x must re-sync the legal list using the MAM CentralSyncAgent to resend dictionary data to the Media Index.

MediaCentral Services 2.6 Upgrading Guide

Verifying Gluster Volume Permissions

11. Once the upgrade is complete, you should verify basic functionality. For more

information, see “PART VII: VERIFYING THE INSTALLATION” of the MediaCentral Platform Services Installation and Configuration Guide.

12. Once the system has been fully upgraded and tested, reconfigure the configuration for

the MCS v2.6 implementation of Mongo. This step is required for all upgrade paths.

For more information, see “PART VI: SHARDED MONGO” in the MediaCentral Platform Services Installation and Configuration Guide.

Note: If you are running a multi-zone configuration consisting of zones with mixed software versions, only zones that have been upgraded to MCS 2.6 can exist in a sharded Mongo configuration. Any zones that are not upgraded at this time, can be added to the Mongo configuration after they have been upgraded to v2.6 at a later date.

The process below was added to the v2.2.0 MediaCentral Platform Services Installation and Configuration Guide. Depending on when your system was installed, permissions for some

Gluster volumes may or may not have been set correctly. If you have upgraded from a system running MCS 1.8.1, MCS 2.0.x or MCS 2.1.x, complete the following procedure. If you have upgraded from MCS 2.2 or higher, this process should have already been completed and is not required.

The following 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

These directories are associated with RHEL directories (/cache/download and /cache/fl_cache) used to store files for http-based streaming, such as media converted to FLV for file-based playback. They are also used to store media converted to Mpeg2TS for playback on iOS devices. The download directory contains links to simplify iOS playback.

Restarting the Gluster daemon (glusterd) results in user ID and group ownership of the Gluster volumes being changed from maxmin to root, which breaks playback on iOS devices. Thus if a cluster node is rebooted, playback issues can arise.

To prevent issues for an existing cluster, you must configure the two Gluster cache volumes to use the same UID and GID as the maxmin user, as described in the following procedure.

To set Gluster volume ownership so it does not change:

On each node in the cluster perform the following steps (all nodes, one at a time in any order):

1. Obtain the user ID (uid) of the user maxmin (this might be different on each machine):

id -u maxmin

2. Change the user ownership of the gluster volume to maxmin using the user ID:

gluster volume set gl-cache-dl storage.owner-uid <uid> gluster volume set gl-cache-fl storage.owner-uid <uid>

MediaCentral Services 2.6 Upgrading Guide

Removing the Gluster Metadata Cache Replication Volume

In the above commands, do not type the angle brackets. Enter the number obtained in the previous step.

Note: Do not alter the gl-cache-mcam (multicam) volume. It uses the default root ownership.

3. Obtain the group ID (gid) of the user maxmin (this might be different on each machine):

id -g maxmin

4. Change the group ownership of the gluster volume to maxmin using the group ID:

gluster volume set gl-cache-dl storage.owner-gid <gid> gluster volume set gl-cache-fl storage.owner-gid <gid>

Note: Do not alter the gl-cache-mcam (multicam) volume. It uses the default root ownership.

5. 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

6. Restart the GlusterFS service:

service glusterd restart

7. Verify the ownership changes are sticky:

ls –la /cache/gluster

Should return same as before:

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. Change ownership of any files residing in gluster_data_download and

gluster_data_fl_cache:

chown –R maxmin:maxmin /cache/gluster/gluster_data_download chown –R maxmin:maxmin /cache/gluster/gluster_data_fl_cache

If you are upgrading from MCS 2.0, additional configuration steps might be required. As part of some cluster deployments, the MediaCentral Platform Services 2.0 Installation and Configuration Guide provided instructions for replicating the cluster file caches using Gluster, an open source software solution. The instructions include creating a metadata cache directory for Interplay | MAM deployments with MPEG-1 browse proxies.

The use of Gluster to replicate metadata has been deprecated due to its negative impact on performance. Please delete the GlusterFS metadata volume from all your server nodes in all affected deployments. Once complete, metadata information is loaded into RAM and is no longer replicated across other nodes.

For instructions, consult the Avid KB article “Removing the GlusterFS Metadata Cache Replication Volume” at the following link:

http://avid.force.com/pkb/articles/en_US/how_to/Removing-the-gluster-metadata-cachereplication-volume

MediaCentral Services 2.6 Upgrading Guide

Upgrading a Single Server RHEL 6.3 System to MCS 2.6

Backing-up System Settings

Installing RHEL 6.5 and MCS 2.6

The upgrade to MCS v2.6 on a RHEL 6.3 system involves a fresh OS and MCS software installation. This process consists of the following procedures:

 Backing-up System Settings  Installing RHEL 6.5 and MCS 2.6  Restoring System Settings and Migrating User Settings  Additional Upgrade Procedures

Note: Before proceeding, back up any private key used to generate a Certificate Signing Request. In this document, see Backing Up and Restoring SSL Private Keys

Expected downtime: 30 min.

As this upgrade requires a re-image of the MCS server, backing-up the system settings is critical to the success of the system upgrade.

1. Prepare the v2.6 MCS Installation USB Drive and connect it to your MCS server.

See “Creating the MCS Installation USB Drive” in the MediaCentral Platform Services Installation and Configuration Guide for details.

2. Mount the USB drive and change to the mount point.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

3. Back up the current system settings and ICS/MCS database using the backup script.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details.

4. Unmount and remove the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

1. Unmount the USB drive (if you have not already done so).

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

2. If your configuration includes a RAID 5 array, delete and recreate the RAID 5.

Destroying and re-creating the RAID 5 eliminates (in advance) any problems with cache permissions that can arise as a result of the RHEL update.

See “Appendix D: Deleting the RAID 5

See “Configuring the Onboard RAID” in the MediaCentral Platform Services Installation and Configuration Guide for details on creating the RAID 5.

” for details on deleting the RAID 5.

MediaCentral Services 2.6 Upgrading Guide

Restoring System Settings and Migrating the User Database

3. Insert the USB drive and boot from it to install RHEL and MCS.

See “Installing RHEL and the MCS Software” in the MediaCentral Platform Services Installation and Configuration Guide for details.

4. Once installed, remove the USB drive and reboot as prompted.

Rebooting after the OS upgrade causes the RHEL Text Mode Setup Utility (“Choose a Tool”) screen to appear, providing access to set-up menus.

5. Quit the RHEL Text Mode Setup Utility and log in to RHEL.

6. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.6.x.x ICPS Version: 2.6.x.x ICPS manager Version: 2.6.x.x ACS Version: 2.6.x.x System ID: "xxxxxxxxxxx"

ICS installer: 2.6 (Build xx) Created on <installer creation date>

Note: If you receive a “command not found” error, logout and log back into the server or SSH

session (PuTTY). This will refresh the login for the upgraded system.

7. Install any RHEL security updates.

See the Avid MediaCentral Platform Services 2.6 ReadMe for more information.

1. Re-insert and re-mount the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

2. Restore the system settings and MCS database using the restore script.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details.

” for details.

Note: It is possible that error messages similar to the following will be output to the shell:

/usr/maxt/maxedit/cluster/resources/_common.sh errors

Ignore the messages, type the following, and press Enter to complete the command:

service avid-all stop

MediaCentral Services 2.6 Upgrading Guide

Additional Upgrade Procedures

You do not need to stop the error messages to type the above command. You can type it even as the error messages are output to the terminal.

3. Unmount and remove the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

4. Reboot and note the restored host name at the login prompt (e.g. wavd-mcs01).

Seeing the original hostname at the login prompt signifies that the system settings were successfully restored.

5. Log in as root and migrate the user settings from the UMS database to the USS database

(new in 2.0):

/opt/avid/bin/avid-uss-import

The system returns the following:

Loading properties.. Fetching zone UUID.. Importing settings for zone UUID: 00000000-0000-0000-0000000000000000 Importing setting_domain_class.. Importing setting_class.. Importing setting_instance.. SUCCESS

The backup and restore procedure saves many system settings which provides the user with a more streamlined upgrade. However, some configuration steps must be manually recreated. Refer to the appropriate section of the MediaCentral Platform Services Installation and Configuration Guide for details on each of these procedures.

1. If your configuration includes a RAID 5, recreate the file cache. See “Creating the File

Cache on the RAID”.

2. Verify the contents of the hosts file. See “Verifying the hosts File Contents”.

3. Verify the date and time settings. See “Configure Date and Time Settings”. a. Though time zone information was restored, you must re-create the symbolic

link RHEL needs to make use of it:

ln –sf /usr/share/zoneinfo/<yourzone> /etc/localtime

If you need to verify the zone in use prior to re-creating the symbolic link:

cat /etc/sysconfig/clock

b. Verify the availability of the in-house NTP server, synchronize the System Clock,

and set up a cron job to keep the clock synchronized.

4. Compare the current and restored filesystem table files “fstab” for changes.

cat /<path>/fstab

• The current “live” filesystem table is located at: /etc/fstab

• The restored filesystem table is located at:

/root/fstab

MediaCentral Services 2.6 Upgrading Guide

The filesystem table cannot be automatically restored to its original location, since some entries are assigned UUIDs dynamically by Linux. These UUIDs can change from one RHEL installation to the next, even if they underlying hardware remains the same. Therefore it is important to compare the contents of the restored file to the original file to ensure all system settings are migrated.

For example, in an MCS system configured for Interplay | MAM, the fstab file contains an entry to automatically mount the Interplay | MAM filesystem.

Other deployments might contain an entry for a RAID5 cache volume.

Add information to the “live” fstab file as necessary.

Note: The UUID information will be different between “live” and restored fstab files. Do not alter this information.

5. If you are deploying MCS for Interplay | MAM or Media Composer | Cloud, you must

update MediaCentral configuration settings.

In this document, see Reconfiguring MCS for Upgrades from ICS 1.7 or Earlier

6. Verify the required version of the ISIS Client for your environment. See “Upgrading the

ISIS Client Software”.

7. Test the system. See “PART VII: VERIFYING THE INSTALLATION“.

8. If your workflow includes Closed Captioning, install the MediaCentral UX Closed

Captioning Service. See “PART VIII: INSTALLING THE CLOSED CAPTIONING SERVICE”.

Note: The Closed Captioning Service requires the ISIS Virtual Host Name in the MediaCentral UX System Settings (Playback Service) to be entered in all lower case. Verify and update this setting if needed.

9. If your workflow requires the MAM Connector, install and configure the software at this

time. See “PART IX: INSTALLING THE MAM CONNECTOR”.

10. If your workflow includes Media Distribute, install and configure the software at this

time.

For information on installing Media Distribute, see the Media |Distribute Installation and Configuration Guide, available on the MediaCentral Platform Services

page of the

Avid Knowledge Base.

11. If your workflow includes multi-zone or Media Index, configure those items at this time.

For multi-zone, see “PART X: MULTI-ZONE CONFIGURATION”.

For information on installing Media Index, see the Avid Media | Index Configuration Guide.

12. If your workflow includes multi-zone, update the configuration for “sharded” mongo.

See “PART VI: SHARDED MONGO”.

13. Once the system is running to your satisfaction, Avid suggests creating a final backup of

the system settings and MCS database.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details.

MediaCentral Services 2.6 Upgrading Guide

Upgrading a Cluster RHEL 6.3 System to MCS 2.6

Identifying the Master, Slave and Load-Balancing Nodes

The upgrade to MCS v2.6 on a RHEL 6.3 system involves a fresh OS and MCS software installation. This process consists of the following procedures:

 Identifying the Master, Slave and Load-Balancing Nodes  Backing Up the System Settings  Taking the Cluster Offline  Upgrading the Software  Restoring System Settings and Migrating the User Database  Additional Upgrade Procedures

Note: Before proceeding, back up any private key used to generate a Certificate Signing Request. In this document, see Backing Up and Restoring SSL Private Keys

Expected downtime: 1 hr. for 2 servers, + 30 min. for each additional server.

To identify the master, slave, and load-balancing nodes:

1. Verify the current role of each node by logging in to any machine in the cluster as the

root user and typing:

crm_mon

2. To identify the master and slave nodes, look for the line containing “Master/Slave Set”.

For example:

Master/Slave Set: ms_drbd_postgres [drbd_postgres] Masters: [ wavd-mcs01 ] Slaves: [ wavd-mcs02 ]

In this example, the master node is wavd-mcs01 and the slave node is wavd-mcs02.

3. To identify the load-balancing nodes, look for the line containing “Clone Set”.

For example:

Clone Set: AvidAllEverywhere [AvidAll] Started: [ wavd-mcs01 wavd-mcs02 wavd-mcs03]

In this example, the load-balancing node is wavd-mcs03.

4. Exit crm_mon by pressing CTRL-C on the keyboard.

MediaCentral Services 2.6 Upgrading Guide

Backing Up the System Settings

As this upgrade requires a re-image of the MCS servers, backing-up the system settings is critical to the success of the system upgrade.

Note: Ensure that t

in standby, only the system settings will be backed up – not the database. All other nodes can be in standby if desired. On the slave node the database is present, but not mounted. Load balancing nodes do not have a database.

he master node is not in standby when you run the backup script. If it is

To back up the system settings:

1. Prepare the v2.6 MCS Installation USB Drive and connect it to the cluster’s master node.

See “Creating the MCS Installation USB Drive” in the MediaCentral Platform Services Installation and Configuration Guide for details.

2. Mount the USB drive and change to the mount point.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

” for details.

3. Back up the current system settings and ICS/MCS database using the backup script.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details.

Be sure to create a copy of the backup directory using the Linux cp command. For example:

cp -r sys-backup sys-backup-<nodename>

Note: It is extremely important to copy the backup directory and rename it. Only the master

node backup contains the complete system settings and database. If you do not create a copy of the master node backup file, it will be overwritten by the backup from a non-master node and you will lose the database, amongst other information.

4. Unmount the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

5. Repeat the above procedure for the slave node and any load-balancing nodes.

6. Before proceeding, make sure you have a backup file for each node.

MediaCentral Services 2.6 Upgrading Guide

Taking the Cluster Offline

Upgrading the Software

Prior to upgrading the cluster, all nodes must be taken offline. To avoid accidental cluster failover, make sure to follow the order represented below.

To take the cluster offline:

1. Begin by putting the Corosync load-balancing nodes into standby mode and stopping

the rabbitmq service. Complete this process one node at a time, waiting 30 seconds between each node:

crm node standby <node name> service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

2. Wait 30 seconds and put the Corosync slave node into standby:

crm node standby <node name> service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

3. Wait 30 seconds and put the Corosync master node into standby:

crm node standby <node name> service rabbitmq-server stop

Verify that the stop command returns a value of [OK]. If the service does not stop correctly, troubleshoot the issue before continuing.

Complete this process for each cluster node (in any order).

To upgrade the software:

1. Unmount the USB drive (if you have not already done so).

See “Appendix B: Mounting and Unmounting a USB Drive

2. If your configuration includes a RAID 5 array, delete and recreate the RAID 5.

Destroying and re-creating the RAID 5 eliminates (in advance) any problems with cache permissions that can arise as a result of the RHEL update.

See “Appendix D: Deleting the RAID 5

” for details on deleting the RAID 5.

See “Configuring the Onboard RAID” in the MediaCentral Platform Services Installation and Configuration Guide for details on creating the RAID 5.

” for details.

3. Insert the USB drive and boot from it to install RHEL and MCS.

4. Once installed, remove the USB drive and reboot as prompted.

Rebooting after the OS upgrade causes the RHEL Text Mode Setup Utility (“Choose a Tool”) screen to appear, providing access to set-up menus.

5. Quit the RHEL Text Mode Setup Utility and log in to RHEL.

MediaCentral Services 2.6 Upgrading Guide

Restoring System Settings and Migrating the User Database

6. Check the installation was successful using the ics_version script:

ics_version

Service version numbers are returned as follows:

UMS Version: 2.6.x.x ICPS Version: 2.6.x.x ICPS manager Version: 2.6.x.x ACS Version: 2.6.x.x System ID: "xxxxxxxxxxx"

ICS installer: 2.6 (Build xx) Created on <installer creation date>

Note: If you receive a “command not found” error, logout and log back into the server or SSH

session (PuTTY). This will refresh the login for the upgraded system and should allow the command to run properly.

7. Install any RHEL security updates.

See the Avid MediaCentral Platform Services v2.6 ReadMe for more information.

1. Insert and Mount the USB drive on the master node.

See “Appendix B: Mounting and Unmounting a USB Drive

Warning: The MCS Installation USB Drive contains all software used to image a new MediaCentral server. Do not reboot the server with this USB drive attached!

2. Restore the system settings and MCS database using the restore script.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details.

Note: It is possible that error messages similar to the following will be output to the shell:

/usr/maxt/maxedit/cluster/resources/_common.sh errors

Ignore the messages and type the following and press Enter to complete the command:

service avid-all stop

You do not need to stop the error messages to type the above command. You can type it even as the error messages are output to the terminal.

” for details.

3. Unmount and remove the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

4. Verify if DRBD is set to run at system startup:

chkconfig –-list drbd

This command includes two dashes (“--“) with no space between them.

MediaCentral Services 2.6 Upgrading Guide

Additional Upgrade Procedures

5. If set to run, disable DRBD (since it will interfere with setting up the cluster):

chkconfig drbd off

6. Reboot and note the restored host name at the login prompt (e.g. wavd-mcs01).

Seeing the original hostname at the login prompt signifies that the system settings were successfully restored.

7. (On the Master Node Only) Log in as root and migrate the UMS database to the USS

database (new in 2.0):

/opt/avid/bin/avid-uss-import

The above command needs to be invoked on the master node only.

The system returns the following:

8. Repeat steps 1 through 7 on the slave and load balancing nodes to restore the system

settings for each node. Step 8 is completed on the master node only.

1. If your configuration includes a RAID 5, recreate the file cache on each cluster node. See

“Creating the File Cache on the RAID”.

2. Verify the contents of the hosts file. See “Verifying the hosts File Contents”.

3. Verify the date and time settings. See “Configure Date and Time Settings”. a. Though time zone information was restored, you must re-create the symbolic

link RHEL needs to make use of it:

ln –sf /usr/share/zoneinfo/<yourzone> /etc/localtime

If you need to verify the zone in use prior to re-creating the symbolic link:

cat /etc/sysconfig/clock

b. Verify the availability of the in-house NTP server, synchronize the System Clock,

and set up a cron job to keep the clock synchronized.

4. Reconfigure the cluster and cache replication. See “PART V: CLUSTERING”.

MediaCentral Services 2.6 Upgrading Guide

5. Compare the current and restored filesystem table files “fstab” for changes.

cat /<path>/fstab

• The current “live” filesystem table is located at: /etc/fstab

• The restored filesystem table is located at:

/root/fstab

For example, in an MCS system configured for Interplay | MAM, the fstab file contains an entry to automatically mount the Interplay | MAM filesystem.

Other deployments might contain an entry for a RAID5 cache or gluster volumes.

Add information to the “live” fstab file as necessary.

Note: The UUID information will be different between “live” and restored fstab files. Do not alter this information.

6. Verify the required version of the ISIS Client for your environment. See “Upgrading the

ISIS Client Software”.

7. Test the cluster. See “PART VII: VERIFYING THE INSTALLATION”.

8. If you are deploying MCS for Interplay | MAM or Media Composer | Cloud, you must

update MediaCentral configuration settings.

In this document, see Reconfiguring MCS for Upgrades from ICS 1.7 or Earlier

9. If your workflow includes Closed Captioning, install the MediaCentral UX Closed

Captioning Service. See “PART VIII: INSTALLING THE CLOSED CAPTIONING SERVICE”.

10. If your workflow requires the MAM Connector, install and configure the software at this

time. See “PART IX: INSTALLING THE MAM CONNECTOR”.

11. If your workflow includes Media Distribute, install and configure the software at this

time.

For information on installing Media Distribute, see the Media |Distribute Installation and Configuration Guide, available on the MediaCentral Platform Services

page of the

Avid Knowledge Base.

12. If your workflow includes multi-zone or Media Index, configure those items at this time.

For multi-zone, see “PART X: MULTI-ZONE CONFIGURATION”.

For information on installing Media Index, see the Avid Media | Index Configuration Guide.

13. If your workflow includes multi-zone, update the configuration for “sharded” mongo.

See “PART VI: SHARDED MONGO”.

MediaCentral Services 2.6 Upgrading Guide

14. Once the cluster is running to your satisfaction, Avid suggests creating a final backup of

the system settings and MCS database.

See Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database for details.

Appendix A: Post Upgrade Notes

Reconfiguring MCS for Upgrades from ICS 1.7 or Earlier

Reconfiguring MCS for Use with Media Composer | Cloud

The following notes may or may not apply to your configuration.

In previous releases, the MCPS Player embedded in the MediaCentral | UX UI required its own user name and password for communicating with the MCS server (from which it receives video). In MCS 2.6 this is no longer the case. As of ICS 1.8 the MCPS Player uses the credentials of the logged-in user.

As a result, if you have deployed MCS in support of Interplay | MAM or Media Composer | Cloud, and are upgrading from ICS 1.7 (or earlier) you will need to reconfigure MCS to support these applications.

1. With the MCS server up and running, log in to MediaCentral as the Administrator user.

2. Select System Settings from the Layout selector.

MediaCentral Services 2.6 Upgrading Guide

3. In the Settings pane, select ICPS> Player.

4. Media Composer | Cloud User: Enter the user name and password for the Cloud user.

Suggested User name: cloud

As a reminder, the Cloud user is a custom account which is added here and in the Interplay (Production) Administrator

Example screenshot of the related section of the Interplay Administrator:

This must be a unique user created solely for this purpose. This user should not be created as an Interplay Production or an ISIS user.

Note: If the credentials do not match, the Media Composer | Cloud console will present a “Sphere XKAsset Error: 6” indicating an invalid username and password.

MediaCentral Services 2.6 Upgrading Guide

Reconfiguring MCS for Use with Interplay | MAM

1. With the MCS server up and running, log in to MediaCentral as the Administrator user.

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. MAM)

• Advance License

• Do not assign the MAM role any layouts

6. Click Apply to save your changes.

The new MAM role is added to the Roles pane.

7. Create the MAM system user by clicking the Create User button.

8. In the Details pane, type the properties for the new user:

• User name (e.g. MAMuser)

• Password

• Uncheck “User must change password at next sign-in”

• Check “User cannot change password

9. Drag the MAM role from Roles pane to the Role section of the Details pane for the new

user.

10. Click Save to save your changes.

The new MAM user is added to the User Tree, as a top-level user.

11. Ensure the System Settings on the Interplay | MAM system are configured to make use

of the assigned user name and password. Example:

See the Avid MediaCentral | UX Administration Guide for more information about user creation and role assignment.

MediaCentral Services 2.6 Upgrading Guide

Resetting Layouts After Upgrading from V2.0 to V2.6

Resetting Layouts After Upgrading from ICS V1.6 or Earlier

Three panes used in MediaCentral UX v2.0 were dropped as of MediaCentral UX v2.1:

• Markers pane: redesigned as Logging pane.

• Layouts pane in Users Layout: replaced by drag-and-drop functionality.

• Search pane in Users Layout: replaced by Filter field.

After Media Central UX is upgraded to v2.6, users who had signed out of V2.0 with these panes open will see them when they sign in again, with the message: “No View implementation found for type undefined” in the pane. Users need to reset the panes.

To reset the outdated panes, do one of the following:

• Close the outdated panes.

• Reset the layout by selecting Reset Layout from the Layout selector.

After upgrading from Interplay Central Services V1.6 or earlier, users who had previously signed in will see the Assets pane and Search panes from their most recent session. However, the Assets tabs and Search panes are not usable.

This problem does not occur when upgrading from ICS V1.7 to MediaCentral Platform V2.6.

To reset the Assets pane and Search panes, do one of the following:

• Close all open Assets tabs and Search panes and reopen them.

• Reset the layout by selecting Reset Layout from the Layout selector.

MediaCentral Services 2.6 Upgrading Guide

Appendix B: Mounting and Unmounting a USB Drive

Refer to the instructions below to mount the USB drive.

To mount and unmount a USB drive:

1. Insert the USB drive into the MCS server.

2. Verify the name of the device using the dmesg command:

dmesg

Linux information relating to hardware appears on the screen.

Information for the USB drive will appear near the end of the output, near the list of SCSI devices. The name of the USB drive is found inside square brackets (e.g. sdc). This is the name you use to mount the drive.

3. If needed, create a mount point for the USB drive:

mkdir /media/usb

4. Mount the USB drive at the mount point you just created:

mount /dev/sdc1 /media/usb

Note the name of the USB drive, sdc (in this case), takes a 1 (one) in the mount command. This simply indicates a partition exists on the USB drive. When the USB drive was formatted, the partition was created.

The USB drive is now mounted and available for use.

5. Verify the USB drive has been mounted:

df -h

Information is displayed about all mounted filesystems and devices, and should include information about the USB drive, similar to the following (other output has been omitted, for clarity):

Filesystem Size Used Avail Use% Mounted on /dev/sdc1 7.5G 5.3G 2.2G 71% /media/usb

6. To change to the mount point:

cd /media/usb

7. To unmount the USB drive when finished, ensure you are not currently on it by changing

directories:

Note: In Linux the cd command without any arguments takes you directly to the user’s home directory. If you are logged in as root, it takes you to the /root directory. You must be off the USB drive to unmount it.

8. Unmount the USB drive:

umount /media/usb

The USB drive is now available for use in another server.

MediaCentral Services 2.6 Upgrading Guide

If you receive an error message that the USB device is busy, it typically indicates the Linux ISO on the USB drive was auto-mounted. Verify what is mounted using the df -h command and/or the mount command. Then, dismount the Linux ISO first, followed by the USB device:

umount /sysinstall umount /media/usb

9. Remove the USB drive from the server.

Removing the USB drive prevents accidental rebooting and re-imaging of the system disk.

MediaCentral Services 2.6 Upgrading Guide

Appendix C: Copying Software to the MCS Server

Copying Software Using WinSCP

At various times during the upgrade, you will need to copy software to the MCS server. The following two processes are provided as examples of how to complete this task:

 Using a Windows system and a SFTP tool such as WinSCP  Connecting a USB drive directly to the server

While the SFTP method may be preferred for ease of access, the USB method may be required for some operations such as backing-up MCS files during a system upgrade.

1. Download and install the WinSCP software on a Windows system that has network

access to the MCS server.

The WinSCP software can be found at: http://winscp.net

2. Launch WinSCP.

3. Click the New button and enter the Host name (or IP address) of your server, User name

(root), and Password.

4. Click Login.

The following warning message is displayed: “Continue connecting and add host key to the cache?”

5. Click Yes.

The WinSCP interface is displayed. The left pane represents your source Windows system. The right pane represents your MCS server.

6. Navigate to the location of the downloaded MCS installation files in the left pane.

7. Navigate to the

8. Create a directory structure for the MCS installer:

a. Right-click in the right pane and select New>Directory. b. In the “New folder name” field, type c. Double-click on the new

/media folder on the MCS server in the right pane.

installers and click OK.

installers folder in the right pane.

MediaCentral Services 2.6 Upgrading Guide

Copying Software Using a USB Drive

d. When copying the MCS installer to the server, the installer must be contained in its

own folder. Create a sub folder for the MCS installer:

Example:

/media/installers/MCS_2.6.0

Note: When manually creating folders, avoid spaces and other illegal Linux characters. Installations will fail if spaces or illegal characters are encountered in the file path.

e. Drag and drop the files or folders you wish to copy from the left pane to the right.

Depending on your WinSCP settings, you might see a dialog box asking if you want to copy the files to the remote directory. If asked, click Copy.

9. After all desired files or folders have been copied, close WinSCP.

For simply mounting and unmounting a USB drive, follow the process below and eliminate steps 7 and 8.

1. Insert the USB drive into the MCS server.

2. Use the display message command to verify the name of the device:

dmesg

Information relating to the hardware appears on the screen.

Information for the USB drive will appear near the end of the output, near the list of SCSI devices. The name of the USB drive is found inside square brackets (for example, sdc). This is the name you use to mount the drive.

3. If needed, create a mount point for the USB drive:

mkdir /media/usb

4. Mount the USB drive at the mount point you just created:

mount /dev/sdc1 /media/usb

Note the name of the USB drive, sdc (in this case) takes a 1 (one) in the mount command. This simply indicates a partition exists on the drive. When the USB drive was formatted, the partition was created.

The USB drive is now mounted and available for use.

5. Verify that the USB drive has been mounted:

df -h

Information is displayed about all mounted filesystems and devices, and should include information about the USB drive, similar to the following (some output omitted for clarity):

Filesystem Size Used Avail Use% Mounted on /dev/sdc1 7.5G 5.3G 2.2G 71% /media/usb

6. To change to the mount point:

cd /media/usb

MediaCentral Services 2.6 Upgrading Guide

7. If necessary, create a directory for the installer packages:

mkdir /media/installers

8. When copying the MCS installer to the MCS server, the installer must be contained in its

own folder. Create a sub folder for the MCS installer:

mkdir /media/installers/MCS_2.6.0

Note: When manually creating folders, avoid spaces and other illegal Linux characters. Installations will fail if spaces or illegal characters are encountered in the file path.

9. Copy files to the MCS server:

For a single file: cp filename /media/installers/MCS_2.6.0 For a folder:

cp -R foldername /media/installers/MCS_2.6.0

10. Once you have finished copying all necessary files, unmount the USB drive.

Note: In Linux the “cd” command without any arguments takes you directly to the user’s home directory. If you are logged in as

root, it takes you to the /root directory. RHEL

will not unmount the USB drive if it is the current active directory.

umount /media/usb

If you receive an error message that the USB device is busy, it typically indicates the Linux ISO on the USB drive was auto-mounted. Verify what is mounted using the command or the mount command, or both. Then dismount the Linux ISO first, followed by the USB device:

umount /sysinstall umount /media/usb

Caution: Once you have copied the necessary software, make sure you unmount and remove the USB drive from the server. If you re-boot with the server with the USB drive still in place, RHEL will be re-installed and all your work will be lost.

11. Remove the USB drive from the server.

Removing the USB drive prevents accidental re-imaging of the system disk following a reboot.

df -h

Appendix D: Deleting the RAID 5

Deleting the RAID 5 on an HP Gen9

When upgrading from one version of RHEL to another, it is recommended that you delete the RAID 5 prior to installing the new OS and MCS software. Deleting and re-creating the RAID 5 eliminates (in advance) any problems with cache permissions that can arise as a result of the RHEL update.

This section provides instructions for deleting the RAID 5. For information on re-creating the RAID 5, in the MediaCentral Platform Services Installation and Configuration Guide, see “Configuring the Onboard RAID”.

See the section that applies to your configuration:

MediaCentral Services 2.6 Upgrading Guide

• Deleting the RAID 5 on an HP Gen9

• Deleting the RAID 5 on an HP Gen8

• Deleting the RAID 5 on an Dell Server

1. Reboot the server and press F10 to select Intelligent Provisioning.

2. Select Perform Maintenance.

3. Select HP Smart Storage Administrator (SSA).

4. At the “Welcome to HP Smart Storage Administrator” screen, select Smart Array P840

from left side menu.

5. Use the Smart Array utility to delete the existing RAID5.

MediaCentral Services 2.6 Upgrading Guide

Deleting the RAID 5 on an HP Gen8

1. Reboot the server.

2. Press any key when prompted (spacebar recommended) to display the HP ProLiant

“Option ROM” messages.

3. 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.

MediaCentral Services 2.6 Upgrading Guide

4. From the Main Menu, select Delete Logical Drive and press Enter.

5. Select the RAID 5 and press F8 to delete.

MediaCentral Services 2.6 Upgrading Guide

6. A warning appears asking you to confirm your choice. Press F3 to delete the RAID.

7. The RAID 5 is removed, and can now be re-created.

In the MediaCentral Platform Services Installation and Configuration Guide, see “Configuring the Onboard RAID”.

Note: As indicated in the MediaCentral Platform Services Installation and Configuration Guide, once you have re-created the RAID 5 and have returned to the Main Menu, do not press <Esc> to exit since this reboots the server. Wait until you have inserted the USB drive and are ready to perform the upgrade.

MediaCentral Services 2.6 Upgrading Guide

Deleting the RAID 5 on an Dell Server

Deleting and recreating the RAID sets using the DELL BIOS utility does not erase data, nor does it delete existing partitions. That is, deleting a RAID does not delete the partition table — unless you initialize the disk at the same time. However, initializing the disk is a slow process.

In this procedure, you boot from the MCS Installation USB Drive and launch a RHEL “rescue” session in order to examine the current system partitions and delete them.

1. Boot from the MCS Installation USB drive.

2. At the RHEL Welcome screen, select “Rescue Installed System”.

3. When prompted choose the language and keyboard.

4. Choose “Hard drive” as the rescue method. For the purposes of booting from a RHEL

image, the USB drive is considered a hard drive.

MediaCentral Services 2.6 Upgrading Guide

5. Select the “/dev/sda1” partition (the USB drive). Leave the “Directory holding image”

field blank.

6. Select No in the Setup Networking window; as networking is not needed at this time.

7. Select “Skip” in the Rescue window.

MediaCentral Services 2.6 Upgrading Guide

8. At the next screen, choose “shell Start shell” and select Ok.

9. At the system prompt, use the RHEL fdisk utility to examine the current partitions:

fdisk -cul

This command will display the available disks and partitions on the system. Use Shift-Pg Up and Shift-Pg Down to view the entire output, since scroll bars will not be present in

the rescue shell.

In this case “sda” should be the USB boot drive, “sdb” should be the RAID 1 volume and “sdc” should be the RAID 5 volume.

The following example shows information for “sdb” with three partitions (sdb1, sdb2, sdb3):

Disk /dev/sdb: 500.1 GB, 500074307584 bytes 255 heads, 63 sectors/track, 60797 cylinders, total 97670732 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xc755f5b0

Device Boot Start End Blocks Id System /dev/sdb1 * 2048 1026047 512000 83 Linux /dev/sdb2 1026048 42051583 20512768 8e Linux LVM /dev/sdb3 42051584 976707583 467328000 8e Linux LVM

Additional entries for the filesystem (sdb4, sdb5) could be possible. Example:

Disk /dev/sdb: 598.9 GB, 598879502336 bytes 255 heads, 63 sectors/track, 72809 cylinders, total 11696828 sectors Units = sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0x930a8a0e

Device Boot Start End Blocks Id System /dev/sdb1 * 2048 1026047 512000 83 Linux /dev/sdb2 1026048 2050047 512000 83 Linux /dev/sdb3 2050048 43075583 20512768 8e Linux LVM /dev/sdb4 43075584 1169686527 563305472 5 Extended /dev/sdb5 43077632 1169686527 563304448 8e Linux LVM

MediaCentral Services 2.6 Upgrading Guide

You will need to delete the any partitions on the RAID 1 volume and the RAID 5 volume (if applicable). This process will assume “sdb” is the RAID 1 and “sdc” is the RAID 5.

10. Use the RHEL fdisk utility to select the sdb volume:

fdisk /dev/sdb

11. Type: p to print the current filesystem partition table. This will show you a similar

output as the fdisk –cul command you used earlier.

12. Type: d to begin deleting the partitions.

13. You will be prompted to specify the partition to delete. Example: 1

Partition number (1-4): 1

14. Repeat the above two steps to delete the remaining “sdb” partitions.

15. Once complete, type p to print the partition table again. An empty partition table

should look like the following:

Device Boot Start End Blocks Id System

16. Type: w to write the changes to the partition table and exit the utility.

17. If you have a RAID 5 volume, repeat this process by specifying the RAID 5 “sdc”

partition:

fdisk /dev/sdc

18. Repeat the above steps and type w to write the changes to the partition table and exit

the utility.

19. Verify that the partitions on sdb and sdc (if applicable) were successfully removed using

the RHEL fdisk utility:

fdisk -cul

MediaCentral Services 2.6 Upgrading Guide

Appendix E: Verifying the Media Index Status

Before you upgrade a MediaCentral system configured with Media Index, you need to ensure that there is no active schema migration currently affecting Media Index. When you change a field set of the system (Interplay Production, iNEWS, or Interplay Archive) and the change propagates to Media Index, any existing data is automatically migrated to reflect the changes. For large indexes, schema migration can take a while. To avoid an inconsistent Media Index state, you need to make sure that there is no schema migration actively affecting your indexes.

Once any current migration completes, you can continue with the MCS upgrade procedures.

To check the migration status prior to upgrading:

1. Sign in to MediaCentral UX as an administrator.

2. Select System Settings from the Layout selector.

The System Settings layout opens.

3. In the Settings pane select Media Index > Cluster State.

The Media Index Cluster State displays in the Details pane.

4. Check the cluster state: i. If there is no active migration, all index labels appear in black.

ii. If the index has an active migration, its label appears in red with an indication of the

migration progress.

5. If there is active migration is in progress, wait for the process to finish before proceeding with

the MCS upgrade procedures.

MediaCentral Services 2.6 Upgrading Guide

Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database

Bucardo configuration file used for database

/etc/collectd.conf

Configuration file for the collectd service

/etc/localtime

Time zone info

/etc/ntp.conf

Network Time Protocol config file

/etc/redis.conf

Configuration file for the redis service

/etc/resolv.conf

DNS config file

/etc/sudoers

List of users with sudo privileges

/etc/collectd.d/

Configuration files for the collectd service

/etc/corosync/corosync.conf

Corosync config file (cluster only)

The cron job that automates synchronization of /etc/drbd.d/r0.res

DRDB config file (cluster only)

/etc/elasticsearch/

/etc/pgpool-II/

Settings related to Multi-Zone configs

Before performing an upgrade it is recommended — and sometimes required — that you back up the ICS/MCS server system settings using the system-backup script. Depending on the upgrade path, you may also be required to restore the backed up system settings after.

The system-backup script provided for this task backs up important files and directories, including NIC card settings, DNS settings, and so on. In addition, the script calls the avid-db command, which dumps and backs up the contents of the ICS/MCS database. The ICS/MCS database contains ACS (Avid Common Services, “the bus”), UMS (User Management Service) and ICPS (Interplay Central Playback Services) data. It collects all this information and backs it up to the USB drive itself.

Note: In a cluster, the ICS/MCS database is replicated across the master and slave node, but it is only mounted on the master. Thus, the ICS/MCS database is only available for dumping and backup on the master node.

If you are backing up multiple nodes in a cluster, rename the backup file for each node before proceeding to the next node. If you do not rename the backup file obtained from the master node, it will be overwritten by the backup from a non-master node and the contents of the ICS/MCS database will be lost (including user information).

The following table lists the files and directories backed up and restored by the systembackup script. The table lists files as they are found in the ics_setup_files.tar backup file:

Directory/File Description

/etc/bucardorc

/etc/cron.d/ntpd

replication in a cluster

the system clock.

/etc/elasticsearch-tribe/

Settings related to Media Index

Directory/File Description

/etc/rsyslog.d/

Configuration file pertaining to the ICPS service

/etc/security/

Simple Network Management Protocol (network /etc/sudoers.d/

List of users with sudo privileges

/etc/sysconfig/

Network settings and more

/etc/udev/rules.d/70-persistent-net.rules

NIC card settings

/opt/avid/etc/avid/avid-interplay-

SSL private key file used with MCS 2.4 and

/opt/avid/etc/pki/certs/site.crt /opt/avid/etc/avid/avid-interplay-

Filesystem settings originally obtained from /usr/maxt/maxedit/etc/*

Maxedit settings (used by ICPS)

/usr/maxt/maxedit/share/MPEGPresets/

/var/lib/avid/db/dumps

RHEL user names and passwords

*** Not backed up. ***

MediaCentral Services 2.6 Upgrading Guide

/etc/snmp/

central/ssl/jetty.keystore

/opt/avid/etc/pki/private/site.key

central/config/application.properties

/root/

MPEG2TS.mpegpreset

monitor)

earlier.

SSL Certificate (site.crt) and private key (site.key) files used with MCS 2.5 and higher.

Contains customized options for MCS.

/etc/fstab

Defines encoding for iOS playback

/var/lib/avid/db/mongodump/*

Note: RHEL user names and passwords (such as the root user) are not backed up or restored by the system-backup script. After the upgrade, log in as “root” with the default password of “Avid123”.

To back up the system settings and ICS/MCS database:

Note: When backing up the master node in a cluster, it must not be in standby mode. When backing up other nodes, they can be in standby.

1. Mount the USB drive containing the system-backup script.

See “Appendix B: Mounting and Unmounting a USB Drive

2. Change to the mount point. For example:

cd /media/usb

ICS/MCS database (ACS, UMS and ICPS data). This includes user information.

” for details.

MediaCentral Services 2.6 Upgrading Guide

3. Back up the ICS/MCS settings and database using the backup script:

./system-backup.sh –b

Note: The following message indicates the system-backup script has already been run on the current machine:

File /root/pcmk.conf exists. Do you want to overwrite it?

Type “yes” or “y” to overwrite the file and continue with the backup.

A backup file is written to the USB drive:

/media/usb/sys-backup/ics_setup_files.tar.gz

Since the system-backup script also calls the avid-db command, a backup of the ICS/MCS database is also written to the following directory (on the ICS/MCS server):

/var/lib/avid/db/dumps

The backup file on the server has a name has the following form:

ALL-YYYYMMDD_HHMMSSZ.sql.gz.cr

Note: Note the time stamp appended to the file name uses the Universal Time Code (UTC), not the local time.

The following message indicates success:

Backup setup successful!

4. Make a copy of the backup file using the Linux cp command. For example:

cp –r sys-backup sys-backup-<nodename>

The above command copies the directory containing the backup file just created. The backup file itself (ics_setup_files.tar.gz) remains unchanged inside the directory.

Note:

Making a copy of the backup file is good practice, and is particularly important if you are backing up multiple nodes in a cluster. Only the master node backup contains a complete set of backup information (including end-user data). If you do not make a copy of the master node backup file, it will be overwritten by the backup from a non-master node.

5. Once the settings are backed up, it is good practice to unmount and remove the USB

drive to avoid accidentally rebooting, resulting in a re-image of the system disk.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

6. If you have a cluster configuration, repeat the above steps on all nodes.

To restore the system settings and ICS/MCS database:

1. Mount the USB drive containing the system-backup script.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

2. Change to the mount point. For example:

cd /media/usb

3. If you made a copy of the backup file, copy it back to its original location:

cp -r sys-backup-<nodename> sys-backup

MediaCentral Services 2.6 Upgrading Guide

4. Restore the ICS/MCS settings and database using the backup script:

./system-backup.sh –r

You are asked to confirm the restoration of the ICS/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. Would you like to continue? [yes/no]

6. Type “yes” (spelled out in full, without the quotes) to confirm the action.

Note: Be careful when typing your response to this question. Typing anything other than “yes” results in the script exiting without restoring the ICS/MCS database. Other items are restored, but not the ICS/MCS database.

Services are shut down, the ICS/MCS database is restored, and services are restarted.

The ICS/MCS database service is stopped, and you are prompted to restore the database.

The following message indicates success:

Restoration done! Your old fstab settings were saved in /root/fstab Please remove the USB key and reboot the server.

Note: The filesystem table (fstab) file contains information to automate mounting

volumes at boot time. It is not restored automatically.

7. Compare the current and restored filesystem table files “fstab” for changes.

cat /<path>/fstab

• The current “live” filesystem table is located at: /etc/fstab

• The restored filesystem table is located at:

/root/fstab

For example, in an MCS system configured for Interplay | MAM, the fstab file contains an entry to automatically mount the Interplay | MAM filesystem.

Other deployments might contain an entry for a RAID5 cache or gluster volumes.

Add information to the “live” fstab file as necessary.

Note: The UUID information will be different between “live” and restored fstab files. Do not alter this information.

8. Once the settings are restored, unmount and remove the USB drive.

See “Appendix B: Mounting and Unmounting a USB Drive

” for details.

MediaCentral Services 2.6 Upgrading 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 Avid's Web site at www.avid.com. The terms of that license are also available in the product in the same directory as

the software. The software may not be reverse assembled and may be used or copied only in accordance with the terms of the

license agreement. It is against the law to copy the software on any medium except as specifically allowed in the license

agreement.

No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, including

photocopying and recording, for any purpose without the express written permission of Avid Technology, Inc.

Attn. Government User(s). Restricted Rights Legend

U.S. GOVERNMENT RESTRICTED RIGHTS. This Software and its documentation are “commercial computer software” or

“commercial computer software documentation.” In the event that such Software or documentation is acquired by or on behalf

of a unit or agency of the U.S. Government, all rights with respect to this Software and documentation are subject to the terms

of the License Agreement, pursuant to FAR §12.212(a) and/or DFARS §227.7202-1(a), as applicable.

This product may be protected by one or more U.S. and non-U.S patents. Details are available at www.avid.com/patents

Trademarks

Adrenaline, AirSpeed, ALEX, Alienbrain, Archive, Archive II, Assistant Avid, Avid Unity, Avid Unity ISIS, Avid VideoRAID,

CaptureManager, CountDown, Deko, DekoCast, FastBreak, Flexevent, FXDeko, iNEWS, iNEWS Assign, iNEWS ControlAir,

Instinct, IntelliRender, Intelli-Sat, Intelli-sat Broadcasting Recording Manager, Interplay, ISIS, IsoSync, LaunchPad, LeaderPlus,

ListSync, MachineControl, make manage move | media, Media Composer, NewsCutter, NewsView, OMF, OMF Interchange,

Open Media Framework, Open Media Management, SIDON, SimulPlay, SimulRecord, SPACE, SPACEShift, Sundance Digital,

Sundance, Symphony, Thunder, Titansync, Titan, UnityRAID, Video the Web Way, VideoRAID, VideoSPACE, VideoSpin, and

Xdeck are either registered trademarks or trademarks of Avid Technology, Inc. in the United States and/or other countries.

All other trademarks contained herein are the property of their respective owners.

MediaCentral Services v2.6 Upgrading Guide• 25 April 2016

• This document is distributed by Avid in online (electronic) form only, and is not available for purchase in printed form.

Pinnacle Systems MediaCentral Platform Services - 2.6 Upgrading Guide

Specifications and Main Features

Frequently Asked Questions

User Manual

Important Information

Revision History

Contents

How to Use this Guide

Obtaining the Software Packages

Operating System

Upgrading Multi-Zone Deployments

Upgrading Media | Index Deployments

Upgrading the iNEWS Client Version

Upgrading the ISIS Client Software

Installing or Upgrading the Closed Captioning Service

Upgrading the MediaCentral Distribution Service (MCDS)

An Important Note on SSL Certificates

Backing Up and Restoring SSL Private Keys

Migrating User Settings from UMS to USS During an Upgrade

Upgrade Prerequisites

Update Installation versus Full Installation

Upgrade Paths

Upgrades for systems already running RHEL 6.5

Upgrades for systems running RHEL 6.3

Upgrades from 1.2.x or 1.3.x to MCS 2.6

Upgrading a Single Server RHEL 6.5 System to MCS 2.6

Installing MediaCentral Platform Services 2.6

Upgrading a Cluster RHEL 6.5 System to MCS 2.6

Identifying the Master, Slave and Load-Balancing Nodes

Backing-up the User Database and System Settings

Updating the Media Index Database

Taking the Cluster Offline

Updating the Cluster

Stopping the RabbitMQ Service and Rebooting the Cluster

Verifying the RabbitMQ Cluster

Bringing the Corosync Cluster Online

Verifying Gluster Volume Permissions

Removing the Gluster Metadata Cache Replication Volume

Upgrading a Single Server RHEL 6.3 System to MCS 2.6

Backing-up System Settings

Installing RHEL 6.5 and MCS 2.6

Restoring System Settings and Migrating the User Database

Additional Upgrade Procedures

Upgrading a Cluster RHEL 6.3 System to MCS 2.6

Identifying the Master, Slave and Load-Balancing Nodes

Backing Up the System Settings

Taking the Cluster Offline

Upgrading the Software

Restoring System Settings and Migrating the User Database

Additional Upgrade Procedures

Appendix A: Post Upgrade Notes

Reconfiguring MCS for Upgrades from ICS 1.7 or Earlier

Reconfiguring MCS for Use with Media Composer | Cloud

Reconfiguring MCS for Use with Interplay | MAM

Resetting Layouts After Upgrading from V2.0 to V2.6

Resetting Layouts After Upgrading from ICS V1.6 or Earlier

Appendix B: Mounting and Unmounting a USB Drive

Appendix C: Copying Software to the MCS Server

Copying Software Using WinSCP

Copying Software Using a USB Drive

Appendix D: Deleting the RAID 5

Deleting the RAID 5 on an HP Gen9

Deleting the RAID 5 on an HP Gen8

Deleting the RAID 5 on an Dell Server

Appendix E: Verifying the Media Index Status

Appendix F: Backing Up and Restoring System Settings and the ICS/MCS Database

Copyright and Disclaimer