Guest

Cisco IOS XR Software (End-of-Sale)

Release Notes for Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2

  • Viewing Options

  • PDF (670.6 KB)
  • Feedback
Release Notes for Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2

Table Of Contents

Release Notes for Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2

Key Changes from Previous Releases in Cisco IOS XR Release 3.9.2

Contents

Introduction

System Requirements

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Other Firmware Support

Cisco IOS Image Level and Boot Helper Migration Requirements

Minimum Firmware Requirement

RMA Card Firmware Upgrade Procedure

Determining Your Software Version

New Features in Cisco IOS XR Software Release 3.9.2

PBTS Default Class Enhancement

policy-class

Hitless DS-TE Migration

Unequal Bandwidth for Link Bundles

MPLS TE Auto-Bandwidth with Link Bundles

auto-bw underflow

show mpls traffic-eng tunnels auto-bw

Bundle Interface Re-size Triggers Immediate Preemption and RSVP

mpls traffic-eng link-management timers preemption-delay

New Features in Cisco IOS XR Software Release 3.9.1

New Software Features Supported on all Platforms

Cisco XR 12000 Series Router-Specific Software Features

New Hardware Features for the Cisco XR 12000 Series Router

Important Notes

Minimum Flash Disk Requirements When Upgrading to Release 3.9.2

Caveats

Resolved Release 3.9.2 Cisco IOS XR Software Caveats

Open Release 3.9.2 Cisco IOS XR Software Caveats

Open Release 3.9.2 Caveats Specific to the Cisco XR 12000 Series Router

Upgrading Cisco IOS XR Software

Troubleshooting

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2


April 16, 2013

Cisco IOS XR Software Release 3.9.2

Text Part Number OL-23380-02

These release notes describe the features provided in the Cisco IOS XR Software Release 3.9.2 for the Cisco XR 12000 Series Router and are updated as needed.


Note For information on the Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.9.2, see the "New Features in Cisco IOS XR Software Release 3.9.2" section.


You can find the most current Cisco IOS XR software documentation at

http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html

These electronic documents may contain updates and modifications. For more information on obtaining Cisco documentation, see the "Obtaining Documentation and Submitting a Service Request".

For a list of software caveats that apply to Cisco IOS XR Software Release 3.9.2, see the "Caveats" section. The caveats are updated for every release and are described at www.cisco.com.

We recommend that you view the field notices for this release located at the following URL to see if your software or hardware platforms are affected:

http://www.cisco.com/public/support/tac/fn_index.html

Key Changes from Previous Releases in Cisco IOS XR Release 3.9.2

Cisco IOS XR Software Release 3.9.2 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB or 4 GB before upgrading to Cisco IOS XR Software Release 3.9.2. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.2" section.

Contents

These release notes contain the following sections:

Introduction

System Requirements

Determining Your Software Version

New Features in Cisco IOS XR Software Release 3.9.2

New Features in Cisco IOS XR Software Release 3.9.1

Important Notes

Minimum Flash Disk Requirements When Upgrading to Release 3.9.2

Caveats

Upgrading Cisco IOS XR Software

Troubleshooting

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

Cisco IOS XRsoftware is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.

Cisco IOS XR software running on the Cisco XR 12000 Series Router provides the following features and benefits:

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

BGP Prefix Independent ConvergenceProvides the ability to converge BGP routes within sub seconds instead of multiple seconds. The Forwarding Information Base (FIB) is updated, independent of a prefix, to converge multiple 100K BGP routes with the occurrence of a single failure. This convergence is applicable to both core and edge failures and with or with out MPLS. This fast convergence innovation is unique to Cisco IOS XR software.

Multiprotocol Label Switching (MPLS)Supports MPLS protocols, including Traffic Engineering (TE), Resource Reservation Protocol (RSVP), Label Distribution Protocol (LDP), Virtual Private LAN Service (VPLS), and Layer 3 Virtual Private Network (L3VPN).

Multicast—Provides comprehensive IP Multicast software including Source Specific Multicast (SSM) and Protocol Independent Multicast (PIM) in Sparse Mode only.

Quality of Service (QoS)—Supports QoS mechanisms including policing, marking, queuing, random and hard traffic dropping, and shaping. Additionally, Cisco IOS XR software also supports modular QoS command-line interface (MQC). MQC is used to configure QoS features.

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

Security—Provides comprehensive network security features including access control lists (ACLs); routing authentications; Authentication, Authorization, and Accounting (AAA)/Terminal Access Controller Access Control System (TACACS+); Secure Shell (SSH); Management Plane Protection (MPP) for management plane security; and Simple Network Management Protocol version3 (SNMPv3). Control plane protections integrated into line card Application-Specific Integrated Circuits (ASICs) include Generalized TTL Security Mechanism (GTSM), RFC 3682, and Dynamic Control Plane Protection (DCPP).

Craft Works Interface (CWI)—CWI is a client-side application used to configure and manage Cisco routers. 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. The 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, nonstop routing for ISIS, LDP, BGP, and OSPF, and nonstop forwarding (NSF).

Multicast service delivery in SP NGN—MVPNv4 support carries multicast traffic over an ISP MPLS core network.

IPv6 Provider Edge Router support for IPv6 applications—Delivers IPv6 traffic over an IPv4/MPLS core with IPv6 provider edge router (6PE) support.

IPv6 VPN over MPLS (6VPE) support—Delivers IPv6 VPN over MPLS (IPv6) VPN traffic over an IPv4 or MPLS core with 6VPE support.

6VPE over L2TPv3 support—Delivers IPv6 VPN traffic over L2TPv3 core with 6VPE support. This feature is also available on Cisco IOS software.

Enhanced core competencies:

IP fast convergence with Fast Reroute (FRR) support for Intermediate System-to-Intermediate System (IS-IS) and OSPF

Traffic engineering support for unequal load balancing

Path Computation Element (PCE) capability for traffic engineering

L2TPv3 Tunneling Mechanism—Service Providers who do not use MPLS in the core, but want to offer VPN services can use the L2TPv3 tunneling mechanism. This feature support includes IPv4 (VPNv4) and IPv6 (6VPE) VPN services using L2TPv3 encapsulation. The L2TPv3 packet is encapsulated in an IPv4 delivery header and is carried across an IPv4 backbone. VPN prefixes are advertised with BGP labels and resolved over L2TPv3 tunnels. This feature is supported only on the Cisco XR 12000 Series Router.

For more information about new features provided on the Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2, see the "New Features in Cisco IOS XR Software Release 3.9.2" section in this document.

System Requirements

This section describes the system requirements for Cisco IOS XR Software Release 3.9.2 supported on the Cisco XR 12000 Series Router. The system requirements include the following information:

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Other Firmware Support

Cisco IOS Image Level and Boot Helper Migration Requirements

Minimum Firmware Requirement

RMA Card Firmware Upgrade Procedure

To determine the software versions or levels of your current system, see the "Determining Your Software Version" section.

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.9.2 features.

Table 1 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for Cisco IOS XR Software Release 3.9.2, supported on the Cisco XR 12000 Series Router.

Table 1 Cisco XR 12000 Series Router Supported Feature Set (Cisco IOS XR Software
Release 3.9.2 PIE Files) 

Feature Set
Filename
Description
Composite Package

Cisco IOS XR IP Unicast Routing Core Bundle

c12k-mini.pie-3.9.2

Contains the required core packages, including OS, Admin, Base, Forwarding, Routing, SNMP Agent, and Alarm Correlation.

Cisco IOS XR IP Unicast Routing Core Bundle

c12k-mini.vm-3.9.2

Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.

Optional Individual Packages 1

Cisco IOS XR Manageability Package

c12k-mgbl.pie-3.9.2

CORBA2 agent, XML Parser, and HTTP server packages.

Cisco IOS XR MPLS Package

c12k-mpls.pie-3.9.2

MPLS-TE,3 LDP, 4 MPLS Forwarding, MPLS OAM,5 LMP,6 OUNI,7 and RSVP.8

Cisco IOS XR Multicast Package

c12k-mcast.pie-3.9.2

Multicast Routing Protocols (PIM,9 MSDP,10 IGMP,11 Auto-RP, BSR12 ), Tools (SAP, MTrace, MRINFO), and Infrastructure (MRIB,13 MURIB,14 MFWD)15 .

Cisco IOS XR Security Package

c12k-k9sec.pie-3.9.2

Support for Encryption, Decryption, IPSec16 , SSH,17 SSL,18 and PKI.19
Software based IPSec support: maximum of 500 tunnels

Cisco IOS XR Standby RP Boot Image

mbiprp-rp.vm-3.9.2

Support for booting the Standby RP on a Cisco XR 12000 Series Router.

Cisco IOS XR Documentation Package

The documentation package is not supported in Cisco IOS XR Software Release 3.9.2.

Please refer to the Cisco XR 12000 Series Router command reference documentation located at the following URL:

http://www.cisco.com/en/US/products/ps6342/prod_command_reference_list.html

Cisco IOS XR FPD Package

c12k-fpd.pie-3.9.2

