Table Of Contents
Release Notes for Cisco TV CDS 1.5.1.4.0
Contents
Enhancements
System Requirements
Limitations and Restrictions
Release Files
Resolved Caveats
CDS
CDSM
New Installation Procedure
High-Level Installation Procedure
Installation Process
Getting a Software File from Cisco.com
Installing the Software on the CDSM
Installing the Software on the Streamer, Vault or SSV
Configuring Each Server for Management Access
Configuring the Content Delivery System Manager
Software Upgrade Procedure
Getting a Software File from Cisco.com
Preparing for the Upgrade
Server Offload of Vaults and Streamers
Upgrade Procedure—Vaults and Streamers
Upgrade Procedure—CDSM
Configuring the Vaults and Streamers Using the CDSM
Converting CDS System from Layer 2 to Layer 3
New Scripts and Commands
Script Enhancements for Asset Ingest Manager
New Commands in the CDSM
New Commands in the CDS
Sample Configuration Files for Vaults and Streamers
/etc/hosts
/etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcgf-eth0
/etc/sysconfig/network-scripts/ifcgf-eth1
/etc/modules.conf
/etc/rc.sysinit
/arroyo/test/vault/run
/arroyo/test/streamer/run
/arroyo/test/vault/setupfile
/arroyo/test/streamer/setupfile
/home/isa/.arroyorc
/etc/rc.local
/etc/grub.conf
Disk Space and System Health Checks
Disk Space Checks
System Health Checks (CServer)
System Health Checks (ISA)
System Health Checks (database)
Documentation Updates
Related Documentation
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco TV CDS 1.5.1.4.0
These release notes cover Cisco TV CDS Release 1.5.1.4.0.
Revised: January 28, 2009
Contents
The following information is in the release notes:
•
Enhancements
•System Requirements
•Limitations and Restrictions
•Release Files
•Resolved Caveats
•New Installation Procedure
•Software Upgrade Procedure
•New Scripts and Commands
•Sample Configuration Files for Vaults and Streamers
•Documentation Updates
•Related Documentation
•Obtaining Documentation and Submitting a Service Request
Enhancements
This section lists the enhancements to TV CDS 1.5.1.4.0.
•Enhancements to the Asset Ingest Manager (AIM)
•Handling of entitlement control messages (ECMs) in trick files
•Ability to use FTP out move content from any Vault to an FTP client
•Ability to use an ISV as a Vault configuration
•Ability to have multiple session gateways
•Ability to separate control and management traffic. In this release you can assign separate NIC interfaces to management traffic and control traffic. Management traffic such as session setup, session termination and message interaction between the backoffice and the CDSM are on one interfere, while control messages coming from the set-top boxes are on another interface.
•Enhancement to the scripts used to create backups, initially install the software, and set the software version
•RTSP enhancements for the DESCRIBE and GET_PARAMETER methods.
•Optimized trick file playback
System Requirements
The Cisco TV CDS Release 1.5.4.1 runs on the CDE100, CDE200, CDE300, and CDE400 hardware models. See the Cisco Content Delivery Engine CDE100/200/300/400 Hardware Installation Guide for set up and installation procedures. 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.
Release Files
Table 1 lists the software image files for Release 1.5.1.4.0.
Table 1 1.5.1.4.0 Software Image Files
Filename
|
File Size
|
File Date
|
r1.5.1.4.0.iso
|
184 MB
|
14-Jan-2009 16:10
|
cdsm_1514.iso
|
417 MB
|
14-Jan-2009 16:28
|
Resolved Caveats
The caveats listed in this section have been resolved in Release 1.5.1.4.0.
CDS
Table 2 lists the caveats related to the CDS software that were resolved in this release.
Table 2 Resolved Caveats—CDS Software
Reference Number
|
Description
|
CSCsj87057
|
FIELD:Hundreds of AVS_MPEG_DELIVERY_ERROR reported
|
CSCsi57457
|
FIELD: Albany arroyo/log continues to fill up server
|
CSCsj87050
|
FIELD:Error reported to the CDSM "STREAM_OBJECT_NOT_EXISTS"
|
CSCsi44238
|
FIELD: statsd - need to bounce statsd after bouncing database
|
CSCsk31884
|
Adding or removinga Vault damages content
|
CSCsk09306
|
Vault hit a control block; callback CPU utilization was too high for 10 seconds
|
CSCsk39569
|
Streamer hit assert "Control Block CPU util was too high for 10 sec"
|
CSCsk08022
|
Vault hit (startTimeInMilliseconds == 0) || (burstAheadTime == 0) failed
|
CSCsk12695
|
Vault hit "request->getStartDelayTime() == 0 || request->getBurst."
|
CSCsj25738
|
Streamer CPU0 lockup at IOX::Retransmitter::writeRttData
|
CSCsj44061
|
Streamer: support for multirate playlists
|
CSCsk13418
|
Streams dropped when the "Fill receive streams" hit to over 1.1Gbps
|
CSCsj91031
|
Streamer assert "revision[0] != StreamManager::REVISION_NOT_SUPPORTED"
|
CSCsj99487
|
Streamer hit "getOpaqueDataRevision() == op.getOpaqueDataRevision()"
|
CSCsk38006
|
Streamer hit "info.m_backupServerId != ROM::Monitor::getMyServerId()"
|
CSCsi78013
|
Setup/Control server not working after destroy streams
|
CSCsi84766
|
Stream Resiliency failure for double failover Motorola environment
|
CSCsi79002
|
SSV 1.5.1.1 crashed by Unable to handle kernel NULL pointer dereference
|
CSCsi87903
|
KDB: ReadRateControlBlock
|
CSCsi77828
|
Streamer KDB in !getStreamPlayLocal()->isStartPlayRequested()
|
CSCsk46879
|
Primary Streamer crashed "Kernel Null Pointer Dereference"
|
CSCsk38012
|
Streamer crashed by "NMI Watchdog detected LOCKUP on CPU2"
|
CSCsk09677
|
Streamer hit "m_controlServiceAddressManager->getBackupServer() != 0"
|
CSCsk10781
|
Streamer hit "Unable to handle kernel paging request at virtual address"
|
CSCsk10798
|
Streamer hit "m_remoteServerKnowsAboutMe ? m_isReachable : true" failed
|
CSCsk34155
|
Streamer crashed by "unable to handle kernel NULL pointer dereference"
|
CSCsk35221
|
Streamer hit "request->m_requesterServiceInfo.m_status == ..." failed
|
CSCsk39184
|
Streamer crashed "LOCKUP CPU3" at scheduleBadReceivePacketErrorReport
|
CSCsj03589
|
Remote smoothing not function as expected
|
CSCsj06419
|
Mirroring failed due to Defrag evaluator stuck at stopping
|
CSCsi79757
|
Local copy does not get cleaned up when copy count reduce.
|
CSCsk12372
|
ISA core dumped at Assertion `m_opaqueDataSetupRefCount != 0' failed
|
CSCsj44892
|
Failure to disable Service Group in SA-ASI mode
|
CSCsk42929
|
protocoltiminglog error: MirrorRecovery held off by ISA (95)
|
CSCsi91360
|
cserver not giving up writing even after receiving error 1
|
CSCsj74384
|
Lost 8 disk drives in one night from one of the streamer.
|
CSCsj75391
|
Many data waits and data lows on the Streamer
|
CSCsk18551
|
Hole filler agent hogging CPU
|
CSCsl35654
|
ISA ContentStore not handling the resume live ingest case correctly
|
CSCsl40098
|
ISA should recover the stream states if caching links are down
|
CSCso17213
|
Turn on LIVE_KLUDGE_FOR_STREAM_RELIENCY_SSV so that this code base can be used for resuming at live for a standalone ISV.
|
CSCso46290
|
Fix for cserver crash when number of unique content rates being played-back on streamer exceeds 32
|
CSCso55811
|
Vaults with 8 GB of memory occasionally exceed the maximum fill transmit bandwidth that can be tracked by reuse locks. This results in a divide-by-zero fault in the reuse-locks when the reuse code attempts and fails to release enough lock space to track a new fill transmit stream.
|
CSCso62256
|
Delay deletion of SC::StreamPlayLocal when embedded locate/select is still active.
|
CSCso56168
|
Backport: Optimized the fragment pattern that is written for the smaller reverse segments (One of the checks for triggering the write was using a local variable of type iooffset_t (32-bit) instead of offset_t (64-bit). This caused the compare with a 64-bit variable to be inaccurate.
|
CSCso51792
|
Merged changes applied to 1.5.1.3.2 to deal with network packet loss.
|
CSCso88133
|
If the delta file that is associated with the content being retrieved via ftp-out is corrupt or incomplete in some way, results in the Delta class recursing and requesting a buffer twice in a row.
|
CSCsq01270
|
Added a conditional REMOVE_OUTBOUND_BANDWIDTH_ADJUST which disables the calculation of an adjustment to outbound transmit bandwidth based on the 75% of the difference between the committed vs. actual outbound bandwidth consumed.
|
CSCsq04315
|
With much packet loss it is possible for much receive data to be delivered in a single call from the polling loop.
|
CSCso93545
|
Handle edge cases in receive Data (there used to be ASSERTs), if the data received is duplicate or overlapping existing data in the receive queue.
|
CSCso93545
|
Reset PackedLen and PackedDesc fields in Chained Descriptors when we do appends, splits, and discards.
|
CSCso95963
|
In removeDisk when disk is going away, we clear the outstandingDirectoryWriteBit and completedDirectoryWriteBit for the disk.
|
CSCso96019
|
where m_readRateControl can become null if the disk on which the firstAllocationUnit is gone and complete is called.
|
CSCso93545
|
In receiveData where the incoming chain of descriptors needs to be split, then reset the new split length for the split descriptor so it is correct when we process it in the next loop.
|
CSCso51792
|
Filling packets get lost
|
CSCso56140
|
Reduced bandwidth between Vault and streamer to 100 MB caused KDB on streamer.
|
CSCso62249
|
KDB on Vault due to extensive packet loss
|
CSCso62256
|
Similar to CSCso62249 . KDB on streamer caused by extensive packet loss
|
CSCso60458
|
Too many log message overran partition for loss messages
|
CSCso30980
|
Development Unit test validated - Stuck Notify Service
|
CSCso72394:
|
The StreamService got hung if the SetStreamInfo gets stuck
|
CSCso53142
|
Thread not waking up on SessionsPollTime timer when it set smaller
|
CSCso53100
|
orphan stream deleted while one session gateway is down
|
CSCso81817
|
LSCP Service to support VODLink client ()
|
CSCso83563
|
ResourceMgr failed to detect playTimeout streams on control site
|
CSCso63937
|
reload_service_group does not remove the deleted service group
|
CSCsq02133
|
CDSM Should toss out update after a receives teardown for a stream
|
CSCsl16214
|
Playing contents from Vaults is not distributed well to the streamers
|
CSCso51792
|
Network problems cause streamers to go into kdb
|
CSCso34800
|
DNS Push corrupts statsd which then corrupts remote server file
|
CSCsk83242
|
Streamer hit totalLengthInBytes!=1 by invalid diskwrite when tracksize is 1
|
CSCso62249
|
Vault hit "CALYPSO ASSERT: "handle != 0" failed due to extensive packet loss.
|
CSCso30980
|
The stuck NotifyService should not cause the CDS ISA services to stuck
|
CSCso38503
|
The StreamService does not come up if NotifyService does not respond
|
CSCso60458
|
Vault KDB during network testing Comcast Denver Lab
|
CSCso61526
|
Ingesting the same content under different name 500 times, creating three copies for 4 Vaults on two sites creates too many outstanding writes.
|
CSCsk83242
|
Streamer hit totalLengthInBytes!=1 by invalid diskwrite when tracksize is 1
|
CSCsq95255
|
Setup IP is configured as Control IP on ISV with separated interface
|
CSCsq80388
|
Service address for setup interface is configured for both setup/control
|
CSCsq28204
|
SA-CR:82371: AIM dbclient delete transaction failing to remove
|
CSCsq28216
|
SA-CR:80666: stunnel process is not running on cds Vault
|
CSCsq28222
|
SA-CR:82102: AIM Listener bind error
|
CSCsq75319
|
NMC: AIM fails when doing a update provision
|
CSCsq76666
|
NMC: AIM fails due to missing db records caused by other bug
|
CSCsq10513
|
NotificationService could stall StreamService
|
CSCso90650
|
CalypsoStreamService under master folder dumps core on reboot
|
CSCso71726
|
run_master_services should break the loop when testdb dumps core
|
CSCso69468
|
The CDSM should provide to configure the multiple session gateways
|
CSCso63222
|
Support for Parent/Child Service Groups in ASI mode
|
CSCsq69248
|
The testdb used by the bsql cores if file system is full
|
CSCso95717
|
testdb core dumped during bsql session
|
CSCsq61746
|
ISA overwrites shared memory for Opaque data after released
|
CSCsq48599
|
lscp server core dumped during streaming after bouncing ISA services
|
CSCsq87728
|
Separated Setup and Control: cores generated by CalypsoPlayStreamService
|
CSCsq84768
|
LSCP Service NOT up when control NIC is brought up after streamer was up
|
CSCsq54497
|
CalypsoStreamService segmentation fault
|
CSCsq87950
|
Separated setup and control: setup ip was not up after primary was down
|
CSCsq18177
|
Guards against defective NIC interface
|
CSCsq27516
|
OpaqueDataUpdate operation gets stuck when backup control server is down
|
CSCsq43291
|
After a live range request, play does not resume at proper offset
|
CSCsq43075
|
Memory leak with preencryption and failure to fill pmt or ecm packet
|
CSCsq43221
|
Need to support the injection of ECM/PMT or PMT-only
|
CSCsq79389
|
Changing Stream Interface IP addresses crashes cache drives
|
CSCvs02114
|
run_isa script can hang if Name/Notification Service does not respond
|
CDSM
Table 3 lists the caveats related to the Content Delivery System Manager (CDSM) GUI that were resolved in this release.
Table 3 Resolved Caveats—CDSM
Reference Number
|
Description
|
CSCsk62630
|
Monitor > Server Level > Services Monitor shows Arroyo for services.
|
CSCsk47402
|
Configure>Server Level>Route Tables - RoutingTable file gets wrong value
|
CSCsk45415
|
Configure>Serverlevel>ServerSetup> Vaultmirror/local copies
|
CSCsk45484
|
Configure>ServerLevel>ServerSetup> Vault server configure
|
CSCsi81527
|
Enabling server offload on Vault cause Vault to go OFFLINE
|
CSCsj11329
|
Fail stream does not have Session ID
|
CSCsj66138
|
Report: Stream Activity Bandwidth report does not take effect
|
CSCsk86069
|
Configure > Interface Setup - warn for Mgmt Intfc missing but Setup Pg
|
CSCsi64168
|
users should be able to enable Vault local mirror copies through CCDSM
|
CSCsi85807
|
Nice to have disk status display before disk rescan
|
CSCsi73836
|
When no records are available to report, it will be nice to say so
|
CSCsk68474
|
Configure > Array Level > Control/Setup - Remove C/SIP wipes out config
|
CSCsk70280
|
Configure > Array Level > Control/Setup - Submit dup IP Address OK
|
CSCsk64085
|
Configure > Server Level > Route Tables submit confirmed for no value
|
CSCsk40966
|
Configure>SystemLevel>QAM Gateway - group members link broken
|
CSCsk40970
|
Directory Listing viewable when URL is typed in browser.
|
CSCsj56496
|
Maintain: ISA services and Service group not take effect
|
CSCsj20166
|
Failure of SA-ASI mode TSID-OUT configuration
|
CSCsk43252
|
Stream Offload operation duplicate the service address line in setupfile
|
CSCsj19084
|
Failure of "disable" links in MQAM NSG Configuration UI
|
CSCsi75936
|
Delete button in Active Ingest Monitor is not working
|
CSCsj93786
|
Provider and Category Columns in Content Summary
|
CSCsk37828
|
Stream Group Preference is set to High for all stream groups by default
|
CSCsk37857
|
Configure >SystemLevel>QAM Gateway QAM MAC update accepts
|
CSCsk37959
|
Configure>SystemLevel>Headend Setup, remove Reset button
|
CSCsk43596
|
Configure>ArrayLevel>StreamGroups>delete group not updating all QAMs
|
CSCsj23807
|
SA-ASI mode movie order failure by "No ControlService"
|
CSCsl89030
|
Allows user to configure mirror copy count to 0
|
CSCso70803
|
The first "Server Setup" page better not showing anything
|
CSCso70880
|
Should not allow user select "stream" or "stream/cache" type for Vault
|
CSCso83846
|
Failed to create new QAM if select multiple stream grps at first time
|
CSCso83144
|
CDS Server IP was removed from server list in page Server Setup CONFIG
|
New Installation Procedure
Note You must connect a monitor and PS/2 keyboard directly to the CDE, because the installation process overwrites the following files in the /etc/sysconfig/network-script/ directory which affects network connectivity. These files are the ifcfg-eth0, ifcfg-eth1, and ifcfg-eth2 files.
Caution The installer must be familiar with the CDS, the Linux operating system, and have an understanding of the Linux command line (including the vi editor).
All server management connections must be network reachable at the time of configuration.
There are sample 1.5.1.4.x configuration files in the "Sample Configuration Files for Vaults and Streamers" section for later comparison. The hostType is Vault, Streamer, or an SSV.
High-Level Installation Procedure
1. Each server must have Linux (RedHat Vallhala 7.3) installed.
2. The CDSM ISO image is copied onto the /arroyo partition, mounted, and installed on the management server, and the server is rebooted.
3. The CDS ISO image is copied onto the /arroyo partition, mounted and installed on each server, and server is rebooted.
4. All systems are configured using the CDSM GUI.
Installation Process
The installation process consists of the following tasks:
•Getting a Software File from Cisco.com
•Installing the Software on the CDSM
•Installing the Software on the Streamer, Vault or SSV
•Configuring Each Server for Management Access
•Configuring the Content Delivery System Manager
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://www.cisco.com/kobayashi/sw-center/sw-video.shtml
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.
Installing the Software on the CDSM
To install Release 1.5.1.4.0 on the CDSM and use the CDSM as the source for the ISO file, do the following:
Step 1 Copy the necessary files from the USB flash drive or the USB CD-ROM.
a. Copy cdsm_1514.iso and r1.5.1.4.0.iso to a USB flash drive, or create a data CD-ROM for each iso file. Do not us the "Create Disk from Image" option.
b. Mount the USB flash drive containing the release ISO image files on to the CDSM.
a. mkdir /mnt/usbstick
b. Insert the USB flash drive into the USB port on the front of the CDSM.
c. mount /dev/sde1 /mnt/usbstick
d. Copy the files from /mnt/usbstick to /arroyo/
e. umount /mnt/usbstick
c. Mount the CD-ROM containing release ISO image files.
a. mkdir /mnt/cdrom
b. Insert the CD in the CD-ROM drive on the CDSM.
c. mount /dev/cdrom /mnt/cdrom
d. Copy the ISO image files from /mnt/cdrom/*.iso to the /arroyo/ directory.
e. umount /mnt/cdrom
Step 2 Mount and install the CDSM overlay, then configure the CDSM.
a. Mount the CDSM ISO image and install it.
a. mount -o loop /arroyo/cdsm_15410.iso /mnt/cdrom
b. cd /mnt/cdrom
c. ./install-asm.sh
b. Edit the network files on the CDSM.
a. Log in as user root.
b. Edit the /etc/hosts file and add the IP address and host name of the server. Make sure you remove any extraneous host names in the line (that includes the loopback and localhost entries).
c. Edit the /etc/sysconfig/network file and add the proper hostname and gateway.
d. Edit the /etc/sysconfig/network-scripts/eth0 file and add the correct values.
c. Edit the .arroyorc file as user isa.
a. Make sure that "self" line is set to the right value (3 for CDSM).
b. Make sure that the "groupid" and "serverid" lines are correct.
The "groupid" line must be the same for each server in the group.
The "serverid" line must be unique. A good practice is to use the last octet of the management IP address.
c. Make sure that "partno" line is correct. For a CDSM it is 1U-SATA-1.
d. Add a line to the CDSM .arroyorc file that says, "nohealth 1"
e. Make sure that all replication members are declared.
Note Make sure the IP address of the local server is not in .arroyorc file.
d. Make sure the database is running. There should be the command `su - isa' in the /etc/rc.local file. The easiest way to do this to log in as user isa.
a. su - isa
b. exit
e. Make sure the web service is running. There should be the command `apachectl start' in the /etc/rc.local file. The easiest way to do this is to open a browser and enter the IP address of the CDSM into the address text box. If the Arroyo CDSM login page does not come up, log in as user root and run the /arroyo/www/bin/apachectl start command.
f. If this is the first time the CDSM has been started, log in as user root and run the /usr/lib/php4/runonce command. This loads the default values and logins for the CDSM GUI.
g. Modify the /etc/rc.local and uncomment the su - isa -c "cd /arroyo/db" line and the /arroyo/www/bin/apachectl start line under ASM Services Start section.
Installing the Software on the Streamer, Vault or SSV
To install the Release 1.5.1.4.0 software on a Streamer, Vault, or SSV, do the following:
Step 1 Network the system and copy the ISO file from the CDSM to each server.
a. Log in as user root.
b. Edit the hosts file (vi /etc/hosts) and enter the IP address and hostname of the server. Make sure you remove any extraneous host names in the line (that includes the loopback and localhost entries).
c. Edit the network file (vi /etc/sysconfig/network) and add the proper hostname and gateway.
d. Edit the configuration file for the management interface. For Streamers, Vaults and SSVs use the vi /etc/sysconfig/network-scripts/ifcfg-eth0 command. Make sure the file has the proper network settings.
e. Run the service network restart command.
f. Copy the ISO file from the CDSM to the server using the scp root@<cdsm ip>:/arroyo/r1.5.1.4.0.iso /arroyo/r1.5.1.4.0.iso command.
a. Enter "yes" at the security prompt.
b. When prompted, enter the user root password.
Step 2 Install the overlay contents.
Installation for Vault
mount r1.5.1.4.0.iso -t iso9660 -o loop /mnt/cdrom
[root@vault167 cdrom]# ./inst.sh vault isa
You are installing CDS image, this will over-write what ever CDS you may have
Do you want to continue installation ? enter "azxHUYkH" to continue: azxHUYkH
#Unpacking the RPM files#
Mon Jun 16 14:48:49 PDT 2008
package wu-ftpd-2.6.2-5 is already installed
package ethereal-base-0.9.7-1.7.2 is already installed
package ethereal-gtk+-0.9.7-1.7.2 is already installed
package ethereal-usermode-0.9.7-1.7.2 is already installed
package ethereal-gnome-0.9.7-1.7.2 is already installed
package ethereal-kde-0.9.7-1.7.2 is already installed
#Unpacking more RPM files#
Mon Jun 16 14:48:55 PDT 2008
Mon Jun 16 14:48:55 PDT 2008
executing forprod from install clean
Mon Jun 16 14:49:10 PDT 2008
Installation for Streamer
mount r1.5.1.4.0.iso -t iso9660 -o loop /mnt/cdrom
[root@streamer168 cdrom]# ./inst.sh streamer isa
You are installing CDS image, this will over-write what ever CDS you may have
Do you want to continue installation ? enter "azxHUYkH" to continue: azxHUYkH
#Unpacking the RPM files#
Mon Jun 16 14:48:49 PDT 2008
package wu-ftpd-2.6.2-5 is already installed
package ethereal-base-0.9.7-1.7.2 is already installed
package ethereal-gtk+-0.9.7-1.7.2 is already installed
package ethereal-usermode-0.9.7-1.7.2 is already installed
package ethereal-gnome-0.9.7-1.7.2 is already installed
package ethereal-kde-0.9.7-1.7.2 is already installed
#Unpacking more RPM files#
Mon Jun 16 14:48:55 PDT 2008
Mon Jun 16 14:48:55 PDT 2008
executing forprod from install clean
Mon Jun 16 14:49:10 PDT 2008
Installation for SSV
mount r1.5.1.4.0.iso -t iso9660 -o loop /mnt/cdrom
[root@streamer168 cdrom]# ./inst.sh streamer ssv
You are installing CDS image, this will over-write what ever CDS you may have
Do you want to continue installation ? enter "azxHUYkH" to continue: azxHUYkH
#Unpacking the RPM files#
Mon Jun 16 14:48:49 PDT 2008
package wu-ftpd-2.6.2-5 is already installed
package ethereal-base-0.9.7-1.7.2 is already installed
package ethereal-gtk+-0.9.7-1.7.2 is already installed
package ethereal-usermode-0.9.7-1.7.2 is already installed
package ethereal-gnome-0.9.7-1.7.2 is already installed
package ethereal-kde-0.9.7-1.7.2 is already installed
#Unpacking more RPM files#
Mon Jun 16 14:48:55 PDT 2008
Mon Jun 16 14:48:55 PDT 2008
executing forprod from install clean
Mon Jun 16 14:49:10 PDT 2008
Step 3 Reboot the server.
Configuring Each Server for Management Access
After the Release 1.5.1.4.0 overlay is installed and a server is rebooted, the serer must be configured so that the CDSM can connect to the server.
Note Once the CDSM is configured and the avsdb database is running you may proceed to prepare each server in the array.
To allow a server to communicate with the CDSM, do the following:
Step 1 Check the /etc/rc.local file and make sure the software is not yet set to start on boot.
a. Log in as user root.
b. Use the vi /etc/rc.local command to edit the rc.local file.
c. Locate the following lines and make sure they are commented out.
# su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
# /arroyo/test/streamer/run
# su - isa -c "cd /home/isa/IntegrationTest; ./run_isa --handle_orphan_streams >&
/home/isa/IntegrationTest/ns_log&"
# /home/stats/statsd -d eth0
d. Edit the network files on each server.
a. Log in as user root.
b. Edit the /etc/hosts file and add the IP address and host name of the server. Make sure you remove any extraneous host names in the line (that includes the loopback and localhost entries).
c. Edit the /etc/sysconfig/network file and add the proper hostname and gateway.
d. Edit the /etc/sysconfig/network-scripts/eth0 file and add the correct values.
e. Edit the .arroyorc file as user root (vi /home/isa/arroyorc).
a. Make sure that "self" line is set to the right value (0 for SSV, 1 for Vault, 2 for Streamer).
b. Make sure that the "groupid" and "serverid" lines are correct.
The "groupid" line must be the same for each server in the group.
The "serverid" line must be unique. A good practice is to use the last octet of the management IP address.
c. Make sure that "partno" line is correct.
For a 8GB Vault with 4 cache/fill ports: 4U-SATA-12
For a 8GB Vault with 6 cache/fill ports: 4U-SATA-11
For a 16GBb Vault with 8 cache/fill ports: 4U-SATA-10
For Streamers: 3U-SCSI-10
For 2U SSV: 2U-SATA-10 or 2U-SATA-11
d. Add a line to the CDSM .arroyorc file that says, "nohealth 1"
e. Make sure the management interface declaration is present and correct. For Streamers, Vaults, and SSVs the management interface is eth0.
f. Make sure that all replication members are declared.
Note Make sure the IP address of the local server is not in .arroyorc file.
g. Use the cds_backup /arroyo/1514-backup command to back up all these files, including the setup file.
Step 2 Start the database on the CDSM.
a. Log in to the CDSM.
b. Use the su - isa command. This switches the user to isa and starts the database.
c. Log out of the CDSM using the exit command.
Step 3 On each server start the statsd process.
a. Login as user root.
b. On the Streamer and the Vault, the command is /home/stats/statsd -d eth0.
Step 4 On each server, run the Config utility to set up some basic information in the databases.
a. Login as user root.
b. Use the /home/stats/svrinit_15 -h rack52 -i 10.11.116.52 -s 255.255.255.0 command.
Configuring the Content Delivery System Manager
Note The avsdb binary file on the CDSM (management controller) must be the same file as the avsdb binary file on each server.
In the CDSM GUI, to access context-sensitive online help, click the Help button in the top-right corner of the GUI.
Step 1 Create a user with an engineering access level.
a. Using your web browser, enter the IP address or hostname of your CDSM. The System Login page is displayed.
b. Log in as user admin with password admin and click Log In.
c. Click Maintain > Users > Add Users.
d. In the New User field, enter a user name.
e. In the Password field, enter a password.
f. From the Access drop-down list, choose Engineering.
g. Click Submit.
h. Click Logout.
Step 2 Log in to the CDSM GUI as the user with engineering access level. The CDSM Setup page is displayed.
Step 3 Initialize the CDS.
a. Click Submit, to save the initial CDSM setup.
b. From the Installation Type drop-down list, select the installation and click Submit.
c. Click Maintain > Software > System Configs. The System Configs page is displayed.
d. For the group map `1' field, set the value to "ISA OpenStream," click Submit.
e. In the License Map section, set the licensed streams field to "6000," and click Submit. The maximum streams for a single Stream Group is 6000.
f. In the Control IP Map section, set the control map name field to "CONTROLIPMAP:1," and the group IP field to "1," and click Submit.
g. Verify the settings on the System Configs page. All values should be listed in the left-panel.
Step 4 Configure each the interfaces for each server.
a. Click Configure > Server Level > Interface Setup.
b. From the Server IP drop-down list, select a server IP address and click Display. All servers that have been configured in the previous section are listed.
c. Set the interfaces for the server (Cache for the fill-only traffic, Stream/Cache for filling/streaming, and so on). On Streamers, eth1 is not used and should be set to general, eth0 is used for management. On Vaults, eth1 is for ingest, and eth0 is for management.
d. Click Submit to save the configuration changes. The Server Setup page is displayed. DO NOT CLICK ANY ITEM IN THE LEFT PANEL. Continue configuring the server using the Server Setup page to enter other information applicable to your network environment.
e. Once all the fields on the Server Setup page are configured, click Submit.
Step 5 Configure the routing for each server.
a. Click Configure > Server Level > Route Tables.
b. From the Server IP drop-down list, select a server IP address and click Display.
c. Enter the route table information for each server and click Submit.
d. In a Layer 2 environment you must set up the Streamer routing tables to be able to reach the QAM Gateways if the network does not find the QAM Gateways using ARP.
Step 6 Repeat Step 4 and Step 5 for each server in the array.
Step 7 Configure the ISA parameters for all Streamers.
a. Click Configure > Array Level > Streamer BMS
b. The Master Streamer IP field will be configured later in the Step 13.
c. Enter the settings as appropriate and click Submit. All fields should be set.
Step 8 Configure the ISA parameters for all the Vaults.
a. Click Configure > Array Level > Vault BMS.
b. Enter the settings as appropriate and click Submit. All fields should be set.
Step 9 Create Stream Groups.
a. Click Configure > Array Level > Stream Group.
b. From the drop-down list, select add new stream group and click Display
c. Enter the new group name and click Submit.
d. From the drop-down list, select the newly created group and click Display. A list of unassigned Streamers is displayed.
e. If you want to add a Streamer to this group, select the Stream Group from the Unassigned Streamers drop-down list associated with this Streamer and click Submit.
Step 10 Configure the QAM devices for the array.
a. Click Configure > System Level > QAM Gateway.
b. Enter the QAM IP address and the QAM MAC address, or leave the MAC address empty for multicast.
c. Select High or None to associate the QAM device to a Stream Group of Streamers and then click Submit.
d. Repeat Step 10 for each QAM device in this system.
Step 11 Configure the Headend Setup.
a. Configure Service Groups
b. Click Configure > System Level > Headend Setup.
c. Enter a value for the Service Group Number and click Submit.
d. After submitting the Service Group Number, management software creates a service group with the syntax "SVCGRP:n:1" or "SVCGRP:n:2."
Step 12 Configure Ingest Tuning. Select the desired Speeds and click "Submit"
Step 13 Configure the Control and Setup servers.
a. Click Configure > Array Level > Control /Setup IP. In Release 1.5.1.4.x, all session requests are sent to the primary Setup server, and stream play requests are sent to the Control server. The Control/Setup IP page allows you to configure primary Setup server. It is like Stream Master IP, in that it processes all the setup requests and then chooses which Streamer to use to play the session.
b. Enter the settings for the Control/Setup IP and Subnet Mask fields, select Control/Setup IP for the IP-Type and click Submit.
Step 14 Disable Server Offload for each server .
a. Click Maintain > Servers > Server Offload.
b. From the Server IP drop-down list, select an IP address and click Display.
c. Select Disable and click Submit.
d. Do this for each of the servers in the cluster
Step 15 Verify all configuration files have been updated.
a. Login as user root.
b. Use the ls -las /arroyo/test command on each server. There should be an ArpTable, RoutingTable, RemoteServers, StreamDestinationMap, and TranportGoupIdTable.
c. Use the ls -las /arroyo/test/streamer command on each Streamer. The - run, setupfile, starteth files should be updated.
d. Use the ls -las /arroyo/test/vault command on each Vault. The - run, setupfile, starteth files should be updated.
e. Use the la -las /arroyo/test/ssv command on each SSV. The - run, setupfile, starteth files should be updated.
Step 16 Activate the Release 1.5.1.4.0 servers.
Once the CDSM configuration is finished, each server should be brought up one at a time. On each server uncomment the following entries from /etc/rc.local file.
su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
/usr/bin/avslauncher >& /root/avslauncher.log& (Only on a Streamer)
/arroyo/test/<hostType>/run
su - isa -c "cd /home/isa/IntegrationTest; ......."
/home/stats/statsd -d eth0
Step 17 Reboot the server through the CDSM.
a. Click Maintain > Servers > Server Restart.
b. From the Server IP drop-down list, select an IP address and click Display.
c. From the Restart drop-down list, select yes" and click Submit.
d. Repeat Step 17 for each server.
Software Upgrade Procedure
Caution Basic understanding of Linux command line and "vi" are required for the completion of the upgrade. Do not attempt this upgrade if you are unfamiliar with the CDS Product, Linux OS, and/or the "vi" interface.
To minimize downtime, off load all servers but the current Vault and Stream Master Servers. After the upgrade, bring up one upgraded server at a time, starting with a Vault Server, followed by a Stream Server. Do not continue until these 2 servers have become Content Store Master and Stream Setup and Control Primary.
The following procedures are covered in this section:
•Getting a Software File from Cisco.com
•Preparing for the Upgrade (This should occur 6-12 hours before starting the upgrade)
•"Server Offload of Vaults and Streamers" section (This should occur 6 hours before starting the upgrade for the Vaults running Start Over and 3 hours before starting the upgrade for the Streamers. )
•Upgrade Procedure—Vaults and Streamers
•Upgrade Procedure—CDSM
•Configuring the Vaults and Streamers Using the CDSM
•Converting CDS System from Layer 2 to Layer 3
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://www.cisco.com/kobayashi/sw-center/sw-video.shtml
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.
Preparing for the Upgrade
(This should occur 6-12 hours before starting the upgrade)
Caution It is mandatory that all systems be checked for disk space availability on the "/" and "/arroyo" partitions as well as overall system health. If needed, archive any log files greater than one month old, delete/upload any core.* files off the root file system and delete/upload any database backups. Failure to perform these steps could result in a failure of the upgrade script. A minimum of 2GB of space should be available on the "/" and "/arroyo" file systems and can be checked with the command "df -h". See the
"Documentation Updates" section for more information.
Caution It is necessary for all backoffice content manipulation processes to be stopped during the upgrade. This includes, but is not limited to Start Over and normal content propagation.
Important Notes:
Best Practice for preparing the CDSM for upgrade 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 will start from the time that the 1.4.4.1.x Master Streamer is placed into TRICKLE_DOWN until the time the first 1.5.1.4.0 Vault and Streamer are configured from the upgraded CDSM and come up as Content Store Master and Stream Setup and Control Primary. CDSM will be upgraded after all but the 1.4.4.1.x Master Vault and Master Streamer have been updated with the new 1.5.1.4.0 software.
•CDSM Configuration and Database Files must be backed up manually.
•CDSM must be upgraded to the 1.5.1.4.0 release before configuration files for 1.5.1.4.0 servers can be changed.
•Version 1.5.1.4.0 of servers will support contents ingested on prior releases.
Step 1 Checking for disk space.
The df -h command can be run from the command line on each device.
You need approximately 2GB of free space (this accounts for the database backups done during the upgrade). If you do not have enough disk space, refer to the "Documentation Updates" section for guidelines on freeing more space.
Step 2 Uploading the upgrade files to the CDSM.
The CDSM is used as a jumping off point.
Step 3 Upload the upgrade files to each Vault and Streamer.
# scp -p <*.iso> <vault or streamer ip address>:/arroyo/
Repeat for each Vault and Streamer.
Server Offload of Vaults and Streamers
(This should occur 3 - 6 hours before starting the upgrade)
Use the CDSM GUI to identify the master Vault and master Streamer.
From the CDSM GUI, click Monitor > System Level > Services and select the IP address of one of the Vaults to display the running services. The "Cisco Content Store Master" service will be running on the Master Content Store. Repeat this process until you locate the Master Content Store.
Likewise, to locate the Master Stream Service repeat this process for the Streamers until you locate the Server with "Cisco Stream Service Master" running.
•Offload all but the master Vault server in a Start Over environment 6 hours before the scheduled maintenance window.
•Offload all but the master Vault and master Streamer in a non-Start Over environment 3 hours before the scheduled maintenance window.
To offload a server, do the following:
Step 1 Click CDSM Maintain > Servers > Server Offload.
Step 2 From the Server IP drop-down list, select the server to be offloaded and click Display.
Step 3 Select Enable and click Submit.
Step 4 Repeat for each server to be offloaded.
Upgrade Procedure—Vaults and Streamers
To upgrade a Vault or Streamer, do the following:
Step 1 Check the CDSM to verify that the stream count on the offloaded server is zero.
a. Click Monitor > Server Level > NIC Monitor.
b. From the Server IP drop-down list, select the IP address of the server and click Display.
c. Click Graph Ports to view any stream traffic.
Step 2 Log in to the server as root and comment out the following lines from /etc/rc.local file and reboot the server.
For a Streamer comment out:
#/arroyo/test/streamer/run
#su - isa -c "cd /home/isa/IntegrationTest; ./run_isa
handle_orphan_streams >>& /home/isa/IntegrationTest/ns_log&"
#/home/stats/statsd -d eth0
For a Vault comment out:
#su - isa -c "cd /home/isa/IntegrationTest; ./run_all >>&
/home/isa/IntegrationTest/ns_log&"
#/home/stats/statsd -d eth0
This will ensure that none of the CDS services are running after the system is rebooted.
Step 3 Change to the arroyo directory.
Step 4 Mount the .iso upgrade image
# mount r1.5.1.4.0.iso -t iso9660 -o loop /mnt/cdrom
Step 5 Change to the cdrom directory.
Step 6 Upgrade the server.
Streamer Upgrade
./inst.sh streamer isa upgrade
Upgrading from cur-1.4.4.1.8 to cur-1.5.1.4-rc6
kill 8509: No such process
kill 8514: No such process
Running Upgrade Installation......
Do you want to take a backup of the current system snapshot?
Enter the directory for backup relative to /arroyo (default:
backup.10-02-08): <enter>
Backup being saved to the default directory backup.10-02-08
Creating /arroyo/backup.10-02-08 directory..
#Unpacking the RPM files#
Mon Jun 16 13:04:34 PDT 2008
package wu-ftpd-2.6.2-5 is already installed
package ethereal-base-0.9.7-1.7.2 is already installed
package ethereal-gtk+-0.9.7-1.7.2 is already installed
package ethereal-usermode-0.9.7-1.7.2 is already installed
package ethereal-gnome-0.9.7-1.7.2 is already installed
package ethereal-kde-0.9.7-1.7.2 is already installed
#Unpacking more RPM files#
Mon Jun 16 13:04:44 PDT 2008
Mon Jun 16 13:04:44 PDT 2008
executing forprod from upgrade
Mon Jun 16 13:05:21 PDT 2008
WARNING: ---------------------------------------------------
WARNING: configured to boot from /dev/hda1
WARNING: if this is not correct, update /boot/grub/grub.conf
WARNING: configured to boot from /dev/hda1
WARNING: if this is not correct, update /boot/grub/grub.conf
WARNING: ---------------------------------------------------
mknod: `/dev/calypso': File exists
[root@streamer117 cdrom]#
Vault Upgrade
./inst.sh vault isa upgrade
Upgrading from cur-1.5.1.3.0 to cur-1.5.1.4-rc6
kill 8509: No such process
kill 8514: No such process
Running 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.10-02-08): <enter>
Backup being saved to the default directory backup.10-02-08
Creating /arroyo/backup.10-02-08 directory..
#Unpacking the RPM files#
Mon Jun 16 13:04:34 PDT 2008
package wu-ftpd-2.6.2-5 is already installed
package ethereal-base-0.9.7-1.7.2 is already installed
package ethereal-gtk+-0.9.7-1.7.2 is already installed
package ethereal-usermode-0.9.7-1.7.2 is already installed
package ethereal-gnome-0.9.7-1.7.2 is already installed
package ethereal-kde-0.9.7-1.7.2 is already installed
#Unpacking more RPM files#
Mon Jun 16 13:04:44 PDT 2008
Mon Jun 16 13:04:44 PDT 2008
executing forprod from upgrade
Mon Jun 16 13:05:21 PDT 2008
WARNING: ---------------------------------------------------
WARNING: configured to boot from /dev/hda1
WARNING: if this is not correct, update /boot/grub/grub.conf
WARNING: configured to boot from /dev/hda1
WARNING: if this is not correct, update /boot/grub/grub.conf
WARNING: ---------------------------------------------------
mknod: `/dev/calypso': File exists
Step 7 Edit the /etc/rc.local file and add the lines listed below for a Release 1.4 to Release 1.5.1.4.0 upgrade. An example of the rc.local file is in the /root/config-inst/etc/rc.d directory.
a. Add these lines to Streamers before the "/arroyo/test/streamer/run" line.
#su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
#/usr/bin/avslauncher >& /root/avslauncher.log&
b. Add this line to Vaults before the "/arroyo/test/vault/run" line.
#su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
c. Add these lines to Streamers before the "/arroyo/test/ssv/run" line.
#su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
# Streamer and ISV Only
#/usr/bin/avslauncher >& /root/avslauncher.log&
Step 8 Check the /arroyo/test/streamer/run and /arroyo/test/vault/run scripts and compare the output with the following information, which can also be found at the end of this document.
# cat /arroyo/test/streamer/run
dir=/arroyo/test/streamer
cp $dir/setupfile /arroyo/test
insmod $dir/avs_cserver.o
while !(test -d /proc/calypso/tunables); do
echo "Waiting to configure avs_cserver"
echo 1 > /proc/calypso/test/readstreamdestinationmap
echo 1 > /proc/calypso/test/readstreamloadfile
echo 1 > /proc/calypso/test/readarptable
echo 1 > /proc/calypso/test/arp_readroutingtable
echo 1 > /proc/calypso/test/readremoteservers
echo 1 > /proc/calypso/tunables/cm_configurationcomplete
# cat /arroyo/test/vault/run
cp $dir/setupfile /arroyo/test
insmod $dir/avs_cserver.o
while !(test -d /proc/calypso/tunables); do
echo "Waiting to configure avs_cserver"
echo 1 > /proc/calypso/test/readarptable
echo 1 > /proc/calypso/test/arp_readroutingtable
echo 1 > /proc/calypso/test/readremoteservers
echo 1 > /proc/calypso/tunables/cm_configurationcomplete
Step 9 Edit the /etc/rc.sysinit file.
An example of this file is located in the /root/config-inst/etc/rc.d directory. Make sure the first uncommented line reads "insmod avsutil."
Step 10 RepeatStep 1 through Step 9 for the rest of the Vaults and Streamers.
Step 11 Reboot the Vaults andStreamers.
Step 12 Verify the version of AVS, CServer, ISA and AVSDB has been upgraded.
[root@vault167 root]# cds_tags
####################################################################
Version:- cur-1.5.1.4.0RC6
####################################################################
kernel :#2-Nr1_5_1_3-kernel-2_4_32-2008-01-11-01
cserver :#1-Nr1_5_1_2-cserver-p4-e006-2008-06-19-01
ISA :#r1_5_1_4_0-isa-e006-2008-06-19-01
avsdb :#1-Navsdb-rel1514-2008-06-03-02
statsd :#1-Nstatsd-2008-06-18-01
avslauncher :#1-Navslauncher-2008-06-13-02
####################################################################
Upgrade Procedure—CDSM
To upgrade the CDSM, do the following:
Step 1 Log in as root.
Step 2 Shutdown the database.
Step 3 Backup the existing database files.
tar zcvf 144data.tgz *.db
Step 4 Backup the existing network files.
cp /home/isa/.arroyorc /home/isa/.arroyorc_144
cp /etc/hosts /etc/hosts._144
cp /etc/sysconfig/network /etc/sysconfig/network_144
cp /etc/sysconfig/network-scripts/ifcfg-eth0 /etc/sysconfig/network-scripts/ifcfg-eth0_144
Step 5 cd /arroyo/1540
Step 6 Mount the .iso upgrade image
mount cdsm_1514.iso -t iso9660 -o loop /mnt/cdrom
Step 7 cd /mnt/cdrom
Step 8 Backup the database to a folder named /arroyo/144bu.
Step 9 Upgrade the CDSM.
./install-asm.sh controller upgrade
Step 10 After the upgrade completes, run the following script.
Step 11 Verify the version of the CDSM, ISA and AVSDB has been upgraded.
##############################################################
ISA :#r1_5_1_4_0-isa-e006-2008-06-19-01
avsdb :#1-Navsdb-rel1514-2008-06-03-02
statsd :#1-Nstatsd-2008-06-18-01
##############################################################
Step 12 Restart the database on the CDSM.
Step 13 After the database comes back up, perform these steps on the CDSM to migrate from Release 1.4.1.x.x to Release 1.5.1.4.0.
a. Log in to the CDSM GUI as a user with engineering access. The CDSM Setup page is displayed.
b. Set the CServer Version to "1.5.x" and the Installation Type to "ISA for 1.5.1.x" and click Submit.
Step 14 Click Maintain > Software > CDSM Diagnostics and verify the values set for the "current setting" column.
Configuring the Vaults and Streamers Using the CDSM
To finish configuring the CDS using the CDSM, do the following:
Step 1 Restart the database on one upgraded Vault and Streamer.
a. Run the following commands from the /etc/rc.local file:
su - isa -c "cd /home/isa/IntegrationTest
b. Verify that the database is running on each CDS server.
c. For Streamers and ISV/SSVs only, run the following command from the /etc/rc.local file.
/usr/bin/avslauncher >& /root/avslauncher.log&
Step 2 Shutdown the master Vault and master Streamer processes.
a. Run the following command on the master Streamer and master Vault.
b. Verify that statsd is not running on each CDS server.
c. Shutdown the master Virtual IP on master Streamer:
ifconfig eth0:1 down (Lindenhurst)
ifconfig eth1:1 down (ServerWorks)
d. Shutdown the Master Virtual IP on Master Vault:
ifconfig eth0:1 down (Lindenhurst)
ifconfig eth2:1 down (ServerWorks)
Step 3 Restart statsd on the same upgraded Vault and Streamer.
a. Run the following command from the /etc/rc.local file.
/home/stats/statsd -d eth0
b. Verify that statsd is running on each CDS server.
c. Verify that databases are communicating.
Step 4 Push the server information to the CDSM via svrinit_15.
a. Issue the command svrinit_15 command on the Vault Server
/home/stats/svrinit_15 -i <ip addr> -s <subnet> -h <hostname>
b. Issue the command svrinit_15 command on the Stream Server
/home/stats/svrinit_15 -i <ip addr> -s <subnet> -h <hostname>
Step 5 Push the configuration information to the Vault and Streamer via the CDSM GUI.
a. Resubmit the Ingest Tuning values.
a. Click Configure- > System Level > Ingest Tuning.
b. Select the proper Forward and Reverse Trick speeds (+/- 10x for most customers)
c. Click Submit to save the configuration changes.
b. Configure each server.
a. Click Configure > Server Level > Interface Setup.
b. Select proper settings for each interface (Cache for the fill only traffic, Stream/Cache for filling/streaming, and so on).
c. Click Submit to save the configuration changes. The Server Setup page is displayed. DO NOT CLICK ANY ITEM IN THE LEFT PANEL. Continue configuring the server using the Server Setup page to enter other information applicable to your network environment.
c. Configure the Server Setup for each Vault. Vault Mirror Copies and Vault Local Copies are VERY IMPORTANT values. Source IPs are not necessary for Layer 2 networks.
d. Configure Setup Streamers. Source IPs are not necessary for Layer 2 Networks.
e. Configure Control/Setup IP for each Stream Group.
a. Click Configure > Array Level- > Control/Setup I.P
b. Set the IP address and Subnet mask to the previous Stream Server Master IP address and Subnet mask. For the IP Type, select Control/Setup IP.
c. Click Submit to save the configuration changes.
Step 6 Verify all configuration files have been updated.
a. Login as user root.
b. Use the ls -las /arroyo/test command on each server. There should be an ArpTable, RoutingTable, RemoteServers, StreamDestinationMap, and TranportGoupIdTable.
c. Use the ls -las /arroyo/test/streamer command on each Streamer. The - run, setupfile, starteth files should be updated.
d. Use the ls -las /arroyo/test/vault command on each Vault. The - run, setupfile, starteth files should be updated.
e. Use the la -las /arroyo/test/ssv command on each SSV. The - run, setupfile, starteth files should be updated.
Step 7 Edit the /etc/rc.local file and uncomment all the services so the CDS will run at boot time.
/sbin/hdparm -d1 /dev/had
su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
/usr/bin/avslauncher >& /root/avslauncher.log&
/arroyo/test/streamer/run
su - isa -c "cd /home/isa/IntegrationTest; ./run_isa --handle_orphan_streams >>&
/home/isa/IntegrationTest/ns_log&"
/home/stats/statsd -d eth0
/sbin/hdparm -d1 /dev/had
su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
su - isa -c "cd /home/isa/IntegrationTest; ./run_isa >& /home/isa/IntegrationTest/ns_log&"
# Streamer and Vault
/home/stats/statsd -d eth0
Step 8 Reboot the configured servers.
a. Verify that the upgraded servers are now running as 1.5.1.4.0 master Vault and master Streamer.
b. If you are not configuring Layer 3 networking at this time you should verify that the system is functioning. And restore the sites Video Ecosystem functionality.
c. Continue to the "Converting CDS System from Layer 2 to Layer 3" section to convert a 1.5.1.4.0 system from Layer 2 to Layer 3.
Converting CDS System from Layer 2 to Layer 3
To convert from a Layer 2 network to a Layer 3, do the following:
Step 1 Log in to the CDSM as a user with engineering access. The CDSM Setup page is displayed.
Step 2 In the Deployment Network Config section, make sure L3 Networked is selected and click Submit.
Step 3 Configure each server.
Step 4 Click Configure > Server Level > Interface Setup.
Step 5 Select the proper settings for each interface (Cache for the fill only traffic, Stream/Cache for filling/streaming and etc.)
Step 6 Click Submit to save the configuration changes. The Server Setup page is displayed. DO NOT CLICK ANY ITEM IN THE LEFT PANEL. Continue configuring the server using the Server Setup page to enter other information applicable to your network environment.
Step 7 Configure the Server Setup for each Vault and Streamer. Enter all the necessary Source IP addresses foe each configured interface.
Step 8 Click Configure > Server Level Route Tables.
Step 9 Enter the route table information for each server.
Step 10 Click Configure > Array Level > Streamer BMS.
Step 11 In the Resource Manager field, add the Session Gateway name and click Submit.
Step 12 Verify all configuration files have been updated.
a. Login as user root.
b. Use the ls -las /arroyo/test command on each server. There should be an ArpTable, RoutingTable, RemoteServers, StreamDestinationMap, and TranportGoupIdTable.
c. Use the ls -las /arroyo/test/streamer command on each Streamer. The - run, setupfile, starteth files should be updated.
d. Use the ls -las /arroyo/test/vault command on each Vault. The - run, setupfile, starteth files should be updated.
e. Use the la -las /arroyo/test/ssv command on each SSV. The - run, setupfile, starteth files should be updated.
Step 13 Reboot each server. Log in to each Vault, Stream, and SSV and enter the reboot the command line.
New Scripts and Commands
This section describes the new scripts and commands added to Release 1.5.1.4.0.
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 --aim
To stop AIM, enter the following command:
[root@Vault167 root]# /home/isa/IntegrationTest/stop_calypso_service -aim
New 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/hosts
•/etc/sysconfig/network
•/etc/sysconfig/network-scripts/ifcgf-eth0
•/etc/sysconfig/network-scripts/ifcgf-eth1
•/etc/modules.conf
•/etc/rc.sysinit
•/arroyo/test/vault/run
•/arroyo/test/streamer/run
•/arroyo/test/vault/setupfile
•/arroyo/test/streamer/setupfile
•/home/isa/.arroyorc
•/etc/rc.local
•/etc/grub.conf
/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 configuration
127.0.0.1 localhost.localdomain localhost
10.22.217.80 SessionGateway
10.22.217.80 NotificationServer
192.168.100.109 rack109-ip1
Streamer
# 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 confoguration
10.22.217.80 SessionGateway
10.22.217.80 NotificationServer
/etc/sysconfig/network
Vault
Streamer
/etc/sysconfig/network-scripts/ifcgf-eth0
Vault
Streamer
/etc/sysconfig/network-scripts/ifcgf-eth1
Vault
Streamer
/etc/modules.conf
Vault
alias parport_lowlevel parport_pc
alias eth2 e1000 #for Vault or SSV
alias usb-controller usb-ohci
Streamer
alias parport_lowlevel parport_pc
#alias eth1 bcm5700 #for Ingest on Vault or SSV
alias eth1 e1000 #for Management on Streamer
#alias eth2 e1000 #for Management on Vault or SSV
alias usb-controller usb-ohci
Note The bcm5700 interface is only applicable to servers that have the ServerWorks chipset.
/etc/rc.sysinit
Vault
# /etc/rc.sysinit - run once at boot time
# Taken in part from Miquel van Smoorenburg's bcheckrc.
# Rerun ourselves through initlog
if [ -z "$IN_INITLOG" ]; then
[ -f /sbin/initlog ] && exec /sbin/initlog $INITLOG_ARGS -r /etc/rc.sysinit
# If we're using devfs, start devfsd now - we need the old device names
[ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev
PATH=/bin:/sbin:/usr/bin:/usr/sbin
Streamer
# /etc/rc.sysinit - run once at boot time
# Taken in part from Miquel van Smoorenburg's bcheckrc.
# Rerun ourselves through initlog
if [ -z "$IN_INITLOG" ]; then
[ -f /sbin/initlog ] && exec /sbin/initlog $INITLOG_ARGS -r /etc/rc.sysinit
# If we're using devfs, start devfsd now - we need the old device names
[ -e /dev/.devfsd -a -x /sbin/devfsd ] && /sbin/devfsd /dev
PATH=/bin:/sbin:/usr/bin:/usr/sbin
/arroyo/test/vault/run
#insmod $dir/e1000.o and_interrupt_delay=1953
cp $dir/setupfile $dir/requestfile /arroyo/test
insmod $dir/avs_cserver.o #16Gig Vault
#insmod $dir/avs_cserver.o maxphysblocks=491520 #8Gig Vault
while !(test -d /proc/calypso/tunables); do
echo "Waiting to configure avs_cserver"
echo 1 > /proc/calypso/test/readarptable
echo 1 > /proc/calypso/test/arp_readroutingtable
echo 1 > /proc/calypso/test/readremoteservers
echo 1 > /proc/calypso/tunables/cm_configurationcomplete
/arroyo/test/streamer/run
dir=/arroyo/test/streamer
cp $dir/setupfile $dir/requestfile /arroyo/test
insmod $dir/avs_cserver.o
while !(test -d /proc/calypso/tunables); do
echo "Waiting to configure avs_cserver"
#echo 1 > /proc/sys/kernel/kdb_keyboard_break_on
echo 1 > /proc/calypso/test/readstreamloadfile
echo 1 > /proc/calypso/test/readarptable
echo 1 > /proc/calypso/test/arp_readroutingtable
echo 1 > /proc/calypso/test/readremoteservers
echo 1 > /proc/calypso/tunables/cm_configurationcomplete
/arroyo/test/vault/setupfile
# CServer core configuration. Changes to this file require
default source ip 192.169.106.1 tport 0 - 0 cport 0
e1000 adapters: maxrate 965
e1000 1: streaming 1 fill 1 ip 192.169.106.1 tport 0 cport 0 tgid 0
e1000 2: streaming 1 fill 1 ip 192.169.106.2 tport 0 cport 0 tgid 0
e1000 3: streaming 1 fill 1 ip 192.169.106.3 tport 0 cport 0 tgid 0
e1000 4: streaming 1 fill 1 ip 192.169.106.4 tport 0 cport 0 tgid 0
trickspeedsv2 2 -2 6 -6 10 -10 60 -60
ftpout if eth2 max utilization mbps 0 max sessions 0
/arroyo/test/streamer/setupfile
# CServer core configuration. Changes to this file require
service address 10.22.216.198 setup 3300 control 9000
bms address 10.22.217.80 5000
default source ip 192.168.207.65 tport 0 - 0 cport 0
e1000 adapters: maxrate 965
e1000 1: streaming 1 fill 1 ip 192.169.106.41 tport 0 cport 0 tgid 0
e1000 2: streaming 1 fill 1 ip 192.169.106.42 tport 0 cport 0 tgid 0
e1000 3: streaming 1 fill 1 ip 192.169.106.43 tport 0 cport 0 tgid 0
e1000 4: streaming 1 fill 1 ip 192.169.106.44 tport 0 cport 0 tgid 0
e1000 5: streaming 1 fill 1 ip 192.169.106.45 tport 0 cport 0 tgid 0
e1000 6: streaming 1 fill 1 ip 192.169.106.46 tport 0 cport 0 tgid 0
e1000 7: streaming 1 fill 1 ip 192.169.106.47 tport 0 cport 0 tgid 0
e1000 8: streaming 1 fill 1 ip 192.169.106.48 tport 0 cport 0 tgid 0
e1000 9: streaming 1 fill 1 ip 192.169.106.49 tport 0 cport 0 tgid 0
e1000 10: streaming 1 fill 1 ip 192.169.106.50 tport 0 cport 0 tgid 0
e1000 11: streaming 1 fill 1 ip 192.169.106.51 tport 0 cport 0 tgid 0
e1000 12: streaming 1 fill 1 ip 192.169.106.52 tport 0 cport 0 tgid 0
/home/isa/.arroyorc
Vault
# Replication Group Members
Streamer
# Replication Group Members
/etc/rc.local
Vault
# 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
echo 222217728 > /proc/sys/kernel/shmmax
echo 222217728 > /proc/sys/kernel/shmall
echo 65535 > /proc/sys/fs/file-max
echo "8388608" > /proc/sys/net/core/wmem_max
echo "8388608" > /proc/sys/net/core/rmem_max
echo "4096 65536 4194304" > /proc/sys/net/ipv4/tcp_wmem
echo "4096 87380 4194304" > /proc/sys/net/ipv4/tcp_rmem
echo 0 > /proc/sys/net/ipv4/tcp_sack
/sbin/hdparm -d1 /dev/hda
su - isa - c "cd /home/isa/IntegrationTest; ./init_isa_env"
#/usr/bin/avslauncher >& /root/avslauncher.log&
#/arroyo/test/streamer/run
#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&"
/home/stats/statsd -d eth0
Streamer
# 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
echo 222217728 > /proc/sys/kernel/shmmax
echo 222217728 > /proc/sys/kernel/shmall
echo 65535 > /proc/sys/fs/file-max
echo "8388608" > /proc/sys/net/core/wmem_max
echo "8388608" > /proc/sys/net/core/rmem_max
echo "4096 65536 4194304" > /proc/sys/net/ipv4/tcp_wmem
echo "4096 87380 4194304" > /proc/sys/net/ipv4/tcp_rmem
echo 0 > /proc/sys/net/ipv4/tcp_sack
/sbin/hdparm -d1 /dev/hda
su - isa - c "cd /home/isa/IntegrationTest; ./init_isa_env"
/usr/bin/avslauncher >& /root/avslauncher.log&
/arroyo/test/streamer/run
#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&"
/home/stats/statsd -d eth0
/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.
# kernel /boot/vmlinuz-version ro root=/dev/hda1
# initrd /boot/initrd-version.img
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
kernel /boot/vmlinuz-2.4.32avs ro root=/dev/hda1 console=tty0 console=ttyS0,115200
nmi_watchdog=1
initrd /boot/initrd-2.4.32avs.img
title Red Hat Linux (2.4.18-3bigmem)
kernel /boot/vmlinuz-2.4.18-3bigmem ro root=/dev/hda1
initrd /boot/initrd-2.4.18-3bigmem.img
title Red Hat Linux-smp (2.4.18-3smp)
kernel /boot/vmlinuz-2.4.18-3smp ro root=/dev/hda1
initrd /boot/initrd-2.4.18-3smp.img
title Red Hat Linux-up (2.4.18-3)
kernel /boot/vmlinuz-2.4.18-3 ro root=/dev/hda1
initrd /boot/initrd-2.4.18-3.img
Streamer
# 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.
# kernel /boot/vmlinuz-version ro root=/dev/hda1
# initrd /boot/initrd-version.img
splashimage=(hd0,0)/boot/grub/splash.xpm.gz
kernel /boot/vmlinuz-2.4.32avs ro root=/dev/hda1 console=tty0 console=ttyS0,115200
nmi_watchdog=1
initrd /boot/initrd-2.4.32avs.img
title Red Hat Linux (2.4.18-3bigmem)
kernel /boot/vmlinuz-2.4.18-3bigmem ro root=/dev/hda1
initrd /boot/initrd-2.4.18-3bigmem.img
title Red Hat Linux-smp (2.4.18-3smp)
kernel /boot/vmlinuz-2.4.18-3smp ro root=/dev/hda1
initrd /boot/initrd-2.4.18-3smp.img
title Red Hat Linux-up (2.4.18-3)
kernel /boot/vmlinuz-2.4.18-3 ro root=/dev/hda1
initrd /boot/initrd-2.4.18-3.img
Disk 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.log
Step 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:
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.log
Step 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 .
Step 3 Verify all ISA services are running by entering the following command:
Step 4 Verify the Name Service and ISA Service checks are working by entering the following command:
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:
On the CDSM:
cd Berkeley
Step 3 Extract the contents of the Berkeley database on each server.
Step 4 Verify that all keys files are synchronized with each other.
For Vault Servers and CDSM:
For Stream Servers and CDSM
Step 5 Verify that all main.db files display the current date and are close in file size.
Step 6 Check the /home/isa/Berkeley/LOG/log file 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 TV CDS Software Configuration Guide
•Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide
•Regulatory Compliance and Safety Information for Cisco Content Delivery Engine 100/200/300/400
The following documents have been added for this release:
•Release Notes for Cisco TV CDS 1.5.4.1
Related Documentation
Refer to the following documents for additional information about the Cisco TV CDS 1.5.1.4.0:
•Cisco Content Delivery Engine 100/200/300/400 Hardware Installation Guide (OL-13478-02)
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 (78-18229-02)
http://www.cisco.com/en/US/docs/video/cds/cde/regulatory/compliance/CDE_RCSI.html
•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.
Feedback
