Guest

Cisco IOS XR Software (End-of-Sale)

Release Notes for Cisco CRS-1 Series Router for Cisco IOS XR Software Release 3.9.2

  • Viewing Options

  • PDF (757.0 KB)
  • Feedback
Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.2

Table Of Contents

Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.2

Key Changes from Previous Releases in Cisco IOS XR Release 3.9.2

Contents

Introduction

System Requirements

Feature Set Table

Memory Requirements

Hardware Supported

Software Compatibility

Other Firmware Support

Determining Your Software Version

New Features in Cisco IOS XR Software Release 3.9.2

New Software Features Supported on all Platforms

Cisco CRS-1 Router Specific Software Features

ATM UNI (L3VPN)

ACL-Chaining (Multi-ACL)

QoS Granularity

CRS 6PE-Pr-VRF-CE-Label

8 + x delivery

8 port 10GE XFP Support

Heartbeat Loss Debug Enhancement

New Hardware Features for the Cisco CRS-1 Router

ACL-Chaining (Multi-ACL) Commands

ipv4 access-group

ipv6 access-group

QoS Granularity Commands

hw-module qos input police granularity

show hw-module qos input police granularity

hw-module qos output police granularity

show hw-module qos output police granularity

hw-module qos output shape granularity

show hw-module qos output shape granularity

6PE per VRF Commands

label-allocation-mode

8 port 10GE XFP Support Commands

controller wanphy

Important Notes

New DWDM Configuration Requirement

Summary of Important DWDM Changes in Cisco IOS XR Software Release 3.9.0 and Later Releases

Configuration Examples in Cisco IOS XR Software Release 3.9.0 and Later Releases

Minimum Flash Disk Requirements When Upgrading to Release 3.9.2

Caveats

Resolved Release 3.9.2 Cisco IOS XR PSIRT-Related Caveats

Open Release 3.9.2 Cisco IOS XR Caveats

Open Release 3.9.2 Caveats Specific to the Cisco CRS-1 Router

Upgrading Cisco IOS XR Software

Troubleshooting

Related Documentation

Obtaining Documentation and Submitting a Service Request


Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.2


April 15, 2013

Cisco IOS XR Software Release 3.9.2

Text Part Number OL-23386-03

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


Note For information on the Cisco CRS-1 Router running Cisco IOS XR Software Release 3.9.2, see the "Important Notes" section.


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

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

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

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

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

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

Key Changes from Previous Releases in Cisco IOS XR Release 3.9.2

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

Contents

These release notes contain the following sections:

Introduction

System Requirements

Determining Your Software Version

New Features in Cisco IOS XR Software Release 3.9.2

Important Notes

New DWDM Configuration Requirement

Minimum Flash Disk Requirements When Upgrading to Release 3.9.2

Caveats

Upgrading Cisco IOS XR Software

Troubleshooting

Related Documentation

Obtaining Documentation and Submitting a Service Request

Introduction

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

Cisco IOS XR software running on the Cisco CRS-1 Router provides the following features and benefits:

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

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

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

Multicast—Provides comprehensive IP Multicast software including Source Specific Multicast (SSM) and Protocol Independent Multicast (PIM) in Sparse Mode only, and 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 is used to configure QoS features.

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

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

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

Availability—Supports rich availability features such as fault containment, fault tolerance, fast switchover, link aggregation, nonstop routing for ISIS, LDP, BGP, and OSPF, and nonstop forwarding (NSF).

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

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

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

Enhanced core competencies:

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

Traffic engineering support for unequal load balancing

Path Computation Element (PCE) capability for traffic engineering

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

System Requirements

This section describes the system requirements for Cisco IOS XR Software Release 3.9.2 supported on the Cisco CRS-1 Router. 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 the "Determining Your Software Version" section.

Feature Set Table

Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.9.2 features.

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

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

Feature Set
Filename
Description
Composite Package

Cisco IOS XR IP Unicast Routing Core Bundle

comp-hfr-mini.pie-3.9.2

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

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

CORBA2 agent, XML3 Parser, and HTTP server packages.

Cisco IOS XR MPLS Package

hfr-mpls-p.pie-3.9.2

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

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

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

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

Please refer to the Cisco CRS-1 command reference documentation located at the following URL:

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

Cisco IOS XR FPD Package

hfr-fpd.pie-3.9.2

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

Cisco IOS XR Diagnostic Package

hfr-diags.pie-3.9.2

Diagnostic utilities for Cisco IOS XR routers.

Cisco IOS XR Documentation Package

hfr-doc.pie-3.9.2

.man pages for Cisco IOS XR software on the Cisco CRS-1 chassis.

Cisco IOS XR Carrier Grade NAT Package

hfr-cgn-p.pie-3.9.2

Support for Carrier Grade NAT on Cisco CRS-1 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 Router TAR files.

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

Feature Set
Filename
Description

Cisco IOS XR IP/MPLS Core Software

CRS-1-iosxr-3.9.2.tar

Cisco IOS XR IP Unicast Routing Core Bundle

Cisco IOS XR Manageability Package

Cisco IOS XR MPLS Package

Cisco IOS XR Multicast Package

Cisco IOS XR Diagnostic Package

Cisco IOS XR FPD Package

Cisco IOS XR IP/MPLS Core Software 3DES

CRS-1-iosxr-k9-3.9.2.tar

Cisco IOS XR IP Unicast Routing Core Bundle

Cisco IOS XR Manageability Package

Cisco IOS XR MPLS Package

Cisco IOS XR Multicast Package

Cisco IOS XR Security Package

Cisco IOS XR Diagnostic Package

Cisco IOS XR FPD Package


Memory Requirements


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

The minimum memory requirements for a Cisco CRS-1 running Cisco IOS XR Software Release 3.9.2 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.9.2 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB or 4 GB before upgrading to Cisco IOS XR Software Release 3.9.2. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.2" section.


Hardware Supported

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

Table 3 lists the supported hardware components on the Cisco 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 Integrated Switch

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 8-Port Ten Gigabit Ethernet Interface Module

8-10GBE-WL-XFP

3.9.1

Cisco CRS-1 Series 4-Port Ten Gigabit Ethernet Interface Module

4-10GBE-WL-XFP

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

Cisco CRS-1 Carrier Grade Service Engine Interface Modules

Cisco CRS-1 Series Carrier Grade Service Engine PLIM

CRS-CGSE-PLIM

3.9.1


Software Compatibility

Cisco IOS XR Software Release 3.9.2 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 supports the following firmware code:

The minimum ROMMON version required for this release is 1.54. For more information about ROMMON specifications, see http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html. For information about upgrading the ROMMON, refer to the Cisco IOS XR ROM Monitor Guide for the Cisco CRS-1 Router at:
http://www.cisco.com/en/US/products/ps5763/products_installation_and_configuration_guides_list.html

The minimum CPUCNTRL version required for this release is 2.07. For more information about CPU controller bits, refer to the Cisco IOS XR System Management Configuration Guide for the Cisco CRS-1 Router at: http://www.cisco.com/en/US/products/ps5763/products_installation_and_configuration_guides_list.html

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

 
   
RP/0/RP0/CPU0:FQ-PE1(admin)#show fpd package
Mon Sep 27 08:32:32.106 PDT
 
   
=============================== ================================================
                                        Field Programmable Device Package
                                ================================================
                                                                 SW      Min Req   Min Req
Card Type            FPD Description            Type Subtype   Version   SW Ver    HW Vers
==================== ========================== ==== ======= =========== ========  =======
1OC768-ITU/C         OPTICS FIRMWARE 110B10     lc   fpga2     110.10        0.0       0.0
------------------------------------------------------------------------------------------
1OC768-DWDM-L        OPTICS FIRMWARE 110B10     lc   fpga2     110.10        0.0       0.0
------------------------------------------------------------------------------------------
1OC768-DPSK/C        OPTICS FIRMWARE 110B14     lc   fpga2     110.14        0.0       0.0
------------------------------------------------------------------------------------------
1OC768-DPSK/C-O      OPTICS FIRMWARE 110B14     lc   fpga2     110.14        0.0       0.0
------------------------------------------------------------------------------------------
1OC768-DPSK/C-E      OPTICS FIRMWARE 110B14     lc   fpga2     110.14        0.0       0.0
------------------------------------------------------------------------------------------
CRS-CGSE-PLIM        FPGA mCPU0 0.559           lc   fpga2       0.559       0.0       0.0
                     FPGA sCPU0 0.559           lc   fpga3       0.559       0.0       0.0
                     FPGA mCPU1 0.559           lc   fpga4       0.559       0.0       0.0
                     FPGA sCPU1 0.559           lc   fpga5       0.559       0.0       0.0
                     FPGA PLIM_SVC 0.41014      lc   fpga1       0.41014     0.0       0.0
