[an error occurred while processing this directive]

Cisco Videoscape Distribution Suite for Internet Streaming

Release Notes for the Cisco TV CDS 1.5.4.6

 Feedback

Table Of Contents

Release Notes for Cisco TV CDS 1.5.4.6.1

Contents

New Features

System Requirements

Open Caveats

Resolved Caveats

Upgrade Procedure from Release 1.5.4.4 to Release 1.5.4.6.1

Introduction

Downloading the Software Upgrade

Loading the ISO Image from a CD-ROM

Running the Upgrade Scripts

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TV CDS 1.5.4.6.1


Revised: June 3, 2009 OL-19959-01

Contents

The following information is in the release notes:

New Features

System Requirements

Open Caveats

Resolved Caveats

Upgrade Procedure from Release 1.5.4.4 to Release 1.5.4.6.1

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request

New Features

Release 1.5.4.6.1 of the TV CDS introduces the following new features:

Application Specific Stream Segregation—Ability to segregate Playlist streaming traffic from Barker streaming traffic by using separate interfaces.

Application Specific Redundant Streaming—Ability for the applications (Playlist or Barker) to stream from one CDE of a paired-array of two CDEs (current implementation) or from both CDEs.

Manage Paired Standalone CDEs—Support for paired-array deployments of two CDEs that may not have connectivity between stream/cache interfaces.

Time of Day Playlist—Easily and quickly select an ingested video asset to create a looped content, with start and end times, in the Playlist.

Schedule Import/Export—Ability to import a Playout schedule that was created for one CDS to all other CDSs

Playout Scheduling GUI enhancements:

Channel Setup (name, IP address, port)

Playout Schedule workflow

Auto-complete when searching for content names

Exportable reports that contain Barker and Playlist activity information.

Playout Status API—Ability to have a global view of all Playout schedules and Barker streams across all CDSs by using an application program interface (API) for monitoring purposes.

Manual Ingest—Manual FTP import of content

System Requirements

The Cisco TV CDS Release 1.5.4.6.1 runs on the CDE200 hardware model. See the Cisco Content Delivery Engine CDE100/200/300/400 Hardware Installation Guide for set up and installation procedures.

Open Caveats

This release contains no open caveats.

Resolved Caveats

The following caveats have been resolved since Cisco TV CDS Release 1.5.4.4. Not all the resolved issues are mentioned here. The following list highlights the caveats associated with customer deployment scenarios.

CSCsq93505

When a timeslot spanning two days in Playout schedule is deleted, the next day's schedule becomes uncommitted.

CSCsl37838

Symptom:

Maximum trick mode speed is 127.

CSCsj05445

Symptom:

Stream monitor continues to display Playout streams after Streamer fails.

CSCsj21083

Symptom:

Disconnecting the cable from the ingest port does not always put ingests into failed state.

CSCsz17619

Symptom:

A filler content stops after playing once instead of repeating to fill the gap between two playout events. This gives a blank screen, until the next playout event starts.

CSCsz57148

The Monitor > System Level > Failed Ingest page does not load completely. When a failed ingest item is selected from the drop-down list, and Display is clicked, the page reloads with just the top menu items. The rest of the page is blank.

CSCsz62532

Streams containing private data on a PID (with type 192) in the PMT have the PMT replaced with one that does not reference the private data PID, which may additionally result in the private data PID not being sent to the STB (because it is stripped by a downstream device like a DCM or QAM).

Upgrade Procedure from Release 1.5.4.4 to Release 1.5.4.6.1

This section contains the following topics:

Introduction

Downloading the Software Upgrade

Loading the ISO Image from a CD-ROM

Running the Upgrade Scripts

Introduction

This document explains how to use the upgrade scripts to upgrade Single Streamer-Vault servers (SSVs) from Release 1.5.4.4 to Release 1.5.4.6.1. There are four scripts that you must run to complete the upgrade procedure:

1. preUpgrade

2. upgrade

3. postUpgradeSetup1

4. postUpgradeSetup2

Each script relies on processes that were completed in the previous script, so the scripts must be run in the correct order. If running a script generates error messages, fix as many of the errors as possible before running the next script.

Downloading the Software Upgrade

To download the ISO image software upgrade, do the following:


Step 1 Launch your web browser and enter the following URL:

http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=268438145

The Log In page is displayed.

Step 2 Log in to Cisco.com using your designated username and password. The Video and Content Delivery page is displayed, listing the available software products.

Step 3 Click Cisco Content Delivery Systems (CDS). The Downloads page is displayed.

