Guest

Cisco IOS XR Software (End-of-Sale)

Release Notes for Cisco IOS XR Software Release 3.3.3

  • Viewing Options

  • PDF (619.6 KB)
  • Feedback
Release Notes for Cisco IOS XR Software Release 3.3.3

Table Of Contents

Release Notes for Cisco IOS XR Software Release 3.3.3

Contents

Introduction

System Requirements

Cisco CRS-1 Router

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Determining the Software Version

Other Firmware Code

Cisco XR 12000 Series Router

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Determining the Software Version

Other Firmware Code

New and Changed Information

Health-Monitoring Diagnostics

Configuring Health-Monitoring Diagnostics

Running Health-Monitoring Diagnostics: Example

Fabric Diagnosis Testing

Configuring Fabric Diagnosis Testing: Example

DRP Update

Diagnostic CLI Change

Quality of Service (QoS) Units of Measure Changes

SONET MIB

Important Notes

Caveats—Release 3.3.3

Platform Independent Caveats

Cisco CRS-1 Router Caveats

Cisco XR 12000 Series Router Caveats

Upgrading Cisco IOS XR Software

Changes to the Format of the File System

Turbobooting PRP Cards

Turbobooting to Disk0:

Turbobooting to Compact Flash

Installing Optional Packages

Troubleshooting

Related Documentation

Hardware Documents

Software Documents

Obtaining Documentation, Obtaining Support, and Security Guidelines


Release Notes for Cisco IOS XR Software Release 3.3.3


March 10, 2013

Cisco IOS XR Software Release 3.3.3

Text Part Number OL-12488-05


Note Please see the "Important Notes" section for important information about Cisco IOS XR Software Release 3.3.3.



Note You can find the most current Cisco IOS XR software documentation on the World Wide Web at http://www.cisco.com/univercd/cc/td/doc/product/ioxsoft/iox33/index.htm. These electronic documents may contain updates and modifications. See the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section for more information on obtaining Cisco documentation.


These release notes describe the features provided in Cisco IOS XR Software Release 3.3.3 and are updated as needed.

For a list of software caveats that apply to Cisco IOS XR Software Release 3.3.3, see the "Caveats—Release 3.3.3" 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

System Requirements

New and Changed Information

Important Notes

Caveats—Release 3.3.3

Upgrading Cisco IOS XR Software

Troubleshooting

Related Documentation

Obtaining Documentation, Obtaining Support, and Security Guidelines

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:

IP and Routing—Supports a wide range of IPv4 and IPv6 services and routing protocols, such as Border Gateway Protocol (BGP), Intermediate System-to-Intermediate System (IS-IS), Open Shortest Path First (OSPF), IP Multicast, Routing Policy Language (RPL), and Hot Standby Router Protocol (HSRP)/Virtual Router Redundancy Protocol features (VRRP).

Multiprotocol Label Switching (MPLS)—Supports MPLS protocols, including Traffic Engineering (TE), Resource Reservation Protocol (RSVP), and Label Distribution Protocol (LDP).

Multicast—Provides comprehensive IP Multicast software, including Source Specific Multicast (SSM). The Cisco CRS-1 router supports Bidirectional Protocol Independent Multicast (BIDIR-PIM).

Quality of Service (QoS)—Supports rich QoS mechanisms, including policing, marking, queuing, dropping, and shaping. Additionally, the operating systems support Modular QoS CLI (MQC). MQC is used to configure various QoS features on various Cisco platforms.

Manageability—Provides industry-standard management interfaces including modular command-line interface (CLI), Simple Network Management Protocol (SNMP), and native Extensible Markup Language (XML) interfaces.

Security—Provides comprehensive network security features, including access control lists (ACLs), the routing authentications AAA and TACACS+, Secure Shell (SSH), and SNMPv3. Control plane protections integrated into line card ASICs include Global Time-to-Live Security Mechanism (GTSM), RFC 3682, and dynamic control plane protection (DCoPP).

Craft Works interface (CWI)—The CWI is a client-side application used to configure and manage Cisco routers. The management and configuration features include fault, configuration, security, and inventory, with an emphasis on speed and efficiency. The CWI provides a context-sensitive graphical representation of the objects in a Cisco router, simplifying the process of configuring and managing the router. CWI allows you to log in to multiple routers and perform management tasks.

Availability—Supports rich availability features such as fault containment, fault tolerance, fast switchover, link aggregation, and nonstop forwarding (NSF).

See the "New and Changed Information" section for a detailed list of new features by platform for Cisco IOS XR Software Release 3.3.3.

System Requirements

The Cisco IOS XR Software Release 3.3.3 is supported on the following platforms:

Cisco CRS-1 Router

Cisco XR 12000 Series Router

Cisco CRS-1 Router

This section describes the system requirements for Cisco IOS XR Software Release 3.3.3 supported on a Cisco CRS-1 router and includes the following information:

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Determining the Software Version

Other Firmware Code


Note The Designated Shelf Controller (DSC) migration feature requires that both shelf route processors (RPs) are in the default SDR of the Cisco CRS-1 Multichassis System.


Feature Set Table

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.3.3 features. These features are delivered in a package called a package installation envelope (PIE). Table 1 and Table 2 list the Cisco IOS XR software feature set matrix and associated PIE and TAR filenames available for the Cisco IOS XR  Software Release 3.3.3 supported on the Cisco CRS-1 router.

Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.3.3 PIE Files) 

Feature Set
Filename
Description
Composite Package

Cisco IOS XR IP Unicast Routing Core Bundle

comp-hfr-mini.pie-3.3.3

Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, and Routing packages.

Optional Individual Packages 1

Cisco IOS XR Manageability Package

hfr-mgbl-p.pie-3.3.3

CORBA agent, XML Parser, HTTP server, SNMP Agent, and Alarm correlation.

Cisco IOS XR MPLS Package

hfr-mpls-p.pie-3.3.3

MPLS-TE, LDP, MPLS Forwarding, MPLS OAM, LMP, OUNI, and RSVP.

Cisco IOS XR Multicast Package

hfr-mcast-p.pie-3.3.3

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.3.3

Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.

Cisco IOS XR Diagnostic Package

hfr-diags-p.pie-3.3.3

Diagnostic utilities, both online and offline, for Cisco IOS XR routers.

1 Packages are installed individually.


 

Table 2 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.3.3 TAR Files) 

Feature Set
Filename
Description

Cisco IOS XR IP/MPLS Core Software

CRS-1-iosxr-3.3.3.tar

Tar file containing:

Cisco IOS XR Diagnostic Package

Cisco IOS XR IP Unicast Routing Core Bundle

Cisco IOS XR Manageability Package

Cisco IOS XR MPLS Package

Cisco IOS XR Multicast Package

Cisco IOS XR IP/MPLS Core Software 3DES

CRS-1-iosxr-k9-3.3.3.tar

Tar file containing:

Cisco IOS XR Diagnostic Package

Cisco IOS XR IP Unicast Routing Core Bundle

Cisco IOS XR Manageability Package

Cisco IOS XR MPLS Package

Cisco IOS XR Multicast Package

Cisco IOS XR Security Package


Memory Requirements

The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR Software
Release 3.3.3 are:

2-GB memory on the route processors (RPs)

1-GB memory on the modular services cards (MSCs)

Hardware Supported

