Guest

Cisco Videoscape Distribution Suite for Internet Streaming

Release Notes for Cisco Internet Streamer CDS 2.6.3

  • Viewing Options

  • PDF (708.2 KB)
  • Feedback
Release Notes for Cisco Internet Streamer CDS 2.6.3

Table Of Contents

Release Notes for Cisco Internet Streamer
CDS 2.6.3

Contents

Enhancements in Release 2.6.3-b50

Enhancements in Release 2.6.3-b47

Enhancements in Release 2.6.3-b45

Enhancements in Release 2.6.3-b35

API Consistency Check

Enhancements in Release 2.6.3-b32

MTU Support

Enhancements in Release 2.6.3-b23

Web Engine

Origin Server Redirect

HTTP Read Timeout

Origin Server HTTP Port

Web Engine Command Change

Movie Streamer Scheduled Broadcast Playlist

API Change

CLI Changes

Authorization Server Geo/IP Plugin Disable

CLI Changes

CDSM GUI Changes

Service Router

Unified Routing Table

Load Monitoring and Reporting

APIs

API to Modify the Origin Server in a Delivery Service

CDSM API Enhancement for File Management

CDSM API Changes

Platform

Proper Disk Shutdown

Disk Latent Sector Failure Handling

Improved Error Handling

MegaRAID Support

Proximity Engine, BGP MIB Support

Other Enhancements

Lengthy URL Content in Content Manager

DirNode Limits

Prepositioning Content

Cached Contents

Interface Mapping CLI Changes

tcpdump Enhancements

contentmgr delivery-service Command

System Requirements

Limitations and Restrictions

System Limits and Thresholds

Important Notes

Open Caveats

Open Caveats in Release 2.6.3-b50

Open Caveats in Release 2.6.3-b47

Open Caveats in Release 2.6.3-b45

Open Caveats in Release 2.6.3-b39

Open Caveats in Release 2.6.3-b35

Open Caveats in Release 2.6.3-b32

Open Caveats in Release 2.6.3-b26

Open Caveats in Release 2.6.3-b23

Service Router

Resolved Caveats

Resolved Caveats in Release 2.6.3-b50

Resolved Caveats in Release 2.6.3-b47

Resolved Caveats in Release 2.6.3-b45

Resolved Caveats in Release 2.6.3-b39

Resolved Caveats in Release 2.6.3-b35

Resolved Caveats in Release 2.6.3-b32

Resolved Caveats in Release 2.6.3-b26

CDSM

Content Manager

FMS

Platform

Transaction Logs

Web Engine

Resolved Caveats in Release 2.6.3-b23

Auth Server

Cache Router

CDSM

CLI

Content Manager

Data Server

DSS

FMS

Live Routing

MegaRaid

MP3 Live

Network

Platform

Service Routing

SNMP

SVC Monitor

Translog

Web Engine

WMT

UNS Server

Accessing Bug Tool kit

Upgrading to Release 2.6.3

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Internet Streamer
CDS 2.6.3


This release note covers Cisco Internet Streamer CDS Release 2.6.3-b50.


Note Release 2.6.3-b50 obsoletes all previous builds of Release 2.6.3.


First Published: June 12, 2012

Last Updated: June 14th, 2013
OL-28681-03

Contents

The following information is included in these release notes:

Enhancements in Release 2.6.3-b50

Enhancements in Release 2.6.3-b47

Enhancements in Release 2.6.3-b45

Enhancements in Release 2.6.3-b35

Enhancements in Release 2.6.3-b32

Enhancements in Release 2.6.3-b23

System Requirements

Limitations and Restrictions

System Limits and Thresholds

Important Notes

Open Caveats

Resolved Caveats

Accessing Bug Tool kit

Upgrading to Release 2.6.3

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request

Enhancements in Release 2.6.3-b50

There are no new enhancements in Release 2.6.3-b50.

Enhancements in Release 2.6.3-b47

There are no new enhancements in Release 2.6.3-b47.

Enhancements in Release 2.6.3-b45

CDSM supports and allows User configuration of disk error-handling, threshold alarm-bad-sectors <value> by GUI page.

These features must be configured via the CLI.

Enhancements in Release 2.6.3-b35

The following enhancement has been added in Release 2.6.3-b35:

API Consistency Check

API consistency check between program name and reference URL. (CSCth89544)

There is now consistency check between the program name and reference URL for an API code. In the CDSM GUI, the reference URL is derived from the program name, and the customer chooses the reference URL from drop-down list. In the API, both fields are filled out by customer in the program file, so there is a possibility of inconsistency.

Enhancements in Release 2.6.3-b32

The following enhancement has been added in Release 2.6.3-b32:

MTU Support

Release 2.6.1 and later expands maximum transmission unit (MTU) support to CDS-IS port channels. (CSCtz67938)

To set the interface MTU packet size, use the mtu interface configuration command. Use the no form of this command to reset the MTU packet size. The MTU is the largest size of IP datagram that can be transferred using a specific data link connection.

mtu mtu_size

no mtu mtu_siz

mtu_size

MTU packet size in bytes (576 to 1500). Default is 1500 bytes.


Enhancements in Release 2.6.3-b23

The following enhancements have been added in Release 2.6.3-b23:

Web Engine

Movie Streamer Scheduled Broadcast Playlist

Authorization Server Geo/IP Plugin Disable

Service Router

APIs

Platform

Proximity Engine, BGP MIB Support

Other Enhancements

Web Engine

The following Web Engine enhancements have been added to Release 2.6.3:

Origin Server Redirect

HTTP Read Timeout

Origin Server HTTP Port

Origin Server Redirect

Previously, if a Service Engine (SE) receives a 301, 302, or 307 response from the Content Acquirer, it sends it back to the client to handle. The Origin server may redirect the request to an external server, in which case the client makes the connection to the external server to get the asset and the CDS is completely bypassed. All subsequent requests for that asset invoke the same redirect mechanism, which results in increased traffic to the external server and losing the benefits of CDS.

With the addition of the Origin Server Redirect feature in Release 2.6.3, the Web Engine handles the 302 redirect itself rather than forwarding the response to the client. This is accomplished by enabling the Origin Server Redirect configuration on a per delivery-service basis. The destination server may return any other valid HTTP response, which may be sent back to the client. There is a count on the number of times a redirect is followed. This count is also set per delivery service through the CDSM. If the number of redirects is exceeded, an error is returned to the client. There is also a client timeout that is the time within which the client returns a a response. If a response cannot be returned within that time, an error is sent to the client.

Because all SEs in the CDS have to be the same or higher software release as the CDSM, if this feature is configured on the CDSM, all SEs in the CDS support this feature.


Note This feature is not supported for the HEAD request; only the GET request is supported (CSCtx29825).


To configure the Origin Server Redirect feature, do the following:


Step 1 Log in to the CDSM GUI.

Step 2 Choose Services > Service Definition > Delivery Services, click the Edit icon next to the delivery service. The Delivery Service Definition page is displayed.

Step 3 Choose General Settings. The General Settings page is displayed.

Step 4 Check the Follow Origin Server redirects check box.

Step 5 In the Number of redirects allowed field, enter the number of times redirection is allowed for each request. If the number of redirects is exceeded, an error is returned to the client. The default is 3. The range is from 1 to 3.

As an example, if the Number of redirects allowed is set to 2 and the Origin server redirects to a server B, B redirects to C, and C redirects to D, then only redirection to C is followed. When C returns 302, the Web Engine on the SE returns an error code 310 to the client.

Step 6 Click Submit


CLI Changes

A new field, Origin Server Redirected Requests, has been added to the output of the show statistics web-engine command under the HTTP Request Type Statistics section. This counter is cleared when the Web Engine is restarted or the clear statistics all command is entered. The counter is per device and is the cumulative sum of requests coming to all delivery services on the SE for which this feature is enabled.

Web Engine Transaction Log Changes

Web Engine ingest transaction log on the Content Acquirer includes all Origin server 302 response transactions and the associated redirected URLs. If an SE is not a Content Acquirer and does not receive the 302 response, the response (probably 200) is returned by the upstream SE. The following is displayed in the fields:

The Response-Code column has either a 302 or 200 (accordingly).

If a 302 response code is received, the "redirected-url" field displays the new URL.

If a 200 response code is received, the "redirected-url" filed has a "-" in it.

HTTP Read Timeout

Previously, the Web Engine had a hardcoded HTTP Read Timeout of 5 seconds. If the Origin Server did not respond within 5 seconds, the connection was terminated and the content was not served. Similarly, if the upstream SE did not respond within 5 seconds, the connection was terminated and the content was not served.

In Release 2.6.3, the HTTP Read Timeout field has been added to allow configuration of this parameter on a per delivery-service basis. This ensures that all SEs at all tiers within that delivery service have the same timeout value.

If the Origin Server Redirect feature is enabled, the configured HTTP Read Timeout period for the delivery service is used for each redirected Origin server. Because each Origin server may have a different idle period, it may cause additional delays to the user depending on the value and frequency of the idle periods.

To configure the HTTP Read Timeout field, do the following:


Step 1 Log in to the CDSM GUI.

Step 2 Choose Services > Service Definition > Delivery Services, click the Edit icon next to the delivery service. The Delivery Service Definition page is displayed.

Step 3 Choose General Settings. The General Settings page is displayed.

Step 4 In the HTTP Response Read Timeout field, enter the timeout value (in seconds) in which a connection to the Origin server or upstream SE is terminated. The default is 5. The range is from 1 to 60.

Step 5 Click Submit


The show web-engine delivery-service-configuration command displays the value of the HTTP Read Timeout field.

Origin Server HTTP Port

Prior to Release 2.6.3, to work with the Web Engine in the Internet Streamer CDS, all Origin servers must be configured to listen to the standard HTTP port (80) for all HTTP traffic.

Release 2.6.3 provides the option to configure non-standard HTTP ports for communication between the Web Engine and the Origin server. The Origin Server HTTP Port numbers can be configured on a per delivery-service basis.

To configure all SEs in a delivery service to use the non-standard HTTP ports, do the following:


Step 1 Log in to the CDSM GUI.

Step 2 Choose Services > Service Definition > Delivery Services, click the Edit icon next to the delivery service. The Delivery Service Definition page is displayed.

Step 3 Choose General Settings. The General Settings page is displayed.

Step 4 In the Origin Server HTTP Port field, enter the non-standard HTTP ports to be used for communication with the Origin server. The default value is 80.

Valid entries consist of port numbers in the 1-65535 range, with the exception of the Well-Known Ports used by the CDS. To view the list of Well-Known Ports used by the CDS, see the System > CDS-IS Well Known Ports page.

Step 5 Click Submit.


Web Engine Command Change

Release 2.6.3 introduces a new Web Engine command that dynamically configure the buffer size to read HTTP body messages, web-engine cache http-body-read-buffer-size <value in KB>. The purpose of this command is to make the BODYREAD_BUFFSIZE macro in HTTPServerXact.cpp to be configurable in run-time (as opposed to compile-time). This is to optimally configure the receiver buffer size to remove adding a possible latency from calling too many read system calls and Xact's callback function calls.

Example output from SE:

ServiceEngine# configure
ServiceEngine(config)# web-engine cache ?
  age-multiplier              Expiration time as a percentage of their age
  http-body-read-buffer-size  configure HTTP body read buffer size (in Kbytes, default is 
32KB)
  max-ttl                     Maximum time to live for objects in the cache. (default is 
61 days)
  min-ttl                     Minimum time to live for objects in the cache. (in minutes, 
default is 60)
ServiceEngine(config)# web-engine cache http-body-read-buffer-size ?
  <1-1000000>  buffer size (in Kbytes, default is 32KB)
ServiceEngine(config)# web-engine cache http-body-read-buffer-size 50
ServiceEngine(config)# end
ServiceEngine# show web-engine all
HTTP heuristic age-multipliers: 30%
 
   
HTTP Body Read Buffer Size: 50 (KB)
 
   
Maximum time to live in days: 61
 
   
Minimum time to live in minutes: 60
 
   
Web-Engine Revalidation Enabled.(default)
 
   
Web-Engine revalidation must-revalidate disabled.
 
   
Web-Engine Cache Range Fill Disabled.
 
   
ServiceEngine#
ServiceEngine# configure
ServiceEngine(config)# no web-engine cache http-body-read-buffer-size 50
ServiceEngine(config)# end
ServiceEngine# show web-engine all
HTTP heuristic age-multipliers: 30%
 
   
HTTP Body Read Buffer Size: 32 (KB)
Maximum time to live in days: 61
Minimum time to live in minutes: 60
Web-Engine Revalidation Enabled.(default)
Web-Engine revalidation must-revalidate disabled.
Web-Engine Cache Range Fill Disabled.
 
   
ServiceEngine#