Step 4 Click the Cisco Content Delivery Applications folder to expand it, and click the Cisco TV Streamer Application. The page refreshes and the software releases are displayed.

Step 5 Click the software release you want. The page refreshes and the software image files are displayed.

Step 6 Click the link for the software image file you want.

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.

The Download page is displayed with the information about the software image file and a Download link.

Step 7 Click Download. The Cisco End User Software License Agreement is displayed.

Step 8 Read the agreement and click Agree. The File Download dialog box is displayed.

Step 9 Click Save. The Save As dialog box is displayed.

Step 10 Navigate to the location where you want to save the file and click Save. The file downloads.


Copy the ISO image file to a CD-ROM for transporting the file to the SSV servers.

Loading the ISO Image from a CD-ROM

To load the ISO image onto the server, you can either mount the CD-ROM containing the ISO image file or mount the ISO image file directly as a loopback device.

If the CD-ROM is connected, the operating system mounts the CD-ROM as /mnt/cdrom. If the CD-ROM is not automatically mounted, enter the following command:

# mount /dev/cdrom

If you are copying the ISO image file directly to the server, you must copy the file to the /root directory. To mount the ISO image file directly as a loopback device, enter the following command:

# mount -o loop /root/ssv_1546.iso /mnt/cdrom

After the image file is mounted by using the CD-ROM or loopback, run the following command to install the upgrade scripts:

# ./install_1544upd_scripts.sh

This command copies all the scripts into the /root/upgrade_from_1544 directory.

Running the Upgrade Scripts

To upgrade the SSVs from Release 1.5.4.4 to Release 1.5.4.6.1, do the following for each SSV in the CDS:


Step 1 Log in to the SSV server as root and navigate to the /root/upgrade_from_1544 directory.

Step 2 Run the preUpgrade script.

sh preUpgrade

This script does the following:

Removes the service start scripts from rc.local file

Saves the original rc.local as rc.local_original

Shuts down the database

Reboots the server

You may see the following output when this script is running:

Removing start script from rc.local...
Done.
Shutting down the database...
Rebooting the server ...
Please run the script 'upgrade' when the server comes back up.

Broadcast message from root (pts/1) (Fri Jul 11 15:54:52 2008):

The system is going down for reboot NOW!

Step 3 Run the upgrade script.

sh upgrade

This script does the following:

Backs up the database and binary files. The files are copied into the /home/backup.1544 directory.

Mounts the ISO image and installs it.

Customizes the .arroyorc file.

Prompts for the IP address of a replication server that you must provide.

You may see the following output when this script is running:

Backing up DB and Binary files...
Done.
installing iso image...
Install SSV System CTRL-C NOW if this is not a SSV Box!
Fri Jul 11 16:01:18 PDT 2008
Done.
Modifying .arroyorc...

The follwing  will be displayed only if servers already configured in .arroyorc

The replication servers configured are :  
--------------------------------------- 
ssv     172.22.30.186
--------------------------------------- 
Do you want to add Replication Servers ? [Y/N]
Please enter the Replication Server IP : 
 Enter the replication server IP here
Done.
Please make the cabling changes now, if necessary. Then run the script postUpgradeSetup1.

Step 4 As it is stated in the last line of the upgrade script, please make any cabling changes necessary.

Step 5 In order to configure the output channels in Release 1.5.4.6.1, you need the IP address and associated ports of each QAM device. Make note of the IP address assigned in the QAM Gateway page, and any associated ports used in sending streams. The Output Channel page allows you to assign an output channel name for each unique QAM IP address and port.

Step 6 Run the postUpgradeSetup1 script.

sh postUpgradeSetup1

This script does the following:

Changes the access rights of /arroyo/log to 777

Starts the database

Checks if the database is started

Starts the web server

Runs the runonce script

Starts statsd

Prompts for the hostname, IP address, and subnet mask of the server

Runs the svrinit_15 script

You may see the following output when this script is running:

starting database
 3244 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3246 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3247 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3248 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3249 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3250 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3251 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3252 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3253 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3254 pts/1    S      0:00 /home/isa/Berkeley/avsdb
 3261 pts/1    S      0:00 grep avsdb
[Fri Jul 11 16:03:53 2008] [alert] httpd: Could not determine the server's fully qualified 
domain name, using 172.22.99.187 for ServerName
Starting web server...
/arroyo/www/bin/apachectl start: httpd started
Running runonce utility...
Initial values inserted successfully
device is: eth0
Please enter the local server host name : 
rack187      	fl Enter the local server host name here
Please enter the local server IP : 
172.22.99.187 	fl Enter the local Server IP here
Please enter the local server Subnet Mask : 
255.255.254.0 	fl Enter the Subnet mask Here
172.22.99.187 ASM tables initalized!
Please do the initial configurations from the GUI and run postUpgradeSetup2.

