Cisco TV CDS 2.4 Installation, Upgrade, and Maintenance Guide for the Cisco ISM (Integrated Service Module) Line Card
Installing and Configuring the TV CDS 2.4 Software
Downloads: This chapterpdf (PDF - 395.0KB) The complete bookPDF (PDF - 889.0KB) | Feedback

Installing and Configuring the TV CDS 2.4 Software

Table Of Contents

Installing and Configuring the TV CDS 2.4 Software

Preparing the CDEs for Initial Configuration

Upgrading New CDEs with Release 2.4.1 TV CDS Software

Upgrading the Software on a Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card

Initial Configuration Sequence of the Content Delivery System (CDS)

VVI Initial Configuration Sequence

CDS Initial Configuration Sequence

Preparing to Initially Configure the CDEs

Initially Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card

Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card as a Streamer


Installing and Configuring the TV CDS 2.4 Software


This chapter covers installation of new Release 2.4.1 systems in either a Content Delivery System (CDS) or a Virtual Video Infrastructure (VVI) design. This chapter includes the following topics:

Preparing the CDEs for Initial Configuration

Initial Configuration Sequence of the Content Delivery System (CDS)

Initially Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card

A CDS consists of Vaults, Streamers, and a Content Delivery System Manager (CDSM). A CDS can also be made of Integrated Streamer-Vaults (ISVs) and a CDSM. A VVI consists of Vaults, Caching Nodes, Streamers, Virtual Video Infrastructure Manager (VVIM) and Stream Manager (also called CDSM). For more information about the different system architectures and network designs, see the "Product Overview" and "Network Design" chapters in the Cisco TV CDS 2.3 ISA Software Configuration Guide and the Cisco TV CDS 2.4 RTSP Software Configuration Guide for the Cisco ISM (Integrated Service Module) Line Card.

Preparing the CDEs for Initial Configuration

Before performing the software installation and initial configuration, you must correctly install the CDEs and connect the cables. The process for installing a new Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) as a Content Delivery Engine (CDE) in a Cisco ASR 9000 Series Aggregation Services Router is described in the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card Hardware Installation Guide.


Note As part of the hardware installation of the CDEs, check to make sure all I/O cards are properly and firmly seated, and all cables are firmly connected.


Connecting to the Serial Port for Administrative Access to the CDE

The RJ-45 serial ports on the route switch processor (RSP) card front and back panels can be used for administrative access to the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) as a Content Delivery Engine (CDE) through a terminal server. Refer to the Connecting to the Router Through the Console Port section of the Cisco ASR 9000 Series Aggregation Services Router Getting Started Guide online. Terminal emulation software must be configured as follows:

Bits per second: 115200

Data bits: 8

Parity: none

Stop bits: 1

Hardware flow control: ON

After installing the CDEs and connecting the cables, the software may need to be upgraded before initial configuration can occur.

Upgrading New CDEs with Release 2.4.1 TV CDS Software

A new Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Content Delivery Engine (CDE) ships with Release 2.4.1 TV CDS software. If you have non-Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) CDEs that have an earlier release of TV CDS software installed you must download the software files for Release 2.4.1 TV CDS software and upgrade the operating system (OS) and software on the CDE models to be configured as CDS servers (Vaults, Caching Nodes, Streamers, and ISVs). You should not need to upgrade the software on the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line cards, which are used for the Streamers. The Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line cards ship with the appropriate level of OS (Operating System) software already installed.


Note Before you can upgrade the CDEs, you must download the TV CDS Release 2.4.1 software image files from the Cisco software download website. See the "Getting the Cisco TV CDS Software Files for Release 2.4.1" section for information on downloading these files.


The following upgrade procedures are for CDEs used in a Release 2.4.1 CDS:

Upgrading the Software on a Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card

Upgrading the Software on a Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card

The Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card is used for a streamer. The Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card ships with a 64-bit OS, and therefore only needs the software image upgraded. The CDS-TV software image MAY need to be upgraded, and the steps for this start at Step 6.

To upgrade the software image on a Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card, complete the following instructions to reload the OS and then perform the CDS-TV application:


Step 1 Once the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card is inserted into the Cisco ASR 9000 Series Aggregation Services Router it will automatically be powered on.

The operating system boots.

Step 2 To login to the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card, access the Cisco ASR 9000 Series Aggregation Services Router using the console or a vty session. If the ISM line card is operational and the network interfaces have been configured, you can ssh directly to the ISM management interface.

Step 3 From the Cisco ASR 9000 Series Aggregation Services Router console or vty session execute the following command:

# run attachCon 0/ISM slot number on ASR9000/CPU1 115200
 
   

For example, to access the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card in slot 6 use the following command:

# run attachCon 0/6/CPU1 115200
 
   

To detach and get back to the Cisco ASR 9000 Series Aggregation Services Router Route Processor (RP) card console prompt, type detach followed by return.

Step 4 Log in as root with the password rootroot. Note that this is the password if this is a clean OS installation of the OS that is already on the disk (like it would have been received from Cisco Manufacturing).


Note To change the default password, use the passwd command.


Step 5 After the rescue image is booted and you are attached to the console on the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card, execute the following script to extract the ISM Install Kit self-extracting script:

[root@sim100-rescue-linux root]# ./cdstv-2.4.1-ism-install-kit.sh
 
   
Extracting files into /root (extracting the ISO file may take a few
minutes):
ism_install/.
ism_install/./vmlinuz-ism
ism_install/./backup_cfg.sh
ism_install/./initrd-ism.img
ism_install/./ism-5.3-x86_64-full-image.iso
ism_install/./cds_upg_report.sh
ism_install/./ism_apiv
ism_install/./ism_apiv/avsm_heartbeat_compat
ism_install/./ism_apiv/avsm_envmon_compat
ism_install/./ism_apiv/apiv_sam_inventory_compat
ism_install/./ism_apiv/apiv_errmsg_compat
ism_install/./ism_apiv/avsm_bundle_apiv_compat
ism_install/./ism_apiv/avsm_l2fib_apiv_compat
ism_install/./ism_apiv/avsm_frr_apiv_compat
ism_install/./ism_apiv/avsm_l3fib_compat
ism_install/./ism_apiv/avsm_l2fib_stats_apiv_compat
ism_install/./ism_apiv/apiv_si_compat
ism_install/./ism_apiv/avsm_l3fib_misc_apiv_compat
ism_install/./ism_apiv/avsm_li_stats_apiv_compat
ism_install/./ism_apiv/amistad_apiv_lib_compat
ism_install/./ism_apiv/apiv_avsm_dbg_compat
ism_install/./ism_apiv/apiv_sim_inventory_compat
ism_install/./ism_apiv/apiv.conf
ism_install/./ism_apiv/apiv_fpd_upgrade_compat
ism_install/./ism_apiv/apiv_sample_compat
ism_install/./ism_apiv/avsm_mcast_stats_apiv_compat
ism_install/./ism_apiv/apiv_se_sysmgr_compat
ism_install/./ism_apiv/avsm_l3fib_lookup_compat
ism_install/./ism_apiv/apiv_test_compat
ism_install/./ism_apiv/apiv_se_info_compat
ism_install/./ism_apiv/avsm_mcast_apiv_compat
ism_install/./ism-iso-full-image.sha1sum
ism_install/./apiv_compat_check
ism_install/./restore_cfg.sh
ism_install/./restore.list
ism_install/./ism_install.sh
ism_install/./backup.list
 
   
ISO file checksum checking (may take a few minutes):
Found SHA1 checksum file: ./ism_install/ism-iso-full-image.sha1sum
ism-5.3-x86_64-full-image.iso: OK
 
   
Install files are extracted in directory: ./ism_install
 
   
[root@sim100-rescue-linux ism_install]# ./ism_install.sh Checking required files for 
installation ... [ DONE ]
  Found file ism_install.sh.
  Found file initrd-ism.img.
  Found file vmlinuz-ism.
  Found file ism-5.3-x86_64-full-image.iso.
  Found file ism-iso-full-image.sha1sum.
 
   