Movie Streamer Scheduled Broadcast Playlist

The Movie SE Scheduled Broadcast Playlist feature allows multiple media files to be rebroadcast by a schedule in a single delivery service, so that new live channels can be generated. The sequence of all contents can now be seamlessly updated using the CDSM and APIs without impacting current rebroadcasting. In addition, multiple SE can be assigned to the rebroadcast delivery service for redundancy.


Note All media contents in the same Movie Streamer rebroadcast program must have the same encoding preset/profile.

All SEs assigned to the rebroadcast program and the CDSM must have the same NTP time.

Because all SEs assigned to the rebroadcast program send packets to the same specified multicast address, all SEs in the device group should be in different multicast domains.


API Change

A new media selection API was introduced to add, update and delete media files. The API adds or deletes one media file each time, and retrieves the media file to be added or deleted from the query string of the HTTPS request. To update the media files, specify a media list file that defines the final order of media files. The media files in the list should have the same media ID and number as the media list returned by getPrograms action of the List API.


Note When using the existing program API to modify a program with an XML file, the media list section must be exactly the same as the media list that is already configured. Use the existing List API to get the medias configured per program and insert them into the XML file following its schema.


SelectMedia API

A new API (/servlet/com.cisco.unicorn.ui.SelectMediaApiServlet) was added to serve the following media file operation requests:

addMedia—Adds a media file into a program.

updateMedia—Updates the order of media files in a program.

deleteMedia—Deletes a media file from a program.


Note All parameters except actions are case sensitive.


If the action parameter is missing or cannot be recognized, the API usage is returned to show all available actions and their API syntax.

addMedia File

Table 1 shows the parameters for the addMedia action. Use this action to add a media file at the end of a program's media list. Use the replication status API getContent action to get the prepositioned contents first, and then choose to add one of them to the program by the addMedia action.

Table 1 addmedia Parameters

Name
Description
Required
Value Type
Note

program

The program ID

Y

String

In format "PlayList_xxx", where xxx is an integer number.

deliveryService

The delivery service ID

Y

String

In format "Channel_xxx", where xxx is an integer number.

url

The file URL

Y

String

[protocol]://myhost/myfile.mp4 or //myserver/folder/myfile.mp4 Protocol can be HTTP, HTTPS or FTP.

updateMedia File

Table 2 shows the parameters for the updateMedia action. Use this action to update the order of media files in a program. This action applies to the media files returned by getProgram action of List API.

Table 2 updateMedia Parameters

Name
Description
Required
Value Type
Note

program

The program ID

Y

String

In format "PlayList_xxx", where xxx is an integer number.

Parameters needed by updateMedia:

Local Media List File

The media list file is mandatory and must be uploaded by posting as a multipart/form-data request. The Document Type Definition (DTD) for the media list file follows:

<?xml version="1.0"?>
<!DOCTYPE media_list[
<!ELEMENT media_list (media+)>
<!ELEMENT media EMPTY>
<!ATTLIST media
index CDATA #IMPLIED // List Order
id CDATA #IMPLIED // PlayList Media ID
>
]>

deleteMedia File

Table 3 shows the parameters for the deleteMedia action. Use this action to remove a media file from a program. Only the media file not in streaming can be removed.

Table 3 deleteMedia Parameters

Name
Description
Required
Value Type
Note

id

The Playlist Media file ID.

Y

String

In format "PlaylistMedia_xxx", where xxx is an integer number.

CLI Changes

The show program command is updated to display what files are currently playing. The following table displays the output of the show program program-id xxx command where the red text is the newly added information.

Source Media File: contents/ms/sample2.mov - 10.0.0.13\contents/ms/sample2.mov (Playing [4 secs/3 mins 22 secs])

This means the current broadcasting file is contents/ms/sample2.mov, whose duration is 3 minutes, 22 seconds, elapse time is 4 seconds and content origin is 10.0.0.13. [N/A /3 mins 22 secs] is displayed at the active play item initialization stage.

Unicast Access URL: rtsp://sr.os13.com/rlu2-ms-rebro.sdp

This means the unicast access URL of this program is rtsp://sr.os13.com/rlu2-ms-rebro.sdp.

Current Time : May 06 2011 @ 16:31:33 HKT (1304670693)
Program ID : 481
Program Name : rlu2-ms-rebro
Type : MS Managed Continuous Rebroadcast
Forwarder List : N/A
Schedules :
Schedule #1:
Start Time (loc) : Always started
End Time (loc) : N/A
Duration : Forever
Repeat : N/A
Repeatdays : N/A
Time spec : local
Source :
Source Media File : contents/ms/sample1.mov - 10.0.0.13\contents/ms/sample1.mov
Source Media File : contents/ms/sample2.mov - 10.0.0.13\contents/ms/sample2.mov 
(Playing [4 secs/3 mins 22 secs])
Source Media File : contents/ms/sample3.mov - 10.0.0.13\contents/ms/sample3.mov
Destination :
Unicast Access URL: rtsp://sr.os13.com/rlu2-ms-rebro.sdp
Multicast URL : http://sr.os13.com/mrlu2-ms-rebro.sdp
Multicast Address : 233.3.3.4:20000 233.3.3.4:20002
Start Time (loc) : Always started
Start Time : Always started
End Time (loc) : N/A
End Time : N/A
Current Status : Playing
Time left : N/A

Authorization Server Geo/IP Plugin Disable

The Authorization Server uses plug-in architecture to manage different authorization services. Geo-blocking plugin is one of the plugins managed by the Authorization Server.

Previously, for every client request, the plugin contacts a Geo-Location server to identify the geographical region of the client. The region is then validated against the region rules configured for the current delivery service. Generally, multiple SEs are associated with a delivery service, and the Geo-Location server is contacted for each SE in that delivery service to validate the region rules. However, contacting the Geo-Location server for every SE in the delivery service may not be cost effective.

Release 2.6.3 provides the option to disable contacting the Geo-Location server for particular SEs of a delivery service (for example, upstream SEs) that has the Geo/IP rules configured.

CLI Changes

The authsvr location-server command now includes the enable keyword to enable the geo-blocking plugin in an SE. The no authsvr location-server enable command disables the geo-blocking plug-in on an SE and allows all queries that are sent to the geo-block plug-in. The Authorization Server Geo-Location is disabled by default.

The show authsvr location-server command now displays the "Geo blocking is disabled" or "Geo blocking is enabled" in the output:

ServiceEngine# config
ServiceEngine(config)# no authsvr location-server enable
ServiceEngine(config)# exit
 
   
ServiceEngine# show authsvr location-server
Geo blocking is disabled
No Primary Location Server Configured
No Secondary Location Server Configured
Location-server timeout 691200
 
   
ServiceEngine# config
ServiceEngine(config)# authsvr location-server enable
ServiceEngine(config)# exit
 
   
ServiceEngine# show authsvr location-server
Geo blocking is enabled

CDSM GUI Changes

To disable the Authorization Server Geo/IP plugin on an SE, do the following:


Step 1 Log in to the CDSM GUI.

Step 2 Choose Devices > Devices > Service Control > Authorization Service. The Authorization Service page is displayed.

Step 3 Uncheck the Enable Geo Plugin check box.

Step 4 Click Submit.


This configuration option is also available for Device Groups.

Service Router

The following Service Router (SR) enhancements have been added to Release 2.6.3:

Unified Routing Table

Load Monitoring and Reporting

Unified Routing Table

The memory usage in the SR is very high when a large number of domains are used.

This feature uses one single global route context to hold route tables for SEs. When looking up the best SE for a request, the available SEs are checked to see if the SE is serving the domain for that request. Only the SEs subscribed to that domain are considered.


Caution Disabling the unified routing table increases the SIR's memory usage. Please make sure the memory usage does not exceed the recommended limit (1.5GB when SR is running without any load and configuration change).

CLI Changes

The [no] service-router unified-routing-table enable command was added to configure the global route table. This configuration is disabled by default, so that newly installed or systems upgraded to Release 2.6.3 have the same behavior as Release 2.6.1 or earlier.

The show service-router unified-routing-table command was added to display this configuration:

ServiceRouter# show service-router unified-routing-table
SR unified-routing-table not enabled
ServiceRouter# config
ServiceRouter(config)# service-router unified-routing-table enable
ServiceRouter(config)# exit
ServiceRouter# show service-router unified-routing-table
SR unified-routing-table enabled
 
   

Command output is changed for the show running-config command when the unified routing table is enabled:

ServiceRouter# show running-config
......
service-router unified-routing-table enable

Load Monitoring and Reporting

This enhancement monitors the aggregate load of a CDS network. It provides the following functionality:

Monitors the load of all SEs in the CDS network.

Monitors the load of all SEs assigned to a specific delivery service.

Raises alarms when the monitored load above exceeds a configurable threshold.

Aggregates load info of all SEs in the CDS network.

Has a web service interface to expose the CDS load and individual SE load.

The SR periodically aggregates the load info of all SEs in the CDS network. The aggregated load information is compared with the threshold configured and when the threshold value is exceeded, an alarm is raised on the SR. The alarms can also be configured to generate an SNMP trap.

SE load monitoring in the SR is disabled by default. Enable monitoring by configuring the monitor load type command. Change the default monitoring interval with the monitor interval configuration command.

The SR configuration also allows monitoring to be done for the aggregate load info of SEs assigned to a specific domain or all SEs in the CDS.

Two types of aggregation are supported in this release:

Average—The average device load of the SEs is considered as the aggregate load.

Maximum—The SE load that has the maximum value compared with other SEs is considered as the aggregate load.

CLI Changes

The service-router cds-monitor type device command was added to support the monitoring of aggregated CDS load. This command is used to configure the type of load that needs to be monitored. Only the device load is monitored. All monitor types are disabled by default.

The service-router cds-monitor sample-period <1-300 secs> command configures the sample period for monitoring the CDS load. The value range is 1-300 seconds and the default value is 2 seconds.

The service-router cds-monitor {domain <domainName> | all-ses} enable} command enables monitoring of aggregated CDS load. If the domainName option is configured, the aggregate load of the SEs subscribed to the domain is monitored. If the all-ses option is configured, the aggregate load value of all SEs in the CDS is monitored. Monitoring is disabled by default for both domain and all-ses.


Note If monitoring of domains or all-ses is enabled and the service-router cds-monitor type device command is not configured, no monitoring is done. Use this command to selectively disable monitoring of all-ses or any domain.


The service-router cds-monitor {domain <domainName> | all-ses} threshold device average <1-100>} command is used to configure the threshold of CDS load aggregated using average load of all SEs. The value range is 1-100 and the default value is 80. If the domainName option is configured, the average value of all SEs subscribed to the domain is used. If the domainName option is not configured, the average value of all SEs in the CDS is used.

The service-router cds-monitor {domain <domainName> | all-ses} threshold device maximum <1-100>} command is used to configure the threshold of CDS load aggregated using the maximum load of all SEs. The value range is 1-100 and the default value is 95. If the domainName option is configured, the maximum value of all SEs subscribed to the domain is used. If the domainName option is not configured, the maximum value of all SEs in the CDS is used.

Following is sample show running config:

service-router cds-monitor type device
service-router cds-monitor sample-period 3
 
   
service-router cds-monitor all-ses enable
service-router cds-monitor all-ses threshold device average 85
service-router cds-monitor all-ses threshold device maximum 96
 
   
service-router cds-monitor domain video.cds.com enable
service-router cds-monitor domain video.cds.com threshold device average 85
service-router cds-monitor domain video.cds.com threshold device maximum 85
 
   
service-router cds-monitor domain music.cds.com enable
service-router cds-monitor domain music.cds.com threshold device average 96
service-router cds-monitor domain music.cds.com threshold device maximum 96
 
   

The show service-router cds-monitor command was added to display CDS monitor-related configuration parameters.

Following is sample show command output:

Device Load Monitoring         : Enabled
Monitor Sample Period          : 3
 
   
Monitoring Of All SEs in CDS:
-----------------------------
 
   
Monitor Enable Status          : Enabled
Average Threshold              : 85
Maximum Threshold              : 96
 
   
Monitoring Of SEs in Domain:
----------------------------
 
   
----- Domain: music.cds.com -----
Monitor Enable Status          : Enabled
Average Threshold              : 96
Maximum Threshold              : 96
 
   
----- Domain: video.cds.com -----
Monitor Enable Status          : Enabled
Average Threshold              : 85
Maximum Threshold              : 85
 
   

CDSM GUI

To configure the sample period and enable monitoring of aggregated CDS load using the CDSM GUI, do the following:


Step 1 Log in to the CDSM GUI.

