Guest

Cisco Videoscape Distribution Suite for Internet Streaming

Release Notes for the Cisco Internet Streamer CDS 2.5.3

  • Viewing Options

  • PDF (420.3 KB)
  • Feedback
Release Notes for Cisco Internet Streamer CDS 2.5.3

Table Of Contents

Release Notes for Cisco Internet Streamer
CDS 2.5.3

Contents

New Features

Current DNS Routing Implementation

New DNS-Based Redirection

Configuring DNS-Based Redirection

Enhancements

Option for Windows Media Streaming Show Statistics Command

Transaction Log Enhancements

System Requirements

Limitations and Restrictions

Important Notes

Open Caveats

Open Caveats in Release 2.5.3-b37

Open Caveats in Release 2.5.3-b36

Open Caveats in Release 2.5.3-b35

Open Caveats in Release 2.5.3-b34

Open Caveats in Release 2.5.3-b15

API

Windows Media Streaming

Flash Media Streaming

Platform

Cache Router

CDSM

Service Monitor

Resolved Caveats

Resolved Caveats in Release 2.5.3-b37

Resolved Caveats in Release 2.5.3-b36

Resolved Caveats in Release 2.5.3-b35

Web Engine

Service Routing

Movie Streamer

CDSM

Windows Media Streaming

UNS Server

URL Manager

Authorization Server

Platform

Resolved Caveats in Release 2.5.3-b34

Resolved Caveats in Release 2.5.3-b15

Windows Media Streaming

Flash Media Streaming

Service Router

Proximity Engine

Service Monitor

Platform

CDSM

CLI

Network

Upgrading to Release 2.5.3

URL Public Key Signing

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco Internet Streamer
CDS 2.5.3


These release notes cover Cisco Internet Streamer CDS Release 2.5.3-b37.

Revised: February 2011, OL-21513-05

Note Release 2.5.3-b37 obsoletes Release 2.5.3-b36, Release 2.5.3-b35, Release 2.5.3-b34, and Release 2.5.3-b15.

Contents

The following information is included in these release notes:

New Features

Enhancements

System Requirements

Limitations and Restrictions

Important Notes

Open Caveats

Resolved Caveats

Upgrading to Release 2.5.3

Documentation Updates

Related Documentation

Obtaining Documentation and Submitting a Service Request

New Features

Release 2.5.3 of the Cisco Internet Streamer CDS introduces the DNS-Based Redirection feature.


Note The Flash Media Streamer DVR support are available as an early field trial release. For more information, contact your Cisco account representative. The Session Shifting feature is not supported in Release 2.5. For 3-Screen Session Shifting, use the Cisco Internet Streamer CDS 2.3 software.

Current DNS Routing Implementation

The Service Router's Request Routing Engine in the CDS network mediates requests from the clients and redirects them to the most appropriate Service Engine in the CDS network. It monitors the load of the Service Engines and performs automatic load balancing. The Request Routing Engine has different routing methodologies; for instance, load-based routing, location-based routing, proximity-based routing, service aware routing and content-based routing.

Figure 1 describes the current Request Routing Engine workflow.

Figure 1 Current Request Routing Engine Workflow of the Service Router

In Figure 1, the client sends a request for a video file (for example, sample.wmv) to http://video.cds.com. The browser in turn sends a recursive DNS request to resolve video.cds.com through the DNS proxy.

The Service Router is configured to be the authoritative DNS for video.cds.com. The DNS proxy resolves video.cds.com to the Service Router's Request Routing Engine and sends the Service Router IP address back to the client. The client then sends a request for sample.wmv to the Service Router.

The Request Routing Engine chooses the Service Engine to redirect the request to based on load, location, and other factors. A 302 redirect message is sent to the client with the redirected URL, http://se1.se.cds.com/sample.wmv.

A DNS request is sent to the Request Routing Engine again through the DNS proxy to resolve se1.se.cds.com. The Request Routing Engine returns the se1's IP address to the DNS proxy which is forwarded to the client.

The client then contacts the Service Engine (se1) directly and requests the sample.wmv. The Service Engine streams the requested content to the client.

New DNS-Based Redirection

The DNS-Based Redirection feature enables requests to get directly routed to the Service Engine without any 302 redirects. It also allows content to be streamed without transforming the request URL.

Figure 2 describes the Service Router's Request Routing Engine workflow using DNS-based redirection.

Figure 2 Request Routing Engine Workflow with DNS-Based Redirection

When DNS-based redirection is enabled, the DNS proxy contacts the Request Routing Engine to resolve video.cds.com (step 8 in Figure 2), the Request Routing Engine determines which Service Engine to redirect the request to based on load, location, and other heuristics, and directly returns the appropriate Service Engine's IP address instead of the Service Router's IP address. The client then directly requests the content from the Service Engine instead of the Service Router.


Note There are certain side effects in adopting this approach. They are as follows:

1. If proximity-based routing is enabled, it will use the DNS proxy's IP address in computing the proximity.

2. Service-aware routing cannot be used because the protocol and content type are not considered at the DNS level.

3. Content-based routing cannot be used because the protocol and content type are not considered at the DNS level.


Configuring DNS-Based Redirection

To configure DNS-based redirection, use the service-router redirect-mode dns-redirect command.

service-router redirect-mode dns-redirect {all | domain domain}

The following example enables DNS-based redirection with the cdsfms.com domain as the domain used to redirect all client requests to.

SR(config)# service-router redirect-mode dns-redirect domain cdsfms.com
 
   

To display information about the redirect mode, use the show service-router redirect-mode command.

To display the statistics, use the show statistics service-router summary command and the show statistics se sename command. The output for the DNS-Based Redirection feature is listed as DNS Requests. In addition to these two show commands, there is also the show statistics service-router dns command.

Enhancements

Release 2.5.3 of the Cisco Internet Streamer CDS has the following enhancements:

Option for Windows Media Streaming Show Statistics Command

Transaction Log Enhancements

Option for Windows Media Streaming Show Statistics Command

The following show command has been added:

show statistics wmt streamstat outgoing [client | SE ]
 
   

The show statistics wmt streamstat outgoing command has been extended with the client and SE options. By specifying the client option, all current WMT streams that are being sent to that client are listed. A history of streams sent to the client are not listed, only current streams are listed. By specifying the SE option, all current WMT streams that are being sent from the SE are listed, which includes all outgoing streams to other SEs as well as clients.

Transaction Log Enhancements

The following enhancements have been made to the transaction logs:

Transaction log filenames have the file generation number appended

Summary line has been appended to the end of each transaction log

Redundant date and header lines have been removed from the beginning of the transaction log

Transaction Log Filename

In Release 2.5.3, the transaction logs have the following naming convention:

Module name

Host IP address

Date

Time

File generation number

For example, the filename for a Web Engine access log would be the following:

we_accesslog_apache_192.0.2.22_20091207_065624_00001

where we_accesslog_apache is the module name, 192.0.2.22 is the IP address of the device, 20091207 is the date of the log file (December 7, 2009), and 065624_00001 is the file generation number. The File Generation Number range from 00001 to 99999.

Summary Line

The transaction logs now include a summary line as the last line in the transaction log, which includes a summary of all the requests that appear in the transaction log.

Redundant Date and Header Lines