------------------------------------------------------------------------------------------
CRS1-SIP-800         JACKET FPGA swv6.0         lc   fpga1       6.00        5.0       0.0
					FPGA swv6.0 hwv80          lc   fpga1       6.00        5.0       0.80
------------------------------------------------------------------------------------------
8-10GBE              FPGA swvA.0                lc   fpga1      10.00        0.0       0.0
------------------------------------------------------------------------------------------
OC48-POS-16-ED       FPGA PLIM_OC48 9.0         lc   fpga1       9.00        0.0       0.0
------------------------------------------------------------------------------------------
4-10GBE              FPGA sw_4p_v15.0           lc   fpga1      15.00        0.0       0.0
------------------------------------------------------------------------------------------
8-10GBE              FPGA sw_8p_v15.0           lc   fpga1      15.00        0.0       0.0
------------------------------------------------------------------------------------------
4-10GE               SQUIRREL FPGA 10.0         lc   fpga1      10.00        0.0       0.0
------------------------------------------------------------------------------------------
42-1GE               FPGA swv6.0                lc   fpga1       6.00        0.0       0.0
					FPGA swv6.0 hwv0.80        lc   fpga1       6.00        0.0       0.80
------------------------------------------------------------------------------------------
20-1GE-FLEX          FPGA swv6.0                lc   fpga1       6.00        0.0       0.0
					FPGA swv6.0 hwv0.80        lc   fpga1       6.00        0.0       0.80
------------------------------------------------------------------------------------------
2-10GE-WL-FLEX       FPGA swv6.0                lc   fpga1       6.00        0.0       0.0
					FPGA swv6.0 hwv0.80        lc   fpga1       6.00        0.0       0.80
------------------------------------------------------------------------------------------
Route Processor      ROMMONA swv1.54 asmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
SC                   ROMMONA swv1.54 asmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
RP                   ROMMONA swv1.54 asmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
Shelf Controller GE  ROMMONA swv1.54 asmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
RP                   ROMMONA swv1.54 asmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
Shelf Controller GE2 ROMMONA swv1.54 asmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
DRP                  ROMMONA swv1.54 asmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
DRP_B                ROMMONA swv1.54 asmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
S1S2S3               ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
S1S3                 ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
S2                   ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
Fabric HS123         ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
Fabric HS123 Star    ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
Fabric HS13 Star     ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
Fabric QQS123        ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
LED                  ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
40G-MSC              ROMMONA swv1.54 asmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
MSC_B                ROMMONA swv1.54 asmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.52        0.0       0.0
                     ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
FP40                 ROMMONA swv1.54 asmp       lc   rommonA     1.53        0.0       0.0
                     ROMMONA swv1.54 dsmp       lc   rommonA     1.53        0.0       0.0
                     ROMMONA swv1.54 sp         lc   rommonA     1.53        0.0       0.0
                     ROMMONB swv1.54 asmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 dsmp       lc   rommon      1.54        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
PSAL                 ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
PSAL                 ROMMONA swv1.54 sp         lc   rommonA     1.54        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
FAN                  ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
FC Fan Controller    ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
LED                  ROMMONA swv1.54 sp         lc   rommonA     1.52        0.0       0.0
                     ROMMONB swv1.54 sp         lc   rommon      1.54        0.0       0.0
------------------------------------------------------------------------------------------
SPA-4XT3/E3          SPA E3 Subrate FPGA        spa  fpga2       1.04        0.0       0.0
                     SPA T3 Subrate FPGA        spa  fpga3       1.04        0.0       0.0
                     SPA I/O FPGA               spa  fpga1       1.00        0.0       0.0
                     SPA ROMMON                 spa  rommon      2.12        0.0       0.0
------------------------------------------------------------------------------------------
SPA-2XT3/E3          SPA E3 Subrate FPGA        spa  fpga2       1.04        0.0       0.0
                     SPA T3 Subrate FPGA        spa  fpga3       1.04        0.0       0.0
                     SPA I/O FPGA               spa  fpga1       1.00        0.0       0.0
                     SPA ROMMON                 spa  rommon      2.12        0.0       0.0
------------------------------------------------------------------------------------------
SPA-OC192POS         SPA FPGA swv1.3            spa  fpga1       1.03        0.0       0.0
------------------------------------------------------------------------------------------
SPA-8XOC12-POS       SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.5
------------------------------------------------------------------------------------------
SPA-4XOC3-POS        SPA FPGA swv3.4            spa  fpga1       3.04        0.0       0.0
------------------------------------------------------------------------------------------
SPA-OC192POS-XFP     SPA FPGA swv1.2            spa  fpga1       1.02        0.0       0.0
------------------------------------------------------------------------------------------
SPA-8X1GE            SPA FPGA swv1.8            spa  fpga1       1.08        0.0       0.0
------------------------------------------------------------------------------------------
SPA-2XOC48POS/RPR    SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.0
------------------------------------------------------------------------------------------
SPA-4XOC48POS/RPR    SPA FPGA swv1.0            spa  fpga1       1.00        0.0       0.0
------------------------------------------------------------------------------------------
SPA-10X1GE-V2        SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0
------------------------------------------------------------------------------------------
SPA-8X1GE-V2         SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0
------------------------------------------------------------------------------------------
SPA-5X1GE-V2         SPA FPGA swv1.10           spa  fpga1       1.10        0.0       0.0
------------------------------------------------------------------------------------------
SPA-1X10GE-L-V2      SPA FPGA swv1.11           spa  fpga1       1.11        0.0       0.0
------------------------------------------------------------------------------------------
SPA-1X10GE-WL-V2     SPA FPGA swv1.11           spa  fpga1       1.11        0.0       0.0
------------------------------------------------------------------------------------------
SPA-1XOC3-ATM-V2     SPA FPGA swv1.2            spa  fpga1       1.03        0.0       0.0
------------------------------------------------------------------------------------------
SPA-2XOC3-ATM-V2     SPA FPGA swv1.2            spa  fpga1       1.03        0.0       0.0
------------------------------------------------------------------------------------------
SPA-3XOC3-ATM-V2     SPA FPGA swv1.2            spa  fpga1       1.03        0.0       0.0
------------------------------------------------------------------------------------------
SPA-1XOC12-ATM-V2    SPA FPGA swv1.2            spa  fpga1       1.03        0.0       0.0
------------------------------------------------------------------------------------------

Determining Your Software Version

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


Step 1 Establish a Telnet session with the router.

Step 2 Enter the show version command from EXEC mode.

 
   
