Table Of Contents
Release Notes for Cisco Internet Streamer
These release notes cover Cisco Internet Streamer CDS Release 2.3.7-b3.Revised: March 2009,OL-19454-01
The following information is included in these release notes:
Release 2.3.7 introduces the CDE220 2G2 platform. There are a total of ten gigabit Ethernet ports in this CDE. In Release 2.3.7, six of the ports are supported as follows:
•First two ports (1/0 and 2/0) are management ports.
•Next four ports ( 3/0. 4/0, 5/0, and 6/0) must be shut down using the CLI commands, and no Ethernet cable should be connected to these four ports.
•Last four ports (7/0, 8/0, 9/0, and 10/0) can be configured as one port channel.
This is the only supported configuration in Release 2.3.7.
The Internet Streamer CDS runs on the CDE100 and CDE200 hardware models. The CDE100 may run as the CDSM, while the CDE200 may 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.
Limitations and Restrictions
This release contains the following limitations and restrictions:
•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.
To maximize the content delivery performance of a CDE200, we recommend you do the following:
1. Use port channel for all client-facing traffic.
Configure interfaces number 3, 4, 5, and 6 (those on the quad-port Gigabit Ethernet Card) 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.0-2.3 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.
3. Tune the TCP parameter.
On the CDE200, execute the following commands once (This tunes the internal TCP configuration for better content delivery performance over HTTP.):Config# tcp server-satelliteConfig# tcp client-satelliteConfig# write memory
4. For high-volume traffic, separate HTTP and WMT.
The CDE200 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 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 servers than usual.
5. 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.
6. 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.
This release contains the following open caveats:
Flash Media Streaming
For pre-positioned MPEG-4 files, the show statistics flash-media-streaming command shows the reads as happening by way of HTTP.
This occurs only for MPEG-4 files ( files with the following extensions: 3gp, mp4, m4v, f4v 3g2, or mov). Even though Flash Media Streaming is responsible for the streaming, Flash Media Streaming reads from an HTTP socket. Because this increases steps in serving H264 files, it affects the H264 performance.
The Flash Media Streaming Admin Allow Hosts (Devices > Application Control > Flash Media Streaming > FMS Admin Allow Hosts) configuration does not display for the show running command.
When you reload the SE, the FMS Admin Allow IP list is gone.
After rebooting the SE, reconfigure the FMS Admin Allow Hosts.
The Flash Media Streaming concurrent connection count keeps increasing, even if the client disconnects. Sometimes Flash Media Streaming is not receiving the disconnect events. This may result in the SR not considering this SE when forwarding requests.
The issue was seen during a longevity test using the Flash load tool. During this testing, some of the disconnect events are not processed by Flash Media Streaming. This causes the connection count to remain the same, even though the netstat command shows the connections as closed.
Disable and re-enable Flash Media Streaming to bring the count down to zero. The Flash Media Streaming process is rolled over to a new instance after three and a half days. The rollover process can live a maximum of another three and a half days. Hence, the statistics count eventually goes down within seven days.
When an RTMP request with a signed URL is sent from the portal to the SE, even if the file is pre-positioned on the SE, the SE proxies the request and fills the cache with the content.
This happens only for pre-positioned content and if the requested URI has a query.
Enable the ignore_query_string flag in the Manifest file during pre-positioning.
Client attempts to open a unicast SDP URL to the SE. The client receives an RTSP 415 error code, "Unsupported Media Type."
A live program name was created with uppercase characters fails to play.
Use only lowercase characters when naming a program.
Choose Application Control > Flash Media Streaming > General Setting. Click Apply Default, the License Agreement page does not display.
If the General Settings for Flash Media Streaming is set using a Device Group, and then an SE is configured with Flash Media Streaming, the General Settings page displays the Select a Device Group drop-down list, which allows the user to select the Device Group the SE will be a member of. If the Device Group that is selected has Flash Media Streaming enabled, the Flash Media Streaming License page is not displayed.
Take the following actions to resolve this issue:
a. Unassign the SE from the Device Group that has the Flash Media Streaming enabled. This allows the Flash Media Streaming License page to display when the SE is configured with Flash Media Streaming.
b. Go to the Device Group's General Settings page for Flash Media Streaming and click Force DG settings to SEs. This forces the configuration from the Device Group to the SE, and makes the SE-specific pages read-only.
When an SE is reloading, the Flash Media Streaming Wholesale License page in the CDSM does not respond, the page is blank for several seconds, and a warning dialog box displays, "The creation/modification will not proceed."
None. The issue does not impact the functionality of the CDSM. All pages except the Wholesale License page, are responsive.
None. The CDSM recovers after about five minutes.
Try to create multiple MIB name associations with a single MIB-view in the CDSM Devices > General Settings > Notification and Tracking > SNMP > View. Creating a second association results in an error message stating the view with name <viewname> is already available, and the configuration is refused. A core dump of cfg_bin_snmp_view occurs on the SE, SR, or CDSM.
Create the SNMP views locally on the device, using the CLI. The CLI accepts the views and displays them in the show running command. On the CDSM, choose Devices > General Settings > Notification and Tracking > SNMP > View. The views are listed. However, you cannot create multiple associates in the CDSM.
Acquisition and Distribution
Pre-positioning content to receiver SEs can sometimes be interrupted. This causes the UniReceiver process to put the SE to go into KDB mode.
If acquisition and distribution is stopped using the acquisition-distribution stop command on the upper tier SEs. The lower tier SEs might get incorrect data from the upstream SEs.
The UniReceiver process should recover automatically after the crash. For the content that had interrupted downloads, the content will be distributed based on user demand.
Core dump of 'standby' process is found.
Run a long performance stress test, after one or two days, the core file is found.
There is no need for a workaround. The 'standby' daemon is automatically restarted. No functionality impact.
Caveats Not Caused by CDS Software
This release contains the following open caveats that are not cause by the CDS software:
Windows Media Streaming
When using a file as the type of source for a live publishing point in Windows Media Server 2008 Standard, after starting multiple streaming requests from that publishing point, when the first stream reaches the end of the source file the second and subsequent streams fail with an error message at the same time. If Windows Media Server 2008 Standard is used as the origin server for a delivery service in CDS-IS, the second and subsequent streams will not fail, but will repeatedly loop the last segment of the stream.
Publishing points can be created using other source types (for example, playlists) rather than a file as the source type with the Windows Media Server 2008 Standard. The symptom described above is not seen with windows Media Server 2008 Enterprise used as the origin server.
The following caveats have been resolved since Cisco Internet Streamer CDS Release 2.3.1 Not all the resolved issues are mentioned here. The following list highlights associated with customer deployment scenarios.
Flash Media Streaming
When an RTMP request specifies port 1935, the request fails.
This happens only for RTMP requests that specify port 1935.
A request for live Flash Media Streaming goes into a loop from one SE to another.
SE1(edge SE) ---> SE2(location leader) ---> SE1 (edge SE)
The show flash-media-streaming livestreams command on SE1 shows SE2 as the forwarder, and SE2 shows SE1 as the forwarder.
This happens on a rare condition, and it is only expected under the following circumstances:
–URL is RTMPT
–RTMP with port number
–RTMPT with port number
–URI ends with a /
The probability of experiencing this problem is the following:
–If a location has one or two SEs, the problem is not experienced.
–If a location has three SEs, the probability is very high.
–If a location has greater than three SEs, the possibility is greatly reduced.
Upgrading to Release 2.3.7
In order to upgrade to Release 2.3.7 from Release 2.2, the following changes between Release 2.2 and Release 2.3.7 need to be considered:
•If IP-based redirection is configured on the Service Router, the Coverage Zone file needs to be modified to reflect this change.
•In Release 2.3.7, SSH is enabled by default and Telnet is disabled by default. If a device is upgraded from Release 2.2 or an earlier release to Release 2.3.7, Telnet will not be enabled. If required, Telnet can be re-enabled by using SSH or console access.
In Release 2.3.3, Network Interface Card (NIC) failure detection and alarm reporting was added. When a Release 2.3.3 system boots without a network cable connected to an Ethernet interface or the interface is not configured, a minor alarm is tripped for each instance. The alarm is deactivated once a cable is connected and the interface is configured and brought up. Following is an example of the NIC alarms displayed.Minor Alarms:-------------Alarm ID Module/Submodule Instance-------------------- -------------------- -------------------------1 shutdown nic GigabitEthernet 1/02 shutdown nic GigabitEthernet 2/03 shutdown nic GigabitEthernet 3/04 shutdown nic GigabitEthernet 4/05 shutdown nic GigabitEthernet 5/06 shutdown nic GigabitEthernet 6/0
Note The only supported upgrade paths are the following:
•Release 2.2 to Release 2.3.1, Release 2.3.3, Release 2.3.5, or Release 2.3.7
•Release 2.3.1 to Release 2.3.3, Release 2.3.5, or Release 2.3.7
•Release 2.3.3 to Release 2.3.5 or Release 2.3.7
•Release 2.3.5 to Release 2.3.7
If you are running a release prior to Release 2.2, you must upgrade to Release 2.2 before upgrading to Release 2.3.
The following documents have been updated for this release:
•Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
•Cisco Internet Streamer 2.0-2.3 API Guide
•Cisco Internet Streamer 2.0-2.3 Quick Start Guide
The following documents have been added for this release:
•Release Notes for Cisco Internet Streamer CDS 2.3.7
Refer to the following documents for additional information about the Cisco Internet Streamer CDS 2.0-2.3:
•Cisco Content Delivery Engine 205/220/420 Hardware Installation Guide (OL-16887-01)
•Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide (OL-13478-02)
•Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide (OL-13493-04)
•Cisco Internet Streamer CDS 2.0-2.3 Quick Start Guide (OL-15479-03)
•Cisco Internet Streamer CDS 2.0-2.3 API Guide (OL-14319-04)
•Cisco Content Delivery System 2.x Documentation Roadmap (OL-13495-06)
•Regulatory Compliance and Safety Information for Cisco Content Delivery Engine 100/200/300/400 (78-18229-02)
The entire CDS software documentation suite is available on Cisco.com at:
The entire CDS hardware documentation suite is available on Cisco.com at:
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:
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.
CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0809R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.