Firmware for shared port adapters (SPA) and for fixed port line cards supported in Cisco IOS XR.

Cisco IOS XR Diagnostic Package

c12k-diags.pie-3.9.2

Diagnostic utilities for Cisco IOS XR routers.

Cisco IOS XR Documentation Package

c12k-doc.pie-3.9.2

.man pages for Cisco IOS XR software on the Cisco XR 12000 Series Router chassis.

1 Packages are installed individually

2 Common Object Request Broker Architecture

3 MPLS Traffic Engineering

4 Label Distribution Protocol

5 Operations, Administration, and Maintenance

6 Link Manager Protocol

7 Optical User Network Interface

8 Resource Reservation Protocol

9 Protocol Independent Multicast

10 Multicast Source Discovery Protocol

11 Internet Group Management Protocol

12 Bootstrap router

13 Multicast Routing Information Base

14 Multicast-Unicast RIB

15 Multicast forwarding

16 IP Security

17 Secure Shell

18 Secure Socket Layer

19 Physical layer interface module


Table 2 lists the Cisco XR 12000 Series Router TAR files.

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

Feature Set
Filename
Description

Cisco IOS XR IP/MPLS Core Software

XR12000-iosxr-3.9.2.tar

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.9.2.tar

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 media in which the software image or configuration is stored, the router may become unstable and fail.

The minimum memory requirements for a Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.9.2 consist of the following:

2-GB route memory on performance route processor 2 (PRP-2)


Note 4-GB route memory on PRP-2 is required if it is planned to scale to more than 64K IPsec tunnels per chassis.


2-GB or greater ATA flash storage on PRP-2

4-GB route memory on performance route processor 3 (PRP-3)

2-GB or greater Compact flash storage on PRP-3

1-GB line card route memory on all Engine 3 line cards

1-GB line card memory on Engine 5-based SPA interface processor (SIP-600)

The default route memory on the 12000-SIP-600 is 1GB

2-GB line card memory on all Engine 5-based SPA interface processors (SIPs)

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


Note The performance route processor 1 (PRP-1) is not supported in production environments.


2-GB PCMCIA Flash Disk


Note Cisco IOS XR Software Release 3.9.2 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB before upgrading to Cisco IOS XR Software Release 3.9.2. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.2" section.


Hardware Supported

All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.

Table 3 lists the supported hardware components on the Cisco XR 12000 Series Router and the minimum required software versions. For more information, see the "Determining Your Software Version" section.

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

Component
Part Number
Support from Version
Cisco XR 12000 Series Router Series Router Systems
   

Cisco XR 12000 Series 4-slot chassis

XR-12000/4

3.3

Cisco XR 12000 Series 6-slot chassis

XR-12000/6

3.3

Cisco XR 12000 Series 10-slot chassis

XR-12000/10

3.3

Cisco XR 12000 Series 16-slot chassis

XR-12000/16

3.3

Cisco XR 12000 Series Router Chassis Hardware

4-slot chassis & backplane, 1 Blower, 2 AC

12000/4-AC

3.3

4-slot chassis & backplane, 1 Blower, 2 DC

12000/4-DC

3.3

6-slot chassis & backplane, 2 Alarm, 1 Blower, 2 AC

12000/6-AC

3.3

6-slot chassis & backplane, 2 Alarm, 1 Blower, 2 DC

12000/6-DC

3.3

10-slot chassis & backplane, 2 Alarm, 1 Blower, 2 AC

12000/10-AC

3.3

10-slot chassis & backplane, 2 Alarm, 1 Blower, 2 DC

12000/10-DC

3.3

16-slot chassis & backplane, 2 Alarm, 2 Blower, 3 AC

12000/16-AC3

3.3

16-slot chassis & backplane, 2 Alarm, 2 Blower, 4 DC

12000/16-DC

3.3

16-slot chassis & backplane, 2 Alarm, 2 Blower, 4 AC

12000/16-AC4

3.3

Cisco XR12000 16-slots; 2 Alarms, Advanced 2 Blowers, up to 8 DC

12000E/16-DC

3.8

Cisco XR12000 16-slots; 2 Alarms, Advanced 2 Blowers, up to 8 AC

12000E/16-AC

3.8

Cisco XR 12000 Series Router Fabric Hardware

Enhanced 20 Gbps Fabric & Alarm card for Cisco 12004

12004E/20

3.6

Enhanced 80 Gbps Fabric & Alarm card for Cisco 12404

12404E/80

3.6

Enhanced 30 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12006

12006E/30

3.6

Enhanced 120 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12406

12406E/120

3.6

Enhanced 50 Gbps Fabric (2xCSC and 5xSFC) for Cisco 12010

12010E/50

3.5.2

Enhanced 200 Gbps Fabric (2xCSC and 5xSFC) for Cisco 12410

12410E/200

3.5.2

Enhanced 800 Gbps Fabric (2xCSC and 5xSFC) for Cisco 12810

12810E/800

3.4

Enhanced 80 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12016

12016E/80

3.5.2

Enhanced 320 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12416

12416E/320

3.5.2

Enhanced 1280 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12816

12816E/1280

3.4

80 Gbps Fabric & Alarm card for Cisco 12404

12404/80

3.3

30 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12006

12006/30

3.3

120 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12406

12406/120

3.3

50 Gbps Fabric (2xCSC and 5xSFC) for Cisco 12010

12010/50

3.3

200 Gbps Fabric (2xCSC and 5xSFC) for Cisco 12410

12410/200

3.3

80 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12016

12016/80

3.3

320 Gbps Fabric (2xCSC and 3xSFC) for Cisco 12416

12416/320

3.3

Cisco XR 12000 Series Route Processor Hardware

Cisco XR 12000 Series Performance Route Processor 2

PRP-2

3.2

Cisco XR 12000 Series Performance Route Processor 3

PRP-3

3.8

Cisco XR 12000 Series 40 GB Hard Drive Option

HD-PRP2-40G

3.2

Cisco XR 12000 Series PRP-3 80G Hard Drive

HD-PRP3

3.8

Cisco XR 12000 Series General Chassis Hardware

Cisco XR 12000 Series PCMCIA Flash Disk 1 GB

MEM-FD1G

3.2

Cisco XR 12000 Series PCMCIA Flash Disk 2 GB

MEM-FD2G

3.2

Cisco XR 12000 Series PCMCIA Flash Disk 4 GB

MEM-FD4G

3.8

Cisco XR 12000 Series PRP-3 2GB Compact Flash

FLASH-PRP3-2G

3.8

Cisco XR 12000 Series PRP-3 4GB Compact Flash

FLASH-PRP3-4G

3.8

Cisco XR 12000 Series PRP-3 4GB Memory (2X2GB DIMM)

MEM-PRP3-4G

3.8

Cisco XR 12000 Series PRP-3 8GB Memory (2X4GB DIMM)

MEM-PRP3-8G

3.8

Cisco XR 12000 Series SPA Interface Processor Hardware

Multirate 2.5G IP Services Engine (Modular)

12000-SIP-401

3.3

Multirate 5G IP Services Engine (Modular)

12000-SIP-501

3.3

Multirate 10G IP Services Engine (Modular)

12000-SIP-601

3.3

Cisco XR 12000 Series SPA Interface Processor 10G

12000-SIP-600

3.2

Cisco XR 12000 Series Router SONET Interface Modules and SPAs

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

4OC12X/POS-I-SC-B

3.2

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

4OC12X/POS-M-SC-B

3.2

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

16OC3X/POS-M-MJ-B

3.2

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

16OC3X/POS-I-LC-B

3.2

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

8OC3X/POS-MM-MJ-B

3.2

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

8OC3X/POS-IR-LC-B

3.2

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

4OC3X/POS-MM-MJ-B

3.2

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

4OC3X/POS-IR-LC-B

3.2

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

4OC3X/POS-LR-LC-B

3.2

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

OC48X/POS-SR-SC

3.2

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

OC48X/POS-LR-SC

3.2

Cisco XR 12000 Series 4-Port OC-3c/STM-1c ATM ISE Line Card, multimode

4OC3X/ATM-MM-SC

3.4

Cisco XR 12000 Series 4-Port OC-3c/STM-1c ATM ISE Line Card, single-mode

4OC3X/ATM-IR-SC

3.4

Cisco XR 12000 Series 4-port OC-12/STM-4 ATM multimode ISE line card with SC connector

4OC12X/ATM-MM-SC

3.4

Cisco XR 12000 Series 4-port OC-12/STM-4 ATM single-mode, intermediate-reach ISE line card with SC Connector

4OC12X/ATM-IR-SC

3.4

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

SPA-OC192POS-VSR

3.3

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

SPA-OC192POS-LR

3.2

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

SPA-OC192POS-XFP

3.2

2-Port OC-48/STM16 POS/RPR Shared Port Adapters

SPA-2XOC48POS/RPR

3.3

1-Port Channelized OC-12/DS0 Shared Port Adapters

SPA-1XCHOC12/DS0

3.5

1-Port Channelized STM-1/OC-3 to DS0 Shared Port Adapter

