Cisco VDS-TV Install, Upgrade and Maintenance Guide, Release

Cisco VDS-TV Installation, Upgrade and Maintenance Guide Release 4.4

September 2016

Cisco Systems, Inc. www.cisco.com

Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)

Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.

CONTENTS

Preface vii Document Revision History vii Audience vii Objective viii Document Organization viii Document Conventions ix Related Documentation x Obtaining Documentation and Submitting a Service Request x

CHAPTER 1 Overview of Upgrading and Downgrading the VDS-TV Software 1-1 Introduction 1-1 Prerequisites for Upgrading or Downgrading the VDS-TV Software 1-2 General Software Upgrade and Downgrade Information for VDS Servers 1-3 Upgrade and Downgrade Considerations 1-4 SNMP Service Disabled after Downgrade 1-4 Baud Setting 1-4 Software Upgrade 1-4 New Installations 1-4 Getting the Cisco VDS-TV Software Files for Release 4.4 1-5 Getting a Software File from Cisco.com 1-5 Upgrade Sequence for Different Deployments 1-6 Upgrading a VVI 1-6 VVI Upgrade Sequence 1-7 Upgrading a VDS 1-9 VDS Upgrade Sequence 1-9 Downgrade Sequence for Different Deployments 1-9 VVI Downgrade Sequence 1-10 VDS Downgrade Sequence 1-10 Upgrade and Downgrade Workflow for a VDS Server 1-11 Software Upgrade Workflow for a VDS Server 1-11 Software Downgrade Workflow for a VDS Server 1-11

Cisco VDS-TV Installation, Upgrade and Maintenance Guide iii Contents

CHAPTER 2 Installing and Configuring the VDS-TV 4.4 Software 2-1 Preparing the CDEs for Initial Configuration 2-1 Upgrading the New CDEs with Release 4.4 VDS-TV Software 2-2 Prerequisite for Asset Scalability Support 2-2 Installing the Software on a CDE110/UCS C220 M4 Hardware 2-3 Installing the Software on a CDE220 or CDE420 or CDE250 or CDE460 or CDE280 2-7 CDE280 BIOS and CIMC Settings 2-7 Imaging a VDS Server with 64-Bit OS using a DVD 2-15 Installing the VDS-TV software 2-16 Configuring the VDS-TV 2-16 Initial Configuration Sequence of the CDEs 2-16 VVI Initial Configuration Sequence 2-16 VDS Initial Configuration Sequence 2-17 Preparing to Initially Configure the CDEs 2-17 Initially Configuring the CDE110/UCS Hardware 2-18 Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280 2-23 Installing the CDSM in UCS C220 M4 2U1 Server 2-36 Procedure 2-36 Configuring BIOS Settings in CIMC 2-36 Hardware Setup 2-37 Installing the VDS-TV OS 2-38 Option 1 2-38 Option 2 2-38 Installing the CDSM software on UCS C220 M4 2U1 Server 2-39 Configuring the VDS-TV Hardware 2-39

CHAPTER 3 Upgrading to Release 4.4 3-1 Upgrading the Software on a CDSM or VVIM to Release 4.4 3-1 Pre-Requisites 3-1 Upgrading the software on a CDSM/VVIM 3-3 Manually Upgrading a VDS-TV Server to Release 4.4 3-7 Pre-Requisites 3-7 Upgrading the VDS-TV server 3-8 Database Migration 3-15

CHAPTER 4 Downgrading from Release 4.4 4-1 Downgrading a VDS-TV Server from Release 4.4 4-1 Downgrading the Software on a CDSM or VVIM 4-6

Cisco VDS-TV Installation, Upgrade and Maintenance Guide iv Contents

CHAPTER 5 System Maintenance 5-1 Replacing a Server 5-2 Replacing a CDSM or VVIM 5-2 Replacing a Redundant CDSM or VVIM 5-2 Replacing a Standalone CDSM 5-6 Replacing a VDS Server 5-7 Removing a Server 5-9 Removing a CDSM 5-10 Removing a VDS Server 5-12 Adding a Server 5-15 Adding a Second CDSM 5-15 Adding a VDS Server 5-18 Recovering a Lost Administrator Password 5-22 Disk Maintenance 5-22

APPENDIX A Troubleshooting A-1 Interfacing with the VDS Server During an Upgrade A-1 Viewing Upgrade Progress with Keyboard and Monitor Interface A-1 Backspace Does Not Work in Terminal A-1 Monitoring OS Load Runtime Syslog File A-2 Error Messages A-2 Warning Messages A-5 Failed or Stalled Upgrade A-5 VNC Listener A-6

Cisco VDS-TV Installation, Upgrade and Maintenance Guide v Contents

Cisco VDS-TV Installation, Upgrade and Maintenance Guide vi

Preface

This preface describes the audience, use, and organization of the Cisco VDS-TV Installation, Upgrade and Maintenance Guide. The preface also outlines the document conventions and support information. This preface contains the following sections: • Document Revision History, page vii • Audience, page vii • Objective, page viii • Document Organization, page viii • Document Conventions, page ix • Related Documentation, page x • Obtaining Documentation and Submitting a Service Request, page x

Document Revision History

The Document Revision History table below records the technical changes to this document.

Date Change Summary September, 2016 Initial release

Audience

This guide is for the networking professional managing the Cisco TV Content Delivery System, hereafter referred to as Videoscape Distribution Suite (VDS). Before using this guide, you should have experience working with the Linux operating system, and be familiar with the concepts and terminology of Ethernet, local area networking, and TV streaming and fundamentals of YUM and RPM.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide vii

Objective

This guide provides the information you need to install, upgrade, and maintain the Cisco VDS-TV servers. This guide provides procedures for upgrading existing VDS servers in a VDS and a Virtual Video Infrastructure (VVI), as well as for installing and initially configuring newly shipped Content Delivery Engines (CDEs) for a new system (VDS or VVI). This guide describes some system messages you might encounter during an upgrade. For information on installing the hardware, see the Cisco Content Delivery Engine 110 Hardware Installation Guide or the Cisco Content Delivery Engine 205/220/250/280/420/460/470 Hardware Installation Guide. See the “Related Documentation” section on page x for links to documentation online. For documentation updates, see the Release Notes for this release.

Document Organization

This document contains the following chapters and appendix:

Chapter or Appendix Descriptions Chapter 2, “Installing and Configuring the Describes how to upgrade the software on the CDEs and VDS-TV 4.4 Software” initially configure them for functioning in the VDS or VVI. Chapter 1, “Overview of Upgrading and Provides an overview of the upgrade and downgrade Downgrading the VDS-TV Software” process, including getting software files from the Cisco software download website. Chapter 3, “Upgrading to Release 4.4” Describes the software and operating system upgrade procedure for VDS servers, and the software upgrade for the Content Delivery System Managers (CDSMs) and Virtual Video Infrastructure Managers (VVIMs). Chapter 4, “Downgrading from Release Describes the software and operating system downgrade 4.4” procedure for the VDS servers, and software downgrade for the VDSMs and VVIMs. Chapter 5, “System Maintenance” Describes the procedures for adding, replacing, and removing a server, backing up and restoring a server, and recovering an administrator password. Appendix A, “Troubleshooting” Provides information on error and warning messages that may be encountered, and other problems that might occur. Output from the scripts are also included in this appendix.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide viii

Document Conventions

This guide uses the following conventions for command syntax descriptions and textual emphasis:

Conventions Descriptions bold font Commands and keywords are in bold. italic font Arguments for which you supply values are in italics. [ ] Elements in square brackets are optional. {x | y | z} Alternative, mutually exclusive, keywords are grouped in braces and separated by vertical bars. [x | y | z] Optional, alternative keywords are grouped in brackets and separated by vertical bars. string A nonquoted set of characters. Do not use quotation marks around the string because the string will include the quotation marks. screen font Terminal sessions and information the system displays are in screen font. bold screen font Information you must enter is in bold screen font. italic screen font Arguments for which you supply values are in italic screen font. ^ The symbol ^ represents the key labeled Control—for example, the key combination ^D in a screen display means hold down the Control key while you press the D key. < > Nonprinting characters, such as passwords, are in angle brackets in contexts where italics are not available. !, # An exclamation point ( ! ) or a pound sign ( # ) at the beginning of a line of code indicates a comment line.

Caution Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in this publication.

Tip Means the following information might help you solve a problem.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide ix

Related Documentation

These documents provide complete information about the VDS, and are available at Cisco.com: • Release Notes for the Cisco VDS-TV 4.4 • Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4 • Cisco VDS-TV ISA Software Configuration Guide, Release 4.4 • Cisco VDS-TV API Guide, Release 4.4 • Cisco Content Delivery Engine 110 Hardware Installation Guide • Cisco Content Delivery Engine 205/220/250/280/420/460/470 Hardware Installation Guide • Cisco UCS C220 M4 Server Installation and Service Guide • Regulatory Compliance and Safety Information for Cisco Content Delivery Engines You can access the software documents at: http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html You can access the hardware documents at: http://www.cisco.com/en/US/products/ps7126/tsd_products_support_series_home.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html Subscribe to the What’s New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide x

CHAPTER 1

Overview of Upgrading and Downgrading the VDS-TV Software

This chapter provides an overview of upgrading and downgrading the CDSM, VVIM, and VDS servers. The chapter covers the following topics: • Introduction, page 1-1 • Getting the Cisco VDS-TV Software Files for Release 4.4, page 1-5 • Upgrade Sequence for Different Deployments, page 1-6 • Downgrade Sequence for Different Deployments, page 1-9 • Upgrade and Downgrade Workflow for a VDS Server, page 1-11

Introduction

The Release 4.4 software upgrade for VDS servers (CDSM, VVIM, Streamer, Vault, Caching Node, and ISV) on a 64-bit operating system (OS) is done with the vdsinit script. The following software upgrade paths are supported for Release 4.4: • Release 2.5.x to Release 3.2.x to Release 4.4 • Release 3.0.x to Release 3.2.x to Release 4.4 • Release 3.2.x to Release 4.4 • Release 3.4.x to Release 4.4 • Release 3.5.x to Release 4.4 • Release 3.7.x to Release 4.4 • Release 3.9.x to Release 4.4 • Release 3.12.x to Release 4.4 • Release 4.2.x to Release 4.4

If the VDS is running an earlier software release, you must first upgrade to one of the supported releases before upgrading to Release 4.4.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-1 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Introduction

Note Due to changes in file system, direct upgrade is supported only from Release 3.2.x to Release 4.4

Warning If the supported upgrade paths are not followed, then CServer will have to be started with -c option that will erase all the GOIDS in the disk.

Note Software upgrades and downgrades should be performed during maintenance windows; that is, during off-peak hours when no new content is ingested into the VDS and stream demands are the lowest.

Caution Basic understanding of the Linux command line and the vi editor are required for the completion of the software upgrade. Do not attempt the software upgrade if you are unfamiliar with the Cisco VDS products and the Linux command line and vi editor.

We recommend that an experienced Linux system administrator perform the software upgrade and downgrade. The VDS-TV Release 4.4 software upgrade and downgrade require disk space and network connectivity verification, knowledge of the VNC application (if applicable), and general administration of the remote backup server for archive storage.

Prerequisites for Upgrading or Downgrading the VDS-TV Software

Upgrading or downgrading a VDS server has the following prerequisites: • At least 20 percent unused disk space on the file system for the /boot directory. • If the /boot_cds directory exists, at least 4.8 GB partition size for the file system and at least 1 GB unused disk space. • VNC Listener setup defined and operational (We highly recommend using a VNC Listener. See the “VNC Listener” section on page A-6 for more information.) • Server is operational, which means connected to the network, boot up has completed, all file systems are mounted, and all content drives are operational. • Any failed content drives should be removed from the server. Upgrading a server with failed content drives may result in a stalled upgrade process, which dramatically increases the amount of time required to perform the upgrade. • Serial console connected TTYS0 (Not mandatory, but we highly recommend a serial console for monitoring the process). • Direct physical access in the event of a major failure (for example, power outage) during upgrade. • Access to a remote server used for backing up each VDS server. The remote Linux server should have enough space to store multiple backups. (The log files that are backed up are not restored.) • All non-essential files should be archived to a remote location and then removed if the disk space usage is high on all partitions. Any file system at 90 percent capacity should be cleaned up. • Before upgrading the CDSM or VVIM, all settings on the CDSM Setup page should be recorded. After the CDSM or VVIM is upgraded, all setting on the CDSM Setup page should be verified with the settings that were recorded and resubmitted.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-2 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Introduction

Note After the upgrade procedure starts, do not make any configuration changes until all the servers have been upgraded. The only exceptions to this are submitting the CDSM Setup page after a CDSM or VVIM upgrade, and submitting the Route Tables page and Interface Setup page after upgrading a VDS server.

Note The /arroyo/log/archive directory is not preserved. If you want to save the archive, copy it to another server before upgrading the software.

Note During the initialization process of a VDS server or after recovering a VDS server that has been down for less than an hour, the VDS database performs a complete synchronization. The database synchronization takes about five minutes before the server becomes ready for service. If the VDS server is down for a much longer time than an hour, the database synchronization takes longer than five minutes. The netstat command will not show the interfaces as up until the synchronization has completed.

General Software Upgrade and Downgrade Information for VDS Servers

The following list provides information about the VDS-TV Release 4.4 software upgrade: • Copy the vdsinit script and the VDS-TV ISO image file to the VDS server. • Upgrade and downgrade procedures are not for imaging a server to the same state as a brand new system. • Upgrade can take approximately one hour. The minimum time to perform an upgrade has been 25 minutes; however, servers in different network deployments may require additional time. This time is also based on no failures during the upgrade (that is, power loss or other major failures). • All configuration information concerning the network should be recorded before upgrading the software. • Upgrade can be monitored (recommended) from a VNC Listener. During the stage 2 boot process of the upgrade, a window is provided to the user to see the operations taking place on the server. Using the VNC Listener provides the additional ability to triage issues through the serial console if there is a failure during the upgrade. • Log files are backed up during the upgrade and downgrade procedures. However, if the log file backup process fails, it is not considered a fatal error and the procedure continues. • File systems preserved across the OS upgrade are those associated with the following directories: /boot, /arroyo/db, and /boot_cds (if it exists). The upgrade procedure creates the /boot_cds directory if it does not exist. • Backups are created in /arroyo/db directory. After the upgrade, the administrator performing the upgrade is responsible for removing these files when they are no longer needed. • Review the file /arroyo/image/tags to see if the installed version on the server is Release 3.2.x or higher. • To perform a downgrade, the ISO image file, cdsinstall for the VDS-TV release and the backup files created during the upgrade (backup.tgz, and backup_db.tgz) are required.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-3 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Introduction

Upgrade and Downgrade Considerations

The following sections contain considerations for the upgrade and downgrade procedures.

SNMP Service Disabled after Downgrade

In release 4.4, SNMP is added to services using the chkconfig script while running the vdsinit script. So, SNMPD is started on reboot. SNMP service can also be started, stopped or restarted using the service snmpd start/ stop/restart command. Once the server is downgraded to any version before 3.0.1, this support is not available. In releases prior to 3.0.1, SNMP can be started by running the cdsconfig script to generate rc.local. This adds the line nice -n 19 /usr/local/sbin/snmpd to the rc.local and SNMP starts on reboot. SNMP can also be started manually by executing nice -n 19 /usr/local/sbin/snmpd on the server after the downgrade procedure has completed.

Baud Setting

Most installations required the baud of 9600 bits per second (bps). The vdsconfig script supports changing the baud without manually editing any files.

Software Upgrade

For a software upgrade, the vdsconfig script may not need to be run. If the baud rate is currently11520 and the user needs to change it to 9600, the user needs to create the /etc/cdsbaud9600 file before running the vdsinit script. The vdsinit script searches for the cdsbaud9600 file, and sets the baud to 9600 if the file is found; otherwise, the baud is set to 115200. After the vdsinit script has completed and the vdsconfig script prompts the user as follows: Serial Console BAUD speed is configured as '9600'. Do you wish to change it (yes/no) [n]: y Please select the speed: 1. 9600 2. 115200 Choice:

For CDE250s, the /etc/cdsbaud9600 file need not be created as the BAUD rate is set to 9600 by default on upgrade (through the vdsinit script). For other servers, the /etc/cdsbaud9600 file must be created if the user wants to change the BAUD speed to 9600 on upgrade. If the BAUD speed was manually changed in the grub.conf and inittab files, it is not changed during upgrade. For software upgrades, vdsconfig script may not be run at all.

New Installations

For a new installation, the vdsinit script still requires the following settings on the terminal server serial port: • 9600 baud • 8 bits • No parity After the vdsinit script has completed and the vdsconfig script prompts the user as follows:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-4 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Getting the Cisco VDS-TV Software Files for Release 4.4

Serial Console BAUD speed is configured as '9600'. Do you wish to change it (yes/no) [n]: y Please select the speed: 1. 9600 2. 115200 Choice:

Getting the Cisco VDS-TV Software Files for Release 4.4

Table 1-1 lists the different files for upgrading and downgrading the CDSM and the CDS servers (Streamers, Caching Nodes, Vaults, and ISVs) to Release 4.4.

Table 1-1 Files for Release 4.4 Software Upgrade

VDS-TV Software Server Operating System Upgrade Package Upgrade CDSM (64-bit OS already installed) vdsinit-4.4.1 tv_repo-4.4.1-x86_64.iso Vault, Caching Node, tv_full-4.4.1-x86_64.iso vdsinit-4.4.1 Streamer, or ISV tv_repo-4.4.1-x86_64.iso

The tv_repo-4.4.1-x86_64.iso file is the ISO image file of the Release 4.4 software. This file is used for the CDS servers and the CDSM and VVIM. The vdsinit script must be downloaded and copied to the CDSMs and VVIMs for upgrading to Release 4.4. The tv_full-4.4.1-x86_64.iso file is an ISO image file that can be burned to a DVD for recovering from an upgrade or used for a clean install of the VDS servers. For more information, see the “Imaging a VDS Server with 64-Bit OS using a DVD” section on page 2-15.

Getting a Software File from Cisco.com

To get a software file from Cisco.com, do the following:

Step 1 Launch your web browser and enter the following URL: http://www.cisco.com/cisco/software/navigator.html The Select a Product page is displayed. The page displays a Navigator for browsing Cisco products. Step 2 Log in to Cisco.com using your designated username and password. Step 3 Click Products > Video and Content Delivery > Content Delivery Systems > Content Delivery Applications > Cisco TV Streamer Application. The Download Software page is displayed, listing the available software releases s for the TV Streamer application. Step 4 Click the software release you want. The page refreshes and the software image files are displayed. Step 5 Click the link for the software image file you want.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-5 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Upgrade Sequence for Different Deployments

• If this is the first time you have downloaded a file from Cisco.com, the Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy is displayed. Read the policy, fill in the unfilled fields, and click Accept. • If you previously filled out the Encryption Software Usage and Handling and Distribution form, the form does not display again. Step 6 Click Download Now to download the file, or click Add to cart to select more image files before downloading them. The Download Cart page is displayed.

Note Make note of the MD5 checksum value to verify the MD5 checksum after download. You can copy and paste the value into a text file for easy reference.

Step 7 Click Proceed With Download. The Cisco End User Software License Agreement is displayed. Step 8 Read the agreement and click Agree. The Download Software page is displayed. Step 9 Choose a download option, either Download Manager Option or Non Java Download Option. A new window displays the filename of the ISO image file. Step 10 Click Download. the File Download dialog box is displayed. Step 11 Click Save. The Save As dialog box is displayed. Step 12 Navigate to the location where you want to save the file and click Save. The file downloads.

Upgrade Sequence for Different Deployments

This section describes the upgrade sequence for a Virtual Video Infrastructure (VVI) and a Content Delivery System (VDS). A VVI includes of Caching Nodes and split-domain management. A VDS consists of Streamers and Vaults, or ISVs.

Upgrading a VVI

This section describes the software upgrade sequence for a Virtual Video Infrastructure (VVI). The upgrade sequence for a VVI in an ISA environment and a VVI in an RTSP environment are the same, except the Caching Nodes are upgraded in a specific order in the RTSP environment.

ISA Environment A VVI in an ISA environment has the following network design: • Multiple video hub offices (VHOs) and multiple sites per VHO • Shared Content Store • ISA with Stream Destination • Vault Group Redundancy • Caching Nodes (VVI) • Split-domain management (VVIM and Stream Manager [CDSM]) • CDSM Redundancy

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-6 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Upgrade Sequence for Different Deployments

RTSP Environment A VVI in an RTSP environment with NGOD deployment and HTTP Streamers has the following network design: • Multiple Stream Groups • Multiple Source Output Ports • Vault Group Redundancy • Caching Nodes (VVI) • Split-domain management (VVIM and Stream Manager [CDSM]) • CDSM Redundancy

VVI Upgrade Sequence

The following is a suggested order for upgrading a VVI: 1. VVIM for the SHEs should be upgraded first. Upgrade the secondary VVIM, then upgrade the primary VVIM. The primary and secondary VVIM can be determined by entering the ifconfig -a | more command. The primary has the following output: eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00 inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Memory:b8820000-b8840000

The primary VVIM has device eth0:1. The secondary VVIM does not have the virtual IP address as up. 2. Vaults. Upgrade all slave Vaults first, then upgrade the master Vault. The master and slave Vault can be determined by entering the ifconfig -a | more command. The master has the following output: eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00 inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Memory:b8820000-b8840000

The master Vault has device eth0:1. The slave Vault does not have the virtual IP address as up. 3. Caching Nodes. There is no specific order for upgrading the Caching Node in an ISA environment, but to guarantee nonstop services, keep at least one Caching Node online at all times at each site. Upgrade the Caching Nodes in an RTSP environment in the following order: a. Available Caching Nodes b. Backup Caching Node c. Primary Caching Node To identify the Caching Nodes, use the cat httpinfo command to view the /proc/calypso/status/cache/httpinfo file. The following example indicates that Caching Node 35 is the primary and Caching Node 36 is the backup: # cat httpinfo C2 Protocol Info: Locate Port Service: IPv4 Address: 192.169.87.100 Primary Server: 35 local

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-7 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Upgrade Sequence for Different Deployments

Backup Server: 36 Time Offset: 0 usec Local Transfer Ports: 192.169.87.10: Up: Allocated 0bps 192.169.87.11: Up: Allocated 0bps 192.169.87.12: Up: Allocated 0bps

4. CDSM of the first Stream Domain (VHO1 in ISA environment). Upgrade the secondary CDSM, then upgrade the primary CDSM. The primary and secondary CDSM can be determined by entering the ifconfig -a | more command. The primary has the following output: eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00 inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Memory:b8820000-b8840000

The primary CDSM has device eth0:1. The secondary CDSM does not have the virtual IP address as up. 5. Streamers in the first Stream Domain. If the Streamers are in multiple Stream Groups (sites), upgrade the Streamers in the “Control” sites first (sites that have Stream Groups with only a Control server), followed by the “Setup/Control” sites (sites that have Stream Groups with a Setup/Control server). In each Stream Group, upgrade the Streamers in the following order: a. Available Streamers b. Backup Streamer c. Primary Streamer To identify the Streamers, use the following command: # cat /proc/calypso/status/streamer/resiliencyinfo Streamer Resiliency Info: Service Address: 172.22.98.50 Control Service: Primary

6. Repeat tasks 1 and 2 for each Stream Domain in the VVI. Upgrade the secondary CDSM, followed by the primary CDSM, then upgrade the Streamers in the Control site (available Streamers first, backup Streamer second, and primary Streamer last), followed by the Streamers in the Setup/Control site.

Note A Stream Manager can manage multiple VHOs (ISA) or Stream Groups (RTSP). Always upgrade the Stream Manager first, then upgrade the Streamers in each VHO (or Stream Group) managed by this CDSM.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-8 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Downgrade Sequence for Different Deployments

Upgrading a VDS

This section describes the software upgrade sequence for a Content Delivery System (VDS) as opposed to a VVI. The upgrade sequence for a VDS in an ISA environment and a VDS in an RTSP environment are the same.

VDS Upgrade Sequence

