|
|
February 15, 2002
These release notes contain information about the Cisco Internet Content Delivery Network (CDN) Software, Version 2.1.1. It describes the following topics:
The Cisco Internet CDN Software Version 2.1.1 contains the following modifications since the release of Version 2.1:
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 Internet CDN Software Version 2.1.1 operates with the following Cisco hardware:
Refer to the Cisco documentation that came with each device for detailed, device-specific instructions on handling, installing, and configuring your Cisco CDN hardware.
For Version 2.1.1, the following upgrade sequences for the Cisco Internet CDN Software are supported:
The following downgrade sequences are supported:
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.
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."
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."
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.
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.
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.
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:
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.
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.
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:
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/cgi-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
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/cgi-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/cgi-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
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.
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:
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:
For detailed information and technical documentation on accessing the Cisco Internet CDN database views, please contact your Cisco Account Representative.
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.
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.)
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.
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:
See the sections that follow for detailed instructions on each of these steps.
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.
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.
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.
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.
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.
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.
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:
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>
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.
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.
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:
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.
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:
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.
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.
This section contains information that you can use to automate the creation of manifest files for your website:
Two sample scripts are provided to you:
These scripts shipped with your CDN software and can serve as the basis for your own automation scripts.
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.
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.
This section contains information on the following topics:
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
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
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
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.
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.
| Keyword | Description | Syntax |
|---|---|---|
--start | Names the location (URL) of the origin server that will be analyzed. | --start=www.cisco.com
|
--allow (optional) | Names a location other than that specified using the start keyword that will be accepted when it is found in URLs. | --allow=forums.cisco.com
|
--db | Names the database file in which content URLs from the origin server and any allowed locations will be placed. | --db=ciscocontent.db
|
--depth (optional) | Causes the spider script to stop after following links a specified number of levels deep on the origin server. | --depth=6
|
--file (optional) | Causes the spider script to read its commands from a specified rules file, one line at a time. | --file=cisco-rules.cfg
|
--hd (optional) | Identifies a hosted domain on your CDN as the hosted domain for the content being searched by the spider script. Used with the --map keyword for mapping content from the CDN back to the origin server. | --hd=www.hosted.cisco.com
|
--limit (optional) | Causes the spider script to stop after retrieving a specified number of pages from the origin server. The default is 100. Specifying 0 sets no limit for the number of pages retrieved. | --limit 1000
|
--map (optional) | Causes the spider script to substitute the second URL prefix (appearing after the second =) for the first in any URLs from the origin server, or substitute the first prefix for the second when running the spider script a second time on origin server content. | --map=http://www.cisco.com/ |
--prefix (optional) | Specifies a URL prefix that will be accepted by the spider script when it is encountered. | --prefix=http://www.cisco.com/partners/CDN/ |
--reject (optional) | Names a location that will be rejected when it is found in URLs. | --reject=cgi-bin
|
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.
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.
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:
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://*)'
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.
| Keyword | Description | Syntax |
|---|---|---|
--file | Causes the manifest script to read its commands from a specified rules file, one line at a time. | --file=ciscocontent.cfg
|
--live | Marks content URLs in the database file that match the terms of the keyword comparison as live (type="live") content in the manifest file. | --live='match(rtsp://*)'
|
--prepos | Marks content URLs in the database file that match the terms of the keyword comparison as pre-positioned content (type='prepos') in the manifest file. | --prepos='type(image/jpg)
and size > 1000k'
|
--set | Sets the specified attribute to the value provided for all content items with URLs in the database file that match the keyword comparison. | --set='ttl=10000 :
match(*/urgent/*)'
|
--playservertable | Adds the playserver table in the specified file to the manifest file. Playserver tables map MIME content types and filename extensions to specific server types to use (for example, "real" or "wmt") for the content in a specific hosted domain. | --playservertable=info.txt
|
--map | Causes the manifest script to substitute the second URL prefix (appearing after the second =) for the first in any URLs from the origin server. | --map=http://www.cisco.com/ |
--db | Names the database file in which content URLs from the origin server and any allowed locations are located. This file provides the data that the manifest script analyzes. | --db=ciscocontent.db |
--xml | Names the manifest file that is generated by the manifest script. | --xml=ciscomanifest.xml
|
match | Comparison keyword that locates text in content URLs that are identical to a value that is provided. | --prepos='match
(http://forums.cisco.com/*)'
|
size | Comparison keyword that identifies content named in the database file according to the specified file size parameter (in kilobytes). | --prepos='size >= 1000k'
|
time | Comparison keyword that identifies content named in the database file according to the time since the content was last modified (in hours). | --prepos= 'time < 72 hours'
|
type | Comparison keyword that identifies content named in the database file according to its MIME type (text, application, image, and so on). | --prepos='type(image/gif)' |
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.
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
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:
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.
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.
| Validator File Name | Purpose |
|---|---|
xerces.jar | Syntax parser |
manval.zip | Standalone manifest validator |
CdnManifest.dtd | Document type definitions for the CDN manifest file |
PlayServerTable.dtd | Document type definitions for CDN PlayServerTables, used to define media servers (RealMedia, Windows Media) for the CDN |
validate | Shell script used to run the validator |
validate.bat | Batch file to run the 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:
When running the manifest file validator, you are required to input the following information:
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:
validate -f [<file> | -u <url>] -o <output> [-s <seconds>]
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.
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:
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 src is not defined.
In the preceding error message:
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 "src" is required and must be specified for element type
"item".
start item
item src: null
ERROR: japan.xml:13:Skip item because src 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.
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:
The total number of warnings encountered in the manifest file is provided at the end of the validator output file.
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 describe unexpected behavior in Cisco Internet CDN Software.
This section describes the caveats--both resolved and unresolved--that are associated with Version 2.1.1 of Cisco Internet CDN Software.
The following caveats are open (unresolved). Unresolved caveats are listed according to their tracking number.
epro100: Device or resource busy rmmod: module acenic is not loaded
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."
Database upgrade failed. Use cli upgrade --rollback to repair. [runmode = 1]
The following caveats are fixed (resolved) in Cisco Internet CDN Software Version 2.1.1. Caveats are listed according to their tracking number.
DBupgrade records contain incomplete operation ... run rollback.
linux single
/cisco/merlot/etc/reset-passwd
<asx version = "3.0">
<entry>
<ref href="mms://www.foo.cisco.com/www.foo.cisco.com/cdn-wmt/cdnfoo.asf"/>
</entry>
</asx>
http://www.foo.cisco.com/cdn-http/foo.asx
|
Note The software does not authenticate origin servers. That is, there is no protection against server impersonation attack aimed at stealing the manifest file username and password. |
This section contains information that was not covered in the following documents:
The following section describes information that has been added to the Cisco Internet CDN Software User Guide since the release of Version 2.1.
In Chapter 4, "Maintaining Cisco Internet CDN Software," Table 4-1 in the section on "Modifying Dynamic Routing Properties" has been updated to include the Consider Load for Routing option.
When enabled, this option causes SuperNodes and standalone Content Engines to report their load to the Content Routers that for use in making routing decisions. Load is based on the response time of HTTP requests between SuperNode leader-Content Engines and SuperNode cluster addresses.
The Content Router then assigns a lower priority to overloaded SuperNodes or standalone Content Engines and a higher priority to unloaded nodes when routing content requests.
The following commands either have been added to the command-line interface, or their syntax has been modified to include options that were not available in earlier versions of the software:
To control or monitor the status of Cisco Internet CDN devices, use the node command in privileged EXEC mode.
The syntax of the node command has been extended to include the following two options:
node {setprop [enableTelnet {1 | 0} | enablePeekable {1 | 0}] | secondnic}
Syntax Description
setprop Sets a system property on a CDN device. enableTelnet Enables or disables the Telnet system property. 1 Enables the system property. 0 Disables the system property. enablePeekable Enables or disables the peekable system property. Enter 1 or 0 to enable or disable, respectively. secondnic Activates the second network interface card (NIC) which can be connected to your Oracle database server behind a firewall for added security.
Defaults
The enableTelnet and enablePeekable keywords are disabled by default.
Command Modes
Privileged EXEC
Usage Guidelines
After you successfully complete an enableTelnet, enablePeekable, or secondnic operation, you must reboot the device by entering the reboot command. Unless you reboot the device, the new settings will not take effect.
Before entering the node secondnic command, you must stop the Content Distribution Manager by entering the node stop command.
Examples
Host> enable
Host# node setprop enablePeekable 1
Host> enable
Host# node secondnic
Configuring eth1.
Enter the Secondary IP DNS Name: secondnic.cisco.com
Warning: Unable to resolve secondnic.cisco.com to an IP address.
Would you like to change this setting? [y/n]: n
Enter the Secondary IP Address: 192.168.0.0
WARNING
-------
secondnic.cisco.com does not currently resolve to 192.168.0.0
DNS must be setup to resolve this name before
the system will operate correctly.
Enter the Secondary IP Netmask: 255.255.255.0
Enable Secondary Nic now? [y/n]: y
Network validation succeeded.
Related Commands
enable
To add or remove RealServer licences or plug-ins from a Content Engine, use the real command in privileged EXEC mode.
real {license | rsmcs}
Syntax Description
license Adds or removes RealServer licenses. rsmcs Deploys the RealServer Media Commerce Suite (RSMCS) plug-in.
Defaults
The default RealServer license on a Content Engine allows ten simultaneous users and no live streams. If distributed licensing is enabled, then these features are controlled by the license server.
Command Modes
User and privileged EXEC
Usage Guidelines
The RealServer Media Commerce Suite (RSMCS) plug-in allows Content Engines to decrypt the encrypted content received from content providers so that the content can be streamed to endusers.
Before you deploy the RSMCS plug-in, you must download the plug-in to your Content Engine's cisco/merlot/state directory by using the ftp or scp command.
Once the plugin is on the device, you can deploy it by entering the real rsmcs command. When the deployment is confirmed, enter the node restart command. This will briefly disrupt service from the Content Engine.
The LICENSE plugin allows you to add or remove a RealServer license file from your CDN device. Before you add the license using the LICENSE plugin, you must download it to your Content Engine's cisco/merlot/state directory by using the ftp scp command. Then deploy it by entering the real license command.
When the deployment is confirmed, enter the node restart command. This will briefly disrupt service from the Content Engine.
Examples
Host> enable
Host# real license
License Administration
1. Add License file
2. Remove License file
3. exit
Select [1-3]:1
Host> enable
Host# real rsmcs
RealSystem Media Commerce Suite (RSMCS) Plugin Administration
1. Add RSMCS license
2. Remove RSMCS license
3. exit
Select [1-3]:1
Related Commands
To securely copy files from a CDN device you are logged on to, to another CDN device, use the scp command in user EXEC mode with the following syntax:
scp {[source_path] merlot@[target_IP_address]:/[target_path]}To securely copy files to a CDN device you are logged on to, from another CDN device, use the scp command in user EXEC mode with the following syntax:
scp {merlot@[source_IP_address]:/[source_path][target_path]}
Syntax Description
merlot BASH account name. You must use this account name in order to execute the scp command. source_path Relative directory path and file name on the source CDN device of the file that is being transferred. target_path Relative directory path on the target CDN device to which the file is being copied. source_IP_address or target_IP_address IP address of the source or target CDN device.
Defaults
No default behavior or values
Command Modes
User EXEC
Usage Guidelines
After logging in to the CLI for either the device from which or to which you will be copying, enter the scp command, following the syntax description provided above, then do the following:
Refer to Chapter 3: Working with the Cisco Internet CDN Software" in the Cisco Internet CDN Software User Guide for information on setting the root password for your CDN devices.
Examples
Host> scp /cisco/merlot/state/mycdmfile.log merlot@10.1.2.3:/cisco/merlot/state/dump/home
Host> scp merlot@10.0.0.0:/cisco/merlot/state/mycdmfile.log /cisco/merlot/state/dump/home
Related Commands
ftp
To manage the Oracle database holding your CDN data, use the utilities accessible from the storeutil command.
storeutil {dbcheck [username password IP_address servicename]| invalidate | purgesyslog [days {number}| count {number} ]| relocate | report | restore | validate}
Syntax Description
dbcheck Tests whether or not the database connection is active. username Database administrator account name password Database administrator account password IP_address Database host IP address servicename Name of the CDN service invalidate Marks database records invalid. purgesyslog Clears syslog records up to a point specified either by a number of days or a record count. days Specifies that the syslog should be purged from the beginning of the log to a point some specified number of days before the end of the log. number The number of days before the end of the log for which syslog messages should not be purged. count Specifies that the syslog should be purged from the beginning of the log to a point some specified number of records before the final record in the log. number The number of records before the end of the log that should not be purged. relocate Launches a simple script that allows you to changes the IP address of the CDN Oracle database. report Saves a list of objects that have been marked invalid in the merlot/state/validation.log file. restore Launches a simple script that allows you to restore invalidated database records. validate Validates the current database store, outputting results to the screen.
Defaults
No default behavior or values
Command Modes
User and privileged EXEC
Usage Guidelines
You must stop the Content Distribution Manager before running the storeutil command. Enter node stop to stop the Content Distribution Manager.
The storeutil command is a privileged level command, so you must enter enable before entering storeutil.
The storeutil set of commands lets you locate and debug invalid database records in which there are references from a store object to a nonexistent store object. The Content Distribution Manager may fail to start if there are invalid database references. If this happens, the user interface is not available and the Merlot log registers an error.
To send a test to your Oracle database to determine whether or not the database connection is active, use the storeutil dbcheck command. When issuing the command, you must provide the following connection information for the database in the command line:
To obtain a list of invalid references, use the storeutil validate command. The list appears in the merlot/state/validation.log file. To prevent invalid references from being loaded, use the storeutil invalidate command to mark the invalid references for exclusion. Run the validate and invalidate commands as many times as necessary to receive a "passed" message from the system.
To point the CDN to its Oracle database at a new IP address, use the storeutil relocate command. This will launch a script that allows you to input the new IP address for the database as well as the following information:
To save a list of objects that have been marked invalid in the merlot/state/validation.log file, use the storeutil report command.
If you have corrected the invalid references through database intervention and want to validate them, use the storeutil restore command.
To free up some of the space in the database that is allocated to system messages, you need to periodically clear the system messages stored in it. To do this, use the storeutil purgesyslog command. When issuing this command, you will be prompted to enter
Examples
host# storeutil validate
Passed Validation.
host# storeutil relocate
Enter Database hostname [10.89.5.180]: 192.168.0.2
Enter Database username [cdmuser]]: cdmuser
Enter Database password [cdmpass]: cdmpass
Enter Database Service Name [service]: service
Operation Successful.
host# storeutil report
controller.storeAdmin[18225]: 1 ClusterConfig.RoutedDomains references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.SkcaConfigId references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.ImsConfigId references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.CmdPurgeRdId references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.RootLocation references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.CustomerId references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.DistTreeId references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
controller.storeAdmin[18225]: 4 RoutedDomain.ClusterConfigs references were found to be
invalid. [Tue Oct 30 20:42:08 GMT 2001]
This section documents corrections to the following documents:
Step 1 Boot the device.
Step 2 Log in as admin with the password default.
Step 3 At the prompt, enter enable. Press Enter.
Step 4 At the prompt, enter config. Press Enter.
Step 5 At the config prompt, enter setup. Press Enter.
Continue with Step 4 in the appropriate section of the Cisco Internet CDN Software Configuration Guide for version 2.1.
SQL> create tablespace cdn DATAFILE 'datafile path on Oracle Server' SIZE 250M REUSE;
SQL> create tablespace cdntemp DATAFILE 'datafile path on Oracle Server' SIZE 250M
REUSE;
Additional data files can be associated with the tablespace using the following command.
SQL> alter tablespace cdn add DATAFILE 'datafile path on Oracle Server' SIZE 250M
REUSE;
Host# dnslookup 172.16.0.0
official hostname: 172.16.0
address: 172.16.0
Host# dnslookup 172.16.0.0
official hostname: cisco.com
address: 172.16.0.0
Your Cisco Internet CDN product shipped with a minimal set of printed documentation, as well as a Documentation CD. The printed documentation provides enough information for you to install and initially configure your product. The CD contains additional product documentation (user guides, configuration manuals, and so forth), which you can access and print out.
The following is a list of the documentation that shipped with your product (you can access the URLs listed for each document on the Documentation CD and at www.cisco.com on the World Wide Web):
The following is a list of related documentation for your product. These documents were not shipped with your product, but you can access them and order them by using the URLs listed below:
The following sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click Leave Feedback at the bottom of the Cisco Documentation home page. After you complete the form, print it out and fax it to Cisco at 408 527-0730.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered user, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Product Documentation Set" and "Related Product Documentation" sections.
This product contains copyrighted programs and license agreements that are used with permission and are the property of the following respective owners.
TomCat Copyright © 1999 The Apache Software Foundation. All rights reserved.
OpenSSH Copyright © 1998 CORE SDI S.A., Buenos Aires, Argentina. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that this copyright notice is retained.
Jama Copyright Notice: This software is a cooperative product of The MathWorks and the National Institute of Standards and Technology (NIST) which has been released to the public domain. Neither The MathWorks nor NIST assumes any responsibility whatsoever for its use by other parties, and makes no guarantees, expressed or implied, about its quality, reliability, or any other characteristic.
ModSSL Copyright © 1998-2001 Ralf S. Engelschall. All rights reserved.
This product includes software developed by Ralf S. Engelschall <rse@engelschall.com> for use in the mod_ssl project (http://www.modssl.org/).
THIS SOFTWARE IS PROVIDED BY RALF S. ENGELSCHALL \Q\QAS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL RALF S. ENGELSCHALL OR HIS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Apache-SSL Server, OpenSSL Copyright © 1995,1996,1997 Ben Laurie. All rights reserved.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
THIS SOFTWARE IS PROVIDED BY BEN LAURIE \Q\QAS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL BEN LAURIE OR HIS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
Java JRE
Software is confidential and copyrighted. Title to Software and all associated intellectual property rights is retained by Sun and/or its licensors. Except as specifically authorized in any Supplemental License Terms, you may not make copies of Software, other than a single copy of Software for archival purposes. Unless enforcement is prohibited by applicable law, you may not modify, decompile, reverse engineer Software. Software is not designed or licensed for use in on-line control of aircraft, air traffic, aircraft navigation or aircraft communications; or in the design, construction, operation or maintenance of any nuclear facility. You warrant that you will not use Software for these purposes. No right, title or interest in or to any trademark, service mark, logo or trade name of Sun or its licensors is granted under this Agreement.
UNLESS SPECIFIED IN THIS AGREEMENT, ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT THESE DISCLAIMERS ARE HELD TO BE LEGALLY INVALID.
GNU GENERAL PUBLIC LICENSE Version 2, June 1991
Copyright (C) 1989, 1991 Free Software Foundation, Inc. 59 Temple Place, Suite 330, Boston, MA 02111-1307 USA.
NO WARRANTY
BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, FrameShare, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, ScriptBuilder, ScriptShare, SMARTnet, TransPath, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and Discover All That's Possible are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, GigaStack, IOS, IP/TV, LightStream, MICA, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0110R)
Copyright © 2001, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Oct 1 03:57:05 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.