Cisco Cisco Internet Streamer Application Release Notes
4
Release Notes for Cisco Internet Streamer CDS 2.2
OL-16951-02
Open Caveats
Config# tcp server-satellite
Config# tcp client-satellite
Config# 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.
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.
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.
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.
Open Caveats
This release contains the following open caveats:
Flash Media Streaming
•
CSCsq35801
Symptom:
The statistics displaying current live and VOD connections may fluctuate during stress testing. It
does not have any adverse effect on the stream quality or transaction logs. These are just
informational statistics and their inaccuracies are benign.
does not have any adverse effect on the stream quality or transaction logs. These are just
informational statistics and their inaccuracies are benign.
Workaround:
Retry the show command after a short interval of time.