The following is a suggested order for upgrading a VDS: 1. CDSM. Upgrade the secondary CDSM, then upgrade the primary CDSM. 2. Streamers. If the Streamers are in multiple Stream Groups (sites), upgrade the Streamers in the “Control” sites first (sites that have Stream Groups with only a Control server), followed by the “Setup/Control” sites (sites that have Stream Groups with a Setup/Control server). In each Stream Group, upgrade the Streamers in the following order: a. Available Streamers b. Backup Streamer c. Primary Streamer To identify the Streamers, use the following command: # cat /proc/calypso/status/streamer/resiliencyinfo Streamer Resiliency Info: Service Address: 172.22.98.50 Control Service: Primary

3. Vaults. Upgrade all slave Vaults first, then upgrade the master Vault.

Note If the VDS consists of a CDSM and ISVs, upgrade the CDSM first followed by the ISVs.

Downgrade Sequence for Different Deployments

This section describes the downgrade sequence for a Virtual Video Infrastructure (VVI) and a Content Delivery System (VDS). The software downgrade should be performed on the VDS server types in the reverse order of the upgrade sequence—that is, Streamer, CDSM, Caching Nodes, Vault and lastly VVIM. If all Streamers have been upgraded, we recommend not downgrading any of the Streamers. This also applies to Caching Nodes and Vaults. If all VDS servers of a specific type (Streamer, Caching Node, Vault, or ISV) have all been upgraded, we recommend not downgrading the software.

Note Before downgrading the software, any problems encountered as a result of the upgrade should be understood first. Downgrading a system (VVI or VDS) may result in loss of configuration changes and loss of content that was ingested since the upgrade. Contact Cisco support before downgrading your system.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-9 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Downgrade Sequence for Different Deployments

VVI Downgrade Sequence

The following is a suggested order for downgrading a VVI: 1. Streamers in the first Stream Domain. Downgrade the Control site first, followed by the Setup/Control site. In each Stream Group, downgrade the Streamers in the following order: a. Available Streamers b. Backup Streamer c. Primary Streamer 2. CDSMs in the first Stream Domain. Downgrade the secondary CDSM before the primary CDSM. 3. Repeat tasks 1 and 2 for each Streaming domain. 4. Caching Nodes. There is no specific order for downgrading the Caching Nodes in an ISA environment, but to guarantee nonstop services, keep at least one Caching Node online at all times at each site. Downgrade the Caching Nodes in an RTSP environment in the following order: a. Available Caching Nodes b. Backup Caching Node c. Primary Caching Node 5. Vaults. Downgrade all slave Vaults first, then downgrade the master Vault. 6. VVIMs managing Vaults and Caching Nodes. Downgrade the secondary VVIM before the primary VVIM. If the Streamers at a Setup/Control site have not been upgraded, just downgrade the Streamers at a Control site. If the Streamers at a Setup/Control site have been upgraded, downgrade these Streamers first, then downgrade the Control site Streamers.

VDS Downgrade Sequence

The following is a suggested order for downgrading a VDS: 1. Vaults. Downgrade all slave Vaults first, then downgrade the master Vault. 2. Streamers. Downgrade the Control site first, followed by the Setup/Control site. In each Stream Group, downgrade the Streamers in the following order: a. Available Streamers b. Backup Streamer c. Primary Streamer 3. CDSM. Downgrade the secondary CDSM before the primary CDSM. If the Streamers at a Setup/Control site have not been upgraded, just downgrade the Streamers at a Control site. If the Streamers at a Setup/Control site have been upgraded, downgrade these Streamers first, then downgrade the Control site Streamers. If the system consists of ISVs and CDSMs, downgrade the ISVs first followed by the CDSMs.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-10 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Upgrade and Downgrade Workflow for a VDS Server

Upgrade and Downgrade Workflow for a VDS Server

The procedure to upgrade or downgrade a VDS server is more complicated than for a CDSM or VVIM. This section covers the following topics: • Software Upgrade Workflow for a VDS Server • Software Downgrade Workflow for a VDS Server

Software Upgrade Workflow for a VDS Server

A high-level view of the software upgrade workflow is as follows: 1. Get the VDS-TV 4.4 ISO file, vdsinit script file and copy it to the target VDS server. 2. Offload the VDS server. 3. Run the vdsinit script and perform the upgrade. 4. Reboot the server and start the services as per the sequence mentioned in vdsServices.conf.

Software Downgrade Workflow for a VDS Server

A high-level view of the software downgrade workflow is as follows: 1. Offload the server. 2. Copy the ISO image file to be downgraded, to the /root directory of the VDS server. 3. Execute the vdstvDowngrade script. 4. Reboot the server and start the services as per the sequence mentioned in /etc/rc.local.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-11 Chapter 1 Overview of Upgrading and Downgrading the VDS-TV Software Upgrade and Downgrade Workflow for a VDS Server

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 1-12

CHAPTER 2

Installing and Configuring the VDS-TV 4.4 Software

This chapter covers the installation of the new Release 4.4 systems in either a Content Delivery System (CDS) or a Virtual Video Infrastructure (VVI). This chapter includes the following topics: • Preparing the CDEs for Initial Configuration, page 2-1 • Upgrading the New CDEs with Release 4.4 VDS-TV Software, page 2-2 • Imaging a VDS Server with 64-Bit OS using a DVD, page 2-15 • Initial Configuration Sequence of the CDEs, page 2-16 • Initially Configuring the CDE110/UCS Hardware, page 2-18 • Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280, page 2-23 • Installing the CDSM in UCS C220 M4 2U1 Server, page 2-36 A VDS consists of Vaults, Streamers, and a Content Delivery System Manager (CDSM). A VDS can also consist of Integrated Streamer-Vaults (ISVs) and a CDSM. A VVI consists of Vaults, Caching Nodes, Streamers, Virtual Video Infrastructure Manager (VVIM), and Stream Manager (also called CDSM). For more information about the different system architectures and network designs, see the “Product Overview” and “Network Design” chapters in the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4 and the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Preparing the CDEs for Initial Configuration

Before performing the software installation and initial configuration, you must correctly install the Content Delivery Engines (CDEs) and connect the cables as described in the Cisco Content Delivery Engine 110 Hardware Installation Guide and the Cisco Content Delivery Engine 205/220/250/280/420/460/470 Hardware Installation Guide.

Note As part of the hardware installation of the CDEs, ensure that all I/O cards are properly and firmly seated, and all cables are firmly connected.

Connecting to the Serial Port on the CDE The RJ-45 serial ports on the front and back panels of the Cisco CDEs can be used for administrative access to the CDEs through a terminal server. Terminal emulation software must be configured as follows:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-1 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

• Bits per second: 9600 • Data bits: 8 • Parity: none • Stop bits: 1 • Hardware flow control: ON After installing the CDEs and connecting the cables, the software must be upgraded before initial configuration can occur.

Upgrading the New CDEs with Release 4.4 VDS-TV Software

A new CDE ships with Release 3.x. Download the software files for Release 4.4, and upgrade the operating system (OS) and software on the CDE models to be configured as VDS servers (Vaults, Caching Nodes, Streamers, and ISVs), and upgrade the software on the CDE110s, which are used for the CDSMs and VVIMs.

Note Before you upgrade the CDEs, download the VDS-TV Release 4.4 software image files from the Cisco software download website. See the “Getting the Cisco VDS-TV Software Files for Release 4.4” section on page 1-5 for information on downloading these files.

Prerequisite for Asset Scalability Support

Starting from Release 3.9, Table size has been reduced in the new content object table (CONTENT_OBJECT3.db in RTSP environment and CONTENT_OBJECT4.db in ISA environment) to support large number of assets. To maintain assets in old and upgraded database, choose Maintain -> Software -> CDSM Setup and set Asset scale Co-existence support to Enabled. Once all servers are upgraded to VDS-TV release 4.4 set Asset scale Co-existence support to Disabled and restart FSI in all the vaults. By default, Asset Scale Co-Existence Support is enabled.

Note Disabling asset co-existence support is an irreversible process and the assets are maintained only in the upgraded database. Disable co-existence support only after upgrading all the servers to version 3.9 or higher.

Note Disable asset scale co-existence support only during the scheduled maintenance time and restart FSI in all the vaults before next ingest.

The following upgrade procedures are for the CDEs used in a Release 4.4 VDS or VVI: • Installing the Software on a CDE110/UCS C220 M4 Hardware • Installing the Software on a CDE220 or CDE420 or CDE250 or CDE460 or CDE280

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-2 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

Installing the Software on a CDE110/UCS C220 M4 Hardware

The Cisco CDE110 is used for a CDSM or VVIM in a VDS or VVI. The CDE110 ships with a 64-bit OS, and therefore, requires only a software image upgrade. Starting from Release 3.9, UCS C220 M4 hardware is also used for a CDSM or VVIM in a VDS or VVI To install the software image on a CDE110/UCS C220 M4, do the following:

Step 1 If the Cisco CDE110 is not powered on, press the front panel power switch on the server. The operating system boots. Step 2 Log in as root with the default password.

Note To change the default password, use the passwd command.

Step 3 To copy the tv_repo-4.4.1-x86_64.iso and vdsinit software files on the CDE110, configure the management interface. a. To configure the Ethernet interface (eth0), which is used to connect to the management network, use a text editor to modify the file /etc/sysconfig/network-scripts/ifcfg-eth0, and add the following lines: – DEVICE=eth0 – BOOTPROTO=static – ONBOOT=yes – IPADDR=ip_address_for_eth0 – NETMASK=netmask_for_eth0 For example: DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=172.22.97.162 NETMASK=255.255.255.128

b. Save and close the ifcfg-eth0 file. c. To configure the network characteristics, use a text editor to modify the file /etc/sysconfig/network, and add the following lines: – NETWORKING=yes – HOSTNAME=name – GATEWAY=gateway_ip_address – GATEWAYDEV =device_id_number – NOZEROCONF =yes For example: NETWORKING=yes HOSTNAME=cdsm162 GATEWAY=172.22.97.129 GATEWAYDEV=eth0 GATEWAY=yes

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-3 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

The gateway_ip_address is the default gateway IP address, the address of the interface on the router that is directly attached to the CDE110 eth0 interface. d. Save and close the network file. e. To restart the network, issue the following command: [root]# /etc/init.d/network restart

Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ]

[root]#

Step 4 Use the scp command to copy the tv_repo-4.4.1-x86_64.iso and vdsinit software files. For example, if the remote server that you downloaded the software files to has the IP address 172.22.97.109, and the files are stored in the CDSdownloads directory, the following commands are used: # scp -p 172.22.97.109:/CDSdownloads/tv_repo-4.4.1-x86_64.iso /root # scp -p 172.22.97.109:/CDSdownloads/vdsinit-4.4.1 /root

Step 5 Run the vdsinit script to install the ISO image to Release 4.4. # cd /root # ./vdsinit-4.4.1 tv_repo-4.4.1-x86_64.iso

Select the deployment type as 1 CDSM/VVIM. The following log output is displayed towards the end of the installation

Note This example log output may not match the final image log output.

Mounting tv_repo-4.4.1-0b1-x86_64.iso at /mnt/cdrom Currently Installed Version is cdstv-4.3.0-b119 Reading deployment from "/etc/vdstv.conf". vds-httpd is running.. Stopping vds-httpd: [OK] avsdb is running.. stopping avsdb appmonitor is running.. stopping appmonitor Removing unnecessary redhat rpms ... 1) CDSM/VVIM

CDSM/VVIM Selected Taking backup of the existing httpd.conf file to httpd.conf-backup at /arroyo/www/conf/ Taking backup of the existing avsdb.config file to restore Loaded plugins: security Skipping security plugin, no data Setting up Update Process Resolving Dependencies Skipping security plugin, no data --> Running transaction check ---> Package vds_cache2app.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_cdsm.x86_64 0:4.4.1-tv0.3 set to be updated ---> Package vds_collectd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_config.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_config-cdsm.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_framework.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_httpd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_isa.x86_64 0:4.4.1-tv0.1.1 set to be updated ---> Package vds_php.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_snmp_cdsm.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_statsd.x86_64 0:4.4.1-tv0.1 set to be updated

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-4 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

---> Package vds_syslogtools.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_tavsdb.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_utils.x86_64 0:4.4.1-tv0.1 set to be updated --> Finished Dependency Resolution

Dependencies Resolved

======Package Arch Version Repository Size ======Updating: vds_cache2app x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 723 k vds_cdsm x86_64 4.4.1-tv0.3 tv-3.11.0-0b25 3.3 M vds_collectd x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 442 k vds_config x86_64 4.4.1-tv0.3.1 tv-3.11.0-0b25 73 k vds_config-cdsm x86_64 4.4.1-tv0.3.1 tv-3.11.0-0b25 13 k vds_framework x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 3.7 M vds_httpd x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 41 M vds_isa x86_64 4.4.1-tv0.1.1 tv-3.11.0-0b25 74 M vds_php x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 8.5 M vds_snmp_cdsm x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 2.7 M vds_statsd x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 142 k vds_syslogtools x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 73 k vds_tavsdb x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 4.1 M vds_utils x86_64 4.4.1-tv0.1 tv-3.11.0-0b25 91 k

Transaction Summary ======Install 0 Package(s) Upgrade 14 Package(s)

Total download size: 139 M Downloading Packages: ------Total 22 GB/s | 139 MB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Updating : vds_framework 1/28 Updating : vds_cache2app 2/28 Updating : vds_php 3/28vds-httpd is already stopped.

Updating : vds_httpd 4/28 Updating : vds_snmp_cdsm 5/28Stopping statsd: [OK]

Updating : vds_statsd 6/28Stopping collectd: [OK]

Updating : vds_collectd 7/28 Updating : vds_syslogtools 8/28 warning: /opt/syslog-ng/etc/cdstv-syslog-ng.conf created as /opt/syslog-ng/etc/cdstv-syslog-ng.conf.rpmnew Updating : vds_tavsdb 9/28 Updating : vds_utils 10/28 Updating : vds_config 11/28Loading File List HW does not appear to be Merrimack... No work to do here.

Updating : vds_isa 12/28 Updating : vds_cdsm 13/28

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-5 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

Updating : vds_config-cdsm 14/28 Cleanup : vds_syslogtools 15/28 Cleanup : vds_utils 16/28 Cleanup : vds_snmp_cdsm 17/28 Cleanup : vds_config-cdsm 18/28 Cleanup : vds_framework 19/28 Cleanup : vds_php 20/28 Cleanup : vds_isa 21/28 Cleanup : vds_collectd 22/28 Cleanup : vds_httpd 23/28 Cleanup : vds_config 24/28 Cleanup : vds_cdsm 25/28 Cleanup : vds_statsd 26/28 Cleanup : vds_cache2app 27/28 Cleanup : vds_tavsdb 28/28

Updated: vds_cache2app.x86_64 0:4.4.1-tv0.1 vds_cdsm.x86_64 0:4.4.1-tv0.3 vds_collectd.x86_64 0:4.4.1-tv0.1 vds_config.x86_64 0:4.4.1-tv0.3.1 vds_config-cdsm.x86_64 0:4.4.1-tv0.3.1 vds_framework.x86_64 0:4.4.1-tv0.1 vds_httpd.x86_64 0:4.4.1-tv0.1 vds_isa.x86_64 0:4.4.1-tv0.1.1 vds_php.x86_64 0:4.4.1-tv0.1 vds_snmp_cdsm.x86_64 0:4.4.1-tv0.1 vds_statsd.x86_64 0:4.4.1-tv0.1 vds_syslogtools.x86_64 0:4.4.1-tv0.1 vds_tavsdb.x86_64 0:4.4.1-tv0.1 vds_utils.x86_64 0:4.4.1-tv0.1

Complete! Loaded plugins: security Setting up Group Process Package vds_cache2app-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_statsd-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_utils-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_snmp_cdsm-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_tavsdb-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_config-4.4.1-tv0.3.1.x86_64 already installed and latest version Package vds_isa-4.4.1-tv0.1.1.x86_64 already installed and latest version Package syslog-ng-3.0.5-1.rhel5.x86_64 already installed and latest version Package vds_httpd-4.4.1-tv0.1.x86_64 already installed and latest version Package monit-5.3-1.el5.x86_64 already installed and latest version Package vsftpd-2.0.5-28.el5.x86_64 already installed and latest version Package vds_cdsm-4.4.1-tv0.3.x86_64 already installed and latest version Package vds_framework-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_config-cdsm-4.4.1-tv0.3.1.x86_64 already installed and latest version Package vds_php-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_collectd-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_syslogtools-4.4.1-tv0.1.x86_64 already installed and latest version No packages in any requested group available to install or update Unmounting /mnt/cdrom New image installed : cdstv-4.4.1-b4 File /etc/vdsServices.conf already exists. Preserving web UI access configuration to HTTP network protocol on upgrade/downgrade process Removal of httpd.conf-backup file Restoring avsdb.config-restore to avsdb.config vdsinit completed. Please reboot the device.

Step 6 Enter the following command to verify the version of VDS-TV installed.

# head /arroyo/image/tags

cdstv-4.4.1-b4

Step 7 Enter the following command to disable the services.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-6 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

# vdsServices disable

Step 8 Reboot the CDE. Step 9 Type the following command to verify the kernel version installed.

# uname -r

2.6.32-4.4.1_tv0.1

Step 10 Enter the following command to manually start the services. # vdsServices start

The CDE110 now has the Release 4.4 VDS-TV software installed. The next step is to initially configure the CDE110, which requires you to run the vdsconfig script and answer the prompts appropriately for your deployment. See the “Preparing to Initially Configure the CDEs” section on page 2-17 for more information.

Installing the Software on a CDE220 or CDE420 or CDE250 or CDE460 or CDE280

CDE280 BIOS and CIMC Settings

Before installing the software on CDE 280, verify that the BIOS and CIMC settings for CDE280 is configured as listed in the Table 2-1.

Table 2-1 CDE 280 BIOS and CIMC Settings

Settings Options Container Image Image file ucs-c240-huu-2.0.9c.iso BIOS_version Version Number C240M4.4.0.9a.0.120120151913 BIOS Main Shipping Order TPM Support Disabled BIOS Advanced Settings Processor Configuration Intel(R) Hyper-Threading Techno Disabled Number of Cores Enabled All Execute Disable Enabled Intel(R) VT Disabled Intel(R) VT-d Disabled

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-7 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

Settings Options Interrupt Remapping Enabled PassThrough DMA Disabled Intel(R) VT-d Coherency Support Disabled Intel(R) VT-d ATS Support Disabled CPU Performance Enterprise Hardware Prefetcher Enabled Adjacent Cache Line Prefetcher Enabled DCU Streamer Prefetch Enabled DCU IP Prefetcher Enabled Direct Cache Access Support Auto Power Technology Disabled Enhanced Intel Speedstep(R) Tec Enabled Intel(R) Turbo Boost Technology Enabled Processor C3 Report Disabled Processor C6 Report Enabled Processor Power state C1 Enhanc Enabled P-STATE Coordination HW ALL Energy Performance Tuning OS Energy Performance Performance Package C State Limit C6 Retention Extended APIC XAPIC Workload Configuration Balanced Memory configuration Select Memory RAS Maximum Performance NUMA Enabled Channel Interleaving Auto Rank Interleaving Auto Patrol Scrub Enabled Demand Scrub Enabled Altitude 300 M QPI Configuration QPI Link Frequency Select Auto Snoop Mode Home Snoop USB Configuration Legacy USB Support Enabled Port 60/64 Emulation Enabled XHCI Mode Disabled

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-8 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

Settings Options PCI Configuration MMIO above 4GB Enabled SR-IOV Support Enabled Serial Configuration Out-of-Band Management Disabled Console Redirection Disabled Terminal Type VT100 Bits per second 9600 Flow Control None Putty KeyPad ESCN Redirection After BIOS POST Enable (Default) LOM and PCIe slot Configuration CDN Support for VIC Disabled PCI ROM CLP Disabled PCH SATA Mode AHCI All Onboard LOM Ports Enabled LOM Port 0 OptionROM Enabled LOM Port 1 OptionROM Enabled All PCIe Slots OptionROM Enabled PCIe Slot:1 OptionROM Enabled PCIe Slot:2 OptionROM Enabled PCIe Slot:3 OptionROM Disabled PCIe Slot:4 OptionROM Enabled PCIe Slot:5 OptionROM Enabled PCIe Slot:6 OptionROM Enabled PCIe Slot:MLOM OptionROM Enabled PCIe Slot:HBA OptionROM Enabled PCIe Slot:N1 OptionROM Enabled PCIe Slot:N2 OptionROM Enabled Server Management FRB-2 Timer Enabled OS Watchdog Timer Disabled OS Watchdog Timer Timeout 10 Mins. OS Watchdog Timer Policy Power Down

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-9 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

The Cisco CDE220 can be used as a Streamer, ISV, or dense Vault, the Cisco CDE420 can be used as a Vault or Caching Node, the Cisco CDE 250 can be used as a Vault/Cache Gateway and Streamer, the Cisco CDE 460 can be used as a Vault and the Cisco CDE 280 can be used as Cache Gateway and Streamer. To upgrade the OS and software image on a CDE220 or CDE420 or CDE250 or CDE460 or CDE 280, do the following:

Step 1 If the Cisco CDE is not powered on, press the front panel power switch on the server. The operating system boots. Step 2 Log in as root with the default password.

Note To change the default password, use the passwd command.

Step 3 To copy the tv_repo-4.4.1-x86_64.iso and vdsinit software files on the CDE hardware, configure the management interface. a. To configure the Ethernet interface (eth0), which is used to connect to the management network, use a text editor to modify the file /etc/sysconfig/network-scripts/ifcfg-eth0 and add the following lines: – DEVICE=eth0 – BOOTPROTO=static – ONBOOT=yes – IPADDR=ip_address_for_eth0 – NETMASK=netmask_for_eth0 For example: DEVICE=eth0 BOOTPROTO=static ONBOOT=yes IPADDR=172.22.97.162 NETMASK=255.255.255.128

b. Save and close the ifcfg-eth0 file. c. To configure the network characteristics, use a text editor to modify the file /etc/sysconfig/network and add the following lines: – NETWORKING=yes – HOSTNAME=name – GATEWAY=gateway_ip_address – GATEWAYDEV =device_id_number – NOZEROCONF =yes For example: NETWORKING=yes HOSTNAME=cdsm162 GATEWAY=172.22.97.129 GATEWAYDEV=eth0 GATEWAY=yes

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-10 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

The gateway_ip_address is the default gateway IP address,the address of the interface on the router that is directly attached to the CDE110 eth0 interface. d. Save and close the network file. e. To restart the network, issue the following command: [root]# /etc/init.d/network restart

Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ]

[root]#

Step 4 Use the scp command to copy the VDS-TV 4.4 ISO file. For example, if the remote server that you downloaded the software files to has the IP address 172.22.97.109, and the files are stored in the CDSdownloads directory, the following command is used: # scp -p 172.22.97.109:/CDSdownloads/tv_repo-4.4.1-x86_64.iso /root # scp -p 172.22.97.109:/CDSdownloads/vdsinit-4.4.1 /root

Step 5 For CDE250 hardware, before upgrading to Release 4.4, reinstall SuperDoctor version 2.111 and upgrade Firmware to version 3.0.6 using the instructions specified in the document CDE 250 IPMI Firmware v3.06 Upgrade. Step 6 Run the vdsinit script to upgrade the ISO image to Release 4.4. When prompted, select the deployment type of the server, choose 1 for an Interactive Services Architecture (ISA) deployment, and 2 for an RTSP/FSI deployment.

Note If you are installing CDS in an RTSP environment and using the Real-Time Capture feature with call signs and home IDs, you must seed the database with the HomeID field for Real-Time Capture (non-Media Scheduler) by running run the cv-account-add-homeid0 script as user isa in the /home/isa directory on the Vault (or ISV).

The following example shows the vdsinit output for an Real Time Streaming Protocol (RTSP) deployment: # cd /root # ./vdsinit-4.4.1 tv_repo-4.4.1-x86_64.iso

Note This example log output may not match the final image log output.

