|
|
November 19, 2001
 |
Note The most current documentation for this product is available on Cisco.com at http://www.cisco.com/univercd/cc/td/doc/product/webscale/content/cdnsp/index.htm. The online documents may contain updates and modifications after the hardcopy documents were printed. |
This release note contains information about the Cisco Internet Content Delivery Network (CDN) Software version 2.1. It describes the following topics:
The following features have been added to the Cisco Internet CDN Software version 2.1 since the release of Version 2.0:
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.
The Cisco Internet CDN Software Version 2.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, 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".
The Cisco Internet CDN Software Version 2.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 Content Engines ship with the Darwin Streaming Server, the RealNetworks RealServer, 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 the Cisco Internet CDN Software Version 2.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 "Maintaining the Cisco Internet CDN Software."
The Cisco Internet CDN Software Version 2.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.89.100.111
Step 2 Log in to the CDM using the administrator username and password.
Step 3 From the Cisco Internet CDN Software Version 2.1 user interface, click Tools.
Step 4 From the System Tools drop-down list, choose Software Update.
Step 5 For each component (CDM, Content Engine, and Content Router), refer to the Version column. The current version of the software installed on that device is displayed.
You can download the software update file from either the Cisco.com website or the Cisco FTP server.
To connect to the Cisco.com website:
Step 1 Launch your web browser and point it to the following URL:
http://www.cisco.com/cgi-bin/tablebuild.pl/cdn-sp
You are prompted to log in. Enter your Cisco.com username and password.
|
Note You need to 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, you need a service contract number, Cisco.com registration number and verification key, PICA registration number and verification key, or packaged service registration number. |
Step 2 Enter your Cisco.com username and password into the fields provided and click OK. The Cisco Internet CDN Software screen appears, listing the Internet CDN Software upgrades available for download.
Step 3 Locate the update file for the version of the Cisco Internet CDN Software that you need. Version numbers are listed in the column labeled Release. Determine which version you need by referring to the "Software Compatibility" section. Depending on the version that you currently have, you may have to go through more than one upgrade to get to version 2.1.
Step 4 Click the link for the file that you need in the Filename column, for example, merlot-2.0.0.0.28.meta.
Step 5 A page is displayed where you can verify the details of the file that you chose. If you are sure that this is the file you need, click the link for the file.
Step 6 You are prompted to open the file or save the file to a location on your hard drive. Choose Save File.
Step 7 Locate a directory on your hard drive or LAN to temporarily hold the update file and click OK.
|
Note You will use the update file later to update the Cisco Internet CDN Software on your CDN devices, so be sure to place the file in a location which is easy to remember and accessible. |
Step 8 Proceed to the section Step 3Update the Software on Your Cisco Internet CDN Devices for instructions on using the update file to update the software on your Cisco Internet CDN devices.
Instead of downloading Cisco Internet CDN Software updates from Cisco.com, you can use your web browser to download the updates from the designated Cisco FTP site: ftp://ftp.cisco.com.
Step 1 Launch a Netscape browser window.
Step 2 Log in to the Cisco FTP server as a registered user or as a guest.
ftp://userid:password@ftp.cisco.com
ftp://ftp.cisco.com
Step 3 Navigate to the following download directory on the FTP server:
cisco/content-delivery/cdn/sp/
Step 4 Locate the .upg update file for the version of the Cisco Internet CDN Software that you need. Determine which version you need by referring to the "Software Compatibility" section. Depending on the version that you currently have, you may have to perform two upgrades to reach version 2.1.
Step 5 Right-click the filename and choose the Save Link As or Save Target As option to save the target file to your local machine.
If you are prompted to open the file or save it to a disk, choose to save the file to a disk. Locate a directory on your hard drive or LAN to temporarily hold the update file and click OK.
|
Note Because you will use the update file later to update the Cisco Internet CDN Software on your CDN devices, place the file in a location which is easy to remember and accessible. |
Step 6 Proceed to Step 3Update the Software on Your Cisco Internet CDN Devices for instructions on using the update file to update the software on your Cisoc Internet CDN devices.
The CDMwill 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 CDM 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 versionto 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 Select the check boxes next to the name of the device you will be upgrading, or select 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 the limitations on and the non-intuitive behavior of some features of the Cisco Internet CDN Software. The topics covered are:
Content Engine log files may be overwritten if they are not removed from the FTP server before new logs files are generated. This happens because of three processes on a Content Engine:
1. Logrotate—Every 10 minutes, the logrotate process on a Content Engine looks for new log files to rotate. At this stage, the filenames have the structure fileroot.N.
2. Stream-logrotate—Every hour, the stream-logrotate process on a Content Engine looks for newly-rotated log files. If there are rotated log files present, it processes and compresses them. When the files are compressed, their filenames are changed to the structure fileroot.N.gz. The filename change makes the previous filename, fileroot.N, available for re-use by the logrotate process.
3. Logmover—At an interval that you define on the Remote Logging page, the logmover process on a Content Engine looks for files of the form fileroot.N.gz and starts putting timestamps on them and moving them to the remote FTP server.
The logrotate, stream-logrotate, and logmover processes are not synchronized. If the setting for remote logging transfer, which activates the logmover process, is too high, the compressed files are still present on the Content Engine while new files are being rotated and compressed. Since the rate at which files are compressed may be faster than the rate at which they are transferred to the FTP server, newly compressed files may overwrite older files with the same filenames.
The frequency with which you need to move the files to the remote FTP server depends on how much time your log files take to reach their maximum size limit. This time depends on the load that your Content Engines experience. Bearing a load of 150 HTTP transactions per second, a single Content Engine, in one hour, has to send out about 10.8 MB of SQuID logs to the FTP server, which amounts to a sustained load of 0.024 MB per second. This figure scales linearly with the number of transactions.
To reduce the likelihood of log files being overwritten, you must:
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. Previously, you could not assign more than 32 interfaces to one 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/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
Do not input fewer than 10 interfaces, unless there are no more to enter. The script will only ask you to input interfaces as many times as it would take 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 only ask you to input the interfaces 6 times. The script does not check to ensure that you input as many interfaces as you specified in your answer to "How many interfaces are bridged to this VLAN?". If you fail to enter all the interfaces in this sequence of the script, you must re-run the script.
A CDN comprising devices using mixed versions of the Cisco Internet CDN Software is supported. However, features that are new to version 2.1 are unusable in the CDN unless all devices are running version 2.1. Some of these features are:
A Content Distribution Manager (CDM) can be deleted from the network. To add it back to the network, establish a Secure Shell connection with the device, determine if your CDM is configured as a standby or a primary, and follow the appropriate procedure:
If the CDM is configured as a standby:
Step 1 Enter register.
Step 2 Go to the primary CDM's user interface.
Step 3 Activate the standby CDM through the user interface.
Step 4 Wait for the standby CDM to come online.
If the CDM is configured as a primary and you want to add it back to the CDN as a standby, follow these steps:
Step 1 At the prompt, enter setup and, when prompted, specify that the CDM is a standby.
Step 2 Enter the current primary CDM name when asked for the DNS name of the active CDM.
Step 3 At the prompt, enter register.
Step 4 Go to the primary CDM user interface.
Step 5 Activate the standby CDM through the user interface.
Step 6 Wait for the standby CDM to come online.
When the user interface indicates online status, the CDM is back on the network and has synchronized its database with the other CDM.
The bug tracking number for this issue is CSCdv43131.
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
Host> open ftp.cisco.com
Host> username: CCO_user_account_name
Host> password: CCO_account_password
Host> passive
Host> cd/cisco/content-delivery/cdn/sp
Host> get upgrade_filename
Host> bye
Host> enable
Host# upgrade swupgrade
When the upgrade is complete, the CDM will reboot itself.
While version 2.1 of the Cisco Internet CDN Software supports 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 so that those supernodes can continue to communicate with the failover CDM.
RealServer's RealSystem Media Commerce Suite (RSMCS) has not been integrated into the software. (bug number CSCdv66612). You must, instead, purchase the appropriate RealServer RSMCS plugin from Real Networks and then install it on a Content Engine running version 2.1 software. Once you have obtained the plugin, follow these steps to install it on your Content Engine:
Step 1 Verify that the plugin 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 a Content Engine in bash mode.
Step 3 Change the current directory to: /cisco/merlot/real/Plugin by entering the following command:
cd /cisco/merlot/real/Plugin
Step 4 Change this directory to read/write mode by entering the rw command.
Step 5 Transfer the plugin to this directory by using SCP or FTP.
Step 6 Change the directory back to read-only mode by entering the ro command.
Step 7 Restart the Internet CDN software by entering control restart.
For Real media 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">
For coverage zones to work, all Content Routers must be running Cisco Internet CDN Software Version 2.1. 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.
The user interface may display an "Internal server error" message when you go to the Tools > System Logs page because it tries to fetch a large set of system messages.
Content Engine log files that are in the process of being generated are transferred to the FTP host if they reach a size that is above the limit specified on the Tools > Remote Logging page. Files that are already generated are not affected in this way.
This section describes guidelines that content providers need to follow when they CDN-enable their content. It also describes the behaviors that users accessing their CDN-enabled content can expect to see. The topics covered are:
Windows Media Player 6.4 is supported only on Microsoft Internet Explorer for Windows Media Technologies (WMT) streams served through the CDN. To support Windows Media Player 6.4, Content Providers need to take the following steps:
| URL Component | Description | ||
|---|---|---|---|
hosted_domain_name | Fourth-level domain name assigned to your hosted domain or the alias assigned to that hosted domain.
| ||
cdn-wmt (optional)
| Specifies that you are designating the WMT server to handle the content item to which you are linking. Playservers can be specified in a number of locations, including the manifest file. Playserver designations in the URL of a content item override a content mapping in the manifest file. | ||
cdn-url | Relative location of the content item on the CDN device. This value is supplied by the cdn-url or src attribute in the <item> tag in the manifest file for each piece of content. Wildcard characters are accepted in the cdn-url attribute only when you link to live content. Actual content URLs must point to the actual content item. |
For a complete discussion of manifest file creation and URL publication for CDNs, see the Cisco Internet CDN Software User Guide for version 2.1, Chapter 2, in the section "Setting Up a CDN."
To open a Windows Media Technologies (WMT) file in a Netscape Version 7.x browser, end users need to install a Window Media Player plug-in. Otherwise, when the Netscape browser launches Windows Media Player, an error message appears, saying "Invalid or corrupt data was encountered."
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 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.
The following caveats are open (unresolved).
epro100: Device or resource busy rmmod: module acenic is not loaded
The following caveats are fixed (resolved) in version 2.1.
This section documents corrections to the following manuals:
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.
In Chapter 4, "Maintaining Cisco Internet CDN Software," the "Setting Up Remote Logging" section contains inaccurate log file formats for the different servers. The correct log file formats for each server are shown below. Note that the time stamp in each of the above log filenames is not given in milliseconds.
Usage guidelines for the shutdown command should state "After entering the shutdown command, you need to boot up the device manually. You need physical access to the device, because you cannot access the device remotely until you physically reboot the device."
This section lists documentation that provides additional information about the Cisco Internet CDN hardware and software.
The following documentation provides additional information about the Cisco Internet CDN hardware:
The following documentation provides additional information about the Cisco Internet CDN software:
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:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
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 "Related Documentation" section.
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:56:37 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.