RP/0/RP0/CPU0:FQ-PE1#show version
Sun Sep 26 09:02:52.591 PDT
 
   
Cisco IOS XR Software, Version 3.9.2[00]
Copyright (c) 2010 by Cisco Systems, Inc.
 
   
ROM: System Bootstrap, Version 1.54(20091016:214209) [CRS-1 ROMMON],
 
   
FQ-PE1 uptime is 1 day, 15 hours, 23 minutes
System image file is "bootflash:disk0/hfr-os-mbi-3.9.2/mbihfr-rp.vm"
 
   
cisco CRS-16/S (7455) processor with 4194304K bytes of memory.
7455 processor at 800Mhz, Revision 3.4
 
   
2 Management Ethernet
75 GigabitEthernet
36 SONET/SDH
35 Packet over SONET/SDH
1 Asynchronous Transfer Mode
8 TenGigE
4 T3
4 Serial network interface(s)
1019k bytes of non-volatile configuration memory.
38079M bytes of hard disk.
2053440k bytes of disk0: (Sector size 512 bytes).
 
   
Boot device on node 0/5/CPU0 is mem:
Package active on node 0/5/CPU0:
hfr-fpd, V 3.9.2[00], Cisco Systems, at disk0:hfr-fpd-3.9.2
    Built on Fri Sep 24 04:12:43 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-diags, V 3.9.2[00], Cisco Systems, at disk0:hfr-diags-3.9.2
    Built on Fri Sep 24 04:12:27 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-mcast, V 3.9.2[00], Cisco Systems, at disk0:hfr-mcast-3.9.2
    Built on Fri Sep 24 06:49:25 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-mpls, V 3.9.2[00], Cisco Systems, at disk0:hfr-mpls-3.9.2
    Built on Fri Sep 24 06:49:10 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-lc, V 3.9.2[00], Cisco Systems, at disk0:hfr-lc-3.9.2
    Built on Fri Sep 24 03:58:19 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-fwdg, V 3.9.2[00], Cisco Systems, at disk0:hfr-fwdg-3.9.2
    Built on Fri Sep 24 03:57:06 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-admin, V 3.9.2[00], Cisco Systems, at disk0:hfr-admin-3.9.2
    Built on Fri Sep 24 03:56:20 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-base, V 3.9.2[00], Cisco Systems, at disk0:hfr-base-3.9.2
    Built on Fri Sep 24 03:59:33 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0
 
   
hfr-os-mbi, V 3.9.2[00], Cisco Systems, at disk0:hfr-os-mbi-3.9.2
    Built on Fri Sep 24 03:51:00 PDT 2010
    By sjc-lds-511 in /auto/srcarchive4/production/3.9.2/hfr/workspace for c4.2.1-p0

New Features in Cisco IOS XR Software Release 3.9.2

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

New Software Features Supported on all Platforms

Cisco CRS-1 Router Specific Software Features

New Hardware Features for the Cisco CRS-1 Router


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


New Software Features Supported on all Platforms

There are no new platform software features in Cisco IOS XR Software Release 3.9.2.

Cisco CRS-1 Router Specific Software Features

The following new software features were introduced in Cisco IOS XR Software Release 3.9.2 on the Cisco CRS-1 platform:

ATM UNI (L3VPN)

ACL-Chaining (Multi-ACL)

QoS Granularity

CRS 6PE-Pr-VRF-CE-Label

8 + x delivery

8 port 10GE XFP Support

Heartbeat Loss Debug Enhancement

ATM UNI (L3VPN)

Cisco IOS XR Software Release 3.9.2 adds support for the ATM UNI feature on the Cisco CRS-1 Carrier Routing System. This feature enables customers to migrate from older platforms to the CRS-1 platform.

The following ATM SPAs are supported:

1-port OC3c/STM1 ATM SPA

3-port OC3c/STM1 ATM SPA

1-port OC12c/STM4 ATM SPA

The following ATM UNI features are supported:

ATM UNI L3 VC termination (UNI 3.0/3.1)

ILMI

Per VC QoS

ATM COS

MPLS L3VPN per VC sub-interface

Support for both L2VPN and L3VPM under the same physical interface

ATM F4/F5 OAM

MR-APS

IGP routing with VRF/VPN support: OSPF, BGP, EIGRP, RIP and static

150 VC/VP connections per port, maximum VC/VP numbering up to 1024

ACL-Chaining (Multi-ACL)

ACL-Chaining (Multi-ACL) enables customers to apply two IPv4/IPv6 (common and interface) ACLs on an interface for packet filtering on the CRS-1 router. One of the ACL's is common across multiple interfaces on the line card. This provides TCAM/HW scalability. This feature allows users to segregate ACEs across two different ACLs (customer and provider specific). This results in operational efficiency, less number of configured lines, and in turn, improved scalability.

This feature is only supported on ingress (input). There are 200 entries per protocol reserved in TCAM HW for IPv4 and IPv6 common ACLs.

For detailed information about new or modified commands, see ACL-Chaining (Multi-ACL) Commands.

QoS Granularity

QoS Granularity allows users to select QoS shaping and policing granularity. Shaping and policing granularity on the MSC card supports low speed interfaces or low shaping / policing rates. This feature is supported on all interface types.

The shaping allows users to select egress QoS shaping granularity actions between 256kbps, 128kbps, and 64kbps. This is on a per line-card basis, and it applies to all MSC-40G linecards (rev-a, rev-b, FP-40). This is not applicable for MSC-140G Taiko Linecards.

Policing granularity is implemented on a per interface basis. This enables users to configure the granularity at the service-policy attachment time. There are four levels of granularity that can be applied to policing. Those levels of granularity are: 30.5kbps, 61kbps, 122kbps, and 244 kbps.

For detailed information about new or modified commands, see QoS Granularity Commands.

CRS 6PE-Pr-VRF-CE-Label

This feature allows customers to choose the label allocation mode (per-vrf/per-ce) for the default VRF's IPv6 routes.

For detailed information about new or modified commands, see 6PE per VRF Commands.

8 + x delivery

Cisco IOS XR Software Release 3.9.2 introduces support on the Cisco CRS Series Router platform for running Ipv4 Multicast on a total of 128 Line Cards spread over 8 Line Card Chassis (the Multi-Chassis platform).

There are no new or modified commands as a result of this feature.

8 port 10GE XFP Support

Cisco IOS XR Software Release 3.9.2 introduces support on the Cisco CRS Series Router platform of the 8x10GE PLIM card. This card provides the Cisco CRS-1 Carrier Routing System platform with 8 10GE interfaces on a single linecard.

For installation information, please see the Cisco CRS-1 Carrier Routing System Gigabit Ethernet Physical Layer Interface Module Installation Note:

http://www.cisco.com/en/US/docs/routers/crs/crs1/plim/installation/guide/eth6437.html

For detailed information about new or modified commands, see 8 port 10GE XFP Support Commands.

Heartbeat Loss Debug Enhancement

Cisco IOS XR Software Release 3.9.2 adds support for saving remote node crash information after heartbeat loss is reported to the Shelf Manager on the Cisco CRS-1 Carrier Routing System.

New Hardware Features for the Cisco CRS-1 Router

The following new hardware feature was introduced in Cisco IOS XR Software Release 3.9.2 on the Cisco CRS-1 Router.

8 port 10GE XFP Support

4 port 10GE XFP Support


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


ACL-Chaining (Multi-ACL) Commands

This section provides details on the commands introduced or changed in Cisco IOS XR Software Release 3.9.2 that are specific to this feature. The ACL Chaining feature extends the existing access-group command to accept a common ACL along with the interface specific ACL. The following commands are modified:

ipv4 access-group

ipv6 access-group

ipv4 access-group

To control access to an interface, use the ipv4 access-group command in interface configuration mode. To remove the specified access group, use the no form of this command.

ipv4 access-group access-list-name {common <acl-p> {[<acl1> ingress [hardware-count] [interface-statistics]] | ingress} | <acl1> {ingress | egress} [hardware-count] [interface-statistics]}

no ipv4 access-group access-list-name {common <acl-p> {[<acl1> ingress [hardware-count] [interface-statistics]] | ingress} | <acl1> {ingress | egress} [hardware-count] [interface-statistics]}

Syntax Description

access-list-name

The name of the ipv4 access list as specified by the ipv4 access-list command.

common

The name of the common ACL. Common ACL is only supported on the ingress direction.

ingress

Filters on inbound packets.

egress

Filters on outbound packets.

hardware-count

(Optional) Specifies to access a group's hardware counters.

interface-statistics

(Optional) Specifies per-interface statistics in the hardware. Not available for common ACL.


Defaults

The interface does not have an IPv4 access list applied to it.

Command Modes

Interface Configuration

Command History

Release
Modification

Release 3.9.2

This command was modified on the Cisco CRS Routers.


Usage Guidelines

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

Use the ipv4 access-group command to control access to an interface. To remove the specified access group, use the no form of the command. Use the access-list-name argument to specify a particular IPv4 access list. Use the ingress keyword to filter on inbound packets or the egress keyword to filter on outbound packets. Use the hardware-count argument to enable hardware counters for the access group.

