Guest

Cisco Videoscape Distribution Suite for Internet Streaming

Release Notes for Cisco TV CDS 3.0.2

  • Viewing Options

  • PDF (182.3 KB)
  • Feedback
Release Notes for Cisco TV CDS 3.0.2

Table Of Contents

Release Notes for Cisco TV CDS 3.0.2

Contents

Enhancements

Supported Environments

System Requirements

Limitations and Restrictions

Open Caveats

CServer

Configuration

FSI

Monitoring

RTSP

Statsd

Resolved Caveats

CServer

ISA

Statsd

Vault

Upgrading to Release 3.0.2

Upgrading from Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, or 3.0.1 to Release 3.0.2

Downgrading from Release 3.0.2

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TV CDS 3.0.2


These release notes cover Cisco TV CDS Release 3.0.2.

Revised: July 2012 OL-27184-01

Contents

The following information is in the release notes:

Enhancements

Supported Environments

System Requirements

Open Caveats

Resolved Caveats

Upgrading to Release 3.0.2

Related Documentation

Obtaining Documentation and Submitting a Service Request

Enhancements

The following enhancements have been added in Release 3.0.2:

Ability to configure the manner of NPT interpretation in playlist specifications on a per-stream basis has been added. Previously, Release 3.0.1 supported configuration of this option on a per-Stream Group basis. (CSCua55408)

Streamer can now resolve a Recorder name in a setup request to a Recorder C2 VIP. The name resolution is done by using the /etc/hosts file. (CSCua41653)

The /etc/hosts file can be updated any time and the Streamer can be made aware of the changes in the /etc/hosts file by entering the following command:

echo 1 > /proc/calypso/tunables/read_etc_hosts
 
   

Maximum number of replication members has been increased to more than 256 members. To support this, only one Vault (the Vault master) is included in the list of replication members of the other CDS servers and the CDSM/VVIM. The Vault that is acting as the Vault master has the virtual IP address (VIP) assigned to it. (CSCua61179)

The .arroyorc file of the VVIM/CDSM should contain the VIP of the Vault (which is the acting Vault master) and all the other Caching Nodes and Streamers.

The .arroyorc file of the Vault master should contain the IP addresses of all the other Vaults.

As an example, the replication members of the VVIM/CDSM would be the following:

Vault 1 (Vault master)

Caching Node and Streamers 1 to 255

and the replication members of the Vault master would be the following:

Vault 1 to 255

controller 1

The VVIM/CDSM replicates the records only to the Vault master, and the Vault master replicates the same records to the other Vaults.

When running the cdsconfig script on the VVIM/CDSM, there is a prompt to add the replication members. In the replication member list, a new role called "vmaster" is introduced for the Vault master. After the "vmaster" role is selected as a replication member for the controller (CDSM/VVIM), the Vault master replication feature is enabled and no other Vaults can be added as replication members for the CDSM/VVIM in the .arroyorc file. If the "vault" role is initially selected as a replication member for the controller, before adding the "vmaster," then the "vmaster" role is not available.

The following enhancements have been added to the interoperability functionality between Streamers and nDVR third-party sources (CSCub02651):

Changed Streamer CIF index file parsing to ignore encoder boundary point and other unknown indexing record types.

Fixed an issue where the Streamer dynamic trick-file generation would not work when the Streamer had not yet streamed the content at normal playback speed.

Added the following tuning parameters for generating dynamic trick files from third-party sources:

To adjust the amount of I-Frame video data initially scheduled for cache-fill when dynamic trick-file generation starts, enter the following command:

/proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyInitTimeInEons
 
   

To adjust the maximum amount of I-Frame video data scheduled for cache-fill for a dynamic trick-file generation, enter the following command:

proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyMaxTimeInEons
 
   

To adjust the interval with which the Streamer increases the amount of scheduled I-Frame video data, enter the following command:

proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyIncreaseTimeInEons
 
   

To reduce the scheduled time when I-Frame data is needed to compensate for a delay in third-party cache-fill delivery, enter the following command:

proc/calypso/tunables/dtPrefetchIFramesFrom3rdPartyDelayAdjustTimeInEons
 
   

For dynamic trick-file generation, added support to re-use a Transfer ID from a single locate for multiple cache-fill transfers, as opposed to issuing a single locate for every transfer. This also includes support to persistent TCP sessions used for transfers.

Improved error handling for failed cache-fill when generating a dynamic trick files.

Implemented support for removing cache-fill reservations from a third-party source by using the C2 TransferIDDelete command.

General HTTP and TCP issues to support communication with a third-party source.

Stream zero-motion Pframes instead of null frames during a pause. The default behavior is to stream null MPEG frames during a pause. (CSCtz70454) To stream Pframes instead of null frames during a pause, enter the following command on each Streamer:

echo 1 > /proc/calypso/tunables/streamPFramesDuringPause
 
   

Duration parameter containing the content duration, has been added to the A3 TransferStatusResponse message that is sent when a content ingest has completed. This feature can be enabled by setting the Duration flag to 1 in the fsi.conf. (CSCub02551)

Fade frames from a playlist are enabled by default and can be disabled by logging in to the CDSM GUI and doing the following (CSCua93730):

1. Choose Configure > Array Level > Stream Group Setup.

2. Select the Stream group,

3. To enable Fade Frame Support, select Enabled.

To disable Fade Frame Support, select Disabled.

4. Clicking Submit to save the settings.

The following line is written to Statsd with either a setting of enabled (0) or disabled (1):

