Feedback
|
Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.5.3
Determining Your Software Version
New Software Features in Cisco IOS XR Software Release 3.5.3
New Hardware Features in Cisco IOS XR Software Release 3.5.3
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
Cisco XR 12000 Series Router-Specific Caveats
Resolved Cisco IOS XR Software PSIRT-Related Caveats
Upgrading Cisco IOS XR Software
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IOS XR Software Release 3.5.3
April 5, 2013
Cisco IOS XR Software Release 3.5.3
Text Part Number OL-15566-03
Note
Please see the "Important Notes" section for important information on Cisco IOS XR Software Release 3.5.3.
Note
You can find the most current Cisco IOS XR software documentation on the World Wide Web at http://www.cisco.com/en/US/partner/products/ps5845/tsd_products_support_series_home.html. These electronic documents may contain updates and modifications. See the "Obtaining Documentation and Submitting a Service Request" section for more information on obtaining Cisco documentation.
These release notes describe the features provided in Cisco IOS XR Software for the current release and are updated as needed.
For a list of software caveats that apply to Cisco IOS XR Software for the current release, see the "Caveats" section. The caveats are updated for every release and are located on the World Wide Web at www.cisco.com.
We recommend that you view the field notices for this release to see if your software or hardware platforms are affected at http://www.cisco.com/public/support/tac/fn_index.html.
Contents
These release notes contain the following sections:
•
Upgrading Cisco IOS XR Software
•
Obtaining Documentation and Submitting a Service Request
Introduction
Cisco IOS XR software is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.
Cisco IOS XR software provides the following features and benefits:
•
IP and Routing—Supports a wide range of IPv4 and IPv6 services, and routing protocols; such as Border Gateway Protocol (BGP), Routing Information Protocol (RIP), Intermediate System-to-Intermediate System (IS-IS), Open Shortest Path First (OSPF), IP Multicast, Routing Policy Language (RPL), and Hot Standby Router Protocol (HSRP)/Virtual Router Redundancy Protocol features (VRRP).
•
BGP Prefix Independent Convergence—Provides the ability to converge BGP routes within subseconds 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), Layer 2 virtual private network (L2VPN), and Layer 3 VPN (L3VPN).
•
Multicast—Provides comprehensive IP Multicast software including Source Specific Multicast (SSM). The Cisco CRS-1 router supports Bidirectional Protocol Independent Multicast (BIDIR-PIM).
•
Quality of service (QoS)—Supports rich QoS mechanisms, including policing, marking, queuing, dropping, and shaping. Additionally, the operating systems support modular QoS command-line interface (MQC). MQC is used to configure various QoS features on various Cisco platforms.
•
Manageability—Provides industry-standard management interfaces including modular command-line interface (CLI), Simple Network Management Protocol (SNMP), and native Extensible Markup Language (XML) interfaces.
•
Security—Provides comprehensive network security features including access control lists (ACLs); routing authentications; authentication, authorization, and accounting (AAA)/Terminal Access Controller Access Control System (TACACS+); Secure Shell (SSH); and Simple Network Management Protocol Versions 3 (SNMPv3). Control plane protections integrated into line card ASICs include Generalized TTL Security Mechanism (GTSM), RFC 3682, and dynamic control plane protection.
•
Craft Works Interface (CWI)—CWI is a client-side application used to configure and manage Cisco routers. The management and configuration features include fault, configuration, security, and inventory, with an emphasis on speed and efficiency. The CWI provides a context-sensitive graphical representation of the objects in a Cisco router, simplifying the process of configuring and managing the router. 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, and nonstop forwarding (NSF).
•
Multicast service delivery in SP NGN—MVPNv4 support carries customer multicast traffic over an ISP IPv4 core network.
•
6PE: Edge support for IPv6 applications—Delivers IPv6 traffic over an IPv4/MPLS core with 6PE support (Cisco XR 12000 Series Router only).
•
6VPE—Delivers IPv6 VPN traffic over an IPv4/MPLS core with 6VPE support (Cisco XR 12000 Series Router only).
•
6VPE over L2TPv3: Delivers IPv6 VPN traffic over L2TPv3 core with 6VPE support (Cisco XR 12000 Series Router only).
•
Enhanced core competencies:
–
Support for IS-IS and OSPF.
–
IP fast convergence with Fast Re-route support for IS-IS.
–
Traffic engineering support for unequal load balancing.
–
Path Computation Element (PCE) capability for traffic engineering.
•
Firewall Services—Seamless insertion of Firewall Services in the data path with Virtual Firewall support on the Multiservice Blade (XR-12K-MSB) for the Cisco XR 12000 Series Router.
•
Voice Video interconnect between providers with SBC on the Cisco CRS-1.
•
L2TPv3 tunneling mechanism—Service providers who do not use MPLS in the core, but want to offer VPN services can use the L2TPv3 tunneling mechanism. The feature support includes IPv4 (VPNv4) and IPv6 (6VPE) VPN services using L2TPv3 encapsulation. The L2TPv3 packet is encapsulated in an IPv4 delivery header and is carried across an IPv4 backbone. VPN prefixes are advertised with BGP labels and resolved over L2TPv3 tunnels.
See the "New and Changed Information" section for a detailed list of new features by platform for Cisco IOS XR Software for the current release.
System Requirements
Cisco IOS XR Software Release 3.5.3 is supported on the following platforms:
•
Determining Your Software Version
Cisco CRS-1
This section describes the system requirements for Cisco IOS XR Software for the current release supported on Cisco CRS-1 routers and includes the following information:
To determine the software versions or levels of your current system, see Determining Your Software Version.
Feature Set Table
The Cisco IOS XR Software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR features related to the current release. Table 1 and Table 2 list the Cisco IOS XR Software feature set matrix and associated filenames available that are supported on the Cisco CRS-1 router in the current release.
Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.5.3 PIE Files)
Feature Set Filename Description Composite PackageCisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.5.3
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.5.3
Contains the required core packages including, OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Optional Individual Packages1Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.5.3
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.5.3
MPLS-TE,4 LDP,5 MPLS Forwarding, MPLS OAM,6 LMP,7 OUNI,8 RSVP,9 and Layer-2 and Layer-3 VPNs.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.5.3
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.5.3
Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI.19
Cisco IOS XR Documentation Package
hfr-doc.pie-3.5.3
Manual pages for Cisco IOS XR CLI commands
Cisco IOS XR FPD Package
hfr-fpd.pie-3.5.3
Firmware for Fixed PLIM and SPA modules as well as ROMMON images for CRS chassis.
Cisco IOS XR Diagnostic Package
hfr-diags-p.pie-3.5.3
Diagnostic utilities for Cisco IOS XR routers.
Cisco IOS XR Session Border Controller Package
hfr-sbc-p.pie-3.5.3
Session Border Controller package for a Cisco CRS-1 Series Router.
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
Memory Requirements
CautionIf you remove the media in which the software image or configuration is stored, the router may become unstable and fail.
The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR Software for the current release consist of the following:
•
2-GB memory on the route processors (RPs)
•
2-GB memory on the modular services cards (MSCs)
Hardware Supported
Cisco IOS XR Software for the current release supports Cisco CRS-1 routers. 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 hardware components supported on the Cisco CRS-1 and the minimum software versions required. See the "Other Firmware Code" section.
Software Compatibility
Cisco IOS XR Software for the current release 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
Other Firmware Code
The following firmware code is supported by the Cisco CRS-1 router:
•
The minimum ROMMON version required for this release is 1.45. For detailed information on ROMMON specifications, see http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html.
•
The minimum CPUCNTRL version required for this release is 2.07. For more information, see http://www.cisco.com/en/US/products/ps5845/products_configuration_guide_chapter09186a00807e018c.html#wp68039.
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.5.3 supported on the Cisco XR 12000 Series Router and includes the following information:
To determine the software versions or levels of your current system, see Determining Your Software Version.
Feature Set Table
Cisco IOS XR Software is packaged in feature sets (also called software images). Each package contains a specific set of Cisco IOS XR Software features related to the current release. Table 4 and Table 5 list the Cisco IOS XR Software feature set matrix and associated filenames available for Cisco IOS XR Software Release 3.5.3, supported on the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Sets (Cisco IOS XR Software
Release 3.5.3 PIE Files) Feature Set Filename Description Composite PackageCisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.5.3
Contains the required core packages, including OS, Admin, Base, Forwarding, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.vm-3.5.3
Contains the required core packages including, OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Optional Individual Packages1Cisco IOS XR Manageability Package
c12k-mgbl.pie-3.5.3
CORBA agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.5.3
MPLS-TE, LDP, MPLS Forwarding, MPLS OAM, LMP, OUNI, and RSVP.
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.5.3
Multicast Routing Protocols (PIM, MSDP, IGMP, Auto-RP, BSR), Tools (SAP, MTrace, MRINFO), and Infrastructure (MRIB, MURIB, MFWD).
Cisco IOS XR Security Package
c12k-k9sec.pie-3.5.3
Support for Encryption, Decryption, IPSec, SSH, SSL, and PKI.
Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.5.3
Support for booting the Standby RP on a Cisco XR 12000 Series Router.
Cisco IOS XR Session Border Controller Package
c12k-sbc.pie-3.5.3
Session Border Controller Package for a Cisco XR 12000 Series Router.
Cisco IOS XR Service IPsec controller package
c12k-ipsec-service.pie-3.5.3
Support for service-ipsec and service-gre interfaces in Cisco IOS XR Software.
Cisco IOS XR Firewall package
c12k-firewall.pie-3.5.3
Support for Virtual Firewall (vFW) on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.5.3
Manual pages for Cisco IOS XR CLI commands.
Cisco IOS XR FPD Package
c12k-fpd.pie-3.5.3
Firmware for shared port adapters (SPA) and for fixed port line cards supported in Cisco IOS XR.
Cisco IOS XR Diagnostic Package
c12k-diags.pie-3.5.3
Diagnostic utilities for Cisco IOS XR routers.
1 Packages are installed individually.
Memory Requirements
CautionIf you remove the media in which the software image or configuration is stored, the router may become unstable and fail.
The minimum memory requirements for Cisco XR 12000 Series Routers running Cisco IOS XR Software Release 3.5.3 consist of the following:
•
2-GB route memory on Performance Route Processor 2 (PRP-2)
•
1-GB ATA flash storage on PRP-2
•
1-GB line card route memory on all Engine 3 line cards
•
1-GB line card memory on all Engine 5-based SPA interface processors (SIPs)
–
The default route memory on the 12000-SIP-600 is 1 GB.
–
The default route memory on the 12000-SIP-401, 501, and 601 is 2 GB.
Note
The Performance Route Processor 1 (PRP-1) is not supported in production environments.
Hardware Supported
Cisco IOS XR Software for the current release supports the Cisco XR 12000 Series Router. All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 6 lists the hardware components supported on the Cisco XR 12000 Series Router and the minimum software versions required. See the "Determining Your Software Version" section.
Software Compatibility
Cisco IOS XR Software for the current release is compatible with the Cisco XR 12000 Series Router systems:
•
Cisco XR 12404 Router
•
Cisco XR 12406 Router
•
Cisco XR 12410 Router
•
Cisco XR 12416 Router
•
Cisco XR 12810 Router
•
Cisco XR 12816 Router
For the existing installed base, the following chassis are supported:
•
Cisco 12008 Router
•
Cisco 12010 Router
•
Cisco 12012 Router
•
Cisco 12016 Router
Note
If you are running IOS XR on a 120xx system with SIP 600, 401, 501 and 601, you must upgrade the fabric. For ROMMON, MBUS, and Fabric Downloader versions, see Other Firmware Code.
Other Firmware Code
The following minimum firmware code is supported by the Cisco XR 12000 Series Router:
•
LCs
–
MBUS Agent Software version 2.54 (RAM) (ROM version is 3.53)
–
ROM Monitor version 17.1
–
Fabric Downloader version 6.5 (ROM version is 6.5)
•
RPs
–
MBUS Agent Software version 2.54 (RAM) (ROM version is 3.53)
–
ROM Monitor version 1.14
Minimum Cisco IOS Image Level and Boot Helper Version for Migration to Cisco IOS XR on the Cisco XR 12000 Series Router
If you are migrating from Cisco IOS to Cisco IOS XR software on the Cisco XR 12000 Series Router, you must have the following minimum Cisco IOS Image Level and Boot Helper version to support Release 3.5.3:
•
Cisco IOS image—12.0(32).S
•
Cisco IOS Boot Helper—12.0(31).S0a
If you have an older version of this system, you must upgrade to the minimum level supported before performing a migration. Otherwise, your migration will fail. For more detailed information, see the document Migrating From Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router.
Determining Your Software Version
To determine the version of Cisco IOS XR software running on your router, log in to the router and enter the show version command, as illustrated below.
Step 1
Establish a Telnet session with the router.
Step 2
Enter the show version command:
RP/0/RP0/CPU0:router# show versionCisco CRS-1
On the Cisco CRS-1, you should see a response similar to the following:
Cisco IOS XR Software, Version 3.5.3[00]Copyright (c) 2008 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.45(20070510:194146) [CRS-1 ROMMON],BL-P uptime is 4 hours, 0 minutesSystem image file is "disk0:hfr-os-mbi-3.5.3/mbihfr-rp.vm"cisco CRS-16/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.24 DWDM controller(s)8 GigabitEthernet/IEEE 802.3 interface(s)4 Ethernet/IEEE 802.3 interface(s)103 Packet over SONET/SDH network interface(s)103 SONET/SDH Port controller(s)28 TenGigabitEthernet/IEEE 802.3 interface(s)2043k bytes of non-volatile configuration memory.38079M bytes of hard disk.981440k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).Boot device on node 0/0/SP is bootflash:Package active on node 0/0/SP:hfr-infra-test, V 3.5.3[00], Cisco Systems, at disk0:hfr-infra-test-3.5.3Built on Wed Jan 16 09:26:36 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-fpd, V 3.5.3[00], Cisco Systems, at disk0:hfr-fpd-3.5.3Built on Wed Jan 16 08:02:25 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-diags, V 3.5.3[00], Cisco Systems, at disk0:hfr-diags-3.5.3Built on Wed Jan 16 08:01:52 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-admin, V 3.5.3[00], Cisco Systems, at disk0:hfr-admin-3.5.3Built on Wed Jan 16 07:20:28 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-base, V 3.5.3[00], Cisco Systems, at disk0:hfr-base-3.5.3Built on Wed Jan 16 07:22:16 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-os-mbi, V 3.5.3[00], Cisco Systems, at disk0:hfr-os-mbi-3.5.3Built on Wed Jan 16 07:20:52 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8Configuration register on node 0/0/CPU0 is 0x102Boot device on node 0/0/CPU0 is mem:Package active on node 0/0/CPU0:hfr-infra-test, V 3.5.3[00], Cisco Systems, at disk0:hfr-infra-test-3.5.3Built on Wed Jan 16 09:26:36 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-fpd, V 3.5.3[00], Cisco Systems, at disk0:hfr-fpd-3.5.3Built on Wed Jan 16 08:02:25 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-diags, V 3.5.3[00], Cisco Systems, at disk0:hfr-diags-3.5.3Built on Wed Jan 16 08:01:52 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-mcast, V 3.5.3[00], Cisco Systems, at disk0:hfr-mcast-3.5.3Built on Wed Jan 16 07:19:31 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-mpls, V 3.5.3[00], Cisco Systems, at disk0:hfr-mpls-3.5.3Built on Wed Jan 16 07:07:32 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-lc, V 3.5.3[00], Cisco Systems, at disk0:hfr-lc-3.5.3Built on Wed Jan 16 07:20:29 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-fwdg, V 3.5.3[00], Cisco Systems, at disk0:hfr-fwdg-3.5.3Built on Wed Jan 16 07:20:10 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-admin, V 3.5.3[00], Cisco Systems, at disk0:hfr-admin-3.5.3Built on Wed Jan 16 07:20:28 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-base, V 3.5.3[00], Cisco Systems, at disk0:hfr-base-3.5.3Built on Wed Jan 16 07:22:16 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8hfr-os-mbi, V 3.5.3[00], Cisco Systems, at disk0:hfr-os-mbi-3.5.3Built on Wed Jan 16 07:20:52 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/hfr/workspace for c2.95.3-p8Cisco XR 12000 Series Router
On the Cisco XR 12000 Series Router, you should see a response similar to the following:
Cisco IOS XR Software, Version 3.5.3[00]Copyright (c) 2008 by Cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20041108:104740) [ashp-cisp-rommon 1.16dev(0.1)] DEVELOPMENT SOFTWARECopyrigh, Inc.PE1 uptime is 9 hours, 49 minutesSystem image file is "disk0:c12k-os-mbi-3.5.3/mbiprp-rp.vm"cisco 12416/PRP (7457) processor with 2097152K bytes of memory.7457 processor at 1266Mhz, Revision 1.21 4 Port ISE Packet Over SONET OC-12c/STM-4 Controller (4 POS)1 Cisco 12000 Series SPA Interface Processor-6002 Cisco 12000 Series - Multi-Service Blade Controllers1 1 Port ISE Packet Over SONET OC-48c/STM-16 Controller (1 POS)1 Cisco 12000 4 Port Gigabit Ethernet Controller (4 GigabitEthernet)2 Cisco 12000 Series Performance Route Processors1 Cisco 12000 4-Port ISE ATM Over SONET OC3/STM-1 Controller (4 ATM)3 Cisco 12000 Series SPA Interface Processor-601/501/4014 ATM Network Interface(s)8 FastEthernet/IEEE 802.3 interface(s)14 GigabitEthernet/IEEE 802.3 interface(s)6 Ethernet/IEEE 802.3 interface(s)2 Controller for the management of multilink interfacess42 Multilink network interface(s)13 PLIM QoS controller(s)5 Packet over SONET/SDH network interface(s)124 Serial network interface(s)10 SONET/SDH Port controller(s)140 T1 Port controller(s)6 T3 Port controller(s)1 TenGigabitEthernet/IEEE 802.3 interface(s)2042k bytes of non-volatile configuration memory.1000496k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).65536k bytes of Flash internal SIMM (Sector size 256k).Boot device on node 0/0/CPU0 is mem:Package active on node 0/0/CPU0:c12k-sbc, V 3.5.3[00], Cisco Systems, at disk0:c12k-sbc-3.5.3Built on Wed Jan 16 14:55:34 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-firewall, V 3.5.3[00], Cisco Systems, at disk0:c12k-firewall-3.5.3Built on Wed Jan 16 10:57:41 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-mcast, V 3.5.3[00], Cisco Systems, at disk0:c12k-mcast-3.5.3Built on Wed Jan 16 10:02:43 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-mpls, V 3.5.3[00], Cisco Systems, at disk0:c12k-mpls-3.5.3Built on Wed Jan 16 10:02:16 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-k9sec, V 3.5.3[00], Cisco Systems, at disk0:c12k-k9sec-3.5.3Built on Wed Jan 16 10:03:35 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-lc, V 3.5.3[00], Cisco Systems, at disk0:c12k-lc-3.5.3Built on Wed Jan 16 10:11:31 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-fwdg, V 3.5.3[00], Cisco Systems, at disk0:c12k-fwdg-3.5.3Built on Wed Jan 16 10:10:30 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-admin, V 3.5.3[00], Cisco Systems, at disk0:c12k-admin-3.5.3Built on Wed Jan 16 10:09:43 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-base, V 3.5.3[00], Cisco Systems, at disk0:c12k-base-3.5.3Built on Wed Jan 16 10:08:19 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8c12k-os-mbi, V 3.5.3[00], Cisco Systems, at disk0:c12k-os-mbi-3.5.3Built on Wed Jan 16 10:04:25 PST 2008By zamboni in /auto/srcarchive2/production/3.5.3/c12k/workspace for c2.95.3-p8
New and Changed Information
The following sections contain information on new features in Cisco IOS XR Software Release 3.5.3:
•
New Software Features in Cisco IOS XR Software Release 3.5.3
•
New Hardware Features in Cisco IOS XR Software Release 3.5.3
New Software Features in Cisco IOS XR Software Release 3.5.3
There are no new software features; Cisco IOS XR Software Release 3.5.3 is a maintenance release only.
New Hardware Features in Cisco IOS XR Software Release 3.5.3
There are no new hardware features; Cisco IOS XR Software Release 3.5.3 is a maintenance release only.
Important Notes
•
Country-specific laws, regulations, and licences—In certain countries, use of these products may be prohibited and subject to laws, regulations, or licenses, including requirements applicable to the use of the products under telecommunications and other laws and regulations; customers must comply with all such applicable laws in the countries in which they intend to use the products.
•
Migrating From Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router—When migrating a Cisco XR 12000 Series Router from Cisco IOS to Cisco IOS XR Software, follow the instructions provided in the documentation Migrating From Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router, Release 3.5.0.
•
Card, fan controller, and RP removal—For all card removal and replacement (including fabric cards, line cards, fan controller, and RP) follow the instructions provided by Cisco to avoid impact to traffic. See the Cisco IOS XR Getting Started Guide for procedures.
•
Exceeding Cisco testing—If you intend to test beyond the combined maximum configuration tested and published by Cisco, please contact your Cisco representative to discuss how to engineer a large-scale configuration maximum for your purpose.
•
More power required for Cisco SIP-600 line cards on the Cisco XR 12000 Series Router—These line cards draw more power than the previous ones. Depending on the exact configuration of power entry modules (PEMs) and other cards in the chassis, there may not be enough power available when inserting a new card or removing a PEM. Before you insert a new card or remove a PEM, run the following command in admin mode:
RP/0/0/CPU0:router# adminRP/0/0/CPU0:router# show environment power-supply table48V CurrentR/S/I Module (V) (A)0/24/* PEM1 54 4PEM2 53 40/25/* PEM1 54 4PEM2 53 4Total Power Supplies: 3200WRedundant Power Supplies: 1600WWorst Case Power Used: 621WCurrent Power Used: 428WCurrent Redundant Power Available: 1172WCurrent Total Power Available: 2772WWorst Case Redundant Power Available: 979WWorst Case Total Power Available: 2579WPID Description Watts--- ----------- -----GRP-B Route Processor 38PRP-1 Cisco 12000 Series Performance Route Processor 60LC-4OC-3-POS-SM 4 Port Packet Over SONET OC-3c/STM-1 804OC3X/POS-MM-MJ-B 4 port ISE OC3 90...If you plan to insert a new card, locate the entry for the card to be inserted and note the power consumed by it. If this power is less than the figure given in Worst Case Redundant Power Available (the figure is displayed in the show environment power-supply table command output), the card can be safely inserted. As long as the Worst Case Redundant Power Available is not zero, a PEM can be powered down for replacement without impact.
Note
No alerts are issued if more cards are inserted than the PEMs can support. It is your responsibility to determine your power budget for the chassis before making any changes to it. Exceeding the power budget may result in the PEM being overloaded and cards powering down due to insufficient power being provided.
•
Per-interface ICMP disable feature unsupported on Cisco XR 12000 Series Routers.
•
Disable the preempt feature in the VFW application—In Cisco IOS XR Release 3.5.3, you must disable the preempt feature in the VFW application. Make sure that you configure no preempt for all fault-tolerant groups under the Admin context on the VFW application. See the following example:
ft group 1peer 1no preemptassociate-context ctx1inservice
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 lists the open caveats for Cisco IOS XR Software Release 3.5.3:
•
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
•
Cisco XR 12000 Series Router-Specific Caveats
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
The following caveat applies to both router platforms:
•
CSCsm19082
Basic Description:
With LDP GR, Lnk Adj del during session recreate makes IGP sync to go down.
Symptom:
L2vpn/L3VPN Traffic Drop after RP FO.
Conditions:
With L2vpn/L3VPN (Intra-AS & Inter-AS), CSC, mVPN traffic drop after executing RP FO on one of the PE in CRS MPLS SIT testbed, traffic drops were observed for about 2-3 minutes.
Workaround:
None. Router recovers after 2-3 minutes.
•
CSCsl83020
Basic Description:
MCAST/MVPN traffic drop up to 1200 seconds on RP FO.
Symptom:
MVPN/MCAST traffic is affected for up to 1200 seconds.
Conditions:
The traffic drop is observed after triggering an RP switchover.
Workaround:
There is no workaround. Traffic recovers automatically after the drop is observed.
•
CSCsl66846
Basic Description:
BFD session flap on adding default route to NULL interface.
Symptom:
When a default route to Null0 is added, all adjacency prefixes are moved to reject and come back to switching after 15 sec. This will cause traffic to those adjacency prefixes to be dropped.
Conditions:
Occurs when a default route to Null0 is added.
Workaround:
None at the moment.
•
CSCsl55570
Basic Description:
TE tunnels flap after RP FO.
Symptom:
TE tunnels flap after RP FO on the Multi-Chassis system.
Conditions:
Seen after DSC RP FO.
Workaround:
Increasing the signaling refresh interval to 180 as a workaround on all the RSVP links. Box will recover by itself. With the workaround, no traffic loss is expected.
•
CSCsl49057
Basic Description:
Netflow configuration may fail to be applied to one or more interfaces on router reload.
Symptom:
This is a random failure that may occur if NetFlow is applied to many interfaces in several line cards. It happens only if traffic starts flowing through the interfaces as soon as they are configured, and flows need to be exported right away.
Workaround:
The workaround is to manually apply the failed configuration with the directive commit configuration failed startup.
•
CSCsj78665
Basic Description:
Cannot successfully perform clear counter t1 command.
Symptom:
Ambiguous command:
RP/0/0/CPU0:Router# clear counter t1 0/1/0/0Condition:
This occurs when both MPLS and k9sec pies are installed on a router and the "clear counter ..." command is issued from exec mode. The cause of the issue is that the above two pies introduces two software interface types "tunnel-te" and "tunnel-ipsec" and the parser detects an ambiguity between these two types. This is a bug in the parser, because at the same level a controller type "T1" is an allowed option. But the parser does not honor this longest match.
Workaround:
Provided the user has a root-system task-id, the same clear command can be run from the ksh as:
RP/0/0/CPU0:Router# run exec_t1e1 clear T10_1_0_0 clear_statsHere, T10_1_0_0 is the T1 controller name without spaces between the type and instance and the digits in instance are separated by "_" (underscores).
•
CSCsj93281
Basic Description:
Make OSPF max-metric router-lsa on RP failover deterministic default.
Symptom:
OSPF max-metric router LSA is not sent on FO even when "max-metric router-lsa on-startup..." is configured.
Conditions:
It is only on 3.4 releases and the LSA with max metric is sent only on power on, not on switchover.
Workaround:
An SMU is available to make max-metric the default. Contact technical support for the location.
Cisco CRS-1-Specific Caveats
The following caveats are specific to the Cisco CRS-1 platform:
•
CSCsl75592
Basic Description:
T3E3 Spa fails to boot up after a soft oir.
Symptom:
SPA T3E3 card failed to boot after performing a soft oir, using the hw-module subslot location x/x/x command.
Conditions:
This issue is likely to happen only if hw-module subslot commands are performed and also sometimes on an entire SIP 800 card reload.
Workaround:
Perform a soft oir of the card again and it will recover.
•
CSCsm08868
Basic Description:
MCAST_DOWN message observed on RP switchover.
Symptom:
MCAST_DOWN message from fabric planes in 2+4 setup after RP failover in DSC rack.
RP/0/RP0/CPU0:Jan 4 15:49:24.861 : fsdb_aserver[189]: %FABRIC-FSDB-1-PLANE_UPDOWN : Plane 1 state changed to MCAST_DOWN;Conditions:
The issue is seen after performing an RP switchover in the DSC rack.
Workaround:
None. No other impact, except for the error message.
•
CSCsm09331
Basic Description:
Online diags configuration is rejected after swapping card type (RPA- RPB).
Symptom:
Online diags configuration is rejected on reload after swapping an RPA with an RPB.
Conditions:
Currently, we see the configuration on the router, but it does not have any effect since the card type changed.
Workaround:
Manually reapply the configuration.
•
CSCsm10628
Basic Description:
OC48 SPA fails to boot after performing MSC swap.
Symptom:
OC48 SPA fails to boot.
Conditions:
The issue can be run into after doing MSC swap when the SIP-800 card is loaded with 6 SPAs.
Workaround:
Recovery is to soft oir the spa card using hw-module subslot x/x/x reload command.
•
CSCsl01722
Basic Description:
RIB/PIM interaction after RP FO on multi-chassis causes temporary multicast loss.
Symptom:
After performing a Fail-Over some multicast traffic streams might be affected for up to three minutes and then recovers.
Conditions:
This was seen on a multi-chassis system with several multicast streams (both SM and SSM). The traffic hit was seen on few streams only and for 2-3 minute period.
Workaround:
Traffic recovers after few minutes of FO with no other side effects.
•
CSCsk78968
Basic Description:
With negotiation mismatch GIG-E flaps continuously.
Symptom:
GIG-E interface continuously flaps.
Conditions:
This happens when there is a negotiation mismatch.
Workaround:
Set correct negotiation.
•
CSCsl09342
Basic Description:
In MC, sysdb responds nothing to show rib and show static.
Symptom:
On multi-chassis systems, the show rib and show route commands show no routes. The symptom is purely cosmetic. All routes remain in operation, and no traffic forwarding or routing is impacted.
Conditions:
The problem can occur after a switchover of a non-dLRSC RP pair.
Workaround:
Use the process restart to restart sysdb_mc on each active RP, followed by sysdb_svr_shared on the dLRSC node.
•
CSCsf02904
Basic Description:
After reload, show route summary shows zero routes.
Symptom:
After reloading the router using admin reload location all, the output of the show route summary and show route commands shows zero routes, even though routes are known to be configured on the router. Local and remote interfaces are pingable. In a multi-rack system, this problem is seen when executing the show commands from any active management node.
Conditions:
This bug has been observed in IOS-XR Release 3.3.2, but it may also exist in the 3.4 release. It is a rare-occurring issue, which is seen after reloading the router using the admin reload location all command.
Workaround:
This is believed to be an issue in the System Database component (SysDB). Restarting the sysdb_mc process on the dSDRSC node, using the process restart sysdb_mc command, most likely fixes the issue. Restarting sysdb_mc is non-traffic-impacting and should not have any other adverse effect on the router.
•
CSCsj20726
Basic Description:
Active RP in Multishelf does not allow intra-rack heartbeats across racks.
Symptom:
In absence of full mesh of cabling between the LCC & FCC SC-GE-22 cards, there is a likelihood that standby SC card may keep reloading due to loss of heartbeats.
Conditions:
In absence of full mesh cabling between the control Ethernet ports of RPs and SC-GE-22. The full mesh details are documented in customer documentation on Cisco.com.
This may occur in spite of an L2 path that is present between the SCs through multiple switches in RPs / SC-GE-22. You may be able to successfully ping across SCs through ctrl eth, but still heartbeats are not passed across.
Workaround:
Complete the full-mesh cabling as recommended in customer documentation on Cisco.com.
Further Problem Description:
This is due to the unexpected behavior of the switch in Active RP to not forward the heartbeats (reserved MAC address) to be passed across the racks.
Cisco XR 12000 Series Router-Specific Caveats
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
CSCsk62338
Basic Description:
Active SBC restart after failover.
Symptom:
Active SBC restart after failover.
Conditions:
This issue is seen after multiple failovers.
Workaround:
None.
•
CSCsk81099
Basic Description:
Configuring SDR with a '/' in the sdr name crashes LRD process.
Symptom:
Configuring SDR with a sdr-name containing the character '/' causes a crash of the lrd process. Subsequent operations are stalled because SDR configuration fails.
Conditions:
Config operation involving SDR carve operation.
Workaround:
Avoid using / in the sdr-name during configuration. If configuration already exists, replace the sdr-name and reapply configuration.
•
CSCsk86218
Basic Description:
Ensure MBI are compatible before the SW Upgrade.
Symptom:
1.
While upgrading lower releases to 3.5.2, the standby PRP gets stuck in MBI state.
2.
While downgrading from 3.5.2 to lower releases, the standby PRP gets stuck in MBI state.
Conditions:
1.
This issue occurs during and after the upgrade, if standby is not coming up (stuck in MBI state). This can happen since there is a version mismatch in the Active and Standby PRPs. One is 3.5.2 and other one is 3.x.x. Then, the standby card may not come up since there is incompatibility in the images. Follow the Workaround 1 or 2 below.
2.
This issue occurs during and after the downgrade if standby is not coming up (stuck in MBI state). This can happen since there is a version mismatch in the Active and Standby PRPs. One is 3.x.x and other one is 3.5.2. Then the standby card may not come up since there is incompatibility in the images. Follow the Workaround 3 below.
3.
This issue occurs mainly when there is MBI incompatibility encountered between software versions and install commit is not issued for one of the software. In the situation when RP reloads it will try to load last committed software that is when the issue occurs.
Workaround:
1.
If the issue is encountered after the successful upgrade to 3.5.2 from 3.4.x, but any of the non-dSC RPs reloaded due to an error condition when booting up or an OIR event before "install commit" was issued. Non-dSC RP is either a standby RP or an RP in non-Owner SDR. Below instructions mention standby RP, the steps are the same for non-Owner RPs.
(a) Verify that this is the issue/situation. Check for the following:
- Install operation completed successfully before issuing a reload for all nodes (console logs).
- Wait for active RP to come up and verify that it's running 3.5.2 ("show install active").
- Verify that standby RP is trying to boot 3.4.2, this can be seen on the standby console in the banner when the image is booting (e.g. "Cisco IOS XR Software for the Cisco XR c12000-mbiprp, Version 3.4.2[1]").
- There should be the following error displayed periodically on the standby console:
Insthelper encountered a fatal error condition, and is exiting:
Error value = (1341786888), Error string = ('Subsystem(8180)' detected the 'warning' condition 'Code(5)': Host is down)
(b) Bring standby RP to ROMMON. This can be done, for example:- Issue "hw-module loc <location> reload" from dSC.
- Issue "send break" on the standby RP console line when the following displayed:
DRAM DIMM Slot 1: 2048M found, Slot 2: Empty MPC7457 platform with 2097152 Kbytes of main memory(c) Reset BOOT variable to a new value.
- Check its current value. It should be pointing to disk0:c12k-os-mbi-3.4.2/mbiprp-rp.vm
- Check if 3.5.2 MBI exists on disk, for example:
rommon 7 > dir disk0:c12k-os-mbi-3.5.2.14I File size Perms File name 0 drw- etc 0 drw- instdb_v 0 drw- mbi 0 drw- drp 0 drw- gsr 10088776 -rw- mbiprp-rp.vm 0 drw- instdb- Set BOOT variable to new 3.5.2 MBI value, for example:
rommon 8 > BOOT=disk0:c12k-os-mbi-3.5.2.14I/mbiprp-rp.vm rommon 9 > sync- Do "reset" to reload this node and let it come up with 3.5.2 MBI.
If you changed config-register value when bringing to ROMMON, change it back to the original value.
If 3.5.2 MBI is not present on disk, need to go through "diskboot procedure" for standby, refer to scenario 2 below.
(d) Verify, "install commit"
- Verify that the node comes up successfully with 3.5.2, wait until it's in IOX-RUN state.
- When all non-dSC RP nodes are up, issue "install commit".
2.
If the router is running 3.5.2 sw and a new standby (or non-Owner) RP is inserted that was diskbooted with 3.4.x previously.
Prepare the new RP in the same way as with original diskboot procedure for standby. For example, by booting mbiprp-rp.vm from tftp or ftp. For example, on the standby console:
rommon 1 > boot tftp address://directory/mbiprp-rp.vm-3.5.2 192.85.16.23For more documentation on diskboot procedure refer to Migrating From Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router, Release 3.5 document on Cisco.com.
3.
If the issue is encountered when:
- Downgrading from 3.5.2 to 3.4.x, but a non-dSC RP rebooted/OIR and booting 3.5.2 while the dSC RP is 3.4.x.
- The router is booted with 3.4.x sw, and a new RP is inserted that was baked with 3.5.2 previously.
•
CSCsl03683
Basic Description:
SPA-4XCT3/DS0 out-of-service state after restarting packet process.
Symptom:
4xCT3/DS0 SPA out of service after restarting packet process. Problem happens in a C12000 router running IOS-XR 3.5.2 release image.
Workaround:
None. Only a reload fixes the problem.
•
CSCsl61560
Basic Description:
CSC Switchover cannot access console/aux port router.
Symptom:
Shutting down the Clock Scheduler Card or switchover of Clock Scheduler Card on XR C12000 Router blocks accessibility to the router console and auxiliary ports.
Conditions:
CSC Switchover on XR C12000 Router.
Workaround:
Reloading the router.
Resolved Cisco IOS XR Software PSIRT-Related Caveats
•
CSCti62211
Basic Description:
BGP flaps due to unknown attribute
Symptom:
Cisco IOS XR Software contains a vulnerability in the Border Gateway Protocol (BGP) feature. The vulnerability manifests itself when a BGP peer announces a prefix with a specific, valid but unrecognized transitive attribute. On receipt of this prefix, the Cisco IOS XR device will corrupt the attribute before sending it to the neighboring devices. Neighboring devices that receive this corrupted update may reset the BGP peering session.
Conditions:
Affected devices running Cisco IOS XR Software corrupt the unrecognized attribute before sending to neighboring devices, but neighboring devices may be running operating systems other than Cisco IOS XR Software and may still reset the BGP peering session after receiving the corrupted update. This is per standards defining the operation of BGP.
Workaround:
No workaround. Cisco developed a fix that addresses this vulnerability and will be releasing free software maintenance upgrades (SMUs) progressively starting 28 August 2010.
A Security Advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100827-bgp.shtml
Upgrading Cisco IOS XR Software
Cisco IOS XR Software is installed and activated from modular packages, allowing specific features or software patches to be installed, upgraded, or downgraded without affecting unrelated processes. Software packages can be upgraded or downgraded on all supported card types, or on a single card (node).
Software packages are installed from package installation envelope (PIE) files that contain one or more software components.
The following URL contains links to information about how to upgrade or downgrade Cisco IOS XR Software to the current release:
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html
Troubleshooting
For information on troubleshooting Cisco IOS XR Software, see the Cisco IOS XR Getting Started Guide and the document Cisco IOS XR Troubleshooting.
Related Documentation
The following sections describe the documentation available for the Cisco CRS-1 and Cisco XR 12000 Series Router. Documentation is available in the form of PDF and HTML files and is available on www.Cisco.com.
Use these release notes with the following documents:
Hardware Documents
You can find the most current hardware documentation at the following URLs:
Cisco CRS-1 Series Router:
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
Cisco XR 12000 Series Router:
http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html
Software Documents
The Cisco IOS XR Software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. For a full list, see About Cisco IOS XR Software Documentation for Release 3.5.0 for a list of Cisco IOS XR Software documentation for Release 3.5.0.
You can find the most current software documentation at the following URL:
http://www.cisco.com/en/US/products/ps5845/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.
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)
Copyright © 2008 Cisco Systems, Inc. All rights reserved.
Feedback