SPA-1XCHSTM1/OC3

3.5

1-Port OC-48c/STM-16 POS/RPR Shared Port Adapter

SPA-1XOC48POS/RPR

3.5

2-Port OC-12c/STM-4 POS Shared Port Adapter

SPA-2XOC12-POS

3.5

4-Port OC-12c/STM-4 POS Shared Port Adapter

SPA-4XOC12-POS

3.5

4-Port OC-3c/STM-1 POS Shared Port Adapter

SPA-4XOC3-POS-V2

3.5

8-Port OC-12c/STM-4 POS Shared Port Adapter

SPA-8XOC12-POS

3.5

8-Port OC-3c/STM-1 POS Shared Port Adapter

SPA-8XOC3-POS

3.5

Cisco 8-Port Channelized T1/E1 Shared Port Adapter

SPA-8XCHT1/E1

3.6

Cisco 1-Port Channelized OC-48/DS3 Optical Packet Processor Shared Port Adapter

SPA-1XCHOC48/DS3

3.6

1-Port Clear Channel OC-3 ATM SPA

SPA-1XOC3-ATM-V2

3.7

3-Port Clear Channel OC-3 ATM SPA

SPA-3XOC3-ATM-V2

3.7

1-Port Clear Channel OC-12 ATM SPA

SPA-1XOC12-ATM-V2

3.7

2-Port Channelized T3/E3 ATM CEoP SPA

SPA-2CHT3-CE-ATM

3.7

Ethernet Interface Modules and SPAs

Cisco XR 12000 Series 4xGE with SFP optics

4GE-SFP-LC

3.2

Cisco 5-Port Gigabit Ethernet Shared Port Adapter, Version 2

SPA-5X1GE-V2

3.4

Cisco 8-Port Gigabit Ethernet Shared Port Adapter, Version 2

SPA-8X1GE-V2

3.4

Cisco 8-Port 10BASE-T/100BASE-TX Fast Ethernet Shared Port Adapter, Version 2

SPA-8X1FE-TX-V2

3.4

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

SPA-8XFE-TX

3.3

Cisco 10-Port Gigabit Ethernet Shared Port Adapter, Version 2

SPA-10X1GE-V2

3.4

Cisco 1-Port Ten Gigabit Ethernet Shared Port Adapter, Version 2

SPA-1X10GE-L-V2

3.4

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

SPA-5X1GE

3.2

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

SPA-10X1GE

3.2

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

SPA-1XTENGE-XFP

3.2

Cisco 2-Port Gigabit Ethernet Shared Port Adapter, Version 2

SPA-2X1GE-V2

3.4.1

Cisco XR 12000 Series Router T3 and E3 Interface Modules and SPAs

2-port Channelized T3 to DS0 Shared Port Adapter

SPA-2XCT3/DS0

3.3

4-port Channelized T3 to DS0 Shared Port Adapter

SPA-4XCT3/DS0

3.3

2-port Clear Channel T3/E3 Shared Port Adapter

SPA-2XT3/E3

3.3

4-port Clear Channel T3/E3 Shared Port Adapter

SPA-4XT3/E3

3.3

Cisco XR 12000 Series Router Channelized Line Cards

Cisco 1-Port Channelized OC-48 line card

CHOC48/DS3-SR-SC

3.6

Cisco 1-Port Channelized OC-12 line card

CHOC12/DS1-SR-SC

3.8

Cisco 4-Port Channelized OC-12 line card

4CHOC12/DS3-I-SCB

3.8


Software Compatibility

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

Cisco XR 12004 Router

Cisco XR 12006 Router

Cisco XR 12010 Router

Cisco XR 12016 Router

Cisco  XR 12404 Router

Cisco XR 12406 Router

Cisco XR 12410 Router

Cisco XR 12416 Router

Cisco XR 12810 Router

Cisco XR 12816 Router

The following chassis are supported for an existing installed base:

Cisco 12008 Router

Cisco 12010 Router

Cisco 12012 Router


Note If you are running Cisco IOS XR software on a Cisco XR120xx system with SIP 600, 401, 501, or 601, you must upgrade the fabric. For ROMMON, MBUS, and Fabric Downloader versions, see the "Other Firmware Support" section.


Other Firmware Support

The Cisco XR 12000 Series Router supports the following firmware code:

Line cards (LCs)

For Engine 3 line card:

Maintenance Bus (MBUS) Agent Software-RAM version 04.7, ROM version 04.7

ROM Monitor version 17.1

Fabric Downloader - RAM version 10.0, ROM version 10.0 (The ROM version will be the same as the RAM version if upgraded.)

For Engine 5 line card:

Maintenance Bus (MBUS) Agent Software-RAM version 04.7, ROM version 04.7

ROM Monitor version 17.1

Fabric Downloader - RAM version 6.1, ROM version 6.1 (The ROM version will be the same as the RAM version if upgraded.)

Route processors (RPs)

For Performance Route Processor 2 (PRP-2):

Maintenance Bus (MBUS) Agent Software-RAM version 04.7, ROM version 04.7

ROM Monitor version 1.24

For Performance Route Processor 3 (PRP-3):

Maintenance Bus (MBUS) Agent Software-RAM version 04.7, ROM version 04.7

ROM Monitor version 1.4.0

Cisco IOS Image Level and Boot Helper Migration Requirements

If you are migrating from Cisco IOS to Cisco IOS XR software on the Cisco XR 12000 Series Router, you must have the following minimum Cisco IOS image level and Boothelper version to support Release 3.9.2:

Cisco IOS image—12.0(32)S

Cisco IOS Boothelper—12.0(32)S0a

If you have an earlier version of this system, you must upgrade to the minimum supported level before performing a migration. Otherwise, your migration fails. For more information, see the Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.

Minimum Firmware Requirement

After completing an RMA the newly-received linecard may not have appropriate IOS XR firmware installed.

Depending on the type of firmware that needs upgrading the symptoms can vary as follows:

ROMMON needs updating the linecard will not boot up

MBUS needs updating the linecard may fail to boot or keeps reloading

Fabric Loader needs updating the linecard will take long time to boot

FPD needs updating the linecard experiences packet corruption / drop


Note The FPD PIE has to be installed in order to upgrade to the latest FPD image. Refer to the Upgrading FPD on Cisco IOS XR Software chapter of the Cisco IOS XR System Management Command Reference for the Cisco XR 12000 Router online.


RMA Card Firmware Upgrade Procedure

To upgrade the fabric-downloader, ROMMON, Mbus, and current field-programmable device (FPD) image package on a single RMA linecard or on all modules installed in a router, use the upgrade all command in administration EXEC mode.

upgrade all location {node-id | all} [force]

Where location node-id specifies that all all firmware images (ROM, MBUS, Fabric Downloader and FPD) will be upgraded on the physical location of the line card received through RMA defined by the node-id argument. The node-id argument is entered in the rack/slot/module notation.

The upgrade all location all command upgrades all all firmware images (ROM, MBUS, Fabric Downloader and FPD) on all line cards (LCs) that are installed in the router.

For an RMA linecard firmware upgrade you'll want to use the upgrade all location node-id command.

The optional force parameter skips the version check and forces an upgrade.

The list of minimum supported firmware versions is available online in this matrix:

http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/XR12000SoftwareFirmwareCompatibilityMatrix.pdf

Links to PDF copies of the IOS XR Firmware Upgrade Guides are available online here:

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

Here's the link to the Cisco Systems IOS XR Firmware Upgrade Guide For CRS-1 and XR12000:

http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/IOSXRFirmwareUpgradeGuide.pdf

Refer to the Hardware Redundancy and Node Administration Commands on Cisco IOS XR Software chapter of the Cisco IOS XR System Management Command Reference for the Cisco XR 12000 Router for the upgrade all command syntax:

http://www.cisco.com/en/US/docs/routers/xr12000/software/xr12k_r3.9/system_management/command/reference/yr39xr12k_chapter7.html

Check the firmware needed by running the show fpd package command in admin mode.

 
   
RP/0/10/CPU0:MSE-PE1(admin)#show fpd package 
Mon Sep 27 08:48:43.012 PDT
 
   
=============================== ================================================
                                        Field Programmable Device Package
                                ================================================
                                                                 SW      Min Req   Min Req
Card Type            FPD Description            Type Subtype   Version   SW Ver    HW Vers
==================== ========================== ==== ======= =========== ========  =======
E3-OC12-ATM-4        Mickey FPGA                lc   fpga2   40971.00        0.0       0.0  
                     IOB FPGA                   lc   fpga3   41091.00        0.0       0.0  
                     SAF 0 FPGA                 lc   fpga4   45586.00        0.0       0.0  
                     Mouse FPGA                 lc   fpga1   40977.00        0.0       0.0  
------------------------------------------------------------------------------------------
E3-OC3-ATM-4         Mickey FPGA                lc   fpga2   40971.00        0.0       0.0  
                     IOB FPGA                   lc   fpga3   41091.00        0.0       0.0  
                     SAF 0 FPGA                 lc   fpga4   45586.00        0.0       0.0  
                     Mouse FPGA                 lc   fpga1   40977.00        0.0       0.0  
