Guest

Cisco Videoscape Distribution Suite for Television

Release Notes for Cisco VDS-TV 2.5.7

  • Viewing Options

  • PDF (197.0 KB)
  • Feedback
Release Notes for Cisco TV CDS 2.5.7

Table Of Contents

Release Notes for Cisco TV CDS 2.5.7

Contents

New Features

Enhancements

Supported Environments

System Requirements

Open Caveats

Cs-file-systems

Resolved Caveats

Avslauncher

Configuration

CServer

Installation

Interoperability

ISA

RTSP

Scripts

SNMP

Statsd

Syslog

Upgrading to Release 2.5.7

Upgrading from Release 2.5.2, 2.5.3, 2.5.4, 2.5.5 or 2.5.6 to Release 2.5.7

Downgrading from Release 2.5.7

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco TV CDS 2.5.7


These release notes cover Cisco TV CDS Release 2.5.7.

Revised: Jan 2013 OL-28820-01

Contents

The following information is in the release notes:

New Features

Enhancements

Supported Environments

System Requirements

Open Caveats

Resolved Caveats

Upgrading to Release 2.5.7

Related Documentation

Obtaining Documentation and Submitting a Service Request

New Features

There are no new features in CDS-TV 2.5.7.

Enhancements

The following enhancements have been added in Release 2.5.7:

There is no easy or built in way to remove remote vaults from cserver if they are detected. If a monitor packet is received and cserver adds the remote vault, there is no way to remove that remote vault (CSCub92363).

To make debugging issues where content is unexpectedly deleted, we include the server id in the log message indicating that we received and invlalidate (delete) request from another server (CSCuc72004).

Statsd is enhanced so that if it determines that the existing master vault has gone away, and that it wants to move the VIP address to this server, it needs to also add the step of sending out the arp query and waiting to see if there is a response. Only if there is no response to the arp query, should it proceed with starting the VIP address on this server. Otherwise it needs to do the same as cserver and wait for a second and then try again if it believes that it still should start the VIP address on this server.

Also, it should try to establish a TCP connection from the current vault's physical IP address to the VIP to see the connection is successful to determine VIP is already running on another vault.

The above two checks should be made on a continual basis with some delay till it determines VIP is running on no other server to make the failover, or if a heartbeat message is received from peer server saying that it is already running as master (CSCud81758).

We have several cases where a remote server gets auto-detected and is causing problems and the only way to remove the server permanently is to reboot all servers. We should add a way to NOT preserve the auto-detected remote servers (CSCu72015).

The MSPP (Minimum Streams Per Port) algorithm needs to be adjusted so that it is more agressive in moving streams from the default streamer out to other streamers in the stream group. Currently the algorithm requires that there are (2 * MSPP) streams that prefer a streamer before those streams will be moved there. This needs to be reduced to (MSPP + 1), (CSCua42598).

Supported Environments

Release 2.5.7 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 2.5.7 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 2.5.7 also runs on the CDE100, CDE200, CDE300, and CDE400 hardware models that use the Lindenhurst chipset. See the Cisco Content Delivery Engine CDE100/200/300/400 Hardware Installation Guide for set up and installation procedures.

Release 2.5.6 does not support the CDEs with the ServerWorks chipset. All CDEs with the ServerWorks chipset need to be replaced with the CDEs with the Lindenhurst chipset or the Next Generation Appliances (CDE110, CDE220, CDE250, andCDE420) before upgrading to Release 2.5.6.


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.


Open Caveats

This release contains the following open caveats:

Cs-file-systems

CSCub38015

Symptom:

The Megaraid firmware fault is still under investigation. When the hard hang occurs the CDS machine cannot be Pinged or attached to via SSH. To recover the machine it must be power cycled.

Conditions:

The Megaraid firmware fault is still under investigation. In order for the hard hang to occur the CDS Machine(s) must have the Megaraid 9261 card installed.

If a Terminal is attached to the CDS Machine when this problem occurs the following messages will be scrolling on the screen.