EXAMPLE Log Output for Vault installation Mounting tv_repo-4.4.1-0b1-x86_64.iso at /mnt/cdrom Currently Installed Version is cdstv-4.3.0-b106 Reading deployment from "/etc/vdstv.conf". avsdb is running.. stopping avsdb appmonitor is running.. stopping appmonitor Removing unnecessary redhat rpms ... 1) ISA 2) RTSP/FSI 3) PEG/BARKER

ISA Selected Taking backup of the existing avsdb.config file to restore

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-11 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package cddm.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package cserver-prod.x86_64 0:4.4.1-tv0.1.1.1 set to be updated ---> Package kernel-vds.x86_64 0:2.6.32-4.4.1_tv0.1 set to be updated ---> Package vds_avslauncher.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_cache2app.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_collectd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_config.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_config-isa.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_framework.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_isa.x86_64 0:4.4.1-tv0.1.1 set to be updated ---> Package vds_snmp.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_statsd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_syslogtools.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_tavsdb.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_tools.x86_64 0:4.4.1-tv0.1.1 set to be updated ---> Package vds_utils.x86_64 0:4.4.1-tv0.1 set to be updated --> Finished Dependency Resolution

Dependencies Resolved

======Package Arch Version Repository Size ======Updating: cddm x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 22 k cserver-prod x86_64 4.4.1-tv0.1.1.1 tv-3.9.1-0b24 5.7 M kernel-vds x86_64 2.6.32-4.4.1_tv0.1 tv-3.9.1-0b24 71 M vds_avslauncher x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 32 k vds_cache2app x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 723 k vds_collectd x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 442 k vds_config x86_64 4.4.1-tv0.3.1 tv-3.9.1-0b24 73 k vds_config-isa x86_64 4.4.1-tv0.3.1 tv-3.9.1-0b24 12 k vds_framework x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 3.7 M vds_isa x86_64 4.4.1-tv0.1.1 tv-3.9.1-0b24 74 M vds_snmp x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 2.8 M vds_statsd x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 142 k vds_syslogtools x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 73 k vds_tavsdb x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 4.1 M vds_tools x86_64 4.4.1-tv0.1.1 tv-3.9.1-0b24 114 k vds_utils x86_64 4.4.1-tv0.1 tv-3.9.1-0b24 91 k

Transaction Summary ======Install 0 Package(s) Upgrade 16 Package(s)

Total download size: 163 M Downloading Packages: ------Total 25 GB/s | 163 MB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction ^M Updating : vds_framework 1/32 ^M Updating : cddm 2/32 ^M Updating : vds_tools 3/32 ^M Updating : vds_cache2app 4/32 ^M Updating : vds_snmp 5/32Stopping statsd: [OK]

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-12 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

^M Updating : vds_statsd 6/32Stopping collectd: [OK]

^M Updating : vds_collectd 7/32 ^M Updating : vds_syslogtools 8/32 warning: /opt/syslog-ng/etc/cdstv-syslog-ng.conf created as /opt/syslog-ng/etc/cdstv-syslog-ng.conf.rpmnew ^M Updating : vds_tavsdb 9/32 ^M Updating : vds_utils 10/32 ^M Updating : vds_config 11/32Loading File List driver: igb driver: igb ...done

Processing File List ...done

Moving modprobe.conf into place ...done

^M Updating : kernel-vds 12/32 ^M Updating : cserver-prod 13/32 ^M Updating : vds_isa 14/32 ^M Updating : vds_avslauncher 15/32 ^M Updating : vds_config-isa 16/32 ^M Cleanup : vds_syslogtools 17/32 ^M Cleanup : vds_utils 18/32 ^M Cleanup : kernel-vds 19/32 ^M Cleanup : vds_framework 20/32 ^M Cleanup : vds_avslauncher 21/32 ^M Cleanup : vds_isa 22/32 ^M Cleanup : vds_collectd 23/32 ^M Cleanup : vds_statsd 24/32 ^M Cleanup : vds_tools 25/32 ^M Cleanup : vds_snmp 26/32 ^M Cleanup : cddm 27/32 ^M Cleanup : cserver-prod 28/32 ^M Cleanup : vds_config-isa 29/32 ^M Cleanup : vds_config 30/32 ^M Cleanup : vds_cache2app 31/32 ^M Cleanup : vds_tavsdb 32/32

Updated: cddm.x86_64 0:4.4.1-tv0.1 cserver-prod.x86_64 0:4.4.1-tv0.1.1.1 kernel-vds.x86_64 0:2.6.32-4.4.1_tv0.1 vds_avslauncher.x86_64 0:4.4.1-tv0.1 vds_cache2app.x86_64 0:4.4.1-tv0.1 vds_collectd.x86_64 0:4.4.1-tv0.1 vds_config.x86_64 0:4.4.1-tv0.3.1 vds_config-isa.x86_64 0:4.4.1-tv0.3.1 vds_framework.x86_64 0:4.4.1-tv0.1 vds_isa.x86_64 0:4.4.1-tv0.1.1 vds_snmp.x86_64 0:4.4.1-tv0.1 vds_statsd.x86_64 0:4.4.1-tv0.1 vds_syslogtools.x86_64 0:4.4.1-tv0.1 vds_tavsdb.x86_64 0:4.4.1-tv0.1 vds_tools.x86_64 0:4.4.1-tv0.1.1 vds_utils.x86_64 0:4.4.1-tv0.1

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-13 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Upgrading the New CDEs with Release 4.4 VDS-TV Software

Package monit-5.3-1.el5.x86_64 already installed and latest version Package apache2-mod_authnz_external-3.1.0-2.36.x86_64 already installed and latest version Package cddm-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_cache2app-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_utils-4.4.1-tv0.1.x86_64 already installed and latest version Package kernel-vds-2.6.32-4.4.1_tv0.1.x86_64 already installed and latest version Package vds_tools-4.4.1-tv0.1.1.x86_64 already installed and latest version Package vds_statsd-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_tavsdb-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_framework-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_snmp-4.4.1-tv0.1.x86_64 already installed and latest version Package cserver-prod-4.4.1-tv0.1.1.1.x86_64 already installed and latest version Package vds_avslauncher-4.4.1-tv0.1.x86_64 already installed and latest version Package cds-vqe-3.5.0-13.x86_64 already installed and latest version Package vds_config-4.4.1-tv0.3.1.x86_64 already installed and latest version Package vds_collectd-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_syslogtools-4.4.1-tv0.1.x86_64 already installed and latest version No packages in any requested group available to install or update Setting up Group Process Package vds_config-isa-4.4.1-tv0.3.1.x86_64 already installed and latest version Package vds_isa-4.4.1-tv0.1.1.x86_64 already installed and latest version No packages in any requested group available to install or update Unmounting /mnt/cdrom New image installed : cdstv-4.4.1-b4 File /etc/vdsServices.conf already exists. Restoring avsdb.config-restore to avsdb.config vdsinit completed. Please reboot the device.

Step 7 Enter the following command to verify the version of VDS-TV installed.

# head /arroyo/image/tags

cdstv-4.4.1-b4

Step 8 Enter the following command to disable the services

# vdsServices disable

Step 9 Reboot the CDE. Step 10 Type the following command to verify the kernel version installed.

# uname -r

2.6.32-4.4.1_tv0.8

Warning Add the line allocation unit size 0 in /arroyo/test/vault/setupfile before starting the CServer when upgrading from 3.2.x release to release 4.4 else the contents will be lost while downgrading from 4.4 to older releases and CServer will have to be started with -c option

Step 11 Enter the following command to manually start the services.

# vdsServices start

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-14 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Imaging a VDS Server with 64-Bit OS using a DVD

The CDE now has the 64-bit OS, and the Release 4.4 VDS-TV software installed. The next step is to initially configure the CDE, which requires you to run the vdsconfig script, and answer the prompts appropriately for your deployment. See the “Preparing to Initially Configure the CDEs” section on page 2-17 for more information.

Imaging a VDS Server with 64-Bit OS using a DVD

If the VDS server upgrade process is interrupted because of power failure or for some similar reason, and if the upgrade was corrupted, you can use the DVD imaging process to load the OS and Release 4.4 software files. The DVD ISO imaging process can also be used for a clean installation. After the imaging is complete, you need to run the vdsinit script to install the software.

To image a VDS server with the OS required to run the VDS-TV Release 4.4 software, do the following:

Step 1 Download the tv_full-4.4.1-x86_64.iso file from the Cisco software download website. See the “Getting the Cisco VDS-TV Software Files for Release 4.4” section on page 1-5 for more information. Step 2 Burn the ISO image file to a DVD. Step 3 Connect USB slim drive to CDE server. Step 4 Insert the VDS-TV ISO image DVD into the USB slim drive. Step 5 Remove the external HDD/SSDs. Step 6 Reboot the server. Step 7 The auto installation begins automatically in 10 seconds. Press Enter to start the installation immediately. Step 8 First, the pre-installation scripts are executed and then a warning message is displayed and the user is prompted with YES or NO to erase the existing data and configure new file system partition.

Note The file system partitioning process can approximately take 1 hour or more. It depends on the platform where the fresh installation is done. At times, erase existing data message appears multiple times even on selecting YES, click YES multiple times to move to next screen.

Step 9 After partitioning, the image is transferred to hard drive and required packages are installed. Step 10 Reboot the server after successful installation. Step 11 For CDE 280, verify that the BIOS and CIMC settings is configured as listed in CDE280 BIOS and CIMC Settings, page 2-7

Note For CDE 220 hardware, once the server reboots do the following: • Press Ctrl+C and go to LSI Corp Config Utility. • Disable the MPTSAS disks from the CDE 220. • Check if PCI Raid option is displayed under Boot Priority Order. • Reboot the server by pressing Ctrl+C.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-15 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initial Configuration Sequence of the CDEs

Note Fresh installation using tv_full-4.4.1-x86_64.iso is not supported on CDE110. Only upgrade to VDS-TV 4.4 is supported.

Installing the VDS-TV software

Proceed with normal installation of the VDS-TV Release 4.4 software by running the vdsinit script. For detailed information on CDSM installation, refer Installing the Software on a CDE110/UCS C220 M4 Hardware, page 2-3. For detailed information on VDS-TV server installation, refer Installing the Software on a CDE220 or CDE420 or CDE250 or CDE460 or CDE280, page 2-7

Configuring the VDS-TV

Proceed with normal configuring of the VDS-TV For detailed information on configuring the VDS-TV hardware, see Initially Configuring the CDE110/UCS Hardware, page 2-18, Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280, page 2-23

Initial Configuration Sequence of the CDEs

This section describes the initial configuration sequence for a VVI and a VDS. A VVI includes of Caching Nodes and possibly split domain management. A VDS consists of Streamers and Vaults or ISVs.

VVI Initial Configuration Sequence

The order in which you initially configure the CDEs for VVI is very important. The CDSM (VVIM for Vaults and Caching Node) and all the Vaults and Caching Nodes in the VVIM domain must be configured first and brought online before the Stream Domain is configured. Following is a high-level view of the initial configuration order: 1. VVIM—See the “Initially Configuring the CDE110/UCS Hardware” section on page 2-18 for more information. Log in to the VVIM GUI as a user with Engineering access and configure the VVIM Setup page. 2. Vaults and Caching Nodes Log in to the VVIM GUI and configure each Vault and Caching Node. 3. Stream Manager (CDSM)—See the “Initially Configuring the CDE110/UCS Hardware” section on page 2-18 for more information. Log in to the CDSM GUI as a user with Engineering access and configure the CDSM Setup page. 4. Streamers—See the “Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280” section on page 2-23 for more information. Make sure a Streamer is configured completely and is displayed in the Stream Manager System Health Monitor page before moving on to the next Streamer. Log in to the Stream Manager GUI and configure each Streamer. 5. Repeat 3 and 4 for each Stream Domain in the VVI.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-16 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initial Configuration Sequence of the CDEs

6. Redundant VVIM and Stream Manager—See the “Initially Configuring the CDE110/UCS Hardware” section on page 2-18 for more information For more information about the CDSM (or VVIM) GUI, see the “Getting Started” chapter in either the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4 or the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Note In an ISA environment, the ISA services cannot be started until the Stream Manager is up and at least one Streamer in a Stream Domain has the VHO Setup and VHO ISA Setup settings configured.

VDS Initial Configuration Sequence

The only requirement with regard to the order in which you initially configure the CDEs for a VDS is that the CDSM must be configured first. The Vaults and Streamers are initialized next, followed by a second CDSM for redundancy. If the VDS consists of ISVs and CDSMs, initialize the primary CDSM first, followed by the ISVs, then the secondary CDSM.

Preparing to Initially Configure the CDEs

Before you run the initial configuration script, gather the following information: • IP address and subnet mask of the CDE management interface—Typically, the eth0 interface is used for the management interface. • IP address of the default gateway interface—This is the address of the interface on the router that is directly attached to the CDE management (eth0) interface. • Hostname for the CDE—Name of the device host. • Group ID—A unique user-defined value. All the VDS servers (ssv [ISV], Vault, Streamer, controller [CDSM]) that are part of the same system (managed by one CDSM) have the same group ID. This group ID should be unique across an enterprise. All the VDS servers that are part of a VVI have different group IDs depending on the number of managers (CDSMs and VVIMs). • Server ID—A unique user-defined value. The ID must be unique for each VDS device.

Note If you are installing a VVI system with split-domain management, the server ID for Streamers in a Stream Domain is generated by the Stream Manager.

• Replication group members—The VDS servers that are replication group members and the IP address of each member. The servers to include in a replication group depends on the network design for the VDS.

Note With the exception of the VDS server you are configuring, all the VDS servers (VVIMs, Stream Managers, ISVs, Caching Nodes, Vaults, and Streamers) that are members of the replication group should be configured at this time. The server you are configuring is not configured as a replication group member.

– In simple cases, because all the VDS servers share information with each other, all the servers are in each other’s replication group.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-17 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE110/UCS Hardware

– In more complex cases, only a subset of the servers are included in a replication group. As an example, if Streamers talk only to the CDSM, Vaults, and Streamers within a specific Streamer group, the Streamers replication group includes only these servers. In both the CDS and VVI, all the Vaults, Caching Nodes, and Streamers (or ISVs) are identified by an array ID, a group ID, and a server ID. In the CDSM GUI, the array ID identifies servers that are part of the same system, the group ID identifies servers that are part of the same group (Vault Group or Stream Group), and the server ID is a unique number that identifies the server. Table 2-2 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and .arroyorc files.

Table 2-2 ID Names in the CDSM GUI and CServer Files

CDSM GUI ID Name CServer ID Name Array ID on the Array Name page groupid Group ID on the Server-Level pages groupid Stream Group ID on the Server Setup page arrayid Cache Group ID on the Server Setup page arrayid Vault Group ID on the Server Setup page arrayid Stream Group ID on the Configuration Generator page arrayid

Note During the initialization process of a VDS server or after recovering a VDS server that has been down for less than an hour, the VDS database performs a complete synchronization. The database synchronization takes about five minutes before the server becomes ready for service. If the VDS server is down for a much longer time than an hour, the database synchronization takes longer than five minutes. The netstat command does not show the interfaces as being up until the synchronization has completed.

Initially Configuring the CDE110/UCS Hardware

To initially configure the CDE110/UCS hardware, do the following:

Step 1 Log in to the server as root. Step 2 Run the vdsconfig script. The script displays prompts with the default values in brackets. If a default value is correct, press Enter to accept the value; otherwise, enter the correct value and press Enter.

Note When bond interface is enabled, the user should first disable the bond configuration and then proceed with vdsconfig. The user can re-enable bonding on successful completion of vdsconfig.

[root]# vdsconfig

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-18 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE110/UCS Hardware

Improper use of this script may result in mis-configuring the device or making it inaccessible.

If a new image is installed on this server, a reboot is required before running vdsconfig. If a reboot is already performed, please continue. Otherwise, please exit and execute vdsconfig after rebooting the server

Do you want to continue ? (yes/no): y Enter management interface: eth0 Please ensure an IP address and netmask are configured for management interface eth0:

Select an option or an interface to re-configure/disable: 1. eth0 ip:10.197.102.25 mask:255.255.255.0 bcast:10.197.102.255 2. Configure another interface 3. Done Choice: 3 Backing up old scripts in /etc/sysconfig/network-scripts Writing new ifcfg-ethX scripts

Enter a hostname: VVIM Enter the number of the eth interface that connects to the gateway Enter the default gateway IP address: 10.197.102.1 Backing up /etc/sysconfig/network Writing new /etc/sysconfig/network Backing up /etc/hosts Writing new /etc/hosts Restarting network services, this may take a minute: Network services restarted; may take a few seconds to establish connectivity Reboot for hostname changes to take effect Network configuration complete

Please choose your platform from the following list of valid platforms:

1. 2U-SCSI-1 2. 3U-SCSI-1 3. 3U-SCSI-10 4. 3U-SCSI-11 5. 2U-SATA-1 6. 2U-SATA-2 7. 2U-SATA-10 8. 2U-SATA-11 9. 4U-SATA-1 10. 4U-SATA-2 11. 4U-SATA-3 12. 4U-SATA-10 13. 4U-SATA-11 14. 4U-SATA-12 15. CDE100-2C-1 16. CDE110-2C-1 17. CDE205-1C1-C 18. CDE220-2A-C 19. CDE220-2A-F 20. CDE220-2C1-C 21. CDE220-2C1-F 22. CDE220-2C2-C 23. CDE220-2C2-F 24. CDE220-2D1-C 25. CDE220-2D1-F 26. CDE220-2S1-C 27. CDE220-2S1-F 28. CDE220-2S3-C 29. CDE220-2S3-F 30. CDE220-2S4-C

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-19 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE110/UCS Hardware

31. CDE220-2S4-F 32. CDE420-4A-C 33. CDE420-4A-F 34. CDE420-4G-C 35. CDE420-4G-F 36. CDE250-2S5 37. CDE250-2S6 38. CDE250-2S8 39. CDE250-2S9 40. CDE250-2S10 41. CDE250-2G3 42. CDE250-2A4 43. CDE250-2A2 44. CDE460-4R1 45. CDE470-4R2 46. CDE460-4R3 47. CDE465-4R4 48. CDE280-2U1 49. CDE280-2U2 50. CDE280-2U3 51. CDE280-2U4 52. UCSC-220M4-2U1 Choice: 16

Please select a device role 1. cdsm Choice: 1

Select a role for this CDSM 1. CDS Manager (Single Management Domain for Content Storage, Caching & Streaming ) 2. VVI Manager (Split Domain Model - Content Storage and Caching Domain) 3. CDS Manager (Split Domain Model - Streaming Domain, with or without local Content Storage) Choice: 2 Please enter a Group ID(Array ID): 77 Please enter a server ID: 25

Note If this is the Stream Manager, choose option 3. The vdsconfig script displays the following questions: Is this Streaming Domain going to use CCP as Cache Fill Protocol? (yes/no) [y]: Y Is this the first CDS Manager getting added to this domain? (yes/no) [y]: Enter Enter the name of this Stream Domain: StreamDomain1 Enter the IP address of the VVIM: 172.22.99.109

Retrieved Server ID '1001' from '172.22.99.109' Please enter a group ID: 12345

For a VVI, the group ID for the VVIM and Stream Manager should be the same. This group ID is the ID of the array. The VVIM assigns the server ID to the Stream Manager. For a VVI in a split domain, when using CCP as the Cache Fill Protocol, the group ID for the VVIM and Streamer Manager must be same; however, when using HTTP as the Cache Fill Protocol, the group ID can be different in two domains. During the running of the vdsconfig script, the Stream Manager communicates with the VVIM to get a range of group IDs and server IDs to use in the Stream Domain. If the Stream Manager is unable to connect to the VVIM, the VVIM administrator can manually generate the IDs and send the information to the Stream Manager installer for manual entry. For more information, see the “Identifying Server IDs and Group IDs for VVI with Split-Domain Management” section in the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4 or the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-20 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE110/UCS Hardware

Note With the exception of the server you are configuring, all the CDS servers (VVIMs, Stream Managers, ISVs, Vaults, Caching Nodes, and Streamers) that are members of the replication group should be configured at this time. The server you are configuring is not configured as a replication group member.

In the following example, the configuration of the VDS servers shows generalized input values. Option 4, cdsmgw, is the Stream Manager. Add the Stream Manager ip by selecting option 4 as replication group member. While configuring CDSM, option vvimgw would be listed and we need to add the VVIM as replication member in the CDSM.

Writing new configuration to /home/isa/.arroyorc

No existing replication group information found Do you want to configure replication group members now? (yes/no): y Do you want to add another replication group member? (yes/no): y

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vmaster 3. vault 4. cache 5. cdsmgw 6. controller 7. exit Choice:

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vmaster 3. vault 4. cache 5. cdsmgw 6. controller 7. exit Choice: 3 Enter an IP address for new vault: 10.197.102.28 Do you want to add another replication group member? (yes/no): y

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vmaster 3. vault 4. cache 5. cdsmgw 6. controller 7. exit Choice: 3 Enter an IP address for new vault: 3 Enter an IP address for new vault: 10.197.102.29 Do you want to add another replication group member? (yes/no): y

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vmaster 3. vault 4. cache 5. cdsmgw 6. controller 7. exit Choice: c

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-21 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE110/UCS Hardware

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vmaster 3. vault 4. cache 5. cdsmgw 6. controller 7. exit Choice: 4 Enter an IP address for new cache: 10.197.102.30 Do you want to add another replication group member? (yes/no): y

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vmaster 3. vault 4. cache 5. cdsmgw 6. controller 7. exit Choice: 7 Do you want to add another replication group member? (yes/no): n Configuring CDSM Do you want to enable CDSM Redundancy ? (yes/no): no Is this node getting added to an existing deployment ? (yes/no): no Do you want to enable Exporter ? (yes/no): no Do you want to enable Importer ? (yes/no): no Do you want to enable MSA Logging ? (yes/no): no

Choose Network Protocol to access CDSM GUI:

1. HTTP 2. HTTPS 3. HTTP and HTTPS Choice: 3 Writing .arroyorc Writing VDS Service config file Do you want to configure Remote Authentication for CDSM GUI? (yes/no): n ATTENTION!! svrinit failed. Please run svrinit manually and start statsd after vdsconfig is completed. CDSM configuration finished Serial Console BAUD speed is configured as '115200'. Do you wish to change it (yes/no): n vdsconfig finished, please use CDSM to complete configuration

Step 3 Reboot the CDSM. # reboot

Step 4 Enter the following command and press Enter, to start the services # vdsServices start

Step 5 To verify that the VDS manager (VVIM, Stream Manager or CDSM) is operational, using your web browser, enter the IP address of your VDS manager. For example, if the IP address of your CDSM is 192.168.0.236, you can access it by entering http://192.168.0.236 in the address or location text box of your browser program. The System Login page is displayed (see Figure 2-1).

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-22 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

Figure 2-1 CDSM Login Page

Step 6 Log in to the VDS manager GUI. Enter admin as the user name and admin as the password, and click Log In. If you are unable to log in with the user name arroyo and the password admin, log in to the CDE110 Linux command line, run the /home/stats/resetpw command, and log in to the VDS manager GUI again. The VVIM Setup page or the CDSM Setup page is displayed. Step 7 Select 4.X as the CServer Version. Step 8 Verify all the other configurations in the page and click Submit. Step 9 Use the VVIM GUI or CDSM GUI to complete the configuration. For more information, see one of the following: • For information about an ISA deployment, see the “Getting Started” chapter in the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4. • For information about an RTSP deployment, see the “Getting Started” chapter in the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

To install the VDS-TV software and initially configure the CDE220, CDE250, CDE420 or CDE460 as a Vault, Caching Node, or Streamer, do the following:

Step 1 Log in to the CDE as root. Step 2 Run the vdsconfig script. The script displays prompts with the default values in brackets. If a default value is correct, press Enter to accept the value; otherwise, enter the correct value and press Enter.

Note When bond interface is enabled, the user should first disable the bond configuration and then proceed with vdsconfig. The user can re-enable bonding on successful completion of vdsconfig.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-23 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

[root]# vdsconfig

ATTENTION!!! The vdsconfig script should be run only to configure the device after an image installation. This script modifies the network and other critical configurations based on the deployment type. Improper use of this script may result in mis-configuring the device or making it inaccessible.

