Release Notes for Cisco ECDS 2.5
Revised: October 26, 2012
OL-24532-03
These release notes support all Cisco Enterprise Content Delivery System (Cisco ECDS) 2.5.x releases
and contain the most current system information.
Contents
•
New Features, page 2
•
Cisco ECDS Application Support and Recommended Software, page 9
•
Cisco ECDS Software Version Compatibility by Platform, page 11
•
Obtaining and Upgrading Software, page 12
•
Unsupported Software Features, page 12
•
Limitations and Restrictions, page 13
•
Cisco ECDS Configuration Tips, page 13
•
Cisco MDE Support, page 14
•
Caveats and Known Issues, page 17
•
Related Documentation, page 28
•
Obtaining Documentation and Submitting a Service Request, page 28
Americas Headquarters:
Cisco Systems, Inc., 170 West Tasman Drive, San Jose, CA 95134-1706 USA
New Features
New Features
The following sections contain new feature information:
•
Features in Software Versions, page 2
•
WCCP for Request Routing, page 4
•
HTTPS Secure Delivery Service, page 4
•
New and Changed CLI Commands, page 5
•
Configuration Changes Since Last Release, page 8
•
Service Engine CLI Setup Wizard in Cisco ECDS Release 2.5.5, page 8
Features in Software Versions
Table 1 lists Cisco ECDS software versions and feature support.
Table 1
Cisco ECDS Software New Feature Support
Software Version
2.5.5
New Feature
•
Cisco MDE 1125, Cisco MDE 3125—Next
generation UCS SL C220 M3 rack servers for
the Cisco ECDS system.
•
WCCP transparent caching with HTTPS
support. You have a choice to use the
Cisco ECDS with WCCP in Release 2.5.5
See WCCP for Request Routing.
•
Storage enhancement for the
Cisco MDE 1100 adds support for 2 or 4
drives/disks. See the “Cisco MDE 1100
Series” section on page 15.
•
MDE 10XVB — Introduces support for
generic, ESXi-based virtual machines.
•
MDE 50WVB — Extends WAAS VB support
to the WAE 294, WAE 594, and WAE 694
platforms.
•
Support for Apple HTTP Live Streaming. See
the Cisco ECDS 2.5 Software Configuration
Guide to enable Apple HLS.
2.5.3 (S5)
2.5.5
2.5.3 (S4)
2.5.3 (S3)
Introduces support for MDE 50IVB.
2.5.3 (S2)
Introduces support for MDE 3100.
2.5.3 (S1)
Introduces support for MDE 50WVB.
2.5.3
Supports the MDE 1100.
Release Notes for Cisco ECDS 2.5
2
OL-24532-03
New Features
Cisco MDE UCS Chassis Support
The Cisco MDE 1125 and Cisco MDE 3125 are the next generation UCS SL C220 M3 rack servers for
the Cisco ECDS system.
Cisco MDE 1125
Cisco UCS C220 (large form factor (LFF) drives, with 4-drive backplane) holds up to four 3.5-inch hard
drives.
Cisco MDE 3125
Cisco UCS C220 (small form-factor (SFF) drives, with 8-drive backplane) holds up to eight 2.5-inch
hard drives or solid state drives.
See the following sections:
•
Supported Software, page 3
•
Unsupported Software, page 3
•
Spare Support, page 4
Supported Software
The Cisco MDE 1125 and Cisco MDE 3125 are supported on Cisco ECDS Software Release 2.5.3 (S5)
and 2.5.5. Use the following part numbers when ordering:
•
MDE-1125-K9
•
MDE-3125-K9
•
MDE-1125-K9= (Spare, without the hard drives)
•
MDE-3125-K9= (Spare, without the hard drives)
The Cisco MDE 1125 and Cisco MDE 3125 use the following software images:
•
2.5.3 s5 b8xx
•
2.5.5 s1 b1xx
Unsupported Software
Prior versions of Cisco ECDS 2.5.3 and 2.5.5 are not supported on the new Cisco MDE platforms, for
example:
Note
•
2.5.3 images with b# where # is less than 800
•
2.5.5 images with b# where # is less than 100
The system does not block installation of unsupported images. For best results, do not install
unsupported software versions. If installation of prior image versions occurs, recover your system with
the mfg-cdrom iso or rescue-cdrom iso supported image version.
Release Notes for Cisco ECDS 2.5
OL-24532-03
3
New Features
Spare Support
The Cisco MDE 1125 and Cisco MDE 3125 spare is only available with Cisco ECDS Software Release
2.5.3. If your chassis shipped with Cisco ECDS Software Release 2.5.5, you must either re-image the
flash drive to release 2.5.3(S5) or run the upgrade to release 2.5.3(S5). Contact your Cisco representative
for support information.
WCCP for Request Routing
To address networking challenges for enterprises, traffic patterns content requests can be fulfilled locally
using WCCP with transparent caching. In previous Cisco ECDS software releases, DNS changes were
required and additional work was necessary to change existing URLs to fit into the Cisco ECDS service
routing-based caching solution. Cisco ECDS Release 2.5.5 introduces WCCP and transparent proxy for
all supported media protocols in Cisco ECDS.
WCCP can be used with Cisco content caching engines and third-party proxy servers, Web caching, and
content filtering appliances. Cisco ECDS 2.5.5 works with WCCP Version 2 to support unmanaged video
caching and Application and Content Networking System (ACNS) migration.
The following is supported:
•
WCCP Services—HTTP, HTTPS, RTSP, RTMP, WMT, Custom Web-Cache, and Dynamic services
•
WCCP Redirect—GRE and L2
•
WCCP Assignment—Hash and Mask
•
WCCP Bypass—Static, load, and port exception server
•
FMS
– Flash Media Server support
– Application name changes: vod-ecds and live-ecds
•
WMT—WMT proxy bypass
To enable WCCP in the Cisco Enterprise CDSM, choose Devices > Request Routing > WCCP.
See the following documents for complete information:
•
Cisco ECDS 2.5 Software Configuration Guide
•
Cisco ECDS 2.5 Command Reference
HTTPS Secure Delivery Service
When WCCP is enabled, HTTPS becomes an option in the delivery service content source URL
configuration. The Content Acquirer fetches content using HTTPS and distributes ECDS content
securely.
The following is supported:
•
Web Engine
– HTTPS certificate management
– HTTP proxy bypass
– IP spoofing
– Max-min cacheable objects
Release Notes for Cisco ECDS 2.5
4
OL-24532-03
New Features
– Cache-query string
– Cache-nonreachable
– Cache-fill-range
To access HTTP Connections in the Cisco Enterprise CDSM, choose Devices > Application Control >
Web > HTTP > HTTP Connections.
HTTPS can only be enabled when WCCP service is enabled. Follow these steps to ensure proper
configuration:
1.
First, make sure WCCP is not enabled by entering the show wccp status command.
2.
Create all the certificates, keys, and certificate groups on the same service engine in the
Cisco CDSM.
3.
Enable the HTTPS server and check HTTPS server status on SE CLI by entering the show https
server command.
4.
Now enable WCCP service for the SE from the Cisco CDSM.
See the following documents for complete information:
•
Cisco ECDS 2.5 Software Configuration Guide
•
Cisco ECDS 2.5 Command Reference
New and Changed CLI Commands
Table 2 lists command support added in Cisco ECDS Release 2.5.5.
Table 2
Cisco ECDS 2.5.5 WCCP and Supported New and Changed Commands
Command
Description
New Commands
alarm
nic-shutdown-alarm
Generates an alarm when the NIC interface is shut down.
bypass
Configures the bypass functions.
https (EXEC)
Manages certificates, certificate groups, and private keys when using the
Service Engine as an HTTPS server:
https cert—Creates certificate objects with a given name, imports a
certificate from external sources into a certificate object, or removes
existing certificate objects.
https certgroup—Creates or removes certificate groups or imports a
certificate from an external source to add it to an existing certificate chain.
https server
Configures the Service Engine to act as an origin HTTPS server.
show bypass list
Determines whether the origin HTTPS server has been added to the
WCCP accept list.
show https
Displays HTTPS proxy status and port policies.
show statistics wccp
Displays the WCCP statistics for the Service Engine.
show wccp
Displays Web Cache Communication Protocol (WCCP) information.
Release Notes for Cisco ECDS 2.5
OL-24532-03
5
New Features
Table 2
Cisco ECDS 2.5.5 WCCP and Supported New and Changed Commands
Command
Description
wccp custom-web-cache
Enables the Service Engine to accept redirected HTTP traffic on a port
other than 80.
wccp flow-redirect
Enables Web Cache Communication Protocol (WCCP) flow redirection
wccp https-cache
Enables Web Cache Communication Protocol (WCCP) flow redirection to
a Service Engine configured as an HTTPS server
wccp port-list
Associates ports with specific Web Cache Communication Protocol
(WCCP) Version 2 dynamic services.
wccp router-list
Configures a router list for Web Cache Communication Protocol (WCCP)
Version 2.
wccp rtmp
Configures Web Cache Communication Protocol (WCCP) Version 2
Real-Time Messaging Protocol (RTMP) media stream transparent
interception.
wccp rtsp
Configures Web Cache Communication Protocol (WCCP) Version 2
Real-Time Streaming Protocol (RTSP) protocol transparent interception.
wccp service-number
Enables up to eight dynamic Web Cache Communication Protocol
(WCCP) redirection services on the Service Engine
wccp shutdown
Sets the maximum time interval after which the Service Engine will
perform a clean shutdown of Web Cache Communication Protocol
(WCCP)
wccp slow-start
Enables the slow-start capability of the caching service on the Service
Engine with Web Cache Communication Protocol (WCCP).
wccp version
Specifies the version of Web Cache Communication Protocol (WCCP)
that the Service Engine should use. The ECDS uses only Version 2.
wccp web-cache
Configures the router to run the web cache service with Web Cache
Communication Protocol (WCCP) Version 2.
wccp wmt
Configures the router to run the web cache service with Web Cache
Communication Protocol (WCCP) and Windows Media Technologies
(WMT).
wccp wmt-rtspu
Configures Web Cache Communication Protocol (WCCP) Version 2
WMT Real-Time Streaming Protocol (RTSP) transparent interception.
wmt proxy outgoing
Configures outgoing bypass proxy lists:
wmt proxy outgoing http bypass—HTTP Proxy Bypass list
wmt proxy outgoing rtsp bypass—RTSP Proxy Bypass list
Changed Commands
Release Notes for Cisco ECDS 2.5
6
OL-24532-03
New Features
Table 2
Cisco ECDS 2.5.5 WCCP and Supported New and Changed Commands
Command
Description
service-router
service-monitor
The service-router service-monitor command is changed to
service-monitor in Cisco ECDS Release 2.5.5
flash-media-streaming
The flash-media-streaming command has changed for configuring the
virtual-path for VOD applications. The new parameter is vod-ecds, as
shown in the following example that maps a VOD folder to media:
SE(config)# flash-media-streaming application-virtual-path
vod-ecds map media
The live keyword is changed to live-ecds in Cisco ECDS Release 2.5.5.
This parameter manages the aggregated live stream in Live applications to
Flash Media Streaming.
Release Notes for Cisco ECDS 2.5
OL-24532-03
7
New Features
Configuration Changes Since Last Release
Table 3 describes hardware and software administration information that has changed since last release.
Table 3
Administration Changes
Topic
Description
Change
Cisco MDE spares
replacement
A spare unit is intended to recover content on
Cisco ECDS hard disks when the Cisco MDE
unit itself is damaged but the hard disks are
ok.
A new section has been added to the
Cisco Media Delivery Engine 1100 Series and
Cisco Media Delivery Engine 3100 Series
hardware installation guides that describes how
to configure a replacement unit.
See the following documentation on
Cisco.com:
NIC shutdown alarm
management
By default, the minor alarm, Network
Interface Controller (NIC) shutdown, is not
displayed in either the show alarms command
output or in CDSM reporting.
•
Cisco Media Delivery Engine 1100 Series
Hardware Installation Guide
•
Cisco Media Delivery Engine 3100 Series
Hardware Installation Guide
You can enable NIC alarm reporting through
either the CLI on the SE or by using the CDSM
administration GUI.
Use the alarm nic-shutdown enable
command.
Tip
After configuring the setting, you may
need to wait a few minutes before the
alarm is no longer shown in show
alarms output.
The CDSM administration GUI navigation has
been changed:
Devices > General Settings > Notification
and Tracking > Alarm Settings.
The “Alarm Overload Detection” check box is
available on the Alarm Settings for Service
Engine page.
Service Engine CLI Setup Wizard in Cisco ECDS Release 2.5.5
Typically when a device is first brought up, you would first run the Setup Wizard on the Service Engine
CLI to configure basic settings. One of these settings is the device mode change where you can change
the device mode to service-router or CDSM for example.
In Cisco ECDS Release 2.5.5, the device mode change in the Setup Wizard does not work. Instead, you
must manually configure the device mode before running the Setup Wizard.
To manually configure the device mode on the SE upon first startup:
1.
Enter the following command:
se(config)# device mode [device-mode]
Release Notes for Cisco ECDS 2.5
8
OL-24532-03
Cisco ECDS Application Support and Recommended Software
2.
Follow the directions in the prompts.
3.
Restart the device when instructed.
After restarting the device, the device mode should be correctly configured and you can run the
Setup Wizard as normal.
Tip
Any device-mode configurations should always be done manually.
Cisco ECDS Application Support and Recommended Software
Table 4 describes the Cisco ECDS application supported on each Cisco ECDS platform and the
recommended software version.
For best results, the following is recommended:
•
Use the most current version of the software. See Table 4 for recommendations per platform.
•
You should use the same software release across your deployment.
•
Generally, downgrade to a lower version is not required or necessary and can render your system
unusable.
Note
•
Downgrade from Cisco ECDS Release 2.5.5 to an earlier release is not supported.
Cisco ECDS 2.5.5 is the current recommended version:
– Supports WCCP/HTTPS
– Applies to all Cisco ECDS platforms and can be used for device group upgrade with mixed
platforms.
– Supports the Cisco ECDS 2.5.5 rescue image if a device goes to a bad state and rescue is
required.
Release Notes for Cisco ECDS 2.5
OL-24532-03
9
Cisco ECDS Application Support and Recommended Software
Table 4
Cisco ECDS Application Support by Platform
Platform
Enterprise Content
Service
Delivery System Manager Router
Streaming
Engine
Content
Acquirer
Supported Software
MDE 3100
Y
Y
Y
2.5.5
Y
MDE 3125 UCS SL C220
M3 rack server
2.5.3 S4
2.5.3 S5
(MDE 3125)
2.5.3 S3
2.5.3 S2
Y
MDE 1100
Y
Y
Y
2.5.5
2.5.3 S4
MDE 1125 UCS SL C220
M3 rack server
2.5.3 S5
(MDE 1125)
2.5.3 S3
2.5.3 S2
MDE 10XVB
N
N
Y
N
2.5.5
2.5.3 S4
MDE 50IVB
N
N
Y
N
2.5.5
2.5.3 S4
2.5.3 S3
MDE 50WVB
N
N
Y
N
2.5.5
2.5.3 S4
2.5.3 S3
2.5.3 S2
Release Notes for Cisco ECDS 2.5
10
OL-24532-03
Cisco ECDS Software Version Compatibility by Platform
Cisco ECDS Software Version Compatibility by Platform
Table 5 describes the Cisco ECDS software version supported on each Cisco ECDS platform and shows
which software version ships on the platform by default.
Table 5
Software
Release
2.5.5
Cisco ECDS Software Compatibility by Platform
Media Delivery Engine
10XVB
Y
(shipping)
MDE 1100
Y
MDE 3100
Y
50IVB
Y
50WVB
Y
(shipping)
Base Platform Software
•
vECDS PCs running ESXi4.1 or ESXi5.0
•
ISR29xx and ISR39xx:
15.1(4)M1 SRE-V Up to 2.0.0.10
•
UCS C200 and C210:
Up to 1.4(2) C200.1.4.1.0
•
WAVE294/WAVE594/WAVE694:
4.4.1.12
•
WAVE574/WAE674:
4.4.3.4
•
vECDS PCs running ESXi4.1 or ESXi5.0
•
ISR29xx and ISR39xx:
15.1(4)M1 SRE-V Up to 2.0.0.10
•
UCS C200 and C210:
Up to 1.4(2) C200.1.4.1.0
•
WAVE294/WAVE594/WAVE694:
4.4.1.12
•
WAVE574/WAE674:
4.4.3.4
•
ISR29xx and ISR39xx: 15.1(4)M1 SRE-V
1.5.1.0
•
UCS C200 and C210:
Up to 1.4(1a) C200.1.4.1.0
•
WAVE574 and WAE674:
4.2.3.7
•
UCS C200 and C210:
Up to 1.3(2d) C200.1.3.2.0
•
WAVE574 and WAE674:
4.2.3.7
(shipping)
2.5.3 S4
Y (shipping)
Y
Y
Y
Y (shipping)
(shipping)
2.5.3 S3
N
Y
Y
Y
Y
(shipping)
2.5.3 S2
N
Y
Y (shipping)
N
Y
2.5.3 S1
N
N
N
N
Y (shipping)
•
WAVE574 and WAE674:
4.2.3.7
2.5.3
N
Y (shipping)
N
N
N
•
UCS C200:
Up to 1.2(2d) C200.1.2.2f.0
Release Notes for Cisco ECDS 2.5
OL-24532-03
11
Obtaining and Upgrading Software
Obtaining and Upgrading Software
To upgrade your Cisco ECDS platform to the latest software supported on the platform, contact the
Cisco Technical Assistance Center (TAC). See the “Obtaining Documentation and Submitting a Service
Request” section on page 28.
Refer to the Cisco ECDS 2.5 Software Configuration Guide on Cisco.com for upgrade instructions.
Unsupported Software Features
The following features may appear in the Cisco Enterprise CDSM or CLI interfaces or be supported in
WCCP in general but are not supported in this release of Cisco ECDS software:
•
Unsupported in Cisco ECDS, page 12
•
Unsupported in Cisco ECDS with WCCP, page 12
Unsupported in Cisco ECDS
•
DVRCAST
•
ICAP
•
IP-based Redirection
•
IP multicast routing
•
Geo-Location Server integration
•
Proximity Server
•
PCMM
•
RTMPT
•
RTMPTE
•
Session Shifting
•
Show and Share over SSL
•
URL Signing
•
Wholesale licensing
•
Windows Media Services Multi Bit Rate
Unsupported in Cisco ECDS with WCCP
•
Access Control Lists with WCCP
•
Bypass Error handling
•
Encrypted private keys for configuring the HTTPS server
•
HTTPS without WCCP
•
IP ACL
•
IP multicast routing
Release Notes for Cisco ECDS 2.5
12
OL-24532-03
Limitations and Restrictions
•
IP Spoofing with non-HTTP protocols or multiple Service Engines
•
L4 Switch for the bypass gateway.
•
Reverse proxy
•
RTMP unmanaged domain
•
Security proxy
•
Show and Share over SSL
•
WCCP CIF/FTP/DNS traffic caching
•
WCCP Web cache packet return
Limitations and Restrictions
Observe the following limitations and restrictions in this release:
•
Cisco ECDS-SRE9x0_RAID0.ova Deployment with vSphere, page 13
•
HTTP Request Header Size, page 13
•
NAT Devices, page 13
Cisco ECDS-SRE9x0_RAID0.ova Deployment with vSphere
Make sure that the system from which you deploy the RAID 0.ova file is running natively on hardware,
or is controlled through a remote desktop. There is an issue with deployment if there are nested vSphere
instances in which vSphere is running on the VM controlled through vSphere. In this case the Cisco SRE
VM is deployed using vSphere from a Windows 2008 server VM. The Windows 2008 server VM is
controlled from the console window of another vSphere client, therefore creating a nesting environment
and the deployment fails.
HTTP Request Header Size
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.
NAT Devices
There is no network address translation (NAT) device separating the MDEs from one another.
Cisco ECDS does not support NAT configuration, where one or more MDEs are behind the NAT device
or firewall. If your Cisco ECDS network is behind a firewall, workaround this issue by configuring each
internal and external IP address pair with the same IP address.
Cisco ECDS 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 Cisco ECDS network and the client
device. However, the NAT device or firewall must support RTP/RTSP.
Cisco ECDS Configuration Tips
Use the following configuration tips to help you manage your system. For more information, see the
Cisco ECDS 2.5 Software Configuration Guide on Cisco.com.
•
Encoders with Variable Bit Rates, page 14
•
Hybrid Ingest, page 14
Release Notes for Cisco ECDS 2.5
OL-24532-03
13
Cisco MDE Support
•
NTP Configuration, page 14
•
WCCP and Streaming Interfaces, page 14
Encoders with Variable Bit Rates
We recommend that customers with variable bit rates cap the bit rate at the encoder to avoid bit rate
spikes, which may result in throughput exceeding the supported throughput allowed in the Cisco ECDS.
Use the show bitrate [movie-streamer | wmt] command in Privileged EXEC mode to display the bit
rate allocated to a particular device. Use the bitrate command in Global configuration mode to configure
the maximum pacing bit rate for large files for the Movie Streamer and to separately configure WMT
bit-rate settings.
Hybrid Ingest
In the current release, the origin server OFQDN is always used, and the hostname/port in the Manifest
file is ignored.
NTP Configuration
When configuring network settings on your Service Engine, make sure that you configure NTP in
General Settings > Network > NTP and enter the ntp server <ntp-server-IP> command. This enables
the Service Engine to work properly with Flash Media Streamer and successfully sync with CDSM.
WCCP and Streaming Interfaces
WCCP always binds to the first interface. The streaming interface can still be configured for service
routing.
Cisco MDE Support
•
Cisco MDE 3100 Series, page 14
•
Cisco MDE 1100 Series, page 15
•
Cisco MDE 50IVB, page 16
•
Cisco MDE 50WVB, page 17
•
Cisco MDE 10XVB, page 17
Cisco MDE 3100 Series
Observe the following recommendations for the Cisco MDE 3100 Series:
•
CIMC RAID Support, page 14
•
KVM Console Support, page 15
•
Spares Support, page 15
CIMC RAID Support
CIMC RAID management is not supported. The appliance drives do not appear on the CIMC
Inventory > Storage screen.
Release Notes for Cisco ECDS 2.5
14
OL-24532-03
Cisco MDE Support
KVM Console Support
By default, console output is available on the KVM console connector on the front of the appliance and
the serial connector on the rear of the appliance. Enabling Serial-over-LAN in CIMC disables the
console output on the serial connector on the rear of the appliance. You can still obtain console output
from a CIMC console session or from the KVM console connector on the front of the chassis.
Spares Support
A spare unit is intended to recover content on Cisco ECDS hard disks when the Cisco MDE unit itself
is damaged but the hard disks are ok. For complete information about managing spares, see the
Cisco Media Delivery Engine 3100 Series Hardware Installation Guide.
Cisco MDE 1100 Series
Observe the following recommendations for the Cisco MDE 1100 Series:
•
Cisco MDE Disk Drive Support, page 15
•
Disconnect USB Devices, page 15
•
Maximum Content Delivery, page 15
•
NIC Settings, page 16
Cisco MDE Disk Drive Support
The Cisco MDE 1100 has four disk slots that allow you to use either two or four 2 465.8GB SATA disks.
Table 1-6
Cisco MDE 1100 Hard Drives
Supported Drive
Part Number
Number of
Disks
ECDS Software Release
Storage
Space
500GB SATA 7.2K RPM 3.5” HDD
MDE-HDDSTA-500GB=
2
All up to 2.5.3(S4)
840.5 GB
4
2.5.5 and later releases
1772,0 GB
Disconnect USB Devices
Disconnect any external USB devices (such as drives and keyboards) before powering on the appliance.
Your appliance may not boot with devices connected to the external USB ports.
Maximum Content Delivery
To maximize the content delivery performance of an MDE 1100 appliance, do the following:
•
Use port channel for the primary and streaming interface.
Configure the gigabit Ethernet interfaces into a single port-channel interface. Use this interface for
all client-facing and administrative traffic. Refer to the Cisco ECDS 2.5 Software Configuration
Guide for detailed instructions.
•
Use the client IP address as the load balancing algorithm.
Assuming port-channel is used between the upstream router/switch and the SE for streaming
real-time data, the port-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.
Release Notes for Cisco ECDS 2.5
OL-24532-03
15
Cisco MDE Support
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.
For high-volume traffic, separate HTTP and WMT.
If you have enough client WMT traffic to saturate the MDE capacity, we recommend that you
provision a dedicated MDE to handle WMT; and likewise for HTTP. In such cases, we do not
recommended that you mix the two traffic types on all MDE servers which could result in
suboptimal aggregate performance and require more MDE servers than usual.
•
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
Cisco Enterprise CDSM.
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.
For typical deployments, it is preferable to leave these parameters set to their defaults.
•
For ASX requests, when the Service Router redirects the request to an alternate domain or to the
origin server, the Service Router does not strip the .asx extension, this is because the .asx extension
is part of the original request. If an alternate domain or origin server does not have the requested
file, the request fails. To ensure requests for .asx files do not fail, make sure the .asx files are stored
on the alternate domain and origin server.
NIC Settings
Do not change the Network Interface Controller (NIC) mode or NIC redundancy settings when
configuring Cisco Integrated Management Controller (CIMC) network settings. The supported settings
are:
•
NIC Mode: Dedicated
•
NIC Redundancy: None
Spares Support
Information about managing spares. See Configuration Changes Since Last Release.
Cisco MDE 50IVB
Portchannelling is not supported on the Cisco MDE 50IVB.
Release Notes for Cisco ECDS 2.5
16
OL-24532-03
Caveats and Known Issues
Cisco MDE 50WVB
Portchannelling is not supported on the Cisco MDE 50WVB.
Cisco MDE 10XVB
Disk Space on the Virtual Machine
For best results, delete unused files and reduce unnecessary storage to conserve memory allocation on
the Cisco ECDS running on the VM. If you have difficulty powering on the device or the system warns
of no space left on the device, reduce the memory allocation then boot the device and delete files from
the server.
Caveats and Known Issues
•
Known Issues, page 17
•
Caveats in Cisco ECDS 2.5.5, page 18
•
Caveats in Cisco ECDS 2.5.3 S4, page 20
•
Caveats in Cisco ECDS 2.5.3 S3, page 20
•
Caveats in Cisco ECDS 2.5.3 S2, page 20
•
Caveats in Cisco ECDS 2.5.3, page 21
•
Apple HTTP Live Streaming, page 17
•
FMS Allocated Cache Size, page 17
Known Issues
Apple HTTP Live Streaming
Apple HLS may experience poor video quality when sending 50 Client requests using IxLoad client
simulator on the Mac Mini. To work around this potential problem, use the Cisco Media Processor
(formerly Spinnaker Inlet Encoder) to send Client requests. See the Cisco AS5100 Series Media
Processor support page for more information. For information about configuring Apple HLS in
Cisco ECDS, see the Cisco ECDS 2.5 Software Configuration Guide on Cisco.com.
FMS Allocated Cache Size
If the flash-media-streaming cache is near maximum, the system may be unable to cache completely.
The show flash-media-streaming cache content command output may be missing content and the
system will issue an error message. The problem occurs when a single file is greater than the size of the
flash-media-streaming allocated cache.
Release Notes for Cisco ECDS 2.5
OL-24532-03
17
Caveats and Known Issues
Caveats in Cisco ECDS 2.5.5
Unresolved Caveats
Table 7 describes issues that are not resolved in the Cisco ECDS 2.5.5 release. They may be present in
previous versions of the software.
Table 7
Caveats Resolved in Cisco ECDS 2.5.3 S4 and S5
Identifier
Description
CSCtz75862
MDE (all platforms) Network Interface Controller (NIC) down minor alarm for interface not in use. See
Configuration Changes Since Last Release for new command information to resolve this issue.
CSCty45216
TACACS key displays in clear text in startup-config.
Symptom If the TACACS key is configured with an older image, upon bootup TACACS key may be shown in
clear text before the first copy running start command is issued.
Workaround None. This issue does not occur after the first copy running start command is issued.
CSCty57898
SE retains DG users in running config even after removing the SE from DG.
Symptom The SE retains the username that was configured in the device group after removing the SE from the
device group.
Workaround None.
CSCty46610
Web-engine does not store mime-type of content cached.
Symptom Some web-content does not open in the browser. Some advertisements in certain websites show as
malformed characters. When the object in the origin server does not have an extension that is understood by
modern day browser. ECDS does not store mime-type set in the origin server. If the object at the origin server
does not have a valid extension that is understood by the browsers, this problem will appear.
Workaround None.
CSCty70055
Able to see the bypass list configuration in the CLI when DG configuration is not pushed in the SE.
Workaround None.
CSCtz71310
WCCP process gone when shutting down WCCP; multiple core dumps seen.
Symptom WCCP process crashes and cannot be restarted. When one of the WCCP service is configured to
have 32 service engines, and any one of those service engines also has WCCP service configured, the WCCP
process crashes.
Workaround Use less than 32 service engines in your WCCP service group.
Release Notes for Cisco ECDS 2.5
18
OL-24532-03
Caveats and Known Issues
Table 7
Caveats Resolved in Cisco ECDS 2.5.3 S4 and S5 (continued)
Identifier
Description
CSCua10670
SRE900: Frequent CPU spikes when files are distributed/playing cache-miss.
Symptom CPU spikes occur while doing acquisition and distribution on the SRE900 acquirer when file sizes
are huge (10GB to 24GB range).
Workaround Avoid replicating files that are huge (>5GB) when your acquirer is SRE900.
CSCua15312
Darwin Streaming Server utilizing 95% of the ECDS-VB CPU.
Symptom Darwin Streaming Server will start utilizing a high amount of CPU (95%) when streaming
dynamically cached files.
Conditions This issue is observed on virtual appliances (Cisco MDE 50s and Cisco MDE 10XVB) due to the
lower amount of system resources. The high CPU utilization is usually seen as the number of unique streams
for dynamically cached content gets high (around 100+). Requests for prepositioned content has little effect
on the CPU spikes. The type of .mov files being prepositioned will also affect the CPU utilization. Unhinted
or incorrectly hinted .mov files will cause a high CPU utilization. Correctly hinted .mov files will result in an
initial high CPU utilization which drops and evens out over time.
This issue has to do with how unhinted files are handled in the dynamic caching scenario. There are some
inefficiencies with how unhinted files are hinted and then indexed that leads to high CPU utilization.
Subsequent calls to the same file do not seem to be handled ideally, and that results in some wasted CPU
cycles. Prepositioned .mov files, whether hinted or unhinted, do not seem to cause this behavior.
Workaround Correctly hinted .mov files will not result in prolonged high CPU utilization. Although this is not
always possible for dynamically cached content, it is the best way to decrease CPU load on the current
Cisco ECDS movie-streamer.
CSCua19871
SDP file could not be parsed by ECDS without manual insertion of CRLF.
Symptom SDP file created in Windows environment (for example, Notepad) will not insert CRLF character at
the end.
Workaround Manually insert CLRF using VI editor.
CSCua37783
CDSM HTTPS server status shows incorrect for device groups.
Symptom After configuring an HTTPS server with either an invalid certificate or key (or any other error
conditions that might cause the configuration to fail) for a device group, the “Enabled” field does not correctly
reflect the “disabled” state. Instead, it erroneously displays the HTTPS server to be in the enabled state even
though one or more SEs are reporting the server to be an invalid configuration.
Conditions This issue only occurs for device group configurations. When the same setting is configured for
individual SEs, the CDSM display for the SE shows the HTTPS server in the disabled state upon the next
keep-alive update from the SE.
Workaround There are no workarounds for the display issue. Users will need to go to the individual SEs and
use the CLI to check on the status of the HTTPS service configuration.
Release Notes for Cisco ECDS 2.5
OL-24532-03
19
Caveats and Known Issues
Caveats in Cisco ECDS 2.5.3 S4
Resolved Caveats
Table 8 describes the issues that were resolved in the Cisco ECDS 2.5.3 S4 release. They may be present
in previous versions of the software.
Table 8
Caveats Resolved in Cisco ECDS 2.5.3 S4 and S5
Identifier
Description
CSCtq65923
IE8-64bit: CIMC: Failed to switch to VM tab on KVM console
CSCts72387
Content source Quick Crawl does not work for file sizes more then 2 Gb
Caveats in Cisco ECDS 2.5.3 S3
Resolved Caveats
Table 9 describes the issues that were resolved in the Cisco ECDS 2.5.3 S3 release. They may be present
in previous versions of the software.
Table 9
Caveats Resolved in Cisco ECDS 2.5.3 S3
Identifier
Description
CSCto92809
Rare case: After CDSM failover and fallback, change manifest has no effect
Caveats in Cisco ECDS 2.5.3 S2
Resolved Caveats
Table 10 describes the issues that were resolved in the Cisco ECDS 2.5.3 S2 release. They may be
present in previous versions of the software.
Table 10
Caveats Resolved in Cisco ECDS 2.5.3 S2
Identifier
Description
CSCtk06964
clear cache flash-media-streaming fails to remove cache contents
CSCtk33261
WMT:RTSP Large ASF Header request fails
CSCtk55503
WMT:HTTP Large ASF header request fails
CSCtl06555
Transaction-logs get re-exported after SE upgrade
CSCtl94214
Scheduled bandwidth Acq-In, Dist-In/Out no effect due to timezone change
CSCtn65587
Getting a lot of close waits on port 1755 when being port scanned
CSCtn84583
HTTP files are corrupted when files are downloaded partially
Release Notes for Cisco ECDS 2.5
20
OL-24532-03
Caveats and Known Issues
Table 10
Caveats Resolved in Cisco ECDS 2.5.3 S2 (continued)
Identifier
Description
CSCtq00766
HTTP streaming and RTSP changes for large ASF header
CSCtq62499
Short TTL causes prepositioning to eventually fail
Caveats in Cisco ECDS 2.5.3
Open Caveats
Table 1 describes possible unexpected behavior by Cisco ECDS 2.5.3 components.
Table 11
Open Caveats in Cisco ECDS 2.5.x
Identifier
Description
CSCtt14910
Incorrect software file URL causes upgrade to stall
Symptom When you upgrade an image from an incorrect URL, Cisco ECDS devices may stall in the
Download Software Failed state, preventing you from continuing the upgrade.
Workaround Reboot Cisco ECDS devices. Correct the link and upgrade again.
CSCtj70660
show hardware command reports wrong number of CPUs
Symptom On the MDE 1100, the show hardware command reports 4 CPUs instead of one quad-core CPU.
On the MDE 3100, the show hardware command reports 16 CPUs instead of two quad-core CPUs.
Workaround None; does not affect functionality.
CSCtj90641
Flash live does not last overnight
Symptom This issue is seen when client issues a live stream to SE and after about 8 hours, the client stream
stopped and connection gets closed.
Conditions This issue occurs when playing live stream continuously more than 8 hours from a single client.
Workaround None. Click the Play or Start button on Flash player can resume playing flash live.
CSCtk11487
FailDiskCnt CLI is not working as expected
Symptom The threshold for failed disks is reached earlier then expected. The “service-router
service-monitor threshold failcntdisk <N>” command is expected to make the SE fail over if N disks fail.
It does a fail over if there are N disk-related alarms. This is caused by having a failed disk that generates more
then one alarm.
Workaround None. A failed disk might generate could produce one or multiple alarms depending on the exact
nature of the problem.
Release Notes for Cisco ECDS 2.5
OL-24532-03
21
Caveats and Known Issues
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCtk16678
show content all command error messages
Symptom During the eviction or stress to disk in streamer device, executing the “show content all” may result
in displaying some error messages. The messages are harmless.
Conditions This occurs in rare situations where eviction is happening and the show content all command is
executed. The command scans through the disk and the process accesses content that is also getting evicted,
displaying the error messages on the console.
Workaround None
CSCtk16762
Failed to play VOD .mov file after prepositioned to SE with FTP
Preposition .mov file with FTP (usr/pwd are required when access FTP server). Then play the .mov file use
RTSP. Failed to play the file with error “rtsp/1.0 504 gateway timeout”. Play with HTTP is ok.
Workaround Preposition .mov file with HTTP or HTTPS. Or play the content with HTTP.
CSCtk58709
CDSM displays gateway IP of last static route entry which is incorrect
Symptom The cause for this issue is that in CDSM gateway IP address is displayed incorrectly when choosing
Devices > Devices > Device Home. The Gateway IP address displayed in CDSM is for the last static IP route
entry on the device if entry was made using CLI command.
Workaround Use the CLI command to remove the static route entry from the device, reload the device, and
re-enter the static route via CDSM using Devices > Devices > General Settings > Network > Static IP
Routes.
CSCtk63442
Unable to no port-channel load-balance setting from CLI
Symptom The cause for this bug is that CLI command “no port-channel load-balance round-robin” fails to
remove the CLI command from the device. This happens when port-channel is configured as round-robin
mode using CLI command “port-channel load-balance round-robin”. The removal of this config fails when
an attempt is made to remove the config using CLI command “no port-channel load-balance round-robin”.
Workaround Use CDSM Devices > Devices > General Settings > Network > Port Channel Settings to
change load balance methods.
Release Notes for Cisco ECDS 2.5
22
OL-24532-03
Caveats and Known Issues
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCtk63659
Failed to play new added Windows media in Windows media
Symptom User may add media to existing play list for Windows rebroadcast, but player stops playing the
content when reaching the newly-added media.
Workaround Follow these steps:
1.
Close Windows Media Player.
2.
Save the Windows rebroadcast program with added media.
3.
Open Windows Media Player and play the program again.
Release Notes for Cisco ECDS 2.5
OL-24532-03
23
Caveats and Known Issues
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCtl45623
Error domain routing not correct for RTMP
Symptom When an RTMP stream request is redirected to the error domain, the redirection URL is only
partially provided to the client, leading to a failed redirection. There are two possible reasons for this:
1.
An RTMP URL can be interpreted as being composed of two parts: the connection URL and the stream
name. The stream name (file being requested) is the last string following the last slash while the
connection URL is everything before the last slash (host, domain, application name, application instance,
and so on).
For example, in the URL rtmp://my_domain.com/vod-ecds/flv/stream1 the
connection_url=rtmp://my_domain.com/vod-ecds/flv/ and stream_name=stream1. Most flash clients
will interpret a redirection URL to only be the connection URL (RTMP URL without the stream name).
It is usually assumed that the stream name will stay the same when being redirected to a new host.
Therefore, even if a stream name is included in the path specified for the “Error File Name,” it is the
stream name from the original request which will be used at this new domain:
Original client request: rtmp://my_domain.com/vod-ecds/stream1
Error domain+file configured for SR: rtmp://error_domain.com/vod-ecds/errorfile
Client request after redirection: rtmp://error_domain.com/vod-ecds/stream1
2.
For the RTMP case, the “Error File Name” is truncated to the first "/". Therefore if the
Error_Domain="error_domain.com and Error_File_Name="vod-ecds/flv/errorfile." During the last
resort case the client will be given the new connection URL "rtmp://error_domain.com/vod-ecds". The
"flv/errorfile" is cut off.
Conditions This occurs when General Settings > Last resort is configured on the SR with an error domain
and error file name. No SE is available to fulfill request and client is redirected to the last resort URL.
Workaround The name of the error stream located at the error domain must match the name of the original
failed stream name. For example, if the failed request is rtmp://my_domain.com/vod-ecds/stream1, stream1
must be available at the error domain so that the client would be redirected to
rtmp://error_domain.com/vod-ecds/stream1 and the Last Resort Configuration would look as follows:
Domain Name: my_domain.com
Error Domain Name: error_domain.com
Error File Name: vod-ecds
Make sure the error files are located only one directory deep after the error domain as any portion of the path
after the first “/” will be truncated. For example, if sample.flv was the error file, it can be located at
rtmp://error_domain.com/dir1/sample.flv but not rtmp://error_domain.com/dir1/dir2/sample.flv.
See Configuration Changes Since Last Release for information about VOD file naming with Flash Media
Streaming. See Table 3 for changes to the flash-media-streaming command.
Release Notes for Cisco ECDS 2.5
24
OL-24532-03
Caveats and Known Issues
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCtl75524
show flash-media-streaming stream-status dvrcast failed to show
Symptom Play FMS live DVR on SE is fine, but show flash-media-streaming stream-status dvrcast does
not display any dvrcast information.
Workaround None
CSCtl78236
Authsvr <deny> <pattern> not working
Symptom Import an authsvr XML configuration file with the keyword “live” defined in <Deny> <Pattern> to
block FMS live video. But FMS live video still can be played even with live key word in <Deny> <Pattern>
Condition: authsvr enabled with authsvr configuration file imported
Workaround None
CSCtl98397
CIMC shutdown does not shutdown MDE 1100
Symptom When user clicks the “Shut Down Server” link from CIMC, it does not trigger any action to MDE.
Conditions This link is generally used in CIMC to gracefully shut down the operating system on server. It has
not been implemented in this release.
Workaround Use one of these other links from CIMC instead if the yare available and suit your needs: “Power
Down”, “Power Cycle” or “Hard Reset”
CSCtn03282
CDSM—Need to click submit twice for IP ACL condition to show up on SE
Symptom This is caused by the IP ACL condition not being applied to the device when the CDSM submit
button is clicked for the first time.
Workaround When using CDSM to configure IP ACL condition click the submit button twice for the config
to be applied to the device.
CSCtn40238
Sometimes can't play FMS due to arthsvr error
Symptom Sometimes FMS VOD request failed due to authsvr error.
Workaround Enable “unknown domains” can solve this issue. To enable unknown domains, click Devices >
Service Control > Authorization Service > Enable Unknown-Server Requests.
CSCtn50826
Failed wmt caching of MBR content during stream switch
Symptom Random playback of MBR content (at different bit rates) results in issues on caching behavior
Workaround None
Release Notes for Cisco ECDS 2.5
OL-24532-03
25
Caveats and Known Issues
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCtn50835
WMT: Video freeze for live MBR request
Symptom When the live program source is MBR, some players will meet errors in buffer state or after playing
for a short time. This is caused when the live program source is MBR with many different bit rate requests
for the live program.
Workaround Configure different live program for same content in different bit rate.
CSCtn50841
The ucache-svr coredumped with clear cache all command
Symptom ucache process coredumps with size of 4GB, no service failure will happen during this period
except a core file in SE. The coredump happens when ucache process memory usage reaches close to 4GB.
Conditions This can happen for multiple reasons:
1.
SE having large amount of contents with larger URLs.
2.
There are many contents files, and clear cache all executed during this period.
Workaround None.
CSCtn50891
Symptom Live video continues to play after program is stopped.
Conditions If a program is stopped, all the clients that already had connections established will continue to
receive the stream This only applies in setups where live streaming is being used.
Workaround After the program is stopped, the stream must also be stopped at the origin server.
CSCtn65708
sh stat http requests not incr. any counter - partial content displays
Symptom When partial content is available in the SE, if a request is sent for the same file, it should increment
“Partial Hit - Refill” counter. But, it doesn't increment any counter as long as the content is not fully available
in the cache.
Conditions If the fill was in progress, the second request would be bypassed and will not increment any partial
request statistics. This is expected.
Workaround None.
Release Notes for Cisco ECDS 2.5
26
OL-24532-03
Caveats and Known Issues
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCtn78171
Redirect URL is changes by one character when “~” is in the content URL
Symptom If a delivery service content URL contains a “~” then one of the characters will be different in the
URL that shows up under “Replication Status” and what will ultimately be used with the routing domain name
from the client.
Conditions Prepositioned content which has a “~” in the URL.
Workaround Refrain from allowing the tilde character “~” in the origin content URL. If necessary make sure
to note the way the URL is changed under “Replication Status”.
CSCto84569
Note
This problem does not affect systems where the Cisco UCS CIMC/BIOS version is 1.4.1 or later.
Boot order changed when removing or inserting HDD
Symptom If user removes an existing hard disk, or adds a new hard disk, when server is reboot/reloaded, it
fails to boot Cisco ECDS.
Conditions Cisco ECDS needs to be boot from internal USB flash drive. Adding or removing hard disk will
cause system BIOS hard disk/USB boot sequence reset, hence USB drive drops from top of the boot sequence.
Workaround Use the following procedure to reset USB drive boot priority:
1.
Log into the CIMC GUI as admin.
2.
Launch the KVM console and power-cycle the server.
3.
When the splash screen displays in the KVM console window, press F2 to go to the “Set Up” screen. You
may need to press F2 a few times.
4.
When Setup Utility screen appears, go to Boot Option > Hard Disk Order and press Enter.
5.
Use PLUS (+) to move the <...USB ...> item to top
6.
Press F10 and select yes to save.
7.
Press ESC to exit and reboot the server.
Release Notes for Cisco ECDS 2.5
OL-24532-03
27
Related Documentation
Table 11
Open Caveats in Cisco ECDS 2.5.x (continued)
Identifier
Description
CSCto95228
SR service router not updated after coverage zone file change
Symptom This issue is seen when client adds new SE and removes old SE entries from coverage zone file then
submits change from CDSM, but CLI still displays old route while show routing statistics responds invalid
SE for newly added entry.
Workaround Delete the existing coverage file and add a new one and this problem will not occur.
CSCtq13061
Intermittent: standard/extended IP ACL condition not deleted from SE
Symptom This intermittent issue is seen when client uses CDSM to delete standard or extended ACL
condition and submits change from CDSM, but CLI on SE does not reflect this change.
Workaround So far this issue is only seen intermittently on the Internet Explorer 8 browser, it has not been
observed when using the Firefox 3.6.x browser.
Related Documentation
For complete document support for the Cisco Media Delivery Engine appliances and the
Cisco Enterprise Content Delivery System, see the Documentation for the Enterprise Content Delivery
System (Cisco ECDS) document roadmap at the following link:
http://www.cisco.com/en/US/docs/video/ecds/documentation.html
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional
information, see the monthly What’s New in Cisco Product Documentation, which also lists all new and
revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What’s New in Cisco Product Documentation as an RSS feed and set content to be
delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently
supports RSS Version 2.0.
Release Notes for Cisco ECDS 2.5
28
OL-24532-03
Obtaining Documentation and Submitting a Service Request
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of
Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The
use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any
examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only.
Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011-2012 Cisco Systems, Inc. All rights reserved.
Release Notes for Cisco ECDS 2.5
OL-24532-03
29
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco ECDS 2.5
30
OL-24532-03