Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.6.3
Minimum and Preferred Cisco IOS Image and Boot Helper Levels for Migration
Determining the Software Version
New Software Features in Cisco IOS XR Software Release 3.6.3
Cisco CRS-1 and Cisco XR 12000 Series Router
Cisco CRS-1 Router-Specific Features Only
Cisco XR 12000 Series Router-Specific Features Only
Cisco XR 12000 Series Router Services
New Hardware Features Supported in Cisco IOS XR Software Release 3.6.3
Minimum Flash Disk Requirements When Upgrading to Release 3.6.3
Activation Requirements for the Cisco CRS-1 Multishelf System Encryption PIE
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
Caveats Specific to the Cisco CRS-1 Router
Caveats Specific to the Cisco XR 12000 Series Router
Upgrading Cisco IOS XR Software
Using a Software Maintenance Update (SMU)
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IOS XR Software Release 3.6.3
July 9, 2009
Cisco IOS XR Software Release 3.6.3
Text Part Number OL-19165-01
Note
For information about Cisco IOS XR Software Release 3.6.3, see "Important Notes" section.
Note
These release notes describe the features provided in the Cisco IOS XR Software Release 3.6.3 and are updated as needed.
For a list of software caveats that apply to Cisco IOS XR Software Release 3.6.3, 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:
•
•
•
•
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:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
–
•
•
•
•
For more information about new features provided on various platforms for Cisco IOS XR Software Release 3.6.3, see the "New Features and Enhancements" section in this document.
System Requirements
Cisco IOS XR Software Release 3.6.3 supports the following platforms:
To determine the software versions or levels of your current system, see the "Determining the Software Version" section.
Cisco CRS-1
This section describes the system requirements for Cisco IOS XR Software Release 3.6.3 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 Determining the 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 Software Release 3.6.3 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.6.3 supported on the Cisco CRS-1 router.
Table 1 Cisco CRS-1 Supported Feature Sets (Cisco IOS XR Software Release 3.6.3 PIE Files)
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.6.3
Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.vm-3.6.3
Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.6.3
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.6.3
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.6.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.6.3
Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI19 (Software based IPSec support - maximum of 500 tunnels).
Cisco IOS XR Documentation Package
hfr-doc.pie-3.6.3
Man pages for Cisco IOS XR CLI commands
Cisco IOS XR FPD Package
hfr-fpd.pie-3.6.3
Firmware for Fixed PLIM20 and SPA21 modules as well as ROMMON22 images for Cisco CRS-1 chassis.
Cisco IOS XR Diagnostic Package
hfr-diags-p.pie-3.6.3
Diagnostic utilities for routers running Cisco IOS XR software.
Cisco IOS XR Session Border Controller Package
hfr-sbc-p.pie-3.6.3
Session Border Controller package for the Cisco CRS-1 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
20 Physical layer interface module
21 Shared port adapters
22 ROM monitor
Table 2 lists Cisco CRS-1 TAR files.
Memory Requirements
Caution
The minimum memory requirements for Cisco CRS-1 routers running Cisco IOS XR Software Release 3.6.3 consist of the following:
•
•
•
Also review the flash disk memory space requirements for future upgrades under the "Minimum Flash Disk Requirements When Upgrading to Release 3.6.3" section.
Release 3.7.x and later releases require installation of at least 2 GB of flash memory before you upgrade.
Hardware Supported
Cisco IOS XR Software Release 3.6.3 is supported on all Cisco CRS-1 routers. Likewise, all the Cisco CRS-1 hardware features are supported by Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 3 lists these Cisco CRS-1 hardware components and the minimum versions of Cisco IOS XR software required in each case. For more information, see the "Firmware Support" section.
Software Compatibility
Cisco IOS XR Software Release 3.6.3 is compatible with the following Cisco CRS-1 systems:
•
•
•
•
Firmware Support
The Cisco CRS-1 router supports the following firmware code:
•
•
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.6.3 supported on the Cisco XR 12000 Series Router. The system requirements include the following information:
To determine the software versions or levels of your current system, see "Determining the 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.6.3 features. Table 4 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for Cisco IOS XR Software Release 3.6.3 and supported on the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Set (Cisco IOS XR Software
Release 3.6.3 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.6.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.6.3
Contains the required core packages including OS, Admin, Base, Forwarding, and Routing SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
c12k-mgbl.pie-3.6.3
CORBA2 agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.6.3
MPLS-TE,3 LDP, 4 MPLS Forwarding, MPLS OAM,5 LMP,6 OUNI,7 and RSVP.8
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.6.3
Multicast Routing Protocols (PIM,9 MSDP,10 IGMP,11 Auto-RP, BSR12 ), Tools (SAP, MTrace, MRINFO), and Infrastructure (MRIB,13 MURIB,14 MFWD)15 .
Cisco IOS XR Security Package
c12k-k9sec.pie-3.6.3
Support for Encryption, Decryption, IPSec16 , SSH,17 SSL,18 and PKI.19 (Software based IPSec support - maximum of 500 tunnels or Hardware based IPSec - maximum of 64K tunnels using the SPA-IPSEC-2G-2)
Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.6.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.6.3
Session Border Controller Package for a Cisco XR 12000 Series Router.
Cisco IOS XR Service IPSec controller Package
c12k-ipsec-service.pie-3.6.3
Support for service-ipsec and service-gre interfaces in Cisco IOS XR software.
Cisco IOS XR Firewall package
c12k-firewall.pie-3.6.3
Support for Virtual Firewall (vFW) on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.6.3
Man pages for Cisco IOS XR CLI commands.
Cisco IOS XR FPD Package
c12k-fpd.pie-3.6.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.6.3
Diagnostic utilities for Cisco IOS XR routers.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 MPLS Traffic Engineering
4 Label Distribution Protocol
5 Operations, Administration, and Maintenance
6 Link Manager Protocol
7 Optical User Network Interface
8 Resource Reservation Protocol
9 Protocol Independent Multicast
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Bootstrap router
13 Multicast Routing Information Base
14 Multicast-Unicast RIB
15 Multicast forwarding
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Physical layer interface module
Table 5 lists the Cisco XR 12000 Series Router TAR files.
Memory Requirements
Caution
The minimum memory requirements for Cisco XR 12000 Series Routers running Cisco IOS XR Software Release 3.6.3 consist of the following:
•
Note
•
•
•
–
–
Note
Hardware Supported
Cisco IOS XR Software Release 3.6.3 is supported on the Cisco XR 12000 Series Router. Likewise, all Cisco XR 12000 Series Router hardware features are supported by Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 6 lists the supported hardware components on the Cisco XR 12000 Series Router and the minimum versions of Cisco IOS XR software they require. For more information, see the "Determining the Software Version" section.
Software Compatibility
Cisco IOS XR Software Release 3.6.3 is compatible with the following Cisco XR 12000 Series Routers with enhanced power and cooling sub-systems:
•
•
•
•
•
•
•
•
•
•
The following models with original, non-enhanced power and cooling sub-systems are supported, but are no longer available for purchase:
•
•
•
•
•
•
•
•
•
•
•
•
Firmware Support
Minimum and Preferred Cisco IOS Image and Boot Helper Levels for Migration
If you are migrating from Cisco IOS to Cisco IOS XR software on the Cisco XR 12000 Series Router, you must have the following minimum Cisco IOS Image Level and Boot Helper version to support Release 3.6.3:
•
However, the recommended Cisco IOS image level to support migration to Release 3.6.3 can be either one of the following:
•
•
If you have an earlier version of this system, you must upgrade to at least the minimum supported level before performing a migration. Otherwise, your migration may fail.
For more information, see the Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.
Table 8 lists the recommended firmware level for Cisco IOS 12.0(32)SY5 when migrating to Cisco IOS XR Software, Release 3.6.3.
Determining the 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:
Step 1
Step 2
RP/0/RP0/CPU0:router# show versionCisco CRS-1
On the Cisco CRS-1 router, you should see a response similar to the following:
Cisco IOS XR Software, Version 3.6.3[00]Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.49(20080319:195807) [CRS-1 ROMMON],MPLS-MR-LR1-6 uptime is 20 hours, 37 minutesSystem image file is "disk0:hfr-os-mbi-3.6.3/mbihfr-rp.vm"cisco CRS-16/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.22 Ethernet/IEEE 802.3 interface(s)21 SONET/SDH Port controller(s)21 Packet over SONET/SDH network interface(s)8 GigabitEthernet/IEEE 802.3 interface(s)4 T3 Port controller(s)4 Serial network interface(s)8 TenGigabitEthernet/IEEE 802.3 interface(s)1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.2053440k 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-fpd, V 3.6.3[00], Cisco Systems, at disk0:hfr-fpd-3.6.3Built on Wed May 13 18:49:20 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-diags, V 3.6.3[00], Cisco Systems, at disk0:hfr-diags-3.6.3Built on Wed May 13 18:48:39 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-admin, V 3.6.3[00], Cisco Systems, at disk0:hfr-admin-3.6.3Built on Wed May 13 18:04:05 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-base, V 3.6.3[00], Cisco Systems, at disk0:hfr-base-3.6.3Built on Wed May 13 18:06:01 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-os-mbi, V 3.6.3[00], Cisco Systems, at disk0:hfr-os-mbi-3.6.3Built on Wed May 13 18:03:16 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.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-fpd, V 3.6.3[00], Cisco Systems, at disk0:hfr-fpd-3.6.3Built on Wed May 13 18:49:20 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-diags, V 3.6.3[00], Cisco Systems, at disk0:hfr-diags-3.6.3Built on Wed May 13 18:48:39 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-mcast, V 3.6.3[00], Cisco Systems, at disk0:hfr-mcast-3.6.3Built on Wed May 13 18:01:16 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-mpls, V 3.6.3[00], Cisco Systems, at disk0:hfr-mpls-3.6.3Built on Wed May 13 17:50:43 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-lc, V 3.6.3[00], Cisco Systems, at disk0:hfr-lc-3.6.3Built on Wed May 13 18:03:58 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-fwdg, V 3.6.3[00], Cisco Systems, at disk0:hfr-fwdg-3.6.3Built on Wed May 13 18:03:57 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-admin, V 3.6.3[00], Cisco Systems, at disk0:hfr-admin-3.6.3Built on Wed May 13 18:04:05 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-base, V 3.6.3[00], Cisco Systems, at disk0:hfr-base-3.6.3Built on Wed May 13 18:06:01 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8hfr-os-mbi, V 3.6.3[00], Cisco Systems, at disk0:hfr-os-mbi-3.6.3Built on Wed May 13 18:03:16 PDT 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/hfr/workspace for c2.95.3-p8...Cisco 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.6.3[00]Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20071011:134444) [skumarss-rommon_upgrade 1.21dev(0.1)] DEVELOPMENT SOFTWARECopyright (c) 1994-2007 by cisco Systems, Inc.P2_UUT uptime is 18 hours, 20 minutesSystem image file is "disk0:c12k-os-mbi-3.6.3/mbiprp-rp.vm"cisco 12416/PRP (7457) processor with 3670016K bytes of memory.7457 processor at 1266Mhz, Revision 1.22 Cisco 12000 4 Port Gigabit Ethernet Controllers (8 GigabitEthernet)3 Cisco 12000 Series SPA Interface Processor-601/501/4012 Cisco 12000 Series Performance Route Processors1 Cisco 12000 4-Port ISE ATM Over SONET OC3/STM-1 Controller (4 ATM)1 Cisco 12000 4-Port ISE ATM Over SONET OC12/STM-4 Controller (4 ATM)1 1 Port ISE Packet Over SONET OC-48c/STM-16 Controller (1 POS)14 PLIM QoS controller(s)13 GigabitEthernet/IEEE 802.3 interface(s)3 TenGigabitEthernet/IEEE 802.3 interface(s)8 FastEthernet/IEEE 802.3 interface(s)6 Ethernet/IEEE 802.3 interface(s)11 SONET/SDH Port controller(s)8 ATM Network Interface(s)3 Packet over SONET/SDH network interface(s)1009k bytes of non-volatile configuration memory.57119M bytes of hard disk.1642240k bytes of ATA PCMCIA card at disk 0 (Sector size 512 bytes).1642240k bytes of ATA PCMCIA card at disk 1 (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-fpd, V 3.6.3[00], Cisco Systems, at disk0:c12k-fpd-3.6.3Built on Wed May 13 23:06:09 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-diags, V 3.6.3[00], Cisco Systems, at disk0:c12k-diags-3.6.3Built on Wed May 13 23:04:53 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-mcast, V 3.6.3[00], Cisco Systems, at disk0:c12k-mcast-3.6.3Built on Wed May 13 20:45:02 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-mpls, V 3.6.3[00], Cisco Systems, at disk0:c12k-mpls-3.6.3Built on Wed May 13 20:44:31 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-k9sec, V 3.6.3[00], Cisco Systems, at disk0:c12k-k9sec-3.6.3Built on Wed May 13 20:46:01 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-lc, V 3.6.3[00], Cisco Systems, at disk0:c12k-lc-3.6.3Built on Wed May 13 18:57:57 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-fwdg, V 3.6.3[00], Cisco Systems, at disk0:c12k-fwdg-3.6.3Built on Wed May 13 18:56:50 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-admin, V 3.6.3[00], Cisco Systems, at disk0:c12k-admin-3.6.3Built on Wed May 13 18:56:03 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-base, V 3.6.3[00], Cisco Systems, at disk0:c12k-base-3.6.3Built on Wed May 13 18:54:10 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8c12k-os-mbi, V 3.6.3[00], Cisco Systems, at disk0:c12k-os-mbi-3.6.3Built on Wed May 13 18:49:47 PST 2009By edde-bld1 in /auto/srcarchive2/production/3.6.3/c12k/workspace for c2.95.3-p8...
New Features and Enhancements
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.6.3:
•
•
New Software Features in Cisco IOS XR Software Release 3.6.3
Cisco CRS-1 and Cisco XR 12000 Series Router
The following Cisco IOS XR Software Release 3.6.3 software features or enhancements to existing features are supported on both the Cisco CRS-1 router and Cisco XR 12000 Series Router platforms. Those features with hypertext links have user documentation available in this release note, but not in Cisco IOS XR Release 3.6.0 documentation on www.cisco.com.
•
•
•
–
–
–
–
–
•
–
Cisco CRS-1 Router-Specific Features Only
The following new features in Cisco IOS XR Software Release 3.6.3 are supported only on the Cisco CRS-1 platform:
•
Cisco XR 12000 Series Router-Specific Features Only
None.
Cisco XR 12000 Series Router Services
None.
OSPFv2 SPF Prefix Prioritization
OSPFv2 SPF prefix prioritization lets you select which prefixes to converge first during routing convergence events.
Information About OSPFv2 SPF PRefix Prioritization
When a large number of prefixes must be installed in the Routing Information Base (RIB) and the Forwarding Information Base (FIB), the update duration between the first and last prefix can be significant during SPF.
In networks where time-sensitive traffic (for example, VoIP) may transit the same router along with other traffic flows, it is important to prioritize RIB and FIB updates during SPF for these time-sensitive prefixes.
The OSPFv2 SPF Prefix Prioritization feature provides the administrator with the ability to prioritize important prefixes to be installed into the RIB during SPF calculations. Important prefixes converge faster among prefixes of the same route type per area. Before RIB and FIB installation, routes and prefixes are assigned to various priority batch queues in the OSPF local RIB based on specified route policy. The RIB priority batch queues are classified as "critical," "high," "medium," and "low," in the order of decreasing priority.
When enabled, prefix alters the sequence of updating the RIB with the following prefix priority:
Critical > High > Medium > Low
As soon as prefix priority is configured, /32 prefixes are no longer preferred by default and are placed in the low-priority queue if they are not matched with higher-priority policies. Route policies must be devised to retain /32s in the higher-priority queues.
Priority is specified using route policy, which can be matched based on IP addresses or route tags. During SPF, a prefix is checked against the specified route policy and is assigned to the appropriate RIB batch priority queue. The following are examples of this scenario:
•
–
–
•
–
–
–
•
–
–
–
•
–
–
Note
The [no] spf prefix-priority route-policy rpl command is used to prioritize OSPFv2 prefix installation into the global RIB during SPF.
SPF prefix prioritization is disabled by default. In disabled mode, /32 prefixes are installed into the global RIB before other prefixes. If SPF prioritization is enabled, routes are matched against the route-policy criteria and are assigned to the appropriate priority queue based on the SPF priority set.
Unmatched prefixes, including /32s, are placed in the low-priority queue. If all /32s are desired in the high-priority queue or medium-priority queue, configure the following single route map:
prefix-set ospf-medium-prefixes0.0.0.0/0 ge 32end-setOSPFv2 SPF Prefix-Priority Commands
The following command was created to support this feature in Cisco IOS XR Release 3.6.3.
spf prefix-priority route-policy (OSPF)
To prioritize OSPFv2 prefix installation into the global Routing Information Base (RIB) during a Shortest Path First (SPF) run, use the spf prefix-priority route-policy command in router configuration mode. To return to the system default value, use the no form of this command.
spf prefix-priority route-policy policy-name
no spf prefix-priority route-policy policy-name
Syntax Description
Command Default
SPF prefix prioritization is disabled.
Command Modes
OSPF router configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
SPF prefix prioritization is disabled, by default. In disabled mode, the /32 prefixes are installed into the global RIB before other prefixes.
If SPF prefix prioritization is enabled, routes are matched against the route-policy criteria and are assigned to the appropriate priority queue based on the spf-priority set. Unmatched prefixes, including the /32 prefixes, are placed in the low-priority queue. For an example of how to configure a queue with a different priority, see the following Examples section.
Task ID
Examples
The following example shows how to configure OSPFv2 SPF prefix prioritization:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# prefix-set ospf-critical-prefixesRP/0/RP0/CPU0:router(config-pfx)# 66.0.0.0/16RP/0/RP0/CPU0:router(config-pfx)# end-setRP/0/RP0/CPU0:router(config)# route-policy ospf-spf-priorityRP/0/RP0/CPU0:router(config-rpl)# if destination in ospf-critical-prefixes then set spf-priority critical endifRP/0/RP0/CPU0:router(config-rpl)# end-policyRP/0/RP0/CPU0:router(config)# router ospf 1RP/0/RP0/CPU0:router(config-ospf)# router-id 66.0.0.1RP/0/RP0/CPU0:router(config-ospf)# spf prefix-priority route-policy ospf-spf-priorityIf all /32 prefixes are desired in the high-priority queue or medium-priority queue, configure the following single route map:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# prefix-set ospf-medium-prefixesRP/0/RP0/CPU0:router(config-pfx)# 0.0.0.0/0 ge 32RP/0/RP0/CPU0:router(config-pfx)# end-setRelated Commands
prefix-set
Enters prefix set configuration mode and defines a prefix set.
route-policy (RPL)
Defines a route policy and enters route-policy configuration mode.
Configuring OSPFv2 SPF Prefix Prioritization
This task allows you to configure OSPFv2 SPF prefix prioritization.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
or
commit7.
DETAILED STEPS
OSPFv2 Message Queue Enhancements
This feature provides a number of enhancements to improve event processing and performance in a scaled configuration environment, using the following commands:
•
•
clear ospf statistics message-queue
To reset the Open Shortest Path First (OSPF) message queue statistics, use the clear ospf statistics message-queue command in EXEC mode.
clear ospf statistics message-queue
Syntax Description
This command has no arguments or keywords.
Command Default
No default behavior or value
Command Modes
EXEC
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Use the clear ospf statistics message-queue command to reset OSPF queue dispatch statistics consisting of peak lengths and total counts.
Task IDExamples
The following example shows how to reset the OSPF statistics message queue:
RP/0/RP0/CPU0:router# clear ospf statistics message-queueRelated Commands
clear ospf statistics
Clears the OSPF statistics of interfaces and neighbors. For information, see Cisco IOS XR Routing Command Reference on www.cisco.com.
queue dispatch flush-lsa
To change the rate-limited LSA scheduled for flushing that are processed in each iteration, use the queue dispatch flush-lsa command in router ospf configuration mode. To return to the default setting, use the no form of this command.
queue dispatch flush-lsa flush-quantum
no queue dispatch flush-lsa flush-quantum
Syntax Description
Command Default
The default is 150 LSAs flushed per run.
Command Modes
OSPF router configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
In scaled configurations, LSA flushes across high-availability events, such as process restarts and RP switchovers (without graceful restart/NSR), can be delayed significantly. This might result in traffic being diverted back to the restarting router prematurely. For this reason, you should use a higher value for flush-quantum argument, so that more LSA flushes are processed per iteration and so that the flushes are completed in less time.
Note
Task ID
Examples
The following example configures a change in the LSA flush queue:
RP/0/CPU0/CPU0:Router(config-ospf)# queue dispatch flush-lsa 300RP/0/0/CPU0:Router# show ospf 1 message-queue | include LSAMon Nov 10 14:46:19.214 PDT PDTRate-limited LSA processing quantum: 150Current rate-limited LSA queue length: 0Rate-limited LSA queue peak len: 508Rate-limited LSAs processed: 870Flush LSA processing quantum: 300Current flush LSA queue length: 0Flush LSA queue peak len: 400Rate-limited flush LSAs processed: 2973Related Commands
show ospf message-queue
Displays information about the queue dispatch values, peak lengths, and limits of the OSPF message queue.
queue dispatch incoming
To limit the number of incoming packets processed, including LSAUpdates, LSAcks, DBDs, LSRequests, and Hellos that trigger a state change, use the queue dispatch incoming command in router configuration mode. To return to the system default value, use the no form of this command.
queue dispatch incoming count
no queue dispatch incoming
Syntax Description
Command Default
The default incoming count is 300 packets (when the count is not configured).
Command Modes
Router configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to limit the number of continuous incoming events processed to 500:
RP/0/RP0/CPU0:router(config-ospf)# queue dispatch incoming 500
Note
Related Commands
queue dispatch rate-limited-lsa
To set the maximum number of rate-limited link-state advertisements (LSAs) re-originated per run, use the queue dispatch rate-limited-lsa command in router configuration mode. To return to the system default value, use the no form of this command.
queue dispatch rate-limited-lsa count
no queue dispatch rate-limited-lsa
Syntax Description
Defaults
The default number of rate-limited LSAs processed per run is 150.
Command Modes
Router configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to set the maximum number of rate-limited LSAs to 300:
RP/0/RP0/CPU0:router(config-ospf)# queue dispatch rate-limited-lsa 300Related Commands
queue dispatch spf-lsa-limit
To change the maximum number of Type 3-4 and Type 5-7 link-state advertisements (LSAs) processed per shortest path first (SPF) iteration within a single SPF run, use the queue dispatch spf-lsa-limit command in router configuration mode. To return to the system default value, use the no form of this command.
queue dispatch spf-lsa-limit count
no queue dispatch spf-lsa-limit
Syntax Description
count
Maximum number of continuous Type 3-4 and Type 5-7 LSAs processed per SPF iteration within a single SPF run. Range is 30 to 3000.
Defaults
The default number of Type 3-4 and Type 5-7 processed per SPF iteration in a single run is 150 LSAs.
Command Modes
Router configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to limit the number of continuous Type 3-4 and Type 5-7 LSAs processed per SPF iteration within a single SPF run, to 100:
RP/0/RP0/CPU0:router(config-ospf)# queue dispatch spf-lsa-limit 100Related Commands
queue limit
To set the high watermark for incoming events by priority, use the queue limit command in router configuration mode. To return to the system default values, use the no form of this command.
queue limit {high | medium | low} count
no queue limit {high | medium | low}
Syntax Description
Defaults
When the corresponding configuration is absent, the default watermark is as follows:
High watermark: 9500
Medium watermark: 9000
Low watermark: 8000Command Modes
Router configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following examples show how to set the maximum number of events per queue0:
RP/0/RP0/CPU0:router(config-ospf)# queue limit high 11000RP/0/RP0/CPU0:router(config-ospf)# queue limit medium 10000RP/0/RP0/CPU0:router(config-ospf)# queue limit low 9000
Note
Related Commands
show ospf message-queue
To display the information about the queue dispatch values, peak lengths, and limits, use the show ospf message-queue command in EXEC mode.
show ospf message-queue
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following is sample output from the show ospf message-queue command:
RP/0/0/CPU0:router# show ospf 1 message-queueOSPF 1Hello Input Queue:Current queue length: 0Event scheduled: 0Total queuing failures: 0Maximum length : 123Total pkts processed: 551088Limit: 5000Router Message QueueCurrent instance queue length: 0Current redistribution queue length: 0Current ex spf queue length: 0Current sum spf queue length: 0Current intra spf queue length: 0Event scheduled: 0Maximum length : 123Total low queuing failures: 0Total medium queuing failures: 0Total high queuing failures: 0Total instance events: 612Processing quantum : 300Low queuing limit: 8000Medium queuing limit: 9000High queuing limit: 9500Rate-limited LSA processing quantum: 150Current rate-limited LSA queue length: 0Rate-limited LSA queue peak len: 16Rate-limited LSAs processed: 320Flush LSA processing quantum: 150Current flush LSA queue length: 0Flush LSA queue peak len: 0Rate-limited flush LSAs processed: 0Summary originations processed: 0Summary origination queue length: 0Summary origination peak queue length: 0SPF-LSA-limit processing quantum: 150Managed timers processing quantum: 25TE msg processing quantum: 60Instance message count: 0Instance pulse send count: 612Instance pulse received count: 612Global pulse count: 0Instance Pulse errors: 0TE Message QueueCurrent queue length: 0Total queuing failures: 0Maximum length : 0Number of Dlink errors: 0
Table 9 describes the significant fields shown in the display.
Related Commands
New and Revised LDP Commands
The following show commands have been introduced or revised as of the current release:
show mpls ldp forwarding
To display information about MPLS Label Distribution Protocol (LDP) routing and forwarding entries, use the show mpls ldp forwarding command in EXEC mode.
show mpls ldp forwarding [IP destination prefix/mask length [detail]] [location node-id | standby]
Syntax Description
Command Default
The default setting of this command shows MPLS LDP forwarding information for the active node.
EXEC
Command Modes
EXEC
Command History
Release 3.6.3
The detail keyword was added to this command on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows the output of the show mpls ldp forwarding command without the use of any keywords:
RP/0/RP0/CPU0:router# show mpls ldp forwarding 1.1.1.1/32
refix Label Label Outgoing Next Hop GR StaleIn Out Interface---------------- ------- ---------- ------------ --------------- -- -----1.1.1.1/32 16000 ImpNull PO0/2/0/3.1001 131.1.1.11 N NThe following example shows new output for the detail keyword containing two new fields, Routing update and Forwarding update, from the show mpls ldp forwarding command, which is used primarily for analyzing and debugging LDP convergence:
RP/0/RP0/CPU0:router# show mpls ldp forwarding 1.1.1.1/32 detailPrefix Label Label Outgoing Next Hop GR StaleIn Out Interface---------------- ------- ---------- ------------ --------------- -- -----1.1.1.1/32 16000 ImpNull PO0/2/0/3.1001 131.1.1.11 N NRouting update : Mar 31 13:35:25.348 (00:55:32 ago)Forwarding update: Mar 31 13:35:25.349 (00:55:32 ago)The Routing update field is a time stamp showing the last time a route update was received from RIB.
The Forwarding update field is a time stamp showing the last time LDP updated MPLS forwarding.
show mpls ldp bindings
New optional keywords and associated output have been added in Cisco IOS XR Software Release 3.6.3 to the show mpls ldp bindings command, as shown below.
show mpls ldp binding [ local-only | remote-only | brief | ... ]
Syntax Description
Defaults
The default setting displays information for all nodes in summary form.
Command Modes
EXEC
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows the new output from show mpls ldp bindings [prefix/mask] detail:
RP/0/RP0/CPU0:router# show mpls ldp bindings 150.150.150.150/32 detail150.150.150.150/32, rev 2Local binding: label: IMP-NULLAdvertised to: (6 peers)120.120.120.120:0 130.130.130.130:0 150.150.150.1:0 150.150.150.2:0150.150.150.3:0 150.150.150.4:0Remote bindings: (3 peers)Peer Label----------------- --------120.120.120.120:0 27018130.130.130.130:0 26017160.160.160.160:0 27274The output changes consist of the following information:
•
•
•
The following example shows sample output for the command show mpls ldp bindings with the brief keyword, which displays the entire LDP binding database in brief format.
When no local label binding is present for a given prefix, the output displays a dash under the Local Label column.
RP/0/RP0/CPU0:router# show mpls ldp bindings briefPrefix Local Advertised Remote BindingsLabel (peers) (peers)------------------ -------- ---------- ---------------2.0.0.1/32 - 0 12.0.0.2/32 - 0 12.2.2.2/32 16000 2 24.4.4.4/32 16001 2 24.4.4.44/32 16002 2 25.5.5.5/32 IMP-NULL 2 25.22.0.0/16 IMP-NULL 2 15.22.2.0/24 16404 2 27.9.1.2/32 16406 2 012.12.5.1/32 IMP-NULL 2 2...The following example shows the output from show mpls ldp bindings command using the local-only keyword:
RP/0/RP0/CPU0:router# show mpls ldp bindings local-only
7.9.1.2/32, rev 212644Local binding: label: 16406No remote bindings25.1.24.0/24, rev 203502Local binding: label: IMP-NULLNo remote bindings25.1.25.0/24, rev 203500Local binding: label: IMP-NULLNo remote bindings25.1.26.0/24, rev 203498Local binding: label: IMP-NULLNo remote bindings25.1.27.0/24, rev 203496Local binding: label: IMP-NULLNo remote bindingsThe output for the local-only keyword is similar to that of show mpls ldp bindings with no keywords, except that the local-only keyword strips out any prefixes for which you have not received a remote label.
The following example shows the output from show mpls ldp bindings command using the remote-only keyword:
RP/0/RP0/CPU0:router# show mpls ldp bindings remote-only2.0.0.1/32, rev 0No local bindingRemote bindings: (1 peers)Peer Label----------------- --------120.120.120.120:0 280182.0.1.1/32, rev 0No local bindingRemote bindings: (1 peers)Peer Label----------------- --------120.120.120.120:0 28019The output for the remote-only keyword is similar to that of show mpls ldp bindings with no keywords, but the remote-only keyword strips out any prefixes for which you have no local label binding.
show mpls ldp discovery
To display MPLS Label-Distribution Protocol (LDP) discovery hello information, use the show mpls ldp discovery command in EXEC mode.
The brief keyword is new in Release 3.6.3.
show mpls ldp discovery [brief] [location node-id | standby]
Syntax Description
Defaults
The default setting displays information for all nodes in summary form.
Command Modes
EXEC
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
Task ID
Examples
The following example shows the output from the show mpls ldp discovery brief command:
RP/0/RP0/CPU0:router# show mpls ldp discovery briefLocal LDP Identifier: 150.150.150.150:0Discovery Source Peer LDP Id Holdtime Session------------------------ -------------------- -------- -------BE35 130.130.130.130:0 15 YGi0/6/0/6 160.160.160.160:0 15 YGi0/6/2/7.1 174.1.1.2:0 45 YTarget: 120.120.120.120 120.120.120.120:0 90 YTarget: 150.150.150.1 150.150.150.1:0 120 Yshow mpls ldp neighbor
Two new columns (NSR and IPv4 Label) have been added in Cisco IOS XR Software Release 3.6.3 to the output of the show mpls ldp neighbor command when using the brief keyword, as follows:
RP/0/RP0/CPU0:router# show mpls ldp neighbor briefPeer GR NSR Up Time Discovery Address IPv4 Label----------------- -- --- ---------- --------- ------- ----------2.2.2.2:0 N Y 01:39:50 1 4 193.3.3.3:0 N N 01:38:04 1 3 5When a session is eligible for NSR and is NSR-ready (meaning that the session has been synchronized to the standby RP to achieve NSR), the column shows Y.
When a session is eligible for NSR, but has not yet been synchronized, the column shows N.
When a session is ineligible for NSR (for example, an L2VPN-ATOM session), the column displays an NA.
The IPv4 Label column shows the number of labels received from peer for the IPv4 prefix, and which are currently in the binding database.
Support for IGP Synchronization Delay on Restart
An LDP process failure occurring in LDP and IGP scale networks configured with the LDP-IGP synchronization feature, may put stress on the network and may also lead to convergence delays and traffic loss.
This new feature introduces a configurable timer-based delay for the sync-achieved notification for LDP interfaces sent to IGP following an LDP process failure. When this configured delay period has elapsed, IGP then receives all sync-achieved event notifications in a single message, thereby reducing stress on the network.
igp sync delay on-proc-restart
To delay the declaration of synchronization events to the Interior Gateway Protocol (IGP) when the Label Distribution Protocol (LDP) fails or restarts, use the igp sync delay command in MPLS LDP configuration mode. To return to the default behavior, use the no form of this command.
igp sync delay on-proc-restart seconds
no igp sync delay on-proc-restart seconds
Syntax Description
seconds
Time duration that notification to IGPs of an LDP synchronization event should be delayed before restarting. Range is from 60 to 600 seconds.
Defaults
This command is disabled by default.
Command Modes
MPLS LDP configuration
Command History
Release 3.6.3
This command was introduced on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
When configured, LDP starts a one-time delay timer for the configured number of seconds after an LDP process failure is detected. While this restart-delay timer is running, LDP-IGP synchronization processing occurs as usual, but IGPs receive no notifications. During this time, the sync status of interfaces that were previously reported as Ready appear as Deferred in the show mpls ldp igp sync command output.
When the timer expires, LDP recomputes the synchronization status (shown in the Sync status field of the show mpls ldp igp sync command output) of all the previously Deferred states and sets their status accordingly, followed by a notification to IGP of all Ready-state LDP interfaces.
This feature is complementary to existing IGP sync features (basic and interface delay timers) and does not affect how they work, the only impact being to defer notification to IGPs until the restart-delay timer expires. For example, when both the interface delay timer and the proc-restart delay timer are configured and running, the synchronization status for interfaces can be in one of the following states:
•
•
•
Task ID
Examples
The following example shows how to configure LDP to delay the declaration of synchronization events to IGP by 60 seconds:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# mpls ldpRP/0/RP0/CPU0:router(config-ldp)# igp sync delay on-proc-restart 60The following example shows the status following execution of the command with the new output for the current release in boldface:
RP/0/RP0/CPU0:router# show mpls ldp igp syncProcess Restart Sync Delay: 60 sec, Global timer running (15 sec remaining)GigabitEthernet0/3/0/2:Sync status: Deferred....When the timer is not running, the output displays the following:
Process Restart Sync Delay: 60 sec, Global timer not runningRelated Commands
Configuring LDP IGP Synchronization Process Restart Delay
Perform this task when you want to delay the declaration of synchronization events to IGP when LDP fails or restarts.
Note
SUMMARY STEPS
1.
2.
3.
4.
or
commitDETAILED STEPS
Enhancement to Multicast Hashing
Enhancements have been made to the keywords of this existing command to make additional hashing algorithms available.
multipath
To enable Protocol Independent Multicast (PIM) to divide the multicast load among several equal-cost paths, use the multipath command in the appropriate configuration mode. To return to the default behavior, use the no form of this command.
multipath [hash {source | source-nexthop} {source-nexthop | interface-extended}]
no multipath
Syntax Description
Defaults
This command is disabled by default.
Command Modes
Multicast routing configuration
Multicast routing IPv4 and IPv6 configuration
Multicast VRF configurationCommand History
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
By default, equal-cost multipath (ECMP) paths are not load-balanced. A single path from each unicast route is used for all multicast routes (which is the equivalent of the no form of the multipath command).
Note
Task ID
Examples
The following example shows how to enable multipath functionality for the default IPv4 addressing:
RP/0/RP0/CPU0:router(config)# multicast-routingRP/0/RP0/CPU0:router(config-mcast)# multipath hash sourceRP/0/RP0/CPU0:router(config-mcast)#Enhanced Process Distribution to Improve Load-Balancing Across Cisco CRS-1 RPs
The default Cisco IOS XR process placement policy has changed to improve the distribution of processing load across active Cisco CRS-1 route processors (RPs). These changes affect systems with more than one active RP, such as Cisco CRS-1 Multichassis systems and Cisco CRS-1 Single-Chassis systems with optional, distributed route processors (DRPs) installed.
Highlights of the New Process Distribution Feature
•
–
–
–
•
•
If a single active non-dLRSC RP pair exists, the IPv4 and IPv6 groups will be placed on that pair.
If more than one active non-dLRSC RP pair exists, the IPv4 group will be placed on one such pair and the IPv6 group on another. The placement of each group occurs when that group starts.
If no non-dLRSC pairs exist, but an unpaired active non-dLRSC RP does, then, the first placeable group to start (IPv4/MPLS or IPv6) will be placed on the dLRSC, with the other group being placed on the non-dLRSC RP pair.
Information About How Process Placement Works
•
•
•
•
•
•
•
•
Note
•
New Hardware Features Supported in Cisco IOS XR Software Release 3.6.3
None
Important Notes
•
Configuration for Cisco IOS XR Software releases earlier than 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!!Configuration for 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!endIn Cisco IOS XR Software Release 3.6.0 and later releases, the implicitly assigned QoS class class-default must have at least one percent bandwidth made available to it.
This can be done either by assigning at least 1 percent explicitly (bandwidth remaining percent 1), or by making sure 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.
Note
•
•
•
•
•
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
•
•
ft group 1peer 1no preemptassociate-context ctx1inservice•
•
Minimum Flash Disk Requirements When Upgrading to Release 3.6.3
•
An installation of Cisco IOS XR Software Release 3.6.3, with all optional packages installed, requires at least 450 MB of free flash disk memory. For this reason, make sure that you have enough free space available before you try to upgrade to Release 3.6.3.
If you are upgrading fromCisco IOS XR Software Release 3.5.4 and you are unable to upgrade to the 2-GB, or 4-GB flash disk, you must first remove all existing Release 3.5.4 SMUs before you proceed with the Cisco IOS XR Software Release 3.6.3 upgrade. Otherwise, the upgrade will fail due to insufficient space.
Note
•
Table 10 specifies the Cisco IOS XR releases when the flash memory upgrade is mandatory for the Cisco CRS-1 router and the Cisco XR 12000 Series Router. The minimums required depend on the release number from which you are upgrading, as indicated in the footnotes.
.
Table 10 Minimum Requirements for Flash Memory by Router Platform and Release
Cisco CRS-12
1 GB
1 GB
1 GB
1 GB
Cisco XR 12000 Series Router
1 GB
2 GB
2 GB
2 GB
1 Supports 2- and 4-GB flash disk memory on both platforms.
2 Upgrade to 2 GB or 4 GB of flash disk memory is compulsory if you are upgrading from a release that has less than the 450 MB minimum of free space required to avoid having to remove SMUs and optional .pie files prior to upgrade.
The flash disk size of a Cisco CRS-1 router or Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.4.0, Release 3.5.0, or Release 3.6.1 can be either 1 GB, 2 GB, or 4 GB.
Note
For details about these flash disks, including the upgrade procedure for both platforms, see the flash disk upgrade instructions at:
http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.pdf.
Activation Requirements for the Cisco CRS-1 Multishelf System Encryption PIE
Previously the Cisco CRS-1 multishelf system encryption PIE was installed and activated when you ordered the Cisco IOS XR IP/MPLS Core Software 3DES image.
With this release, you must explicitly activate the Cisco IOS XR IP/MPLS Core Software 3DES image [hfr-k9sec-p.pie-3.6.3, PID is XC-RPK9-03.06], by following these instructions:
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious.
This section lists the caveats for Cisco IOS XR Software Release 3.6.3:
•
•
•
Cisco CRS-1 and Cisco XR 12000 Series Router Caveats
The following caveats apply to both platforms:
•
Basic Description:
Delayed syslog messages occur as a result of the back pressure introduced from the console and virtual terminals. If the rate of incoming syslog messages becomes very high, the console and virtual terminals become busy printing all the messages.
Symptom:
The syslogd process is blocked and the syslog messages on the console are delayed for several minutes and appear very slowly.
The same behavior occurs with syslog messages sent to the syslog server.
•
Basic Description:
When polling IP-MIB from a Cisco IOS XR Software system, the ipAdEntAddr process fails to return the IP address of interfaces placed in a VRF.
Conditions:
Although the ipAdEntAddr process returns the expected IP address for interfaces that are not used in the context of MPLS VPN, it does not do so for interfaces that are configured in a VRF instance.
Workaround:
None.
•
Basic Description:
The documentation of the key-string (keychain) command in Cisco IOS XR System Security Command Reference, Release 3.6.0 and earlier did not include the character limitations for the key-string-text argument, which will be enforced in later releases.
The following text provides an abbreviated representation of the documentation for this command that details these limitations.
key-string (keychain)
To specify the text string for the key, use the key-string command in keychain-key configuration mode. To disable this feature, use the no form of this command.
[no] key-string [clear | password] key-string-text
Syntax Description
Usage Guidelines
To use this command, your Cisco IOS XR software system administrator must assign you to a user group associated with a task group that includes the corresponding command task IDs. If you need assistance with your task group assignment, contact your system administrator. For detailed information about user groups and task IDs, see the Configuring AAA Services on Cisco IOS XR Software module of Cisco IOS XR System Security Configuration Guide.
For an encrypted password to be valid, the following statements must be true:
–
–
–
Either of the following examples would be valid encrypted passwords:
1234abcdor
50aefdExamples
The following example shows how to use the key-string command:
RP/0/RP0/CPU0:router# configureRP/0/RP0/CPU0:router(config)# key chain isis-keysRP/0/RP0/CPU0:myhost(config-isis-keys)# key 8RP/0/RP0/CPU0:myhost(config-isis-keys-0x8)# key-string password 50aefd•
Basic Description:
Using FTP to install packages may result in incorrect parsing of the FTP URL. URLs that have multiple slashes may be sent to the server as a relative path instead of an absolute path.
Conditions:
Use of a path such as ftp://username:password@server//directory/file normally initiates an attempt to download /directory/file from the server. However, due to incorrect parsing, an attempt is actually made to download $HOME/directory/file instead.
Workaround:
Two possible workarounds exist:
–
ftp://username:password@server/directory/file downloads $HOME/directory/file–
•
Basic Description:
The netio process crashes while enabling debug commands with ACL filter.
Symptom:
Sometimes, the netio process terminates abnormally when debug cef command with acl filter is used.
Conditions:
The problem occurs when the user enables debug cef packet ipv4acl and there is slowpathipv6 traffic being switched.
Workaround:
Specify the afi filter to the debug cef command that matches the type of debug acl being supplied to the debug command.
For example, use the commands in the following formats:
–
Or
–
Caveats Specific to the Cisco CRS-1 Router
•
The Cisco CRS-1 Multichassis goes down after the command hw-module location node-id reload is issued to reload the s2 card without first shutting down the controller fabric plane.
Conditions:
The issue may occur during non-graceful reloads of an s2 card.
The recommended procedure requires a graceful reload (using the administration -level configuration command controller fabric plane x shutdown before any cables are removed). In other words, the fabric plane must first be shut down before attempting a reload.
Note
Workaround:
None.
•
Basic Description:
Multiple classes in a policy map can be marked with priority. This results in all traffic from these classes being placed in the same high-priority queue. In such a configuration, the default queue limit value is applied to the queue and this cannot be altered. The configuration line is accepted, but is ignored.
Conditions:
This inability to change the queue limit value occurs only if multiple priority classes are configured.
Workaround:
The following steps summarize the workaround, an example of which appears in the workaround example below:
1.
2.
3.
4.
Example:
policy-map parentclass gold_and_platinumpriorityservice-policy priority-class!class class-defaultend-policy-mappolicy-map priority-classclass goldpolice rate percent 25!class platinumpolice rate percent 25!class class-defaultqueue-limit 5 ms!end-policy-map•
Basic Description:
On a multichassis 4+4 system, during startup, upgrade, and reloads of various types such as power cycle and reload CLI, a flood of sysdb timeout messages is generated from various processes. This indicates potential transport issues and online diagnostic errors, and that the diag configurations will not work. This may sometimes also be accompanied by process restarts.
Example:
SP/0/7/SP:Mar 31 17:39:12.290 : dumper[56]: %OS-DUMPER-4-ERR_SYSDB_REG_NOTIFY : Sysdb notifier registration for /admin/cfg/gl/dumper/ failed. Error: 'sysdb' detected the 'fatal' condition 'A management request timed out before a response was received (check for potential transport issues within the system, or deadlocked SysDB processes)' SP/0/7/SP:Mar 31 17:39:12.315 : online_diag_hfr_sp[220]: %DIAG-DIAG-3-GOLDXR_ERROR : Failed to register verification for /admin/cfg/gl/diags_online/node/0_7_SP/. Error: 0xA0812000 ('sysdb' detected the 'fatal' condition 'A management request timed out before a responsewas received (check for potential transport issues within the system, SP/0/7/SP:Mar 31 17:39:12.388 : reddrv_listener[245]: arbitrate_sysdb_thread: error -1602150400 ('sysdb' detected the 'fatal' condition 'A management request timed out before a response was received (check for potential transport issues within the system, or deadlockedSysDB processes)') from sysdb_register_notification SP/2/13/SP:Mar 31 10:39:47.173 : sysdb_mc[265]: %SYSDB-SMC-7-TIMEOUT : Message #42, destined for admin plane (2/RP0/CPU0), timed out having received 0 of 1 expected responses: returning error to client syslogd_helper. Check for potential transport issues within the system, or deadlocked SysDB processes.Conditions:
Observed on a 4+4 multichassis setup scaled with 64 line cards.
Workaround:
No workaround is necessary. The errors stop after about 10 to 15 minutes.
•
Basic Description:
After a system reload, OSPF neighbors/adjacencies can take an extended period of time to become established. During this time, OSPF commands are unresponsive and an error message similar to the following example may appear:
RP/0/RP0/CPU0: sysdb_svr_shared[555]: %SYSDB-SYSDB-7-TIMEOUT : EDM request for 'oper/ipv4-ospf/gl/proc/100/vrf/default/public/xml/process/area_proc_terse/'from 'ospf_show' (jid 65798, node 0/RP0/CPU0). No response from 'ospf' (jid 426, node 3/RP0/CPU0) within the timeout period (100 seconds).Conditions:
This condition occurs in the following circumstances: a) a multi- chassis system running Cisco IOS XR Software, Release 3.6.3 without SNMP configuration, with default process distribution; b) a single-chassis system DRP/B(s) for automatic or manual process distribution (manual process distribution is not formally supported); c) when using Secure Domain Routers (SDR) with a DRP/B hosting the SDR function.
In all of the foregoing instances, no SNMP configurations can be present.
Note
Workaround:
Configure SNMP on the system.
Note
•
Basic Description:
Copying a very large prefix set, or a configuration with a very large prefix set, to the running configuration takes 30 minutes or more due to the prefix set verification process. The larger the prefix list, the more time it takes.
Conditions:
This condition is seen under the following circumstances:
–
–
Workaround:
None.
•
Basic Description:
Sometimes, exec process is terminated when describe CLI commands are used.
Symptom:
WD sysmon may terminate the exec process if there is a severe increase in CPU usage.
Conditions:
This symptom is observed on Cisco CRS-1 routers when using the command describe show tech-support or describe show screddrv standby.
Workaround:
None. However, this problem appears very rarely and there is no impact to the functionality of the router.
Caveats Specific to the Cisco XR 12000 Series Router
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
Basic Description:
IKE fails during Phase 2 and the ISAKMP security association is deleted, generating the following error message:
%SECURITY-IKE-3-RETRANSMISSION_LIMIT.Symptom:
The IPSec tunnel goes down and crypto traffic is lost
Conditions:
Occurs when there is a restart or crash in the UDP process
Workaround:
Restart the ike and ipsec_mp processes one or more times, as needed.
•
Basic Description:
A kernel crash may be seen on a Multi-Service Blade line card when a Clock Scheduler card is Online, Inserted, or Removed. Although this has been observed during CSC switchover either by OIR or CSC shutdown, the same issue may be encountered during the initial router startup.
Conditions:
This issue is seen on a fully populated Cisco XR 12416 Series Router running Cisco IOS XR Software Release 3.6.3.
Workaround:
None. Line card reloads and recovers automatically.
•
Basic Description:
Ace error messages appear and the traffic stops during spa-mix while sending IPSec and Clear IP Traffic over SPA-4XCT3/DS0 and SPA-IPSEC-2G.
Symptom:
Fails to process HAPI rx packet when spa-mix.
Conditions:
–
–
Workaround:
If the IPSec SPA is used at full rate (1 Gbps per direction), locate the other SPA on a separate line card.
•
Basic Description:
Bit error rate test (BERT) errors for the 3-in-24 pattern on the channel-group BERT for the 8-Port Channelized T1/E1 Shared Port Adapters (SPA).
Symptom:
Invoking BERT pattern 3-in-24 on the channel-group may result in BERT errors incrementing for the 8-Port Channelized T1/E1 SPA.
Conditions:
For the 8-Port Channelized T1/E1 SPA, invoking BERT pattern 3-in-24 on the channel-group may result in an increase in BERT errors.
Workaround:
None. There is no impact on the functionality of the system.
•
Basic Description:
Before initiating field diagnostics, the user is not warned to remove the cabling from the linecard under test.
Symptom:
Unexpected interrupts while field diagnostics are in progress.
Conditions:
–
–
Workaround:
Remove all external cables to the line card under test before initiating field diagnostics.
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
Using a Software Maintenance Update (SMU)
A SMU is used as a software patch delivery unit that after installation and activation provides a point-fix for a critical issue in a given software release. The SMU consists of a SMU file and an associated caveat listing.
Remember to periodically check the online SMU download page for new SMUs that may apply to your software release. Go to this URL and then click on IOS XR Software Maintenance Upgrades (SMU):
The following URL points to SMU FAQs to assist you with questions you may have regarding how and when to install SMUs for your release:
http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/SMU_FAQ.pdf
Troubleshooting
For information on troubleshooting Cisco IOS XR software, see the Cisco IOS XR Getting Started Guide and Cisco IOS XR Troubleshooting Guide.
Related Documentation
The following sections describe the documentation available for the Cisco CRS-1 and the Cisco XR 12000 Series Router. Documentation is available in the form of PDF and HTML files and is available on www.Cisco.com.
Use these release notes with the following documents:
Hardware Documents
To access the most current hardware documentation, go to:
Cisco CRS-1:
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
Cisco XR 12000 Series Router:
http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html
Software Documents
The Cisco IOS XR software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. For a full list, see About Cisco IOS XR Software Documentation for Release 3.6 for a list of Cisco IOS XR Software documentation for Release 3.6.0.
To access the most current software documentation, go to:
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.
CCDE, CCSI, CCENT, Cisco Eos, Cisco HealthPresence, the Cisco logo, Cisco Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco WebEx, DCE, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn and Cisco Store are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website 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. (0903R)
Copyright © 2009 Cisco Systems, Inc. All rights reserved
Guest