------------------------------------------------------------------------------------------
12000-ServEngCard    TREX FPGA                  lc   fpga2     162.45        0.0       0.0  
                     TREX FPGA                  lc   fpga1       0.41257     0.0       0.0  
------------------------------------------------------------------------------------------
12000-SIP            HABANERO FPGA              lc   fpga2     240.03        0.0       0.0  
                     JALAPENO FPGA              lc   fpga5     240.13        0.0       0.0  
                     JALAPENO FPGA              lc   fpga5     240.13        0.0       0.0  
                     JALAPENO FPGA              lc   fpga1     255.23        0.0       0.0  
------------------------------------------------------------------------------------------
E3-OC12-CH-1         Shiver FPGA                lc   fpga1       1.01        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-IPSEC-2G         Sequoia                    spa  fpga2       1.01        0.0       1.0  
                     Lodi                       spa  fpga1       1.22        0.0       1.0  
                     SPA PROM                   spa  rommon      1.01        0.0       1.0  
------------------------------------------------------------------------------------------
SPA-4XT3/E3          SPA E3 Subrate FPGA        spa  fpga2       1.04        0.0       0.0  
                     SPA T3 Subrate FPGA        spa  fpga3       1.04        0.0       0.0  
                     SPA I/O FPGA               spa  fpga1       1.01        0.0       0.0  
                     SPA ROMMON                 spa  rommon      2.12        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-2XT3/E3          SPA E3 Subrate FPGA        spa  fpga2       1.04        0.0       0.0  
                     SPA T3 Subrate FPGA        spa  fpga3       1.04        0.0       0.0  
                     SPA I/O FPGA               spa  fpga1       1.01        0.0       0.0  
                     SPA ROMMON                 spa  rommon      2.12        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-4XCT3/DS0 	SPA T3 Subrate FPGA        spa  fpga2       0.11        0.0       0.100
	SPA T3 Subrate FPGA        spa  fpga2       1.04        0.0       0.200
	SPA I/O FPGA               spa  fpga1       2.08        0.0       0.100
	SPA ROMMON                 spa  rommon      2.12        0.0       0.100
------------------------------------------------------------------------------------------
SPA-2XCT3/DS0 	SPA T3 Subrate FPGA        spa  fpga2       0.11        0.0       0.100
	SPA T3 Subrate FPGA        spa  fpga2       1.04        0.0       0.200
	SPA I/O FPGA               spa  fpga1       2.08        0.0       0.100
	SPA ROMMON                 spa  rommon      2.12        0.0       0.100
------------------------------------------------------------------------------------------
SPA-1XCHSTM1/OC3     SPA T3 Subrate FPGA        spa  fpga2       1.04        0.0       0.0  
                     SPA I/O FPGA               spa  fpga1       1.08        0.0       0.0  
                     SPA ROMMON                 spa  rommon      2.12        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-2CHT3-CE-ATM     SPA T3 Subrate FPGA        spa  fpga2       1.10        0.0       1.0  
                     SPA I/O FPGA               spa  fpga1       2.22        0.0       1.0  
                     SPA ROMMON                 spa  rommon      1.04        0.0       1.0  
------------------------------------------------------------------------------------------
SPA-IPSEC-2G-2       Sequoia                    spa  fpga2       1.01        0.0       1.0  
                     Lodi                       spa  fpga1       1.22        0.0       1.0  
                     SPA PROM                   spa  rommon      1.01        0.0       1.0  
------------------------------------------------------------------------------------------
SPA-1XCHOC48/DS3 	SPA I/O FPGA               spa  fpga2       1.00        0.0       0.49 
	SPA I/O FPGA               spa  fpga3       1.00        0.0       0.52 
	SPA I/O FPGA               spa  fpga1       1.36        0.0       0.49 
	SPA ROMMON                 spa  rommon      2.02        0.0       0.49 
------------------------------------------------------------------------------------------
SPA-1XCHOC12/DS0 	SPA I/O FPGA               spa  fpga2       1.00        0.0       0.49 
	SPA I/O FPGA               spa  fpga1       1.36        0.0       0.49 
	SPA ROMMON                 spa  rommon      2.02        0.0       0.49 
------------------------------------------------------------------------------------------
SPA-OC192POS         SPA FPGA swv1.2            spa  fpga1       1.02        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-8XOC12-POS       SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.5  
------------------------------------------------------------------------------------------
SPA-8XCHT1/E1 	SPA I/O FPGA               spa  fpga1       2.08        0.0       0.0  
	SPA ROMMON                 spa  rommon      2.12        0.0       0.140
------------------------------------------------------------------------------------------
SPA-OC192POS-XFP     SPA FPGA swv1.2            spa  fpga1       1.02        0.0       0.0  
                     SPA FPGA swv1.2 hwv2       spa  fpga1       1.02        0.0       2.0  
------------------------------------------------------------------------------------------
SPA-10X1GE           SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-5X1GE            SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-2XOC48POS/RPR    SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-1XTENGE-XFP      SPA FPGA swv1.9            spa  fpga1       1.09        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-8X1FE            SPA FPGA swv1.1            spa  fpga1       1.01        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-1XOC48POS/RPR    SPA FPGA swv1.2            spa  fpga1       1.02        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-8XOC3-POS        SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.5  
------------------------------------------------------------------------------------------
SPA-2XOC12-POS       SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.5  
------------------------------------------------------------------------------------------
SPA-4XOC12-POS       SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.5  
------------------------------------------------------------------------------------------
SPA-10X1GE-V2        SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-8X1GE-V2         SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-5X1GE-V2         SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-2X1GE-V2         SPA FPGA swv1.1            spa  fpga1       1.01        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-1X10GE-L-V2      SPA FPGA swv1.11           spa  fpga1       1.11        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-8X1FE-V2         SPA FPGA swv1.1            spa  fpga1       1.01        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-4XOC3-POS-V2     SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.5  
------------------------------------------------------------------------------------------
SPA-1XOC3-ATM-V2     TATM SPA IOFPGA            spa  fpga1       1.04        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-2XOC3-ATM-V2     SPA TATM IOFPGA            spa  fpga1       1.04        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-3XOC3-ATM-V2     SPA TATM IOFPGA            spa  fpga1       1.04        0.0       0.0  
------------------------------------------------------------------------------------------
SPA-1XOC12-ATM-V2    SPA TATM IOFPGA            spa  fpga1       1.04        0.0       0.0  
------------------------------------------------------------------------------------------

Determining Your Software Version

To determine the version of Cisco IOS XR software running on your router, log into the router and enter the show version command:


Step 1 Establish a Telnet session with the router.

Step 2 Enter the show version command from EXEC mode.

RP/0/7/CPU0:ios#sh version
Sat Sep 25 14:26:18.305 UTC
 
   
Cisco IOS XR Software, Version 3.9.2[00]
Copyright (c) 2010 by Cisco Systems, Inc.
 
   
ROM: ROMMON System Bootstrap, Version 1.4(0), RELEASE SOFTWARE
 
   
ios uptime is 7 hours, 30 minutes
System image file is "disk0:c12k-os-mbi-3.9.2/mbiprp-rp.vm"
 
   
cisco 12816/PRP (8641D) processor with 4194304K bytes of memory.
8641D processor at 1330Mhz, Revision 2.1
 
   
11 Cisco 12000 Series SPA Interface Processor-601/501/401
2 Cisco 12000 Series Performance Route Processor 3s
1 Cisco 12000 Series Performance Route Processor
4 Management Ethernet
44 PLIM_QOS
3 TenGigE
20 GigabitEthernet/IEEE 802.3 interface(s)
15 SONET/SDH
6 Packet over SONET/SDH
5 MgmtMultilink
8 FastEthernet
 
   
RP/0/7/CPU0:ios#show install active summumary
Sat Sep 25 14:26:33.561 UTC
  Active Packages:
    disk0:c12k-doc-3.9.2
    disk0:c12k-fpd-3.9.2
    disk0:c12k-diags-3.9.2
    disk0:c12k-k9sec-3.9.2
    disk0:c12k-mgbl-3.9.2
    disk0:c12k-mcast-3.9.2
    disk0:c12k-mpls-3.9.2
    disk0:c12k-mini-3.9.2

New Features in Cisco IOS XR Software Release 3.9.2

PBTS Default Class Enhancement

Policy Based Tunnel Selection (PBTS) directs traffic into TE tunnels based on incoming packets TOS/EXP bits.

Add a new class called "default" such that the user can configure a tunnel of class (1-7 or default).

We can configure more than 1 default tunnel.

Similar to other classes of tunnels, the control plane can pick up to 8 default tunnels to carry default traffic.

The forwarding plane applies the same load-balancing logic on the default tunnels such that default traffic load is shared over them.

Default tunnels will not be used to forward traffic if each class of traffic is served by at least one tunnels of the respective class.

A tunnel is still implicitly assigned to class 0 if the tunnel is not configured with a specific class.

Tunnels of class 0 are no longer to serve as default tunnel by default.

