Guest

Cisco Videoscape Distribution Suite for Television

Release Notes for Cisco TV CDS 3.2.1

  • Viewing Options

  • PDF (253.3 KB)
  • Feedback
Release Notes for Cisco TV CDS 3.2.1

Table Of Contents

Release Notes for Cisco TV CDS 3.2.1

Contents

New Features

All Environments

New Hardware Platforms

Support H.264

Remote Software Upgrade

Vault Decommissioning

System Level Configuration Backup and Restore

Web Services APIs for Server-Level and System-Level Configuration Settings

ISA Environments

TV On Demand

ATIS C2 Support

RTSP Environments

FSI Resiliency for Media Scheduler and Ingest Steering

Catch-Up-to-Live Announce, Status, and Return to Normal Play

Supported Environments

System Requirements

Limitations and Restrictions

Open Caveats

CServer

FSI

RTSP

Statsd

Monitoring

CDSM

Configuration:

Resolved Caveats

Scripts

Statsd

CServer

FSI

Syslog

ISA

AVSlauncher

Interoperability

RTSP

Configuration

Installation

Database

Upgrading to Release 3.2.1

Upgrading to Cisco TV CDS Release 3.2.1

Downgrading from Release 3.2.1

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TV CDS 3.2.1


These release notes cover Cisco TV CDS Release 3.2.1.

Revised: October 2012 OL-28208-01

Contents

The following information is in the release notes:

New Features

Supported Environments

System Requirements

Open Caveats

Resolved Caveats

Upgrading to Release 3.2.1

Related Documentation

Obtaining Documentation and Submitting a Service Request

New Features

The following new features introduced in Release 3.2.1 are grouped as follows:

All Environments

ISA Environments

RTSP Environments

All Environments

The following features are supported for all environments:

New Hardware Platforms

Support H.264

Remote Software Upgrade

Vault Decommissioning

System Level Configuration Backup and Restore

Web Services APIs for Server-Level and System-Level Configuration Settings

New Hardware Platforms

Release 3.2.1 supports the following new CDEs for the TV CDS Streamer:

CDE250-2S8

CDE250-2S9

CDE250-2S10

For more information, see the Cisco Content Delivery Engine 205/220/250/420/460 Hardware Installation Guide.

Support H.264

Release 3.2.1 supports H.264 (also known as MPEG-4 Part 10 or Advanced Video CODEC [AVC]) ingests, trick-mode file generation, and streaming. Dynamic trick modes are supported for the RTSP NGOD nDVR feature.

Remote Software Upgrade

Release 3.2.1 introduces the ability to upgrade the CDS servers (Vault, Caching Node, and Streamer) remotely through the CDSM GUI. Before upgrading any of the CDS servers, first upgrade the CDSM/VVIM. If your system has redundant CDSMs/VVIMs, upgrade the secondary CDSM/VVIM followed by the primary CDSM/VVIM.

Manually upgrading each CDS server is still supported. Both the manual upgrade and the remote upgrade cover general upgrade procedures. Any deviations from the general upgrade procedures for a specific TV CDS software release are described in the Release Notes for that release.

The Software Upgrade page offers the option to upgrade all CDS servers in the system, CDS servers in a specific group (Stream Group, Vault Group, or Cache Group), or a specific CDS server in a specific group.

Remote Software Upgrade Workflow

The Remote Software Upgrade feature performs the following tasks:

1. Sends parameters set in the CDSM GUI or through the Web Services API to the CDS server.

2. Logs in to the CDS server using the credentials specified in the parameter settings and copies the new cdsinstall script, the .bin image file, and the required libraries.

3. Runs the new cdsinstall script on the CDS server, which performs the following tasks:

a. Copies ISO image file from specified location. If the file is already present, this step is skipped.

b. Backs up the essential configuration files

/etc/hosts

/etc/rc.local

/etc/sysconfig/network

/etc/sysconfig/network-scripts/ifcfg-eth()

/home/isa/.arroyorc