Do you want to continue ? (yes/no): y Enter management interface: eth0 Please ensure an IP address and netmask are configured for management interface eth0:

Select an option or an interface to re-configure/disable: 1. eth0 ip:10.197.86.207 mask:255.255.255.0 bcast:10.197.86.255 2. Configure another interface 3. Done Choice: 3 Backing up old scripts in /etc/sysconfig/network-scripts Writing new ifcfg-ethX scripts

Enter a hostname: TWC-MKT3-S2-207 Enter the number of the eth interface that connects to the gateway Enter the default gateway IP address: 10.197.86.1 Backing up /etc/sysconfig/network Writing new /etc/sysconfig/network Backing up /etc/hosts Writing new /etc/hosts Restarting network services, this may take a minute: Network services restarted; may take a few seconds to establish connectivity Reboot for hostname changes to take effect Network configuration complete

Please choose your platform from the following list of valid platforms:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-24 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

24. CDE220-2D1-C 25. CDE220-2D1-F 26. CDE220-2S1-C 27. CDE220-2S1-F 28. CDE220-2S3-C 29. CDE220-2S3-F 30. CDE220-2S4-C 31. CDE220-2S4-F 32. CDE420-4A-C 33. CDE420-4A-F 34. CDE420-4G-C 35. CDE420-4G-F 36. CDE250-2S5 37. CDE250-2S6 38. CDE250-2S8 39. CDE250-2S9 40. CDE250-2S10 41. CDE250-2G3 42. CDE250-2A4 43. CDE250-2A2 44. CDE460-4R1 45. CDE470-4R2 46. CDE460-4R3 47. CDE465-4R4 48. CDE280-2U1 49. CDE280-2U2 50. CDE280-2U3 51. CDE280-2U4 52. UCSC-220M4-2U1 Choice: 51

Please select a device role 1. streamer Choice: 1 Is this Server going to get added to a Stream Domain in a CDN Split Domain Management Environment ? (yes/no): no Please enter a Group ID(Array ID): 3000 Please enter a server ID: 1754 Enter Stream Control interface (Hit 'Enter' to skip) Writing new configuration to /home/isa/.arroyorc

No existing replication group information found Do you want to configure replication group members now? (yes/no): yes Do you want to add another replication group member? (yes/no): y

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vault 3. streamer 4. cache 5. controller 6. cdsmvip 7. exit Choice: 5 Enter an IP address for new controller: 10.197.86.202 Do you want to add another replication group member? (yes/no): yes

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vault 3. streamer 4. cache 5. controller 6. cdsmvip

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-25 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

7. exit Choice: 2 Enter an IP address for new vault: 10.197.86.211 Do you want to add another replication group member? (yes/no): yes

Select a role for the new replication group member. Select 'exit' to exit this menu 1. ssv 2. vault 3. streamer 4. cache 5. controller 6. cdsmvip 7. exit Choice: 3 Enter an IP address for new streamer: 10.197.86.213 Do you want to add another replication group member? (yes/no): n Configuring ISA ecosystem Is this node getting added to an existing deployment ? (yes/no) : no Writing VDS Service config file Run svrinit to seed database? (yes/no) : n Is this a Distributed Content Storage deployment? (yes/no) : yes Subnet Mask for Virtual IP failover : 255.255.255.0 ISA ecosystem configuration finished Serial Console BAUD speed is configured as '9600'. Do you wish to change it (yes/no): n vdsconfig finished, please use CDSM to complete configuration

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-26 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

Note If the device role selected is a option 3 (Streamer), the vdsconfig script displays the following questions: Is this server going to get added to a Stream Domain in a CDN Split Domain Management Environment? (yes/no) [y]: y Is this Stream Domain going to use CCP as Cache Fill Protocol? (yes/no) [y]: y Enter the IP address of the Stream Manager:

For Streamers in a VVI using CCP, the Streamer communicates with the Stream Manager to get a server ID. If the Streamer is unable to connect to the Stream Manager, the Stream Manager administrator can manually generate the server ID and send the information to the Streamer installer for manual entry. For more information, see the “Identifying Server IDs and Group IDs for VVI with Split-Domain Management” section in the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4or the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Note If the device role is a Streamer, you have the option to enter the Stream Control interface using the vdsconfig script, or later through the CDSM GUI.

Writing new configuration to /home/isa/.arroyorc

No existing replication group information found Do you want to configure replication group members now? (yes/no) [y]:

There are currently no replication group members. Do you want to add another replication group member? (yes/no) [y]:

Select a role for the new replication group member: 1. ssv 2. vault 3. streamer 4. cdsm 5. cache

Choice: device_role Enter an IP address for new CDS_device: IP_Address

Current replication group members: device_role IP_Address

Do you want to add another replication group member? (yes/no) [n]: n

Note For RTSP deployments, the vdsconfig script displays the following questions: Is this an NGOD deployment (yes/no): Choose NPT Syntax: 1. NGOD 2. NGOD_SC 3. Standard Choice [NGOD]:3 Writing /home/isa/bss/scripts/arroyo-env.sh Writing /home/isa/bss/scripts/arroyo-site-env.sh Setting attributes for AVSRTSPServer Do you want to enable Redirect Server ? (yes/no) [y]: n Do you want to enable Authentication Server ? (yes/no) [y]: n

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-27 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

Is this node getting added to an existing deployment? (yes/no) [y]: n Started avsdb, verify with "arroyo status" Starting statsd Run svrinit to seed database? (yes/no) [n]: y Running svrinit

Note Always select yes because you must seed the database whenever you add a new CDE to a network. You are asked to enter the IP address, netmask, hostname, and gateway for the CDE you are configuring. These are the same parameters you entered when you started running this script.

Please enter an IP address for svrinit: mgmt_ip_address Please enter a netmask for svrinit: mgmt_netmask Please enter a hostname for svrinit: hostname Please enter a gateway for svrinit gateway

Note If you receive an error message indicating the database is unavailable and cannot be set up, enter the following commands to initialize the database tables for a VDS server in an ISA environment:

[root]# service avsdb start

Enter the following commands to initialize the database tables for a VDS server in an RTSP environment: [root]# service avsdb start

Note For ISA deployments, the vdsconfig script displays the following question: Is this an IPTV deployment with Dual CAS? (yes/no) [n]:Enter

Writing /home/isa/bss/scripts/arroyo-env.sh Writing /home/isa/bss/scripts/arroyo-site-env.sh Setting attributes for AVSRTSPServer Do you want to enable Redirect Server ? (yes/no) [y]: n Do you want to enable Authentication Server ? (yes/no) [y]: n Do you want to enable Watermark Server ? (yes/no) [y]: n Is this node getting added to an existing deployment ? (yes/no) [y]: y

Starting database sync...

BDB2525 No log files found 1 size: 4180 2 size: 3148 3 size: 2136 4 size: 11412 5 size: 4180 6 size: 3148 7 size: 17628 8 size: 5208 10 size: 60 11 size: 1104 12 size: 52 14 size: 60 15 size: 2492

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-28 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

16 size: 156 17 size: 3164 18 size: 144 19 size: 180 20 size: 160 21 size: 1164 22 size: 16 23 size: 4228 24 size: 164 25 size: 14800 27 size: 1108 28 size: 3508 29 size: 156 30 size: 1108 31 size: 276 32 size: 1916 33 size: 1496 34 size: 1880 35 size: 3672 36 size: 6676 37 size: 1548 38 size: 184 39 size: 1748 40 size: 1492 41 size: 212 42 size: 212 43 size: 244 44 size: 144 45 size: 280 46 size: 156 48 size: 1024 49 size: 224 50 size: 660 51 size: 340 52 size: 2132 53 size: 1816 54 size: 440 56 size: 1440 57 size: 4244 58 size: 7468 59 size: 336 60 size: 204 63 size: 5336 64 size: 204 65 size: 24 66 size: 17732 70 size: 164 71 size: 1236 72 size: 5336 74 size: 3348 75 size: 2140 76 size: 5260 77 size: 12436 78 size: 6240 79 size: 340 80 size: 11412 81 size: 228 82 size: 24 83 size: 2208 84 size: 2128 85 size: 4348 86 size: 1168 88 size: 4180 89 size: 96

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-29 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

90 size: 2084 91 size: 84 92 size: 1444 93 size: 512 94 size: 172 95 size: 1512 96 size: 288 97 size: 2412 98 size: 5644 99 size: 160 100 size: 84 110 size: 476 111 size: 564 112 size: 5228 113 size: 88 115 size: 40 116 size: 292 117 size: 236 119 size: 1432 120 size: 5380 121 size: 1484 122 size: 14780 125 size: 24 126 size: 1376 128 size: 1296 130 size: 2292 131 size: 400 132 size: 144 134 size: 16488 135 size: 124 136 size: 2540 137 size: 2540 138 size: 2540 139 size: 1044 140 size: 10160 141 size: 3292 145 size: 116 146 size: 108 147 size: 360 148 size: 396 150 size: 1444 151 size: 184 152 size: 192 153 size: 11412 155 size: 1572 156 size: 832 157 size: 204 158 size: 292 159 size: 468 160 size: 240 161 size: 428 162 size: 2612 165 size: 672 166 size: 2192 167 size: 592 169 size: 272 171 size: 1168 175 size: 1208 180 size: 2724 181 size: 2396 182 size: 1120 183 size: 152 184 size: 164 185 size: 212

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-30 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

191 size: 628 192 size: 6228 195 size: 120 197 size: 140 200 size: 21772 204 size: 60 205 size: 16 206 size: 6292 207 size: 108 208 size: 1140 210 size: 2548 211 size: 2548 212 size: 240 213 size: 2732 214 size: 216 215 size: 104 220 size: 92 230 size: 1288 231 size: 1500 250 size: 80 251 size: 8352 252 size: 28 253 size: 3200 254 size: 416 255 size: 252 256 size: 104 257 size: 3264 266 size: 24656 267 size: 80 270 size: 660 271 size: 156 272 size: 144 273 size: 88 274 size: 28 275 size: 32 276 size: 32 282 size: 20 283 size: 184 285 size: 33456 290 size: 2556 353 size: 564 354 size: 51664 355 size: 11776 356 size: 1144 357 size: 2108 358 size: 20 359 size: 1316 360 size: 40 361 size: 1088 362 size: 1580 363 size: 44 364 size: 680 365 size: 4308 366 size: 1452 367 size: 192 368 size: 1436 369 size: 408 370 size: 520 371 size: 1592 372 size: 76 373 size: 208 374 size: 216 375 size: 84 376 size: 2964

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-31 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

377 size: 856 378 size: 592 379 size: 304 380 size: 276 381 size: 1100 382 size: 576 383 size: 3164 384 size: 2264 385 size: 2264 386 size: 13264 387 size: 1360 388 size: 2212 389 size: 2212 390 size: 2212 392 size: 348 393 size: 724 394 size: 32 395 size: 8416 396 size: 13264 397 size: 2264 398 size: 2264 399 size: 928 400 size: 8176 403 size: 3164 404 size: 92 405 size: 348 406 size: 280 407 size: 100 408 size: 4192 409 size: 3644 410 size: 1024 411 size: 7180 413 size: 116 414 size: 76 2015-10-07 15:04:23.505531 UTC iptv-s1-67: tavsdb:berkeley_db_error_logging.c:berkeley_db_error_logging():132: DBCursor->close: BDB0062 Successful return: 0 (backtrace: 0: 0x431d1a - ./avsdb(berkeley_db_error_logging+0x7a) [0x431d1a]; 1: 0x7fcbaa0855ef - /usr/lib/libdb-6.0.so(__db_errcall+0x9f) [0x7fcbaa0855ef]; 2: 0x7fcbaa0913c8 - /usr/lib/libdb-6.0.so [0x7fcbaa0913c8]; 3: 0x43218d - ./avsdb(check_playout_scheduler_config+0x20d) [0x43218d]; 4: 0x42e848 - ./avsdb(main+0x11d8) [0x42e848]; 5: 0x7fcba98129f4 - /lib64/libc.so.6(__libc_start_main+0xf4) [0x7fcba98129f4]; 6: 0x42c969 - ./avsdb [0x42c969]) 2015-10-07 15:04:27.493605 UTC iptv-s1-67: tavsdb:berkeley_db_error_logging.c:berkeley_db_error_logging():132: DBCursor->close: BDB0062 Successful return: 0 (backtrace: 0: 0x431d1a - ./avsdb(berkeley_db_error_logging+0x7a) [0x431d1a]; 1: 0x7fcbaa0855ef - /usr/lib/libdb-6.0.so(__db_errcall+0x9f) [0x7fcbaa0855ef]; 2: 0x7fcbaa0913c8 - /usr/lib/libdb-6.0.so [0x7fcbaa0913c8]; 3: 0x432497 - ./avsdb(check_rts_transformtype_scheduler_config+0x2f7) [0x432497]; 4: 0x42e84d - ./avsdb(main+0x11dd) [0x42e84d]; 5: 0x7fcba98129f4 - /lib64/libc.so.6(__libc_start_main+0xf4) [0x7fcba98129f4]; 6: 0x42c969 - ./avsdb [0x42c969]) 2015-10-07 15:04:27.493855 UTC iptv-s1-67: tavsdb:berkeley_db_error_logging.c:berkeley_db_error_logging():132: DBCursor->close: BDB0062 Successful return: 0 (backtrace: 0: 0x431d1a - ./avsdb(berkeley_db_error_logging+0x7a) [0x431d1a]; 1: 0x7fcbaa0855ef - /usr/lib/libdb-6.0.so(__db_errcall+0x9f) [0x7fcbaa0855ef]; 2: 0x7fcbaa0913c8 - /usr/lib/libdb-6.0.so [0x7fcbaa0913c8]; 3: 0x5236d2 - ./avsdb(check_future_recording+0x202) [0x5236d2];

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-32 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

4: 0x42e85a - ./avsdb(main+0x11ea) [0x42e85a]; 5: 0x7fcba98129f4 - /lib64/libc.so.6(__libc_start_main+0xf4) [0x7fcba98129f4]; 6: 0x42c969 - ./avsdb [0x42c969]) 2015-10-07 15:04:27.494189 UTC iptv-s1-67: tavsdb:berkeley_db_error_logging.c:berkeley_db_error_logging():132: DBCursor->close: BDB0062 Successful return: 0 (backtrace: 0: 0x431d1a - ./avsdb(berkeley_db_error_logging+0x7a) [0x431d1a]; 1: 0x7fcbaa0855ef - /usr/lib/libdb-6.0.so(__db_errcall+0x9f) [0x7fcbaa0855ef]; 2: 0x7fcbaa0913c8 - /usr/lib/libdb-6.0.so [0x7fcbaa0913c8]; 3: 0x5238e2 - ./avsdb(check_redirect_server+0x202) [0x5238e2]; 4: 0x42e85f - ./avsdb(main+0x11ef) [0x42e85f]; 5: 0x7fcba98129f4 - /lib64/libc.so.6(__libc_start_main+0xf4) [0x7fcba98129f4]; 6: 0x42c969 - ./avsdb [0x42c969]) pollconfig thread starting: tid: 140512654469440 trickle thread starting: tid: 140512646076736 deadlock thread starting: tid: 140512637684032 checkpoint thread starting: tid: 140512629291328 trigger_worker thread starting: tid: 140512620898624 compaction thread starting: thread number = 6; thread identifier = 0xa45ad940 resource monitor thread starting: thread number = 7; thread identifier = 0xa3dac940

2015-10-07 15:04:27.496177 UTC iptv-s1-67: MALLOC STATS starts Arena 0: system bytes = 14835712 in use bytes = 14738368 Total (incl. mmap): system bytes = 52396032 in use bytes = 52298688 max mmap regions = 6 max mmap bytes = 37560320 2015-10-07 15:04:27.496209 UTC iptv-s1-67: MALLOC STATS ends 10.197.102.61: threadid 140512595720512: Performing full resync for node addition with 10.197.102.61 10.197.102.61: threadid 140512595720512: Full Resync SUCCESS 10.197.102.50: threadid 140512587327808: Performing full resync for node addition with 10.197.102.50 10.197.102.50: threadid 140512587327808: Full Resync SUCCESS 10.197.102.64: threadid 140512578935104: Performing full resync for node addition with 10.197.102.64 10.197.102.64: db_resync_content_object: Finished with 3 new records found and 0 records deleted, 3 processed in getall 10.197.102.64: db_resync_content_object4_cmpgetall: still processing remote getall, 0 contents processed so far 10.197.102.64: db_resync_content_object4: Finished with 0 new records found and 0 records deleted, 0 processed in getall 10.197.102.64: db_resync_content_object3_cmpgetall: still processing remote getall, 0 contents processed so far 10.197.102.64: db_resync_content_object3: Finished with 0 new records found and 0 records deleted, 0 processed in getall 10.197.102.64: threadid 140512578935104: Full Resync SUCCESS 10.197.102.68: threadid 140512570542400: Performing full resync for node addition with 10.197.102.68 10.197.102.68: threadid 140512570542400: Full Resync SUCCESS serverid: 67 servertype: 2 ipaddr: 180708931 controller archiving thread starting: tid: 140512553756992 rep_mgr thread starting: tid: 140512472332608 rthreads: 4 trigger manager thread starting: tid: 140512463939904 pthread created: 140512654469440 pthread created: 140512646076736 pthread created: 140512637684032 pthread created: 140512629291328 pthread created: 140512620898624 pthread created: 140512612505920

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-33 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

pthread created: 140512604113216 pthread created: 140512595720512 pthread created: 140512587327808 pthread created: 140512578935104 pthread created: 140512570542400 pthread created: 140512562149696 pthread created: 140512553756992 pthread created: 140512472332608 pthread created: 140512463939904 replication threads: 4

Database sync completed.

Starting avsdb: [OK] Started avsdb, verify with "service avsdb status" Run svrinit to seed database? (yes/no) [n]: y Please enter an IP address for svrinit [10.197.102.67]: Please enter a netmask for svrinit [255.255.255.0]: Please enter a hostname for svrinit [iptv-s1-67]: 10.197.102.67 ASM tables initialized!

Writing VDS Service config file Waiting for 30 sec max for cserver to come up ... cserver not running, statsd starting without cserver. Starting statsd.bin: device is: eth0 [ OK ] Waiting for 30 sec max for cserver to come up ... cserver not running, collectd starting without cserver... Starting collectd.bin: [ OK ] RTSP ecosystem configuration finished Serial Console BAUD speed is configured as '9600'. Do you wish to change it (yes/no) [n]: Synchronizing logging config files: Wrote logging configuration file (/home/isa/logging.conf) Wrote syslog configuration file (/opt/syslog-ng/etc/cdstv-syslog-ng.conf) Reloading syslog-ng's config file: Reloaded syslog-ng. Removing symbolic links to log files: done. Establishing symbolic links to log files: done. vdsconfig finished, please use CDSM to complete configuration [root@iptv-s1-67 ~]# vdsServices status Status of the following VDS Services: avsdb avslauncher cserver statsd collectd appmonitor avsdb (pid 9376 9374) is running... avslauncher.bin is stopped cserver is not running statsd.bin (pid 9550) is running... collectd.bin (pid 9749) is running... cds-app-monitor stopped monit (pid 3572) is running...

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-34 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Initially Configuring the CDE220, CDE250, CDE420 and CDE460 or CDE280

Step 3 Verify connectivity to the CDSM by logging in to the CDSM GUI. The System Health Monitor page is displayed, showing the devices and their IP address (see Figure 2-2).

Figure 2-2 System Health Monitor Page

The VDS-TV installation is complete. Step 4 Restart collectd in both primary and secondary CDSM.

# service collectd restart

Step 5 To complete the server configuration, log in to the CDSM GUI and go through the Configure > Server Level pages for the new server.

Note In RTSP deployments, if you need to enable the Redirect Server in Release 4.4, run the vdsconfig script and answer yes (Y) at the following prompt:

Do you want to enable Redirect Server ? (yes/no) [y]

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-35 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Installing the CDSM in UCS C220 M4 2U1 Server

Installing the CDSM in UCS C220 M4 2U1 Server

Procedure

Table 2-3 Installing the CDSM in UCS C220 M4 Server

Action Purpose Step 1 Configuring BIOS Settings Configure BIOS Settings in CIMC GUI before in CIMC, page 2-36 installing the CDSM. Step 2 Hardware Setup, page 2-37 Configure your UCS C220 M4 server and assign CIMC IP Address. Step 3 Installing the VDS-TV OS, Install the VDS-TV kernel. page 2-38 Step 4 Installing the CDSM Install and configure the VDS-TV CDSM. software on UCS C220 M4 2U1 Server, page 2-39

Configuring BIOS Settings in CIMC

Before installing the CDSM in UCS C220 M4 server, configure the BIOS settings in Cisco Integrated Management Controller (CIMC) for UCS C220 M4 used as CDSM. To configure the BIOS settings, do the following

Step 1 Configure CIMC and assign an IP Address to manage the UCS server. a. Upgrade CIMC to the latest version. Step 2 Connect Ethernet cable to CIMC management NIC and configure the network access. Step 3 Launch CIMC GUI. Step 4 Choose Server > BIOS > Configure BIOS > Main. The BIOS Settings Main tab page is displayed. Step 5 Enter the BIOS settings as appropriate. See Table 2-4 for description of the fields. Table 2-4 BIOS Main tab settings

Field Description TPM Support From the drop-down box, choose Disabled

Step 6 Choose Server > BIOS > Configure BIOS > Advanced. The BIOS Settings Advanced tab page is displayed. Step 7 Enter the BIOS settings as appropriate. See Table 2-5 for description of the fields. Table 2-5 BIOS Advanced tab settings

Field Description Intel(R) Hyper-Threading Technology From the drop-down box, choose Disabled Intel(R) VT-d ATS Support From the drop-down box, choose Disabled

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-36 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Installing the CDSM in UCS C220 M4 2U1 Server

Table 2-5 BIOS Advanced tab settings

Field Description Intel(R) VT From the drop-down box, choose Disabled Intel(R) VT-d From the drop-down box, choose Disabled Power Technology From the drop-down box, choose Disabled Energy Performance From the drop-down box, choose Performance Bits per second From the drop-down box, choose 9600

Note For the remaining BIOS Advanced tab settings, the default option is retained.

Step 8 Click Save Changes. Step 9 Reboot/Power Cycle the server for the settings to take effect.

Hardware Setup

To configure the UCS C220 M4 server and assign CIMC IP address, do the following:

Step 1 Ensure that the server has all the expected hardware. Step 2 Connect console, USB keyboard and USB mouse. Step 3 Configure single virtual drive using CIMC. • Choose Storage > Virtual Drive Info The Virtual Drive details are displayed. To create a new virtual drive from unused physical drives, do the following: – Clear any existing virtual drives. – Choose Storage > Controller Info and click Create Virtual Drive from Unused Physical Drives. – Create two RAID50 drive groups with four physical drives each. Configure the following settings for the RAID Config: 1. RAID Level: 50 2. Write Policy: Always Right Back

Note For the remaining RAID Config settings, the default option is retained.

– Using the two RAID50 drive groups, create one RAID50 drive and format it. – Initialize the virtual drive and set it as boot drive.

Note Once the virtual drive is created, verify if the Write Policy is set as Always Right Back. If not edit the virtual drive, choose Write Policy as Always Right Back and resubmit.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-37 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Installing the CDSM in UCS C220 M4 2U1 Server

Installing the VDS-TV OS

There are two options to install the VDS-TV Operating System (OS).

Option 1

To install the VDS-TV OS, do the following:

Step 1 Download the latest TV image from the Cisco software download website and burn a DVD.of tv_full.4.4.1-bxx ISO image Step 2 Connect a USB DVD drive to UCS C220 server a. On CIMC, choose Server -> BIOS -> Configure Boot Order. The Configure Boot Order page is displayed. – Verify if the boot order for USB is 1.

Note To modify the boot order, select the boot device and click Modify.

Step 3 Insert the VDS-TV disc into the USB DVD drive. Step 4 On CIMC, choose Server -> Summary a. Select Power Cycle Server

Option 2