Step 2 Choose Devices > Service Router > General Settings > Notification and Tracking > CDS Monitor > General Settings. The CDSM Monitor General Settings page is displayed.

Step 3 Enter 1 in the Sample Period field.

Step 4 Check the Enabled the checkbox.

Step 5 Click Submit.

Step 6 Choose Devices > Service Router > General Settings > Notification and Tracking > CDS Monitor > Streamer Settings. The CDSM Monitor Streamer Settings page is displayed.

Step 7 Check the Enabled the checkbox.

Step 8 Enter 1 in the Device Average Threshold field.

Step 9 Enter 100 in the Device Maximum Threshold field.

Step 10 Click Submit.

Step 11 Choose Devices > Service Router > General Settings > Notification and Tracking > CDS Monitor > Domain Settings. The CDSM Monitor Domain Settings page is displayed showing the Domain Entries for the SR.


Transaction Logs

If transaction logging is enabled on the SR, the web service requests are logged. Following are sample transaction log entries for web service requests:

172.22.67.249 curl/7.12.1_(i386-redhat-linux-gnu)_libcurl/7.12.1_OpenSSL/0.9.7a_
zlib/1.2.1.2_libidn/0.5.6 2011-12-14 19:35:06 http://ksr/srwebsvc/seload?seName=
w13-cde200-1 HTTP - - 200 -
 
   
172.22.67.249 curl/7.12.1_(i386-redhat-linux-gnu)_libcurl/7.12.1_OpenSSL/0.9.7a_
zlib/1.2.1.2_libidn/0.5.6 2011-12-14 19:35:10 http://ksr/srwebsvc/cdsload HTTP -
 - 200 -
 
   
172.22.67.249 curl/7.12.1_(i386-redhat-linux-gnu)_libcurl/7.12.1_OpenSSL/0.9.7a_
zlib/1.2.1.2_libidn/0.5.6 2011-12-14 19:35:15 http://ksr/srwebsvc/cdsload?domain
Name=karthik.com HTTP - - 200 -

Error logs

All error messages is logged in errorlog/service_router_errorlog.

Alarms

Minor alarms are raised when the monitored load exceeds the average threshold or maximum threshold. The instance displays the domain name when the monitored load of the domain exceeds the threshold. The instance displays the string "cds" when the monitored load of all devices in the CDS exceeds the threshold.

Following is a portion of the show alarms output:

Minor Alarms:
-------------
     Alarm ID             Module/Submodule     Instance
     -------------------- -------------------- -------------------------
   1 CdsAvgThreshold      sr                   cds
 
   
   2 CdsMaxThreshold      sr                   cds
 
   
   3 CdsAvgThreshold      sr                   music.domain.com
 
   
   4 CdsMaxThreshold      sr                   videos.domain.com

Web Service Request Statistics

The statistics of a number of web service requests served by the SR can be obtained by entering the show statistics service-router summary command. The API value displays the web service request statistics.

ServiceRouter# show statistics service-router summary
 
   
Requests Received        :                 27
  HTTP Requests (normal) :                  0
  HTTP Requests (ASX)    :                  0
  HTTP Requests (API)    :                 27
  RTSP Requests          :                  0
  RTMP Requests          :                  0
  DNS Requests           :                  0
 
   
Requests Served          :                  0
  HTTP Requests Served   :                  0
 
   
Requests Redirected      :                 27
  HTTP 302 Redirects     :                  0
  ASX Redirects          :                  0
  HTTP API Redirects     :                 27
  RTSP redirects         :                  0
  RTMP redirects         :                  0
  DNS redirects          :                  0

APIs

API to Modify the Origin Server in a Delivery Service

The delivery service API has been enhanced to modify the content origin association on the specified delivery service without first deleting the existing delivery service.

CDSM GUI Changes