Output of the ifconfig -a command to a new file (/root/ifconfig_<system_date>


Note A backup of the /arroyo/db/DATADIR and /arroyo/test is not performed.


c. Performs the pre-upgrade checks.

d. Backs up existing software image.

e. Performs the upgrade process.

4. Sends the upgrade status to statsd by writing into the /tmp/.upgrade_status file.

After upgrading the software on the CDS server, restart the server by logging in to the Linux operating system on the server as user root and enter the reboot command. After the CDS server has rebooted, set the server to online (Maintain > Servers > Server Offload).

Configuring the Software Upgrade Settings on the CDSM GUI

Before upgrading the software, perform the following tasks:

1. Download the Cisco TV CDS software file and copy it to the server that will be accessed during the upgrade (this could be "Local Image," which is the CDS server that is being upgraded).

For information on getting the Cisco TV CDS software file, see the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

2. Offload each CDS server you want to upgrade (Maintain > Servers > Server Offload).

For more information, see the "System Maintenance' chapter in the Cisco TV CDS 3.2 ISA Software Configuration Guide or the Cisco TV CDS 3.2 RTSP Software Configuration Guide.

Software Upgrade using the Web Service API

The same remote software upgrade capabilities provided by the CDSM GUI are also provided by a Web Service API. The following upgrade.xsd XML schema can be used to create an upgrade XML file that is uploaded to the CDSM.

For more information, see the "Remote Software Upgrade and Configuration" chapter in the Cisco TV CDS 3.2 API Guide.

Vault Decommissioning

Release 3.2.1 offers the ability to gracefully decommission a Vault from the system by using the CDSM GUI. Content on the Vault is moved to other Vaults during the decommission process so that no content is lost.

The process of decommissioning a Vault requires that the Vault be first put into Offline (No Ingest & Fill) mode. After the Vault is offline the option to decommission is listed in the Server Offload page.

After the decommission is complete, the Vault is isolated from the CDS. If the Vault is rebooted, it has the state of "Offline (No Ingest & Fill). The Vault entries in the database and .arroyorc remain intact. To remove the Vault entries from the database and .arroyorc file, the avsdb and statsd processes must be restarted, which impacts the serviceability of the system. Removal of a Vault from the database and .arroyorc file should be performed during a maintenance window.

For more information, see the "System Maintenance" chapter in the Cisco TV CDS 3.2 ISA Software Configuration Guide or the Cisco TV CDS 3.2 RTSP Software Configuration Guide.

System Level Configuration Backup and Restore

The System-Level Configuration Backup and Restore feature builds on the Server-Level Configuration Backup and Restore feature introduced in Release 3.0.1. All system-level configuration pages are supported, except Error Repair, Billing Service, and Shared Recorder Setting.

Through the System-Level Configuration Backup and Restore feature on the CDSM GUI, it is possible to backup (export) the system-level configuration for all CDS servers in a system, modify the parameters as appropriate, and restore (import) the configuration to all CDS servers in the existing system or all CDS servers in a new system.

In addition to complete backup and restore functionality for all system-level configurations for the specified CDS servers, this feature also offers export and import on each system-level configuration page for all CDS servers managed by the CDSM (or VVIM).


Note The restore and import function does not overwrite the following pre-existing system-level configuration settings:

System DNS

System NTP

Host Service

QAM Gateway

Stream Destination

Parent/Child Service Groups

Input Channels

Output Channels

Source Output Port

All other supported pre-existing system-level configuration settings are overwritten.


Using the System-Level Configuration Backup and Restore Feature

Using the Backup and Restore feature involves the following tasks:

Enabling the Backup and Restore Feature

Backup or Restore System-Level Settings

Export or Import Specific System-Level Configurations

Enabling the Backup and Restore Feature

The Backup & Restore page (Maintain > Software > Backup & Restore) and the Import/Export System Configuration option on the System Level configuration pages (Configure > System Level) are displayed when the Bulk Import/Export Configuration is enabled.

To enable the Bulk Import/Export Configuration feature, log in to the CDSM GUI as a user with Engineering access level, and on the CDSM Setup page in the Bulk Import/Export Configuration section click the Enabled radio button and click Submit.

Backup or Restore System-Level Settings

The Backup & Restore page offers the following capabilities:

Backup all the system-level configuration parameters for the CDS

Backup the server-level configuration parameters of specific CDS servers

After the backup has been performed, the configuration parameters can be modified as appropriate and restored to all the system-level configuration parameters in the existing or new system or all the server-level configuration parameters to the existing or new CDS servers.

After the backup XML configuration file has been created, you can edit the values of the configuration parameters as appropriate.

Export or Import Specific System-Level Configurations

The Import/Export System Configuration option offers the ability to export or import the specific system-level configuration for all the CDS servers. After the export XML configuration file has been created, you can edit the values of the configuration parameters as appropriate for the existing CDS or a new CDS.

For more information and to see a copy of the System-Level Configuration XML schema, see the Cisco TV CDS 3.2 ISA Software Configuration Guide or the Cisco TV CDS 3.2 RTSP Software Configuration Guide.

Web Services APIs for Server-Level and System-Level Configuration Settings

In addition to the CDSM GUI Backup and Restore feature, Release 3.2.1 offers the ability to send an XML file created by the Export or Backup feature by way of an API call using the curl utility. The XML file that is created by the Export or Backup feature can be modified as appropriate for the system or CDS servers.

The same server-level and system-level configuration settings supported in the Backup and Restore feature are supported for the web services API.

For more information, see the "Remote Software Upgrade and Configuration" chapter in the Cisco TV CDS 3.2 API Guide.

ISA Environments

The following features are supported for ISA environments:

TV On Demand

ATIS C2 Support

TV On Demand

The TV On Demand (TVOD) feature enables broadcast recording of live content for a Virtual Video Infrastructure (VVI) system in an ISA environment CDS and interacting with the Ericsson OpenStream backoffice.

The Ericsson Recording Control System (RCS) located at the super headend (SHE) is used to schedule recordings on different channels. Each channel is assigned a call sign ID and is marked as a central channel or a local channel. Central channels are handled by the central Vault and local channels are handled by the local Vaults located at each video hub office (VHO).


Note In Release 3.2.1, only local Vaults are supported in a legacy CDS system configuration. A VVI system configuration is not supported for TVOD.


The Ericsson Recording Manager (RM) located at each VHO, gets the recording schedule from the RCS and sends it to the TVOD server process on the Vault.

The TVOD server processes the schedule recording requests from the RM by sending the request to the Content Store to start the recording and sending status updates (recording started, recording ended) of each recording to the RM. The TVOD server acts as the C5++ interface (an extension of the ATIS-IIF C5 specification) for real-time captures. In the C5++ interface, content is acquired by capturing a linear multicast stream.

Enabling and Configuring TVOD

To enable the TVOD feature, log in to the CDSM GUI as a user with engineering access level, the CDSM Setup page is displayed. In the TVOD Setup section, click Enabled for TVOD Setup. To start the TVOD server on each Vault, the Vaults must be rebooted.

To ensure the TVOD server is running, log in to the Vault as user isa, go to the /home/isa/IntegrationTest directory, and run the ./show_calypso_services script. The TVOD Manager should be listed as running.

When the TVOD Setup is enabled, the CallSign Setup page (Configure > System Level > Callsign Setup) is displayed. The Callsign Setup page is used to configure the call signs of the program channels.

For more information, see the "Configuring the CDS" chapter in the Cisco TV CDS 3.2 ISA Software Configuration Guide or the Cisco TV CDS 3.2 RTSP Software Configuration Guide.

ATIS C2 Support

The CDS Streamers support Alliance for Telecommunications Industry Solutions (ATIS) C2 interface for cache-fill of content from the Cisco VDS Origin Server (VDS-OS) and third-party CDNs. If the content requested during a session setup is based on a CDN HTTP URI, the content is not ingested by the CDS Vaults but is instead pulled directly by the Streamers. CDS Streamers directly contact the VOD library of the third-party CDN or Cisco VDS-OS by using the ATIS C2 protocol.

Long-tail content (content that is not requested often) can be stored in the third-party CDN and provisioned on demand and pulled on demand by the CDS Streamers from the CDN. Short-tail content (content that is requested often) continues to be provisioned, ingested, and streamed normally for a Cisco ISA CDS or VVI.


Note If the HTTP URI has a domain name instead of an IP address, static mapping between domain names and IP addresses is required in the CDS. Static mapping of domain names and IP addresses can be configured in the /etc/hosts file or through the CDSM GUI Configure > System Level > Host Service page. Depending on when this configuration is added, it may be necessary to force the CServer to get this change by entering the echo 1 > /proc/calypso/tunables/read_etc_hosts command on each Streamer.


Long-tail content (ATIS C2 content) from third-party CDNs or Cisco VDS-OS has the file size listed in green on the Completed Ingests page (Monitor > System Level > Completed Ingests). The information listed on the Completed Ingests page consists of information received from the ATIS MediaResourceSet. ATIS content cannot be deleted through the CDSM GUI.


Note The ATIS C2 support does not include support for Digital Video Watermarking, dynamic trick modes, and live content.


ATIS Media Resource Requirements

Each media resource in an ATIS environment has a MediaResourceSet consisting of the following:

Base media file, also called the 1X file

Media Resource Metadata (MRM) file in XML format, which has information about the presence and location (URI) of trick-mode files and index files

Index file (ATIS standard index file), which has information about the 1X file and associated trick-mode file

Streamer Workflow for ATIS C2 HTTP

On the Streamer designated as the Setup server, the following occurs in initiating a session:

1. The Streamer sends a GET request for the URI (1X file URI) to the VDS-OS or third-party CDN.

2. The MetadataFile URL is retrieved from the link header in the response from the VDS-OS or third-party CDN.

3. The Streamer sends a GET request for the asset metadata file.

4. The Streamer receives the asset metadata file from the VDS-OS or third-party CDN and gets information about the trick-mode files and IndexFile. If more metadata is required from the IndexFile, the Streamer fetches the index file from the CDN and parses it as necessary.

The Streamer designated as the Control server chooses a Streamer to act as the Play server for the request. On the Streamer acting as the Play server, the following occurs:

1. Send a GET request for the IndexFile and parse it to get the information required to stream the 1X file and trick-mode files.

2. Send a GET request for the 1X file to the VDS-OS or third-party CDN and stream it to the set-top box (STB).

If the Control server sends a request for a trick-mode file and the MediaResourceSet has pre-generated trick-mode files, the Play server gets the byte range associated with the requested play time (the index information is used to find the mapping) and plays the stream.

RTSP Environments

The following features are supported for RTSP environments:

FSI Resiliency for Media Scheduler and Ingest Steering

Catch-Up-to-Live Announce, Status, and Return to Normal Play

FSI Resiliency for Media Scheduler and Ingest Steering

FSI resiliency is supported for Media Scheduler and Ingest Steering. For Media Scheduler, the backup recording server is selected across the Vault Groups by the Master Vault. For Ingest Steering, the Master Vault selects the backup recording server from the same Vault Group as the primary recording server. If there is no available server, other than the primary recording server, then no backup recording is performed.

Catch-Up-to-Live Announce, Status, and Return to Normal Play

For U.S. RTSP NGOD environments, to support catch-up-to-live, a new ANNOUNCE code (2107) is sent by way of the R2 interface to the ODRM to indicate the catch-up-to-current ingest has been reached. At the same time, the Streamer sends an LSC Done with status code 0x06 to signal that the catch-up-to-current ingest has been reached. The Streamer also converts any trick-mode action to normal play just behind the current or live ingest.

To enable this feature, do the following:


Step 1 Log in to the Linux operating system of the Streamer and edit the arroyo script in the /home/isa/bss/scripts/ directory by replacing cuTL STD with cuTL DROP1X.

Step 2 Log in to the CDSM GUI.

Step 3 Choose Configure > Server Level > Server Setup. The Server Setup page is displayed.

Step 4 From the Server IP drop-down list, select the IP address of the Streamer and click Display. The Streamer Server Setup fields are displayed.

Step 5 For Live Playback, click Enabled.

Step 6 Click Submit to save the settings.

Step 7 Repeat this procedure for each Streamer.


Supported Environments

Release 3.2.1 of the Cisco TV CDS supports both the ISA and RTSP environments. Some RTSP environment features are only applicable to certain RTSP Deployment Types.

System Requirements

The Cisco TV CDS Release 3.2.1 runs on the CDE110, CDE220, CDE250, and CDE420. See the Cisco Content Delivery Engine110 Hardware Installation Guide, and the Cisco Content Delivery Engine 205/220/250/420/460 Hardware Installation Guide.

The Cisco TV CDS Release 3.2.1 does not run on the CDE100, CDE200, CDE300, and CDE400 hardware models.


Note If you are using Internet Explorer 8 to access the CDSM GUI, for the online help to display correctly, you need to turn on Compatibility View. To turn on Compatibility View in Internet Explorer 8, choose Tools > Compatibility View.


Limitations and Restrictions

This release contains the following limitations and restrictions:

RTSP Redirect Server Limitations—The TV CDS Redirect Server provides a central entry-point for stream requests, which are then redirected based on internal load balancing policies to other Setup servers in the CDS deployment for session processing. The load balancing policies require that the CDS server running the Redirect Server have access to the database of each potential Setup server. The policies use key pieces of information from the database, such as the RTSP server status, the server load, and the Setup IP address to management IP address mappings. If the Redirect Server does not have access to this data, it cannot properly redirect the setup request to the "best" Setup server.

In the case of multiple Stream Groups, with the Redirect Server configured to run on Streamers within one of the Stream Groups, it is required that the database replication partners for the Streamers contain all of the Streamers from all Stream Groups, which basically constitutes a full-mesh database replication approach among all of the Streamers

If a full-mesh database replication for the Streamers is not desired, the Redirect Server can operate on the Vaults, which already have the necessary database replication partners defined to support required data.

Open Caveats

This release contains the following open caveats:

CServer

CSCud36413

Symptom:

With the recently added "Catch up to the Live point" behaivor(As part of Rosetta) in place, almost 2 to 5 seconds delay is observed during the transition from FF to 1x play, when the play reaches the live point.

Conditions:

When the Live ingest is going on, when there is a stream in FF mode, upon reaching the Live point, the delay is observed.

Workaround:

No Workaround at this point of time.

CSCud35620

Symptom:

Server goes to KDB in ASSERT failure.

Conditions:

DEBUG version of image running. ATIS streaming is done.

Workaround:

None.

CSCud09769

Symptom:

In Sreamer Failover system, each primary and backup Streamer handling some plays session. When primary Streamer is rebooted, some of play sessions from this rebooting server coming as "play complete" in backup Streamer

Conditions:

In primary and backup Streamer failover setup, each server handling some play sessions and one of the server is rebooted

Workaround:

None.

CSCud02724

Symptom:

Play doesnot continue from last pause npt in the session after jump command with NPT range ended. Rather it starts from NPT 0.

Conditions:

1) Jump was given to play a particular NPT range [ If STB has this facility to give Range for a jump ]