This section describes the procedure to map the storage drive connected to Laptop/PC as a virtual media and install the OS. The storage device should be a Local HDD in PC from where the CIMC is launched and the PC must have a bootable tv_full-4.4.1-x86_64.iso file. To install the VDS-TV OS, do the following:

Step 1 Launch CIMC GUI. Step 2 Choose Server > Summary. The Server Summary page is displayed. Step 3 Click Launch KVM Console. The KVM Console is launched. Step 4 Choose Power > Power Off System to power off the device. Step 5 Choose Virtual Media > Activate Virtual Devices. Step 6 Accept the pop-up displayed. Choose Virtual Media > Map CD/DVD > Map Device and browse for the image to be installed from your hard drive. Step 7 On selecting the Map Device, the virtual device mapped is displayed under Virtual Media tab. Step 8 Choose Power > Power On System to power on the device. Step 9 On server reboot, enter F6 on the initial Cisco logo screen. The boot options are displayed. Step 10 Select Cisco vKVM-Mapped vDVD1.22 on the menu and Enter. Step 11 The OS installation screen is displayed. Step 12 Press Enter to proceed with the OS installation. Step 13 On successful installation of the OS, the server reboots.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-38 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Installing the CDSM in UCS C220 M4 2U1 Server

Note The file system creation can take between 2 to 4 hours.

Installing the CDSM software on UCS C220 M4 2U1 Server

To install the CDSM software on UCS C220 M4 2U1 server, refer Installing the Software on a CDE110/UCS C220 M4 Hardware, page 2-3.

Configuring the VDS-TV Hardware

For detailed information on configuring the VDS-TV hardware, see Initially Configuring the CDE110/UCS Hardware, page 2-18,

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-39 Chapter 2 Installing and Configuring the VDS-TV 4.4 Software Installing the CDSM in UCS C220 M4 2U1 Server

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 2-40

CHAPTER 3

Upgrading to Release 4.4

This chapter describes the upgrade procedure for the CDSM, VVIM, and VDS servers. This chapter covers the following topics: • Upgrading the Software on a CDSM or VVIM to Release 4.4, page 3-1 • Manually Upgrading a VDS-TV Server to Release 4.4, page 3-7 • Database Migration, page 3-15

Caution Before proceeding with the software upgrade, review Chapter 1, “Overview of Upgrading and Downgrading the VDS-TV Software” for information on getting the Release 4.4 software files, prerequisites for the software upgrade, the upgrade sequence for the devices in the VDS. Also, refer Prerequisite for Asset Scalability Support, page 2-2 for details on enabling/disabling asset scale co-existence support.

Upgrading the Software on a CDSM or VVIM to Release 4.4

If the VVI or CDS has redundant CDSMs or VVIMs, upgrade the secondary CDSM or VVIM first, then upgrade the primary. The primary and secondary CDSM (or VVIM) can be determined by entering the ifconfig -a | more command. The primary has the following output: eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00 inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Memory:b880000-b8840000

The primary CDSM or VVIM has device eth0:1. The secondary CDSM or VVIM does not have the virtual IP address as up.

Pre-Requisites

Before upgrading the software on a CDSM or VVIM, do the following:

Step 1 Upgrading a CDSM requires that the VDS-TV 4.4 ISO file and vdsinit software files have been downloaded and copied to the CDSM. Make sure you download the vdsinit script from Cisco and copy it to /root directory on each CDSM before upgrading them. Use the scp command to copy the software files. For example, if the remote server that you downloaded the software files to has an IP address of 172.22.97.109 and the files are stored in the CDSdownloads directory, the following commands are used:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-1 Chapter 3 Upgrading to Release 4.4 Upgrading the Software on a CDSM or VVIM to Release 4.4

# scp -p 172.22.97.109:/CDSdownloads/tv_repo-4.4.1-x86_64.iso /root # scp -p 172.22.97.109:/CDSdownloads/vdsinit-4.4.1 /root

Step 2 Before upgrading the CDSMs, review the information in the “Introduction” section on page 1-1. For information on downloading the software files, see the “Getting the Cisco VDS-TV Software Files for Release 4.4” section on page 1-5. Step 3 If custom modifications have been made to the root crontab (for example, in ISA environments the MSV script to delete orphaned content), create the /etc/cds_noCrontabOverwrite file before upgrading the VDS-TV software in order to avoid the custom crontab being overwritten. To create this file, enter the following command: touch /etc/cds_noCrontabOverwrite Step 4 Execute the command yum info yum on the VVIM and check the yum version installed. Execute the following commands if the yum version in the VVIM is old. mount -o loop -t iso9660 tv_repo-4.4-1bxx-x86_64.iso /mnt/cdrom/ cd /mnt/cdrom/Packages/ ls -l yum* -r--r--r-- 2 root root 1034777 Jul 23 09:17 yum-3.2.22-40.el5.noarch.rpm -r--r--r-- 2 root root 26063 Jun 6 18:52 yum-metadata-parser-1.1.2-4.el5.x86_64.rpm -r--r--r-- 2 root root 75317 Jul 2 09:51 yum-utils-1.1.16-21.el5.noarch.rpm rpm -Uvh yum-3.2.22-40.el5.noarch.rpm cd [go to root folder] umount /mnt/cdrom/

Step 5 If you are upgrading the software on a CDSM or VVIM from a version below 3.9 to a version 3.9 or above, then verify the zone information configure in /etc/sysconfig/clock is same as the time zone configured in the server.

For example,

# cat /etc/sysconfig/clock ZONE="America/New_York?

UTC=false

ARC=false

Step 6 If the zone information is incorrect, then update the zone information in /etc/sysconfig/clock file and execute the following command: /usr/sbin/tzdata-update Once the zone information is configured, verify the date by executing the date command.

Note Any commands, for example route information commands that should be retained on upgrade to 4.4.1 must be placed above the “# Lines below this one modified by cdsflavconfig:” line in the /etc/rc.local.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-2 Chapter 3 Upgrading to Release 4.4 Upgrading the Software on a CDSM or VVIM to Release 4.4

Upgrading the software on a CDSM/VVIM

To upgrade the software on a CDSM or VVIM, do the following:

Step 1 Log in to the secondary CDSM or VVIM as root. Step 2 Back up the configuration and database files on the existing CDSM or VVIM. Step 3 Verify there is enough disk space on / and /arroyo. # df-h Filesystem Size Used Avail Use% Mounted on /dev/sda2 3.5G 624M 2.7G 19% / /dev/sdc1 3.9G 2.4G 1.4G 64% /usr /dev/sde1 7.8G 5.0G 2.4G 68% /arroyo /dev/sdh1 97G 9.0G 83G 10% /arroyo/db /dev/sdf1 7.8G 529M 6.9G 8% /home /dev/sdd1 7.8G 204M 7.2G 3% /var /dev/sda1 244M 12M 219M 6% /boot tmpfs 3.9G 0 3.9G 0% /dev/shm

If the disk space is high and you run the script, you receive the following message:

The filesystem usage is more than 90% for at least one of the Mount Points The image installation may fail.

Step 4 Enter the following command and press Enter to shut down the database.

# db_shutdown

Step 5 Execute the vdsinit script to upgrade the ISO image to Release 3.9.

# cd /root

# ./vdsinit-4.4.1 tv_repo-4.4.1-x86_64.iso

The following log output is displayed towards the end of the upgrade.

Note This example log output may not match the final image log output.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-3 Chapter 3 Upgrading to Release 4.4 Upgrading the Software on a CDSM or VVIM to Release 4.4

---> Package vds_cdsm.x86_64 0:4.4.1-tv0.3 set to be updated ---> Package vds_collectd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_config.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_config-cdsm.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_framework.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_httpd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_isa.x86_64 0:4.4.1-tv0.1.1 set to be updated ---> Package vds_php.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_snmp_cdsm.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_statsd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_syslogtools.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_tavsdb.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_utils.x86_64 0:4.4.1-tv0.1 set to be updated --> Finished Dependency Resolution

Dependencies Resolved

Transaction Summary ======Install 0 Package(s) Upgrade 14 Package(s)

Updating : vds_httpd 4/28 Updating : vds_snmp_cdsm 5/28Stopping statsd: [OK]

Updating : vds_statsd 6/28Stopping collectd: [OK]

Updating : vds_collectd 7/28 Updating : vds_syslogtools 8/28

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-4 Chapter 3 Upgrading to Release 4.4 Upgrading the Software on a CDSM or VVIM to Release 4.4

warning: /opt/syslog-ng/etc/cdstv-syslog-ng.conf created as /opt/syslog-ng/etc/cdstv-syslog-ng.conf.rpmnew Updating : vds_tavsdb 9/28 Updating : vds_utils 10/28 Updating : vds_config 11/28Loading File List HW does not appear to be Merrimack... No work to do here.

Updating : vds_isa 12/28 Updating : vds_cdsm 13/28 Updating : vds_config-cdsm 14/28 Cleanup : vds_syslogtools 15/28 Cleanup : vds_utils 16/28 Cleanup : vds_snmp_cdsm 17/28 Cleanup : vds_config-cdsm 18/28 Cleanup : vds_framework 19/28 Cleanup : vds_php 20/28 Cleanup : vds_isa 21/28 Cleanup : vds_collectd 22/28 Cleanup : vds_httpd 23/28 Cleanup : vds_config 24/28 Cleanup : vds_cdsm 25/28 Cleanup : vds_statsd 26/28 Cleanup : vds_cache2app 27/28 Cleanup : vds_tavsdb 28/28

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-5 Chapter 3 Upgrading to Release 4.4 Upgrading the Software on a CDSM or VVIM to Release 4.4

Step 6 Enter the following command to verify the version of VDS-TV installed.

# head /arroyo/image/tags

cdstv-4.4.1-b4

Step 7 Enter the following commands to disable the services from starting automatically after reboot.

# vdsServices disable

Step 8 Reboot the server. Step 9 Enter the following command to verify the kernel version installed.

# uname -r

2.6.32-4.4.1_tv0.1

Step 10 On successful upgrade, migrate the database to newer version. For detailed information on database migration, see Database Migration, page 3-15. Step 11 Enter the following command to start the services:

# vdsServices start

Step 12 Verify that the required baud is 9600 in /etc/grub.conf. If it is 115200, edit the file to change it to 9600. See Baud Setting, page 1-4 for additional information on setting the baud. Step 13 After both CDSMs or VVIMs are upgraded, it is optional to reset the password on one CDSM or VVIM. To reset the password, do the following: a. To reset the password, run the following script as root user: # /home/stats/resetpw Parsed 4 tokens, use SHA, image version: 4.4-b204 Did not find regular file /etc/cdsremoteauth Password values reset successfully

b. Then login the the CDSM or VVIM GUI. Login with the User Name and Password as “admin”. c. Go to Maintain then Users. In the Edit Users page, change the password and select Submit. Step 14 To complete the software upgrade, log in to the CDSM GUI as a user with Engineering access level. The CDSM Setup page is displayed. In the Deployed CServer Version drop-down list, choose 4.X. In all deployments, verify all settings on the CDSM Setup page and click Submit. Step 15 After upgrading the secondary CDSM or VVIM, assign the secondary CDSM or VVIM as primary and then upgrade the current secondary CDSM or VVIM (Step 1 to Step 14), if applicable.

Note Ensure that after upgrade to release 4.4 the primary and backup controllers are seeded so that collectd reports the correct status of the VDS-TV servers.

When the VVIM/CDSM is upgraded to 4.4 and the vaults and streamers are in version lower than 3.9.1 the GUI Dashboard displays the VDS servers as Online even when the database is shutdown on those servers. To obtain the correct status of the non 4.4 VDS servers on 4.4 CDSM dashboard, do the following: • ·Add/Edit below line in /etc/collectd.conf and save the file

FLUSH_DB_STATS = 1

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-6 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

• ·Get PID for collectd

pgrep collectd

kill -SIGUSR1

Note Execute the above steps on 4.4 CDSM whenever a non 4.4 server database is shutdown to reflect the correct status in CDSM

Note There is a known issue where the disk status of the server with image lower than 3.9.1 is displayed wrong by the 4.4 controller. Currently there is no workaround solution. This issue is fixed on upgrading to release 4.4.

Manually Upgrading a VDS-TV Server to Release 4.4

This section describes the procedure for upgrading a server to VDS-TV 4.4 software release. Servers may be caching nodes or Vaults or Streamer. There may be several Cache Groups in your configuration, but only upgrade them one group at a time. When upgrading a Cache Node in one group, update the slave server first then upgrade the master server. There may be several Streamer Groups in your configuration, but only upgrade them one group at a time.When upgrading a streamer in one group, upgrade the available streamer first followed by backup streamer and then the primary streamer. There are two types of Vault Groups, first upgrade the slave group then upgrade the master group. Keep the following in mind: • Upgrade the vaults in the slave group one by one in sequence. • Upgrade the slave vaults in the master group one by one in sequence followed by the master server. • Always upgrade the master server in the end.

Pre-Requisites

Before upgrading the VDS-TV server, do the following:

Step 1 Before upgrading the CDS servers, review the information in Chapter 1, “Overview of Upgrading and Downgrading the VDS-TV Software.” Step 2 For RTSP environments with NGOD deployments, before upgrading to Release 4.4 from Release 3.2.x, log in to the CDSM, choose Configure > Server Level > RTSP Server, select the IP address of a Streamer and write down the settings for the SOP fields for each Streamer. For more information, see the “Configuring Source Output Ports” section in the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4. Step 3 If custom modifications have been made to the root crontab (for example, in ISA environments the MSV script to delete orphaned content), create the /etc/cds_noCrontabOverwrite file before upgrading the VDS-TV software in order to avoid the custom crontab being overwritten. To create this file, enter the following command:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-7 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

touch /etc/cds_noCrontabOverwrite Step 4 If you are upgrading the software on a CDSM or VVIM from a version below 3.9 to a version 3.9 or above, then verify the zone information configure in /etc/sysconfig/clock is same as the time zone configured in the server.

For example,

# cat /etc/sysconfig/clock ZONE="America/New_York?

UTC=false

ARC=false

Step 5 If the zone information is incorrect, then update the zone information in /etc/sysconfig/clock file and execute the following command: /usr/sbin/tzdata-update Once the zone information is configured, verify the date by executing the date command.

Upgrading the VDS-TV server

To upgrade a VDS server, do the following:

Step 1 If you are upgrading a vault, disable mirroring on all vaults in all Vault Groups before upgrading the software. Mirroring will be enabled once all the vaults in all the Vault Groups have been upgraded to release 4.4. If you are upgrading a Cache Node or Streamer, go to Step 4. Step 2 Disable ingest through the Server Offload option in the CDSM GUI. Go to Maintain > Servers > Server Offload. The Server Offload page is displayed. Select Offline (No Ingest) and select Submit. Step 3 If you are upgrading a vault you must first disable the Vault Group Mirror. Use Secure Shell (SSH) to access each Vault and enter the following command at the root: # echo 0 > /proc/calypso/tunables/allowvaultarraymirroring

a. Make sure the following lines are in /arroyo/test/afterrun for all Vaults in all Vault Groups: echo <# of copy> > /proc/calypso/tunables/maintenancemirrorcopies echo 0 > /proc/calypso/tunables/maintenancearraymirroringallowed echo > /proc/calypso/tunables/maintenancetimer echo 0 > /proc/calypso/tunables/allowvaultarraymirroring

The # of copy here should be one less than the mirror copies setting. b. Run the following lines in the command lines on all the Vaults in all Vault Groups: echo <# of copy> > /proc/calypso/tunables/maintenancemirrorcopies echo 0 > /proc/calypso/tunables/maintenancearraymirroringallowed echo > /proc/calypso/tunables/maintenancetimer

The # of copy here should be one less than the mirror copies setting.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-8 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

Note When modifying /proc/calypso/tunables/maintenancetimer, it stays with the modified value until the cserver has reacted to it. Once the cserver has reacted to it, the value is reset to ffffffff. So whether it is set to 60 or 0, it is not really in effect until the value is reset to ffffffff.

c. Add the following line to /home/isa/.arroyorc on all offline content library servers. Do not add this line to the servers in the Master Vault Group. nofailover 1

d. Verify the databases are in sync across all the Vaults: # cd root # asset_to_goids.py asset_goid.out

Step 4 Ensure that the server is fully offloaded. a. For vaults, disable ingest and fill through the Server Offload option in the CDSM GUI. Go to Maintain > Servers > Server Offload. The Server Offload page is displayed. Select Offline (No Ingest & Fill) and select Submit. b. Verify that the TRICKLE_DOWN file exists in the /var/tmp directory. c. For a Streamer, check that the protocoltiming log displays a warning message indicating that the server is going offline. tail -f /arroyo/log/protocoltiming.log.20090917

You should see the following: Remote vaults 2 caches 0 streamers 1, Adapters fill 4 (1024) stream 4 (1316) CPU Receive: Ave0+0+0 Cur 0+0+0, Network: 0, Poll: 34 (0 scaled) Warning: Server is going OFFLINE

d. For a Streamer, make sure that all the active streams have moved over to the other Streamers. Check the Active Streams line in the protocoltiming log. e. For a Vault, make sure that all active ingests on this server have finished. Check that there is no Active Ingest Connections line in the protocoltiming log. f. Check there is no active traffic on the network interface cards (NICs) using the /home/stats/ifstats command. Step 5 Enter the following command and press enter to stop the database.

# db_shutdown

Step 6 For CDE250 hardware, before upgrading to Release 4.4, reinstall SuperDoctor version 2.111 and upgrade Firmware to version 3.0.6 using instructions specified in the document CDE 250 IPMI Firmware v3.06 Upgrade. Step 7 Copy the VDS-TV 4.4 ISO and vdsinit files to the /root directory of the VDS server and run the vdsinit script. # scp -p @:tv_repo-4.4.1-x86_64.iso /root # scp -p @:vdsinit-4.4.1 /root # cd /root # ./vdsinit-4.4.1 tv_repo-4.4.1-x86_64.iso

EXAMPLE Log Output for Vault installation

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-9 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

Note This example log output may not match the final image log output.

Mounting tv_repo-4.4.1-0b1-x86_64.iso at /mnt/cdrom Currently Installed Version is cdstv-4.3.0-b106 Reading deployment from "/etc/vdstv.conf". avsdb is running.. stopping avsdb appmonitor is running.. stopping appmonitor Removing unnecessary redhat rpms ... 1) ISA 2) RTSP/FSI 3) PEG/BARKER

ISA Selected Taking backup of the existing avsdb.config file to restore Setting up Update Process Resolving Dependencies --> Running transaction check ---> Package cddm.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package cserver-prod.x86_64 0:4.4.1-tv0.1.1.1 set to be updated ---> Package kernel-vds.x86_64 0:2.6.32-4.4.1_tv0.1 set to be updated ---> Package vds_avslauncher.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_cache2app.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_collectd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_config.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_config-isa.x86_64 0:4.4.1-tv0.3.1 set to be updated ---> Package vds_framework.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_isa.x86_64 0:4.4.1-tv0.1.1 set to be updated ---> Package vds_snmp.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_statsd.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_syslogtools.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_tavsdb.x86_64 0:4.4.1-tv0.1 set to be updated ---> Package vds_tools.x86_64 0:4.4.1-tv0.1.1 set to be updated ---> Package vds_utils.x86_64 0:4.4.1-tv0.1 set to be updated --> Finished Dependency Resolution

Dependencies Resolved

Transaction Summary ======

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-10 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

Install 0 Package(s) Upgrade 16 Package(s)

^M Updating : vds_statsd 6/32Stopping collectd: [OK]

Processing File List ...done

Moving modprobe.conf into place ...done

Updated:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-11 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

cddm.x86_64 0:4.4.1-tv0.1 cserver-prod.x86_64 0:4.4.1-tv0.1.1.1 kernel-vds.x86_64 0:2.6.32-4.4.1_tv0.1 vds_avslauncher.x86_64 0:4.4.1-tv0.1 vds_cache2app.x86_64 0:4.4.1-tv0.1 vds_collectd.x86_64 0:4.4.1-tv0.1 vds_config.x86_64 0:4.4.1-tv0.3.1 vds_config-isa.x86_64 0:4.4.1-tv0.3.1 vds_framework.x86_64 0:4.4.1-tv0.1 vds_isa.x86_64 0:4.4.1-tv0.1.1 vds_snmp.x86_64 0:4.4.1-tv0.1 vds_statsd.x86_64 0:4.4.1-tv0.1 vds_syslogtools.x86_64 0:4.4.1-tv0.1 vds_tavsdb.x86_64 0:4.4.1-tv0.1 vds_tools.x86_64 0:4.4.1-tv0.1.1 vds_utils.x86_64 0:4.4.1-tv0.1

Complete! Setting up Group Process Package httpd-2.2.3-91.el5.x86_64 already installed and latest version Package ipmitool-1.8.15-1.el5.x86_64 already installed and latest version Package 1:mod_ssl-2.2.3-91.el5.x86_64 already installed and latest version Package SuperDoctor2-2.88-1.el5.x86_64 already installed and latest version Package kexec-tools-1.101-194.4.tv.x86_64 already installed and latest version Package MegaCli-8.00.40-1.i386 already installed and latest version Package syslog-ng-3.0.5-1.rhel5.x86_64 already installed and latest version Package monit-5.3-1.el5.x86_64 already installed and latest version Package apache2-mod_authnz_external-3.1.0-2.36.x86_64 already installed and latest version Package cddm-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_cache2app-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_utils-4.4.1-tv0.1.x86_64 already installed and latest version Package kernel-vds-2.6.32-4.4.1_tv0.1.x86_64 already installed and latest version Package vds_tools-4.4.1-tv0.1.1.x86_64 already installed and latest version Package vds_statsd-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_tavsdb-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_framework-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_snmp-4.4.1-tv0.1.x86_64 already installed and latest version Package cserver-prod-4.4.1-tv0.1.1.1.x86_64 already installed and latest version Package vds_avslauncher-4.4.1-tv0.1.x86_64 already installed and latest version Package cds-vqe-3.5.0-13.x86_64 already installed and latest version Package vds_config-4.4.1-tv0.3.1.x86_64 already installed and latest version Package vds_collectd-4.4.1-tv0.1.x86_64 already installed and latest version Package vds_syslogtools-4.4.1-tv0.1.x86_64 already installed and latest version No packages in any requested group available to install or update Setting up Group Process Package vds_config-isa-4.4.1-tv0.3.1.x86_64 already installed and latest version Package vds_isa-4.4.1-tv0.1.1.x86_64 already installed and latest version No packages in any requested group available to install or update Unmounting /mnt/cdrom New image installed : cdstv-4.4.1-b4 File /etc/vdsServices.conf already exists. Restoring avsdb.config-restore to avsdb.config vdsinit completed. Please reboot the device.

Step 8 Select the deployment type of the server, choose 1 for an ISA deployment and 2 for an RTSP/FSI deployment and 3 for Playout.

Step 9 Enter the following command to verify the version of VDS-TV installed.

# head /arroyo/image/tags

cdstv-4.4.1-b4

Step 10 If jumbo frames are enabled in cache-fill interfaces in vault/cache/streamer, do the following: • Start avsdb and statsd services. service avsdb start service statsd start

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-12 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

• Ensure 2-way avsdb connection is established between the Controller and the vault/cache/streamer. # netstat -an |grep 9999 tcp 0 0 0.0.0.0:9999 0.0.0.0:* LISTEN tcp 0 0 10.197.101.117:48526 10.197.101.116:9999 ESTABLISHED tcp 0 0 10.197.101.117:9999 10.197.101.116:45867 ESTABLISHED • Verify that the Cache Jumbo Frames is enabled in Configure > Server Level > Server Setup page and click Submit. • . Ensure MTU=8174 is set in network scripts for all configured cache fill interfaces. Example cat /etc/sysconfig/network-scripts/ifcfg-eth2 Generated from CDSM configuration. Do not edit it. DEVICE=eth2 BOOTPROTO=static IPADDR=192.165.3.11 NETMASK=255.255.255.0 MTU=8174 ONBOOT=yes Step 11 Enter the following command and press Enter to disable the services from starting automatically after reboot.

# vdsServices disable

