Cisco Cisco TV Streamer Application

Seite von 18
 
5
Release Notes for Cisco TV CDS 2.5.6
OL-27171-01
  Supported Environments
Supported Environments
Release 2.5.6 of the Cisco TV CDS supports both the ISA and RTSP environments. Some RTSP 
environment features are only applicable to certain RTSP Deployment Types.
System Requirements
The Cisco TV CDS Release 2.5.6 runs on the CDE110, CDE220, CDE250, and CDE420. See the Cisco 
Content Delivery Engine110 Hardware Installation Guide
, and the Cisco Content Delivery Engine 
205/220/250/420 Hardware Installation Guide
.
The Cisco TV CDS Release 2.5.6 also runs on the CDE100, CDE200, CDE300, and CDE400 hardware 
models that use the Lindenhurst chipset. See the Cisco Content Delivery Engine CDE100/200/300/400 
Hardware Installation Guide 
for set up and installation procedures. 
Release 2.5.6 does not support the CDEs with the ServerWorks chipset. All CDEs with the ServerWorks 
chipset need to be replaced with the CDEs with the Lindenhurst chipset or the Next Generation 
Appliances (CDE110, CDE220, CDE250, andCDE420) before upgrading to Release 2.5.6.
Note
If you are using Internet Explorer 8 to access the CDSM GUI, for the online help to display correctly, 
you need to turn on Compatibility View. To turn on Compatibility View in Internet Explorer 8, choose 
Tools > Compatibility View
Limitations and Restrictions
This release contains the following limitations and restrictions:
RTSP Redirect Server Limitations—The TV CDS Redirect Server provides a central entry-point 
for stream requests, which are then redirected based on internal load balancing policies to other 
Setup servers in the CDS deployment for session processing.  The load balancing policies require 
that the CDS server running the Redirect Server have access to the database of each potential Setup 
server.  The policies use key pieces of information from the database, such as the RTSP server status, 
the server load, and the Setup IP address to management IP address mappings.  If the Redirect Server 
does not have access to this data, it cannot properly redirect the setup request to the "best" Setup 
server.
In the case of multiple Stream Groups, with the Redirect Server configured to run on Streamers 
within one of the Stream Groups, it is required that the database replication partners for the 
Streamers contain all of the Streamers from all Stream Groups, which basically  constitutes a 
full-mesh database replication approach among all of the Streamers
If a full-mesh database replication for the Streamers is not desired, the Redirect Server can operate 
on the Vaults, which already have the necessary database replication partners defined to support 
required data.