Permitted packets are counted only when hardware counters are enabled using the hardware-count argument. Denied packets are counted whether hardware counters are enabled or not.


Note For packet filtering applications using the ipv4/ipv6 access-group command, packet counters are maintained in hardware for each direction. If an access group is used on multiple interfaces in the same direction, then packets are counted for each interface that has the hardware-count argument enabled.


If the access list permits the addresses, the software continues to process the packet. If the access list denies the address, the software discards the packet and returns an Internet Control Message Protocol (ICMP) host unreachable message.

If the specified access list does not exist, all packets are passed.

By default, the unique or per-interface ACL statistics are disabled.

Task ID
Task ID
Operations

acl

read, write

network

read, write


Examples

Following is an example of the show access-lists command:

DRP/0/4/CPU0:P2_CRS-8_sdr2#show access-lists
Tue Jun 22 05:30:17.739 DST
ipv4 access-list acl-common
 10 permit ipv4 host 205.205.205.1 host 200.175.175.1 log-input
 15 deny ipv4 any host 200.175.175.1
 20 permit ipv4 host 205.205.205.1 host 201.175.175.1 log-input
 25 deny ipv4 any host 201.175.175.1
 30 permit ipv4 host 205.205.205.1 host 202.175.175.1 log-input
 35 deny ipv4 any host 202.175.175.1
ipv4 access-list acl-unique1
 10 permit ipv4 host 205.205.205.1 host 203.175.175.1 log-input
 15 deny ipv4 any host 203.175.175.1
 20 permit ipv4 any any
ipv4 access-list ssm-acl
 10 permit ipv4 232.0.0.0 0.255.255.255 any log
 
   

Following in an example of a configured IPv4 ACL:

DRP/0/4/CPU0:P2_CRS-8_sdr2(config-if)#ipv4 access-group common acl-common acl-unique1 
ingress

Related Commands

Command
Description

clear access-list ipv4

Resets the IPv4 list match counters.

deny (IPv4)

Sets the deny conditions for an IPv4 access list.

ipv4 access-list

Defines an IPv4 access list and enters IPv4 access list configuration mode.

permit (IPv4)

Sets the permit conditions for an IPv4 access list.

show access-lists ipv4

Displays the contents of all current IPv4 lists.

show ipv4 interface

Displays the usability status of interfaces configured for IPv4.


ipv6 access-group

To control access to an interface, use the ipv6 access-group command in interface configuration mode. To remove the specified access group, use the no form of this command.

ipv6 access-group access-list-name {common <acl-p> {[<acl1> ingress [hardware-count] [interface-statistics]] | ingress} | <acl1> {ingress | egress} [hardware-count] [interface-statistics]}

no ipv6 access-group access-list-name {common <acl-p> {[<acl1> ingress [hardware-count] [interface-statistics]] | ingress} | <acl1> {ingress | egress} [hardware-count] [interface-statistics]}

Syntax Description

access-list-name

The name of the ipv6 access list as specified by the ipv6 access-list command.

common

The name of the common ACL. Common ACL is only supported on the ingress direction.

ingress

Filters on inbound packets.

egress

Filters on outbound packets.

hardware-count

(Optional) Specifies to access a group's hardware counters.

interface-statistics

(Optional) Specifies per-interface statistics in the hardware. Not available for common ACL.


Defaults

The interface does not have an IPv6 access list applied to it.

Command Modes

Interface Configuration

Command History

Release
Modification

Release 3.9.2

This command was modified on the Cisco CRS Routers.


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 ipv6 access-group command is similar to the ipv4 access-group command, except that it is IPv6-specific.

Use the ipv6 access-group command to control access to an interface. To remove the specified access group, use the no form of the command. Use the access-list-name to specify a particular IPv6 access list. Use the ingress keyword to filter on inbound packets or the egress keyword to filter on outbound packets.


Note For packet filtering applications using the ipv6 access-group command, packet counters are maintained in hardware for each direction. If an access group is used on multiple interfaces in the same direction, then packets are counted for each interface.


If the access list permits the addresses, the software continues to process the packet. If the access list denies the address, the software discards the packet and returns a rate-limited Internet Control Message Protocol (ICMP) host unreachable message.

If the specified access list does not exist, all packets are passed.

By default, the unique or per-interface ACL statistics are disabled.

Task ID
Task ID
Operations

acl

read, write

ipv6

read, write


Examples

Following is an example of the show access command:

DRP/0/4/CPU0:P2_CRS-8_sdr2#show access ipv6
Tue Jun 22 12:20:57.817 DST
ipv6 access-list acl-common-v6
 10 permit ipv6 host 2001:db8::202:202:202:202 host 2001:db8::204:175:175:1 log-input
 15 deny ipv6 any host 2001:db8::204:175:175:1
 20 permit ipv6 host 2001:db8::202:202:202:202 host 2001:db8::205:175:175:1 log-input
 25 deny ipv6 any host 2001:db8::205:175:175:1
 30 permit ipv6 host 2001:db8::202:202:202:202 host 2001:db8::206:175:175:1 log-input
 35 deny ipv6 any host 2001:db8::206:175:175:1
ipv6 access-list acl-unique1-v6
 10 permit ipv6 host 2001:db8::202:202:202:202 host 2001:db8::207:175:175:1 log-input
 15 deny ipv6 any host 2001:db8::207:175:175:1
 20 permit ipv6 any any
 
   

Following in an example of a configured IPv6 ACL:

DRP/0/4/CPU0:P2_CRS-8_sdr2(config-if)#ipv6 access-group common acl-common-v6 
acl-unique1-v6 ingress

Related Commands

Command
Description

copy access-list ipv6

Copies an existing IPv6 access list.

deny (IPv6)

Sets the deny conditions for an IPv6 access list.

ipv6 access-list

Defines an IPv6 access list and enters IPv6 access list configuration mode.

permit (IPv6)

Sets the permit conditions for an IPv6 access list.

show access-lists ipv6

Displays the contents of all current IPv6 lists.

show ipv6 interface

Displays the usability status of interfaces configured for IPv6.


QoS Granularity Commands

This section provides details on the commands introduced or changed in Cisco IOS XR Software Release 3.9.2 that are specific to this feature. The following commands are new:

hw-module qos input police granularity

show hw-module qos input police granularity

hw-module qos output police granularity

show hw-module qos output police granularity

hw-module qos output shape granularity

show hw-module qos output shape granularity

hw-module qos input police granularity

To set the QoS input police granularity, use the hw-module qos input police granularity command in Config mode. To remove the QoS input police granularity from the configuration file and restore the system to its default condition, use the no form of this command.

hw-module qos input police granularity <x> location <rack>/<slot>/<instance>

no hw-module qos input police granularity <x> location <rack>/<slot>/<instance>

Syntax Description

granularity

The input police rate deviation tolerance in percent (%) units. The range of value is 1-100.

location

The name of the location to apply the input police rate deviation tolerance.


Defaults

2%

Command Modes

Configuration

Command History

Release
Modification

Release 3.9.2

This command was introduced on the Cisco CRS Routers.


Usage Guidelines

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

Task ID
Task ID
Operations

root-lr

read, write


Examples

RP/0/RP0/CPU0:P2_CRS-8(config)#hw-module qos input police granularity 4 location 
0/6/CPU0

Related Commands

Command
Description

show hw-module qos input police granularity

This command displays the QoS input police granularity.


show hw-module qos input police granularity

To display the QoS input police granularity, use the show hw-module qos input police granularity command in EXEC mode.

show hw-module qos input police location <rack>/<slot>/<instance>

Syntax Description

location

The name of the location to display the police rate deviation tolerance.


Defaults

Add content or N/A

Command Modes

EXEC

Command History

Release
Modification

Release 3.9.2

This command was introduced on the Cisco CRS Routers.


Usage Guidelines

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