Package compatibility check PASSED
Removing existing partitions on /dev/sda ... [ DONE ]
  Maximum partition index found 8
  Deleted partition /dev/sda8.
  Deleted partition /dev/sda7.
  Deleted partition /dev/sda6.
  Deleted partition /dev/sda5.
  Deleted partition /dev/sda4.
  Deleted partition /dev/sda3.
  Deleted partition /dev/sda2.
  Deleted partition /dev/sda1.
 
   
Creating partitions on /dev/sda ... -SCSI device sda: 118122224 512-byte hdwr se ctors 
(60479 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write through
 sda:
/SCSI device sda: 118122224 512-byte hdwr sectors (60479 MB)
sda: Write Protect is off
SCSI device sda: drive cache: write through
 sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 > [ DONE ]
  Successfully created partitions on /dev/sda.
 
   
Changing /dev/sda1 to ext3 format ... [ DONE ]
  Created symbolic link /etc/mtab to /proc/mounts.
  Executed mkfs.ext3 on /dev/sda1.
 
   
Changing /dev/sda8 to ext3 format ... [ DONE ]
  Created symbolic link /etc/mtab to /proc/mounts.
  Executed mkfs.ext3 on /dev/sda8.
 
   
Mounting /dev/sda1 to /mnt/boot/ ... ... \kjournald starting.  Commit interval 5  seconds
EXT3 FS on sda1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
[ DONE ]
  Mounted /dev/sda1 to /mnt/boot
 
   
Mounting /dev/sda8 to /mnt/upgrade_part/ ... ... \kjournald starting.
Commit in
terval 5 seconds
EXT3 FS on sda8, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
[ DONE ]
  Mounted /dev/sda8 to /mnt/upgrade_part
 
   
Copying files to /dev/sda ... [ DONE ]
  Copied /usr/share/grub/x86_64-redhat/* to ..
  Created symbolic link menu.lst to grub.conf.
  Installed grub on /dev/sda
  Copied vmlinuz-ism to /mnt/upgrade_part/.
  Copied initrd-ism.img to /mnt/upgrade_part/.
  Copied ism_install.sh to /mnt/upgrade_part/.
  Copied ism-iso-full-image.sha1sum to /mnt/upgrade_part/.
  Copied ism-5.3-x86_64-full-image.iso to /mnt/upgrade_part/upgrade/.
  Copied backup_cfg.sh to /mnt/upgrade_part/upgrade/.
  Copied backup.list to /mnt/upgrade_part/upgrade/.
  Copied restore_cfg.sh to /mnt/upgrade_part/upgrade/.
  Copied restore.list to /mnt/upgrade_part/upgrade/.
  Copied cds_upg_report.sh to /mnt/upgrade_part/upgrade/.
 
   
The installation script completes successfully. Please type
  'hw-module location x/y/z reload'
on ASR9K console to reboot this AVSM.
 
   

Step 6 Reload the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card by executing the hw-module location reload command in admin mode.

The syntax is hw-module location 0/x/CPU0 reload or hw-module location 0/x/CPU1 reload, where x is the slot number.

Here is the example output from executing the hw-module location 0/1/CPU0 reload command:

RP/0/RSP0/CPU0:VKG-2#hw-module location 0/1/CPU0 reload 
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)] y
 
   

Wait for the OS installation to complete. After this is done you will be able to log in as root with the password rootroot. Note that this is the default password since this is a clean OS installation of the OS that is already on the disk (like it would have been received from Cisco Manufacturing).. Also if the OS is being reloaded, and the image that comes with the install is the CDS-TV application to install, you will not need to copy it to the system. This means you can skip Step 7.

Step 7 After configuring an interface to the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card, use the scp command to copy the CDS-TV-2.4.1.iso and cdsinstall 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, use the following commands to copy down the files:

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

Note The install kit leaves a copy of the ISO image in /root. You only need to use the scp command to copy the CDS-TV-2.4.1.iso and cdsinstall software files if a different version or patch needs to be applied, Otherwise the existing CDS-TV-2.4.1.iso file in /root can be installed


 
   

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

RTSP Deployment Example

# /root
# ./cdsinstall /CDS-TV-2.4.1.iso
 
   
Select Deployment Type (ctrl-c to quit):
  1) ISA
  2) RTSP/FSI
2
RTSP Selected
Mounting /CDS-TV.iso at /mnt/cdrom
Calling inst.sh for common files
Killing running processes: statsd
 
   
Starting cdsupgrade.sh
   WARNING: No existing version found on this server. Cannot backup existing files
Un-taring common-base.tgz
Fixing modprobe.conf
Loading File List
...done
 
   
Processing File List
...done
 
   
Moving modprobe.conf into place
...done
 
   
Installing kernel rpm
Installing cserver production rpm
Disabled various startup scripts in /etc/init.d
Installing busybox
warning: /home/packages/busybox-1.2.0-4.el5.i386.rpm: Header V3 DSA signature: NOKEY, key 
ID 37017186
Installing kdump
warning: /home/packages/kexec-tools-1.101-194.4.el5.x86_64.rpm: Header V3 DSA signature: 
NOKEY, key ID 37017186
 
   
Configuring kdump...
 
   
Starting kdump service...
 
   
No kdump initial ramdisk found.[WARNING]
Rebuilding /boot/initrd-2.6.18-53.el5kdump.img
kernel-debuginfo-2.6.18-53.el5 is not installed. You need this to use makedumpfile!
please install it and restart the kdump service
Failed to run mkdumprd
Installing logrotate
warning: /home/packages/logrotate-3.7.4-8.i386.rpm: Header V3 DSA signature: NOKEY, key ID 
37017186
Installing CmdTool2
                                     
Set Write Policy to WriteBack on Adapter 0, VD 0 (target id: 0) success
                                     
Set Write Cache OK if bad BBU on Adapter 0, VD 0 (target id: 0) success
                                     
Set Disk Cache Policy to Enabled on Adapter 0, VD 0 (target id: 0) success
 
   
Starting fixperms.sh
   Loading File List
   Processing File List
Ending fixperms.sh
Calling inst.sh for rtsp
Killing running processes: statsd
Un-taring rtsp-base.tgz
Calling forprod.sh
Removing ISA-specific files
Installing RTSP-specific files (existing files backed up to .file)
mv: `/home/isa/bss/database/avsdb' and `/arroyo/db/avsdb' are the same file
mv: `/home/isa/bss/database/AVSDBUtil' and `/arroyo/db/AVSDBUtil' are the same file
mv: `/home/isa/bss/database/DATADIR' and `/arroyo/db/DATADIR' are the same file
mv: `/home/isa/bss/database/lost+found' and `/arroyo/db/lost+found' are the same file
RTSP installation complete
 
   
Starting fixperms.sh
   Loading File List
   Processing File List
Ending fixperms.sh
Unmounting /mnt/cdrom
cdsinstall completed. Please reboot the device.
 
   

ISA Deployment Example

[root@localhost ~]# ./cdsinstall /CDS-TV.iso
Select Deployment Type (ctrl-c to quit):
  1) ISA
  2) RTSP/FSI
1
ISA Selected
Mounting /CDS-TV.iso at /mnt/cdrom
Calling inst.sh for AVSM
Killing running processes: statsd
Un-taring avsm_infra.tgz 
Verifying infra package compatibility ...
Module   4 - Error Message module     : compatible
Module   6 - SAM Inventory            : compatible
Module   7 - Service Interface Agent  : compatible
Module   8 - AVSM FIB L3FIB thread    : compatible
Module   9 - AVSM FIB L3FIB lookup    : compatible
Module  10 - Bundle Manager           : compatible
Module  11 - FIB FRR                  : compatible
Module  12 - SE System Manager        : compatible
Module  13 - FPD Upgrade              : compatible
Module  15 - SIM Inventory            : compatible
Module  16 - Multicast UFA MFIB       : remote peer not registered, bypass compat check
 
   
 
   

Note The warning, "Failed to run," and the move messages are known, benign errors. Both the "Failed to run" warning and the move messages can be ignored.


Step 9 Reboot the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card from your terminal connection to the Cisco ASR 9000 Series Aggregation Services Router Route Processor card.

# hw-module location 0/ISM slot number on ASR9K/CPU0 reload
 
   

Here is the example output from executing the hw-module location 0/1/CPU0 reload command:

RP/0/RSP0/CPU0:VKG-2#hw-module location 0/1/CPU0 reload 
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)]y
 
   
RP/0/RSP0/CPU0:Apr 13 13:21:01.329 EST: shelfmgr[357]: %PLATFORM-SHELFMGR-6-USER_RESET : 
Node 0/1/CPU0 is reset due to user reload request 
RP/0/RSP0/CPU0:Apr 13 13:21:01.335 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:IOS XR FAILURE 
LC/0/1/CPU0:Apr 13 13:21:01.338 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:21:01.338 EST: ism_se_sm[127]: %PLATFORM-SIM_SE-5-STATE_CHANGE : 
Service Engine is in shutting down state. 
LC/0/1/CPU0:Apr 13 13:21:01.340 EST: ipv4_mfwd_partner[224]: Deactivating MCAST APIV ...
LC/0/1/CPU0:Apr 13 13:21:01.340 EST: l2fib[231]: Deactivating APIV module 
MOD_ID_ISM_L2FIB...
LC/0/1/CPU0:Apr 13 13:21:01.340 EST: vkg_sis[293]: Starting of SI APIV Deletion ...
RP/0/RSP0/CPU0:Apr 13 13:21:01.417 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM0 removed  
RP/0/RSP0/CPU0:Apr 13 13:21:01.419 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81c 
RP/0/RSP0/CPU0:Apr 13 13:21:01.434 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM1 removed  
RP/0/RSP0/CPU0:Apr 13 13:21:01.435 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81d 
LC/0/1/CPU0:Apr 13 13:21:03.003 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.003 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.004 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.004 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.006 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.006 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.007 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.007 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.007 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.008 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Down 
RP/0/RSP0/CPU0:Apr 13 13:21:08.968 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM1, state: BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:21:08.979 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM0, state: BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:22:01.474 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:22:01.541 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM0 removed  
RP/0/RSP0/CPU0:Apr 13 13:22:01.546 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81c 
RP/0/RSP0/CPU0:Apr 13 13:22:01.572 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM1 removed  
RP/0/RSP0/CPU0:Apr 13 13:22:01.573 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81d 
RP/0/RSP0/CPU0:Apr 13 13:22:01.584 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:22:13.235 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:ROMMON 
RP/0/RSP0/CPU0:Apr 13 13:22:44.043 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/1/CPU0, RomMon Version: 
1.2 
RP/0/RSP0/CPU0:Apr 13 13:22:44.046 EST: shelfmgr[357]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED 
: Remote location 0/1/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.1.0.35I/lc/mbiasr9k-lc.vm 
validated 
RP/0/RSP0/CPU0:Apr 13 13:22:44.047 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:MBI-BOOTING 
RP/0/RSP0/CPU0:Apr 13 13:23:35.447 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:MBI-RUNNING 
LC/0/1/CPU0:15: init[65540]: %OS-INIT-7-MBI_STARTED : total time 9.242 seconds 
LC/0/1/CPU0:Apr 13 13:23:38.912 EST: insthelper[61]: %INSTALL-INSTHELPER-7-PKG_DOWNLOAD : 
MBI running; starting software download 
LC/0/1/CPU0:Apr 13 13:23:53.184 EST: sysmgr[89]: %OS-SYSMGR-5-NOTICE : Card is COLD 
started  
LC/0/1/CPU0:Apr 13 13:23:53.490 EST: init[65540]: %OS-INIT-7-INSTALL_READY : total time 
28.024 seconds 
LC/0/1/CPU0:Apr 13 13:23:54.820 EST: sysmgr[316]: %OS-SYSMGR-6-INFO : Backup system 
manager is ready  
LC/0/1/CPU0:Apr 13 13:23:55.989 EST: syslog_dev[87]: dumper_config[153]:  
LC/0/1/CPU0:Apr 13 13:23:56.027 EST: syslog_dev[87]: dumper_config[153]:  The node id is 
2065 
LC/0/1/CPU0:Apr 13 13:23:58.631 EST: linux_maint_fpd_agent[236]: linux_maint_fpd_agent: 
Registering the handlers
LC/0/1/CPU0:Apr 13 13:23:58.645 EST: linux_maint_fpd_agent[236]: 
update_linux_maint_sw_version Updated the sw_ver 6
LC/0/1/CPU0:Apr 13 13:23:58.648 EST: linux_maint_fpd_agent[236]: publish_maint_fpd_info 
Publishing FPD info : type 1, subtype 4, card type 16777989, module 0, instance 0, sw_ver 
6, hw_ver 1
LC/0/1/CPU0:Apr 13 13:23:58.878 EST: vkg_sis[293]: Initializing APIV modules ...
LC/0/1/CPU0:Apr 13 13:23:58.890 EST: vkg_sis[293]: Registering for SysDB notifications ...
LC/0/1/CPU0:Apr 13 13:23:58.897 EST: vkg_sis[293]: Registering for SysDB SE READY 
notifications ...
LC/0/1/CPU0:Apr 13 13:23:59.997 EST: fca_server[165]: bridge_asic_get_ver: msg send 
problem: Invalid argument 
LC/0/1/CPU0:Apr 13 13:23:59.999 EST: fca_server[165]: bridge_asic_get_ver: msg send 
problem: Invalid argument 
LC/0/1/CPU0:Apr 13 13:24:03.156 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:24:03.543 EST: sysmgr[89]: %OS-SYSMGR-7-DEBUG : 
sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.   
LC/0/1/CPU0:Apr 13 13:24:04.113 EST: sync_agent[310]: %PLATFORM-FSYNC-6-UNKNOWN_BOARD_TYPE 
: Frequency Synchronization feature does not recognize hardware board type 0x1000305 
LC/0/1/CPU0:Apr 13 13:24:04.163 EST: sync_agent[310]: %PLATFORM-FSYNC-6-NOT_SUPPORTED : 
Frequency Synchronization is not supported on this line card. 
RP/0/RSP0/CPU0:Apr 13 13:24:04.464 EST: syslog_dev[93]: envmon[199]:  
RP/0/RSP0/CPU0:Apr 13 13:24:04.466 EST: syslog_dev[93]: envmon[199]: 
envmon_sam_sensor_cens_handler:359 mytype is not ENS_CMD_WRITE 
LC/0/1/CPU0:Apr 13 13:24:06.247 EST: BM-ADJ[129]: Registering for SysDB notifications ...
LC/0/1/CPU0:Apr 13 13:24:07.585 EST: fib_mgr[167]: Initializing APIV modules ...
LC/0/1/CPU0:Apr 13 13:24:07.600 EST: fib_mgr[167]: Registering for SysDB notifications ...
LC/0/1/CPU0:Apr 13 13:24:08.350 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:24:16.422 EST: canb_upg_agt[134]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : 
cbc instance 0 is down-rev (V18.04), upgrade to (V18.05). Use the "upgrade hw-module fpd" 
CLI in admin mode. 
LC/0/1/CPU0:Apr 13 13:24:16.910 EST: l2fib[231]: Initializing L2 FIB APIV modules ...
LC/0/1/CPU0:Apr 13 13:24:16.937 EST: l2fib[231]:  L2fib Registering for SysDB 
notifications ...
RP/0/RSP0/CPU0:Apr 13 13:24:21.806 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:IOS XR RUN 
RP/0/RSP0/CPU0:Apr 13 13:24:21.826 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: IOS XR RUN 
LC/0/1/CPU0:Apr 13 13:24:22.738 EST: ifmgr[189]: %PKT_INFRA-LINK-5-CHANGED : Interface 
Service-Mgmt0/1/0/3, changed state to Administratively Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.744 EST: cfgmgr-lc[138]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/1/0' has been restored. 
LC/0/1/CPU0:Apr 13 13:24:22.754 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.755 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.755 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.758 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.764 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.767 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.049 EST: cfgmgr-lc[138]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/1/0' has been restored. 
LC/0/1/CPU0:Apr 13 13:24:25.052 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.053 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.053 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.054 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.055 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.058 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.061 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.064 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:26.107 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.107 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.108 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.108 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.110 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.110 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.111 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.112 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.115 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.116 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.117 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.118 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.119 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.120 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:50.648 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:04.333 EST: ipv4_mfwd_partner[224]: Registering for SysDB 
notifications ...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: ipv4_mfwd_partner[224]: Initializing APIV modules ...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: l2fib[231]: Starting of APIV version negotiation ...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: fib_mgr[167]: Starting of APIV version negotiation 
...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: BM-ADJ[129]: Starting of APIV version negotiation ...
LC/0/1/CPU0:Apr 13 13:25:07.459 EST: vkg_sis[293]: Starting of APIV version negotiation 
(CREATE) ...
LC/0/1/CPU0:Apr 13 13:25:08.094 EST: inv_agent[196]: %PLATFORM-INV_AGENT-7-INFO : Sending 
SIM x86 inventory info  
LC/0/1/CPU0:Apr 13 13:25:09.634 EST: vkg_sis[293]: SIS APIV is up
LC/0/1/CPU0:Apr 13 13:25:10.471 EST: ipv4_mfwd_partner[224]: MCAST APIV is up
LC/0/1/CPU0:Apr 13 13:25:10.489 EST: l2fib[231]: ISM L2FIB: IPCP is up fd:50099c58, 
stats_fd:0
LC/0/1/CPU0:Apr 13 13:25:11.624 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:13.620 EST: fib_mgr[167]: L3 FIB, FRR, LOOKUP & MISC APIV is up
LC/0/1/CPU0:Apr 13 13:25:13.622 EST: fib_mgr[167]: Initialized FIB State Machine!!!
LC/0/1/CPU0:Apr 13 13:25:16.737 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:16.737 EST: vkg_sis[293]: Received SE Operation Ready 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:16.740 EST: ism_se_sm[127]: %PLATFORM-SIM_SE-5-STATE_CHANGE : 
Service Engine is in ready state. 
LC/0/1/CPU0:Apr 13 13:25:16.742 EST: ism_se_sm[127]: %PLATFORM-SIM_SE-5-SW_INFO : Service 
Engine heartbeat started on A9K-ISM-100 
LC/0/1/CPU0:Apr 13 13:25:26.744 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.745 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.745 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.745 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.746 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.746 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.747 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.747 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.750 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.758 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.760 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.763 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.765 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.806 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:29.814 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 0 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.815 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 1 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.817 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 2 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.821 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 3 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.824 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 4 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.827 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 5 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.830 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 7 XAUI 
link status changed to UP!! 
RP/0/RSP0/CPU0:Apr 13 13:26:23.489 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM0, state: OK 
RP/0/RSP0/CPU0:Apr 13 13:26:23.716 EST: invmgr[235]: %PLATFORM-INV-6-OIRIN : OIR: Node 
0/1/SAM0 inserted  
RP/0/RSP0/CPU0:Apr 13 13:26:23.718 EST: eem_ed_oir[185]: Messge received content : Event 0 
NodeId: 0x81c 
RP/0/RSP0/CPU0:Apr 13 13:26:36.684 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM1, state: OK 
RP/0/RSP0/CPU0:Apr 13 13:26:36.697 EST: invmgr[235]: %PLATFORM-INV-6-OIRIN : OIR: Node 
0/1/SAM1 inserted  
RP/0/RSP0/CPU0:Apr 13 13:26:36.699 EST: eem_ed_oir[185]: Messge received content : Event 0 
NodeId: 0x81d 
RP/0/RSP0/CPU0:Apr 13 13:29:30.316 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM0, state: OK 
RP/0/RSP0/CPU0:Apr 13 13:29:41.314 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM1, state: OK 
 
   

The Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card now has the Release 2.4.1 TV CDS software installed. The next step is to initially configure the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card, which requires that you run the cdsconfig script and answer the prompts appropriately for your deployment. See the "Preparing to Initially Configure the CDEs" section for more information.

Initial Configuration Sequence of the Content Delivery System (CDS)

This section describes the initial configuration sequence for a Content Delivery System (CDS). A CDS consists of Streamers and Vaults, or ISVs. For instructions on configuring a Virtual Video Infrastructure (VVI) refer to the Cisco TV CDS 2.3 Installation, Upgrade, and Maintenance Guide online. A VVI includes Caching Nodes and possibly split-domain management.

VVI Initial Configuration Sequence

The order in which you initially configure the CDEs for VVI is very important. The VVIM (Vault/Cache CDSM) and all the Vaults and Caching Nodes in the VVIM domain must be configured first and brought online before the Stream Domain is configured. A high-level view of the initial configuration order follows:

1. Vaults and Caching Nodes—Log in to the VVIM GUI and configure each Vault and Caching Node.

2. Stream Manager (CDSM)—See the "Initially Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card" section for more information.

Log in to the CDSM GUI as a user with Engineering access and configure the CDSM Setup page.

3. Streamers—See the "Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card as a Streamer" section for more information. Make sure the Streamer is configured completely and displaying in the Stream Manager's System Health Monitor page before moving on to the next Streamer.

4. Log in to the Stream Manager GUI and configure each Streamer.

5. Repeat 3 and 4 for each Stream Domain in the VVI.

6. Redundant VVIM and Stream Manager—See the "Initially Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card" section for more information.

For more information about the CDSM (or VVIM) GUI, see the "Getting Started" chapter in either the Cisco TV CDS ISA 2.3 Software Configuration Guide or the Cisco TV CDS RTSP 2.4 Software Configuration Guide.


Note In an ISA environment, the ISA services cannot be started until the Stream Manager is up and at least one Streamer in a Stream Domain has had the VHO Setup and VHO ISA Setup settings configured.


CDS Initial Configuration Sequence

The only requirement with regards to the order in which you initially configure the CDEs for a CDS is that the CDSM must be configured first. The Vaults and Streamers are initialized next, followed by a second CDSM for redundancy. If the CDS consists of ISVs and CDSMs, initialize the primary CDSM first, followed by the ISVs and then the secondary CDSM.

Preparing to Initially Configure the CDEs

Refer to the ISM (Integrated Service Module) Line Card Software Installation Overview appendix in the Cisco ASR 9000 Aggregation Services Router ISM Line Card Installation Guide online. This appendix describes the required steps to install Cisco IOS XR software in support of the ISM (Integrated Service Module) line card on the Cisco ASR 9000 Series Aggregation Services Router.

It includes the following sections:

Upgrading Field-Programmable Devices

Entering System Recovery Mode

Configuring the ISM Service-Management Interface

Copying and Extracting the Image Files

Reloading the ISM Line Card

Installing the ISO Image File

Configuring the Service Engine Interfaces to the ISM

Running the cdsconfig Script

For instructions on configuring a Virtual Video Infrastructure (VVI) refer to the Cisco TV CDS 2.3 Installation, Upgrade, and Maintenance Guide online.

Before you run the initial configuration script, you should gather the following information:

IP address and subnet mask of the CDE management interface—For the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card the eth0 interface is used for the management interface.

IP address of the default gateway interface—This is the address of the interface on the router that is directly attached to the CDE management (eth0) interface.

Hostname for the CDE—Name for the device host.

Group ID—A unique user-defined value. All CDS servers (ssv [ISV], Vault, Streamer, controller [CDSM]) that are part of the same system (managed by one CDSM) have the same group ID. This group ID should be unique across an enterprise. All CDS servers that are part of a VVI have different group IDs depending on the number of managers (CDSMs and VVIMs).

Server ID—A unique user-defined value. The ID must be unique for each CDS device.


Note If you are installing a VVI system with split-domain management, the server ID for Streamers in a Stream Domain is generated by the Stream Manager.


Replication group members—The CDS servers that are replication group members and the IP address of each member. The servers to include in a replication group depends on the network design for the CDS.


Note With the exception of the CDS server you are configuring, all CDS servers (VVIMs, Stream Managers, ISVs, Caching Nodes, Vaults, and Streamers) that are members of the replication group should be configured at this time. The server you are configuring is not configured as a replication group member.


In simple cases, because all CDS servers share information with each other, all servers are in each other's replication group.

In more complex cases, only a subset of the servers are included in a replication group. As an example, if Streamers only talk to the CDSM, Vaults, and Streamers within a specific Streamer group, then the Streamers replication group includes only these servers.

In both the CDS and VVI, all Vaults, Caching Nodes, and Streamers (or ISVs) are identified by an array ID, a group ID, and a server ID. In the CDSM GUI, the array ID identifies servers that are part of the same system, the group ID identifies servers that are part of the same group (Vault Group or Stream Group), and the server ID is a unique number that identifies the server. Table 1-1 lists the CDSM GUI ID names and maps them to the CServer names in the setupfile and .arroyorc files.

Table 1-1 ID Names in the CDSM GUI and CServer Files 

CDSM GUI ID Name
CServer Files ID Name

Array ID on the Array Name page

groupid

Group ID on the Server-Level pages

groupid

Stream Group ID on the Server Setup page

arrayid

Cache Group ID on the Server Setup page

arrayid

Vault Group ID on the Server Setup page

arrayid

Stream Group ID on the Configuration Generator page

arrayid



Note During the initialization process of a CDS server or after recovering a CDS server that has been down for less than an hour, the CDS database performs a complete synchronization. The database synchronization takes about five minutes before the server becomes ready for service. If the CDS server is down for a much longer time than an hour, the database synchronization takes longer than five minutes. The netstat command does not show the interfaces as up until the synchronization has completed.


Initially Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card

To initially configure the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card, do the following:


Step 1 Log in to the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card as root.

[root@CDSM-2 ]# ssh root@20.20.1.11
	 The authenticity of host '20.20.1.11 (20.20.1.11)' can't be established.
	 RSA key fingerprint is 66:aa:97:0a:a5:31:e2:8a:d7:f0:da:84:ff:ab:f8:0d.
	 Are you sure you want to continue connecting (yes/no)? yes
	 Warning: Permanently added '20.20.1.11' (RSA) to the list of known hosts.
	 root@20.20.1.11's password: 
	 Last login: Sat May  7 18:10:33 2011 from 20.20.1.3
 [root@Ilocalhost ~]# 
 
   
 
   

Step 2 Run the cdsconfig script. The script displays prompts with the default values in brackets. If a default value is correct, press Enter to accept the value; otherwise, enter the correct value and press Enter. Note that the following example is for adding a Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card into an existing deployment.

[root@localhost ~]# cdsconfig                                         
ATTENTION!!!                                              
 If a new image is installed on this server, a reboot is required before running 
cdsconfig.If a reboot is already performed, please continue.Otherwise, please exit and 
execute cdsconfig after rebooting the server Do you want to continue ? (yes/no) [y]: y
Enter management interface [eth0]: 
Please ensure an IP address and netmask are configured for  management interface eth0: 
 
   
Enter a hostname [localhost.localdomain]: avsm-110
Backing up /etc/sysconfig/network
Writing new /etc/sysconfig/network
Backing up /etc/hosts
Writing new /etc/hosts
Skipping network restart for AVSM
Network configuration complete
 
   
Skipping network restart for AVSM
Network configuration complete
Use detected platform: A9K-ISM-100 ? (yes/no) [y]: y  <<<<<< Note Platform
 
   
Please select a device role:
    1. streamer
Choice: 1
Is this Server going to get added to a Stream Domain in a CDN Split Domain Management 
Environment ? (yes/no) [y]: n
Please enter a Group ID(Array ID): 6147
Please enter a server ID [3]: 1232
Enter Stream Control interface (Hit 'Enter' to skip):
Writing new configuration to /home/isa/.arroyorc
No existing replication group information found
Do you want to configure replication group members now? (yes/no) [y]:
 
   
There are currently no replication group members.
Do you want to add another replication group member? (yes/no) [y]:
 
   
 
   

Step 3 When the cdsconfig script completes, edit the rc.local file and uncomment all the command lines. The su - isa -c "cd /home/isa/RTScheduler/Exporter..." command is only used when the MediaX feature needs to send notifications to a catalog server or similar type of server. Following is an example with all the lines uncommented:

# vi /etc/rc.local
 
   
#!/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
/etc/ism/ip_rules.sh
# Lines below this one modified by cdsflavconfig (ISA):
 
   
# All CDS/TV commands are run in a CDS-TV subshell
RC_LOCAL_LOG=/root/rc.local.log
echo "***************************************************" # CDS-TV subshell
echo "Starting CDS/TV application in background." # CDS-TV subshell
echo "Application startup logs written to $RC_LOCAL_LOG." # CDS-TV subshell
echo "***************************************************" # CDS-TV subshell
 
   
( # Start of CDS-TV subshell
 
   
su - isa -c "cd /home/isa/IntegrationTest; ./init_isa_env"
 
   
sleep 30
 
   
 
   
# Firmware upgrade for ssd
/usr/sbin/cdsupgradessdfw
 
   
/usr/bin/avslauncher >& /root/avslauncher.log&
 
   
sleep 5
 
   
# Uncomment the following line to start cserver:
/arroyo/test/run
 
   
sleep 30
 
   
# Streamer
su - isa -c "cd /home/isa/IntegrationTest; ./run_isa --handle_orphan_streams >>&
/home/isa/IntegrationTest/ns_log&"
 
   
sleep 30
 
   
# Streamer
/home/stats/statsd -d eth0
 
   
# Uncomment the following line for kdump
echo 1 > /proc/sys/kernel/panic
 
   
# End of CDS-TV subshell
) > $RC_LOCAL_LOG 2>&1 &
 
   
 
   

Step 4 Reboot the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card from your terminal connection to the Cisco ASR 9000 Series Aggregation Services Router Route Processor card.

# hw-module location 0/ISM slot number on ASR9K/CPU0 reload
 
   

Here is the example output from executing the hw-module location 0/1/CPU0 reload command:

RP/0/RSP0/CPU0:VKG-2#hw-module location 0/1/CPU0 reload 
WARNING: This will take the requested node out of service.
Do you wish to continue?[confirm(y/n)]y
 
   
RP/0/RSP0/CPU0:Apr 13 13:21:01.329 EST: shelfmgr[357]: %PLATFORM-SHELFMGR-6-USER_RESET : 
Node 0/1/CPU0 is reset due to user reload request 
RP/0/RSP0/CPU0:Apr 13 13:21:01.335 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:IOS XR FAILURE 
LC/0/1/CPU0:Apr 13 13:21:01.338 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:21:01.338 EST: ism_se_sm[127]: %PLATFORM-SIM_SE-5-STATE_CHANGE : 
Service Engine is in shutting down state. 
LC/0/1/CPU0:Apr 13 13:21:01.340 EST: ipv4_mfwd_partner[224]: Deactivating MCAST APIV ...
LC/0/1/CPU0:Apr 13 13:21:01.340 EST: l2fib[231]: Deactivating APIV module 
MOD_ID_ISM_L2FIB...
LC/0/1/CPU0:Apr 13 13:21:01.340 EST: vkg_sis[293]: Starting of SI APIV Deletion ...
RP/0/RSP0/CPU0:Apr 13 13:21:01.417 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM0 removed  
RP/0/RSP0/CPU0:Apr 13 13:21:01.419 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81c 
RP/0/RSP0/CPU0:Apr 13 13:21:01.434 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM1 removed  
RP/0/RSP0/CPU0:Apr 13 13:21:01.435 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81d 
LC/0/1/CPU0:Apr 13 13:21:03.003 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.003 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.004 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.004 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.005 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.006 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.006 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.007 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.007 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.007 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:21:03.008 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Down 
RP/0/RSP0/CPU0:Apr 13 13:21:08.968 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM1, state: BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:21:08.979 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM0, state: BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:22:01.474 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:22:01.541 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM0 removed  
RP/0/RSP0/CPU0:Apr 13 13:22:01.546 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81c 
RP/0/RSP0/CPU0:Apr 13 13:22:01.572 EST: invmgr[235]: %PLATFORM-INV-6-OIROUT : OIR: Node 
0/1/SAM1 removed  
RP/0/RSP0/CPU0:Apr 13 13:22:01.573 EST: eem_ed_oir[185]: Messge received content : Event 1 
NodeId: 0x81d 
RP/0/RSP0/CPU0:Apr 13 13:22:01.584 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: BRINGDOWN 
RP/0/RSP0/CPU0:Apr 13 13:22:13.235 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:ROMMON 
RP/0/RSP0/CPU0:Apr 13 13:22:44.043 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR_HAL-6-BOOT_REQ_RECEIVED : Boot Request from 0/1/CPU0, RomMon Version: 
1.2 
RP/0/RSP0/CPU0:Apr 13 13:22:44.046 EST: shelfmgr[357]: %PLATFORM-MBIMGR-7-IMAGE_VALIDATED 
: Remote location 0/1/CPU0: : MBI tftp:/disk0/asr9k-os-mbi-4.1.0.35I/lc/mbiasr9k-lc.vm 
validated 
RP/0/RSP0/CPU0:Apr 13 13:22:44.047 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:MBI-BOOTING 
RP/0/RSP0/CPU0:Apr 13 13:23:35.447 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:MBI-RUNNING 
LC/0/1/CPU0:15: init[65540]: %OS-INIT-7-MBI_STARTED : total time 9.242 seconds 
LC/0/1/CPU0:Apr 13 13:23:38.912 EST: insthelper[61]: %INSTALL-INSTHELPER-7-PKG_DOWNLOAD : 
MBI running; starting software download 
LC/0/1/CPU0:Apr 13 13:23:53.184 EST: sysmgr[89]: %OS-SYSMGR-5-NOTICE : Card is COLD 
started  
LC/0/1/CPU0:Apr 13 13:23:53.490 EST: init[65540]: %OS-INIT-7-INSTALL_READY : total time 
28.024 seconds 
LC/0/1/CPU0:Apr 13 13:23:54.820 EST: sysmgr[316]: %OS-SYSMGR-6-INFO : Backup system 
manager is ready  
LC/0/1/CPU0:Apr 13 13:23:55.989 EST: syslog_dev[87]: dumper_config[153]:  
LC/0/1/CPU0:Apr 13 13:23:56.027 EST: syslog_dev[87]: dumper_config[153]:  The node id is 
2065 
LC/0/1/CPU0:Apr 13 13:23:58.631 EST: linux_maint_fpd_agent[236]: linux_maint_fpd_agent: 
Registering the handlers
LC/0/1/CPU0:Apr 13 13:23:58.645 EST: linux_maint_fpd_agent[236]: 
update_linux_maint_sw_version Updated the sw_ver 6
LC/0/1/CPU0:Apr 13 13:23:58.648 EST: linux_maint_fpd_agent[236]: publish_maint_fpd_info 
Publishing FPD info : type 1, subtype 4, card type 16777989, module 0, instance 0, sw_ver 
6, hw_ver 1
LC/0/1/CPU0:Apr 13 13:23:58.878 EST: vkg_sis[293]: Initializing APIV modules ...
LC/0/1/CPU0:Apr 13 13:23:58.890 EST: vkg_sis[293]: Registering for SysDB notifications ...
LC/0/1/CPU0:Apr 13 13:23:58.897 EST: vkg_sis[293]: Registering for SysDB SE READY 
notifications ...
LC/0/1/CPU0:Apr 13 13:23:59.997 EST: fca_server[165]: bridge_asic_get_ver: msg send 
problem: Invalid argument 
LC/0/1/CPU0:Apr 13 13:23:59.999 EST: fca_server[165]: bridge_asic_get_ver: msg send 
problem: Invalid argument 
LC/0/1/CPU0:Apr 13 13:24:03.156 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:24:03.543 EST: sysmgr[89]: %OS-SYSMGR-7-DEBUG : 
sysmgr_admin_plane_check:SYSMGR_PLANE_ADMIN Notification sent.   
LC/0/1/CPU0:Apr 13 13:24:04.113 EST: sync_agent[310]: %PLATFORM-FSYNC-6-UNKNOWN_BOARD_TYPE 
: Frequency Synchronization feature does not recognize hardware board type 0x1000305 
LC/0/1/CPU0:Apr 13 13:24:04.163 EST: sync_agent[310]: %PLATFORM-FSYNC-6-NOT_SUPPORTED : 
Frequency Synchronization is not supported on this line card. 
RP/0/RSP0/CPU0:Apr 13 13:24:04.464 EST: syslog_dev[93]: envmon[199]:  
RP/0/RSP0/CPU0:Apr 13 13:24:04.466 EST: syslog_dev[93]: envmon[199]: 
envmon_sam_sensor_cens_handler:359 mytype is not ENS_CMD_WRITE 
LC/0/1/CPU0:Apr 13 13:24:06.247 EST: BM-ADJ[129]: Registering for SysDB notifications ...
LC/0/1/CPU0:Apr 13 13:24:07.585 EST: fib_mgr[167]: Initializing APIV modules ...
LC/0/1/CPU0:Apr 13 13:24:07.600 EST: fib_mgr[167]: Registering for SysDB notifications ...
LC/0/1/CPU0:Apr 13 13:24:08.350 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:24:16.422 EST: canb_upg_agt[134]: %PLATFORM-UPGRADE_FPD-4-DOWN_REV : 
cbc instance 0 is down-rev (V18.04), upgrade to (V18.05). Use the "upgrade hw-module fpd" 
CLI in admin mode. 
LC/0/1/CPU0:Apr 13 13:24:16.910 EST: l2fib[231]: Initializing L2 FIB APIV modules ...
LC/0/1/CPU0:Apr 13 13:24:16.937 EST: l2fib[231]:  L2fib Registering for SysDB 
notifications ...
RP/0/RSP0/CPU0:Apr 13 13:24:21.806 EST: shelfmgr[357]: 
%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE : 0/1/CPU0 A9K-ISM-100 state:IOS XR RUN 
RP/0/RSP0/CPU0:Apr 13 13:24:21.826 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/CPU0, state: IOS XR RUN 
LC/0/1/CPU0:Apr 13 13:24:22.738 EST: ifmgr[189]: %PKT_INFRA-LINK-5-CHANGED : Interface 
Service-Mgmt0/1/0/3, changed state to Administratively Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.741 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:22.744 EST: cfgmgr-lc[138]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/1/0' has been restored. 
LC/0/1/CPU0:Apr 13 13:24:22.754 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.755 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.755 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.758 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.764 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:22.767 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.046 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.047 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:25.049 EST: cfgmgr-lc[138]: %MGBL-CONFIG-6-OIR_RESTORE : 
Configuration for node '0/1/0' has been restored. 
LC/0/1/CPU0:Apr 13 13:24:25.052 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.053 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.053 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.054 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.055 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.058 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.061 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:25.064 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:24:26.107 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.107 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.108 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.108 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.110 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.110 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.111 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.112 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.115 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.116 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.117 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.118 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.119 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:26.120 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Down 
LC/0/1/CPU0:Apr 13 13:24:50.648 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:04.333 EST: ipv4_mfwd_partner[224]: Registering for SysDB 
notifications ...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: ipv4_mfwd_partner[224]: Initializing APIV modules ...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: l2fib[231]: Starting of APIV version negotiation ...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: fib_mgr[167]: Starting of APIV version negotiation 
...
LC/0/1/CPU0:Apr 13 13:25:07.458 EST: BM-ADJ[129]: Starting of APIV version negotiation ...
LC/0/1/CPU0:Apr 13 13:25:07.459 EST: vkg_sis[293]: Starting of APIV version negotiation 
(CREATE) ...
LC/0/1/CPU0:Apr 13 13:25:08.094 EST: inv_agent[196]: %PLATFORM-INV_AGENT-7-INFO : Sending 
SIM x86 inventory info  
LC/0/1/CPU0:Apr 13 13:25:09.634 EST: vkg_sis[293]: SIS APIV is up
LC/0/1/CPU0:Apr 13 13:25:10.471 EST: ipv4_mfwd_partner[224]: MCAST APIV is up
LC/0/1/CPU0:Apr 13 13:25:10.489 EST: l2fib[231]: ISM L2FIB: IPCP is up fd:50099c58, 
stats_fd:0
LC/0/1/CPU0:Apr 13 13:25:11.624 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:13.620 EST: fib_mgr[167]: L3 FIB, FRR, LOOKUP & MISC APIV is up
LC/0/1/CPU0:Apr 13 13:25:13.622 EST: fib_mgr[167]: Initialized FIB State Machine!!!
LC/0/1/CPU0:Apr 13 13:25:16.737 EST: vkg_sis[293]: Received SYSDB_EVENT_SET 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:16.737 EST: vkg_sis[293]: Received SE Operation Ready 
Notification.....
LC/0/1/CPU0:Apr 13 13:25:16.740 EST: ism_se_sm[127]: %PLATFORM-SIM_SE-5-STATE_CHANGE : 
Service Engine is in ready state. 
LC/0/1/CPU0:Apr 13 13:25:16.742 EST: ism_se_sm[127]: %PLATFORM-SIM_SE-5-SW_INFO : Service 
Engine heartbeat started on A9K-ISM-100 
LC/0/1/CPU0:Apr 13 13:25:26.744 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.745 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.745 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.745 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.746 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.746 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.747 EST: ifmgr[189]: %PKT_INFRA-LINK-3-UPDOWN : Interface 
Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.747 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.750 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/0, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.758 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.760 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/1, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.763 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.765 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Mgmt0/1/0/2, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:26.806 EST: ifmgr[189]: %PKT_INFRA-LINEPROTO-5-UPDOWN : Line 
protocol on Interface Service-Engine0/1/0/3, changed state to Up 
LC/0/1/CPU0:Apr 13 13:25:29.814 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 0 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.815 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 1 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.817 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 2 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.821 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 3 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.824 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 4 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.827 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 5 XAUI 
link status changed to UP!! 
LC/0/1/CPU0:Apr 13 13:25:29.830 EST: ism_agent[126]: %ISM_SIA-6-INFO : Interface # 7 XAUI 
link status changed to UP!! 
RP/0/RSP0/CPU0:Apr 13 13:26:23.489 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM0, state: OK 
RP/0/RSP0/CPU0:Apr 13 13:26:23.716 EST: invmgr[235]: %PLATFORM-INV-6-OIRIN : OIR: Node 
0/1/SAM0 inserted  
RP/0/RSP0/CPU0:Apr 13 13:26:23.718 EST: eem_ed_oir[185]: Messge received content : Event 0 
NodeId: 0x81c 
RP/0/RSP0/CPU0:Apr 13 13:26:36.684 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM1, state: OK 
RP/0/RSP0/CPU0:Apr 13 13:26:36.697 EST: invmgr[235]: %PLATFORM-INV-6-OIRIN : OIR: Node 
0/1/SAM1 inserted  
RP/0/RSP0/CPU0:Apr 13 13:26:36.699 EST: eem_ed_oir[185]: Messge received content : Event 0 
NodeId: 0x81d 
RP/0/RSP0/CPU0:Apr 13 13:29:30.316 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM0, state: OK 
RP/0/RSP0/CPU0:Apr 13 13:29:41.314 EST: invmgr[235]: %PLATFORM-INV-6-NODE_STATE_CHANGE : 
Node: 0/1/SAM1, state: OK 
 
   
 
   

Step 5 To verify that the CDS manager (Stream Manager or CDSM) is operational, using your web browser, enter the IP address of your CDS manager.

For example, if the IP address of your CDSM is 192.168.0.236, you can access it by entering http://192.168.0.236 in the address or location text box of your browser program.

The System Login page is displayed (see Figure 1-1).

Figure 1-1 CDSM Login Page

Step 6 Log in to the CDS manager GUI. Enter admin as the user name and admin as the password and click Login.

If you are unable to log in with the user name admin and the password admin, log in to the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) line card Linux command line and run the /home/stats/runonce command, then log in to the CDS manager GUI again.

The CDSM Setup page is displayed.

Step 7 Use the CDSM GUI to complete the configuration.

For more information, see one of the following:

For an ISA deployment, see the "Getting Started" chapter in the Cisco TV CDS 2.4 ISA Software Configuration Guide.

For an RTSP deployment, see the "Getting Started" chapter in the Cisco TV CDS 2.4 RTSP Software Configuration Guide.


Configuring the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card as a Streamer

To install the TV CDS software and initially configure the Cisco ASR 9000 Series Aggregation Services Router ISM (Integrated Service Module) Line Card as a streamer, do the following:


Step 1 Log in to the Cisco ASR 9000 Series Aggregation Services Router as root.

Step 2 Run the cdsconfig script. The script displays prompts with the default values in brackets. If a default value is correct, press Enter to accept the value; otherwise, enter the correct value and press Enter.

[root@ism ~]# cdsconfig
 
   
ATTENTION!!!
If a new image is installed on this server, a reboot is required before running 
cdsconfig.
If a reboot is already performed, please continue.
Otherwise, please exit and execute cdsconfig after rebooting the server
 
Do you want to continue ? (yes/no) [y]: y
Enter management interface [eth0]: 
Please ensure an IP address and netmask are configured for
  management interface eth0: 
 
   
Enter a hostname [ism]: 
Backing up /etc/sysconfig/network
Writing new /etc/sysconfig/network
Backing up /etc/hosts
Writing new /etc/hosts
Skipping network restart for ISM
Network configuration complete
Use detected platform: A9K-ISM-100 ? (yes/no) [y]: 
 
   
Please select a device role:
    1. streamer
Choice: 1
Is this Server going to get added to a Stream Domain in a CDN Split Domain Manag
ement Environment ? (yes/no) [y]: no
Please enter a Group ID(Array ID): 6147
Please enter a server ID [3]: 1232
Enter Stream Control interface (Hit 'Enter' to skip): 
Writing new configuration to /home/isa/.arroyorc 
 
   
No existing replication group information found 
Do you want to configure replication group members now? (yes/no) [y]: 
 
   
There are currently no replication group members.
Do you want to add another replication group member? (yes/no) [y]: 
 
   
Select a role for the new replication group member. Select 'exit' to exit this menu:
    1. ssv
    2. vault
    3. streamer
    4. cache
    5. controller
    6. exit
Choice: 5
Enter an IP address for new controller: 15.10.19.2
 
   
Current replication group members:
  controller    15.10.19.2
Do you want to add another replication group member? (yes/no) [n]: yes
 
   
Select a role for the new replication group member. Select 'exit' to exit this m
enu:
    1. ssv
    2. vault
    3. streamer
    4. cache
    5. controller
    6. exit
Choice: 2
Enter an IP address for new vault: 15.10.30.2
 
   
Current replication group members:
  controller    15.10.19.2
  vault         15.10.30.2
Do you want to add another replication group member? (yes/no) [n]: 
Configuring ISA ecosystem
Is this node getting added to an existing deployment ? (yes/no) [y]: 
 
   
Starting database sync...
 
   
./start_db: Command not found.
1 size: 4180
2 size: 3148
3 size: 2136
4 size: 11412
5 size: 4180
6 size: 3148
7 size: 17628
8 size: 5208
10 size: 60
11 size: 1108
12 size: 52
14 size: 60
15 size: 2492
16 size: 156
17 size: 3164
18 size: 144
19 size: 180
20 size: 160
21 size: 1164
22 size: 16
23 size: 4228
24 size: 164
25 size: 14800
27 size: 1108
28 size: 3508
29 size: 156
30 size: 1108
31 size: 276
32 size: 1916
33 size: 1496
34 size: 1880
35 size: 3672
36 size: 6676
37 size: 1548
38 size: 184
39 size: 1748
40 size: 1492
41 size: 212
42 size: 212
43 size: 244
44 size: 144
45 size: 280
46 size: 156
48 size: 1024
49 size: 224
50 size: 660
51 size: 340
52 size: 2132
53 size: 1816
54 size: 440
56 size: 1440
57 size: 4244
58 size: 7468
59 size: 336
60 size: 204
63 size: 5336
64 size: 204
65 size: 24
66 size: 17732
70 size: 164
71 size: 1236
72 size: 5336
74 size: 3348
75 size: 2140
76 size: 5260
77 size: 12436
78 size: 6240
79 size: 340
80 size: 11412
81 size: 228
82 size: 24
83 size: 2208
84 size: 2128
85 size: 4348
86 size: 1168
88 size: 4180
89 size: 88
90 size: 2084
91 size: 84
92 size: 1444
93 size: 512
94 size: 172
95 size: 1512
96 size: 288
97 size: 2412
98 size: 5644
99 size: 160
100 size: 84
110 size: 476
111 size: 564
112 size: 5228
113 size: 88
115 size: 40
116 size: 292
117 size: 236
120 size: 5380
121 size: 1484
122 size: 14780
125 size: 24
128 size: 1296
130 size: 2292
131 size: 400
132 size: 144
134 size: 16488
135 size: 124
136 size: 2540
137 size: 2540
138 size: 2540
139 size: 1044
140 size: 10160
141 size: 3292
145 size: 116
146 size: 108
147 size: 360
148 size: 396
150 size: 1444
151 size: 184
152 size: 192
153 size: 11412
155 size: 1572
156 size: 832
157 size: 204
158 size: 292
159 size: 468
160 size: 240
161 size: 428
162 size: 2612
165 size: 672
166 size: 2192
167 size: 592
169 size: 17732
171 size: 1168
175 size: 1208
180 size: 2724
181 size: 2396
182 size: 1120
183 size: 152
184 size: 164
185 size: 212
191 size: 628
192 size: 6228
195 size: 120
200 size: 21772
204 size: 60
205 size: 16
206 size: 6292
207 size: 108
208 size: 1140
210 size: 2548
211 size: 2548
212 size: 240
213 size: 2732
214 size: 216
215 size: 104
220 size: 92
230 size: 1288
231 size: 1500
250 size: 80
266 size: 24656
267 size: 80
270 size: 660
271 size: 156
272 size: 144
273 size: 88
274 size: 28
275 size: 32
276 size: 32
trickle thread starting: tid: 4131216272
deadlock thread starting: tid: 4130163600
checkpoint thread starting: tid: 4129110928
trigger_worker thread starting: tid: 4128058256
15.10.19.2: Performing full resync for node addition with 15.10.19.2
15.10.19.2: Full Resync SUCCESS
15.10.30.2: Performing full resync for node addition with 15.10.30.2
   15.10.30.2: db_resync_content_object: still processing remote getall, 1000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 2000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 3000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 4000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 5000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 6000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 7000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: still processing remote getall, 8000 co
ntents processed so far
   15.10.30.2: db_resync_content_object: Finished with 8005 new records found an
d 0 records deleted, 8005 processed in getall
15.10.30.2: Full Resync SUCCESS
serverid: 1232 servertype: 2 ipaddr: 353698051
controller archiving thread starting: tid: 4042255248
rep_mgr thread starting: tid: 4041202576 rthreads: 2
pthread created: 4131216272
pthread created: 4130163600
pthread created: 4129110928
pthread created: 4128058256
pthread created: 4127001488
pthread created: 4125948816
pthread created: 4043307920
pthread created: 4042255248
pthread created: 4041202576
pthread created: 4040149904
replication threads: 2
trigger manager thread starting: tid: 4040149904
 
   
Database sync completed.
 
   
Run svrinit to seed database? (yes/no) [n]: yes
Please enter an IP address for svrinit [21.21.1.3]: 
Please enter a netmask for svrinit [255.255.255.0]: 
Please enter a hostname for svrinit [ism]: 
Please enter a gateway for svrinit: 21.21.1.1
21.21.1.3 (ism) ASM tables initialized!
Starting statsd
Is this an IPTV deployment with Dual CAS? (yes/no) [n]: 
Writing rc.local
ISA ecosystem configuration finished
cdsconfig finished, please use CDSM to complete configuration 
 
   

Note If the device role selected is a option 3 (Streamer), the cdsconfig script displays the following questions:

Is this server going to get added to a Stream Domain in a CDN Split Domain Management 
Environment? (yes/no) [y]: y
Is this Stream Domain going to use CCP as Cache Fill Protocol? (yes/no) [y]: y
Enter the IP address of the Stream Manager:
 
   

For Streamers in a VVI using CCP, the Streamer communicates with the Stream Manager to get a server ID. If the Streamer is unable to connect to the Stream Manager, the Stream Manager administrator can manually generate the server ID and send the information to the Streamer installer for manual entry.

For more information, see the "Identifying Server IDs and Group IDs for VVI with Split-Domain Management" section in the Cisco TV CDS ISA 2.3 Software Configuration Guide or the Cisco TV CDS RTSP 2.3 Software Configuration Guide.



Note If the device role is a Streamer, you have the option to enter the Stream Control interface using the cdsconfig script, or later through the CDSM GUI.


Writing new configuration to /home/isa/.arroyorc
 
   
No existing replication group information found
Do you want to configure replication group members now? (yes/no) [y]: y
 
   
There are currently no replication group members.
Do you want to add another replication group member? (yes/no) [y]: y
 
   
Select a role for the new replication group member:
    1. ssv
    2. vault
    3. streamer
    4. cdsm
5. cache
 
   
Choice: device_role 
Enter an IP address for new CDS_device: IP_Address 
 
   
Current replication group members: device_role IP_Address 
 
   
Do you want to add another replication group member? (yes/no) [n]: n 
 
   

Note For RTSP deployments, the cdsconfig script displays the following questions:

Is this an NGOD deployment (yes/no):
Choose NPT Syntax:
1. NGOD
2. NGOD_SC
3. Standard
Choice [NGOD]:3
Writing /home/isa/bss/scripts/arroyo-env.sh
Writing /home/isa/bss/scripts/arroyo-site-env.sh
Setting attributes for AVSRTSPServer
Do you want to enable Redirect Server ? (yes/no) [y]: n
Do you want to enable Authentication Server ? (yes/no) [y]: n
 
   

Is this node getting added to an existing deployment? (yes/no) [y]: n
Started avsdb, verify with "arroyo status"
Starting statsd
Run svrinit to seed database? (yes/no) [n]: y
Running svrinit
 
   

Note Always select yes because you must seed the database whenever you add a new CDE to a network. You are asked to enter the IP address, netmask, hostname, and gateway for the CDE you are configuring. These are the same parameters you entered when you started running this script.


Please enter an IP address for svrinit: mgmt_ip_address
Please enter a netmask for svrinit: mgmt_netmask
Please enter a hostname for svrinit: hostname
Please enter a gateway for svrinit gateway
 
   

Note If you receive an error message indicating the database is unavailable and cannot be set up, enter the following commands to initialize the database tables for a CDS server in an ISA environment:

[root]# su - isa 
[isa]# exit
[root]# /home/stats/svrinit_15 -h <hostname> -i <ip address> -s <mask-ip address> -g 
<gateway>
 
   

Enter the following commands to initialize the database tables for a CDS server in an RTSP environment:

[root]# su - isa 
[isa]# arroyo start avsdb 
[isa]# exit
[root]# /home/stats/svrinit_15 -h <hostname> -i <ip address> -s <mask-ip address> -g 
<gateway>

Step 3 Verify connectivity to the CDSM by logging in to the CDSM GUI.

The System Health Monitor page is displayed, showing the devices and their IP address (see Figure 1-2).

Figure 1-2 System Health Monitor Page

The TV CDS installation is complete.


Note In RTSP deployments, if you need to enable the Redirect Server in Release 2.4.1, run the cdsconfig script and answer yes (Y) at the following prompt:

Do you want to enable Redirect Server ? (yes/no) [y] y