Table of Contents

Release Notes for Cisco Internet CDN Software, Version 2.1.1

February 15, 2002

Contents

These release notes contain information about the Cisco Internet Content Delivery Network (CDN) Software, Version 2.1.1. It describes the following topics:

• Introduction
  
  
• System Requirements
  
  
• Updating to a New Software Version
  
  
• Important Notes for Service Providers
  
  
• Important Notes for Content Providers
  
  
• Caveats
  
  
• Documentation Omissions
  
  
• Documentation Corrections
  
  
• Product Documentation Set
  
  
• Related Product Documentation
  
  
• Obtaining Documentation
  
  
• Obtaining Technical Assistance
  
  

Introduction

The Cisco Internet CDN Software Version 2.1.1 contains the following modifications since the release of Version 2.1:

• New and expanded command-line interface (CLI) commands relating to system configuration properties, RealServer, file copying, and database troubleshooting
  
  
• A manifest file validator utility that validates the Extensible Markup Language (XML) syntax of a manifest file
  
  
• Ability to query database using Structured Query Language (SQL) queries and read-only database views
  
  
• Enhanced security for manifest file retrieval and for the Oracle database connection
  
  
• Load-based routing to Content Engines
  
  
• Various fixes since the previous software release
  
  

System Requirements

This section describes the devices and third-party applications that are supported on an Internet CDN, the media servers that are native to these devices, and the software and servers that are required for you to set up and manage an Internet CDN.

Cisco-Supported Hardware

Cisco Internet CDN Software Version 2.1.1 operates with the following Cisco hardware:

• Content Distribution Manager 4670 ICDN (model number CDM-4670-ICDN-K9)
  
  
• Content Router 4450 ICDN (model number CR-4450-ICDN-K9)
  
  
• AC and DC versions of the Content Engine 500 ICDN Series (model numbers CE-590-ICDN-K9 and CE-590-DC-ICDN-K9, respectively)
  
  
• AC and DC versions of the Content Engine 7320 ICDN Series (model numbers CE-7320-ICDN-K9 and CE-7320-DC-ICDN-K9, respectively)
  
  
• Content Services Switch 1115x and 1180x
  
  
• Cisco Catalyst switches (optional)
  
  
• AC and DC versions of the Storage Array 6 (model numbers SA6-SHF-6Disk-AC and SA6-SHF-6Disk-DC, respectively) for use with the Content Engine 590
  
  
• Storage Array 12 (model number SA12-SHF-12Disk-AC) for use with the Content Engine 7320
  
  

Refer to the Cisco documentation that came with each device for detailed, device-specific instructions on handling, installing, and configuring your Cisco CDN hardware.

Software Compatibility

For Version 2.1.1, the following upgrade sequences for the Cisco Internet CDN Software are supported:

• Version 2.0.1 —> Version 2.1.1
  
  
• Version 2.0 —> Version 2.1.1
  
  
• Version 2.1 (25) —> 2.1.1
  
  
• Version 2.1 (28) —> 2.1.1
  
  
• Version 1.0.2 —> Version 2.0.1 —> 2.1.1
  
  
• Version 1.0.1 —> Version 2.0.1—> Version 2.1 —> 2.1.1
  
  

The following downgrade sequences are supported:

• Version 2.1.1 —> 2.0.1
  
  
• Version 2.1.1 —> Version 2.1 (25)
  
  

Workstations That Access the Web-Based Interface

You interact with the Cisco Internet CDN Software using the web-based graphical user interface that is installed on the Content Distribution Manager. The following minimum hardware and software requirements apply to each machine that is used as a workstation for accessing the graphical user interface.

Network

• Ethernet connection
  
  
• Connection to the Internet
  
  

Platform and Operating System

• Windows 95/98 Pentium-class system, 266 MHz, 64 MB of RAM
  
  
• Windows NT/2000 Pentium-class system, 266 MHz, 64 MB of RAM
  
  

Software

• Microsoft Internet Explorer 4.x/5.0 (or later)
  
  
• Netscape 4.7 (or later)
  
  

Database Management System

The Cisco Internet CDN Software requires that the Oracle 8i database management system (DBMS) be installed on your host network. The Cisco Internet CDN Content Distribution Manager uses an Oracle database for persistent storage of system information and statistics.

The Cisco Internet CDN does not require a dedicated Oracle database. If you already have an Oracle database in use within your organization, that database can also be used with your Internet CDN.

If you have not already done so, you must purchase Oracle 8i from Oracle. The DBMS requirement is Oracle 8i Version 8.1.6 or later.

For information about setting up the Oracle 8i database, refer to the Oracle documentation, and the Cisco Internet CDN Software Configuration Guide for version 2.1, Chapter 2, in the section "Setting Up the Oracle 8i DBMS."

Domain Name System

Cisco Internet CDN Software Version 2.1.1 uses the Domain Name System (DNS) to route requests to Content Engines. To serve content in your CDN, you must configure DNS. For information on how to do this, see the Cisco Internet CDN Software Configuration Guide for Version 2.1, Chapter 2, in the section "Configuring DNS."

RealServer, Darwin Streaming Server, and WMT Server

Content Engines that serve QuickTime media files using the Apple Computer Darwin Streaming Server, RealNetworks RealMedia files, or Windows Media files require that the server software be installed. Cisco Internet CDN Version 2.1.1 Content Engines ship with the Darwin Streaming Server Version 3.0, the RealNetworks RealServer Version 8.0, and the Starbak Windows Media Technologies (WMT) Server already installed.

If you wish to distribute RealMedia content over your CDN, you must also purchase a server license from RealNetworks in order to use the RealServer feature.

If you intend to serve live content using RealServer on Cisco Internet CDN Software Version 2.1.1, you must upgrade the RealServer software on your origin server to RealServer Version 8.0 if you have not already done so.

If you wish to distribute WMT content over your CDN, you must purchase a WMT server license from Cisco Systems for each Content Engine that will be serving WMT content.

File Transfer Protocol Server

You need a File Transfer Protocol (FTP) server configured to receive ACTIVE-mode transmissions if you want to enable remote logging. For information, refer to the Cisco Internet CDN Software online help or the Cisco Internet CDN Software User Guide for version 2.1.

SNMP Manager

You need a Simple Network Management Protocol (SNMP) manager if you want to monitor
system statistics using SNMP. For information about creating and registering an SNMP manager with your CDN, refer to the Cisco Internet CDN Software User Guide for version 2.1, Chapter 4, in the section "Creating an SNMP Manager."

The Cisco Internet CDN Software Version 2.1.1 implements the HOST-RESOURCES MIB (IETF standard RFC 2790) and the CISCO-CONTENT-NETWORK-MIB. The CISCO-CONTENT-NETWORK-MIB monitors statistics related to the operation of the CDN.
You can find the definition of the CISCO-CONTENT-NETWORK-MIB at ftp://ftp.cisco.com/pub/mibs/v2/CISCO-CONTENT-NETWORK-MIB.my. For information on traps and variables in this MIB, refer to the Cisco Internet CDN Software User Guide for version 2.1.

Updating to a New Software Version

Review this entire section before beginning a software upgrade. It is important to have a clear view of the entire upgrade process before beginning.

To update your Internet CDN Software, you must follow this three-step procedure:

• Step 1—Determine the current software version
  
  
• Step 2—Add the software update file to your CDN
  
  
• Step 3—Update the software on your Internet CDN devices
  
  

In order to access and download your Cisco Internet CDN Software update, you need a registered username and password. If you are a Cisco customer and service contract owner, a Cisco reseller, Premier Certified Partner, the customer of a Cisco certified Partner Initiated Customer Access (PICA) partner, or a Cisco consultant, you can acquire a login directly from the Cisco.com website.

If you have questions or concerns about the upgrade, contact your designated Cisco Internet CDN Technical Support representative.

Step 1—Determine the Current Software Version

To determine the version of the Cisco Internet CDN Software that you are using:

Step 1   In your web browser, enter the secure IP address or DNS name of the Content Distribution Manager (CDM). For example:

https://10.0.0.0

 

Step 2   Log in to the Content Distribution Manager using the administrator username and password.

Step 3   From the Content Distribution Manager user interface, click Tools.

Step 4   From the System Tools drop-down list, choose Software Update.

Step 5   For each component (Content Distribution Manager, Content Engine, and Content Router), refer to the Version column. The current version of the software installed on that device is displayed.

Step 2—Adding a New Update File

Before you can update your Cisco Internet CDN Software, you must first acquire the appropriate software update file from Cisco.

In order to acquire the software update from Cisco, you must first:

• Access the Cisco.com website and locate the software update files.
  
  
• Download the software update files to a web server within your own organization or copy the location (URL) for the files (see the "Adding a New Update File Directly from Cisco.com" section).
  
  
• Add the update to the CDN by copying the URL for the update files (pointing either to your web server or Cisco.com) to the Content Distribution Manager.
  
  
• Use the software update feature to import the update file pointed to by the link.
  
  