The lowest class tunnels will be assigned to carry default traffic only if no default tunnel is available for forwarding.

LDP/IGP paths will be assigned to the new default class. LDP/IGP no longer statically associates to class 0 in the platforms which support the new enhancement.

Restrictions

The class 0 tunnel is no longer the default tunnel. There is a new default class which does not associate with any of existing classes 0 to 7. For a class of traffic that does not have a respective class tunnel to serve it, the forwarding plane will use the available default tunnels and IGP/LDP paths to carry that class of traffic.

The new behavior takes effective only when the control plan resolves a prefix to use at least one default tunnel to forward traffic. In case a prefix is resolved to not use any default tunnel to forward traffic, it will fall back to the existing behavior. The lowest class tunnels will be used to serve as default tunnels. The class 0 tunnels will be used as default tunnels if no default tunnel is configured. In this case, we provide the backward compatibility to customers who keep using the existing configurations.

Configuration

Command to configure policy-class for PBTS

RP/0/RP1/CPU0:#configure 
RP/0/RP1/CPU0:(config)#interface tunnel-te 18
RP/0/RP1/CPU0:(config-if)#policy-class ?
  <1-7>           Tunnel policy class
  <default>       Default tunnel policy class
RP/0/RP1/CPU0:(config-if)#policy-class default
RP/0/RP1/CPU0:(config-if)#commit

Configuration example with PBTS enabled

RP/0/RP1/CPU0:(config)#interface tunnel-te 280 
RP/0/RP1/CPU0:(config)#policy-class default 
 
   

For more information about Policy Based Tunnel Selection, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 docs:

Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9

and IOS XR MPLS Configuration Guide

Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.

policy-class

To configure policy-based tunnel selection (PBTS) to direct traffic into specific TE tunnels, use the policy-class command in interface configuration mode. To disable this feature, use the no form of this command.

policy-class [<1-7> <default>]

no policy-class

Syntax Description

1-7

Policy-class attribute to map the correct traffic class to this policy.

default

(Optional) Default tunnel policy class.


Defaults

The lowest class tunnels will be assigned to carry default traffic only if no default tunnel is available for forwarding.

Command Modes

CONFIG-IF

Command History

Release
Modification

Release 3.9.2

New parameter "default" added to the CLI for defining the default tunnel on the Cisco XR 12000 Series Router


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.

Use the policy-class command to enable policy-based tunnel selection (PBTS). See Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router for more information on PBTS.

To display the configured PBTS policy-class value, use the show mpls traffic-eng tunnels command.

To display information about PBTS configuration, use the show cef and show cef hardware commands.

Task ID
Task ID
Operations

mpls-te

read, write


Examples

The following is an example of how to configure a default policy-class tunnel.

RP/0/5/CPU0:PE22_C12406(config-if)#policy-class ?
  <1-7>    Tunnel policy class
  default  Default class for policy-based tunnel selection
  <cr>
RP/0/5/CPU0:PE22_C12406(config-if)#policy-class default
RP/0/5/CPU0:PE22_C12406(config-if)#show
Tue Jul 27 20:29:04.850 DST
interface tunnel-te2206
 policy-class default

Related Commands

Command
Description

interface tunnel-te

Configures an MPLS-TE tunnel interface.

show cef

Displays the IPv4 or IPv6 Cisco Express Forwarding table.

show cef hardware

Displays Cisco Express Forwarding IPv4 or IPv6 hardware status and configuration information.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.


Hitless DS-TE Migration

The IETF DS-TE migration is hitless, which means the DS-TE mode is changed to IETF, when the TE does not flap tunnels when the class type is set to 0. The priority value matches the TE-class index (for example, TE-class map 5 is set to class-type 0 and priority 5) for all TE-class maps.

Standard defined extensions are used for IGPs and RSVP signalling, and DS-TE in this mode interoperates with third-party equipment.

The IETF mode supports two bandwidth constraint models: the Russian Doll Model (RDM) and Maximum Allocation Model (MAM).

RDM is the default model.

Router advertises variable-length bandwidth constraints, max-reservable-bandwidth, and unreserved bandwidths in TE-classes.

Tunnels must have valid class-type and priority configured as per TE-class map in use; otherwise, tunnels remain down.

The TE-class map (a set of tunnel priority and class-type values) is enabled to interpret unreserved bandwidth values advertised in IGP; therefore, TE-class map must be identical on all nodes for TE tunnels to be successfully established.

For DS-TE to function properly, DS-TE modes must be configured identically on all MPLS-TE nodes.

If you need to change the DS-TE mode, you must bring down all tunnel interfaces and, after the change, you should flood the updated bandwidth values through the network.


Note Changing the DS-TE mode affects the entire LSR and can have a major impact on system performance when tunnels are torn down.


For more information about DS-TE Migration, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 docs:

Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9

and IOS XR MPLS Configuration Guide

Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.

Unequal Bandwidth for Link Bundles

Link Bundling is one of the mechanisms to increase available link bandwidth without hardware upgrading. A link bundle interface is a group of physical interfaces of the same media type which are aggregated together such that they are treated as a single link by high layer protocols and features.

Traffic sent to the bundle is distributed among the member links and collected again at the far end

Current Link Bundling implementation supports having all members in the link bundle of equal bandwidth. This Unequal Bandwidth for Link Bundles provides the ability to configure member links of different weights in a Link Bundle but only if the weight ratio amongst the members is 4:1.

Currently, all the interfaces in a Link Bundle need to have same bandwidth characteristic. This means an OC-3 POS link can be part of a bundle which is either having 0 or more OC-3 links but it cannot be part of bundle with either OC-12 or OC-48 links. Unequal bandwidth on LB will enable this by allowing links with different bandwidth characteristics to be part of the same bundle. This feature will allow 4:1 ratio in bandwidth characteristic of participating links in the same bundle, which means

Bundle with OC-3 links and OC-12 links will be allowed

Bundle with OC-12 links and OC-48 links will be allowed

Bundle with OC-3 links and OC-48 links will not be allowed

Bundle with 1-Gig links and 10-Gig links will not be allowed

Bundle with Gig and POS link will not be allowed

Bundle with 1-Gig links and 10-Gig links will not be allowed

Bundle with Gig and POS link will not be allowed

Hardware Limitations:

Only supported on POS interfaces.

Gig Link bundles do not support this feature.

Packet throughput on member links will not be as per the configured ratio (e.g 4:1). This is because the member link selection is based on IP Src / IP Dst hash calculation and therefore if a higher weight link is selected for a low pps IP stream and lower weight link is selected for a high pps IP stream then packet throughput over the member links would be skewed.

Configuration:

No new CLI is introduced with this feature.

MPLS TE Auto-Bandwidth with Link Bundles

Automatic Bandwidth adjustment for TE Tunnels feature provides the means to automatically adjust the bandwidth allocation for traffic engineering tunnels based on their measured traffic load. The configured bandwidth in the running configuration is changed due to the automatic bandwidth behavior.

If a number of consecutive bandwidth samples are greater than the underflow threshold (bandwidth percentage) and the minimum bandwidth configured, then a bandwidth application is updated immediately; instead of waiting for the end of the application period.

Prerequisites

Your network must support the following:

Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels

Cisco Express Forwarding

Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF)

MPLS TE must be configured on the interface and on the tunnels.

Restrictions

The automatic bandwidth adjustment feature treats each tunnel for which it has been enabled independently. That is, it adjusts the bandwidth for each such tunnel according to the adjustment frequency configured for the tunnel and the sampled output rate for the tunnel since the last adjustment without regard for any adjustments previously made or pending for other tunnels.

If a tunnel is brought down to calculate a new label switched path (LSP) because the LSP is not operational, the configured bandwidth is not saved. If the router is reloaded, the last saved automatic bandwidth value is used.

You cannot configure MPLS TE over the logical generic routing encapsulation (GRE) tunnel interface.

For more information about MPLS-TE Auto-Bandwidth, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 document,

Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9

and IOS XR MPLS Configuration Guide

Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.

auto-bw underflow

To configure the auto-bw underflow on a tunnel interface, use the auto-bw command to enter the MPLS-TE automatic bandwidth interface configuration mode. To disable the automatic bandwidth on that tunnel, use the no form of this command.

auto-bw underflow threshold <1-100> min <10-4294967295> limit <1-10>

no auto-bw

Syntax Description

underflow

Configuring the tunnel underflow detection

threshold

Set the bandwidth change percent to trigger an underflow

<1-100>

Bandwidth change percent to trigger an underflow

limit

Set the number of consecutive collections exceeding threshold

min

Set the bandwidth change value to trigger an underflow

<10-4294967295>

Bandwidth change value to trigger an underflow (kbps)

<1-10>

Number of consecutive collections exceeding threshold


Defaults

By default, automatic bandwidth is not enabled.

Command Modes

CONFIG-IF

Command History

Release
Modification

Release 3.9.2

New parameter "underflow" added to the CLI for defining auto-bw on the Cisco XR 12000 Series Router


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.

Use the auto-bw command to enter MPLS-TE automatic bandwidth interface configuration mode.

