Migrating to a Cisco CRS-3 Carrier Routing System

Transcription

1 CHAPTER 1 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 Release T Release Release Modification The single-chassis Cisco CRS-3 Carrier Routing System was introduced. The single-chassis Cisco CRS-3 Carrier Routing System adds support for 100GE interfaces. 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, page 1-2 Prerequisites for Upgrading IOS-XR Software Prior to Migrating to a Cisco CRS-3 Carrier Routing System, page 1-3 Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3, page 1-5 File System Upgrade Procedure for 2GB Flash Disks, page 1-7 IOS-XR Software Upgrade Procedure, page 1-9 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware, page

2 CRS-1 to CRS-3 Software Migration Compatibility Matrix Chapter 1 Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix, page 1-20 Information About, page 1-21 How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot), page 1-23 How to Migrate to a Cisco CRS-3 Carrier Routing System (8-Slot), page 1-40 How to Migrate to a Cisco CRS-3 Carrier Routing System (4-Slot), page 1-58 Configuration Examples for, page 1-80 Where to Go Next, page 1-85 Additional References, page 1-86 Warning Do NOT insert any CRS-3 hardware before completing the software migration to Cisco IOS XR software Release 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 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 3.4.x(PPC) 3.5.x(PPC) 3.6.x(PPC) 3.7.x(PPC) 3.8.0(PPC) 3.8.1(PPC) 3.8.2(PPC) Migration Version T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) Direct PIE Upgrade/Downgrade Supported No (must be done using Turbo Boot - refer to Appendix A for more information) No (must be done using Turbo Boot - refer to Appendix A for more information) No (must be done using Turbo Boot - refer to Appendix A for more information) No (must be done using Turbo Boot - refer to Appendix A for more information) Yes. Migration to FAT32 recommended before upgrading. Yes. Migration to FAT32 recommended before upgrading. Yes. Migration to FAT32 recommended before upgrading. 1-2

3 Prerequisites for Upgrading IOS-XR Software Prior to Table 1-1 CRS-1 to CRS-3 Software Migration Compatibility Matrix (continued) 3.8.3(PPC) T (PX), 4.0.1(PX), or 4.0.2(PX) Yes. Migration to FAT32 recommended before upgrading. Current Version 3.8.4(PPC) 3.9.0(PPC) 3.9.1(PPC) 3.9.2(PPC) 4.0.0(PPC) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) Migration Version T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) T (PX), 4.0.1(PX), or 4.0.2(PX) 4.0.0(PPC) 3.x.x(PPC) Direct PIE Upgrade/Downgrade Supported Yes. Migration to FAT32 recommended before upgrading. Yes. Migration to FAT32 recommended before upgrading. Yes. Migration to FAT32 recommended before upgrading. Yes. Migration to FAT32 recommended before upgrading. No (must be done using Turbo Boot - refer to Appendix A for more information). Upgrade package required. No (downgrades must be done using Turbo Boot - refer to Appendix A for more information). No (downgrades must be done using Turbo Boot - refer to Appendix A for more information). Note All IOS-XR Software releases prior to (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be upgraded to IOS XR software release or higher prior to being upgraded to IOS XR software release T (PX), 4.0.1(PX), or 4.0.2(PX) or be upgraded directly to IOS XR software release 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 T or higher. 1-3

4 Prerequisites for Upgrading IOS-XR Software Prior to At least a 2 GB FAT32 flashdisk is required to upgrade to Cisco IOS XR software Release 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 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 or higher or IOS-XR Software Release or higher images ROMMON version 1.54 is supported/installed. While upgrading from IOS-XR Software Release or higher to IOS-XR Software Release 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 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. 1-4

5 Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3 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 or above. If you are running a release of Cisco IOS XR software earlier than please refer to Upgrading Your File System From FAT16 to FAT32 in Appendix A, 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: 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: dumper-lnk rw qsm/dumper_nvram: dumper-lnk rw qsm/dumper_harddisk: dumper-lnk rw qsm/dumper_disk1: dumper-lnk rw qsm/dumper_disk0: dumper-lnk rw qsm/dumper_bootflash: harddisk rw harddisk: flash-disk rw disk0: flash-disk rw disk1: nvram rw nvram: 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 Series Router and Cisco CRS-1 Router Flash Disk Upgrade Tasks document online here: 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 1-5

6 Cisco IOS-XR Flash Disk Requirements for Migration to CRS-3 Chapter 1 RP/0/RP0/CPU0:router# show filesystem disk1: Model: UNIGEN FLASH Capacity: Sectors, Total 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 Enabled /disk1a: FAT16 FAT32 0.5G Mounted 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. 1-6

7 File System Upgrade Procedure for 2GB Flash Disks 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 Reducing Disk Space Usage 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. 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. 1-7

8 File System Upgrade Procedure for 2GB Flash Disks Chapter 1 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 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) 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 Step 4 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. 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 1-8