2) Play completed for the duration of time given in NPT range and in pause state.

3) New play command is given after 10-15 seconds .

Workaround:

Play has to be given immediately with in 10 seconds after a JUMP play command has been issued with a NPT range and completed. This is typically done by STB and should not be seen normall.

CSCuc65382

Symptom:

In 2.5.6, on RTSP master, the rtsp.log file grows so large and cause the system no space for archive other logs.

Conditions:

2.5.6 and rtsp master logging level set to high

Workaround:

Change the rtsp logging level to low.

FSI

CSCtt46144

Symptom:

For a duplicated live future request, the state field in response XML body is empty instead of having the correct state of the scheduled live recording.

Conditions:

The client sends a request to schedule a live content with the same assetID, providerID, captureStart and captureEnd as an already scheduled future recording on the same channel.

Workaround:

None.

RTSP

CSCud14149

Symptom:

Teardown request is not generated after a timeout of session has happened.

Conditions:

In VOO Model, after a session expired , RTSP has to generate a announce message send to SRM , SRM will generate a Teardown request based on that.

Workaround:

No workaround.

CSCtw91475

Symptom:

RTSP Session contents are not deleted properly in AVSDB.

Conditions:

When content streaming is very high, the database transmits and the transmits in the Thread Pools are high, which results in updates to the database in a mixed asynchronous and synchronous manner. This results in the orphans sessions in the database.