The auto-bw and load-share unequal commands should not be used together.

The load-share unequal command determines the load-share for a tunnel based on the bandwidth. However, the MPLS-TE automatic bandwidth feature changes the bandwidth. If you are configuring both the load-share unequal command and the MPLS-TE automatic bandwidth feature, we recommend that you specify an explicit load-share value configuration under each MPLS-TE automatic bandwidth tunnel.

The following automatic bandwidth scenarios are described:

If you configure the automatic bandwidth on a tunnel, the automatic bandwidth is enabled on that tunnel. If no other configuration is specified, defaults for the various parameters are used, the operation stops.

The automatic operation (for example, output rate collection) starts as soon as the automatic bandwidth is enabled on one tunnel. If automatic bandwidth is disabled from all tunnels, the operation stops.

If the output rate collection is already active when the automatic bandwidth is configured on a tunnel, the statistics collection for that tunnel starts at the next collection configuration.


Note Because the collection timer is already running, the first collection event for that tunnel happens in less than C minutes (for example, on an average of C/2 minutes).


Task ID
Task ID
Operations

mpls-te

read, write


Examples

The following example shows how to configure MPLS-TE automatic bandwidth underflow:

RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow 
  threshold  Set the bandwidth change percent to trigger an underflow
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 
  <1-100>  Bandwidth change percent to trigger an underflow
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 
  limit  Set the number of consecutive collections exceeding threshold
  min    Set the bandwidth change value to trigger an underflow
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 
  <10-4294967295>  Bandwidth change value to trigger an underflow (kbps)
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 100 
  limit  Set the number of consecutive collections exceeding threshold
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 100 limit 
  <1-10>  Number of consecutive collections exceeding threshold
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 100 limit 10 
  <cr>
 
   
RP/0/5/CPU0:PE22_C12406(config-if)#show
Wed Jul 28 14:58:27.957 DST
interface tunnel-te2066
 auto-bw
  underflow threshold 10 min 100 limit 10

Related Commands

Command
Description

adjustment-threshold (MPLS-TE)

Configures the tunnel-bandwidth change threshold to trigger an adjustment.

application (MPLS-TE)

Configures the application frequency, in minutes, for the applicable tunnel.

bw-limit (MPLS-TE)

Configures the minimum and maximum automatic bandwidth to set on a tunnel.

collect-bw-only (MPLS-TE)

Enables only the bandwidth collection without adjusting the automatic bandwidth.

interface tunnel-te

Configures an MPLS-TE tunnel interface.

overflow threshold (MPLS-TE)

Configures tunnel overflow detection.

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.


show mpls traffic-eng tunnels auto-bw

To display auto bandwidth information about MPLS-TE tunnels, use the show mpls traffic-eng tunnels auto-bw command in EXEC mode.

show mpls traffic-eng tunnels auto-bw

Syntax Description

This command has no arguments or keywords.

Defaults

No default behavior or values

Command Modes

EXEC

Command History

Release
Modification

Release 3.9.2

New "underflow threshold" parameter added to the CLI output to display underflow bandwidth statistics on the Cisco XR 12000 Series Router


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.

Task ID
Task ID
Operations

mpls-te

read


Examples

The following shows a sample output from the show mpls traffic-eng tunnels auto-bw command specifying the tunnel number in brief form:

RP/0/5/CPU0:PE22_C12406#show mpls traffic-eng tunnels auto-bw
Thu Jul 29 18:25:08.627 DST
Signalling Summary:
              LSP Tunnels Process:  running
                     RSVP Process:  running
                       Forwarding:  enabled
          Periodic reoptimization:  every 3600 seconds, next in 1438 seconds
           Periodic FRR Promotion:  every 300 seconds, next in 167 seconds
          Auto-bw enabled tunnels:  1
 
   
Name: tunnel-te2206  Destination: 10.6.6.6
  Status:
    Admin:    up Oper:   up   Path:  valid   Signalling: connected
 
   
    path option 1,  type dynamic  (Basis for Setup, path weight 3)
    Last Signalled Error: Wed Jul 28 03:01:33 2010
      Info: [22] PathErr(2,5)-(Admin, flow preempted) at 10.12.12.1
    G-PID: 0x0800 (derived from egress interface properties)
    Bandwidth Requested: 0 kbps  CT0
 
   
  Config Parameters:
    Bandwidth:    25000 kbps (CT0) Priority:  0  0 Affinity: 0x0/0xffff
    Metric Type: TE (default)
    AutoRoute:  enabled  LockDown: disabled   Policy class: not set
    Forwarding-Adjacency: disabled
    Loadshare:          0 equal loadshares
    Auto-bw: enabled
      Last BW Applied: 0 kbps CT0   BW Applications: 1
      Last Application Trigger: Underflow Condition
      Bandwidth Min/Max: 0-4294967295 kbps
      Application Frequency: 1440 min   Jitter: 0s   Time Left: 22h 36m 12s
      Collection Frequency: 5 min
      Samples Collected: 17   Next: 3m 52s
      Highest BW: 0 kbps   Underflow BW: 0 kbps
      Adjustment Threshold: 10%   10 kbps
      Overflow Detection disabled
      Underflow Threshold: 10%   100 kbps   Limit: 0/10   Underflow BW Applications: 1
    Fast Reroute: Enabled, Protection Desired: Any
    Path Protection: Not Enabled
  History:
    Tunnel has been up for: 1d15h (since Wed Jul 28 03:01:33 DST 2010)
    Current LSP:
      Uptime: 01:41:09 (since Thu Jul 29 16:44:00 DST 2010)
    Reopt. LSP:
      Last Failure:
        LSP not signalled, identical to the [CURRENT] LSP
        Date/Time: Thu Jul 29 16:49:07 DST 2010 [01:36:02 ago]
    Prior LSP:
      ID: path option 1 [59]
      Removal Trigger: reoptimization completed
 
   
  Path info (OSPF 100 area 0):
  Hop0: 10.222.4.2
  Hop1: 10.12.12.2
  Hop2: 10.12.12.1
  Hop3: 10.16.8.1
  Hop4: 10.16.8.6
  Hop5: 10.6.6.6
Displayed 1 (of 2) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads
 
   

Related Commands

Command
Description

show mpls traffic-eng tunnels

Displays information about MPLS-TE tunnels.


Bundle Interface Re-size Triggers Immediate Preemption and RSVP

For bundle interfaces, TE delays 60 secs before reacting to link capacity bandwidth reduction updates.

When enabling RSVP with 'bandwidth' on a bundle interface (75%), an individual member link failure will take 60 seconds for the router to realize the member is gone and resize the interface bandwidth.

When member links of a bundle fail successively leading to insufficient RSVP bandwidth on the bundle, tunnels are not immediately preempted. TE control waits for 60 seconds (default) for more member failures that may trigger FRR before preempting any tunnel. The link management preemption delay parameter allows the customer to configure the amount of time that tunnels stay in service before being preempted due to insuffiecient RSVP bandwidth on a bundle.

For more information about Bundle Interfaces, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 documents:

Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9

and IOS XR MPLS Configuration Guide

Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.

mpls traffic-eng link-management timers preemption-delay

To configure the preemption-delay on a tunnel interface, enter MPLS-TE mpls traffic-eng interface configuration mode and use the mpls traffic-eng link-management preemption-delay command. To disable the preemption-delay on that tunnel, use the no form of this command.

mpls traffic-eng link-management timers [preemption-delay bundle-capacity <1-300> ] [bandwith-hold <1-300>] [periodic-flooding <0-3600>]

Syntax Description

bandwidth-hold

Bandwidth hold timer

<1-300>

Bandwidth hold timer value (seconds)

periodic-flooding

Periodic flooding timer

<0-3600>

Periodic flooding value (seconds), minimum 30 seconds

preemption-delay

Delay LSP preemption

bundle-capacity

Bundle capacity change preemption delay timer

<1-300>

Bundle capacity change preemption timer value (seconds)


Defaults

There is no default value for this command.

Command Modes

CONFIG-IF

Command History

Release
Modification

Release 3.9.2

Added new parameter, preemption, to the CLI for defining link management timers on the Cisco XR 12000 Series Router


Usage Guidelines

To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.

Task ID
Task ID
Operations

mpls-te

read, write


Examples

The following example shows how to configure the preemption delay timer.

RP/0/5/CPU0:(config)#mpls traffic-eng link-management timers

RP/0/5/CPU0:(config)#$mpls traffic-eng link-management timers preemption

RP/0/5/CPU0:(config)#$mpls traffic-eng link-management timers preemption bundle-capacity

RP/0/5/CPU0:(config)#$mpls traffic-eng link-management timers preemption bundle-capacity 1

New Features in Cisco IOS XR Software Release 3.9.1

The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.9.1:

New Software Features Supported on all Platforms

Cisco XR 12000 Series Router-Specific Software Features

New Hardware Features for the Cisco XR 12000 Series Router


Note Cisco Session Border Controller (SBC) is not supported on any platform in Cisco IOS XR Software Release 3.9.1. Cisco IOS XR Software Release 3.7 is the last release that supports SBC.