In Release 2.6.3, in the CDSM GUI on the Services > Delivery Services > Definition Page the `Content Origin' field is changed from read-only text field to editable drop down list to support the association change between the content origin and current delivery service.

Once the content origin assignment is changed, the CDSM updates the association in the local database and composes a database update messages for this change to notify all individual SE(s) that are assigned to this delivery service to update the association in their local database.

This notification triggers the following:

All programs subscribed on this particular delivery service update the R-FQDN based on the latest content origin automatically and immediately. Use the show programs program-id <program-id> command to verify this.

UNS at all individual SE(s) gets notification and updates the existing UNS entry with the latest O-FQDN. Use the show content url <origin-url> command to verify this, or check with the UNS logs under "/local1/errorlog/uns_errorlog*".

API Change

The modifyDeliveryService API was changed within ChannelApiServlet.

CDSM API Enhancement for File Management

CDSM GUI provides configuration file management functionalities for those features which have complex or a large number of configuration entries (e.g., Coverage Zone File, Geo/IP Plugin File, Rule File), or demand the flexibility to suit the dynamic change supposed to have in the later releases (e.g, NAS File, CDN Selector File).

The CDSM GUI provides uniform pages and operations to manage these functions. The File Management API provides the same functions as the GUI so that customers can automate the file operations.

The applyGeoIpFile action was also added. Table 4 shows the parameters for the new applyGeoIpFile action.

Table 4 applyGeoIpFile Parameters

Name
Description
Required
Value Type
Note

deliveryService

The delivery service ID.

Y

String

In format "Channel_xxx" where xxx is an integer number.

geoIpFile

The registered Geo/IP file ID / "none".

Y

String

"none" or FileInfo_yyy where yyy is an integer number.

CDSM API Changes

Release 2.6.3 provides better API support, including new APIs and changes to some existing API syntax.

New APIs

Three new actions are added into delivery service provisioning API (com.cisco.unicorn.ui.ChannelApiServlet):

createDeliveryServiceGenSettings

modifyDeliveryServiceGenSettings

deleteDeliveryServiceGenSettings

Table 5 shows the parameters for the new createDeliveryServiceGenSettings API.

Table 5 createDeliveryServiceGenSettings Parameters

Name
Description
Required
Value Type
Note

deliveryService

Delivery service ID.

Yes

String (Channel_231)

Bitrate

Maximum bitrate limit per session for HTTP.

Yes

Integer, range is 0-2000000

HashLevel

URL Hash Level for Cache Routing.

Yes

Integer, range is 0-10

TmpfsSize

Memory Cache Size.

Yes

Integer, range is 1-10

OsHttpPort

Origin Server HTTP Port (web-engine only, default 80).

Yes

Integer, range is 1-65535 except well known port numbers

ReadTimeout

HTTP Response Read Timeout.

Yes

Integer, range is 1-60

HttpAllow

Enable/Disable HTTP Download.

Optional

"true" or "false"

True means disable HTTP download.

ContentFlowTrace

Enable Content Flow Trace.

Optional

"true" or "false"

FilterTraceFlowToClient

Enable Filter Trace Flow to Client.

Optional

"true" or "false"

HttpExtAllow

Enable streaming over HTTP.

Optional

"true" or "false"

HttpExt

HTTP Allowed Extensions.

Optional

String

Invalid if "HttpExtAllow" is false.

GreenCookie

Outgoing Cookie.

Optional

String

EnableCacheError

Enable Error Response Caching.

Optional

"true" or "false"

CacheError

Cacheable Error Responses.

Optional

String

Invalid if "EnableCacheError" is false.

OSRedirectEnable

Optional

"true" or "false"

NrOfRedir

Optional

Integer, range is 1-3

Invalid if "OSRedirectEnable" is false.

EnableAbrLive

Disable File Caching on Disk.

Optional

"true" or "false"

True means disable file caching on disk.

SkipLL

Skip Location Leader Selection for Edge SE.

Optional

"true" or "false"

WmtUserAgent

WMT User Agent.

Optional

String

Table 6 shows the parameters for the new modifyDeliveryServiceGenSettings API.

Table 6 modifyDeliveryServiceGenSettings Parameters 

Name
Description
Required
Value Type
Note

deliveryService

Delivery service ID.

Required

String (Channel_231).

Bitrate

Maximum bitrate limit per session for HTTP.

Optional

Integer, range is 0-2000000.

HashLevel

URL Hash Level for Cache Routing.

Optional

Integer, range is 0-10.

TmpfsSize

Memory Cache Size.

Optional

Integer, range is 1-10.

OsHttpPort

Origin Server HTTP Port (web-engine only, default 80).

Optional

Integer, range is 1-65535 except well known port numbers.

ReadTimeout

HTTP Read Timeout.

Optional

Integer, range is 1-60.

HttpAllow

Enable/Disable HTTP Download.

Optional

"true" or "false"

True means disable HTTP download.

ContentFlowTrace

Enable Content Flow Trace.

Optional

"true" or "false"

FilterTraceFlowToClient

Enable Filter Trace Flow to Client.

Optional

"true" or "false"

HttpExtAllow

Enable streaming over HTTP.

Optional

"true" or "false"

HttpExt

HTTP Allowed Extensions.

Optional

String

Invalid if "HttpExtAllow" is false.

GreenCookie

Outgoing Cookie.

Optional

String

EnableCacheError

Enable Error Response Caching.

Optional

"true" or "false"

CacheError

Cacheable Error Responses.

Optional

String

Invalid if "EnableCacheError" is false.

OSRedirectEnable

Optional

"true" or "false"

NrOfRedir

Optional

Integer, range is 1-3

Invalid if "OSRedirectEnable" is false.

EnableAbrLive

Disable File Caching on Disk.

Optional

"true" or "false"

True means disable file caching on disk.

SkipLL

Skip Location Leader Selection for Edge SE.

Optional

"true" or "false"

WmtUserAgent

WMT User Agent.

Optional

String

Table 7 shows the parameters for the new deleteDeliveryServiceGenSettings API.

Table 7 deleteDeliveryServiceGenSettings Parameters

Name
Description
Required
Value Type
Note

deliveryService

Delivery service ID.

required

String (Channel_231).

API Changes

Table 8 shows the new "deliveryQos" parameter that was added for:

com.cisco.unicorn.ui.ChannelApiServlet?action=createDeliveryService

com.cisco.unicorn.ui.ChannelApiServlet?action=modifyDeliveryService&deliveryService

Table 8 New deliveryQos Parameter

Name
Description
Required
Value Type
Note

deliveryQos

Delivery Services > Definition > Qos value for content delivery.

Optional

Integer (range, 0-63).

Table 9 shows the new "se_enable_primed" parameter that was added for the com.cisco.unicorn.ui.ChannelApiServlet?action=assignSEs.

Table 9 New se_enable_primed Parameter

Name
Description
Required
Value Type
Note

se_enable_primed

When assigning SE to a delivery service, enable the "primed" option.

Optional

String (all or SE ID list).

all | <se_ID>, <se_ID>...

Table 10 shows the new "quota" parameter that was added for:

com.cisco.unicorn.ui.ChannelApiServlet?action=createDeliveryService

com.cisco.unicorn.ui.ChannelApiServlet?action=modifyDeliveryService&deliveryService

Table 10 New quota Parameter

Name
Description
Required
Value Type
Note

quota

Delivery Service quota.

Optional

Integer

The "quota" parameter was removed from:

com.cisco.unicorn.ui.ChannelApiServlet?action=addManifest

com.cisco.unicorn.ui.ChannelApiServlet?action=modifyManifest.

Platform

The following Platform enhancements have been added to Release 2.6.3:

Proper Disk Shutdown

Disk Latent Sector Failure Handling

Improved Error Handling

MegaRAID Support

Proper Disk Shutdown

An unsafe disk shutdown might cause data corruption, data loss and other disk errors. A disk must be issued a specific command (STANDBY_IMMEDIATE ATA command) prior to removing power so that it has enough time to prepare for a power down. Drives with write cache need to copy local buffers to persistent memory while drives with moving parts need to safely halt them to prevent damage.

Solid State Drives (SSDs) are more prone to failure because of unsafe disk shutdown than Hard Disk Drives (HDDs). This feature provides a driver independent solution to safely shutdown both SSDs and HDDs running on hardware platforms that support the STANDBY_IMMEDIATE command.

The Safe Disk Shutdown requirements are as follows:

Safely shutdown all disks during system shutdown through the shutdown poweroff command.

Safely shutdown a disk by executing disk unuse <diskXX> command.


Note This feature does not safely shutdown Internal SSDs connected to a megaRAID controller.



Note Do not physically remove a disk from the bay without first issuing the disk unuse <diskXX> command or without shutting down the system using shutdown poweroff command or the disk may be severely damaged.


CLI Changes

Because the disk unuse command powers down a disk, old procedures involving disk unuse cannot be used in the same way. For example, a disk cannot be unused and then erased anymore. This is because it already has been shutdown after unuse. Simply running a disk erase would suffice.

Table 11 shows all the command changes for this feature.

Table 11 disk Command Changes 

Function
Old Commands/Procedure
New Command/Procedure Changes

Unuse disk

1. disk unuse <diskXX>

2. Disk does not appear as "missing".

1. disk unuse <diskXX>

2. Disk is powered off and appears as "missing" until the disk policy apply command is executed.

Erase disk

1. disk unuse <diskXX>

2. disk erase <diskXX>

3. disk policy apply <diskXX>

1.

2. disk erase <diskXX>

3. disk policy apply <diskXX>

Erase disk with unuse disk submenu

1. disk unuse <diskXX>

2. disk unuse <diskXX> erase-partitions

1. disk unuse <diskXX> erase-partitions

Additional user prompt after erasing: Prepare disk for safe removal? Upon a positive response, disk is powered off.

Secure erase disk (for SSDs)

New command.

1. disk erase <diskXX> secure

2. disk policy apply <diskXX>

Disk already marked bad

1. disk mark good <diskXX>

2. disk unuse <diskXX>

1. disk unuse <diskXX>

This clears all statistics related to a bad drive just like the disk mark good command.

Disk policy apply

disk policy apply

disk policy apply

May report the presence of corrupted or unresponsive disks.


Disk Latent Sector Failure Handling

Beginning with release 2.6.3, the ability of the CDS-IS system to detect, report and recover from disk related sector I/O errors (also known as Latent Sector Errors or LSEs) has been significantly improved. Following is a list of the improvements:

Improve application level error-recovery.

Protocol engines pro-actively delete "errored" or corrupt content.

Increase total disk uptime (availability) and capacity utilization for CDNFS.

Optimize the disk alarm reporting experience for the end user.

Introduce an automated disk repair (background) mechanism.

Improved Error Handling

As mentioned above, CDS-IS applications (Protocol Engines) now proactively delete corrupt content. Because of this, the system can tolerate a higher level of faulty sectors.

Once content has been deleted, any corresponding errored sectors effectively "wait" to be repaired. Sectors are repaired when they are subsequently overwritten (as a result of their being re-allocated to new cached content). The disk drive itself repairs sectors and remaps them to a spare sector pool.

Sectors are considered "Active" if they continue to be accessed within the "Bad Sectors Monitoring Period" (default 24 hours). If an errored sector is not accessed within this period, it transitions to an "Inactive" state. "Inactive" sectors do not contribute to overall LSE error-threshold monitoring; therefore, such errored sectors cannot cause a drive to be marked bad.

Deferred Alarming

Bad Sector Alarm

Prior to release 2.6.3, when a sector I/O error is detected by the Internet Streamer CDS platform health monitor (sysmon), a "badsector" alarm is raised against the corresponding disk itself. This occurs immediately, even if a single sector error exists on the drive. This can be problematic because sector errors occur during the lifetime of a disk.

Starting with release 2.6.3, the "badsector" alarm is no longer immediately raised (it is deferred until the number of bad sectors exceeds a new LSE error-threshold). The following new LSE error-threshold command has been added to manage the "badsector" alarm:

ServiceEngine(config)# disk error-handling threshold alarm-bad-sectors threshValue
 
   

The default threshold for the "badsector" alarm is set to 15 errored sectors.

Disk Failure Alarm

Once the number of LSEs exceeds the configured LSE error-thresholds, the disk is marked bad and sysmon raises a separate "disk_failure" alarm against the drive.

Because of the automatic sector repair employed by release 2.6.3, CDS-IS software can tolerate a higher level of LSEs. This allows both of the "LSE error-thresholds" to (potentially) be increased, thereby deferring marking a disk bad until the higher LSE threshold(s) are exceeded.The following table documents the changes made to the LSE error-thresholds for release 2.6.3.

Table 12 LSE Error-Thresholds

LSE Threshold
Description
2.6.1 Value
2.6.3 Value

bad-sectors

Number of unique "active" bad sectors allowed before marking a disk bad. These sectors can transition to "inactive" if their "age" exceeds the Bad Sectors Monitoring Period.

15

30

errors

Total number of I/O errors allowed across all bad sectors before marking a disk bad. This is a fail-safe mechanism that prevents an application that is not repairing errors from indefinitely generating I/O errors.

The threshold limit currently applies to both HDDs and SSDs.

500

500

Spared (Remapped) Sectors List

When the number of spared (re-mapped and/or "grown") sectors exceeds an application specific "Remapped Sectors Error-Threshold" of the total available spare pool size, the drive is considered non-functional and taken off-line. For a 500 GB drive, there are typically ~ 2000 spare sectors.

The SMART error-threshold for this attribute (Reallocated_Sector_Ct) was lowered to 5% when polling the SMART statistics. If this threshold is exceeded, then a specialized "SMARTinfo" alarm is raised:

ServiceEngine# show alarms minor detail
 
   
Minor Alarms:
-------------
     Alarm ID             Module/Submodule     Instance
     -------------------- -------------------- -------------------------
    3 disk_SMARTinfo       sysmon               disk08
       Apr 28 09:01:31.584 PDT, Equipment Alarm, #000002, 1000:445004
       Disk minor early-detection error occurred on disk08:
       Excessive remapped sectors detected; disk replacement recommended

CLI Changes

The show disks error-handling command was enhanced to show the breakdown between Active and Inactive errored sector states:

ServiceEngine# show disks error-handling details
disk05: [GOOD] Total bad sectors = 1, total I/O errors = 2
     disk05: sector (LBA): 3000005      I/O errors: 2   (Active)
 
   
disk10: [FAIL] Total bad sectors = 3, total I/O errors = 712 
        disk10: sector (LBA): 16000        I/O errors: 300 (Active)
        disk10: sector (LBA): 170001       I/O errors: 410 (Inactive)
        disk10: sector (LBA): 180001       I/O errors: 2   (Active)
 
   
Total failed disks = 1
 
   

For additional disk health statistics, execute the following commands:

ServiceEngine# show disks SMART-info
ServiceEngine# show alarms
 
   

The disk error-handling threshold alarm-remapped-sectors <threshValue> command was added so that the Remapped Sectors Error-Threshold can be tunable.

Because there does not appear to be a way to programmatically query the total available spare pool size, <threshValue> must be specified as an absolute number of sectors. A default value of 128 is used for HDDs. Because SSDs can tolerate a much higher level of remapped sectors without a performance impact, the default driver SMART limit is used.

The following existing commands have been modified for this feature:

ServiceEngine(config)# disk error-handling threshold bad-sectors <threshValue>
ServiceEngine(config)# disk error-handling threshold errors <threshValue>
ServiceEngine# show disks error-handling details
 
   

The following new commands have been added for this feature:

ServiceEngine(config)# disk error-handling threshold alarm-bad-sectors <threshValue>
ServiceEngine(config)# disk error-handling threshold alarm-remapped-sectors <threshValue>
ServiceEngine(config)# disk error-handling bad-sectors-mon-period <minutes>

MegaRAID Support

The current MegaRAID controller has reliability issues, so it has been upgraded to the 9261-8i PCI Express SAS 6 Gb/s card for Release 2.6.3. The 9261-8i has an improved on-board Battery Backup Unit (BBU) (model iBBU08), which operates reliably over a wider ambient temperature range. The new MegaRAID 9261-8i is installed into the CDE250 2S6, 2S8, 2S9, and 2S10 platforms at manufacturing time.

Proximity Engine, BGP MIB Support

Release 2.6.3 software supports sending BGP-4 traps outlined in the BGP-4 MIB. The BGP component sending out traps populates the dataserver with the entries required for the trap, and the SNMP component constructs and sends out the trap based on the dataserver entry.

The BGP component populates two dataserver items for the two traps that are supported as part of this feature. The namespace is defined in $UNICORN/sg/cisco/base/cli/include/bgp_ns.h:

# define BGP_NS_TRAP_SUBTREE             "/stat/sg/bgp/traps/"
# define BGP_NS_TRAP_ESTABLISHED         "/stat/sg/bgp/traps/established"
# define BGP_NS_TRAP_BACKWARD            "/stat/sg/bgp/traps/backward"
 
   

The dataserver values for these entries are defined in the $UNICORN/sg/cisco/base/cli/include/bgp_traps.h file, which is a new file created for this feature.

typedef struct {
  char          peer_addr[INET6_ADDRSTRLEN];
  uint32_t      state;
  uint8_t       bgp_peer_last_error[2];
} bgp_trap_established_t;
 
   
typedef struct {
  char          peer_addr[INET6_ADDRSTRLEN];
  uint32_t      state;
  uint8_t       bgp_peer_last_error[2];
} bgp_trap_backward_t;
 
   

The following two macros are also defined in this header file:

# define BGP_TRAP_ESTABLISHED_SIZE sizeof(bgp_trap_established_t)
# define BGP_TRAP_BACKWARD_SIZE sizeof(bgp_trap_backward_t)

Other Enhancements

The following additional enhancements have been added to Release 2.6.3:

Lengthy URL Content in Content Manager

DirNode Limits

Prepositioning Content

Cached Contents

Interface Mapping CLI Changes

tcpdump Enhancements

contentmgr delivery-service Command

Lengthy URL Content in Content Manager

In calculating the maximum length of the URL (2048 characters), an MD5 hash must be considered as part of the overall URL length, and therefore the maximum length of the URL should not exceed 2028 characters. (CSCtx07074)

DirNode Limits

Due to larger memory footprint of DirNode, the Content Manager cannot afford to have too many DirNodes in the system. Therefore, when the number of DirNode exceeds the limit (1 million), the Content Manager starts evicting files. It is the similar procedure when dealing with object count eviction.

Prepositioning Content

In Release 2.6.3, if the "Origin Server HTTP Port" value of the delivery service is changed to a non-default value (other than 80), use the following method of prepositioning contents from the Origin server. (CSCtx67261)

in the CDSM GUI on the Services > Delivery Services > Delivery Service Content Page, add Content Items, including the port number of the Origin server's HTTP port. In the following example the non-default port number is configured as 99, so include that port in the URL:

http://3.22.0.10:99/cds-ims-64.bin
http://3.22.0.10:99/powered_by_100.wmv
 
   

This is slightly different from the usual way of configuring URLs. Also, use the wget with the port number of the Origin server's HTTP port, for example:

wget http://3.22.0.10:99/powered_by_100.wmv

Cached Contents

In Release 2.6.3 cached contents are marked as incomplete and status 2 always. (CSCtx94994)

Do the following to check the cached contents:


Step 1 Start Cache miss requests for .mbr contents.

Step 2 Make sure WMPlayer plays the streaming without any issues.

Step 3 Check the details of the cached contents and observe that all cached contents are marked as incomplete by issuing the following command:

ServiceEngine# show content url <url>
 
   
CAL content object attributes:
	URL: http://X.XXX.XXX.XX/fastcal_sanity/mbr.wmv
	Status is 2 (Servable)
	Content is Incomplete
	File size is 16 Bytes
	Playable by WMT 
	Content is CACHED
 
   

You can also use the detail option to see more information.


Interface Mapping CLI Changes

In Release 2.6.3 three new commands were introduced that enable a user to view a table in admin-shell showing the mapping between a Cisco style higher-level interface ID and a Linux interface ID. (CSCtr46826)

The new commands are:

show hardware mapping interface all

show hardware mapping interface GigabitEthernet

show hardware mapping interface TenGigabitEthernet

The output is shown below:

ServiceEngine# show hardware ?
  all      Display all hardware class information
  core     Display core hardware information
  dmi      Display Desktop Management Interface (DMI) information
  mapping  Show mapping between Cisco and Linux hardware names
  |        Output Modifiers
  <cr>
ServiceEngine# show hardware mapping ?
  interface  Map Cisco interface name to Linux device name
ServiceEngine# show hardware mapping interface ?
  all                 Display all interface information
  GigabitEthernet     Select a 1G ethernet interface
  TenGigabitEthernet  Select a 10G ethernet interface
EE7-2S3-3# show hardware mapping interface all
GigabitEthernet 1/0     eth0
GigabitEthernet 2/0     eth1
GigabitEthernet 3/0     eth2
GigabitEthernet 4/0     eth3
GigabitEthernet 5/0     eth4
GigabitEthernet 6/0     eth5
GigabitEthernet 7/0     eth6
GigabitEthernet 8/0     eth7
GigabitEthernet 9/0     eth8
GigabitEthernet 10/0    eth9
GigabitEthernet 11/0    eth10
GigabitEthernet 12/0    eth11
GigabitEthernet 13/0    eth12
GigabitEthernet 14/0    eth13
 
   
ServiceEngine# show hardware mapping interface GigabitEthernet 1/0
eth0

tcpdump Enhancements

Release 2.6.3 introduces a new tcpdump interface alias and the tcpdumpx command.

tcpdump Interface Alias

Current: tcpdump -i eth0

Implemented: "tcpdump -i GigabitEthernet 1/0" and "tcpdump -i eth0" give same result.

"tcpdump -i PortChannel 1" and "tcpdump -i bond0" give same result.

tcpdumpx Command

A new tcpdumpx command in admin-shell enables tcpdump to capture multiple interfaces in separate files. Each member interface of a PortChannel can be captured in a separate file. For example, if eth2, eth3, eth4 and eth5 are members of PortChannel 1 (bond0), they can be captured in different files (see example below).

Current: issue "tcpdump -i" for each PortChannel member in a different shell at the same time.

Implemented: New flag (-j), not used by tcpdump, under tcpdumpx handles this:

tcpdumpx -j PortChannel 1 -w filename.cap
 
   

This command internally expands to capture each physical interface's dump in an individual file:

tcpdump -i eth2 -w filename.eth2.cap
tcpdump -i eth3 -w filename.eth3.cap
tcpdump -i eth4 -w filename.eth4.cap
tcpdump -i eth5 -w filename.eth5.cap
 
   

If eth2 and eth3 need to be captured, use "--" as a command separator to separate the two tcpdump instances:

tcpdumpx -i eth2 -w filename.cap -k -m -- -i eth3 -w filename2.cap -c -k -- ... --
 
   

This command internally expands to:

tcpdump -i eth2 -w filename.cap 
tcpdump -i eth3 -w filename.cap
 
   

Other examples:

tcpdumpx -j PortChannel 1 -w filename.cap -- -j PortChannel 2 -w filename2.cap
tcpdumpx -i eth2 -w filename.cap -- -i eth3 -w filename2.cap -- j PortChannel 1  -w 
filename3.cap 
 
   

This is documented in tcpdumpx help "tcpdumpx -h":

tcpdump                   Dump traffic on a network
tcpdumpx                 tcpdump extension for multi-interface capture
tcpdumpx -h
tcpdumpx - tcpdump extension for multiple interface capture
[WARNING] This program consumes HIGH CPU & memory and impacts system performance
 
   
Usage: tcpdumpx [-w filename] [-j PortChannel X] [--] [all tcpdump options]
 
   
  [-w filename]         Required. Write tcpdump output to filename
  [-j PortChannel X]    Capture each PortChannel slave to file:
                        "filename" --> "filenameslavename"
                        "filename.xxx"   --> "filename.slavename.xxx"
  [--]                  Interface seperator. Capture Multiple Interfaces by:
                        tcpdumpx -i eth0 -w eth0 -- -i eth2 -w eth2 -- ... -- ..
                        tcpdumpx -i eth0 -w eth0 -- -j PortChannel 1 -w pc
                        tcpdumpx -j PortChannel 1 -w pc1 -- -j PortChannel 2
                        -w pc2
  [all tcpdump options] Specify any tcpdump options
                        Please use "tcpdump -h" to get tcpdump help options
  [-h(elp)]             Print this help

contentmgr delivery-service Command

In Release 2.6.3, you can configure how fast to check to evict those contents after delivery service removal. You can also turn this feature off by putting a "0" as the argument, so that no content is evicted after delivery service removal.

CLI Changes

The delivery-service keyword was added to the contentmanager command. The full syntax of this command is:

ServiceEngine(config)# contentmgr delivery-service cache-content purge-on-delete ?
  <0-1440>  Purge after minutes[0 means not deleting]

System Requirements

The Internet Streamer CDS runs on the CDE205, CDE220, and the CDE250 hardware models.

Table 13 lists the different device modes for the Cisco Internet Streamer CDS software, and which CDEs support them.

Table 13 Supported CDEs

Device Mode
CDE205
CDE220-2G2
CDE220-2S3i
CDE250-2S6
CDE250-2M0

CDSM

Yes

No

No

No

No

SR

Yes

Yes

No

No

No

SE

Yes

Yes

Yes

Yes

Yes

SR—Proximity Engine standalone

Yes

Yes

No

No

No


CDE250-2S6 and CDE250-2M0 platforms have four interfaces at 10 gigabit Ethernet speeds and four interfaces at gigabit Ethernet speeds (plus two additional gigabit ethernet interfaces for management).

The CDE220-2S3i platform has a total of 14 gigabit Ethernet ports in this CDE. The first two ports (1/0 and 2/0) are management ports. The remaining 12 gigabit Ethernet ports can be configured as two port channels. See the Cisco Content Delivery Engine CDE205/220/250/420 Hardware Installation Guide for set up and installation procedures for the CDE220-2S3i and the Cisco Internet Streamer CDS 2.6 Software Configuration Guide for information on configuring the Multi Port Support feature.

The CDE220-2G2 platform has a total of ten gigabit Ethernet ports. The first two ports (1/0 and 2/0) are management ports. The remaining eight gigabit Ethernet ports can be configured as one port channel. See the Cisco Content Delivery Engine CDE205/220/250/420 Hardware Installation Guide for set-up and installation procedures for the CDE220-2G2.

The CDE205 can run as the CDSM, SR or SE. See the Cisco Content Delivery Engine CDE205/220/250/420 Hardware Installation Guide for set-up and installation procedures for the CDE205.


Note For performance information, see the release-specific performance bulletin.


Limitations and Restrictions

This release contains the following limitations and restrictions:

There is a 4 KB maximum limit for HTTP request headers. This has been added to prevent client-side attacks, including overflowing buffers in the Web Engine.

Standby interface is not supported for Proximity Engine. Use port channel configuration instead.

There is no network address translation (NAT) device separating the CDEs from one another.

Do not run the CDE with the cover off. This disrupts the fan air flow and causes overheating.


Note The CDS does not support network address translation (NAT) configuration, where one or more CDEs are behind the NAT device or firewall. The workaround for this, if your CDS network is behind a firewall, is to configure each internal and external IP address pair with the same IP address.

The CDS does support clients that are behind a NAT device or firewall that have shared external IP addresses. In other words, there could be a firewall between the CDS network and the client device. However, the NAT device or firewall must support RTP/RTSP.


System Limits and Thresholds

This release has the following limits and thresholds:

Service Router Limits and Thresholds

Service Monitor Limits and Thresholds

Web Engine Limits and Thresholds

CDSM Limits and Thresholds

RTSP Gateway and Movie Streamer

Windows Media Streaming

Flash Media Streaming

Service Router Limits and Thresholds

The Service Router has memory-related limits and thresholds. Memory usage of the Service Router depends on the number of coverage zone entries, the number of Content Origin servers, the distribution of subnets in the Coverage Zone file, and the number of Service Engines in the CDS. From our tests using a sample Coverage Zone file, we have observed that we can support 20,000 Coverage Zone entries with 26 SEs, and 40 Content Origins servers.


Note The number of Coverage Zone entries, SEs, and Content Origin servers are subject to change depending on the Coverage Zone configured.

We recommend keeping the memory usage (both virtual and resident) below 1.5 GB.


Frequent configuration updates could cause memory fragmentation, which raises the memory usage.

Service Monitor Limits and Thresholds

When the Service Monitor thresholds are exceeded, an alarm is raised on the respective device and an SNMP trap is sent to the CDSM. The parameters monitored and thresholds for each component or protocol engine can be modified. The default thresholds are as outlined below.

Following are the parameters that are monitored on each device (SE, SR, and CDSM) and the default threshold setting of each parameter:

CPU—80 percent

Memory—80 percent

Kernel memory—50 percent

Disk usage—0 percent

Disk failures—75 percent

Augmentation alarms—80 percent

Following are the parameters that are monitored only on the SE, along with default threshold setting of each parameter:

Windows Media Streaming thresholds—90 percent

Flash Media Streaming thresholds—90 percent

Movie Streamer—90 percent%

Maximum number of concurrent sessions—200

Maximum Bandwidth—200,000 kbps

NIC bandwidth—90 percent

Burst Count—1

Web Engine Limits and Thresholds

The Web Engine has the following limits and thresholds:

Memory Usage

Session Limits

CAL Limits

Memory Usage

In Release 2.5.9, the memory threshold on each SE is 3.2 GB. If the threshold is exceeded, the memory_exceeded alarm is raised and trickle mode is enabled. In Release 2.5.9, the admission control is based on 30,000 session and 3.2 GB of memory.

In Release 2.6.1, the memory threshold on each SE is 3.2 GB. If the threshold is exceeded, the memory_exceeded alarm is raised. In cases where the memory reaches 3.7 GB, trickle mode is enabled and eventually the Web Engine is restarted. The above memory values, and the 20,000-60,000 sessions and 100,000 open file/socket descriptor (FD) limit are used for admission control in Release 2.6.1.

Session Limits

Web Engine supports the following session-threshold limits:

49,800 session count for the CDE250

15,000 session count for all other CDEs

The max_session_exceeded alarm is raised if the session-threshold limit is reached. If further requests are sent to the SE even when the session threshold is reached, the Web Engine attempts to process the requests but does not accept any more requests when the request count reaches 60,000 on a CDE250, and 20,000 on all other CDEs.

CAL Limits

Outstanding CAL Lookup threshold is 25,000 on the CDE250 and 15,000 on all other CDEs. The WebCalLookupThreshold alarm is raised on reaching this threshold limit.

Outstanding CAL disk Write threshold is 3,000 CAL requests (create, update, delete, popularity update) on the CDE250, and 1,500 on all other CDEs. The WebCalDiskWriteThreshold alarm is raised on reaching this threshold.

Other CAL thresholds are as follows:

File Descriptor usage threshold is 85 percent

TEMPFS usage threshold is 80 percent

Active datasource threshold is 2,000


Note CAL-related thresholds and the File Descriptor-related thresholds are introduced in Release 2.6.1.

Web Engine thresholds are also applicable to adaptive bit rate (ABR) streaming.


CDSM Limits and Thresholds

The CDSM has the following limits and thresholds:

RPC Connections

File Synchronization

CDSM Availability (primary and standby)

SE Configuration Change Synchronization

RPC Connections

A maximum of 40 RPC connections are supported among the managed devices (SE, SR, standby CDSM, and primary CDSM). The RPC connection maximum is defined in the httpd.conf.rpc configuration file located in the /state directory.

File Synchronization

The primary CDSM checks for file updates and synchronization with the managed devices (SE, SR, and standby CDSM) every ten minutes.

CDSM Availability (primary and standby)

The SE and SR check for the availability of the primary and standby CDSM on a regular interval; however, if the CDSM does not respond, the SE and SR use an exponential-backoff call for retrying the connection.

The exponential backoff call means that if the CDSM does respond to the first attempt, the SE or SR sleep for ten seconds before trying again. If the second attempt does not succeed, the wait time doubles (20 seconds), if that attempt does not succeed, the wait time doubles again (40 seconds). The wait time doubles every attempt (10, 20, 40, 80, and so on) until the maxWaitingTime of 320 seconds.

SE Configuration Change Synchronization

The period of time before the local configuration manager (LCM) on an SE sends a configuration change to the primary CDSM is a maximum of 2.25 times the polling rate. The polling rate is configurable through the CDSM GUI (System > Configuration > System Properties, System.datafeed.pollRate).

RTSP Gateway and Movie Streamer

The default RTSP Gateway transactions per second (tps) is 40. There are no other limits to the RTSP Gateway.

The Movie Streamer default maximum concurrent session is 200 and the default maximum bandwidth is 200 Mbps.

Windows Media Streaming

Windows Media Streaming has the following limits and thresholds:

Windows Media Streaming recommended concurrent remote server sessions 300


Note Regarding concurrent remote server sessions, if all requests are unique cache-miss cases, Windows Media Streaming can reach up to 1000 sessions of 1 Mbps file each. Windows Media Streaming can sustain 1000 remote server sessions at most if the Content Origin server can respond, but the recommended value is 300.


Windows Media Streaming transactions per second is 40 (because of the RTSP Gateway limitation).

Memory threshold 3 GB

CPU threshold is 80 percent

Flash Media Streaming

With the basic license, Flash Media Streaming the default maximum concurrent sessions is 200 and the default maximum bandwidth is 200 Mbps.

Buying more licenses can increase the concurrent sessions and maximum bandwidth as follows:

CDE220-2G2 and CDE220-2S3—15,000 concurrent sessions and 8 Gbps maximum bandwidth

CDE250-2M0—40,000 concurrent sessions and 40 Gbps maximum bandwidth

We recommend that the Flash Media Streaming process memory usage not exceed 3 GB resident set size (RSS). If the memory usage for Flash Media Streaming exceeds 3 GB RSS, a threshold exceeded alarm is raised.


Note RSS is the portion of a process that exists in physical memory (RAM), as opposed to virtual memory size (VSIZE), which includes both RAM and the amount in swap. If the device has not used swap, the RSS number is equal to VSIZE.


Important Notes

To maximize the content delivery performance of a CDE205, CDE220, or CDE250, we recommend you do the following:

1. Use port channel for all client-facing traffic.

Configure interfaces on the quad-port gigabit Ethernet cards into a single port-bonding interface. Use this bonding channel, which provides instantaneous failover between ports, for all client-facing traffic. Use interfaces number 1 and 2 (the two on-board Ethernet ports) for intra-CDS traffic, such as management traffic, and configure these two interfaces either as standby or port-channel mode. Refer to the Cisco Internet Streamer CDS 2.6 Software Configuration Guide for detailed instruction.

2. Use the client IP address as the load balancing algorithm.

Assuming ether-channel (also known as port-channel) is used between the upstream router/switch and the SE for streaming real-time data, the ether-channel load balance algorithms on the upstream switch/router and the SE should be configured as "Src-ip" and "Destination IP" respectively. Using this configuration ensures session stickiness and general balanced load distribution based on clients' IP addresses. Also, distribute your client IP address space across multiple subnets so that the load balancing algorithm is effective in spreading the traffic among multiple ports.


Note The optimal load-balance setting on the switch for traffic between the Content Acquirer and the edge Service Engine is dst-port, which is not available on the 3750, but is available on the Catalyst 6000 series.


3. For high-volume traffic, separate HTTP and WMT.

The CDE205, or CDE220 performance has been optimized for HTTP and WMT bulk traffic, individually. While it is entirely workable to have mixed HTTP and WMT traffic flowing through a single server simultaneously, the aggregate performance may not be as optimal as the case where the two traffic types are separate, especially when the traffic volume is high. So, if you have enough client WMT traffic to saturate the full capacity of a server, we recommend that you provision a dedicated server to handle WMT; and likewise for HTTP. In such cases, we do not recommended that you mix the two traffic types on all CDE servers which could result in suboptimal aggregate performance and require more servers than usual.

4. For mixed traffic, turn on the HTTP bitrate pacing feature.

If your deployment must have Streamers handle HTTP and WMT traffic simultaneously, it is best that you configure the Streamer to limit each of its HTTP sessions below a certain bitrate (for example, 1Mbps, 5Mbps, or the typical speed of your client population). This prevents HTTP sessions from running at higher throughput than necessary, and disrupting the concurrent WMT streaming sessions on that Streamer. To turn on this pacing feature, use the HTTP bitrate field in the CDSM Delivery Service GUI page.

Please be aware of the side effects of using the following commands for Movie Streamer:

Config# movie-streamer advanced client idle-timeout <30-1800>
Config# movie-streamer advanced client rtp-timeout <30-1800>
 
   

These commands are only intended for performance testing when using certain testing tools that do not have full support of the RTCP receiver report. Setting these timeouts to high values causes inefficient tear down of client connections when the streaming sessions have ended.

For typical deployments, it is preferable to leave these parameters set to their defaults.

5. For ASX requests, when the Service Router redirects the request to an alternate domain or to the origin server, the Service Router does not strip the .asx extension, this is because the .asx extension is part of the original request. If an alternate domain or origin server does not have the requested file, the request fails. To ensure requests for asx files do not fail, make sure the .asx files are stored on the alternate domain and origin server.

Open Caveats

The open caveats section has the following subsections:

Open Caveats in Release 2.6.3-b50

Open Caveats in Release 2.6.3-b47

Open Caveats in Release 2.6.3-b45

Open Caveats in Release 2.6.3-b39

Open Caveats in Release 2.6.3-b35

Open Caveats in Release 2.6.3-b32

Open Caveats in Release 2.6.3-b26

Open Caveats in Release 2.6.3-b23

Open Caveats in Release 2.6.3-b50

There are no new open caveats in release 2.6.3-b50.

Open Caveats in Release 2.6.3-b47

There are no new open caveats in release 2.6.3-b47.

Open Caveats in Release 2.6.3-b45

There are no new open caveats in release 2.6.3-b45.

Open Caveats in Release 2.6.3-b39

There are no new open caveats in release 2.6.3-b39.

Open Caveats in Release 2.6.3-b35

There are no new open caveats in release 2.6.3-b35.

Open Caveats in Release 2.6.3-b32

There are no new open caveats in release 2.6.3-b32.

Open Caveats in Release 2.6.3-b26

There are no new open caveats in 2.6.3-b26.

Open Caveats in Release 2.6.3-b23

Release 2.6.3-b23 contains the following open caveat:

Service Router

CSCty71678

Symptom:

TCP connection half-closed when Quova server restarts.

Condition:

If Quova server restarted when the SR is processing a request, the SR skips location routing and falls back to the next routing method.

Workaround:

SR re-establishes the TCP connection to Quova later when another request needs to be sent.

Resolved Caveats

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

The resolved caveats section has the following subsections:

Resolved Caveats in Release 2.6.3-b50

Resolved Caveats in Release 2.6.3-b45

Resolved Caveats in Release 2.6.3-b39

Resolved Caveats in Release 2.6.3-b35

Resolved Caveats in Release 2.6.3-b32

Resolved Caveats in Release 2.6.3-b26

Resolved Caveats in Release 2.6.3-b23

Resolved Caveats in Release 2.6.3-b50

Table 14 lists the issues resolved in the Cisco Internet Streamer CDS 2.6.3-b50 release.

Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit.

Table 14 Resolved Caveats in Cisco Internet Streamer CDS 2.6.3-b50Release 

BUG ID
Description

CSCty87766

Content cached without querystring though fms ignore -query-string disabled

CSCuf30834

Change many syslogs to error log

CSCuf73480

Daemon unified_log hangs while fd receiving

CSCuf82185

Stuck fms_stats_daemon causing slow cli

CSCug48872

CDS-IS Command Execution Vulnerability

CSCug52546

Maximum session exceeded

CSCug71848

Frequent WebEngine memory_exceeded alarms on the SE

CSCug74168

Valgrind report memory leak for WebEngine

CSCug76826

rpc_httpd is disabled alarm


Resolved Caveats in Release 2.6.3-b47

Table 15 lists the issues resolved in the Cisco Internet Streamer CDS 2.6.3-b47 release.

Click on the bug ID to view the bug details. This information is displayed in the Bug Toolkit.

Table 15 Resolved Caveats in Cisco Internet Streamer CDS 2.6.3-b47 Release 

BUG ID
Description

CSCud79607

AAC playlists not working through CDS-IS

CSCud79731

CDS-CLIENT-INFO not printed in custom transaction log for cache hit case

CSCud92507

WMT related warning messages filling up syslog

CSCue10363

WMT: fails to play partially cached content

CSCue15576

content-length header field missing in cache bypass scenario

CSCue27133

500 error after upgrade to 2.6.3.b39

CSCue75693

Transaction export does not clear alarms after successful transport

CSCue94284

Add errorlog in module "translog"

CSCuf00686

ftp_export should be controlled by nodemgr

CSCue79628

Clearing content ingested after OS redirect

CSCuf30834

Change many syslogs to errorlog


Resolved Caveats in Release 2.6.3-b45

The following are resolved in 2.6.3-b45:

CSCty62095

Symptom:

If ACQ path is down (tier-1), the edge SE returns 500 (internal error) to client instead of 504(gateway-timeout) or 503(DNS failure).

Conditions:

The SE returns 500 to the client when its tier-1 nodes are down.

CSCty93920

Symptom:

False Power Supply Temperature alarm(s) appears in "show alarms".

Conditions:

Execute the "show tech" CLI command, and look for the "-- system health --" section.

CSCtz54312

Symptom:

Customer needs to setup cookie that include "=" and ":"

This is to conform with RFC 2109.

Conditions:

None.

CSCuc31017

Symptom:

Alarms from ftp_export does not cleared.

Conditions:

The instance of alarm (address of ftp-server) is stuck. The configuration of the address has been removed.

CSCuc31049

Symptom:

In cli prompt, RTSP max-request-rate shows as range <1-2147483647>.

Conditions:

When invokes this cli.

CSCuc32752

Symptom:

Alarms are not cleared despite rtspg logs showing that there is no traffic hitting the box. At the same time the service_monitor_errorlog fills up with threshold exceeded

Conditions:

This is generated during a change where 11 Internet Streamers were removed from a custom Device Group & assigned to "BASELINE" Device Group.

CSCuc41744

Symptom:

When CDS-IS serves a AAC encoded shoutcast stream (Content-type: audio/aacp), it also adds the HTTP header "Content-length: 0). This header is normally used to indicate that there is no data to be transferred.

Conditions:

Some clients like VLC ignore this header and play te stream properly, but some other clients such as Iphone/Ipad honor the header and immediately close the connection.

CSCuc45864

Symptom:

Lots of estashlished TCP connections don't timeout.

Conditions:

Client connects to SR (TCP port 80/554) and does not send any requests.

CSCuc59183

Symptom:

Ftp_export was stuck. Debugging with gdb, it was waiting for read in socket.

Conditions:

Sftp-server (SSH) doesn't respond to the ftp_export and doesn't break the connection.

CSCuc67508

Symptom:

Rpc_httpd (the Apache process) hit core dump when reloading.

Conditions:

When the device is reloading, the rpc_httpd process will exit.

CSCuc67728

Symptom:

Snmp willl return imcomplete info when query processes info.

Conditions:

The file under /proc was just deleted when snmp try to read it.

CSCuc70270

Symptom:

Cache router hash level calculation would go wrong if the URL used for calculating starts with "xxx.se".

Conditions:

If the ofqdn has the format 'xxx.se.yyy', it will be stripped by web-engine, and makes the hash level use the default value 0.

CSCuc74059

Symptom:

Whenremote client closes connection, error messages are printed in the error log.

Conditions:

When remote client abnormally closes connection, for example, directly close, not pause/stop, the window media player.

CSCuc93205

Symptom:

Authsrv returns 302 in 2.6.3 comparing to 403 in 2.5.11 when geo server fail while URL signing pass.

Conditions:

URL signing is applied and error-redirect-url is configured.

CSCud01575

Symptom:

WebEngine coredump on long urls.

Conditions:

The request is a POST message which is posted by client for WMT translog.

CSCud09062

Symptom:

In syslog.txt, there are lines as

Nov 5 14:12:29 edgecache501-cardiff wmt_be: %SE-SYSLOGD-4-581002: pid-2426: HTEndLoop=0, should set timeout!

Conditions:

Issue the Http request on wmt and A&D.

CSCud29094

Symptom:

Service engine, service router does not reply with an ACK on a TCP syn.

Conditions:

CDE is accessed by different clients behind a NAT, cablemodem using the same IP address and non-persistent connections.

CSCud29116

Symptom:

Add a show command to know the TCP settings after addition of the CLIs.

Conditions:

None

CSCud30196

Symptom:

Content acquirers are exceeding WebEngine threshold and causing 504's on subordinate SE's.

Conditions:

This appears to be an issue for both 2.6.3 and 3.1.X.

CSCud44422

Symptom:

On Acquirer SE, one of the data source gets to an error state and it is stuck in memory forever.

This causes new requests for the same file to go into Cache bypass, increasing the load on OS.

"show stat web-engine detail" shall report non zero "Active DataSource" count.

Conditions:

On Acquirer, a HTTP request for a large file initiates a cache fill operation using a DataSource object.

This DataSource object goes into an error state. There are two reasons this can happen, namely when a file is created or disk write error, and the origin server timeout or abrupt connection termination.

Now there is a second request for the same file, web-engine finds an existing DataSource which was in an error state.

Web-Engine initiates the revalidation process but this returns a failure, due to TCP connection attempt failure or HEADER response timeout.

504 Gateway timeout is returned to the second client request but the existing data source is stuck in memory.

CSCud57879

Symptom:

Bad usage of CDSRegex regular expression leads to memory leak, it doesn't free the memory pointed to by "real_preg".

Conditions:

Valgrind tool check if auther server releases rule file in memory when deliver service change rule file fromone file to another(none).

Resolved Caveats in Release 2.6.3-b39

The following are resolved in 2.6.3-b39:

CSCub41468

Symptom:

When a service_monitor process is hung, an SE state inside an SR is flapping.

The interval of UDP packets for keepalive is increased from 2 seconds to 8 seconds. because there are multiple SR devices in the production network. Each query adds an extra delay.

Conditions:

An SE service_monitor process is hung.

CSCub58009

Symptom/Conditions:

Additional requests for revalidation of content despite a 304 response within a cache timeout.

Conditions:

Cache is timed out.

CSCub59480

Symptom:

Client configures two IP Address for an SE. One of the IP address maps to a delivery service. The other IP Address is still able to play the stream of the delivery service.

Conditions:

The client configures the other IP Address of the SE in the client host file, so client can play the stream.

CSCub98887

Symptom:

Customer gets a garbled video image on screen.

Conditions:

Customer changes the resolution of the video.

CSCuc00271

Symptom:

Number of bad sector thresholds in the CDSM is shown as 15.

Conditions:

CDSM display.

CSCuc12956

Symptom:

The SR performs a core dump while checking the SR statistics for the API request and 302 redirect.

Conditions:

1. Give SR API request from browser Syntax of API:

http://ServicerouterIP/routeURL?CDNURL=<RequestedURL>&ClientIP=<IPOfTheClient>;

2. Give the SR 302 redirect request from the client in the same network as given in API request.

3. Check the SR statistics for the API request and 302 redirect.

CSCuc49835

Symptom:

The Web Engine in an edge SE bypasses the CA and reaches OS directly.

Conditions:

1. Edge SE, which means it is serving the client directly.

2. HTTP Head request.

3. The requesting content is cache-hit and expired and must be revalidated.

4. There is an existing Datasource for the requesting IRL but no existing DataSourceFinder for the request URL.

Resolved Caveats in Release 2.6.3-b35

The following are resolved in 2.6.3-b35:

CSCua40930

Symptom:

Transaction logs are exported again to the server.

Conditions:

Upgrade procedure or reload or CLI is affecting the transaction logs issued.

CSCub42175

Symptom:

Clients receive 504 error when streaming WMT.

Conditions:

There is a rare condition in the Web Engine when OS times out that may cause all subsequent clients requesting this movie to receive a 504 error.

CSCua65921

Symptom:

The service_rule does not include '(' when the NOT ('!') operator is used.

Conditions:

When CDS-IS is configured for service rules using rule xml and the rule has !(<some regex>), then the '(' after the NOT operator is not considered.

CSCua90083

Symptom:

Extra space is seen between fields in transaction logs.

Conditions:

Custom transaction logging is used.

CSCub33092

Symptom:

Based on the investigation over the error logs and the web-engine code, the root cause is:

1. Some existing data sources in the memory ended up with a bad status due to content downloading being terminated by OS HTTP response body read timeout 504 (due to OS being overloaded).

2. At the same time, many new requests kept hitting the existing data sources.

3. Before using those data sources, there is not status check. Therefore, 500 was returned to client.

4. Since new requests kept hitting the data sources, the data sources could not be evicted from the memory.

Conditions:

2.5.11.15 origin server is under heavy load.

CSCtx23762

Symptom:

WMT streams affected.

Conditions:

Incoming bytes does not increment for that stream.

CSCua77316

Symptom:

Windows Media (http) - SE sometimes denies request.

Conditions:

1. URL sign generation is enabled through authsvr rule file.

2. URL sign verification is enabled through CLI rule configuration.

CSCub06673

Symptom:

High disk utilization.

Conditions:

Slow scan on progress.

CSCua71204

Symptom:

Users may get http 404 errors when new feature "follow origin server redirect" is enabled on CDS delivery service. This is due to hostname not being re-written to what is listed in the 302 redirect location.

Conditions:

Enable new feature "Follow Origin Server Redirect" on a delivery service in CDS-IS. Redirected web server cares about/needs proper hostname to route traffic to proper application pool.

CSCua92633

Symptom:

Stream-schedule core dump on customer device.

Conditions:

There is no corresponding record found from the (DB) table uni_multicast_info. But we have logic issue for this case.

CSCub41474

Symptom:

The ability of the content based routing feature is limited when URL signing is used. Content based routing generates a hash on the whole URL, which includes the signed part and therefore is always unique. So all traffic goes to origin server.

Conditions:

When the URL signing feature is used.

Resolved Caveats in Release 2.6.3-b32

The following are resolved in 2.6.3-b32:

CSCty71678

Symptom:

TCP connection half closed when the Quova server restarts.

Conditions:

If the Quova server restarted when the SR is processing a request, the SR skips location routing and falls back to the next routing method.

CSCtz32361

Symptom:

Acquirer process core-dumps.

Conditions:

Occurs very rarely. When the Acquirer is processing the manifest file, take the SE off of the Delivery Service. If you are not using pre-positioning, the chances of hitting this issue are negligible.

CSCtz50130

Symptom:

Custom access logs (transaction logs) show large value in the column which corresponds to the "Bytes-Transferred-Excluding-Header" when no data is sent out to the downstream SE.

Conditions:

Only under overloaded conditions when the SE or CA take too long to send the data to the downstream SE. But the downstream SE (after waiting for a certain time; default= 5secs), disconnects from the upstream SE and sends a 504-Gateway timeout to the client.

CSCtz77214

Symptom:

Bitrate exceeded error and streaming issues.

Conditions:

The OS encoder sent an ASF header with no ASF_Stream_Bitrate_Properties_Object, and has more than 3 streams in it.

CSCtz99849

Symptom:

CPU threshold exceeded alarms and UKSE process at 100% CPU.

Conditions:

In Release 2.6.1.

Xbox may be involved as a client.

CSCua04909

Symptom:

WTMP file is not managed properly.

Conditions:

In Release 2.6.1.

CSCua21224

Symptom:

SE sends HTTP connections directly to the Origin Server bypassing CA.

Conditions:

Code upgrade from Release 2.5.9 to 2.5.11.

CSCua39395

Symptom:

When the WebEngine is unable to cache and responses a cds_proxy back to FMS, FMS fails to initiate a series of range requests.

Conditions:

When WebEngine responses cds_proxy back to FMS.

CSCua52103

Symptom:

Web Engine core dump.

Conditions:

1. There is traffic ongoing during the Web Engine startup.

2. Thread transfer happens.

Resolved Caveats in Release 2.6.3-b26

The following are resolved in 2.6.3-b26:

CDSM

CSCtz42796

Symptom:

The live program API allows duplicate IDs for different addrPort entries. For example, the following two addrPort entries have same ID, but the API doesn't reject it.

<addrPort addrVal="229.231.6.19" portVal="12080" id="1" />
<addrPort addrVal="229.231.6.19" portVal="12082" id="1" />
 
   

Conditions:

None.

CSCtz42802

Symptom:

The GUI "Live Programs -> Streaming" page does not show the following items for rebroadcast programs created by API:

Unicast URL Reference:*

Multicast URL Reference:*

Conditions:

None.

CSCtz42898

Symptom:

The GUI page does not show the reference URL for a live program created via API:

<ucastInfo referenceUrl="rtsp://dss.john52-crdc.com/test.sdp"/>
<mcastInfo referenceUrl="http://dss.john52-crdc.com/mtest.sdp">
<addrPort addrVal="229.251.161.149" portVal="14588" id="1" />
 
   

CSCtz22185

Symptom:

For Movie Streamer rebroadcast feature, media files cannot be added by the Media Selection API.

Conditions:

None.

Content Manager

CSCtz01248

Symptom:

When the snapshot file has stale entries and restarts the Content Manager before the Content Manager refresh snapshot. After the Content Manager starts up, sanity will not delete the stale entry.

Conditions:

Snapshot file has the stale entries and Content Manager restarts.

FMS

CSCtz25604

Symptom:

When streaming mp3 using JWplayer, timeline and progress bar does not appear.

Conditions:

When client requests mp3 streaming.

Platform

CSCtz32682

Symptom:

This alarm is occurring on the CDS appliances running 2.6 after a number of days runtime.

Conditions:

Appears to be caused by a change from 2.5.9 in the way WTMP is logged In 2.5.9 output was logged to '/local/local1/var/log/wtmp' and the file was managed. No issue in 2.6. It is now logged to '/var/log/wtmp' and grows until the inodes in root are completely used.

Transaction Logs

CSCtz46315

Symptom:

Transaction logs files are not exported.

Conditions:

Small transaction logs files are removed in process of compression.

Web Engine

CSCtz25891

Symptom:

When downgrading an SE from 3.0 to 2.6.3 and the CDSM is still running 3.0, response read timeout, reconfigured port, and number of 302 redirection will be set to 0.

Conditions:

When SE and CDSM loaded 3.0 image, and downgrade SE to 2.6.3 first.

Resolved Caveats in Release 2.6.3-b23

The following are resolved in 2.6.3-b23:

Auth Server

CSCtt20808

Symptom:

When multiple Domains are specified in a matchgroup, a validation error must be thrown, as input URL matches only a single domain.

CSCtw70444

Symptom:

If the authsvr rule file contains PatternListGrp with a duplicated name, rule file validation does not give warning.

Condition:

When authorization service rule file has entries of PatternListGrp with duplicated name, for example, 2 PatternListGrp are both named as "group1". The later PatternListGrp is used.

CSCty31360

Symptom:

Clients received 403 response from the SE.

Condition:

SE failed to reach the quova server when quova API call failed.

Cache Router

CSCty11856

Symptom:

CacheRouter does not take into account all the CAs/SEs in a location for it's route calculations. It picks only the first two (in the dynamic hash list of SEs generated for every URL) and sends liveness queries only to those two.

Condition:

Only when at least two of the CAs in the root location are offloaded/go-down and there are other live CAs in the root location.

CDSM

CSCtc48460

Symptom:

In the Device Group home page, The "Pages configured for this device group" section does not show all menu items with pages that have been configured with the device group settings.

CSCtu21535

Symptom:

After the device is upgraded to 2.5.9 or 2.5.11, the CLI change cannot be synced back to CDSM, it is reverted to the existing CDSM configuration.

Condition:

The banner is enabled, and an exec message is configured.

CSCtu34804

Symptom:

CDSM reports SEs to be offline when they are not really offline.

Condition:

Service monitor on the SEs hung.

CSCtu47390

Symptom:

After fail over, the daily statistics data were lost for the time before switch.

Condition:

Always.

CSCtu51601

Symptom:

Content-based routing is enabled for the SR and also at the Origin server configuration from GUI perspective. But from the SR perspective, the content-based routing is only enabled globally and disabled for all delivery services.

Condition:

After upgrading to Release 2.6.3 from Release 2.5.x.

CSCtu89207

Symptom:

In 2.5.x release, Speed and Duplex are not displayed for the interface that has a slot sequence number bigger then 9 (for example, GigabitEthernet 10/0).

Condition:

Always.

CSCtw74161

Symptom:

Customer has recently re-purposed some of our internet streamers, and is now receiving 302 response when trying to stream from them.

Condition:

When changing the hostname of some of the SEs, a hostname was used that was already applied to an SE.

CSCtx59305

Symptom:

FTP password reported in clear text in CMS logs.

Condition:

When an upgrade job sent by the Central Manager is failing (for example, if the CDE cannot connect to the FTP server where the upgrade software is stored).

CSCtx69884

Symptom:

When you assign a new device with base configuration (that does not include SSH settings) to a device group with SSH settings, the SSH settings are not inherited.

Condition:

Device is configured with base configuration (no SSH settings).

CSCtx73089

Symptom:

SE retains the username configured in the Device group.

Condition:

After removing the SE from the Device group.

CSCtx95872

Symptom:

System Log settings created over CDSM and pushed to an SE have inheritance issues.

CLI

CSCti17713

Symptom:

CLI range given is incorrect, it should reflect the true limit of the platform as shown in the `show wmt'.

