Cisco TV CDS 2.4 Installation, Upgrade, and Maintenance Guide for the Cisco ISM (Integrated Service Module) Line Card
Upgrading to Release 2.4.1
Downloads: This chapterpdf (PDF - 113.0KB) The complete bookPDF (PDF - 889.0KB) | Feedback

Upgrading to Release 2.4.1

Table Of Contents

Upgrading to Release 2.4.1

Upgrading the Software on a CDSM or VVIM

Upgrading a New CDS Server to Release 2.4.1


Upgrading to Release 2.4.1


This chapter describes the upgrade procedure for the CDSM, VVIM, and CDS servers. This chapter covers the following topics:

Upgrading the Software on a CDSM or VVIM

Upgrading a New CDS Server to Release 2.4.1


Caution Before proceeding with the software upgrade, review Chapter 2 "Overview of Upgrading and Downgrading the TV CDS Software" for information on getting the Release 2.4.1 software files, prerequisites for the software upgrade, the upgrade sequence for the devices in the CDS, and information about the upgrade and downgrade kits.

Upgrading the Software on a CDSM or VVIM

To upgrade the software on a Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card serving as a CDSM or VVIM, complete the procedures described in this section.

If the VVI or CDS has redundant VVIMs or CDSMs, upgrade the secondary CDSM or VVIM first, then upgrade the primary.

The primary and secondary CDSM (or VVIM) can be determined by entering the ifconfig -a | more command. The primary has the following output:

eth0:1    Link encap:Ethernet HWaddr 00:11:00:00:00:00 
          inet addr:172.22.98.54 Bcast:172.22.99.255 Mask:255.255.254.0
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          Memory:b8820000-b8840000 
 
   

The primary CDSM has device eth0:1. The secondary CDSM does not have the virtual IP address as up.


Note Upgrading a CDSM requires that the CDS-TV-2.4.1.iso and cdsinstall software files have been downloaded and copied to the CDSM. The cdsinstall script has changed for Release 2.4.1. Make sure you download the cdsinstall script from Cisco and copy it to /root directory on each CDSM and VVIM before upgrading them. Use the scp command to copy the software files. For example, if the remote server that you downloaded the software files to has an IP address of 172.22.97.109 and the files are stored in the CDSdownloads directory, the following commands are used:

# scp -p 172.22.97.109:/CDSdownloads/CDS-TV.2.4.1.iso /
# scp -p 172.22.97.109:/CDSdownloads/cdsinstall /root


Note Before upgrading the CDSMs, review the information in the "Introduction" section. For information on downloading the software files, see the "Getting the Cisco TV CDS Software Files for Release 2.4.1" section.


To upgrade the software on a CDSM or VVIM, do the following:


Step 1 Log in to the secondary CDSM as root.

Step 2 Back up the configuration and database files on the existing CDSM. For information on this procedure, see the "Performing a Backup on the CDSM" section.

Step 3 Run the cdsinstall script to upgrade the ISO image to Release 2.4.1.

# /root
# ./cdsinstall /CDS-TV-2.4.1.iso
Select Deployment Type (ctrl-c to quit):
  1) CDSM
1
CDSM Selected
Mounting CDS-TV-PROD.iso at /mnt/cdrom
Running inst.sh for isa
Killing running processes: statsd
Un-taring isa-base.tgz
Calling forprod.sh
Removing RTSP-specific files
Installing ISA-specific files (existing files backed up to .file)
ISA installation complete
 
   
Starting fixperms.sh
   Loading File List
   Processing File List
Ending fixperms.sh
Calling inst.sh for cdsm
Killing running processes: statsd
 
   
Starting cdsupgrade.sh
   Current SW version to backup is cdstv-2.1.3-es4-b4
   Processing File Lists
      /arroyo/image/backup/cdstv-2.1.3-es4-b4/files/common-files: does not exist
      /arroyo/image/backup/cdstv-2.1.3-es4-b4/files/isa-files: does not exist
      /arroyo/image/backup/cdstv-2.1.3-es4-b4/files/rtsp-files: does not exist
   Processing /arroyo/image/backup/cdstv-2.1.3-es4-b4/files/cdsm-files