Previously, the date and header line appeared twice in the transaction log. Each now only appears once. The header line lists the fields in each data line in the log file.

System Requirements

The Internet Streamer CDS runs on the CDE100, CDE200, CDE205, and the CDE220 hardware models. Table 1 lists the different device modes for the Cisco Internet Streamer CDS software, and which CDEs support them.

Table 1 Supported CDEs

Device Mode
CDE100
CDE200
CDE205
CDE220

CDSM

Yes

No

Yes

No

SR

Yes

Yes

Yes

Yes

SE

Yes

Yes

Yes

Yes


Release 2.5.3 supports the CDE220 2G2 platform. There are a total of ten gigabit Ethernet ports in this CDE. 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 CDE100 can run as the CDSM, while theCDE200 can run as the Service Router or the Service Engine. See the Cisco Content Delivery Engine CDE100/200/300/400 Hardware Installation Guide for set up and installation procedures for the CDE100 and CDE200.

The CDE205 can run as the CDSM, Service Router, or Service Engine. 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.

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.



Note In Release 2.5.3, configuring Replication Bandwidth Scheduling is only supported on a per SE-basis; Device Group configuration of Replication Bandwidth Scheduling is not supported.

Important Notes

To maximize the content delivery performance of a CDE200, CDE205, or CDE220, 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.4 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 CDE200, 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 CDE200 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 a full CDE200, CDE205, or CDE220 capacity, we recommend that you provision a dedicated CDE200 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 CDE200, CDE205, or CDE220 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.

6. When upgrading from a previous release, the primary interface is converted to a streaming-interface by the upgrade process. When configuring new delivery traffic interfaces, either because of a new installation or because of removing existing configuration, you must use the streaming-interface command.

streaming-interface {GigabitEthernet 1-10/port | PortChannel 1-2 | Standby group_num}
no streaming-interface {GigabitEthernet 1-10/port | PortChannel 1-2 | Standby group_num}

Open Caveats

The open caveats section has the following subsections:

Open Caveats in Release 2.5.3-b37

Open Caveats in Release 2.5.3-b36

Open Caveats in Release 2.5.3-b35

Open Caveats in Release 2.5.3-b34

Open Caveats in Release 2.5.3-b15

Open Caveats in Release 2.5.3-b37

CSCtf74656 [MEDIUM IMPACT]

Symptom:

After run a certain long time SE can not server any requests in Longevity test.

Conditions:

In longevity tests with mixed heavy traffic and "cache revalidate for each request" enabled, after running a certain period of time (duration depends on the test profile), the SE cannot serve requests. The following is an example of the profile:

1200 all-unique 100kbps sessions -propositioned    length : 30mins
1200 all-unique 300kbps sessions -prepositioned    length : 30mins
600 all-unique 700kbps sessions - cache hit           length :30mins
800 all-unique 1mbps sessions - cache hit              length :1hr
200 all-unique 2mbps sessions - cache hit              length :30mins
100 long url single-unique 700kbps sessions - prepositioned         length : 30mins
600 single-unique 1mbps sessions - cache hit         length : 1hr 
Total : 4700 concurrent requests
 
   

Workaround:

Disable cache revalidate for each request."

CSCtj81042 [MEDIUM IMPACT]

Symptom:

Service Monitor goes into core dump.

Conditions:

During stress test.

Workaround:

Service Monitor process restarts by itself.

CSCtj85882 [MEDIUM IMPACT]

Symptom:

Some invalid SNMP query messages can cause the SNMP daemon to go into core dump.

Conditions:

Invalid SNMP messages are sent to the device.

Workaround:

Use the CDSM or CLI to retrieve system information and healthy status.

CSCtn38059 [HIGH IMPACT]

Symptom:

A core.wmt_ml found on device.

Conditions:

When Windows Media Streaming attempts to write to a full drive, it cannot write and a core dump file is generated.

Workaround:

Clear the cache so that the database is synchronized again, and the issue is resolved. No further action required. Or, reduce the number of content files manually, then keep monitoring the cache, and remove more content it if the disks are approaching full again.

CSCtf37689 [MEDIUM IMPACT]

Symptom:

The UNS server goes into core dump after a device reload (after running Flash Media Streaming mixed traffic).

Conditions:

When running Flash Media Streaming mixed performance testing(70-20-10: 70percent all unique, 20 percent single unique, 10 percent cache-miss) traffic.

Workaround:

This core dump happens at random when the UNS process starts. This could be while SE is reloading, and it should not affect any customers because it is not service impacting.

CSCtk18297 [MEDIUM IMPACT]

Symptom:

When RTMPT stress test is running, fmsedge process memory keeps growing and reaches 4 GB. Finally, a 4 GB core-dump file is generated.

Conditions:

Configure 1400 concurrent VOD sessions, all unique, cache-miss RTMPT stress traffic. Monitor the memory usage for two to three hours. The memory usage for the fmsedge process keeps increasing. When the memory reaches 4 GB, the process goes into core dump.

Workaround:

Setting the SR Burst Control feature monitors the memory usage and SR stops sending any further requests to the SE. Currently, 10 users per second ramp-up rate is a reasonable value.

CSCtk12424 [MEDIUM IMPACT]

Symptom:

Sometimes more connections are served than the maximum configured connections on the server.

Conditions:

If a maximum number of connections (e.g. X connections) is configured on the server and more connections are requested at nearly the same instant (more than X connections) then all of them may be served successfully by the server. This is because it takes some time for the server to record a new connection and enforce access control policies before which the next subsequent connection comes in.

Workaround:

No workaround at this point, however this issue will not be seen if the connections are separated by a few seconds.

CSCtl93373 [HIGH IMPACT]

Symptom:

The fmsdge process core dumps sometimes on the SR when a stress test using RTMPT is running.

Conditions

When a very high or uncontrolled ramp up rate is used in the load tool and more RTMPT connections are sent than what is the maximum configured, the extra connections are rejected. As a result the tool tries to send more connections leading to more connections getting rejected. As this happens the memory usage of the fmsedge process keeps increasing and it coredumps at 4GB.

Workaround:

If a controlled ramp up rate is used which is not very high (less than 10 users per second) then this issue is not seen.

CSCtc20212 [MEDIUM IMPACT]

Symptom:

The following messages can be seen on a neighbor router when the BGP password is unconfigured on Proximity Engine, after the BGP adjacency has been formed, but corresponding removal is not performed on the router:

*Feb  7 03:32:14.861: %TCP-6-BADAUTH: No MD5 digest from 192.168.82.33(179) to 
192.168.82.2(24018)
*Feb  7 03:34:00.573: %TCP-6-BADAUTH: No MD5 digest from 192.168.82.33(179) to 
192.168.82.2(24018) (RST)
 
   

Conditions:

This issue occurs when adjacency is established with a neighboring router and the password is removed from Proximity Engine configuration and not re-configured within the hold time.

Workaround:

When the password is unconfigured on the Proximity Engine side, the two peers cannot communicate with each other. This state is reported on the router side with the following repeated messages:

*Feb  7 03:32:14.861: %TCP-6-BADAUTH: No MD5 digest from 192.168.82.33(179) to 
192.168.82.2(24018)
 
   

