 Feedback
|
Table Of Contents
Release Notes for Cisco Internet Streamer
CDS 2.5.1Authorization Service with Geographical Blocking
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Internet Streamer
CDS 2.5.1
These release notes cover Cisco Internet Streamer CDS Release 2.5.1-b4.
Revised: November 2009,OL-20687-01Contents
The following information is included in these release notes:
•
Obtaining Documentation and Submitting a Service Request
New Features
Release 2.5 of the Cisco Internet Streamer CDS introduces the following new features:
•
NoteProximity Engine
In Release 2.5, the Service Router has two engines:
•
•
NoteThe Request Routing Engine contains all the functionality that was part of the Service Router in Release 2.4 and previous releases. Because the Service Router now contains the Proximity Engine, the original Service Router functionality has been encapsulated and renamed the Request Routing Engine.
The Service Router can be configured as both the Request Routing Engine and the Proximity Engine, or the Service Router can be configured only as the Request Routing Engine. Additionally, the Service Router can act as a standalone Proximity Engine by not configuring the Request Routing Engine as the authoritative DNS server.
The Proximity Engine contains the functionality of the Proximity Servers used for proximity-based routing. The Proximity Engine peers with network routers and listens in on route updates to get topology and routing path information. This information is used to locate the closest resource in the network. Real-time measurements of reachability and delay are also considered.
Authorization Service with Geographical Blocking
In Release 2.4, when Authorization Service was enabled, client requests from unknown hosts were blocked by default. The Authorization Service verified that all client requests had a router fully qualified domain name (RFQDN) or origin server that is recognized as part of a delivery service.
Release 2.5 introduces functionality to block client requests based on client's geographic locations or the client's IP address. Each delivery service participating in the Authorization Service has an XML configuration file that contains information on the allowed IP address ranges and geographic locations, and the denied IP address ranges and geographic locations.
In order to block client requests based on geographical location, the SE communicates with a Geo-Location server, which maps IP addresses to a geographic locations. The Geo-Location server, which is the same geo-location server used for location-based routing on the SR, identifies the geographic location of a client request by the country, state, and city of the client.
Enhancements
Table 1 describes the enhancements to Internet Streamer CDS 2.5.1.
System Requirements
The Internet Streamer CDS runs on the CDE100, CDE200, CDE205, and the CDE220 hardware models. Table 2 lists the different device modes for the Cisco Internet Streamer CDS software, and which CDEs support them.
Table 2 Supported CDEs
CDSM
Yes
No
Yes
No
SR
Yes
Yes
Yes
Yes
SE
Yes
Yes
Yes
Yes
Release 2.5.1 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.
NoteLimitations 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.
NoteImportant 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.
Note3.
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.
6.
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
This release contains the following open caveats:
Windows Media Streaming
•
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 WMT live stream, and a second player joins the same live stream at a different bit-rate.
Workaround:
None, but if the first player reconnects (at the same low bit-rate) to the edge SE, it would reestablish the (low bit-rate) stream while the other (high bit-rate) stream would stay up.
•
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
•
Symptom:
This issue happens when switching streams at the end of play duration. The transaction log shows stopping of the stream that is not yet switched to.
Condition:
It only happens when switching at the end of the current playing stream to another stream.
Workaround:
No workaround.
•
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.
•
Symptom:
The issue occurs on the Service Router when too many redirect requests keep coming in, because lots of file descriptors are opened by the Adobe Flash Media Server processes when the system is under stress and the CPU utilization is around 90 percent. A few hours after stopping the test, the memory usage is kept at the same level without dropping.
Condition:
This issue only happens when the CPU usage is about 90 percent and RTMP redirect requests keep coming in.
Workaround:
No workaround.
•
Symptom:
The issue was found in a three-level setup with an interactive application. The client first makes a request for VOD-like streaming to the edge SE and the Flash Media Streaming service is restarted on the edge SE. Then the client makes the same request again, the stream gets closed after about four minutes.
Condition:
This issue only happens in a three-level setup. Two-level setups do not have this issue. Also, this issue only happens when the Flash Media Streaming service is restarted on the edge SE while streaming. Lastly, this issue only happens for interactive applications.
Workaround:
No workaround.
•
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.
Proximity Engine
•
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.
Workaround:
Make sure the BGP next-hop is advertised by IGP.
•
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.
Workaround:
Use the show ip ospf database command.
Platform
•
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.
•
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."
Workaround:
There is no workaround.
CDNFS
•
Symptom:
CDNFS usage shows used storage on a Service Engine that has been unassigned from all delivery services.
Condition:
Content not removed from Service Engine that has been unassigned from all delivery services.
Workaround:
Use the cdnfs cleanup start command to remove the content that remained after unassigning the SE from all delivery services.
Cache Router
•
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
•
Symptom:
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."
Workaround:
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.
•
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.
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:
Stale session in Play state is displayed when the show statistics wmt streamstat command is entered. Even after the session is not increasing the bytes.
•
Symptom:
DSCP value is not set for RTSPU.
•
Symptom:
SE mark 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 has audio track == 1 and video track = 31.
•
Symptom:
SE to send A -record instead of AAAA-record for DNS resolution.
•
Symptom:
Windows Media Streaming core dumps during longevity testing.
Condition:
When multiple bit-rates, live, VOD, and protocols are used and a server-side playlist (SSPL) is used as the live source.
•
Symptom:
Windows Media Streaming core dumps during testing of live streaming.
Condition:
This happens when a server-side playlist (SSPL) source is used and automation scripts are used as clients.
Flash Media Streaming
•
Symptom:
This is regarding location leader loop issue. On further investigation we found the root cause that leads to this looping.
Condition:
The loop happens when the same set of SEs are assigned to both a failed program (the program fails due to encoder failure) and a successful program. When this particular combination occurs, the liveness query is not being sent from the child SE to the parent SE for the successful program. This causes the location leader selection to go wrong resulting in a loop.
•
Symptom:
The FMS core process generates a core dump file.
Condition:
The core dump occurs once in awhile during high-stress scenarios (that is, when the CPU and disk thresholds are reached). The high-stressed scenario is coupled with both cache-hit and cache-miss traffic for MPEG-4 VOD Flash Media Streaming.
•
Symptom:
Flash Media Streaming edge server process keeps printing syslog message on console during SR RTMP performance test.
Condition:
Performance test conditions.
CDSM
•
Symptom:
Priming is enabled but priming is not applied to the live program.
Condition:
When device group based SE assignment to live program and priming configuration are done independently.
•
Symptom:
SNMP settings are not applied to SE via Device Group.
Condition:
When the CDSM is upgraded from Release 2.3 to Release 2.4 and the following SNMP settings were configured in the database: Service Engine (Disk Read, Disk Write, Transaction Logging), Event, and MIB Persistent.
•
Symptom:
The transaction log configuration from device group cannot apply to the SE in this special case.
Condition:
If configure any value from CLI and negative it, a CLI with default value will still show in running config.
•
Symptom:
The CDSM GUI incorrectly accepts the same domain name for the Origin server and the SRDN during a modification of the fields.
Service Router
•
Symptom:
SR core dumps with proximity-based or location-based routing when under stress.
Authorization Server
•
Symptom:
Authorization Server lookup for domain name with mixed-case characters failed.
Acquisition and Distribution
•
Symptom:
Acquisition and distribution processes are exited and the service disabled alarms are raised because the excessive usage of virtual memory. This issue could be due to more acquisition and distribution process usage or could happen in cache-miss scenarios.
•
Symptom:
The Content Acquirer service stops working and the following critical alarm is seen in the output of show alarms detail command:
########################################################################Critical Alarms:----------------Alarm ID Module/Submodule Instance-------------------- -------------------- -------------------------1 svcdisabled nodemgr acquirer<date> <time> <timezone>, Processing Error Alarm, #000081, 2000:330001nodemgr: The acquirer service has been disabled.########################################################################Condition:
This issue happens if any delivery service exceeds its disk quota.
Kernel Streaming Engine
•
Symptom:
Memory leak due to Windows Media Streaming delivery service configured with priming for live radio delivery service.
•
Symptom:
Windows Media Streaming engine hand-off caused KDB.
•
Symptom:
A client disconnecting triggers an internal error in the Windows Media Streaming engine.
Platform
•
Symptom:
Some hard disk drives are not recognized when the CDE200 gets a cold restart.
•
Symptom:
The link state of a switch port is always "up" when connected to a gigabit Ethernet over optical fiber interface on the SE. Depending on how the port channel and load-balancing are configured, this may cause the switch to send packets to a shut down interface on the SE.
Condition:
When the shutdown command is manually entered on a gigabit Ethernet over optical fiber interface
•
Symptom:
Changing the time zone to "daylight savings" (or "summer time") does not take affect.
Condition:
Although the Internet Streamer CDS supports time-zone adjustments, changes to "daylight savings" (or "summer time") do not occur "on-the-fly."
•
Symptom:
If a Service Engine is configured with "dst-ip" as the load-balancing algorithm for a port-channel interface, all the traffic is sent out using only one of the interfaces, regardless of the destination.
SNMP
•
Symptom:
SNMP MIBs are reporting the CPU on the Service Routers and a Content Acquirer as 100 percent, whereas when this is checked with the CLI using the top command, the CPU loading seems to be normal.
URL Manager
•
Symptom:
The first request is SETUP not DESCRIBE so ClientInfo->request_info.request_url is a "000000....." string.
URL Signing
•
Symptom:
RTSPD core dumps when url validation is done using private key signing when URL is signed using public key
Condition:
RTSPD core dump happens and requests are not served.
Upgrading to Release 2.5.1
The only supported upgrade paths are Release 2.4.x to Release 2.5.1. 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.1.
Note
When upgrading to Release 2.5.1, 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.
NoteURL Public Key Signing
Table 3 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 updated for this release:
•
•
•
The following documents have been added for this release:
•
•
•
•
Related Documentation
Refer to the following documents for additional information about the Cisco Internet Streamer CDS 2.5:
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_5/configuration_guide/is_cds25-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_5/command_reference/Command_Ref.html
•
http://www.cisco.com/en/US/docs/video/cds/cda/is/2_5/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 Pulse, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AllTouch, 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, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Fast Step, Follow Me Browsing, FormShare, GainMaker, GigaDrive, HomeLink, iLYNX, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, 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. (0908R)
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.