Ending cdsupgrade.sh
Un-taring cdsm-base.tgz
Calling forprod.sh
Installing CDSM-specific files (existing files backed up to .file)
Upgrading CmdTool2 if necessary
 
   
Set Write Policy to WriteBack on Adapter 0, VD 0 (target id: 0) success
Set Write Policy to WriteBack on Adapter 0, VD 1 (target id: 1) success
Set Write Policy to WriteBack on Adapter 0, VD 2 (target id: 2) success
Set Write Policy to WriteBack on Adapter 0, VD 3 (target id: 3) success
Set Write Policy to WriteBack on Adapter 0, VD 4 (target id: 4) success
Set Write Policy to WriteBack on Adapter 0, VD 5 (target id: 5) success
Set Write Policy to WriteBack on Adapter 0, VD 6 (target id: 6) success
 
   
Set Write Cache OK if bad BBU on Adapter 0, VD 0 (target id: 0) success
Set Write Cache OK if bad BBU on Adapter 0, VD 1 (target id: 1) success
Set Write Cache OK if bad BBU on Adapter 0, VD 2 (target id: 2) success
Set Write Cache OK if bad BBU on Adapter 0, VD 3 (target id: 3) success
Set Write Cache OK if bad BBU on Adapter 0, VD 4 (target id: 4) success
Set Write Cache OK if bad BBU on Adapter 0, VD 5 (target id: 5) success
Set Write Cache OK if bad BBU on Adapter 0, VD 6 (target id: 6) success
 
   
Set Disk Cache Policy to Enabled on Adapter 0, VD 0 (target id: 0) success
Set Disk Cache Policy to Enabled on Adapter 0, VD 1 (target id: 1) success
Set Disk Cache Policy to Enabled on Adapter 0, VD 2 (target id: 2) success
Set Disk Cache Policy to Enabled on Adapter 0, VD 3 (target id: 3) success
Set Disk Cache Policy to Enabled on Adapter 0, VD 4 (target id: 4) success
Set Disk Cache Policy to Enabled on Adapter 0, VD 5 (target id: 5) success
Set Disk Cache Policy to Enabled on Adapter 0, VD 6 (target id: 6) success
CDSM installation complete
 
   
Starting fixperms.sh
   Loading File List
   Processing File List
Ending fixperms.sh
Unmounting /mnt/cdrom
cdsinstall completed. Please reboot the device.
 
   

Step 4 Reboot the CDSM.

# reboot
 
   

Step 5 To finalize the software upgrade, log in to the CDSM GUI as a user with Engineering access level. The CDSM Setup page is displayed. In the Deployed CServer Version drop-down list, choose 2.4.x. Verify the other settings on the CDSM Setup page and click Submit.

Step 6 Upgrade the primary CDSM (Step 1 to Step 5), if applicable.


Upgrading a New CDS Server to Release 2.4.1

The Cisco TV CDS CDEs ship with the software installation files for Release 2.1.3. If a CDE received from Cisco is expected to be installed into a Release 2.4.1 deployment, it must be upgraded with the upgrade kit.

To upgrade a new CDS server, configure the management network on the CDS server by performing the following steps:


Step 1 To configure the Ethernet interface (eth0), which will be used to connect to the management network, use a text editor to modify the file /etc/sysconfig/network-scripts/ifcfg-eth0 and add the following lines:

DEVICE=eth0

BOOTPROTO=static

ONBOOT=yes

IPADDR=ip_address_for_eth0

NETMASK=netmask_for_eth0

For example:

DEVICE=eth0
BOOTPROTO=static
ONBOOT=yes
IPADDR=172.22.97.162 
NETMASK=255.255.255.128 
 
   

Step 2 Save and close the ifcfg-eth0 file.

Step 3 To configure the network characteristics, use a text editor to modify the file /etc/sysconfig/network and add the following lines:

NETWORKING=yes

NETWORKING_IPV6=no

HOSTNAME=name

GATEWAY=gateway_ip_address

For example:

NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=cdsm162 
GATEWAY=172.22.97.129 
 
   

The gateway_ip_address is the default gateway IP address—the address of the interface on the router that is directly attached to the CDE110 eth0 interface.

Step 4 Save and close the network file.

Step 5 To restart the network, issue the following command:

[root]# /etc/init.d/network restart 
 
   
Shutting down interface eth0:                              [ OK ]
Shutting down loopback interface:                          [ OK ]
Bringing up loopback interface:                            [ OK ]
Bringing up interface eth0:                                [ OK ]
 
   
[root]# 
 
   


Note A serial console connection is highly recommended.


Perform the software upgrade procedure in Chapter 3 "Upgrading to Release 2.4.1." After completing the upgrade procedure, perform the add a server procedure in the "Adding a Server" section.