Step 7 As stated in the last line of the postUpgradeSetup1 script, some of the Release 1.5.4.6.1 features affect network connectivity and require configuration using the CDSM. The new features introduced in Release 1.5.4.6.1 that require configuration are the following:

Transport Groups

Interface Setup

Server Setup

Route Tables

Ingest Tuning

Application Configuration active-active or active-standby mode

For more information about configuring these features, see the Cisco TV CDS Software Configuration Guide that is available through the CDSM under Maintenance > Manual page.

Additionally, the Media Scheduler option must be set to "Off" in the CDSM Setup page by logging in to the CDSM as user arroyo password arr0y021 with the engineering access level.

Step 8 Run the postUpgradeSetup2 script.

sh postUpgradeSetup2

This script does the following:

Shuts down the database

Stops statsd

Upgrades the database

Changes the access rights of /arroyo/log to 777

You may see the following output when this script is running:

shutting down database....
Done.
stopping statsd...
Done.
Upgrading  database ...
Database is running.
DB->Cursor: Successful return: 0
send: Transport endpoint is not connected
no reply: Bad file descriptor
send: Transport endpoint is not connected
no reply: Bad file descriptor
Done.
Scripts executed successfully. Please follow these steps below :
1. Copy the data base files to the other server.
2. Uncomment the service start commands in /etc/rc.local 
3. Reboot the servers.


Once you have completed running all the scripts, you must do the following steps manually:


Step 1 Copy the database files to the other SSV servers, if required.

a. Log in as isa on the other SSV and delete the database.

	cd /arroyo/db
	rm -rf DATADIR

b. Log in as isa on the SSV that has the upgraded database and run the following command:

	cd /arroyo/db 
	scp -pr DATADIR isa@<CDS02>:/arroyo/db/ 

Step 2 Edit the /etc/rc.local file by removing the comment marks from the lines that start the Apache web server and avsdb on boot.

[isa@cdsm isa]# vi /etc/rc.local
#!/bin/sh
#
# This script will be executed *after* all the other init scripts.
# You can put your own initialization stuff in here if you don't
# want to do the full Sys V style init stuff.

export LD_ASSUME_KERNEL=2.4.19

touch /var/lock/subsys/local

# ISA Kernel Tune
echo 222217728 > /proc/sys/kernel/shmmax
echo 222217728 > /proc/sys/kernel/shmall
echo 65535 > /proc/sys/fs/file-max

# TCP Kernel Tune
echo 8388608 > /proc/sys/net/core/wmem_max
echo 8388608 > /proc/sys/net/core/rmem_max
echo "4096    65536   4194304" > /proc/sys/net/ipv4/tcp_wmem
echo "4096    87380   4194304" > /proc/sys/net/ipv4/tcp_rmem
echo 0 > /proc/sys/net/ipv4/tcp_sack

/arroyo/test/ssv/run

#The following command will start the database for statsd.
su - isa -c "sleep 10"
/home/stats/statsd -f 2 -d eth0
sleep 5
rm -f /arroyo/www/logs/httpd.pid
/arroyo/www/bin/apachectl start

su - isa -c "sleep 10;cd /home/isa/IntegrationTest; ./run_isa >>& 
/home/isa/IntegrationTest/ns_log&" 
sleep 5

Step 3 Reboot the servers.


All servers should be up and running when you complete the procedures outlined in this document.

Documentation Updates

The following documents have been updated for this release:

Cisco TV CDS Software Configuration Guide

Cisco TV CDS Playout and Barker Applications Data Input Quick Start Guide

Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide

Regulatory Compliance and Safety Information for Cisco Content Delivery Engine 100/200/300/400

The following documents have been added for this release:

Release Notes for Cisco TV CDS 1.5.4.6.1

Cisco TV CDS C Content Detail Retrieval API

Related Documentation

Refer to the following documents for additional information about the Cisco Internet Streamer CDS 2.0-2.2:

Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide

http://www.cisco.com/en/US/docs/video/cds/cde/installation/guide/CDE_Install_Book.html

Regulatory Compliance and Safety Information for Cisco Content Delivery Engine 100/200/300/400

http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html

Cisco TV CDS Software Configuration Guide

Available through the CDSM GUI.

Cisco TV CDS C Content Detail Retrieval API

Available through the CDSM GUI.

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.


[an error occurred while processing this directive]