/proc/calypso/tunables/disable_fade_frame
 
   

Supported Environments

Release 3.0.2 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.2 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.2 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

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.

Workaround:

Reboot the Streamer.

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.

Statsd

CSCua64597

Symptom:

When any of the Fail Ingest Settings parameters are updated from the CDSM/VVIM page (Configure > System Level > Ingest Tuning), the values are not updated in the /proc file tunables on the Vaults.

Conditions:

Fail Ingest Tuning is enabled from the CDSM/VVIM Setup page, and individual parameters are changed on the Ingest Tuning page.

Workaround:

Update the tunables directly on the Vault by echoing the appropriate values into the tunables, for example:

echo 1 > /proc/calypso/tunables/bRateErrorFailsIngest
 
   

Complete list of tunables is as follows:

PSI Errors:               bPSIErrorFailsIngest  (1 = Enabled, 0 = Disabled)
Bit Rate Errors:         bRateErrorFailsIngest  (1 = Enabled, 0 = Disabled)
Error Count Method:   bEveryNMinutes        (1 = Per Minute, 0 = Per Sample)
Number Of Minutes:    nEveryNMinutes        (minutes)
Discontinuity Rate:     nDiscErrorsFailIngest
Number Of Picture Gaps:  nPicGapsFailIngest
Continuity Counter Errors: nCCErrorsFailIngest
Number Of Sync Loss Errors:  nSyncLossesFailIngest
Picture Gap Duration:  nPicGapsinHSFailIngest          (hectoseconds)
Sync Loss Duration:     nSyncLossesinHSFFailIngest (hectoseconds)
 
   

Note The "b_" tunables are booleans, where 1 = Enabled, 0 = Disabled; the "n_" tunables are numeric, where -1 denotes Ignore; the nEveryNMinutes tunable takes values in minutes; the "_HS_" tunables take values in hecto-seconds (that is, M * 0.01 seconds).


Resolved Caveats

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

CServer

CSCub06826

Symptom:

When upgrading a CDE220-2S3-C or CDE220-2S3-F with 300 GB SSD s and changing the part number to either CDE220-2S4-C or CDE220-2S4-F in a CDS running Release 2.5.6, the disk count and layout in the CDSM GUI does not show correctly, some pages show "Part Number Not Recognized" error messages, and the setupfile does not contain the correct disk information.

Conditions:

Occurs in Release 2.5.6 When upgrading a CDE220-2S3-C or CDE220-2S3-F with 300 GB SSDs and changing the part number to either CDE220-2S4-C or CDE220-2S4-F.

CSCua88768

Symptom:

The CDS server enters a KDB state and displays the following error:

BUG: unable to handle kernel NULL pointer dereference at 0000000000000818
IP: [<ffffffffa036a4c8>] CM::Object::fillSegment+0x468/0x19c0 [avs_cserver]
 
   

Conditions:

Specific conditions are required to reproduce this defect. The system must have a heavy load of disk traffic - nearly 100% of capacity - and it must have a heavy load on the network or the remote vaults containing the desired content. When the system tries to initially read the desired content and fails, it retries reading both a local copy and filling a remote copy. Under certain circumstances when the remote read and the local read fail at precisely the right (wrong) time the data read object leaves the cache data object (ObjectSegment) in an invalid state that allows the null pointer dereference.

CSCua51956

Symptom:

The Streamer Backup server goes into kernel debugger (KDB) mode 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.

ISA

CSCub17028

Symptom:

The ContentStore(Master) restarts because of ORB threads go into deadlock. The monitoring script (run_isa) restarts this application because it does not respond for 15-20 seconds.

Conditions:

Heavy load of db calls, and provisioning requests are served by leader thread. If Leader thread from the thread pool gets blocked on the provision call, then worker threads do not process any incoming requests rather just wait for leader thread to signal them. This causes unnecessary deadlock.

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 has no market reference and a provision request is received for it from the market.

Statsd

CSCua10700

Symptom:

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

Conditions:

DCS setup with no Caching Nodes and local Vaults.

Vault

CSCua88768

Symptom:

The CDS server kernel debugger displays the following error:

      BUG: unable to handle kernel NULL pointer dereference at 0000000000000818
      IP: [<ffffffffa036a4c8>] CM::Object::fillSegment+0x468/0x19c0 [avs_cserver]
 
   

Conditions:

The system must have a heavy load of disk traffic (nearly 100% of capacity) and a heavy load on the network or the remote vaults containing the content. When the system tries to initially read the content and fails, it retries reading both a local copy and filling a remote copy. When the remote read and the local read fail at precisely the right (wrong) time, the data read object leaves the cache data object (ObjectSegment) in an invalid state that allows the null pointer dereference.

Upgrading to Release 3.0.2

The supported upgrade paths are the following:

Release 2.5.2 to Release 3.0.2

Release 2.5.3 to Release 3.0.2

Release 2.5.5 to Release 3.0.2

Release 2.5.6 to Release 3.0.2

Release 3.0.1 to Release 3.0.2

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

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

Upgrading from Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, or 3.0.1 to Release 3.0.2

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.2-.iso) and the cdsinstall-3.0.2 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.2 script to the CDS server.

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

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

# cd /root
# ./cdsinstall-3.0.2 /CDS-TV-3.0.2.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.2

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 from Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, or 3.0.1 to Release 3.0.2").

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 from Release 2.5.2, 2.5.3, 2.5.5, 2.5.6, or 3.0.1 to Release 3.0.2" 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.