|
|
July 2001
These release notes contain information about Cisco Internet CDN Software Version 2.0.1 and describe the following topics:
The Cisco Internet CDN Software Version 2.0.1 release introduces new configuration options for the Content Services Switch and for Content Engines engaged in remote logging of CDN data. After upgrading to Version 2.0.1 of the Cisco Internet CDN Software, you will be able to:
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.1 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.1
Version 1.0.1 —> Version 2.0.1
Version 1.0.2 —> Version 2.0.1
Version 2.0 —> Version 2.0.1
In addition, the following downgrade sequence is supported:
Version 2.0.1 —> 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 for Version 2.0 of the Cisco Internet CDN Software.
Cisco Internet CDN Software Version 2.0.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 "Configuring DNS" section in Chapter 2 of the Cisco Internet CDN Software Configuration Guide for Version 2.0 of the Cisco Internet CDN Software.
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.1 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.1, 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 Version 2.0 of the Cisco Internet CDN Software.
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 for Version 2.0 of the Cisco Internet CDN Software.
Updates to Cisco Internet CDN Software are distributed through Cisco.com. Please review this entire section before beginning a software 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 Version 2.0.1 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 the "Step 3Update the Software on Your Internet CDN Devices" section 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 the "Step 3Update the Software on Your Internet CDN Devices" section for instructions on using the update file to update the software on your CDN devices.
Unless you are updating from Cisco Internet CDN Software Version 1.0, you can update software on your devices as needed using the Software Update feature. If you are updating from Version 1.0, see the "Updating from Version 1.0" section, otherwise use the procedure that follows.
When updating software, begin with Content Engines and Content Routers before upgrading the Content Distribution Manager.
The Content Distribution Manager will reboot at the conclusion of the upgrade procedure, causing you to temporarily lose contact with the device and the graphic user interface.
Once the Content Distribution Manager has updated its software and rebooted, it may be unable to communicate with devices running different versions of the CDN software.
To update the Cisco Internet CDN Software on your devices, follow these steps:
Step 1 From the Cisco Internet CDN Software Version 2.0.1 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 available update file 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 Always update Content Engines and Content Routers before the associated Content Distribution Manager. |
Step 5 Refer to the column labeled Version to verify that the devices you are choosing are not already running the version you wish to upgrade to, or that the current version has an upgrade path to the version that you will upgrade to.
|
Note If you have questions regarding upgrade paths, see the "Software Compatibility" section or contact Cisco Technical Support. |
Step 6 Check the check boxes next to the name of the device you will be upgrading, or check the box in the column header to select all devices.
Step 7 Click OK. The selected devices begin the update process and go offline temporarily.
Step 8 Repeat Step 4 through Step 7 for each device that you wish to upgrade.
Step 9 Click the Refresh button to see the status of your upgrade.
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://urlToUpg File > $S/Merlot.upg
$upgrade $S/MERLOT.upg
were 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. |
Step 4 Proceed to the next section, Step 4Re-run Setup on Your Internet CDN Devices for Upgrades from Version 1.0.
If you are not upgrading from Cisco Internet CDN Software Version 1.0 to Version 2.0.1, you have completed the software update procedure.
Allow 15 to 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. When devices come back online, they will be recognized by the Content Distribution Manager.
If you have just done a Version 1.0 —> Version 1.0.2 update, repeat the steps outlined in the "Step 2Download the Software Update File" section, and the "Step 3Update the Software on Your Internet CDN Devices" section, downloading the 2.0.1 .upg file.
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 for Version 2.0 of the Internet CDN Software. |
Cisco Internet CDN Software Version 2.0.1 contains the following new features:
Cisco Internet CDN Software Version 2.0.1 now supports the secure transfer of log files from CDN devices to a remote logging server. This feature prevents outsiders from "sniffing," intercepting, and gaining access to the information in CDN log files as they are being transferred between Content Engines on your CDN and your designated remote logging server.
Encrypted log files have a .gpg extension on your remote logging server. For example:
192.168.3.24~access.log.1~20010628082504.cdn.gpg
You need to have the Gnu Privacy Guard (GPG) software installed on your remote logging server in order to decrypt the CDN log files once they are received. GPG is freely available as shareware on the Internet. Refer to the Gnu Privacy Guard web page at http://www.gnupg.org.
To specify that Content Engines deposit log information about HTTP requests, follow these steps:
Step 1 From the Cisco Internet CDN Software Version 2.0.1 user interface, click tools.
Step 2 From the drop-down list, choose System Configuration.
The System Configuration page appears.
Step 3 Locate the enableLogFileEncryption option in the left-hand column.
Step 4 In the middle column, enter true in the field provided. This enables the secure log file transfer feature.
Step 5 Locate the LogFileEncryptionKey option in the left-hand column.
Step 6 In the middle column, enter an alphanumeric encryption password in the field provided. This password is used to encrypt outgoing log files and then decrypt the same files once they have been received on the remote logging FTP server. You must enter a value in this field in order for the encryption to take place.
Step 7 Click Save. The Secure log file transfer option is enabled on all Content Engines on your CDN.
Refer to the "Setting up Remote Logging" section in Chapter 4: Maintaining the Internet CDN Software in the Cisco Internet CDN Software User Guide for more information on configuring your Content Engines to transfer CDN log files to a remote server.
The Cisco Internet CDN Version 2.0.1 supports the naming of Virtual Local Area Networks (VLANs) during configuration of the Content Services Switch. Naming a VLAN makes it easier to coordinate VLAN deployment between Content Services Switches and Cisco Catalyst Switches deployed on the same CDN.
|
Note Although it is possible to name VLANs on the Content Services Switch without using the merlot-css-setup script, we strongly recommend using the script. For information on naming VLANs manually, contact Cisco Technical Support. |
Before attempting to configure your Content Services Switch using the setup script, remember to prepare the device to use the script. Refer to the "Preparing the Content Services Switch and Uploading the Script" section in the Cisco Internet CDN Software Configuration Guide. In addition, review the definitions of the various CDN addresses in the "CDN Device Network Addressing" section in Chapter 2 of the Cisco Internet CDN Software Configuration Guide.
Use the following procedure to configure your Content Services Switch to use multiple, named VLANs:
Step 1 Log in to the Content Services Switch using the admin login and the password default.
Step 2 From the prompt, discard any existing configuration settings using the clear running-config command as follows:
css-device-name>clear running-config
|
Note If you are unsure whether or not the switch has been configured previously, proceed to Step 3. The Content Services Switch setup will automatically detect any previous configurations and prompt you to discard them before continuing. Enter y (yes) when prompted to run clear running-config. |
Step 3 From the prompt, launch the setup script by entering the following command:
css-device-name>script play merlot-css-setup
Step 4 When prompted to continue with setup, enter y (yes). For example:
No startup-config was found, continue with the setup script [y/n]? y
Step 5 When prompted to indicate the number that will be used to identify the Virtual Local Area Network (VLAN) for the configuration and internal subnet, enter a number between 1 and 4095.
Step 6 When prompted to identify the interfaces (or ports) that are assigned to this VLAN, enter the interface number in the proper format for the switch you are configuring:
2/1 2/2
ethernet-5 ethernet-6 ethernet-7
css-device-name> sh interface
Step 7 When prompted, enter the configuration IP address and subnet mask for the Content Services Switch. For example:
What is the CONFIGURATION address of this CSS? [default = 192.168.0.1] 10.89.1.3
What is the CONFIGURATION subnet mask of this CSS? [default = 255.255.0.0] 255.255.240.0
Step 8 When prompted, enter the default gateway for the Content Services Switch. For example:
What is the default gateway of this CSS? [default = 192.168.0.1]
10.89.0.1
Step 9 When prompted, enter the internal subnet and internal subnet mask for the Content Services Switch. For example:
What is the INTERNAL SUBNET of this CSS? [default = 192.168.0.0] 192.168.1.0
The Content Services Switch setup script automatically sets the internal IP address (also referred to as the hidden address in the script) to the first available address in the subnet. For example,
The hidden address of this CSS is set to the first address of this CSS: 192.168.1.1
What is the INTERNAL subnet mask of this CSS? [default = 255.255.0.0] 255.255.255.0
Step 10 When prompted, indicate whether you will be designating a separate VLAN for the uplink connection from the device to your CDN. For example:
Do you want a separate VLAN for the uplink? [y/n]? y
Step 11 If you are not configuring a separate uplink VLAN, skip to Step 13.
If you are configuring a separate VLAN for the uplink interface, enter a number between 1 and 4095 to identify the VLAN. For example:
What is the number [1-4095] of this VLAN? [default = 3] 200
The deployment of multiple virtual LANs (VLANs), such as a separate VLAN for the uplink interface, provides additional address space for Content Engines grouped behind Content Services Switches in deployments in which more than one Content Services Switch is deployed on the same CDN.
Step 12 When prompted, identify the interfaces (or ports) that are assigned to the uplink VLAN; enter the interface number in the proper format for the switch you are configuring:
1/2
ethernet-2
css-device-name> sh interface
Step 13 When prompted, enter the uplink IP address and subnet mask for the Content Services Switch. This is the address and subnet used by the Content Services Switch to communicate with the uplink subnet. For example:
What is the UPLINK IP address of this CSS? [default = 192.168.0.1] 192.168.128.12
What is the subnet mask of the UPLINK? [default = 255.255.0.0] 255.255.128.0
Step 14 When prompted, indicate whether this Content Services Switch is part of a redundant Content Services Switch deployment. For example:
Is this a redundant CSS configuration? [y/n]? y
Step 15 If you are not configuring a redundant Content Services Switch, you have successfully configured the Content Services Switch. The setup script will end, returning you to the Content Services Switch prompt.
If you are configuring a redundant Content Services Switch, continue with Step 16.
Step 16 When prompted, enter a number between 1 and 4095 to identify the redundant VLAN. For example:
What is the number [1-4095] of this VLAN? [default = 3] 300
Step 17 When prompted, identify the interface that is assigned to the redundant VLAN; enter the interface number in the proper format for the switch you are configuring:
1/1
ethernet-1
css-device-name> sh interface
Step 18 When prompted, enter the redundancy subnet and subnet mask of the Content Services Switch. The redundancy addresses are used for communication between master and backup Content Services Switches in a redundant CSS implementation. For example:
What is the redundancy subnet of this CSS? [default = 192.168.0.0] 192.168.128.0
Once you have assigned the redundant subnet, the setup script automatically assigns the redundancy address to both the master and backup Content Services Switch, even if the backup Content Services Switch has not yet been configured. The master CSS address will always be the first available address on the redundant subnet, and the backup CSS address will always be the second available address. For example:
Master CSS address: 192.168.128.1, backup CSS address: 192.168.128.2
What is the redundancy subnet mask of this CSS? [default = 255.255.0.0] 255.255.255.0
Step 19 When prompted, indicate whether the Content Services Switch is a master or backup switch. Enter y (yes) to indicate that it is a master switch. Enter n (no) to indicate that it is a backup switch. For example:
Is this master CSS? 'y' for master, 'n' for backup [y/n]? y
Step 20 If you are configuring a redundant Content Services Switch, connect a crossover Ethernet cable from interface 1 on the master Content Services Switch to interface 1 on the backup switch, then repeat Step 1 through Step 19 for the backup switch.
You have now completed configuration of your Content Services Switch. The setup script will end, returning you to the Content Services Switch prompt.
As designed, Content Engines in the root location should retrieve their copy of the manifest file from the root location leader (the hosted domain leader Content Engine). Leader Content Engines for all non-root locations retrieve a copy of the updated manifest from the leader Content Engine in the root location. Content Engines in the non-root locations then retrieve their copy of the updated manifest file from the leader Content Engine in their location.
In Version 2.0.1 of Cisco Internet CDN Software, when an updated manifest file is "fetched" for a hosted domain Content Engines in both the root and non-root locations retrieve the updated manifest file from the origin server as opposed to the leader Content Engine for their location.
When running the setup script for a redundant Content Services Switch, and error stating that "the script is in use by another session" may be generated. If you receive this message, you should enter the following command on the Content Services Switch serving as the master CSS using the Command Line Interface:
master-css-device-name>clear script config_sync_lock
After entering this command, return to your redundant CSS and try again to configure the device. If this or other error messages persist, contact Cisco Technical Support.
The "New and Changed Information" section describes the new secure log transfer feature in the Cisco Internet CDN Software Version 2.0.1. It should be noted that CDN log file packages (with a .gz extension) that are generated before the enableLogFileEncryption option is enabled are not encrypted prior to transfer to the remote logging server.
When changing passwords as documented in the section on "Changing System Passwords" in Chapter 4 of the Cisco Internet CDN Software User Guide, note that passwords are only validated up to the eighth character. If only characters after the eighth are changed, the CDN software will not recognize that a password change has occurred. In addition, both the original and the changed password values will be accepted by the CDN software.
Make sure to alter at least one character within the first eight positions of the existing password when changing a CDN password value.
The CISCO-CONTENT-NETWORK-MIB monitors statistics related to the operation of the CDN and specifies SNMP traps for capturing CDN-related messages.
When used with the Version 2.0.1 CDN software, the SNMP traps do not capture serverstop messages generated by CDN devices when they are stopped or restarted.
You can find the definition of the CISCO-CONTENT-NETWORK-MIB at:
ftp://ftp.cisco.com/pub/mibs/v2/CISCO-CONTENT-NETWORK-MIB.my
To determine whether or not a CDN device has stopped and is offline, refer to the "Viewing Content Engine Statistics" section in "Chapter 3: Working with Cisco CDN Software" in the Cisco Internet CDN Software User Guide for information on viewing the Content Engine status. Content Engines display a status of offline within a few minutes of a serverstop being issued.
The following are open (unresolved) caveats for the Internet CDN Software Version 2.0.1 at the time of release:
The following are resolved caveats for the Internet CDN Software Version 2.0.1 at the time of release:
The following sections detail changes to the Cisco Internet CDN Software documentation in Version 2.0.1
The section "About Cisco Internet CDN Software" in Chapter 1 of the Cisco Internet CDN Software User Guide for Version 2.0 omits the following information on secure communications between CDN devices:
The Cisco Internet CDN Software uses Secure Sockets Layer (SSL) for Java to encrypt all inter-device communications. Developed by Netscape, the SSL protocol is supported by both the Netscape and Microsoft browsers and is a widely accepted and deployed encryption technology on the Internet. SSL uses the sockets method of communication between client and server, coupled with RSA Security's public key encryption technology to secure data using digital certificates as it is transmitted between CDN devices over the Internet.
The Cisco Internet CDN Software User Guide for Version 2.0 omits an icon legend that identifies the new status icons. In the Version 2.0 release, status icons were added for required fields, password field validation, and for accessing device configuration features as follows:
| Status Icon | Description |
|---|---|
* | Required field. The designated field must be filled in before clicking Save. |
| Error. Data was not entered, or invalid data was entered in the field. Check to make sure you are entering data in the correct format for the field. If this is a password field, enter the password again, making sure to enter it correctly. |
| Valid password. The password value you entered was accepted by the system. Your new password values take affect immediately. |
| System Tools. Click this icon to access the System Tools dialog for the selected device. The System Tools dialog contains advanced configuration options for CDN devices. |
In the section on "Setting up Remote Logging" in Chapter 4 of the Cisco Internet CDN Software User Guide for Version 2.0, the following note regarding errors produced during import for a hosted domain was omitted:
|
Note Manifest file error messages generated by the Content Engine during import may take a few moments to appear in the CDN system logs. |
In the section on "Viewing the Status of Content Replication to a Hosted Domain" in Chapter 3 of the Cisco Internet CDN Software User Guide for Version 2.0, the following note regarding the replication status was omitted:
|
Note It may take a few moments for the replication status to be updated on the Replication Status display when a Content Engine encounters errors in a Manifest file. |
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 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 documents listed in the "It may take a few moments for the replication status to be updated on the Replication Status display when a Content Engine encounters errors in a Manifest file." section.
AccessPath, 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, 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, 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 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. (0104R)
Copyright © 2000, Cisco Systems, Inc.
All rights reserved.
Posted: Tue Oct 1 03:12:59 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.