This occurs until the TCP connection is closed on Proximity Engine side and enters TIME_WAIT state. While this state lasts, no messages are printed on the router. The router is still retransmitting TCP packets, but the Proximity Engine is ignoring them, as per TIME_WAIT state. After about 60-75 seconds, the following messages start to display on the router:

*Feb  7 03:37:32.937: %TCP-6-BADAUTH: No MD5 digest from 192.168.82.33(179) to 
192.168.82.2(24018) (RST)
 
   

These indicate that the TCP connection has been completely closed on the Proximity Engine side, which therefore no longer has any knowledge of the TCP connection and responds to each retransmitted packet with an RST packet, which does not have an MD5 signature. This situation is described in RFC 2385, section 4.1 (Connectionless Resets). The messages are logged as long as the router retransmits TCP packets of the lost connection, which has been observed to occur for up to ten minutes.

This issue does not affect correct operation.

CSCtj25001 [MEDIUM IMPACT]

Symptom:

The Cache Router goes into core dump during Web Engine small-objects stress testing.

Conditions:

This occurs in a two-tier setup (Client->Edge->Acq->OS) with all unique cache-miss stress, running for about a day. The transactions per second was 200.

Workaround:

No service Impact. Self-correcting in seconds.

CSCtj19955 [MEDIUM IMPACT]

Symptom:

Cache Router goes into core dump.

Conditions:

When under stress testing, by using the siege tool to issue 200 concurrent requests to VOD content on the origin server. The siege tool was configured to issue RFQDNs to the edge SE. (www.<EDGE-SE-NAME>.se.<OFQDN>/<content>)

Workaround:

No service Impact. Self-correcting in seconds.

This happens very rarely under prolonged stress testing using all cache-miss traffic, without SR load balancing. When it core-dumps, the Web Engine still proceeds and serves the client requests successfully, despite not getting the route information from the cache-router module. Just the route information the Web Engine uses will be from its own memory cache, and not the latest from the cache-router module. If the Web Engine's cached routes do not contain any upstream SEs, the Web Engine fulfills the client request from the origin server. If there is no connectivity to the origin server, a "504 Gateway Timeout" error is returned to the client. While the cache-router is core-dumping or restarting and is not available, the SR does not direct further traffic to this SE until the cache-router is back up and running. The cache router restarts within a matter of seconds and all normal operations resume. So this is self-correcting within a few seconds.

CSCtl09712 [LOW IMPACT]

Symptom:

After deleting the Authorization configuration XML file, the Authorization Server does not get notified of the deletion.

Conditions:

When deleting the Authorization configuration file by clicking delete button, Delete Authorization Settings in the task bar on the Authorization Service page, the file is removed in the SE, but when the Authorization Server updates the delivery service information, it does not recognize that the file has been deleted.

Workaround:

Use the delete button, Delete File, next to the File Type in the main part of the Authorization Service page to remove the Authorization configuration file.

CSCtk83097 [MEDIUM IMPACT]

Symptom:

In a multiple-tier, cache-miss scenario, if many users are watching the same content and are performing extensive trick operations, a race condition and some packet delay may occur, causing the downstream SE to timeout and play to fail.

Condition:

This happens in certain multiple-tier, cache-miss scenarios.

Workaround:

Pre-position the content for the SE to serve.

CSCtk31094 [LOW IMPACT]

Symptom:

In some VOD cache-miss scenarios where a non-extracted, idle-to-be-released Front-end (FE) is picked up to fetch content for another Back-end (BE), if the FE exits due to a BE timeout during the serving time, video freeze may be observed.

Condition:

This occurs during certain cache-miss scenarios.

Workaround:

Pre-position the content for the SE to serve.

CSCtk64806 [MEDIUM IMPACT]

Symptom:

When playing a WMT stream in a VOD cache-miss scenario, the client sometimes receives a 504 error and quits before the end.

Condition:

This occurs only in a VOD cache-miss scenario.

Workaround:

The second request for the same content will work.

CSCtk62383 [MEDIUM IMPACT]

Symptom:

WMV Streaming stops prematurely.

Condition:

This occurs during a cache-miss scenario.

Workaround:

Turn off MMS-over-HTTP on the Content Acquirer, and turn off fast-cache and fast-start on all the SEs running the WMT.

CSCtk31079 [MEDIUM IMPACT]

Symptom:

The WMT session still appears in the output of the show wmt stats, even after the client has disconnected.

Condition:

This happens randomly when the client requests HTTP streaming for the WMT.

Workaround:

Restart the WMT to end the sessions that have hung.

CSCti52364 [LOW IMPACT]

Symptom:

The SE core dumps.

Condition:

When the first request is an OPTION request and no subsequent requests arrive, the SE times out and generates a core-dump.

Workaround:

None. A fix will be available in Release 2.5.9.

CSCti52358/CSCtj61353 [MEDIUM IMPACT]

Symptom:

Under certain conditions, when the WMT posts a log to an upstream SE with deleted libwww objects, the WMT core dumps.

Condition:

The client sends a PLAY request from an Edge SE, to a mid SE, to an upstream SE. The client sends data back in response. Under stress conditions, the WMT internally kills all libwww objects and, while in process of posting a log to an upstream SE for the same objects, the WMT core dumps.

Workaround:

The core files affect all playing streams. Users must click the Play button again to continue to play the stream. A fix will be available in the next software release.

CSCtj36490 [MEDIUM IMPACT]

Symptom:

When the SE streams cache-miss MBR content, the client fails to fast-forward or rewind the content.

Condition:

This happens in a cache-miss scenario when the client tries to fast-forward or rewind the stream.

Workaround:

None. A fix will be available in Release 2.5.9.

CSCth99727 [MEDIUM IMPACT]

Symptom:

HTTP requests for files with large ASF headers fail.

Condition:

The content has a large ASF header which is greater than 32K.

Workaround:

None. A fix will be available in the next software release.

CSCtl19905 [LOW IMPACT]

Symptom:

The wmt_be logging process core dumps.

Condition:

This happens when an invalid translog message is included in RTSP SET_PARAMETER request from the Player.

Workaround:

The Player sends valid messages which comply with Microsoft specifications; MS-RTSP and MS-WMLOG.

Open Caveats in Release 2.5.3-b36

CSCtj89982 [LOW IMPACT]

Symptom:

This feature allows us to specify domains that the service router should subscribe to. By default the service-router takes all the domains specified in the CDSM. With this feature even if we configure one domain subscription through the CLI mentioned below, the service router will take the list of domains subscribed through the CLI to be complete list.

Syntax for config:

(config)# service-router subscribe domain test3.com
 
   

Show command for config:

# show service-router subscribe domain

Domains subscribed:
    test1.com
    test5.com
    test4.com
    test3.com
 
   

Condition:

The Service Router takes all the domains specified in the CDSM. This new command allows the SR to only take the domain configured via this CLI.

Workaround:

Feature Enhancement

CSCtk02867 [MEDIUM IMPACT]

Symptom:

Windows Media Streaming video freezes in Release 2.5.3 b35 for a 2.5mbps file.

Condition:

Topology: two-tier

Request for a file encoded at 2.5mbps

Allow the content to play for some time and control actions like seek forward and backward.

Could see video freeze and client side errors thrown.

Workaround:

