 Feedback
|
Table Of Contents
Release Notes for Cisco Internet Streamer
CDS 2.4.5Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Internet Streamer
CDS 2.4.5
These release notes cover Cisco Internet Streamer CDS Release 2.4.5-b3.
Revised: December 2009,OL-21469-01Contents
The following information is included in these release notes:
•
Obtaining Documentation and Submitting a Service Request
Release 2.4.5 consists of resolved caveats. See the "Resolved Caveats" section for more information.
Note
Note
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
CDSM
Yes
No
Yes
No
SR
No
Yes
Yes
Yes
SE
No
Yes
Yes
Yes
Release 2.4.5 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/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/420 Hardware Installation Guide for set up and installation procedures for the CDE205.
Note
Limitations and Restrictions
This release contains the following limitations and restrictions:
•
•
Note
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.
Important Notes
To maximize the content delivery performance of a CDE200, CDE205, or CDE220, we recommend you do the following:
1.
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.
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
3.
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.
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.
Resolved Caveats
The following caveats have been resolved since Cisco Internet Streamer CDS Release 2.4.3. Not all the resolved issues are mentioned here. The following list highlights the resolved caveats associated with customer deployment scenarios.
Windows Media Streaming
•
Symptom:
Because the content is very specific (encrypted flag in ASF file is 1), client sends a request with stream-switch-entry=ffff:8001:0 ffff:8002:0. 8001&8002 are flags of ASF file only 0~6 bits are used as stream number. This case is not addressed.
•
Symptom:
DSCP value not set for RTSP.
•
Symptom:
SE marks fast-cache for RTSPT when fast-cache is disabled.
•
Symptom:
Only audio is available when HTTP request is used to playback some of the media files. These media files have an audio track == 1 and a video track = 31.
•
Symptom:
SE to send A-record instead of AAAA-record for DNS resolution.
•
Symptom:
Windows Media Streaming core dumps during testing of live streaming.
Conditions:
This happens when a server-side playlist (SSPL) source is used and automation scripts are used as clients.
Flash Media Streaming
•
Symptom:
Rule-enable configuration does not persist across a reboot. After a system reboot, the rule enable configuration is not being set in shared memory, which results in inconsistent rule allow/blocking behavior across reboot.
Kernel Streaming Engine
•
Symptom:
Client disconnecting triggers internal error in Windows Media Streaming.
•
Symptom:
Windows Media Streaming hand off causes KDB crash.
•
Symptom:
Memory leak occurred when Windows Media Streaming delivery service is configured with Primed configuration for a live radio delivery service.
Acquisition and Distribution
•
Symptom:
Virtual memory size exceeds limit causing acquisition and distribution processes to get disabled and exit.
•
Symptom:
Disk quota exceeds limit causing Content Acquirer to restart loop.
URL Manager
•
Symptom:
When a client sends a request for live Flash Media Streaming content with a signed URL using a private key and a .flv extension, a core dump occurs.
•
Symptom:
The first request from client is SETUP not DESCRIBE. This is not handle this case properly.
Service Router
•
Symptom:
The SR transactions per second (TPS) drops to 200 when proximity cache-hit case.
•
Symptom:
The SR returns an empty DNS response for AAAA if IPv6 is not configured.
•
Symptom:
When there are multiple cache entries for the same route, the one with longest match is used. However, once the matched one expires, the SR ignores the other valid one and sends a proximity request to the Proximity Engine for all future client requests from that subnet. This causes a performance issue since the cache-miss transactions per second (TPS) is a lot lower than the cache hit TPS.
•
Symptom:
SR core dumps when Proximity Engine or location-based routing is under stress.
SNMP
•
Symptom:
SNMP MIB incorrectly reports that CPU on SR and Content Acquirer is at 100 percent.
Platform
•
Symptom:
Some hard disk drives are not recognized when the CDE200 gets a cold restart.
Service Monitor
•
Symptom:
Alarm ID is wrong for CPU and memory thresholds. Alarm 560006 is for disk fail count, while 560001/560002 are for cpu/mem alarm.
Upgrading to Release 2.4.5
The only supported upgrade paths are Release 2.4.x to Release 2.4.5 and Release 2.3.x to Release 2.4.5. If you are running a release prior to Release 2.3.x, you must upgrade to Release 2.3.x before upgrading to Release 2.4.5.
Note
1.
2.
3.
4.
5.
6.
7.
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.
Documentation Updates
The following documents have been added for this release:
•
The following documents have no changes:
•
•
•
•
•
•
Related Documentation
Refer to the following documents for additional information about the Cisco Internet Streamer CDS 2.4:
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_4/configuration_guide/is_cds24-cfguide.html
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_4/quick_guide/ISCDSQuickStart.html
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_4/developer_guide/is_cds_24_apiguide.html
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_4/command_ref/Command_Ref.html
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_4/message_guide/Messages.html
•
http://www.cisco.com/en/US/docs/video/cds/overview/CDS_Roadmap.html
•
•
http://www.cisco.com/en/US/docs/video/cds/cde/installation/guide/CDE_Install_Book.html
•
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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card 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. (0907R)
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.
© 2009 Cisco Systems, Inc. All rights reserved.