Cisco IOS XR Software Release 3.3.3 supports Cisco CRS-1 routers. All hardware features are supported by Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" 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" section.

Table 3 Cisco CRS-1 Supported Hardware and Minimum Software Requirements 

Component
Part Number
Min. Software Version Required
Cisco CRS-1 Series 16-Slot Line Card Chassis

Cisco CRS-1 16-Slot Line Card Chassis

CRS-16-LCC

3.2

Cisco CRS-1 Fan Tray for 16-Slot LCC

CRS-16-LCC-FAN-TR

3.2

Cisco CRS-1 16-Slot Fabric Card / Single

CRS-16-FC/S

3.2

Cisco CRS-1 Fan Controller for 16-Slot Line Card Chassis

CRS-16-LCC-FAN-CT

3.2

Cisco CRS-1 16-Slot Route Processor

CRS-16-RP

3.2

Cisco CRS-1 Memory Module 2 GB

CRS-MEM-2G

3.2

Cisco CRS-1 PCMCIA Flash Disk 1 GB

CRS-FLASH-DISK-1G

3.2

Cisco CRS-1 Modular Services Card

CRS-MSC

3.2

Cisco CRS-1 LCC Front AC Power Panel

CRS-16-ACGRILLE

3.2

Cisco CRS-1 LCC Front DC Power Panel

CRS-16-DCGRILLE

3.2

Cisco CRS-1 16-Slot Alarm Board

CRS-16-ALARM

3.2

Cisco CRS-1 AC Delta Power Shelf for 16-Slot LCC

CRS-16-LCC-PS-ACD

3.2

Cisco CRS-1 AC Wye Power Shelf for 16-Slot LCC

CRS-16-LCC-PS-ACW

3.2

Cisco CRS-1 DC Power Shelf for 16-Slot LCC

CRS-1-LCC-PS-DC

3.2

Cisco CRS-1 4xOC-192/STM64 POS/DPT Interface Module/VS

4OC192-POS/DPT-VS

3.2

Cisco CRS-1 4xOC-192/STM64 POS/DPT Interface Module/SR

4OC192-POS/DPT-SR

3.2

Cisco CRS-1 4xOC-192/STM64 POS/DPT Interface Module/IR

4OC192-POS/DPT-IR

3.2

Cisco CRS-1 4xOC-192/STM64 POS/DPT Interface Module/LR

4OC192-POS/DPT-LR

3.2

Cisco CRS-1 16xOC-48/STM16 POS/DPT Interface Module

16OC48-POS/DPT

3.2

Cisco CRS-1 2.5 G SFP LR Optic

POM-OC48-LR2-LC-C

3.2

Cisco CRS-1 2.5 G SFP SR Optic

POM-OC48-SR-LC-C

3.2

Cisco CRS-1 Line Card Chassis Front Doors

CRS-16-LCC-DRS-F

3.2

Cisco CRS-1 Line Card Chassis Front Cable Mgmt

CRS-16-LCC-FRNT

3.2

Cisco CRS-1 LCC Expanded Front Cable Mgmt

CRS-16-LCC-FRNT-E

3.2

Cisco CRS-1 Line Card Chassis Rear Cable Mgmt

CRS-16-LCC-BCK-CM

3.2

Cisco CRS-1 Line Card Chassis Rear Doors

CRS-16-LCC-DRS-R

3.2

Cisco CRS-1 Lift for LCC 16 and FCC

CRS-16-LIFT/B

3.2

Cisco CRS-1 Series 8-Slot Line Card Chassis

Cisco CRS-1 8-Slot Line Card Chassis

CRS-8-LCC

3.2

Cisco CRS-1 Fan Tray for 8-Slot Line Card Chassis

CRS-8-LCC-FAN-TR

3.2

Cisco CRS-1 Line Card Chassis Filter Pack

CRS-8-LCC-FILTER

3.2

Cisco CRS-1 AC Pwr Rectifier for 8-Slot LCC

CRS-8-AC-RECT

3.2

Cisco CRS-1 DC Power Entry Module for 8-Slot LCC

CRS-8-DC-PEM

3.2

Cisco CRS-1 AC & DC Power Module Filter for 8-Slot LCC

CRS-8-PWR-FILTER

3.2

Cisco CRS-1 AC Delta PDU for CRS-8 LCC

CRS-8-LCC-PDU-ACD

3.2

Cisco CRS-1 AC Wye PDU for CRS-8 LCC

CRS-8-LCC-PDU-ACW

3.2

Cisco CRS-1 DC PDU for CRS-8 LCC

CRS-8-LCC-PDU-DC

3.2

Cisco CRS-1 8-Slot Fabric Card / Single

CRS-8-FC/S

3.2

Cisco CRS-1 8-Slot Fabric Card Blank

CRS-8-FC-BLANK

3.2

Cisco CRS-1 8-Slot Fabric Handle

CRS-8-FC-HANDLE

3.2

CRS-FCC= Cisco CRS-1 Series Fabric Card Chassis Only

CRS-FCC=

3.2

CRS-1 Fabric Chassis AC Delta Power Kit

CRS-FCC-ACD-KIT

3.2

CRS-1 Fabric Chassis AC Grille

CRS-FCC-ACGRILLE

3.2

CRS-1 Fabric Chassis AC-Wye Power Kit

CRS-FCC-ACW-KIT

3.2

CRS Fabric Chassis DC Power Kit

CRS-FCC-DC-KIT

3.2

CRS-1 Fabric Chassis DC Power Grille

CRS-FCC-DCGRILLE

3.2

CRS Fabric Chassis Lift Bracket

CRS-FCC-LIFT-BRKT

3.2

CRS Fabric Chassis OIM Modules

CRS-FCC-OIM-1S=

3.2

Cisco CRS-1 Series FC Chassis Shelf/Fan/Enet cntr

CRS-FCC-SC-GE=

3.2

CRS-1 Fabric Chassis AC Intake Grille

CRS-FCC-ACGRILLE=

3.2

CRS-1 Fabric Chassis DC Intake Grille

CRS-FCC-DCGRILLE=

3.2

Cisco CRS-1 Series Fan Tray for FCC

CRS-FCC-FAN-TR=

3.2

CRS-1 Fabric Card Chassis Fan Tray Filters

CRS-FCC-FILTER=

3.2

CRS-1 Fabric Chassis Front Cosmetic Kit

CRS-FCC-FRNT-CM=

3.2

Cisco CRS-1 Series Fabric Card Chassis Fiber Module LED

CRS-FCC-LED=

3.2

Cisco CRS-1 Series DC Power Shelf for FCC

CRS-FCC-PS-DC=

3.2

CRS-1 Fabric Chassis Rear Cosmetic Kit

CRS-FCC-REAR-CM=

3.2

CRS-LIFT Brackets for Fabric Chassis

CRS-FCC-LIFT-BRKT=

3.2

CRS Fabric Chassis OIM Module

CRS-FCC-OIM-1S

3.2

CRS-1 Fabric Chassis AC Delta Power Supply

CRS-FCC-PS-ACD

3.2

CRS-1 Fabric Chassis AC Wye Option

CRS-FCC-PS-ACW

3.2

CRS-1 Fabric Chassis DC Power Option

CRS-FCC-PS-DC

3.2

