cc/td/doc/product/webscale/content/cdnsp
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for the Cisco CDN Software Service Provider Solution Version 1.0.1

Release Notes for the Cisco CDN Software Service Provider Solution Version 1.0.1

February 6th, 2001

Contents

These Release Notes describe the following topics:

Introduction

Features of the Cisco (CDN) Software Service Provider Solution Version 1.0.1 include:

System Requirements

Cisco Content Delivery Network Devices

Cisco Content Delivery Network (CDN) Software Service Provider Solution Version 1.0.1 operates with the Content Distribution Manager 4670, the Content Router 4450, the Content Engine 590, and the Content Engine 7320.

Workstations that Access the Web-based Interface

You interact with Cisco CDN Software Service Provider Solution product 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 will be used as a workstation for accessing the graphical user interface:

Network
Platform and Operating System
Browser

Database Management System

The Content Distribution Manager uses an Oracle database for persistent storage of system information and statistics. The Cisco CDN Software Service Provider Solution requires that the Oracle 8i Version 8.1.6 (or higher) database management system (DBMS) be installed on your host network. You must purchase the Oracle 8i DBMS from Oracle Corporation.

For information about setting up the Oracle 8i database, refer to the Oracle documentation and the Cisco CDN Software Service Provider Solution Configuration Guide.

Domain Name System

Cisco CDN Service Provider Solution uses the Domain Name System (DNS) to route requests to Content Engines. To serve content in your CDN, you must configure DNS. For information, refer to the Cisco CDN Software Service Provider Solution Configuration Guide.

FTP Server

You need an FTP server if you want to enable remote logging. For information, refer to the online help or the Cisco CDN Software Service Provider Solution User Guide.

SNMP Manager

You need a Simple Network Management Protocol (SNMP) manager if you want to monitor system statistics using SNMP. For information about licensing SystemEDGE so you can use the SystemEDGE SNMP manager, refer to the Cisco CDN Software Service Provider Solution Configuration Guide.

Determining the Current Software Version

To determine the version of Cisco CDN Software Service Provider Solution 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 CDN Software Service Provider Solution user interface, click Tools.

Step 4   From the System Tools drop-down list, click 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.


Updating to a New Software Version

Updates to Cisco CDN Software Service Provider Solution are distributed through Cisco.com. The following procedure provides instructions on downloading updated software from Cisco.com and then using the Cisco CDN Software Service Provider Solution user interface to perform a software update to install the downloaded software on all your CDN devices.

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 web site.

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.

Downloading Software from the Cisco.com Web Site

To connect to the Cisco.com Web site:


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.

Step 2   Enter your Cisco.com username and password into the fields provided and click OK. The Cisco CDN Service Provider Software screen appears, listing the CDN Service Provider software upgrades available for download.

Step 3   Locate the update file for the version of the Cisco CDN Software Service Provider Solution that you need. Version numbers are listed in the column labeled Release.

Step 4   For the update file you need to download, click the filename to initiate the download.

Step 5   If you are prompted to open the file or save it to a disk, choose Save 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.

Step 6   Proceed to the "Updating Software Using the Cisco CDN Software Update Feature" section for instructions on using the update file to update the software on your CDN devices.


Downloading Software from the Cisco.com FTP Server

In addition to downloading CDN software updates from Cisco.com, you can also use your web browser to download 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
You are prompted to log on. If you were given a special access code by e-mail or through a customer support representative, enter the special access code as a user ID and enter your e-mail address as a password in the format user@host.domain. It should appear similar to:

    ftp://access_code:userid@host.domain/coded

Step 3   Navigate to the following download directory on the FTP server:

cisco/content-delivery/cdn/sp/

Step 4   Click the filename for each update file to download the file to your local machine, or 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.

Step 5   Proceed to the"Updating Software Using the Cisco CDN Software Update Feature" section for instructions on using the update file to update the software on your CDN devices.


Updating Software Using the Cisco CDN Software Update Feature

To update the Cisco CDN Software Service Provider Solution software on your devices:


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

Step 2   From the Cisco CDN Software Service Provider Solution user interface, click Tools.

Step 3   From the System Tools drop-down list, click Software Update.

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

Step 4   Click Add New Update File.

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

Step 5   Enter the URL for the update metafile that refers to the update file.

For example, enter:

http://internal.mysite.com/cdnsw.meta

Step 6   Click OK.

The version and URL for the update file display on the Software Update page.

For example:

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

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

Step 8   Check the check box next to each device on which you want to update software.

You can choose one or more devices. To select all Content Routers and Content Engines, check the Content Router Name and Content Engine Name check boxes.

Step 9   Click OK.


New and Changed Information

The following sections detail new software features included in Version 1.0.1.