Workaround:

On all Streamers in that Stream Group and the associated CDSM, log in as user root, stop avsdb, and remove rtsp databases by enter the following commands:

/usr/bin/db_shutdown
rm rtsp_session.db rtsp_annex.db
 
   

Start avsdb on Streamers in that Stream Group and the associated CDSM.

su - isa
arroyo start avsdb
 
   

Statsd

CSCtw73571

Symptom:

SDT prints unexpected low thresholds values for one of the power supplies.

Conditions:

The conditions are not apparent to the end-user, but arise from a hardware defect or failure in the power supply unit.

The root cause is an empty FRU in the errant power supply. This causes the temperature high limit to default to 0 degree C. It is currently uncertain whether the FRU was not written at the production time, or it was erased during customer usage. Either way, this is a hardware issue, and not an SDT software defect.

Workaround:

There are currently no workarounds. Any defective PSU will have to be RMA'd for fault analysis and/or replaced by a healthy one.

Monitoring

CSCua60678

Symptom:

VVIM GUI does not display Content Data information on System Snapshot. The browser may also report an error in the webpage rendering as well, due to a zend error being generated.

Conditions:

There are greater than 256 unique server id records in the SERVERMAP_15 table.

Workaround:

Cull the entries in the SERVERMAP_15 table to have at most 256 unique server ids if possible. If there are old/unneeded entries, they can be removed.