Step 12 Reboot the server. Step 13 Type the following command to verify the kernel version installed.

# uname -r

2.6.32-4.4.1_tv0.1

Step 14 If you upgrade VDS-TV software from version 3.9.x or above, skip Step 15. Step 15 On successful upgrade, migrate the database to newer version. For detailed information on database migration, see Database Migration, page 3-15. Step 16 Enter the following command and press Enter to manually start the services:

# vdsServices start

Note Depending on the deployment type verify all the relevant services are started. vdsServices status displays the current status of the services.

Step 17 Delete the old database *idx file. # rm -f /aroyo/db/DATADIR/*.idx

Note Perform Step 17 only if DB does not start after the reboot.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-13 Chapter 3 Upgrading to Release 4.4 Manually Upgrading a VDS-TV Server to Release 4.4

Step 18 Verify the partition, there should be one boot_cds partition. # df-h Filesystem Size Used Avail Use% Mounted on /dev/hda2 7.2G 1.2G 5.7G 17% / /dev/sda3 9.5G 163M 8.9G 2% /var /dev/sda2 29G 387M 27G 2% /home /dev/sda6 35G 177M 33G 1% /arroyo /dev/sda1 48G 273M 45G 1% /arroyo/db /dev/hda1 244M 34M 197M 15% /boot /dev/sda7 4.6G 704M 4.4G 16% /boot_cds tmpfs 16G 0 16G 0% /dev/shm

Note During the initialization process of a VDS server or after recovering a VDS server that has been down for less than an hour, the VDS database performs a complete synchronization. The database synchronization takes about five minutes before the server becomes ready for service. If the VDS server is down for a much longer time than an hour, the database synchronization takes longer than five minutes. The netstat command does not show the interfaces as up until the synchronization has completed.

Step 19 If you are upgrading a Vault in an RTSP configuration, resubmit the FSI log level. If you are upgrading a caching node, go to Step 21. After the server is up, re-submit the FSI log level through the VVIM. a. Click Configuration > Server Level > Logging. The FSI Setup Screen is displayed. b. Enter the following commands at the root to validate the process.

# service fsi stop

# service fsi start

Step 20 If you are upgrading a Vault in an ISA configuration, execute the following command to verify if the Content Store Master and Slave are up running:

# vdsServices status

Step 21 After the VDS server has been verified as being reachable, log in to the CDSM GUI and disable the server offload. a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP drop-down list, choose the IP address or nickname of the server. c. From the New Server Status drop-down list, choose Online and click Submit. Step 22 Using the CDSM GUI, verify the server is online. a. Click Monitor > System Health. The System Health Monitor page is displayed. b. The status boxes for the server should all be green.

Note It takes a few minutes to synchronize the database. Wait until the other VDS servers become reachable and the services are running. The CDSM GUI System Health Monitor Page can be used to verify that the VDS server is functioning correctly after the upgrade. The CDSM GUI System Health Monitor page shows the states of the network, disk, and services on each VDS server.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-14 Chapter 3 Upgrading to Release 4.4 Database Migration

Step 23 Perform this step only if you are upgrading a Vault. After all Vaults are upgraded (in slave and master group), enable the Vault Mirror. Use SSH to access each Vault and enter the following command at the root: # echo 1 > /proc/calypso/tunables/allowvaultarraymirroring

Check the /arroyo/test/vault/setupfile, and edit the following line: allow vault array mirroring 1

Step 24 Migrate SNMP settings from the old table to the new table. On the VVIM GUI, go to Configure > Server Level > SNMP Agent page and select the Vault. Verify field SNMP Contact, SNMP Location, Community Name, Trap Station and Version have correct settings and select Submit.

Note Step 24 is only applicable for upgrades from 3.2.x to 4.4

The upgrade is complete.

Database Migration

Note For all server upgrades, database migration is not required if you upgrade VDS-TV software from version 3.9.x or above.

To migrate the database after the upgrade, do the following:

Step 1 Enter the following command and press Enter, to stop the AVSDB.

# service avsdb stop

# pgrep avsdb (to make sure there is no avsdb process running)

Step 2 Edit the avsdb file and add -m 1 as specified below:

# vi /etc/rc.d/init.d/avsdb

# su - isa -c "cd /arroyo/db/; /bin/bash -c '/arroyo/db/avsdb –m 1 >>/arroyo/log/avsdb.out 2>> /arroyo/log/avsdb.err &'"

Step 3 Execute the following commands to start avsdb, statsd and collectd services.

# service avsdb start

# service statsd start

# service collectd start

Step 4 Execute the upgrade migration script located in /arroyo/db directory. For ISA deployment:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-15 Chapter 3 Upgrading to Release 4.4 Database Migration

# ./DBContentObjSizeReductionUpgradeMigrator -t 1 -d 1 -c 1 -s 150 > upgrade_migration &

For RTSP deployment :

# ./DBContentObjSizeReductionUpgradeMigrator -t 2 -d 1 -c 1 -s 150 > upgrade_migration &

[-t] mandatory specifies deployment type. 1 for ISA deployment and 2 for RTSP deployment [-d] optional, specifies debug level. 1 for debug and 0 for no debug logs, default is 0

Note Redirect the output logs if debug is enabled.

[-c] optional, check before migration. 0 for no check and 1 for check before migration, default is 1 [-v] optional, verify migration. 1 for verifying migration and 0 for not verifying migration, [-s] optional, timeout value in seconds and default is 60 seconds Step 5 Enter the following command and press Enter to stop the AVSDB.

# service avsdb stop

# pgrep avsdb (to make sure there is no avsdb process running)

Step 6 Edit the avsdb file and remove -m 1 as edited Step 2.

Note The database migration script can take a maximum of 2 hours for 600K data. For faster migration process, once a copy of DATADIR directory is created, use the same directory across same server type. Before copying the DATADIR directory, verify that the asset count is same across all servers or execute the migration script first on the server with maximum asset count and use that DATADIR directory for the other servers.

Note Once all servers are upgraded to Release 4.4 in a VHO disable Asset Scale Co-existence Support in Maintain > Software> VVIM/CDSM Setup page for each server in a VHO. Once all VHOs are upgraded to Release 4.4, disable Asset Scale Co-existence Support for SHE.

Step 7 Take a backup of migrated DATADIR by executing the following commands:

pgrep avsdb [Ensure no process id returns for this command]

cd /arroyo/db/

tar -cvf DATADIR.tar.gz DATADIR

Note To fasten the upgrade/migration procedure for the servers of the same type in the system, replace the migrated backup DATADIR by executing the following steps: • Login to the Server which has the backed up migrated DATADIR • cd /arroyo/db

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-16 Chapter 3 Upgrading to Release 4.4 Database Migration

• scp DATADIR.tar.gz root@//arroyo/db • Login to DATADIR copied Server • cd /arroyo/db • tar -xvf DATADIR.tar.gz • Reboot the server

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-17 Chapter 3 Upgrading to Release 4.4 Database Migration

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 3-18

CHAPTER 4

Downgrading from Release 4.4

This chapter describes the downgrade procedure for the CDSM, VVIM, and VDS servers. The chapter covers the following topics: • Downgrading a VDS-TV Server from Release 4.4, page 4-1 • Downgrading the Software on a CDSM or VVIM, page 4-6

Caution Before proceeding with the software downgrade, review Chapter 1, “Overview of Upgrading and Downgrading the VDS-TV Software” for information on getting the Release 4.4 software files, prerequisites for the software downgrade, the downgrade sequence for the devices in the VDS, and information about the upgrade and downgrade kits.

Downgrading a VDS-TV Server from Release 4.4

Note Before downgrading the VDS servers, review the information in Chapter 1, “Overview of Upgrading and Downgrading the VDS-TV Software.”

Note Any commands, for example route information commands that should be retained on downgrade from 4.4.1 must be placed above the “# Lines below this one modified by cdsflavconfig:” line in the /etc/rc.local.

To downgrade a VDS server, do the following:

Step 1 Login to the VDS server as root. a. If you are downgrading a Vault Group, you must disable Vault Group Mirroring. If you are downgrading a different server, go to Step 2.

Use SSH to access each vault in the group and enter the following command: echo 0 > /proc/calypso/tunables/allowvaultarraymirroring

b. If you are downgrading a vault group, turn maintenance mode on for all vaults.If you are downgrading a different server, go to Step 2. c. Use SSH to access each vault in the group as root and enter the following commands:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-1 Chapter 4 Downgrading from Release 4.4 Downgrading a VDS-TV Server from Release 4.4

echo 600 > /proc/calypso/tunables/maintenancetimer

echo 0 > /proc/calypso/tunables/maintenancearraymirroringallowed

echo <# of copies> > /proc/calypso/tunables/maintenancemirrorcopies

Where, # of copies is one less than the mirror copies setting configured in the GUI.

Note When you modify the /proc/calypso/tunables/maintenancetimer value, the modified value remains the same until the cserver has reacted to it. Once the cserver has reacted to it, the value will be reset to ffffffff. So whether it is set to 60 or 0, it is not really in effect until the value is reset to ffffffff.

d. Go to vi /arroyo/test/afterrun and ensure that the correct permissions are set.

# ls -al /arroyo/test/afterrun

-rwxr-xr-x 1 root root 178 Sep 12 2015 /arroyo/test/afterrun

e. Validate if the following lines exist in the /arroyo/test/afterrun file for all vaults in all vault groups:

echo <# of copies> > /proc/calypso/tunables/maintenancemirrorcopies

Where, # of copies is one less than the mirror copies setting configured in the GUI.

echo 0 > /proc/calypso/tunables/maintenancearraymirroringallowed

echo 600 > /proc/calypso/tunables/maintenancetimer

echo 0 > /proc/calypso/tunables/allowvaultarraymirroring

f. If you are downgrading a streamer, execute the following tunable on the primary streamer:

echo 1 > /proc/calypso/internal/allow_lower_backup

Step 2 Using the CDSM or VVIM GUI, offload the server that you want to downgrade. a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. c. Select Offline (No Ingest) for Vaults or select Offline for Cache Nodes and Streamers and click Submit. When Server Offload is enabled on a vault, the vault is configured to reject new provisioning; When Server Offload is enabled for a Cache Node/Streamer, it gracefully moves existing Streams to another Cache Node or Streamer.

Note The Vaults, Streamers, and ISVs must be offloaded. There is no requirement to offload the Caching Nodes for a software downgrade.

Step 3 Log into the server as root. Step 4 Ensure that the server is fully offloaded. a. Verify that the TRICKLE_DOWN file exists in the /usr/tmp directory.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-2 Chapter 4 Downgrading from Release 4.4 Downgrading a VDS-TV Server from Release 4.4

b. For a Streamer, check that the protocoltiming log displays a warning message indicating that the server is going offline. tail -f /arroyo/log/protocoltiming.log.20090917

c. For a Streamer, make sure that all the active streams have moved over to the other Streamers. Check the Active Streams line in the protocoltiming log. d. For a Vault, make sure that all active ingests on this server have finished. Check that there is no Active Ingest Connections line in the protocoltiming log. e. Check there is no active traffic on the network interface cards (NICs) using the /home/stats/ifstats command. Step 5 Enter the following command and press Enter, to stop the database.

# service avsdb stop

# pgrep avsdb (to make sure there is no avsdb process running)

Step 6 For ISA deployment, enter the following command and press Enter, to take a backup of statsd.conf file.

# cp /etc/statsd.conf /etc/statsd.conf_bkp

Step 7 If you downgrade to a release greater than or equal to 3.9.x, skip Step 8 to Step 16 Step 8 Check the deployment type. For ISA deployment do the following and for RTSP deployment go to Step 9: a. Login to VVIM. b. Execute the avsdb_util.py script from /arroyo/db/avsdb_util to retrieve the content store location.

# ./avsdb_util.py -s avsdb_tabletemplate.s -i 1 -o output

# cat output/avsdb_util_output.csv | awk 'BEGIN{FS=","} {print $3,$6}' | grep -v " $" > CSL

c. Copy the CSL file from the VVIM server to the server to being downgraded in /arroyo/db/avsdb_util directory. Step 9 Go to the downgrade server SSH window. Step 10 If contents in the system is more than 200K, then do the following else go to Step 11: a. Edit the avsdb file and add -m 1 as specified below:

# vi /etc/rc.d/init.d/avsdb

# su - isa -c "cd /arroyo/db/; /bin/bash -c '/arroyo/db/avsdb –m 1 >>/arroyo/log/avsdb.out 2>> /arroyo/log/avsdb.err &'"

Step 11 Enter the following command and press Enter to start the database.

# service avsdb start

Step 12 Execute the DB downgrade migration script located in /arroyo/db directory.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-3 Chapter 4 Downgrading from Release 4.4 Downgrading a VDS-TV Server from Release 4.4

For ISA deployment:

# ./DBContentObjSizeReductionDowngradeMigrator -t 1 -d 1 -c 1 -s 150 -i /arroyo/db/avsdb_util/CSL > Downgrade_migration &

For RTSP deployment :

# ./DBContentObjSizeReductionDowngradeMigrator -t 2 -d 1 -c 1 -s 150 > Downgrade_migration &

[-t] mandatory specifies deployment type. 1 for ISA deployment and 2 for RTSP deployment [-d] optional, specifies debug level. 1 for debug and 0 for no debug logs, default is 0

Note Redirect the output logs if debug is enabled.

[-c] optional, check before migration. 0 for no check and 1 for check before migration, default is 1 [-v] optional, verify migration. 1 for verifying migration and 0 for not verifying migration, [-s] optional, timeout value in seconds and default is 60 seconds [-i] mandatory for ISA deployment, file name containing content store location details Step 13 Enter the following command and press Enter to stop the AVSDB.

# service avsdb stop

# pgrep avsdb (to make sure there is no avsdb process running)

Step 14 Edit the avsdb file and remove -m 1 as edited in Step 10.

Note Depending on the content, the downgrade migration script can take a maximum of 2 hours for 600K data. For faster conversion, once a copy of DATADIR directory is created, use the same directory across same server type.

Step 15 Execute the following tunable, to restore the Cisco VDS-TV 4.4 file system to earlier versions.

Note This tunable should be executed only for downgrades below 3.4.2.

# echo 107 >/proc/calypso/tunables/cm_logserverinfo

On successful execution of the tunable, the following output is displayed on the console 2015 Jan 21 00:58:35 OPAH-S232 Downgrade of file system initiated 2015 Jan 21 00:58:43 OPAH-S232 Downgrade of file system updating directory 2015 Jan 21 00:58:44 OPAH-S232 Downgrading to FS version 38 2015 Jan 21 00:58:44 OPAH-S232 Downgrade of file system complete 2015 Jan 21 00:58:44 OPAH-S232 LOM shutdown - waiting for directory write to finish 2015 Jan 21 00:58:45 OPAH-S232 Shut down request is removing all disk devices 2015 Jan 21 00:58:45 OPAH-S232 Shutdown has finished removing all disk drives 2015 Jan 21 00:58:46 OPAH-S232 LOM shutdown completed

Step 16 Execute the following script to downgrade the Berkeley DB version:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-4 Chapter 4 Downgrading from Release 4.4 Downgrading a VDS-TV Server from Release 4.4

#cd /arroyo/db/BerkeleyDB_downgrade_bin

#./BerkeleyDB_downgrade.sh

------2015-02-20 10:43:30 : START DATABASE DOWNGRADE------Starting BerkeleyDB dump/reload for CONTENT_OBJECT.db Created CONTENT_OBJECT.db in /arroyo/db/DATADIR_4_5 ...... Time taken: 2067 secs ------2015-02-20 11:18:31 : END DATABASE DOWNGRADE------

Note Downgrading the database from version 6.0 to 4.5 takes about one hour for 600K records in content_object.db.

Step 17 Take a backup of /root/crontab.root. Step 18 Execute the downgrade script.

vdstvDowngrade.sh -d

EXAMPLE

In this example VDS-TV 4.4 is downgraded to VDS-TV 3.9.1-b24

# /usr/sbin/vdstvDowngrade.sh -d /root/cdstv-3.9.1-b24-repo.iso

Step 19 Reboot the server. Step 20 After the VDS server reboots, log in as root. Step 21 Enter the following command and press Enter to restore the crontab entries.

crontab /root/crontab.root

Step 22 Start the services as per the sequence mentioned /etc/rc.local.

Note If the DB crashes on downgrade, then get a copy of DATADIR from a successfully downgraded server and start the services.

Note During the initialization process of a VDS server or after recovering a VDS server that has been down for less than an hour, the VDS database performs a complete synchronization. The database synchronization takes approximately five minutes before the server becomes ready for service. If the VDS server is down for a much more than an hour, the database synchronization takes longer than five minutes. The netstat command does not show the interfaces as up until the synchronization has completed.

Step 23 Using the CDSM GUI, verify the server is online: a. Click Monitor > System Health. The System Health Monitor page is displayed. b. Verify the status boxes for the server are green.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-5 Chapter 4 Downgrading from Release 4.4 Downgrading the Software on a CDSM or VVIM

It takes a few minutes to synchronize the database. Wait until the other VDS servers become reachable and the services are running. The CDSM GUI System Health Monitor Page can be used to verify the VDS server is functioning correctly after the downgrade. The CDSM GUI System Health Monitor page shows the states of the network, disk, and services on each VDS server. Step 24 After the VDS server has been verified as being reachable, log in to the CDSM GUI and disable the server offload: a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. c. Choose Online and click Submit. Step 25 If you are downgrading a Vault, enable the vault mirror group and turn the maintenance mode off for all the vaults. If you are downgrading a different server, go to Step 26. a. Use SSH to access each vault in the group as root and enter the following commands:

echo 1 > /proc/calypso/tunables/allowvaultarraymirroring

echo 0 > /proc/calypso/tunables/maintenancetimer

b. Go to vi /arroyo/test/vault/setup and uncomment the following line:

allow vault array mirroring 1

c. Go to vi /arroyo/test/afterrun and uncomment the following lines:

echo <# of copies> > /proc/calypso/tunables/maintenancemirrorcopies

Where, # of copies is one less than the mirror copies setting configured in the GUI.

echo 0 > /proc/calypso/tunables/maintenancearraymirroringallowed

echo 600 > /proc/calypso/tunables/maintenancetimer

echo 0 > /proc/calypso/tunables/allowvaultarraymirroring

Step 26 To verify that the VDS server is online, make sure that the file /var/tmp/TRICKLE_DOWN does not exist. Step 27 Login to CDSM and restart the collectd service.

# service collectd restart

Note The collectd process is restarted so that a 4.4 CDSM can monitor non-4.4 server.

The downgrade is complete.

Downgrading the Software on a CDSM or VVIM

If the CDS or VVI has redundant CDSMs or VVIMs, downgrade the secondary first, then downgrade the primary.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-6 Chapter 4 Downgrading from Release 4.4 Downgrading the Software on a CDSM or VVIM

The primary and secondary CDSM or VVIM can be determined by entering the ifconfig -a | more command. The primary has the following output: eth0:1 Link encap:Ethernet HWaddr 00:11:00:00:00:00 inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 Memory:b8820000-b8840000

The primary CDSM has device eth0:1. The secondary CDSM does not have the virtual IP address as up.

Note Downgrading a CDSM requires that the CDS-TV ISO image file has been downloaded and copied to the CDSM and if applicable, VVIM. Before downgrading the software, review the information in the “Introduction” section on page 1-1. For information on downloading the software files, see the “Getting the Cisco VDS-TV Software Files for Release 4.4” section on page 1-5.

Note Before downgrading a CDSM or VVIM, delete all sites and thin pipes from the CDSM or VVIM, if any exist.

To downgrade the software on a CDSM or VVIM, do the following:

Step 1 Log in to the CDSM as root. Log in to the secondary CDSM and downgrade it first, if redundant CDSMs exist. Step 2 Enter the following command and press Enter, to stop the database.

# service avsdb stop

# pgrep avsdb (to make sure there is no avsdb process running)

Step 3 If you downgrade to a release greater than or equal to 3.9.x, skip Step 4 to Step 11 Step 4 Check the deployment type. For ISA deployment do the following and for RTSP deployment go to Step 5: a. Login to VVIM. b. Execute the avsdb_util.py script from /arroyo/db/avsdb_util to retrieve the content store location.

# ./avsdb_util.py -s avsdb_tabletemplate.s -i 1 -o output

# cat output/avsdb_util_output.csv | awk 'BEGIN{FS=","} {print $3,$6}' | grep -v " $" > CSL

c. Copy the CSL file from the VVIM server to the server to being downgraded in /arroyo/db/avsdb_util directory. Step 5 Go to downgraded controller SSH window. Step 6 If contents in the system is more than 200K, then do the following else go to Step 7: a. Edit the avsdb file and add -m 1 as specified below:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-7 Chapter 4 Downgrading from Release 4.4 Downgrading the Software on a CDSM or VVIM

# vi /etc/rc.d/init.d/avsdb

# su - isa -c "cd /arroyo/db/; /bin/bash -c '/arroyo/db/avsdb –m 1 >>/arroyo/log/avsdb.out 2>> /arroyo/log/avsdb.err &'"

Step 7 Enter the following command and press Enter to start the database.

# service avsdb start

Step 8 Execute the DB downgrade migration script located in /arroyo/db directory. For ISA deployment:

# ./DBContentObjSizeReductionDowngradeMigrator -t 1 -d 1 -c 1 -s 150 -i /arroyo/db/avsdb_util/CSL > Downgrade_migration &

For RTSP deployment :

# ./DBContentObjSizeReductionDowngradeMigrator -t 2-d 1 -c 1 -s 150 > Downgrade_migration &

[-t] mandatory specifies deployment type. 1 for ISA deployment and 2 for RTSP deployment [-d] optional, specifies debug level. 1 for debug and 0 for no debug logs, default is 0

Note Redirect the output logs if debug is enabled.

[-c] optional, check before migration. 0 for no check and 1 for check before migration, default is 1 [-v] optional, verify migration. 1 for verifying migration and 0 for not verifying migration, [-s] optional, timeout value in seconds and default is 60 seconds [-i] mandatory for ISA deployment, file name containing content store location details Step 9 Enter the following command and press Enter to stop the AVSDB.

# service avsdb stop

# pgrep avsdb (to make sure there is no avsdb process running)

Step 10 Edit the avsdb file and remove -m 1 as edited in Step 6.

Step 11 Execute the following script to downgrade the Berkeley DB version: #cd /arroyo/db/BerkeleyDB_downgrade_bin

#./BerkeleyDB_downgrade.sh

------2015-02-20 10:43:30 : START DATABASE DOWNGRADE------Starting BerkeleyDB dump/reload for CONTENT_OBJECT.db Created CONTENT_OBJECT.db in /arroyo/db/DATADIR_4_5 ....

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-8 Chapter 4 Downgrading from Release 4.4 Downgrading the Software on a CDSM or VVIM

.... Time taken: 2067 secs ------2015-02-20 11:18:31 : END DATABASE DOWNGRADE------

Note Downgrading the database from version 6.0 to 4.5 takes about one hour for 600K records in content_object.db.

Step 12 Take a backup of /root/crontab.root. Step 13 Execute the downgrade script.

vdstvDowngrade.sh -d

EXAMPLE

In this example VDS-TV 4.4 CDSM is downgraded to VDS-TV 3.9.1-b24 CDSM

# /usr/sbin/vdstvDowngrade.sh -d /root/cdstv-3.9.1-b24-repo.iso

Step 14 Reboot the server. The OS downgrade is complete. Step 15 After the CDSM reboots, log in as root. Step 16 Enter the following command and press Enter to restore the crontab entries.

crontab /root/crontab.root

Step 17 Start the services as per the sequence mentioned /etc/rc.local.

Note If the DB crashes on downgrade, then get a copy of DATADIR from a successfully downgraded controller and start the services.

Step 18 Submit the CDSM setup page once and check if the data displayed in the primary and the backup CDSM match. Step 19 After downgrading the secondary CDSM or VVIM, assign the secondary CDSM or VVIM as primary and then downgrade the current secondary CDSM or VVIM as described above. Step 20 After both CDSMs or VVIMs are downgraded (secondary and primary), reset the password on one of CDSMs or VVIMs if you are unable to access the GUI. To reset the password, execute the following command as root user on the CDSM or VVIM: # /home/stats/resetpw Parsed 3 tokens, use PlainText, image version: 3.2.2-b0 Did not find regular file /etc/cdsremoteauth Password values reset successfully