Cisco CRS-1 Series Fabric Card Chassis Switch Fabric Card

CRS-FCC-SFC=

3.2

Cisco CRS-1 8-Slot Route Processor

CRS-8-RP

3.2

Cisco CRS-1 8-Slot Route Processor Blank

CRS-8-RP-BLANK

3.2

Cisco CRS-1 8-Slot Route Processor Handle

CRS-8-RP-HANDLE

3.2

Cisco CRS-1 8x10 GbE Interface Module/LR

8-10GBE

3.2

Cisco CRS-1 4xOC-192/STM64 POS/DPT Interface Module/LR

4OC192-POS/DPT-LR

3.2

Cisco CRS-1 1xOC-768/STM256 POS Interface Module/SR

1OC768-POS-SR

3.2

Cisco Carrier 1 Series SPA Interface Processor 40G

CRS1-SIP-800

3.2

Cisco 1-Port OC-192c/STM-64c POS/RPR Shared Port Adapter with XFP Optics

SPA-OC192POS-XFP

3.2

Cisco 8-Port Gigabit Ethernet Shared Port Adapter

SPA-8X1GE

3.2

Cisco 4-Port OC-3 Shared Port Adapter

SPA-4XOC3-POS

3.2

10GBASE-DWDM XENPAK

CRS 1 CRS-XENPAK10GB-DWDM

3.2.2

Cisco CRS-1 8-Port OC-12 Shared Port Adapter

SPA-8XOC12-POS

3.3.0

ITU grid 4X10G PLIM

4-10GE-ITU/C

3.3.0

ITU grid 40G PLIM

1OC768-ITU/C

3.3.0

Cisco CRS-1 Distributed Route Processor

CRS-DRP

3.3.0

Cisco CRS-1 Distributed Route Processor Revision B

CRS-DRP-B

3.3.3

Cisco CRS-1 16-slot route processor

CRS-16-RP-B

3.3.0

Cisco 10-GBASE-LR XENPAK Module for CRS-1

CRS-XENPAK10GB-LR

3.3.3, 3.4.0

Cisco 10-GBASE Extended Range XENPAK Module for SMF

XENPAK-10GB-ER+=

3.3.3, 3.4.0

Cisco 10-GBASE Long Range XENPAK Module for SMF

XENPAK-10GB-LR+=

3.3.3, 3.4.0

Cisco CRS-1 8-Slot Install Kit

CRS-8-INSTALL-KT

N/A

Cisco CRS-1 8-Slot Fork Lift Tube

CRS-8-LIFT-TUBE

N/A

Cisco CRS-1 8-Slot Front Badge Panel

CRS-8-BDG-PANEL

N/A

Cisco CRS-1 8-Slot Front Inlet Grill

CRS-8-FRNT-GRILL

N/A

Cisco CRS-1 8-Slot Horizontal Install Rails

CRS-8-HRZ-RAILS

N/A


Software Compatibility

Cisco IOS XR Software Release 3.3.3 is compatible with the following Cisco CRS-1 systems:

Cisco CRS-1 8-Slot Line Card Chassis

Cisco CRS-1 16-Slot Line Card Chassis


Note The Cisco CRS-1 4-Slot Line Card Chassis requires Cisco IOS XR Software Release 3.4.0 and, therefore cannot operate with Cisco IOS XR Software Release 3.3.3.


Determining the Software Version

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 Establish a Telnet session with the router.

Step 2 Enter the show version command:

RP/0/RP0/CPU0:router# show version
 
   
RP/0/RP0/CPU0:ios#show version 
 
   
Cisco IOS XR Software, Version 3.3.3[00]
Copyright (c) 2007 by cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 1.43(20061109:045749) [CRS-1 ROMMON],  
 
   
ios uptime is 2 hours, 13 minutes
System image file is "disk0:hfr-os-mbi-3.3.3/mbihfr-rp.vm"
 
   
cisco CRS-8/S (7457) processor with 4194304K bytes of memory.
7457 processor at 1197Mhz, Revision 1.2
 
   
17 Packet over SONET/SDH network interface(s)
17 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.
998576k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).
 
   
Configuration register on node 0/RP0/CPU0 is 0x102
 
   

Other Firmware Code

The following firmware code is supported by the Cisco CRS-1 router:

The minimum ROMMON version required for this release is 1.45. For detailed information on ROMMON specifications, see http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html.


Note Before you upgrade a Cisco CRS-1 system to Cisco IOS XR Software Release 3.3.3 or a later release, make sure that ROM Monitor software is version 1.45 or a later version on all RPs and all nodes on the router. If the router comes up with an incompatible version of the ROM Monitor, the standby RP or other nodes might fail to boot.

In addition, Cisco CRS-1 multishelf systems should be upgraded to ROMMON version 1.45 before being upgraded to Cisco IOS XR software Release 3.3.3 to ensure that RPs receive the correct rack number assignments during system boot.


The minimum CPUCNTRL version required for this release is 2.07.

For detailed information on ROMMON, see Cisco IOS XR ROM Monitor Guide.

Cisco XR 12000 Series Router

This section describes the system requirements for Cisco IOS XR Software Release 3.3.3 supported on the Cisco XR 12000 Series Router and includes the following information:

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Determining the Software Version

Other Firmware Code

Feature Set Table

The Cisco IOS XR software is packaged in feature sets (software images). Each feature set contains a specific set of features. Table 4 and Table 5 list the Cisco IOS XR software feature set matrix and the associated filenames for the Cisco XR 12000 Series Router.

Table 4 Cisco XR 12000 Series Router Supported Feature Sets (Cisco IOS XR Software Release 3.3.3 PIE Files) 

Feature Set
Filename
Description
Composite Package

Cisco IOS XR IP Unicast Routing Core Bundle

c12k-mini.vm-3.3.3

Contains the required core packages including, OS, Admin, Base, Forwarding, and Routing packages.

Optional Individual Packages 1

Cisco IOS XR Manageability Package

c12k-mgbl.pie-3.3.3

CORBA agent, XML Parser, HTTP server, SNMP Agent, and Alarm correlation.

Cisco IOS XR MPLS Package

c12k-mpls.pie-3.3.3

MPLS-TE, LDP, MPLS Forwarding, MPLS OAM, LMP, OUNI, and RSVP.

Cisco IOS XR Multicast Package

c12k-mcast.pie-3.3.3

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.3.3

Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.

Cisco IOS XR Standby RP Boot Image

mbiprp-rp.vm-3.3.3

Support for booting the standby RP on a Cisco XR 12000 Series Router (PRP).

Cisco IOS XR Diagnostic Package

c12k-diags.pie-3.3.3

Diagnostic utilities for Cisco IOS XR routers

1 Packages are installed individually.


 

Table 5 Cisco XR 12000 Series Router Supported Feature Sets (Cisco IOS XR Software Release 3.3.3 TAR Files) 

Feature Set
Filename
Description

Cisco IOS XR IP/MPLS Core Software

XR12000-iosxr-3.3.3.tar

Tar file containing:

Cisco IOS XR IP Unicast Routing Core Bundle

Cisco IOS XR Manageability Package

Cisco IOS XR MPLS Package

Cisco IOS XR Multicast Package

Cisco IOS XR IP/MPLS Core Software 3DES

XR12000-iosxr-k9-3.3.3.tar

Tar file containing:

