Guest

Cisco IOS XR Software (End-of-Sale)

Release Notes for Cisco IOS XR Release 3.8.1

  • Viewing Options

  • PDF (883.3 KB)
  • Feedback
Release Notes for Cisco IOS XR Software Release 3.8.1

Table Of Contents

Release Notes for Cisco IOS XR Software Release 3.8.1

Key Changes from Previous Releases in Cisco IOS XR Release 3.8.1

Contents

Introduction

System Requirements

Cisco CRS-1

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Other Firmware Support

Cisco XR 12000 Series Router

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Firmware Support

Minimum and Preferred Cisco IOS Image and Boot Helper Levels for Migration

Minimum Firmware Requirement

Determining Your Software Version

New Software Features in Cisco IOS XR Software Release 3.8.1

New Software Features Supported on All Platforms

LACP Short Period Time Intervals

Cisco CRS-1 Router-Specific Software Features

Multicast Fabric Test

Enhanced Process Distribution to Improve Load-Balancing Across Cisco CRS-1 RPs

Cisco XR 12000 Series Router-Specific Software Features

Power Manager

ATM Support for Layer 2 Tunnel Protocol Version 3 on Engine-5 Line Cards

New Hardware Features for Cisco IOS XR Software Release 3.8.1

Cisco CRS-1 Router-Specific Hardware Features

Cisco XR 12000 Series Router-Specific Hardware Features

Important Notes

Minimum Flash Disk Requirements When Upgrading to Release 3.8.1

Caveats

Caveats Specific to the Cisco CRS-1 Router

Cisco IOS XR Caveats

Caveats Specific to the Cisco XR 12000 Series Router

Resolved Cisco IOS XR Software PSIRT-Related Caveats

Upgrading Cisco IOS XR Software

Product Life Cycle of Cisco IOS XR Software Release 3.8.1

Troubleshooting

Related Documentation

Hardware Documents

Software Documents

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco IOS XR Software Release 3.8.1


April 5, 2013

Cisco IOS XR Software Release 3.8.1

Text Part Number OL-19620-02

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


Note For information about Cisco IOS XR Software Release 3.8.1, see the "Important Notes" section.


You can find the most current Cisco IOS XR software documentation on the World Wide Web at http://www.cisco.com/en/US/partner/products/ps5845/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" section on page 25.

For a list of software caveats that apply to Cisco IOS XR Software Release 3.8.1, see the "Caveats" section. The caveats are updated for every release and are described 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.

Key Changes from Previous Releases in Cisco IOS XR Release 3.8.1

Cisco IOS XR Software Release 3.8.1 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.8.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.8.1" section.

Contents

These release notes contain the following sections:

Introduction

System Requirements

Determining Your Software Version

New Software Features in Cisco IOS XR Software Release 3.8.1

New Hardware Features for Cisco IOS XR Software Release 3.8.1

Important Notes

Caveats

Upgrading Cisco IOS XR Software

Product Life Cycle of Cisco IOS XR Software Release 3.8.1

Troubleshooting

Related Documentation

Obtaining Documentation and Submitting a Service Request

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 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). The Cisco CRS-1 router supports Layer 2 Virtual Private Network (L2VPN).

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

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 simplifies the configuration of 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. Includes a comprehensive set of Syslog messaging.

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 control plan 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 (Cisco XR 12000 Series Router only). 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)

Traffic engineering support for unequal load balancing

Path Computation Element (PCE) capability for traffic engineering

Firewall Services—Seamless insertion of Firewall Services in the data path with Virtual Firewall support on Multi Service Blade (XR-12K-MSB) for the Cisco XR 12000 Series Router.

VPN IPSec Aggregation —The IPSec Aggregation feature is provided through SPA-IPSEC-2G-2 card. The IPSec Aggregation feature allows you to terminate up to 64-K VPN tunnels, both site-to-site and remote access, if four VPN SPAs are used.

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 various platforms for Cisco IOS XR Software Release 3.8.1, see the "New Software Features in Cisco IOS XR Software Release 3.8.1" section in this document.

System Requirements

Cisco IOS XR Software Release 3.8.1 supports the following platforms:

Cisco CRS-1

Cisco XR 12000 Series Router

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

Cisco CRS-1

This section describes the system requirements for Cisco IOS XR Software Release 3.8.1 supported on the Cisco CRS-1 router platform. The system requirements include the following information:

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Other Firmware Support

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

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.8.1 features. Table 1 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 3.8 supported on the Cisco CRS-1.

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

Feature Set
Filename
Description
Composite Package

Cisco IOS XR IP Unicast Routing Core Bundle

comp-hfr-mini.pie-3.8.1

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

Cisco IOS XR IP Unicast Routing Core Bundle

comp-hfr-mini.vm-3.8.1

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

Optional Individual Packages 1

Cisco IOS XR Manageability Package

hfr-mgbl-p.pie-3.8.1

CORBA2 agent, XML3 Parser, and HTTP server packages.

Cisco IOS XR MPLS Package

hfr-mpls-p.pie-3.8.1

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

Cisco IOS XR Multicast Package

hfr-mcast-p.pie-3.8.1

Multicast Routing Protocols (PIM, MSDP,10 IGMP,11 Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB,12 MURIB13 , MFWD14 ), and BIDIR-PIM.15

Cisco IOS XR Security Package

hfr-k9sec-p.pie-3.8.1

Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI19 (Software based IPSec support—maximum of 500 tunnels)

Cisco IOS XR Documentation Package

hfr-doc.pie-3.8.1

Man pages for Cisco IOS XR CLI commands

Cisco IOS XR FPD Package

hfr-fpd.pie-3.8.1

Firmware for Fixed PLIM20 and SPA21 modules as well as ROMMON22 images for Cisco CRS-1 chassis.

Cisco IOS XR Diagnostic Package

hfr-diags-p.pie-3.8.1

Diagnostic utilities for Cisco IOS XR routers.

1 Packages are installed individually

2 Common Object Request Broker Architecture

3 Extensible Markup Language

4 MPLS Traffic Engineering

5 Label Distribution Protocol

6 Operations, Administration, and Maintenance

7 Link Manager Protocol

8 Optical User Network Interface

9 Resource Reservation Protocol

10 Multicast Source Discovery Protocol

11 Internet Group Management Protocol

12 Multicast Routing Information Base

13 Multicast-Unicast RIB

14 Multicast forwarding

15 Bidirectional Protocol Independent Multicast

16 IP Security

17 Secure Shell

18 Secure Socket Layer

19 Public-key infrastructure

20 Physical layer interface module

21 Shared port adapters

22 ROM monitor


Table 2 lists the Cisco CRS-1 TAR files.

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

Feature Set
Filename
Description

Cisco IOS XR IP/MPLS Core Software

CRS-1-iosxr-3.8.1.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 Diagnostic Package

Cisco IOS XR FPD Package

Cisco IOS XR Documentation Package

Cisco IOS XR IP/MPLS Core Software 3DES

CRS-1-iosxr-k9-3.8.1.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

Cisco IOS XR Diagnostic Package

Cisco IOS XR FPD Package

Cisco IOS XR Documentation 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 Cisco CRS-1 running Cisco IOS XR Software Release 3.8.1 consist of the following:

4-GB memory on the route processors (RPs)

2-GB memory on each modular services card (MSC)

2-GB PCMCIA flash disk


Note Cisco IOS XR Software Release 3.8.1 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.8.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.8.1" section.


Hardware Supported

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

The following table lists the supported hardware components on the Cisco CRS-1 and the minimum required software versions. For more information, see the "Other Firmware Support" section.

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

Component
Part Number
Support from Version
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 Fan Controller for 16-Slot Line Card Chassis

CRS-16-LCC-FAN-CT

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 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 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 DC PEM for 16 slot LCC and FCC

CRS-16-DC-PEM

3.2

Cisco CRS-1 16 Slot System Reduced-Noise DC PEM

CRS-16-DC-PEM-B

3.8

Cisco CRS-1 16 Slot System Reduced-Noise Fan Tray

CRS-16-LCC-FNTR-B

3.8

Cisco CRS-1 Series 8-Slot Line Card Chassis

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

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 Series 4-Slot Line Card Chassis

Cisco CRS-1 4-Slot Single-Shelf System

CRS-4/S

3.4

Cisco CRS-1 Fabric Chassis Hardware

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

CRS-1 Fabric Chassis Integrated Switch Controller Card

CRS-FCC-SC-22GE=

3.4.1

Cisco CRS-1 General Chassis Hardware

Cisco CRS-1 PCMCIA Flash Disk 1 GB

CRS-FLASH-DISK-1G

3.2

Cisco CRS-1 PCM CIA Flash Disk 2 GB

CRS-FLASH-DISK-2G

3.7

Cisco CRS-1 PCMCIA Flash Disk 4 GB

CRS-FLASH-DISK-4G

3.8

Cisco CRS-1 Modular Services Card

CRS-MSC

3.2

Cisco CRS-1 Modular Service Card B

CRS-MSC-B

3.6

Cisco CRS-1 Series Forwarding Processor 40G

CRS-FP40

3.8.1

Cisco CRS-1 SFPs

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 Fabric Cards

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

Cisco CRS-1 16-Slot Fabric Card/Single

CRS-16-FC/S

3.2

Cisco CRS-1 Interface and Router Processor Cards

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 Carrier 1 Series SPA Interface Processor 40G

CRS1-SIP-800

3.2

Cisco CRS-1 16-Slot Route Processor

CRS-16-RP

3.2

Cisco CRS-1 Distributed Route Processor

CRS-DRP

3.3

Cisco CRS-1 Distributed Route Processor CPU Module

CRS-DRP-B-CPU

3.4.1

Cisco CRS-1 Distributed Route Processor PLIM Module

CRS-DRP-B-PLIM

3.4.1

Cisco CRS-1 16-slot Route Processor, revision B

CRS-16-RP-B

3.3