Step 21 Reload the CDSM or VVIM GUI and enter the password. Step 22 Submit the CDSM/VVIM setup page once and verify that all configurations are retained after the downgrade.

The downgrade is complete.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-9 Chapter 4 Downgrading from Release 4.4 Downgrading the Software on a CDSM or VVIM

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 4-10

CHAPTER 5

System Maintenance

This chapter explains how to replace, remove, and add a VDS server, perform a backup and recovery of the configuration and database files, and recover the administrator password. This chapter covers the following topics: • Replacing a Server, page 5-2 • Removing a Server, page 5-9 • Adding a Server, page 5-15 • Recovering a Lost Administrator Password, page 5-22 • Recovering a Lost Administrator Password, page 5-22 • Disk Maintenance, page 5-22

Note If Virtual Video Infrastructure (VVI) with split-domain management is enabled, the CDSM pages associated with the Vaults and Caching Nodes display only on the VVI Manager (VVIM), and the CDSM pages associated with the Streamers display only on the Stream Manager. For more information, see the “Engineering Access Level Pages” appendix in the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4 or the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Caution Many of the functions discussed in this chapter involve rebooting a VDS server. Rebooting a Vault server does not interrupt stream services, but causes current ingests to fail. If your VDS does not have stream failover, rebooting a Streamer without offloading it interrupts all stream services. If possible, you should perform functions that require a system restart during times when the least number of users are actively connected to your system.

Caution Do not attempt to access the Linux command line unless you are familiar with the VDS, the Linux operating system, and have an understanding of the Linux command line.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-1 Chapter 5 System Maintenance Replacing a Server

Replacing a Server

You may need to replace a VDS server if the server is experiencing unresolvable problems. The procedure to replace a server in the VDS differs based on the type of server being replaced. This section covers the following procedures: • Replacing a CDSM or VVIM • Replacing a VDS Server

Note The new replacement server must be the same hardware model as that of the server being replaced.

Replacing a CDSM or VVIM

The procedure to replace a CDSM or VVIM differs based on whether or not there are redundant CDSMs (or VVIMs). With CDSM redundancy, if the primary CDSM becomes unavailable, the secondary CDSM takes over the virtual IP address and the administrator can connect to the secondary CDSM within 15 seconds.

Note These procedures assume the new server has the same software version as the server being replaced.

Before you can replace a server, the new server must have the same Cisco VDS-TV software release as the server being replaced. To verify the software version, use the cat /arroyo/image/tags command. For information on upgrading the software, see Chapter 3, “Upgrading to Release 4.4.”

Replacing a Redundant CDSM or VVIM

Replacing a redundant CDSM or VVIM involves the following tasks: 1. Shut down the old CDSM or VVIM. 2. Start up the new CDSM which is configured with the same IP address as the old CDSM. 3. Stop the database on the primary CDSM and copy it to the new CDSM. 4. Run the vdsconfig script to configure the new CDSM and inform the other CDS servers of the new CDSM. 5. Reboot the new CDSM. To replace a redundant CDSM, do the following:

Step 1 Log in to the CDSM being replaced as root. Step 2 Stop Auto Importer if it is enabled on the CDSM being replaced. a. Check that the Auto Importer process is not running. service importer status

b. If Auto Importer is running, use the following command to stop the importer. service importer stop

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-2 Chapter 5 System Maintenance Replacing a Server

Step 3 In an ISA deployment, stop the Exporter process if it is enabled on the CDSM being replaced. a. Check that the Exporter process is not running. service exporter status

b. If the Exporter is running, use the following command to stop the exporter. service exporter stop

Step 4 Stop the database on the CDSM being replaced. # service avsdb stop

Step 5 Ensure that the database is fully stopped on the CDSM being replaced. a. Check that the database thread count returns nothing. netstat –an | grep 9999

b. Make sure that no process ID (PID) is returned. service avsdb status

c. If the database is still up, use the following command to stop the database. service avsdb stop

Step 6 To prevent the CDSM being removed from impacting the CDS network if it boots up again, do the following: a. Log in to the CDSM being replaced as user isa and edit the .arroyorc file to remove all entries in the Replication Group members section of the file. Step 7 Shut down the CDSM being replaced. # poweroff

Step 8 You must stop the database on the primary CDSM before copying it to the new CDSM. Log in to the primary CDSM as root. Step 9 Stop Auto Importer if it is enabled on the primary CDSM. a. Check that the Auto Importer process is not running. service importer status

b. If Auto Importer is running, use the following command to stop the importer. service importer stop

Step 10 In an ISA deployment, stop the Exporter process if it is enabled on the primary CDSM. a. Check that the Exporter process is not running. service exporter status

b. If the Exporter is running, use the following command to stop the exporter. service exporter stop

Step 11 Stop the database on the primary CDSM. # service avsdb stop

Step 12 Ensure that the database is fully stopped on the primary CDSM. a. Check that the database thread count returns nothing.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-3 Chapter 5 System Maintenance Replacing a Server

netstat –an | grep 9999

b. Make sure that no process ID (PID) is returned. service avsdb status

c. If the database is still up, use the following command to stop the database. service avsdb stop

Note The new replacement server has already been verified or upgraded to the same Cisco VDS-TV software version as the server it is replacing. This includes running the vdsinit script to install the software; not the vdsconfig script.

The new replacement CDSM has been configured with the same IP address as the CDSM being replaced.

Step 13 On the new CDSM, use the scp command to copy the DATADIR directory from the primary CDSM. For example, if the primary CDSM has an IP address of 172.22.98.109, the following command is used: # scp -r 172.22.98.109:/arroyo/db/DATADIR /arroyo/db

Step 14 On the primary CDSM, start the database again. [root]# service avsdb start

Step 15 On the primary CDSM, start the Auto Importer again if it had been running on the primary CDSM prior to the shutdown of the database. [root]# service importer start [root]# service importer status

Step 16 In an ISA environment, on the primary CDSM, start the Exporter again if it had been running on the primary CDSM prior to the shutdown of the database. [root]# service exporter start [root]# service exporter status

Step 17 On the new CDSM, change the ownership of DATADIR from root:root to isa:isa. # chown –R isa:isa /arroyo/db/DATADIR

Step 18 Run the vdsconfig script. Answer the following prompts using the same configuration as the CDSM being replaced. • When the script returns the list of current replication groups, verify that all members have been listed. If any member is missing, at the “Do you want to edit the replication group members?” prompt, enter Y for yes, and enter the missing member. • At the “Do you want to enable CDSM redundancy?” prompt, enter Y for yes. • At the “Is this node getting added to an existing deployment?” prompt, enter N for no because the DATADIR has already been copied from the primary CDSM. • Answer appropriately to the prompts for getting the ID from the first CDSM. Step 19 Reboot the CDSM. Step 20 Login to the GUI of the new CDSM as a user with Engineering access. The CDSM Setup page is displayed.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-4 Chapter 5 System Maintenance Replacing a Server

Step 21 In the Installation drop-down list on the CDSM Setup page, choose either RTSP or ISA depending on your environment. Step 22 If Media Scheduler is enabled on the existing CDSM, do the following: a. Scroll down to the Media Scheduler section of the CDSM Setup page, and click the ON radio button next to the Media Scheduler field. In the Activation Key field, enter the software access key from your Right to Use Notification for the Content Delivery Application Media Scheduler (CDAMS) product. b. Scroll down to the Ingest Manager section, and click the ON radio button next to the Ingest Manager field. In the Activation key field, enter the software access key from your Right to Use Notification from the CDAMS product. Step 23 Verify that all other settings on the CDSM Setup page are the same as on the existing CDSM and click Submit. Step 24 Choose Maintain > Software > System Configs. The System Configs page is displayed. Step 25 Verify the CDS parameters on the System Configs page and click Submit. Step 26 Configure NTP on the new CDSM. a. Set your time zone on the CDSM by copying your time zone file to the /etc/local file. In the following example, the time zone is Asia/Shanghai. #cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

b. Verify that the clock information displayed in the file /etc/sysconfig/clock is correct. The file should display the following information: Zone=time zone UTC=fale ARC=false

The Zone filed represents the time zone as presented by the zone file under directory /usr/share/zoneinfo. Setting the UTC field to false sets the clock to the local time. Setting the ARC field to false, sets the time to Unix epoch time. c. Remove all existing lines from the NTP configuration file /etc/ntp.conf and add the NTP server using the command server NTP_Server_IP_Address # local clock. In the following example, the NTP server has an IP address of 10.74.124.189. # server 10.74.124.189 # local clock

d. Start the NTP service. # service ntpd start

e. Enable the NTP service. # chkconfig ntpd on

Step 27 Enter the following command to start the services in the new CDSM. # vdsServices start

Step 28 Check the newly added CDSM’s health monitor page to verify if all the server statuses are displayed correctly.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-5 Chapter 5 System Maintenance Replacing a Server

Step 29 Shut down the database and reboot the new secondary CDSM. # service avsdb stop # service avsdb status # netstat -an | grep 9999 # reboot

Replacing a Standalone CDSM

Note This procedure assumes the new server has the same software version as the server being replaced.

Replacing a standalone CDSM includes the following tasks: 1. Remove the old CDSM from the CDS. 2. Add the new replacement CDSM into the CDS with the same IP address as the old CDSM.

Step 1 Log in to the existing CDSM GUI as a user with Engineering access. Step 2 Choose Maintain > Software > CDSM Setup. The CDSM Setup page is displayed. Step 3 Write down all the settings on the CDSM Setup page. Step 4 Back up the configuration and database files on the existing CDSM. Step 5 To prevent the existing CDSM from impacting the CDS network if it boots up again, do the following: a. Log in to the CDSM as user isa and edit the .arroyorc file to remove all entries in the Replication Group members section of the file. Step 6 Shut down the existing CDSM. poweroff

Step 7 On the new CDSM, restore the configuration and database files using the backup that was made from the existing CDSM.

Note The new replacement server has already been verified or upgraded to the same Cisco VDS-TV software version as the server it is replacing.

Step 8 Run the vdsconfig script. At the “Do you want to enable CDSM redundancy?” prompt, enter N for no. At the “Is this node getting added to an existing deployment?” prompt, enter N for no because the CDSM is not a newly-added CDSM, it is replacing an existing CDSM. vdsconfig

Step 9 Shut down the database and reboot the newly secondary CDSM. # service avsdb stop # service avsdb status # netstat -an | grep 9999 # reboot

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-6 Chapter 5 System Maintenance Replacing a Server

Step 10 Log in to the new CDSM GUI as a user with Engineering access. If a user account with the Engineering access level does not exist, log in to the CDSM as admin, or as another user that has Master access, and add a user with Engineering access. a. Choose Maintain > User > Add Users. The Add Users page is displayed. b. In the New User and Password fields, enter the user name and password for this account. c. From the Access drop-down list, choose Engineering. d. Click Add User. Log out of the CDSM, and log in as the user with the Engineering access level. The CDSM Setup page is displayed. If the CDSM Setup page is not displayed, choose Maintain > Software > CDSM Setup. Step 11 In the Installation drop-down list, choose either RTSP or ISA depending on your environment. Step 12 If Media Scheduler is enabled on existing CDSM, do the following: a. Scroll down to the Media Scheduler section, and click the ON radio button next to the Media Scheduler field. In the Activation Key field, enter the software access key from your Right to Use Notification for the CDAMS product. b. Scroll down to the Ingest Manager section, and click the ON radio button next to the Ingest Manager field. In the Activation key field, enter the software access key from your Right to Use Notification from the CDAMS product. Step 13 Verify that all other settings are the same as on the existing CDSM and click Submit. Step 14 On the GUI of the new CDSM, choose Maintain > Software > System Configs. The System Configs page is displayed. Step 15 Verify the VDS parameters on the System Configs page and click Submit. Step 16 Choose Monitor > System Health, and verify connectivity to all the VDS servers by checking the status of each server. All status boxes should be green.

Replacing a VDS Server

Replacing a Vault, Streamer, ISV, or Caching Node includes the following tasks: 1. Offload the server and shut down the processes on the server. 2. Back up the configuration to an available Linux server. 3. Restore the backup on the new replacement server. 4. Log in to the CDSM and complete the configuration.

Note The replacement server and the server being removed must be of the same server type. Otherwise, remove the old server from the network by following the procedure in the “Removing a Server” section on page 5-9 and then, add the new server to the network by following the procedure in the “Adding a Server” section on page 5-15.

To replace a Vault, Streamer, ISV, or Caching Node, do the following:

Step 1 Using the CDSM GUI, offload the server that is being replaced. a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-7 Chapter 5 System Maintenance Replacing a Server

b. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. c. Choose Enable and click Submit. When Server Offload is enabled on a server, the server is configured to reject new provisioning; that is, do not allow new ingests on a Vault and do not allow new streams on a Streamer and move existing streams to another Streamer gracefully. Step 2 Log in to the server as root. Step 3 Ensure the server is fully offloaded. a. Verify that the TRICKLE_DOWN file exists in the /usr/tmp directory. b. For a Streamer, check that the protocoltiming log displays a warning message indicating that the server is going offline. tail -f /arroyo/log/protocoltiming.log.20090917

c. For a Streamer, make sure that all the active streams have moved over to the other Streamers. Check the Active Streams line in the protocoltiming log. d. For a Vault, make sure that all active ingests on this server have finished. Check that there is no Active Ingest Connections line in the protocoltiming log. e. Check there is no active traffic on the network interface cards (NICs) using the /home/stats/ifstats command. Step 4 Stop the database and statsd processes using the following commands: # service avsdb stop # service statsd stop

Step 5 Ensure the database and statsd are fully stopped. a. Check that the database thread count returns nothing. netstat -an | grep 9999

b. Check that the statsd process returns nothing. service statsd status

Step 6 Back up the configuration and database files. Step 7 On the VDS server being replaced, to prevent the VDS server from impacting the VDS network if it boots up again, comment out all of the lines in the /etc/rc.local file and edit the .arroyorc file to remove all entries in the Replication Group members section of the file. Step 8 Using the CDSM GUI, shut down the server. a. Click Maintain > Servers > Server Shutdown. b. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. c. From the Shutdown drop-down list, choose Yes and click Submit. Step 9 Log in to the new server as user root.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-8 Chapter 5 System Maintenance Removing a Server

Step 10 Move a copy of the DATADIR from a working server to the replacement server. Step 11 Execute vdsconfig and Enter No for the following question, Is this node getting added to an existing deployment ? (yes/no) :

Step 12 Start the avsdb/statstd/collectd on the Server and submit the pages for replaced server in the CDSM/VVIM. # service avsdb start # service statsd start # service collectd start

Step 13 Verify that configuration values are written and stop the services. # service avsdb stop # service statsd stop # service collectd stop

Step 14 Enter the following command and press Enter to start all the services. # vdsServices start

Step 15 Using the CDSM, disable the server offload. a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. c. Choose Disable and click Submit. When Server Offload is enabled on a server, the server is configured to reject new provisioning; that is, do not allow new ingests on a Vault and do not allow new streams on a Streamer and move existing streams to another Streamer gracefully. Step 16 Using the CDSM GUI, verify the server is online. a. Click Monitor > System Health. The System Health Monitor page is displayed. b. The status boxes for the server should all be green.

Removing a Server

You can remove a server if the server is experiencing unresolvable problems or when the network address or configuration has changed and you need to add the server back into the VDS network using a new address or configuration. This section documents the following procedures: • Removing a CDSM • Removing a VDS Server

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-9 Chapter 5 System Maintenance Removing a Server

Removing a CDSM

Note A CDSM should only be removed if there are redundant CDSMs because at least one CDSM must be operational at all times.

To remove a CDSM, do the following:

Step 1 Log in to the CDSM to be removed as root. Step 2 Stop Auto Importer if it is enabled on the CDSM being removed. a. Check that the Auto Importer process is not running. service importer status

b. If Auto Importer is running, stop the auto importer process. service importer stop

Step 3 In an ISA deployment, stop the Exporter process if it is enabled on the CDSM being removed. a. Check that the Exporter process is not running. service exporter status

b. If the Exporter is running, stop the exporter process. service exporter stop

Step 4 Execute the following commands to de-seed the CDSM. cd /home/stats ./svrinit_15 -d -i -s -h -g

Step 5 Stop the database on the CDSM being removed. # service avsdb stop

Step 6 Ensure that the database is fully stopped on the CDMS being removed. a. Check that the database thread count returns nothing. netstat –an | grep 9999

b. Make sure that no process ID (PID) is returned. service avsdb status

c. If the database is still up, stop the database service avsdb stop

Step 7 On the primary CDSM, do the following: a. Edit the .arroyorc file and remove the CDSM entry, which is the controller entry in the Replication Group Members section. b. If the Auto Importer is running on the primary CDSM, stop this process. [root]# service importer status [root]# service importer stop

c. In an ISA environment, if the Exporter is running on the primary CDSM, stop this process.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-10 Chapter 5 System Maintenance Removing a Server

[root]# service exporter status [root]# service exporter stop

d. Stop the database on the primary CDSM. [root]# service avsdb stop [root]# service avsdb status [root]# netstat -an | grep 9999

e. Restart the database on the primary CDSM. [root]# service avsdb start

f. If the Auto Importer was running on the primary CDSM, wait five minutes until the database has restarted, and restart the Auto Importer processes. [root]# service importer start [root]# service importer status

g. In an ISA environment, if the Exporter process was running on the primary CDSM, restart the Exporter processes. [root]# service exporter start [root]# service exporter status

h. Restart collectd in primary CDSM. [root]# service collectd restart

Step 8 On each VDS server in the system, do the following: a. Edit the .arroyorc file and remove the CDSM entry, which is the controller entry in the Replication Group Members section. b. In an RTSP environment, stop the database and all applications on the VDS server. [root]# vdsServices stop [root]# vdsServices status

c. In an ISA environment, stop the database on the VDS server. [root]# service avsdb stop [root]# service avsdb status [root]# netstat -an | grep 9999

d. In an RTSP environment, restart the database and applications on Vaults using the following commands: [root]# vdsServices start [root]# vdsServices status

e. In an ISA environment, restart the database on the VDS server using the following commands: [root]# service avsdb start [root]# service avsdb status

Step 9 Modify the file /etc/sysconfig/statsd to reflect OPTIONS = -d eth0 instead of the IP address. Step 10 Stop the statsd process. # service statsd stop

Step 11 To verify that the statsd process has stopped, try accessing the remaining CDSM by the virtual IP address that was used for CDSM redundancy. If successful, shut down the virtual IP address by using the ifconfig eth0:1 down command.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-11 Chapter 5 System Maintenance Removing a Server

Step 12 To prevent the CDSM being removed from impacting the VDS network if it boots up again, do the following: a. Log in to the CDSM as user isa and edit the .arroyorc file to remove all entries in the Replication Group members section of the file. Step 13 Shut down the CDSM being removed. #poweroff

Removing a VDS Server

Removing a Vault, Streamer, ISV, or Caching Node includes the following tasks: 1. Offload the server, shut down the processes on the server, and deregister the server. 2. Remove the server entry from the .arroyorc file on each VDS server. 3. Shut down the server and remove it from the CDSM. To permanently remove a Vault, Streamer, Caching Node, or ISV, do the following:

Step 1 Using the CDSM GUI, offload the server that you want to remove. a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed. b. From the Server IP drop-down list, choose the IP address or nickname of the server and click Display. c. Choose Enable and click Submit. When Server Offload is enabled on a server, the server is configured to reject new provisioning; that is, do not allow new ingests on a Vault and do not allow new streams on a Streamer and move existing streams to another Streamer gracefully. Step 2 Log into the server as root. Step 3 Ensure that the server is fully offloaded. a. Verify that the TRICKLE_DOWN file exists in the /usr/tmp directory. b. For a Streamer, check that the protocoltiming log displays a warning message indicating that the server is going offline. tail -f /arroyo/log/protocoltiming.log.20090917

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-12 Chapter 5 System Maintenance Removing a Server

Step 4 If the server is a member of a group, remove the server from the group. a. From the VDS GUI, click Configure > Array Level > Stream/Vault/Cache Groups Setup. The Group Configure page is displayed. b. From the Select Stream/Vault/Cache Group drop-down list, choose the group ID and click Display. c. From the New Group drop-down list, choose None for the VDS server and click Submit.

Note If replication group support is enabled then remove the server from the corresponding replication group by navigating to Configure > Array Level > Replication Groups Setup.

Step 5 Stop the statsd process. # service statsd stop

Step 6 Ensure the statsd process is fully stopped. Check that the statsd process returns nothing. # service statsd status

Note If statsd is running when the svrinit_15 command is used, the VDS server still shows up in the CDSM GUI as a phantom server. Stop the statsd process, then use the svrinit_15 command, and the phantom server is removed. The database must still be running on the VDS server at the time of using the svrinit_15 command.

Step 7 Use the svrinit_15 command to deregister the server by using the -d option. # cd/home/stats # ./svrinit_15 -d -i -s -h -g

Step 8 In an RTSP environment, stop the database and applications on the VDS server being removed using the following commands: [root]# vdsServices stop [root]# vdsServices status

Step 9 In an ISA environment, stop the database on the VDS server being removed using the following command: # service avsdb stop

Step 10 Ensure that the database is fully stopped. a. Check that the database thread count returns nothing. netstat –an | grep 9999

b. Make sure that no process ID (PID) is returned. service avsdb stop

c. If the database is still up, stop the database. service avsdb stop

Step 11 On each CDSM, do the following: a. Log in to the server as user root.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-13 Chapter 5 System Maintenance Removing a Server

b. Edit the .arroyorc file and remove the server entry under the Replication Group Members section. a. Stop the Auto Importer process if it is running using the following commands: # service importer stop

b. In an ISA environment, stop the Exporter process if it is running. # service exporter stop

c. Shut down the database. #service avsdb stop

d. Ensure that the database has fully stopped. netstat –an | grep 9999 service avsdb stop

e. Restart the database on the CDSM. [root]# service avsdb restart

f. Restart the Auto Importer process if it had been running. [root]# service importer restart

g. In an ISA environment, on the primary CDSM, start the Exporter again if it had been running on the CDSM prior to the shutdown of the database. [root]# service exporter restart

Step 12 On each VDS server, do the following: a. Log in to the server as user isa. b. Edit the .arroyorc file and remove the server entry under the Replication Group Members section. c. Stop the database and applications. In an RTSP environment, use the following commands: # vdsServices stop

In an ISA environment, use the following commands: # service avsdb stop

d. Restart the database and applications. For a Vault in an RTSP environment, use the following commands: [root]# vdsServices start [root]# vdsServices status

For a Streamer in an RTSP environment, use the following commands: [root]# service avsdb start [root]# service rtsp start [isa]# vdsServices status

In an ISA environment, use the following commands: [root]# service avsdb start [root]# service avsdb status

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-14 Chapter 5 System Maintenance Adding a Server

Step 13 On the VDS server being removed, to prevent the VDS server from impacting the VDS network if it is boots up again, edit the .arroyorc file to remove all entries in the Replication Group members section of the file. Step 14 Shut down the VDS server. [root]# vdsServices stop [root]# poweroff

Step 15 Log in to the CDSM GUI and verify that the VDS server is not displayed in the System Health Monitor page. If the removed VDS server displays in the System Health Monitor page, do the following: a. Log in to the CDSM as root. b. Edit the .arroyorc file, record the server ID and group ID of the CDSM, then change the server ID and group ID entry for the CDSM to be the same as the server ID and group ID as the removed server. c. Execute the ./svrinit_15 command. This manually removes the VDS server. # cd /home/stats # ./svrinit_15 -d -i -s -h -g

d. Restart collectd in CDSM. # service collectd restart

e. Edit the .arroyorc file again and change the server ID and group ID entry back to the CDSM values.

Adding a Server

The procedure to add a server in the VDS is different depending on the type of server being added. This section provides information on the following procedures: • Adding a Second CDSM • Adding a VDS Server

