-
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide
-
Preface
-
Migrating to a Cisco CRS-3 Carrier Routing System
-
Downgrading your Cisco CRS-3 Carrier Routing System Router back to a Cisco CRS-1 Carrier
-
Cisco CRS-3 Carrier Routing System Router Command Changes
-
Turbo Boot Procedure
-
Cisco CRS-1 to Cisco CRS-3 Upgrade Decision Trees
-
Cisco CRS-1 Carrier Routing System to Cisco CRS-3 Carrier Routing System Migration Guide index
-
Feedback
Table Of Contents
Migrating to a Cisco CRS-3 Carrier Routing System
CRS-1 to CRS-3 Software Migration Compatibility Matrix
Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3
Checking your Existing Flash Disk Size
Flash Disk Upgrade Process to 4GB
Verifying the Disk File System
Verifying Standby RP Disk Upgrade
File System Upgrade Procedure for 2GB Flash Disks
Minimizing Traffic Loss During the Upgrade
Verifying that the System Meets RP Memory Requirements
IOS-XR Software Upgrade Procedure
New Image Name Changes for 4.0 and Onwards
Additional Pre-upgrade System Checks
Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware
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
How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot)
Administratively Disabling the Fabric Plane
Disabling Power to the CRS-1 Fabric Card
Physically Removing the CRS-1 Fabric Card
Installing a CRS-3 Fabric Card
Verifying the Installation of the CRS-3 Fabric Card
Understanding the Alphanumeric LEDs
Troubleshooting the CRS-3 Fabric Card
Powering up the Replaced Fabric Card
How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot)
Administratively Disabling the Fabric Plane
Disabling Power to the CRS-1 Fabric Card
Physically Removing the CRS-1 Fabric Card
Installing a CRS-3 Fabric Card
Verifying the Installation of the CRS-3 Fabric Card
Understanding the Alphanumeric LEDs
Troubleshooting the CRS-3 Fabric Card
Powering up the Replaced Fabric Card
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
Disabling Power to the CRS-1 Fabric Card
Physically Removing the CRS-1 Fabric Card
Installing a CRS-3 Fabric Card
Verifying the Installation of the CRS-3 Fabric Card
Understanding the Alphanumeric LEDs
Troubleshooting the CRS-3 fabric card
Powering up the Replaced Fabric Card
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
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
Related Cisco CRS Carrier Routing System 16-Slot Line Card Chassis Documentation
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
Contents
This chapter contains the following sections:
•
•
•
•
•
•
•
•
•
•
•
WarningCRS-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.
Note
Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System
WarningAt 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
Route Processor (RP)
1.54
Distributed Route Processor (DRP)
1.54
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 disk0For Auto FPD to work please execute the following command in admin mode
RP/0/RP0/CPU0:CRS-1(admin-config)# fpd auto-upgradeOPTION-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 filesystemWed Feb 11 15:28:57.401 PST PSTFile 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 FLASHCapacity: 8215201 Sectors, Total 4206182912 Bytes, (512 Bytes/sectorDisk 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/cpu0The above command will create a partition of 3.5/0.5 between disk1 and disk1a
Note
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/cpu0Mountpoint FsType FsType Size State DrvrPid Mirror Flags================================================================================/disk1: FAT16 FAT32 3.4G Mounted 0032792 Enabled/disk1a: FAT16 FAT32 0.5G Mounted 0032792Setting 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/cpu0Swapping 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
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
Step 2
For OSPF use the max-metric command.
router(config-ospf)#max-metric router-lsaFor ISIS use the spf-overload-bit command.
router(config-isis)#set-overload-bitStep 3
For OSPF use the no max-metric command
router(config-ospf)#no max-metric router-lsaFor ISIS use the no spf-overload-bit command.
router(config-isis)#no set-overload-bitPrior 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-changeYou 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
router#copy running-config tftp://...running_config.txtrouter#adminrouter(admin)#copy running-config tftp://...admin-running_config.txtrouter(admin)#exitStep 5
Step 6
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 memoryTue Oct 12 22:17:28.761 PSTPhysical 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:
Note
Note
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.
.-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 platformTue Oct 12 23:34:37.898 PSTNode Type PLIM State Config State-------------------------------------------------------------------------------------- -0/0/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/1/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/2/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/3/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/4/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/5/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/6/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/7/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/8/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/9/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/10/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/11/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/12/CPU0 MSC-140G 20-10GbE IOS XR RUN PWR,NSHUT,MON0/13/CPU0 MSC-140G 14-10GbE IOS XR RUN PWR,NSHUT,MON0/14/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON0/14/CPU0 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/14/CPU1 DRP(Active) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/15/SP DRP(SP) N/A IOS XR RUN PWR,NSHUT,MON0/15/CPU0 DRP(Standby) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/15/CPU1 DRP(Standby) DRP-ACC IOS XR RUN PWR,NSHUT,MON0/RP0/CPU0 RP(Active) N/A IOS XR RUN PWR,NSHUT,MON0/RP1/CPU0 RP(Standby) N/A IOS XR RUN PWR,NSHUT,MON0/FC0/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON0/FC1/SP LCC-FAN-CT(SP) N/A IOS XR RUN PWR,NSHUT,MON0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MONExecute the show redundancy command to verify that a Standby RP is available and in "ready" state.
RP/0/RP0/CPU0:router#show redRedundancy information for node 0/RP0/CPU0:==========================================Node 0/RP0/CPU0 is in ACTIVE rolePartner node (0/RP1/CPU0) is in STANDBY roleStandby node in 0/RP1/CPU0 is readyStandby node in 0/RP1/CPU0 is NSR-readyExecute 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 summaryTue Oct 12 23:41:48.562 PSTInterface Type Total UP Down Admin Down-------------- ----- -- ---- ----------ALL TYPES 750 712 0 38--------------IFT_LOOPBACK 1 1 0 0IFT_ETHERNET 6 2 0 4IFT_NULL 1 1 0 0IFT_TENGETHERNET 232 198 0 34IFT_VLAN_SUBIF 510 510 0 0show install active summary (verify that the proper set of packages are active)
Single-chassis example:
RP/0/RP0/CPU0:router(admin)#show install active summaryWed Oct 13 06:47:17.604 UTCDefault Profile:Admin ResourcesSDRs:OwnerActive Packages:disk0:hfr-cgn-px-4.0.0.65Idisk0:hfr-mpls-px-4.0.0.65Idisk0:hfr-mcast-px-4.0.0.65Idisk0:hfr-mini-px-4.0.0.65IMultishelf example:
RP/0/RP0/CPU0:MC-SCALE(admin)#show install active summaryDefault Profile:Admin ResourcesSDRs:Ownertaiko-sdrActive Packages:disk0:hfr-fit-px-4.0.2.19Idisk0:hfr-doc-px-4.0.2.19Idisk0:hfr-mpls-px-4.0.2.19Idisk0:hfr-mgbl-px-4.0.2.19Idisk0:hfr-mcast-px-4.0.2.19Idisk0:hfr-mini-px-4.0.2.19Idisk0:hfr-fpd-px-4.0.2.19Idisk0:hfr-diags-px-4.0.2.19IExecute 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
RP/0/RP0/CPU0:router(admin)#show filesystemWed Oct 13 06:54:57.000 UTCFile 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
RP/0/RP0/CPU0:router(admin)# show install inactiveNode 0/0/CPU0 [LC] [SDR: Owner]Boot Device: mem:Inactive Packages:disk0:hfr-fit-px-4.0.0.63Idisk0:hfr-infra-test-px-4.0.0.65Idisk0:hfr-upgrade-px-4.0.0.65Idisk0:hfr-fit-px-4.0.0.65Idisk0:hfr-cgn-px-4.0.0.63Idisk0:hfr-mpls-px-4.0.0.63Idisk0:hfr-mcast-px-4.0.0.63Idisk0:hfr-fpd-px-4.0.0.65Idisk0:hfr-fpd-px-4.0.0.63Idisk0:hfr-diags-px-4.0.0.63Idisk0:hfr-diags-px-4.0.0.65IExecute 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 syncInfo: This operation will remove the following packages:Info: disk0:hfr-diags-px-4.0.0.65IInfo: disk0:hfr-diags-supp-4.0.0.65IInfo: disk0:hfr-doc-px-4.0.0.65IInfo: disk0:hfr-doc-supp-4.0.0.65IInfo: disk0:hfr-fit-px-4.0.0.65IInfo: disk0:hfr-fit-4.0.0.65IThe install operation will continue asynchronously.
RP/0/RP0/CPU0:router(admin)#Install operation 192 completed successfullyStep 3
RP/0/RP0/CPU0:router(admin)#install commitWed Oct 13 07:10:37.141 UTCInstall 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/cpu0Step 4
router#copy running-config tftp://...running_config.txtrouter#adminrouter(admin)#copy running-config tftp://...admin-running_config.txtrouter(admin)#exitStep 5
Note
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
Step 1
router(admin)# install add tar <source>/<path>/<pie> syncThe
<source>keywordcan be one ofdisk0:,disk1:,compactflash:,harddisk:,tftp:,ftp:orrcp:.
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
<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
Note
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> syncStep 2
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
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 testThe install operation ID is printed after finishing each install command or can be obtained by running the show install log command.
Step 3
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.piesyncThe 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
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
Step 5
Step 6
router(admin)# install commitStep 7
router# show config failed startupIn 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
router# run nvgen -F 1Step 9
router# configrouter(config)#hostname <hostname>router(config)#commitrouter(config)#endStep 10
router# reloadUpdating Commit Database. Please wait...[OK]Proceed with reload? [confirm] <- Press "n"In same cases the following error may be reported:
router#reloadPreparing 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
OSPF
router(config-ospf)#no max-metric router-lsaISIS
router(config-isis)#no set-overload-bitDisk 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
router(admin)# show install inactive briefStep 2
router(admin)# install remove disk0:<package_name1> disk0:<package_name2> .. disk0:<pkg_nameN> syncor
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
router(admin)#cfs checkStep 4
OSPF
router(config-ospf)#no max-metric router-lsaISIS
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 startuprouter(admin)# show configuration failed startupMDR - 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
a.
b.
Step 2
Step 3
Step 4
Warning
Note
Note
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
a.
b.
Step 6
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.
Refer to Table 1-6 for a compatibility matrix of CRS-1 (legacy, 40G) and CRS-3 (140G) hardware:
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.
2.
3.
4.
5.
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 versionMon Mar 1 06:18:22.261 UTCCisco 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],•
RP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON<snip>•
RP/0/RP0/CPU0:router(admin)#show controllers fabric plane all<snip>Plane Admin Oper up->dn up->mcastId State State counter counter---------------------------------------------0 UP UP 0 01 UP UP 0 02 UP UP 0 03 UP UP 0 04 UP UP 0 05 UP UP 0 06 UP UP 0 07 UP UP 0 0
Note
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.
•
•
Note
•
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:
•
•
•
•
•
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.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
The following example shows commands to Administratively Disable the Fabric Plane on the CRS-1 Fabric Card:
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#commitRP/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 detailFri Jan 7 17:02:44.919 PSTFlags: P - plane admin down, p - plane oper downC - card admin down, c - card oper downA - asic admin down, a - asic oper downL - link port admin down, l - linkport oper downB - bundle port admin Down, b - bundle port oper downI - bundle admin down, i - bundle oper downN - node admin down, n - node downX - ctrl admin down, x - ctrl downo - other end of link down d - data downf - failed component downstreamm - plane multicast down, s - link port permanently shutdownt - no barrier input O - Out-Of-Service oper downT - topology mismatch down e - link port control onlyD - plane admin data downPlane Admin Oper up->dn up->mcast Down Total DownId State State counter counter Flags Bundles Bundles-------------------------------------------------------------------------0 DOWN DOWN 0 0 27 151 UP UP 0 0 27 152 UP UP 0 0 27 153 UP UP 0 0 27 154 UP UP 0 0 27 155 UP UP 0 0 27 156 UP UP 0 0 27 157 UP UP 0 0 27 15What 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.
2.
3.
4.
5.
6.
DETAILED STEPS
Example
The following example shows commands to disable power to the CRS-1 Fabric Card:
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP1/CPU0:router(admin-config)# end
RP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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
WarningOn 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
Required Tools and Equipment
You need the following tools to perform this task:
•
•
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
Step 1
Step 2
Step 3
Caution
Step 4
Step 5
Step 6
Caution
Step 7
Step 8
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
WarningFigure 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
Required Tools and Equipment
You need the following tools and part to perform this task:
•
•
•
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
Step 1
Step 2
Caution
Step 3
Note
Step 4
Step 5
Step 6
Step 7
Note
Step 8
Caution
Step 9
Step 10
Caution
Step 11
Note
Step 12
Note
Step 13
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)
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
Troubleshooting the CRS-3 Fabric Card
If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:
•
•
•
•
Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:
•
•
Prerequisites
Software Requirements
•
•
Hardware Requirements
•
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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
•
•
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
DETAILED STEPS
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#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitVerify that power has been enabled to the Fabric Node (state is not UNPOWERED).
RP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONHow 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:
•
•
•
•
•
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
•
•
•
Caution
For more information, see Cisco IOS XR ROM Monitor Guide.
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
DETAILED STEPS
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
•
•
•
Caution
For more information, see Cisco IOS XR ROM Monitor Guide.
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Example
The following example shows commands to disable power to the CRS-1 Fabric Card:
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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
WarningFigure 1-6 CRS-1 Fabric Card
Prerequisites
Before performing this task, you must first open the front cosmetic doors (if installed).
Caution
Required Tools and Equipment
You need the following tools to perform this task:
•
•
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
Step 1
Step 2
Step 3
Caution
Step 4
Step 5
Step 6
Caution
Step 7
Step 8
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
WarningFigure 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
Required Tools and Equipment
You need the following tools and part to perform this task:
•
•
•
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
Step 1
Step 2
Caution
Step 3
Note
Step 4
Step 5
Step 6
Step 7
Note
Step 8
Caution
Step 9
Step 10
Caution
Step 11
Note
Step 12
Note
Step 13
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)
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
Troubleshooting the CRS-3 Fabric Card
If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:
•
•
•
•
Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:
•
•
Prerequisites
Software Requirements
•
•
Hardware Requirements
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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
•
•
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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 platformNode Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONAdministratively 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#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 1 shutRP/0/RP0/CPU0:router(admin-config)#commitVerify 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 allPlane Admin Oper up->dn up->mcastId State State counter counter---------------------------------------------0 UP UP 2 21 UP UP 2 22 UP UP 0 03 UP UP 0 04 UP UP 0 05 UP UP 0 06 UP UP 0 07 UP UP 0 0Each 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 detailTotal number of providers for the statistics: 1Total received data cells: 7063Total received unicast data cells: 4487Total received low priority unicast data cells: 4487Total received high priority unicast data cells: 0Total received multicast data cells: 2576Total received low priority multicast data cells: 2050Total received high priority multicast data cells: 526Total transmitted data cells: 21094Total transmitted unicast data cells: 4487Total transmitted low priority unicast data cells: 4487Total transmitted high priority unicast data cells: 0Total transmitted multicast data cells: 16607Total transmitted low priority multicast data cells: 13977Total transmitted high priority multicast data cells: 2630Total received correctable errored cells: 0Total received uncorrectable errored cells: 0Total received parity error cells: 0Total received stomp cells: 0Total received kill cells: 0Total received unknown cells: 0Total transmitted bogus cells: 4Total transmitted statically routed control cells: 0Total transmitted stomp cells: 0Total transmitted kill cells: 0Total transmitted ECI cells: 0Total transmitted LCE cells: 0Total unicast lost cells: 0Total multicast lost cells: 0Total ctb enqueue to off queue cells: 0Total non-ctb enqueue to off queue cells: 0Total incoming header error cells: 0Total incoming data error cells: 0Total outgoing header error cells: 0Total outgoing data error cells: 0Total scs ce error cells: 0Total scs uce error cells: 0Last clearing of "show controller fabric plane" counters 00:06:22Verifying 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/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT----------------------------------------------------.0 0 UP UP UP 20 8 UP UP UP 20 16 UP UP UP 20 24 UP UP UP 21 1 UP UP UP 21 9 UP UP UP 21 17 UP UP UP 21 25 UP UP UP 22 2 UP UP UP 12 10 UP UP UP 12 18 UP UP UP 12 26 UP UP UP 13 3 UP UP UP 13 11 UP UP UP 13 19 UP UP UP 13 27 UP UP UP 14 4 UP UP UP 14 12 UP UP UP 14 20 UP UP UP 14 28 UP UP UP 15 5 UP UP UP 15 13 UP UP UP 15 21 UP UP UP 15 29 UP UP UP 16 6 UP UP UP 16 14 UP UP UP 16 22 UP UP UP 16 30 UP UP UP 17 7 UP UP UP 17 15 UP UP UP 17 23 UP UP UP 17 31 UP UP UP 1RP/0/RP0/CPU0:router(admin)#show controllers fabricq link-info all loc 0/5/cpu0Location: 0/5/CPU0Asic Instance: 0Fabric Destination Address: 20Retry period: 0 secLink 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/CPU0Asic Instance: 1Fabric Destination Address: 21Retry period: 0 secLink 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:
•
•
•
•
•
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
•
•
•
Caution
For more information, see Cisco IOS XR ROM Monitor Guide.
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
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
•
•
•
Caution
For more information, see Cisco IOS XR ROM Monitor Guide.
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
DETAILED STEPS
Example
The following example shows commands to disable power to the CRS-1 Fabric Card:
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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
WarningFigure 1-11 CRS-1 Fabric Card
Prerequisites
Before performing this task, you must first open the front cosmetic doors (if installed).
Caution
Required Tools and Equipment
You need the following tools to perform this task:
•
•
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
Step 1
Step 2
Step 3
Caution
Step 4
Step 5
Step 6
Caution
Step 7
Step 8
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
WarningFigure 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
Required Tools and Equipment
You need the following tools and part to perform this task:
•
•
•
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
Step 1
Step 2
Caution
Step 3
Note
Step 4
Step 5
Step 6
Step 7
Note
Step 8
Caution
Step 9
Step 10
Caution
Step 11
Note
Step 12
Note
Step 13
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)
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
Troubleshooting the CRS-3 fabric card
If the installed or replaced CRS-3 fabric card fails to operate or power up on installation:
•
•
•
•
Use the Status LEDs, located on the CRS-3 fabric card faceplate, to verify the correct installation of the CRS-3 fabric card:
•
•
Prerequisites
Software Requirements
•
•
Hardware Requirements
•
RP/0/RP0/CPU0:router#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitRP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC/S(SP) N/A UNPOWERED PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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
•
•
Hardware Requirements
•
•
•
Restrictions
None.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
Node Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/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 platformNode Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONAdministratively 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#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 0 shutRP/0/RP0/CPU0:router(admin-config)#no controller fabric plane 1 shutRP/0/RP0/CPU0:router(admin-config)#commitVerify 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 allPlane Admin Oper up->dn up->mcastId State State counter counter---------------------------------------------0 UP UP 2 21 UP UP 2 22 UP UP 0 03 UP UP 0 04 UP UP 0 05 UP UP 0 06 UP UP 0 07 UP UP 0 0Each 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 detailTotal number of providers for the statistics: 1Total received data cells: 7063Total received unicast data cells: 4487Total received low priority unicast data cells: 4487Total received high priority unicast data cells: 0Total received multicast data cells: 2576Total received low priority multicast data cells: 2050Total received high priority multicast data cells: 526Total transmitted data cells: 21094Total transmitted unicast data cells: 4487Total transmitted low priority unicast data cells: 4487Total transmitted high priority unicast data cells: 0Total transmitted multicast data cells: 16607Total transmitted low priority multicast data cells: 13977Total transmitted high priority multicast data cells: 2630Total received correctable errored cells: 0Total received uncorrectable errored cells: 0Total received parity error cells: 0Total received stomp cells: 0Total received kill cells: 0Total received unknown cells: 0Total transmitted bogus cells: 4Total transmitted statically routed control cells: 0Total transmitted stomp cells: 0Total transmitted kill cells: 0Total transmitted ECI cells: 0Total transmitted LCE cells: 0Total unicast lost cells: 0Total multicast lost cells: 0Total ctb enqueue to off queue cells: 0Total non-ctb enqueue to off queue cells: 0Total incoming header error cells: 0Total incoming data error cells: 0Total outgoing header error cells: 0Total outgoing data error cells: 0Total scs ce error cells: 0Total scs uce error cells: 0Last clearing of "show controller fabric plane" counters 00:06:22Verifying 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/cpu0Ingressq link stateplane-id link-id ADMIN-STATE OPER-STATE AVAIL-STATE UP-COUNT----------------------------------------------------.0 0 UP UP UP 20 8 UP UP UP 20 16 UP UP UP 20 24 UP UP UP 21 1 UP UP UP 21 9 UP UP UP 21 17 UP UP UP 21 25 UP UP UP 22 2 UP UP UP 12 10 UP UP UP 12 18 UP UP UP 12 26 UP UP UP 13 3 UP UP UP 13 11 UP UP UP 13 19 UP UP UP 13 27 UP UP UP 14 4 UP UP UP 14 12 UP UP UP 14 20 UP UP UP 14 28 UP UP UP 15 5 UP UP UP 15 13 UP UP UP 15 21 UP UP UP 15 29 UP UP UP 16 6 UP UP UP 16 14 UP UP UP 16 22 UP UP UP 16 30 UP UP UP 17 7 UP UP UP 17 15 UP UP UP 17 23 UP UP UP 17 31 UP UP UP 1RP/0/RP0/CPU0:router(admin)#show controllers fabricq link-info all loc 0/5/cpu0Location: 0/5/CPU0Asic Instance: 0Fabric Destination Address: 20Retry period: 0 secLink 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/CPU0Asic Instance: 1Fabric Destination Address: 21Retry period: 0 secLink 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.
8.
9.
10.
11.
12.
13.
14.
DETAILED STEPS
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#adminRP/0/RP0/CPU0:router(admin)#configRP/0/RP0/CPU0:router(admin-config)#no hw-module power disable loc 0/SM0/SPRP/0/RP0/CPU0:router(admin-config)#commitVerify that power has been enabled to the Fabric Node (state is not UNPOWERED).
RP/0/RP0/CPU0:router(admin)#show platformNode Type PLIM State Config State<snip>0/SM0/SP FC-140G/S(SP) N/A PRESENT PWR,NSHUT,MON0/SM1/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM2/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM3/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM4/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM5/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM6/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MON0/SM7/SP FC/S(SP) N/A IOS XR RUN PWR,NSHUT,MONConfiguration Examples for Migrating to a Cisco CRS-3 Carrier Routing System
This section provides examples for the following procedures:
•
•
•
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 chassisRACK 0 :MAIN: board type 0001e0800-24872-01 rev 20dev N/AS/N TBA08260159PCA: 73-7640-05 rev 20PID: CRS-16-LCCVID: V01CLEI: IPM6700DRAECI: 445022RACK NUM: 0RACK 1 :MAIN: board type 0001e0800-24872-01 rev 20dev N/AS/N TBA08260159PCA: 73-7640-05 rev 20PID: CRS-16-LCCVID: V01CLEI: IPM6700DRAECI: 445022RACK NUM: 0RACK 240 :MAIN: board type 0001e0800-24872-01 rev 20dev N/AS/N TBA08260159PCA: 73-7640-05 rev 20PID: CRS-16-LCCVID: V01CLEI: IPM6700DRAECI: 445022RACK NUM: 0Adding 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# adminRP/0/RP1/CPU0:router(admin)# configureRP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820052000001 rack 0RP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820052000000 rack F0RP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM9/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 1RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM6/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 2RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM3/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 3RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM0/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 4RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM12/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 5RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM15/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 6RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM18/FMRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 7RP/0/RP1/CPU0:router(admin-config)# oim count 1RP/0/RP1/CPU0:router(admin-config)# oim instance 0 location F0/SM21/FMRP/0/RP1/CPU0:router(admin-config)# commitRP/0/RP1/CPU0:router(admin-config)# endPower 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,MONF0/SM3/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM6/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM9/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM12/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM15/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM18/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SM21/SP FCC-SFC(SP) FCC-FM-1S IOS XR RUN PWR,NSHUT,MONF0/SC0/CPU0 FCC-SC(Standby) N/A IOS XR RUN PWR,NSHUT,MONF0/SC1/CPU0 FCC-SC(Active) N/A IOS XR RUN PWR,NSHUT,MONF0/AM0/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/AM1/SP ALARM(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/LM0/SP FCC-LED(SP) N/A IOS XR RUN PWR,NSHUT,MONF0/LM1/SP FCC-LED(SP) N/A IOS XR RUN PWR,NSHUT,MONRP/0/RP1/CPU0:router(admin)# configureRP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane allFlags: P - plane admin down, p - plane oper downC - card admin down, c - card oper downL - link port admin down, l - linkport oper downA - asic admin down, a - asic oper downB - bundle port admin Down, b - bundle port oper downI - bundle admin down, i - bundle oper downN - node admin down, n - node downo - other end of link down d - data downf - failed component downstreamm - plane multicast downPlane Admin OperId State State--------------------0 UP UP1 UP UP2 UP UP3 UP UP4 UP UP5 UP UP6 UP UP7 UP UPRP/0/RP1/CPU0:router(admin-config)# controllers fabric plane 0 shutdownRP/0/RP1/CPU0:router(admin-config)# commitRP/0/RP1/CPU0:router(admin-config)# endRP/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 removedRP/0/RP1/CPU0:Mar 4 18:38:54.328 : oir_daemon[245]: %PLATFORM-OIRD-5-OIRIN : OIR: Node 0/SM0/SP insertedSP/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 defaultSP/0/SM0/SP:Mar 4 18:41:34.027 : sfe_drvr[108]: %FABRIC-FABRIC_DRVR-6-ASIC_INITIALIZED : Fabric ASICs initializedRP/0/RP1/CPU0:router(admin)# show platform 0/sm9/sp0/SM9/SP FC-140G/S(SP) N/A IOS-XR RUN PWR,NSHUT,MONThe fabric cable is attached to the FC-140G/S card at this point.
RP/0/RP1/CPU0:router(admin)# configureRP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane 0 detail...Plane Admin Oper Down Total DownId State State Flags Bundles Bundles------------------------------------------------------0 DOWN DOWN pPm 9 6RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric plane 0 detail...Plane Admin Oper Down Total DownId State State Flags Bundles Bundles------------------------------------------------------0 DOWN DOWN P 9 6RP/0/RP1/CPU0:router(admin-config)# no controllers fabric plane 0 shutdownRP/0/RP1/CPU0:router(admin-config)# commitRP/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)# endRP/0/RP1/CPU0:router(admin)# show controllers fabric plane allFlags: P - plane admin down, p - plane oper downC - card admin down, c - card oper downL - link port admin down, l - linkport oper downA - asic admin down, a - asic oper downB - bundle port admin Down, b - bundle port oper downI - bundle admin down, i - bundle oper downN - node admin down, n - node downo - other end of link down d - data downf - failed component downstreamm - plane multicast downPlane Admin OperId State State--------------------0 UP UP1 UP UP2 UP UP3 UP UP4 UP UP5 UP UP6 UP UP7 UP UPAdding 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# adminRP/0/RP1/CPU0:router(admin)# configureRP/0/RP1/CPU0:router(admin-config)# dsc serial TBC0820031000000 rack 1RP/0/RP1/CPU0:router(admin-config)# control fabric rack 1 install-modeRP/0/RP1/CPU0:router(admin-config)# commitApply power, attach cables, and check cable LEDs.
RP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detailRack Rack ServerNum Status Status---- ------ ------0 NORMAL PRESENT1 INSTALL PRESENT Oper State----------------------Plane Admin Rack in Rack outNum State Install of Install----- ----- ------- ----------0 UP UP UP1 UP UP DOWN2 UP UP DOWN3 UP UP DOWN4 UP UP DOWN5 UP UP DOWN6 UP UP DOWN7 UP UP DOWNF0 NORMAL PRESENTRP/0/RP1/CPU0:router(admin-config)# do show controllers fabric rack-status all detailRack Rack ServerNum Status Status---- ------ ------0 NORMAL PRESENT1 INSTALL PRESENT Oper State----------------------Plane Admin Rack in Rack outNum State Install of Install----- ----- ------- ----------0 UP UP UP1 UP UP UP2 UP UP UP3 UP UP UP4 UP UP UP5 UP UP UP6 UP UP UP7 UP UP UPF0 NORMAL PRESENTRP/0/RP1/CPU0:router(admin-config)# show controllers fabric fabric-backpressure summaryExpected BP Fabric Groups in the System: 0 1 2 3Rack 0: All Groups Received? : Yes------Rack 1: All Groups Received? : YesRP/0/RP1/CPU0:router(admin-config)# no controllers fabric rack 1 install-modeRP/0/RP1/CPU0:router(admin-config)# commitRP/0/RP1/CPU0:router(admin-config)# do show controllers rack-status all detailRack Rack ServerNum Status Status---- ------ ------0 NORMAL PRESENT1 NORMAL PRESENTF0 NORMAL PRESENTWhere 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
For additional documentation related to hardware installation and site planning, see the following Cisco Systems documents:
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:
Technical Assistance
