Table Of Contents
Release Notes for Cisco CRS-1 for Cisco IOS XR Software Release 3.9.0
April 15, 2013
Cisco IOS XR Software Release 3.9.0
Text Part Number OL-21180-02
These release notes describe the features provided in the Cisco IOS XR Software Release 3.9.0 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.0, see the "Important Notes" section.
You can find the most current Cisco IOS XR software documentation at
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.0, 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:
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.0
Cisco IOS XR Software Release 3.9.0 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.0. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.0" section.
These release notes contain the following sections:
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 Routing—Supports 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 Convergence—Provides 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.0, see the "New Features in Cisco IOS XR Software Release 3.9.0" section in this document.
This section describes the system requirements for Cisco IOS XR Software Release 3.9.0 supported on the Cisco CRS-1 Router. The system requirements include the following information:
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.0 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.0 supported on the Cisco CRS-1 Router.
Table 1 Cisco CRS-1 Supported Feature Sets
(Cisco IOS XR Software Release 3.9.0 PIE Files)
Feature Set Filename Description Composite Package
Cisco IOS XR IP Unicast Routing Core Bundle
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
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
Cisco IOS XR MPLS Package
Cisco IOS XR Multicast Package
Cisco IOS XR Security Package
Cisco IOS XR Documentation Package
The documentation package is not supported in Cisco IOS XR Software Release 3.9.0.
Please refer to the Cisco CRS-1 command reference documentation located at the following URL:
Cisco IOS XR FPD Package
Cisco IOS XR Diagnostic Package
Diagnostic utilities for Cisco IOS XR routers.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 Extensible Markup Language
4 MPLS Traffic Engineering
5 Label Distribution Protocol
6 Operations, Administration, and Maintenance
7 Link Manager Protocol
8 Optical User Network Interface
9 Resource Reservation Protocol
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Multicast Routing Information Base
13 Multicast-Unicast RIB
14 Multicast forwarding
15 Bidirectional Protocol Independent Multicast
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Public-key infrastructure
20 Physical layer interface module
21 Shared port adapters
22 ROM monitor
Table 2 lists the Cisco CRS-1 Router TAR files.
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.0 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.0 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.0. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.0" section.
All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Cisco IOS XR Software Release 3.9.0 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:
•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
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:router# show versionTue Dec 15 15:44:27.332 PSTCisco IOS XR Software, Version 3.9.0Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.54(20091016:214209) [CRS-1 ROMMON],BL-P1 uptime is 9 hours, 29 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.9.0/mbihfr-rp.vm"cisco CRS-16/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.24 Management Ethernet40 TenGigE90 GigabitEthernet82 SONET/SDH4 SRP over SONET74 Packet over SONET/SDH4 DWDM controller(s)1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.2053440k bytes of disk0: (Sector size 512 bytes).1642208k bytes of disk1: (Sector size 512 bytes).Boot device on node 0/8/CPU0 is mem:Package active on node 0/8/CPU0:hfr-fpd, V 3.9.0, Cisco Systems, at disk0:hfr-fpd-3.9.0Built on Sun Dec 13 23:57:51 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-diags, V 3.9.0, Cisco Systems, at disk0:hfr-diags-3.9.0Built on Sun Dec 13 23:57:36 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-mcast, V 3.9.0, Cisco Systems, at disk0:hfr-mcast-3.9.0Built on Mon Dec 14 01:17:14 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-mpls, V 3.9.0, Cisco Systems, at disk0:hfr-mpls-3.9.0Built on Mon Dec 14 01:17:12 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-lc, V 3.9.0, Cisco Systems, at disk0:hfr-lc-3.9.0Built on Sun Dec 13 23:53:01 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-fwdg, V 3.9.0, Cisco Systems, at disk0:hfr-fwdg-3.9.0Built on Sun Dec 13 23:51:06 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-admin, V 3.9.0, Cisco Systems, at disk0:hfr-admin-3.9.0Built on Sun Dec 13 23:49:39 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-base, V 3.9.0, Cisco Systems, at disk0:hfr-base-3.9.0Built on Sun Dec 13 23:50:34 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-os-mbi, V 3.9.0, Cisco Systems, at disk0:hfr-os-mbi-3.9.0Built on Sun Dec 13 23:46:13 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0Boot device on node 0/10/CPU0 is disk0:Package active on node 0/10/CPU0:hfr-fpd, V 3.9.0, Cisco Systems, at disk0:hfr-fpd-3.9.0Built on Sun Dec 13 23:57:51 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-diags, V 3.9.0, Cisco Systems, at disk0:hfr-diags-3.9.0Built on Sun Dec 13 23:57:36 PST 2009By sjc-lds-524 in /auto/srcarchive3/production/3.9.0/hfr/workspace for c4.2.1-p0hfr-k9sec, V 3.9.0, Cisco Systems, at disk0:hfr-k9sec-3.9.0Built on Sun Dec 13 23:56:23 PST 2009
New Features in Cisco IOS XR Software Release 3.9.0
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.9.0:
Note Cisco Session Border Controller (SBC) is not supported on any platform in Cisco IOS XR Software Release 3.9.0. Cisco IOS XR Software Release 3.7 is the last release that supports SBC.
New Software Features Supported on all Platforms
The following new software features in Cisco IOS XR Software Release 3.9.0 are supported on all platforms:
•BGP ASPLAIN Notation
•SFTP Interactive Client
•BGP Prepend ASN into the Path
•SSHv2 Enhancements for RSA Keys
•BGP Best External
•BGP Support for Dual AS Configuration for Network AS Migrations
•Hide Local AS support
•RSVP MIB Support
Cisco CRS-1 Router-Specific Software Features
The following new features in Cisco IOS XR Software Release 3.9.0 are supported on the Cisco CRS-1 platform:
•BFD Support for HSRP
•BGP PIC Unipath
•Ethernet OAM: 802.3 OAM with Neighbor Discovery, Link Monitoring and Remote Fault Indication, Ethernet Connectivity Fault Management: 802.1ag support on physical interface, 802.1q and 802.1ad
•Generic Routing Encapsulation (GRE)
•IP Precedence for GRE Tunnels
•IPv6 Tunneling: Manually Configured IPv6 over IPv4 Tunnels
•IPv6 Tunneling: IPv6 over IPv4 GRE Tunnels
•L2TPv3 Based VPNs
•Label Switched Multicast Point-to-Multipoint Traffic Engineering
•MPLS IP TTL Propagate Local vs. Forwarded Packets
•MPLS VPN over IP Tunnels
•MVPN MDT Source Select
•Native MPLS over GRE
•OSPF Loop Free Alternates
•QoS: Tunnel Marking for L2TPv3 Tunnels
•SSO - HSRP
•SSO - VRRP
•BFD Support for VRRP
•WAN-PHY Signal Failure (SF) and Signal Degrade (SD) Bit Error Rate (BER) Reporting and Thresholds
Cisco IOS XR Software Release 3.9.0 includes support for prefix-length notation for ACLs on the Cisco CRS-1 platform.
The following example shows how to define an access list named Internetfilter with prefix-length notation:RP/0/RSP0/CPU0:router(config)# ipv4 access-list Internetfilter10 permit ipv4 184.108.40.206/24 any20 permit ipv4 220.127.116.11/16 any30 permit ipv4 18.104.22.168/27 any40 permit ipv4 22.214.171.124/24 any50 permit ipv4 any any
New Hardware Features for the Cisco CRS-1 Router
No new hardware features were introduced inCisco IOS XR Software Release 3.9.0 on the Cisco CRS-1 Router.
For detailed information on the shared port adapters (SPAs) and SPA interface processors (SIPs), see the following documents:
•Cisco CRS-1 SIP and SPA Hardware Installation Guide
•Cisco Interface and Hardware Component Configuration Guide for the Cisco CRS-1 Router, Release 3.9
Note Contact firstname.lastname@example.org for hardware availability.
•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_exampleClass class-defaultrandom-detect exp 0 384 packets 484 packetsrandom-detect exp 1 384 packets 484 packetsrandom-detect exp 2 384 packets 484 packetsrandom-detect exp 3 484 packets 584 packetsrandom-detect exp 4 484 packets 584 packetsrandom-detect discard-class 0 384 packets 484 packetsrandom-detect discard-class 1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth remaining percent 20
Cisco IOS XR Software Release 3.6.0 and later releases:policy-map wred_exampleclass class-defaultrandom-detect exp 0,1,2 384 packets 484 packetsrandom-detect exp 3,4 484 packets 584 packetsrandom-detect discard-class 0,1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth 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.
•The following commands are not supported on the Cisco CRS-1 Series Router:
–affinity location set
–affinity location type
•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)#bfdRP/0/RP0/CPU0:CRS-A(config-bfd)#ipv6 checksum disableRP/0/RP0/CPU0:CRS-A(config-bfd)#end
–To enable BFD IPv6 UDP checksum calculation:RP/0/RP0/CPU0:CRS-A(config)#bfdRP/0/RP0/CPU0:CRS-A(config-bfd)#no ipv6 checksum disableRP/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 3.9.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# configureRP/0/RP0/CPU0:Router(config)# controller dwdm 0/1/0/1RP/0/RP0/CPU0:Router(config-dwdm)# admin-state in-serviceRP/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# configureRP/0/RP0/CPU0:Router(config)# controller dwdm 0/1/0/1RP/0/RP0/CPU0:Router(config-dwdm)# admin-state out-of-serviceRP/0/RP0/CPU0:Router(config-dwdm)# commit
Minimum Flash Disk Requirements When Upgrading to Release 3.9.0
Cisco IOS XR Software Release 3.9.0 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.0. 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 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 Release 3.9.0 software and those specific to the Cisco CRS-1 Router.
Cisco IOS XR Caveats
The following open caveats apply to Cisco IOS XR Software Release 3.9.0 and are not platform specific:
%SECURITY-LOCALD-3-LWA_ADD_FAIL error when secret is added for a user
In rare circumstances, when a user tries to configure username and secret password, the configuration succeeds, but the following console message is generated, which seems to suggest that the configuration did not succeed:"% Failed to commit one or more configuration items. Please issue show configuration failed from this session to view the errors"
No specific trigger is identified. This is an issue that has been observed a few times over several months.
None. Although the configuration failure message is reported, the operation is successful. There is no operational impact of this issue.
None. Only a console message appears, and there is no functional impact.
lpts_pa tracebacks after clear cef on line card
An error log is printed along with the traceback when a message send to the BCDL agent fails.
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.
Not required. BCDL restarts automatically.
Further Problem Description:
The error message says that the BCDL agent has failed. This would not cause an error in lpts as the BDCL process restarts automatically.
OSPFv3 default-information originate does not work in 6PE
OSPFv3 might fail to originate a default route when the default-information originate command is configured and there is a default route of ::/0 present in the routing table.
The problem happens when the default route in the RIB is received from a 6PE peer, and the next hop address is a v4-mapped-v6 address.
Use route-policy to specify the next hop address.
Telnet session does not return the prompt/control after show commands
When the terminal length is set to zero and the show commands are executed for continuous output, the telnet session does not return the command router prompt and seems to be hanging. However, only the last few lines of the show command output are not displayed.
Pressing the Enter key displays one line of output. Pressing the spacebar advances one character on the output device. When the next command is entered, the previous missing lines are displayed along with the command prompt. The last few lines of the new output are not displayed. You can type the new commands, and they are executed. However, you do not see the typed commands.
This behavior is not exclusively related to long outputs. It can occur with shorter outputs from the ADMIN plane as well as the EXEC plane when the terminal length 0 command is entered for the continuous output display. The trigger is a timing issue and manifests itself at different loads and activities on the router.
Exit the current session and re-login which gives you a new TTY session. Also, issuing the process restart devc-vty command should clear all of the sessions.
CLI over XML configuration fails
CLI over XML configuration request fails.
This happens when both of the following conditions are met:
–The CLI command lines in an XML request exceed 200 lines or more.
–The CLI commands are split internally in middle of sub-mode.
You do not need to use CLI over XML for configuration commands that already support XML natively. Split the commands into multiple requests, so the command lines of each request are less than 200 lines.
Connected route missing from routing table after an APS flap and RP failover
Connected route is missing from the routing table for APS protected interfaces after an APS switchover that is immediately followed by an RP failover.
This issue occurs when an APS switchover is immediately followed by an RP failover.
Reload the line card associated with the connected route.
SSM does not support static map for groups other than 126.96.36.199/8
Cisco IOS XR does not support configurable static SSM-map ranges outside the default IANA range of 232.x.x.x/8. This applies to both IGMP version 2 and version 3 hosts.
This issue does not have any specific conditions.
show route backup only shows 50 entries
The show route backup command only lists the first 50 entries.
This issue occurs with the use of the show route backup command.
Use the show route summary detailed command which shows the correct number of backup routes.
Not able to modify RPL and delete prefix-set in a single commit.
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.
The commit must be performed in two steps:
1. Modify the policy to remove the reference to the policy or set and then commit.
2. Remove the policy or set and commit.
Caveats Specific to the Cisco CRS-1 Router
The following open caveats are specific to the Cisco CRS-1 platform:
LED on 5x1GE SPA stays OFF after subslot shut and unshut
After shutting down power for a 5x1GE SPA card, the LED for this SPA card goes OFF and stays OFF forever, even after unshutting the SPA card.
This is seen after shutting and unshutting the 5x1GE SPA cards.
To shut:RP/0/RP1/CPU0:router(config)#hw-module subslot 0/4/3 shutdown unpowered
To unshut:RP/0/RP1/CPU0:router(config)#no hw-module subslot 0/4/3 shutdown unpowered
Reload the jacket card to recover this issue.RP/0/RP1/CPU0:router#hw-module location 0/4/sp reload
entPhysicalParentRelPos not giving correct slot number
In logical router configurations (SDRs) it is possible that the Entity-MIB entity physical relative position object (entPhysicalRelPos) does not match the actual slot number which is included in the Entity MIB entity physical name (entPhysicalName). According to the RFC, these do not have to match. However, it is recommended that they do match.
Network management systems, for example Cisco ANA, incorrectly model the slot number for logical router configurations.
This issue only arises in SDR configurations.
Resolved Cisco IOS XR Software PSIRT-Related Caveats
BGP flaps due to unknown attribute
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.
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.
No workaround. Cisco developed a fix that addresses this vulnerability and will be releasing free software maintenance upgrades (SMUs) progressively starting 28 August 2010.
A Security Advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100827-bgp.shtml
Upgrading Cisco IOS XR Software
Cisco IOS XR software is installed and activated from modular packages, allowing specific features or software patches to be installed, upgraded, or downgraded without affecting unrelated processes. Software packages can be upgraded or downgraded on all supported card types, or on a single card (node).
Software packages are installed from package installation envelope (PIE) files that contain one or more software components.
The following URL contains links to information about how to upgrade Cisco IOS XR software:
Note Cisco IOS XR Software Release 3.9.0 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.0. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.0" section.
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.
The most current Cisco CRS-1 Router hardware documentation is located at the following URL:
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.0 software documentation.
The most current Cisco CRS-1 Router software documentation is located at the following URL:
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2010 Cisco Systems, Inc. All rights reserved.