Guest

Cisco Videoscape Distribution Suite for Television

Release Notes for Cisco VDS-TV 3.0.3

  • Viewing Options

  • PDF (167.0 KB)
  • Feedback
Release Notes for Cisco TV CDS 3.0.3

Table Of Contents

Release Notes for Cisco TV CDS 3.0.3

Contents

Supported Environments

System Requirements

Limitations and Restrictions

Open Caveats

CServer

Configuration

FSI

Monitoring

RTSP

Resolved Caveats

CServer

FSI

RTSP

ISA

Interoperability

CDE220

Other

Upgrading to Release 3.0.3

Upgrading to Cisco TV CDS Release 3.0.3

Downgrading from Release 3.0.3

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TV CDS 3.0.3


These release notes cover Cisco TV CDS Release 3.0.3.

Revised: October 2012 OL-28208-01

Contents

The following information is in the release notes:

Supported Environments

System Requirements

Open Caveats

Resolved Caveats

Upgrading to Release 3.0.3

Related Documentation

Obtaining Documentation and Submitting a Service Request

Supported Environments

Release 3.0.3 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.0.3 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 Hardware Installation Guide.

The Cisco TV CDS Release 3.0.3 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

CSCtn28329

Symptom:

In the CDSM (or VVIM) GUI, on the Server Setup page (Configure > Server > Server Setup), when specifying an interface for the FTP Out Interface field under the FTP Out Setting section, the configuration setting does not take affect and the specified interface is not used for FTP out operations.

Conditions:

Using the CDSM (or VVIM) GUI, specify an FTP out interface and submit the Server Setup page. The setupfile on the server will be updated to reflect this configuration, as in following example:

ftpout if eth0 max utilization mbps 0 max sessions 0
 
   

Workaround:

The IP address of the interface to be used in FTP out operations can be specified on the ftp command line.

Configuration

CSCti78219

Symptom:

Not all packages are found in the drop-down list on the Monitor > System Level > Package Monitor page.

Conditions:

When the number of packages in the system reaches a level greater than 70,000.

Workaround:

If the number of packages in the system grows much beyond 70,000, then the drop-down list may not be able to display them all. The solution is to delete packages that are no longer needed. The maximum number of packages that will display in the drop-down list is variable, and is dependent on the system that is accessing the web page.

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.

Monitoring

CSCua35309

Symptom:

Occasionally, the Monitor > Server Level > NIC Monitor > Graph Ports page display does not match exactly the received Mbps and transmit Mbps reported by way of the ifstat for some CDS servers.

Conditions:

This appears almost randomly, and may be a temporary condition because of congested traffic between the CDS server and the CDSM.

Workaround:

There is no workaround at this time and this condition is rarely seen.

RTSP

CSCua49251

Symptom:

RTSP Setup failed and error thrown as ""RTSP/1.0 771 Server Setup Failed - Asset Not Found"

Conditions:

1. Configure a thin pipe between a Vault and a Caching Node.

2. Set up session with content that needs to be filled from Vault and that exceeds the bandwidth limit configured.

3. The session fails and the following error is thrown: RTSP/1.0 771 Server Setup Failed - Asset Not Found.

Workaround:

None.

CSCty30779

Symptom:

Streamers take about 13 seconds to respond to a Session Setup request.

Conditions:

During load test on Streamers running Release 2.3.3 or Release 2.5.2 with RTSP-BNI Backoffice, responses to Session Setup requests takes between 13 and15 seconds.

Workaround:

None.

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:

Stop AVSDB on all Streamers in that Stream Group and enter the following command on each CDS server:

rm rtsp_session.db rtsp_annex.db
 
   

Start AVSDB on Streamers in that Stream Group.

Resolved Caveats

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

CServer

CSCuc30278

Symptom:

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

Conditions:

When an end-user issues a SETUP and TEARDOWN request during a live recording, and then issues another SETUP followed by PLAY after the live recording is over.

CSCub60335

Symptom:

Rewind of live nDVR stream does not function properly.

Conditions:

Occurs when a streamer has not been configured explicitly to fill from an HTTP source, and is attempting to stream nDVR content.

CSCub72094

Symptom:

Warnings in the C2K log.

Conditions:

Dynamic trick generation and fast-forward.

CSCub64021

Symptom:

Stream fails on fast-forward or rewind.

Conditions:

Fast-forward or rewind on a live recording with dynamic tricks.

CSCua63860

Symptom:

Server crash with a bad reference.

Conditions:

When all network adapters are pulled and reinserted in quick succession.

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.