Cisco CRS-1 SONET Interface Modules and SPAs

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 1xOC-768/STM256 POS Interface Module/SR

1OC768-POS-SR

3.2

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

SPA-8XOC12-POS

3.3

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

SPA-2XOC48-POS/RPR

3.4

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

SPA-4XOC48-POS/RPR

3.4

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

SPA-OC192POS-XFP

3.2

Cisco CRS-1 4-Port OC-3 Shared Port Adapter

SPA-4XOC3-POS

3.2

Cisco CRS-1 4-Port T3/E3 Serial Shared Port Adapter

SPA-4XT3/E3

3.4.1

Cisco CRS-1 1-Port OC-192/STM-64 POS/RPR SPA VSR Optics

SPA-OC192POS-VSR

3.4.1

ITU grid 40G PLIM

1OC768-ITU/C

3.3

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

Cisco CRS-1 1-Port OC-768/STM-256c (C-band) DPSK DWDM PLIM

1OC768-DPSK/C

3.6

Cisco CRS-1 Ethernet Interface Modules and SPAS

Cisco CRS-1 8x10 GbE Interface Module/LR

8-10GBE

3.2

10GBASE-LR XENPAK Module for Cisco CRS-1

CRS-XENPAK10GB-LR

3.2

10GBASE-LR XENPAK Module for Cisco CRS-1

XENPAK-10GB-LR+

3.4

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 Gigabit Ethernet Shared Port Adapter

SPA-8X1GE

3.2

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

10GBASE-DWDM XENPAK

CRS 1 CRS-XENPAK10GB-DWDM

3.2.2

ITU grid 4X10G PLIM

4-10GE-ITU/C

3.3

10GBASE-ER XENPAK Modular for Cisco CRS-1

XENPAK-10GB-ER+

3.4

1-port 10GbE SPA WAN/LAN PHY

SPA-1X10GE-WL-V2

3.5.2

Cisco CRS-1 Series 4x10GE Interface Module

4-10GE

3.8.1

Cisco CRS-1 Series 42x1GE Interface Module

42-1GE

3.8.1

Cisco CRS-1 Series 20x1GE Flexible Interface Module

20-1GE-FLEX

3.8.1

Cisco CRS-1 Series 2x10GE WAN/LAN Flexible Interface Module

2-10GE-WL-FLEX

3.8.1


Software Compatibility

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

Cisco CRS-1 4-Slot Line Card Chassis

Cisco CRS-1 8-Slot Line Card Chassis

Cisco CRS-1 16-Slot Line Card Chassis

Cisco CRS-1 Multishelf

Other Firmware Support

The Cisco CRS-1 router supports the following firmware code:

The minimum ROMMON version required for this release is 1.53. For more information about ROMMON specifications, see http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html. For information about upgrading the ROMMON, see http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/rommon/configuration/guide/rm38.html

The minimum CPUCNTRL version required for this release is 2.07. For more information about CPU controller bits, see http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/system_management/configuration/guide/yc38hdwr.html.

Cisco XR 12000 Series Router

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

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Firmware Support

To determine the software versions or levels of your current system, see "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.8.1 features. Table 4 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for Cisco IOS XR Software Release 3.8.1, supported on the Cisco XR 12000 Series Router.

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

Feature Set
Filename
Description
Composite Package

Cisco IOS XR IP Unicast Routing Core Bundle

c12k-mini.pie-3.8.1

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

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

CORBA2 agent, XML Parser, and HTTP server packages.

Cisco IOS XR MPLS Package

c12k-mpls.pie-3.8.1

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

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

Support for Encryption, Decryption, IPSec16 , SSH,17 SSL,18 and PKI.19
Software based IPSec support: maximum of 500 tunnels or Hardware based IPSec: maximum of 64K tunnels using the SPA-IPSEC-2G-2

Cisco IOS XR Standby RP Boot Image

mbiprp-rp.vm-3.8.1

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

Cisco IOS XR Service IPsec Controller Package

c12k-ipsec-service.pie-3.8.1

Support for service-ipsec and service-gre interfaces in Cisco IOS XR software.

Cisco IOS XR Firewall Package

c12k-firewall.pie-3.8.1

Support for Virtual Firewall (vFW) on a Cisco XR 12000 Series Router.

Cisco IOS XR Documentation Package

c12k-doc.pie-3.8.1

Man pages for Cisco IOS XR CLI commands.

Cisco IOS XR FPD Package

c12k-fpd.pie-3.8.1

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

Diagnostic utilities for Cisco IOS XR routers.

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 5 lists the Cisco XR 12000 Series Router TAR files.

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

Feature Set
Filename
Description

Cisco IOS XR IP/MPLS Core Software

XR12000-iosxr-3.8.1.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.8.1.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 Cisco XR 12000 Series Routers running Cisco IOS XR Software Release 3.8.1 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.8.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.8.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.8.1" section.


Hardware Supported

Cisco IOS XR Software Release 3.8.1 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 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 6 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 4GB 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 Services

IPSEC Shared Port Adapter with 2 Gbps DES/3DES/AES

SPA-IPSEC-2G-2

3.4

Cisco Multi Service Blade (MSB)

XR-12K-MSB

3.5

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.8.1 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 "Firmware Support" section.


Firmware Support

Table 7 Cisco XR 12000 Series Router Firmware Versions for Release 3.8.1

Firmware Type
Engine 3 LC
Engine 5 LC
Route Processor

Maintenance Bus (Mbus) Agent Software

RAM

ROM



4.4

4.4



4.4

4.4



4.4

4.4

ROM Monitor

17.1

17.1

1.20

Fabric Downloader

RAM version

ROM version

8.0

8.0

4.7

4.7



Minimum and Preferred Cisco IOS Image and Boot Helper Levels for Migration

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 Boot Helper version to support Release 3.8.1:

Cisco IOS and Boot Helper images—12.0(32)S

However, the recommended Cisco IOS image level to support migration to Release 3.8.1 can be either one of the following:

12.0(32)SY5

12.0(32)s6

If you have an earlier version of this system, you must upgrade to at least the minimum supported level before performing a migration. Otherwise, your migration may fail.

For more information, see the Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.

Table 8 lists the recommended firmware level for Cisco IOS 12.0(32)SY5 when migrating to Cisco IOS XR Software Release 3.8.1.

Table 8 Recommended Cisco IOS Firmware Versions for Migration to Cisco IOS XR 

Serial No.
Description
Version

1

Cisco 12000 Series Router line-card image

12

2

Mbus ROM firmware

3.51

3

Mbus RAM firmware

2.52

5

BFRP field diags

6.12(1.0)

6

PRP field diags

6.13(1.0)

9

Engine 3 LC fabric downloader

7

11

Engine 5 LC fabric downloader

4

12

Mbus downloader

1.1

13

RP MBus downloader

2

14

PRP MBus downloader

1

15

BFPRP ROM image

1.17(0.1)

16

LC ROMMON bootstrap

17.1

17

LC ROMMON upgrade

17.1

18

Cisco 12000 Series Router PRP Beetle FPGA

1.1

19

Cisco 12000 Series Router PRP Chopper FPGA

1.1

20

Cisco 12000 Series Router PRP Assembler FPGA

1.1

21

Cisco 12000 Series Router PRP-1 Chopper FPGA

1.1


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, Release 3.8 for the upgrade all command syntax:

http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/system_management/command/reference/yr38hw.html

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.

Cisco CRS-1

On the Cisco CRS-1, you should see a response similar to the following (which has been abbreviated for the Release Notes):

RP/0/RP0/CPU0:MPLS-PE5#show version
 
   
Thu Jul 30 14:27:41.521 PST
Cisco IOS XR Software, Version 3.8.1[00]
Copyright (c) 2009 by Cisco Systems, Inc.
ROM: System Bootstrap, Version 1.53(20090311:225342) [CRS-1 ROMMON], 
MPLS-PE5 uptime is 11 hours, 48 minutes
System image file is "bootflash:disk0/hfr-os-mbi-3.8.1/mbihfr-rp.vm"
cisco CRS-16/S (7457) processor with 4194304K bytes of memory.
7457 processor at 1197Mhz, Revision 1.2
2 Management Ethernet
5 TenGigE
29 SONET/SDH
28 Packet over SONET/SDH
1 WANPHY controller(s)
8 GigabitEthernet
1 Asynchronous Transfer Mode
1019k bytes of non-volatile configuration memory.
38079M bytes of hard disk.
2052832k bytes of disk0: (Sector size 512 bytes).
Boot device on node 0/0/CPU0 is bootflash:
Package active on node 0/0/CPU0:
hfr-fpd, V 3.8.1[00], Cisco Systems, at disk0:hfr-fpd-3.8.1
Built on Wed Jul 29 03:41:40 PST 2009
By edde-bld1 in /auto/srcarchive3/production/3.8.1/hfr/workspace for c4.2.1-p0
...

Cisco XR 12000 Series Router

On the Cisco XR 12000 Series Router, you should see a response similar to the following (which has been abbreviated for the Release Notes):

RP/0/0/CPU0:PE6_C12406# show version
 
   
RP/0/10/CPU0:PE1-E5#sh ver  
Thu Jul 30 21:30:25.653 UTC
Cisco IOS XR Software, Version 3.8.1[00] 
Copyright (c) 2009 by Cisco Systems, Inc.
ROM: ROMMON System Bootstrap, Version 1.0(0), RELEASE SOFTWARE
PE1-E5 uptime is 2 hours, 38 minutes 
System image file is "disk0:c12k-os-mbi-3.8.1/mbiprp-rp.vm"
cisco 12416/PRP (8641D) processor with 4194304K bytes of memory. 
8641D processor at 1330Mhz, Revision 2.1
8 Cisco 12000 Series SPA Interface Processor-601/501/401 
2 Cisco 12000 Series Performance Route Processor 3s 
4 Management Ethernet 
32 PLIM_QOS 
8 MgmtMultilink 
10 SONET/SDH 
124 T3 
200 Multilink network interface(s) 
596 T1 
2690 Serial network interface(s) 
2 Packet over SONET/SDH 
7 Serial network interface(s) 
4 E3 
21 E1 
15 GigabitEthernet/IEEE 802.3 interface(s) 
2 TenGigE 
895k bytes of non-volatile configuration memory. 
1947M bytes of compact flash card. 
76170M bytes of hard disk. 
1993912k bytes of disk0: (Sector size 512 bytes).
... 