Cisco IOS XR IP Unicast Routing Core Bundle

Cisco IOS XR Manageability Package

Cisco IOS XR MPLS Package

Cisco IOS XR Multicast Package

Cisco IOS XR Security Package


Memory Requirements


Caution If you remove the medium in which the software image or configuration is stored, the router might become unstable and fail.

The minimum memory requirements for Cisco XR 12000 Series routers running Cisco IOS XR Software Release 3.3.3 are:

2-GB route memory on Performance Route Processor 2 (PRP-2)

1-GB ATA flash storage on PRP-2

1-GB industrial grade compact flash storage on PRP-2 (FLASH-PRP2-1G)


Note 1-GB compact flash is supported only with Cisco IOS XR software version 3.3.0 and later releases. Therefore, if you are upgrading from a release prior to Release 3.3.0, you must continue to use disk0.

In the current release, only the FLASH-PRP2-1G compact flash is supported.


1-GB line-card route memory on all line Engine 3 cards installed in the system

1-GB line-card route memory on all Engine 5-based SPA Interface Processors in the system:

The default route memory on the 1200-SIP-600 is 1G.

The default route memory on the 1200-SIP-401, 1200-SIP-501, and 1200-SIP-601 is 2 G.

Hardware Supported

Cisco IOS XR Software Release 3.3.3 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" 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" section.

.

Table 6 Cisco XR 12000 Series Router Supported Hardware and Minimum Software Requirements 

Component
Part Number
Minimum Software Version Required

Cisco XR 12000 Series 12404/80 Chassis

GSR4/80-xx

3.2.0

Cisco XR 12000 Series 12406/120 Chassis

GSR6/120-AC

3.2.0

Cisco XR 12000 Series 12410/200 Chassis

GSR10/200-xx

3.2.0

Cisco XR 12000 Series 12416/320 Chassis

GSR16/320-xx

3.2.0

Cisco XR 12000 Series Performance Route Processor 2

PRP-2

3.2.0

Cisco 12000 Series 40 GB Hard Drive Option

HD-PRP2-40G

3.2.0

Cisco 12000 Series 4xOC12c/STM4c POS Intermediate Reach Single-Mode optics

4OC12X/POS-I-SC-B

3.2.0

Cisco 12000 Series 4xOC12c/STM4c POS Short Reach Multi-Mode optics

4OC12X/POS-M-SC-B

3.2.0

Cisco 12000 Series 16xOC3c/STM1c POS Short Reach Multi-Mode optics

16OC3X/POS-M-MJ-B

3.2.0

Cisco 12000 Series 16xOC3c/STM1c POS Intermediate Reach Single-Mode optics

16OC3X/POS-I-LC-B

3.2.0

Cisco 12000 Series 8xOC3c/STM1c POS Short Reach Multi-Mode optics

8OC3X/POS-MM-MJ-B

3.2.0

Cisco 12000 Series 8xOC3c/STM1c POS Intermediate Reach Single-Mode optics

8OC3X/POS-IR-LC-B

3.2.0

Cisco 12000 Series 4xOC3c/STM1c POS Short Reach Multi-Mode optics

4OC3X/POS-MM-MJ-B

3.2.0

Cisco 12000 Series 4xOC3c/STM1c POS Intermediate Reach Single-Mode optics

4OC3X/POS-IR-LC-B

3.2.0

Cisco 12000 Series 4xOC3c/STM1c POS Long Reach Single-Mode optics

4OC3X/POS-LR-LC-B

3.2.0

Cisco 12000 Series 1xOC48c/STM16c POS Short Reach Single-Mode optics

OC48X/POS-SR-SC

3.2.0

Cisco 12000 Series 1xOC48c/STM16c POS Long Reach Single-Mode optics

OC48X/POS-LR-SC

3.2.0

Cisco 12000 Series 4xGE with SFP optics

4GE-SFP-LC

3.2.0

Cisco 12000 Series SPA Interface Processor 10G

12000-SIP-600

3.2.0

Cisco 1-Port OC-192c/STM-64c POS/RPR Shared Port Adapter with VSR Optics

SPA-OC192-POS-VSR

3.2.0

Cisco 1-Port OC-192c/STM-64c POS/RPR Shared Port Adapter with LR Optics

SPA-OC192-POS-LR

3.2.0

Cisco 1-Port OC-192c/STM-64c POS/RPR Shared Port Adapter with XFP Optics

SPA-OC192-POS-XFP

3.2.0

Cisco 5-Port Gigabit Ethernet Shared Port Adapter with SFP optics

SPA-5X1GE

3.2.0

Cisco 10-Port Gigabit Ethernet Shared Port Adapter with SFP optics

SPA-10X1GE

3.2.0

Cisco 1-Port 10 Gigabit Ethernet Shared Port Adapter with XFP optics

SPA-1XTENGE-XFP

3.2.0

12010 50 Gbps; 1PRP, 2 CSC, 5 SFC, 2 Alarm, 2 AC

12010-AC

3.3.0

12010 50 Gbps; 1PRP, 2 CSC, 5 SFC, 2 Alarm, 2 DC

12010-DC

3.3.0

12006 30 Gbps; 1PRP, 2 CSC, 3 SFC, 2 Alarm, 2 AC

12006-AC

3.3.0

12006 30 Gbps; 1PRP, 2 CSC, 3 SFC, 2 Alarm, 2 DC

12006-DC

3.3.0

80Gbps Fabric Option with 3xSFC and 2xCSC for 12016 Chassis

12016/80

3.3.0

Multirate 2.5G IP Service (Modular)

12000-SIP-401

3.3.0

Multirate 5G IP Services Engine (Modular)

12000-SIP-501

3.3.0

Multirate 10G IP Services Engine (Modular)

12000-SIP-601

3.3.0

2-port Channelized T3 to DS0 Shared Port Adapter

SPA-2XCT3/DS0

3.3.0

4-port Channelized T3 to DS0 Shared Port Adapter

SPA-4XCT3/DS0

3.3.0

2-port Clear Channel T3/E3 Shared Port Adapter

SPA-2XT3/E3

3.3.0

4-port Clear Channel T3/E3 Shared Port Adapter

SPA-4XT3/E3

3.3.0

2-port OC48/STM16 POS/RPR Shared Port Adapter

SPA-2XOC48POS/RPR

3.3.0

Cisco 8-Port 100BASE-TX Fast Ethernet Shared Port Adapter

SPA-8XFE-TX

3.3.0


Software Compatibility

Cisco IOS XR Software Release 3.3.3 is compatible with the following Cisco XR 12000 Series Router systems:

Cisco XR 12404 Router

Cisco XR 12406 Router

Cisco XR 12410 Router

Cisco XR 12416 Router

For the existing installed base, the following chassis are supported:

Cisco 12006 Router

Cisco 12008 Router

Cisco 12010 Router

Cisco 12012 Router

Cisco 12016 Router

Determining the Software Version

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 Establish a Telnet or SSH session with the router.

Step 2 Enter the show version command:

RP/0/5/CPU0:PE4#show version
 
   
Cisco IOS XR Software, Version 3.3.3[00]
Copyright (c) 2007 by cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] 
DEVELOPMENT SOFTWARE
Copyright,  Inc.
 
   
PE4 uptime is 18 hours, 49 minutes
System image file is "disk0:c12k-os-mbi-3.3.3/mbiprp-rp.vm"
 
   
cisco 12406/PRP (7457) processor with 2097152K bytes of memory.
7457 processor at 1265Mhz, Revision 1.2
 
   
3 1 Port ISE Packet Over SONET OC-48c/STM-16 Controllers (3 POS)
1 Cisco 12000 Series SPA Interface Processor- Controller (4294967295 Unknown)
2 Cisco 12000 Series Performance Route Processors
4 Packet over SONET/SDH network interface(s)
4 SONET/SDH Port controller(s)
4 PLIM QoS controller(s)
6 Ethernet/IEEE 802.3 interface(s)
10 GigabitEthernet/IEEE 802.3 interface(s)
2042k bytes of non-volatile configuration memory.
1000496k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).
65536k bytes of Flash internal SIMM (Sector size 256k).
 
   

Other Firmware Code

The following firmware code is supported by the Cisco XR 12000 Series Router:

The minimum ROMMON version required for this release is 1.15. For more information on the minimum ROMMON version required for this release, ROMMON upgrade procedures, and flashdisk information, see the Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.

The flashdisk Cisco part numbers are: MEM-12KRP-FD512M (=), MEM-12KRP-FD1G(=), and FLASH-PRP2-1G

New and Changed Information

No new software or hardware features are introduced in Cisco IOS XR Software Release 3.3.3.

This section includes the following information:

Health-Monitoring Diagnostics

Fabric Diagnosis Testing

DRP Update

Diagnostic CLI Change

Quality of Service (QoS) Units of Measure Changes

SONET MIB

Health-Monitoring Diagnostics

Health-monitoring diagnostic tests are non disruptive and run in the background while the system is in operation. The role of health-monitoring diagnostics is to be proactive in detecting hardware failures in the live network environment and inform appropriate entities of a failure. It is up to you to determine the interval at which to run health-monitoring checks. The interval can be as granular as 50ms.

You can configure health-monitoring diagnostics, including support for monitor intervals and the failure count thresholds of tests.

The show diagnostic content command output was modified to include diagnostic monitoring support.


Note Health-monitoring and other diagnostic configurations are not persistent across system reloads. You must manually reapply the configurations after rebooting the system.


Configuring Health-Monitoring Diagnostics

To configure health-monitoring diagnostic testing on specified cards while the router is connected to a

live network, perform the following procedure. You can configure the:

Execution interval for each health-monitoring test

Failure threshold for each health-monitoring test

Location where each health-monitoring test is run

Prerequisites

The Cisco IOS XR Diagnostics Package must be installed before starting this procedure. See Cisco IOS XR Getting Started Guide for information on installing packages.

SUMMARY STEPS

1. admin

2. configure

3. diagnostic monitor location node-id test {id | test-name} [disable]

4. diagnostic monitor interval location node-id test {id | test-name} number-of-days hour:minutes:seconds.milliseconds

5. diagnostic monitor threshold location node-id test {id | test-name} failure count failures

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

admin

Example:

RP/0/RP0/CPU0:router# admin

Enters administration EXEC mode.

Step 2 

configure

Example:

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

Enters administration configuration mode.

Step 3 

diagnostic monitor location node-id test {id | test-name} [disable]

Example:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor location 0/1/cpu0 test 1

Configures the health-monitoring diagnostic testing for a specified location.

Step 4 

diagnostic monitor interval location node-id

test {id | test-name} number-of-days

hour:minutes:seconds.milliseconds

Example:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor interval location 0/1/cpu0 test 1 12:55:25.100

Configures the health-monitoring diagnostic testing for a specified interval for a specified location.

Step 5 

diagnostic monitor threshold location node-id

test {id | test-name} failure count failures

Example:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor location 0/1/cpu0 test 1 failure count 25

Configures the health-monitoring diagnostic testing failure threshold.

Running Health-Monitoring Diagnostics: Example

In the following example, health-monitoring diagnostic test 1 for 0/1/CPU0 is enabled:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor location 0/1/cpu0 test 1
 
   

In the following example, health-monitoring diagnostic test 1 for 0/1/CPU0 is set to an interval of every 15 days and 6 hours:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor interval location 0/1/cpu0 test 1
15 6:0:0.0
 
   

In the following example, the health-monitoring diagnostic testing failure threshold is set to 25 failures for test 1 on 0/1/CPU0:

RP/0/RP0/CPU0:router(admin-config)# diagnostic monitor threshold location 0/1/CPU0 test 1 
failure count 25
 
   

The following example shows a sample result of the diagnostic test using the show diagnostic result location <loc> detail command.

 
   
  Overall diagnostic result: PASS
  Diagnostic level at card bootup: minimal
 
   
  Test results: (. = Pass, F = Fail, U = Untested)
 
   
1  ) ControlEthernetPingTest ---------> .
          Error code ------------------> 0 (DIAG_SUCCESS)
          Total run count -------------> 1
          Last test execution time ----> Wed Oct  4 05:29:28 2006
          First test failure time -----> n/a
          Last test failure time ------> n/a
          Last test pass time ---------> Wed Oct  4 05:29:28 2006
          Total failure count ---------> 0
          Consecutive failure count ---> 0
  2  ) SelfPingOverFabric --------------> .
          Error code ------------------> 0 (DIAG_SUCCESS)
          Total run count -------------> 1
          Last test execution time ----> Wed Oct  4 05:29:28 2006
          First test failure time -----> n/a
          Last test failure time ------> n/a
          Last test pass time ---------> Wed Oct  4 05:29:28 2006
          Total failure count ---------> 0
          Consecutive failure count ---> 0
  3  ) FabricPingTest ------------------> .
          Error code ------------------> 0 (DIAG_SUCCESS)
          Total run count -------------> 1
          Last test execution time ----> Wed Oct  4 05:29:58 2006
          First test failure time -----> n/a
          Last test failure time ------> n/a
          Last test pass time ---------> Wed Oct  4 05:29:58 2006
          Total failure count ---------> 0
          Consecutive failure count ---> 0
  4  ) ControlEthernetInactiveLinkTest -> .
          Error code ------------------> 0 (DIAG_SUCCESS)
          Total run count -------------> 1
          Last test execution time ----> Wed Oct  4 05:30:00 2006
          First test failure time -----> n/a
          Last test failure time ------> n/a
          Last test pass time ---------> Wed Oct  4 05:30:00 2006
          Total failure count ---------> 0
          Consecutive failure count ---> 0
  5  ) RommonRevision ------------------> .
          Error code ------------------> 0 (DIAG_SUCCESS)
          Total run count -------------> 1
          Last test execution time ----> Wed Oct  4 05:30:09 2006
          First test failure time -----> n/a
          Last test failure time ------> n/a
          Last test pass time ---------> Wed Oct  4 05:30:09 2006
          Total failure count ---------> 0
          Consecutive failure count ---> 0
 
   

By default, tests do not report any syslogs during health-monitoring. Only test results indicate any errors.

Fabric Diagnosis Testing