CSCub29293

Symptom:

Invalid GET message to Caching Node causes Vault to send incorrect GOID to downstream servers.

Conditions:

Example of invalid GET follows:

GET /nCircle.ip360 HTTP/1.0
 
   

CSCua91655

Symptom:

In extreme conditions of initializing services, when the system is starting, the system fails.

Conditions:

When a Streamer is being booted, a very rare race condition may occur causing a null pointer to be created thus causing an exception and the server to fail.

FSI

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

RTSP

CSCub63164

Symptom:

RTSP Calling Cserver API GetContentStruct twice times to setup a NDVR request

Conditions:

For every time to setup a request for nDVR content this issue will occur

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.

ISA

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.

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.

CDE220

CSCuc60942

Symptom:

The CDEx20 chassis may be populated with two internal, RAIDed, SSDs attached to a LSI MegaRAID controller. During a CDSTV upgrade event, it may be determined that the firmware on the internal SSDs should be updated. When the firmware update occurs, it's possible that only the 1st SSD's firmware is updated due to the misinterpretation of a completion code produced by the firmware update utility which was also updated during the CDSTV upgrade.

Conditions:

The firmware update utilities were updated in CDSTV version 2.5.6 and updates to this version, or greater, are susceptible to this firmware update failure.

CSCub47346

Symptom:

Streamer crashes upon setup of nDVR playlist.

Conditions:

The Streamer may crash when processing an nDVR playlist where a playlist element has an index file which has not been generated in the CIF format.

Other

CSCub83258

Symptom:

Evaluators are stuck. A "WARNING: Evaluators are disabled" entry is logged incessantly to the protocol timing log (more than several minutes). One or more local copy evaluator agents (Defrag, Local Mirroring or Local Smoother) are still active and never complete.

Conditions:

This is a very rare condition.

First a large ObjectSegment is created in the memory cache. This may happen if a fill overlaps with another "runt" fill (one that has not yet received any data). When this condition occurs (quite rare) the code will continue to add data to the previous ObjectSegment; thus generating an unusually large ObjectSegment. This is not a catastrophic condition, but is nonetheless undesired.

Next one of the local evaluators must be triggered while this large ObjectSegment is still present in cache (memory) and attempt to read this ObjectSegment and then issue a corresponding write for this ObjectSegment. This will only happen if the conditions within the evaluator indicate that this segment of the object must be copied (again this adds to the unlikelihood that this condition will occur).

Finally, while re-writing this large ObjectSegment, four conditions must occur:

1) The write size of this ObjectSegment must be larger than the maxDiskStartWrite size.

2) The corresponding read agent must have already queued double the maxDiskStartWrite size to be written.

3) When the write actually occurs the track boundary alignment for this write must cause it to write a portion of, but not all of this data.

4) The remaining queued, but unwritten data must be less than the maxDiskStartWrite size.

Given all of these conditions the likelihood of seeing this issue is very rare. These issues have been in the code since it was originally written (1.5.x).

Upgrading to Release 3.0.3

The supported upgrade paths are the following:

Release 2.5.2 to Release 3.0.3

Release 2.5.3 to Release 3.0.3

Release 2.5.5 to Release 3.0.3

Release 2.5.6 to Release 3.0.3

Release 3.0.1 to Release 3.0.3

Release 3.0.2 to Release 3.0.3

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

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

Upgrading to Cisco TV CDS Release 3.0.3

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.0 Installation, Upgrade, and Maintenance Guide.

To upgrade a CDS device, do the following:


Step 1 Download the ISO image file (CDS-TV-3.0.3-.iso) and the cdsinstall-3.0.3 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.0 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. Select Enable and click Submit.

d. Ensure the CDS server has been offloaded by checking the protocoltiming log.

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-3.0.3 script to the CDS server.

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

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

# cd /root
# ./cdsinstall-3.0.3 /CDS-TV-3.0.3.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 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, disable the Server offload.

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 Disable 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.0.3

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.0 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.0 Installation, Upgrade, and Maintenance Guide.

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

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, disable the Server offload.

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 Disable 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.0.3" procedure).


Related Documentation

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

Cisco TV CDS 3.0 ISA Software Configuration Guide

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

Cisco TV CDS 3.0 RTSP Software Configuration Guide

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

Cisco TV CDS 3.0 API Guide

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

Cisco TV CDS 3.0 Installation, Upgrade, and Maintenance Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/3_0/installation_guide/tv_cds_3_0_maint_guide.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 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.0

http://www.cisco.com/en/US/products/ps7127/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.