Condition:

When configuring bandwidth for WMT or Movie Streamer.

CSCtu77507

Symptom:

Many of the show options are missing for normal user created through CDSM.

Condition:

Release 2.5.9.

CSCtx99820

Symptom:

SE stopped exporting syslogs to syslog servers.

Condition:

Logging facility local0- cli in running configuration.

Content Manager

CSCtu26655

Symptom:

When an SE is un-assigned from delivery service, Content Manager triggers a delivery service procedure. Due to high object count (13M) delivery service removal, disk IO is very high on a 2G2 device.

Condition:

Due to high disk IO utilization, the SR is not redirecting a request to an SE.

Data Server

CSCtx28540

Symptom:

Service router generated coredumps.

Condition:

Workload/stress.

DSS

CSCts97014

Symptom:

Insufficient bandwidth error on end device (Nokia 6120c hand-held).

Condition:

Incorrect bandwidth specifiers in SDP.

CSCtw48163

Symptom:

RTSP request from Nokia mobile is refused by CDS-IS.

Condition:

The URL field in Nokia's request has only domain and port, no path in it.

FMS

CSCtt70609

Symptom

FMS SWF Verification failed when using portal page, which has embedded SWF file.

Condition:

When we using Portal page, SWF verification is blocked by the authsvr as the customer is getting .html extension instead of .swf.

