Cisco Cisco Internet Streamer Application 릴리즈 노트
3
Release Notes for Cisco Internet Streamer CDS 2.4.5
OL-21469-01
Important Notes
Important Notes
To maximize the content delivery performance of a CDE200, CDE205, or CDE220, we recommend you
do the following:
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.
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.
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.
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.
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.
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.
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.