|
|
August 26, 2002
 |
Note The most current Cisco documentation for released products is available at Cisco.com at http://www.cisco.com. The online documents may contain updates and modifications made after the hardcopy documents were printed. |
These release notes contain information about the Cisco Internet Content Delivery Network (CDN) Software, Version 2.1.2. These release notes describe the following topics:
Cisco Internet CDN Software Version 2.1.2 contains fixes for a variety of issues reported since the release of Version 2.1.1.
This section describes the devices and third-party applications that are supported on an Internet CDN, the media servers that are native to these devices, and the software and servers that are required for you to set up and manage an Internet CDN.
Cisco Internet CDN Software Version 2.1.2 operates with the following Cisco hardware:
Refer to the Cisco documentation that came with each device for detailed, device-specific instructions on handling, installing, and configuring your Cisco CDN hardware.
You interact with the Cisco Internet CDN Software using the web-based graphical user interface (GUI) that is installed on the Content Distribution Manager. The following minimum hardware and software requirements apply to each machine that is used as a workstation for accessing the graphical user interface.
The Cisco Internet CDN Software requires that the Oracle 8i database management system (DBMS) be installed on your host network. The Cisco Internet CDN Content Distribution Manager uses an Oracle database for persistent storage of system information and statistics.
The Cisco Internet CDN does not require a dedicated Oracle database. If you already have an Oracle database in use within your organization, that database can also be used with your Internet CDN.
If you have not already done so, you must purchase Oracle 8i from Oracle. The DBMS requirement is Oracle 8i Version 8.1.6 or later.
For information about setting up the Oracle 8i database, refer to the Oracle documentation, and the Cisco Internet CDN Software Configuration Guide, Version 2.1, Chapter 2, in the section "Setting Up the Oracle 8i DBMS."
Cisco Internet CDN Software Version 2.1.2 uses the Domain Name System (DNS) to route requests to Content Engines. To serve content in your Internet CDN, you must configure DNS. For information on how to do this, refer to the Cisco Internet CDN Software Configuration Guide, Version 2.1, Chapter 2, in the section "Configuring DNS."
Content Engines that serve QuickTime media files using the Apple Computer Darwin Streaming Server, RealNetworks RealMedia files, or Windows Media files require that the server software be installed. Cisco Internet CDN Version 2.1.2 Content Engines ship with the Darwin Streaming Server Version 3.0, the RealNetworks RealServer Version 8.0, and the Starbak Windows Media Technologies (WMT) Server already installed.
If you wish to distribute RealMedia content over your Internet CDN, you must also purchase a server license from RealNetworks in order to use the RealServer feature.
If you intend to serve live content using RealServer on Cisco Internet CDN Software Version 2.1.2, you must upgrade the RealServer software on your origin server to RealServer Version 8.0 if you have not already done so.
If you wish to distribute WMT content over your Internet CDN, you must purchase a WMT server license from Cisco Systems for each Content Engine that will be serving WMT content.
You need a File Transfer Protocol (FTP) server configured to receive ACTIVE-mode transmissions if you want to enable remote logging. For information, refer to the Cisco Internet CDN Software online help or the Cisco Internet CDN Software User Guide, Version 2.1.
You need a Simple Network Management Protocol (SNMP) manager if you want to monitor system statistics using SNMP. For information about creating and registering an SNMP manager with your CDN, refer to the Cisco Internet CDN Software User Guide, Version 2.1, Chapter 4, in the section "Creating an SNMP Manager."
Cisco Internet CDN Software Version 2.1.2 implements the HOST-RESOURCES MIB (IETF standard RFC 2790) and the CISCO-CONTENT-NETWORK-MIB. The CISCO-CONTENT-NETWORK-MIB monitors statistics related to the operation of the CDN. You can find the definition of the CISCO-CONTENT-NETWORK-MIB at ftp://ftp.cisco.com/pub/mibs/v2/CISCO-CONTENT-NETWORK-MIB.my. For information on traps and variables in this MIB, refer to the Cisco Internet CDN Software User Guide, Version 2.1.
Review this entire section before beginning a software upgrade or downgrade. It is important to have a clear view of the entire upgrade or downgrade process before beginning.
In order to access and download Cisco Internet CDN Software updates, you need a registered username and password. If you are a Cisco customer and service contract owner, a Cisco reseller, Premier Certified Partner, the customer of a Cisco certified Partner Initiated Customer Access (PICA) partner, or a Cisco consultant, you can acquire a login directly from the Cisco.com website.
If you have questions or concerns about the upgrade, contact your designated Cisco Internet CDN Technical Support representative.
To upgrade your Cisco Internet CDN Software, you must follow this three-step procedure:
To determine the version of the Cisco Internet CDN Software that you are using:
Step 1 In your web browser, enter the secure IP address or DNS name of the Content Distribution Manager (CDM). For example:
https://10.0.0.0
Step 2 Log in to the Content Distribution Manager using the administrator username and password.
Step 3 From the Content Distribution Manager user interface, click Tools.
Step 4 From the System Tools drop-down list, choose Software Update.
Step 5 For each component (Content Distribution Manager, Content Engine, and Content Router), refer to the Version column. The current version of the software installed on that device is displayed.
Before you can update your Cisco Internet CDN Software, you must first acquire the appropriate software update file from Cisco.
In order to acquire the software update from Cisco, you must first:
You must have a Cisco.com username and password before attempting to download a software update from Cisco.com. In order to acquire a Cisco.com login, go to http://www.cisco.com and click the Register link.
|
Note You need a service contract number, Cisco.com registration number and verification key, Partner Initiated Customer Access (PICA) registration number and verification key, or packaged service registration number in order to obtain a Cisco.com username and password. |
To add an update file for the Cisco Internet CDN Software:
Step 1 Launch your preferred web browser and point it to:
http://www.cisco.com/cgi-bin/tablebuild.pl/cdn-sp
Step 2 When prompted, log in to Cisco.com using your designated Cisco.com username and password.
The Cisco Internet CDN Software download page appears, listing the available software updates for the Cisco Internet CDN Software product.
|
Note Each software update consists of two files: a binary-format update file (*.upg) and a smaller meta file (*.meta). Both files must be downloaded in order to successfully complete a Cisco Internet CDN Software update. |
Step 3 Locate the files you wish to download by referring to the Release column for the proper release version of the software.
Step 4 Click the link for the software update file that you wish to download. The order in which you download the update files does not matter. The download page appears.
Step 5 Click the Software License Agreement link. A new browser window opens, displaying the license agreement.
Step 6 After you have read the license agreement, close the browser window displaying the agreement and return to the Software Download page.
Step 7 Click the filename link labeled Download.
Step 8 Click Save to file and then choose a location on your workstation to temporarily store the update file.
Step 9 Post the file you downloaded (*.meta or *.upg) to a designated area on your organization's web server and make note of the URL required to access this file. You will need it later.
|
Note It is imperative that the upgrade (*.upg) file be placed in the same directory as its corresponding meta (*.meta) file. |
Step 10 Repeat Step 3 through Step 9 for the other software update file.
Step 11 Launch the Content Distribution Manager and log in using an administrative username and password.
Step 12 Click tools.
Step 13 From the drop-down list, choose Software Update.
The Software Update page appears, listing available software updates. If there is currently no update available, a message appears.
Step 14 Click Add New Update File.
A page appears with a field for entering the URL of your software update.
Step 15 Paste the URL for the update meta file on your web server into the field provided. For example, a valid URL might look like this:
http://internal.mysite.com/cdn/internet-CDN-version.meta
where internet-CDN-version is the version number of the software update.
|
Note Do not attempt to link directly to the UPG file. The relative location of the update file is provided by the meta file. |
Step 16 Click OK.
The version and URL for the update file appear, for example:
1.0.3 http://internal.mysite.com/cdnsw.upg
It is also possible to add a software update to the Internet CDN directly from Cisco.com, rather than posting it on a web server within your organization first.
To add the software update directly from Cisco.com:
Step 1 Launch your preferred web browser and point it to:
http://www.cisco.com/cgi-bin/tablebuild.pl/cdn-sp
Step 2 When prompted, log in to Cisco.com using your designated username and password.
The Cisco Internet CDN Software (Cisco CDN Service Provider Software) download page appears, listing the available software updates for the Cisco Internet CDN Software product. Note that each software update consists of two files: a binary-format upgrade file (*.upg) and a smaller meta file (*.meta).
Locate the software update that you wish to install by consulting the Release column for the proper release version of the software.
Step 3 Click the link for the meta (*.meta) file. The download page appears.
Step 4 Click the Software License Agreement link. A new browser window opens, displaying the license agreement.
Step 5 After you have read the license agreement, close the browser window displaying the agreement and return to the Software Download page.
Step 6 Right-click the filename link labeled Download and choose the Create Shortcut option (Netscape) or the Copy Shortcut option (Internet Explorer). If you are using the Netscape browser, copy the contents of the URL field in the dialog box that appears, and then click Cancel to close the Create Shortcut dialog box.
Step 7 Point your browser to the address of your Cisco Internet CDN Software Version 2.1 Content Distribution Manager and log in using an administrative username and password.
Step 8 Click tools.
Step 9 From the drop-down list, choose Software Update.
Step 10 The Software Update page appears, listing available software updates. If there is currently no update available, a message appears.
Step 11 Click Add New Update File.
A page appears for specifying the URL for the update location.
Step 12 Paste the shortcut you copied for the update meta file on Cisco.com into the field provided. The URL should begin with:
http://www.cisco.com/cgi-bin/Software/Tablebuild/download.cgi/...
Step 13 Click OK.
The version and URL for the update file appear, for example:
1.0.3 http://internal.mysite.com/cdnsw.upg
The Content Distribution Manager will reboot at the conclusion of the upgrade procedure, causing you to temporarily lose contact with the device and the graphical user interface.
To update the Cisco Internet CDN Software on your devices, follow these steps:
Step 1 From the Content Distribution Manager user interface, click tools.
Step 2 From the drop-down list, choose Software Update.
Step 3 On the Software Update page, click the radio button next to the update file that you want to use.
Step 4 Click the tab corresponding to the type of device that you want to upgrade, for example, Content Routers. The window refreshes, listing the devices of the selected type on your Internet CDN.
|
Note When updating the software on your Content Engines, you need to ensure that all Content Engines in a single supernode are updated at the same time. |
Step 5 Refer to the column labeled Version to verify that the devices you are choosing are not already running the version to which you will be upgrading. Also verify that the current version has an upgrade path to the version to which you are upgrading.
|
Note If you have questions regarding upgrade paths, see the "Upgrade Paths" section 11 or contact Cisco Technical Support. |
Step 6 Check the check boxes next to the name of the device you will be upgrading, or check the box in the column header to select all devices.
Step 7 Click OK. The update process begins on the selected devices and they go offline temporarily.
Step 8 Repeat Step 4 through Step 7 for each device or group of devices that you wish to upgrade.
Step 9 Click the Refresh button to see the status of your upgrade.
You have completed the software update procedure.
Allow 15 to 30 minutes for the devices to come online on the Content Distribution Manager user interface after the upgrade has been completed. The CE-7320-ICDN-K9 takes longer to come online than the CE-590-ICDN-K9 because of the number of drives on the device.
The Cisco Internet CDN Software supports software and database downgrades, as well as upgrades. Downgrades may be necessary when an upgrade introduces unforeseen problems in your CDN, or when an upgrade fails and your CDN devices need to be restored to their state prior to upgrade.
When you upgrade to a later version of the Cisco Internet CDN Software, backup copies of your CDN database tables are created on your Oracle server. If you need to restore the earlier version of your Internet CDN Software, these duplicate database tables must be restored before you restore the earlier CDN software version.
When you restore your database, all CDN configuration changes that were made after the upgrade are lost and need to be manually restored once your CDN devices are up and running with the restored software version.
|
Note It is not necessary to downgrade your database when downgrading from Version 2.1.2 to Version 2.1.1 of the Cisco Internet CDN Software. |
To downgrade your Internet CDN Software:
Step 1 If you have not already done so, acquire the software update file for the Internet CDN Software version to which you will be downgrading by following the instructions in the "Step 2Adding a New Update File" section.
Step 2 Log in to the Content Distribution Manager's command-line interface (CLI) using either a direct console connection or a terminal emulation client.
Step 3 If necessary, use the ftp or scp command to move or copy the software update file you will be using for your downgrade into the following location on your Content Distribution Manager.
/cisco/merlot/state/dump/home
Refer to the "Updating the Software on a Warm Standby Content Distribution Manager" section in Chapter 4, "Maintaining Cisco Internet CDN Software" of the Cisco Internet CDN Software User Guide Version 2.1 for step-by-step instructions on uploading a software update file to your Content Distribution Manager using FTP.
Step 4 Enter user EXEC mode to back up your existing database. For example:
Host> enable
Host#
Step 5 Stop the Content Distribution Manager using the node stop command:
Host# node stop
Step 6 Use the upgrade display command to output a record of past database upgrades. You will use this output to locate the last successful database upgrade. This is the database version to which you will be downgrading. In the following example the last successful database upgrade is bolded.
Host# upgrade display
Current DbUpgrade version is 2.1.1.0.2
StoreUpgrade List of DbUpgrade records.
DbUpgrade/1/gen#1:StartTime=Tue May 07 22:17:15 GMT
2002:Operation=creation:FromVersion=2.0.1.0.1:ToVersion=2.0.1.0.1:State=complete:BackupId=
null:BackupImage=null:RestoreId=null
DbUpgrade/2/gen#232:StartTime=Tue May 07 22:17:18 GMT
2002:Operation=upgrade:FromVersion=2.0.1.0.1:ToVersion=2.1.1.0.2:State=complete:BackupId=A
:BackupImage=null:RestoreId=null
DbUpgrade/3/gen#4939:StartTime=Wed Jul 10 17:09:07 GMT
2002:Operation=backup:FromVersion=2.1.1.0.2:ToVersion=2.1.1.0.2:State=complete:BackupId=B:
BackupImage=null:RestoreId=null
DbUpgrade/4/gen#4970:StartTime=Wed Jul 10 18:42:27 GMT
2002:Operation=backup:FromVersion=2.1.1.0.2:ToVersion=2.1.1.0.2:State=complete:BackupId=C:
BackupImage=null:RestoreId=null
DbUpgrade/5/gen#4971:StartTime=Wed Jul 10 18:43:43 GMT
2002:Operation=backup:FromVersion=2.1.1.0.2:ToVersion=2.1.1.0.2:State=complete:BackupId=D:
BackupImage=null:RestoreId=null
List of Version Upgrades available in this storeUpgrade.
2.0.1.0.1 - 2.0.2.0.8 Default Upgrade Module.
2.1.0.0.1 - 2.1.0.0.7 Oracle Upgrade from 2.0.1 to 2.1.0.0.7 .
2.1.0.0.8 - 2.1.0.0.15 Oracle Upgrade for build 2.1.0.0.15
2.1.0.0.16 - 2.1.0.0.16 Oracle Upgrade for build 2.1.1.0.4
2.1.0.0.17 - 2.1.1.0.1 Oracle Upgrade for build 2.1.1.0.1
2.1.1.0.2 - 2.1.1.0.4 Oracle Upgrade for build 2.1.1.0.4
controller.storeUpgrade Done.
Step 7 In the block of text that appears immediately after the heading "StoreUpgrade List of DbUpgrade records," find the last occurrence of the following text:
Operation=upgrade
This denotes the last successful database upgrade.
Step 8 Make a note of the date and the number that follows "DbUpgrade." You will need this information for Step 12.
Step 9 Use the upgrade restore command to begin your database downgrade, for example:
Host# upgrade restore
You are asked to choose which backup you wish to restore, for example:
Available Database backups
1. 2.1.1.0.2 created on Tue May 07 22:17:18 GMT 2002 [id=2]
2. 2.1.1.0.2 created on Wed Jul 10 17:09:07 GMT 2002 [id=3]
3. 2.1.1.0.2 created on Wed Jul 10 18:42:27 GMT 2002 [id=4]
4. 2.1.1.0.2 created on Wed Jul 10 18:43:43 GMT 2002 [id=5]
Host# [1-4]:
Step 10 Enter the number corresponding to the line containing the date and ID number of the last database backup. In the case of the example output provided in Step 6, you would enter 1to select the database backup created on Tuesday, May 7 2002 at 7:22:17:18 GMT.
After you have completed your database downgrade, you are ready to restore the earlier software version on your Content Distribution Manager.
Step 11 Enter upgrade swupgrade to initiate the software update on the Content Distribution Manager, for example:
Host# upgrade swupgrade
Available Update files
1. /cisco/merlot/state/dump/home/merlot-2.1.0.0.25.upg
Step 12 Enter the number of the software version that you wish to downgrade to.
Step 13 When prompted to upgrade to the software version you selected, enter y for "yes."
Do you want to update the system with
/cisco/merlot/state/dump/home/merlot-2.1.0.0.25.upg? [y/n]: y
Executing Update using file:
/cisco/merlot/state/dump/home/merlot-2.1.0.0.25.upg
The system is going to reboot when the Update is complete.
Starting upgrade using \Q/cisco/merlot/state/dump/home/merlot-2.1.0.0.25.upg'
Verifying upgrade file integrity.
Unpacking upgrade file.
Running installation using /cisco/merlot/dist/install
Rebooting post software-update
The Content Distribution Manager will reboot once the software update is complete.
No new features have been added to Version 2.1.2 of the Cisco Internet CDN Software.
The following sections contain installation-specific information for Version 2.1.2 of the Cisco Internet CDN Software.
For Version 2.1.2, the following upgrade sequences for the Cisco Internet CDN Software are supported:
For Version 2.1.2 of the Cisco Internet CDN Software, the following downgrade sequences are supported:
|
Note No database downgrade is required when downgrading from Version 2.1.2 to Version 2.1.1. |
If you are deploying a Cisco 11500 Series Content Services Switch (CSS) on your Internet CDN, you must upgrade all CDN devices to Version 2.1.2 of the Cisco Internet CDN Software. The Cisco 11500 Series CSS will not work with versions of the Cisco Internet CDN Software that predate the Version 2.1.2 release.
See the "Configuring the Content Services Switch" section in "Chapter 3: Configuring CDN Devices," in the Cisco Internet CDN Software Configuration Guide for information on configuring Content Services Switches for use with the Internet CDN Software.
In some instances following the initial configuration of a new Content Distribution Manager, the Content Distribution Manager database is not properly configured following execution of the dbsetup script. In such cases, the Content Distribution Manager displays a status of "pending" in the Resources > Content Distribution Manager page. In addition, the CDM is not listed on the Tools > Software Update > Content Distribution Manager tab. Finally, a review of the /cisco/merlot/safe-state/node.dat file shows that the Content Distribution Manager ID has a value of zero.
If you encounter this situation, use the following procedure to re-create your Content Distribution Manager database.
The following procedure results in your Oracle database being rewritten. All data previously stored on your database will be lost and will have to be reentered following completion of the dbsetup routine.
To rerun dbsetup on your Content Distribution Manager:
Step 1 Verify that your Content Distribution Manager is showing the behavior described above by logging in to the Content Distribution Manager GUI and access the Resources > Content Distribution Manager page. Determine that the CDM has a status of "pending," and access the Software Update > Content Distribution Manager page to verify that the Content Distribution Manager is not listed on the Content Distribution Manager tab.
If both of the above conditions are true, use the following steps to properly reconfigure your CDM database:
Step 2 Log in to the CLI of the Content Distribution Manager.
Step 3 Enter configuration mode by entering the enable command followed by the configure command.
Host> enable
Host# configure
Host(config)#
Step 4 Enter the dbsetup command to begin the database setup routine.
Host(config)# dbsetup
Step 5 You are asked if you want to delete the user. Enter y to overwrite the user. Your database will be regenerated from scratch. All database content will be lost in the process, and you will have to reenter that information after the dbsetup routine concludes.
Step 6 The dbsetup program verifies whether database tables exist. You create them now unless you already created the database schema using the script that shipped with Cisco Internet CDN Software, described in the "Setting Up the Oracle 8i DBMS" section on page 2-6 of the Cisco Internet CDN Software Configuration Guide Version 2.1.
Step 7 To create the database tables, enter y.
Step 8 The dbsetup program verifies whether the database tables have been initialized. To initialize the tables, enter y.
Step 9 Enter the database administrator username.
Step 10 Enter the database administrator password.
Step 11 Reboot the Content Distribution Manager.
|
Note When you bring up the Content Distribution Manager user interface in your browser, you must ensure that you have cookies enabled in your browser. |
Step 12 Log back in to the Content Distribution Manager GUI and use its features to reenter any CDN configuration data such as hosted domains, content providers, and regions that existed before you reran the dbsetup program.
This section describes important issues related to Version 2.1.2 of Cisco Internet CDN Software that are not covered by new features or otherwise addressed in the product documentation.
Because of technical problems related to RealServer's implementation of distributed licensing, that feature cannot be used with Cisco Internet CDN Software Version 2.1.2.
If you are currently using distributed licensing in an Internet CDN deployment and intend to upgrade to Version 2.1.2 of the Internet CDN Software, we encourage you to disable the distributed licensing feature and use local licensing to update RealServer licenses on your Internet CDN devices.
See the "Configuring RealServer Licensing" section for instructions on disabling RealServer distributed licensing.
In Cisco Internet Software Version 2.1.2, nonredundant Content Distribution Managers that experience hardware failure also experience problems attempting to reconnect to the Internet CDN Software database following restoration of the Content Distribution Manager hardware.
The following procedure was developed to enable customers who experienced such failures in a nonredundant Content Distribution Manager configuration to restore their Content Distribution Manager. However, we strongly recommend deploying a redundant (standby) Content Distribution Manager to minimize downtime in the event of such a failure and to streamline recovery of your Content Distribution Manager data.
Use the following procedure to restore your nonredundant Content Distribution Manager following a hardware failure:
Step 1 Follow the instructions to install and activate your new Cisco Content Distribution Manager hardware by referring to the printed or online documentation for your hardware.
Step 2 With your Content Distribution Manager properly mounted and cabled, refer to Chapter 3, "Configuring CDN Devices," in the Cisco Internet CDN Software Configuration Guide to configure the Cisco Internet CDN Software on your new Content Distribution Manager hardware.
When configuring your new Content Distribution Manager, perform the setup normally, using the same IP address and database values that you used to configure the device that failed. However, when prompted to enter an Oracle database username, enter a different username from that used in your previous installation. This creates a new certificate, and generates the node.dat file with the correct node ID and signature.
Step 3 Shut down the Content Distribution Manager by following the instructions in the Cisco Internet CDN Software User Guide.
Step 4 Log on to the Content Distribution Manager device and navigate to the /safe-state directory.
Step 5 Use the rw command to make the file system writable, for example:
Host> rw
Step 6 Edit the node.dat file using your preferred Linux text editor, such as vi, replacing the current dbusername with the initial username. Then save the file.
|
Note Do not modify any other values in this file. |
Step 7 Use the control start command to restart the Content Distribution Manager, which will come back on line, for example:
Host> control start
Step 8 Once the Content Distribution Manager has successfully restarted and come on line, log on to each of your Content Routers in turn, entering the register -force command on the Content Router to reregister each device with the Content Distribution Manager, for example:
Host> register -force
Step 9 Log on to the Content Distribution Manager GUI and activate the Content Routers by following the instructions for activating Content Routers in Chapter 2, "Creating Content Delivery Networks," in the Cisco Internet CDN Software User Guide. Each Content Router will come on line.
Step 10 From the Content Distribution Manager GUI, write down the hosted domain assignments and disk space allocations for each Content Engine in your CDN.
Step 11 Use the Content Distribution Manager GUI to unassign all hosted domains from each of your Content Engines.
Step 12 Log on to each Content Engine in turn and enter the register -force command to reregister each device with the Content Distribution Manager.
Step 13 Log on to the Content Distribution Manager GUI and activate the Content Engines. Each Content Engine will come on line.
Step 14 Use the Content Distribution Manager GUI to reassign hosted domains for each of your Content Engines.
Caveats describe unexpected behavior in Cisco Internet CDN Software.
This section describes the caveats—both resolved and unresolved—that are associated with Version 2.1.2 of Cisco Internet CDN Software.
The following caveats are open (unresolved). Unresolved caveats are listed according to their tracking number. Caveats describe unexpected behavior in Internet CDN Software, Version 2.1.2. Severity 1 caveats are the most serious; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats.
mount: / is busy
Operation Successful
Error - 100%
/cisco/merlot/state/pid/squid.pid empty
/cisco/merlot/lib/MerlotUtils.pm
c:\Asfroot\wmt.asf.
10.1.2.3
livedemo.asf
http://10.1.2.3
www.cisco.com/rm/house.rt
/rm/house.rt
The following caveats are fixed (resolved) in Cisco Internet CDN Software Version 2.1.2. Caveats are listed according to their tracking number.
Apr 16 14:38:12 bur-icdn-sur02 director[28811]: [W] TFManager: Location
leader has no path for RD 500 (null)
Apr 16 14:38:12 bur-icdn-sur02 director[28811]: [W] TFManager: Location
leader has no path for RD 521 (null)
(32075)ERRO:server.c:362-> my_sig_segv_handler: (sig 11)
(30506)ERRO:server.c:402-> already in my_sig_segv_handler (sig 11)
Unable to close mms/logs/xxxx file.
Apr 8 15:05:29 b2-ce3 stream-logrotate[1252]: [W] Unable to close
/cisco/merlot/state/mms/logs/192.1.2.3~mms_export.020408.log~20024815529.cdn..tmp:
10.8.9.10~access.log.3~20011023081707.cdn.gz
10.8.9.10~access.log.3~20011023081707.cdn.gz.ok
10.11.12.13~access.log.4~20011023081711.cdn.gz
10.11.12.13~access.log.4~20011023081711.cdn.gz.ok
access.log.number.gz
access.log.number.gz.ok
access.log.number.gz
access.log.number.gz.ok
1027706317.900 192.168.1.2 TCP_MISS/200 310 OPTIONS http://localhost/ -
DIRECT/10.89.1.2 -
The following sections detail updates to the Cisco Internet CDN Software Version 2.1 documentation. Updates include corrections to printed documentation errors, information that has been updated or added since the last full documentation release, and information that was omitted in the last release.
The following sections describe inaccuracies in Version 2.1 of the Cisco Internet CDN Software documentation. In each case, information is provided that corrects the inaccuracies.
SQL> grant CREATE SESSION, connect, resource to username;
In Chapter 2, "Creating Content Delivery Networks," the "<CdnManifest>" section contains the following statement:
This should read:
The following sections provide updates to content in Version 2.1 of the Cisco Internet CDN Software documentation.
Cisco Internet CDN Software does not support distributed licensing for use with RealServers that are serving CDN content. Individual licensing is the preferred and supported method for license distribution on a Cisco Internet CDN.
Distributed licensing is disabled on Cisco Internet CDN devices by default. If you have previously used distributed licensing, however, you must use the following procedure to ensure that it is disabled.
To disable RealServer distributed licensing:
Step 1 From the Cisco Internet CDN Software Version 2.1 user interface, click tools.
Step 2 From the drop-down list, choose Real Server Configuration.
The Real Server Configuration Tool page appears.
Step 3 If it is checked, uncheck the Enable Distributed Licensing check box.
Step 4 Click Save to save your configuration changes. Any CDN devices with RealServer installed will restart to integrate the new license distribution configuration change.
Step 5 Next, log in to each Content Engine in your Internet CDN network in turn and use the real CLI command to install an individual RealServer license on each device that will be streaming RealServer content.
Refer to the "Documentation Omissions" section in the Release Notes for Cisco Internet CDN Software Version 2.1.1 for instructions on using the real command to install a RealServer license.
The following sections provide new information that was omitted from or unavailable for Version 2.1 of the Cisco Internet CDN Software documentation.
To update your Cisco Internet CDN Software on a Content Engine or Content Router:
Step 1 Log in to the CDN device using the admin account and password.
Step 2 At the prompt, enter enable to enable administrative mode.
Host> enable
Host#
The prompt changes to a pound sign (#) to indicate that you are in administrative mode.
Step 3 Enter ftp to launch the file transfer application.
The prompt changes to indicate that you are in FTP mode.
Step 4 Enter the open command, followed by the DNS name or IP address of the host machine containing the software upgrade package, for example:
ftp> open 10.89.11.1
You may need to log in separately to the host machine.
Step 5 Enter bin to switch to binary transfer mode.
In addition, if you are manually upgrading a Content Engine that is part of a supernode (that is, the Content Engine is located behind a Content Services Switch), enter the passive command to switch to passive mode.
Step 6 Enter the cd command followed by the remote path of the upgrade file, for example:
ftp> cd /upgrade
The directory changes to the location that you specified.
Step 7 Enter the get command, followed by the name of the upgrade file, MERLOT.upg:
ftp> get MERLOT.upg
Step 8 Enter the quit command to close the file transfer application.
Step 9 Enter upgrade swupgrade to initiate the software update on the Content Engine or Content Router:
# upgrade swupgrade
The Content Engine or Content Router automatically restarts following the software update.
Using the manifest file clearlog tag, you can clear the manifest log files on your Content Engines at the same time as you update ("fetch") your manifest. However, when the content owner is not the owner of the CDN hardware, this capability may not be desirable.
Using the clearManifestLog system configuration property, you can enable or disable the clearlog tag. The clearManifestLog property is set to "false" by default, meaning that the clearlog tag cannot be used to clear the contents of manifest log files.
|
Note Modifying the clearManifestLog configuration property causes all Content Engines affected by the change to automatically stop and restart. |
To enable or disable the clearlog manifest file tag:
Step 1 From the Cisco Internet CDN Software Version 2.1 user interface, click tools.
Step 2 From the tools drop-down list, choose the System Configuration option. The System Configuration page appears.
Step 3 Click the Add Property button.
Step 4 Click the Catalogs tab. The page refreshes, listing CDN properties.
Step 5 Click the button next to the mover.clearManifestLog option.
|
Note Properties are not listed alphabetically, so if you have trouble locating the property, use the Ctrl F key combination to display the Find dialog box, enter clearManifestLog in the field provided and then click Find or Find Next to locate the property. |
Step 6 Scroll back to the top of the list of properties and click the Add button. The Modify Properties page refreshes, listing the name of the property in the Name field and other fields for configuring the property.
Step 7 In the Value field, enter "true" to make it possible for the manifest log files to be cleared using the clearlog XML tag in the manifest file, or "false" to make it impossible for the manifest logs to be cleared using the clearlog tag, for example:
true
Step 8 Check the CE check box, indicating that this configuration option should be applied only to the Content Engines (CEs) on your CDN.
Step 9 Click the Content Engines tab to display a list of Content Engines on your CDN.
Step 10 Check the box next to each Content Engine to which the clearlog tag limitation will apply.
Step 11 Scroll back to the top of the list of properties and click the Add button. The unique numeric identifiers for each CDN device are added to the Send to Nodes field automatically.
Step 12 At the bottom of the page, click the Save button. The new setting is distributed to the Content Engines you identified.
The affected Content Engines are automatically stopped and restarted, allowing the new configuration property to take effect.
The new setting is distributed to the Content Engines you identified and the clearManifestLog configuration option is added to the System Configuration Page, from which it can be easily accessed and modified in the future.
Refer to the "Modifying System Properties" section in Chapter 4, "Maintaining the Internet CDN Software" of the Cisco Internet CDN Software User Guide Version 2.1 for instructions on modifying system properties using the System Configuration feature of the Content Distribution Manager GUI.
Before you can configure the maximum item limit used by manifest files on your CDN, you must first add the manifestItemLimit property to the System Configuration page. Once this property has been added, you can modify the manifest file ceiling used by one or more of your Content Engines by simply adjusting the limit field.
To add the manifest file item limit property to your system configuration and then modify the item limit used by your manifest files:
Step 1 From the Cisco Internet CDN Software Version 2.1 user interface, click tools.
Step 2 From the tools drop-down list, choose the System Configuration option. The System Configuration page appears.
Step 3 Click the Add Property button.
Step 4 Click the Catalogs tab. The page refreshes, listing CDN properties.
Step 5 Click the button next to the mover.manifestItemLimit option.
|
Note Properties are not listed alphabetically, so if you have trouble locating the property, use the Ctrl F key combination to display the Find dialog box, enter manifestItemLimit in the field provided and then click Find or Find Next to locate the property. |
Step 6 Scroll back to the top of the list of properties and click the Add button. The Modify Properties page refreshes, listing the name of the property in the Name field and other fields for configuring the property.
Step 7 In the Value field, enter the maximum number of items that can be included in a single manifest file, for example:
2000000
This maximum value is 10 million items (10000000).
Step 8 Click the CE check box, indicating that this configuration option should be applied only to the Content Engines (CEs) on your CDN.
Step 9 Click the Content Engines tab to display a list of Content Engines on your CDN.
Step 10 Check the box next to each Content Engine to which the parameter will apply.
Step 11 Scroll back to the top of the list of properties and click the Add button. The unique numeric identifiers for each CDN device are added to the Send to Nodes field automatically.
Step 12 At the bottom of the page, click the Save button.
The new limit setting is distributed to the Content Engines you identified and the manifestItemLimit configuration option is added to the System Configuration Page, from which it can be easily accessed and modified in the future.
Your Cisco Internet CDN product shipped with a minimal set of printed documentation, as well as a Documentation CD. The printed documentation provides enough information for you to install and initially configure your product. The CD contains additional product documentation (user guides, configuration manuals, and so forth), which you can access and print out.
The following sections list related documentation for your product. These documents were not shipped with your product, but you can access them and order them by using the URLs listed below:
The following release-specific documents are associated with the Cisco Internet CDN product.
The following hardware documents are associated with the Cisco Internet CDN product.
The following software documentation is available online and can be ordered in hardcopy format for your Cisco Internet CDN product.
The following sections explain how to obtain documentation from Cisco Systems.
You can access the most current Cisco documentation on the World Wide Web at the following URL:
Translated documentation is available at the following URL:
http://www.cisco.com/public/countries_languages.shtml
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which is shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Cisco documentation is available in the following ways:
If you are reading Cisco product documentation on Cisco.com, you can submit technical comments electronically. Click the Fax or Email option under the "Leave Feedback" at the bottom of the Cisco Documentation home page.
You can e-mail your comments to bug-doc@cisco.com.
To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:
Cisco Systems
Attn: Document Resource Connection
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools by using the Cisco Technical Assistance Center (TAC) Web Site. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC Web Site.
Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com is a highly integrated Internet application and a powerful, easy-to-use tool that provides a broad range of features and services to help you to
You can self-register on Cisco.com to obtain customized information and service. To access Cisco.com, go to the following URL:
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two types of support are available through the Cisco TAC: the Cisco TAC Web Site and the Cisco TAC Escalation Center.
Inquiries to Cisco TAC are categorized according to the urgency of the issue:
Which Cisco TAC resource you choose is based on the priority of the problem and the conditions of service contracts, when applicable.
The Cisco TAC Web Site allows you to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC Web Site, go to the following URL:
All customers, partners, and resellers who have a valid Cisco services contract have complete access to the technical support resources on the Cisco TAC Web Site. The Cisco TAC Web Site requires a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to the following URL to register:
http://www.cisco.com/register/
If you cannot resolve your technical issues by using the Cisco TAC Web Site, and you are a Cisco.com registered, you can open a case online by using the TAC Case Open tool at the following URL:
http://www.cisco.com/tac/caseopen
If you have Internet access, it is recommended that you open P3 and P4 cases through the Cisco TAC Web Site.
The Cisco TAC Escalation Center addresses issues that are classified as priority level 1 or priority level 2; these classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer will automatically open a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to the following URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled; for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). In addition, please have available your service agreement number and your product serial number.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2002, Cisco Systems, Inc.
All rights reserved.
Posted: Thu Sep 5 15:01:08 PDT 2002
All contents are Copyright © 1992--2002 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.