Enabling and Disabling the Debug Logging Option

Cisco CDN Software Service Provider Solution Version 1.0.1 allows administrators to enable or disable debug logging for CDN devices using the Content Distribution Manager user interface. When enabled, debug logging records a range of events in the CDN Software Service Provider log file, merlot.log, that would otherwise be omitted.

With the additional logged information provided by the debug logging feature, CDN administrators, working with Cisco's Technical Assistance Center, can more quickly isolate and resolve problems with CDN devices.


Note   When enabling or disabling debug logging for a Content Router, Content Engine, or Content Distribution Manager, the CDN software automatically restarts the device controller on the selected device.

Enabling Debug Logging on CDN Devices

To enable debug logging on a CDN device:


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

Step 2   From the Cisco CDN Software Service Provider Solution user interface, click Tools.

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

Step 4   From the list of devices that appears, choose the desired Content Engine, Content Router, or Content Distribution Manager under the appropriate heading.

Step 5   Click the icon next to the name of the device. A second System Tools browser window appears.

Step 6   From the drop-down list, select the Enable Debugging option, then click Go. A message is displayed indicating that the debugging feature has been enabled.

Step 7   Close the System Tools window and return to the Content Distribution Manager.

Step 8   Repeat Step 4 through Step 7 for each device on which you wish to enable debug logging.


Disabling Debug Logging on CDN Devices

To disable debug logging on a CDN device:


Step 1   Follow Step 1 through Step 5 from the "Enabling Debug Logging on CDN Devices" section.

Step 2   From the drop-down list, select the Disable Debugging option, then click Go. A message indicating that the debugging feature has been disabled is displayed.

Step 3   Close the System Tools window.

Step 4   Repeat these steps for each device on which you wish to disable debug logging.


Enabling and Disabling the Telnet Option

Cisco CDN Software Service Provider Solution Version 1.0.1 includes both SSH and Telnet software, which allow administrators to connect and issue commands to CDN devices remotely. Because the information sent back and forth to CDN devices using SSH is encrypted, we recommend using SSH for all remote interaction with CDN devices.

In the event that your organization does not use SSH or that an SSH client is unavailable, you can use Telnet to communicate with your CDN devices. By default, all CDN Service Provider Solution Version 1.0.1 devices have Telnet enabled. If you will be using SSH and not Telnet to communicate with your CDN devices, we recommend disabling the Telnet feature on those devices by following the instructions in the "Disabling Telnet on CDN Devices" section.

Enabling Telnet on CDN Devices

To enable Telnet on a CDN device:


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

Step 2   From the Cisco CDN Software Service Provider Solution user interface, click Tools.

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

Step 4   From the list of devices that appears, choose the Content Engine, Content Router, or Content Distribution Manager under the appropriate heading.

Step 5   Click the icon next to the name of the device. A second System Tools browser window appears.

Step 6   From the drop-down list, select the Enable Telnet option, and then click Go. A message is displayed indicating that the Telnet feature has been enabled.

Step 7   Close the System Tools window and return to the Content Distribution Manager.

Step 8   Repeat Step 4 through Step 7 for each device on which you wish to enable Telnet.


Disabling Telnet on CDN Devices

To disable Telnet on a CDN device:


Step 1   Follow Step 1 through Step 5 from the "Enabling Telnet on CDN Devices" section.

Step 2   From the drop-down list, select the Disable Telnet option, then click Go. A message indicating that the Telnet feature has been disabled is displayed.

Step 3   Close the System Tools window.

Step 4   Repeat these steps for each device on which you wish to disable Telnet.


Generating a Debug File Package

Version 1.0.1 of the Cisco CDN Software Service Provider Solution enables users or administrators to generate a tape archive (or "tar" file) containing configuration and log files that can help troubleshoot problems that may be occurring on your CDN device.

Debug file packages are generated as TGZ-format archives on the device that is experiencing problems. They are then downloaded to the local drive of the CDN user or administrator's workstation. Debug packages can be unpacked using any archive program, such as WinZIP for the Windows operating system.

To generate a debug file package for a CDN device:


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

Step 2   From the Cisco CDN Software Service Provider Solution user interface, click Tools.

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

Step 4   From the list of devices that appears, locate the Content Engine, Content Router or Content Distribution Manager under the appropriate heading.

Step 5   Click the icon adjacent to the name of the device. A second System Tools browser window appears.

Step 6   From the drop-down list, select the Create Debug Package option, then click Go to generate a debug file package for the selected device. A message is displayed indicating that the debug file package is being generated.

Step 7   Click the link provided to download the debug file package from the remote device. You are prompted to choose a location on your local hard drive for the downloaded debug tarfile (.tgz file extension).

