Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
Migrating to a Cisco CRS-3 Carrier Routing System
Downloads: This chapterpdf (PDF - 2.84MB) The complete bookPDF (PDF - 8.67MB) | Feedback

Migrating to a Cisco CRS-3 Carrier Routing System

Table Of Contents

Migrating to a Cisco CRS-3 Carrier Routing System

Contents

CRS-1 to CRS-3 Software Migration Compatibility Matrix

Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System

ROMMON Upgrades

OPTION-A

OPTION-B

Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3

Checking your Existing Flash Disk Size

Flash Disk Upgrade Process to 4GB

Inserting the 4GB Flashdisk

Disk Formatting

Verifying the Disk File System

Setting Up Disk Mirroring

Swapping Mirrored Disks

Verifying Standby RP Disk Upgrade

Performing Switchover

Upgrading the Standby RP

File System Upgrade Procedure for 2GB Flash Disks

Reducing Disk Space Usage

Minimizing Traffic Loss During the Upgrade

Verifying that the System Meets RP Memory Requirements

IOS-XR Software Upgrade Procedure

Obtain the Required PIE Files

New Image Name Changes for 4.0 and Onwards

Verify System Stability

Additional Pre-upgrade System Checks

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

Post-Upgrade Procedure

Upgrade Firmware (Mandatory)

Caveats:

Upgrade Instructions for FAT32

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix

Information About Migrating to a Cisco CRS-3 Carrier Routing System

Verify That the Correct Version of IOS-XR Software is Installed

Benchmark the Traffic

How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot)

Administratively Disabling the Fabric Plane

What to Do Next

Disabling Power to the CRS-1 Fabric Card

Example

What to Do Next

Physically Removing the CRS-1 Fabric Card

Prerequisites

Required Tools and Equipment

Steps

What to Do Next

Installing a CRS-3 Fabric Card

Prerequisites

Required Tools and Equipment

Steps

What to Do Next

Verifying the Installation of the CRS-3 Fabric Card

Understanding the Alphanumeric LEDs

Troubleshooting the CRS-3 Fabric Card

Prerequisites

Powering up the Replaced Fabric Card

Prerequisites

Restrictions

What to Do Next

Troubleshooting Tips

Example

How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot)

Administratively Disabling the Fabric Plane

Prerequisites

Restrictions

What to Do Next

Disabling Power to the CRS-1 Fabric Card

Prerequisites

Restrictions

Example

What to Do Next

Physically Removing the CRS-1 Fabric Card

Prerequisites

Required Tools and Equipment

Steps

What to Do Next

Installing a CRS-3 Fabric Card

Prerequisites

Required Tools and Equipment

Steps

What to Do Next

Verifying the Installation of the CRS-3 Fabric Card

Understanding the Alphanumeric LEDs

Troubleshooting the CRS-3 Fabric Card

Prerequisites

Restrictions

Powering up the Replaced Fabric Card

Prerequisites

Restrictions

Booting Up the Newly Migrated Cisco CRS-3 Fabric

Administratively Enabling the Fabric Plane

Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node

Verifying Fabric Link Connectivity

How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot)

Administratively Disabling the Fabric Plane

Prerequisites

Restrictions

What to Do Next

Disabling Power to the CRS-1 Fabric Card

Prerequisites

Restrictions

Example

What to Do Next

Physically Removing the CRS-1 Fabric Card

Prerequisites

Required Tools and Equipment

Steps

What to Do Next

Installing a CRS-3 Fabric Card

Prerequisites

Required Tools and Equipment

Steps

What to Do Next

Verifying the Installation of the CRS-3 Fabric Card

Understanding the Alphanumeric LEDs

Troubleshooting the CRS-3 fabric card

Prerequisites

Powering up the Replaced Fabric Card

Prerequisites

Restrictions

Booting Up the Newly Migrated Cisco CRS-3 Fabric

Administratively Enabling the Fabric Plane

Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node

Verifying Fabric Link Connectivity

What to Do Next

Troubleshooting Tips

Example

Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System

Displaying Chassis Serial Numbers: Example

Adding a Fabric Card Chassis: Example

Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example

Where to Go Next

Additional References

Related Documents

Related Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Documentation

Related Documentation for Configuring the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Using Cisco IOS XR

Technical Assistance


Migrating to a Cisco CRS-3 Carrier Routing System


This chapter describes how to migrate a single-chassis Cisco CRS-1 Carrier Routing System to a single-chassis Cisco CRS-3 Carrier Routing System.


Note For an introduction to the single-chassis Cisco CRS-3 Carrier Routing System, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description. For information on planning a single-chassis Cisco CRS-3 Carrier Routing System system installation, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Site Planning Guide.


Feature History for the Cisco CRS-3 Carrier Routing System

Release
Modification

Release 4.0.0.T

The single-chassis Cisco CRS-3 Carrier Routing System was introduced.

Release 4.0.1

The single-chassis Cisco CRS-3 Carrier Routing System adds support for 100GE interfaces.

Release 4.0.2

Multishelf Cisco CRS-3 Carrier Routing System operation is supported and multishelf Cisco CRS-1 Carrier Routing System to multishelf Cisco CRS-3 Carrier Routing System migration is supported.


Contents

This chapter contains the following sections:

CRS-1 to CRS-3 Software Migration Compatibility Matrix

Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System

Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3

File System Upgrade Procedure for 2GB Flash Disks

IOS-XR Software Upgrade Procedure

Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix

Information About Migrating to a Cisco CRS-3 Carrier Routing System

How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot)

How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot)

How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot)

Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System

Where to Go Next

Additional References


Warning Do NOT insert any CRS-3 hardware before completing the software migration to Cisco IOS XR software Release 4.0.0.T or higher.

CRS-1 to CRS-3 Software Migration Compatibility Matrix

Your existing Cisco CRS-1 16-Slot Line Card Chassis must be running 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX) software before migrating to a Cisco CRS-3 16-Slot Line Card Chassis. Table 1-1 describes the migration paths that are supported.

Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix 

Current Version
Migration Version
Direct PIE Upgrade/Downgrade Supported

3.4.x(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information)

3.5.x(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information)

3.6.x(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information)

3.7.x(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information)