CDSM

CSCud38536

Symptom:

Web Service API for System Level Import Feature does not allow to import stream destination configurations.

Conditions:

CDSM Setup configured as RTSP-NGOD deployment and the Stream Destination Type as IPTV / Mixed.

Workaround:

Import the Stream Destination configurations through GUI.

Configuration:

CSCud38536

Symptom:

Web Service API for System Software Upgrade feature, Transfer Mode with Local Image Option is not working.

Conditions:

Place CDS build ISO image on Local Server and request Software Upgrade Process using Webservice API with transfer mode as Local Image.

Workaround:

User can use GUI to perform System software Upgrade for Local Image Option.

Resolved Caveats

This section contains he resolved caveats in Cisco TV CDS Release 3.2.1. Not all resolved issues are mentioned here. The following list highlights resolved caveats associated with customer deployment scenarios.

Scripts

CSCuc69041

Symptom:

Run_isa_boot line is not in rc.local file of Vault.

Conditions:

Script modified to support run_isa_boot in Vault.

CSCtx23643

Symptom:

Log files are not archived. The /arroyo/log/archive directory is empty. The files are deleted from /arroyo/log directory also.

Conditions:

If there is a large file that takes more than 50% of the /arroyo/log/archive folder, then the trim_archive script will delete the files starting from oldest to newest to create space. If the newest file is so large that it takes major space of the /arroyo/log, it will result in deletion of all files in the folder.

Statsd

CSCua10700

Symptom:

In DCS setup with no Caching Nodes and local Vaults, Streamer RemoteServers file contains both local and regional Vaults. However, local and regional Vault files do not contain Streamers.

Conditions:

In DCS setup with no Caching Nodes and local Vaults,

CServer

CSCud09793

Symptom:

When multiple restrictions are requested per content, no trciks are restricted to that content

Conditions:

The issue is observed during streaming only when multiple restrictions are issued on a single content

CSCud08082

Symptom:

When tricks are issued on the same restricted trick stream itself, PLAY_REPLY is returned as LSC_OK instead of LSC_NO_PERMISSION.

Conditions:

The issue is observed only when RTSPTrickRestrictionEnabled = 0.

CSCuc70497

Symptom:

QAM leading to an extended period of black being played out at splice point.

Conditions:

PCR packets are missing in the splice sequence, which leads QAM to black-out.

CSCud06222

Symptom:

Backup primary/control streamer crashes in SC::Stream::continueUpdateStreamData() or SC::StreamControlLocal::nptToIdx() after processing a bad playlist entry where the start time exceeds the end time.

Conditions:

Backup office sends playlist to RTSP containing an entry where the start time exceeds the real end time. The bad playlist entry has a non-zero start time and end time of EOS (0x7FFFFFFF). The EOS stamp is converted by CServer to a real end time which is determined by content's size and the bit rate. Both the ingest logs and AVSDB report the correct content size. The backup setup/control streamer crashes shortly after the adjusted playlist for a stream has been synced to it.

CSCuc60801

Symptom:

Rogue HTTP traffic on Cache Fill interface causes kernel crash.

Conditions:

When the system is not configured for the C2 protocol and HTTP requests are sent to the streamer, the streamer sometimes crashes.

CSCuc51089

Symptom:

The stream plays at live point for start over session in some circumstances. The start over sessions never catches up live because fast-forward is not allowed (disabled).

Conditions:

Initiate a start-over sessions and rewind it till beginning and then play again which causes session is jumping to live point.

CSCuc30278

Symptom:

RTSP server sends "End-Of-Stream" when trying to play a Live recorded content.

Conditions:

When user issues a SETUP and TEARDOWN during Live recording, and then issues another SETUP followed by PLAY after the Live recording gets over.

CSCuc29054

Symptom:

Play streamer is reporting INSUFFICIENTRESOURCES back to the control streamer as soon as the stream is started. The control streamer assigns the stream back to the same streamer, and the problem repeats, until the stream is destroyed.

Conditions:

Play streamer is playing at its egress capacity. It reports it has capacity back to the control primary which assigns it new streams. The streamer cannot start the stream and reports INSUFFICIENTRESOURCES to the control server. The control streamer re-costs the stream to reassign it, the same streamer still reports that it has streaming capacity and the stream is assigned back to the same streamer, and the problem repeats until the stream is destroyed by the back office.

CSCuc03388

Symptom:

CServer crashes in IOX::ControlSlot::transmitDone(). The kernel dmesg log reports "AND_clean_tx_irq: corrupted tx_ring."

Conditions:

CDSTV 2.5.6. In version 2.5.6, driver sharing between CServer and Linux was enabled. We suspect that the interaction between CServer and Linux is corrupting the driver's transmit ring.

CSCub29293

Symptom:

Invalid GET message to CGW causes Vault sends incorrect GOID to downstream servers

Conditions:

Example of invalid GET:

GET /nCircle.ip360 HTTP/1.0

CSCua51956

Symptom:

Backup server crashes while becoming primary. The trace event log shows an infinite loop while trying to handle a stream that had been assigned to play on the backup streamer and is in the playing state. However, the stream play no longer exists for the stream and the backup server gets into an infinite loop trying to cancel a non-existent play stream.

Conditions:

The conditions that caused this are not yet fully understood; there was not enough history in the trace event log for this stream. The backup control is out of sync with the primary control streamer.

CSCua65579

Symptom:

Remote Mirroring or Array Mirroring are slow, yet plenty of BW is available.

Conditions:

This issue is seen where there are only a few vaults in a system. The problem is that the communications from one vault to another has a connection table that is limiting the number of concurrent connections (per destination - which is why this is seen only on a system with just a few vaults). The result is that even though there is plenty of BW available; due to the connection limit communications are artificially throttled.

FSI

CSCub00772

Symptom:

Content is not deleted from the vault when a delete request is given.

Conditions:

A delete request must be given as soon as the cserver content capture of primary recording is complete and before the FSI has performed

CSCuc05875

Symptom:

AIM crashes when merging old and new content after ingest.

Conditions:

Old content needs to be in the database.

CSCua67514

Symptom:

FSI response message does not contain Volume Name for a completed live content ingestion.Backoffice returns error for such FSI response messages.

