Cisco Cisco Content Acquirer Application Release Notes

Page of 20
 
4
Release Notes for Cisco Internet Streamer CDS 2.5.7
OL-20688-02
  New Features
Note
Multi-port support is only supported on the CDE220-2S3i platform. 
The main reason Multi-port support is added is because a switch has a hard limit of 8 interfaces that can 
be grouped into a port-channel, so in order to fully utilize all 12 gigabit Ethernet interfaces, multi-port 
support was added.
Prior to Release 2.5 only a single streaming interface could be configured; the streaming interface was 
configured as the primary interface. In order to separate management and streaming traffic, the 
management interface was configured as a dedicated management interface by using the CDSM’s Device 
Activation page. A port channel, as well as a standby group, could be created for the management 
interface in order to provide redundancy. In Release 2.5, the streaming interface is introduced for 
streaming content.
Configuring Multiple IP Address in a Private Network
If the CDE220-2S3i has multiple IP addresses and is configured in a private network address space, then 
each internal IP address needs an external NAT entry defined on the main core router or switch.
Configuring a Default Gateway for Multi-Port Support
The IP default gateway can only be configured when the physical network connection and VLAN is 
configured and active on the switch or router. If the VLAN is not ready when you configure the IP default 
gateway, you get an error message stating that the default gateway address is invalid.
Delivery Service-based Service Rules for Web Engine
The Service Rule file is an XML file used to specify the service rules for all the SEs in a delivery service. 
The Service Rule file is only supported for the Web Engine. All other protocol engines should continue 
to configure service rules by device. 
Note
For the Web Engine in Release 2.5.7, the Service Rule file must be used if service rules are to be 
confided.
You do not need to enable Service Rules on each SE for the Web Engine, just create a Service Rule file, 
upload it to the CDS, and select it through for the delivery service. 
The Service Rule XML file supports the following service rule pattern lists in Release 2.5.7:
Domain
SrcIP
UrlRegex
Note
In Release 2.5.7, the Header pattern list is not supported in the Service Rule XML file for the Web 
Engine.
The Service Rule XML file supports the following service rule actions for the Web Engine (HTTP only) 
in Release 2.5.7:
Allow
Block