Fabric Diagnosis test is a non-disruptive, fault isolation test that "pings" each fabric node in a chassis from the standby RP node. The test steers ping test packets through different fabric planes, aggregates ping (pass or fail) results with fabric plane information, analyzes the results, and points out the most logical point of failure (if any) in the chassis. The test can only be executed from the standby RP Executing this test in a Cisco CRS-1 Carrier Routing System Multishelf System may help determine which fabric stage (s1, s2, or s3) is the most logical point of failure in the system. This test must be run in each LC rack standby RP in the system. For example, if the test reports failures on multiple LC racks, and the failure information points to the same fabric plane, then the most likely point of failure is the S2 stage, which is the card in fabric chassis of the system.

This test is recommended for Health Monitoring and reports syslogs, regardless of the "monitor syslog" setting. For certain types of failures, this test can help quickly detect fabric hardware issues.

The following restrictions apply to the Fabric Diagnosis tests:

By default, this test is not running in Health Monitoring mode. You must activate the test manually.

When you first run the test, you might not receive reports of defects. If you run the test manually, (and it is not already configured for Health Monitoring active mode), run the test once, wait for a couple of minutes, and then run it again to get a definite test result.

This initial period also applies when you start or restart a card that is running IOS XR. The test takes a few minutes before it can reliably detect issues with the newly added card.

Configuring Fabric Diagnosis Testing: Example

Cisco recommends that you configure the fabric diagnosis test as periodical health monitoring. Set the interval based on how soon you want to catch and isolate the fabric error. Cisco recommends that you set the interval for a minimum of 2 seconds. The following example shows the recommended configuration:

RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor location 0/RP0/CPU0 test 4
RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor interval location 0/RP0/CPU0 test 4 
0 00:00:03.0
RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor location 0/RP1/CPU0 test 4
RP/0/RP0/CPU0:router(admin-config)#diagnostic monitor interval location 0/RP1/CPU0 test 4 
0 00:00:03.0
RP/0/RP0/CPU0:router(admin-config)#commit
 
   

Use the show running-config command to confirm the settings.

RP/0/RP0/CPU0:router# show running-config
 
   
diagnostic monitor location 0/RP0/CPU0 test FabricDiagnosisTest
diagnostic monitor interval location 0/RP0/CPU0 test FabricDiagnosisTest 0 00:00:03.0
diagnostic monitor location 0/RP1/CPU0 test FabricDiagnosisTest
diagnostic monitor interval location 0/RP1/CPU0 test FabricDiagnosisTest 0 00:00:03.0

DRP Update

DRP and DRP-B are now supported as "location" in the CLI from RPs in the system.

The diagnostic CLI is not available on the DRP console. You must configure DRP tests from RP consoles.

Diagnostic CLI Change

Syntax for specifying a list of tests in configuration of "diagnostic schedule location <R/S/I> test <ID list>... " has changed. The new syntax for <ID list> is now "i;j-k" (previously "i,j-k").

Quality of Service (QoS) Units of Measure Changes

For Cisco IOS XR Software Release 3.3.0 and later releases, a number of new units of measure that have been introduced as options within the various Modular QoS command-line interface (MQC) can be applied within policy-maps.

Because the default units of measure may no longer be the same, care must be taken when taking a configuration earlier than Cisco IOS XR Software Release 3.3.0 and applying it to Cisco IOS XR Software Release 3.3.0 or later releases. Table 7 lists the changes to QoS units of measure.

Table 7 Changes to Quality of Service Units of Measure 

Command
Cisco IOS XR Release 3.2 (Default)
Cisco IOS XR Release 3.3.x and Cisco IOS XR Release 3.4.x (Default)

bandwidth

kbps

kbps

police rate

kbps

bps (change)

queue-limit

bytes

packets (change)

random-detect

bytes

packets (change)

shape average

kbps

packets (change)



Note The default units of measure (see Table 7) are inserted into the QoS policy following the upgrade. This results in a change to the policy's behavior. Therefore, manual review and keyword changes must be performed by the operator to ensure that the policy operates as expected.


Keywords cannot be inserted into the running configuration on a router running Cisco IOS XR Release 3.2.x in advance of the upgrade. An option is to edit the configuration offline, and add the necessary keywords.


Note To make change to a QoS policy, the policy must first be removed from any interfaces making a reference to it.


To remove a service policy from an input or output interface, use the no form of the service-policy command in interface configuration mode, as shown in the following syntax:

no service-policy {input | output}
 
   

When the policy is removed from any interfaces, the edited policy is applied. See the following Cisco IOS XR command reference sections:

Cisco IOS XR Modular Quality of Service Command Reference, Release 3.3

http://www.cisco.com/en/US/partner/products/ps5845/products_command_reference_book09186a008069e202.html

Cisco IOS XR Modular Quality of Service Command Reference, Release 3.4

http://www.cisco.com/en/US/partner/products/ps5845/products_command_reference_book09186a00806b06ab.html

SONET MIB

SONET MIB is supported and available through the online customer MIB support facility at http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml.

Important Notes

In certain countries, use of these products might 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 Upgrading from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router, Release 3.3 for procedures.