Task ID`
Task ID
Operations

root-lr

read, write


Examples

Following is an example of the show hw-module qos input police granularity command:

RP/0/RP0/CPU0:P2_CRS-8#show hw-module qos input police granularity 0/6/CPU0
Tue Jun 22 00:53:37.126 DST
=========================== 
    QOS POLICE GRANULARITY   
 =========================== 
                             
 Location     Rate Deviation 
              Tolerance (%)  
==========    ============== 
0/6/CPU0            2
----------------------------
 
   
 
   

hw-module qos output police granularity

To set the QoS output police granularity, use the hw-module qos output police granularity command in Config mode. To remove the QoS output police granularity from the configuration file and restore the system to its default condition, use the no form of this command.

hw-module qos output police granularity <x> location <rack>/<slot>/<instance>

no hw-module qos output police granularity <x> location <rack>/<slot>/<instance>

Syntax Description

granularity

The output police rate deviation tolerance in percent (%) units. The range of value is 1-100.

location

The name of the location to apply the output police rate deviation tolerance.


Defaults

2%

Command Modes

Configuration

Command History

Release
Modification

Release 3.9.2

This command was introduced on the Cisco CRS Routers.


Usage Guidelines

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

Task ID
Task ID
Operations

root-lr

read, write


Examples

RP/0/RP0/CPU0:P2_CRS-8(config)#hw-module qos output police granularity 8 location 
0/6/cpu0

Related Commands

Command
Description

show hw-module qos output police granularity

This command displays the QoS output police granularity.


show hw-module qos output police granularity

To display the QoS output police granularity, use the show hw-module qos output police granularity command in EXEC mode.

show hw-module qos output police granularity location <rack>/<slot>/<instance>

Syntax Description

location

The name of the location to display the output police rate deviation tolerance.


Defaults

Add content or N/A

Command Modes

EXEC

Command History

Release
Modification

Release 3.9.2

This command was introduced on the Cisco CRS Routers.


Usage Guidelines

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

Task ID
Task ID
Operations
   

Examples

RP/0/RP0/CPU0:P2_CRS-8#show hw-module qos output police granularity 0/6/CPU0
Tue Jun 22 00:54:06.604 DST
=========================== 
    QOS POLICE GRANULARITY   
 =========================== 
                             
 Location     Rate Deviation 
              Tolerance (%)  
==========    ============== 
0/6/CPU0            5
----------------------------

Related Commands

Command
Description

show hw-module qos input police granularity

This command shows the QoS input police granularity


hw-module qos output shape granularity

To set the QoS output shape granularity, use the hw-module qos output shape granularity command in Config mode. To remove the QoS output shape granularity from the configuration file and restore the system to its default condition, use the no form of this command.

hw-module qos output shape granularity {64 | 128 | 256} location <rack>/<slot>/<instance>

no hw-module qos output shape granularity {64 | 128 | 256} location <rack>/<slot>/<instance>


Note For configured granularity to be effective, the applicable Line Card must be reloaded, or the service policy has to be reapplied on the interface.


Syntax Description

granularity

There are three granularity options: 64, 128, and 256Kbps.

location

The name of the location to apply the output shape granularity.


Defaults

256Kbps

Command Modes

Configuration

Command History

Release
Modification

Release 3.9.2

This command was introduced on the Cisco CRS Routers.


Usage Guidelines

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

Task ID
Task ID
Operations

root-lr

read, write


Examples

RP/0/RP0/CPU0:P2_CRS-8(config)#hw-module qos output shape granularity 128 location 
0/6/cpu0

Related Commands

Command
Description

show hw-module qos output shape granularity

This command displays the QoS output shape granularity.


show hw-module qos output shape granularity

To display the QoS output shape granularity, use the show hw-module qos output shape granularity command in EXEC mode.

show hw-module qos output shape granularity location <rack>/<slot>/<instance>

Syntax Description

location

The name of the location to display the output shape granularity.


Defaults

Add content or N/A

Command Modes

EXEC

Command History

Release
Modification

Release 3.9.2

This command was introduced on the Cisco CRS Routers.


Usage Guidelines

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

Task ID
Task ID
Operations
   

Examples

RP/0/RP0/CPU0:P2_CRS-8#show hw-module qos output shape granularity 0/3/CPU0
Tue Jun 22 00:55:21.199 DST
============= ==================================== 
               QOS SHAPING GRANULARITY              
              ==================================== 
              Configured    HW            LC      
 Location     Shape         Programmed    reload  
              Granularity   Granularity   (Y / N) 
============  ===========   ============ ========
 0/3/CPU0        64Kbps       256Kbps        Y
--------------------------------------------------

Related Commands

Command
Description

show hw-module qos input police granularity

This command shows the QoS input police granularity


6PE per VRF Commands

This section provides details on the commands introduced or changed in Cisco IOS XR Software Release 3.9.2 that are specific to this feature. The 6PE per VRF feature adds support for IPv6. The following command is modified:

label-allocation-mode

label-allocation-mode

To set the MPLS/VPN label allocation mode, use the label-allocation-mode command in VRF configuration mode. To remove the label-allocation-mode command from the configuration file and restore the system to its default condition, use the no form of this command.

label-allocation-mode [per-ce | per-vrf]

no label-allocation-mode [per-ce | per-vrf]

Syntax Description

per-ce

Specifies that the same label is used for all the routes advertised from a unique customer edge (CE) peer or router.

per-vrf

Specifies that the same label is used for all the routes advertised from a unique VRF.


Defaults

Per-prefix is the default label allocation mode.

Command Modes

VRF configuration

Command History

Release
Modification

Release 3.9.2

IPv6 support was added.


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.

Each prefix that belongs to a VRF instance is advertised with a single label, causing an additional lookup to be performed in the VRF forwarding table to determine the customer edge (CE) next hop for the packet. Use the label-allocation-mode command with the per-ce keyword to avoid the additional lookup on the PE router and conserve label space. This mode allows the PE router to allocate one label for every immediate next hop. The label is directly mapped to the next hop so there is no VRF route lookup performed during data forwarding. However, the number of labels allocated is one for each CE rather than one for each prefix.

Task ID
Task ID
Operations

bgp

read, write


Examples

The following example shows how to set the label allocation mode to customer edge:

 
   
RP/0/RP0/CPU0:router(config)# router bgp 109
RP/0/RP0/CPU0:router(config-bgp)# vrf vrf-1
RP/0/RP0/CPU0:router(config-bgp-vrf)# label-allocation-mode per-ce 
 
   

The following example shows how to set the label allocation mode to VRF:

RP/0/RP0/CPU0:router(config)#router bgp 109
RP/0/RP0/CPU0:router(config-bgp)# vrf vrf-1
RP/0/RP0/CPU0:router(config-bgp-vrf)# label-allocation-mode per-vrf
 
   

Related Commands

Command
Description
   

8 port 10GE XFP Support Commands

This section provides details on the commands introduced or changed in Cisco IOS XR Software Release 3.9.2 that are specific to this feature. The following command is new:

controller wanphy

controller wanphy

To enable wanmode on a 10-Gigabit Ethernet XFP PLIM, use the controller preconfigure wanphy command in global configuration mode. To return the controller to its default setting, use the no form of this command.

controller wanphy interface-id <Rack>/<Slot>/<Module>/<Port> wanmode on

no controller wanphy interface-id <Rack>/<Slot>/<Module>/<Port> wanmode on

Syntax Description

interface-id

Physical interface instance. Naming notation is rack/slot/module/port and a slash between values is required as part of the notation.

rack. Chassis number of the rack.

slot. Physical slot number of the line card.

module. Module number. A physical layer instance module (PLIM) is always 0. Shared port adapters (SPAs) are referenced by their subslot number.

subslot number.

port. Physical port number of the interface.

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


Defaults

LAN

Command Modes

global configuration

Command History

Release
Modification

Release 3.9.2

This command was modified on the Cisco CRS Routers.


Usage Guidelines

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

Task ID
Task ID
Operations

interface

read, write


Examples

The following example shows how to enable wanmode for a 10-Gigabit Ethernet XFP PLIM controller in slot 5:

RP/0/RP0/CPU0:P2_CRS-8(config)#controller wanphy 0/5/0/0
RP/0/RP0/CPU0:P2_CRS-8(config-wanphy)wanmode on
 
   

The following example shows how to return a a 10-Gigabit Ethernet XFP PLIM controller in slot 5 to the defaults setting:

RP/0/RP0/CPU0:P2_CRS-8(config)# controller wanphy 0/5/0/0
RP/0/RP0/CPU0:P2_CRS-8(config-wanphy)no wanmode on
 
   
 
   

Command
Description

show controllers wanphy

Displays alarms, registers, and module information for a 10-Gigabit Ethernet WAN/LAN SPA or XFP PLIM controller.


Important Notes

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

affinity location set

affinity location type

affinity program

affinity self

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

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

Configuration prior to Cisco IOS XR Software Release 3.6.0:

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

Cisco IOS XR Software Release 3.6.0 and later releases:

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

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

Country-specific laws, regulations, and licences—In certain countries, use of these products may be prohibited and subject to laws, regulations, or licenses, including requirements applicable to the use of the products under telecommunications and other laws and regulations; customers must comply with all such applicable laws in the countries in which they intend to use the products.

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

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

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.

BFD IPv6 UDP Checksum Calculation—In Cisco IOS XR Software Release 3.9, you turn the BFD IPv6 UDP checksum calculation on and off:

To disable the BFD IPv6 UDP checksum calculation:

RP/0/RP0/CPU0:CRS-A(config)#bfd
RP/0/RP0/CPU0:CRS-A(config-bfd)#ipv6 checksum disable
RP/0/RP0/CPU0:CRS-A(config-bfd)#end
 
   

To enable BFD IPv6 UDP checksum calculation:

RP/0/RP0/CPU0:CRS-A(config)#bfd
RP/0/RP0/CPU0:CRS-A(config-bfd)#no ipv6 checksum disable
RP/0/RP0/CPU0:CRS-A(config-bfd)#end
 
   

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

New DWDM Configuration Requirement


Note This section describes only the new DWDM configuration requirements in Cisco IOS XR 3.9.0 and later releases. It does not describe all updates to the DWDM feature. For more information about DWDM configuration, refer to the "Configuring Dense Wavelength Division Multiplexing Controllers on Cisco IOS XR Software" module in the Cisco IOS XR Interface and Hardware Component Configuration Guide for the Cisco CRS-1 Router.


Cisco IOS XR Software Release 3.9.0 introduces new commands in addition to an important change to the default laser state for all of the DWDM physical layer interface modules (PLIMs) supported on the Cisco CRS-1 router, which impacts the required configuration to support those cards.

This change affects all models of the following hardware on the Cisco CRS-1 router:

Cisco 1-Port OC-768c/STM-256c DWDM PLIM

Cisco 4-Port 10-Gigabit Ethernet DWDM PLIM

Summary of Important DWDM Changes in Cisco IOS XR Software Release 3.9.0 and Later Releases

The laser off and shutdown (DWDM) commands are replaced by the admin-state out-of-service command.

The default state of the laser has changed from "On" to "Off" for all PLIMs. Therefore, the laser for all DWDM controllers must explicitly be turned on using the admin-state in-service command in DWDM configuration mode.

Configuration Examples in Cisco IOS XR Software Release 3.9.0 and Later Releases

This section provides configuration examples for turning on and off the laser on a DWDM PLIM.

Turning On the Laser: Example


Note This is a required configuration beginning in Cisco IOS XR Software Release 3.9.0. The DWDM PLIMs will not operate without this configuration.


The following example shows how to turn on the laser and place a DWDM port in In Service (IS) state:

RP/0/RP0/CPU0:router# configure 
RP/0/RP0/CPU0:Router(config)# controller dwdm 0/1/0/1 
RP/0/RP0/CPU0:Router(config-dwdm)# admin-state in-service
RP/0/RP0/CPU0:Router(config-dwdm)# commit

Turning Off the Laser: Example


Note This configuration replaces the laser off and shutdown (DWDM) configuration commands.


The following example shows how to turn off the laser, stop all traffic and place a DWDM port in Out of Service (OOS) state:

RP/0/RP0/CPU0:router# configure 
RP/0/RP0/CPU0:Router(config)# controller dwdm 0/1/0/1 
RP/0/RP0/CPU0:Router(config-dwdm)# admin-state out-of-service
RP/0/RP0/CPU0:Router(config-dwdm)# commit

Minimum Flash Disk Requirements When Upgrading to Release 3.9.2

Cisco IOS XR Software Release 3.9.2 requires a 2-GB Flash Disk as a minimum. If your Cisco CRS-1 currently uses a 1-GB Flash Disk, you must upgrade it to 2-GB before upgrading to Cisco IOS XR Software Release 3.9.2. 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.

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

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

To upgrade from a 1-GB flash disk to a 2-GB or greater flash disk, refer to the Flash Disk Upgrade Tasks link on the following Cisco CRS-1 Router Installation and Upgrade URL: http://www.cisco.com/en/US/products/ps5763/prod_installation_guides_list.html

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 caveats; severity-2 caveats are less serious.

This section contains caveats that are generic to the Cisco IOS XR software and those specific to the Cisco CRS-1 Router.

Resolved Release 3.9.2 Cisco IOS XR 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

Open Release 3.9.2 Cisco IOS XR Caveats

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

CSCtf93555

Basic Description:

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

Symptom:

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

Conditions:

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

Workaround:

None.

Recovery:

Bring the TACACS server up.

CSCtd17516

Basic Description:

CLI over XML Configuration Fails

Symptom:

CLI over XML configuration request fails.

Conditions:

This happens when

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

AND

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

Workaround:

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

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

Recovery:

None.

CSCta71930

Basic Description:

lpts_pa tracebacks after clear cef on line card

Symptom:

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

Conditions:

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

Workaround:

Not required, as BCDL will come up eventually.

Further Problem Description:

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

CSCtg48346

Basic Description:

Standby RP not ready - ospf Waiting for primary node

Symptom:

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

Conditions:

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

Workaround:

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

Recovery:

CSCti01478

Basic Description:

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

Symptom:

Lots of processes (admin plane) complain that the registrations/get/bind operations are timing out.

The next thing to notice is the Pending MsgCount which indicates the servers inability to process

incoming messages. This triggers a snmp issue as snmp doesn't handles the error core related to sysdb registration properly.

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

Conditions:

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

Workaround:

None.

Recovery:

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

CSCti74249

Basic Description:

Admin Plane config loss upon Turboboot

Symptom:

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

Conditions:

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

Workaround:

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

Recovery:

None.

CSCtj19602

Basic Description:

Install operation failed due to insufficient disk space on SP cards

Symptom:

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

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

Conditions:

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

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

Example: Upgrading from 3.9.2.22i to 3.9.2.
 
   

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

Workaround:

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

Recovery:

Use turboboot to run the new image

CSCti19533

Basic Description:

Wildcard does not work on activating inactive pies

Symptom:

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

Conditions:

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

Workaround:

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

Recovery:

None.

CSCti67148

Basic Description:

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

Symptom:

Command authorization fails:

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

Conditions:

This happens:

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

Tacacs authorization is enabled.

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

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

Workaround:

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

Recovery:

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

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

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

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

usergroup priv13
  taskgroup root-system
  taskgroup cisco-support
 
   

CSCti50227

Basic Description:

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

Symptom:

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

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

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

Workaround:

The commit must be performed in two steps:

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

2. Remove the policy or set and commit.

Open Release 3.9.2 Caveats Specific to the Cisco CRS-1 Router

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

CSCtd69256

Basic Description:

ATM SPA errors after VPI reuse in scaled configuration

Symptom:

SPA related errors generally accompanied by channel stats error.

Conditions:

1. Configure a scaled setup with 4k ATM xconnect sessions under a L2 VP mode.

2. Delete the L2 VPs thus bringing the xconnects down.

3. Configure VC mode L2 transport and bring the xconnect sessions backup.

Under such a sequence of actions, there is a possibility that one of the VP teardown does not go through clean leaving behind stale Channel of the VP. If a subsequent VC is created with same VPI value, it might sometimes result in traffic outage on that particular L2-VC.

When the problem occurs, the show hw-module subslot <> counter sar will indicate a CID for VCD mapped to the L2 VP which was deleted indicating it is stale.

Workaround:

Avoid using a L2VC with the same VPI value as the VPI of the previously configured VP on the same port. If the VPI has been re-used and the traffic does not pass over the newly configured L2 connection, change the VPI value to have a different CID allocated..

Recovery:

Please reload the SPA to recover from this issue.

CSCtf25526

Basic Description:

On a fibre pull, LOS counter is not always incremented

Symptom:

The LOS counter may not increment correctly on the 1x10GE WANPHY SPA.

Conditions:

When a LOS occurs on the 1x10GE Wanphy SPA receive port, a LOS alarm is raised as expected, however the LOS counter may fail to increment. This condition occurs only when LOS is caused due to a fiber pull.

Workaround:

None.

CSCtg30180

Basic Description:

NAT fails on modifying Active/Standby pair config to Active only after Failover

Symptom:

NAT Translation fails on following actions -

1) CGSE Failover in redundancy setup.

2) Remove standby location config to make it non redundant setup.

Conditions:

This symptom is observed when all of the following conditions occur: When Active/Standby CGSE is configured and Failover is triggered. Modify the service-location config to preferred active only and do not configure standby location

Workaround:

Restart cgn_ma process.

CSCte37113

Basic Description:

VRF related configurations failing if standby alone reloaded

Symptom:

CGN specific VRF and Address pool map related config doesn't get applied on standby CGSE after reloading standby CGSE alone.

Conditions:

This symptom is observed when all of the following conditions occur: When Active & Standby CGSE is configured and Standby CGSE is reloaded. When preferred-active location is configured first and then configure preferred standby location along with active location. Modify preferred standby location.

Workaround:

Restart cgn_ma process.

CSCsr86019

Basic Description:

fib_mgr : Platform upd failed traceback console messages were seen for CGSE

Symptom:

Following error message is observed on the console once (while service interface creation) or in very rare cases every 15 seconds on a CGSE LC.

LC/0/7/CPU0:Jan 25 17:48:07.576 : fib_mgr[163]: %ROUTING-FIB-3-PLATF_UPD_FAIL
: Platform upd failed: Obj=DATA_TYPE_NHINFO[ptr=a40c65dc,refc=0,flags=0]
Action=CREATE Proto=ipv6. Cerr=Invalid argument  : pkg/bin/fib_mgr :
(PID=122975) :  -Traceback= 4d270a9c 4005e144 400683fc 40069c44 4006c824
4006cca4 400a15c0 400a1a70 400071c4 4c2146b8 4c2127d4 400004fc 4000f6c8 4c2943c4
 LC/0/0/CPU0:Aug  7 01:26:40.960 : fib_mgr[146]: %ROUTING-FIB-3-PLATF_UPD_FAIL
: Platform upd failed: Obj=DATA_TYPE_NHINFO[ptr=7a9e7ed4,refc=0x1,flags=0]
Action=MODIFY Proto=ipv4. Cerr=Invalid argument  : pkg/bin/fib_mgr :
(PID=86104) :  -Traceback= f90745d0 48255c10 4825c5d4 48261c70 48262988
f917ac34 f8209120 f8206f88 48200f08 4820cff8 f82895ec
 
   

This message is seen on both Active and Standby CGSE linecards.

Conditions:

This symptom is observed when one of the following conditions occur:

Configuring/modifying Service interfaces on a CGSE PLIM.

CGSE Reload.

Delete one / more already configured serviceapp interfaces from a stable system and you follow it up with a fib_mgr or an aib restart on that CGSE linecard.

Workaround:

No workaround other than CGSE linecard OIR.

CSCti09260

Basic Description:

Incorrect Origin AS and NextHop AS in CEF for a prefix

Symptom:

This may impact netflow collection based on BGP attribute if Netflow feature enabled to collect stats based on BGP as-path

IOS XR version 3.8.3/3.8.4/3.9.1/4.0 are affected

Conditions:

BGP graceful restart feature is configured AND

BGP attribute-download feature is enabled AND

BGP process gets restarted due SMU installation or process crash AND

Netflow feature enabled to collect stats based on BGP as-path

Workaround:

1. Unconfigure BGP attribute-download.

2. Wait for a few minutes and then issue show rib attribute sum command to verify that RIB has no attributes left.

3. Restart RIB if it continues to have old attributes after BGP attribute-download is unconfigured.

4. Wait for 5 minutes in case of a RIB restart.

5. Install the BGP SMU -> If the BGP restart is being triggered by BGP SMU installation.

This only applies for installation of SMU. Will be skipped if SMU is already installed or BGP process is restarted.

6. Reconfigure BGP attribute-download 10 minutes after BGP SMU installation.

Recovery:

None

CSCti62570

Basic Description:

sysdb warning message upon trying to resequence prefix-list

Symptom:

Unable to delete the prefix-list entires

Conditions:

After trying to resequence the prefix-list where it returns sysdb warning message

Workaround:

Configure the same prefix-list and unconfigure it.

Recovery:

None

CSCth58327

Basic Description:

PLATFORM-SHELFMGR-3-UNKNOWN_BOARD - invalid board type msg after OIR

Symptom:

Card is not booting , it is kept in "IN-RESET" and the similar message is seen in the logs

Conditions:

System reload or single board reload

Workaround:

None.

Recovery:

hw-module reload location <> could be tried first but if this is still giving the same symptom then a physical OIR of the board should recover it.

CSCti97773

Basic Description:

Stndby RPs 2RP1 & 3RP1 Not ready due to "rdsfs_svr Replica-/ipodwdm_log"

Symptom:

This issue happens when QUERY_PEERS_TIMED_OUT. The following rdsfs tracebacks are typically seen on multiple nodes when such issue happened :-

LC/3/12/CPU0:Sep 15 00:52:05.899 : rdsfs_svr[253]: %OS-RDS-7-QUERY_PEERS_TIMED_OUT :
TID=9 Couldnt cmd=262 for GID=0x81b CHDL=0x40000043(0x40000043) #to_resp=15 req=1
got=14 state=0x10, expstate=0x20 preq_id=9 rds_type=1 : pkg/bin/rdsfs_svr :
(PID=49218) : -Traceback= 4cd82be8 4cd84940 4cd8ff14 4cd93628 4cd93b24 4000fc8c
40000bb0 40005310 40005ec0 4c2cba8c 4c2cd278 4c2b127c 4c2b05e8 4c2af394 4c2ae9d4
4c29e3c4^M
 
   

This could also lead to standby not ready for extended period of time. Sample show redundancy output as follows:-

Active node reload "Cause: Node reload is required by install operation"
Standby node reload "Cause: Node reload is required by install operation"
Redundancy information for node 3/RP0/CPU0:
==========================================
Node 3/RP0/CPU0 is in ACTIVE role
Partner node (3/RP1/CPU0) is in STANDBY role
Standby node in 3/RP1/CPU0 is not ready
Standby node in 3/RP1/CPU0 is NSR-ready
Details
--------
Current active redcon state: 4 (I_READY)
<jid> <node> <name> Reason for standby not ready
388 3/RP1/CPU0 rdsfs_svr Replica-/ipodwdm_log
Not ready set Wed Sep 15 00:57:54 2010: 3 hours, 7 minutes ago
154 3/RP1/CPU0 cfgmgr-rp Configuration manager initialization in progress
Not ready set Wed Sep 15 00:46:43 2010: 3 hours, 18 minutes ago
154 3/RP1/CPU0 cfgmgr-rp Management interface configuration not yet applied
Not ready set Wed Sep 15 00:47:04 2010: 3 hours, 18 minutes ago
 
   

Conditions:

This is usually seen only on Router reload or RACK OIR where the underlying transport layers are under stress where packets lost are seen most often.

In this particular case, while RDS on 3/RP1 was doing an initial data-transfer from the DSC node, it also got a MEMBER-UP notification from GSP (which is basically a node-up). Now a very rare race-condition was hit in RDS, where RDS was deleting a replica entry while at the same time another thread was handling this node-up. This race led to a deadlock between the 2 threads. Because of this deadlock, multiple other threads were also blocked. This led to standby being set not ready as all threads were blocked.

Workaround:

None

Recovery:

Restart process rdsfs_svr on the standby node. rdsfs_svr will get out of the deadlocked state and recover normally. The initial data transfer would get completed and standby would be set ready and redundancy established. The rdsfs_svr process recovers by itself. After the crash it comes back up fine and no impact is seen.

CSCti98760

Basic Description:

Multiple tracebacks due to TLU mem leak seen after clear cef linecard.

Symptom:

After executing 'clear cef linecard' multiple times, operator may sometimes notice fib_mgr trace backs such as the ones shown below.

LC/0/7/CPU0:Sep 16 12:02:14.692 : fib_mgr[164]: %ROUTING-FIB-3-PLATF_UPD_FAIL :
Platform upd failed: Obj=DATA_TYPE_NHINFO[ptr=a0b83140,refc=0,flags=0] Action=CREATE
Proto=ipv6. Cerr=Not enough memory : pkg/bin/fib_mgr : (PID=94301) : -Traceback=
4d2b6b58 4005dc08 4006809c 4006994c 4006d69c 4006de10 4006e534 4006e6a0 4006ee38
40048d04 40051564 40053494 40058a70 40059304 400a0bf0 400a1c94
LC/0/7/CPU0:Sep 16 12:02:20.867 : fib_mgr[164]: %PLATFORM-PLAT_FIB_HAL-3-ERR_STR_RT :
Failed to allocate RPF TLU entry, may notice inconsistent RPF behavior. %s (%u): Not
enough memory (12) : pkg/bin/fib_mgr : (PID=94301) : -Traceback= 4dc18e00 4d356ad0
4d356e50 4d358c50 4d33c900 4d33f43c 4d3404a8 4d33c7d0 4d32c85c 4d2b6d28 40043338
40044270 400276bc 400cdb4c 400d2930 40010ff0
LC/0/7/CPU0:Sep 16 12:02:14.692 : fib_mgr[164]: %ROUTING-FIB-3-PLATF_UPD_FAIL :
Platform upd failed: Obj=DATA_TYPE_NHINFO[ptr=a0b83140,refc=0,flags=0] Action=CREATE
Proto=ipv6. Cerr=Not enough memory : pkg/bin/fib_mgr : (PID=94301) : -Traceback=
4d2b6b58 4005dc08 4006809c 4006994c 4006d69c 4006de10 4006e534 4006e6a0 4006ee38
40048d04 40051564 40053494 40058a70 40059304 400a0bf0 400a1c94
LC/0/7/CPU0:Sep 16 12:02:20.867 : fib_mgr[164]: %PLATFORM-PLAT_FIB_HAL-3-ERR_STR_RT :
Failed to allocate RPF TLU entry, may notice inconsistent RPF behavior. %s (%u): Not
enough memory (12) : pkg/bin/fib_mgr : (PID=94301) : -Traceback= 4dc18e00 4d356ad0
4d356e50 4d358c50 4d33c900 4d33f43c 4d3404a8 4d33c7d0 4d32c85c 4d2b6d28 40043338
40044270 400276bc 400cdb4c 400d2930 40010ff0
 
   

Conditions:

This issue is seen on a 16 slot Cisco Internet Series router booted with Cisco IOS XR version 3.9.2-22i.

Issue is only seen with Strict Unicast RPF (Reverse Path Forwarding) configuration enabled on the line card.

Workaround:

Reload the line card which exhibits the trace backs

Recovery:

Reload the linecard which exhibits the trace backs

CSCti95349

Basic Description:

rdsfs crash/RDS threads are acting on an already deleted replica entry

This is usually seen only on Router reload or RACK OIR when the underlying transport layers are under stress where packet lost are seen often. This issue is not seen during steady state.

This particular instance happened on a router reload, RDS fails the reader_init (i.e. QUERY_PEERS_TIMED_OUT) and destroys the replica entry without checking other threads are waiting on condvar for same replica. This results in rdsfs_svr crash. After the crash rdsfs_svr recovers by itself and there are no issues.

Symptom:

This issue happens as a result of QUERY_PEERS_TIMED_OUT. Rdsfs tracebacks are seen in multiple nodes with the following signature -

LC/3/12/CPU0:Sep 15 00:52:05.899 : rdsfs_svr[253]: %OS-RDS-7-QUERY_PEERS_TIMED_OUT : 
TID=9 Couldnt cmd=262 for GID=0x81b CHDL=0x40000043(0x40000043) #to_resp=15 req=1 
got=14 state=0x10, expstate=0x20 preq_id=9 rds_type=1  : pkg/bin/rdsfs_svr : 
(PID=49218) :  -Traceback= 4cd82be8 4cd84940 4cd8ff14 4cd93628 4cd93b24 4000fc8c 
40000bb0 40005310 40005ec0 4c2cba8c 4c2cd278 4c2b127c 4c2b05e8 4c2af394 4c2ae9d4 
4c29e3c4

Conditions:

rdsfs_svr process crash leads to delay in standby RP readiness. There is no traffic impact as this is seen on the standby RP. Rdsfs_svr should recover itself upon restart.

Workaround:

None.

Recovery:

The rdsfs_svr process recovers by itself after the crash and no impact is seen.

CSCti95114

Basic Description:

copy config loss due to qsm retransmissions

This is mainly due to too much traffic on the SPs which has very low memory. All bugs that reduces the memory usage on SP will help alleviate the chances of hitting this issue.

Symptom:

During copy running to HD or disk0 we see sysdb timed out msgs, nvgen error and missing config in the destination file.

Conditions:

control packets are loss due to qsm retransmissions. this is observed on large MC systems with SDRs that contains a lot of nodes. When these nodes are reloaded.. ie rack OIR or SDR carve/uncarve, it can cause a storm of qsm retransmissions that may get worst over time and eventually one of the symptoms we observed is config loss during config copy.

Workaround:

None. Router reload may recover.

Recovery:

None.

CSCti92622

Basic Description:

Seeing "NO_SUCH_INSTANCE_EXCEPTION" error for few snmp queries

Symptom:

On CRS-1, a snmp query of the CE MIB may not provide an output . The MIB query returns with error like " NO_SUCH_INSTANCE_EXCEPTION"

Conditions:

When CE MIB elements are queried through SNMP

Workaround:

None

Recovery:

Restart of cemgbl process can resolve the issue.

CSCti55946

Basic Description:

Upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0 fails with CGN PIE

Symptom:

Upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0 fails with CGN PIE. There is no issue if there is no CGN PIE involved in the upgrade.

Conditions:

Seen while upgrading from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0.

Workaround:

Remove the CGN PIE and upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0 and than install the CGN PIE.

Similar workaround needs to be applied if you downgrade from Cisco IOS XR software release 4.0.0 to Cisco IOS XR software release 3.9.x.

Procedure for Workaround


Step 1 Save the CGN config

Step 2 De-active CGN PIE before upgrade.

Step 3 Upgrade CRS without CGN PIE

Step 4 Once the new image is up. Install the new CGN PIE.

Step 5 Since CGN config is lost during this process, apply the previously saved CGN config.



Note The upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.0.T does not need this workaround.


CSCtl92320

Basic Description:

CSCth49227 in 4.0.1 broke the fix for CSCti55946

Symptom:

Upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.1 fails with CGN PIE. There is no issue if there is no CGN PIE involved in the upgrade.

Conditions:

Seen while upgrading from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.1.

Workaround:

Remove the CGN PIE and upgrade from Cisco IOS XR software release 3.9.x to Cisco IOS XR software release 4.0.1 and than install the CGN PIE.

Similar workaround needs to be applied if you downgrade from Cisco IOS XR software release 4.0.1 to Cisco IOS XR software release 3.9.x.

Procedure for Workaround


Step 1 Save the CGN config

Step 2 De-active CGN PIE before upgrade.

Step 3 Upgrade CRS without CGN PIE

Step 4 Once the new image is up. Install the new CGN PIE.

Step 5 Since CGN config is lost during this process, apply the previously saved CGN config.


Upgrading Cisco IOS XR Software

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

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

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

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


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


Troubleshooting

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

Related Documentation

The most current Cisco CRS-1 Router hardware documentation is located at the following URL:

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

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

The most current Cisco CRS-1 Router software documentation is located at the following URL:

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

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

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

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.