Step 8   Use the dialog to choose a directory on your workstation to hold the tarfile, then click OK to generate the tarfile and deposit it on your local hard drive.

Step 9   Close the System Tools window and return to the Software Update page on the Content Distribution Manager.

Step 10   Repeat Step 4 through Step 9 for each device on which you wish to generate a debug file package.


Starting and Stopping Remote Logging

Cisco CDN Software Service Provider Solution Version 1.0.1 now allows administrators to enable and disable remote logging for all Content Engines in the CDN.

For updated instructions on starting or stopping remote logging, refer to the "Documentation Updates" section.

Third-Party Billing Software Integration

Cisco CDN Software Service Provider Solution Version 1.0.1 supports integration with third-party billing applications, for example, Apogee Networks, through the Content Distribution Manager's Remote Logging feature, which tracks information locally about the Hypertext Transfer Protocol (HTTP) requests that each Content Engine processes. Log files are stored on a remote File Transfer Protocol (FTP) server that is identified on the Remote Logging screens, along with an upload path and maximum log file transfer size.

When integrating with a third-party billing vendor, no additional actions are necessary when remote logging is configured. However, CDN administrators must make sure that the third-party billing system has access to the same FTP server and path specified on the Remote Logging screen. Administrators must also clear a path through any firewalls located between the Content Engines performing remote logging and the FTP server that will store each Content Engine's log files, or between the third-party billing system and the FTP server.

Limitations and Restrictions

The following are known limitations of the Cisco CDN Software Service Provider Solution Version 1.0.1.

Internet Explorer Version 5.5 Not Supported

Use of the Cisco CDN Software web-based Content Distribution Manager interface with Internet Explorer Version 5.5 or later is not supported.

Caveats

The following section documents resolved and unresolved caveats in the Cisco CDN Software Service Provider Solution Version 1.0.1.

Open Caveats - Version 1.0.1

The following caveats are open (unresolved) at the time of shipment.

Content Delivery Network

The private and public IP address for CDN devices must be unique in the CDN.

Content Distribution Manager

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

There is no visual indication if passwords have been overridden on a CDN device.

The software update user interface does not indicate which CDN device is being upgraded, nor does it provide information on what version the device is upgrading from or to.

When deleting a software update file from the Content Distribution Manager, administrators are not prompted to confirm the decision to delete the file.

It is possible to delete upgrade files while an upgrade is in process.

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

A "System Error" message is generated in the Content Distribution Manager Add Update File window when an invalid path to the upgrade files is specified.

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

Dynamic error messages are required when attempting to download upgrade files.

It is possible to add the same upgrade files multiple times to the same Content Distribution Manager.

Content Engine and Content Router

EnodeConfig and RrConfig names must be unique.

A "503 Service Unavailable" message is generated when the Content Engine is unable to resolve the origin server name.

A "File already scheduled for transfer" error message is generated in the Content Engine log file when an invalid server is named for remote logging.

Content Engines fail to reboot after an upgrade and must be physically rebooted.

Resolved Caveats - Version 1.0.1

The following caveats are fixed (resolved) in Version 1.0.1.

Content Delivery Network

The remote log file name format has been changed from:

    IP address-access.log.log number.gz.-timestampMilliseconds
to:

    Content Engine Address~access.log.File Number~Time Stamp.cdn.gz
Where:

This new format makes it easier to sort logs chronologically and eliminates errors resulting from invalid file extensions.

Content Distribution Manager

Updates for the CDN Service Provider Solution software can be downloaded from CCO.

Remote logging on the Content Distribution Manager can now be disabled and re-enabled.

Instructions for configuring CDN devices in the Cisco CDN Software Service Provider Solution Configuration Guide now instruct the user to enter the "setup" command before configuring CDN devices, as required.

Instructions for setting up Content Engines in the Cisco CDN Software Service Provider Solution Configuration Guide now provide the default password for the "root" account.

The System Error page now displays error message text when a device is unavailable, not just a message indicating that the device is "Not Available."

Administrators using the Remote Logging feature can now specify a fractional hour in the Update Interval (Hours) field.

Documentation concerning the configuration of remote logging now properly defines the purpose of the Update Interval.

Content Engine and Content Router

Content Engines map out failed drives, enabling Content Engines to start even with errors on one or more drive partitions.

Troubleshooting

Mapping Out Failed or Damaged Content Engine Drives

In the event that one or more drives on a Content Engine have failed, or are not performing reliably, Cisco CDN Service Provider Software Version 1.0.1 supplies a new diagnostic script, cache-repair, which identifies Content Engines with failed drives to the Content Distribution Manager, and provides tools that CDN administrators can use to bring these Content Engines back online.