Follow the instructions provided by Cisco for all card removal and replacement (fabric cards, line cards, 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 the 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.

Cisco SIP-600 line cards for the Cisco XR 12000 Series Router draw more power than previous line cards. Depending on the configuration of power entry modules (PEMs) and other cards in the system, sufficient power might not be available when a new card is inserted or a PEM is removed. Before you insert a new card or remove a PEM, run the environment show command in admin EXEC mode:

RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router(admin)# show environment power-supply table
 
   
                      48V       Current
R/S/I     Module      (V)           (A)
0/24/*    PEM1         54             4
          PEM2         53             4
0/25/*    PEM1         54             4
          PEM2         53             4
 
   
Total Power Supplies:                  3200W
    Redundant Power Supplies:              1600W
    Worst Case Power Used:                  621W
    Current Power Used:                     428W
    Current Redundant Power Available:     1172W
    Current Total Power Available:         2772W
    Worst Case Redundant Power Available:   979W
    Worst Case Total Power Available:      2579W
 
   
PID                  Description                                        Watts
---                  -----------                                        -----
PRP-1                Cisco 12000 Series Performance Route Processor        60
4OC3X/POS-MM-MJ-B    4 port ISE OC3                                        90
.
.
.
 
   

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 No alerts are issued if more cards are inserted than the PEMs can support. Therefore, you must determine the power budget for the chassis before making any changes to it. Exceeding the power budget might result in the PEM being overloaded and cards powering down due to insufficient power availability.


CaveatsRelease 3.3.3

This section lists the caveats for Cisco IOS XR Software Release 3.3.3. Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious.

Caveats are organized as follows:

Platform Independent Caveats

Cisco CRS-1 Router Caveats

Cisco XR 12000 Series Router Caveats

Platform Independent Caveats

The following caveats occur on both platforms:

CSCeh42441

Basic Description: IMD does not clean notification queue during deregistration.

Symptom: ISIS related trace backs will be seen on the Vlan interfaces of LC after that LC reloads.

Conditions: These traceback messages will be seen only on the Vlan interfaces and does not consistently occur. This issue is very rare.

Workaround: No external workaround needed. These messages will stop by themselves and there is no system impact.

CSCek43987

Basic Description: Cisco IOS XR software displays error message during NetFlow configuration for interface using load config command.

Symptom: If a configuration is loaded using load filepath and the configuration file applies NetFlow to interfaces while it configures the NetFlow parameters, the configuration will fail with the following message:

Syntax/Authorization errors in one or more commands. Please use 'show configuration failed load' to view errors.

3376 bytes parsed in 1 sec (3329)bytes/sec

The output of the command show configuration failed load will display the following message:

!! CONFIGURATION FAILED DUE TO SYNTAX/AUTHORIZATION ERRORS

Conditions: This is caused by the order of the configuration parameters being wrong in the plain text configuration file. The NetFlow configuration is listed after the interfaces configuration that references those NetFlow items. This is not a problem if the system is booted with the configuration already in place.

Workaround: Issue the directive commit best-effort first, which will cause the correct configuration statements to be applied. And then issue the commit command which will cause the failed configuration - the application of NetFlow to the interfaces - to be processed and applied since the definition of the NetFlow information has already been accepted.

CSCsc05163

Basic Description: The CISCO-FLASH-MIB is not sending traps when the flash device is OIRed. SNMP traps ciscoFlashDeviceInsertedNotif and ciscoFlashDeviceRemovedNotif are not supported

Symptom: SNMP traps are not sent when a flash card is inserted or removed.

Conditions: All cases.

Workaround: None.

CSCsd32597

Basic Description: BGP Routing failure in next hop registrations.

Symptom: This error message is seen after we do a redundancy switchover.

Conditions: This message is seen only one time after doing a redundancy switchover.

Workaround: No workaround necessary. This message has no system impact.

CSCse08168

Basic Description: After a reload, RADIUS does not find the source interface.

Symptom: The source interface does not seem to take effect upon reload or RP failover.

Conditions: This happens for software interfaces such as Loopback. Using physical interfaces does not appear to be a condition that causes the problem.

Workaround: Restart the RADIUS process.

CSCse41524

Basic Description: An SNMPD coredump occurs during the committing of the community.

Symptom: Process SNMPD fails when the community string is configured or during router reload with a startup configuration containing SNMP-specific configurations.

Conditions: Intermittent.

Workaround: Reapply the SNMP configurations.

CSCsh27207

Basic Description: Unable to resolve recursive VPN label for a prefix and an RP failover.

Symptom: Traffic not passing in the topology of LDP over TE-Tunnel after RP FO.

Conditions: After RP FO or executing reload location all.

Workaround: There are 3 workarounds for the issue:

1. Specify a non-zero next hop in a static route through tunnel. For example,

            router static
             address-family ipv4 unicast
              172.16.1.7/32 tunnel-te306 172.16.0.8
             !
            !

2. Remove the static route (without using the first workaround) and then add it back.

3. Enter proc restart mpls_lsd.

Cisco CRS-1 Router Caveats

The following caveats occur only on the Cisco CRS-1 platform:

CSCsf27515

Basic Description: SONET J1 path trace mismatch not supported in CRS-1.

Symptom: The capability to define the expected SONET path trace does not exist in IOS-XR.

Conditions: The user must configure expected path trace. Upon receiving a path trace that does not match what is expected, the router generates a TIM-P according to SONET standards.

Workaround: None.

CSCsh38707

Basic Description: admin diagnostic configurations are lost after router reload.

Symptom:

After a router reload, admin diagnostic configurations are lost from the running configuration, and admin diagnostic configurations are listed under failed startup configurations.

For example, before reload (all commands are in admin mode) show running-config displays this output:

Building configuration...

<some non-diagnostic configs>

diagnostic schedule location 0/1/CPU0 test all daily 13:25

<some more non-diagnostic configs>

After reload (all commands are in admin mode) show running-config displays this output:

Building configuration...

<some non-diagnostic configs>

<some more non-diagnostic configs>

Entering show configuration failed startup displays this output:

!!21:08:17 UTC Wed Jan 10 2007

!! CONFIGURATION FAILED DUE TO SYNTAX/AUTHORIZATION ERRORS

diagnostic schedule location 0/1/CPU0 test all daily 13:25

Conditions: This can only happen after router reload or after DSC migration in a Multichassis system, if the diagnostic PIE is activated and the diagnostic configurations have been applied.

Workaround: In order to recover the originally configured and intended diagnostic behavior, the user must re-apply the failed configuration(s) manually.

Using the example above (all commands are in admin mode):

RP/0/RP0/CPU0:router(admin)# config
RP/0/RP0/CPU0:router(admin)# diagnostic schedule location 0/1/CPU0
RP/0/RP0/CPU0:router(admin)# test all daily 13:25 commit 
RP/0/RP0/CPU0:router(admin)# exit
 
   

CSCsh54368

Basic Description: Clearing ARP cache on 8x10GE LC logs errors and trace backs.

Symptom: Clearing ARP cache on the router generates errors from fib_mgr process.

Conditions: These messages can be safely ignored.

Workaround: None.

CSCsh68927

Basic Description: Exception kernel memory kernel not seen in running config.

Symptom: show running config does not show the kernel memory dumper command although it has been configured.

Conditions: Configuring and committing exception kernel memory kernel filepath harddisk:/K.

Workaround: None. The command works when configured but does not show up in the running configuration.

CSCsh80154

Basic Description: A non-existent node 0/0/0 may show up after software upgrade.

Symptom: After an upgrade, a new non-existent slot 0/0/SP could be shown under show platform admin mode.

Conditions: Currently, this symptom is seen when a router is upgraded from 3.3.1 to 3.3.3.

Workaround: None found.

Cisco XR 12000 Series Router Caveats

The following caveats are specific to the Cisco XR 12000 Series Router platform:

CSCsd73524

Basic Description: Using the clear route vrf vrf_name command produces an error.

Symptom: When you try to clear the VRF routes using clear route vrf vrf_name, you receive an error message saying that there is no RIB (routing) table.

Conditions: This error message is displayed only when using clear route vrf command. Other clear commands work properly.

Workaround: No workaround available.

CSCse49838

Basic Description: %FWD_HAL-2-ADJ_ERR: Cisco XR 12000 Series Router adj. internal error on console during an RP failover.

Symptom: When we a do a redundancy switchover, we see this message continuously for one minute, and then this message stops.

Conditions: This message is seen only for a minute, and this message stops. No other impact is seen.

Workaround: No workaround is needed. The node recovers from these messages by itself.

Upgrading Cisco IOS XR Software

The following URL links to online information that describes how to upgrade Cisco IOS XR software on Cisco CRS-1 and Cisco XR 12000 Series Router systems from earlier releases to Release 3.3.3:

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


Note Before you install or upgrade the software, you must upgrade the ROM Monitor software to the correct version. If a Cisco CRS-1 system running Cisco IOS XR Software Release 3.3.3 is brought up with the incorrect ROM Monitor software, the standby RP fails to boot and an error message appears. For information on correct ROM Monitor software on a single-shelf router, see "Upgrading and Downgrading ROM Monitor Software on Cisco CRS-1 Routers" in Cisco IOS XR ROM Monitor Guide.



Note If you are upgrading to Cisco IOS XR Software Release 3.3.3 and there is a NetFlow configuration, you will likely encounter caveat CSCek43987. Reapply the NetFlow configuration by commands using reload config failed startup and commit after the router reboots from upgrade. For further details, see the "Platform Independent Caveats" section.


Changes to the Format of the File System

For Cisco IOS XR Software Release 3.3.3, changes were made to the format of the file system that is used to store the router configuration files. When upgrading from earlier software releases, the following behavior can occur:

On the first upgrade from Cisco IOS XR Software Release 3.3.1 (or earlier release) to Cisco IOS XR Software Release 3.3.3, the Cisco IOS XR Software Release 3.3.3 creates new format configuration files based on the contents of the old format files, which were left behind by the Cisco IOS XR Software Release 3.3.1 (or earlier release). Included in the files, which are created in this way, are those that contain the persistent copy of the router configuration that is used to restore the running configuration. The history of changes to the running configuration, however, is not recreated. This means that after the upgrade, it is not possible to view or roll back any changes previously contained in the configuration history.

If the router is subsequently downgraded back to Cisco IOS XR Software Release 3.3.1 (or earlier release), the default behavior is to restore the router running configuration by using the old format configuration files left behind from the last time Cisco IOS XR Software Release 3.3.1 (or earlier release) was running. This means that any changes to the running configuration made while Cisco IOS XR Software Release 3.3.3 was running are lost.

To prevent this from happening, the following command is used before performing the downgrade operation:

delete disk0:/config/running/commitdb/*

Note disk0: is substituted with the appropriate device name if an alternate boot device is being used.


This forces the Cisco IOS XR Software Release 3.3.1 (or earlier release) to create old format configuration files based on the contents of the new-format files left behind by Cisco IOS XR Software Release 3.3.3. Included in the files, which are created in this way, are those that contain the persistent copy of the router configuration that is used to restore the running configuration. The history of changes to the running configuration, however, is not recreated. This means that after the downgrade, it is not possible to view or roll back any changes previously contained in the configuration history.

If the router is again upgraded to Cisco IOS XR Software Release 3.3.3, the default behavior is to restore the router running configuration by using the new format configuration files left behind from the last time Cisco IOS XR Software Release 3.3.3 was running. This means that any changes to the running configuration made while Cisco IOS XR Software Release 3.3.3 (or earlier release) was running is lost.

To prevent this from happening, the following command is used before performing the repeat upgrade operation:

delete disk0:/config/lr/running/commitdb/*

Note disk0: is substituted with the appropriate device name if an alternate boot device is being used.


This forces the Cisco IOS XR Software Release 3.3.3 to create new format configuration files that are based on the contents of the old format files left behind by Cisco IOS XR Software Release 3.3.3 (or earlier release), during the first upgrade.

Turbobooting PRP Cards

This section contains instructions for turbobooting the PRP cards. The first series of steps apply when disk0: is the target. Instructions for using compact flash as the target come after these steps.


Note 1-GB compact flash is supported only with Cisco IOS XR Software Release 3.3.0 and later releases. Therefore, if you are upgrading from a release earlier than Release 3.3.0, you must continue to use disk0.

In the current release, only the FLASH-PRP2-1G compact flash is supported.


Turbobooting to Disk0:

Take the following steps when disk0: is the target.


Step 1 Boot the DSC RP with the composite image:

rommon> confreg 0x0
rommon> reset
rommon> unset BOOT
rommon> TURBOBOOT=on,disk0
rommon> sync
rommon> boot tftp://../c12k-mini.vm-3.3.3
 
   

The confreg step ensures that ROMMON does not autoboot from previously installed software.

The following line shows TURBOBOOT ROMMON variable usage:

TURBOBOOT=option1, option2, ...

Available options:

on

Turns Turboboot procedure on.

disk0, disk1, compactflash

Specifies the target boot device (default: disk0).

clean, format

Cleans (deletes any package directories or files) or formats target device before installing the software.


For example:

rommon> TURBOBOOT=on,disk0,format
rommon> sync
 
   

Step 2 Without waiting, netboot all other RPs with the MBI:

rommon> unset TURBOBOOT
rommon> unset BOOT
rommon> sync
rommon> boot tftp://../mbiprp-rp.vm-3.3.3

Note The TURBOBOOT variable should not be set on other RPs.


Step 3 Wait for the Turboboot process to finish (approximately 30 minutes).

The DSC netboots (image is loaded in memory).

Target boot devices are cleaned and formatted (depending on the TURBOBOOT option).

Software is copied from memory to the target boot device.

All RPs that are found in MBI running state by the DSC are turbobooted.

ROMMON variables (confreg and BOOT) are set appropriately.

When all cards are done, the DSC resets and reloads the software from disk.

All other RP cards self-reset and reload from disk.


Turbobooting to Compact Flash

The steps in this section apply to turbobooting to compact flash.


Note 1-GB compact flash is supported only with Cisco IOS XR Software Release 3.3.0 and later releases. Therefore, if you are upgrading from a release earlier than Release 3.3.0, you must continue to use disk0.

In the current release, only the FLASH-PRP2-1G compact flash is supported.



Step 1 Boot the DSC RP with the composite image:

rommon> confreg 0x0
rommon> reset
rommon> unset BOOT
rommon> TURBOBOOT=on,compactflash
rommon> IOX_CONFIG_MEDIUM=compactflash:/config/
rommon> sync
rommon> boot tftp://../c12k-mini.vm-3.3.3
 
   

Step 2 Without waiting, netboot all other RPs with the MBI:

rommon> unset TURBOBOOT
rommon> unset BOOT
rommon> IOX_CONFIG_MEDIUM=compactflash:/config/
rommon> sync
rommon> boot tftp://../mbiprp-rp.vm-3.3.3

Note The TURBOBOOT variable should not be set on other RPs.


Step 3 Wait for the Turboboot process to finish (approximately 30 minutes).

The DSC netboots (image is loaded in memory).

Target boot devices are cleaned and formatted (depending on the TURBOBOOT option).

Software is copied from memory to the target boot device.

All RPs that are found in MBI Running state by the DSC are turbobooted.

ROMMON variables (confreg and BOOT) are set appropriately.

When all cards are done, the DSC resets and reloads the software from the disk.

All other RP cards self-reset and reload from disk.


Installing Optional Packages

The events in Step 3 in the preceding section must occur before you begin the steps in this section.


Note All installation commands must be performed in admin EXEC mode.



Note If the system was turbobooted to compactflash:, disk0: shows compactflash:.


.

Action/Description
Sample Commands

Install optional packages.

RP/0/0/CPU0(admin)# install add 
tftp://../c12k-mpls.pie-3.3.3 

RP/0/0/CPU0(admin)# install activate 
disk0:/c12k-mpls-3.3.3

For automated execution, we recommend that you use the synchronous option for all package/PIE activation or deactivation commands. This approach ensures that the console prompt does not come back up until the system finishes the package/PIE activations or deactivations.

Troubleshooting

For information on troubleshooting Cisco IOS XR software, see Cisco IOS XR Getting Started Guide.

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 the release notes with the hardware and software user documentation found at applicable URLs:

Hardware Documents

Software 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. See the About Cisco IOS XR Software Documentation for Release 3.3.0 for a list of Cisco IOS XR software documentation for Release 3.3.3.

You can find the most current software documentation at the following URL:

http://www.cisco.com/univercd/cc/td/doc/product/ioxsoft/iox33/index.htm

Obtaining Documentation, Obtaining Support, and Security Guidelines

For information about how to obtain documentation or support, on how to provide documentation feedback, for security guidelines, as well as on recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

This document is to be used in conjunction with the documents listed in the "Related Documentation" section.