9 IOS-XR Software Upgrade Procedure Step 5 Step 6 Verify Mgmt access to the router (see caveats section) 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: 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: 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) Upgrade Package* (see note) Multicast Package Manageability Package MPLS Package Security Package Diagnostic package hfr-mini-px.pie or hfr-upgrade-px.pie or hfr-mcast-px.pie or hfr-mgbl-px.pie or hfr-mpls-px.pie or hfr-k9sec-px.pie or hfr-diags-px.pie or disk0:comp-hfr-mini-px or disk0:hfr-px-upgrade or disk0:hfr-mcast-px or disk0:hfr-mgbl-px or disk0:hfr-mpls-px or disk0:hfr-k9sec-px or disk0:hfr-diags-px or

10 IOS-XR Software Upgrade Procedure Chapter 1 Table 1-3 OS XR PPX Software PIE Filenames (continued) Documentation package hfr-doc-px.pie or Field Programmable Device package hfr-fpd-px.pie or disk0:hfr-doc-px or disk0:hfr-fpd-px or 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 (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 hfr-mini-p comp-hfr-full.vm hfr-full-p.vm comp-hfr-full hfr-full-p comp-hfr-mini-px.vm hfr-mini-px.vm comp-hfr-mini-px hfr-mini-px comp-hfr-full-px.vm hfr-full-px.vm comp-hfr-full-px c hfr-full-px comp-hfr-mini.pie hfr-mini-p.pie comp-hfr-mini hfr-mini-p comp-hfr-mini-px.pie hfr-mini-px.pie comp-hfr-mini-px hfr-mini-px hfr-fpd.pie hfr-fpd-p.pie hfr-fpd hfr-fpd-p 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. 1-10

11 IOS-XR Software Upgrade Procedure RP/0/RP0/CPU0:router(admin)#show platform Tue Oct 12 23:34: PST Node Type PLIM State Config State /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: PST Interface Type Total UP Down Admin Down ALL TYPES IFT_LOOPBACK IFT_ETHERNET IFT_NULL IFT_TENGETHERNET IFT_VLAN_SUBIF

12 IOS-XR Software Upgrade Procedure Chapter 1 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: UTC Default Profile: Admin Resources SDRs: Owner Active Packages: disk0:hfr-cgn-px i disk0:hfr-mpls-px i disk0:hfr-mcast-px i disk0:hfr-mini-px i 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 i disk0:hfr-doc-px i disk0:hfr-mpls-px i disk0:hfr-mgbl-px i disk0:hfr-mcast-px i disk0:hfr-mini-px i disk0:hfr-fpd-px i disk0:hfr-diags-px i 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 release. When upgrading to release 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: UTC File Systems: flash-disk rw disk0: flash-disk rw disk1a: flash-disk rw disk1: flash-disk rw disk0a: 1-12

13 IOS-XR Software Upgrade Procedure nvram rw nvram: flash rw bootflash: Step 2 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. 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 i disk0:hfr-infra-test-px i disk0:hfr-upgrade-px i disk0:hfr-fit-px i disk0:hfr-cgn-px i disk0:hfr-mpls-px i disk0:hfr-mcast-px i disk0:hfr-fpd-px i disk0:hfr-fpd-px i disk0:hfr-diags-px i disk0:hfr-diags-px i 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 i Info: disk0:hfr-diags-supp i Info: disk0:hfr-doc-px i Info: disk0:hfr-doc-supp i Info: disk0:hfr-fit-px i Info: disk0:hfr-fit i 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: UTC Install operation 193 '(admin) install commit' started by user 'lab' via CLI at 07:10:38 UTC Wed Oct Install operation 193 completed successfully at 07:10:46 UTC Wed Oct 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 1-13

14 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 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 1-14

15 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 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 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 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. 1-15

16 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 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. Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10 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. 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. Verify activation is successful. Once activation is done and before the install commit operation, deactivate and remove the upgrade-px.pie. After removing the upgrade-px.pie execute the install commit command to commit the newly activated software router(admin)# install commit 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: Clear the NVGEN cache: router# run nvgen -F 1 Create a dummy config commit: router# config router(config)#hostname <hostname> router(config)#commit router(config)#end 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 1-16

17 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 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 Step 2 Obtain the list of inactive packages and note the names of packages that are not needed: router(admin)# show install inactive brief 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) Step 3 Step 4 Using the sync option prevents other users from executing any other command during the install operation. Verify/fix the configuration file system (mandatory) router(admin)#cfs check 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:

18 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 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 document which can be accessed at: 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 Limitations With the Preconfig Interface The MDR (Minimum Disruption Restart) feature is not supported for upgrades to the Cisco IOS XR software T, Cisco IOS XR software 4.0.1, or Cisco IOS XR software releases. 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 1-18

19 Upgrading to Cisco IOS XR Software Release 4.0.X(PX) Before Migrating to Cisco CRS-3 Hardware 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 Step 2 Step 3 Step 4 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 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 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. Make sure system (RP) has available memory. Please refer to the table above with title RP/SP/LC Memory Requirements during Upgrade. 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. 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 Step 5 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.. 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 1-19

20 Cisco CRS-3 Carrier Routing System and CRS-1 Carrier Routing System Hardware Compatibility Matrix Step 6 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. Now perform an install commit command and continue testing the Cisco IOS XR software release 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 on page 1-20 for the new 140G-based Cisco CRS-3 hardware. Table G-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 4 slot chassis MSC-140G FP-140G MC : 16 slot LCC MSC-140G FP-140G 14x10GE 20x10GE 1x100GE 14x10GE 20x10GE 1x100GE 14x10GE 20x10GE 1x100GE Current CRS-1 MSC-140 must NOT be plugged in with CRS-1 Fabric 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] 1-20

21 Information About Refer to Table 1-6 on page 1-21 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 T and higher software. As detailed in the section CRS-1 to CRS-3 Software Migration Compatibility Matrix, page 1-2, a direct IOS-XR upgrade to Release 4.0.X(PX) is available for a router running Cisco IOS XR releases through All IOS-XR Software releases prior to (IOS XR releases 3.4.2, 3.5.3, or 3.6.2) must be 1-21

22 Information About Chapter 1 upgraded to IOS XR software release 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 Appendix A, 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: UTC Cisco IOS XR Software, Version T[Default] Copyright (c) 2010 by Cisco Systems, Inc. ROM: System Bootstrap, Version 1.304( :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 UP UP UP UP UP UP UP UP UP UP UP UP UP UP 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] 1-22

23 How to Migrate to a Cisco CRS-3 Carrier Routing System (16-Slot) 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 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 SUMMARY STEPS 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. 1. admin 1-23