3.8.0(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.8.1(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.8.2(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.8.3(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

     
Current Version
Migration Version
Direct PIE Upgrade/Downgrade Supported

3.8.4(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.9.0(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.9.1(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

3.9.2(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

Yes. Migration to FAT32 recommended before upgrading.

4.0.0(PPC)

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

No (must be done using Turbo Boot - refer to Appendix A for more information). Upgrade package required.

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

4.0.0(PPC)

No (downgrades must be done using Turbo Boot - refer to Appendix A for more information).

4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX)

3.x.x(PPC)

No (downgrades must be done using Turbo Boot - refer to Appendix A for more information).



Note All IOS-XR Software releases prior to 3.8.0 (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be upgraded to IOS XR software release 3.8.0 or higher prior to being upgraded to IOS XR software release 44.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX) or be upgraded directly to IOS XR software release 4.0.0.T (PX), 4.0.1(PX), or 4.0.2(PX) using Turbo Boot - refer to Appendix A for more information.


Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System


Warning Do NOT insert any CRS-3 hardware before completing the software upgrade to Cisco IOS XR software Release 4.0.0.T or higher.

At least a 2 GB FAT32 flashdisk is required to upgrade to Cisco IOS XR software Release 4.0.0.T (PX) or Cisco IOS XR software Release 4.0.1(PX). Refer to the Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3 section for more information.

The minimum version of ROMMON software supported is ROMMON release 1.54. Refer to the ROMMON Upgrades section for more information.

ROMMON Upgrades

Your existing Cisco CRS-1 16-Slot Line Card Chassis Route Processors (RPs) and Distributed Route Processors (DRPs) must be running minimum ROMMON versions before migrating to a Cisco CRS-3 16-Slot Line Card Chassis. Table 1-2 describes the minimum ROMMON versions that are supported.

Table 1-2 Cisco CRS-1 to Cisco CRS-3 IOS XR Software Supported ROMMON Versions 

FPD
Minimum Version Required

Route Processor (RP)

1.54

Distributed Route Processor (DRP)

1.54



Warning While performing a turbo boot of 4.0.X (PX) images the ROMMON version needs to be 2.01 due to image size increase, otherwise the turbo boot will fail. Refer to Appendix A for more information on performing the turbo boot. Appendix A also describes how to upgrade your ROMMON version to 2.01

OPTION-A

Currently on most systems with IOS-XR Software Release 3.8.4 or higher or IOS-XR Software Release 3.9.0 or higher images ROMMON version 1.54 is supported/installed. While upgrading from IOS-XR Software Release 3.8.4 or higher to IOS-XR Software Release 4.0.0.X (PX) you can upgrade the FPD images using the Auto FPD procedure. The Auto FPD procedure upgrades the ROMMON images on ROMMON B before resetting the router for upgrades. After the software upgrade is complete and the router is up and running you then have to manually upgrade the ROMMON A images. Upgrade ROMMON A by executing the following command from admin mode:

RP/0/RP0/CPU0:CRS-1(admin)#upgrade rommon a all disk0
 
   

For Auto FPD to work please execute the following command in admin mode

RP/0/RP0/CPU0:CRS-1(admin-config)# fpd auto-upgrade 

OPTION-B

The other option is to upgrade the ROMMON manually after the image upgrade. The upgrade will not fail even if the ROMMON images are 1.54 or 1.52.

Detailed procedures for ROMMON upgrade is detailed inthe Upgrading and Downgrading ROM Monitor Firmware on Cisco CRS Routers section in the Cisco IOS XR ROM Monitor Guide for the Cisco CRS Router document online.

Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3

You can only upgrade your filesystem to FAT32 using the CLI specifed in this section if you are running Cisco IOS XR software Release 3.8.2 or above.

If you are running a release of Cisco IOS XR software earlier than 3.8.2 please refer to Upgrading Your File System From FAT16 to FAT32 in "Turbo Boot Procedure" for formatting the File system to FAT32 using KSH.

Cisco IOS XR software Release 4.0.X (PX) requires at least a 2GB flash disk for installation or upgrade. So prior to upgrading your current IOS XR software to IOS-XR Software Release 4.0.X (PX), you will need to upgrade the flash disk to either 2GB or 4GB.

The size of the image is significantly higher on the Cisco CRS-3 because x86 support is now included in addition to the PPC support. A FAT32 formatted flash disk will decrease the required space for the file system significantly. It is highly recommended to use a 4G flash disk with FAT-32 file-system on the Cisco CRS-3.

Checking your Existing Flash Disk Size

Execute the show filesystem command to check the actual disk0 size:

RP/0/RP0/CPU0:Router#sho filesystem
Wed Feb 11 15:28:57.401 PST PST
File Systems:
 
   
     Size(b)     Free(b)        Type  Flags  Prefixes
           -           -     network     rw  qsm/dev/fs/tftp:
           -           -     network     rw  qsm/dev/fs/rcp:
           -           -     network     rw  qsm/dev/fs/ftp:
     1043456     1005568  dumper-lnk     rw  qsm/dumper_nvram:
 39929724928 39605428224  dumper-lnk     rw  qsm/dumper_harddisk:
  1004994560   184500224  dumper-lnk     rw  qsm/dumper_disk1:
  1024606208   423608320  dumper-lnk     rw  qsm/dumper_disk0:
    62390272    49101348  dumper-lnk     rw  qsm/dumper_bootflash:
 39929724928 39605428224    harddisk     rw  harddisk:
  1024606208   423608320  flash-disk     rw  disk0:	-----
  1004994560   184500224  flash-disk     rw  disk1:
     1043456     1005568       nvram     rw  nvram:
    62390272    49101348       flash     rw  bootflash:
 
   

In the example shown, the flash disk (disk0) size is 1 Gig.

If the disk size is smaller than 2Gig you will need to upgrade the flash disk.

The procedures for flash disk upgrade are detailed in the Cisco XR 12000 Series Router and Cisco CRS-1 Router Flash Disk Upgrade Tasks document online here:

http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.html

Flash Disk Upgrade Process to 4GB

Inserting the 4GB Flashdisk

The first step is to insert a 4GB Cisco Authorized Flash disk into slot disk1 of Active and Standby RP. After Insertion verify the 4GB disk is accessible from RP

RP/0/RP0/CPU0:router# show filesystem disk1:
Model:       UNIGEN FLASH
Capacity:    8215201 Sectors, Total 4206182912 Bytes, (512 Bytes/sector
 
   

Disk Formatting

Format the 4GB flashdisk on standby RP disk1: by executing the following command

RP/0/RP0/CPU0:ios#format disk1: partition filesystem fat32 location 0/rp1/cpu0
 
   

The above command will create a partition of 3.5/0.5 between disk1 and disk1a


Note Executing this command will not cause the RP to reset


Verifying the Disk File System

Verify the filesytem is changed to FAT32 file system and desired 80% and 20% partition between disk1 and disk1a disks by executing the following command

RP/0/RP0/CPU0:ios#show media location 0/rp1/cpu0   
  Mountpoint       FsType  FsType   Size   State         DrvrPid  Mirror  Flags
================================================================================
  /disk1:          FAT16   FAT32    3.4G Mounted         0032792  Enabled
  /disk1a:         FAT16   FAT32    0.5G Mounted         0032792
 
   

Setting Up Disk Mirroring

Mirror the primary disk0 and standby disk1 disks on Standby RP using the command

RP/0/RP0/CPU0: LOAD(config)#mirror location 0/rp1/cpu0 disk0:disk1:
 
   

Verify that mirroring is enabled by executing the following command

RP/0/RP0/CPU0:LOAD#show mirror location 0/rp1/cpu0
 
   

Swapping Mirrored Disks

After verifying that disk mirroring is successfully enabled in the previous section, swap disk0 with disk1 (insert 4GB disk in disk0 slot)

Verifying Standby RP Disk Upgrade

Verify that the Standby RP boots with the 4GB flashdisk as the primary disk(disk0) on the Standby RP.

Performing Switchover

Perform an RP switchover and verify that the Standby RP becomes the Active RP.

Upgrading the Standby RP

Once you have verified the switchover was successful, repeat the flashdisk upgrade steps on the new Standby RP and verify results.

File System Upgrade Procedure for 2GB Flash Disks

First do the format of the boot device of the standby RP location.

format disk0: unpartition filesystem fat32 location 0/rp1/CPU0

This command formats the boot device of the standby RP and results in a reload of the standby RP. This will result in a 2GB FAT32 file system, Since the device is unpartitioned means no disk mirroring.

Once the standby RP reload, it would come back, format the device with your specifications and would start downloading all the packages from RP again. This takes time depending on the number of packages/config you have on the RP.

Verify using the below command that Standby RP disk is running with your expected filesystem/partition.

show media location 0/rp1/CPU0

Once the standby RP is up and running, perform a Switch Over from the active to the standby RP and let the new Standby RP (old Active) come up as standby Ready.

Perform the process for the new standby RP location as well.

Reducing Disk Space Usage

If the flash disk size is 2 Gig you still may want to increase available disk space. In order to provide as much room as possible on the disk, one can remove old files from the disk. This may include files which the operator has placed on the disk device such as PIE files or temporary directories that have been created.

When preparing for the upgrade to the next version of the operating system, the old, non-operational version should be removed.

To remove old SMU files and old versions of the operating system use the admin-commands

install commit

to ensure all active packages are 'committed', then issue the command

install remove inactive

The install remove inactive test sync command can be used first to show which packages will be removed from the disk.


Note In addition to checking the installation disk device, the bootflash device on the MSCs should also be checked. Extraneous files such as crashinfo files can be removed.


To check the free space of the bootflash use the following command:

dir bootflash: location 0/1/CPU0

Check if all the cards in the system are all up using the admin command

show platform

If any of the cards do not boot properly they have to be replaced or be shut down using the admin command

hw-module power disable location <loc>

Minimizing Traffic Loss During the Upgrade

To minimize traffic loss during the upgrade please follow below steps:


Step 1 Make sure that all the traffic flowing through the router which needs to be upgraded has an alternate path. In this scenario one can take one of the redundant routers out of service, upgrade it and then bring it back into service without any significant traffic loss (this should work for the core routers, for the edge devices usually the redundant path may not be available)

Step 2 Set IGP metric to the highest possible value so the IGP will try to route the traffic through the alternate path.

For OSPF use the max-metric command.

router(config-ospf)#max-metric router-lsa
 
   

For ISIS use the spf-overload-bit command.

router(config-isis)#set-overload-bit
 
   

Step 3 After all the software is upgraded restore the IGP metric by removing the commands:

For OSPF use the no max-metric command

router(config-ospf)#no max-metric router-lsa
 
   

For ISIS use the no spf-overload-bit command.

router(config-isis)#no set-overload-bit
 
   

Prior to release 3.8 the above commands have to be run before the install activate command is executed, resulting in a long period of time when the router is taken out of forwarding path.

To minimize this behavior starting from release 3.8, an enhancement has been provided which allows you to pause the install activate command just prior to the router reloading and to execute configuration changes such as IGP commands listed above.

Execute the following command to enable this install option:

router(config-isis)#install activate disk0:*4.0.* pause sw-change
 
   

You will be prompted prior to the system reload to execute configuration changes such as IGP commands. At this point the IGP cost-out operation can be executed.

Step 4 Copy the running-configuration and admin-configuration to a temporary storage location. This could be on a remote TFTP server or a device such as the hard disk: or disk0: present on the RP.

router#copy running-config tftp://...running_config.txt
router#admin
router(admin)#copy running-config tftp://...admin-running_config.txt
router(admin)#exit
 
   

Step 5 Verify Mgmt access to the router (see caveats section)

Step 6 While upgrading from 3.x.x images to 4.x.x images upgrade the file system of flash disks (boot device which is typically disk0) to FAT32 file system for 2 GB and 4 GB flash disks. The procedure to upgrade the file system of flash disks is different for 2GB and 4 GB Flash disks.


Verifying that the System Meets RP Memory Requirements

Due to image size increase on x86 based PX images you will need to have at least 1 GB of free memory on each of the Route Processor (RP) modules.

Execute the following command to verify the free memory on the RP.

RP/0/RP0/CPU0:BELUGA-QQ-4#show memory 
Tue Oct 12 22:17:28.761 PST
Physical Memory: 4096M total (1840M available)
 
   

IOS-XR Software Upgrade Procedure

For links to the latest IOS XR software upgrade instructions, refer to the Cisco IOS XR General Information page here:

http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html

Obtain the Required PIE Files

The Composite Mini Package is mandatory to perform the upgrade. The additional PIE files listed below are optional. whether they are needed or not depends on your router configuration and required features:

Table 1-3 OS XR PPX Software PIE Filenames 

PIE File Description
  Sample PIE Filename
  Package Name

Mini Package (OS-MBI, Base, Admin, Fwdg, lc Rout)

hfr-mini-px.pie-4.0.1 or 4.0.2

disk0:comp-hfr-mini-px-4.0.1 or 4.0.2

Upgrade Package* (see note)

hfr-upgrade-px.pie-4.0.1 or 4.0.2

disk0:hfr-px-upgrade-4.0.1 or 4.0.2

Multicast Package

hfr-mcast-px.pie-4.0.1 or 4.0.2

disk0:hfr-mcast-px-4.0.1 or 4.0.2

Manageability Package

hfr-mgbl-px.pie-4.0.1 or 4.0.2

disk0:hfr-mgbl-px-4.0.1 or 4.0.2

MPLS Package

hfr-mpls-px.pie-4.0.1 or 4.0.2

disk0:hfr-mpls-px-4.0.1 or 4.0.2

Security Package

hfr-k9sec-px.pie-4.0.1 or 4.0.2

disk0:hfr-k9sec-px-4.0.1 or 4.0.2

Diagnostic package

hfr-diags-px.pie-4.0.1 or 4.0.2

disk0:hfr-diags-px-4.0.1 or 4.0.2

Documentation package

hfr-doc-px.pie-4.0.1 or 4.0.2

disk0:hfr-doc-px-4.0.1 or 4.0.2

Field Programmable Device package

hfr-fpd-px.pie-4.0.1 or 4.0.2

disk0:hfr-fpd-px-4.0.1 or 4.0.2



Note The filenames listed here may not necessarily be the filenames of the actual files since the files can be renamed.  The actual filenames used will not affect the operation.



Note The upgrade Package needs to be activated along with the Mini Package.PIE file. The Upgrade Package is ONLY mandatory when performing the upgrade from 3.x to 4.x. The upgrade package must be deactivated and removed after the 3.x to 4.x upgrade operation is complete.
Currently removing the upgrade PIE file triggers a false error message stating that all the active packages will be removed. This message is due to a known bug which will be fixed in later releases. You can ignore this the false warning message and safely go ahead and remove the upgrade package despite the false warning message.


New Image Name Changes for 4.0 and Onwards

Table 1-4 lists the new file names for the images for IOS XR Software release 4.0.1(PX) and onwards.

Table 1-4 New Image Name Changes for IOS XR Software Release 4.0.1 (PX) and Onwards 

Old File Name
New File Name
Old Name on Router
New Name on Router

comp-hfr-mini.vm

hfr-mini-p.vm

comp-hfr-mini-4.0.1

hfr-mini-p-4.0.1

comp-hfr-full.vm

hfr-full-p.vm

comp-hfr-full-4.0.1

hfr-full-p-4.0.1

comp-hfr-mini-px.vm

hfr-mini-px.vm

comp-hfr-mini-px-4.0.1

hfr-mini-px-4.0.1

comp-hfr-full-px.vm

hfr-full-px.vm

comp-hfr-full-px-4.0.0.17C

hfr-full-px-4.0.1

comp-hfr-mini.pie

hfr-mini-p.pie

comp-hfr-mini-4.0.1

hfr-mini-p-4.0.1

comp-hfr-mini-px.pie

hfr-mini-px.pie

comp-hfr-mini-px-4.0.1

hfr-mini-px-4.0.1

hfr-fpd.pie

hfr-fpd-p.pie

hfr-fpd-4.0.1

hfr-fpd-p-4.0.1

hfr-upgrade.pie

hfr-upgrade-p.pie

NA

NA


.-p - only ppc based images

.-px - ppc + x86 based images

Verify System Stability

The following commands should be executed to verify basic system stability before the upgrade:

Execute the show platform command while in admin mode to verify that all nodes are in "IOS XR RUN" state, the PLIMs are in "OK" state, and that the SPAs are in "READY" state.

RP/0/RP0/CPU0:router(admin)#show platform 
Tue Oct 12 23:34:37.898 PST
Node            Type                 PLIM             State           Config State
--------------------------------------------------------------------------------------
-
0/0/CPU0        MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/1/CPU0        MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/2/CPU0        MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/3/CPU0        MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/4/CPU0        MSC-140G             20-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/5/CPU0        MSC-140G             20-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/6/CPU0        MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/7/CPU0        MSC-140G             20-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/8/CPU0        MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/9/CPU0        MSC-140G             20-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/10/CPU0       MSC-140G             20-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/11/CPU0       MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/12/CPU0       MSC-140G             20-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/13/CPU0       MSC-140G             14-10GbE         IOS XR RUN      PWR,NSHUT,MON
0/14/SP         DRP(SP)              N/A              IOS XR RUN      PWR,NSHUT,MON
0/14/CPU0       DRP(Active)          DRP-ACC          IOS XR RUN      PWR,NSHUT,MON
0/14/CPU1       DRP(Active)          DRP-ACC          IOS XR RUN      PWR,NSHUT,MON
0/15/SP         DRP(SP)              N/A              IOS XR RUN      PWR,NSHUT,MON
0/15/CPU0       DRP(Standby)         DRP-ACC          IOS XR RUN      PWR,NSHUT,MON
0/15/CPU1       DRP(Standby)         DRP-ACC          IOS XR RUN      PWR,NSHUT,MON
0/RP0/CPU0      RP(Active)           N/A              IOS XR RUN      PWR,NSHUT,MON
0/RP1/CPU0      RP(Standby)          N/A              IOS XR RUN      PWR,NSHUT,MON
0/FC0/SP        LCC-FAN-CT(SP)       N/A              IOS XR RUN      PWR,NSHUT,MON
0/FC1/SP        LCC-FAN-CT(SP)       N/A              IOS XR RUN      PWR,NSHUT,MON
0/AM0/SP        ALARM(SP)            N/A              IOS XR RUN      PWR,NSHUT,MON
0/AM1/SP        ALARM(SP)            N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM0/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC-140G/S(SP)        N/A              IOS XR RUN      PWR,NSHUT,MON
 
   

Execute the show redundancy command to verify that a Standby RP is available and in "ready" state.

RP/0/RP0/CPU0:router#show red
Redundancy information for node 0/RP0/CPU0:
	==========================================
Node 0/RP0/CPU0 is in ACTIVE role
Partner node (0/RP1/CPU0) is in STANDBY role
Standby node in 0/RP1/CPU0 is ready
Standby node in 0/RP1/CPU0 is NSR-ready
 
   

Execute the show ipv4 interface brief command or the show ipv6 interface brief command or the show interface summary command to verify that all necessary interfaces are "UP".

RP/0/RP0/CPU0:router#show interfaces summary 
Tue Oct 12 23:41:48.562 PST
Interface Type              Total    UP       Down     Admin Down
--------------              -----    --       ----     ----------
ALL TYPES                    750     712        0             38      
--------------         
IFT_LOOPBACK              1         1        0              0       
IFT_ETHERNET              6         2        0              4       
IFT_NULL                  1         1        0              0       
IFT_TENGETHERNET        232       198        0              34      
IFT_VLAN_SUBIF          510       510        0              0      
 
   
 

show install active summary (verify that the proper set of packages are active)

Single-chassis example:

RP/0/RP0/CPU0:router(admin)#show install active summary 
Wed Oct 13 06:47:17.604 UTC
Default Profile:
  Admin Resources
  SDRs:
    Owner
  Active Packages:
    disk0:hfr-cgn-px-4.0.0.65I
    disk0:hfr-mpls-px-4.0.0.65I
    disk0:hfr-mcast-px-4.0.0.65I
    disk0:hfr-mini-px-4.0.0.65I
 
   

Multishelf example:

RP/0/RP0/CPU0:MC-SCALE(admin)#show install active summary 
Default Profile:
  Admin Resources
  SDRs:
    Owner
    taiko-sdr
  Active Packages:
    disk0:hfr-fit-px-4.0.2.19I
    disk0:hfr-doc-px-4.0.2.19I
    disk0:hfr-mpls-px-4.0.2.19I
    disk0:hfr-mgbl-px-4.0.2.19I
    disk0:hfr-mcast-px-4.0.2.19I
    disk0:hfr-mini-px-4.0.2.19I
    disk0:hfr-fpd-px-4.0.2.19I
    disk0:hfr-diags-px-4.0.2.19I
    
 
   
 
   
 
   

Execute the cfs check/clear configuration inconsistency command to verify/fix configuration file system in exec and admin mode.

Additional Pre-upgrade System Checks

Due to increasing size of the images sufficient disk space is required to perform the upgrade. the 2Gig flash disk option was first introduced in release 3.7.0, An optional 4Gig flash disk is available starting with the IOS XR 3.8.4 release.

When upgrading to release 4.0.0 or higher, a PCMCIA flash disk of 2Gig or larger has to be installed in the system BEFORE the software upgrade is performed.


Step 1 Use the show filesystem command to check the actual disk0 size:

RP/0/RP0/CPU0:router(admin)#show filesystem 
Wed Oct 13 06:54:57.000 UTC
File Systems:
 
   
3694129152  1131577344  flash-disk     rw  disk0: 
2102788096  2102657024  flash-disk     rw  disk1a:
2102722560   180682752  flash-disk     rw  disk1:
 504471552   504152064  flash-disk     rw  disk0a:
   1043456      940032       nvram     rw  nvram:
  62390272    25756520       flash     rw  bootflash:
 
   

In order to provide as much room as possible on the disk, one can remove old files from the disk. This may include files which the operator has placed on the disk device such as PIE files or temporary directories that have been created.

When preparing for the upgrade to the next version of the operating system, any old, non-operational versions should be removed.

Step 2 Remove old SMUs and old versions of the operating system files by executing the following admin commands:

RP/0/RP0/CPU0:router(admin)# show install inactive 
 
   
 
   
Node 0/0/CPU0 [LC] [SDR: Owner]
    Boot Device: mem:
    Inactive Packages: 
      disk0:hfr-fit-px-4.0.0.63I
      disk0:hfr-infra-test-px-4.0.0.65I
      disk0:hfr-upgrade-px-4.0.0.65I
      disk0:hfr-fit-px-4.0.0.65I
      disk0:hfr-cgn-px-4.0.0.63I
      disk0:hfr-mpls-px-4.0.0.63I
      disk0:hfr-mcast-px-4.0.0.63I
      disk0:hfr-fpd-px-4.0.0.65I
      disk0:hfr-fpd-px-4.0.0.63I
      disk0:hfr-diags-px-4.0.0.63I
      disk0:hfr-diags-px-4.0.0.65I
      

Execute the install remove inactive test sync command first to show which packages will be removed from the disk.

RP/0/RP0/CPU0:router(admin)#install remove inactive test sync
Info:     This operation will remove the following packages:
Info:         disk0:hfr-diags-px-4.0.0.65I
Info:         disk0:hfr-diags-supp-4.0.0.65I
Info:         disk0:hfr-doc-px-4.0.0.65I
Info:         disk0:hfr-doc-supp-4.0.0.65I
Info:         disk0:hfr-fit-px-4.0.0.65I
Info:         disk0:hfr-fit-4.0.0.65I
 
   

The install operation will continue asynchronously.

RP/0/RP0/CPU0:router(admin)#Install operation 192 completed successfully 
 
   

Step 3 Ensure all active packages are 'committed', then issue the install commit command

	RP/0/RP0/CPU0:router(admin)#install commit 
Wed Oct 13 07:10:37.141 UTC
Install operation 193 '(admin) install commit' started by user 'lab' via CLI at 
07:10:38 UTC Wed Oct 13 2010.
Install operation 193 completed successfully at 07:10:46 UTC Wed Oct 13 2010.
 
   

If any node is not booting properly it has to be replaced or shut down using the hw-module power disable location 0/1/cpu0 command executed while in admin mode

RP/0/RP0/CPU0:router(admin-config)#hw-module power disable location 0/1/cpu0 
 
   

Step 4 Copy the running-configuration and admin-configuration to a temporary storage location. This could be on a remote TFTP server or a device such as the harddisk: or disk0: present on the RP.

router#copy running-config tftp://...running_config.txt
router#admin
router(admin)#copy running-config tftp://...admin-running_config.txt
router(admin)#exit
 
   

Step 5 Verify Mgmt access to the router

 
   
 
   

Note Cisco recommends copying all the Mandatory PIE files, Optional PIE files, and Recommended SMUs to the hard disk as part of pre-maintenance activity. This will save significant time during the upgrade process.



Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware

Before migrating your CRS-1 hardware to CRS-3 hardware you must complete the software upgrade to Cisco IOS XR software Release 4.0.X(PX).


Note All install operations should be done while logged into admin mode.



Step 1 Add the required PIEs to disk:

router(admin)# install add tar <source>/<path>/<pie> sync
 
   

The <source> keyword can be one of disk0:, disk1:, compactflash:, harddisk:, tftp:, ftp: or rcp:.
The above step must be repeated for each PIE file, or all of the PIEs can be added together in a single install add command. To add all PIEs using a single command, list all of the PIEs (including their source) within the install add command in the following manner:

router(admin)# install add <source>/hfr-mini-px.pie-<version> 
<source>/hfr-mcast-px.pie-<version> <source>/hfr-mgbl-px.pie-<version> 
<source>/hfr-mpls-px.pie-<version> <source>/hfr-k9sec-px.pie-<version> 
<source>/hfr-diags-px.pie-<version> hfr-upgrade-px.pie  sync
 
   

Note The use of the sync option prevents other users from executing any other command during the install operation.


The <source> keyword can be specified just once rather than for each package. This simplifies the command:

router(admin)# install add <source> hfr-mini-px.pie-<version> 
hfr-mcast-px.pie-<version> hfr-mgbl-px.pie-<version> hfr-mpls-px.pie-<version> 
hfr-k9sec-px.pie-<version> hfr-diags-px.pie-<version> hfr-upgrade-px.pie <version> 
sync
 
   

Note Under idle conditions, the "install add" operation may take up to 65 to 100 minutes. During the "install add" operation your Cisco CRS Series router will remain fully functional.



Note If you have any other optional packages installed, the current upgrade has to be done with the optional packages already installed. Otherwise all optional packages have to be deactivated (following by the commit) before the upgrade. Side effect of this is loss of the configuration supported by the PIE.


From Cisco IOS XR software release 3.6.0 onward, an alternate way of adding and installing PIEs is available. If the PIE files are compressed using tar format they can be loaded on the router using the following command:

router(admin)# install add tar <source>/<path>/<tar_file> sync
 
   

Step 2 Test the activation using the test option. Testing the activation will give you a preview of the activation.

router(admin)# install activate disk0:hfr-mini-px.pie<version> 
disk0:hfr-mcast-px.pie<version> disk0:hfr-mgbl-px.pie<version> 
disk0:hfr-k9sec-px.pie<version> disk0:hfr-mpls-px.pie<version> 
disk0:hfr-diags-px.pie<version> hfr-upgrade-px.pie sync test

Note No actual changes will be made when you use the test option with the sync command.
Any config that is incompatible with the new version being activated will be identified. The show configuration removed command can be used to view what will be removed as result of the software upgrade (see the Caveats section for details).


Each removed configuration can be reapplied using the load config removed <config>.cfg command from config mode AFTER the upgrade has been completed (see the Caveats section for details).

From Cisco IOS XR software release 3.6 onwards, the install command will accept the use of wildcard pattern matching. The install activate command can be simplified to install activate *3.9* sync test.

FromCisco IOS XR software release 3.7.0 onwards, PIEs can subsequently be activated using the following single command. The <install_operation_id> variable is based on the install operation ID generated after each install command:

router(admin)# install activate id <install_operation_id> sync test
 
   

The install operation ID is printed after finishing each install command or can be obtained by running the show install log command.

Step 3 Activate all of the packages added in step 1:

router(admin)# install activate disk0:hfr-mini-px.pie<version> 
disk0:hfr-mcast-px.pie<version> disk0:hfr-mgbl-px.pie<version> 
disk0:hfr-k9sec-px.pie<version> disk0:hfr-mpls-px.pie<version> 
disk0:hfr-diags-px.pie<version>  hfr-upgrade-px.piesync
 
   

The output of the install add command executed in step 1 provides the list of names of packages to be used in the install activate operation.

Using the sync option prevents other users from executing any other commands during the install operation.

The router will reload at the end of activation to start using the new packages.


Note Under idle conditions, this operation may take at least 20 minutes to complete.


From Cisco IOS XR software release 3.8 onwards, the install command install activate *3.9.* pause sw-change sync can be used to enable the user to cost the router out of the IGP path just before the router reloads, rather than at the point where the activation commences.

Step 4 Verify system stability through executing the commands described under the Check System Stability section. This release does not support downgrades from PX to P images.

Step 5 Verify activation is successful. Once activation is done and before the install commit operation, deactivate and remove the upgrade-px.PIE.

Step 6 After removing the upgrade-px.PIE execute the install commit command to commit the newly activated software

router(admin)# install commit
 
   

Step 7 Check to see if there were any failed startup configurations. If there were any startup configurations that failed (were not applied), then refer to the Caveats section to see how it should be handled.

router# show config failed startup
 
   

In same very rare cases inconsistencies in the content of the internal configuration files can occur. In order to avoid such situations, the following steps are recommended before activating packages:

Step 8 Clear the NVGEN cache:

router# run nvgen -F 1
 
   

Step 9 Create a dummy config commit:

router# config
router(config)#hostname <hostname>
router(config)#commit
router(config)#end
 
   

Step 10 Force commit update by using the reload command. Press n when the confirmation prompt appears:

router# reload
Updating Commit Database.  Please wait...[OK]
Proceed with reload? [confirm] <- Press "n"
 
   

In same cases the following error may be reported:

router#reload
Preparing system for backup. This may take a few minutes ............System 
configuration backup in progress [Retry later]
 
   

In such a case please re-try the command after some time.


Post-Upgrade Procedure


Step 1 Restore the IGP metric if it had been changed before the upgrade

OSPF

router(config-ospf)#no max-metric router-lsa
 
   

ISIS

router(config-isis)#no set-overload-bit
 
   

Disk Cleanup (Optional)

Once the software upgrade or downgrade has been completed, you can recover some disk space by removing any inactive packages that are no longer needed (if the packages are required at a later time, they can be re-added):


Step 1 Obtain the list of inactive packages and note the names of packages that are not needed:

router(admin)# show install inactive brief
 
   

Step 2 Remove the unnecessary inactive packages:

router(admin)# install remove disk0:<package_name1> disk0:<package_name2> .. 
disk0:<pkg_nameN> sync
 
   

or

router(admin)# install remove inactive	(to remove all inactive packages)
 
   

Using the sync option prevents other users from executing any other command during the install operation.

Step 3 Verify/fix the configuration file system (mandatory)

router(admin)#cfs check
 
   

Step 4 If the max-metric or set overload bit was set during any of the pre-upgrade tasks restore the metric using the following commands:

OSPF

router(config-ospf)#no max-metric router-lsa
 
   

ISIS

router(config-isis)#no set-overload-bit
 
   

Upgrade Firmware (Mandatory)

Both the ROMMON and the FPGA firmware need to be upgraded after the <version> image installation on the system. For detailed upgrade procedure please refer to the IOS XR Firmware Upgrade Guide document which can be accessed at:

http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html

Also refer to the "Other Firmware Support" section in the Release Notes for Cisco CRS-1 and Cisco CRS-3 for Cisco IOS XR Software Release 4.0.2 document which can be accessed at:

http://www.cisco.com/en/US/docs/routers/crs/software/crs_r4.0/general/release/notes/reln_402crs.html

Caveats:

During software upgrade or downgrade, the system could detect incompatible configuration and remove it from the running configuration. The removed configuration will be saved to a file on the router. A configuration could also fail due to syntax or semantic error as the router boots the new version of the software.

To resolve these issues, you must browse the removed or failed configuration and then address the changes so that the configuration can be properly applied on the new version of software.

Addressing Incompatible and Removed Configurations

During the test activation of a new software version, incompatible configurations will be identified and removed from the router running configuration. Syslog and console logs will provide the necessary information on the name of the removed configuration file. To address the incompatible configuration, you should browse the removed configuration file, address the syntax and semantics errors and re-apply the config as required and/or applicable after upgrade.

To display the removed configuration, execute the following command from exec mode:

router# show configuration removed <removed config filename> 
 
   

Addressing Failed Admin and Non-Admin Configurations During Reload

Some configuration may fail to take effect when the router boots with the new software. These configurations will be saved as failed configurations. During activation of the new software version, you will be notified via syslog and console log if a configuration failed to take effect. To address the failed configuration, you should browse both the admin and non-admin failed configurations, address any syntax and semantics errors found, and then re-apply it as required.

To display the failed configuration, execute the following commands:

router# show configuration failed startup
router(admin)# show configuration failed startup
 
   

MDR - Minimum Disruption Restart

The MDR (Minimum Disruption Restart) feature is not supported for upgrades to the Cisco IOS XR software 4.0.0.T, Cisco IOS XR software 4.0.1, or Cisco IOS XR software 4.0.2 releases.

Limitations With the Preconfig Interface

It is important that you check to see whether the persistent config and the running config are the same or different. If they are different then it will have a problem after reload/upgrade, because reload/upgrade will use the persistent config to restore configuration and the restored configuration will be different from the one you were running.

Execute the following commands to verify that the persistent config and the running config are the same:

show cfgmgr persistent-config - shows the persistent config in CLI form

show running-config - shows running config

You should not use the no interface preconfig <> command if you find that the same config exists in both preconfig and activate. Use the cfs check command to resolve the inconsistency.


Upgrade Instructions for FAT32


Step 1 Once the system is up and running with FAT32, please check the disk usage on the router and make sure at least 1.3 GB is free on the Cisco CRS router (We don't need 1.3 GB for the upgrade, but 4.0.0.T shouldn't be taking more than 600 MB)

a. Please make sure all inactive old Cisco IOS XR software release packages (older than Cisco IOS XR software release 4.0.0.T) are removed from the disk.

b. Please make sure all dumper core files and any user files like PIEs etc. are removed from the boot device to save space.

Step 2 Make sure system (RP) has available memory. Please refer to the table above with title RP/SP/LC Memory Requirements during Upgrade.

Step 3 Make sure other management nodes RP/DRP/SC also have available memory. This is applicable to a multishelf platform. The available memory on other RPs should be around the same as the Standby RP of the DSC.

Step 4 Copy the TAR ball of all Cisco IOS XR software release 4.0 PX packages (mini-px.pie + upgrade package + optional PX Package and any SMUs) to the hard disk.


Warning DO NOT COPY THIS TAR BALL PACKAGE TO THE BOOT DEVICE WHICH IS TYPICALLY DISK 0:.

Note The Upgrade Package is absolutely necessary in order to upgrade from a pre 4.0 PX Cisco IOS XR software release to the 4.0 PX Cisco IOS XR software release



Note Make sure all mini and optional packages/SMUs are PX. Do not mix and match packages/SMUs.



Warning Make sure the TAR package contains all the necessary optional packages (mgbl, mpls, mcast, k9sec, doc, diag, fpd). If any of the packages are missed during the upgrade, upgrade activation doesn't complain about the missing package and incompatibilities.

If install add is being done as TAR ball, then the memory requirements on the Route Processor (RP) would be high as contents would be untarred in the /tmp folder. To avoid the usage of RP memory, you can resort to install add of independent packages using the below command. But this typically leads to longer install add times than with the TAR ball install add.

install add source harddisk: pie1 pie2 pie3.....

Step 5 Once the router comes back up with new software, please perform your stability checks and then do the below operations to unblock further install operations.

a. Install the Deactivate Upgrade Package

b. Install the Remove Upgrade Package: This operation removes the dummy packages of Cisco IOS XR software release 4.0; no Cisco IOS XR software release 4.0 software is being removed. This is only a bridging package to facilitate upgrade from Cisco IOS XR software release pre-4.0 software to Cisco IOS XR software release 4.0 software as the package names have changed. The upgrade package contains Cisco IOS XR software release 4.0 dummy packages compatible with Cisco IOS XR software release pre-4.0 packages which are not typically used once you have upgraded to Cisco IOS XR software release 4.0 software. Once your upgrade to Cisco IOS XR software release 4.0 has completed successfully, the Cisco IOS XR software release 4.0 dummy packages (which were installed solely for compatibility with the existing Cisco IOS XR software release pre-4.0 packages) can be removed safely.

Step 6 Now perform an install commit command and continue testing the Cisco IOS XR software release 4.0.0.T.PX Image.


Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix

To convert the existing 40G based Cisco CRS-1 system to 140G based Cisco CRS-3 system, the MSC, PLIM & Fabric cards would need to be replaced.

Refer to Table 1-5 for the new 140G-based Cisco CRS-3 hardware.

Table 1-5 140G-based Cisco CRS-3 Hardware 

Existing
Chassis
CRS-3 MSC
CRS-3 PLIM
Note

SC : 16 slot

MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

Current CRS-1

8 slot chassis

MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

Current CRS-1

4 slot chassis

MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

MSC-140 must NOT be plugged in with CRS-1 Fabric

MC : 16 slot LCC

MSC-140G

FP-140G

14x10GE

20x10GE

1x100GE

Current CRS-1

MC : 16 slot FCC

N/A

N/A

CRS-FCC-FC140/M (S2)

[8 planes | 1 plane/board]

[8 planes | 1 plane/ 3 boards for Multimodule config]


Refer to Table 1-6 for a compatibility matrix of CRS-1 (legacy, 40G) and CRS-3 (140G) hardware:

Table 1-6 CRS-1 and CRS-3 Hardware Compatibility Matrix 

Fabric Type
MSC/FP/RP/DRP Type
Supported
Note

CRS-1 Fabric

MSC-40 (both A and B)

Yes

Current CRS-1

CRS-1 Fabric

RP-A/RP-B/DR-B

Yes

Current CRS-1

CRS-1 Fabric

MSC-140

No

MSC-140 must NOT be plugged in with CRS-1 Fabric

CRS-1 Fabric

FP-40

Yes

Current CRS-1

CRS-1 Fabric

FP-140

No

FP-140 must NOT be plugged in with CRS-1 Fabric

CRS-3 Fabric

MSC-40 (both A and B)

Yes

40G throughput

CRS-3 Fabric

RP-A/RP-B/DRP-B

Yes

With upgraded FPD/XR.

CRS-3 Fabric

MSC-140

Yes

140G throughput

CRS-3 Fabric

FP-40

Yes

40G throughput

CRS-3 Fabric

FP-140

Yes

140G throughput


Information About Migrating to a Cisco CRS-3 Carrier Routing System

The difference between migrating a single-chassis Cisco CRS-1 Carrier Routing System to a single-chassis Cisco CRS-3 Carrier Routing System and installing a new single-chassis Cisco CRS-3 Carrier Routing System is the fabric upgrade. A single-chassis Cisco CRS-1 Carrier Routing System uses fabric cards designed for 40 GB operation (FC/S cards), and an LCC in a Cisco CRS-3 Carrier Routing System uses fabric cards designed for 140 GB operation (FC-140G/S cards). On a single chassis system, each fabric card represents one fabric plane. To migrate a single-chassis Cisco CRS-1 Carrier Routing System to a single-chassis Cisco CRS-3 Carrier Routing System without interrupting service, you must do the following:

1. Use CLI commands to prepare the FC/S fabric card for replacement with an FC-140G/S card.

2. Shut down the plane on the FC/S card before it is replaced.

3. Replace the FC/S card with an FC-140G/S card.

4. Bring up the FC-140G/S card.

5. Repeat Step 2 through Step 4 until all planes (0 through 7) are upgraded.

Verify That the Correct Version of IOS-XR Software is Installed

The Cisco CRS-3 is only supported on Cisco IOS-XR release 4.0.0.T and higher software. As detailed in the section CRS-1 to CRS-3 Software Migration Compatibility Matrix, a direct IOS-XR upgrade to Release 4.0.X(PX) is available for a router running Cisco IOS XR releases 3.8.0 through 3.9.0. All IOS-XR Software releases prior to 3.8.0 (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be upgraded to IOS XR software release 3.8.0 or higher prior to being upgraded to IOS XR software Release 4.0.X(PX) or be upgraded directly to IOS XR software Release 4.0.X(PX) using Turbo Boot as described in "Turbo Boot Procedure,".

Execute the show version command to verify that the CRS-1 to be migrated is running Cisco IOS-XR Release 4.0.X(PX):

RP/0/RP0/CPU0:router#show version
Mon Mar  1 06:18:22.261 UTC
 
   
Cisco IOS XR Software, Version 4.0.0.T[Default]
Copyright (c) 2010 by Cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 1.304(20091103:191235) [CRS-1 ROMMON],  
 
   

Next, execute the show platform command to verify that all Fabric cards are operational (i.e. State is IOS-XR RUN)

RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>
 
   
 
   

Next, execute the show controllers fabric plane all command to verify that all Fabric Planes are UP:

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane all
<snip>
 Plane  Admin   Oper       up->dn    up->mcast
 Id     State   State      counter   counter  
 ---------------------------------------------
 0      UP      UP           0               0              
 1      UP      UP           0               0              
 2      UP      UP           0               0              
 3      UP      UP           0               0              
 4      UP      UP           0               0              
 5      UP      UP           0               0              
 6      UP      UP           0               0              
 7      UP      UP           0               0    
 
   

Note The up->down counter records the number of times the plane has flapped between UP and DOWN. Similarly, up->mcast_Down counter records the number of plane transitions between MCAST_DOWN and UP]


 
   

Benchmark the Traffic

Before starting the migration process, take a snapshot of the traffic flowing through the router and use it as a benchmark to compare against traffic flow during the migration and/or after completing the migration. Since it is a hitless migration, there should be zero impact to the traffic flow during the migration and/or after completing the migration.

To avoid traffic loss, you must upgrade the switch fabric one plane at a time. To do that, you must replace each FC/S card with a new FC-140G/S card and restore service to that fabric plane before upgrading the next fabric plane.

You will probably want to perform the migration during a network maintenance window or when system traffic is light.


Note Be sure to review the migration procedures before deciding when to schedule the migration. That way, you can familiarize yourself with the migration procedure and determine if there are other issues to consider before performing the migration.


Cisco recommends not moving a chassis after it is cabled. Before the fabric cables are installed, the chassis should be fully installed with power supplies, console cables, grounded, and so forth

How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot)

To migrate from a 16-slot Cisco CRS-1 Carrier Routing System to a 16-slot Cisco CRS-3 Carrier Routing System, you must complete the following tasks:

Administratively Disabling the Fabric Plane, page 1-5

Disabling Power to the CRS-1 Fabric Card, page 1-7.

Physically Removing the CRS-1 Fabric Card, page 1-9

Installing an SFC, page 1-11.

Verifying the Installation of an SFC, page 1-15

The migration procedure may be done on one Fabric Card at-a-time.

In a CRS-1 system with redundant fabric (i.e. 8 planes), upgrade to CRS-3 fabric is hitless - zero drop in traffic as we upgrade plane by plane from a CRS-1 to CRS-3.

The detailed migration procedure is detailed in the sections below, for the 16-slot Cisco CRS-1 Carrier Routing System.

Administratively Disabling the Fabric Plane

This section describes how to migrate the fabric cards in a single-chassis system and establish communications between the designated shelf controller (DSC) LCC and one or more FCCs.

SUMMARY STEPS

1. admin

2. configure

3. controller fabric plane 0 shut

4. commit

5. end

6. Repeat Step 3 through Step 5 for each fabric plane.

7. show controllers fabric plane all detail

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:
RP/0/RP0/CPU0:router#admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

controller fabric plane 0 shut

Example:

RP/0/RP1/CPU0:router(admin-config)# controller fabric plane 0 shut

Shuts down the fabric plane in the system.

In a 16-slot CRS-1 router, we have eight fabric nodes, or CRS-1 Fabric Controller cards, numbered 0/SM0/SP to 0/SM7/SP. Each CRS-1 Fabric Controller card has one plane. So for a 16-slot CRS-1 to CRS-3 migration we will be upgrading one plane at a time for all eight planes.

For more information, see Cisco IOS XR Getting Started Guide.

Step 4 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

This step brings up the previously shutdown plane, which is now configured to use the FCC-CRS-3 fabric card.

Step 5 

end

Example:

RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 6 

Repeat Step 3 through Step 5 for each fabric plane.

 

Step 7 

show controllers fabric plane all detail

Example:

RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all detail

Displays the administrative and operational status of all eight fabric planes.

Verify that all fabric planes are administrative state down.

Note There are a total of 42 bundles. There are 3 bundles per LCC. Bundles for LCCs not in service will be down.

The following example shows commands to Administratively Disable the Fabric Plane on the CRS-1 Fabric Card:

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#controller fabric plane 0 shut
RP/0/RP0/CPU0:router(admin-config)#commit

RP/0/RP1/CPU0:router(admin-config)# end

RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all detail

Example of the show controllers fabric plane all detail Command

Execute the show controllers fabric plane all detail command to display the status of the planes. The following example shows a multishelf Cisco CRS Carrier Routing System node:

RP/3/RP0/CPU0:MC-SCALE(admin)#show controllers fabric plane all detail 
Fri Jan  7 17:02:44.919 PST
  Flags: P - plane admin down,       p - plane oper down
         C - card admin down,        c - card  oper down
         A - asic admin down,        a - asic oper down
         L - link port admin down,   l - linkport oper down
         B - bundle port admin Down, b - bundle port oper down
         I - bundle admin down,      i - bundle oper down
         N - node admin down,        n - node down
         X - ctrl admin down,        x - ctrl down
         o - other end of link down  d - data down
         f - failed component downstream
         m - plane multicast down,   s - link port permanently shutdown
         t - no barrier input        O - Out-Of-Service oper down
         T - topology mismatch down  e - link port control only
         D - plane admin data down 
 
   
 Plane  Admin   Oper       up->dn   up->mcast     Down    Total     Down   
 Id     State   State      counter  counter       Flags   Bundles   Bundles
 -------------------------------------------------------------------------
 0      DOWN    DOWN         0          0                     27        15     
 1      UP      UP           0          0                     27        15     
 2      UP      UP           0          0                     27        15     
 3      UP      UP           0          0                     27        15     
 4      UP      UP           0          0                     27        15     
 5      UP      UP           0          0                     27        15     
 6      UP      UP           0          0                     27        15     
 7      UP      UP           0          0                     27        15     
 
   
 
   
 
   

What to Do Next

Next we disable power to the Fabric node, and verify that node is moved to Unpowered state.

Disabling Power to the CRS-1 Fabric Card

SUMMARY STEPS

1. admin

2. configure

3. hw-module power disable loc 0/SM0/SP

4. commit

5. end

6. show platform

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:
RP/0/RP0/CPU0:router#admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

hw-module power disable loc 0/SM0/SP

Example:

RP/0/RP1/CPU0:router(admin-config)# hw-module power disable loc 0/SM0/SP

Disables the power to the specified fabric plane in your single-chassis system.

Step 4 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

This step brings up the previously shutdown plane, which is now configured to use the FCC-CRS-3 fabric card.

Step 5 

end

Example:

RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 6 

show platform

Example:

RP/0/RP0/CPU0:router(admin)#show platform

Displays the power status of all eight fabric planes.

Verify that the CRS-1 fabric card in node 0/SM0/SP is in the UNPOWERED state.

Example

The following example shows commands to disable power to the CRS-1 Fabric Card:

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit

RP/0/RP1/CPU0:router(admin-config)# end

RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             UNPOWERED       PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>

What to Do Next

Next we physically remove the CRS-1 fabric card.

Physically Removing the CRS-1 Fabric Card

This section describes how to physically remove the CRS-1 fabric card, and verify that node is ready to have a CRS-3 fabric card installed in its place.

This section describes how to remove a switch fabric card (SFC) [in this case, the CRS-1 fabric card] from the Cisco CRS Fabric Card Chassis. For more detailed information on the Cisco CRS fabric cards, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description.


Caution Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281


Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

On the LCC chassis disconnect the Trimese cables on the SM cards associated with the planes that you have shut down. If the cables are going to be disconnected for an extended period of time cap the ends with dust covers.

Figure 1-1 Switch Fabric Card

Prerequisites

Before performing this task, you must first open the front cosmetic doors (if installed).


Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools to perform this task:

ESD-preventive wrist strap

Large Phillips screwdriver

Steps

To remove the CRS-1 fabric card, see Figure 1-2 and follow these steps:

Figure 1-2 Removing the CRS-1 Fabric Card

1

Captive screw

3

Direction of installation or removal

2

Ejector lever

   


Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Identify the card to be removed in the card cage. Use the screwdriver to turn the two captive screws on the front panel of the card counterclockwise to loosen the card from the slot.

Step 3 Grasp the two card ejector levers and simultaneously pivot both ejector levers about 90 degrees away from the front edge of the card carrier to unseat the card from the backplane connector.


Caution To prevent ESD damage, handle the CRS-1 fabric card by its ejector levers, the CRS-1 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

Step 4 Grasp the slide-assistance arm and gently pull the CRS-1 fabric card halfway from the slot.

Step 5 Move one hand under the CRS-1 fabric card to guide it. Avoid touching the CRS-1 fabric card printed circuit board, components, and any connector pins. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Step 6 Slide the card completely from the slot.


Caution The CRS-1 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-1 fabric card.

Step 7 Replace the caps on the HBMT connectors on the back of the card.

Step 8 Place the card directly into an antistatic sack or other ESD-preventive container. If you plan to return the defective card to the factory, repackage it in a Cisco CRS-1 fabric card shipping container.


What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the "Installing the Front and Rear (SFC) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on installing a CRS-3 fabric card, see the "Installing a CRS-3 Fabric Card" section.

Installing a CRS-3 Fabric Card

This section describes how to install a CRS-3 fabric card in the Cisco CRS Fabric Card Chassis. For more detailed information on the CRS-3 fabric card, see Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description.


Warning Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281

Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

Figure 1-3 Switch Fabric Card (QQ123-140G)

Prerequisites

Before performing this task, you must first open the front (SFC) side cosmetic doors (if installed). You must already have an OIM installed in your chassis in the slot corresponding to where you plan to install the CRS-3 fabric card before you install the CRS-3 fabric card (for example, if you are planning on installing the CRS-3 fabric card in slot 0, you must have an OIM installed in slot 0 on the rear of the chassis), and you must remove any impedance carrier or slot cover from the slot in which you are installing the CRS-3 fabric card. See the "Installing an OIM" section, the "Removing a Slot Cover" section, and the "Removing an Impedance Carrier" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.

A CRS-3 fabric card can be installed in any of the slots SFC0 to SFC11 (upper card cage) and SFC12 to SFC23 (lower card cage).


Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools and part to perform this task:

ESD-preventive wrist strap

Large Phillips screwdriver

CRS-3 fabric card

Steps

To install the CRS-3 fabric card, see Figure 1-4 and follow these steps:

Figure 1-4 Installing a CRS-3 Fabric Card

1

Captive screw

3

Direction of installation or removal

2

Ejector lever

   


Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Choose an available CRS-3 fabric card slot for the CRS-3 fabric card.


Caution To prevent ESD damage, handle the CRS-3 fabric card by its ejector levers, the CRS-3 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

Step 3 Remove the CRS-1 fabric card impedance carrier or CRS-1 fabric card you are replacing from the designated slot, and set it carefully aside. (See the "Removing an Impedance Carrier" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide or the "Removing an SFC" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.)


Note Remove only one impedance carrier or CRS-1 fabric card and install one CRS-3 fabric card at a time. Be sure to verify that each CRS-3 fabric card is fully installed and secured before installing another card.


Step 4 Remove the CRS-3 fabric card you are installing from its antistatic packaging.

Step 5 Use the screwdriver to unscrew and remove the sheetmetal cover over the HBMT connectors on the rear of the CRS-3 fabric card, and set it aside.

Step 6 Remove the caps from the HBMT connectors on the back of the card, and set them carefully aside.

Step 7 Visually inspect the connector on the card before you insert it into the chassis. Do not attempt to install a card with a damaged or dirty connector, as this action may damage the backplane connector or OIM.


Note Rails exist on the upper and lower left edges of the card that align with the slots in the card cage. When you install a card in the card cage, make sure that you orient the card correctly and align these rails when sliding the card into the chassis.


Step 8 Grasp the slide assistance arm with one hand and place your other hand under the carrier to support and guide it into the correct slot. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.


Caution A CRS-3 fabric card weighs about 30 lb (14 kg). You should use two hands when handling a CRS-3 fabric card.

Step 9 Slide the card halfway into the slot. Avoid touching the card circuitry and any connectors.

Step 10 Pivot both card ejector levers so the openings on the card ejector cams at the top and bottom of the card pass over the tabs on each side of the card cage slot.


Caution Verify that the openings on the card ejector cams pass over the tabs; otherwise, one or both ejector levers might bind when you attempt to close the ejector levers, thereby damaging or breaking one or both ejector levers.

Step 11 Continue sliding the card into the card cage slot until the openings on the card ejector cams engage the tabs on each side of the card cage slot.


Note The CRS-3 fabric card has guide pins that make initial contact with the backplane connector as you slide the card into its slot. After the guide pins make contact, continue pushing on the card carrier until the card ejector levers begin pivoting forward, toward the handle in the card carrier.


Step 12 To seat the card in the backplane connector, grasp both card ejector levers and pivot them inward toward the handle in the card carrier until they are flush against the front edge of the card carrier.


Note You may hear a crunching noise when seating the card; this noise is normal.


Step 13 Use the screwdriver to turn the two captive screws on the front panel of the CRS-3 fabric card clockwise to seat the card firmly in the slot.


What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the "Installing the Front and Rear (SFC) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on removing the front cosmetic cover plates, see the "Removing the Rear (OIM) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide. For information on how to power down your chassis, see the "Powering an AC Power Shelf Energized Chassis Up and Down" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide or the "Powering a DC Power Shelf Energized Chassis Up and Down" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide. For information on installing an OIM, see the "Installing an OIM" section in the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide.

Verifying the Installation of the CRS-3 Fabric Card

This section describes how to verify that the CRS-3 fabric card has been properly installed. Figure 1-5 is an illustration of the QQ123-140G switch fabric card front panel.

Figure 1-5 Switch Fabric Card Front View (QQ123-140G Shown)

1

Status LED

2

Alphanumeric LEDs


Understanding the Alphanumeric LEDs

At one end of the faceplate, near an ejector lever, the CRS-3 fabric card has two four-digit alphanumeric LED displays that show a sequence of messages indicating the state of the card. In normal operation, the LED module should display IOS-XR.


Note It is normal for some displayed messages to appear too briefly in the LED display to be read.


Troubleshooting the CRS-3 Fabric Card

If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:

Make sure that the card is seated firmly in the Cisco CRS Fabric Card Chassis slot. One easy way to verify physical installation is to see whether the front faceplate of the CRS-3 fabric card is even with the fronts of the other cards installed in the card cage.

Check whether the ejector levers are latched and that the captive screws are fastened properly. If you are uncertain, unlatch the levers, loosen the screws, and attempt to reseat the CRS-3 fabric card.

Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System 16-Slot System Description.)

Examine the Cisco CRS Fabric Card Chassis power shelves to see whether the chassis, as a whole, is receiving power.

Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:

When the CRS-3 fabric card is properly installed, the Status LED turns green. If this LED is off, verify that the CRS-3 fabric card is installed correctly.

If there is a failure during the board boot sequence, the two four-digit alphanumeric LED displays indicate the current boot phase to assist you in debugging the board failure.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version

Hardware Requirements

The Fabric card to be added must be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit
 
   
RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             UNPOWERED       PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>
 
   

Powering up the Replaced Fabric Card

This section describes how to enable power back to the Fabric node, and verify that node is moved to Powered state.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version

Hardware Requirements

The LCC to be added must be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be operational and connected to all chassis.

The power should be off for the FCC to be added.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. no hw-module power disable loc 0/SM0/SP

4. commit

5. Apply power to the new LCC (Rack 1).

6. Connect all fabric cables that connect the fabric planes in the new LCC to the FCCs.

7. Specify that the LED in question is the one on the FCC OIM-LED module.

8. do show controllers fabric rack-status all detail

9. do show controllers fabric fabric-backpressure summary

10. no controllers fabric rack 1 install-mode

11. commit

12. do show controllers rack-status all detail

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/RP1/CPU0:router# admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

no hw-module power disable loc 0/SM0/SP

Example:

RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable loc 0/SM0/SP

Enables the power to the specified fabric plane in your single-chassis system.

Step 4 

controllers fabric rack 1 install-mode

Example:

RP/0/RP1/CPU0:router(admin-config)# controllers fabric rack 1 install-mode

Modifies the target configuration to change the Rack 1 configuration to installation mode.

Step 5 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 6 

Apply power to the new LCC (Rack 1).

Starts up the second LCC (Rack 1).

Step 7 

Connect all fabric cables that connect the fabric planes in the new LCC to the FCCs.

Interconnects the fabric cards in the LCC and FCC.

Step 8 

In the FCCs, check the LEDs for the cables that connect to the new LCC (Rack 1).

Green LEDs indicate that the cables are connected correctly.

If the LEDs display a color other than green, see Cisco IOS XR Getting Started Guide for information on interpreting the LED display.

Step 9 

do show controllers fabric rack-status all detail

Example:

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail

Displays the status of all racks and additional information for racks in installation mode.

Wait for the status in the Rack in Install and Rack out of Install columns to change to UP for all planes.

Step 10 

do show controllers fabric fabric-backpressure summary

Example:

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric fabric-backpressure summary

Displays the backpressure status for all racks.

The status for the row labeled "Rack 1: All Groups Received? :" should be "Yes."

Step 11 

no controllers fabric rack 1 install-mode

Example:

RP/0/RP1/CPU0:router(admin-config)# no controllers fabric rack 1 install-mode

Modifies the target configuration to change the Rack 1 configuration to normal mode.

Step 12 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 13 

do show controllers rack-status all detail

Example:

RP/0/RP1/CPU0:router(admin-config)# do show controllers rack-status all detail

Displays the status of all racks in the system.

In a properly operating system, the rack status for all racks should be Normal, and the server status should be Present.

What to Do Next

When all chassis in the multishelf system are operational and communicating with each other, it is time to continue system configuration, as described in the documents in the "Related Documents" section on page 1-63.

Troubleshooting Tips

For troubleshooting information, see the documents described in the "Related Documents" section on page 1-63.

Example

The following example shows commands to enable power to the newly installed CRS-3 Fabric Card:

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#no hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit

Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC-140G/S(SP)        N/A             PRESENT         PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON

How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot)

To migrate from an 8-slot Cisco CRS-1 Carrier Routing System to an 8-slot Cisco CRS-3 Carrier Routing System, you must complete the following tasks:

Administratively Disabling the Fabric Plane, page 1-5

Disabling Power to the CRS-1 Fabric Card, page 1-7.

Physically Removing the CRS-1 Fabric Card, page 1-9

Installing a CRS-3 Fabric Card, page 1-11.

Verifying the Installation of the CRS-3 Fabric Card, page 1-15

The migration procedure may be done on one Fabric Card at-a-time.

In a CRS-1 system with redundant fabric (i.e. 8 planes), migrating to the CRS-3 fabric is hitless - zero drop in traffic as we migrate plane by plane from a CRS-1 to CRS-3 .

The detailed migration procedure is detailed in the sections below, for the 8-slot Cisco CRS-3 Carrier Routing System.

Administratively Disabling the Fabric Plane

This section describes how to migrate the fabric cards in a single-chassis system and establish communications between the designated shelf controller (DSC) LCC and one or more FCCs.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version (for Route Processor [RP])

ROMMON 1.52 or later version (for Dual Route Processor [DRP])


Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v.

For more information, see Cisco IOS XR ROM Monitor Guide.

Hardware Requirements

The system hardware should be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be set up as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The single-chassis system that is being migrated does not have to be powered down.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. controller fabric plane 0 shut

4. controller fabric plane 1 shut

5. commit

6. end

7. Repeat Step 3 through Step 6 for each fabric plane.

8. show controllers fabric plane all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:
RP/0/RP0/CPU0:router#admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

controller fabric plane 0 shut

Example:

RP/0/RP1/CPU0:router(admin-config)# controller fabric plane 0 shut

Shuts down the first fabric plane in the system.

In an 8-slot CRS-1 router, we have 4 fabric nodes, or Fabric Controller cards numbered 0/SM0/SP to 0/SM3/SP. Each Fabric Controller card has two planes. So for an 8-slot CRS-1 to CRS-3 migration we will be upgrading 2 planes at a time of the pre-existing single-chassis system.

Step 4 

controller fabric plane 1 shut

Example:

RP/0/RP1/CPU0:router(admin-config)# controller fabric plane 1 shut

Shuts down the second fabric plane in the system.

In an 8-slot CRS-1 router, we have 4 fabric nodes, or Fabric Controller cards numbered 0/SM0/SP to 0/SM3/SP. Each Fabric Controller card has two planes. So for an 8-slot CRS-1 to CRS-3 migration we will be upgrading 2 planes at a time of the pre-existing single-chassis system.

Step 5 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

This step brings up the previously shutdown plane, which is now configured to use the FCC-CRS-3 fabric card.

Step 6 

end

Example:

RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 7 

Repeat Step 3 through Step 6 for each fabric plane.

 

Step 8 

show controllers fabric plane all

Example:

RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all

Displays the administrative and operational status of all eight fabric planes.

Verify that all fabric planes are administrative state down.

What to Do Next

Next we disable power to the Fabric node, and verify that node is moved to Unpowered state.

Disabling Power to the CRS-1 Fabric Card

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version (for Route Processor [RP])

ROMMON 1.52 or later version (for Dual Route Processor [DRP])


Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is upgraded to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v.

For more information, see Cisco IOS XR ROM Monitor Guide.

Hardware Requirements

The system hardware should be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be set up as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The single-chassis system that is being migrated does not have to be powered down.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. hw-module power disable loc 0/SM0/SP

4. commit

5. end

6. Repeat Step 3 through Step 5 for each fabric plane.

7. show platform

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:
RP/0/RP0/CPU0:router#admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

hw-module power disable loc 0/SM0/SP

Example:

RP/0/RP1/CPU0:router(admin-config)# hw-module power disable loc 0/SM0/SP

Disables the power to the specified fabric plane in your single-chassis system.

Step 4 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

This step brings up the previously shutdown plane, which is now configured to use the FCC-CRS-3 fabric card.

Step 5 

end

Example:

RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 6 

show platform

Example:

RP/0/RP0/CPU0:router(admin)#show platform

Displays the power status of all eight fabric planes.

Verify that the fabric card in node 0/SM0/SP is in the UNPOWERED state.

Example

The following example shows commands to disable power to the CRS-1 Fabric Card:

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit
RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             UNPOWERED       PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>

What to Do Next

Next we physically remove the CRS-1 fabric card.

Physically Removing the CRS-1 Fabric Card

This section describes how to physically remove the CRS-1 fabric card, and verify that node is ready to have a CRS-3 fabric card installed in its place.

This section describes how to remove a CRS-1 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System 8-Slot Line Card Chassis System Description.


Caution Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281


Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

Figure 1-6 CRS-1 Fabric Card

Prerequisites

Before performing this task, you must first open the front cosmetic doors (if installed).


Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools to perform this task:

ESD-preventive wrist strap

Large Phillips screwdriver

Steps

To remove a CRS-1 fabric card, see Figure 1-2 and follow these steps:

Figure 1-7 Removing a CRS-1 Fabric Card

1

Captive screw

3

Direction of installation or removal

2

Ejector lever

   


Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Identify the card to be removed in the card cage. Use the screwdriver to turn the two captive screws on the front panel of the card counterclockwise to loosen the card from the slot.

Step 3 Grasp the two card ejector levers and simultaneously pivot both ejector levers about 90 degrees away from the front edge of the card carrier to unseat the card from the backplane connector.


Caution To prevent ESD damage, handle a CRS-1 fabric card by its ejector levers, the CRS-1 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

Step 4 Grasp the slide-assistance arm and gently pull the CRS-1 fabric card halfway from the slot.

Step 5 Move one hand under the CRS-1 fabric card to guide it. Avoid touching the CRS-1 fabric card printed circuit board, components, and any connector pins. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Step 6 Slide the card completely from the slot.


Caution A CRS-1 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-1 fabric card.

Step 7 Replace the caps on the HBMT connectors on the back of the card.

Step 8 Place the card directly into an antistatic sack or other ESD-preventive container. If you plan to return the defective card to the factory, repackage it in a Cisco CRS-1 fabric card shipping container.


What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the "Installing the Front and Rear (SFC) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on installing a CRS-3 fabric card, see the "Installing a CRS-3 Fabric Card" section below.

Installing a CRS-3 Fabric Card

This section describes how to install a CRS-3 fabric card in the Cisco CRS Fabric Card Chassis. For more detailed information on the CRS-3 fabric card, see Cisco CRS Carrier Routing System 8-Slot Line Card Chassis System Description.


Warning Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281

Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

Figure 1-8 Switch Fabric Card (QQ123-140G)

Prerequisites

Before performing this task, you must first open the front (SFC) side cosmetic doors (if installed).

A CRS-3 fabric card can be installed in any of the slots SFC0 to SFC11 (upper card cage) and SFC12 to SFC23 (lower card cage).


Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools and part to perform this task:

ESD-preventive wrist strap

Large Phillips screwdriver

CRS-3 fabric card

Steps

To install a CRS-3 fabric card, see Figure 1-4 and follow these steps:

Figure 1-9 Installing a CRS-3 Fabric Card

1

Captive screw

3

Direction of installation or removal

2

Ejector lever

   


Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Choose an available CRS-3 fabric card slot for the CRS-3 fabric card.


Caution To prevent ESD damage, handle a CRS-3 fabric card by its ejector levers, the CRS-3 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

Step 3 Remove the SFC impedance carrier or CRS-1 fabric card you are replacing from the designated slot, and set it carefully aside. (See the "Removing an Impedance Carrier" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide or the "Removing an SFC" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide.)


Note Remove only one impedance carrier or CRS-1 fabric card and install one CRS-3 fabric card at a time. Be sure to verify that each CRS-3 fabric card is fully installed and secured before installing another card.


Step 4 Remove the CRS-3 fabric card you are installing from its antistatic packaging.

Step 5 Use the screwdriver to unscrew and remove the sheetmetal cover over the HBMT connectors on the rear of the CRS-3 fabric card, and set it aside.

Step 6 Remove the caps from the HBMT connectors on the back of the card, and set them carefully aside.

Step 7 Visually inspect the connector on the card before you insert it into the chassis. Do not attempt to install a card with a damaged or dirty connector, as this action may damage the backplane connector or OIM.


Note Rails exist on the upper and lower left edges of the card that align with the slots in the card cage. When you install a card in the card cage, make sure that you orient the card correctly and align these rails when sliding the card into the chassis.


Step 8 Grasp the slide assistance arm with one hand and place your other hand under the carrier to support and guide it into the correct slot. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.


Caution A CRS-3 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-3 fabric card.

Step 9 Slide the card halfway into the slot. Avoid touching the card circuitry and any connectors.

Step 10 Pivot both card ejector levers so the openings on the card ejector cams at the top and bottom of the card pass over the tabs on each side of the card cage slot.


Caution Verify that the openings on the card ejector cams pass over the tabs; otherwise, one or both ejector levers might bind when you attempt to close the ejector levers, thereby damaging or breaking one or both ejector levers.

Step 11 Continue sliding the card into the card cage slot until the openings on the card ejector cams engage the tabs on each side of the card cage slot.


Note A CRS-3 fabric card has guide pins that make initial contact with the backplane connector as you slide the card into its slot. After the guide pins make contact, continue pushing on the card carrier until the card ejector levers begin pivoting forward, toward the handle in the card carrier.


Step 12 To seat the card in the backplane connector, grasp both card ejector levers and pivot them inward toward the handle in the card carrier until they are flush against the front edge of the card carrier.


Note You may hear a crunching noise when seating the card; this noise is normal.


Step 13 Use the screwdriver to turn the two captive screws on the front panel of the CRS-3 fabric card clockwise to seat the card firmly in the slot.


What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the "Installing the Front and Rear (SFC) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on removing the front cosmetic cover plates, see the "Removing the Rear (OIM) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide. For information on how to power down your chassis, see the "Powering an AC Power Shelf Energized Chassis Up and Down" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide or the "Powering a DC Power Shelf Energized Chassis Up and Down" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide. For information on installing an OIM, see the "Installing an OIM" section in the Cisco CRS Carrier Routing System 8-Slot Line Card Chassis Installation Guide.

Verifying the Installation of the CRS-3 Fabric Card

This section describes how to verify that the CRS-3 fabric card has been properly installed. Figure 1-10 is an illustration of the QQ123-140G switch fabric card front panel.

Figure 1-10 Switch Fabric Card Front View (QQ123 Shown)

1

Status LED

2

Alphanumeric LEDs


Understanding the Alphanumeric LEDs

At one end of the faceplate, near an ejector lever, a CRS-3 fabric card has two four-digit alphanumeric LED displays that show a sequence of messages indicating the state of the card. In normal operation, the LED module should display IOS-XR.


Note It is normal for some displayed messages to appear too briefly in the LED display to be read.


Troubleshooting the CRS-3 Fabric Card

If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:

Make sure that the card is seated firmly in the Cisco CRS Fabric Card Chassis slot. One easy way to verify physical installation is to see whether the front faceplate of the CRS-3 fabric card is even with the fronts of the other cards installed in the card cage.

Check whether the ejector levers are latched and that the captive screws are fastened properly. If you are uncertain, unlatch the levers, loosen the screws, and attempt to reseat the CRS-3 fabric card.

Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System 8-Slot Line Card Chassis System Description.)

Examine the Cisco CRS Fabric Card Chassis power shelves to see whether the chassis, as a whole, is receiving power.

Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:

When the CRS-3 fabric card is properly installed, the Status LED turns green. If this LED is off, verify that the CRS-3 fabric card is installed correctly.

If there is a failure during the board boot sequence, the two four-digit alphanumeric LED displays indicate the current boot phase to assist you in debugging the board failure.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version

Hardware Requirements

The Fabric card to be added must be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. hw-module power disable loc 0/SM0/SP

4. commit

5. Verify that power has been removed from the Fabric Node (state is UNPOWERED).

6. show platform

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit
 
   
RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             UNPOWERED       PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>
 
   

Powering up the Replaced Fabric Card

This section describes how to enable power back to the Fabric node, and verify that node is moved to Powered state.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version

Hardware Requirements

The LCC to be added must be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be operational and connected to all chassis.

The power should be off for the FCC to be added.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. no hw-module power disable loc 0/SM0/SP

4. commit

5. Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

6. show platform

Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC-140G/S(SP)        N/A             PRESENT         PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>

Booting Up the Newly Migrated Cisco CRS-3 Fabric

This section describes the process for booting up the new Cisco CRS-3 fabric.

When the Cisco CRS-3 fabric node is powered on, The Route Processor (RP) will automatically boot the new fabric. Please wait for the boot process to complete. The node will transition from state MBI-BOOT to MBI-RUNNING as the software is being installed.

When the boot process completes the node-state will be IOS-XR RUN.

RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC-140G/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
 
   

Administratively Enabling the Fabric Plane

This section describes the process for administratively enabling each new Cisco CRS-3 fabric plane.

Once enabled, the fabric plane status would be "Up".

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 0 shut
RP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 1 shut
RP/0/RP0/CPU0:router(admin-config)#commit

Verify that each of the eight fabric planes is enabled by executing the show controllers fabric plane all command:

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane all
Plane  Admin   Oper       up->dn    up->mcast
 Id     State   State      counter   counter  
 ---------------------------------------------
 0      UP      UP           2               2              
 1      UP      UP           2               2              
 2      UP      UP           0               0              
 3      UP      UP           0               0              
 4      UP      UP           0               0              
 5      UP      UP           0               0              
 6      UP      UP           0               0              
 7      UP      UP           0               0    

Each plane transitions from UP -> MCAST_DOWN -> DOWN -> MCAST_DOWN -> UP. Thus each plane will cycle through up->dn twice. This is why the up->dn counter shows 2. Similarly each plane will cycle through mcast_dn->up twice as well and the mcast_dn->up counter shows 2.

Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node

To ascertain that traffic is flowing on the CRS-3 node please run the following command on both the planes that have been migrated. Run it a few times to ensure that the counters are incrementing. The lost or error counters should not be incrementing.

The same command should also be applied on the legacy nodes (not yet migrated) to make sure there is no traffic lost or traffic with errored cells.

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane 0 statistics detail
 
   
  Total number of providers for the statistics: 1
  Total received data cells: 7063
  Total received unicast data cells: 4487
  Total received low priority unicast data cells: 4487
  Total received high priority unicast data cells: 0
  Total received multicast data cells: 2576
  Total received low priority multicast data cells: 2050
  Total received high priority multicast data cells: 526
  Total transmitted data cells: 21094
  Total transmitted unicast data cells: 4487
  Total transmitted low priority unicast data cells: 4487
  Total transmitted high priority unicast data cells: 0
  Total transmitted multicast data cells: 16607
  Total transmitted low priority multicast data cells: 13977
  Total transmitted high priority multicast data cells: 2630
  Total received correctable errored cells: 0
  Total received uncorrectable errored cells: 0
  Total received parity error cells: 0
  Total received stomp cells: 0
  Total received kill cells: 0
  Total received unknown cells: 0
  Total transmitted bogus cells: 4
  Total transmitted statically routed control cells: 0
  Total transmitted stomp cells: 0
  Total transmitted kill cells: 0
  Total transmitted ECI cells: 0
  Total transmitted LCE cells: 0
  Total unicast lost cells: 0
  Total multicast lost cells: 0
  Total ctb enqueue to off queue  cells: 0
  Total non-ctb enqueue to off queue  cells: 0
  Total incoming header error cells: 0
  Total incoming data error cells: 0
  Total outgoing header error cells: 0
  Total outgoing data error cells: 0
  Total scs ce error cells: 0
  Total scs uce error cells: 0
  Last clearing of "show controller fabric plane" counters 00:06:22

Verifying Fabric Link Connectivity

This section describes the commands used to check the Line Card (LC) to Fabric and Route Processor (RP) to Fabric links for all LCs and RPs in the router (and for DRPs as well). The following commands may be used to check the link connectivity for each LC/RP node.

IngressQ to Fabric connectivity:

show controller ingressq fabric links loc <LC/RP/DRP location>

Fabric to FabricQ connectivity:

show controller fabricq link all loc <LC/RP/DRP location>

All links should be UP. Please repeat the CLI for ALL LC/RP/DRP locations in the router.

RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0
Ingressq link state
plane-id    link-id     ADMIN-STATE OPER-STATE  AVAIL-STATE UP-COUNT    
----------------------------------------------------.
0           0           UP          UP          UP          2           
0           8           UP          UP          UP          2           
0           16          UP          UP          UP          2           
0           24          UP          UP          UP          2           
1           1           UP          UP          UP          2           
1           9           UP          UP          UP          2           
1           17          UP          UP          UP          2           
1           25          UP          UP          UP          2           
2           2           UP          UP          UP          1           
2           10          UP          UP          UP          1           
2           18          UP          UP          UP          1           
2           26          UP          UP          UP          1           
3           3           UP          UP          UP          1           
3           11          UP          UP          UP          1           
3           19          UP          UP          UP          1           
3           27          UP          UP          UP          1           
4           4           UP          UP          UP          1           
4           12          UP          UP          UP          1           
4           20          UP          UP          UP          1           
4           28          UP          UP          UP          1           
5           5           UP          UP          UP          1           
5           13          UP          UP          UP          1           
5           21          UP          UP          UP          1           
5           29          UP          UP          UP          1           
6           6           UP          UP          UP          1           
6           14          UP          UP          UP          1           
6           22          UP          UP          UP          1           
6           30          UP          UP          UP          1           
7           7           UP          UP          UP          1           
7           15          UP          UP          UP          1           
7           23          UP          UP          UP          1           
7           31          UP          UP          UP          1           
RP/0/RP0/CPU0:router(admin)#show controllers fabricq link-info all loc 0/5/cpu0 
 
   
  Location:  0/5/CPU0
  Asic Instance:   0
  Fabric Destination Address:    20
  Retry period:  0 sec
  Link Active bitmap (1=up,0=down):  0xffffffff
  +------------------------------------------------------------------------+
  |Link #|Driver state | FSDB state  |Barrier state|Up (Drv Barr)| Errors  |
  +------------------------------------------------------------------------+
  |    0 |     Up      |     Up      |     Up      |     2  2    |         |
  |    1 |     Up      |     Up      |     Up      |     2  2    |         |
  |    2 |     Up      |     Up      |     Up      |     2  2    |         |
  |    3 |     Up      |     Up      |     Up      |     2  2    |         |
  |    4 |     Up      |     Up      |     Up      |     2  2    |         |
  |    5 |     Up      |     Up      |     Up      |     2  2    |         |
  |    6 |     Up      |     Up      |     Up      |     2  2    |         |
  |    7 |     Up      |     Up      |     Up      |     2  2    |         |
  |    8 |     Up      |     Up      |     Up      |     1  1    |         |
  |    9 |     Up      |     Up      |     Up      |     1  1    |         |
  |   10 |     Up      |     Up      |     Up      |     1  1    |         |
  |   11 |     Up      |     Up      |     Up      |     1  1    |         |
  |   12 |     Up      |     Up      |     Up      |     1  1    |         |
  |   13 |     Up      |     Up      |     Up      |     1  1    |         |
  |   14 |     Up      |     Up      |     Up      |     1  1    |         |
  |   15 |     Up      |     Up      |     Up      |     1  1    |         |
  |   16 |     Up      |     Up      |     Up      |     1  1    |         |
  |   17 |     Up      |     Up      |     Up      |     1  1    |         |
  |   18 |     Up      |     Up      |     Up      |     1  1    |         |
  |   19 |     Up      |     Up      |     Up      |     1  1    |         |
  |   20 |     Up      |     Up      |     Up      |     1  1    |         |
  |   21 |     Up      |     Up      |     Up      |     1  1    |         |
  |   22 |     Up      |     Up      |     Up      |     1  1    |         |
  |   23 |     Up      |     Up      |     Up      |     1  1    |         |
  |   24 |     Up      |     Up      |     Up      |     1  1    |         |
  |   25 |     Up      |     Up      |     Up      |     1  1    |         |
  |   26 |     Up      |     Up      |     Up      |     1  1    |         |
  |   27 |     Up      |     Up      |     Up      |     1  1    |         |
  |   28 |     Up      |     Up      |     Up      |     1  1    |         |
  |   29 |     Up      |     Up      |     Up      |     1  1    |         |
  |   30 |     Up      |     Up      |     Up      |     1  1    |         |
  |   31 |     Up      |     Up      |     Up      |     1  1    |         |
  +------------------------------------------------------------------------+
 
   
Location:  0/5/CPU0
  Asic Instance:   1
  Fabric Destination Address:    21
  Retry period:  0 sec
  Link Active bitmap (1=up,0=down):  0xffffffff
  +------------------------------------------------------------------------+
  |Link #|Driver state | FSDB state  |Barrier state|Up (Drv Barr)| Errors  |
  +------------------------------------------------------------------------+
  |    0 |     Up      |     Up      |     Up      |     2  2    |         |
  |    1 |     Up      |     Up      |     Up      |     2  2    |         |
  |    2 |     Up      |     Up      |     Up      |     2  2    |         |
  |    3 |     Up      |     Up      |     Up      |     2  2    |         |
  |    4 |     Up      |     Up      |     Up      |     2  2    |         |
  |    5 |     Up      |     Up      |     Up      |     2  2    |         |
  |    6 |     Up      |     Up      |     Up      |     2  2    |         |
  |    7 |     Up      |     Up      |     Up      |     2  2    |         |
  |    8 |     Up      |     Up      |     Up      |     1  1    |         |
  |    9 |     Up      |     Up      |     Up      |     1  1    |         |
  |   10 |     Up      |     Up      |     Up      |     1  1    |         |
  |   11 |     Up      |     Up      |     Up      |     1  1    |         |
  |   12 |     Up      |     Up      |     Up      |     1  1    |         |
  |   13 |     Up      |     Up      |     Up      |     1  1    |         |
  |   14 |     Up      |     Up      |     Up      |     1  1    |         |
  |   15 |     Up      |     Up      |     Up      |     1  1    |         |
  |   16 |     Up      |     Up      |     Up      |     1  1    |         |
  |   17 |     Up      |     Up      |     Up      |     1  1    |         |
  |   18 |     Up      |     Up      |     Up      |     1  1    |         |
  |   19 |     Up      |     Up      |     Up      |     1  1    |         |
  |   20 |     Up      |     Up      |     Up      |     1  1    |         |
  |   21 |     Up      |     Up      |     Up      |     1  1    |         |
  |   22 |     Up      |     Up      |     Up      |     1  1    |         |
  |   23 |     Up      |     Up      |     Up      |     1  1    |         |
  |   24 |     Up      |     Up      |     Up      |     1  1    |         |
  |   25 |     Up      |     Up      |     Up      |     1  1    |         |
  |   26 |     Up      |     Up      |     Up      |     1  1    |         |
  |   27 |     Up      |     Up      |     Up      |     1  1    |         |
  |   28 |     Up      |     Up      |     Up      |     1  1    |         |
  |   29 |     Up      |     Up      |     Up      |     1  1    |         |
  |   30 |     Up      |     Up      |     Up      |     1  1    |         |
  |   31 |     Up      |     Up      |     Up      |     1  1    |         |
  +------------------------------------------------------------------------+

How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot)

To migrate from a 4-slot Cisco CRS-1 Carrier Routing System to a 4-slot Cisco CRS-3 Carrier Routing System, you must complete the following tasks:

Administratively Disabling the Fabric Plane, page 1-5

Disabling Power to the CRS-1 Fabric Card, page 1-7.

Physically Removing the CRS-1 Fabric Card, page 1-9

Installing a CRS-3 Fabric Card, page 1-11.

Verifying the Installation of a CRS-3 Fabric Card, page 1-15

The migration procedure may be done on one Fabric Card at-a-time.

In a CRS-1 system with redundant fabric (i.e. 8 planes), migration to CRS-3 fabric is hitless - zero drop in traffic as we migrate plane by plane from a CRS-1 to CRS-3 .

The detailed migration procedure is detailed in the sections below, for the 4-slot Cisco CRS-3 Carrier Routing System.

Administratively Disabling the Fabric Plane

This section describes how to migrate the fabric cards in a single-chassis system and establish communications between the designated shelf controller (DSC) LCC and one or more FCCs.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version (for Route Processor [RP])

ROMMON 1.52 or later version (for Dual Route Processor [DRP])


Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is migrated to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v.

For more information, see Cisco IOS XR ROM Monitor Guide.

Hardware Requirements

The system hardware should be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be set up as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The single-chassis system that is being migrated does not have to be powered down.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. controller fabric plane 0 shut

4. commit

5. end

6. Repeat Step 3 through Step 5 for each fabric plane.

7. show controllers fabric plane all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:
RP/0/RP0/CPU0:router#admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

controller fabric plane 0 shut

Example:

RP/0/RP1/CPU0:router(admin-config)# controller fabric plane 0 shut

Shuts down the fabric plane in the system.

In a 4-slot CRS-1 router, we have four fabric nodes, or Fabric Controller cards, numbered 0/SM0/SP to 0/SM3/SP. Each Fabric Controller card has one plane. So for a 4-slot CRS-1 to CRS-3 migration we will be migrating one plane at a time for all four planes.

Step 4 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

This step brings up the previously shutdown plane, which is now configured to use the CRS-3 fabric card.

Step 5 

end

Example:

RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 6 

Repeat Step 3 through Step 5 for each fabric plane.

 

Step 7 

show controllers fabric plane all

Example:

RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all

Displays the administrative and operational status of all eight fabric planes.

Verify that all fabric planes are administrative state down.

What to Do Next

Next we disable power to the Fabric node, and verify that node is moved to Unpowered state.

Disabling Power to the CRS-1 Fabric Card

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version (for Route Processor [RP])

ROMMON 1.52 or later version (for Dual Route Processor [DRP])


Caution The ROM Monitor software must be upgraded to version 1.54 or a later version on all RPs and/or upgraded to version 1.52 or a later version on all DRPs before a Cisco CRS-1 system is migrated to Cisco IOS XR Software Release 4.0.0.T or later release. If the router is brought up with an incompatible version of the ROM Monitor software, then the standby RP may fail to boot. For instructions to overcome a boot block in the standby RP in a single chassis system, see Cisco IOS XR ROM Monitor Guide. For other issues, contact your Cisco Systems support representative for assistance. See Obtaining Documentation, Obtaining Support, and Security Guidelines, page v.

For more information, see Cisco IOS XR ROM Monitor Guide.

Hardware Requirements

The system hardware should be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be set up as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The single-chassis system that is being migrated does not have to be powered down.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. hw-module power disable loc 0/SM0/SP

4. commit

5. end

6. Repeat Step 3 through Step 5 for each fabric plane.

7. show controllers fabric plane all

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:
RP/0/RP0/CPU0:router#admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

hw-module power disable loc 0/SM0/SP

Example:

RP/0/RP1/CPU0:router(admin-config)# hw-module power disable loc 0/SM0/SP

Disables the power to the specified fabric plane in your single-chassis system.

Step 4 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

This step brings up the previously shutdown plane, which is now configured to use the CRS-3 fabric card.

Step 5 

end

Example:

RP/0/RP1/CPU0:router(admin-config)# end

Changes the mode from administration configuration mode to administration EXEC mode.

Step 6 

show platform

Example:

RP/0/RP0/CPU0:router(admin)#show platform

Displays the power status of all eight fabric planes.

Verify that the fabric card in node 0/SM0/SP is in the UNPOWERED state.

Example

The following example shows commands to disable power to the CRS-1 Fabric Card:

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit
RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             UNPOWERED       PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>
 
   
 
   

What to Do Next

Next we physically remove the CRS-1 fabric card.

Physically Removing the CRS-1 Fabric Card

This section describes how to physically remove the CRS-1 fabric card, and verify that node is ready to have a CRS-3 fabric card installed in its place.

This section describes how to remove a CRS-1 fabric card from the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System 4-Slot Line Card Chassis System Description.


Caution Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281


Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

Figure 1-11 CRS-1 Fabric Card

Prerequisites

Before performing this task, you must first open the front cosmetic doors (if installed).


Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools to perform this task:

ESD-preventive wrist strap

Large Phillips screwdriver

Steps

To remove an CRS-1 fabric card, see Figure 1-12 and follow these steps:

Figure 1-12 Removing a CRS-1 Fabric Card

1

Captive screw

3

Direction of installation or removal

2

Ejector lever

   


Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Identify the card to be removed in the card cage. Use the screwdriver to turn the two captive screws on the front panel of the card counterclockwise to loosen the card from the slot.

Step 3 Grasp the two card ejector levers and simultaneously pivot both ejector levers about 90 degrees away from the front edge of the card carrier to unseat the card from the backplane connector.


Caution To prevent ESD damage, handle the CRS-1 fabric card by its ejector levers, the CRS-1 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

Step 4 Grasp the slide-assistance arm and gently pull the CRS-1 fabric card halfway from the slot.

Step 5 Move one hand under the CRS-1 fabric card to guide it. Avoid touching the CRS-1 fabric card printed circuit board, components, and any connector pins. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Step 6 Slide the card completely from the slot.


Caution A CRS-1 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-1 fabric card.

Step 7 Replace the caps on the HBMT connectors on the back of the card.

Step 8 Place the card directly into an antistatic sack or other ESD-preventive container. If you plan to return the defective card to the factory, repackage it in a Cisco CRS-1 fabric card shipping container.


What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the "Installing the Front and Rear (SFC) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on installing a CRS-3 fabric card, see the "Installing a CRS-3 Fabric Card" section on page 1-60.

Installing a CRS-3 Fabric Card

This section describes how to install a CRS-3 fabric card in the Cisco CRS Fabric Card Chassis. For more detailed information on the switch fabric card, see Cisco CRS Carrier Routing System 4-Slot Line Card Chassis System Description.


Warning Class 1M laser radiation when open. Do not view directly with optical instruments. Statement 281

Warning For diverging beams, viewing the laser output with certain optical instruments within a distance of 100 mm may pose an eye hazard. For collimated beams, viewing the laser output with certain optical instruments designed for use at a distance may pose an eye hazard. Statement 282

Warning Laser radiation. Do not view directly with optical instruments. Class 1M laser product. Statement 283

Figure 1-13 Switch Fabric Card (QQ123-140G)

Prerequisites

Before performing this task, you must first open the front (SFC) side cosmetic doors (if installed). You must already have an OIM installed in your chassis in the slot corresponding to where you plan to install the CRS-3 fabric card before you install the CRS-3 fabric card (for example, if you are planning on installing the CRS-3 fabric card in slot 0, you must have an OIM installed in slot 0 on the rear of the chassis), and you must remove any impedance carrier or slot cover from the slot in which you are installing the CRS-3 fabric card.

A CRS-3 fabric card can be installed in any of the slots SFC0 to SFC11 (upper card cage) and SFC12 to SFC23 (lower card cage).


Caution Use the slide-assistance arm to slide cards from the card carrier. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM! Rotate cards onto their vertical axes, then lift them from the bottom, using the slide-assistance arm only as an aid for balance.

Required Tools and Equipment

You need the following tools and part to perform this task:

ESD-preventive wrist strap

Large Phillips screwdriver

CRS-3 fabric card

Steps

To install a CRS-3 fabric card, see Figure 1-14 and follow these steps:

Figure 1-14 Installing a CRS-3 Fabric Card

1

Captive screw

3

Direction of installation or removal

2

Ejector lever

   


Step 1 Attach the ESD-preventive wrist strap to your wrist and connect its leash to an ESD connection socket on the front of the chassis or to a bare metal surface on the chassis.

Step 2 Choose an available CRS-3 fabric card slot for the CRS-3 fabric card.


Caution To prevent ESD damage, handle the CRS-3 fabric card by its ejector levers, the CRS-3 fabric card carrier edges, or the slide-assistance arm only. Do not touch any of the electrical components, pins, and circuitry.

Step 3 Remove the impedance carrier or CRS-1 fabric card you are replacing from the designated slot, and set it carefully aside. (See the "Removing an Impedance Carrier" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide or the "Removing an SFC" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide.)


Note Remove only one impedance carrier or CRS-1 fabric card and install one CRS-3 fabric card at a time. Be sure to verify that each CRS-3 fabric card is fully installed and secured before installing another card.


Step 4 Remove the CRS-3 fabric card you are installing from its antistatic packaging.

Step 5 Use the screwdriver to unscrew and remove the sheetmetal cover over the HBMT connectors on the rear of the CRS-3 fabric card, and set it aside.

Step 6 Remove the caps from the HBMT connectors on the back of the card, and set them carefully aside.

Step 7 Visually inspect the connector on the card before you insert it into the chassis. Do not attempt to install a card with a damaged or dirty connector, as this action may damage the backplane connector or OIM.


Note Rails exist on the upper and lower left edges of the card that align with the slots in the card cage. When you install a card in the card cage, make sure that you orient the card correctly and align these rails when sliding the card into the chassis.


Step 8 Grasp the slide assistance arm with one hand and place your other hand under the carrier to support and guide it into the correct slot. DO NOT LIFT CARDS BY THE SLIDE-ASSISTANCE ARM; lift them from the bottom, using the slide-assistance arm only as an aid for balance.


Caution A CRS-3 fabric card weighs about 30 lb (14 kg). You should use two hands when handling the CRS-3 fabric card.

Step 9 Slide the card halfway into the slot. Avoid touching the card circuitry and any connectors.

Step 10 Pivot both card ejector levers so the openings on the card ejector cams at the top and bottom of the card pass over the tabs on each side of the card cage slot.


Caution Verify that the openings on the card ejector cams pass over the tabs; otherwise, one or both ejector levers might bind when you attempt to close the ejector levers, thereby damaging or breaking one or both ejector levers.

Step 11 Continue sliding the card into the card cage slot until the openings on the card ejector cams engage the tabs on each side of the card cage slot.


Note The CRS-3 fabric card has guide pins that make initial contact with the backplane connector as you slide the card into its slot. After the guide pins make contact, continue pushing on the card carrier until the card ejector levers begin pivoting forward, toward the handle in the card carrier.


Step 12 To seat the card in the backplane connector, grasp both card ejector levers and pivot them inward toward the handle in the card carrier until they are flush against the front edge of the card carrier.


Note You may hear a crunching noise when seating the card; this noise is normal.


Step 13 Use the screwdriver to turn the two captive screws on the front panel of the CRS-3 fabric card clockwise to seat the card firmly in the slot.


What to Do Next

After performing this task, you may replace any front cosmetic cover plates (see the "Installing the Front and Rear (SFC) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide).

For complete information on regulatory compliance and safety, see Regulatory Compliance and Safety Information for the Cisco CRS Carrier Routing System. For information on removing the front cosmetic cover plates, see the "Removing the Rear (OIM) Side Cosmetic Components" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide. For information on how to power down your chassis, see the "Powering an AC Power Shelf Energized Chassis Up and Down" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide or the "Powering a DC Power Shelf Energized Chassis Up and Down" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide. For information on installing an OIM, see the "Installing an OIM" section in the Cisco CRS Carrier Routing System 4-Slot Line Card Chassis Installation Guide.

Verifying the Installation of the CRS-3 Fabric Card

This section describes how to verify that a CRS-3 fabric card (QQ123-140G) has been properly installed. Figure 1-15 is an illustration of the QQ123-140G switch fabric card front panel.

Figure 1-15 Switch Fabric Card Front View (QQ123-140G Shown)

1

Status LED

2

Alphanumeric LEDs


Understanding the Alphanumeric LEDs

At one end of the faceplate, near an ejector lever, a CRS-3 fabric card has two four-digit alphanumeric LED displays that show a sequence of messages indicating the state of the card. In normal operation, the LED module should display IOS-XR.


Note It is normal for some displayed messages to appear too briefly in the LED display to be read.


Troubleshooting the CRS-3 fabric card

If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:

Make sure that the card is seated firmly in the Cisco CRS Fabric Card Chassis slot. One easy way to verify physical installation is to see whether the front faceplate of the CRS-3 fabric card is even with the fronts of the other cards installed in the card cage.

Check whether the ejector levers are latched and that the captive screws are fastened properly. If you are uncertain, unlatch the levers, loosen the screws, and attempt to reseat the CRS-3 fabric card.

Examine the Cisco CRS Fabric Card Chassis alarm module to see if there are any active alarm conditions. (See the section on the alarm module in Cisco CRS Carrier Routing System 4-Slot Line Card Chassis System Description.)

Examine the Cisco CRS Fabric Card Chassis power shelves to see whether the chassis, as a whole, is receiving power.

Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:

When the CRS-3 fabric card is properly installed, the Status LED turns green. If this LED is off, verify that the CRS-3 fabric card is installed correctly.

If there is a failure during the board boot sequence, the two four-digit alphanumeric LED displays indicate the current boot phase to assist you in debugging the board failure.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version

Hardware Requirements

The Fabric card to be added must be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit
 
   
RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC/S(SP)             N/A             UNPOWERED       PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>
 
   

Powering up the Replaced Fabric Card

This section describes how to enable power back to the Fabric node, and verify that node is moved to Powered state.

Prerequisites

Software Requirements

Cisco IOS XR Software Release 4.0.0.T or later release (Cisco IOS XR Software Release 4.0.2 for multishelf nodes)

ROMMON 1.54 or later version

Hardware Requirements

The LCC to be added must be prepared as described in the "Prerequisites for Upgrading to a Cisco CRS-3 Carrier Routing System" section on page 1-2.

The control network must be operational and connected to all chassis.

The power should be off for the FCC to be added.

Restrictions

None.

SUMMARY STEPS

1. admin

2. configure

3. no hw-module power disable loc 0/SM0/SP

4. commit

5. Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

6. show platform

Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC-140G/S(SP)        N/A             PRESENT         PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
<snip>

Booting Up the Newly Migrated Cisco CRS-3 Fabric

This section describes the process for booting up the new Cisco CRS-3 fabric.

When the Cisco CRS-3 fabric node is powered on, The Route Processor (RP) will automatically boot the new fabric. Please wait for the boot process to complete. The node will transition from state MBI-BOOT to MBI-RUNNING as the software is being installed.

When the boot process completes the node-state will be IOS-XR RUN.

RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC-140G/S(SP)        N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
 
   

Administratively Enabling the Fabric Plane

This section describes the process for administratively enabling each new Cisco CRS-3 fabric plane.

Once enabled, the fabric plane status would be "Up".

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 0 shut
RP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 1 shut
RP/0/RP0/CPU0:router(admin-config)#commit

Verify that each of the eight fabric planes is enabled by executing the show controllers fabric plane all command:

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane all
Plane  Admin   Oper       up->dn    up->mcast
 Id     State   State      counter   counter  
 ---------------------------------------------
 0      UP      UP           2               2              
 1      UP      UP           2               2              
 2      UP      UP           0               0              
 3      UP      UP           0               0              
 4      UP      UP           0               0              
 5      UP      UP           0               0              
 6      UP      UP           0               0              
 7      UP      UP           0               0    

Each plane transitions from UP -> MCAST_DOWN -> DOWN -> MCAST_DOWN -> UP. Thus each plane will cycle through up->dn twice. This is why the up->dn counter shows 2. Similarly each plane will cycle through mcast_dn->up twice as well and the mcast_dn->up counter shows 2.

Verifying Traffic Statistics on the Newly Migrated Cisco CRS-3 Node

To ascertain that traffic is flowing on the CRS-3 node please run the following command on both the planes that have been migrated. Run it a few times to ensure that the counters are incrementing. The lost or error counters should not be incrementing.

The same command should also be applied on the legacy nodes (not yet migrated) to make sure there is no traffic lost or traffic with errored cells.

RP/0/RP0/CPU0:router(admin)#show controllers fabric plane 0 statistics detail
 
   
  Total number of providers for the statistics: 1
  Total received data cells: 7063
  Total received unicast data cells: 4487
  Total received low priority unicast data cells: 4487
  Total received high priority unicast data cells: 0
  Total received multicast data cells: 2576
  Total received low priority multicast data cells: 2050
  Total received high priority multicast data cells: 526
  Total transmitted data cells: 21094
  Total transmitted unicast data cells: 4487
  Total transmitted low priority unicast data cells: 4487
  Total transmitted high priority unicast data cells: 0
  Total transmitted multicast data cells: 16607
  Total transmitted low priority multicast data cells: 13977
  Total transmitted high priority multicast data cells: 2630
  Total received correctable errored cells: 0
  Total received uncorrectable errored cells: 0
  Total received parity error cells: 0
  Total received stomp cells: 0
  Total received kill cells: 0
  Total received unknown cells: 0
  Total transmitted bogus cells: 4
  Total transmitted statically routed control cells: 0
  Total transmitted stomp cells: 0
  Total transmitted kill cells: 0
  Total transmitted ECI cells: 0
  Total transmitted LCE cells: 0
  Total unicast lost cells: 0
  Total multicast lost cells: 0
  Total ctb enqueue to off queue  cells: 0
  Total non-ctb enqueue to off queue  cells: 0
  Total incoming header error cells: 0
  Total incoming data error cells: 0
  Total outgoing header error cells: 0
  Total outgoing data error cells: 0
  Total scs ce error cells: 0
  Total scs uce error cells: 0
  Last clearing of "show controller fabric plane" counters 00:06:22

Verifying Fabric Link Connectivity

This section describes the commands used to check the Line Card (LC) to Fabric and Route Processor (RP) to Fabric links for all LCs and RPs in the router (and for DRPs as well). The following commands may be used to check the link connectivity for each LC/RP node.

IngressQ to Fabric connectivity:

show controller ingressq fabric links loc <LC/RP/DRP location>

Fabric to FabricQ connectivity:

show controller fabricq link all loc <LC/RP/DRP location>

All links should be UP. Please repeat the CLI for ALL LC/RP/DRP locations in the router.

RP/0/RP0/CPU0:router(admin)#show controllers ingressq fabric links loc 0/5/cpu0
Ingressq link state
plane-id    link-id     ADMIN-STATE OPER-STATE  AVAIL-STATE UP-COUNT    
----------------------------------------------------.
0           0           UP          UP          UP          2           
0           8           UP          UP          UP          2           
0           16          UP          UP          UP          2           
0           24          UP          UP          UP          2           
1           1           UP          UP          UP          2           
1           9           UP          UP          UP          2           
1           17          UP          UP          UP          2           
1           25          UP          UP          UP          2           
2           2           UP          UP          UP          1           
2           10          UP          UP          UP          1           
2           18          UP          UP          UP          1           
2           26          UP          UP          UP          1           
3           3           UP          UP          UP          1           
3           11          UP          UP          UP          1           
3           19          UP          UP          UP          1           
3           27          UP          UP          UP          1           
4           4           UP          UP          UP          1           
4           12          UP          UP          UP          1           
4           20          UP          UP          UP          1           
4           28          UP          UP          UP          1           
5           5           UP          UP          UP          1           
5           13          UP          UP          UP          1           
5           21          UP          UP          UP          1           
5           29          UP          UP          UP          1           
6           6           UP          UP          UP          1           
6           14          UP          UP          UP          1           
6           22          UP          UP          UP          1           
6           30          UP          UP          UP          1           
7           7           UP          UP          UP          1           
7           15          UP          UP          UP          1           
7           23          UP          UP          UP          1           
7           31          UP          UP          UP          1           
RP/0/RP0/CPU0:router(admin)#show controllers fabricq link-info all loc 0/5/cpu0 
 
   
  Location:  0/5/CPU0
  Asic Instance:   0
  Fabric Destination Address:    20
  Retry period:  0 sec
  Link Active bitmap (1=up,0=down):  0xffffffff
  +------------------------------------------------------------------------+
  |Link #|Driver state | FSDB state  |Barrier state|Up (Drv Barr)| Errors  |
  +------------------------------------------------------------------------+
  |    0 |     Up      |     Up      |     Up      |     2  2    |         |
  |    1 |     Up      |     Up      |     Up      |     2  2    |         |
  |    2 |     Up      |     Up      |     Up      |     2  2    |         |
  |    3 |     Up      |     Up      |     Up      |     2  2    |         |
  |    4 |     Up      |     Up      |     Up      |     2  2    |         |
  |    5 |     Up      |     Up      |     Up      |     2  2    |         |
  |    6 |     Up      |     Up      |     Up      |     2  2    |         |
  |    7 |     Up      |     Up      |     Up      |     2  2    |         |
  |    8 |     Up      |     Up      |     Up      |     1  1    |         |
  |    9 |     Up      |     Up      |     Up      |     1  1    |         |
  |   10 |     Up      |     Up      |     Up      |     1  1    |         |
  |   11 |     Up      |     Up      |     Up      |     1  1    |         |
  |   12 |     Up      |     Up      |     Up      |     1  1    |         |
  |   13 |     Up      |     Up      |     Up      |     1  1    |         |
  |   14 |     Up      |     Up      |     Up      |     1  1    |         |
  |   15 |     Up      |     Up      |     Up      |     1  1    |         |
  |   16 |     Up      |     Up      |     Up      |     1  1    |         |
  |   17 |     Up      |     Up      |     Up      |     1  1    |         |
  |   18 |     Up      |     Up      |     Up      |     1  1    |         |
  |   19 |     Up      |     Up      |     Up      |     1  1    |         |
  |   20 |     Up      |     Up      |     Up      |     1  1    |         |
  |   21 |     Up      |     Up      |     Up      |     1  1    |         |
  |   22 |     Up      |     Up      |     Up      |     1  1    |         |
  |   23 |     Up      |     Up      |     Up      |     1  1    |         |
  |   24 |     Up      |     Up      |     Up      |     1  1    |         |
  |   25 |     Up      |     Up      |     Up      |     1  1    |         |
  |   26 |     Up      |     Up      |     Up      |     1  1    |         |
  |   27 |     Up      |     Up      |     Up      |     1  1    |         |
  |   28 |     Up      |     Up      |     Up      |     1  1    |         |
  |   29 |     Up      |     Up      |     Up      |     1  1    |         |
  |   30 |     Up      |     Up      |     Up      |     1  1    |         |
  |   31 |     Up      |     Up      |     Up      |     1  1    |         |
  +------------------------------------------------------------------------+
 
   
Location:  0/5/CPU0
  Asic Instance:   1
  Fabric Destination Address:    21
  Retry period:  0 sec
  Link Active bitmap (1=up,0=down):  0xffffffff
  +------------------------------------------------------------------------+
  |Link #|Driver state | FSDB state  |Barrier state|Up (Drv Barr)| Errors  |
  +------------------------------------------------------------------------+
  |    0 |     Up      |     Up      |     Up      |     2  2    |         |
  |    1 |     Up      |     Up      |     Up      |     2  2    |         |
  |    2 |     Up      |     Up      |     Up      |     2  2    |         |
  |    3 |     Up      |     Up      |     Up      |     2  2    |         |
  |    4 |     Up      |     Up      |     Up      |     2  2    |         |
  |    5 |     Up      |     Up      |     Up      |     2  2    |         |
  |    6 |     Up      |     Up      |     Up      |     2  2    |         |
  |    7 |     Up      |     Up      |     Up      |     2  2    |         |
  |    8 |     Up      |     Up      |     Up      |     1  1    |         |
  |    9 |     Up      |     Up      |     Up      |     1  1    |         |
  |   10 |     Up      |     Up      |     Up      |     1  1    |         |
  |   11 |     Up      |     Up      |     Up      |     1  1    |         |
  |   12 |     Up      |     Up      |     Up      |     1  1    |         |
  |   13 |     Up      |     Up      |     Up      |     1  1    |         |
  |   14 |     Up      |     Up      |     Up      |     1  1    |         |
  |   15 |     Up      |     Up      |     Up      |     1  1    |         |
  |   16 |     Up      |     Up      |     Up      |     1  1    |         |
  |   17 |     Up      |     Up      |     Up      |     1  1    |         |
  |   18 |     Up      |     Up      |     Up      |     1  1    |         |
  |   19 |     Up      |     Up      |     Up      |     1  1    |         |
  |   20 |     Up      |     Up      |     Up      |     1  1    |         |
  |   21 |     Up      |     Up      |     Up      |     1  1    |         |
  |   22 |     Up      |     Up      |     Up      |     1  1    |         |
  |   23 |     Up      |     Up      |     Up      |     1  1    |         |
  |   24 |     Up      |     Up      |     Up      |     1  1    |         |
  |   25 |     Up      |     Up      |     Up      |     1  1    |         |
  |   26 |     Up      |     Up      |     Up      |     1  1    |         |
  |   27 |     Up      |     Up      |     Up      |     1  1    |         |
  |   28 |     Up      |     Up      |     Up      |     1  1    |         |
  |   29 |     Up      |     Up      |     Up      |     1  1    |         |
  |   30 |     Up      |     Up      |     Up      |     1  1    |         |
  |   31 |     Up      |     Up      |     Up      |     1  1    |         |
  +------------------------------------------------------------------------+

7. Apply power to the new LCC (Rack 1).

8. Connect all fabric cables that connect the fabric planes in the new LCC to the FCCs.

9. Specify that the LED in question is the one on the FCC OIM-LED module.

10. do show controllers fabric rack-status all detail

11. do show controllers fabric fabric-backpressure summary

12. no controllers fabric rack 1 install-mode

13. commit

14. do show controllers rack-status all detail

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/RP1/CPU0:router# admin

Places the router in administration EXEC mode.

All commands listed in this procedure should be entered on the pre-existing single-chassis system.

Step 2 

configure

Example:

RP/0/RP1/CPU0:router(admin)#configure

Places the router in administration configuration mode.

Step 3 

no hw-module power disable loc 0/SM0/SP

Example:

RP/0/RP1/CPU0:router(admin-config)# no hw-module power disable loc 0/SM0/SP

Enables the power to the specified fabric plane in your single-chassis system.

Step 4 

controllers fabric rack 1 install-mode

Example:

RP/0/RP1/CPU0:router(admin-config)# controllers fabric rack 1 install-mode

Modifies the target configuration to change the Rack 1 configuration to installation mode.

Step 5 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 6 

Apply power to the new LCC (Rack 1).

Starts up the second LCC (Rack 1).

Step 7 

Connect all fabric cables that connect the fabric planes in the new LCC to the FCCs.

Interconnects the fabric cards in the LCC and FCC.

Step 8 

In the FCCs, check the LEDs for the cables that connect to the new LCC (Rack 1).

Green LEDs indicate that the cables are connected correctly.

If the LEDs display a color other than green, see Cisco IOS XR Getting Started Guide for information on interpreting the LED display.

Step 9 

do show controllers fabric rack-status all detail

Example:

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail

Displays the status of all racks and additional information for racks in installation mode.

Wait for the status in the Rack in Install and Rack out of Install columns to change to UP for all planes.

Step 10 

do show controllers fabric fabric-backpressure summary

Example:

RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric fabric-backpressure summary

Displays the backpressure status for all racks.

The status for the row labeled "Rack 1: All Groups Received? :" should be "Yes."

Step 11 

no controllers fabric rack 1 install-mode

Example:

RP/0/RP1/CPU0:router(admin-config)# no controllers fabric rack 1 install-mode

Modifies the target configuration to change the Rack 1 configuration to normal mode.

Step 12 

commit

Example:

RP/0/RP1/CPU0:router(admin-config)# commit

Commits the target configuration to the router running configuration.

Step 13 

do show controllers rack-status all detail

Example:

RP/0/RP1/CPU0:router(admin-config)# do show controllers rack-status all detail

Displays the status of all racks in the system.

In a properly operating system, the rack status for all racks should be Normal, and the server status should be Present.

What to Do Next

When all chassis in the multishelf system are operational and communicating with each other, it is time to continue system configuration, as described in the documents in the "Related Documents" section on page 1-63.

Troubleshooting Tips

For troubleshooting information, see the documents described in the "Related Documents" section on page 1-63.

Example

The following example shows commands to enable power to the newly installed CRS-3 Fabric Card:

RP/0/RP0/CPU0:router#admin
RP/0/RP0/CPU0:router(admin)#config
RP/0/RP0/CPU0:router(admin-config)#no hw-module power disable loc 0/SM0/SP
RP/0/RP0/CPU0:router(admin-config)#commit

Verify that power has been enabled to the Fabric Node (state is not UNPOWERED).

RP/0/RP0/CPU0:router(admin)#show platform 
Node            Type                 PLIM            State           Config State
<snip>
0/SM0/SP        FC-140G/S(SP)        N/A             PRESENT         PWR,NSHUT,MON
0/SM1/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM2/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM3/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM4/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM5/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM6/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON
0/SM7/SP        FC/S(SP)             N/A             IOS XR RUN      PWR,NSHUT,MON

Configuration Examples for Migrating to a Cisco CRS-3 Carrier Routing System

This section provides examples for the following procedures:

Displaying Chassis Serial Numbers: Example, page 1-58

Adding a Fabric Card Chassis: Example, page 1-58

Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example, page 1-61

Displaying Chassis Serial Numbers: Example

The following example shows how to display the chassis serial numbers in a Cisco CRS-3 Carrier Routing System:

RP/0/RP0/CPU0:router(admin)# show diag chassis
 
   
RACK   0 :
  MAIN:  board type 0001e0
         800-24872-01 rev 20
         dev N/A
         S/N TBA08260159
  PCA:   73-7640-05 rev 20
  PID:   CRS-16-LCC
  VID:   V01
  CLEI:  IPM6700DRA
  ECI:   445022
  RACK NUM: 0
 
   
RACK   1 :
 
   
  MAIN:  board type 0001e0
         800-24872-01 rev 20
 
   
         dev N/A
         S/N TBA08260159
  PCA:   73-7640-05 rev 20
  PID:   CRS-16-LCC
  VID:   V01
  CLEI:  IPM6700DRA
  ECI:   445022
  RACK NUM: 0
 
   
RACK 240 :
  MAIN:  board type 0001e0
         800-24872-01 rev 20
         dev N/A
         S/N TBA08260159
  PCA:   73-7640-05 rev 20
  PID:   CRS-16-LCC
  VID:   V01
  CLEI:  IPM6700DRA
  ECI:   445022
  RACK NUM: 0

Adding a Fabric Card Chassis: Example

The following example shows how to add a single FCC to an existing single-chassis system:

RP/0/RP1/CPU0:router# admin
RP/0/RP1/CPU0:router(admin)# configure 
RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820052000001 rack 0
 
   
RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820052000000 rack F0
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM9/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 1 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM6/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 2 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM3/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 3 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM0/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 4 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM12/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 5 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM15/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 6 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM18/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 7 
RP/0/RP1/CPU0:router(admin-config)# oim count 1
RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM21/FM
 
   
RP/0/RP1/CPU0:router(admin-config)# commit
RP/0/RP1/CPU0:router(admin-config)# end
 
   

Power is applied to the FCC at this time.

RP/0/RP1/CPU0:router(admin)# show platform F0/**/*
 
   
Node            Type            PLIM            State           Config State
-----------------------------------------------------------------------------
F0/SM0/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM3/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM6/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM9/SP       FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM12/SP      FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM15/SP      FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM18/SP      FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SM21/SP      FCC-SFC(SP)     FCC-FM-1S       IOS XR RUN      PWR,NSHUT,MON
F0/SC0/CPU0     FCC-SC(Standby) N/A             IOS XR RUN      PWR,NSHUT,MON
F0/SC1/CPU0     FCC-SC(Active)  N/A             IOS XR RUN      PWR,NSHUT,MON
F0/AM0/SP       ALARM(SP)       N/A             IOS XR RUN      PWR,NSHUT,MON
F0/AM1/SP       ALARM(SP)       N/A             IOS XR RUN      PWR,NSHUT,MON
F0/LM0/SP       FCC-LED(SP)     N/A             IOS XR RUN      PWR,NSHUT,MON
F0/LM1/SP       FCC-LED(SP)     N/A             IOS XR RUN      PWR,NSHUT,MON
 
   
RP/0/RP1/CPU0:router(admin)# configure 
 
   
RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane all
 
   
  Flags: P - plane admin down,       p - plane oper down 
         C - card admin down,        c - card  oper down 
         L - link port admin down,   l - linkport oper down 
         A - asic admin down,        a - asic oper down 
         B - bundle port admin Down, b - bundle port oper down 
         I - bundle admin down,      i - bundle oper down 
         N - node admin down,        n - node down 
         o - other end of link down  d - data down
         f - failed component downstream 
         m - plane multicast down 
 
   
 Plane  Admin   Oper      
 Id     State   State
 --------------------
 0      UP      UP        
 1      UP      UP        
 2      UP      UP         
 3      UP      UP        
 4      UP      UP        
 5      UP      UP         
 6      UP      UP        
 7      UP      UP         
 
   
RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdown
RP/0/RP1/CPU0:router(admin-config)# commit
RP/0/RP1/CPU0:router(admin-config)# end
 
   
RP/0/RP1/CPU0:Mar  4 18:37:55.055 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDOWN : Plane 
0 state changed to DOWN: 
RP/0/RP1/CPU0:Mar  4 18:37:55.088 : config[65733]: %MGBL-LIBTARCFG-6-ADMIN_COMMIT : 
Administration configuration committed by user 'user_a'. 
 
   

The FC/S card is replaced with an FC-140G/S card at this point.

 
   
RP/0/RP1/CPU0:Mar  4 18:38:32.680 : oir_daemon[245]: %PLATFORM-OIRD-5-OIROUT : OIR: Node 
0/SM0/SP removed  
RP/0/RP1/CPU0:Mar  4 18:38:54.328 : oir_daemon[245]: %PLATFORM-OIRD-5-OIRIN : OIR: Node 
0/SM0/SP inserted 
SP/0/SM0/SP:Mar  4 18:40:52.575 : alphadisplay[100]: %PLATFORM-ALPHA_DISPLAY-6-CHANGE : 
Alpha display on node 0/SM0/SP changed to IOS-XR   in state default 
SP/0/SM0/SP:Mar  4 18:41:34.027 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_INITIALIZED : 
Fabric ASICs initialized   
 
   
RP/0/RP1/CPU0:router(admin)# show platform 0/sm9/sp
 
   
0/SM9/SP       FC-140G/S(SP)     N/A         IOS-XR RUN      PWR,NSHUT,MON
 
   

The fabric cable is attached to the FC-140G/S card at this point.

 
   
RP/0/RP1/CPU0:router(admin)# configure 
RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane 0 detail
...
 Plane  Admin   Oper       Down       Total     Down   
 Id     State   State      Flags      Bundles   Bundles
 ------------------------------------------------------
 0      DOWN    DOWN       pPm        9         6 
 
   
RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane 0 detail
...
 Plane  Admin   Oper       Down       Total     Down   
 Id     State   State      Flags      Bundles   Bundles
 ------------------------------------------------------
 0      DOWN    DOWN        P          9         6 
 
   
RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdown
RP/0/RP1/CPU0:router(admin-config)# commit
 
   
RP/0/RP1/CPU0:Mar  4 18:47:42.930 : fsdb_aserver[173]: %FABRIC-FSDB-1-PLANE_UPDOWN : Plane 
0 state changed to UP:  
RP/0/RP1/CPU0:Mar  4 18:47:42.954 : config[65733]: %MGBL-LIBTARCFG-6-ADMIN_COMMIT : 
Administration configuration committed by user 'user_a'.
 
   
RP/0/RP1/CPU0:router(admin-config)# end
RP/0/RP1/CPU0:router(admin)# show controllers fabric plane all
 
   
  Flags: P - plane admin down,       p - plane oper down 
         C - card admin down,        c - card  oper down 
         L - link port admin down,   l - linkport oper down 
         A - asic admin down,        a - asic oper down 
         B - bundle port admin Down, b - bundle port oper down 
         I - bundle admin down,      i - bundle oper down 
         N - node admin down,        n - node down 
         o - other end of link down  d - data down
         f - failed component downstream 
         m - plane multicast down 
 
   
 Plane  Admin   Oper      
 Id     State   State
 --------------------
 0      UP      UP        
 1      UP      UP        
 2      UP      UP         
 3      UP      UP        
 4      UP      UP        
 5      UP      UP         
 6      UP      UP        
 7      UP      UP         
 
   

Adding an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis: Example

The following example shows how to add an LCC to a Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis:

RP/0/RP1/CPU0:router# admin
RP/0/RP1/CPU0:router(admin)# configure 
RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820031000000 rack 1
RP/0/RP1/CPU0:router(admin-config)# control fabric rack 1 install-mode
RP/0/RP1/CPU0:router(admin-config)# commit
 
   

Apply power, attach cables, and check cable LEDs.

 
   
RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail
 
   
Rack   Rack       Server
Num    Status     Status
----   ------     ------
 
   
 0       NORMAL    PRESENT   
 1      INSTALL    PRESENT                         Oper State       
                                             ---------------------- 
                               Plane  Admin  Rack in     Rack out   
                               Num    State  Install     of Install 
                               -----  -----  -------     ---------- 
                               0      UP     UP          UP         
                               1      UP     UP          DOWN       
                               2      UP     UP          DOWN   
                               3      UP     UP          DOWN   
                               4      UP     UP          DOWN         
                               5      UP     UP          DOWN        
                               6      UP     UP          DOWN   
                               7      UP     UP          DOWN     
 
   
 F0      NORMAL    PRESENT   
 
   
RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detail
 
   
Rack   Rack       Server
Num    Status     Status
----   ------     ------
 
   
 0       NORMAL    PRESENT   
 1      INSTALL    PRESENT                         Oper State       
                                             ---------------------- 
                               Plane  Admin  Rack in     Rack out   
                               Num    State  Install     of Install 
                               -----  -----  -------     ---------- 
                               0      UP     UP          UP         
                               1      UP     UP          UP       
                               2      UP     UP          UP   
                               3      UP     UP          UP   
                               4      UP     UP          UP         
                               5      UP     UP          UP        
                               6      UP     UP          UP   
                               7      UP     UP          UP     
 
   
 F0      NORMAL    PRESENT   
 
   
RP/0/RP1/CPU0:router(admin-config)# show controllers fabric fabric-backpressure summary 
 
   
  Expected BP Fabric Groups in the System:  0  1  2  3  
 
   
  Rack 0:   All Groups Received? :  Yes
  ------
 
   
  Rack 1:   All Groups Received? :  Yes
 
   
RP/0/RP1/CPU0:router(admin-config)# no controllers fabric rack 1 install-mode
RP/0/RP1/CPU0:router(admin-config)# commit
RP/0/RP1/CPU0:router(admin-config)# do show controllers rack-status all detail
 
   
Rack   Rack       Server
Num    Status     Status
----   ------     ------
 
   
 0       NORMAL    PRESENT   
 1       NORMAL    PRESENT                         
 F0      NORMAL    PRESENT  
 
   

Where to Go Next

When all fabric planes on both LCCs are migrated, configured and connected to the FCCs, see Cisco IOS XR Getting Started Guide for information on general system setup and operation.

If you need to downgrade your Cisco CRS-3 Carrier Routing System 16-Slot Line Card Chassis back to a Cisco CRS-1 Carrier Routing System 16-Slot Line Card Chassis, see Chapter 2, "Converting to an Integrated Switch System."

For this release use the Turbo boot procedure described in Appendix A to downgrade the system before swapping out the fabric to downgrade your Cisco CRS-3 Carrier Routing System Router back to a Cisco CRS-1 Carrier Routing System Router.

Additional References

The following sections provide references related to upgrading a single-chassis Cisco CRS-1 system to a single-chassis Cisco CRS-3 system.

Related Documents

Related Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Documentation, page 1-63

Related Documentation for Configuring the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Using Cisco IOS XR, page 1-63

Related Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Documentation

For additional documentation related to hardware installation and site planning, see the following Cisco Systems documents:

Related Topic
Document Title

Cisco CRS Carrier Routing System 16-slot line card chassis system description and installation planning

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Site Planning Guide

FCC installation

Cisco CRS Carrier Routing System Fabric Card Chassis Installation Guide

LCC installation

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Installation Guide

Cabling between all system components

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Interconnection and Cabling Guide

Color codes for FCC OIM-LED panel LEDs

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis System Description

Troubleshooting

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Troubleshooting Guide


Related Documentation for Configuring the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Using Cisco IOS XR

For additional documentation related to the configuration of the Cisco CRS Carrier Routing System 16-Slot Line Card Chassis using Cisco IOS XR, see the following Cisco Systems documents:

Related Topic
Document Title

Cisco CRS Carrier Routing System 16-Slot Line Card Chassis configuration and general system configuration after the fabric installation and configuration is complete

Cisco IOS XR Getting Started Guide


Technical Assistance

Description
Link

The Cisco Technical Support website contains thousands of pages of searchable technical content, including links to products, technologies, solutions, technical tips, and tools. Registered Cisco.com users can log in from this page to access even more content.

http://www.cisco.com/techsupport