"megaraid_sas: fw state while internal state changes, state:c0000000, disableOCR=0"

"megaraid_sas: fw state while internal state change operational, state:c0000000"

Workaround:

The Megaraid firmware fault is still under investigation. There is currently no workaround for this problem.

Resolved Caveats

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

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.

Configuration

CSCuc19419

Symptom:

CDSM setup page does not reflect the correct value for Change notification.

Conditions:

When submitting the CDSM setup page for a central content store, the Change Notification always shows disabled even though it MAY be enabled.

CSCua56548

Symptom:

Before we did not allow "-" character for productId in GUI.

Conditions:

Now we allow the use of the following character 'a-z, or A-Z and "_" or "-" without blank spaces'

Workaround:

In GUI Java Script we have changed code to allow the '-' character for Product Id. Which will allow the user to use 'a-z, or A-Z and "_" or "-" without blank spaces'.

CServer

CSCub92363

Symptom:

The customer had created a national site and was re-purposing and moving some vaults from local sites to the national site.

The same old cache-fill IP addresses were reused by the vaults moved to the national site. The remote servers file on both the national and remote sites were properly configured. After the vaults were moved, some of them reconnected to vaults in their old vault groups. Later, this caused another issue were GOIDs deleted from vaults one the national site, were sometimes removed from vaults on the local sites.

Conditions:

When the re-purposed vault from a local site were moved to the national site, the other vaults from the local site were still trying to talk to the moved vaults. They needed to be configured and rebooted, but were not.

Workaround:

Added some rules to the way CServer adds new remote servers when the CServer option "allow new L3 remote servers" option is enabled.

Vaults can automatically add new caches and streamers; caches can add streamers, and streamers can add other streamers.

Typically the "allow new L3 remote servers" option is used by vaults and caches to add new streamers that are configured to connect to them.

Vaults won't automatically add other vaults, nor caches to other caches. Vaults and caches in a group have to be configured to do so, and this is what is currently being done by the VVIM. If the old behavior is desired, set the tunable /proc/calypso/internal/allow_all_new_l3_remote_servers to 1.

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

Conditions:

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

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.

Workaround:

Fixed code in primary streamer code to blacklist a streamer which reports INSUFFICIENTRESOURCES so that the stream will reassigned to a different streamer.

CSCub29293

Symptom:

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

Conditions:

Example of invalid GET: GET /nCircle.ip360 HTTP/1.0

Workaround:

Once the server gets into this situation, follow the following procedure to recover the system:

First, avsdb on all affect vaults need reboot.

Second, the in memory PAID-to-GOID mappings need flushed on all CGWs as they could now have cached invalid PAID-to-GOID mappings. This can be done by 'echo remove all > /proc/calypso/internal/paid_to_goid_cache.

Third, avsdb content records on the streamers will need to be compared to the vaults to find which assets are not pointing to correct GOIDs. These avsdb records will then need removed.

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.

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 artifically throttled.

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.

CSCub06826

Symptom:

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

Conditions:

CDSTV 2.5.6 When upgrading a CDE220-2S3-C or CDE220-2S3-F with 300 GB SSD drives and changing the part number to either CDE220-2S4-C or CDE220-2S4-F.

CSCud09793

Symptom:

The issue is observed only when RTSPTrickRestrictionEnabled = 0.

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.

CSCua72269

Symptom:

4 Vaults, totaly 200 live recordings, account redundancy, 100 live recordings for each Vault, and 1000 streams for these 200 live recordings, other 1000 streams from 200 different vod contents. Some of Vaults will hit KDB after running a while.

Conditions:

This symptom has been observed after a longevity testing.

CSCud6222

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

Workaround:

There is not a workaround. The only thing CDSTV can do is to protect itself. The real fix is to make sure the back office uses a correct start time.

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.

Workaround:

Disable the TCP/HTTP traffic on the next level router/switch through which the Cache Fill interfaces are connected.

CSCus01310

Symptom:

Primary Control Streamer crashes while selecting a play server(costing) for a session playlist which has same content repeated in playlist.

Conditions:

CDSTV Software version 2.5.3 2.5.4 2.5.5 2.5.6 running on control server Play is given for a session playlist which has same Content being repeated in the Playlist.

CSCuc03388

Symptom:

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

Conditions:

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.

Installation

CSCuc63641

Symptom:

During the CDSTV upgrade process, the firmware of the two SSDs attached to the MegaRAID controller is validated and updated if necessary. If a firmware update is needed, the firmware update process would report a failure after updating only the first of the two SSDs. This was due to a newer MegaCLI64 utility that potentially reports an unexpected, but nevertheless successful, exit code.

Conditions:

CDE box must have internal 64GB X25-E SSDs. CDSTV is being upgraded from 2.5.2 to anything prior to 2.5.6-b17

Workaround:

A manual firmware update process was created for field engineers to perform if necessary.

Interoperability

CSCuc18028

Symptom:

The script "run_resource_manager" starts ResourceManager that reaps the orphan streams. This script feeds the list of session gateways to ResurceManager 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.

ISA

CSCud84017

Symptom:

The Segment Index and Content NPT is reported incorrectly in the VE_STOP event if playlist size if bigger than 5.

Conditions:

The session should be a playlist session and normally to reproduce the problem the playlist should be bigger than 5.

Workaround:

There is no work around available. The only way to prevent this issue, just use use the smaller playlist size in the session.

CSCud84164

Symptom:

LSC Mode is changed to "Open" from "Pause" if LSC Pause request shows up twice.

Conditions:

Consecutive Pause requests. Not a normal condition and not a direct impact on the service but as per standard the mode should not be changed.

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.

CSCub17028

Symptom:

The ContentStore(Master) restarts because 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.

Workaround:

Deploying Vault virtualization could help because it moves the content store interface to VHO and divides the load by 12.

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.

Workaround:

Manually add the market reference to it by running the script "inc_ref_count".

Example: ./inc_ref_count <NumericMarketId>.

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 only once if DCS/VCS feature on a VHO is enabled.

RTSP

CSCua26048

Symptom:

Incorrect checking of parameters within handleSRMSync process, on the RTSP server, causes threads to get exhausted and eventually causes RTSP to crash.

Conditions:

There is an incorrect condtion to get the info on session_list are exist or not.

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.

CSCutx23643

Symptom:

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

Condition:

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.

Workaround:

Disable the archiving and trimming by commenting out the following lines in /sbin/avs_archive.

/sbin/avs_archive_logs

/sbin/avs_trim_archives

In 2.5.X, the new archiving mechanism will compress the log files and move to /arroyo/log/archive. CAUTION : By doing this, care should be taken to clean up this folder if the usage is high.

SNMP

CCSCua77598

Symptom:

Some vaults appear as red in CDSM/VVIM GUI.

Conditions:

Debugging reveals that in some conditions, DB can become stuck while trying to send a message to snmpd, because snmpd does not handle sockets properly. This makes DB unable to continue communicating properly with the UI.

Workaround:

Restart snmpd.

# service snmpd restart.

Statsd

CSCua10700

Symptom:

In DCS setup with no caches and local vaults, streamer RemoteServers file contains both local and regional vaults. However, local and regional vault files do not contain streamers.

Conditions:

DCS setup with no caches and local vaults.

Workaround:

Manually edit RemoteServers file on vaults to include streamers.

CSCutx30156

Symptom:

When two vaults are used in failover group but connected to different switches, a condition may occur when the slave (B) vault fails to get advertisement from master (A) during the expected default failover interval, assumes master, and sends out ARPs to the neighbors. When heartbeats from original master (A) are resumed being received, the new master (B) assumes slave. (A) continues to send ARPs every minute to update neighbors, but the caches on the device path from (A) to the BMS/backoffice are not necessarily updated. Hence, when backoffice tries to connect to the master vault, it accidentally ends-up contacting the (B), but master services are not running on (B) anymore.

