Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.2.2
Feature Set Table for the Cisco CRS-1
Memory Requirements for the Cisco CRS-1
Hardware Supported for the Cisco CRS-1
Software Compatibility for the Cisco CRS-1
Determining the Software Version for the Cisco CRS-1
Other Firmware Code for the Cisco CRS-1
Feature Set Table for the Cisco XR 12000 Series Router
Memory Requirements for the Cisco XR 12000 Series Router
Hardware Supported for the Cisco XR 12000 Series Router
Software Compatibility for the Cisco XR 12000 Series Router
Determining the Software Version for the Cisco XR 12000 Series Router
Other Firmware Code for the Cisco XR 12000 Series Router
New Software Features in Cisco IOS XR Software Release 3.2.2
Changed Software Features in Cisco IOS XR Software Release 3.2.2
Cisco XR 12000 Series Router-specific Caveats
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Appendix A: Software Installation and Upgrade Notes
Information About Software Installation and Upgrade Procedures
Upgrading Cisco IOS XR Software from Release 3.0.1 to 3.2.2 (Cisco CRS-1)
Upgrading Cisco IOS XR Software
Upgrading Cisco IOS XR Software from Release 3.2.0 to 3.2.2 (Cisco CRS-1)
Upgrading Cisco IOS XR Software
Upgrading Cisco IOS XR Software from Release 3.2.1 to 3.2.2 (Cisco CRS-1)
Upgrading Cisco IOS XR Software
Upgrading Cisco IOS XR Software from Release 3.2.0 to 3.2.2 (Cisco XR 12000 Series Router)
Upgrading Cisco IOS XR Software
Upgrading Cisco IOS XR Software from Release 3.2.1 to 3.2.2 (Cisco XR 12000 Series Router)
Required SMUs and SMU Installation Procedure
Upgrading Cisco IOS XR Software
Restoring the Bootflash on RP, LC, and SP Nodes (CRS-1 Only)
Restoring the Bootflash: on the RP Nodes
Restoring the Bootflash: on the LC and SP Nodes
Removing Inactive Packages from the Disk
Appendix B: Upgrading and Downgrading ROM Monitor Software on Cisco CRS-1 Routers
Release Notes for Cisco IOS XR Software Release 3.2.2
November 22, 2005
Cisco IOS XR Software Release 3.2.2
Text Part Number OL-8819-01
Note
See the "Important Notes" section for important information on Cisco IOS XR Software Release 3.2.2.
Note
These release notes describe the features provided in Cisco IOS XR Software Release 3.2.2 and are updated as needed.
For a list of software caveats that apply to Cisco IOS XR Software Release 3.2.2, see the "Caveats" section. The caveats are updated for every release and are located on the World Wide Web at www.cisco.com.
We recommend that you view the field notices for this release to see if your software or hardware platforms are affected, at http://www.cisco.com/public/support/tac/fn_index.html.
Contents
These release notes contain the following sections:
•
•
•
•
•
Introduction
Cisco IOS XR software is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.
Cisco IOS XR software provides the following features and benefits:
•
•
•
•
•
•
•
•
•
•
See the "New and Changed Information" section for a detailed list of new features by platform for Cisco IOS XR Software Release 3.2.2.
System Requirements
The Cisco IOS XR Software Release 3.2.2 is supported on the following platforms:
Cisco CRS-1
This section describes the system requirements for Cisco IOS XR Software Release 3.2.2 supported on Cisco CRS-1 routers and includes the following information:
•
•
•
•
•
•
Feature Set Table for the Cisco CRS-1
Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.2.2 features. Table 1 and Table 2 list the Cisco IOS XR software feature set matrix and associated filenames that are available for the Cisco IOS XR Software Release 3.2.2 that is supported on the Cisco CRS-1.
Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.2.2 PIE Files)
Cisco IOS XR Unicast Routing Core Bundle
comp-hfr-mini.pie-3.2.2
Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, and Routing packages.
Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.2.2
CORBA agent, XML Parser, HTTP server, SNMP Agent, and Alarm correlation.
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.2.2
MPLS-TE, LDP, MPLS-TE Link Management, MPLS Forwarding, Optical Link Management, OUNI, and RSVP.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.2.2
Multicast Routing Protocols (PIM, MSDP, IGMP, Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB, MURIB, MFWD), and BIDIR.
Cisco IOS XR Security Package
hfr-k9sec-p.pie-3.2.2
Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.
1 Packages are installed individually.
Memory Requirements for the Cisco CRS-1
The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR Software Release 3.2.2 are:
•
•
Hardware Supported for the Cisco CRS-1
Cisco IOS XR Software Release 3.2.2 supports Cisco CRS-1 routers. All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements for the Cisco CRS-1" section.
Table 3 lists the hardware components supported on the Cisco CRS-1 and the minimum software versions required. See the "Determining the Software Version for the Cisco CRS-1" section.
Software Compatibility for the Cisco CRS-1
Cisco IOS XR Software Release 3.2.2 is compatible with the Cisco CRS-1 systems:
•
•
Determining the Software Version for the Cisco CRS-1
To determine the version of Cisco IOS XR software running on your router, log in to the router and enter the show version command:
Step 1
Step 2
RP/0/RP0/CPU0:BB01# show versionCisco IOS XR Software, Version 3.2.2[00]Copyright (c) 2005 by cisco Systems, Inc.ROM: System Bootstrap, Version 1.32(20050525:193559) [CRS-1 ROMMON],BB01 uptime is 2 days, 2 hours, 6 minutesSystem image file is "disk0:hfr-os-mbi-3.2.2/mbihfr-rp.vm"cisco CRS-16/S (7455) processor with 4194304K bytes of memory.7455 processor at 800Mhz, Revision 3.418 Packet over SONET network interface(s)1 SRP over SONET network interface(s)20 SONET/SDH Port controller(s)8 TenGigabitEthernet/IEEE 802.3 interface(s)2 Ethernet/IEEE 802.3 interface(s)8 GigabitEthernet/IEEE 802.3 interface(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.1000592k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).62452k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes).Package active on node 0/2/SP:hfr-admin, V 3.2.2[00], Cisco Systems, at disk0:hfr-admin-3.2.2Built on Fri Nov 11 20:16:09 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/hfr/workspace for c2.95.3-p8hfr-base, V 3.2.2[00], Cisco Systems, at disk0:hfr-base-3.2.2Built on Fri Nov 11 20:02:41 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/hfr/workspace for c2.95.3-p8hfr-os-mbi, V 3.2.2[00], Cisco Systems, at disk0:hfr-os-mbi-3.2.2Built on Fri Nov 11 19:10:25 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/hfr/workspace for c2.95.3-p8Package active on node 0/2/CPU0:hfr-mcast, V 3.2.2[00], Cisco Systems, at disk0:hfr-mcast-3.2.2Built on Fri Nov 11 20:56:19 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/hfr/workspace for c2.95.3-p8< snipped rest of lengthy output >
Other Firmware Code for the Cisco CRS-1
The following firmware code is supported by the Cisco CRS-1 router:
•
Note
•
•
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.2.2 supported on the Cisco XR 12000 Series Router and includes the following information:
•
•
•
•
•
•
Feature Set Table for the Cisco XR 12000 Series Router
The Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.2.2 features. Table 4 and Table 5 list the Cisco IOS XR software feature set matrix and associated filenames available for Cisco IOS XR Software Release 3.2.2 supported on the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Sets (Cisco IOS XR Software Release 3.2.2 PIE Files)
Cisco IOS XR Unicast Routing Core Bundle
c12k-mini.vm-3.2.2
Contains the required core packages including, OS, Admin, Base, Forwarding, Line Cards, and Routing packages.
Cisco IOS XR Manageability Package
c12k-mgbl.pie-3.2.2
CORBA agent, XML Parser, HTTP server, SNMP Agent, and Alarm correlation.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.2.2
MPLS-TE, LDP, MPLS-TE Link Management, MPLS Forwarding and RSVP.
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.2.2
Multicast Routing Protocols (PIM, MSDP, IGMP, Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB, MURIB, MFWD).
Cisco IOS XR Security Package
c12k-k9sec.pie-3.2.2
Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.
Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.2.2
Support for booting the standby RP on a Cisco XR 12000 (PRP).
1 Packages are installed individually.
Memory Requirements for the Cisco XR 12000 Series Router
The minimum memory requirements for Cisco XR 12000 Series Router routers running Cisco IOS XR Software Release 3.2.2 are:
•
•
•
Hardware Supported for the Cisco XR 12000 Series Router
Cisco IOS XR Software Release 3.2.2 supports the Cisco XR 12000 Series Router. All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements for the Cisco XR 12000 Series Router" section.
Table 6 lists the hardware components supported on the Cisco XR 12000 Series Router and the minimum software versions required. See the "Determining the Software Version for the Cisco XR 12000 Series Router" section.
Software Compatibility for the Cisco XR 12000 Series Router
Cisco IOS XR Software Release 3.2.2 is compatible with the Cisco XR 12000 Series Router systems:
•
•
•
•
For the existing installed base, the following chassis are supported:
•
•
Determining the Software Version for the Cisco XR 12000 Series Router
To determine the version of Cisco IOS XR software running on your router, log in to the router and enter the show version command:
Step 1
Step 2
RP/0/0/CPU0:AR04# show versionCisco IOS XR Software, Version 3.2.2[00]Copyright (c) 2005 by cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20040624:164256) [assafb-misc1 1.14dev(0.91)] DEVELOPMENT SOFTWARECopyright (, Inc.BOOTFLASH: GS Software (C12KPRP-BOOT-M), Version 12.0(nightly.S050516) NIGHTLY BUILD, synced to conn isp V120 30 4 SAR04 uptime is 2 days, 2 hours, 8 minutesSystem image file is "compactflash:c12k-os-mbi-3.2.2/mbiprp-rp.vm"cisco 12410/PRP (7457) processor with 2097152K bytes of memory.7457 processor at 1265Mhz, Revision 1.12 Cisco 12000 Series Performance Route Processors1 Cisco 12000 4 Port Gigabit Ethernet Controller (4 GigabitEthernet)1 16 port ISE OC3 channelized DS3/E3 Controller (16 POS)2 1 Port ISE Packet Over SONET OC-48c/STM-16 Controllers (2 POS)18 Packet over SONET network interface(s)18 SONET/SDH Port controller(s)1 PLIM QoS controller(s)6 Ethernet/IEEE 802.3 interface(s)4 GigabitEthernet/IEEE 802.3 interface(s)2042k bytes of non-volatile configuration memory.975M bytes of compact flash card.38145M bytes of hard disk.62452k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).62452k bytes of ATA PCMCIA card at disk 1 (Sector size 512 bytes).65536k bytes of Flash internal SIMM (Sector size 256k).Configuration register on node 0/0/CPU0 is 0x102Package active on node 0/0/CPU0:c12k-mgbl, V 3.2.2[00], Cisco Systems, at compactflash:c12k-mgbl-3.2.2Built on Fri Nov 11 22:16:29 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/prp/workspace for c2.95.3-p8c12k-mcast, V 3.2.2[00], Cisco Systems, at compactflash:c12k-mcast-3.2.2Built on Fri Nov 11 22:16:04 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/prp/workspace for c2.95.3-p8c12k-mpls, V 3.2.2[00], Cisco Systems, at compactflash:c12k-mpls-3.2.2Built on Fri Nov 11 22:15:35 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/prp/workspace for c2.95.3-p8c12k-rout, V 3.2.2[00], Cisco Systems, at compactflash:c12k-rout-3.2.2Built on Fri Nov 11 23:17:09 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/prp/workspace for c2.95.3-p8c12k-k9sec, V 3.2.2[00], Cisco Systems, at compactflash:c12k-k9sec-3.2.2Built on Fri Nov 11 22:16:47 PST 2005By edde-bld1 in /vws/afz/production/3.2.2/prp/workspace for c2.95.3-p8< snipped rest of lengthy output >
Other Firmware Code for the Cisco XR 12000 Series Router
The following firmware code is supported by the Cisco XR 12000 Series Router:
•
•
New and Changed Information
The following sections contain information on new features in Cisco IOS XR Software Release 3.2.2:
•
•
New Software Features in Cisco IOS XR Software Release 3.2.2
The following new features in Cisco IOS XR Software Release 3.2.2 are supported on the Cisco CRS-1 and Cisco XR 12000 Series Router platforms:
•
For more information, see the Cisco IOS XR Interface and Hardware Component Configuration Guide, Release 3.2 and the Cisco IOS XR Interface and Hardware Component Command Reference, Release 3.2.
•
•
For more information, see the Cisco IOS XR Routing Configuration Guide, Release 3.2 and the Cisco IOS XR Routing Command Reference, Release 3.2.
•
•
For more information, see the Cisco IOS XR Routing Configuration Guide, Release 3.2 and the Cisco IOS XR Routing Command Reference, Release 3.2.
Changed Software Features in Cisco IOS XR Software Release 3.2.2
No software feature changes to report in Cisco IOS XR software Release 3.2.2.
Important Notes
In certain countries, use of these products may be prohibited and subject to laws, regulations, or licenses, including requirements applicable to the use of the products under telecommunications and other laws and regulations; customers must comply with all such applicable laws in the countries in which they intend to use the products.
When upgrading a Cisco XR 12000 Series Router from Cisco IOS to Cisco IOS XR software, follow the upgrade instructions provided to minimize traffic impact. For detailed instructions, see the Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco 12000 Series Router, Release 3.2 document for procedures.
Follow the instructions provided by Cisco for all card removal and replacement (fabric cards, LC, fan controller and RP, and so on) to avoid impact to traffic. See the Cisco IOS XR Getting Started Guide for procedures.
If you intend to test beyond combined maximum configuration tested and published by Cisco, contact your Cisco representative to discuss how to engineer a large-scale configuration maximum for your testing.
The Cisco SIP-600 line cards draw more power than previous line cards. Depending on the exact configuration of power entry modules (PEMs) and other cards in the chassis, there may not be enough power available when inserting a new card or removing a PEM. The admin command show environment power-supply table helps plan the power budget for the chassis. Before inserting a new card (of any type, not just a line card) or removing a PEM, run the following commands:
RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)#show env power-supply table48V Current R/S/I Module (V) (A) 0/24/* PEM1 46 12 PEM2 47 10 0/25/* PEM1 47 12 PEM2 47 10Total Power Supplies: 4800W Redundant Power Supplies: 2400W Worst Case Power Used: 1559W Current Power Used: 1022W Current Redundant Power Available: 1378W Current Total Power Available: 3778W Worst Case Redundant Power Available: 841W Worst Case Total Power Available: 3241WPID Description Watts --- ----------- ----- GRP-B Route Processor 38 PRP-1 Cisco 12000 Series Performance Route Processor 60 LC-4OC-3-POS-SM 4 Port Packet Over SONET OC-3c/STM-1 80 4OC3X/POS-MM-MJ-B 4 port ISE OC3 90 8OC3/POS-SM 8 Port Packet Over SONET OC-3c/STM-1 100 8OC3X/POS-MM-MJ-B 8 port ISE OC3 105 16OC3/POS-SM 16 Port Packet Over SONET OC-3c/STM-1 100 16OC3X/POS-M-MJ-B 16 port ISE OC3 channelized DS3/E3 140 LC-1OC12/POS-SM 1 Port OC12/STM4 Packet Over SONET/SDH Line Card 80 EOS. 4 Port E.D. Packet Over SONET OC-12c/STM-4 100 4OC12/POS-IR-SC-B 4 Port Packet Over SONET OC-12c/STM-4 100 4OC12X/POS-M-SC-B 4 Port ISE Packet Over SONET OC-12c/STM-4 140 EOS. 1 Port E.D. Packet Over SONET OC-48c/STM-16 80 OC48E/POS-SR-SC-B 1 Port Packet Over SONET OC-48c/STM-16 78 OC48X/POS-LR-SC 1 Port ISE Packet Over SONET OC-48c/STM-16 140 OC192/POS-VSR 1 Port Packet Over SONET OC-192c/STM-64 174 LC-OC12-DS3 1 port SONET OC12 channelized to DS3 80 CHOC-12/STS3-IR-SC 1 port SONET OC12 channelized to STS3/STM-1 80 4CHOC12/DS3-IR-SC-B 4 port ISE OC12 channelized STS-3c/STM-1 or DS3/E3 140 CHOC48/DS3-IR-SC 1 port ISE OC48 channelized STS-12c/STM-4, STS-.. 140 6DS3-SMB-B 6 Port Packet over DS3 80 12DS3-SMB-B 12 Port Packet over DS3 80 4OC3/ATM-SM-SC 4 port ATM Over SONET OC-3c/STM-1 70 LC-1OC12/ATM-SM 1 port ATM Over SONET OC12c/STM-4c 62 4OC12/ATM-IR-SC 4 port ATM Over SONET OC12c/STM-4c 122 8FE-FX-SC-B 8 Port Fast Ethernet 77 GE-GBIC-SC-B 1 Port Gigabit Ethernet 65 3GE-GBIC-SC Cisco 12000 3 port Gigabit Ethernet 71 4GE-SFP-LC Cisco 12000 4 Port Gigabit Ethernet 106 OC12/SRP-IR-SC-B 1 Port SONET based SRP OC-12c/STM-4 80 OC48/SRP-LR-SC 1 Port SONET based SRP OC-48c/STM-16 100 12000-SIP-600 Cisco 12000 Series SPA Interface Processor-600 256 GSR04-FABRIC GSR 12404 Consolidated Fabric/Alarm Card 143 GSR6-CSC GSR 12406 Clock Scheduler Card 56 GSR6-SFC GSR 12406 Switch Fabric Card 45 GSR10-CSC GSR 12410 Clock Scheduler Card 19 GSR10-SFC GSR 12410 Switch Fabric Card 64 CSC-160,GSR12810 Clock Scheduler Card(10) OC-768 54 SFC-160,GSR12810 Switch Fabric Card(10) OC-768 107 GSR16/80-CSC Cisco 12016 80 Gbps GSR Clock Scheduler Card 43 GSR16/80-SFC Cisco 12016 80 Gbps GSR Switch Fabric Card 35 GSR16/320-CSC Cisco 12416 320 Gbps GSR Clock Scheduler Card 106 GSR16/320-SFC Cisco 12416 320 Gbps Switch Fabric Card 93 CSC-256,GSR12816 Clock Scheduler Card(16) OC-768 177 SFC-256,GSR12816 Switch Fabric Card(16) OC-768 151 GSR04-FABRIC Alarm Board(404) 208 GSR6-ALRM GSR 12406 Alarm Module 26 GSR10-ALRM GSR 12410 Alarm Module 33 GSR16-ALRM Cisco 12016 Alarm Module 35 GSR6-BLOWER GSR 12406 Blower Module 178 GSR16-BLOWER GSR 12016 Blower Module 178 Bus Board(16) 20 RP/0/0/CPU0:c12k#If you plan to insert a new card, locate the entry for the card to be inserted and note the power consumed by it. If this power is less than the figure given in Worst Case Redundant Power Available (the figure is displayed in the show environment power-supply table command output), the card can be safely inserted. As long as the Worst Case Redundant Power Available is not zero, a PEM can be powered down for replacement without impact.
Note
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. The following sections include both resolved and open relevant caveats.
Resolved Caveats
This following caveats from prior releases were resolved in Cisco IOS XR Software Release 3.2.2.
•
Basic Description: The rommon unhang sequence on the CRS-16 Fan Controller card does not cover the fan tray EEPROM. This fix is to add that device to the unhang list.
Symptoms: There are two symptoms, as follows:
–
–
Conditions: While the i2c_server process on Fan Controller is doing a routine I2C transaction to the fan tray EEPROM, the Fan Controller card was reloaded for some reason (say, due to an install operation that required the card reload), leaving an I2C transaction incomplete. The next time IOX came back after the reload, the first I2C access to the fan tray EEPROM caused the hang.
Workaround: Recovery mechanisms are possible in the previous scenario, as follows:
–
–
•
Basic Description: Entries in the MPLS Label Forwarding Information Base (LFIB) may be incorrect.
Symptom: Forwarding over TE tunnels may stop.
Conditions: This symptom is observed following a route processor (RP) switchover on a Cisco router that has many BGP/IGP routes and thousands of MPLS TE tunnels.
Workaround: Restart the MPLS TE control plane process with "process restart te_control".
•
Basic Description: Various failure scenarios in the control plane of an IPv6 enabled router that would result in disruptions to data forwarding. OSPF configuration is needed to support controlling the multicast-intact feature.
Symptom: Disruptions to data forwarding.
Conditions: Various failure scenarios in the control plane of an IPv6-enabled router.
Workaround: OSPF configuration is needed to support controlling the multicast-intact feature.
Open Caveats—Release 3.2.2
This section lists the open caveats for Cisco IOS XR Software Release 3.2.2. The caveats are organized as follows:
•
Platform-Independent Caveats
The following caveats apply to all platforms:
•
Brief Description: Internally found cosmetic defect: Assigned (A) % complete during the install add command is inaccurate.
Symptoms: During the install add command operations, there may be a window of 4-5 minutes in which no add operation status is displayed on the user's terminal or console.
Conditions: This occurs only when performing the install add command operations.
Workaroud: No workaround. Note that this does not impact the add operation. The user should wait for the next install % (percentage) message to see the status of the install add command operations.
•
Basic Description: IPv6 ping fails to link-local address.
Symptom: An error "ping6: failed to get receiving hop limit" is displayed and IPv6 ping to a directly connected neighbor's link-local address is not successful. IPv6 ping to the interface is successful.
Conditions: This symptom occurs on Cisco routers with 3.2.2 Cisco IOS XR software configured with IPv6.
Workaround: No workarounds.
•
Basic Description: Removing and restoring configuration of address family can cause a BGP peer to remain down.
Symptom: IPv4 BGP neighbors do not come up after Address Family Identifier configuration is restored.
Conditions: If the address-family ipv4 is restored (for example, with rollback configuration) under router BGP approximately three minutes after the configuration was removed, the IPv4 BGP neighbors do not come back up.
Workaround: Restart the bgp process on the RP by using process restart bgp command.
•
Basic Description: An Optical User Network Interface (OUNI) connection goes down a few minutes after the Resource Reservation Protocol (RSVP) hellos come back up.
Symptom: On an RSVP hello control-channel failure, an OUNI connection may go down.
Conditions: The OUNI connection goes down if the control channel failure is detected by the passive side of the OUNI connection. This is because the passive side of the OUNI connection stops refreshing its RSVP state for the OUNI connection, and the active side eventually times out.
Workaround: After the RSVP hello control-channel failure on the passive side restart the RSVP process with process restart rsvp command.
Cisco CRS-1-specific Caveats
The following caveats are specific to the Cisco CRS-1 platform:
•
Basic Description: On Cisco CRS-1 single-shelf chassis, the show hfr command shows UNKNOWN entry after multiple AM0/AM1 card OIRs.
Symptom: After performing more than 15-20 OIRs of the alarm card while it is in various stages of booting, show hfr command shows an UNKNOWN entry.
Conditions: On a Cisco CRS-1 single-shelf chassis, if we do more than 15-20 OIRs of AM0 or AM1 while these nodes are booting (that is, in MBI-BOOT or MBI-RUN state), an UNKNOWN entry may eventually show up in the output of the show hfr command.
Workaround: The process restart invmgr command fixes this problem.
•
Basic Description: Following a SPA OIR operation, an error may be encountered which results in subsequent packet loss. This can be corrected by restarting the affected SPA.
Symptom: The following error message is reported: %L2-BAMBI-3-ASIC_ERR : plaspa instance 0 L2P UIDB Multi, check uidb hash table. Data arriving on the affected SPA is dropped.
Conditions: This symption is observed on Cisco CRS-1 routers Shared Port Adapters (SPA) during Online Insertion and Removal (OIR).
Workaround: Consider the following workaround:
–
–
–
Cisco XR 12000 Series Router-specific Caveats
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
Basic Description: TURBOBOOT (cold boot) procedure with the -clean option cleans all files on the boot disk (disk0:) of all non-DSC RPs.
Symptom: The TURBOBOOT procedure used with the -clean option cleans only the package files on the boot disk (typically disk0:) on the DSC. However on all other RPs in the system, all files on the boot disk are deleted (including any user or configuration files).
The configuration for non-owner LRs is stored on the boot device of the RPs of those LRs (not the DSC). If a turboboot is issued with the -clean option when LRs are carved out, this has the effect of deleting the configuration on any non-owner LRs.
Conditions: All package and user files on disk0: are deleted when TURBOBOOT starts on the non-DSC RPs.
Workaround: The user should back up any configuration for non-owner LRs before starting the turboboot and re-apply this configuration manually when the turboboot has finished. Also, any other user files on the disk of any RP should be backed up before starting the turboboot.
•
Brief Description: Class or mark policy counters multiply depending on the number of match criteria.
Symptom: When a QoS policy uses a class map that classifies traffic based on a number of match-any criteria and this policy is applied to an interface in ingress or egress direction, the show policy map command counters can increment in the multiples of the number of match criteria.
Conditions: This condition is observed on the Cisco XR 12000 Series Router using QoS configurations involving class maps with multiple match criteria.
Workaround: No workaround.
•
Brief Description: Configuring APS in a router-to-router configuration may result in a PGP failure.
Symptom: Adding a working group and a protect group in a two-router topology may result in a PGP "no contact" failure between the newly configured groups.
Condition: The ipv4_rib_best_local_address command is returning 0 to aps.
Workaround: Remove the APS group configuration, followed by re-applying the configuration.
Troubleshooting
Refer to the Cisco IOS XR Getting Started Guide for information on troubleshooting the Cisco IOS XR software.
Related Documentation
The following sections describe the documentation available for the Cisco CRS-1 and Cisco XR 12000 Series Router. These documents consist of hardware and software installation guides, Cisco IOS XR software configuration and command references, feature modules, and other documents.
Documentation is available as electronic documents, which are available online on Cisco.com.
Use these release notes with these documents:
Hardware Documents
You can find the most current hardware documentation at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/core/crs/index.htm
Software Documents
The Cisco IOS XR software documentation set consists of the Cisco IOS XR software configuration guides and command references, a getting started guide, and other supporting documents. Refer to the About Cisco IOS XR Software Documentation for Release 3.2 for a list of Cisco IOS XR software documentation for Release 3.2.2.
You can find the most current software documentation at the following URL:
http://www.cisco.com/univercd/cc/td/doc/product/core/crs/index.htm
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have PDF versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•
•
•
A current list of security advisories and notices for Cisco products is available at this URL:
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•
In an emergency, you can also reach PSIRT by telephone:
•
•
Tip
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•
http://www.cisco.com/go/marketplace/
•
•
•
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•
•
http://www.cisco.com/en/US/products/index.html
•
http://www.cisco.com/discuss/networking
•
http://www.cisco.com/en/US/learning/index.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Copyright © 2005 Cisco Systems, Inc. All rights reserved
Appendix A: Software Installation and Upgrade Notes
This appendix describes how to upgrade or downgrade the ROM Monitor software on a Cisco CRS-1.
Contents
•
•
•
•
•
•
•
Information About Software Installation and Upgrade Procedures
Cisco IOS XR software is installed and activated as modular packages, allowing specific features or software patches to be installed, upgraded, or downgraded without impacting unrelated processes. In addition, a software package can be upgraded or downgraded on all supported card types. Cisco IOS XR software packages are installed from package installation envelopes (PIE) files that contain one or more software components.
Use the procedures in Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco 12000 Series Router, Release 3.2 to upgrade a Cisco XR 12000 Series Router from Cisco IOS software 12.0(31)Sa to Cisco IOS XR Software Release 3.2.2.
Note
Cisco IOS XR Getting Started Guide.Before performing an upgrade, perform the following tasks:
•
•
•
Note
RP/0/RP0/CPU0:router# copy running-config harddisk:/destination•
•
RP/0/RP0/CPU0:router(admin)# show install rollback ?•
RP/0/RP0/CPU0:router(admin)# copy bootflash:/source harddisk:/destination
Note
RP/0/RP0/CPU0:CRS#admin
RP/0/RP0/CPU0:CRS(admin)#The following sections provide special instructions for upgrading Cisco IOS XR software on your router.
Verifying System Stability
Before upgrading the software on a Cisco CRS-1 or Cisco XR 12000 Series Router, use the following commands to verify basic system stability before the upgrade:
•
•
•
•
Note
For more information on the show ipv4 interface brief and show ipv6 interface brief commands, refer to the Cisco IOS XR IP Addresses and Services Command Reference.
For more information on the show install active command, refer to the Cisco IOS XR System Management Command Reference.
Upgrading Cisco IOS XR Software from Release 3.0.1 to 3.2.2 (Cisco CRS-1)
This section provides instructions for upgrading Cisco IOS XR software from Release 3.0.1 to
Release 3.2.2 on a Cisco CRS-1.This section covers the following topics:
•
Required Packages
The following packages are required for upgrading IOS XR software from Release 3.0.1 to Release 3.2.2 on Cisco CRS-1.
Note
Installing the Required SMU
Table 8 describes the SMU required to perform the upgrade from Release 3.0.1 to Release 3.2.2 on a Cisco CRS-1.
Use the following procedure to install the SMU on the Cisco CRS-1:
Step 1
RP/0/RP0/CPU0:router# install add <device or tftp:/ftp:/rcp:>/hfr-admin-3.0.1.CSCeh04631.pie to disk0:Step 2
RP/0/RP0/CPU0:router# install activate disk0:hfr-admin-3.0.1.CSCeh04631-1.0.0Step 3
RP/0/RP0/CPU0:router# install commit
Pre-Upgrade Checks
Before performing an upgrade, perform the following pre-upgrade checks on the Cisco CRS-1:
Step 1
Step 2
Step 3
RP/0/RP0/CPU0:router# copy running-config storage_deviceStep 4
RP/0/RP0/CPU0:router# show install rollback ?Step 5
Step 6
RP/0/RP0/CPU0:router# copy bootflash:/source harddisk:/destination
Note
Upgrading Cisco IOS XR Software
Use the following procedure to upgrade the Cisco IOS XR software from Release 3.0.1 to Release 3.2.2 on a Cisco CRS-1:
Step 1
RP/0/RP0/CPU0:router# install add <device or tftp/ftp/rcp>/PIE_filename to disk0: sync
Note
RP/0/RP0/CPU0:router# install add <device or tftp/ftp/rcp>/comp-hfr-mini.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mcast.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mgbl-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mpls-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-k9sec-p.pie-3.2.2 to disk0: sync
Note
Step 2
RP/0/RP0/CPU0:router# install activate disk0:comp-hfr-mini-3.2.2 disk0:hfr-mcast-3.2.2 disk0:hfr-mgbl-3.2.2 disk0:hfr-k9sec-3.2.2 disk0:hfr-mpls-3.2.2 sync
Note
Note
Note
Note
Step 3
Step 4
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# install commit
Note
Step 5
RP/0/RP0/CPU0:router# format bootflash: location RP_locationRP/0/RP0/CPU0:router# dir bootflash: location RP_locationRP/0/RP0/CPU0:router# format bootflash: location Standby_RP_locationRP/0/RP0/CPU0:router# dir bootflash: location Standby_RP_locationStep 6
RP/0/RP0/CPU0:router(admin)# copy harddisk:/source bootflash:/destination
Upgrading Cisco IOS XR Software from Release 3.2.0 to 3.2.2 (Cisco CRS-1)
This section provides instructions for upgrading Cisco IOS XR software from Release 3.2.0 to Release 3.2.2 on a Cisco CRS-1.
This section covers the following topics:
•
Required Packages
The following packages are required for upgrading IOS XR software from Release 3.2.0 to Release 3.2.2 on Cisco CRS-1.
Note
Installing the Required SMU
Table 10 describes the SMU required to perform the upgrade from Release 3.2.0 to Release 3.2.2 on a Cisco CRS-1.
Use the following procedure to install the SMU on the Cisco CRS-1:
Step 1
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)#Step 2
RP/0/RP0/CPU0:router(admin)# install add <device or tftp:/ftp:/rcp:>/hfr-base-3.2.0.CSCei45039.pie to disk0:Step 3
RP/0/RP0/CPU0:router(admin)# install activate disk0:hfr-base-3.2.0.CSCei45039-1.0.0Step 4
RP/0/RP0/CPU0:router(admin)# exitRP/0/RP0/CPU0:router#Step 5
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# hostname current_hostnameRP/0/RP0/CPU0:router(config)# commitRP/0/RP0/CPU0:router(config)# exitStep 6
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# install commit
Pre-Upgrade Checks
Before performing an upgrade, perform the following pre-upgrade checks on the Cisco CRS-1:
Step 1
Step 2
Step 3
RP/0/RP0/CPU0:router# copy running-config locationStep 4
RP/0/RP0/CPU0:router(admin)# show install rollback ?Step 5
Upgrading Cisco IOS XR Software
Use the following procedure to upgrade the Cisco IOS XR software from Release 3.2.0 to Release 3.2.2 on a Cisco CRS-1.
Step 1
RP/0/RP0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/PIE_file_name to disk0: sync
Note
RP/0/RP0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/comp-hfr-mini.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mcast-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mgbl-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mpls-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-k9sec-p.pie-3.2.2 to disk0: sync
Note
Step 2
RP/0/RP0/CPU0:router(admin)# install activate disk0:comp-hfr-mini-3.2.2 disk0:hfr-mcast-3.2.2 disk0:hfr-mgbl-3.2.2 disk0:hfr-k9sec-3.2.2 disk0:hfr-mpls-3.2.2 sync
Note
Note
Note
Note
Step 3
Step 4
RP/0/RP0/CPU0:router(admin)# install commit
Upgrading Cisco IOS XR Software from Release 3.2.1 to 3.2.2 (Cisco CRS-1)
This section provides instructions for upgrading Cisco IOS XR software from Release 3.2.1 to Release 3.2.2 on a Cisco CRS-1.
This section covers the following topics:
•
Required Packages
The following packages are required for upgrading IOS XR software from Release 3.2.1 to Release 3.2.2 on Cisco CRS-1.
Note
Installing the Required SMU
No SMUs are required for this installation.
Pre-Upgrade Checks
Before performing an upgrade, perform the following pre-upgrade checks on the Cisco CRS-1:
Step 1
Step 2
Step 3
RP/0/RP0/CPU0:router# copy running-config locationStep 4
RP/0/RP0/CPU0:router(admin)# show install rollback ?
Upgrading Cisco IOS XR Software
Use the following procedure to upgrade the Cisco IOS XR software from Release 3.2.1 to Release 3.2.2 on a Cisco CRS-1:
Step 1
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)#Step 2
RP/0/RP0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/PIE_filename to disk0: sync
Note
RP/0/RP0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/comp-hfr-mini.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mcast-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mgbl-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-mpls-p.pie-3.2.2 <device or tftp/ftp/rcp>/hfr-k9sec-p.pie-3.2.2 to disk0: sync
Note
Step 3
RP/0/RP0/CPU0:router(admin)# install activate disk0:comp-hfr-mini-3.2.2 disk0:hfr-mcast-3.2.2 disk0:hfr-mgbl-3.2.2 disk0:hfr-k9sec-3.2.2 disk0:hfr-mpls-3.2.2 sync
Note
Note
Note
Note
Step 4
Step 5
RP/0/RP0/CPU0:router(admin)# install commit
Upgrading Cisco IOS XR Software from Release 3.2.0 to 3.2.2 (Cisco XR 12000 Series Router)
This section provides instructions for upgrading Cisco IOS XR software from Release 3.2.0 to
Release 3.2.2 on a Cisco XR 12000 Series Router.This section covers the following topics:
•
Required Packages
The following packages are required for upgrading IOS XR software from Release 3.2.0 to Release 3.2.2 on Cisco XR 12000 Series Router.
Note
Installing the Required SMU
Table 13 describes the SMU required to perform the upgrade from Release 3.2.0 to Release 3.2.2 on a Cisco XR 12000 Series Router.
Use the following procedure to install the SMU on the Cisco XR 12000 Series Router:
Step 1
RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)#Step 2
RP/0/0/CPU0:router(admin)# install add <device or tftp:/ftp:/rcp:>/c12k-base-3.2.0.CSCei45039.pie to disk0:Step 3
RP/0/0/CPU0:router(admin)# install activate disk0:c12k-base-3.2.0.CSCei45039-1.0.0Step 4
RP/0/0/CPU0:router(admin)# exitRP/0/0/CPU0:router#Step 5
RP/0/0/CPU0:router# configureRP/0/0/CPU0:router(config)# hostname current_hostnameRP/0/0/CPU0:router(config)# commitRP/0/0/CPU0:router(config)# exitStep 6
RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# install commit
Pre-Upgrade Checks
Before performing an upgrade, perform the following pre-upgrade checks on the Cisco XR 12000 Series Router:
Step 1
Step 2
RP/0/0/CPU0:router# copy running-config tftp://host/dir/filenameStep 3
RP/0/0/CPU0:router(admin)# show install rollback ?Step 4
Upgrading Cisco IOS XR Software
Use the following procedure to upgrade the Cisco IOS XR software from Release 3.0.1 to Release 3.2.2 on Cisco XR 12000 Series Router:
Step 1
RP/0/0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/PIE_file_name to disk0: sync
Note
RP/0/0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/c12k-mini.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-mcast.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-mgbl.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-mpls.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-k9sec.pie-3.2.2 to disk0: sync
Note
Step 2
RP/0/0/CPU0:router(admin)# install activate disk0:package_name_or_alias> disk0:package_name_or_alias> <..> sync
Note
Note
Note
Step 3
Step 4
RP/0/0/CPU0:router(config)# adminRP/0/0/CPU0:router(admin)# install commit
Upgrading Cisco IOS XR Software from Release 3.2.1 to 3.2.2 (Cisco XR 12000 Series Router)
This section provides instructions for upgrading Cisco IOS XR software from Release 3.2.1 to
Release 3.2.2 on a Cisco XR 12000 Series Router.This section covers the following topics:
•
•
Required Packages
The following packages are required for upgrading IOS XR software from Release 3.2.1 to Release 3.2.2 on Cisco XR 12000 Series Router.
Note
Required SMUs and SMU Installation Procedure
No SMUs are required for this installation.
Pre-Upgrade Checks
Before performing an upgrade, perform the following pre-upgrade checks on the Cisco XR 12000 Series Router:
Step 1
Step 2
RP/0/0/CPU0:router# copy running-config tftp://host/dir/filenameStep 3
RP/0/0/CPU0:router(admin)# show install rollback ?Step 4
Upgrading Cisco IOS XR Software
Use the following procedure to upgrade the software from Release 3.2.1 to Release 3.2.2 on a Cisco XR 12000 Series Router.
Step 1
RP/0/0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/PIE_file_name to disk0: sync
Note
RP/0/0/CPU0:router(admin)# install add <device or tftp/ftp/rcp>/c12k-mini.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-mcast.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-mgbl.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-mpls.pie-3.2.2 <device or tftp/ftp/rcp>/c12k-k9sec.pie-3.2.2 to disk0: sync
Note
Step 2
RP/0/0/CPU0:router(admin)# install activate disk0:<device or tftp/ftp/rcp package_name_or_alias> disk0:package_name_or_alias <..> sync
Note
Note
Note
Step 3
Step 4
RP/0/0/CPU0:router# adminRP/0/0/CPU0:router(admin)# install commit
Downgrade Procedure
Each install activate, deactivate, or commit operation automatically creates a rollback point, so that a software configuration can be reverted to a previous software configuration. Use the following procedure to downgrade Cisco IOS XR software to a previous rollback point.
Note
Note
Note
Step 1
RP/0/RP0/CPU0:router# adminStep 2
RP/0/RP0/CPU0:router#(admin)# show install rollback ?Step 3
RP/0/RP0/CPU0:router#(admin)# show install rollback point-id
Note
Step 4
RP/0/RP0/CPU0:router(admin)# install rollback point-id sync
Note
Based on the set of packages being activated and deactivated as part of the rollback operation, one or more nodes may be reloaded. This operation could take some time.
If you are downgrading from 3.2.2 to 3.0.1 version of Cisco IOS XR software, use the procedure in the "Restoring the Bootflash on RP, LC, and SP Nodes (CRS-1 Only)" section that follows to restore the bootflash on RP, LC, and SP nodes.
Restoring the Bootflash on RP, LC, and SP Nodes (CRS-1 Only)
To ensure that a router comes up as quickly as possible after a reload, reformat the bootflash: on the RP, LC, and SP nodes that are present in the router. The following sections describe how to restore the bootflashes on RP, LC, and SP nodes:
•
•
Restoring the Bootflash: on the RP Nodes
Use the following procedure to restore the boot flashes on RP nodes.
Note
Step 1
RP/0/RP0/CPU0:router# format bootflash: location node-idStep 2
RP/0/RP0/CPU0:router# dir bootflash: location node-idStep 3
Step 4
RP/0/RP0/CPU0:router# copy harddisk:/source bootflash:/destination
Restoring the Bootflash: on the LC and SP Nodes
Use the following procedure to restore the bootflash: on the LC and SP nodes.
After they have been downgraded, the LC and SP nodes run from memory due to the boot flash migration to Version 3 during the upgrade process. You need to manually downgrade the LC and SP nodes to restore proper operation.
Step 1
RP/0/RP0/CPU0:router# show platformStep 2
RP/0/RP0/CPU0:router# format bootflash location node-id forceStep 3
RP/0/RP0/CPU0:router# dir bootflash: location node-idStep 4
RP/0/RP0/CPU0:router# hw-module node node-id reloadThe node downloads all packages that it must its bootflash:, and then the node resets itself. At this point, the node boots from the software package on its local bootflash.
Step 5
Step 6
Removing Inactive Packages from the Disk
Once a software upgrade or downgrade is complete, you can clear space on a disk by removing any inactive packages that are not needed any more. Use the following procedure to remove unnecessary inactive packages:
Step 1
RP/0/RP0/CPU0:router# adminStep 2
RP/0/RP0/CPU0:router(admin)# show install inactive briefStep 3
RP/0/RP0/CPU0:router(admin)# install remove disk0:package sync
Note
Note
RP/0/RP0/CPU0:router(admin)# install remove disk0:package1 disk0:package2 disk0:package3 syncAppendix B: Upgrading and Downgrading ROM Monitor Software on Cisco CRS-1 Routers
This appendix describes how to upgrade the ROM Monitor software on a Cisco CRS-1.
Follow these steps:
Step 1
http://www.cisco.com/pcgi-bin/tablebuild.pl/crs1rommonStep 2
RP/0/RP0/Router# dir disk0:/*.binDirectory of disk0:65920 -rwx 360464 Fri Oct 28 12:58:02 2005 rommon-hfr-ppc7450-sc-dsmp-A.bin66112 -rwx 360464 Fri Oct 28 12:58:03 2005 rommon-hfr-ppc7450-sc-dsmp-B.bin66240 -rwx 376848 Fri Oct 28 12:58:05 2005 rommon-hfr-ppc7455-asmp-A.bin66368 -rwx 376848 Fri Oct 28 12:58:06 2005 rommon-hfr-ppc7455-asmp-B.bin66976 -rwx 253904 Fri Oct 28 12:58:08 2005 rommon-hfr-ppc8255-sp-A.bin67104 -rwx 253492 Fri Oct 28 12:58:08 2005 rommon-hfr-ppc8255-sp-B.binStep 3
RP/0/RP0/CPU0:ROUTER(admin)# show diag | inc ROM|NODE|PLIMNODE 0/0/SP : MSC(SP)ROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]PLIM 0/0/CPU0 : 4OC192-POS/DPTROMMON: Version 1.19b(20050216:033559) [CRS-1 ROMMON]NODE 0/2/SP : MSC(SP)ROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]PLIM 0/2/CPU0 : 8-10GbEROMMON: Version 1.19b(20050216:033559) [CRS-1 ROMMON]NODE 0/4/SP : Unknown Card TypeNODE 0/6/SP : MSC(SP)ROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]PLIM 0/6/CPU0 : 16OC48-POS/DPTROMMON: Version 1.19b(20050216:033559) [CRS-1 ROMMON]NODE 0/RP0/CPU0 : RPROMMON: Version 1.19b(20050216:033559) [CRS-1 ROMMON]NODE 0/RP1/CPU0 : RPROMMON: Version 1.19b(20050216:033559) [CRS-1 ROMMON]NODE 0/SM0/SP : FC/SROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]NODE 0/SM1/SP : FC/SROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]NODE 0/SM2/SP : FC/SROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]NODE 0/SM3/SP : FC/SROMMON: Version 1.19b(20050216:033352) [CRS-1 ROMMON]Step 4
RP/0/RP0/CPU0:ROUTER# adminRP/0/RP0/CPU0:ROUTER(admin)# upgrade rommon a all disk0Please do not power cycle, reload the router or reset any nodes untilall upgrades are completed.Please check the syslog to make sure that all nodes are upgraded successfully.If you need to perform multiple upgrades, please wait for current upgradeto be completed before proceeding to another upgrade.Failure to do so may render the cards under upgrade to be unusable.Step 5
RP/0/RP0/CPU0:ROUTER# show logging | inc "OK, ROMMON A"RP/0/RP0/CPU0:Oct 28 14:40:57.223 PST8: upgrade_daemon[380][360]: OK, ROMMON A is programmed successfully.SP/0/0/SP:Oct 28 14:40:58.249 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.SP/0/2/SP:Oct 28 14:40:58.251 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.LC/0/6/CPU0:Oct 28 14:40:58.336 PST8: upgrade_daemon[244][233]: OK, ROMMON A is programmed successfully.LC/0/2/CPU0:Oct 28 14:40:58.365 PST8: upgrade_daemon[244][233]: OK, ROMMON A is programmed successfully.SP/0/SM0/SP:Oct 28 14:40:58.439 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.SP/0/SM1/SP:Oct 28 14:40:58.524 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.LC/0/0/CPU0:Oct 28 14:40:58.530 PST8: upgrade_daemon[244][233]: OK, ROMMON A is programmed successfully.RP/0/RP1/CPU0:Oct 28 14:40:58.593 PST8: upgrade_daemon[380][360]: OK, ROMMON A is programmed successfully.SP/0/6/SP:Oct 28 14:40:58.822 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.SP/0/SM2/SP:Oct 28 14:40:58.890 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.SP/0/SM3/SP:Oct 28 14:40:59.519 PST8: upgrade_daemon[125][121]: OK, ROMMON A is programmed successfully.Step 6
RP/0/RP0/CPU0:ROUTER# adminRP/0/RP0/CPU0:ROUTER(admin)# upgrade rommon b all disk0Please do not power cycle, reload the router or reset any nodes untilall upgrades are completed.Please check the syslog to make sure that all nodes are upgraded successfully.If you need to perform multiple upgrades, please wait for current upgradeto be completed before proceeding to another upgrade.Failure to do so may render the cards under upgrade to be unusable.Step 7
RP/0/RP0/CPU0:Router# show logging | inc "OK, ROMMON B"RP/0/RP0/CPU0:Oct 28 13:27:00.783 PST8: upgrade_daemon[380][360]: OK, ROMMON B is programmed successfully.LC/0/6/CPU0:Oct 28 13:27:01.720 PST8: upgrade_daemon[244][233]: OK, ROMMON B is programmed successfully.SP/0/2/SP:Oct 28 13:27:01.755 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.LC/0/2/CPU0:Oct 28 13:27:01.775 PST8: upgrade_daemon[244][233]: OK, ROMMON B is programmed successfully.SP/0/0/SP:Oct 28 13:27:01.792 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.SP/0/SM0/SP:Oct 28 13:27:01.955 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.LC/0/0/CPU0:Oct 28 13:27:01.975 PST8: upgrade_daemon[244][233]: OK, ROMMON B is programmed successfully.SP/0/6/SP:Oct 28 13:27:01.989 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.SP/0/SM1/SP:Oct 28 13:27:02.087 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.RP/0/RP1/CPU0:Oct 28 13:27:02.106 PST8: upgrade_daemon[380][360]: OK, ROMMON B is programmed successfully.SP/0/SM3/SP:Oct 28 13:27:02.695 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.SP/0/SM2/SP:Oct 28 13:27:02.821 PST8: upgrade_daemon[125][121]: OK, ROMMON B is programmed successfully.Step 8
When you reload the card, the new ROMMON is active. This is done by resetting each node, one at a time, or just reset the entire router.
Note
RP/0/RP0/CPU0:ROUTER# hw-module node 0/RP0/CPU0 or 0/RP1/CPU0 reloadRP/0/RP0/CPU0:ROUTER# reloadUpdating Commit Database. Please wait...[OK]Proceed with reload? [confirm]Reload each Node - For Fan Controllers (FCx), Alarm Modules (AMx), Fabric Cards (SMx), and RPs (RPx), you must wait until the reloaded node is fully reloaded before resetting the next node of the pair. But non-pairs can be reloaded without waiting.RP/0/RP0/CPU0:ROUTER# hw-module node 0/RP0/CPU0 or 0/RP1/CPU0 reloadRP/0/RP0/CPU0:ROUTER# hw-module node 0/FC0/SPRP/0/RP0/CPU0:ROUTER# hw-module node 0/AM0/SPRP/0/RP0/CPU0:ROUTER# hw-module node 0/SM0/SPRP/0/RP0/CPU0:ROUTER# hw-module node 0/0/CPU
Note
Step 9
RP/0/RP1/CPU0:CRS-B(admin)# show diag | inc ROM|NODE|PLIMNODE 0/0/SP : MSC(SP)ROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]PLIM 0/0/CPU0 : 4OC192-POS/DPTROMMON: Version 1.32(20050525:193559) [CRS-1 ROMMON]NODE 0/2/SP : MSC(SP)ROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]PLIM 0/2/CPU0 : 8-10GbEROMMON: Version 1.32(20050525:193559) [CRS-1 ROMMON]NODE 0/6/SP : MSC(SP)ROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]PLIM 0/6/CPU0 : 16OC48-POS/DPTROMMON: Version 1.32(20050525:193559) [CRS-1 ROMMON]NODE 0/RP0/CPU0 : RPROMMON: Version 1.32(20050525:193559) [CRS-1 ROMMON]NODE 0/RP1/CPU0 : RPROMMON: Version 1.32(20050525:193559) [CRS-1 ROMMON]]NODE 0/SM0/SP : FC/SROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]NODE 0/SM1/SP : FC/SROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]NODE 0/SM2/SP : FC/SROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]NODE 0/SM3/SP : FC/SROMMON: Version 1.32(20050525:193402) [CRS-1 ROMMON]
Notes
•
The required SMU for Cisco IOS XR Software Release 3.0.1 to be compatible with ROMMON 1.32 is comp-hfr-001.CSCee55511; this must be installed before the ROMMON upgrade.
Use the show platform command to retrieve the location IDs.
Note
RP/0/RP1/CPU0:CRS-B(admin)# show platformNode Type PLIM State Config State-----------------------------------------------------------------------------0/0/SP MSC(SP) N/A IOS-XR RUN PWR,NSHUT,MON0/0/CPU0 MSC 4OC192-POS/DPT IOS-XR RUN PWR,NSHUT,MON0/2/SP MSC(SP) N/A IOS-XR RUN PWR,NSHUT,MON0/2/CPU0 MSC 8-10GbE IOS-XR RUN PWR,NSHUT,MON0/6/SP MSC(SP) N/A IOS-XR RUN PWR,NSHUT,MON0/6/CPU0 MSC 16OC48-POS/DPT 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/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,MON•
•
SP/0/0/SP:Oct 17 16:42:37.320 : rommon_burner[65584]:%PLATFORM-ROMMON_BURNER-3-FILE_OP_ERR : Opening ROMMON flash partitionfailed: No such file or directory in function main at line 992You need to upgrade the bootflash of that node to MONLIB 3.0 for Cisco IOS XR Software Release 3.2.x and MONLIB 2.2 for Cisco IOS XR Software Release 3.0.1. To do this, follow the MONLIB upgrade procedure, as follows:
–
–
–
RP/0/RP0/CPU0:ROUTER# show diag | inc MONLIB|NODE|PLIMNODE 0/0/SP : MSC(SP)MONLIB: QNXFFS Monlib Version 3.0PLIM 0/0/CPU0 : 4OC192-POS/DPTMONLIB: QNXFFS Monlib Version 3.0NODE 0/2/SP : MSC(SP)PLIM 0/2/CPU0 : 8-10GbENODE 0/6/SP : MSC(SP)MONLIB: QNXFFS Monlib Version 3.0PLIM 0/6/CPU0 : 16OC48-POS/DPTMONLIB: QNXFFS Monlib Version 3.0NODE 0/RP0/CPU0 : RPMONLIB: QNXFFS Monlib Version 3.0NODE 0/RP1/CPU0 : RPNODE 0/SM0/SP : FC/SMONLIB: QNXFFS Monlib Version 3.0NODE 0/SM1/SP : FC/SNODE 0/SM2/SP : FC/SMONLIB: QNXFFS Monlib Version 3.0NODE 0/SM3/SP : FC/SMONLIB: QNXFFS Monlib Version 3.0•
format bootflash: location node-id•
Guest
