|
Table Of Contents
Release Notes for Cisco TV CDS 1.5.1.5.0
Getting a Software File from Cisco.com
Preparation for Software Upgrade
Important Notes for Upgrading from Release 1.5.1.4.0 to Release 1.5.1.5.0
Upgrade the Software on the CDSM
Upgrade the Software on Each Streamer and Vault
Script Enhancements for Asset Ingest Manager
Sample Configuration Files for Vaults and Streamers
/etc/sysconfig/network-scripts/ifcgf-eth0
/etc/sysconfig/network-scripts/ifcgf-eth1
/arroyo/test/streamer/setupfile
Disk Space and System Health Checks
System Health Checks (CServer)
System Health Checks (database)
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco TV CDS 1.5.1.5.0
These release notes cover Cisco TV CDS Release 1.5.1.5.0.
Revised: May 28, 2009, OL-19757-01Contents
The following information is in the release notes:
•Sample Configuration Files for Vaults and Streamers
•Disk Space and System Health Checks
•Obtaining Documentation and Submitting a Service Request
Enhancements
Release 1.5.1.5.0 introduces support for next-generation hardware platform, CDE110-2. CDS Manager application running on CDE110-2 offers higher scalability and performance characteristics than with the CDE100 platform. CDE110-2 also offers several resiliency enhancements such as redundant power supplies, reliable storage of the database and log files using RAID, and a reliable boot mechanism.
System Requirements
The Cisco TV CDS Release 1.5.1.5.0 runs on the CDE100, CDE110, CDE200, CDE300, and CDE400 hardware models. See the "Related Documentation" section for links to the documentation online.
Limitations and Restrictions
This release contains the following limitations and restrictions:
•Separation of RTSP messages from the management port has been implemented and is undergoing regression and longevity testing. This feature is certified, pending the results of the test cycle.
•The Parent-Child Service Groups Feature will be certified in a future release pending results of the test cycle.
Open Caveats
This release contains the following open caveats:
Vault
•CSCsw41047
Symptom:
Content storage on the Vaults can be unbalanced, causing some Vaults to reach capacity while other Vaults have available storage. This could cause the CDS to not be able to acquire new content.
Condition:
The Remotesmoothing feature is off by default.
Workaround:
Enable the Remotesmoothing feature by running the /proc/calypso/tunables/allowvaultremotesmoothing command on a Vault or add the following command to the /arroyo/test/vault/run file:
"echo 1 > /proc/calypso/tunables/allowvaultremotesmoothing "•CSCsy88266
Symptom:
The IP-Capture system was found in kernel debugger (KDB) mode.
Condition:
The back trace showed that the IP-Capture stopped during the "TrickGen::FixFrame" process.
Workaround:
Reboot the system.
Streaming
•CSCsu65569
Symptom:
If the resolv.conf file is not set up manually on the CDSM CDE100, the Reload Service Group command does not complete and streaming to service groups could be affected.
Condition:
The Reload Service Group command needs to reach the nameserver through a DNS search.
Workaround:
Make sure the DNS search is set up in resolv.conf and resubmit the Reload Service Group command through the CDSM GUI.
•CSCsu83085
Symptom:
Fast-forward and fast-rewind does not appear smooth to the human eye.
Condition:
This issue only occurs for AVC HD encoded content. It does not happen on all vendor STBs. Some STBs do not show any signs of poor fast-forward or fast-rewind for AVC HD content.
Workaround:
When Instantaneous Decoder Refresh (IDR) is set to "always," there is a big improvement. Try various STB vendors.
•CSCsy84731
Symptom:
When a stream destination is configured for multiple Stream Groups with the same priority, streams for the destination are only directed to Streamers in a single Stream Group.
Condition:
CDS-TV 1.5.1.x and later software filter out duplicate stream destination map entries with the same priority. As a result only the last group entry is used. In deployments where a stream may be streamed equally well from any group, CDS-TV instead only streams from a single group. This problem is encountered any time a new QAM device is added and configured with all Stream Groups having the same priority.
Workaround:
As a workaround, a script may be deployed by Cisco Technical Support to bypass the stream destination maps. Each time a QAM device is added the stream destination maps become affected again, so the script runs every minute as a cron job to make sure the stream destination maps are not affected.
SNMP
•CSCsx81833
Symptom:
A trap is not being generated and sent to trap recipient when a disk is taken offline. This is defined in the MIB as arDiskHealthDown trap.
Condition:
The trap should be sent when a drive is taken offline by CServer or if a drive is pulled from the array.
Workaround:
There is no workaround.
CDSM
•CSCsz30891
Symptom:
Running a large report will cause the database to direct all resources to processing the report and give the impression that the CDSM is unresponsive.
Condition:
This symptom is likely to happen when reports are run with extremely large data sets.
Workaround:
Run reports with smaller date ranges.
Resolved Caveats
The following caveats have been resolved since Cisco TV CDS Release 1.5.1.4.1. Not all the resolved issues are mentioned here. The following list highlights the resolved caveats associated with customer deployment scenarios.
CServer
•CSCsm43562
Mirroring may be prematurely held off when streaming in an ISV system.
•CSCsq93151
Loss of link on all adapters may cause remote mirror agent to misbehave.
•CSCsq97615
The remote mirror agent can get stuck trying to fix a mirror copy that has all of the data, but the length of the object is not known.
•CSCsr05721
Vault server goes into KDB mode when ingesting content that is missing a PMT.
•CSCsr44052
Server can run out of memory and crash. Requires unresponsive disk and much activity on low RAM system.
•CSCsv23925
Streams controlled from a server running Release 1.5.1.3 cannot play on a server running Release .5.1.4.0, and vice versa.
•CSCsv73174
FTP out content from a remote Vault may cause the memory reuse code to get confused.
•CSCsw74743
Server crashes trying to clean up backup control state of a destroyed stream that is in an inconsistent state due to a network partitioning event.
•CSCsw78314
Streams cannot be assigned to a Streamer that appears to have capacity.
•CSCsw86946
A stream application sent a destroy for a stream that had not completed its setup. This happened during a maintenance procedure and is a very rare case.
•CSCsx21555
Experiencing a burst of 232 errors and the ns_log file shows CheckIsaServices is probably stuck.
•CSCsy42252
Slow memory leak in Delta class when ingests are aborted due to bad content.
Database
•CSCsm27424
In certain stress scenarios the file system on the CDSM can fill up because of archival processes not being aggressive enough in deleting data.
•CSCsv55563
The database (avsdb) is stopped on a Vault, which means the Vault should not perform any ingests. No matter if RTI or MOD. The issue was seen in the RTI initially but fixed for both RTI and MOD.
•CSCsv93954
The asm-archiver takes a long time to run and does a full table scan inappropriately, this could exhaust the system of resources and cause a database failure.
•CSCsx59732
Startover content ingestion caused a slow leak of file descriptors on the system. Eventually, the system ran out of file descriptors and the database was not accepting new connections and crashed.
•CSCsx59974
An enhancement request was made that if the database should fail on the master Vault, the master services moves to another Vault.
•CSCsz23362
The Streamer references freed memory and crashes unpredictably. This occurs during a very small window where a pending play is not canceled prior to deleting a stream's local play state.
•CSCsz33510
Drives used for TV CDS caching (Streamers, Caching Nodes, and Vaults) may falsely get removed during a network partitioning event.
Streaming
•CSCsr68629
Tricks display black or freeze-frame on certain STBs. The content still moves through the 1x file as you fast-forward or rewind, but the tricks themselves simply display black while they are on screen.
•CSCsx22125
Experiencing a burst of 232 errors. The problem is due to bad encoding of the video feed.
CDSM
•CSCsr81309
When adding QAM devices, the system does not automatically use the configuration created for them.
•CSCsu43584
Stream Reporting roll-up shows the timestamp of the posting of the stream destroy and not the actual LSCP stream destroy command.
•CSCsw32146
During a software upgrade from Release 1.4.4 to Release 1.5.1, a failure was seen when attempting to convert the service group and TSID information.
•CSCsw91767
The log archiver feature manages the system disk space and provides a location to archive older logs. This feature runs based on log file size. When the DEBUG level is set, the ISA log files grow fast. The archiver has to do more work, and during high volumes, this can cause some delays in stream setup.
•CSCsx32419
The asm-archiver seems to take longer and longer to run and eventually causes the CDSM to appear halted.
•CSCsx76140
The CDSM can appear unresponsive. Attempting to connect to the CDSM causes the web browser to hang and eventually the browser times out.
ISA
•CSCsu26756
The FTP pull ingests fail with the FileZilla FTP server. The ContentStore (slave) can not parse header information coming in as two TCP segments.
•CSCsv02114
The issue is caused if the ISA-based backoffice has problems with Naming or Notification Services. If the services keep stopping and restarting, then there could be some race condition in registering the CDS (ISA) services and recreating the event channels. The race condition causes some errors, which causes the run_isa to lock up.
•CSCsw19924
The BMS can re-use a cached connection (network socket) and it will timeout because CDS will not respond to the request. This causes a 5070 error, session timeout on the LSCP Proxy.
•CSCsw94184
When the master Vault is performing most of the RTIs, running the ps -ef | grep CalypsoContentStoreMaster | wc command shows a very large number l(64 or larger).
•CSCsy19090
A new thread is created by the ContentStore (master) service for each live ingest connection. If the Sectamus drops the FTP control connection, the thread associated to the connection should be released and all the resources associated with it should also be released. The thread is getting released but it does not clean the database connection it has created, so it is causing the database connection (file desc) leak, which could go up to 65K (max limit) in few months.
•CSCsy25914
When the primary Streamer goes into KDB mode at the same time the ContentStore service is finding out the sessions associated with some deleted content, the content store thread gets stuck. This causes the list of deleted content to keep growing, and eventually the list takes up all the storage capacity.
•CSCsy33065
When the Sectamus closes the control connection, the thread on the Content Store (master) just spins on the broken connection. This results in one of the ContentStore (master) services taking too much of the CPU.
•CSCsy56849
A condition exists where a client pauses the stream at STB, which pauses the stream at the Streamer. The STB is reset or the connection is broken, the stream on the Streamer becomes orphan.
Vault
•CSCsu93982
A Vault can go out of service if another Vault in the deployment is not unreachable for hours.
•CSCsx04705
FTP out connections may hang and if enough connections hang the maximum allowed FTP sessions is exceeded.
•CSCsy26946
A faulty drive can falsely cause the system to trap.
Drivers
•CSCsy49208
At random times SCSI drives attached to the same controller are removed from the system. Servers using the Adaptec SCSI controller may at random times experience errors requiring the SCSI bus to be reset. Unfortunately, a bus reset may take too long or cause the bus to hang. This results in all the SCSI drives on the controller being reset, to get removed.
New Installation Procedure
This section describes the new installation procedure for Release 1.5.1.5.0.
To install the software, do the following:
Step 1 Mount the ISO image on /mnt/cdrom.
mount <iso> /mnt/cdrom -t iso9660 -o ro,loop=/dev/loop0Step 2 You are asked for confirmation that you want to mount the ISO image. Enter the characters requested to continue.
Step 3 Run the installation script for the Content Delivery Application (CDA) you want to install (Vault, Streamer, ISV, CDSM).
Following is the installation steps for a Vault server:
[root@vault167 cdrom]# cd /mnt/cdrom[root@vault167 cdrom]# ./inst.sh vault isa
Server is VaultYou are installing CDS image, this will over-write what ever CDS you may haveDo you want to continue installation ? enter "azxHUYkH" to continue: azxHUYkH
#Unpacking the RPM files#Mon Jun 16 14:48:49 PDT 2008package wu-ftpd-2.6.2-5 is already installedpackage ethereal-base-0.9.7-1.7.2 is already installedpackage ethereal-gtk+-0.9.7-1.7.2 is already installedpackage ethereal-usermode-0.9.7-1.7.2 is already installedpackage ethereal-gnome-0.9.7-1.7.2 is already installedpackage ethereal-kde-0.9.7-1.7.2 is already installed#Unpacking more RPM files#Mon Jun 16 14:48:55 PDT 2008#Un-taring the base.tgz#Mon Jun 16 14:48:55 PDT 2008executing forprod from install cleanRunning Forprod.shMon Jun 16 14:49:10 PDT 2008Server is Vaultroot@Vault167 cdrom]Following is the installation steps for a Streamer server:
[root@streamer168 cdrom]# cd /mnt/cdrom[root@streamer168 cdrom]# ./inst.sh streamer isa
Server is streamerYou are installing CDS image, this will over-write what ever CDS you may haveDo you want to continue installation ? enter "azxHUYkH" to continue: azxHUYkH
#Unpacking the RPM files#Mon Jun 16 14:48:49 PDT 2008package wu-ftpd-2.6.2-5 is already installedpackage ethereal-base-0.9.7-1.7.2 is already installedpackage ethereal-gtk+-0.9.7-1.7.2 is already installedpackage ethereal-usermode-0.9.7-1.7.2 is already installedpackage ethereal-gnome-0.9.7-1.7.2 is already installedpackage ethereal-kde-0.9.7-1.7.2 is already installed#Unpacking more RPM files#Mon Jun 16 14:48:55 PDT 2008#Un-taring the base.tgz#Mon Jun 16 14:48:55 PDT 2008executing forprod from install cleanRunning Forprod.shMon Jun 16 14:49:10 PDT 2008Server is streamerroot@streamer168 cdrom]#Following is the installation steps for a CDSM server;
[root@streamer168 cdrom]# cd /mnt/cdrom[root@streamer168 cdrom]# ./install-asm.sh controllerInstall ASM Controller System CTRL-C NOW if this is not an ASM Box! Tue Dec 2 16:44:25 PST 2008..<list of files in the tar files>...../sbin/asm-archiver ./sbin/streamclean_1513 /bin/cp: `/lib/libssl.so.4' and `/lib/libssl.so.2' are the same file /bin/cp: `/lib/libcrypto.so.4' and `/lib/libcrypto.so.2' are the same file Please reboot now! Installation completeUpgrade Procedure
The following procedures are covered in this section:
•Getting a Software File from Cisco.com
•Preparation for Software Upgrade
•Upgrade the Software on the CDSM
•Upgrade the Software on Each Streamer and Vault
Caution Basic understanding of the Linux command line and the vi editor are required for the completion of the software upgrade. Do not attempt the software upgrade if you are unfamiliar with the Cisco CDS products and the Linux command line and vi editor.
A high-level view of the CDS software upgrade procedure is as follows:
1. Upgrade CDSM to 1.5.1.5.0
2. Upgrade the Streamers in the "Control" sites first (sites that have Stream Groups with only a Control server), followed by the "Setup/Control" sites (sites that have Stream Groups with a Setup/Control server).
Use the following procedural order to upgrade the Streamers:
•Enable Server Offload on the server
•Upgrade to 1.5.1.5.0
•Reboot the server
•Disable Server Offload on the server
Repeat for every Streamer on the site starting with the "Available" Streamers, followed by the "Backup" Streamer, and ending with the "Primary" Streamer. To identify the Streamers, use the following command:
[root@s65 root]# cat /proc/calypso/status/streamer/resiliencyinfoStreamer Resiliency Info:Service Address: 172.22.98.50Control Service: Primary3. Upgrade all the Vaults using the same procedural order as the Streamers (offload, upgrade, reboot, and online). Start the Vault upgrade at the Control sites and the finish with the Setup/Control site.
Getting a Software File from Cisco.com
To get a software file from Cisco.com, do the following:
Step 1 Launch your web browser and enter the following URL:
http://tools.cisco.com/support/downloads/go/Redirect.x?mdfid=268438145
The Log In page is displayed.
Step 2 Log in to Cisco.com using your designated username and password. The Video and Content Delivery page is displayed, listing the available software products.
Step 3 Click Cisco Content Delivery Systems (CDS). The Downloads page is displayed.
Step 4 Click the Cisco Content Delivery Applications folder to expand it, and click the Cisco TV Application. The page refreshes and the software releases are displayed.
Step 5 Click the software release you want. The page refreshes and the software image files are displayed.
Step 6 Click the link for the software image file you want.
•If this is the first time you have downloaded a file from Cisco.com, the Cisco Systems Inc., Encryption Software Usage Handling and Distribution Policy is displayed. Read the policy, fill in the unfilled fields, and click Accept.
•If you previously filled out the Encryption Software Usage and Handling and Distribution form, the form does not display again.
The Download page is displayed with the information about the software image file and a Download link.
Step 7 Click Download. The Cisco End User Software License Agreement is displayed.
Step 8 Read the agreement and click Agree. The File Download dialog box is displayed.
Step 9 Click Save. The Save As dialog box is displayed.
Step 10 Navigate to the location where you want to save the file and click Save. The file downloads.
Preparation for Software Upgrade
Note The preparation procedure should occur three to four hours before starting the software upgrade.
Caution It is mandatory that you check each server for available space in the root and /arroyo directories, as well as check each server for overall system health.
A minimum of 2GB of space must be available in the root (/) and /arroyo directories. To check the disk space availability, use the df -h command.
If needed, archive any log files greater than one month old, delete or copy over any core.* files from the /home/isa directory, and delete or copy over any database backups. Failure to perform these steps could result in a failure of the upgrade script. See the "Disk Space and System Health Checks" section.
Note Release 1.5.1.5.0 supports content ingested using earlier releases.
Important Notes for Upgrading from Release 1.5.1.4.0 to Release 1.5.1.5.0
When upgrading from Release 1.5.1.4.0 to Release 1.5.1.5.0, it is necessary to upgrade all the servers before bringing them online, and to delete all the report files on the CDSM.
Best Practice for preparing the CDSM for upgrade from 1.5.1.4.0 to 1.5.1.5.0 includes archiving all CDSM database files and removing the reporting database files to decrease the CDSM database downtime. This task can happen as early as one day prior to the upgrade. We also need to move any backup folders in /arroyo/db to /arroyo prior to running any CDSM backup or upgrade scripts.
The Reporting Database files are as Follows:
•/arroyo/db/asmaudit.db
•/arroyo/db/cntrpt.db
•/arroyo/db/cvrecordrpt.db
•/arroyo/db/msa_unprocessed.db
•/arroyo/db/rpt.db
•/arroyo/db/sfail.db
•/arroyo/db/tm.db
The /arroyo/db/tm.db file should be removed prior to restarting the CDSM database after the upgrade. Any of the reporting database files that are greater than 2GB should also be removed prior to restarting the CDSM database after upgrade.
•Downtime starts from the time that the 1.5.1.4.0 Master Streamer is placed into TRICKLE_DOWN until the time the first 1.5.1.5.0 Vault and Streamer are configured from the upgraded CDSM and come up as Content Store Master, Stream Setup, and Control Primary. The CDSM is upgraded after all but the 1.5.1.4.0 Master Vault and Master Streamer have been updated with the new 1.5.1.5.0 software.
•CDSM configuration and database files must be backed up manually.
•CDSM must be upgraded to Release 1.5.1.5.0 before configuration files for 1.5.1.5.0 servers can be changed.
•Release 1.5.1.5.0 supports content ingested by a prior CDS software release.
Preparation Procedure
To prepare each CDS server for the software upgrade, do the following:
Step 1 Log in to each server as root, and check for enough disk space
df -h /arroyo/You need approximately 2GB of unused disk space. This allows for the database backups performed during the software upgrade. For more information on checking disk space and system health, see the "Disk Space and System Health Checks" section.
Step 2 Copy the ISO image file you downloaded in the "Getting a Software File from Cisco.com" procedure to the root directory on the server.
Step 3 Delete the rpt.db file, all the index files, and all the replay logs.
a. Change to the /home/isa/Berkeley folder.
# cd /home/isa/Berkeleyb. Stop the database.
# db_shutdownc. Ensure the database has stopped.
# netstat -an | grep avsdbd. Remove the rpt.db file, the index files, and the replay logs.
# rm -f *.idx rpt.db *.*.*.*Step 4 Collect the configuration information on the existing system.
Use the CDSM to find the following configuration settings on each server and write them down:
•Management IP address
•Gateway IP address
•Network mask
•Stream ID
•Stream Group ID
•Name Service IP address
•Ingest IP address
•Service Groups
Write down any other configuration settings as necessary. If the CDSM is not available, collect the configuration information from the configuration files on each server. For more information on the configuration files, see the "Sample Configuration Files for Vaults and Streamers" section.
Upgrade the Software on the CDSM
Note The CDSM upgrade script does the following:
•Stops the database and the apache server before upgrading the software.
•Prompts you to make a backup of the CDSM.
•Prompts you to delete the replay log files and the index files.
•If you decide to make a backup, one tar archive file is created.
To upgrade the software on the CDSM, do the following:
Step 1 Log in to the CDSM Linux operating system as root.
Step 2 Mount the ISO image on /mnt/cdrom and run the install script.
# mount <iso_image> /mnt/cdrom -t iso9660 -o ro,loop=/dev/loop0# cd /mnt/cdromStep 3 Upgrade the CDS software on the CDSM by entering the following command.
# ./install-asm.sh controller upgradeInstall ASM Controller System CTRL-C NOW if this is not an ASM Box!Mon Dec 8 20:36:37 PST 2008Server is controllerStopping databaseStopping apache webserverDo you want to remove index and replay files? [yes|no]yesRemoving index filesRemoving replay filesDo you want to take a backup of the system? [yes/no]yesCreating backup archive.../arroyo/cdsm_120808_2036.tar.gzBackup is successful. The backup is saved as /arroyo/cdsm_120808_2036.tar.gzInstalling package.../bin/cp: `/lib/libssl.so.4' and `/lib/libssl.so.2' are the same file/bin/cp: `/lib/libcrypto.so.4' and `/lib/libcrypto.so.2' are the same filePlease reboot now!Installation is completed.Step 4 Reboot the CDSM.
# rebootStep 5 Verify that the database is running on the CDSM.
ps -ef | grep avsdb
Upgrade the Software on Each Streamer and Vault
Perform this procedure for each Vault and Streamer in the CDS.
Note In a multi-site CDS, upgrade the Streamers in the "Control" sites first (sites that have Stream Groups with only a Control server), followed by the "Setup/Control" sites (sites that have Stream Groups with a Setup/Control server).
In a multi-site CDS, upgrade all the Vaults using the same procedural order as the Streamers (offload, upgrade, reboot, and online). Start the Vault upgrade at the Control sites, then finish with the Setup/Control site.
Note The upgrade script does the following:
•Stops the database before upgrading the software.
•Prompts you to make a backup.
•Prompts you to delete the replay log files and the index files.
•If you decide to make a backup, a backup directory is created.
To upgrade the software on a Vault or Streamer, do the following:
Step 1 Using the CDSM GUI, offload the server.
a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed.
b. From the Server IP drop-down list, choose a server's IP address or nickname and click Display. The server type and ID, as well as the array ID, are displayed.
c. Select Enable and click Submit.
Step 2 Check the CDSM to verify that the stream count on the offline server is zero.
a. Using the CDSM, click Monitor > Server Level > NIC Monitor.
b. From the Server IP drop-down list, choose a server and click Display.
c. Click Graph Ports to view any stream traffic.
Step 3 Log in to the Vault or Streamer Linux operating system as root.
Step 4 Mount the ISO image on /mnt/cdrom.
# mount <iso_image> /mnt/cdrom -t iso9660 -o ro,loop=/dev/loop0# cd /mnt/cdromStep 5 Upgrade the CDS software on the Streamers and Vaults by entering the following commands.
To Upgrade the CDS Software on a Streamer:
[root@streamer117 cdrom]# ./inst.sh streamer isa upgrade
Server is streamerUpgrading from cur-1.5.1.4.1 to cur-1.5.1.5.0press y to continue..y
Killing avsdb and statsdkill 8509: No such processkill 8514: No such processRunning Upgrade Installation......Do you want to take a backup of the current system snapshot? enter (y/n) y
Enter the directory for backup relative to /arroyo (default: backup.12-08-08):Backup being saved to the default directory backup.12-08-08Creating /arroyo/backup.12-08-08 directory..Removing replay filesBackup done in /arroyo/backup.12-08-08Backup done .#Start installing new version cur-1.5.1.5.0##Unpacking the RPM files#Mon Jun 16 13:04:34 PDT 2008package wu-ftpd-2.6.2-5 is already installedpackage ethereal-base-0.9.7-1.7.2 is already installedpackage ethereal-gtk+-0.9.7-1.7.2 is already installedpackage ethereal-usermode-0.9.7-1.7.2 is already installedpackage ethereal-gnome-0.9.7-1.7.2 is already installedpackage ethereal-kde-0.9.7-1.7.2 is already installed#Unpacking more RPM files#Mon Jun 16 13:04:44 PDT 2008#Un-taring the base.tgz#Mon Jun 16 13:04:44 PDT 2008executing forprod from upgradeRunning Forprod.shMon Jun 16 13:05:21 PDT 2008Server is streamerWARNING: ---------------------------------------------------WARNING: configured to boot from /dev/hda1WARNING: if this is not correct, update /boot/grub/grub.confWARNING: configured to boot from /dev/hda1WARNING: if this is not correct, update /boot/grub/grub.confWARNING: ---------------------------------------------------mknod: `/dev/calypso': File exists#Please reboot now!#Kernel InstalledInstallation complete[root@streamer117 cdrom]#To Upgrade the CDS Software on a Vault:
[root@Vault167 cdrom]# ./inst.sh Vault isa upgrade
Server is VaultUpgrading from cur-1.5.1.4.1 to cur-1.5.1.5.0press y to continue..yKilling avsdb and statsdkill 914: No such processkill 31522: No such processkill 31529: No such processRunning Upgrade Installation......Do you want to take a backup of the current system snapshot? enter (y/n) yEnter the directory for backup relative to /arroyo (default: backup.12-08-08):Backup being saved to the default directory backup.12-08-08Creating /arroyo/backup.12-08-08 directory....../etc/sysconfig/network-scripts/ifcfg-eth2 does not exist............Removing index filesRemoving replay filesBackup done in /arroyo/backup.12-08-08Backup done .#Start installing new version cur-1.5.1.5.0##Unpacking the RPM filesMon Dec 8 16:07:21 PST 2008package wu-ftpd-2.6.2-5 is already installedpackage ethereal-base-0.9.7-1.7.2 is already installedpackage ethereal-gtk+-0.9.7-1.7.2 is already installedpackage ethereal-usermode-0.9.7-1.7.2 is already installederror: failed dependencies:gnome-core >= 1.2 is needed by ethereal-gnome-0.9.7-1.7.2error: failed dependencies:kdebase >= 2.0 is needed by ethereal-kde-0.9.7-1.7.2#Unpacking more RPM files#Mon Dec 8 16:07:27 PST 2008#Un-taring the base.tgz#Mon Dec 8 16:07:27 PST 2008#Installing the kernel#executing forprod from upgradeRunning Forprod.shMon Dec 8 16:07:51 PST 2008Server is vaultWARNING: ---------------------------------------------------WARNING: configured to boot from /dev/hda1WARNING: if this is not correct, update /boot/grub/grub.confWARNING: ---------------------------------------------------mknod: `/dev/calypso': File existsln: `/etc/rc3.d/S87ntpd': File exists#Please reboot now!#Kernel InstalledInstallation completeStep 6 Using the CDSM GUI, reboot the server.
a. Click Maintain > Servers > Server Restart. The Server Restart page is displayed.
b. From the Server IP drop-down list, choose the IP address of the server and click Display.
c. From the Restart drop-down list, choose Yes and click Submit.
Step 7 Using the CDSM GUI, wait for the server to come online.
a. Click Monitor > System Health. The System Health page is displayed.
b. The colored boxes for the server should all be green.
Step 8 Using the CDSM GUI, disable Server Offload.
a. Click Maintain > Servers > Server Offload. The Server Offload page is displayed.
b. From the Server IP drop-down list, choose a server's IP address or nickname and click Display. The server type and ID, as well as the array ID, are displayed.
c. Select Disable and click Submit.
Step 9 Repeat this procedure for the rest of the Vaults and Streamers.
New Scripts and Commands
This section describes the new scripts and commands added to Release 1.5.1.x.x.
Script Enhancements for Asset Ingest Manager
To Verify that Asset Ingest Manager (AIM) is running on a Vault, enter the following command:
[root@Vault167 root]# /home/isa/IntegrationTest/show_calypso_services --aimTo stop AIM, enter the following command:
[root@Vault167 root]# /home/isa/IntegrationTest/stop_calypso_service -aimNew Commands in the CDSM
cdsm_tags
Prints the tags of the CDSM modules that are currently loaded.
cdsm_backup <archive_name>
Backs up the current CDSM system, which includes the CDSM software and the configuration files.
cdsm_restore <archive_name>
Restores the CDSM software and configuration files from the directory specified in the cdsm_backup command.
New Commands in the CDS
cds_tech
Retrieves the CDS server information necessary for TAC to assist you with your server. We recommend you log the output to a disk file.
cds_backup <directory>
Backs up the current CDS system, which includes the CDS software and the configuration files.
cds_restore <directory>
Restores the CDS software and configuration files from the directory specified in the cds_backup command.
[root@Vault167 root]# cds_restore Usage: restore <backup-dir> <directory> should be relative to /arroyo. [root@Vault167 root]# [root@Vault167 root]# cds_restore backup_1 in /arroyo/backup_1 restoring from /arroyo/backup_1 file ./etc/hosts into /etc/hosts restoring from /arroyo/backup_1 file ./etc/sysconfig/network into /etc/sysconfig/network restoring from /arroyo/backup_1 file ./etc/sysconfig/network-scripts/ifcfg-eth0 into /etc/sysconfig/network-scripts/ifcfg-eth0 restoring from /arroyo/backup_1 file ./etc/sysconfig/network-scripts/ifcfg-eth1 into /etc/sysconfig/network-scripts/ifcfg-eth1 restoring from /arroyo/backup_1 file ./etc/sysconfig/network-scripts/ifcfg-eth2 into /etc/sysconfig/network-scripts/ifcfg-eth2 restoring from /arroyo/backup_1 file ./etc/rc.d/rc.local into /etc/rc.d/rc.local restoring from /arroyo/backup_1 file ./etc/rc.d/rc.sysinit into /etc/rc.d/rc.sysinit restoring from /arroyo/backup_1 file ./etc/resolv.conf into /etc/resolv.conf restoring from /arroyo/backup_1 file ./etc/modules.conf into /etc/modules.conf restoring from /arroyo/backup_1 file ./usr/local/share/snmp/snmpd.conf into /usr/local/share/snmp/snmpd.conf restoring from /arroyo/backup_1 file ./arroyo/test into /arroyo/test restoring from /arroyo/backup_1 file ./home/isa/.arroyorc into /home/isa/.arroyorc restoring from /arroyo/backup_1 file ./home/isa/Berkeley into /home/isa/Berkeley restoring from /arroyo/backup_1 file ./home/isa/ISA.tar.gz into /home/isa/ISA.tar.gz restoring from /arroyo/backup_1 file ./home/stats into /home/stats [root@Vault167 root]#cds_tags
Prints the tags of CDS modules that are currently loaded
Sample Configuration Files for Vaults and Streamers
This section provides the following examples of the configuration files for the Vault and Streamer servers:
•/etc/sysconfig/network-scripts/ifcgf-eth0
•/etc/sysconfig/network-scripts/ifcgf-eth1
•/arroyo/test/streamer/setupfile
/etc/hosts
Vault
# Do not remove the following line, or various programs# that require network functionality will fail.# This is updated at 2007-02-21 for ISA end-to-end configuration127.0.0.1 localhost.localdomain localhost10.22.217.80 SessionGateway10.22.217.80 Metadata10.22.217.80 Asset10.22.217.80 NotificationServer10.22.217.80 NameServer192.168.100.109 rack109-ip110.22.216.109 rack109Streamer
# Do not remove the following line, or various programs# that require network functionality will fail.127.0.0.1 localhost.localdomain localhost# This is updated at 2007-02-21 for ISA end-to-end confoguration10.22.216.109 rack10910.22.217.80 SessionGateway10.22.217.80 Metadata10.22.217.80 Asset10.22.217.80 NotificationServer10.22.217.80 NameServer10.22.216.152 rack152/etc/sysconfig/network
Vault
NETWORKING=yesHOSTNAME='rack109'GATEWAY=10.22.216.1Streamer
NETWORKING=yesHOSTNAME='rack152'GATEWAY=10.22.216.1/etc/sysconfig/network-scripts/ifcgf-eth0
Vault
DEVICE='eth0'BOOTPROTO=staticIPADDR='192.168.100.109'NETMASK='255.255.255.0'ONBOOT='yes'Streamer
DEVICE=eth0BOOTPROTO=staticIPADDR='192.168.111.152'NETMASK='255.255.255.0'ONBOOT=yes/etc/sysconfig/network-scripts/ifcgf-eth1
Vault
DEVICE='eth1'BOOTPROTO=staticIPADDR='192.168.100.109'NETMASK='255.255.255.0'ONBOOT='yes'Streamer
DEVICE='eth1'BOOTPROTO=staticIPADDR='10.22.216.152'NETMASK='255.255.254.0'ONBOOT='yes'/etc/modules.conf
Vault
alias parport_lowlevel parport_pcalias eth0 e1000alias eth2 e1000 #for Vault or SSValias usb-controller usb-ohciStreamer
alias parport_lowlevel parport_pcalias eth0 bcm5700#alias eth1 bcm5700 #for Ingest on Vault or SSValias eth1 e1000 #for Management on Streamer#alias eth2 e1000 #for Management on Vault or SSValias usb-controller usb-ohci
Note The bcm5700 interface is only applicable to servers that have the ServerWorks chipset.
/etc/rc.sysinit
Vault
#!/bin/bash## /etc/rc.sysinit - run once at boot time## Taken in part from Miquel van Smoorenburg's bcheckrc.#insmod avsutil# Rerun ourselves through initlogif [ -z "$IN_INITLOG" ]; then[ -f /sbin/initlog ] && exec /sbin/initlog $INITLOG_ARGS -r /etc/rc.sysinitfi# If we're using devfs, start devfsd now - we need the old device names[ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev# Set the pathPATH=/bin:/sbin:/usr/bin:/usr/sbinexport PATH........................Streamer
#!/bin/bash## /etc/rc.sysinit - run once at boot time## Taken in part from Miquel van Smoorenburg's bcheckrc.#insmod avsutil# Rerun ourselves through initlogif [ -z "$IN_INITLOG" ]; then[ -f /sbin/initlog ] && exec /sbin/initlog $INITLOG_ARGS -r /etc/rc.sysinitfi# If we're using devfs, start devfsd now - we need the old device names[ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev# Set the pathPATH=/bin:/sbin:/usr/bin:/usr/sbin....................../arroyo/test/vault/run
dir=/arroyo/test/Vaultinsmod linuxIAL#insmod $dir/e1000.o and_interrupt_delay=1953$dir/startethcp $dir/setupfile $dir/requestfile /arroyo/testsleep 5insmod $dir/avs_cserver.o #16Gig Vault#insmod $dir/avs_cserver.o maxphysblocks=491520 #8Gig Vaultwhile !(test -d /proc/calypso/tunables); doecho "Waiting to configure avs_cserver"sleep 1doneecho 1 > /proc/calypso/test/readarptableecho 1 > /proc/calypso/test/arp_readroutingtableecho 1 > /proc/calypso/test/readremoteserversecho 1 > /proc/calypso/tunables/cm_configurationcomplete/arroyo/test/streamer/run
dir=/arroyo/test/streamerinsmod aic79xx$dir/startethcp $dir/setupfile $dir/requestfile /arroyo/testinsmod $dir/avs_cserver.owhile !(test -d /proc/calypso/tunables); doecho "Waiting to configure avs_cserver"sleep 1donesleep 15#echo 1 > /proc/sys/kernel/kdb_keyboard_break_onecho 1 > /proc/calypso/test/readstreamloadfileecho 1 > /proc/calypso/test/readarptableecho 1 > /proc/calypso/test/arp_readroutingtableecho 1 > /proc/calypso/test/readremoteserversecho 1 > /proc/calypso/tunables/cm_configurationcompletesleep 5/arroyo/test/vault/setupfile
# CServer core configuration. Changes to this file require# a server reboot.serverid 109groupid 199198ingest eth1management eth2localip 00a16d86dcache_dscp 38cache_ecn 0streamer 0 vault 1default source ip 192.169.106.1 tport 0 - 0 cport 0e1000 adapters: maxrate 965e1000 1: streaming 1 fill 1 ip 192.169.106.1 tport 0 cport 0 tgid 0e1000 2: streaming 1 fill 1 ip 192.169.106.2 tport 0 cport 0 tgid 0e1000 3: streaming 1 fill 1 ip 192.169.106.3 tport 0 cport 0 tgid 0e1000 4: streaming 1 fill 1 ip 192.169.106.4 tport 0 cport 0 tgid 0vault mirror copies 2trickspeedsv2 2 -2 6 -6 10 -10 60 -60ftpout if eth2 max utilization mbps 0 max sessions 0test 4/arroyo/test/streamer/setupfile
# CServer core configuration. Changes to this file require# a server reboot.serverid 152groupid 199198arrayid 1management eth1localip 00a16d898cache_dscp 38cache_ecn 0transport_dscp 46transport_ecn 0streamer 1 vault 0service address 10.22.216.198 setup 3300 control 9000bms address 10.22.217.80 5000default source ip 192.168.207.65 tport 0 - 0 cport 0e1000 adapters: maxrate 965e1000 1: streaming 1 fill 1 ip 192.169.106.41 tport 0 cport 0 tgid 0e1000 2: streaming 1 fill 1 ip 192.169.106.42 tport 0 cport 0 tgid 0e1000 3: streaming 1 fill 1 ip 192.169.106.43 tport 0 cport 0 tgid 0e1000 4: streaming 1 fill 1 ip 192.169.106.44 tport 0 cport 0 tgid 0e1000 5: streaming 1 fill 1 ip 192.169.106.45 tport 0 cport 0 tgid 0e1000 6: streaming 1 fill 1 ip 192.169.106.46 tport 0 cport 0 tgid 0e1000 7: streaming 1 fill 1 ip 192.169.106.47 tport 0 cport 0 tgid 0e1000 8: streaming 1 fill 1 ip 192.169.106.48 tport 0 cport 0 tgid 0e1000 9: streaming 1 fill 1 ip 192.169.106.49 tport 0 cport 0 tgid 0e1000 10: streaming 1 fill 1 ip 192.169.106.50 tport 0 cport 0 tgid 0e1000 11: streaming 1 fill 1 ip 192.169.106.51 tport 0 cport 0 tgid 0e1000 12: streaming 1 fill 1 ip 192.169.106.52 tport 0 cport 0 tgid 0test 4/home/isa/.arroyorc
Vault
# Local settingsself 1groupid 199198serverid 109partno 4U-SATA-1mirroring 0mgmtif 2ingestif 1nohealth 1# Database Paramsdbdomsock /tmp/isadbdbnetport 9999# Replication Group Membersstreamer 10.22.216.152streamer 10.22.216.197vault 10.22.216.111controller 10.22.216.85Streamer
# Local settingsself 2groupid 199198serverid 152partno 3U-SCSI-1mirroring 0mgmtif 1ingestif 1nohealth 1# Database Paramsdbdomsock /tmp/isadbdbnetport 9999# Replication Group Membersstreamer 10.22.216.197vault 10.22.216.109vault 10.22.216.111controller 10.22.216.85/etc/rc.local
Vault
#!/bin/sh## This script will be executed *after* all the other init scripts.# You can put your own initialization stuff in here if you don't# want to do the full Sys V style init stuff.touch /var/lock/subsys/local# NOT FOR USE WITH LINDENHURST OR IBM. Please comment out setpci# NorthBridge Tunesetpci -s 0:0.0 cc.b=02# ISA Kernel Tuneecho 222217728 > /proc/sys/kernel/shmmaxecho 222217728 > /proc/sys/kernel/shmallecho 65535 > /proc/sys/fs/file-max# TCP Kernel Tuneecho "8388608" > /proc/sys/net/core/wmem_maxecho "8388608" > /proc/sys/net/core/rmem_maxecho "4096 65536 4194304" > /proc/sys/net/ipv4/tcp_wmemecho "4096 87380 4194304" > /proc/sys/net/ipv4/tcp_rmemecho 0 > /proc/sys/net/ipv4/tcp_sack/sbin/hdparm -d1 /dev/hdasu - isa - c "cd /home/isa/IntegrationTest; ./init_isa_env"# Streamer Only#/usr/bin/avslauncher >& /root/avslauncher.log&#/arroyo/test/streamer/run/arroyo/test/Vault/run#/arroyo/test/ssv/run# Streamer and Vault#su - isa -c "cd /home/isa/IntegrationTest; ./run_isa >& /home/isa/IntegrationTest/ns_log&"su - isa -c "cd /home/isa/IntegrationTest; ./run_isa --handle_orphan_streams >& /home/isa/IntegrationTest/ns_log&"# Streamer and Vault/home/stats/statsd -d eth0ntpdate 10.22.216.1Streamer
#!/bin/sh## This script will be executed *after* all the other init scripts.# You can put your own initialization stuff in here if you don't# want to do the full Sys V style init stuff.touch /var/lock/subsys/local# ISA Kernel Tuneecho 222217728 > /proc/sys/kernel/shmmaxecho 222217728 > /proc/sys/kernel/shmallecho 65535 > /proc/sys/fs/file-max# TCP Kernel Tuneecho "8388608" > /proc/sys/net/core/wmem_maxecho "8388608" > /proc/sys/net/core/rmem_maxecho "4096 65536 4194304" > /proc/sys/net/ipv4/tcp_wmemecho "4096 87380 4194304" > /proc/sys/net/ipv4/tcp_rmemecho 0 > /proc/sys/net/ipv4/tcp_sack/sbin/hdparm -d1 /dev/hdasu - isa - c "cd /home/isa/IntegrationTest; ./init_isa_env"# Streamer Only/usr/bin/avslauncher >& /root/avslauncher.log&/arroyo/test/streamer/run#/arroyo/test/vault/run#/arroyo/test/ssv/run# Streamer and Vault#su - isa -c "cd /home/isa/IntegrationTest; ./run_isa >& /home/isa/IntegrationTest/ns_log&"su - isa -c "cd /home/isa/IntegrationTest; ./run_isa --handle_orphan_streams >& /home/isa/IntegrationTest/ns_log&"# Vault & Streamer/home/stats/statsd -d eth0ntpdate 10.22.216.1/etc/grub.conf
Vault
# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE: You do not have a /boot partition. This means that# all kernel and initrd paths are relative to /, eg.# root (hd0,0)# kernel /boot/vmlinuz-version ro root=/dev/hda1# initrd /boot/initrd-version.img#boot=/dev/hdadefault=0timeout=10splashimage=(hd0,0)/boot/grub/splash.xpm.gztitle Linux (2.4.32avs)root (hd0,0)kernel /boot/vmlinuz-2.4.32avs ro root=/dev/hda1 console=tty0 console=ttyS0,115200 nmi_watchdog=1initrd /boot/initrd-2.4.32avs.imgtitle Red Hat Linux (2.4.18-3bigmem)root (hd0,0)kernel /boot/vmlinuz-2.4.18-3bigmem ro root=/dev/hda1initrd /boot/initrd-2.4.18-3bigmem.imgtitle Red Hat Linux-smp (2.4.18-3smp)root (hd0,0)kernel /boot/vmlinuz-2.4.18-3smp ro root=/dev/hda1initrd /boot/initrd-2.4.18-3smp.imgtitle Red Hat Linux-up (2.4.18-3)root (hd0,0)kernel /boot/vmlinuz-2.4.18-3 ro root=/dev/hda1initrd /boot/initrd-2.4.18-3.imgStreamer
# grub.conf generated by anaconda## Note that you do not have to rerun grub after making changes to this file# NOTICE: You do not have a /boot partition. This means that# all kernel and initrd paths are relative to /, eg.# root (hd0,0)# kernel /boot/vmlinuz-version ro root=/dev/hda1# initrd /boot/initrd-version.img#boot=/dev/hdadefault=0timeout=10splashimage=(hd0,0)/boot/grub/splash.xpm.gztitle Linux (2.4.32avs)root (hd0,0)kernel /boot/vmlinuz-2.4.32avs ro root=/dev/hda1 console=tty0 console=ttyS0,115200 nmi_watchdog=1initrd /boot/initrd-2.4.32avs.imgtitle Red Hat Linux (2.4.18-3bigmem)root (hd0,0)kernel /boot/vmlinuz-2.4.18-3bigmem ro root=/dev/hda1initrd /boot/initrd-2.4.18-3bigmem.imgtitle Red Hat Linux-smp (2.4.18-3smp)root (hd0,0)kernel /boot/vmlinuz-2.4.18-3smp ro root=/dev/hda1initrd /boot/initrd-2.4.18-3smp.imgtitle Red Hat Linux-up (2.4.18-3)root (hd0,0)kernel /boot/vmlinuz-2.4.18-3 ro root=/dev/hda1initrd /boot/initrd-2.4.18-3.imgDisk Space and System Health Checks
These checks should be performed prior to, and immediately after, any upgrade procedure to ensure system integrity and functionality.
Disk Space Checks
Step 1 Log in to the CDSM as root.
Step 2 Tail the log file using the following command:
tail -f /arroyo/tmp/monitor.logStep 3 Check the "Other Info:" section for LSP disk space availability.
Step 4 If there is less than 88% left on any server, log in to that server and enter the following commands:
cd /arroyo/archive/arroyo_log
rm -f *.log.<months older than 2 months in the past>*Two examples follow:
rm -f *.log.01*rm -f *.log.02*Step 5 Check the "Other Info:" section for ISP disk space availability.
Step 6 If there is less than 88% left, log in to that server and enter the following command:
find /home/isa/ -name core.*
Upload or remove any core files found.
System Health Checks (CServer)
Step 1 Log in to the CDSM as root.
Step 2 Tail the log file using the following command:
tail -f /arroyo/tmp/monitor.logStep 3 Look at the role column and verify that one master Streamer and one master Vault are listed.
Step 4 Verify the correct number of disks available on each server.
Step 5 Verify all Streamers are serving streams.
Step 6 Verify GOID counts on all Vaults.
System Health Checks (ISA)
Step 1 Log in to each server as user isa.
Step 2 Change to the IntegrationTest directory .
cdintStep 3 Verify all ISA services are running by entering the following command:
./show_calpyso_services
Step 4 Verify the Name Service and ISA Service checks are working by entering the following command:
tail -100f ns_log
System Health Checks (database)
Step 1 Log in to each server as user isa.
Step 2 Change to the Berkeley directory.
On Streamers and Vaults:
cddb
On the CDSM:
cd Berkeley
Step 3 Extract the contents of the Berkeley database on each server.
dumpDBStep 4 Verify that all keys files are synchronized with each other.
For Vault Servers and CDSM:
ctnobj.lst
For Stream Servers and CDSM
stmsvc.lst
svcgrp.lst
tsin.lst
tsout.lst
Step 5 Verify that all main.db files display the current date and are close in filesize.
Step 6 Check the /home/isa/Berkeley/LOG/logfile for any recent database errors.
Step 7 Check the /arroyo/log/avsdb.log.<today's date> for any recent database errors.
Documentation Updates
The following documents have been updated for this release:
•Cisco Content Delivery System Administrator's Guide
The following documents have been added for this release:
•Release Notes for Cisco TV CDS 1.5.1.5.0
Related Documentation
Refer to the following documents for additional information about the Cisco TV CDS 1.5.1.5.0:
•Cisco Content Delivery Engine 110 Hardware Installation Guide
http://www.cisco.com/en/US/docs/video/cds/cde/cde110/installation/guide/cde110_install.html
•Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide
http://www.cisco.com/en/US/docs/video/cds/cde/installation/guide/CDE_Install_Book.html
•Regulatory Compliance and Safety Information for Cisco Content Delivery Engine 100/200/300/400
http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html
•Cisco Content Delivery System Administrator's Guide
Available through the CDSM GUI.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS version 2.0.
CDE, CCENT, Cisco Eos, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way CCDE, CCENT, Cisco Eos, Cisco Lumin, Cisco Nexus, Cisco StadiumVision, the Cisco logo, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn is a service mark; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website 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. (0805R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.