You must have a Cisco.com username and password before attempting to download a software update from Cisco.com. In order to acquire a Cisco.com login, go to http://www.cisco.com and click the Register link.

Note   You need a service contract number, Cisco.com registration number and verification key, Partner Initiated Customer Access (PICA) registration number and verification key, or packaged service registration number in order to obtain a Cisco.com username and password.

To add an update file for the Cisco Internet CDN Software:

Step 1   Launch your preferred web browser and point it to:

http://www.cisco.com/pcgi-bin/tablebuild.pl/cdn-sp  

 

Step 2   When prompted, log in to Cisco.com using your designated Cisco.com username and password.

The Cisco Internet CDN Software download page appears, listing the available software updates for the Cisco Internet CDN Software product.

---

Note   Each software update consists of two files: a binary-format update file (*.upg) and a smaller meta file (*.meta). Both files must be downloaded in order to successfully complete a Cisco Internet CDN Software update.

---

Step 3   Locate the files you wish to download by referring to the Release column for the proper release version of the software.

Step 4   Click the link for the software update file you wish to download. The order in which you download the update files does not matter. The download page appears.

Step 5   Click the Software License Agreement link. A new browser window will open displaying the license agreement.

Step 6   After you have read the license agreement, close the browser window displaying the agreement and return to the Software Download page.

Step 7   Click the filename link labeled Download.

Step 8   Click Save to file and then choose a location on your workstation to temporarily store the update file.

Step 9   Post the file you downloaded (*.meta or *.upg) to a designated area on your organization's web server and make note of the URL required to access this file. You will need it later.

---

Note   It is imperative that the upgrade (*.upg) file be placed in the same directory as its corresponding meta (*.meta) file.

---

Step 10   Repeat Step 3 through Step 9 for the other software update file.

Step 11   Launch the Cisco Internet CDN Software Version 2.1 Content Distribution Manager and log in using an administrative username and password.

Step 12   Click tools.

Step 13   From the drop-down list, choose Software Update.

The Software Update page appears listing available software updates. If there is currently no update available, a message appears.

Step 14   Click Add New Update File.

A page appears with a field for entering the URL of your software update.

Step 15   Paste the URL for the update meta file on your web server into the field provided. For example, a valid URL might look like this:

http://internal.mysite.com/cdn/internet-CDN-version.meta
 

where internet-CDN-version is the version number of the software update.

---

Note   Do not attempt to link directly to the UPG file. The relative location of the update file is provided by the meta file.

---

Step 16   Click OK.

The version and URL for the update file appear, for example:

1.0.3 http://internal.mysite.com/cdnsw.upg
 

Adding a New Update File Directly from Cisco.com

It is also possible to add a software update to the CDN directly from Cisco.com, rather than posting it on a web server within your organization first.

To add the software update directly from Cisco.com:

Step 1   Launch your preferred web browser and point it to:

http://www.cisco.com/pcgi-bin/tablebuild.pl/cdn-sp  

 

Step 2   When prompted, log in to Cisco.com using your designated username and password.

The Cisco Internet CDN Software (Cisco CDN Service Provider Software) download page appears, listing the available software updates for the Cisco Internet CDN Software product. Note that each software update consists of two files: a binary-format upgrade file (*.upg) and a smaller meta file (*.meta).

Locate the software update you wish to install by consulting the Release column for the proper release version of the software.

Step 3   Click the link for the meta (*.meta) file. The download page appears.

Step 4   Click the Software License Agreement link. A new browser window will open displaying the license agreement.

Step 5   After you have read the license agreement, close the browser window displaying the agreement and return to the Software Download page.

Step 6   Right-mouse click the filename link labeled Download and choose the Create Shortcut option (Netscape) or the Copy Shortcut option (Internet Explorer). If you are using the Netscape browser, copy the contents of the URL field in the dialog that appears, then click Cancel to close the Create Shortcut dialog.

Step 7   Point your browser to the address of your Cisco Internet CDN Software Version 2.1 Content Distribution Manager and log in using an administrative username and password.

Step 8   Click tools.

Step 9   From the drop-down list, choose Software Update.

Step 10   The Software Update page appears, listing available software updates. If there is currently no update available, a message appears.

Step 11   Click Add New Update File.

A page appears for specifying the URL for the update location.

Step 12   Paste the shortcut you copied for the update meta file on Cisco.com into the field provided. The URL should begin with:

http://www.cisco.com/pcgi-bin/Software/Tablebuild/download.cgi/...  
 

Step 13   Click OK.

The version and URL for the update file appear, for example:

1.0.3 http://internal.mysite.com/cdnsw.upg
 

Step 3—Update the Software on Your Cisco Internet CDN Devices

The Content Distribution Manager will reboot at the conclusion of the upgrade procedure, causing you to temporarily lose contact with the device and the graphical user interface.

To update the Cisco Internet CDN Software on your devices, follow these steps:

Step 1   From the Content Distribution Manager user interface, click tools.

Step 2   From the drop-down list, choose Software Update.

Step 3   On the Software Update page, click the radio button next to the update file that you want to use.

Step 4   Click the tab corresponding to the type of device that you want to upgrade, for example, Content Routers. The window refreshes, listing the devices of the selected type on your CDN.

---

Note   When updating the software on your Content Engines, you need to ensure that all Content Engines in a single supernode are updated at the same time.

---

Step 5   Refer to the column labeled Version to verify that the devices you are choosing are not already running the version to which you will be upgrading. Also verify that the current version has an upgrade path to the version to which you are upgrading.

---

Note   If you have questions regarding upgrade paths, see the "Software Compatibility" section on or contact Cisco Technical Support.

---

Step 6   Check the check boxes next to the name of the device you will be upgrading, or check the box in the column header to select all devices.

Step 7   Click OK. The update process begins on the selected devices and they go offline temporarily.

Step 8   Repeat Step 4 through Step 7 for each device or group of devices that you wish to upgrade.

Step 9   Click the Refresh button to see the status of your upgrade.

You have completed the software update procedure.

Allow 15 to 30 minutes for the devices to come online on the CDM user interface after the upgrade has been completed. The CE-7320-CDN takes longer to come online than the CE-590-CDN because of the number of drives on the device.

Important Notes for Service Providers

This section describes issues related to Version 2.1.1 of the Cisco Internet CDN Software that may be of use or interest to service providers. The topics covered are:

• Accessing CDN Database Tables Using Read-Only Database Views
  
  
• Restoring a Deleted Content Distribution Manager to the CDN
  
  
• Deploying Cisco Internet CDN Behind a Firewall
  
  
• Implementing a Private Ethernet Link to the CDN Database
  
  
• Re-Synchronizing the Content Distribution Manager with an NTP Server
  
  
• Standby Content Distribution Manager Cannot Be Upgraded Through the User Interface
  
  
• Deployment of Standby Content Distribution Manager Requires Content Engines in Supernodes to Be Running Version 2.1 or Higher
  
  
• Using the RealServer RealSystem Media Commerce Suite
  
  
• Encoding Windows Media File Information in the Manifest File
  
  
• Limitations on Coverage Zones
  
  
• Large Content Engine Log Files May Be Transferred to FTP Host
  
  
• Some Features Are Unusable Unless All Devices Are Running the Same Software Version
  
  
• Configuration Script for the Content Services Switch Has Been Modified
  
  

Accessing CDN Database Tables Using Read-Only Database Views

Cisco has created a way for customers to gain programmatic access to data stored in the CDN Oracle database. Database views provide a look into data that is persisted by the CDM and can be accessed using SQL queries directly against the CDN database.

Information gathered through database views can be then be used to monitor the Content Distribution Network (CDN) for changes.

The following database views are now available:

• CE_VIEW (Detailed information for Content Engine)
  
  
• CR_VIEW (Detailed information for Content Router)
  
  
• REGION_VIEW
  
  
• LOCATION_VIEW
  
  
• SUPERNODE_VIEW
  
  
• CLUSTER_VIEW
  
  
• HOSTEDDOMAIN_VIEW (Hosted Domain information)
  
  
• SYS_MESSAGE_LOG_VIEW (System messages - these include liveness information)
  
  
• VIRTUAL_CDN_VIEW
  
  
• CDM_VIEW
  
  
• CUSTOMER_VIEW
  
  
• UPDATE_LOG_VIEW
  
  
• HOSTEDDOMAIN_TO_CLUSTER_VIEW
  
  
• VIRTUAL_CDN_TO_CLUSTER_VIEW
  
  
• CONFIG_PROPERTY_VIEW (System configuration properties - including specifications on third party services (applications) running on nodes.
  
  

For detailed information and technical documentation on accessing the Cisco Internet CDN database views, please contact your Cisco Account Representative.

Restoring a Deleted Content Distribution Manager to the CDN

Content Distribution Managers (CDMs) that are designated as "standby" CDMs can be deleted from the network. To add deleted CDMs back to the network, use the following procedure:

Step 1   Establish a Secure Shell (SSL) connection to the Content Distribution Manager and log on using your administrative login and password.

Step 2   Enter register. This causes the standby device to identify itself to the primary Content Distribution Manager.

Step 3   Point your web browser to the address of the primary Content Distribution Manager and log in to the graphic user interface.

Step 4   Activate the standby Content Distribution Manager through the user interface by following the instructions for "Changing the Warm Standby Content Distribution Manager Role" in Chapter 4: Maintaining Cisco Internet CDN Software of the Cisco Internet CDN Software User Guide.

Step 5   Wait for the standby CDM to come online, refreshing the CDM user interface periodically until you see the standby device status change.

When the user interface indicates online status, the CDM is back on the network and has synchronized its database with the other CDM.

Deploying Cisco Internet CDN Behind a Firewall

It is possible to deploy your Cisco Internet CDN behind a firewall. Technical documentation now exists with detailed information on supported and unsupported Internet CDN configurations if you will be deploying behind a firewall as well as port utilization for CDN devices.

For more information and for access to technical information on configuring your CDN behind a firewall, contact your Cisco Account Representative. (Issue CSCdv76716.)

Implementing a Private Ethernet Link to the CDN Database

Version 2.1.1 of the Cisco Internet CDN Software allows you to link your Content Distribution Manager to your designated CDN database server via a secondary, private network interface card (NIC). This allows your CDM to communicate with the CDN database without simultaneously exposing the database host to the larger CDN network.

For more information and for access to technical information on configuring a private ethernet connection to your CDN database, contact your Cisco Account Representative.

Re-Synchronizing the Content Distribution Manager with an NTP Server

The Content Distribution Manager (CDM) acts as the default network time protocol (NTP) server for the CDN. Content Engines and Content Routers synchronize their time with that of the CDM.

However, if the CDM is behind a firewall that blocks access to public NTP servers such as tick.usno.navy.mil, it may be prevented from synchronizing, thus preventing the Content Engines and Content Routers from synchronizing with it.

If this happens, the CDM must be synchronized with an NTP server that it can access—for example, an NTP server that is also located behind the firewall.

To re-synchronize your CDM with an NTP server, you must:

• Identify an NTP server that is accessible to your CDM
  
  
• Update the list of NTP servers used by the CDM to include the address of this NTP server, if that address is not already on the list
  
  
• Synchronize the CDM with the NTP server
  
  

See the sections that follow for detailed instructions on each of these steps.

Identifying an NTP Server for the CDM

To determine whether your CDM can communicate with a NTP server:

Step 1   Use Secure Shell (SSH) to connect to your CDM.

Step 2   Log on to the CDM using the "merlot" account and password. The bash shell will load.

Step 3   At the bash prompt, enter the following command:

0 # /etc/rc.d/init.d/xntpd stop

Step 4   Next, verify that the CDM is communicating with your recognized public or private NTP server using the following command:

0 # ntpdate <ntp_server_name>

Step 5   If you receive a message that no suitable server is found at the address you provided, repeat Step 4 until you receive a confirmation.

Update the NTP Server List

Step 1   Once you receive a confirmation, write down the address of the NTP server.

Step 2   Open a web browser and log in to the CDM graphical user interface.

Step 3   Use the System Configuration page to set the address of the NTP server.

Refer to the "Customizing the Network Time Protocol Server List" section in Chapter 4, Maintaining Cisco Internet CDN Software" of the Cisco Internet CDN Software User Guide for instructions on adding an NTP server to the list consulted by the CDM.

Synchronize the Content Distribution Manager

Step 1   Reboot the CDM. When the CDM reboots, it will synchronize its time with the NTP server you specified.

Step 2   Once your CDM has synchronized, you can reboot the other nodes in your CDN to force them to synchronize with your CDM.

Refer to Chapter 3: "Working with Cisco Internet CDN Software" in the Cisco Internet CDN Software User Guide for instructions on stopping and starting your CDN devices.

Refer to Chapter 4: "Maintaining Cisco Internet CDN Software" in the Cisco Internet CDN Software User Guide for instructions on adding an removing NTP servers from the list consulted by the CDM.

Standby Content Distribution Manager Cannot Be Upgraded Through the User Interface

To upgrade a standby Content Distribution Manager (CDM):

Step 1   Log in as admin to a Secure Shell (SSH) session with the CDM.

Step 2   Load the upgrade file onto the CDM by entering the following commands:

ftp
ftp> open ftp.cisco.com

ftp> username: CCO_user_account_name
ftp> password: CCO_account_password
ftp> passive

ftp> cd/cisco/content-delivery/cdn/sp

ftp> get upgrade_filename

ftp> bye

Host> enable

Host# upgrade swupgrade

 

When the upgrade is complete, the CDM will reboot itself.

Deployment of Standby Content Distribution Manager Requires Content Engines in Supernodes to Be Running Version 2.1 or Higher

While versions 2.1 or higher of the Cisco Internet CDN Software support CDNs in which some nodes are running earlier (2.0.x) CDN software releases, if you have deployed a failover Content Distribution Manager (CDM) and supernodes on the same CDN, it is necessary to update the software on all Content Engines and Content Routers in your supernodes to Version 2.1 or higher so that those supernodes can continue to communicate with the failover CDM.

Using the RealServer RealSystem Media Commerce Suite

The RealServer RealSystem Media Commerce Suite (RSMCS) has not been shipped with the software. (Caveat CSCdv66612). You must instead purchase the appropriate RealServer RSMCS plug-in from Real Networks and then install it on a Content Engine running Version 2.1 or later of the Cisco Internet CDN Software. For Version 2.1.1 a special command, real rsmcs, has been implemented to streamline deployment of the plug-in.

Note   For RealMedia content that you want protected by RSMCS, specify the playserver property as "real" in the manifest. For example, if you have an RSMCS file named foo.rms, and want the cdn-url to be cdn_foo.rms, the item in the manifest file should read: <item playserver="real" src="/foo.rms" cdn-url="/cdn_foo.rms">

Once you have obtained the plug-in, follow these steps to install it on your Content Engine:

Step 1   Verify that the plug-in file you have is rmffplin-linux.so.6.0, the Linux version that you need for the Cisco Internet CDN.

Step 2   Log in to the Content Engine on which you will be deploying the Commerce Suite.

Step 3   Transfer the plug-in to the cisco/merlot/state directory on the Content Engine using the scp or ftp commands.

Step 4   Enter enabled mode. For example:

Host>enable

Host#

Step 5   Enter the following command:

Host#real rsmcs

The RealSystem Media Commerce Suite (RSMCS) Plugin Administration menu appears.

Step 6   Choose option 1 to add your RSMCS license.

Step 7   Restart the Cisco Internet CDN Software by entering control restart.

Encoding Windows Media File Information in the Manifest File

In previous Cisco Internet CDN Software releases, if a HTTP URL was contained in a published ASX file, file information (like author and copyright) contained in the ASX file was not displayed on the player. The use of HTTP URLs is integral to the functioning of hybrid routing on the CDN.

In Version 2.1.1 an attribute, streamProperty, has been added to the <item/> and <item-group/> tags for use with Windows Media files (WMA, WMV, and ASF) only.

Note   The streamProperty attribute only works with Windows Media Player Version 7.0 and later.

This attribute specifies one or more file properties that are displayed in the Windows Media Player when the file is played.

The supported attributes are:

• abstract
  
  
• title
  
  
• author
  
  
• copyright
  
  

For example, a manifest file might contain the following syntax:

<CdnManifest>
<server name="origin-server">
<host name="www.name.com"
proto="http"
		port="80" />
</server>
<item cdn-url= "q4results.asf"

server="originserver"

src= "video/q4results.asf"
type="live"

playserver="wmt"
streamProperty = "author='paul roberts' 
title='Cisco Q4 Results'  copyright='Cisco 02'"
ttl=300/>
</CdnManifest>

Limitations on Coverage Zones

For coverage zones to work, all Content Routers must be running Cisco Internet CDN Software Version 2.1 or higher. Coverage zones for a particular hosted domain work only if all Content Engines serving that hosted domain are running Internet CDN Software Version 2.1 or higher.

Large Content Engine Log Files May Be Transferred to FTP Host

If Content Engine log files exceed the size limit specified on the Tools > Remote Logging page on the Content Distribution Manager graphic user interface while still being generated, they are transferred to the FTP remote logging host. Existing log files are not affected in this way.

Some Features Are Unusable Unless All Devices Are Running the Same Software Version

A CDN comprised of devices using mixed versions of the Cisco Internet CDN Software is supported. However, some features are unusable in the CDN unless all devices are running the same version. These features are:

• Windows Media Technologies (WMT) support— If you want to serve WMT for a hosted domain, you must ensure that all Content Engines serving that hosted domain are running Version 2.1 or higher.
  
  
• Hybrid routing— To use the hybrid routing feature, all CDN devices need to be running version 2.1 or higher.
  
  
• Warm standby Content Distribution Manager (CDM)—CDN devices that are not running Version 2.1 or higher will not be aware of the standby CDM.
  
  

Configuration Script for the Content Services Switch Has Been Modified

The Content Services Switch (CSS) configuration script has been modified to allow you to add as many interfaces to a VLAN as are available on the CSS. In prior releases, a maximum of 32 interfaces was imposed for any single VLAN. After you assign a number to the VLAN, you are asked to assign interfaces in increments of ten. For example:

What is the number (1-4095) of this VLAN? [default = 1] 821

Configuring interfaces bridged to this VLAN...
How many interfaces are bridged to this VLAN? 56

Please input interfaces from 1 to 10: Separate them by space.
1/1 1/2 1/3 1/4 1/5 1/6 1/7 1/8 2/1 2/2

Please input interfaces from 11 to 20: Separate them by space. 
2/3 2/4 2/5 2/6 2/7 2/8 3/1 3/2 3/3 3/4

Do not input fewer than ten interfaces, unless there are no more to enter. The script asks you to input interfaces only as many times as it takes for you to enter all the bridged interfaces in increments of ten.

For example, if you entered 56 as the number of interfaces you would like bridged to the VLAN, the script will prompt you six times. The script does not check to ensure that you input as many interfaces as you initially asked for. If you fail to enter all the interfaces in this sequence of the script, you must run the script again until all interfaces are accounted for.

Important Notes for Content Providers

This section describes guidelines that content providers need to follow when modifying their web site to place content on their CDN. It also describes the behaviors that users accessing their CDN-enabled content can expect to see. The topics covered are:

• Windows Media Player Plug-In Required for a Netscape Browser
  
  
• Uppercase Tags Should Not Be Used in Content URLs
  
  
• Automating Manifest File Generation
  
  
• Using the Manifest Validator to Validate Manifest File Syntax
  
  

Windows Media Player Plug-In Required for a Netscape Browser

If the end user has Windows Media Player Version 7.1 installed and tries to open a Windows Media Technologies (WMT) file in a Netscape Version 4.76 browser, an error message may appear, saying "Invalid or corrupt data was encountered." Content providers should inform end users that if they encounter this error message, they may need to install a Window Media Player plug-in for Netscape. To download the plugin, end users should:

Step 1   Go to http://www.microsoft.com/windows/windowsmedia/download/default.asp.

Step 2   In the Select Version field, choose Player Plugin for Netscape from the drop-down menu.

Step 3   Click the Download Now button to download the plug-in.

Uppercase Tags Should Not Be Used in Content URLs

Browsers display a "Page Not Found" message and fail to stream content if the CDN tag in the content URL has uppercase letters, for example:

		http://hosted_domain/CDN-MEDIA/filename.xx.  

Automating Manifest File Generation

This section contains information that you can use to automate the creation of manifest files for your website:

• Overview
  
  
• Installing PERL on Your Workstation
  
  
• Obtaining the Scripts
  
  
• Listing Website Content Using the Spider Script
  
  
• Spider Script Syntax Guidelines
  
  
• Combining Spider Data
  
  
• Customizing the Spider Script
  
  
• Selecting Live and Pre-Positioned Content Using the Manifest Script
  
  
• Manifest Script Syntax Guidelines
  
  
• Customizing the Manifest Script
  
  
• Creating a Rules File for the Spider and Manifest Scripts
  
  

Overview

Two sample scripts are provided to you:

• Spider—Crawls over the content of an origin server and outputs a database file containing a list of URLs for all potentially pre-positioned or live content objects on that origin server, regardless of whether that content will eventually be pre-positioned or streamed live from the hosted domain
  
  
• Manifest—Reads the database file output by the spider script and, using rules set out by the content provider, produces an XML-format manifest file containing the URLs of just those items or types of content that a Content Provider wants to make available to users through a hosted domain.
  
  

These scripts shipped with your CDN software and can serve as the basis for your own automation scripts.

Installing PERL on Your Workstation

You need to have PERL installed on your workstation before to working with or running the spider or manifest scripts. It may also be useful to have a PERL compiler available. PERL is open source software and can be downloaded for free from a variety of locations on the Internet. Refer to the Comprehensive PERL Archive Network (CPAN) at http://www.cpan.org, or http://www.perl.com.

Obtaining the Scripts

The spider and manifest scripts can be obtained from Cisco.com using the same procedure that is used to obtain updated versions of the Cisco Internet CDN Software.

To obtain the scripts from Cisco.com:

Step 1   See the "Step 2Adding a New Update File" section for instructions on locating the Internet CDN Software Download area of Cisco.com.

Step 2   When you are asked to locate the files you wish to download, look for the file named manifest-tools.zip. This is a ZIP archive containing both the manifest and spider PERL scripts.

Step 3   Follow the rest of the instructions to download the manifest-tools.zip file from Cisco.com.

Step 4   Use your preferred unzip program to unpack the scripts to a location on your workstation or your network.

Listing Website Content Using the Spider Script

This section contains information on the following topics:

• Spider Script Syntax Guidelines
  
  
• Combining Spider Data
  
  
• Customizing the Spider Script
  
  

In the simplest scenario, the spider script is pointed to the address of an origin server and given the name of a database (.db) file into which it will place any valid URLs it discovers on that site. For example, if you wanted to analyze the contents of www.cisco.com for content that might be pre-positioned, you would issue the following command:

spider --start=www.cisco.com --db=ciscocontent.db

 

Limiting Scope

But running the spider script on all of www.cisco.com might take too long and produce more information than you want. What if you want to limit your review of an origin server to just a particular part of that server? The spider script contains a variety of tools that enable you to limit as well as broaden the scope of the search action.

For example, to limit the search of www.cisco.com to just that part of the server containing product-related support information, you could enter the following command:

spider --start=www.cisco.com/public/support/ --db=ciscocontent.db

 

Broadening Scope

To ask the spider script to broaden its search and follow links from www.cisco.com to the Cisco networking professionals forum, you could enter the following spider command:

spider --start=www.cisco.com --allow=forums.cisco.com --db=ciscocontent.db

 

Running the Spider Script Against Servers More Than Once

In addition to searching new origin servers, the spider script can also be run on sites that have already been analyzed and that contain links to the CDN. When running the spider script on a server that has already been analyzed, you use the --hd keyword to specify the name of hosted domain on which content from the origin server will be hosted, and the --map keyword to provide mapping information between URLs on the origin server and on the Internet CDN.

For example, the following commands will trace the content mapped to the /support area on the hosted domain www.hosted.cisco.com back to its origins in the support area of www.cisco.com:

--start=http://www.cisco.com/public/support/tac/home.html  
--hd=www.hosted.cisco.com

--map=http://www.cisco.com/public/support/tac/=/support  

--db=ciscocontent.db
 

In each of the examples listed above, the spider script analyzes the URL of each piece of content on the origin server or in that area of the origin server that has been targeted and applies filters to the content that incorporate the parameters supplied when the spider script was run previously, identifying potential pre-positioning or live streaming candidates. If the URL matches the pattern provided by the spider script search, it is accepted and its URL is recorded in the database being created by the script. If the pattern does not match, the content is rejected and the spider script search moves on.

Spider Script Syntax Guidelines

The spider script uses the following syntax:

spider {--start=origin_server_url
[--allow=allowed_url | --depth=number | --file=filename |
{--hd=hosted_domain_name --map={origin_server_url_prefix=cdn_prefix} } |
--limit=number | --prefix=url_prefix | --reject=disallowed_url | ]
--db=database_name.db}

Table 1describes the spider script keywords.

--start=www.cisco.com

--allow=forums.cisco.com

--db=ciscocontent.db

--depth=6

--file=cisco-rules.cfg

--hd=www.hosted.cisco.com

--limit 1000

--map=http://www.cisco.com/  

public/support/tac/=/support

--reject=cgi-bin

Combining Spider Data

You can run the Spider script on two separate locations on an origin server and then combine the content into one database from which a manifest file will be generated.

To combine spider script data:

Step 1   Open the *.db file containing the data you want to move, select that data and copy it.

Step 2   Open the *.db file you want to serve as the merged file.

Step 3   Locate the end of the file, and paste the data you copied into it.

The manifest script can now be run on the merged data. See the "Manifest Script Syntax Guidelines" section.

Customizing the Spider Script

Because the Spider script anticipates certain platforms and scenarios that might not correspond to your own website configuration, Cisco provides you with the PERL source code for the spider script, which you can modify to suit your own needs.

See the "Obtaining the Scripts" section for instructions on downloading the spider script from Cisco.com.

Selecting Live and Pre-Positioned Content Using the Manifest Script

Whereas the spider script is used to gather a list of potential hosted content from an origin server, it is in the manifest file that you analyze all the information gathered by the spider script and decide which content you will actually import to the CDN for placement on a hosted domain.

This section contains information on the following topics:

• Manifest Script Syntax Guidelines
  
  
• Customizing the Manifest Script
  
  

Pre-Positioned versus Live Content

The manifest script distinguishes between content that needs to be pre-positioned and live, streamed content that by definition cannot be pre-positioned.

Using the prepos command, you identify and pre-position all content which meets criteria that you specify. For example, to pre-position all image files from cisco.com larger than one megabyte, you would enter the following command:

manifest --prepos='type(image/*) and size > 1000k' --db=ciscocontent.db --xml=cisco.xml

 

Using the live command, you identify the URLs of live content. Unlike pre-positioned content, live content cannot be identified by information stored in the header, so you will need to devise a method of locating live content based solely on information contained in the URL of that content. For example, you might identify streamed content with the following command:

manifest --live='match(rtsp://*)'

Manifest Script Syntax Guidelines

The manifest script uses the following syntax:

manifest {[--file=filename | --live='keyword_comparison' | --prepos='keyword_comparison' | --set='attribute=value : keyword_comparison' | --playservertable=filename | --map={origin_server_url_prefix=cdn_prefix}] --db=database_name.db --xml=manifest_file_name.xml}

Table 2 describes the manifest script keywords.

--file=ciscocontent.cfg

--live='match(rtsp://*)'

--prepos='type(image/jpg) 
and size > 1000k'

--set='ttl=10000 : 
match(*/urgent/*)'

--playservertable=info.txt

--xml=ciscomanifest.xml

--prepos='match 
(http://forums.cisco.com/*)'  

--prepos='size >= 1000k'

--prepos= 'time < 72 hours'

Customizing the Manifest Script

Because the manifest script anticipates certain platforms and scenarios that might not correspond to your own website configuration, Cisco provides you with the PERL source code for the manifest script, which you can modify to suit your own needs.

See the "Obtaining the Scripts" section for instructions on downloading the manifest script from Cisco.com.

Creating a Rules File for the Spider and Manifest Scripts

When using the spider and manifest scripts on a large web server, the parameters and rules you set for your scripts may be numerous and complex. When this is the case, it may make more sense to create a file containing all your instructions to the scripts that you can then simply point to rather than having to type a long series of commands again and again.

Using a rules file makes it easy to rerun the spider and manifest scripts and be confident that the scripts are receiving identical commands each time. In addition, the same rules file can be read by both the manifest and the spider scripts without generating incorrect output; the spider script simply ignores commands for the manifest script, and vice versa.

To create a rules file for the spider and manifest scripts to use:

Step 1   Open your preferred text editor.

Step 2   Enter your commands one at a time, each on its own line. Each line of your rules file is sent to the scripts as a single argument.

For example, a rules file for the Cisco website might read:

--start=www.cisco.com

--allow=forums.cisco.com

--reject=cgi-bin

--limit=0

--db=ciscocontent.db

--prepos='match(image/gif) and size > 1000k'
--xml=ciscomanifest.xml

Step 3   Save your file in a location relative to the spider and manifest scripts.

Step 4   Use the file command to run each script using your rules file. For example:

spider --file=cisco-rules.cfg

manifest --file=cisco-rules.cfg
 

Using the Manifest Validator to Validate Manifest File Syntax

Because correct and accurate manifest file syntax is vital to the proper deployment of your website content on the CDN, Cisco makes a manifest file syntax checker available at no cost to its customers. This command-line-based utility can be used to proof the manifest files that you have created for your hosted domain.

When run, the manifest validator reviews each line of your manifest file, identifying syntax errors where they exist and determining whether or not the manifest is valid and ready for use in importing content to your hosted domain. The results of the manifest validator's review of the manifest file are output to a text file in a location that you name.

The manifest validator is designed to run in the Windows (95/98, NT, 2000 and XP) and the Linux (RedHat 6.2) environments.

This section contains the following topics:

• Obtaining the Manifest File Validator
  
  
• Installing the Manifest File Validator
  
  
• Running the Manifest File Validator
  
  
• Understanding Manifest File Validator Output
  
  
• Repairing Manifest File Syntax
  
  

Obtaining the Manifest File Validator

The Manifest Validator utility can be obtained without cost from Cisco.com using the same procedure that is used to obtain updated versions of the Cisco Internet CDN Software.

To obtain the scripts from Cisco.com:

Step 1   See the "Step 2Adding a New Update File" section for instructions on locating the Internet CDN Software Download area of Cisco.com.

Step 2   When you are asked to "locate the files you wish to download," look for the file named manifest-validator.zip. This is a ZIP archive containing the validator utility.

Step 3   Follow the rest of the instructions to download the manifest-validator.zip file from Cisco.com.

Step 4   Use your preferred unzip program to unpack the utility to a location on your workstation or your network. Make sure all validator files are unzipped to the same location.

Installing the Manifest File Validator

Before installing the manifest validator, you must first install the Java (TM) 2 Runtime Environment, Version 1.2 or 1.3 on your workstation. The Java 2 Runtime Environment (JRE) contains the Java virtual machine, runtime class libraries, and Java application launcher. These components are necessary to run the Cisco manifest validator utility.

If you are using an earlier version of the JRE on your workstation, install either Version 1.2 or 1.3. You can download the latest version of the JRE along with instructions for installing it from the following web site:

http://java.sun.com  
 

After you install the JRE, use the following instructions to install and run the Cisco manifest validator utility:

Step 1   Create a directory for the manifest validator on your local drive. For example:

c:\manifest

Step 2   Locate the manifest validator archive, manifest-validator.zip, that was provided to you by your service provider.

Step 3   Unzip the manifest validator files into the directory you created.

Step 4   Verify that all manifest validator files are present in the manifest directory you created. Table 3 contains a list of the sources files that constitute the manifest validator utility and their purpose.

Running the Manifest File Validator

Once you have installed the Java 2 Runtime Environment and the Cisco manifest validator program files, you are ready to run the validator on a manifest file that you have created.

The manifest file validator can be run in one of two modes:

• Default mode—The manifest validator checks the syntax of your manifest file to make sure that source files are named for each content item in the manifest.
  
  
• Check size mode—The manifest validator checks the syntax of your manifest file to make sure that source files are named for each content item in the manifest. It then follows the URL for each content item to verify that the content is placed correctly and, if possible, to determine the size of the item. A special switch (-s) is used to run the validator in check size mode.
  
  

When running the manifest file validator, you are required to input the following information:

• Name and location of your manifest file, expressed either as a network file location <file> or a valid Internet URL <url>
  
  
• Name and location of the manifest validator's output file <output>.
  
  
• (Optional.) When the manifest file validator is used in check size mode, the length of time <seconds> that the manifest file validator should attempt to confirm the existence of content named in the manifest
  
  

To run the manifest validator utility:

Step 1   If you are running Windows, open a command prompt. Otherwise, proceed to Step 2.

Step 2   Change directories to the program directory for the manifest validator. For example, if you are running Windows, you would enter the following at the command prompt:

C:\>cd manifest

C:\manifest>
 

Step 3   Run the manifest validator as follows:

• If you are running Windows, enter the validate command and provide either a path and filename or URL pointing to your manifest file in the following format:
  
  

validate -f [<file> | -u <url>] -o <output> [-s <seconds>]

• If you are running Linux, enter the following commands, providing either a path and filename or URL pointing to your manifest file in the following format:
  
  

chmod u+x validate
validate -f [<file> | -u <url>] -o <output> [-s <seconds>]

Once you execute the validator, text output is displayed, indicating that the validator is running.

Step 4   Wait until the following message is displayed, indicating that the validator has completed processing the manifest file you pointed to:

Finish parsing /<manifest_file_name>.xml
 

Step 5   Locate the output file in the location that you specified and review it for errors.

The final lines of the manifest file validator's output will indicate whether or not the manifest is valid or not. For example, a valid manifest file output might read:

number of manifest warnings: 1
number of manifest errors: 0
manifest syntax is CORRECT
finish parsing
 

In this instance, one nonfatal syntax irregularity was located, but the manifest file was found to be syntactically correct. This file could be transferred to your service provider and used to deploy website content to your CDN.

The output file for an invalid manifest file will list the number of errors and warnings issued, for example:

number of manifest warnings: 1
number of manifest errors: 1
manifest syntax is INCORRECT
finish parsing
 

See the next section, "Understanding Manifest File Validator Output" for detailed information that will help you understand the manifest file validator results.

Understanding Manifest File Validator Output

Your manifest file validator output file will appear in the location you specified (using the -o option) when the validator was run.

Each output file has a similar structure and syntax and clearly identifies any errors or warning messages stemming from your manifest file syntax. Manifest files are judged by the validator either to be:

• CORRECT—Possibly containing syntax irregularities, but syntactically valid and ready for deployment on a CDN
  
  
• INCORRECT—Containing syntax errors and unsuitable for deployment on a CDN
  
  

Syntax Errors

The manifest file validator issues syntax errors only when the manifest file validator cannot identify a source file for a listed content item, either because it is not listed, or it is listed using improper syntax. All files containing syntax errors are marked INCORRECT.

Syntax errors are identified in the output with the ERROR label. In addition to the label, the line number containing the error is provided, as well as the manifest attribute for which the error was issued, valid options, and the default value for that attribute. For example, the following error appears in Example 1:

ERROR: japan.xml:13:Skip item because  is not defined.

In the preceding error message:

• japan.xml is the manifest file name
  
  
• 13 is the manifest file line number where the error occurs
  
  
• is the manifest file attribute generating the warning
  
  

start parsing file japan.xml

start options

 option clearlog: false

 option rd: null

 option prepos-tag: null

 option live-tag: null

 option notFoundUrl: null

 option noRedirectToOrigin: false

 option timezone: JST

 option manifest-id: null

end options

start server

 server name: WMTServer

start host

  host name: origin.cdn-japan.com

  host proto: http

  host port: 80

  host user: ceadmin

  host password: 3kDC

  creating new hash entry for WMTServer and origin.cdn-japan.com

 end host

end server

WARNING: japan.xml:13:Attribute "" is required and must be specified for element type 
"item".

start item

 item : null

 ERROR: japan.xml:13:Skip item because  is not defined.

end item

end CdnManifest

number of items processed: 1

number of manifest warnings: 1

number of manifest errors: 1

manifest syntax is INCORRECT

finish parsing

The total number of errors encountered in the manifest file is provided at the end of the validator output file.

Syntax Warnings

The manifest file validator issues syntax warnings for a wide variety of irregularities in the manifest file syntax. Files containing syntax warnings may be marked CORRECT or INCORRECT, depending on whether or not syntax errors have also been issued.

Syntax warnings are identified in the output with the WARNING label. In addition to the label, the line number containing the warning is provided, as well as the manifest attribute for which the warning was issued, valid options, and the default value for that attribute. For example, the following warning might appear in the output for the japan.xml manifest file:

WARNING: /~content/manifest/japan.xml:12:Attribute "type" with value "vod" must have a value from the list "(prepos|live)"

In the preceding warning message:

• japan.xml is the manifest file name
  
  
• 12 is the manifest file line number where the warning was issued
  
  
• type is the manifest file attribute generating the warning
  
  
• vod is the offending value
  
  
• (prepos | live) are the valid options for that attribute
  
  

The total number of warnings encountered in the manifest file is provided at the end of the validator output file.

Repairing Manifest File Syntax

Once you have identified syntax errors and warnings using the output from the manifest file validator, you can correct your manifest file syntax and then rerun the manifest file generator on the corrected file.

To repair your manifest file:

Step 1   Open your manifest file using your preferred XML editor.

Step 2   Referring to your manifest file validator output, use the line numbers provided by the manifest file validator to locate the syntax violations in your manifest file.

In general, it is a good idea to review each WARNING and ERROR tag in your manifest. Some warnings, although they still allow the manifest file validator to find your manifest file syntax correct, may still be the source of problems when you deploy your website content.

Step 3   After you have made all necessary corrections for syntax warnings and errors, save your manifest file.

Step 4   Run the manifest file through the manifest file validator again, and review the validator output for errors and warnings.

Step 5   Repeat Step 1 through Step 4 until all errors and warnings have been adequately resolved and until the manifest validator labels your manifest file CORRECT.

Caveats

Caveats describe unexpected behavior in Cisco Internet CDN Software.

• Severity 1 caveats are deemed critical.
  
  
• Severity 2 caveats are serious, but not critical.
  
  
• Severity 3 caveats are of moderate seriousness and are only selectively included in the release notes documentation.
  
  

This section describes the caveats--both resolved and unresolved--that are associated with Version 2.1.1 of Cisco Internet CDN Software.

Open Caveats

The following caveats are open (unresolved). Unresolved caveats are listed according to their tracking number.

• CSCdt96485
  
  

The QuickTime server runs even if you disable it.

• CSCdu04445
  
  

After you run netsetup on a Content Engine 7320, you see the following message:

epro100: Device or resource busy rmmod: module acenic is not loaded

You can ignore this message.

• CSCdu21113
  
  

The Supernode page allows you to create multiple supernodes with one Content Services Switch (CSS), even though creation of multiple supernodes on a single CSS is not supported. If you erroneously create multiple supernodes on one CSS, you should delete all supernodes associated with that CSS, and then create only one supernode.

• CSCdu24791
  
  

The sort indicator on the View Supernode page does not appear after you click the Refresh button.

• CSCdu38518
  
  

To preserve security, FTP is disabled on the Content Services Switch (CSS) by default. To transfer upgrade files to a CSS, you need to enable FTP on the switch. After you have transferred the file, you should disable FTP again.

• CSCdu41069
  
  

When an inactive Content Engine or Content Router is registered, the Modify Content Engine or Modify Content Router page initially displays the fully qualified domain name (for example, ce590-1.canada.org). Once the Content Engine or Content Router reboots for the first time and comes online, only the host name (for example, ce590-1) is displayed on the user interface. This does not impact the routing capability of the CDN.

• CSCdu42467
  
  

The clock on a device is not updated if the Network Time Protocol (NTP) server is inaccessible while the device is booting. To avoid this, you should wait until the NTP server is available and then reboot the device.

• CSCdu44384
  
  

When a RealServer license expires on a Content Engine, an error message indicating the expiration is not logged. An expired RealServer license prevents the Content Engine from serving content through the RealServer.

• CSCdu45008
  
  

If you delete a supernode from the CDM and then create a new supernode that is identical to the deleted one, all Content Engines associated with the re-created supernode must be rebooted to function properly. If they are not rebooted, they fail to serve content.

• CSCdu50308
  
  

In the command-line interface, if you run setup remotely through Secure Shell (SSH) using the Dynamic Host Configuration Protocol (DHCP) address, you are disconnected from the device when netsetup is completed. You can reconnect to the device by using the IP address you specified during setup.

• CSCdu53388
  
  

In Netscape, if you try to assign Content Engines to a hosted domain and fail to select a root location, the user interface does not display a warning message; it accepts the change when you click the Save button. If you do this using Internet Explorer, the user interface tells you that you must specify a root location.

• CSCdu56255
  
  

The system allows you to surpass the limit on the number of content items you can assign to a Content Engine (CE). When you have reached the limit, the CE warns you that you have reached the limit but allows you to assign further items. By default, the limit is set to 500,000 items, but the CE-7320 can support up to 1 million.

• CSCdu57706
  
  

The dnslookup command in the command-line interface does not function as documented; it fails to resolve the host name of an IP address that you enter.

• CSCdu57718
  
  

If you enter the show logs command-line interface command during a period of high end user activity on the system, the log output gets stuck on the SQuID log (the SQuID log records HTTP requests for content). To break out of this command, press Ctrl-C. To view selected logs, use the view path_of_log_file privileged level EXEC command. The following log files are available:

• /cisco/merlot/state/merlot.log
  
  
• /cisco/merlot/state/apache/log/*_log
  
  
• /cisco/merlot/state/squid/logs/*.log
  
  
• /cisco/merlot/state/sysout/*.log
  
  

• CSCdu60211
  
  

If you have assigned a Content Engine (CE) to a location, you must manually restart the CE if you later change it to a different location through the Content Engine Details page. Otherwise, your routing performance will not be optimal.

• CSCdu64147
  
  

While you modify a supernode cluster, an extra row is added to the Content Engine table.

• CSCdu66216
  
  

On the Software Update page, the file at the top of the list of upgrade metafiles is selected by default. When you choose a different file, this choice is not perpetuated to all the other device tabs. Under the other device tabs, the file at the top of the list remains as the default. You must choose the upgrade file for each device individually.

• CSCdu69371
  
  

Content Engines fetch the manifest file from the origin server instead of the hosted domain leader Content Engine. This is by design.

• CSCdu70671
  
  

When you attempt to update a CDN password, the ! icon appears next to the wrong field after an incorrect value is entered into the Old Password field.

• CSCdu71747
  
  

Password verification is limited to the first eight characters of the password.

• CSCdv44831
  
  

If you use a browser that does not have cookies or JavaScript enabled, you receive a session timeout message. For the user interface to function, you must have both cookies and JavaScript enabled in your browser options.

• CSCdv47796
  
  

Do not downgrade a Content Distribution Manager (CDM) from the user interface; doing so may corrupt your database's table structure. Instead, downgrade your CDM through the command-line interface using the upgrade command. For more information on using the command-line interface, refer to the Cisco Internet CDN Software Command Reference for Version 2.1.

• CSCdv52128
  
  

In Internet Explorer, next-click failover does not work for Windows Media Technologies (WMT) 7.1 content requested through HTTP. If you send HTTP requests through an Internet Explorer browser after a Content Engine failure behind a supernode, you need to take one of the following actions:

• Go back to the original HTTP URL and click it again.
  
  
• Do a refresh for any URL you enter in the browser location field.
  
  
• Publish the HTTP URL as a web link.
  
  

If you are using Internet Explorer 6.0, you can also get next-click failover by closing the WMT player, entering the HTTP URL directly into the browser location field, and then pressing Enter.

• CSCdv62694
  
  

The peekable interface is disabled by default on Content Engines and Content Routers. If you do not enable the peekable interface:

• You receive a "Page not found" error when clicking on a Content Engine on the
  Hosted Domains > Replication Status page.
  
  
• You cannot access the Java Monitor for RealServer.
  
  
• You cannot view the Tools > System Tools > Simple Peek page for the device, which you use to enable or disable Telnet and debugging.
  
  
• You cannot view manifest log files for hosted domains.
  
  

To enable the peekable interface, enter the node peekable command in the command-line interface. For more information, refer to the Cisco Internet CDN Software Command Reference for Version 2.1.

• CSCdv62704
  
  

In a single software upgrade transaction, you can upgrade only the devices on one page. When you choose the check-all check box on the Upgrade Software page, all of the devices on that web page are selected. If you then go to the next page and choose all the devices, the devices on the first page are deselected.

• CSCdv64154
  
  

When you are running setup on a Content Distribution Manager (CDM), you are prompted to enter the Oracle database username that you specified during Oracle configuration. You should not use the username of the database account to which you assigned administrator privileges. Doing so causes problems during upgrades and downgrades. If you only created one user account during database setup and gave it administrator privileges, you have to run the setup command to create a second user without administrator privileges. Once you have done so, you can rerun dbsetup on the CDM.

• CSCdv65761
  
  

If you have Content Engines with Version 2.0.1 and a Content Router that never rebooted after Version 2.0.1 was installed on it, you must reboot the Content Router before upgrading it to version 2.1. If you do not reboot prior to upgrading, Content Engines running Version 2.0.1 will lose contact with the Content Router until they are rebooted.

• CSCdv70049
  
  

The no command that appears in the command-line interface configuration menu is nonfunctional.

• CSCdv80269
  
  

Your Content Engine may stall during a Version 2.0.1 to Version 2.1 software upgrade. If this happens, you need to reboot the Content Engine and repeat the upgrade procedure.

• CSCdv84379
  
  

When you change the status of a Content Distribution Manager from primary to standby, the change is not recorded in the system log.

• CSCdv88053
  
  

If you enter a video on demand (VOD) quota setting on a Content Engine by using the node diskadmin command-line interface command, the change is not registered. Changes made through the Content Distribution Manager (CDM) user interface are registered. This may cause a discrepancy between the VOD quota value that the CDM user interface displays and the value that the command-line interface show disk command displays.

• CSCdw14298
  
  

You are unable to use the command-line interface (CLI) following a CLI downgrade. Following reboot of the device, the CLI session disconnects and if you attempt to reestablish a CLI connection, you see an error message similar to the following:

Last login: Wed Dec  5 19:39:09 2001 from 
dhcp-161-44-174-117.cisco.com/cisco/merlot/state/dump/home/script-4364: No such file 
or directory
Command terminated on signal 15."
 

Workaround:

To downgrade from 2.1.0.0.27 to 2.0.1.0.6:

• Login in to the box as "root" using the bash shell.
  
  
• Type your device password.
  
  
• At the :: prompt type the 867...password.
  
  
• mkdir -p /cisco/merlot/state/dump/home
  
  
• exit out of bash.
  
  

• CSCdw16838
  
  

It is not possible to disable the peekable system configuration property on the Content Distribution Manager, regardless of the setting of the enablePeekable property. This is because both peekable and the Content Distribution Manager user interface use the same port so if you disable peekable, the Content Distribution Manager user interface is also disabled.

• CSCdw28253
  
  

SMIL files do not play reliably if distributed licensing is enabled on RealServer. When the enduser requests a SMIL file, the RealPlayer stalls and there is an indefinite delay in playback.

Workaround:

Disable distributed licensing until a fix is available.

• CSCdw36766
  
  

You can only access one Content Distribution Manager user interface from one host. Multiple CDNs cannot be accessed at the same time by the same client.

• CSCdw41627
  
  

When playing Windows Media Technologies (WMT) files through a Netscape browser that has not had a start page defined, only the first content file for a hosted domain plays per Netscape session.

Workaround:

Select the Home Page option in Netscape's Preferences dialog and provide a unique URL for that page in the field provided. Do not choose either the Blank Page or Last page visited options.

• CSCdw54426
  
  

Content Distribution Manager User Interface upgrade fails, with the following error, then corrects:

Database upgrade failed. Use cli upgrade --rollback to repair. [runmode = 1] 

Workaround:

• Log on to the Content Distribution Manager Cisco Command Line Interface.
  
  
• Execute the upgrade display command to verify the error. You should see the error message listed above.
  
  
• Execute the upgrade rollback command.
  
  
• Execute the upgrade display command a second time. The error message should have been removed.
  
  
• Execute the upgrade backup command.
  
  
• Execute the upgrade display command a third time. You should see a record showing successful backup of the database.
  
  
• Execute the upgrade restore command and choose the version you wish to restore.
  
  
• Execute the upgrade display command a fourth time. You should see one restore and one upgrade record listed.
  
  
• Execute the node stop command to shut down the Content Distribution Manager.
  
  
• Execute the node start command to re-start the Content Distribution Manager with the correct database version loaded.
  
  

• CSCdw61220
  
  

Need procedure to set date and time on Internet CDN node via the bash shell.

• CSCdw64452
  
  

After a software upgrade, Windows Media Services settings are not retained for hosted domains.

Workaround:

• From the Content Distribution Manager, select Tools > Windows Media Services Configuration.
  
  
• Click the Read and Accept Windows Media Server License Agreement option, then click Save. The Windows Media License Agreement appears in the browser window.
  
  
• Read it and click the Accept button that appears at the bottom of the Agreement.
  
  
• Click Yes in the dialog appears. You will be returned to the Windows Media Services Configuration page. Windows Media Services will now be re-enabled on all hosted domains on which it was enabled prior to the software upgrade.
  
  

• CSCdw64794
  
  

WMA file not playing using mmsu protocol only.

Workaround:

• Open your Windows Media Player V.7.
  
  
• Click the Tools menu then select Options. The Options dialog appears.
  
  
• Click the Network tab.
  
  
• In the area marked Protocols, uncheck the UDP and verify that the TCP option is checked.
  
  
• The mmst protocol will be used for all files with a mms* URL.
  
  

• CSCdw65140
  
  

Running dbsetup on a Content Engine destroys the device's setup.cfg file.

Workaround: Do not attempt to run dbsetup on Content Engines.

• CSCsp00588
  
  

If a Content Engine or Content Router is shut down, the event may not be logged in the System Event Log on the Content Distribution Manager.

• CSCsp01022
  
  

There is no visual indication whether or not passwords have been overridden on a Content Delivery Network device.

• CSCsp01245
  
  

A "Page not Found" error message is displayed in the Add Update File window when the Content Distribution Manager cannot reach the device hosting the upgrade file.

• CSCsp01249
  
  

The web browser times out, displaying a "Page Not Found" error when the Content Distribution Manager attempts to locate upgrade files on an unreachable server.

• CSCsp01372
  
  

It is possible to add the same upgrade files multiple times to the same Content Distribution Manager. This does not impact the upgrade in any way.

Resolved Caveats

The following caveats are fixed (resolved) in Cisco Internet CDN Software Version 2.1.1. Caveats are listed according to their tracking number.

• CSCdu03195
  
  

The RealServer Java Monitor is not fully implemented.

• CSCdu16048
  
  

Deployment of a standby Content Distribution Manager in the event of failover should be supported to allow for geographic diversity.

• CSCdu21104
  
  

During setup, it should be possible to specify a VLAN name for a Content Services Switch.

• CSCdu23464
  
  

The distributed licensing for RealServer feature does not work for live streams.

• CSCdu24818
  
  

On the Content Router details page, under the Management Information heading, the Content Router IP address appears where you should see the Content Router host name. This resolves itself after some time.

• CSCdu26028
  
  

The graphical user interface should display an error if the file named in the Manifest field does not exist.

• CSCdu32063
  
  

Ability to configure the maximum number of manifest items allowed.

• CSCdu34339
  
  

The status message on the Replication Progress page identifies live content files as "live items" but pre-positioned content files as "items."

• CSCdu37494
  
  

Manifest errors that appear in the logs are not displayed on the user interface.

• CSCdu39865
  
  

By default, there is no inactivity timeout associated with the CDM user interface, which users can set through the Tools > System Configuration page. There is, however, a cdm.session.timeout property that can be set as a user interface logout interval. For instructions on how to modify this property, refer to the Cisco Internet CDN Software User Guide for version 2.1, Chapter 4, in the section "Modifying the System Timeout Value."

• CSCdu45677
  
  

The sorting button on the user interface first sorts uppercase items and then lowercase items.

• CSCdu48305
  
  

There should be multiple levels of user access.

• CSCdu49531
  
  

If you connect to a Content Engine with only the Gigabit Ethernet interface connected, the device fails to register with the Content Distribution Manager.

• CSCdu52703
  
  

It should be possible to distribute configuration scripts from the Content Distribution Manager to the Content Services Switch through the user interface.

• CSCdu53202
  
  

There should be a command-line interface command for creating optional static routes for a Content Router.

• CSCdu56623
  
  

The node restart command in the command-line interface does not work.

• CSCdu57678
  
  

The contentmask command in the configuration menu of the command-line interface is not implemented.

• CSCdu58508
  
  

The node update command in the command-line interface does not work.

• CSCdu59102
  
  

The prompt that is visible when you are logged in to a Content Services Switch (CSS) should be identical to the name of the supernode that the CSS is a member of.

• CSCdu62385
  
  

The system allows you to add Content Engines with insufficient free disk space to hosted domains. This results in pre-positioned content being dropped from the Content Engine.

• CSCdu67146
  
  

When a Content Engine that is the last node in the root location changes its location, the assigned hosted domains using that root location must have their root location changed as well.

• CSCdu70447
  
  

A supernode cannot come on line if the Content Distribution Manager is off line.

• CSCdu71733
  
  

Server stop notifications are not issued to the SNMP manager if you run node stop, exit, and reboot commands on a device.

• CSCdu73919
  
  

The configuration script for each device should enable users to use their company name as a signature on certificates.

• CSCdu74015
  
  

If you delete the location leader Content Engine and add it back, two Content Engines will take on the role of location leader.

• CSCdu74880
  
  

Access logs for Content Engines that are behind a Content Services Switch need to be labeled with the primary IP address, not the hidden IP address. This is because the same hidden IP address may be used on different supernodes.

• CSCdu76981
  
  

SNMP times out while scanning ghost drives on Content Engine-590 devices.

• CSCdu80912
  
  

When configuring Content Services Switches in a redundant configuration, administrators receive the following message: "The script is in use by another session."

• CSCdu89261
  
  

Content Engines report to Content Routers and their supernode leader while shutting down. This increases the period when Content Routers route requests to Content Engines that cannot serve them.

• CSCdu89276
  
  

Content Engines and Content Routers report being on line even when they fail to serve content.

• CSCdv01319
  
  

System time is not displayed on all pages of the user interface.

• CSCdv02380
  
  

The IP address or location of the origin server should not be displayed in the error message you see when the origin server goes down while trying to retrieve content.

• CSCdv02431
  
  

The gateway IP address that you assign to a Content Engine must be reverse-resolvable.

• CSCdv07620
  
  

Generation of SNMP traps due to changes in run-mode level is not implemented.

• CSCdv12657
  
  

Running the command-line interface command node stop may prevent the system from restarting.

• CSCdv13330
  
  

Running the node status command after your Content Distribution Manager (CDM) fails to come online after a reboot may instruct you to perform a database rollback. Before doing so, look at the CDM merlot log for the following message:

DBupgrade records contain incomplete operation ... run rollback.

If you see this message, running the upgrade rollback in the command-line interface will correct the booting problem.

If you do not see this message, the Content Distribution Manager may be experiencing a connectivity problem with the database. Remove the DBUPGRADE-FAILED file from the merlot-state directory and restart the Cisco Internet CDN Software by entering the node restart command in the command-line interface.

• CSCdv14297
  
  

The Windows Media Technologies (WMT) server continues running on Content Engines even when Windows Media Server (WMS) is deactivated on the Tools > WMS Configuration page.

• CSCdv14346
  
  

Origin Server failover does not work.

• CSCdv15182
  
  

Content Engine statistics are not displayed correctly on a hosted-domain-by-hosted-domain basis.

• CSCdv15190
  
  

To restore the default CLI or HTTP passwords on Cisco Internet CDN devices:

• Reboot the device.
  
  
• At the LILO prompt, enter:
  
  

linux single

You can now log in to the device using the default passwords. The passwords will remain reset until a new password is set using the Content Distribution Manager user interface.

• CSCdv17970
  
  

Scroll bars are missing on the Routing Diagnostics > View Supernodes page.

• CSCdv19565
  
  

The user interface does not always give a warning or require confirmation when an operation will result in a reboot or restart.

• CSCdv24460
  
  

Telnet ports respond to probes even when they are disabled.

• CSCdv27477
  
  

If you erroneously enter "http://" before the origin server name on the Hosted Domain Details page and click Save, the system rejects the whole transaction and requires you to start over. You also lose all information that you may have entered in the fields.

• CSCdv28773
  
  

Sometimes you do not receive server stop traps because the SNMP agent shuts down early.

• CSCdv30542
  
  

The system does not keep track of used WMT licenses or require acknowledgment of an end user license agreement.

• CSCdv30840
  
  

The node status command-line interface command does not give you information about the WMT server, as it does for the QuickTime Server and RealServer.

• CSCdv31624
  
  

Content Engine performance drops briefly on an hourly basis because of usage log processing.

• CSCdv33683
  
  

For RAM files, content providers must use a CDN tag in the manifest file. The syntax must use the cdn-http tag, for example: http://hosted_domain_name/cdn-http/path_to_file.ram.

• CSCdv33958
  
  

Scroll bars are missing on the Content Router peek page.

• CSCdv34752
  
  

You cannot log in to the command-line interface as admin after doing a manual upgrade. Instead, you have to log in to the bash shell and reboot the device.

• CSCdv34827
  
  

The DNS statistics on the Content Engine Statistics page always show a value of 0. This is incorrect.

• CSCdv35138
  
  

If the wildcard is removed from a manifest file and the file is fetched again, RealPlayer returns an error message stating that either the file cannot be found or "A General Error has occurred" when trying to access the live stream.

• CSCdv38305
  
  

If you are upgrading from Version 2.0.1 to 2.1, subsequent to running setup on a device, you should immediately change the device password through the Content Distribution Manager user interface. If you do not change it, the security of your system is compromised because somebody can access the device using default information. The password that you set during setup only protects your device temporarily following reboot.

• CSCdv49216
  
  

When you create or modify a routed domain or Secure Key Content Authentication (SKCA) or If-Modified-Since (IMS) settings, the newly created information may take up to 10 minutes to propagate to the Content Engines.

• CSCdv50154
  
  

Upgrade scripts do not report that the upgrade file is invalid; they merely report "Script missing inside distribution."

• CSCdv50195
  
  

If you reset your Content Distribution Manager (CDM) password to the default using the reset-password script, you should change it immediately afterward through the CDM user interface.

• CSCdv58270
  
  

A checkbox is missing on the Simple Peek Page when the UPG Metafile is not present.

• CSCdv62752
  
  

Cancel button disappears from CDM interface when browser window is sized down.

• CSCdv66627
  
  

The Netscape browser doesn't support mmst URLs.Windows Media Player 6.4 doesn't work with http URLs in Merlot 2.1, therefore Windows Media files that are played on the Netscape browser using Windows Media Player Version 6.4 will not load.

Workaround:

Include the non-ASX files in an ASX file, then deploy the ASX file. For example, if the user has a foo.asf, and a hosted domain: www.foo.cisco.com, then in order to use Netscape and Windows Media Player 6.4, you would create an ASX file, foo.asx, which is something like:

 <asx version = "3.0">
 <entry>
 <ref href="mms://www.foo.cisco.com/www.foo.cisco.com/cdn-wmt/cdnfoo.asf"/>
 </entry>
 </asx>

Note: cdnfoo.asf is the cdn url for foo.asf. You would preposition both foo.asf and foo.asx on the hosted domain, then use the following URL to link to them from your website:

 http://www.foo.cisco.com/cdn-http/foo.asx