None.

CSCth32290 [MEDIUM IMPACT]

Symptom:

The wmt_be core dumped for memory logic error.

Conditions:

When running under stress for long term, wmt_be may core dump. Cannot find in which explicit condition this occurs.

Workaround:

If a memory logic error occurs, initialize the memory again and skip the wrong logic when the core dump happens. The new request is not served for a short span until the Windows Media Streaming process is restarted.

CSCtk15288 [LOW IMPACT]

Symptom:

Authorization Server logd file continues to be generated, even though the debug authsvr trace command is not enabled.

Conditions:

Authorization Server logs are generated every five minutes, even though logs are disabled.

Workaround:

Use the debug authsvr error command to turn off trace logging for Authorization Server. By default, error logging is enabled for Authorization Server. In Release 2.5.3, there were additional log level messages in Authorization Server, which may be causing logs printing when Authorization Server. error is enabled alone.

CSCtk15496 and CSCtj21662 [LOW IMPACT]

Symptom:

Not able to turn-off authserver debugging

Undebug and no debug all does not disable authsvr trace logs

Conditions:

After enabling debugging authsvr trace, when trying to disable the debugging using the undebug all command, there is no change (that is, debugs for authserver is not disabled). When trying the undebug authsvr trace command, it enabled the error debugging of authsvr without giving the debug authsvr error command. The authsvr trace messages continue to be added to the errorlog of authsvr. The show debugging command displays, Debug Authsvr error is on.

Workaround:

Use the debug authsvr error command to turn off trace logging for Authorization Server. By default, error logging is enabled for Authorization Server. In Release 2.5.3, there were additional log level messages in Authorization Server, which may be causing logs printing when Authorization Server. error is enabled alone.

CSCtk34460 [LOW IMPACT]

Symptom:

Transaction logs are not working with XBOX in WMT over HTTP cases.

Conditions:

WMT does not parse XBOX logging header correctly.

Workaround:

Use WMT over RTSP instead.

CSCtj42783 [LOW IMPACT]

Symptom:

Delete one of the UNS entries for a content and then request the same content. The SE fails to server it.

Conditions:

One of UNS entries is deleted for a content.

Workaround:

Do not delete the cache entries manually. Use the clear cache command to clear cached entries.

CSCtk02115 [LOW IMPACT]

Symptom:

Service Router does not detect internal issues with the SE.

Conditions:

Because the faulty WMT process logic within Service Engine got stuck, it results in the new request not being served.

Workaround:

None, this is being addressed as design requirement enhancement.

Open Caveats in Release 2.5.3-b35

CSCtj44579 and CSCtj58682 [MEDIUM IMPACT]

Symptom:

The Authorization Server core dumps because of a memory leak. When a large number of delivery services are configured and each delivery service has a huge Authorization Service XML file associated with it.

Conditions:

There is a memory leak when a large number of delivery services are configured and each delivery service has a large Authorization Service XML file associated with it.

Workaround:

Do not create a large number of delivery service with a large Authorization Service XML file associated with each one.

CSCtj48988 and CSCtj37857 [MEDIUM IMPACT]

Symptom:

The following log entry is seen:

ukse_wmt.c:1114 : SE restarting while running WMT stress 
 
   

Conditions:

When Windows Media Streaming is streaming under stress. This has been observed for both for single bit rate (SBR) content and multiple bit rate (MBR) content.

Workaround:

None.

CSCtj59062 [LOW IMPACT]

Symptom:

The following log entry is seen:

WMT:Wmt req hits directly to OS
 
   

Conditions:

A two-tier topology, under stress, and using a WMLoad tool with 100 clients for a lengthy period.

Workaround:

None. Rarely happens.

CSCtj83262 [MED IMPACT]

Symptom:

The Service Router sometimes core dumps after uploading a 4 MB Coverage Zone file.

Conditions:

The Coverage Zone file is too big (28,000 entries), with 10 delivery services and multiple SEs.

Workaround:

Reduce one of the three: number of Coverage Zone entries, number of delivery services, or number of SEs per location.

Open Caveats in Release 2.5.3-b34

The following open caveats were identified in Release 2.5.3-b34:

CSCti46019

Symptom:

The ucache process goes into core dump when the memory usage reaches close to 4 GB, no service failure occurs during this period, just a core file is generated on the SE.

Conditions:

The core dump happens when the ucache process memory usage reaches close to 4 GB. This can happen for the following reasons:

SE has large amounts of content with large URLs.

The clear cache all command was entered when there are many content files.

Workaround:

If the number of content objects in the SE is not large and the URL size is small, then this core dump can be avoided. Maximum cache object count can be set by using the cache content max-obj-count command.

CSCti60355 and CSCti60408 [LOW IMPACT]

Symptom:

Under a particularly rare race condition, the client could not download the file at first, but the file was downloaded during the client automatic retry. If a client does not automatically retry the download, the download fails, but the file downloads if the download is reinitiated.

Condition:

In a cache-miss case (the file is not currently cached on the SE) with two clients downloading the file at exactly the same time from the same SE, if during the file download, one client disconnects, then the other client gets disconnected. Usually the client has automatic retry logic, and the download would succeed upon retry or re-click.

Workaround:

Client automatic retry or re-click resolves the issue. Also the chance of hitting this issue is dramatically reduced if the following CLI is configured on the SE:

U2-CDE220-4# http cache-on-abort enable
U2-CDE220-4# show http cache-on-abort
Policy based cache on abort feature is enabled
Percent threshold is enabled for 90%
U2-CDE220-4#
 
   

CSCtj01303 [LOW IMPACT]

Symptom:

When a user request to an unknown domain is denied, the TCP_DENY is not logged in the transaction log as expected.

Condition:

If the Authorization Server is enabled, transaction logs are enabled, and extended-squid format is configured, when client requests a URL that is for an unknown domain, the request is denied and the SE responds with a 403 error message.

Workaround:

No workaround

CSCtg55017 [LOW IMPACT]

Symptom

When the live program source is multiple bit rate (MBR), some players get errors in the buffer state or after playing for a short time.

Condition

A live program source is MBR and lots of different bit-rate requests for the live program causes this issue.

Workaround

Configure different live programs for the same content with different bit rates.

CSCti89222 and CSCth86738 [MEDIUM IMPACT]

Symptom:

The show service-router routes command on the SR does not display output when the Coverage Zone files are large and the CPU usage spikes to 100 percent An alarm may be raised or a core dump may occur on the SR.

Condition:

When Coverage Zone file is very large, the follow CLI output is displayed:

RT-612-7# show service-router routes
Timed out in obtaining data due to routing table being locked - please try later
 
   

Workaround:

After the core dump, the SR restarts.

CSCti92988 [LOW IMPACT]

Symptom:

The Movie Streamer transaction log has different header than standard QuickTime Streaming Server (QTSS) and is missing #Fields: identifier from field definition line.

Condition:

The transaction log header has #Software: Cisco-CDS Version: 2.0.0 as the header instead of #Software: QTSS or #Software: DSS.

Workaround:

None.

Open Caveats in Release 2.5.3-b15

The following open caveats were identified in Release 2.5.3-b15:

API

CSCth44836

Symptom:

UNS-related errors occur because the program name and reference URL had uppercase and lowercase characters, but the API only allows lowercase characters for both the program name and reference URL.

Condition:

Live programs with uppercase characters in the program name and reference URL (unicast or multicast) are not consistent with API calls, which expect only lowercase characters.

Workaround:

Only use lowercase characters for the program name and reference URLs.

Windows Media Streaming

CSCte54738

Symptom:

RTSP service on the SE fails to accept more requests and new Windows Media Streaming requests fail.

Condition:

When the SE is running 6000 sessions with a mixture of live and VOD requests.

Workaround:

None.

CSCsq46063

Symptom:

Multiple stale outgoing sessions are displayed for the show statistics wmt streamstat command.

Condition:

When an SSPL broadcast publishing point is stopped and a managed live Windows Media Streaming program is scheduled.

Workaround:

Stale sessions are removed periodically and do not impact streaming. Alternatively, you can enable the SSPL broadcast publishing point source.

Flash Media Streaming

CSCta44470

Symptom:

This issue is seen when the client requests a live stream to the SE and after about eight hours, the client stream is stopped and the connection gets closed.

Condition:

This issue occurs only when playing a live stream continuously for more than eight hours to a single client. If the clients keeps connecting to the live stream and disconnecting from the live stream, this issue does not occur.

Workaround:

No workaround, however the next click does work.

CSCtc99610

Symptom:

The issues is seen with VOD-like streaming with an interactive application. CDS-IS internally caches a file segment up to two GB. After the cache reaches more than two GB, the SE cannot serve the previous content.

Condition:

This only happens in three SE chaining setup. Two-level setups do not have this issue.

Workaround:

No workaround.

Platform

CSCtd16093

Symptom:

CDS-IS software does not currently support the lowering of SMART alarms. Should an event which triggers a SMART alarm clear, the SMART alarm will remain raised until the CDS-IS system has been reloaded.

For a CDS-IS system, the typical SMART alarm pertains to drive failure prediction, and will be raised whenever a hard drive predicts its own imminent failure. The nature of this type of alarm is persistent. Once the prediction is made, it will not be cleared. Once more, because CDS-IS only supports replacing failed drives across reboot, the consequence of not lowering the alarm will go largely unnoticed.

Condition:

Unlike the typical 'failure prediction' alarm, other SMART conditions, namely the temperature alarm, are intermittent, and can be raised and lowered over time. This style of alarm is effected by the current bug, and will not be lowered once they have been raised.

Workaround:

The current workaround, is to monitor the smart conditions using the show disk smart detail command. Once the situation has been cleared, the system can be rebooted, and the alarms will be gone.

Cache Router

CSCta92439

Symptom:

Cache Router core dumps with Movie Streamer Live traffic is under stress.

Condition:

This happens very randomly and probably after 4-5 days of stress traffic, when the Cache Router may not be able to process the client request. The impact is minimal, as the protocol engine fails over to next upstream SE or Origin Server. Client playback should not get effected.

Workaround:

None.

CDSM

CSCte09496

Symptom:

The cms_cdsm service is halted after downgrading the CDSM from Release 2.5.3-b5 to Release 2.4.3-b7 when the standby interface is the primary interface.

Condition:

The following two conditions could occur:

1. If a standby group is configured, then it will be removed after downgrade and will prevent cms startup as the removal is not clean.

2. If port channel is configured and there is no GigE assigned, the port channel will be removed.

Workaround:

If a standby group is used, use one of the following two workarounds:

1. Avoid using a standby group.

2. Replace the standby group with a portchannel or simple GigE before downgrading and restore it after downgrade is complete.

CSCtd28332

Symptom:

Multicast-in-multicast-out (MIMO) Movie Streamer live programs do not work, because the Unicast URL and Multicast URL fields in the CDSM GUI are exactly the same.

Condition:

This happens when creating a Movie Streamer live program with the multicast-out option.

Workaround:

No workaround so far, currently we cannot create MIMO Movie Stream live programs.

Service Monitor

CSCte10655

Symptom:

The major alarm for disk failure count is not cleared although the disk failure count threshold is cleared.

Conditions:

Enter the show running-config command, displays two port channels configured on the device and the show service-router service-monitor command displays disk failure count threshold enabled.

Workaround:

To ensure that the major alarm gets cleared, do the following:

1. Shut down one of the port channels.

2. Bring up the port channel again after the major alarm has cleared.

Resolved Caveats

The resolved caveats section has the following subsections:

Resolved Caveats in Release 2.5.3-b37

Resolved Caveats in Release 2.5.3-b36

Resolved Caveats in Release 2.5.3-b35

Resolved Caveats in Release 2.5.3-b34

Resolved Caveats in Release 2.5.3-b15

Resolved Caveats in Release 2.5.3-b37

CSCtj38623

Symptom:

WMT MBR—when seeking backwards, playing stops.

Condition:

This occurs in a two-tier topology.

1. Create a VOD delivery service.

2. Request MBR preposition content and play this content for some time.

3. Seek backwards and the streaming stops.

CSCtk95283

Symptom:

On a race condition of a MBR cache-miss scenario, the FE and the BE may not sync with each other for the bitmap file, causing the BE to wait for a data block until timeout. During this time, video freeze occurs.

Condition:

Occurs in certain MBR cache-miss scenarios.

CSCtk64570

Symptom:

When a WMT stream is playing in a VOD cache-miss scenario and the client is using RTSP interleave mode, the stream sometimes freezes for several minutes before resuming play.

Condition:

This happens only in a VOD cache-miss scenario when the client uses RTSP interleave mode.

CSCtk65149

While a cache fill is in progress, if multiple BEs attach to the same bufobj and one of the users performs a seek, the block range of bufobj may change, causing a freeze for other users.

Condition:

This happens when a cache fill is in progress while multiple users are viewing the same content and performing some trick operations.

CSCtl07928

Symptom:

HTTP files are corrupted when files are downloaded partially on the Content Acquirer and the Edge SE.

Condition:

This issue can be observed after you perform the following steps:

1. Issue the request to Content Acquirer

2. Issue the request to Edge SE.

3. Terminate the Edge SE session. (The Edge SE would continue to cache data from Content Acquirer, despite terminating the client request.)

4. Terminate the Content Acquirer session. (The caching of the file would continue on both SEs; it would complete on the Content Acquirer, but some lag would be observed on the Edge SE.)

5. Send a new request to the Edge SE and terminate it. (By this time, the Edge SE would have also cached the content completely.)

6. Check the file size, UNS lookup and the MD5 checksum. The MD5 check sum on the Edge SE is incorrect.

CSCtl17888

Symptom:

Incorrect file size and MD5 check sum reported by the Edge SE on repeated client abortions.

Workaround:

In a two-tier setup, when you stress the Edge SE with 100 cache-miss requests and repeated client abortions using Spirent, and retry the connections a number of times, with Web Engine pacing settings being changed frequently in the interim, the file size reported on the Edge SE is larger than the file size on the Origin Server. This leads to data corruption as well as an incorrect MD5 checksum. This issue was found during a a Web Engine pacing configuration change, but also applies to other configuration changes.

Resolved Caveats in Release 2.5.3-b36

CSCti92988

Symptom:

Non-standard Quicktime Streaming Server format appears. Sawmill recognizes QTSS by the W3C header:

  #Software: QTSS 
  #Software: DSS 
 
   

The following header will not work:

  #Software: Cisco-CDS Version: 2.0.0 Remark: all time values are in GMT.
 
   

Condition:

A new format, not yet supported by Sawmill.

CSCtj38736 [LOW IMPACT]

Symptom:

Sometimes the cms service restarts when a program is being scheduled in the CDSM GUI (Live Programs > Schedule). Users are logged out from the GUI and need to log back in again.

Conditions:

When scheduling a program by using CDSM GUI.

CSCtj65755

Symptom:

When navigating to System / AAA / Domains / Entity Management as a TACACS user, an access forbidden (403) message is presented.

Conditions:

Login as a TACACS user.

CSCtj69901 [MEDIUM IMPACT]

Symptom:

When a client sends a request for a live program it does not play. Run the show statistics wmt streamstat command on the SE, and the output shows the stream is in PLAY, but no data is sent out.

Conditions:

The SE does not send packets to a client under Windows Media Streaming live program.

CSCtk12244

Symptom:

The data of the linked list is corrupted and causes an endless loop when the list is traversed.

Conditions:

Occurred once in a location leader when upgrading from Release 2.5.3 b34 to Release 2.5.3 b35.

CSCte64034

Symptom:

Request is not redirected to the SE with lower metric.

Conditions:

When there are more than one SE that can be chosen for a a particular client IP address, the SEs are assigned different metrics and when the SE with the lowest metric has reached its burst rate threshold.

CSCtk06918

Symptom:

Memory usage of Service Router is very high.

Condition:

When the Coverage Zone file has zero networks configured.

CSCth84349

Symptom:

When the no-cache action is configured for Windows Media Streaming, the exceed-max size counter is getting incremented, instead of the cache bypass counter, which should be incremented.

Condition:

When configuring the service rule for No-cache action and running a Windows Media Streaming client request.

Resolved Caveats in Release 2.5.3-b35

Web Engine

CSCth28650

Symptom:

The device reloads when the debug http service-router or undebug all commands are entered.

Condition:

When the debug http service-router or undebug all commands are entered.

Workaround:

Do not enter the debug http service-router or undebug all commands. If you encounter this problem, contact Cisco customer support.

CSCtj19942

Symptom:

Simultaneous non-range requests are redirected to origin server.

Conditions:

In 2.5.3 we will always send range-requests to the origin server, until the entire file is fully cached. Once the content is cached by using the "Cache fill Range" setting for the first range request, subsequent requests must not go to the origin server.

If a client request is a "Range" request and it for the first range starting from byte "0" of content, then the "Range" header is unset from the request and a GET request is sent to the origin server. This makes the origin server reply with a "200 OK" response, which is cached along with the updated metadata for the content.