New Software Features Supported on all Platforms

The following new software features in Cisco IOS XR Software Release 3.9.1 are supported on all platforms:

SSH Remote Command Execution

Non-default SSM Range

Cisco XR 12000 Series Router-Specific Software Features

The following new software feature was introduced in Cisco IOS XR Software Release 3.9.1 on the Cisco XR 12000 Series Router platform:

BFD over labelled path 1-hop iBGP

New Hardware Features for the Cisco XR 12000 Series Router

No new hardware features were introduced in Cisco IOS XR Software Release 3.9.1 on the Cisco XR 12000 Series Router.

For detailed information on the shared port adapters (SPAs) and SPA interface processors (SIPs), see the following documents:

Cisco XR 12000 Series Router SIP and SPA Hardware Installation Guide

Cisco Interface and Hardware Component Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9


Note Contact gsr-pm@cisco.com for hardware availability.


Important Notes

Default timestamp setting—The timestamp prompt that precedes console output is enabled by default in Cisco IOS XR Release 3.8. To disable the timestamp prompt, use the no service timestamp command. For more information, refer to the Cisco IOS XR System Management Command Reference for the Cisco XR 12000 Series Router.

From Cisco IOS XR Software Release 3.6.0, WRED statements are collapsed in that if different random-detect statements using the same match types (EXP, DSCP, Prec, and so forth) are entered with identical minimum and maximum threshold values, a single configuration line is shown in the output of show running config. This reduces the length of the configuration but creates a problem with backward compatibility with previous releases. In such a situation, on rollback, the QoS policy is rejected and must be manually entered again.

Configuration prior to Cisco IOS XR Software Release 3.6.0:

Policy-map wred_example
   Class class-default
       random-detect exp 0 384 packets 484 packets
       random-detect exp 1 384 packets 484 packets
       random-detect exp 2 384 packets 484 packets
       random-detect exp 3 484 packets 584 packets
       random-detect exp 4 484 packets 584 packets
       random-detect discard-class 0 384 packets 484 packets
      random-detect discard-class 1 384 packets 484 packets
      random-detect discard-class 2 484 packets 584 packets
      bandwidth remaining percent 20

Cisco IOS XR Software Release 3.6.0 and later releases:

policy-map wred_example
 class class-default
  random-detect exp 0,1,2 384 packets 484 packets
  random-detect exp 3,4 484 packets 584 packets
  random-detect discard-class 0,1 384 packets 484 packets
  random-detect discard-class 2 484 packets 584 packets
  bandwidth remaining percent 20
 !
 end-policy-map
!
end 
 
   

In Cisco IOS XR Software Release 3.6.0 and later releases, the implicitly assigned QoS class class-default must have at least 1 percent bandwidth made available to it. This can be done either by assigning at least 1 percent explicitly (bandwidth remaining percent 1) or by ensuring that the total bandwidth assigned to all other classes in the policy is a maximum of 99 percent, leaving 1 percent available for the class-default. A QoS policy that does not have any bandwidth for class-default is rejected when upgrading to Cisco IOS XR Software Release 3.6.0 or later releases.

Country-specific laws, regulations, and licences—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.

Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router—When migrating a Cisco XR 12000 Series Router from Cisco IOS to Cisco IOS XR software, follow the instructions provided in Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.

Card, fan controller, and RP removal—For all card removal and replacement (including fabric cards, line cards, fan controller, and RP) follow the instructions provided by Cisco to avoid impact to traffic. See the Cisco IOS XR Getting Started Guide for the Cisco XR 12000 Series Router for procedures.

Exceeding Cisco testing—If you intend to test beyond the combined maximum configuration tested and published by Cisco, contact your Cisco Technical Support representative to discuss how to engineer a large-scale configuration maximum for your purpose.

More power required for Cisco SIP line cards (SIP-401/501/600/601) on the Cisco XR 12000 Series Router—These line cards draw more power than previous generation 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. Before you insert a new card or remove a PEM, run the following command in admin mode:

RP/0/0/CPU0:router# admin
RP/0/0/CPU0:router# 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
---                  -----------                                        -----
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
 
   
 
   

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. It is your responsibility to determine your power budget for the chassis before making any changes to it. Exceeding the power budget may result in the PEM being overloaded and cards powering down due to insufficient power being provided.


Per-interface Internet Control Message Protocol (ICMP) disable feature is not supported on the Cisco XR 12000 Series Router.

Online Diagnostics is not supported on the Cisco XR 12000 Series Router—If you execute the diagnostic command, an error appears stating that there is no online diagnostics process running on the router.

The rp mgmtethernet forwarding command is not supported on the Cisco XR 12000 Series Router.

mpls traffic engineering igp-intact command—This command must be used only when policy based tunnel selection is configured for all tunnels originating on the device.

Minimum Flash Disk Requirements When Upgrading to Release 3.9.2

Cisco IOS XR Software Release 3.9.2 requires a 2-GB Flash Disk as a minimum. If your Cisco XR 12000 Series Router currently uses a 1-GB Flash Disk, you must upgrade it to 2-GB before upgrading to Cisco IOS XR Software Release 3.9.1. The PCMCIA 1-GB Flash Disk was the default size for the Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.6 and earlier.

In Cisco IOS XR Software Release 3.6 and later releases, disk partitioning is supported. Partitioning of a 2-GB disk is possible but not required. Partitioning of a 4-GB disk is required.

A 4-GB Flash Disk can be installed instead of the 2-GB for greater disk storage.

To upgrade from a 1-GB flash disk to a 2-GB or greater flash disk, refer to the Flash Disk Upgrade Tasks link on the followingCisco XR 12000 Series Router Installation and Upgrade URL:

http://www.cisco.com/en/US/products/ps6342/prod_installation_guides_list.html

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.

This section contains Release 3.9.2 and Release 3.9.1 caveats that are generic to the Cisco IOS XR software and those specific to the Cisco XR 12000 Series Router.

Resolved Release 3.9.2 Cisco IOS XR Software Caveats

CSCti62211

Basic Description:

BGP flaps due to unknown attribute

Symptom:

Cisco IOS XR Software contains a vulnerability in the Border Gateway Protocol (BGP) feature. The vulnerability manifests itself when a BGP peer announces a prefix with a specific, valid but unrecognized transitive attribute. On receipt of this prefix, the Cisco IOS XR device will corrupt the attribute before sending it to the neighboring devices. Neighboring devices that receive this corrupted update may reset the BGP peering session.

Conditions:

Affected devices running Cisco IOS XR Software corrupt the unrecognized attribute before sending to neighboring devices, but neighboring devices may be running operating systems other than Cisco IOS XR Software and may still reset the BGP peering session after receiving the corrupted update. This is per standards defining the operation of BGP.

Workaround:

No workaround. Cisco developed a fix that addresses this vulnerability and will be releasing free software maintenance upgrades (SMUs) progressively starting 28 August 2010.

A Security Advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100827-bgp.shtml

Open Release 3.9.2 Cisco IOS XR Software Caveats

The following open caveats apply to Cisco IOS XR software Release 3.9.2 and are not platform specific:

CSCtf93555

Basic Description:

CLI command not authorized to execute during persist time of EEM policy

Symptom:

After persist time start for eem policy user, CLI command failed to authorize.

Conditions:

When the TACACS server is down, persist time starts for the user credentials which registered for EEM policy. If the EEM policy gets triggered and opens a vty connection and try to execute any CLI while the TACACS server is down, it failed to authorize that command.

Workaround:

None.

Recovery:

Bring the TACACS server up.

CSCtd17516

Basic Description:

CLI over XML Configuration Fails

Symptom:

CLI over XML configuration request fails.

Conditions:

This happens when

- CLI command lines in XML request exceeds 200 lines or more

AND

- CLI commands are split internally and it happens to be split in middle of sub-mode.

Workaround:

- No need to use CLI over XML for config commands that already support XML natively.

- Split the commands into multiple requests so that command lines of each request are less than 200 lines.

Recovery:

None.

CSCta71930

Basic Description:

lpts_pa tracebacks after clear cef on line card

Symptom:

An error log is printed along with the traceback when a message send to BCDL agent fails.

Conditions:

The BCDL agent has gone down thus the message send is failing. This is a very rare scenario and would not happen under normal circumstances.

Workaround:

Not required, as BCDL will come up eventually.

Further Problem Description:

The error message is just to say that BCDL agent might have gone down. This would not cause an error in lpts as BDCL will eventually come up and the messages are sent again. The only caveat is that it might be some time before the messages are sent again. The solution would aim to put an upper bound on the resend time by having a retrying mechanism for the same.

CSCtg48346

Basic Description:

Standby RP not ready - ospf Waiting for primary node

Symptom:

The trigger for this issue is standby node is coming up and somebody trying to do some configuration from the active.

Conditions:

The consequence is that the new configuration might be lost and the impact would be depending on the new configuration. e.g., if the new configuration is to spawn new osfp, then those new ospf will not be spawned.

Workaround:

The workaround is to re-apply the new configuration once the standby is up completely.

Recovery:

None.

CSCti01478

Basic Description:

sysdb busy, timeouts after rack OIR of rack with DRP pair

Symptom:

Lots of processes (admin plane) complain that the registrations/get/bind operations are timing out. The next thing to notice is the Pending MsgCount which indicates the servers inability to process incoming messages. This triggers a snmp issue as snmp doesn't handles the error core related to sysdb registration properly.

# gsp_show -c 395 (jid of sysdb_svr_admin)
 Group messages received by client id 8, process pid:127038
(pkg/bin/sysdb_svr_admin) 
 28               Max Thresh    10000         Red High     9500
                   Flow Zone        0 Pending MsgCount        0
               Pending Bytes        0    High MsgCount        0
                  High Bytes        0      Total Bytes        0
                 Max MsgSize        0   Msgs Delivered        0
                Msgs Dropped        0
                      Lwg(s)

Conditions:

This issue occurs on a multi chassis system upon an OIR.

Workaround:

None.

Recovery:

Restarting sysdb_svr_admin on the active+standby DSC nodes (not simultaneously though) will help recover the issue.

CSCti74249

Basic Description:

Admin Plane config loss upon Turboboot

Symptom:

Admin config loss upon Turboboot, user have to create new root user name and password in order to log into the router.

Conditions:

Impact might be that for MC, all other racks may not be able to boot until new admin config re-applied.

Workaround:

Just re-apply the admin configuration saved before the turbo boot.

Recovery:

None

CSCtj19602

Basic Description:

Install operation failed due to insufficient disk space on SP cards

Symptom:

Upgrade or install rollback may fail accompanied with "insufficient disk space on SPs" error messages like the following example.

Example:
 Error:    Cannot proceed with the rollback operation because there is
 Error:    insufficient disk space on the following devices:
 Error:     - 0/0/SP: bootflash: (5932652 bytes required, 3522772 bytes
 Error:       available)
 Error:     - 0/1/SP: bootflash: (5932652 bytes required, 3512316 bytes
 Error:       available)
 Error:     - 0/2/SP: bootflash: (5932652 bytes required, 3506976 bytes
 Error:       available)
 Error:     - 0/3/SP: bootflash: (5932652 bytes required, 3519248 bytes
 Error:       available)
 Error:     - 0/4/SP: bootflash: (5932652 bytes required, 3502804 bytes
 Error:       available)
 Error:     - 0/5/SP: bootflash: (5932652 bytes required, 3529776 bytes
 Error:       available)
 
   

Conditions:

This problem is triggered by switching to a release where the new version id is a substring of the old version id. This will only occur when upgrading from a test version with a test version suffix (ex: 3.9.2.22i) to a release version with no suffix (3.9.2).

1. Upgrading to a release where the new release id is a substring of the old release.

Example: Upgrading from 3.9.2.22i to 3.9.2.
 
   

2. Rolling back to a release where the release being rolled back to is a substring of the currently running release. Example: Rolling back from 3.9.2.22i to 3.9.2.

Workaround: Use turboboot instead of a PIE upgrade if the above conditions apply.

Recovery:

Use turboboot to run the new image

CSCti19533

Basic Description:

Wildcard does not work on activating inactive pies

Symptom:

When attempting to activate packages using wild cards, certain packages are not being found which prevents the activation from taking place.

Conditions:

When a activation to a new release (3.9.2) is attempted from 3.7.3 while using wild cards to specify the packages instead of specifying them explicitly by name.

Workaround:

Instead of using wild cards, explicitly name each package to be activated.

Recovery:

None

CSCti67148

Basic Description:

Optional task-maps not downloaded as part of exec authorization & Service exec tasks received from the TACACS server are not processed during AAA authorization

Symptom:

Command authorization fails:

RP/0/RP0/CPU0:router#show int desc
% This command is not authorized
RP/0/RP0/CPU0:router#

Conditions:

This happens:

On a router running IOS XR 3.9.2 or 4.0.0. These are the only 2 versions affected. It did not happen before and it's fixed afterwards.

Tacacs authorization is enabled.

Router is supposed to retrieve its list of usergroup/taskgroup/task from the tacacs server through a service exec (optional) task configured on the tacacs server.

The problem with this bug is that the service exec tasks received from the tacacs server are not processed during aaa authorization with tacacs. So the user ends up with no task on the router and no command is authorized. Even though the command is permitted on the tacacs server.

Workaround:

Instead of using wild cards, explicitly name each package to be activated.

Recovery:

The way to make tacacs authorization work in 3.9.2 or 4.0.0 is through a privilege level:

If privilege level 15 is assigned on the tacacs server, then user will end up with the tasks/commands of the group root-system.

If privilege level 14 is assigned on the tacacs server, then user will end up with the tasks/commands of the group owner-sdr.

If a privilege level between 1 and 13 (let's call it X), then we can configure a usergroup 'privX' on the router and the user will inherit the list of tasks of that group. For instance, if we want to have a user with all commands available, we can assign privilege level 13 on the router and configure this usergroup on the router:

usergroup priv13
  taskgroup root-system
  taskgroup cisco-support
 
   

CSCti50227

Basic Description:

Not able to modify RPL and delete prefix-set in a single commit.

Symptom:

When a policy that is attached directly or indirectly to an attach point needs to be modified, a single commit operation cannot be performed when:

Removing a set or policy referred by another policy that is attached to any attach point directly or indirectly.

Modifying the policy to remove the reference to the same set or policy that is getting removed.

Workaround:

The commit must be performed in two steps:

1. Modify the policy to remove the reference to the policy or set and then commit.

2. Remove the policy or set and commit.

Open Release 3.9.2 Caveats Specific to the Cisco XR 12000 Series Router

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

CSCta86699

Basic Description:

Entity goes missing after RP Failover on the 16 slot c12000

Symptom:

Some subentities in the Entity-MIB go missing after RP FO. This condition occurs intermittently on a 16 slot GSR chassis.

Conditions:

On an RP failover on the 16 slot C12000 chassis, there is an intermittent condition in which subentities go missing.

Workaround:

None.

Recovery:

A forced failover or restart of the invmgr process should resolve the condition.

CSCtf17283

Basic Description:

FIB_MGR Traceback while removing OSPF process & re-adding OSPF process

Symptom:

FIB_MGR Traceback while removing and re-adding OSPF process in scaled setup.

Conditions:

Removing and re-adding OSPF process in the same commit.

Workaround:

The issue is not seen when some time gap (~3-5 sec) is given between removing and re-adding OSPF process.

CSCtg09403

Basic Description:

multilink MTU size is not pushed to member links

Symptom:

On a multilink bundle, when MTU is changed under the bundle interface, the value should be automatically pushed to all member links but this does not happen.

Conditions:

This applies to changing the MTU value of multilink bundles.

Workaround:

Set the MTU on all member links before adding to the bundle. Set the bundle MTU properly at creation time.

Recovery:

All member links need to be removed from bundle and then change their their MTU and finally set the MTU on the bundle itself. This will be service impacting.

CSCti52909

Basic Description:

Dampening penalty increased after "no shut" on bundle-pos member

Symptom:

Dampening penalty seems to increase after a "no shut" is issued on the SONET controller on Eng 3 POS linecard.

Conditions:

No shut on Sonet Controller

Workaround:

No workaround.

Recovery:

None

CSCti50941

Basic Description:

Convergence values not consistent on bundle member shut on E3 & E5 LCs

Symptom:

Traffic loss during bundle member removal. The impact will be higher if a Service policy is applied to the bundle interface. The impact is occurring due to reprogramming of Bundle adjacency in Rx Engine and Tx Engine and when QoS Policy is applied, then TCAM entry modification is also required to take care of bandwidth modification.

Conditions:

A link bundle with traffic flowing over it

Workaround:

None.

Upgrading Cisco IOS XR Software

Cisco IOS XR software is installed and activated from modular packages, allowing specific features or software patches to be installed, upgraded, or downgraded without affecting unrelated processes. Software packages can be upgraded or downgraded on all supported card types, or on a single card (node).

Software packages are installed from package installation envelope (PIE) files that contain one or more software components.

The following URL contains links to information about how to upgrade Cisco IOS XR software:

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


Note Cisco IOS XR Software Release 3.9.1 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB before upgrading to Cisco IOS XR Software Release 3.9.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.2" section.


Troubleshooting

For information on troubleshooting Cisco IOS XR software, refer to the Cisco IOS XR Troubleshooting Guide for the Cisco XR 12000 Series Router and the Cisco IOS XR Getting Started Guide for the Cisco XR 12000 Series Router.

Related Documentation

The most current Cisco XR 12000 Series Router hardware documentation is located at the following URL:

http://www.cisco.com/en/US/products/ps6342/prod_installation_guides_list.html

The Cisco IOS XR software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. See About Cisco IOS XR Software Documentation for Release 3.9 for a list of Cisco IOS XR Release 3.9.1 software documentation.

The most current Cisco XR 12000 Series Router software documentation is located at the following URL:

http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.

Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.

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