Conditions:

When Ingest steering is enabled and primary recording fails, back_up recording became success (content swap), this issue will be seen

Syslog

CSCua85547

Symptom:

The /arroyo/log/archive directory is not available.

Conditions:

If Install build version greater than 2.5.2, then /arroyo/log/archive directory not available.

ISA

CSCuc91212

Symptom:

The logging level is really default but the system drive is replaced with SD to size is limited to 64G for all partitions. So the /arroyo/log partition is getting filled much quicker.

Conditions:

The hard drive is replaced by solid state drive. There are lscp status (hear beat) messages for each sessions reported 2 per minute so it is getting more than 200 requests reported in a second causing to

log created 100-200M per hr.

CSCuc09525

Symptom:

The script "sync_with_bms_and_clean_orphaned_contents" did not update the content records with

serverId = 999999.

Conditions:

This script has to be run once only if enable DCS/VCS feature on a VHO.

CSCua99552

Symptom:

Content which was successfully ingested or cloned to regional vaults gets deleted if it does not have any market reference and a market sends a provision request for it.

Conditions:

A content exists on the regional vaults but have no market reference and a provision request is received for it from the market.

AVSlauncher

CSCub82806

Symptom:

In DCS/SCS setup, when a Control/Setup IP with a non-default (i.e. not "255.255.255.0") subnet mask is configured, avslauncher still uses the default subnet mask when launching commands for that IP.

Conditions:

DCS/SCS setup, where CONTROLIPMAP record is stored with a VHOID, e.g. CONTROLIPMAP:2002, and a non-default mask is configured.

Interoperability

CSCuc18028

Symptom:

The script "run_resource_manager" starts ResourceManager that reaps the orphan streams. This script feeds the list of session gateways to ResourceManager by generating SessionGateways.lst file. In the VCS configuration the file SessionGateways.lst does not have appropriate names of the session gateways so causing none of the session gateway gets resolved by resource manager.

Conditions:

If we enable DCS/VCS feature on a VHO.

RTSP

CSCuc73721

Symptom:

The RTSP application is leaking memory causing excessive growth of virtual memory and data sections. Given enough traffic, the application can run out of process space causing unexpected system exceptions. This can result in the loss of application threads and subsequent hangs, or even application core dumps.

Conditions:

This will be seen when more no. of requests have been sent to RTSP application.

Configuration

CSCuc97726

Symptom:

When a Vault Group entry is cleared, preference is set to 'None' in the Cache To Vault Map page, it is not being removed in the RemoteServers file.

Conditions:

NGOD Deployment type.

Installation

CSCuc63641

Symptom:

During the product update processes the firmware on the internal SSDs may be updated. If the firmware update is performed then only the first of two SSDs will have its firmware updated. The firmware update process will report an error and stop despite the first SSD's firmware being successfully updated.

Conditions:

This firmware update failure occurs only when updating to 2.5.6 from a version prior to 2.5.6.

CSCuc94112

Symptom:

Limited storage capacity for /arroyo/log partition restrict system log history to a few days. /arroyo/log capacity was increased by reducing the /home partition that had much more capacity than was needed.

Conditions:

None.

Workaround:

None.

Database

CSCud31674

Symptom:

DB resync failed when avsdb resyned with mixed version.

Conditions:

When VVIM(3.0.3) tries to resync with CDSM(2.5.6), some of tables which are added in latest version will fail.

Upgrading to Release 3.2.1

The supported upgrade paths are the following:

Release 2.5.2 to Release 3.2.1

Release 2.5.3 to Release 3.2.1

Release 2.5.5 to Release 3.2.1

Release 2.5.6 to Release 3.2.1

Release 3.0.1 to Release 3.2.1

Release 3.0.2 to Release 3.2.1

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

For software upgrade procedures, see the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

Upgrading to Cisco TV CDS Release 3.2.1

