Table Of Contents
Release Notes for Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.2
Cisco IOS Image Level and Boot Helper Migration Requirements
RMA Card Firmware Upgrade Procedure
Determining Your Software Version
New Features in Cisco IOS XR Software Release 3.9.2
PBTS Default Class Enhancement
Unequal Bandwidth for Link Bundles
MPLS TE Auto-Bandwidth with Link Bundles
show mpls traffic-eng tunnels auto-bw
Bundle Interface Re-size Triggers Immediate Preemption and RSVP
mpls traffic-eng link-management timers preemption-delay
New Features in Cisco IOS XR Software Release 3.9.1
New Software Features Supported on all Platforms
Cisco XR 12000 Series Router-Specific Software Features
New Hardware Features for the Cisco XR 12000 Series Router
Minimum Flash Disk Requirements When Upgrading to Release 3.9.2
Resolved Release 3.9.2 Cisco IOS XR Software Caveats
Open Release 3.9.2 Cisco IOS XR Software Caveats
Open Release 3.9.2 Caveats Specific to the Cisco XR 12000 Series Router
Upgrading Cisco IOS XR Software
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2
January 27, 2011
Cisco IOS XR Software Release 3.9.2
Text Part Number OL-23380-02
These release notes describe the features provided in the Cisco IOS XR Software Release 3.9.2 for the Cisco XR 12000 Series Router and are updated as needed.
Note
For information on the Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.9.2, see the "New Features in Cisco IOS XR Software Release 3.9.2" section.
You can find the most current Cisco IOS XR software documentation at
http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html
These electronic documents may contain updates and modifications. For more information on obtaining Cisco documentation, see the "Obtaining Documentation and Submitting a Service Request".
For a list of software caveats that apply to Cisco IOS XR Software Release 3.9.2, see the "Caveats" section. The caveats are updated for every release and are described at www.cisco.com.
We recommend that you view the field notices for this release located at the following URL to see if your software or hardware platforms are affected:
http://www.cisco.com/public/support/tac/fn_index.html
Key Changes from Previous Releases in Cisco IOS XR Release 3.9.2
Cisco IOS XR Software Release 3.9.2 requires a 2-GB Flash Disk as a minimum. Therefore, you must upgrade an existing PCMCIA 1-GB Flash Disk to 2 GB or 4 GB before upgrading to Cisco IOS XR Software Release 3.9.2. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.9.2" section.
Contents
These release notes contain the following sections:
•
•
•
•
•
•
Introduction
Cisco IOS XRsoftware is a distributed operating system designed for continuous system operation combined with service flexibility and high performance.
Cisco IOS XR software running on the Cisco XR 12000 Series Router provides the following features and benefits:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
–
–
–
•
For more information about new features provided on the Cisco XR 12000 Series Router for Cisco IOS XR Software Release 3.9.2, see the "New Features in Cisco IOS XR Software Release 3.9.2" section in this document.
System Requirements
This section describes the system requirements for Cisco IOS XR Software Release 3.9.2 supported on the Cisco XR 12000 Series Router. The system requirements include the following information:
•
•
To determine the software versions or levels of your current system, see the "Determining Your Software Version" section.
Feature Set Table
Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.9.2 features.
Table 1 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for Cisco IOS XR Software Release 3.9.2, supported on the Cisco XR 12000 Series Router.
Table 1 Cisco XR 12000 Series Router Supported Feature Set (Cisco IOS XR Software
Release 3.9.2 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.9.2
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.9.2
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.9.2
CORBA2 agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.9.2
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.9.2
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.9.2
Support for Encryption, Decryption, IPSec16 , SSH,17 SSL,18 and PKI.19
Software based IPSec support: maximum of 500 tunnelsCisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.9.2
Support for booting the Standby RP on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
The documentation package is not supported in Cisco IOS XR Software Release 3.9.2.
Please refer to the Cisco XR 12000 Series Router command reference documentation located at the following URL:
http://www.cisco.com/en/US/products/ps6342/prod_command_reference_list.html
Cisco IOS XR FPD Package
c12k-fpd.pie-3.9.2
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.9.2
Diagnostic utilities for Cisco IOS XR routers.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.9.2
.man pages for Cisco IOS XR software on the Cisco XR 12000 Series Router chassis.
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 2 lists the Cisco XR 12000 Series Router TAR files.
Memory Requirements
Caution
The minimum memory requirements for a Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.9.2 consist of the following:
•
Note
•
•
•
•
•
–
•
–
Note
•
Note
Hardware Supported
All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 3 lists the supported hardware components on the Cisco XR 12000 Series Router and the minimum required software versions. For more information, see the "Determining Your Software Version" section.
Software Compatibility
Cisco IOS XR Software Release 3.9.2 is compatible with the following Cisco XR 12000 Series Router systems:
•
•
•
•
•
•
•
•
•
•
The following chassis are supported for an existing installed base:
•
•
•
Note
Other Firmware Support
The Cisco XR 12000 Series Router supports the following firmware code:
•
For Engine 3 line card:
–
–
–
•
–
–
–
•
For Performance Route Processor 2 (PRP-2):
–
–
For Performance Route Processor 3 (PRP-3):
–
–
Cisco IOS Image Level and Boot Helper Migration Requirements
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 Boothelper version to support Release 3.9.2:
•
•
If you have an earlier version of this system, you must upgrade to the minimum supported level before performing a migration. Otherwise, your migration fails. For more information, see the Migrating from Cisco IOS to Cisco IOS XR Software on the Cisco XR 12000 Series Router document.
Minimum Firmware Requirement
•
Depending on the type of firmware that needs upgrading the symptoms can vary as follows:
–
–
–
–
Note
RMA Card Firmware Upgrade Procedure
To upgrade the fabric-downloader, ROMMON, Mbus, and current field-programmable device (FPD) image package on a single RMA linecard or on all modules installed in a router, use the upgrade all command in administration EXEC mode.
upgrade all location {node-id | all} [force]
Where location node-id specifies that all all firmware images (ROM, MBUS, Fabric Downloader and FPD) will be upgraded on the physical location of the line card received through RMA defined by the node-id argument. The node-id argument is entered in the rack/slot/module notation.
The upgrade all location all command upgrades all all firmware images (ROM, MBUS, Fabric Downloader and FPD) on all line cards (LCs) that are installed in the router.
For an RMA linecard firmware upgrade you'll want to use the upgrade all location node-id command.
The optional force parameter skips the version check and forces an upgrade.
•
http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/XR12000SoftwareFirmwareCompatibilityMatrix.pdf
•
http://www.cisco.com/web/Cisco_IOS_XR_Software/index.html
Here's the link to the Cisco Systems IOS XR Firmware Upgrade Guide For CRS-1 and XR12000:
http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/IOSXRFirmwareUpgradeGuide.pdf
•
•
RP/0/10/CPU0:MSE-PE1(admin)#show fpd packageMon Sep 27 08:48:43.012 PDT=============================== ================================================Field Programmable Device Package================================================SW Min Req Min ReqCard Type FPD Description Type Subtype Version SW Ver HW Vers==================== ========================== ==== ======= =========== ======== =======E3-OC12-ATM-4 Mickey FPGA lc fpga2 40971.00 0.0 0.0IOB FPGA lc fpga3 41091.00 0.0 0.0SAF 0 FPGA lc fpga4 45586.00 0.0 0.0Mouse FPGA lc fpga1 40977.00 0.0 0.0------------------------------------------------------------------------------------------E3-OC3-ATM-4 Mickey FPGA lc fpga2 40971.00 0.0 0.0IOB FPGA lc fpga3 41091.00 0.0 0.0SAF 0 FPGA lc fpga4 45586.00 0.0 0.0Mouse FPGA lc fpga1 40977.00 0.0 0.0------------------------------------------------------------------------------------------12000-ServEngCard TREX FPGA lc fpga2 162.45 0.0 0.0TREX FPGA lc fpga1 0.41257 0.0 0.0------------------------------------------------------------------------------------------12000-SIP HABANERO FPGA lc fpga2 240.03 0.0 0.0JALAPENO FPGA lc fpga5 240.13 0.0 0.0JALAPENO FPGA lc fpga5 240.13 0.0 0.0JALAPENO FPGA lc fpga1 255.23 0.0 0.0------------------------------------------------------------------------------------------E3-OC12-CH-1 Shiver FPGA lc fpga1 1.01 0.0 0.0------------------------------------------------------------------------------------------SPA-IPSEC-2G Sequoia spa fpga2 1.01 0.0 1.0Lodi spa fpga1 1.22 0.0 1.0SPA PROM spa rommon 1.01 0.0 1.0------------------------------------------------------------------------------------------SPA-4XT3/E3 SPA E3 Subrate FPGA spa fpga2 1.04 0.0 0.0SPA T3 Subrate FPGA spa fpga3 1.04 0.0 0.0SPA I/O FPGA spa fpga1 1.01 0.0 0.0SPA ROMMON spa rommon 2.12 0.0 0.0------------------------------------------------------------------------------------------SPA-2XT3/E3 SPA E3 Subrate FPGA spa fpga2 1.04 0.0 0.0SPA T3 Subrate FPGA spa fpga3 1.04 0.0 0.0SPA I/O FPGA spa fpga1 1.01 0.0 0.0SPA ROMMON spa rommon 2.12 0.0 0.0------------------------------------------------------------------------------------------SPA-4XCT3/DS0 SPA T3 Subrate FPGA spa fpga2 0.11 0.0 0.100SPA T3 Subrate FPGA spa fpga2 1.04 0.0 0.200SPA I/O FPGA spa fpga1 2.08 0.0 0.100SPA ROMMON spa rommon 2.12 0.0 0.100------------------------------------------------------------------------------------------SPA-2XCT3/DS0 SPA T3 Subrate FPGA spa fpga2 0.11 0.0 0.100SPA T3 Subrate FPGA spa fpga2 1.04 0.0 0.200SPA I/O FPGA spa fpga1 2.08 0.0 0.100SPA ROMMON spa rommon 2.12 0.0 0.100------------------------------------------------------------------------------------------SPA-1XCHSTM1/OC3 SPA T3 Subrate FPGA spa fpga2 1.04 0.0 0.0SPA I/O FPGA spa fpga1 1.08 0.0 0.0SPA ROMMON spa rommon 2.12 0.0 0.0------------------------------------------------------------------------------------------SPA-2CHT3-CE-ATM SPA T3 Subrate FPGA spa fpga2 1.10 0.0 1.0SPA I/O FPGA spa fpga1 2.22 0.0 1.0SPA ROMMON spa rommon 1.04 0.0 1.0------------------------------------------------------------------------------------------SPA-IPSEC-2G-2 Sequoia spa fpga2 1.01 0.0 1.0Lodi spa fpga1 1.22 0.0 1.0SPA PROM spa rommon 1.01 0.0 1.0------------------------------------------------------------------------------------------SPA-1XCHOC48/DS3 SPA I/O FPGA spa fpga2 1.00 0.0 0.49SPA I/O FPGA spa fpga3 1.00 0.0 0.52SPA I/O FPGA spa fpga1 1.36 0.0 0.49SPA ROMMON spa rommon 2.02 0.0 0.49------------------------------------------------------------------------------------------SPA-1XCHOC12/DS0 SPA I/O FPGA spa fpga2 1.00 0.0 0.49SPA I/O FPGA spa fpga1 1.36 0.0 0.49SPA ROMMON spa rommon 2.02 0.0 0.49------------------------------------------------------------------------------------------SPA-OC192POS SPA FPGA swv1.2 spa fpga1 1.02 0.0 0.0------------------------------------------------------------------------------------------SPA-8XOC12-POS SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.5------------------------------------------------------------------------------------------SPA-8XCHT1/E1 SPA I/O FPGA spa fpga1 2.08 0.0 0.0SPA ROMMON spa rommon 2.12 0.0 0.140------------------------------------------------------------------------------------------SPA-OC192POS-XFP SPA FPGA swv1.2 spa fpga1 1.02 0.0 0.0SPA FPGA swv1.2 hwv2 spa fpga1 1.02 0.0 2.0------------------------------------------------------------------------------------------SPA-10X1GE SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-5X1GE SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-2XOC48POS/RPR SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.0------------------------------------------------------------------------------------------SPA-1XTENGE-XFP SPA FPGA swv1.9 spa fpga1 1.09 0.0 0.0------------------------------------------------------------------------------------------SPA-8X1FE SPA FPGA swv1.1 spa fpga1 1.01 0.0 0.0------------------------------------------------------------------------------------------SPA-1XOC48POS/RPR SPA FPGA swv1.2 spa fpga1 1.02 0.0 0.0------------------------------------------------------------------------------------------SPA-8XOC3-POS SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.5------------------------------------------------------------------------------------------SPA-2XOC12-POS SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.5------------------------------------------------------------------------------------------SPA-4XOC12-POS SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.5------------------------------------------------------------------------------------------SPA-10X1GE-V2 SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-8X1GE-V2 SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-5X1GE-V2 SPA FPGA swv1.10 spa fpga1 1.10 0.0 0.0------------------------------------------------------------------------------------------SPA-2X1GE-V2 SPA FPGA swv1.1 spa fpga1 1.01 0.0 0.0------------------------------------------------------------------------------------------SPA-1X10GE-L-V2 SPA FPGA swv1.11 spa fpga1 1.11 0.0 0.0------------------------------------------------------------------------------------------SPA-8X1FE-V2 SPA FPGA swv1.1 spa fpga1 1.01 0.0 0.0------------------------------------------------------------------------------------------SPA-4XOC3-POS-V2 SPA FPGA swv1.0 spa fpga1 1.00 0.0 0.5------------------------------------------------------------------------------------------SPA-1XOC3-ATM-V2 TATM SPA IOFPGA spa fpga1 1.04 0.0 0.0------------------------------------------------------------------------------------------SPA-2XOC3-ATM-V2 SPA TATM IOFPGA spa fpga1 1.04 0.0 0.0------------------------------------------------------------------------------------------SPA-3XOC3-ATM-V2 SPA TATM IOFPGA spa fpga1 1.04 0.0 0.0------------------------------------------------------------------------------------------SPA-1XOC12-ATM-V2 SPA TATM IOFPGA spa fpga1 1.04 0.0 0.0------------------------------------------------------------------------------------------Determining Your Software Version
To determine the version of Cisco IOS XR software running on your router, log into the router and enter the show version command:
Step 1
Step 2
RP/0/7/CPU0:ios#sh versionSat Sep 25 14:26:18.305 UTCCisco IOS XR Software, Version 3.9.2[00]Copyright (c) 2010 by Cisco Systems, Inc.ROM: ROMMON System Bootstrap, Version 1.4(0), RELEASE SOFTWAREios uptime is 7 hours, 30 minutesSystem image file is "disk0:c12k-os-mbi-3.9.2/mbiprp-rp.vm"cisco 12816/PRP (8641D) processor with 4194304K bytes of memory.8641D processor at 1330Mhz, Revision 2.111 Cisco 12000 Series SPA Interface Processor-601/501/4012 Cisco 12000 Series Performance Route Processor 3s1 Cisco 12000 Series Performance Route Processor4 Management Ethernet44 PLIM_QOS3 TenGigE20 GigabitEthernet/IEEE 802.3 interface(s)15 SONET/SDH6 Packet over SONET/SDH5 MgmtMultilink8 FastEthernetRP/0/7/CPU0:ios#show install active summumarySat Sep 25 14:26:33.561 UTCActive Packages:disk0:c12k-doc-3.9.2disk0:c12k-fpd-3.9.2disk0:c12k-diags-3.9.2disk0:c12k-k9sec-3.9.2disk0:c12k-mgbl-3.9.2disk0:c12k-mcast-3.9.2disk0:c12k-mpls-3.9.2disk0:c12k-mini-3.9.2
New Features in Cisco IOS XR Software Release 3.9.2
PBTS Default Class Enhancement
Policy Based Tunnel Selection (PBTS) directs traffic into TE tunnels based on incoming packets TOS/EXP bits.
•
•
•
•
•
•
•
•
•
Restrictions
The class 0 tunnel is no longer the default tunnel. There is a new default class which does not associate with any of existing classes 0 to 7. For a class of traffic that does not have a respective class tunnel to serve it, the forwarding plane will use the available default tunnels and IGP/LDP paths to carry that class of traffic.
The new behavior takes effective only when the control plan resolves a prefix to use at least one default tunnel to forward traffic. In case a prefix is resolved to not use any default tunnel to forward traffic, it will fall back to the existing behavior. The lowest class tunnels will be used to serve as default tunnels. The class 0 tunnels will be used as default tunnels if no default tunnel is configured. In this case, we provide the backward compatibility to customers who keep using the existing configurations.
Configuration
Command to configure policy-class for PBTS
RP/0/RP1/CPU0:#configureRP/0/RP1/CPU0:(config)#interface tunnel-te 18RP/0/RP1/CPU0:(config-if)#policy-class ?<1-7> Tunnel policy class<default> Default tunnel policy classRP/0/RP1/CPU0:(config-if)#policy-class defaultRP/0/RP1/CPU0:(config-if)#commitConfiguration example with PBTS enabled
RP/0/RP1/CPU0:(config)#interface tunnel-te 280RP/0/RP1/CPU0:(config)#policy-class defaultFor more information about Policy Based Tunnel Selection, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 docs:
Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9
and IOS XR MPLS Configuration Guide
Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.
policy-class
To configure policy-based tunnel selection (PBTS) to direct traffic into specific TE tunnels, use the policy-class command in interface configuration mode. To disable this feature, use the no form of this command.
policy-class [<1-7> <default>]
no policy-class
Syntax Description
1-7
Policy-class attribute to map the correct traffic class to this policy.
default
(Optional) Default tunnel policy class.
Defaults
The lowest class tunnels will be assigned to carry default traffic only if no default tunnel is available for forwarding.
Command Modes
CONFIG-IF
Command History
Release 3.9.2
New parameter "default" added to the CLI for defining the default tunnel on the Cisco XR 12000 Series Router
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Use the policy-class command to enable policy-based tunnel selection (PBTS). See Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router for more information on PBTS.
To display the configured PBTS policy-class value, use the show mpls traffic-eng tunnels command.
To display information about PBTS configuration, use the show cef and show cef hardware commands.
Task ID
Examples
The following is an example of how to configure a default policy-class tunnel.
RP/0/5/CPU0:PE22_C12406(config-if)#policy-class ?<1-7> Tunnel policy classdefault Default class for policy-based tunnel selection<cr>RP/0/5/CPU0:PE22_C12406(config-if)#policy-class defaultRP/0/5/CPU0:PE22_C12406(config-if)#showTue Jul 27 20:29:04.850 DSTinterface tunnel-te2206policy-class defaultRelated Commands
Hitless DS-TE Migration
The IETF DS-TE migration is hitless, which means the DS-TE mode is changed to IETF, when the TE does not flap tunnels when the class type is set to 0. The priority value matches the TE-class index (for example, TE-class map 5 is set to class-type 0 and priority 5) for all TE-class maps.
•
•
•
•
•
•
For DS-TE to function properly, DS-TE modes must be configured identically on all MPLS-TE nodes.
If you need to change the DS-TE mode, you must bring down all tunnel interfaces and, after the change, you should flood the updated bandwidth values through the network.
Note
For more information about DS-TE Migration, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 docs:
Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9
and IOS XR MPLS Configuration Guide
Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.
Unequal Bandwidth for Link Bundles
Link Bundling is one of the mechanisms to increase available link bandwidth without hardware upgrading. A link bundle interface is a group of physical interfaces of the same media type which are aggregated together such that they are treated as a single link by high layer protocols and features.
Traffic sent to the bundle is distributed among the member links and collected again at the far end
Current Link Bundling implementation supports having all members in the link bundle of equal bandwidth. This Unequal Bandwidth for Link Bundles provides the ability to configure member links of different weights in a Link Bundle but only if the weight ratio amongst the members is 4:1.
Currently, all the interfaces in a Link Bundle need to have same bandwidth characteristic. This means an OC-3 POS link can be part of a bundle which is either having 0 or more OC-3 links but it cannot be part of bundle with either OC-12 or OC-48 links. Unequal bandwidth on LB will enable this by allowing links with different bandwidth characteristics to be part of the same bundle. This feature will allow 4:1 ratio in bandwidth characteristic of participating links in the same bundle, which means
•
•
•
•
•
•
•
Hardware Limitations:
•
•
•
Configuration:
No new CLI is introduced with this feature.
MPLS TE Auto-Bandwidth with Link Bundles
Automatic Bandwidth adjustment for TE Tunnels feature provides the means to automatically adjust the bandwidth allocation for traffic engineering tunnels based on their measured traffic load. The configured bandwidth in the running configuration is changed due to the automatic bandwidth behavior.
If a number of consecutive bandwidth samples are greater than the underflow threshold (bandwidth percentage) and the minimum bandwidth configured, then a bandwidth application is updated immediately; instead of waiting for the end of the application period.
Prerequisites
Your network must support the following:
•
•
•
•
Restrictions
The automatic bandwidth adjustment feature treats each tunnel for which it has been enabled independently. That is, it adjusts the bandwidth for each such tunnel according to the adjustment frequency configured for the tunnel and the sampled output rate for the tunnel since the last adjustment without regard for any adjustments previously made or pending for other tunnels.
If a tunnel is brought down to calculate a new label switched path (LSP) because the LSP is not operational, the configured bandwidth is not saved. If the router is reloaded, the last saved automatic bandwidth value is used.
You cannot configure MPLS TE over the logical generic routing encapsulation (GRE) tunnel interface.
For more information about MPLS-TE Auto-Bandwidth, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 document,
Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9
and IOS XR MPLS Configuration Guide
Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.
auto-bw underflow
To configure the auto-bw underflow on a tunnel interface, use the auto-bw command to enter the MPLS-TE automatic bandwidth interface configuration mode. To disable the automatic bandwidth on that tunnel, use the no form of this command.
auto-bw underflow threshold <1-100> min <10-4294967295> limit <1-10>
no auto-bw
Syntax Description
Defaults
By default, automatic bandwidth is not enabled.
Command Modes
CONFIG-IF
Command History
Release 3.9.2
New parameter "underflow" added to the CLI for defining auto-bw on the Cisco XR 12000 Series Router
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Use the auto-bw command to enter MPLS-TE automatic bandwidth interface configuration mode.
The auto-bw and load-share unequal commands should not be used together.
The load-share unequal command determines the load-share for a tunnel based on the bandwidth. However, the MPLS-TE automatic bandwidth feature changes the bandwidth. If you are configuring both the load-share unequal command and the MPLS-TE automatic bandwidth feature, we recommend that you specify an explicit load-share value configuration under each MPLS-TE automatic bandwidth tunnel.
The following automatic bandwidth scenarios are described:
•
•
•
Note
Task ID
Examples
The following example shows how to configure MPLS-TE automatic bandwidth underflow:
RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflowthreshold Set the bandwidth change percent to trigger an underflowRP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold<1-100> Bandwidth change percent to trigger an underflowRP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10limit Set the number of consecutive collections exceeding thresholdmin Set the bandwidth change value to trigger an underflowRP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min<10-4294967295> Bandwidth change value to trigger an underflow (kbps)RP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 100limit Set the number of consecutive collections exceeding thresholdRP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 100 limit<1-10> Number of consecutive collections exceeding thresholdRP/0/5/CPU0:PE22_C12406(config-if)#auto-bw underflow threshold 10 min 100 limit 10<cr>RP/0/5/CPU0:PE22_C12406(config-if)#showWed Jul 28 14:58:27.957 DSTinterface tunnel-te2066auto-bwunderflow threshold 10 min 100 limit 10Related Commands
show mpls traffic-eng tunnels auto-bw
To display auto bandwidth information about MPLS-TE tunnels, use the show mpls traffic-eng tunnels auto-bw command in EXEC mode.
show mpls traffic-eng tunnels auto-bw
Syntax Description
This command has no arguments or keywords.
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.9.2
New "underflow threshold" parameter added to the CLI output to display underflow bandwidth statistics on the Cisco XR 12000 Series Router
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following shows a sample output from the show mpls traffic-eng tunnels auto-bw command specifying the tunnel number in brief form:
RP/0/5/CPU0:PE22_C12406#show mpls traffic-eng tunnels auto-bwThu Jul 29 18:25:08.627 DSTSignalling Summary:LSP Tunnels Process: runningRSVP Process: runningForwarding: enabledPeriodic reoptimization: every 3600 seconds, next in 1438 secondsPeriodic FRR Promotion: every 300 seconds, next in 167 secondsAuto-bw enabled tunnels: 1Name: tunnel-te2206 Destination: 10.6.6.6Status:Admin: up Oper: up Path: valid Signalling: connectedpath option 1, type dynamic (Basis for Setup, path weight 3)Last Signalled Error: Wed Jul 28 03:01:33 2010Info: [22] PathErr(2,5)-(Admin, flow preempted) at 10.12.12.1G-PID: 0x0800 (derived from egress interface properties)Bandwidth Requested: 0 kbps CT0Config Parameters:Bandwidth: 25000 kbps (CT0) Priority: 0 0 Affinity: 0x0/0xffffMetric Type: TE (default)AutoRoute: enabled LockDown: disabled Policy class: not setForwarding-Adjacency: disabledLoadshare: 0 equal loadsharesAuto-bw: enabledLast BW Applied: 0 kbps CT0 BW Applications: 1Last Application Trigger: Underflow ConditionBandwidth Min/Max: 0-4294967295 kbpsApplication Frequency: 1440 min Jitter: 0s Time Left: 22h 36m 12sCollection Frequency: 5 minSamples Collected: 17 Next: 3m 52sHighest BW: 0 kbps Underflow BW: 0 kbpsAdjustment Threshold: 10% 10 kbpsOverflow Detection disabledUnderflow Threshold: 10% 100 kbps Limit: 0/10 Underflow BW Applications: 1Fast Reroute: Enabled, Protection Desired: AnyPath Protection: Not EnabledHistory:Tunnel has been up for: 1d15h (since Wed Jul 28 03:01:33 DST 2010)Current LSP:Uptime: 01:41:09 (since Thu Jul 29 16:44:00 DST 2010)Reopt. LSP:Last Failure:LSP not signalled, identical to the [CURRENT] LSPDate/Time: Thu Jul 29 16:49:07 DST 2010 [01:36:02 ago]Prior LSP:ID: path option 1 [59]Removal Trigger: reoptimization completedPath info (OSPF 100 area 0):Hop0: 10.222.4.2Hop1: 10.12.12.2Hop2: 10.12.12.1Hop3: 10.16.8.1Hop4: 10.16.8.6Hop5: 10.6.6.6Displayed 1 (of 2) heads, 0 (of 0) midpoints, 0 (of 0) tailsDisplayed 1 up, 0 down, 0 recovering, 0 recovered headsRelated Commands
Bundle Interface Re-size Triggers Immediate Preemption and RSVP
For bundle interfaces, TE delays 60 secs before reacting to link capacity bandwidth reduction updates.
When enabling RSVP with 'bandwidth' on a bundle interface (75%), an individual member link failure will take 60 seconds for the router to realize the member is gone and resize the interface bandwidth.
When member links of a bundle fail successively leading to insufficient RSVP bandwidth on the bundle, tunnels are not immediately preempted. TE control waits for 60 seconds (default) for more member failures that may trigger FRR before preempting any tunnel. The link management preemption delay parameter allows the customer to configure the amount of time that tunnels stay in service before being preempted due to insuffiecient RSVP bandwidth on a bundle.
For more information about Bundle Interfaces, refer to the Cisco IOS XR MPLS Command Reference Release 3.9 documents:
Cisco IOS XR MPLS Command Reference for the Cisco XR 12000 Series Router, Release 3.9
and IOS XR MPLS Configuration Guide
Cisco IOS XR MPLS Configuration Guide for the Cisco XR 12000 Series Router, Release 3.9.
mpls traffic-eng link-management timers preemption-delay
To configure the preemption-delay on a tunnel interface, enter MPLS-TE mpls traffic-eng interface configuration mode and use the mpls traffic-eng link-management preemption-delay command. To disable the preemption-delay on that tunnel, use the no form of this command.
mpls traffic-eng link-management timers [preemption-delay bundle-capacity <1-300> ] [bandwith-hold <1-300>] [periodic-flooding <0-3600>]
Syntax Description
Defaults
There is no default value for this command.
Command Modes
CONFIG-IF
Command History
Release 3.9.2
Added new parameter, preemption, to the CLI for defining link management timers on the Cisco XR 12000 Series Router
Usage Guidelines
To use this command, you must be in a user group associated with a task group that includes the proper task IDs. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Task ID
Examples
The following example shows how to configure the preemption delay timer.
RP/0/5/CPU0:(config)#mpls traffic-eng link-management timers
RP/0/5/CPU0:(config)#$mpls traffic-eng link-management timers preemption
RP/0/5/CPU0:(config)#$mpls traffic-eng link-management timers preemption bundle-capacity
RP/0/5/CPU0:(config)#$mpls traffic-eng link-management timers preemption bundle-capacity 1
New Features in Cisco IOS XR Software Release 3.9.1
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.9.1:
•
•
•
Note
New Software Features Supported on all Platforms
The following new software features in Cisco IOS XR Software Release 3.9.1 are supported on all platforms:
•
•
Cisco XR 12000 Series Router-Specific Software Features
The following new software feature was introduced in Cisco IOS XR Software Release 3.9.1 on the Cisco XR 12000 Series Router platform:
•
New Hardware Features for the Cisco XR 12000 Series Router
No new hardware features were introduced in Cisco IOS XR Software Release 3.9.1 on the Cisco XR 12000 Series Router.
For detailed information on the shared port adapters (SPAs) and SPA interface processors (SIPs), see the following documents:
•
•
Note
Important Notes
•
•
Configuration prior to Cisco IOS XR Software Release 3.6.0:
Policy-map wred_exampleClass class-defaultrandom-detect exp 0 384 packets 484 packetsrandom-detect exp 1 384 packets 484 packetsrandom-detect exp 2 384 packets 484 packetsrandom-detect exp 3 484 packets 584 packetsrandom-detect exp 4 484 packets 584 packetsrandom-detect discard-class 0 384 packets 484 packetsrandom-detect discard-class 1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth remaining percent 20Cisco 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 1 percent bandwidth made available to it. This can be done either by assigning at least 1 percent explicitly (bandwidth remaining percent 1) or by ensuring that the total bandwidth assigned to all other classes in the policy is a maximum of 99 percent, leaving 1 percent available for the class-default. A QoS policy that does not have any bandwidth for class-default is rejected when upgrading to Cisco IOS XR Software Release 3.6.0 or later releases.
•
•
•
•
•
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 90If 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
•
•
•
•
Minimum Flash Disk Requirements When Upgrading to Release 3.9.2
Cisco IOS XR Software Release 3.9.2 requires a 2-GB Flash Disk as a minimum. If your Cisco XR 12000 Series Router currently uses a 1-GB Flash Disk, you must upgrade it to 2-GB before upgrading to Cisco IOS XR Software Release 3.9.1. The PCMCIA 1-GB Flash Disk was the default size for the Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.6 and earlier.
In Cisco IOS XR Software Release 3.6 and later releases, disk partitioning is supported. Partitioning of a 2-GB disk is possible but not required. Partitioning of a 4-GB disk is required.
A 4-GB Flash Disk can be installed instead of the 2-GB for greater disk storage.
To upgrade from a 1-GB flash disk to a 2-GB or greater flash disk, refer to the Flash Disk Upgrade Tasks link on the followingCisco XR 12000 Series Router Installation and Upgrade URL:
http://www.cisco.com/en/US/products/ps6342/prod_installation_guides_list.html
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious caveats; severity-2 caveats are less serious.
This section contains Release 3.9.2 and Release 3.9.1 caveats that are generic to the Cisco IOS XR software and those specific to the Cisco XR 12000 Series Router.
Resolved Release 3.9.2 Cisco IOS XR Software Caveats
•
Basic Description:
BGP flaps due to unknown attribute
Symptom:
Cisco IOS XR Software contains a vulnerability in the Border Gateway Protocol (BGP) feature. The vulnerability manifests itself when a BGP peer announces a prefix with a specific, valid but unrecognized transitive attribute. On receipt of this prefix, the Cisco IOS XR device will corrupt the attribute before sending it to the neighboring devices. Neighboring devices that receive this corrupted update may reset the BGP peering session.
Conditions:
Affected devices running Cisco IOS XR Software corrupt the unrecognized attribute before sending to neighboring devices, but neighboring devices may be running operating systems other than Cisco IOS XR Software and may still reset the BGP peering session after receiving the corrupted update. This is per standards defining the operation of BGP.
Workaround:
No workaround. Cisco developed a fix that addresses this vulnerability and will be releasing free software maintenance upgrades (SMUs) progressively starting 28 August 2010.
A Security Advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20100827-bgp.shtml
Open Release 3.9.2 Cisco IOS XR Software Caveats
The following open caveats apply to Cisco IOS XR software Release 3.9.2 and are not platform specific:
•
Basic Description:
CLI command not authorized to execute during persist time of EEM policy
Symptom:
After persist time start for eem policy user, CLI command failed to authorize.
Conditions:
When the TACACS server is down, persist time starts for the user credentials which registered for EEM policy. If the EEM policy gets triggered and opens a vty connection and try to execute any CLI while the TACACS server is down, it failed to authorize that command.
Workaround:
None.
Recovery:
Bring the TACACS server up.
•
Basic Description:
CLI over XML Configuration Fails
Symptom:
CLI over XML configuration request fails.
Conditions:
This happens when
- CLI command lines in XML request exceeds 200 lines or more
AND
- CLI commands are split internally and it happens to be split in middle of sub-mode.
Workaround:
- No need to use CLI over XML for config commands that already support XML natively.
- Split the commands into multiple requests so that command lines of each request are less than 200 lines.
Recovery:
None.
•
Basic Description:
lpts_pa tracebacks after clear cef on line card
Symptom:
An error log is printed along with the traceback when a message send to BCDL agent fails.
Conditions:
The BCDL agent has gone down thus the message send is failing. This is a very rare scenario and would not happen under normal circumstances.
Workaround:
Not required, as BCDL will come up eventually.
Further Problem Description:
The error message is just to say that BCDL agent might have gone down. This would not cause an error in lpts as BDCL will eventually come up and the messages are sent again. The only caveat is that it might be some time before the messages are sent again. The solution would aim to put an upper bound on the resend time by having a retrying mechanism for the same.
•
Basic Description:
Standby RP not ready - ospf Waiting for primary node
Symptom:
The trigger for this issue is standby node is coming up and somebody trying to do some configuration from the active.
Conditions:
The consequence is that the new configuration might be lost and the impact would be depending on the new configuration. e.g., if the new configuration is to spawn new osfp, then those new ospf will not be spawned.
Workaround:
The workaround is to re-apply the new configuration once the standby is up completely.
Recovery:
None.
•
Basic Description:
sysdb busy, timeouts after rack OIR of rack with DRP pair
Symptom:
Lots of processes (admin plane) complain that the registrations/get/bind operations are timing out. The next thing to notice is the Pending MsgCount which indicates the servers inability to process incoming messages. This triggers a snmp issue as snmp doesn't handles the error core related to sysdb registration properly.
# gsp_show -c 395 (jid of sysdb_svr_admin)Group messages received by client id 8, process pid:127038(pkg/bin/sysdb_svr_admin)28 Max Thresh 10000 Red High 9500Flow Zone 0 Pending MsgCount 0Pending Bytes 0 High MsgCount 0High Bytes 0 Total Bytes 0Max MsgSize 0 Msgs Delivered 0Msgs Dropped 0Lwg(s)Conditions:
This issue occurs on a multi chassis system upon an OIR.
Workaround:
None.
Recovery:
Restarting sysdb_svr_admin on the active+standby DSC nodes (not simultaneously though) will help recover the issue.
•
Basic Description:
Admin Plane config loss upon Turboboot
Symptom:
Admin config loss upon Turboboot, user have to create new root user name and password in order to log into the router.
Conditions:
Impact might be that for MC, all other racks may not be able to boot until new admin config re-applied.
Workaround:
Just re-apply the admin configuration saved before the turbo boot.
Recovery:
None
•
Basic Description:
Install operation failed due to insufficient disk space on SP cards
Symptom:
Upgrade or install rollback may fail accompanied with "insufficient disk space on SPs" error messages like the following example.
Example:Error: Cannot proceed with the rollback operation because there isError: insufficient disk space on the following devices:Error: - 0/0/SP: bootflash: (5932652 bytes required, 3522772 bytesError: available)Error: - 0/1/SP: bootflash: (5932652 bytes required, 3512316 bytesError: available)Error: - 0/2/SP: bootflash: (5932652 bytes required, 3506976 bytesError: available)Error: - 0/3/SP: bootflash: (5932652 bytes required, 3519248 bytesError: available)Error: - 0/4/SP: bootflash: (5932652 bytes required, 3502804 bytesError: available)Error: - 0/5/SP: bootflash: (5932652 bytes required, 3529776 bytesError: available)Conditions:
This problem is triggered by switching to a release where the new version id is a substring of the old version id. This will only occur when upgrading from a test version with a test version suffix (ex: 3.9.2.22i) to a release version with no suffix (3.9.2).
1.
Example: Upgrading from 3.9.2.22i to 3.9.2.2.
Workaround: Use turboboot instead of a PIE upgrade if the above conditions apply.
Recovery:
Use turboboot to run the new image
•
Basic Description:
Wildcard does not work on activating inactive pies
Symptom:
When attempting to activate packages using wild cards, certain packages are not being found which prevents the activation from taking place.
Conditions:
When a activation to a new release (3.9.2) is attempted from 3.7.3 while using wild cards to specify the packages instead of specifying them explicitly by name.
Workaround:
Instead of using wild cards, explicitly name each package to be activated.
Recovery:
None
•
Basic Description:
Optional task-maps not downloaded as part of exec authorization & Service exec tasks received from the TACACS server are not processed during AAA authorization
Symptom:
Command authorization fails:
RP/0/RP0/CPU0:router#show int desc% This command is not authorizedRP/0/RP0/CPU0:router#Conditions:
This happens:
–
–
–
The problem with this bug is that the service exec tasks received from the tacacs server are not processed during aaa authorization with tacacs. So the user ends up with no task on the router and no command is authorized. Even though the command is permitted on the tacacs server.
Workaround:
Instead of using wild cards, explicitly name each package to be activated.
Recovery:
The way to make tacacs authorization work in 3.9.2 or 4.0.0 is through a privilege level:
–
–
–
usergroup priv13taskgroup root-systemtaskgroup cisco-supportOpen Release 3.9.2 Caveats Specific to the Cisco XR 12000 Series Router
The following open caveats are specific to the Cisco XR 12000 Series Router:
•
Basic Description:
Entity goes missing after RP Failover on the 16 slot c12000
Symptom:
Some subentities in the Entity-MIB go missing after RP FO. This condition occurs intermittently on a 16 slot GSR chassis.
Conditions:
On an RP failover on the 16 slot C12000 chassis, there is an intermittent condition in which subentities go missing.
Workaround:
None.
Recovery:
A forced failover or restart of the invmgr process should resolve the condition.
•
Basic Description:
FIB_MGR Traceback while removing OSPF process & re-adding OSPF process
Symptom:
FIB_MGR Traceback while removing and re-adding OSPF process in scaled setup.
Conditions:
Removing and re-adding OSPF process in the same commit.
Workaround:
The issue is not seen when some time gap (~3-5 sec) is given between removing and re-adding OSPF process.
•
Basic Description:
multilink MTU size is not pushed to member links
Symptom:
On a multilink bundle, when MTU is changed under the bundle interface, the value should be automatically pushed to all member links but this does not happen.
Conditions:
This applies to changing the MTU value of multilink bundles.
Workaround:
Set the MTU on all member links before adding to the bundle. Set the bundle MTU properly at creation time.
Recovery:
All member links need to be removed from bundle and then change their their MTU and finally set the MTU on the bundle itself. This will be service impacting.
•
Basic Description:
Dampening penalty increased after "no shut" on bundle-pos member
Symptom:
Dampening penalty seems to increase after a "no shut" is issued on the SONET controller on Eng 3 POS linecard.
Conditions:
No shut on Sonet Controller
Workaround:
No workaround.
Recovery:
None
•
Basic Description:
Convergence values not consistent on bundle member shut on E3 & E5 LCs
Symptom:
Traffic loss during bundle member removal. The impact will be higher if a Service policy is applied to the bundle interface. The impact is occurring due to reprogramming of Bundle adjacency in Rx Engine and Tx Engine and when QoS Policy is applied, then TCAM entry modification is also required to take care of bandwidth modification.
Conditions:
A link bundle with traffic flowing over it
Workaround:
None.
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
Troubleshooting
For information on troubleshooting Cisco IOS XR software, refer to the Cisco IOS XR Troubleshooting Guide for the Cisco XR 12000 Series Router and the Cisco IOS XR Getting Started Guide for the Cisco XR 12000 Series Router.
Related Documentation
The most current Cisco XR 12000 Series Router hardware documentation is located at the following URL:
http://www.cisco.com/en/US/products/ps6342/prod_installation_guides_list.html
The Cisco IOS XR software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. See About Cisco IOS XR Software Documentation for Release 3.9 for a list of Cisco IOS XR Release 3.9.1 software documentation.
The most current Cisco XR 12000 Series Router software documentation is located at the following URL:
http://www.cisco.com/en/US/products/ps6342/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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at 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. (1005R)
© 2010 Cisco Systems, Inc. All rights reserved.