If you have a Content Engine with a damaged or failed drive, contact Cisco Technical Support for instructions on using the cache-repair script to repair the drive. Refer to the "Obtaining Technical Assistance" section for instructions on contacting Cisco Technical Support.

Documentation Updates

The following sections detail updates to or omissions from the latest release of the Cisco CDN Software Service Provider Solution documentation.

Changes

The following sections present passages, organized by document, that have been substantially revised based on changes to the CDN software in accordance with the 1.0.1 release.

Cisco CDN Software Service Provider Solution Configuration Guide

The following sections in the CDN Software Service Provider Solution Configuration Guide have been updated for Version 1.0.1.

Configuring DNS

The section "Configuring DNS" includes the following statement:

The public interface of each Content Router must be assigned a domain name, and DNS must be able to resolve that name both forward and backward, domain name to IP address and IP address to domain name.

This should read:

Both the public and private addresses on Content Routers and Content Engines, as well as the private IP address of the Content Distribution Manager must be able to be resolved both forwards and backwards by DNS--domain name to IP address and IP address to domain name.

Configuring a CE

The section "Configuring a CE" provides the following instructions for connecting to a Content Engine prior to configuring it:

This should instead read:

Configuring a CR

The section "Configuring a CR" provides the following instructions for connecting to a Content Router prior to configuring it:

This should instead read:

Configuring the CDM

The section "Configuring the CDM" provides the following instructions for connecting to the Content Distribution Manager prior to configuring it:

This should instead read:

Cisco CDN Software Service Provider Solution User Guide

The following section in the CDN Software Service Provider Solution User Guide has been updated for Version 1.0.1.

Setting Up Remote Logging

Each Content Engine logs information locally about the HTTP requests that the Content Engine processes. You can specify that log files be periodically deposited (in compressed form) on an FTP site. You can then use this information for billing content providers.

If you choose not to enable remote logging, log files are stored locally for a time on the Content Engine, but are eventually deleted to make room for more recent log files. Each Content Engine stores approximately 100 to 150 MB of archived log files, which are groomed off the Content Engine based upon their age, with the oldest log files being deleted first.

To specify that Content Engines log information about HTTP requests, follow these steps:


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

Step 2   In the System Tools drop-down list, click Remote Logging.

The Remote Logging page appears. (See Figure 1.)


Figure 1: Remote Logging


Step 3   In the Host Name field, enter the DNS name or the IP address of the remote FTP site where you want the Content Engine usage information logs to be deposited. For example, enter:

ftp.mydomain.com

Step 4   In the Log Files Storage Path field, enter the path on the remote FTP server where you want the log files deposited. For example, enter:

/cenglog/path

Step 5   In the Size Limit field, enter the maximum allowed size for log files transferred to the remote server. Log files that are larger than the maximum allowed size will not be transported to the remote FTP server, so be sure to use a conservative estimate when supplying this ceiling.

Step 6   In the Update Interval field, enter the frequency (in hours) with which the system checks for log files on the selected device that can be transferred to the remote FTP server. If log files are not available for transfer, no action is taken.

Step 7   In the Username field and the Password field, enter a username and a password to use to access the remote FTP server.

Step 8   Click START to begin remote logging on the selected device. Clicking STOP cancels remote logging if it has already been enabled. Clicking Cancel restores the Content Distribution Manager to its previous state.

Once it is enabled, remote logging occurs from the selected device to the designated remote FTP server at the intervals you specified.


Related Documentation

The following documentation provides information about the Cisco CDN Service Provider hardware and software:

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Documentation CD-ROM

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.

Ordering Documentation

Cisco documentation is available in the following ways:

http://www.cisco.com/cgi-bin/order/order_root.pl

http://www.cisco.com/go/subscription

Documentation Feedback

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.

Obtaining Technical Assistance

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

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:

http://www.cisco.com

Technical Assistance Center

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.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

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

Contacting TAC by Telephone

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 CDN Software Service Provider Solution User Guide and the Cisco CDN Software Service Provider Solution Configuration Guide.

AtmDirector, Browse with Me, CCDA, CCDE, CCDP, CCIE, CCNA, CCNP, 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, PIX, RateMUX, ScriptBuilder, ScriptShare, SlideCast, SMARTnet, TransPath, Voice LAN, Wavelength Router, WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, Empowering the Internet Generation, are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, 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, Network Registrar, Post-Routing, Pre-Routing, Registrar, StrataView Plus, Stratm, SwitchProbe, TeleRouter, and VCO are registered trademarks of Cisco Systems, Inc. or its affiliates in the U.S. and certain other countries.

All other brands, names, or 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. (0011R)

Copyright © 2001, Cisco Systems, Inc.
All rights reserved.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Tue Oct 1 02:56:05 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.