Conditions:

This happens when the following conditions are met:

a) Vaults are used in failover group but connected to different switches, and

b) Slave (B) vault fails to get advertisement from master (A) during the expected threshold (default or set from command line using -f), and

c) Heartbeats from original master (A) are then resumed being received and (B) assumes slave

Workaround:

Ensure all failover devices are connected to one switch (co-located). Or, increase failover interval to 6 seconds (instead of default 3), by running statsd with switch: "-f 6". CDS-TV 3.0 uses a default of 9 seconds, to counter any delays in the network.

Syslog

CSCua85547

1. Symptom:
/arroyo/log/archive directory not available.
Conditions:
If Install build version greater than 2.5.2, then /arroyo/log/archive directory not available.
Workaround:
mkdir /arroyo/log/archive
/* "/home/isa/logrotate/rotate.conf" */

2. Symptom:
"/home/isa/logrotate/rotate.conf" file not available.
Conditions:
None
Workaround:
cp rotate.conf.default rotate.conf

Upgrading to Release 2.5.7

The supported upgrade paths are the following:

Release 2.5.2 to Release 2.5.7

Release 2.5.3 to Release 2.5.7

Release 2.5.4 to Release 2.5.7

Release 2.5.5 to Release 2.5.7

Release 2.5.6 to Release 2.5.7

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

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


Note To upgrade from Release 2.5.1 to Release 2.5.2, see EDCS-1141294.

To upgrade from Release 2.5.1-ES1 to Release 2.5.5, see EDCS- 1138748. The following are described in EDCS-1138748:

CDSM and Vaults upgrade from Release 2.5.1-ES1 to Release 2.5.5

CDE220 and CDE300 servers upgrade from Release 2.3.3-ES1 to Release 2.5.5

CDE250 servers upgrade from Release 2.4.1 to Release 2.5.5


Upgrading from Release 2.5.2, 2.5.3, 2.5.4, 2.5.5 or 2.5.6 to Release 2.5.7

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

To upgrade a CDS device, do the following:


Step 1 Download the ISO image file (CDS-TV-2.5.7.iso) and the cdsinstall-2.5.7 script from the Cisco Software Download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV CDS 2.5 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-2.5.7 script to the CDS server.

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

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

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

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

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

# pgrep avsdb
# reboot
 
   

Step 9 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 2.5.7

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 2.5 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.2.iso) and the cdsinstall script (for example, cdsinstall-2.5.2) for Release 2.5.2, 2.5.3, or 2.5.5 from the Cisco software download website. For more information on downloading the software files, see the "Overview" chapter in the Cisco TV CDS 2.5 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.4, 2.5.5 or 2.5.6 to Release 2.5.7").

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

# scp -p <user>@<remote_ip_address>:CDS-TV-2.5.2.iso /
# scp -p <user>@<remote_ip_address>:cdsinstall-2.5.2 /
# cd /root
# ./cdsinstall-2.5.2  /CDS-TV-2.5.2.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.4, 2.5.5 or 2.5.6 to Release 2.5.7" procedure).


Related Documentation

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

Cisco TV CDS 2.5 ISA Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/2_5/configuration/isa_guide/tv_cds_2_5_isa_config.html

Cisco TV CDS 2.5 RTSP Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/2_5/configuration/rtsp_guide/tv_cds_2_5_rtsp_config.html

Cisco TV CDS 2.5 API Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/2_5/developer_guide/tv_cds_2_5_apiguide.html

Cisco TV CDS 2.5 Installation, Upgrade, and Maintenance Guide

http://www.cisco.com/en/US/docs/video/cds/cda/tv/2_5/installation_guide/tv_cds_2.5_maint_guide.html

Cisco Content Delivery System 2.x Documentation Roadmap

http://www.cisco.com/en/US/docs/video/cds/overview/CDS_Roadmap.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

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 Engines

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

Open Source Used in TV CDS 2.5

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.