|
|
July 3, 2001
These release notes describe the following topics:
 |
Note The most current Cisco documentation is on Cisco.com. The electronic documents may contain updates and modifications made after the hardcopy documents are printed. |
New features of the Cisco Internet CDN Software Version 2.0 are:
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,6,7 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.
Cisco Internet CDN Software Version 2.0 operates with the Content Distribution Manager 4670, the Content Router 4450, the Content Engine 590 and 7320, the Content Services Switch 11500 and 11800, and the Catalyst 4000 Family and Catalyst 5000 Family switch hardware. Each of these devices has a Simple Network Management Protocol (SNMP) agent that enables you to obtain system information through an SNMP console. Refer to the Cisco documentation that came with each device for detailed, device-specific instructions on handling, installation, and configuration of your Cisco CDN hardware.
Cisco supports the following upgrade sequences for Cisco Internet CDN Software:
Version 1.0 —> Version 1.0.2 —> Version 2.0
Version 1.0.1 —> Version 2.0
Version 1.0.2 —> Version 2.0
You interact with 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.
Cisco Internet CDN Software requires that the Oracle 8i database management system (DBMS) be installed on your host network. The Internet CDN Content Distribution Manager uses an Oracle database for persistent storage of system information and statistics.
The 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 see the "Setting Up the Oracle 8i DBMS" section in Chapter 2 of the Cisco Internet CDN Software Configuration Guide.
Cisco Internet CDN Software Version 2.0 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 "Configuring DNS" section in Chapter 2 of the Cisco Internet CDN Software Configuration Guide.
Devices such as Content Distribution Managers and Content Engines that serve QuickTime media files using the Apple Computer Darwin Streaming Server or RealNetworks RealMedia files also require that the server software be installed.
Cisco Internet CDN Version 2.0 devices ship with the Darwin Streaming Server and RealNetworks RealServer already installed. However, 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.
In addition, if you intend to serve live content using RealServer on the Cisco Internet CDN Software Version 2.0, you will have to upgrade the RealServer software on your origin server to RealServer Version 8.0 if you have not already done so.
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 information about creating and registering an SNMP manager with your CDN, refer to Chapter 4, "Maintaining the Cisco Internet CDN Software," in the Cisco Internet CDN Software User Guide.
Updates to Cisco Internet CDN Software are distributed through Cisco.com. Please review the entirety of this section before beginning the upgrade. It is important to have a clear view of the entire upgrade process before beginning any single part of it.
To update your Internet CDN Software, you must follow the following four steps:
In order to access Cisco.com and download your CDN software update, you need a registered username and password for the site. 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 Cisco.com login directly from the Cisco website.
CDN software can be downloaded from Cisco.com using either a browser pointed to the Cisco.com web site, or an FTP application connected to the Cisco FTP site. Use the directions that follow to connect to Cisco.com. If you have questions or concerns about the upgrade, please do not hesitate to contact your designated Cisco Internet CDN Technical Support representative.
To determine the version of 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. For example:
https://10.89.100.111
Step 2 Log in to the Content Distribution Manager using the administrator username and password.
Step 3 From the Cisco Internet CDN Software 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.
You can download the software update file either from the Cisco.com website or from 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.
Step 4 Click Site 1 (San Jose, CA).
|
Note Do not use Site 2, because this opens an FTP connection and prints the upgrade file to the browser. |
You are prompted to open the file or save the file to a location on your hard drive. Choose Save File.
Step 5 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 Cisco Internet CDN Software on your CDN devices, so be sure to place the file in a location that is easy to remember and which you will be able to access later. |
Step 6 Proceed to Step 3Update the Software on Your Internet CDN Devices for instructions on using the update file to update the software on your CDN devices.
In addition to downloading Internet CDN Software updates from Cisco.com, you can also use your web browser to download Internet CDN Software updates from the designated Cisco FTP site: ftp://ftp.cisco.com.
Step 1 Launch your web browser.
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
ftp://access_code:userid@host.domain/coded
Step 3 Navigate to the following download directory on the FTP server:
cisco/content-delivery/cdn/sp/
|
Note Guest users are only able to see images that are located under the pub/ directory, and will not be able to access the cisco/ directory. |
Step 4 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.
Step 5 Right-click the filename and choose the Save Link As or Save Target As options 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 You will use the update file later to update Cisco Internet CDN Software on your CDN devices, so be sure to place the file in a location that is easy to remember and which you will be able to access later. |
Step 6 Proceed to Step 3Update the Software on Your Internet CDN Devices for instructions on using the update file to update the software on your CDN devices.
Step 1 Log in to your Content Engine, Content Router, or Content Distribution Manager through Secure Shell or Telnet.
Step 2 At the command-line prompt, enter:
$ rw
$ lynx --source http://urlToUpgFile > $S/MERLOT.upg
$ upgrade $S/MERLOT.upg
where http://urlToUpgFile is the URL to your local web server and the path to the upgrade file on the local web server.
Step 3 When the upgrade is complete, you are returned to a command-line prompt. Soon after, the device reboots and you lose your connection to it.
|
Note The device may reboot twice after the upgrade is successfully completed. |
Allow 15—30 minutes for the device to come online on the Content Distribution Manager 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.
|
Note If you have just done a Version 1.0 —> Version 1.0.2 update, go through Steps 1 to 3 a second time. This time, download the 2.0 .upg file. Once you have gone through the procedure a second time, proceed with Step 4. |
After a successful update, you must re-run setup on your Content Distribution Manager, Content Router, and Content Engines.
|
Note When you update the software, you do not need to configure DNS prior to running setup on a Content Distribution Manager, Content Router, or Content Engine. DNS only needs to be configured if you are installing the software for the first time. |
For instructions on how to run setup on a:
|
Note If you are deploying supernodes on your CDN, and intend to make the Content Engine part of a supernode, make sure that you have configured your Content Services Switch before running setup on the Content Engine that will be assigned to it. For instructions on how to configure a Content Services Switch, see the "Configuring the Content Services Switch" section in Chapter 3 of the Cisco Internet CDN Software Configuration Guide. |
| Version 1.0.x | Version 2.0 |
|---|---|
CDN Software Service Provider Solution | Internet CDN Software |
Distributed Networks | Virtual Content Delivery Networks |
Routed Domains | Hosted Domains |
Public IP address | Content IP address |
Private IP address | Primary IP address |
When an error occurs with a manifest file, an error is logged immediately into the log files of the Content Engine, but the status bar on the user interface may read "Done" for some time before an error message appears. This is because it takes time for the Content Engine to push the information to the Content Distribution Manager for logging.
Errors from the Hosted Domain page are logged on the System Logs page of the Content Distribution Manager user interface. These error logs do not identify which hosted domain the error is associated with, so if you have created more than one hosted domain, you cannot tell from looking at the system logs in which domain the error occurred.
You can enable Java Monitor by checking the Enable check box on the Real Server Configuration page. However, the Content Engines page does not have a link to enable access to Java Monitor for each individual Content Engine. You need to run Java Monitor as a separate application. To run Java Monitor for a Content Engine:
Step 1 Download and install an evaluation version of RealServer from the RealNetworks website: http://www.realnetworks.com/products/.
Step 2 On the computer from which you want to view Java Monitor, download and install Version 1.1 of the Java Development Kit, available as a free download from the Sun website, at http://java.sun.com/j2se/. Follow the installation instructions on the website to install the Java Development Kit on your system.
Step 3 Choose Tools > RealServer Configuration on your Content Distribution Manager.
Step 4 Make sure that the check box next to Enable Java Monitor is selected.
Step 5 Enter a password of your choice in the Password field.
Step 6 Run the following command from your Real Server Java Monitor directory, ...\programfiles\real\realserver\realadministrator\javamonitor:
The Java Monitor application and a login screen display.
Step 7 On the login screen, enter the following items:
Step 8 Click OK to launch the Java Monitor application.
For information on how to use the Java Monitor, refer to Chapter 18, "Monitoring RealServer Activity," of the RealServer Administration Guide at this URL:
http://service.real.com/help/library/guides/server8/realsrvr.htm
When you create a new hosted domain and then try to view it right away through a browser, you may get a "Page Not Found" error message. This is because the hosted domain is not immediately propagated to the Content Router.
To avoid this, wait at least 10 minutes before you attempt to access the newly created hosted domain. If you don't wait long enough, the browser caches the fact that it was unable to get to that domain; it will take the browser aproximately 30 minutes to "forget" that it failed.
If you have already tried to access the hosted domain and received the "Page Not Found" error message, you can do one of the following:
Once you have registered a node with the CDM, the only way to set its content IP is through the CDM user interface. You cannot set it again through netsetup.
Small time differences on CDN nodes are automatically adjusted while the node is running. However, if you find that the clock of a Content Engine or Content Router is significantly different (1000 seconds higher or lower) from that of the CDM, or that the clock of the CDM is significantly different from that of the NTP server (1000 seconds higher or lower), you need to reboot the node to synchronize its clock.
You may get a "EXT2-fs warning: Maximal mount count reached, running e2fsck is recommended" warning. This is a benign message. To avoid seeing it, reboot your node.
The following section documents resolved and unresolved caveats in the Cisco Internet CDN Software Version 2.0.
The following caveats are open (unresolved) at the time of shipment.
epro100: Device or resource busy rmmod: module acenic is not loaded
error... hostname not found try again
error...unable to resolve hostname to IP address entered in content IP address
WARNING
hostname does not currently resolve to IP addressnet {976} No primary IP can't reach
gateway, did you specify?
register:can't resolve localhost.localdomain to IP address
network check failed
please correct the problem and retry register
rw
lynx --source http://urltoUpgFile > $S/MERLOT.upg
upgrade $/MERLOT.upg
The following caveats are fixed (resolved) in Version 2.0.
In the event that one or more drives on a Content Engine have failed or are not performing reliably, use the node diskadmin command in the command-line interface to repair the disks. For more information on using the command-line interface and the node diskadmin command, refer to the Cisco Internet CDN Software Command Reference.
If you have a Content Engine with a damaged or failed drive, contact Cisco Technical Support for assistance with repairing it. See the "Obtaining Technical Assistance" section for instructions on contacting Cisco Technical Support.
The following sections detail errors in, updates to, or omissions from the latest release of the Cisco Internet CDN Software documentation.
In the "Viewing Content Engines" section in Chapter 3, all references to viewing Content Engine statistics by Hosted Domain are not applicable to version 2.0. This feature will be available in future releases.
The syntax and description provided for the telnet privileged-level EXEC command in Chapter 1 and Chapter 2 are incorrect. The telnet command does not enable or disable telnet capabilities on a device. The purpose of the telnet command is to enable you to establish a telnet session with an Internet CDN device. Following are the entries for this command as they should appear in Chapter 1 and Chapter 2, respectively:
telnet {IP_address_of_device} | Establishes a telnet session with an Internet CDN device. |
To establish a Telnet session with an Internet CDN device, use the telnet EXEC command.
telnet {IP_address_of_device}
Syntax Description
IP_address_of_device IP address of the Internet CDN device with which you want to establish a Telnet session.
Defaults
Telnet and SSH are enabled by default on all Internet CDN devices.
Command Modes
EXEC
Usage Guidelines
SSH and Telnet can run concurrently.
Examples
Host# telnet 209.165.200.225
The following sections present passages, organized by document, that have been substantially revised based on changes to the CDN software for Version 2.0.
The following sections in the Cisco Internet CDN Software Configuration Guide have been updated for Version 2.0.
Chapter 1, "System Requirements," has been upated with new requirements.
This new section in Chapter 2, "Preparing to Configure CDN Devices," describes what procedures you need to complete and what information you need to verify or obtain before configuring your Content Distribution Manager, Content Router, and Content Engines.
This section in Chapter 2, "Preparing to Configure CDN Devices," has been updated to include information on configuring Hosted Domains.
This section in Chapter 2, "Preparing to Configure CDN Devices," describes the different kinds of network addresses used in configuring CDN devices. Names denoting network addresses have changed form Version 1.0.x to Version 2.0; this section helps to clarify the nomenclature.
This new section in Chapter 2, "Preparing to Configure CDN Devices," identifies what information you will require to repond to prompts during the configuration process.
This new section in Chapter 2, "Preparing to Configure CDN Devices," describes how you can access the command-line interface of a CDN device.
This new section in Chapter 3, "Configuring Content Delivery Network Devices," describes the different options available to you when configuring your Content Services Switch and structuring your Content Delivery Network.
This new section in Chapter 3, "Configuring Content Delivery Network Devices," describes how to configure a Content Services Switch manually or by using a setup script.
This new section in Chapter 3, "Configuring Content Delivery Network Devices,"descibes how to configure a Catalyst Switch for one or two VLAN deployment.
This new section in Chapter 3, "Configuring Content Delivery Network Devices,"describes how to wire Content Engines to use primary and content IP addresses.
The following sections in the Cisco Internet CDN Software User Guide are new to or updated for Version 2.0.
This is a new section in Chapter 2, "Creating Content Delivery Networks." The manifest file is a new feature in Version 2.0. It allows you to define a series of servers from which content can be fetched, as well as a list of content items on each server to be fetched. This section describes the function of the manifest file, describes its structure and syntax, describes how to create a manifest file, and provides a sample manifest file.
This new section in Chapter 2, "Creating Content Delivery Networks," describes how to create URLs that point end users to your CDN content.
This is a new section in Chapter 2, "Creating Content Delivery Networks." SuperNodes (a new feature in Version 2.0) consist of two or more Content Engines grouped behind a Content Services Switch. They provide data redundancy and next-click failover for CDN content, as well as load balancing between Content Engines for improved response time. This section describes how to create and configure SuperNodes and Content Engine clusters.
This section in Chapter 2, "Creating Content Delivery Networks," replaces a section on configuring routed domains. "Hosted domains" in Version 2.0 replace "routed domains" in Version 1.0. A new subsection, "Assigning Content Engines to Hosted Domains," describes how to import content from an origin server to a hosted domain, using the manifest file.
This is a new section in Chapter 2, "Creating Content Delivery Networks." Virtual CDNs in Version 2.0 replace the concept of distribution networks in Version 1.0. Virtual CDNs allow administrators to group Content Engines according to criteria of their choice, rather than just grouping them according to their geographic region and location. This section describes how to create a virtual CDN and how to assign Content Engines to it.
This new section in Chapter 3, "Working with Cisco Internet CDN Software," describes how to create, modify, and delete virtual Content Delivery Networks (CDNs). Virtual CDNs in Version 2.0 replace the concept of distribution networks in Version 1.0.
This new section in Chapter 3, "Working with Cisco Internet CDN Software," describes how to monitor the performance of Content Engines across the CDN network.
This new section in Chapter 3, "Working with Cisco Internet CDN Software," describes how to create, modify, and delete SuperNodes and Content Engine clusters.
This new section in Chapter 3, "Working with Cisco Internet CDN Software," describes how to view, modify, delete, purge, update, and monitor a Hosted Domain.
This new section in Chapter 3, "Working with Cisco Internet CDN Software," describes how to output tabular data on your CDN network in either printed or electronic format.
Chapter 4, "Maintaining the Cisco Internet CDN Software," is a new chapter including a lot of content from what was Chapter 3, "Working with the Internet CDN Software," in the version 1.0 User Guide.
This section in Chapter 4, "Maintaining the Cisco Internet CDN Software," has been updated with details on how to create an SNMP manager and activate it using the CDM user interface.
This section in Chapter 4, "Maintaining the Cisco Internet CDN Software," has been updated with information on how to modify RealServer and Quicktime Server settings.
This new section in Chapter 4, "Maintaining the Cisco Internet CDN Software," describes how to assign a person as a contact for each Hosted Domain and save the responsible person's contact information in the CDM user interface.
The Remote Logging procedure in Chapter 4, "Maintaining the Cisco Internet CDN Software," has been updated to reflect the following new fields: Host Names, Log Files Storage Path, Update Interval, and Size Limit. This section also contains updates about SQuID Cache, RealServer, and QuickTime log file formats.
This is a new section in Chapter 4, "Maintaining the Cisco Internet CDN Software." It describes how to modify configuration settings for a device or for the whole CDN.
The Troubleshooting section in Chapter 4, "Maintaining the Cisco Internet CDN Software," contains the following new sections: Enabling and Disabling the Debug Logging Option, Enabling and Disabling Telnet, Generating a Debug File Package, Enabling and Disabling DNS Trace, and Mapping Out Failed or Damaged Content Engine Drives. These sections document features that were available in version 1.0, but not accessible through the CDM user interface.
Appendix A, "Error and Event Messages, " has been updated for version 2.0.
The following sections provide sources for obtaining documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following sites:
Cisco documentation and additional literature are available in a CD-ROM package, which ships 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 as an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.
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:
Attn Document Resource Connection
Cisco Systems, Inc.
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. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.
Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.
Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.
To access Cisco.com, go to the following website:
The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.
If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:
P3 and P4 level problems are defined as follows:
In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.
To register for Cisco.com, go to the following website:
http://www.cisco.com/register/
If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:
http://www.cisco.com/tac/caseopen
If you have a priority level 1(P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
P1 and P2 level problems are defined as follows:
This document is to be used in conjunction with the Cisco Internet CDN Software User Guide and the Cisco Internet CDN Software Configuration Guide.
AccessPath, AtmDirector, Browse with Me, CCDE, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco NetWorks logo, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Fast Step, Follow Me Browsing, FormShare, FrameShare, GigaStack, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, Packet, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Unity, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Discover All That's Possible, and Empowering the Internet Generation, 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 Systems, Cisco Systems Capital, the Cisco Systems logo, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch, IOS, IP/TV, LightStream, MICA, Network Registrar, PIX, Post-Routing, Pre-Routing, Registrar, 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. (0105R)
Posted: Tue Oct 1 03:12:57 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.