New Software Features in Cisco IOS XR Software Release 3.8.1

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

New Software Features Supported on All Platforms

Cisco CRS-1 Router-Specific Software Features

Cisco XR 12000 Series Router-Specific Software Features

New Software Features Supported on All Platforms

The following new software feature in Cisco IOS XR Software Release 3.8.1 is supported on both the Cisco CRS-1 and the Cisco XR 12000 Series Router:

LACP Short Period Time Intervals


Note Cisco Session Border Controller (SBC) is not supported on any platform.


LACP Short Period Time Intervals

The Link Aggregation Control Protocol (LACP) Short Period Time Interval feature is supported in Cisco IOS XR Software Release 3.8.1 on the Cisco CRS-1 Router and Cisco XR 12000 Series Router.


Note The Cisco XR 12000 Series Router also supports Packet-over- SONET (POS) bundled interfaces in Release 3.8.1.


LACP packets are exchanged periodically across bundle-member links to verify the link's stability and reliability. Configuring short period time intervals in which LACP packets are sent enables faster detection and recovery from link failures.


Note On the Cisco XR 12000 Series Router, only the default short period (1000 milliseconds) is supported.


Short period time intervals are configured as follows:

In milliseconds

In increments of 100 milliseconds

In the range 100 to 1000 milliseconds

1000 milliseconds (1 second default)

Up to 64 member links

Up to 1280 packets per second (pps)

After six missed packets, the link is detached from the bundle.

When the short period time interval is not configured, LACP packets are transmitted over a member link every 30 seconds by default.

When the short period time interval is configured, LACP packets are transmitted over a member link once every 1000 milliseconds (1 second) by default. Optionally, both the transmit and receive intervals can be configured to less than 1000 milliseconds, independently or together, in increments of 100 milliseconds (100, 200, 300, and so on).

When you configure a custom LACP short period transmit interval at one end of a link, you must configure the same time period for the receive interval at the other end of the link.


Note You must always configure the transmit interval at both ends of the connection before you configure the receive interval at either end of the connection. Failure to configure the transmit interval at both ends first results in route flapping (a route going up and down continuously). When you remove a custom LACP short period, you must do it in reverse order. You must remove the receive intervals first and then the transmit intervals.


Configuring the Default LACP Short Period Time Interval

This section describes how to configure the default short period time interval for sending and receiving LACP packets on a Gigabit Ethernet interface. This procedure also enables the LACP short period.

SUMMARY STEPS

To enable an LACP short period time interval, using the default time of 1 second, perform the following steps.

1. configure

2. interface GigabitEthernet interface-path

3. bundle id number mode active

4. lacp period short

5. commit

DETAILED STEPS

 
Command or Action
Purpose

Step 1 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode.

Step 3 

bundle id number mode active

Example:

RP/0/RP0/CPU0:router(config-if)# bundle id 1 mode active

Specifies the bundle interface and puts the member interface in active mode.

Step 4 

lacp period short

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short

Configures a short period time interval for the sending and receiving of LACP packets, using the default time period of 1000 milliseconds or 1 second.

Step 5 

end

or

commit

Example:

RP/0/RP0/CPU0:router(config-if)# end