Subsequent range requests are served from the SE cache as the content is fresh enough to be served for client, and the request is not sent to origin server until the next time the time-to-live (TTL_ expires.

CSCtd42838

Symptom:

The CDSM has more rpc_httpd processes and all the SEs go offline.

Conditions:

The SSL_Mutex should be global, but it was not for different invocations of the httpd process.

Service Routing

CSCtg96216

Symptom:

The service chosen depends completely on the user agent. So if there is a request from a user agent that is not supported by the Service Router, the default service is chosen. With this fix, we associate file extension types with specific players, instead of using the default service when the user agent is not supported.

Condition:

When the request is from non-supported user agent.

Movie Streamer

CSCti94906

Symptom:

The Movie Streamer process enters a core dump, terminating all Movie Streamer sessions from the downstream clients on this SE.

Conditions:

This happens once a Movie Streamer Unicast-In and Multicast-Out (UIMO) live program is configured and Movie Streamer fails to join the specified multicast group.

CDSM

CSCtj20538

Symptom:

Service rule actions configured by using the CLI are lost when Force full database update is clicked.

Conditions:

When this issue occurs under the following conditions:

Only the service rule action CLIs aggregated for a device group are lost.

Lost CLI configuration can be recovered by clicking the Force full database update button again.

GUI configuration is not lost, nor are the individual CLI SE configurations.

CSCte82376

Symptom:

The System-Wide Bandwidth Served table legend is incorrectly labeled. Instead of saying "Table values are expressed in bytes per second." it should say "Table values are expressed in bits per second."

Conditions:

Click View Detailed Report for System-Wide Bandwidth Served. Table to the right of the graph has the wrong unit of measure.

CSCtf05775

Symptom:

The cms log file prints all the stored upgrade patch information, even though the old path is not used, it is printed as well.

Conditions:

When there is a stored upgrade.

Windows Media Streaming

CSCtg91339

Symptom:

There are no requests for Windows Media Streaming content with a file size greater than the maximum object size configured; however, the statistic for "Exceed max-size" is increased.

Conditions:

When the first request from the client is a fast-forward or rewind request, the "Exceed max-size" statistic is increased.

CSCtj40968

Symptom:

Windows Media Streaming core dumps when parsing a corrupted ASF header.

Conditions:

When the message body size value in the ASF header and the actual message body size does not match.

CSCtj41000

Symptom:

When playing a stream by using HTTP, Window Media Streaming core dumps. It occurred when requests for a session come in, but the internal data structure maintaining the session already terminated it.

Conditions:

This occurs when the edge SE or client has not received termination notification, but the upstream SE has already terminated session.

CSCtg74743

Symptom:

Video abort/teardown issue with random playback.

Conditions:

Window Media Streaming playback might send a video aborted message when trying to view a stream.

CSCtg91264

Symptom:

Sometimes Windows Media Streaming fast cache is disabled, but the SE is still performing fast cache.

Conditions:

Under which conditions this occurs is not clear.

CSCtc98771

Symptom:

The output for the show statistics wmt streamstat command displays stale sessions in either setup, play, or pause states.

Conditions:

The Content Acquirer has a misconfigured streaming interfaces, which increases the possibility of creating a hanged session.

CSCte70234

Symptom:

Window Media Streaming core dumps when the session is being teared down.

Conditions:

When waiting for a pause response from the origin server, an RTP packet is received.

CSCth58862

Symptom:

Video hang issue is seen in a specific scenario. When seeking to a time point, the player hangs for several minutes.

Conditions:

The request goes through three tiers, seeks to a point, then closes the player. Then a new player is started and the seek goes to the same time point. After repeating the above steps several times, the end user might see the hang issue.

CSCti58938 [LOW IMPACT]

Symptom:

The Windows Media Streaming engine process enters core-dump, which terminates the offending client session. All other Windows Media Streaming sessions on this SE continue to function properly.

Condition:

Not confirmed. Two core dump files are found on a test bed and both are because of a PAUSE request coming from another edge SE that has unclean XFS issues.

UNS Server

CSCtj04740

Symptom:

Memory is corrupted at a specific location. This particular location can cause a UNS thread to go into an infinite loop, all other UNS threads can potentially get blocked while they wait for this thread to finish. This causes high CPU usages for UNS process.

Conditions:

Various URL requests.

URL Manager

CSCtj30209

Symptom:

When URL is not signed correctly and has %20, NULL is returned for a strchr operation.

Conditions:

NULL check is missing for a strchr.

Authorization Server

CSCth37786

Symptom:

Occasional restart of Authorization server during delivery service configuration update.

Conditions:

Service Engines in a delivery service are added and removed in quick succession.

Platform

CSCsy56641

Symptom:

The CDE220-2G2 goes into KDB mode when loading a .bin image from the installer.

Conditions:

Caused by way of the XFS message board, adding a synchronized fix. This rarely happens.

Resolved Caveats in Release 2.5.3-b34

The following resolved caveats were identified in Release 2.5.3-b34:

CSCth05856

Symptom:

SEs go intermittently offline and come back online and alarms are generated.

Conditions:

Happens when a large Coverage Zone file is uploaded (4 MB) with several thousand entries.

CSCth86190

Symptom:

SE does not get picked for routing even though it has a lower metric.

Conditions:

After SE transit from offload back to online, SR does not redirect requests to it.

CSCth27308

Symptom:

Because the wrong error code is returned, the URL validation passes.

Conditions:

A signed URL with "s" tag value is missing.

CSCte80412

Symptom:

There is a delay of approximately one second in the request being redirected to a Service Engine.

Conditions:

When the browser used is Firefox or Safari.

CSCti30585

Symptom:

The Authorization Server stops because of signal 6. A core dump is generated.

Conditions:

A very large Authorization XML file is uploaded containing repeated values of IP addresses and various combinations of subnet masks.

CSCti56480

Symptom:

Devices may lose some configurations after reload, upgrade, or downgrade. Sometimes all configurations are lost.

Conditions:

Before the device reboots, the file /local/local1/.running_backupfile exists. If this file is not the same as the running-config, or after a reload the configuration commands changed, the configuration is lost.

CSCti89422

Enhancement:

Allow caching to continue regardless of when client aborts the download. Allow the cache-on-abort threshold to be configured to 0 percent. Valid range changed to 0-99 from 1-99.

Conditions:

Setting cache-on-abort threshold to 0 percent allows cache fill to continue regardless of when the client disconnects.

Resolved Caveats in Release 2.5.3-b15

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

Windows Media Streaming

CSCtb54485

Symptom:

When multiple bit-rate live stream-splitting serves two Windows Media player with different connection speeds (for example, 128kbps and 768kbps), the first player plays the stream, but the stream stops when the second player sends an RTSP request, even though the second stream would stay up.

Condition:

A player is connected to the edge SE of a Windows Media Streaming live stream, and a second player joins the same live stream at a different bit-rate.

CSCte10313

Symptom:

Windows Media Streaming process crashed and dumped core with playback of server-side playlist.

Condition:

When the client clicks pause and SE forwards the log to origin server, the origin server returns a stream switch request causing the crash.

Further problem description:

Fix is isolated to Windows Media Streaming streaming. No impact to other subsystems.

CSCte94654

Symptoms:

Run Windows Media Streaming streaming stress test of all-unique requests, sometimes some sessions may hang and cannot be released.

Conditions:

Windows Media Streaming streaming stressed tests.

Further problem description:

Fix is isolated to Windows Media Streaming streaming. No impact to other subsystems.

CSCtf07360

Symptom:

MBR VOD payback sometimes fails for a large file.

Conditions:

Occurs when Fast Cache is enabled.

Further Problem Description:

Fix is isolated to Windows Media Streaming. No impact to other subsystems.

CSCtf26064

Symptom:

The CDS cannot serve specific Windows Media Player requests.

Conditions:

When a Windows Media player sends an OPTION method as the first RTSP method and Movie Streamer is disabled, the request cannot be served by CDS-IS Windows Media Streaming module.

Further Problem Description:

Enable RTSP Gateway to direct OPTION method header request to Windows Media Streaming, no impact to other subsystems.

Flash Media Streaming

CSCsz23407

Symptom:

A minor alarm is generated on the SE stating that the fmsadmin process is down. The following sentry is added to the syslog:

"%SE-UNKNOWN-3-899999: Failed to create listener for adaptor, IP 127.0.0.1, port 
11110: TCCommBridge::createListener 127.0.0.1:11110/v4: bind failed!!!." 
 
   

The show statistics flash-media-streaming command does not work.

Condition:

This issue happens randomly once Flash Media Streaming is restarted or the SE is restarted. This issue happens because fmsadmin process port was taken by some other process.

Further Problem Description:

No other modules are affected because the fix changes the internal communication port numbers.

CSCte91008

Symptom:

The fms_stats_daemon process has a very slow memory leak with memory usage steadily increasing. As the memory usage increases, there could be a point when the SR stops forwarding requests to this SE.

Conditions:

The memory leak in fms_stats_daemon is triggered by a periodic function. Stats daemon periodically collects statistics whether any RTMP request are served by the SE or not. As long as Flash Media Streaming is enabled, this process runs.

Further Problem Description:

No extra test required as the fix is very much inside stats daemon periodic function.

Service Router

CSCtf23634

Symptom:

The SR picks an SE, but the Flash Media Streaming process receives a different SE from the SR.

Condition:

When an SE (SE1) is provisioned for live content and another SE (SE2) for VOD content, if both are available for streaming, the issue can be seen more prominently. If instead of SE1, SE2 is selected, it might not be able to serve the corresponding live or VOD content.

Further Problem Description:

Fix is isolated to SR module. No impact to other subsystems.

CSCte85557

Symptom:

SR returns 0.0.0.0 instead of primary interface IP address.

Conditions:

When the SR is rebooted with the standby as the primary interface and individual or port channel interfaces are added to the standby.

Further problem description:

Fix in loading network interface ordering from dataserver. No impact to other subsystems.

CSCte70302

Symptom:

Failed to remove or change errordomain and errorfile under lastresort configuration.

Conditions:

When the length of the command exceeds 130 characters.

Further problem description:

Fix in SR configuration utility. No impact to other subsystems.

Proximity Engine

CSCtd39820

Symptom:

Service Router may not redirect client requests based on the correct IGP proximity rating when proximity based routing is configured.

Condition:

One or more Service Engines or the client requesting content are in a subnet advertised as a BGP route with its next-hop also advertised by BGP and only BGP.

CSCtd30613

Symptom:

When the Proximity Engine contains a large number of OSPF types 7, 9, 10, or 11 LSAs, using the show ip ospf database detail command may cause OSPF process to restart.

Condition:

The problem can only happen when OSPF is enabled on the Proximity Engine, when the Proximity Engine has hundreds of type 7, 9, 10, or 11 LSAs in the OSPF database, and when the show command show ip ospf database detail is entered.

Service Monitor

CSCte87906

Symptom:

Service monitor has a memory leak. It appears to be leaking 4K of memory every 30 seconds. The top or show process system command shows the process leaking memory over several days, The show service-router service-monitor command shows the memory usage increasing 1 percent over several days.

Conditions:

Found in Release 2.4.3 and Release 2.4.5.

Platform

CSCtd95377

Symptom:

After upgrade to Release 2.5.1, the configuration line defining the default gateway disappears after reloads.

Condition:

This is seen after reload during and after upgrade, on devices that have a standby group interface configured as the primary interface.

CSCta27060

Symptom:

The link state of a switch port will always be "up" when connected to a fiber GigabitEthernet interface on the SE. Depending on how PortChannel and load-balancing are configured, this may cause the switch to send packets to a shutdown interface on the SE.

Condition:

When the "shutdown" CLI is manually configured on a connected fiber GigabitEthernet interface.

CSCtd21115

Symptom:

Using the clock timezone command to configure a custom daylight savings time is not supported in Release 2.5.1.

Condition:

When configuring a custom daylight savings time as the time zone on a device using the CLI, results in a "Custom daylight savings time are unsupported at this time."

CSCte20834

Symptoms :

When running Windows Media Streaming streaming traffic, the SE go into KDB if KDB is enabled; otherwise, the device reboots.

Conditions :

Running Windows Media Streaming cache miss streaming tests. This issue is extremely hard to reproduce.

Further problem description:

Fix has no impact to other subsystems.

CDSM

CSCte74664

Symptom:

Content URL removal cannot work sometimes when a request to remove a content URL is sent from the GUI or using the API.

Conditions:

If all IP addresses assigned to the interfaces (including streaming and management) are reachable from the CDSM to the SE, content URL removal works correctly; otherwise, the functionality of content URL removal may fail.

Workaround:

Need to guarantee that the IP address assigned to the interfaces (including streaming and management) are all reachable from the CDSM to the SE.

CSCte26524

Symptom:

Primary CDSM always show as "rebooting."

Condition:

The primary CDSM always display as "rebooting" even it has completed boot up.

CSCtd32222

Symptom:

When an upgrade is pending by way of the CDSM, there is no way to cancel it.

Condition:

Configure an upgrade on the standby CDSM by using the primary CDSM, determine that the configuration is wrong. Upgrade the standby CDSM by using the CLI. After upgrading the standby CDSM , the primary CDSM GUI still shows the upgrade pending for more than 20 minutes after the the standby is up.

CSCtd66502

Symptom:

If the task bar Deactivate button is clicked in the Device Activation page for a primary CDSM, the primary CDSM is placed into offline status. The Deactivate button is only applicable to the standby CDSM.

Conditions:

From Primary CDSM Device Activation page, click the Deactivate button in the task bar.

Further Problem Description:

Remove the Deactivate button from primary CDSM. There is no impact to other subsystems.

CSCte45405

Symptoms:

If the SR management communication IP address configured is not the primary interface, the show commands and clear commands cannot reach the SR and no response is returned.

Condition:

For the SR, choose Devices > Device Activation and configure the management IP address as something different than primary interface address.

Choose Devices > Monitoring > Show/Clear Commands and Show Commands or Clear Commands. and submit a show or clear command.

Further Problem Description:

If the management communication IP address is not reachable, the show or clear command does not work.

CLI

CSCte61907

Symptom:

When a query is sent to the CDS-IS as NTP server, the response has information similar to the following: processor='x86_64', system='Linux2.6.23.9-cds-64'.

Conditions:

Configure CDS-IS as NTP client and query it as NTP server.

Further Problem Description:

If more than one NTP server needs to be configured, configure them using one command, for example:

(config)# ntp server 10.0.0.16 10.74.61.108
 
   

Network

CSCte76934

Symptom:

Static IP routes are appended with interface x.0.0.0 after upgrading from Release 2.4.x to Release 2.5.1 or Release 2.5.3.

Condition:

This only happens when you have existing static IP routes configured and you upgrade to Release 2.5.1 or Release 2.5.3.

Further problem description:

Fix has no impact to other subsystems.

CSCtf01052

Symptoms:

After upgrading from Release 2.4.x to Release 2.5.3, static routes may get lost.

Conditions:

Upgrading from Release 2.4.x to Release 2.5.3.

Further problem description:

Fix is within static route configuration. No impact to other subsystems.

CSCte05421

Symptoms:

Network connectivity sometimes works and sometime doe not. When checking the routes by using the show ip route command, all default gateway and IP routes are there.

Conditions:

The port-channel load-balance command toggles interface down and up. After that, Linux removes per interface IP route table. Proper restoration does not occur in the CLI . Sometimes this command is sent by CDSM during registering to CDSM.

Further problem description:

Fix is isolated to this command. There is no impact to other subsystems.

CSCte63230

Symptoms:

Standby interface core dumps. See core alarm on standby.

Conditions:

When the current member in a standby group is down, the standby daemon tries to bring up another member interface and the standby process core dumps.

Further Problem Description:

Fix is in the standby module. No impact to other subsystem.

Upgrading to Release 2.5.3

The only supported upgrade paths are Release 2.4.x to Release 2.5.3 and Release 2.5.1 to Release 2.5.3. If you are running a release prior to Release 2.4.x, you must upgrade to Release 2.4.x before upgrading to Release 2.5.3.


Note Upgrading to Release 2.5.3 includes SHA-256-encrypted user passwords. If the config file contains users with SHA-256 encrypted passwords, if you downgrade to an earlier release, the user information will be lost because the older software cannot recognize the new method of encrypting passwords.

When upgrading to Release 2.5.3 from Release 2.4.x, configuring the Proximity Server port number field is no longer required for the Proximity-Based Routing feature. The port number for all Proximity servers is 7003.

Note Because the functionality of having the SR act as both the Request Routing Engine and the Proximity Server was not part of Release 2.4.x, downgrading from Release 2.5.x to Release 2.4.x results in losing the configuration of 127.0.0.1 (SR loopback address) as the Proximity Server. All other Proximity Servers are still configured.

URL Public Key Signing

Table 2 describes the compatibility and results when using a prior CDS software release to perform URL signing and the current software release to perform URL validation.

Table 2 Release Compatibility of URL Signing and URL Validation

Release Used for URL Signing
Release Used for URL Validation
Results

2.3.x

2.4.3, 2.4.5, or 2.5.x

Does not work because the Release 2.3.x URL signing uses the port and schema for signing, but the port is stripped off during validation by the current software release.

2.4.3

2.5.3

Works for URL signing version 0, 1, or 2. and will not work for version 3 (CSCtb99898).

2.4.5

2.5.3

Works for URL signing version 0, 1, or 2. and will not work for version 3 (CSCtb99898).

2.5.1

2.5.3

Works for all versions.


Documentation Updates

The following documents have been added for this release:

Release Notes for Cisco Internet Streamer CDS 2.5.3

The following documents have no changes:

Cisco Internet Streamer CDS 2.4-2.5 API Guide

Cisco Internet Streamer CDS 2.4-2.5 Quick Start Guide

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

Cisco Internet Streamer CDS 2.5 Software Configuration Guide

Cisco Internet Streamer CDS 2.5 Command Reference Guide

Cisco Internet Streamer CDS 2.5 Alarms and Error Messages Guide

Related Documentation

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

Cisco Internet Streamer CDS 2.5 Software Configuration Guide

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

Cisco Internet Streamer CDS 2.4-2.5 Quick Start Guide

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

Cisco Internet Streamer CDS 2.4-2.5 API Guide

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

Cisco Internet Streamer CDS 2.5 Command Reference Guide

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

Cisco Internet Streamer CDS 2.5 Alarms and Error Messages Guide

http://www.cisco.com/en/US/docs/video/cds/cda/is/2_5/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

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

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

Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide

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

Regulatory Compliance and Safety Information for Cisco Content Delivery Engines

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

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.