Adding a Second CDSM

Note All VDS servers and CDSM that are part of the same system as the CDSM you are adding must be online for the database synchronization to work properly.

Note The database synchronization copies database information from all existing VDS servers and the existing CDSM, with the exception of Stream Report data. If you require a copy of Stream Report data, copy the database on the existing CDSM to the new CDSM. The copy is performed during a maintenance window on the existing CDSM.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-15 Chapter 5 System Maintenance Adding a Server

To implement the CDSM Redundancy feature, do the following:

Step 1 Log in to the new CDSM as root .

Note The new server has already been verified or upgraded to the same Cisco VDS-TV software version as the server it is replacing. This includes running the vdsinit script to install the software; not the vdsconfig script.

Step 2 Run the vdsconfig script. The following are some user prompts to be aware of when running the vdsconfig script. : – When the script returns the list of current replication groups, verify that all members have been listed. If any member is missing, at the “Do you want to edit the replication group members?” prompt, enter Y for yes, and enter the missing member. – At the “Is this node getting added to an exiting deployment?” prompt, enter Y for yes to dynamically add this CDSM. – At the “Do you want to enable CDSM redundancy?” prompt, enter Y for yes. You are prompted for the virtual IP address and netmask that is used to access the CDSM. Answer appropriately to the prompts related to getting the ID from the first CDSM. Step 3 Login in to the existing CDSM as root. Step 4 Stop Auto Importer if it is enabled on the existing CDSM. a. Check that the Auto Importer process is not running. service importer status

b. If Auto Importer is running, stop the auto importer. service importer stop

Step 5 In an ISA deployment, stop the Exporter process if it is enabled on the existing CDSM. a. Check that the Exporter process is not running. service exporter status

b. If the Exporter is running, stop the exporter service exporter stop

Step 6 Stop the database on the existing CDSM. [root]# service avsdb stop

Step 7 Ensure that the database is fully stopped. a. Check that the database thread count returns nothing. netstat –an | grep 9999

b. Make sure that no process ID (PID) is returned. service avsdb status

c. If the database is still up, stop the database. service avsdb stop

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-16 Chapter 5 System Maintenance Adding a Server

Step 8 Stop the database on the new CDSM and verify that the database has fully stopped using the procedure outline in Step 6 to Step 7. Step 9 On the new CDSM, use the scp command to copy the DATADIR directory from the existing CDSM. For example, if the existing CDSM has an IP address of 172.22.98.109, the following command is used: # scp -r 172.22.98.109:/arroyo/db/DATADIR /arroyo/db

Step 10 Change the ownership of DATADIR from root:root to isa:isa. # chown –R isa:isa /arroyo/db/DATADIR

Step 11 Start the database on the existing CDSM. # service avsdb start

Step 12 On the existing CDSM, start the Auto Importer again if it had been running prior to shutting down the database. [root]# service importer start [root]# service importer status

Step 13 In an ISA environment, on the existing CDSM, start the Exporter again if it had been running prior to shutting down the database. [root]# service exporter start [root]# service exporter status

Step 14 On the new CDSM, start the Apache server by running the following command: service vds-httpd start

Step 15 Log in to the GUI on the new CDSM as a user with Engineering access level. The CDSM Setup page is displayed. Step 16 In the Installation drop-down list, choose either RTSP or ISA depending on your environment. Step 17 If Media Scheduler is enabled on existing CDSM, do the following: a. Scroll down to the Media Scheduler section, and click the ON radio button next to the Media Scheduler field. In the Activation Key field, enter the software access key from your Right to Use Notification for the CDAMS product. b. Scroll down to the Ingest Manager section, and click the ON radio button next to the Ingest Manager field. In the Activation key field, enter the software access key from your Right to Use Notification from the CDAMS product. Step 18 Verify that all other settings are the same as on the existing CDSM and click Submit. Step 19 On the GUI of the new CDSM, choose Maintain > Software > System Configs. The System Configs page is displayed. Step 20 Verify the CDS parameters on the System Configs page and click Submit. Step 21 Configure NTP on the new CDSM. a. Set your time zone on the CDSM by copying your time zone file to the /etc/local file. In the following example, the time zone is Asia/Shanghai. #cp /usr/share/zoneinfo/Asia/Shanghai /etc/localtime

b. Verify that the clock information displayed in the file /etc/sysconfig/clock is correct. The file should display the following information Zone=time zone UTC=fale ARC=false

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-17 Chapter 5 System Maintenance Adding a Server

Timezone represents zone as presented by the zone flie under directory /usr/share/zoneinf. Setting UTC to lase sets the clock to the local time. Setting ARC to false, sets the time to Unix epoch time. c. Remove all existing lines from the NTP configuration file /etc/ntp.conf and add the NTP server using the command server NTP_Sever_IP_Address # local clock. In the following example, the NTP server has an IP address of 10.74.124.189. # server 10.74.124.189 # local clock

d. Start the NTP service. # service ntpd start

e. Turn on the NTP service. # chkconfig ntpd on

Step 22 Shut down the database and reboot the newly added CDSM. # service avsdb stop # service avsdb status # netstat -an | grep 9999 # reboot

Step 23 Wait for the CDSM to come up and start the services using the following command: # vdsServices start

Step 24 Execute the svrinit_15 on the new CDSM. # cd /home/stats # ./svrinit_15 -d -i -s -h -g

Step 25 Restart collectd on both the CDSMs. # service collectd restart

Step 26 Check the newly added CDSM health monitor page to verify if all the server statuses are displayed correctly. Step 27 On the existing CDSM, run the vdsconfig script to enable redundancy. Step 28 When the vdsconfig script completes, edit the rc.local file and uncomment all the command lines. Step 29 Reboot the existing CDSM. The CDSM Redundancy feature is configured.

Adding a VDS Server

Note All VDS servers and CDSMs that are part of the same system as the VDS server you are adding must be online for the database synchronization to work properly.

To add a Vault, Streamer, Caching Node, or ISV to an existing VDS, do the following:

Step 1 Log into the new server as user root.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-18 Chapter 5 System Maintenance Adding a Server

Step 2 Make sure the only interface that is configured is the management interface. If other interfaces are configured (for example, the ingest interface), the adding a server procedure fails. ifconfig -a | more

If other interfaces are configured on this VDS server, manually shut them down by using the ifconfig eth# down command, where eth# is the interface name (for example, eth1). Step 3 Run the vdsconfig script to configure the VDS server, create the VDS service config file, and edit the .arroyorc file on every VDS server in the same system. The script prompts display default values in brackets. To accept the default, press Enter. If the default value is incorrect, enter the correct value and press Enter.

Note The vdsconfig script detects all configured interfaces. When adding a new VDS server, only the management interface should be configured. The script provides the ability to disable the other interfaces. You must disable all other interfaces and leave only the management interface configured for the vdsconfig script to complete successfully.

[root]# vdsconfig

Please ensure an IP address and netmask are configured for management interface eth0:

Select an option or an interface to re-configure/disable: 1. eth0 ip:172.22.99.237 mask:255.255.254.0 bcast:172.22.99.255 2. Configure another interface 3. Done Choice [3]: 3

Backing up old scripts /etc/sysconfig/network-scripts Writing new ifcfg-ethx scripts

Enter a hostname: hostname Enter the number of the eth interface that connects to the gateway [eth0]: Enter the default gateway: gateway

Backing up /etc/sysconfig/network Writing new /etc/sysconfig/network Backing up /etc/hosts Writing new /etc/hosts Shutting down interface eth0: [ OK ] Shutting down loopback interface: [ OK ] PCI: Enabling device 0000:0e:00.0 (0000 -> 0003) PCI: Enabling device 0000:0e:00.1 (0000 -> 0003) Restarting network services, this may take a minute: Shutting down loopback interface: [ OK ] Bringing up loopback interface: [ OK ] Bringing up interface eth0: [ OK ] Network services restarted; may take a few seconds to establish connectivity Reboot for hostname changes to take effect Network configuration complete

Please choose your platform from the following list of valid platforms:

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-19 Chapter 5 System Maintenance Adding a Server

1. 2U-SCSI-1 2. 1. 2U-SCSI-1 2. 3U-SCSI-1 3. 3U-SCSI-10 ...... 16. CDE110-2C-1 17. CDE205-1C1-C 18. CDE220-2A-C ...... 32. CDE420-4G-C 33. CDE420-4G-F Choice: server_platform

Please select a device role: 1. ssv 2. vault 3. cache 4. streamer Choice: device_role

Step 4 The vdsconfig script asks for information about your VDS to get a server ID and group ID for the new VDS server. Answer the questions correctly for your system to make sure the correct server ID and group ID are applied. If the device role is a Streamer, you have the option to enter the Stream Control interface through the script, or later through the CDSM GUI. Step 5 The vdsconfig script prompts you to add the replication group members. Add all the VDS servers, including CDSMs, that share information with this server. Do you want to edit the replication group members (yes/no) [n]: y

Note With the exception of the server you are configuring, all VDS servers (VVIMs, Stream Managers, CDSMs, ISVs, Vaults, Caching Nodes, and Streamers) that are members of the replication group should be configured at this time. The server you are configuring is not configured as a replication group member.

Step 6 If this is an RTSP deployment, you are asked if it is an NGOD deployment and what NPT syntax is used for the deployment. Configuring RTSP ecosystem Is this an NGOD deployment (yes/no):

Choose NPT Syntax: 1. NGOD 2. NGOD_SC 3. Standard Choice [NGOD]:3

Writing /home/isa/bss/scripts/arroyo-env.sh Writing /home/isa/bss/scripts/arroyo-site-env.sh Setting Sttributes for AVSRTSPServer

Step 7 In an RTSP deployment, the vdsconfig script asks if you want to enable Redirect Server. Answer no (N) to disable the Redirect Server. Do you want to enable Redirect Server ? (yes/no) [y]: no

Step 8 The vdsconfig script asks if the server is being added to an existing deployment. Answer yes (Y) to synchronizes the database on the new server with the database on all the other CDS servers. Is this node getting added to an existing deployment ? (yes/no) [y]:y

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-20 Chapter 5 System Maintenance Adding a Server

Starting database sync...

...Output omitted

Database sync completed. Started avsdb, verify with “service avsdb status” Starting statsd

Note The time it takes to synchronize the database is proportional to the size of the database. Database synchronization could take up to 30 minutes for 90,000 content objects.

Step 9 The vdsconfig script asks if you want to run svrinit to seed the database. Enter Y for yes to run svrinit to seed the database or N for no. Enter the IP address, netmask, hostname, and gateway of this VDS server when prompted. These are the same settings as you configured for the eth0 interface at the beginning of the vdsconfig script.

Note You must seed the database whenever you are adding a new VDS server to a network or installing the VDS-TV software on a VDS server. Wait until all e database connections are established before entering the management IP address, management netmask, hostname, and gateway of this VDS server.

Run svrinit to seed database? (yes/no) [n]: y Running svrinit Please enter an IP address for svrinit: mgmt_ip_address Please enter a netmask for svrinit: mgmt_netmask Please enter a hostname for svrinit: hostname Please enter a gateway for svrinit:gateway Writing /etc/rc.d/rc.local RTSP ecosystem configuration finished vdsconfig finished, please use CDSM to complete configuration

If you receive an error message indicating the database is unavailable and cannot be set up, enter the following commands to initialize the database tables for a VDS server in an ISA/RTSP environment: [root]# service avsdb start

Note If this server has, at some point, been part of a Cisco VDS array before this configuration, clean out /arroyo/db by deleting *.db *.idx and all replication IP address files. Also, in an ISA deployment, delete all /persist directories found in the directories under /home/isa/Streaming and /home/isa/ContentStore.

Step 10 Restart collectd in both primary and secondary CDSM.

# service collectd restart

Step 11 Verify connectivity to the CDSM. Using the CDSM GUI, choose Monitor > System Health. The System Health Monitor page is displayed. The status boxes for the server should all be green. The services status box may be yellow because some services may not be running. Step 12 To complete the server configuration, log in to the CDSM GUI and go through the Configure > Server Level pages for the new server.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-21 Chapter 5 System Maintenance Recovering a Lost Administrator Password

Note In RTSP deployments, if you need to enable the Redirect Server in Release 4.4, run the vdsconfig script and answer yes (Y) at the following prompt:

Do you want to enable Redirect Server ? (yes/no) [y]

Recovering a Lost Administrator Password

If an administrator password is forgotten, lost, or mis configured, you must reset the password on the server.

Note There is no way to recover a lost administrator password. You must reset the password to a new one.

To reset the password, do the following:

Step 1 Log into the server as root. Step 2 Enter the following command: /home/stats/resetpw

Step 3 Log in to the CDSM with the username admin and the password admin. Step 4 Reset the admin password by following the steps detailed in the “Editing User Settings” section on page 7-3 in the Cisco VDS-TV ISA Software Configuration Guide, Release 4.4 or the Cisco VDS-TV RTSP Software Configuration Guide, Release 4.4.

Disk Maintenance

The hard disk drives on theCDE110, CDE220, CDE420, CDE250 and CDE460 are hot-swappable. For the procedure outlining the steps for removing and replacing a hard disk drive, see Removing and Replacing a Hard Disk Drive in the Cisco Content Delivery Engine 110 Hardware Installation Guide and “Installing External Storage Drives” in the Cisco Content Delivery Engine 205/220/250/280/420/460/470 Hardware Installation Guide.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide 5-22

APPENDIX A

Troubleshooting

This appendix presents troubleshooting tips for the upgrade and downgrade procedures. The topics covered in this appendix include: • Interfacing with the VDS Server During an Upgrade, page A-1 • Error Messages, page A-2 • Warning Messages, page A-5 • Failed or Stalled Upgrade, page A-5 • VNC Listener, page A-6

Interfacing with the VDS Server During an Upgrade

This section covers the following topics: • Viewing Upgrade Progress with Keyboard and Monitor Interface • Backspace Does Not Work in Terminal • Monitoring OS Load Runtime Syslog File

Viewing Upgrade Progress with Keyboard and Monitor Interface

If the serial and VNC Listener cannot be used to perform an upgrade, the keyboard and video monitor can be used for the upgrade. However, performing the upgrade using the keyboard and monitor provides limited visibility and is not recommended. If the only option is to use a keyboard and monitor for the upgrade, press Enter when the upgrade script prompts for the VNC Listener. The server reboots several times. During the second stage of the operating system (OS) upgrade, the package installation progress and other steps of the upgrade can be viewed on the third virtual terminal on the keyboard/monitor interface. To access this virtual terminal press Alt-F3 and the video switches to the third terminal.

Backspace Does Not Work in Terminal

When working with different applications that provide SSH or telnet capability there are times when the terminal definition does not translate correctly to the shell opened to the server being upgraded. This causes the scripts to be unable to read the text entered and the backspace key does not function correctly.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide A-1 Appendix A Troubleshooting Error Messages

To assist in allowing the backspace to work, determine the backspace key definition and use stty erase command to set the definition.

Note This does not always work because the application closest to the user may still not translate the key definition correctly even after determining the key definition.

To determine the backspace key definition, do the following:

Step 1 After logging in to the VDS server, press Ctrl-V followed by the Backspace or Delete key. The key sequence for the backspace is displayed. Typically, the key sequences are ^H or ^?. Step 2 Enter the key sequence exactly with the stty erase command; for example: stty erase ^H

Note The ^H or ^? are specifically Shift-6 and uppercase H or question mark.

Monitoring OS Load Runtime Syslog File

During the upgrade, when a VNC Listener is used, the stage 2 OS loading process can be monitored from the serial console window. View the /tmp/syslog file for details of the operations currently taking place. To view the syslog file use the tail –f /tmp/syslog command. After the stage 2 OS load has completed, the tail is killed and the server reboots.

Note The following messages in the syslog file are known benign messages: • <4>end_request: I/O error, dev fd0, sector 0 • <4>end_request: I/O error, dev fd0, sector 0 • <3>Buffer I/O error on device fd0, logical block 0

Error Messages

The following error messages may occur during the software upgrade:

***ERROR: Unable to copy to : cp: cannot stat … If this error is seen, it is most likely a result of a corrupted kit. During the initial extraction of the kit, the contents are checked to ensure integrity. Verify that the initial kit extraction did not have errors. Recovery procedure for this issue is provided in the “Warning Messages” section on page A-5.

***ERROR: Failed to delete partition /dev/sda# If this error is seen, it may be a result of an initial system configuration issue. See the“Warning Messages” section on page A-5 to attempt to correct this issue.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide A-2 Appendix A Troubleshooting Error Messages

***ERROR: /boot_cds is not mounted. Please manually mount it before running this upgrade script again. This could be an indication that the /boot_cds directory has been manually unmounted. Mount this partition before proceeding with the upgrade.

***ERROR: You have to be root to perform the remote ISO installation! You must be logged in as user root to run the upgrade or downgrade kit.

***ERROR: Hardware type is neither Merrimack nor Lindenhurst. You are attempting to run the upgrade or downgrade script on a nonsupported server.

***ERROR: Unable to create directory

This may be the result of a missing parent directory or failed hardware. Run the cds_upg_report.sh script and contact Cisco Support.

***ERROR: Unable to mount

on This may be the result of a missing file or directory, or hardware failure. Run the cds_upg_report.sh and contact Cisco Support.

***ERROR: Absolute path to ISO image not given. This indicates the ISO image file provided on the command line was not provided with the full path. Under normal operation this command line option is not needed. Rerun the command without providing the ISO option.

***ERROR: Unable to find ISO image This may be an indication that the kit was corrupted. Verify that no errors were provided during the initial extraction and rerun the self-extracting file.

***ERROR: is not a "ISO 9660 CD-ROM filesystem" format file This indicates the ISO image file provided on the command line is not the standard ISO image file required for the upgrade. Under normal operation this command line option is not needed. Rerun without providing the ISO option.

***ERROR: Unable to unmount This is an indication that a running process has a file open, or a shell is open currently in the mount point. Be sure there are no users running processes (for example, the vi editor) in the location that is identified as mount point.

***ERROR: VNC Listener : is not reachable. This is an indication that the VNC Listener cannot be reached. Verify system, vnc_ip, has a running VNC Listener and that the server to be upgraded can ping the VNC system (check that your management routes are correct).

***ERROR: Partition /dev/sda7 does not exist on /dev/sda On initial running of the script, this is an expected benign error.

***ERROR: Hard drive not detected on server. The server has a hardware failure. Verify that the server was operating correctly and all drives defined in the hardware guide are operational.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide A-3 Appendix A Troubleshooting Error Messages

***ERROR: unknown command line option An unknown or unsupported upgrade command line option was provided. Verify syntax of the command entered and rerun.

***ERROR: There is no default route on this server, cannot deduce the management interface. The upgrade script expects an operational server to perform the upgrade. In this situation a management default route should exist on the server. If a default route does not exist, log in to the CDSM GUI and verify one exists for this server (Server Setup page). If it does, re-submit and verify that a default route is configured on the server by running the netstat –rn command. If this is a newly shipped CDS server, manually configure the management interface configuration, enable the interface and manually put in a default route. For more information, see the “Upgrading the New CDEs with Release 4.4 VDS-TV Software” section on page 2-2.

***ERROR: ISO image SHA1 checksum does not match in iso.sha1sum. This means the upgrade or downgrade kit is corrupted. Redownload the kit and extract it again.

***ERROR: /arroyo/db is not mounted. This could be an indication that the /arroyo/db directory has been manually unmounted or the upgrade exited prematurely in a previous run. Reboot the server and verify that the /arroyo/db directory is mounted.

***ERROR: restore.list|backup.list does not exist. This indicates that the kit has been corrupted in transition to the destination server. Verify that the checksum provided the Cisco software download website is the same as the checksum as the file on the server. If the checksums match, reextract the kit and run the upgrade again.

***ERROR: scp failed. Please retry: A failure occurred during the transfer of the backup archive to the remote server. Check the IP address, username, password, and network connectivity to the remote server.

***ERROR: Cannot create archive .tgz. This indicates that the creation of the backup archive failed, most likely because of limited space in the /arroyo/db directory. The upgrade gives a best effort to calculate the amount of required space before the initial reboot, however if files have changed during the initial reboot this error may occur. Remove all non-essential files in the /, /home, and /arroyo/db directories and rerun the upgrade.

***ERROR: is XX % used, please clean up before running this upgrade script again. This means the partition does not have enough space for the upgrade to continue. Clean the partition space and rerun the upgrade.

***ERROR: There are two or more upgrade partitions on the system. If this error is encountered, it means there is more then one upgrade partition created. There can only be one upgrade partition, the second partition must be removed before proceeding.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide A-4 Appendix A Troubleshooting Warning Messages

Warning Messages

The following warning messages may occur during the software upgrade:

***WARNING: Cannot create backup archive The backup of the configuration, database, or log files has failed. Cleanup the file system space and rerun the upgrade.

***WARNING: Not enough space available to perform backup. The /arroyo/db directory does not have enough space to perform the backup. Remove all non-essential files and re-run the upgrade. All other errors that have not been commented on should be provided to Cisco Support along with the cds_upg_report.sh archive and the output of the Linux history command (run as root).

***WARNING: /dev/sda7 does not exist, it needs to be created from /dev/sda6. The /dev/sda6 partition has XXXXXXXXXXKB total disk space, which is more than the 8000000KB required to create new /dev/sda7 partition. This is an expected warning the first time the cds_remote_iso_install runs. No action is required.

“WARNING!!! VNC server running with NO PASSWORD! You can use the vncpassword= boot option if you would like to secure the server. This is an expected benign warning. No action required.

WARNING: No existing version found on this server. Cannot backup existing files. This warning is provided when running the vdsinit after the server has been upgraded. This is an expected warning and no action is required.

“No kdump initial ramdisk found.[WARNING]” … “Failed to run mkdumprd” This warning is provided when running the vdsinit after the upgrade and on first boot after vdsinit. The kdump configuration is resolved on the first reboot after the software installation. No action is required.

Failed or Stalled Upgrade

In rare instances there is a failed or stalled upgrade. For example, this could occur if power is not maintained during the upgrade. The backup performed before the upgrade was started can be used with the new server image procedure to install Release 4.4.

Note If power is lost during an upgrade there is no guarantee the upgrade will continue when power is restored.

A first attempt of just restoring power and booting the server should be performed. If this fails, then the server must be imaged directly to Release 4.4 and the configuration should be restored. To image the server directly and restore the configuration, do the following:

Step 1 Follow the instructions in the “Imaging a VDS Server with 64-Bit OS using a DVD” section on page 2-15.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide A-5 Appendix A Troubleshooting VNC Listener

If the server OS upgrade has not completed within 45 minutes or the upgrade is hung for a long time, then the upgrade has encountered an uncorrectable error. If the upgrade has stalled on the rpm kernel add portion and a VNC Listener was used, tail the /tmp/syslog file from the serial port console. If VNC Listener was not used, go to the video console and press Alt-F3 to switch to the virtual terminal. If the following error is seen: Code={SATA NCQ Fail All Commands After Error},

the loading of the kernel is failing on a disk drive. Look on the front of the server to see if one of the drives is slowly blinking. If the drive is slowly blinking, remove it. If another drive starts blinking, remove it as well. Continue removing drives until no drives are blinking. After this, the server should continue to proceed with the installation. Step 2 Run the vdsinit script. # cd /root # ./vdsinit-4.4.1 tv_repo-4.4.1-x86_64.iso

Step 3 Move the /etc/rc.d/upgrade.rc.local file to /etc/rc.d/rc.local. # mv –f /etc/rc.d/upgrade.rc.local /etc/rc.d/rc.local

VNC Listener

The VNC Listener is an application that waits to receive input from a remote host. When upgrading or downgrading the VDS-TV, the VNC Listener is used to remotely display the status of an upgrade, instead of the upgrade or downgrade output being sent to the video console. We recommend that the software upgrade be monitored from a VNC Listener. During the stage 2 boot process of the upgrade, a window is provided to the user to see the operations taking place on the server. Using the VNC Listener provides the additional ability to triage issues through the serial console if there is a failure during the upgrade.

Cisco VDS-TV Installation, Upgrade and Maintenance Guide A-6