CSCtu38218

Symptom:

When entering a URL signing string in the OSMF player, such as FMP or Strobe. Query string part becomes part of the URI property in Access adapter, which is not expected, and the request becomes proxy application for CDS-IS.

Condition:

Using OSMF player with URL signing feature.

Live Routing

CSCtu08478

Symptom:

WMT live stream request goes directly to OS from non-CA service engines.

Condition:

Primary CAs were on reloading or down. Some liveness query to backup CA return failure on WMT engine alive.

MegaRaid

CSCty75131

Symptom:

File that needs to be purged from running MegaCLI command.

Condition:

Underlying issue with the MegaRAID controller card on the CDE220-2S3I and CDE250-2S6 systems.

MP3 Live

CSCtx75279

Symptom:

We do not support Response messages with header `content-type:audio/aacp'.

Condition:

Always.

Network

CSCtt39983

Symptom:

DSCP marking for IP packet was done by the edge router. In the new deployment, management and cache fill traffic (packets) are going through core router instead. Customer requested CDS-IS software to mark DSCP bits.

Platform

CSCto01795

Symptom:

CDS raises alarms for normal operating conditions.

Condition:

Known conditions include smartd "Pending sectors" and "Offline uncorrectable sector" alarms.

CSCts65440

Symptom:

See following messages in /local/local1/var/log:

named[8890]: %SE-UNKNOWN-4-899999:
client 127.0.0.1#33208: RFC 1918 response from Internet for 145.59.152.10.in-addr.arpa
 
   

Condition:

Internal calls to SSHD or NTPD trigger s a reverse DNS lookup through named. This lookup fails with an external DNS server.

CSCtt03347

Symptom:

Under rare circumstances, the following disk failure message is periodically displayed (once / hour) in syslog:

   %SE-DISK-1-200036: 1 disk(s) have failed. Please check syslog for more information.
 
   

Condition:

One or more disk(s) must have previously failed, been subsequently replaced, and the original "disk_failure" alarm(s) successfully cleared.

CSCtt33265

Symptom:

In order to completely eliminate CDS-IS dependency on the BBU health issue, it is desirable to configure the MegaRAID controller to use WriteThrough mode (i.e., disable caching). This should be done at boot-time (independent of installation).

CSCtt42883

Symptom:

The show tech command takes long time to run.

Condition:

SR has hundreds of routes and the DNS server is down.

CSCtu10985

Symptom:

After upgrade, timezone defaults to PDT, instead of UCT.

Condition:

This happens after upgrading from Release 2.5. to 2.6.

CSCtu37729

Symptom:

Interface speed 1000 MBPS displays as 1000baseTX, which is misleading.

Condition:

show tech-support.

CSCtx49711

Symptom:

A rootfs could reach > 90% and cause alarm.

Condition:

MegaSAS.log file under root may be accumulated to huge size.

CSCtx62688

Symptom:

A diskfail core file may be generated.

Condition:

Unknown, but it is an extremely rare situation.

CSCtx92751

Symptom:

SMART statistics polling should be optimized and identify device minimized.

CSCty30762

Symptom:

Bogus CPU values reported by show process command.

Condition:

System uptime more than 7 weeks.

CSCty32803

Symptom:

SSD lockup issue during high TPS load.

CSCty39315

Symptom:

Enhance disk repair to recover failed SSD drives.

Condition:

SSD drive may take offline after fail, need to enhance disk repair to reduce RMA.

Service Routing

CSCtq45818

Symptom:

Service Routing is wrongly matching network prefixes "x.y.z.0/24" when not expected. For example, 1.2.3.4 matching 1.2.0.0/24 or 1.2.5.0/24.

Condition:

This is observed when the service engine that is the best match is not available. This can happen if that particular service engine associated with say a prefix, "x.y.a.0/24" has thresholds exceeded/offloaded/offline/service unavailable. Service Routing starts to match entries for prefix "x.y.0.0/24" or "x.y.z.0/24" after that.

CSCtu00872

Symptom:

Service Router falling back to last resort in some cases.

Condition:

When requests for Service Engine alias with a domain it is not subscribed to are received, after which requests are received, for which that Service Engine is chosen for a domain it is subscribed to. The requests fails over to last resort.

CSCty16903

Symptom:

WMP live streaming cannot be played via VLC player.

Condition:

Player is VLC.

CSCty30928

Symptom:

Core dump in SR during cached Geo-location lookup.

Condition:

Core dump happened when location-based routing is enabled, and an invalid entry is in the location information cache.

SNMP

CSCtx33977

Symptom:

Support for two traps defined in BGP4-MIB latest version: bgpEstablishedNotification, bgpBackwardTransNotification.

SVC Monitor

CSCtw50810

Symptom:

Abnormal UNS CPU values seen in service monitor logs.

Condition:

Rare.

CSCtw59404

Symptom:

Device is shown as offline in the CDSM. show service-router service-monitor command takes a lot of time and does not print all values.

Condition:

Rare.

CSCtw88101

Symptom:

wmt-splitting status fluctuates on the edge SE.

Condition:

When the RTSPG TPS threshold is exceeded on the acquirer.

Translog

CSCtw54470

Symptom:

When selecting custom format for transaction logs, customer cannot use "Separators" for further log file processing.

Condition:

Transaction log in custom format.

CSCtw71134

Symptom:

No alarm is raised when FTP export failed.

Condition:

FTP export failed.

CSCtw93948

Symptom:

WMT translog field C-byte shows wrong unexpected value (0.0.0.0).

Condition:

Receives a wrong transaction log from client.

CSCtx41974

Symptom:

Custom transaction logs were printed continuously without a new line character.

Condition:

Workload/stress.

Web Engine

CSCto75342

Symptom:

WE talks to the auth server to apply the rule configuration and whether to allow the client or not.

Condition:

Workload/stress.

CSCts99053

Symptom:

1. All the 4 SRs and 1 backup CDSM were reported to be down on the primary CDSM. Only these 5 devices were observed to flip between online and offline modes while the SE's status seem to be ok.

2. There were no reported interruption to the end user. But the CDN monitoring system (CDSM) is reported to be unreliable.

3. Huge /local/local1/logs/rpc_httpd/ssl_scache.pag file size (~44GB) on the primary CDSM.

4. No core files observed.

Condition:

SRs/SEs/backup CDSM send http[s] messages to the primary CDSM which is handled by the rpc_httpd process on the CDSM. These requests are the http[s] messages that report the health of the various nodes to CDSM.

CSCtx20484

Symptom:

WebEngine does not properly recover from sector I/O errors (Latent Sector Errors or LSEs). The current behavior is to simply close the client connection upon I/O error. Subsequent client requests may continue to repeatedly access the same errored sector(s), possibly introducing unnecessary I/O delays and performance degradation.

Condition:

Cached video content containing pending sector(s) errors.

CSCtx82934

Symptom:

Web Engine crash (core-dumped) soon after SE reboot to perform disk swapout.

Condition:

Sometimes.

CSCty37006

Symptom:

When customers are changing channels, they start at the same point within the video for between 3 to 10 minutes as the manifest file is not updating as frequently as it should (every second or so).

Condition:

Using ABR.

CSCty70994

Symptom:

When two range requests simultaneously requests same file, Web Engine Total Outgoing Requests do not increase correctly. It only accounts for 1.

Condition:

When two range requests simultaneously requests the same file.

WMT

CSCtt13298

Symptom:

CDS-IS cannot stream a specific file.

Condition:

File has a big ASF header object (Metadata Library object).

CSCtu10081

Symptom:

After client seek operation, Internet Streamer does not serve the I-frame at the first packet to client.

Condition:

When OS is Apache HTTP server and in cache miss case.

CSCtu28774

Symptom:

Non-corrupted cached contents were reported corrupt by asf_dump utility.

Condition:

Files bigger than 2GB.

CSCtw45903

Symptom:

wmt_be coredump generated on the SE.

Condition:

Memory corruption happened during data transfer.

CSCtw84322

Symptom:

SE failed to set C-ip and S-ip in transaction logs.

Condition:

Rare.

CSCtx23762

Symptom:

WMT streams affected.

Condition:

Incoming bytes do not increment for that stream.

UNS Server

CSCtf37689

Symptom:

UNS server core dumped after reload (after running FMS mixed).

Condition:

Under running FMS mixed performance testing (70-20-10 70% all unique/20% single unique/10% cache miss) traffic.

Accessing Bug Tool kit

This section explains how to use the Bug Toolkit to search for a specific bug or to search for all bugs in a release.


Step 1 Go to http://tools.cisco.com/Support/BugToolKit.

Step 2 At the Log In screen, enter your registered Cisco.com username and password; then, click Log In. The Bug Toolkit page opens.


Note If you do not have a Cisco.com username and password, you can register for them at http://tools.cisco.com/RPF/register/register.do.


Step 3 To search for a specific bug, click the Search Bugs tab, enter the bug ID in the Search for Bug ID field, and click Go.

Step 4 To search for bugs in the current release, click the Search Bugs tab and specify the following criteria:

Select Product Category—Video.

Select Products—Cisco Content Delivery Engine Series.

Software Version—[2.6].

Search for Keyword(s)—Separate search phrases with boolean expressions (AND, NOT, OR) to search within the bug title and details.

Advanced Options—You can either perform a search using the default search criteria or define custom criteria for an advanced search. To customize the advanced search, click Use custom settings for severity, status, and others and specify the following information:

Severity—Choose the severity level.

Status—Choose Terminated, Open, or Fixed.

Choose Terminated to view terminated bugs. To filter terminated bugs, uncheck the Terminated check box and select the appropriate suboption (Closed, Junked, or Unreproducible) that appears below the Terminated check box. Select multiple options as required.

Choose Open to view all open bugs. To filter the open bugs, uncheck the Open check box and select the appropriate suboptions that appear below the Open check box. For example, if you want to view only new bugs in Prime Optical 9.5, choose only New.

Choose Fixed to view fixed bugs. To filter fixed bugs, uncheck the Fixed check box and select the appropriate suboption (Resolved or Verified) that appears below the Fixed check box.

Advanced—Check the Show only bugs containing bug details check box to view only those bugs that contain detailed information, such as symptoms and workarounds.

Modified Date—Choose this option to filter bugs based on the date when the bugs were last modified.

Results Displayed Per Page—Specify the number of bugs to display per page.

Step 5 Click Search. The Bug Toolkit displays the list of bugs based on the specified search criteria.

Step 6 To export the results to a spreadsheet:

a. In the Search Bugs tab, click Export All to Spreadsheet.

b. Specify the filename and location at which to save the spreadsheet.

c. Click Save. All bugs retrieved by the search are exported.

If you cannot export the spreadsheet, log into the Technical Support website at http://www.cisco.com/cisco/web/support/index.html or contact the Cisco Technical Assistance Center (TAC).

Upgrading to Release 2.6.3

Release 2.6.3 supports upgrades from Release 2.5.9, 2.5.11 and 2.6.1. If your CDS is running an older release, you need to upgrade to one of these releases before upgrading to Release 2.6.3. Note the following:

Case 1: 2.6.1 to 2.6.3, cache content is preserved.

Case 2: 2.5.x to 2.6.3, cache content is erased because of the file system reformat.

After the upgrade procedure starts, do not make any configuration changes until all the devices have been upgraded. For information on the upgrade procedure, see the Cisco Internet Streamer CDS 2.6 Software Upgrade Guide.

Documentation Updates

The following document has been added for this release:

Release Notes for Cisco Internet Streamer CDS 2.6.3

The following Cisco Internet Streamer CDS 2.6 documents have not changed:

Cisco Internet Streamer CDS 2.6 Software Upgrade Guide

Cisco Internet Streamer CDS 2.6 Software Configuration Guide

Cisco Internet Streamer CDS 2.6 Command Reference Guide

Cisco Internet Streamer CDS 2.6 Quick Start Guide

Cisco Internet Streamer CDS 2.6 Alarms and Error Message Guide

Cisco Internet Streamer CDS 2.6 API Guide

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

Related Documentation

Refer to the following documents for additional information about the Cisco Internet Streamer CDS 2.6:

Cisco Internet Streamer CDS 2.6 Software Upgrade Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/upgrade_guide/upgrade.html

Cisco Internet Streamer CDS 2.6 Software Configuration Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/configuration_guide/is_cds26-cfguide.html

Cisco Internet Streamer CDS 2.6 Quick Start Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/quick_guide/ISCDSQuickStart.html

Cisco Internet Streamer CDS 2.6 API Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/developer_guide/is_cds_26_apiguide.html

Cisco Internet Streamer CDS 2.6 Command Reference Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/command_reference/Command_Ref.html

Cisco Internet Streamer CDS 2.6 Alarms and Error Messages Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/message_guide/messages.html

Cisco Content Delivery System 2.x Documentation Roadmap

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

Open Source Used in Cisco Internet Streamer CDS 2.6

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_6/third_party/open_source/OL-25149-01.pdf

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

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

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.

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.