Cisco Cisco Internet Streamer Application Notas de publicación

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.

For performance information, see the release-specific performance bulletin.

This release contains the following limitations and restrictions:

There is a 4 KB maximum limit for HTTP request headers. This has been added to prevent 
client-side attacks, including overflowing buffers in the Web Engine.

Standby interface is not supported for Proximity Engine. Use port channel configuration instead.

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.

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, CDE205, or CDE220, we recommend you 
do the following:

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 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.