For the upgrade sequence of the CDS devices in your system (CDSM/VVIM and CDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

To upgrade a CDS device, do the following:


Step 1 Download the ISO image file (CDS-TV-3.2.1-.iso) and the cdsinstall-3.2.1 script from the Cisco Software Download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

Step 2 For the CDS servers, offload the device before upgrading the software.

a. From the CDSM GUI, choose Maintain > Servers > Server Offload. The Server Offload page is displayed.

b. From the Server IP drop-down list, select the IP address or nickname of the sever and click Display.

c. From the New Server Status drop-down list, select Offline for a Streamer or Caching Node, select Offline (No Ingest & Fill) for a Vault.

d. Click Submit.

e. Ensure the CDS server has been offloaded by checking the protocol timing log.

Step 3 Log in to the CDS server as user root.

Step 4 For CDS servers, before installing the image file, stop the database with the following command:

# db_shutdown
 
   

Wait until the following command returns no output:

# netstat -an | grep 9999 and #pgrep avsdb
 
   

Step 5 Copy the ISO image file and the cdsinstall-3.2.1 script to the CDS server.

# scp -p <user>@<remote_ip_address>:CDS-TV-3.2.1.iso /
# scp -p <user>@<remote_ip_address>:cdsinstall-3.2.1 /
 
   

Step 6 Run the cdsinstall script to upgrade the ISO image to Release 3.2.1.

# cd /root
# ./cdsinstall-3.2.1 /CDS-TV-3.2.1.iso
 
   

Step 7 For the CDSM or VVIM, when the script has completed, reboot the server.

Step 8 For the CDSM or VVIM, log in to the GUI as a user with Engineering access level and configure the settings on the CDSM Setup page.

Step 9 For CDS servers, make sure that the database is not running and reboot the server.

# pgrep avsdb
# reboot
 
   

Step 10 For CDS servers, after the CDS server has been verified as reachable, return the server to online.

a. Choose Maintain > Servers > Server Offload. The Server Offload page is displayed.

b. From the Server IP dropdown list, select the IP address or nickname of the server and click Display.

c. Choose Online and click Submit.

d. Verify the CDS server is online by viewing the status on the Monitor > System Level > System Health page.


Downgrading from Release 3.2.1

For the downgrade sequence of the CDS devices in your system (CDSM/VVIM and CDS servers [Vault, Streamer, Caching Node, ISV]), see the "Overview" chapter in the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

To downgrade a CDS device, do the following:


Step 1 Download the ISO image file (for example, CDS-TV-2.5.6.iso) and the cdsinstall script (for example, cdsinstall-2.5.6) for Release 2.5.2, 2.5.3, 2.5.5, or 2.5.6 from the Cisco software download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide.

Step 2 For CDS servers, offload the server (see Step 2 in "Upgrading to Cisco TV CDS Release 3.2.1").

Step 3 Log in to the CDS device as user root.

Step 4 For CDS servers, before installing the image file, stop the database with the following command:

# db_shutdown
 
   

Wait until the following command returns no output:

# netstat -an | grep 9999 and #pgrep avsdb
 
   

Step 5 Copy the ISO image file and the cdsinstall script to the /root directory and run the cdsinstall script to download the software. For example, the following commands are for downgrading to Release 2.5.6:

# scp -p <user>@<remote_ip_address>:CDS-TV-2.5.6.iso /
# scp -p <user>@<remote_ip_address>:cdsinstall-2.5.6 /
# cd /root
# ./cdsinstall-2.5.6 /CDS-TV-2.5.6.iso
 
   

Step 6 For the CDSM or VVIM, when the script has completed, reboot the server.

Step 7 For CDS servers, make sure that the database is not running and reboot the server.

# pgrep avsdb
# reboot
 
   

Step 8 For CDS servers, after the CDS server has been verified as reachable, return the server to online.

a. Choose Maintain > Servers > Server Offload. The Server Offload page is displayed.

b. From the Server IP dropdown list, select the IP address or nickname of the server and click Display.

c. From the New Server Status drop-down list, select Online and click Submit.

d. Verify the CDS server is online by viewing the status on the Monitor > System Level > System Health page. (see Step 7 in "Upgrading to Cisco TV CDS Release 3.2.1" procedure).


Related Documentation

Refer to the following documents for additional information about the Cisco TV CDS 3.2:

Cisco TV CDS 3.2 ISA Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/configuration/isa_guide/tv_cds_3_2_isa_config.html

Cisco TV CDS 3.2 RTSP Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/configuration/rtsp_guide/tv_cds_3_2_rtsp_config.html

Cisco TV CDS 3.2 API Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/developer_guide/tv_cds_3_2_api_guide.html

Cisco TV CDS 3.2 Installation, Upgrade, and Maintenance Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_2/installation_guide/TV_cds_3_2_install_upgrade_maint.html

Cisco Content Delivery System 3.x Documentation Roadmap

http://www.cisco.com/en/US/docs/video/cds/overview/CDS_Roadmap3.x.html

Cisco Content Delivery Engine 205/220/250/420/460 Hardware Installation Guide

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

Cisco Content Delivery Engine 110 Hardware Installation Guide

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

Regulatory Compliance and Safety Information for Cisco Content Delivery Engines

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

Open Source Used in TV CDS 3.2

http://www.cisco.com/en/US/products/ps12653/products_licensing_information_listing.html

The entire CDS software documentation suite is available on Cisco.com at:

http://www.cisco.com/en/US/products/ps7127/tsd_products_support_series_home.html

The entire CDS hardware documentation suite is available on Cisco.com 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.