or

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting (yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuring Custom LACP Short Period Time Intervals

This section describes how to configure custom short period time intervals (less than 1000 milliseconds) for sending and receiving LACP packets on a Gigabit Ethernet interface.


Note You must always configure the transmit interval at both ends of the connection before you configure the receive interval at either end of the connection. Failure to configure the transmit interval at both ends first results in route flapping (a route going up and down continuously). When you remove a custom LACP short period, you must do it in reverse order. You must remove the receive intervals first and then the transmit intervals.


SUMMARY STEPS

To configure custom receive and transmit intervals for LACP packets, perform the following steps.

Router A

1. configure

2. interface GigabitEthernet interface-path

3. bundle id number mode active

4. lacp period short

5. commit

Router B

6. configure

7. interface GigabitEthernet interface-path

8. lacp period short

9. commit

Router A

10. configure

11. interface GigabitEthernet interface-path

12. lacp period short transmit interval

13. commit

Router B

14. configure

15. interface GigabitEthernet interface-path

16. lacp period short transmit interval

17. commit

Router A

18. configure

19. interface GigabitEthernet interface-path

20. lacp period short receive interval

21. commit

Router B

22. configure

23. interface GigabitEthernet interface-path

24. lacp period short receive interval

25. commit or end

DETAILED STEPS

 
Command or Action
Purpose
 
Router A

Step 1 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 2 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode.

Step 3 

bundle id number mode active

Example:

RP/0/RP0/CPU0:router(config-if)# bundle id 1 mode active

Specifies the bundle interface and puts the member interface in active mode.

Step 4 

lacp period short

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short

Enables the short period time interval.

Step 5 

commit

Example:

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes and exits to EXEC mode.

 
Router B

Step 6 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 7 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode.

Step 8 

lacp period short

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short

Enables the short period time interval.

Step 9 

commit

Example:

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes and exits to EXEC mode.

 
Router A

Step 10 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 11 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode at one end of the connection.

Step 12 

lacp period short transmit interval

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500

Configures the short period transmit time interval for LACP packets at one end of the connection.

Valid values are 100 to 1000 milliseconds in multiples of 100, such as 100, 200, 300, and so on.

Step 13 

commit

Example:

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes and exits to EXEC mode.

 
Router B

Step 14 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 15 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode at one end of the connection.

Step 16 

lacp period short transmit interval

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500

Configures the short period transmit time interval for LACP packets at one end of the connection.

Valid values are 100 to 1000 milliseconds in multiples of 100, such as 100, 200, 300, and so on.

Step 17 

commit

Example:

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes and exits to EXEC mode.

 
Router A

Step 18 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 19 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode at one end of the connection.

Step 20 

lacp period short receive interval

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500

Configures the short period receive time interval for LACP packets at one end of the connection.

Valid values are 100 to 1000 milliseconds in multiples of 100, such as 100, 200, 300, and so on.

Step 21 

commit

Example:

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes and exits to EXEC mode.

 
Router B

Step 22 

configure

Example:

RP/0/RP0/CPU0:router# configure

Enters global configuration mode.

Step 23 

interface GigabitEthernet interface-path
Example:

RP/0/RP0/CPU0:router(config)# interface GigabitEthernet 0/0/0/1

Creates a Gigabit Ethernet interface and enters interface configuration mode at one end of the connection.

Step 24 

lacp period short receive interval

Example:

RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500

Configures the short period receive time interval for LACP packets at one end of the connection.

Valid values are 100 to 1000 milliseconds in multiples of 100, such as 100, 200, 300, and so on.

Step 25 

end

or

commit

Example:

RP/0/RP0/CPU0:router(config-if)# end

or

RP/0/RP0/CPU0:router(config-if)# commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them 
before exiting (yes/no/cancel)? 
[cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

Configuration Examples for LACP Short Period

The following example shows how to configure the LACP short period time interval to the default time of 1000 milliseconds (1 second):

config
interface gigabitethernet 0/0/0/1
   bundle id 1 mode active
   lacp period short 
   commit
 
   

The following example shows how to configure custom LACP short period transmit and receive intervals to less than the default of 1000 milliseconds (1 second):

Router A

config
interface gigabitethernet 0/0/0/1
   bundle id 1 mode active
   lacp period short 
   commit

Router B

config
interface gigabitethernet 0/0/0/1
   lacp period short 
   commit

Router A

config
interface gigabitethernet 0/0/0/1
    lacp period short transmit 100
	commit

Router B

config
interface gigabitethernet 0/0/0/1
    lacp period short transmit 100
	commit

Router A

config
interface gigabitethernet 0/0/0/1
   lacp period short receive 100
   commit

Router B

config
interface gigabitethernet 0/0/0/1
   lacp period short receive 100
   commit

LACP Commands

This section includes the following commands associated with the LACP Short Period Time Interval feature:

lacp period short

show lacp io

lacp packet-capture

show lacp packet-capture

lacp period short

To enable a short period time interval for the transmission and reception of Link Aggregation Control Protocol (LACP) packets, use the lacp period short command in interface configuration mode. To return to the default short period, use the no form of this command.

lacp period short [receive interval] [transmit interval]

no lacp period short [receive interval] [transmit interval]

Syntax Description

receive interval

Time interval (in milliseconds) for receiving LACP packets when LACP short period is enabled. The range is 100 to 1000 and must be multiples of 100, such as 100, 200, 300, and so on.

transmit interval

Time interval (in milliseconds) for transmitting LACP packets when LACP short period is enabled. The range is 100 to 1000 and must be multiples of 100, such as 100, 200, 300, and so on.


Defaults

The default is 1000.

Command Modes

Interface configuration

Command History

Release
Modification

Release 3.2

This command was introduced on the Cisco CRS-1.

Release 3.3.0

No modification.

Release 3.4.0

No modification.

Release 3.5.0

No modification.

Release 3.6.0

This command was first supported on the Cisco XR 12000 Series Router.

Release 3.7.0

No modification.

Release 3.8.0

No modification.

Release 3.8.1

The keywords transmit and receive were added on the Cisco CRS-1 and 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. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.


Note On the Cisco XR 12000 Series Router, only the default short period (1 second) is supported.


When you configure a custom LACP short period transmit interval at one end of a link, you must configure the same time period for the receive interval at the other end of the link.


Note You must always configure the transmit interval at both ends of the connection before you configure the receive interval at either end of the connection. Failure to configure the transmit interval at both ends first results in route flapping (a route going up and down continuously). When you remove a custom LACP short period, you must do it in reverse order. You must remove the receive intervals first and then the transmit intervals.


Task ID
Task ID
Operations

bundle

read, write


Examples

The following example shows how to enable a default Link Aggregation Control Protocol (LACP) short period on a Gigabit Ethernet interface:

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short 
RP/0/RP0/CPU0:router(config-if)# commit 
 
   

The following example shows how to configure custom Link Aggregation Control Protocol (LACP) short period transmit and receive intervals at both ends of a connection:

Router A

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short 
RP/0/RP0/CPU0:router(config-if)# commit 

Router B

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short 
RP/0/RP0/CPU0:router(config-if)# commit 

Router A

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500 
RP/0/RP0/CPU0:router(config-if)# commit 

Router B

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500 
RP/0/RP0/CPU0:router(config-if)# commit 

Router A

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500 
RP/0/RP0/CPU0:router(config-if)# commit 

Router B

RP/0/RP0/CPU0:router# config 
RP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0 
RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500 
RP/0/RP0/CPU0:router(config-if)# commit 

Related Commands

Command
Description

lacp packet-capture

Captures packets to be displayed by the show lacp packet-capture command.

lacp period short

Enables a short period time interval for the transmitting and receiving of LACP packets.

show lacp io

Displays the LACP transmitting information.

show lacp packet-capture

Displays LACP transmitting and receiving information.


show lacp io

To display the Link Aggregation Control Protocol (LACP) transmission information that used by the transmitting device for sending packets on an interface, use the show lacp io command in EXEC mode.

show lacp io [Bundle-Ether bundle-id] [Bundle-POS bundle-id] [GigabitEthernet interface-path-id] [POS interface-path-id] [TenGigE interface-path-id]

Syntax Description

Bundle-Ether bundle-id

(Optional) Displays information for the Ethernet bundle interface with the specified bundle-id argument. The range is 1 through 65535.

Bundle-POS bundle-id

(Optional) Displays information for the POS bundle interface with the specified bundle-id argument. The range is 1 through 65535.

GigabitEthernet

(Optional) Displays information for the Gigabit Ethernet interface with the specified interface-path-id argument.

TenGigE

(Optional) Displays information for the Ten Gigabit Ethernet interface with the specified interface-path-id argument.

POS

(Optional) Displays information for the POS interface with the specified interface-path-id argument.

interface-path-id

Physical interface or virtual interface.

Note Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.


Defaults

The default takes no parameters and displays information for all actively transmitting interfaces.

Command Modes

EXEC

Command History

Release
Modification

Release 3.8.1

This command was introduced on the Cisco CRS-1 and 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.

This command displays information only for interfaces that are actively transmitting packets.

Task ID
Task ID
Operations

bundle

read


Examples

The following example shows how to display Link Aggregation Control Protocol (LACP) information for the Ethernet bundle interface with bundle ID 28.

RP/0/RP0/CPU0:router# show lacp io bundle-ether 28
 
   
Thu Jun 18 16:28:54.068 PST
 
   
Bundle-Ether28
 
   
Interface GigabitEthernet0/1/5/6
================================
Interface handle:       0x01180100
Interface media type:   Ethernet
Fast periodic interval: 1000ms
Source MAC address:     0015.63c0.b3b8
Actor system:   0x8000, 00-15-63-c0-b0-04
Actor key:      0x001c
Actor port:     0x8000, 0x0001
Actor state:     Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
Partner system: 0x8000, 00-15-63-58-b9-04
Partner key:    0x001c
Partner port:   0x0001, 0x0003
Partner state:   Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
 
   
Interface GigabitEthernet0/1/5/7
================================
Interface handle:       0x01180120
Interface media type:   Ethernet
Fast periodic interval: 1000ms
Source MAC address:     0015.63c0.b3b9
Actor system:   0x8000, 00-15-63-c0-b0-04
Actor key:      0x001c
Actor port:     0x8000, 0x0002
Actor state:     Act  (T/o)  Agg   Sync  (Coll) (Dist) (Def) (Exp)
Partner system: 0x8000, 00-15-63-58-b9-04
Partner key:    0x001c
Partner port:   0x0002, 0x0004
Partner state:   Act  (T/o)  Agg  (Sync) (Coll) (Dist) (Def) (Exp)
 
   
RP/0/RP0/CPU0:router#
 
   

The following example shows how to display Link Aggregation Control Protocol (LACP) information for all actively transmitting interfaces:

RP/0/RP0/CPU0:router# show lacp io 
 
   
Thu Jun 18 16:33:57.330 PST
 
   
Bundle-Ether28
 
   
Interface GigabitEthernet0/1/5/6
================================
Interface handle:       0x01180100
Interface media type:   Ethernet
Fast periodic interval: 1000ms
Source MAC address:     0015.63c0.b3b8
Actor system:   0x8000, 00-15-63-c0-b0-04
Actor key:      0x001c
Actor port:     0x8000, 0x0001
Actor state:     Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
Partner system: 0x8000, 00-15-63-58-b9-04
Partner key:    0x001c
Partner port:   0x0001, 0x0003
Partner state:   Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
 
   
Interface GigabitEthernet0/1/5/7
================================
Interface handle:       0x01180120
Interface media type:   Ethernet
Fast periodic interval: 1000ms
Source MAC address:     0015.63c0.b3b9
Actor system:   0x8000, 00-15-63-c0-b0-04
Actor key:      0x001c
Actor port:     0x8000, 0x0002
Actor state:     Act  (T/o)  Agg   Sync  (Coll) (Dist) (Def) (Exp)
Partner system: 0x8000, 00-15-63-58-b9-04
Partner key:    0x001c
Partner port:   0x0002, 0x0004
Partner state:   Act  (T/o)  Agg  (Sync) (Coll) (Dist) (Def) (Exp)
 
   
 
   
Bundle-POS24
 
   
Interface POS0/1/4/0
====================
Interface handle:       0x011804c0
Interface media type:   POS
Fast periodic interval: 1000ms
Actor system:   0x8000, 00-15-63-c0-b0-04
Actor key:      0x0018
Actor port:     0x8000, 0x0003
Actor state:     Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
Partner system: 0x8000, 00-15-63-58-b9-04
Partner key:    0x0018
Partner port:   0x8000, 0x0001
Partner state:   Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
 
   
Interface POS0/1/4/1
====================
Interface handle:       0x011804e0
Interface media type:   POS
Fast periodic interval: 1000ms
Actor system:   0x8000, 00-15-63-c0-b0-04
Actor key:      0x0018
Actor port:     0x8000, 0x0004
Actor state:     Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
Partner system: 0x8000, 00-15-63-58-b9-04
Partner key:    0x0018
Partner port:   0x8000, 0x0002
Partner state:   Act  (T/o)  Agg   Sync   Coll   Dist  (Def) (Exp)
 
   

Related Commands

Command
Description

lacp packet-capture

Captures packets to be displayed by the show lacp packet-capture command.

lacp period short

Enables a short period time interval for the transmitting and receiving of LACP packets.

show lacp io

Displays the LACP transmitting information.

show lacp packet-capture

Displays LACP transmitting and receiving information.


lacp packet-capture

To capture LACP packets so that their information can be displayed by the show lacp packet-capture command, use the lacp packet-capture command in EXEC mode.

lacp packet-capture gigabitethernet interface-path-id | pos interface-path-idtengige interface-path-id number-of-packets

To stop capturing packets or to clear captured packets, use the lacp packet-capture command in EXEC mode.

lacp packet-capture [bundle-ether bundle-id | bundle-pos bundle-id gigabitethernet interface-path-id | pos interface-path-id | tengige interface-path-id] clear | stop

Syntax Description

bundle-ether

Ethernet bundle interface specified by the bundle-id argument.

bundle-pos

Packet-over-SONET (POS) bundle interface specified by the bundle-id argument.

GigabitEthernet

Gigabit Ethernet interface specified by the interface-path-id argument.

POS

Packet-over-SONET (POS) interface specified by the interface-path-id argument.

TenGigE

Ten Gigabit Ethernet interface specified by the interface-path-id argument.

interface-path-id

Physical interface or virtual interface.

Note Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.

bundle-id

Number specifying the bundle interface. The range is 1 to 65535.

number-of-packets

Number of packets to capture.

clear

Clears all currently captured packets.

stop

Stops capturing packets.


Defaults

The default (no parameters) executes globally for all interfaces on the line card.

Command Modes

EXEC

Command History

Release
Modification

Release 3.8.1

This command was introduced on the Cisco CRS-1 and 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.

The lacp packet-capture command captures transmitted and received LACP packets on a single bundle member interface. The contents of these packets can then be displayed by the show lacp packet-capture command. If the lacp packet-capture command is not issued, the show lacp packet-capture command does not display any information.

The lacp packet-capture command continues capturing packets until the stop keyword is issued for that port or that bundle. Captured packets are stored and continue to be displayed until the clear keyword is issued for that port or that bundle.

Packets can be only captured for one port on a line card at a time. Starting a packet capture on a port implicitly stops and clears all packet captures on all other ports on that line card.

To stop capturing packets before the specified number of packets has been captured, issue the stop keyword.

If stop is specified for a single interface, packet capturing is stopped only on that interface.

If stop is specified for a bundle interface, packet capturing is stopped on all members of that bundle.

If stop is specified globally (the default—no parameters), packet capturing is stopped on all bundle interfaces on the router.

To clear all captured packets that are stored for an interface, issue the clear keyword.

If clear is specified for a single interface, packets are cleared only on that interface.

If clear is specified for a bundle interface, packets are cleared on all members of that bundle.

If clear is specified globally (the default—no parameters), packets are cleared on all bundle interfaces on the router.

Task ID
Task ID
Operations

bundle

read


Examples

 
   

The following example shows how to capture LACP packets on a POS interface:

RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 100 
 
   

The following example shows how to stop capturing LACP packets on a POS interface:

RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 stop 

Related Commands

Command
Description

lacp packet-capture

Captures packets to be displayed by the show lacp packet-capture command.

lacp period short

Enables a short period time interval for the transmitting and receiving of LACP packets.

show lacp io

Displays the LACP transmitting information.

show lacp packet-capture

Displays LACP transmitting and receiving information.


show lacp packet-capture

To display the contents of Link Aggregation Control Protocol (LACP) packets that are sent and received on an interface, use the show lacp packet-capture command in EXEC mode.

show lacp packet-capture [decoded] [in | out] GigabitEthernet interface-path-id | POS interface-path-id | TenGigE interface-path-id

Syntax Description

decoded

(Optional) Displays packet information in decoded form for the specified interface.

in

(Optional) Displays packet information for ingress packets only.

out

(Optional) Displays packet information for egress packets only.

GigabitEthernet

Displays packet information for the Gigabit Ethernet interface specified by interface-path-id.

POS

Displays packet information for the POS interface specified by interface-path-id.

TenGigE

Displays packet information for the Ten Gigabit Ethernet interface specified by interface-path-id.

interface-path-id

Physical interface.

Note Use the show interfaces command to see a list of all interfaces currently configured on the router.

For more information about the syntax for the router, use the question mark (?) online help function.


Defaults

The default displays both in and out information.

Command Modes

EXEC

Command History

Release
Modification

Release 3.8.1

This command was introduced on the Cisco CRS-1 and 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.


Note The lacp packet-capture command captures transmit and receive packets on a single interface. The contents of these packets can then be displayed by the show lacp packet-capture command. If the lacp packet-capture command is not issued, the show lacp packet-capture command does not display any information.


Task ID
Task ID
Operations

bundle

read


Examples

Example 1

The following example shows how to display raw LACP packet contents in hexadecimal format for a Gigabit Ethernet interface:


Note In the following example, after you issue the lacp packet-capture command, you must wait for a reasonable amount of time for the system to capture packets that are sent and received on the interface before you issue the show lacp packet-capture command. Otherwise, there is no information to display.


RP/0/RP0/CPU0:router# lacp packet-capture gigabitethernet 0/1/0/0 100 
RP/0/RP0/CPU0:router# show lacp packet-capture gigabitethernet 0/1/0/0 
 
   
Wed Apr 29 16:27:40.996 GMT
OUT  Apr 29 17:05:50.123
========================
01 01 01 14 80 00 02 a7 4c 81 95 04 00 01 80 00 00 01 45 00 
00 00 02 14 ff ff 00 00 00 00 00 00 00 00 ff ff 00 00 40 00 
00 00 03 10 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
00 00 00 00 00 00 00 00 00 00 
 
   
OUT  Apr 29 17:35:50.124
========================
...
 
   

Example 2

 
   

The following example shows how to display the LACP parameters decoded from individual packets that are transmitted and received on a Gigabit Ethernet interface:


Note In the following example, after you issue the lacp packet-capture command, you must wait for a reasonable amount of time for the system to capture packets that are sent and received on the interface before you issue the show lacp packet-capture command. Otherwise, there is no information to display.


RP/0/RP0/CPU0:router# lacp packet-capture gigabitethernet 0/1/0/0 100
RP/0/RP0/CPU0:router# show lacp packet-capture decoded gigabitethernet 0/1/0/0 
 
   
Wed Apr 29 16:27:54.748 GMT
OUT  Apr 29 17:06:03.008
========================
Subtype: 0x01 - LACP     Version: 1
 
   
TLV: 0x01 - Actor Information       Length:  20
System: Priority: 32768, ID: 02-a7-4c-81-95-04
Key: 0x0001, Port priority: 32768, Port ID:     1
State:  Act  (T/o)  Agg  (Sync) (Coll) (Dist)  Def  (Exp)
 
   
TLV: 0x02 - Partner Information     Length:  20
System: Priority: 65535, ID: 00-00-00-00-00-00
Key: 0x0000, Port priority: 65535, Port ID:     0
State: (Act) (T/o) (Agg) (Sync) (Coll) (Dist)  Def  (Exp)
 
   
TLV: 0x03 - Collector Information   Length:  16
Max delay: 65535
 
   
TLV: 0x00 - Terminator              Length:   0

Related Commands

Command
Description

lacp packet-capture

Captures packets to be displayed by the show lacp packet-capture command.

lacp period short

Enables a short period time interval for the transmitting and receiving of LACP packets.

show lacp io

Displays the LACP transmitting information.

show lacp packet-capture

Displays LACP transmitting and receiving information.


Cisco CRS-1 Router-Specific Software Features

The following new features in Cisco IOS XR Software Release 3.8.1 are supported only on the Cisco CRS-1 platform:

Multicast Fabric Test

Enhanced Process Distribution to Improve Load-Balancing Across Cisco CRS-1 RPs

Multicast Fabric Test

A new test, Multicast Fabric Test, has been added to the standard diagnostics tests as test number 11. There are no visible changes to the CLI. This test runs automatically with the standard diagnostics tests configured on the router or when the diagnostic start command is issued. This is supported on the Cisco CRS-1 Series Router.

Enhanced Process Distribution to Improve Load-Balancing Across Cisco CRS-1 RPs

This feature was introduced in Cisco IOS XR Release 3.6.3.

The default Cisco IOS XR process placement policy has changed to improve the distribution of processing load across active Cisco CRS-1 route processors (RPs). These changes affect systems with more than one active RP, such as Cisco CRS-1 multichassis systems and Cisco CRS-1 single-chassis systems with optional, distributed route processors (DRPs) installed.

Highlights of the New Process Distribution Feature

The new default process placement policy creates three groups of placeable processes:

Central Services and Infrastructure (CSI) group

IPv4 Routing/MPLS (IPv4) group

IPv6 Routing (IPv6) group

Each group is placed as a unit, with all processes within a group placed together on the same node.

The CSI group is, by definition, always placed on the dLRSC node. The only placement variation that can occur is in regard to the IPv4 and IPv6 groups.

If a single active non-dLRSC RP pair exists, the IPv4 and IPv6 groups are placed on that pair.

If more than one active non-dLRSC RP pair exists, the IPv4 group is placed on one such pair and the IPv6 group on another. The placement of each group occurs when that group starts.

If no non-dLRSC pairs exist, but an unpaired active non-dLRSC RP does, then, the first placeable group to start (IPv4/MPLS or IPv6) is placed on the dLRSC, with the other group being placed on the non-dLRSC RP pair.

Information About How Process Placement Works

An RP is considered paired for placement purposes if it was paired during system startup. This ensures that it is still considered to be paired even if the standby RP later becomes inactive. If a new pair was configured after system startup, you should perform a manual placement reoptimization to make sure that it is incorporated in the placement service. (See below.)

Process placement is SDR-scoped, occurring independently in each SDR.

Each DRP contains two processor complexes, CPU0 and CPU1, which are considered independent nodes by the placement service. For example, in a Cisco CRS-1 single-chassis system with two DRPs installed and configured as a pair, there are two non-dLRSC RP pairs, the CPU0 pair, and the CPU1 pair.

Tie-breaker rule—When determining placement for a group where multiple candidate nodes for the group, each of which satisfies the placement policy, exist, the candidates are ordered first by RP versus DRP (with the RP taking precedence), and then by node ID. The group is then placed at the first node in the resulting list.

RP failover events have no effect on process placement.

If an RP pair or an unpaired RP fails, any processes that were on the failed location migrate automatically to an active RP in accordance with the rules previously described. This would occur, for example, on Cisco CRS-1 multichassis systems when a rack online insertion and removal (OIR) take place.

No automatic placement changes occur as the result of a new node becoming active.

To redetermine placement of process groups based on the current state of the system, use the placement reoptimize command in EXEC mode.


Note You should use the placement reoptimize command only during a maintenance window, because migrating routing processes between nodes may have a negative effect on traffic. However, to view the effects that a placement reoptimize command would have before you execute it, use the show placement reoptimize command.


Following an upgrade or downgrade of Cisco IOS XR software, you must execute the placement reoptimize command to make sure that process placement is consistent.

Cisco IOS XR Software Release 3.8.1 includes support for prefix-length notation for ACLs on the Cisco CRS-1 platform.

The following example shows how to define an access list named Internetfilter with prefix-length notation:

RP/0/RSP0/CPU0:router(config)# ipv4 access-list Internetfilter
10 permit ipv4 12.10.10.1/24 any
20 permit ipv4 125.10.10.1/16 any
30 permit ipv4 135.10.10.1/27 any
40 permit ipv4 135.200.10.1/24 any
50 permit ipv4 any any

Cisco XR 12000 Series Router-Specific Software Features

The following new features in Cisco IOS XR Software Release 3.8.1 are supported only on the Cisco XR 12000 Series Router platform:

Power Manager

ATM Support for Layer 2 Tunnel Protocol Version 3 on Engine-5 Line Cards

Power Manager

The Power Manager software manages the following types of power requirements for the chassis components:

Type of power systems

Power supplies

Line cards installed in the chassis

Number of operational components in the chassis

With this software, newly discovered or inserted modules are prevented from powering up unless sufficient power is available to operate them.

The Power Manager software performs the following functions:

Sets the correct initial power manager state.

Identifies power supply number, type, power manager policy mode, and operational status to determine total available power and then accounts reserved chassis components.

Evaluates line cards for power-on, starting at the lowest numbered slots, and progressing upward until all slots are accounted for or available power is dropped below zero.

Minimizes added delay to chassis bootup or in the OIR insertion to LC usable time.

Performs a configuration check that generates warning messages or refuses to power up line cards if any of the configuration requirements are not met.

Determines the power available from the power shelf, predicts the maximum power required by all the chassis components, and uses this information to decide which components should be brought up during chassis bootup to remain within system power limits.


Note Automatic fan speed control for thermal management is included with the Power Management feature to support the new blower modules with enhanced airflow cooling capacity.


SUMMARY STEPS

1. admin

2. configure

3. (Optional) power-mgr additive

4. (Optional) power-mgr disable

5. (Optional) power-mgr scale-factor percentage

6. show power-mgr

7. Use one of the following commands:

end

commit

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 

power-mgr additive
Example:
RP/0/RP0/CPU0:router(admin-config)# 
power-mgr additive

(Optional) Configures the power manager in additive mode, where the wattage of all power sources is summed together to compute the total available power. The decision of whether to power up a line card is based on whether there is surplus power available from the total sum of all the power supplies. The default operational mode is redundancy. In this mode, the failure of at least one power supply is already assumed in the calculation of the available power. In redundancy mode, only those cards that can be powered by the redundant power supplies are allowed to power up.

Note Use the no power-mgr additive command to return to the default redundancy mode.

Step 4 

power-mgr disable
Example:
RP/0/RP0/CPU0:router(admin-config)# 
power-mgr disable
 
        

(Optional) Disables the power manager. The power manager is enabled by default.

Disabling the power manager results in a warning message to the SYSLOG indicating that redundancy protection has been disabled.

Note The power manager is enabled in passive mode. Cards are allowed to come up even if there is insufficient power, and warning messages are displayed indicating low power conditions.

Step 5 

power-mgr scale-factor percentage
Example:
RP/0/RP0/CPU0:router(admin-config)# 
power-mgr scale-factor 150

(Optional) Derates or super-rates the power consumption from 50 to 150 percent of the actual power consumption.

Step 6 

show power-mgr
Example:
RP/0/RP0/CPU0:router(admin-config)# 
show power-mgr

Displays the power manager configuration for the chassis.

Step 7 

end

or

commit
Example:
RP/0/RP0/CPU0:router(config-ospf)# 
end


or

RP/0/RP0/CPU0:router(config-ospf)# 
commit

Saves configuration changes.

When you issue the end command, the system prompts you to commit changes:

Uncommitted changes found, commit them before 
exiting (yes/no/cancel)? [cancel]:
 
        

Entering yes saves configuration changes to the running configuration file, exits the configuration session, and returns the router to EXEC mode.

Entering no exits the configuration session and returns the router to EXEC mode without committing the configuration changes.

Entering cancel leaves the router in the current configuration session without exiting or committing the configuration changes.

Use the commit command to save the configuration changes to the running configuration file and remain within the configuration session.

1

show power-mgr Output: Example

The following example shows sample output from the show power-mgr command.

RP/0/5/CPU0:router(admin)# show power-mgr trace
Sun Jun 28 12:25:40.763 PST
97 wrapping entries (1152 possible, 0 filtered, 97 total)
Jun 12 04:27:12.426 power_manager/debug 0/5/CPU0 t33 -------power_manager starting--------
Jun 12 04:27:12.426 power_manager/debug 0/5/CPU0 t33 PM Spawning main Process
Jun 12 04:27:12.426 power_manager/debug 0/5/CPU0 t33 Performing pre-config monvar parsing
Jun 12 04:27:12.626 power_manager/debug 0/5/CPU0 t35 Power Manager EDM Bind successful
Jun 12 04:27:12.658 power_manager/debug 0/5/CPU0 t35 Power Manager Bag registration done
Jun 12 04:27:12.715 power_manager/debug 0/5/CPU0 t35 Power Manager EDM Registration is 
done
Jun 12 04:27:14.516 power_manager/debug 0/5/CPU0 t1 Event: DISCOVERY_DONE on zone=2 with
data 0x00000000
Jun 12 04:27:14.517 power_manager/debug 0/5/CPU0 t33 PM Dequeued Event = DISCOVERY_DONE
Jun 12 04:27:14.520 power_manager/debug 0/5/CPU0 t36 Running on primary RP
Jun 12 04:27:14.539 power_manager/debug 0/5/CPU0 t36 MBus path to PEMs now available
Jun 12 04:27:14.539 power_manager/debug 0/5/CPU0 t36 Attempting to discover powershelf 
type
Jun 12 04:27:15.073 power_manager/debug 0/5/CPU0 t36 PEM FAMILY determined to be =0
Jun 12 04:27:15.240 power_manager/debug 0/5/CPU0 t36 Successfully discovered powershelf
type=2
Jun 12 04:27:15.240 power_manager/debug 0/5/CPU0 t36 Discovering installed PEMs
Jun 12 04:27:19.550 power_manager/debug 0/5/CPU0 t22 Discarding LC_OIR_INSERTED for slot
25; in DISCOVERY_PHASE
Jun 12 04:27:19.551 power_manager/debug 0/5/CPU0 t16 Discarding LC_OIR_INSERTED for slot
16; in DISCOVERY_PHASE
Jun 12 04:27:19.551 power_manager/debug 0/5/CPU0 t19 Discarding LC_OIR_INSERTED for slot
19; in DISCOVERY_PHASE
Jun 12 04:27:19.552 power_manager/debug 0/5/CPU0 t25 Discarding LC_OIR_INSERTED for slot
28; in DISCOVERY_PHASE
Jun 12 04:27:19.562 power_manager/debug 0/5/CPU0 t20 Discarding LC_OIR_INSERTED for slot
20; in DISCOVERY_PHASE
Jun 12 04:27:19.564 power_manager/debug 0/5/CPU0 t12 Discarding LC_OIR_INSERTED for slot
2; in DISCOVERY_PHASE
Jun 12 04:27:19.565 power_manager/debug 0/5/CPU0 t15 Discarding LC_OIR_INSERTED for slot
5; in DISCOVERY_PHASE
Jun 12 04:27:19.565 power_manager/debug 0/5/CPU0 t10 Discarding LC_OIR_INSERTED for slot
0; in DISCOVERY_PHASE
Jun 12 04:27:19.566 power_manager/debug 0/5/CPU0 t13 Discarding LC_OIR_INSERTED for slot
3; in DISCOVERY_PHASE
Jun 12 04:27:19.575 power_manager/debug 0/5/CPU0 t21 Discarding LC_OIR_INSERTED for slot
24; in DISCOVERY_PHASE
Jun 12 04:27:19.577 power_manager/debug 0/5/CPU0 t14 Discarding LC_OIR_INSERTED for slot
4; in DISCOVERY_PHASE
Jun 12 04:27:19.583 power_manager/debug 0/5/CPU0 t11 Discarding LC_OIR_INSERTED for slot
1; in DISCOVERY_PHASE
Jun 12 04:27:19.598 power_manager/debug 0/5/CPU0 t18 Discarding LC_OIR_INSERTED for slot
18; in DISCOVERY_PHASE
Jun 12 04:27:23.418 power_manager/debug 0/5/CPU0 t36 PEM 2 open part failed ; retry 
count=25
Jun 12 04:27:31.335 power_manager/debug 0/5/CPU0 t36 PEM 2 open part failed ; retry 
count=25
Jun 12 04:27:31.536 power_manager/err 0/5/CPU0 t36 Intelligence check for pem 2 failed 
with result =4
Jun 12 04:27:31.536 power_manager/debug 0/5/CPU0 t36 PEM2 discovered as GSR6 legacy AC
Jun 12 04:27:31.683 power_manager/debug 0/5/CPU0 t36 PEM2 can supply up to 1600 watts
Jun 12 04:27:31.683 power_manager/debug 0/5/CPU0 t36 Zone discovery found 1 power zone for
this chassis
Jun 12 04:27:31.683 power_manager/debug 0/5/CPU0 t36 Discovering cards present and 
populating slot data
Jun 12 04:27:36.684 power_manager/debug 0/5/CPU0 t36 Cardtype 150 found in slot 0, needing
134 W
Jun 12 04:27:36.684 power_manager/debug 0/5/CPU0 t36 Cardtype 150 found in slot 1, needing
134 W
Jun 12 04:27:36.702 power_manager/debug 0/5/CPU0 t36 Cardtype 149 found in slot 2, needing
240 W
Jun 12 04:27:36.717 power_manager/debug 0/5/CPU0 t36 Cardtype 149 found in slot 3, needing
240 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 149 found in slot 4, needing
240 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 96 found in slot 5, needing
60 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 6; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 7; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 8; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 9; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 10; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 11; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 12; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 13; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 14; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 15; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 29 found in slot 16, needing
56 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 17; marking
phantom
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 30 found in slot 18, needing
45 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 30 found in slot 19, needing
45 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 30 found in slot 20, needing
45 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 21; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 22; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 23; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 15 found in slot 24, needing
26 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 15 found in slot 25, needing
26 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 26; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 27; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 112 found in slot 28, 
needing
178 W
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 29; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 30; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 31; skipping
Jun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Changing phase to INIT_DECISION_PHASE
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Powershelf capacity at 1600 watts
zone1, 0 watts zone2
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Reserved chassis power is 477 W 
zone1,
0 W zone2
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Available power for chassis is 1123 W
zone1,0 W zone2,
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Starting power-on decision process
with 1123/0 W
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Starting power-on decision process
with 5/60 W
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 After accounting for RPs, 1063/0 W
avail
Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 After accounting for priority slots,
1063/0 W avail
Jun 12 04:28:46.718 power_manager/debug 0/5/CPU0 t36 slot 0 needs 134 W, 929 avail;
Jun 12 04:28:46.718 power_manager/debug 0/5/CPU0 t36 slot 1 needs 134 W, 795 avail;
Jun 12 04:28:46.735 power_manager/debug 0/5/CPU0 t36 slot 2 needs 240 W, 555 avail;
Jun 12 04:28:46.750 power_manager/debug 0/5/CPU0 t36 slot 3 needs 240 W, 315 avail;
Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 slot 4 needs 240 W, 75 avail;
Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 After accounting for normal slots,
75/0 W avail
Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 RP in-use power is 60 W zone1, 0 W
zone2
Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 Linecard in-use power is 988 W zone1,
0 W zone2
Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 Available power for chassis is 75 W
zone1,0 W zone2,
Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 Starting periodic task to monitor 
PEMs
Jun 12 04:28:46.778 power_manager/debug 0/5/CPU0 t36 Changing phase to RUNNING_PHASE
Jun 12 04:28:47.706 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringup
slot 1
Jun 12 04:28:47.711 power_manager/debug 0/5/CPU0 t10 Sufficient power available to bringup
slot 0
Jun 12 04:28:47.713 power_manager/debug 0/5/CPU0 t12 Sufficient power available to bringup
slot 2
Jun 12 04:28:47.715 power_manager/debug 0/5/CPU0 t14 Sufficient power available to bringup
slot 4
Jun 12 04:28:47.718 power_manager/debug 0/5/CPU0 t13 Sufficient power available to bringup
slot 3
Jun 12 04:28:59.467 power_manager/debug 0/5/CPU0 t33 PEM2 busy; skipping polling
Jun 12 04:29:10.161 power_manager/debug 0/5/CPU0 t33 PEM2 no longer busy; resuming polling
Jun 12 04:36:30.950 power_manager/debug 0/5/CPU0 t10 Sufficient power available to bringup
slot 0
Jun 12 04:36:54.291 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringup
slot 1
Jun 12 09:13:43.219 power_manager/debug 0/5/CPU0 t10 Sufficient power available to bringup
slot 0
Jun 12 09:13:44.514 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringup
slot 1
Jun 12 09:14:29.463 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringup
slot 1

ATM Support for Layer 2 Tunnel Protocol Version 3 on Engine-5 Line Cards

In Cisco IOS XR Software Release 3.8.1, the Cisco XR 12000 Series Router supports the following Layer 2 Tunnel Protocol Version 3 (L2TPv3) features on the Engine-5 line cards:

L2TPv3 ATM like-to-like pseudowires

The following modes are supported:

Cell relay

Cell packing

ATM adaptation layer 5 (AAL5)

L2TPv3 ATM IP Interworking

The following modes support interworking:

Ethernet port mode/VLAN, ATM AAL5 (SNAP/Mux/NLPID)

Frame Relay point-to-point DLCI/MLFR, ATM AAL5 (SNAP/Mux/NLPID)

For detailed information about L2TPv3, see the Implementing Layer 2 Tunnel Protocol Version 3 on Cisco IOS XR Software module of Cisco IOS XR MPLS Configuration Guide.

New Hardware Features for Cisco IOS XR Software Release 3.8.1

The following new hardware features were introduced in Cisco IOS XR Software Release 3.8.1:

Cisco CRS-1 Router-Specific Hardware Features

Cisco XR 12000 Series Router-Specific Hardware Features

Cisco CRS-1 Router-Specific Hardware Features

The following new features in Cisco IOS XR Software Release 3.8.1 are supported on the Cisco CRS-1 platform:

4 port 10GE LAN (4-10GE)

20 port 1GE Flex PLIM (20-1GE-FLEX)

2-10 GE-WL-FLEX PLIM (2-10 GE-WL-FLEX)

42 port 1GE (42-1GE)

40G forwarding processor (CRS-FP40)

CRS-FP40 Licenses

The following licenses apply to the CRS-FP40 on a per slot basis:

XC-L2L3VPN—This license applies to the line card that needs to enable L2 Attachment Circuit for L2VPN (VPWS and VPLS), and/or L3 VRF interface for L3VPN applications.

XC-PERF-NETFLOW—This license enables CRS-FP40 to support down to 1:360 Netflow sample rate running 45Mpps at a 40Gbps line rate. Without this license, the CRS-FP40 can support down to 1:1500 Netflow sample rate.

XC-ADV-IP—This license is a placeholder for IP features, for example Lawful Interception, GRE tunnel, and L2TPv3.

For GRE and L2TPv3, this license applies to the line card required to enable GRE and/or L2TPv3 encapsulation.

Restrictions

Link bundle cannot have members from CRS-MSC and CRS-FP40 at the same time.

OC-192 DPT is not supported by 20-1GE-WL-FLEX.

In general, the CRS-MSC and CRS-FP40 support the same features, but the FP40 requires a software license for some features.

CRS-FP40 is not supported in CRS16 single chassis and multichassis configurations.

A minimum ROMMON release of 1.53 is required to support the 20-port 1GE Flex PLIM (20-1GE-FLEX) and 42-port 1GE (42-1GE)

QoS Restrictions

MQC-based QoS configuration will be accepted only on the port level but not on the VLAN subinterface level.

CRS-FP40 supports Limited H-QoS on VLAN/VLAN-Group using L3/1C/1D, L3/1C/nD, and L3/nC/mD QoS Model with up to 8 queues per port in each direction.

Table 9 Chassis and Line Card Compatibility Matrix

Chassis
I/O Module
Line Card

Multichassis, CRS-16/S

4 port 10GE LAN (4-10GE)
42-1GE
20-1GE-FLEX
2-10 GE-WL-FLEX
All existing CRS-1 PLIM/SIP800

CRS-MSC-40G-B

CRS-8/S, CRS-4/S

4 port 10GE LAN (4-10GE)
42-1GE
20-1GE-FLEX
2-10 GE-WL-FLE

CRS-FP401 or CRS-MSC-40G-B

All existing CRS-1 PLIM/SIP800

CRS-MSC-40G-B

1 CRS-FP40 is supported only in 4/8 slot chassis and can be only paired with new PLIMs. New PLIMs can be paired with the CRS-FP40 and CRS-MSC-40G-B


Table 10 SPA Support for FLEX PLIMs

FLEX PLIM
SPA Type
SPA

20-1GE-FLEX
2-10 GE-WL-FLEX

POS

SPA-4XOC3-POS

SPA-8XOC12-POS (Multi-rate1 )

SPA-2XOC48POS/RPR

SPA-4XOC48POS/RPR

SPA-OC192POS-VSR

SPA-OC192POS-XFP

Ethernet

SPA-1X10GE-L-V2

SPA-1X10GE-WL-V2

SPA-10X1GE-V2

SPA-8X1GE

SPA-8X1GE-V2

SPA-5X1GE-V2

1 Multi-rate: SPA-8XOC12-POS can support SFP-OC12-x and SFP-OC3-x.


Cisco XR 12000 Series Router-Specific Hardware Features

The following new features in Cisco IOS XR Software Release 3.8.1 are supported on the Cisco XR 12000 Series Router platform:

E5 ATM Layer-2 TPv3 and FRF12 Over L2 VP

SPA-OC3/STM1 1&3 port; SPA-OC12/STM4 1-port

SPA-2CTH3-CE-ATM

L2TPv3 ATM like-to-like pseudowires on Engine 5 LC (cell-relay, cell-packing, AAL5)

L2TPv3 IP Interworking on Engine 5 LCs:

Ethernet port mode / 1Q (VLAN) <—> ATM AAL5 (SNAP/Mux/NLPID)

Frame Relay point-to-point DLCI/MLFR <—> ATM AAL5 (SNAP/Mux/NLPID)


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 Software Release 3.8.1. To disable the timestamp prompt, use the timestamp disable command. For more information, see http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/system_management/command/reference/yr38term.html#wp1311395.

For Cisco IOS XR Software Release 3.6.0 and later releases, WRED statements are collapsed, so 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 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 Cisco XR 12000 Series Routers.

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.

L2TPv3 traffic is not supported on Ethernet bundle interfaces on the Cisco XR 12000 Series Router.

In Cisco IOS XR Release 3.8.1, the show running-config command includes an option to display the large configuration format. Using the formal option means that the output does not include submode indentations.

The following commands are not supported on the Cisco CRS-1 Series Router:

affinity location set

affinity location type

affinity program

affinity self

When configuring the LDP (Label Distribution Protocol) GR (graceful restart) process in a network with multiple [link and/or targeted] LDP hello adjacencies with the same neighbor, make sure that GR is activated on the session before any hello adjacency times out due to neighbor control plane failures. One way of achieving this is by configuring a lower session hold time between neighbors such that session time out always occurs before hello adjacency can time out. Cisco recommends setting LDP session hold time using the following formula:

LDP session hold time <= (Hello hold time - Hello interval) * 3

This means that for default values of 15/5 seconds respectively for the link Hello hold time and the Hello interval, the LDP session hold time should be set to 30 seconds or less.

For more information, refer to the "Implementing MPLS Label Distribution Protocol on Cisco IOS XR Software" section of the Cisco IOS XR MPLS Configuration Guide, Release 3.8.1.

Minimum Flash Disk Requirements When Upgrading to Release 3.8.1

Cisco IOS XR Software Release 3.8.1 requires a 2-GB flash disk as a minimum, so if your Cisco CRS-1 or 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.8.1.

The PCMCIA 1-GB flash disk was the default size for the Cisco CRS-1 running Cisco IOS XR Software Release 3.6 and earlier and for the Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.5 and earlier.

A 4-GB flash disk is available for both platforms and can be installed instead of the 2-GB for greater disk storage for Cisco IOS XR Software Release 3.4 and later.

To upgrade from a 1-GB flash disk to a 2-GB or greater flash disk, refer to the Cisco XR12000 and CRS-1 Flash Disk Upgrade Tasks document at http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.pdf.

Additional upgrade instructions for the Cisco CRS-1 router are available from http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/ReplacingPCMCIACardOnCRS-1.pdf.

Caveats

Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious.

The following caveats are open for Cisco IOS XR Software Release 3.8.1 on the router platforms indicated:

Caveats Specific to the Cisco CRS-1 Router

Cisco IOS XR Caveats

Caveats Specific to the Cisco XR 12000 Series Router

Caveats Specific to the Cisco CRS-1 Router

The following caveats are specific to the Cisco CRS-1 platform:

CSCta84988

Symptom:

Cisco CRS-1 systems might not reload successfully due to fabric planes remaining in MCAST DOWN state until manually recovered.

Description:

Occasionally on CRS-1 Multi-chassis systems with greater than 2 active planes the system may come up with one or more fabric planes in the MCAST DOWN state following a system reload.

The fabric plane state is found by issuing the show controllers fabric plane all admin command as shown in Example 1. If all odd or all even planes are in the MCAST DOWN state, the system does not come up and eventually reloads.

Example 1 Fabric Plane States in a Failed Condition

RP/0/RP0/CPU0:router# admin
RP/0/RP0/CPU0:router(admin)# show controllers fabric plane all
 
Plane  Admin   Oper   up->dn        Down    Total     Down
Id     State   State  counter       Flags   Bundles   Bundles
 ------------------------------------------------------------
 0     UP     MCAST_DOWN 0          m          27        18
 1     UP     UP         0                     27        15
 2     UP     MCAST_DOWN 0          m          27        18
 3     UP     UP         0                     27        15
 4     UP     UP         0                     27        15
 5     UP     UP         0                     27        15
 6     UP     UP         0                     27        15
 7     UP     UP         0                     27        15
 
   
 
   

Conditions:

This issue might occur after a system reload.

Workaround:

None.

Recovery:

Use the following procedure to recover from this problem:

1. Determine the affected planes by issuing the admin command admin show controllers fabric plane all.

The affected planes report the operating state as MCAST_ DOWN.

2. Determine the affected S13 card in the affected plane.

Each line card chassis rack that is present in the system has an associated S13 card for each plane. For example, if a system that has three LCCs, the S13 cards for plane 0 are: 0/SM0/SP, 1/SM0/SP and 2/SM0/SP.

3. Issue the following command for all SM cards in the affected plane:

show controllers backplane ethernet clients 25 statistics location [R]/sm[P]/sp]

where:

[R] is for each rack in the system, and [P] is for each affected plane in the system.

The following example shows LCC0 if plane 0 is MCAST_DOWN:

show controllers backplane ethernet clients 25 statistics location 0/sm0/sp
 
   

Repeat this command for all LCCs for each affected plane.

4. In the resulting display, look for the following line:

Rx mem score 264, alloc fails 0, free fails 0  
 
   

If the Rx mem score is 0 or any value other than 264, the card is OK.

If the Rx mem score is 264, this card is affected.

5. Reload the affected S13 card by issuing the following admin command:

hw-module location [R]/SM[P]/SP reload
 
   

where:

[R] is the rack of the affected card and [P] is the affected plane.

For example, if 2/SM0/SP had an Rx mem score of 264, apply the following reload command:

admin hw-module location 2/SM0/SP reload

Cisco IOS XR Caveats

The following caveats apply to both platforms:

CSCso32070

Basic Description:

ipv4_mfwd_partner: %ROUTING-IPV4_MFWD-5-IP_ADDR_RETRY

Symptom:

Multicast packets dropped.

Conditions:

This issue could happen due to SPA/LC OIR or commit replace.

After LC OIRed ARM updates to MFWD for non existent interface, MFWD attempts to update TYPE_ADD/TYPE_CHANGE for a non-existent interface handle. For these event types, MFWD checks with the IFH server to determine the interface type to see if this is a multicast supported interface.

The IFH server does not have any information for this OIRed interface. If this error occurs, ARM update for address does not process. The MFWD retries this failure every 30 seconds. The retry always fails since IFH does not know about the interface.

Workaround:

None.

Recovery:

Clear the mfib database location.

CSCsv00649

Basic Description:

Bundle members with LACP short flap once during RP fail over

Symptom:

Bundle members flap once and traffic loss occurs when LACP short is configured on members.

Conditions:

This issue occurs when RP FO with LACP short is configured on the members.

Workaround:

None.

Impact:

Traffic loss occurs during failover until the members come up. This issue does not have any impact on the router bring-up time.

Recovery:

No manual recovery is necessary. Traffic resumes automatically when the bundle members recover.

CSCsw23382

Basic Description:

devc_conaux crash—multiple triggers

Symptom:

Under specific circumstances, the Devc-conaux process could crash and automatically restart. Sessions on the console or auxiliary port are terminated as a result.


Note Telnet or SSH connections are not affected.


Conditions:

This issue may occur during the following scenarios:

1. Turbo Boot

2. When using the break sequence "Ctrl-C" on the console or auxiliary port of the active or standby route processor to stop excessive output appearing on the terminal

Workaround:

Avoid the use of this break sequence on the active or standby route processor console or auxiliary port.

CSCsx58577

Basic Description:

Process on crashing silently.

Symptom:

Process crash on is seen in named SDR.

Conditions:

The trigger is to issue the show process or show memory command on a non-existing node.

Workaround:

Workaround is not needed because there is no impact on the functionality of the router. However, the show command does not work on a non-existing node.

System Impact:

This issue does not have a functional impact. The show process command does not work on a non-existing node, and an error message displays.

CSCsy52598

Basic Description:

ATM L2 PVCs remain in AIS OUT state after LC OIR.

Symptom:

AIS cells injected on a L2 VC event though L2VPN UP.

Conditions:

Programming the SAR sometimes misses while configuring the subinterface in L2 transport and sometimes with RP FO.

Workaround:

None.

Recovery:

Reload the affected SPA.

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.

Caveats Specific to the Cisco XR 12000 Series Router

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

CSCsw25926

Basic Description:

Removing and adding back PRP-3 to a client LR results in its looped reset.

Symptom:

A PRP-3 RP resets continuously after using an SDR command to add the RP to a named SDR. The functionality of the owner SDR is not affected.

Conditions:

This issue occurs if a PRP-3 RP is removed from a named SDR and added back to the same SDR as part of the same commit.

For example, the router has the following configuration:

0/0/CPU0—Owner LR Active

0/1/CPU0—Owner LR Standby

0/2/CPU0—E5 LC in Owner

0/3/CPU0—Client LR1

0/4/CPU0—Client LR1

0/5/CPU0—E3 LC in LR1

The following command sequence causes 0/3 to start continuously resetting:

RP/0/0/CPU0:ios(admin-config)#logical-router lr1 
RP/0/0/CPU0:ios(admin-config-lr:lr1)#loc 0/3/* 
RP/0/0/CPU0:ios(admin-config-lr:lr1)#no loc 0/3/* 
RP/0/0/CPU0:ios(admin-config-lr:lr1)#logical-router lr2 
RP/0/0/CPU0:ios(admin-config-lr:lr2)#loc 0/3/* RP/0/0/CPU0:ios(admin-config-lr:lr2)#en 
Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:y 
 
   

Workaround:

Avoid triggering this issue by splitting the commit into two commits:

1. In the first commit, remove the node from the first logical router.

2. In the second commit, add the node to the second logical router.

Recovery:

To recover from the issue after it is triggered:

1. Restart psarb and lrd on the DSC.

2. Reload the entire router (owner and all client sdrs).

Resolved Cisco IOS XR Software PSIRT-Related 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

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.8.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.8.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.8.1" section.


Product Life Cycle of Cisco IOS XR Software Release 3.8.1

The Cisco IOS XR Software release strategy is time-based with a fixed release date and life cycle, as opposed to being a feature-based release strategy with a variable release date.

Table 11 lists the major milestones of Cisco IOS XR Software Release 3.8.1.


Note Cisco IOS XR Software Release 3.8.1 follows the Cisco IOS XR Software Release 3.8.0 product life cycle.


Table 11 Major Milestones for Cisco IOS XR Software Release 3.8.1 

Milestone
Definition
Date

Availability Date

The date that the Cisco IOS XR Software Release 3.8.0 information is published on Cisco.com and becomes available to the general public.

March 20, 2009

End-of-Life Announcement Date

The official End-of-Life document that announces the end of sale and end of life of Cisco IOS XR Software Release 3.8.0 is distributed to the public.

December 31, 2009

End-of-Sale Date

The last date to order the product through Cisco point-of-sale mechanisms. The product is no longer for sale after this date.

September 30, 2010

End-of-Maintenance Date

This marks end of engineering, maintenance rebuilds, and software fixes through rebuilds of Cisco IOS XR Software Release 3.8.x and through SMUs built off of Cisco IOS XR Software, Release 3.8.x. After this date, maintenance rebuilds and software-fix support will be provided only through rebuilds of Cisco IOS XR Software Release 3.9.x or later.

June 30, 2011

End of Software Maintenance Releases through migration: OS Software

The last date that Cisco Engineering may release any final software maintenance releases or bug fixes through SMU for issues seen on Cisco IOS XR Software, Release 3.8.x. From June 30, 2011 until June 30, 2012, maintenance rebuilds and software fix through SMU support for Cisco IOS XR Software Release 3.8.x will be provided only through migration to rebuilds of Cisco IOS XR Software Release 3.9.x or later releases, and through SMUs built off of Cisco IOS XR Software Release 3.9.x or later releases, as appropriate. After June 30, 2012, Cisco Engineering will no longer develop, repair, maintain, or test Cisco IOS XR Software Release 3.8.x.

June 30, 2012

Last Date of Support

The last date to receive service and support for the product. After this date, all support services for the product are unavailable and the product becomes obsolete.

September 30, 2015


For official End-of-Life and End-of-Sale announcements for Cisco IOS XR software, please visit http://www.cisco.com/en/US/products/ps5845/prod_eol_notices_list.html or contact your local account representative.

Troubleshooting

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

Related Documentation

The following sections describe the documentation available for the Cisco CRS-1 router and the Cisco XR 12000 Series Router. Documentation is available in the form of PDF and HTML files and is available on www.cisco.com:

Hardware Documents

Software Documents

Hardware Documents

You can find the most current hardware documentation at the following URLs:

Cisco CRS-1:

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

Cisco XR 12000 Series Router:

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

Software Documents

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.8 for a list of Cisco IOS XR Release 3.8.1 software documentation.

You can find the most current software documentation for the Cisco CRS-1 and Cisco XR 12000 Series Router at the following URL:

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

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

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.