 Feedback
|
Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.8.2
Key Changes from Previous Releases in Cisco IOS XR Release 3.8.2
Minimum and Preferred Cisco IOS Image and Boot Helper Levels for Migration
Determining Your Software Version
New Software Features in Cisco IOS XR Software Release 3.8.2
New Software Features Supported on All Platforms
Cisco CRS-1 Router-Specific Software Features
Cisco XR 12000 Series Router-Specific Software Features
New Hardware Features for Cisco IOS XR Software Release 3.8.2
Cisco CRS-1 Router-Specific Hardware Features
Cisco XR 12000 Series Router-Specific Hardware Features
Minimum Flash Disk Requirements When Upgrading to Release 3.8.2
Caveats Specific to the Cisco CRS-1 Router
Caveats Specific to the Cisco XR 12000 Series Router
Resolved Cisco IOS XR Software PSIRT-Related Caveats
Upgrading Cisco IOS XR Software
Product Life Cycle of Cisco IOS XR Software Release 3.8.2
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IOS XR Software Release 3.8.2
April 9, 2013
Cisco IOS XR Software Release 3.8.2
Text Part Number OL-20796-04
These release notes describe the features provided in the Cisco IOS XR Software Release 3.8.2 and are updated as needed.
Note
For information about Cisco IOS XR Software Release 3.8.2, see the "Important Notes" section.
You can find the most current Cisco IOS XR software documentation on the World Wide Web at: http://www.cisco.com/en/US/partner/products/ps5845/tsd_products_support_series_home.html
These electronic documents may contain updates and modifications. For more information on obtaining Cisco documentation, see the "Obtaining Documentation and Submitting a Service Request" section on page 45.
For a list of software caveats that apply to Cisco IOS XR Software Release 3.8.2, see the "Caveats" section. The caveats are updated for every release and are described 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
Key Changes from Previous Releases in Cisco IOS XR Release 3.8.2
Cisco IOS XR Software Release 3.8.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.8.2. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.8.2" section.
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.8.2, see the "New Software Features in Cisco IOS XR Software Release 3.8.2" section in this document.
System Requirements
Cisco IOS XR Software Release 3.8.2 supports the following platforms:
To determine the software versions or levels of your current system, see the "Determining Your Software Version" section.
Cisco CRS-1 Router
This section describes the system requirements for Cisco IOS XR Software Release 3.8.2 supported on the Cisco CRS-1 router platform. The system requirements include the following information:
To determine the software versions or levels of your current system, see Determining Your Software Version.
Feature Set Table
Cisco IOS XR software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco IOS XR Software Release 3.8.2 features. Table 1 lists the Cisco IOS XR software feature set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 3.8 supported on the Cisco CRS-1.
Table 1 Cisco CRS-1 Supported Feature Sets
(Cisco IOS XR Software Release 3.8.2 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.8.2
Contains the required core packages, including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.vm-3.8.2
Contains the required core packages including OS, Admin, Base, Forwarding, Modular Services Card, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
hfr-mgbl-p.pie-3.8.2
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.8.2
MPLS-TE4 , LDP5 , MPLS Forwarding, MPLS OAM6 , LMP7 , OUNI8 , RSVP9 , and Layer 2 VPN and Layer 3 VPN.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.8.2
Multicast Routing Protocols (PIM, MSDP10 , IGMP11 , Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB12 , MURIB13 , MFWD14 ), and BIDIR-PIM15 .
Cisco IOS XR Security Package
hfr-k9sec-p.pie-3.8.2
Support for Encryption, Decryption, IPSec16 , SSH17 , SSL18 , and PKI19 (Software based IPSec support—maximum of 500 tunnels)
Cisco IOS XR Documentation Package
hfr-doc.pie-3.8.2
Man pages for Cisco IOS XR CLI commands
Cisco IOS XR FPD Package
hfr-fpd.pie-3.8.2
Firmware for Fixed PLIM20 and SPA21 modules as well as ROMMON22 images for Cisco CRS-1 chassis.
Cisco IOS XR Diagnostic Package
hfr-diags-p.pie-3.8.2
Diagnostic utilities for Cisco IOS XR routers.
1 Packages installed individually
2 CORBA = Common Object Request Broker Architecture
3 Extensible Markup Language
4 MPLS Traffic Engineering
5 Label Distribution Protocol
6 Operations, Administration, and Maintenance
7 Link Manager Protocol
8 Optical User Network Interface
9 Resource Reservation Protocol
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Multicast Routing Information Base
13 Multicast-Unicast RIB
14 Multicast forwarding
15 Bidirectional Protocol Independent Multicast
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Public-key infrastructure
20 Physical layer interface module
21 Shared port adapters
22 ROM monitor
Table 2 lists the Cisco CRS-1 TAR files.
Memory Requirements
Caution
The minimum memory requirements for Cisco CRS-1 running Cisco IOS XR Software Release 3.8.2 consist of the following:
•
•
•
Note
Hardware Supported
All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
The following table lists the supported hardware components on the Cisco CRS-1 and the minimum required software versions. For more information, see the "Other Firmware Support" section.
Software Compatibility
Cisco IOS XR Software Release 3.8.2 is compatible with the following Cisco CRS-1 systems:
•
•
•
•
Other Firmware Support
The Cisco CRS-1 router supports the following firmware code:
•
For information about upgrading the ROMMON, see http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/rommon/configuration/guide/rm38.html
•
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.8.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 "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.8.2 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.8.2, supported on the Cisco XR 12000 Series Router.
Table 4 Cisco XR 12000 Series Router Supported Feature Set (Cisco IOS XR Software
Release 3.8.2 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.8.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.8.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.8.2
CORBA2 agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.8.2
MPLS-TE3 , LDP 4 , MPLS Forwarding, MPLS OAM5 , LMP6 , OUNI7 , and RSVP8 .
Cisco IOS XR Multicast Package
c12k-mcast.pie-3.8.2
Multicast Routing Protocols (PIM9 ,MSDP10 , IGMP11 , Auto-RP, BSR12 ), Tools (SAP, MTrace, MRINFO), and Infrastructure (MRIB13 , MURIB14 , MFWD15 ).
Cisco IOS XR Security Package
c12k-k9sec.pie-3.8.2
Support for Encryption, Decryption, IPSec16 , SSH17 , SSL18 , and PKI19 .
Software based IPSec support: maximum of 500 tunnels or Hardware based IPSec: maximum of 64K tunnels using the SPA-IPSEC-2G-2Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.8.2
Support for booting the Standby RP on a Cisco XR 12000 Series Router.
Cisco IOS XR Service IPsec Controller Package
c12k-ipsec-service.pie-3.8.2
Support for service-ipsec and service-gre interfaces in Cisco IOS XR software.
Cisco IOS XR Firewall Package
c12k-firewall.pie-3.8.2
Support for Virtual Firewall (VFW) on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.8.2
Man pages for Cisco IOS XR CLI commands.
Cisco IOS XR FPD Package
c12k-fpd.pie-3.8.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.8.2
Diagnostic utilities for Cisco IOS XR routers.
1 Packages installed individually
2 CORBA = 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.8.2 consist of the following:
•
Note
•
•
•
•
•
–
•
–
Note
•
Note
Hardware Supported
Cisco IOS XR Software Release 3.8.2 supports the Cisco XR 12000 Series Router. All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 6 lists the 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.8.2 is compatible with the following Cisco XR 12000 Series Router systems:
•
•
•
•
•
•
•
•
•
•
The following chassis are supported for an existing installed base:
•
•
•
Note
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.8.2:
•
However, the recommended Cisco IOS image level to support migration to Release 3.8.2 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.8.2.
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
•
http://www.cisco.com/en/US/docs/ios_xr_sw/iosxr_r3.8/system_management/command/reference/yr38hw.html
Determining Your Software Version
To determine the version of Cisco IOS XR software running on your router, log into the router and enter the show version command:
Step 1
Step 2
Cisco CRS-1
On the Cisco CRS-1, you should see a response similar to the following (which has been abbreviated for the Release Notes):
RP/0/RP0/CPU0:MPLS-PE5# show versionThu Oct 29 10:14:26.269 PSTCisco IOS XR Software, Version 3.8.2[00]Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.53(20090311:225342) [CRS-1 ROMMON],MPLS-MR-LR1-6 uptime is 1 hour, 2 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.8.2/mbihfr-rp.vm"cisco CRS-16/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.22 Management Ethernet21 SONET/SDH21 Packet over SONET/SDH8 TenGigE8 GigabitEthernet4 T34 Serial network interface(s)1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.2053440k bytes of disk0: (Sector size 512 bytes).Cisco XR 12000 Series Router
On the Cisco XR 12000 Series Router, you should see a response similar to the following (which has been abbreviated for the Release Notes):
RP/0/0/CPU0:PE6_C12406# show versionWed Oct 28 16:44:58.425 PSTCisco IOS XR Software, Version 3.8.2[00]Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 12.0(20090226:235859) [rtauro-sw30346-33S 1.23dev(0.35)] DEVELOPMENT SOFTWARECopyright (c) 1994-2009 by cisco Systems, Inc.P2_UUT uptime is 54 minutesSystem image file is "disk0:c12k-os-mbi-3.8.2/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)6 Management Ethernet14 PLIM_QOS11 SONET/SDH3 Packet over SONET/SDH18 GigabitEthernet/IEEE 802.3 interface(s)2 T38 FastEthernet10 Asynchronous Transfer Mode2 TenGigE1017k bytes of non-volatile configuration memory.2053376k bytes of disk0: (Sector size 512 bytes).2053376k bytes of disk1: (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.8.2[00], Cisco Systems, at disk0:c12k-fpd-3.8.2Built on Wed Oct 28 05:29:41 PST 2009By edde-bld1 in /auto/srcarchive3/production/3.8.2/c12k/workspace for c4.2.1-p0
New Software Features in Cisco IOS XR Software Release 3.8.2
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.8.2:
•
•
•
New Software Features Supported on All Platforms
The following new software feature in Cisco IOS XR Software Release 3.8.2 is supported on both the Cisco CRS-1 and the Cisco XR 12000 Series Router:
Note
Multicast Only Fast Reroute
Multicast only fast reroute (MoFRR) is a video feature that supports redundancy.
Two copies of the same multicast stream flow through disjoint paths in the network. At the point in the network where the two streams merge, one of the streams is accepted and forwarded on the downstream links, while the other stream is discarded.
MoFRR is triggered when a failure is detected on the primary path. MoFRR transmits a multicast join from a receiver towards a source on a primary path and then transmits a secondary multicast join message from the receiver towards the source on a backup path. Data packets are received from the primary and secondary paths, with the redundant packets being discarded at topology merge points based on reverse-path forwarding (RPF) checks.
When a failure is detected on the primary path, the repair occurs by changing the interface on which packets are accepted to the secondary interface. This redundancy improves the convergence times in the event of a node or link failure on the primary path.
Note
MoFRR switchover occurs at the software level based on routing information base (RIB) convergence. RIB events are used as triggers for a switchover.
Multipath and non-multipath modes support MoFRR. Better convergence time is achieved in multipath mode because of the load-balancing of traffic streams across different paths.
MoFRR supports equal cost multipath (ECMP) topologies, IPv4 and IPv6, and XML.
The flow monitoring metric may be used to trigger other network events like rerouting of multicast flows for fast convergence.
Prerequisites
Before you configure MoFRR, ensure that you have set up a multicast network. For information regarding configuring your network for multicast, refer to Cisco IOS XR Multicast Configuration Guide, Release 3.8.
Configuring MoFRR
This section describes how to configure MoFRR based on RIB convergence.
SUMMARY STEPS
1.
2.
3.
4.
DETAILED STEPS
Cisco CRS-1 Router-Specific Software Features
No new Cisco CRS-1 platform-specific features were added in Cisco IOS XR Software Release 3.8.2.
Cisco IOS XR Software Release 3.8.2 includes support for prefix-length notation for ACLs on the Cisco CRS-1 platform.
The following example shows how to define an access list named Internetfilter with prefix-length notation:
RP/0/RSP0/CPU0:router(config)# ipv4 access-list Internetfilter10 permit ipv4 12.10.10.1/24 any20 permit ipv4 125.10.10.1/16 any30 permit ipv4 135.10.10.1/27 any40 permit ipv4 135.200.10.1/24 any50 permit ipv4 any anyCisco XR 12000 Series Router-Specific Software Features
No new Cisco XR 12000 Series Router platform-specific features were added in Cisco IOS XR Software Release 3.8.2.
New Hardware Features for Cisco IOS XR Software Release 3.8.2
The following new hardware features were introduced in Cisco IOS XR Software Release 3.8.2:
•
•
Cisco CRS-1 Router-Specific Hardware Features
The following new features in Cisco IOS XR Software Release 3.8.2 are supported on the Cisco CRS-1 platform:
•
•
•
•
•
CRS-FP40 Licenses
The following licenses apply to the CRS-FP40 on a per slot basis:
•
•
•
For GRE and L2TPv3, this license applies to the line card required to enable GRE and/or L2TPv3 encapsulation.
Restrictions
•
•
•
•
•
QoS Restrictions
•
•
Table 9 Chassis and Line Card Compatibility Matrix
Multichassis, CRS-16/S
4 port 10GE LAN (4-10GE)
42-1GE
20-1GE-FLEX
2-10 GE-WL-FLEX
All existing CRS-1 PLIM/SIP800CRS-MSC-40G-B
CRS-8/S, CRS-4/S
4 port 10GE LAN (4-10GE)
42-1GE
20-1GE-FLEX
2-10 GE-WL-FLECRS-FP401 or CRS-MSC-40G-B
All existing CRS-1 PLIM/SIP800
CRS-MSC-40G-B
1 CRS-FP40 is supported only in 4/8 slot chassis and can be only paired with new PLIMs. New PLIMs can be paired with the CRS-FP40 and CRS-MSC-40G-B.
Table 10 SPA Support for FLEX PLIMs
20-1GE-FLEX
2-10 GE-WL-FLEXPOS
SPA-4XOC3-POS
SPA-8XOC12-POS (Multi-rate1 )
SPA-2XOC48POS/RPR
SPA-4XOC48POS/RPR
SPA-OC192POS-VSR
SPA-OC192POS-XFP
Ethernet
SPA-1X10GE-L-V2
SPA-1X10GE-WL-V2
SPA-10X1GE-V2
SPA-8X1GE
SPA-8X1GE-V2
SPA-5X1GE-V2
1 Multi-rate: SPA-8XOC12-POS can support SFP-OC12-x and SFP-OC3-x.
Cisco XR 12000 Series Router-Specific Hardware Features
The following new features in Cisco IOS XR Software Release 3.8.2 are supported on the Cisco XR 12000 Series Router platform:
•
–
–
•
•
–
–
Note
New Commands
This section contains the new multicast commands that are introduced in Cisco IOS XR Software Release 3.8.2. These commands are supported on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
router pim global maximum
To configure a global or per process maximum route-interface limit for Protocol Independent Multicast (PIM), use the router pim global maximum command.
router pim global maximum {register-states | route-interfaces | routes} threshold
Syntax Descriptionr
Defaults
If this limit is not configured, the following default values apply:
•
•
•
Command Modes
Global configuration
Command History
Release 3.8.2
This command was introduced on the Cisco CRS-1 and 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. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS-XR Software module of the Cisco IOS-XR System Security Configuration Guide.
Task ID
Examples
The following example shows how to enter the maximum number of 5000 PIM interfaces on all routes for all VRF instances:
RP/0/RP0/CPU0:router#configureRP/0/RP0/CPU0:router(config)router pim global maximum route-interfaces 5000RP/0/RP0/CPU0:router(config)commitRP/0/RP0/CPU0:router(config)endshow mrib route
To display all entries in the Multicast Routing Information Base (MRIB), use the show mrib route command in EXEC mode.
show mrib [vrf vrf-name] [ipv4 | ipv6] [old-output] route [summary| [[outgoing-interface] [* | source-address] [group-address [/prefix-length]]] [detail]
Syntax Description
Defaults
IPv4 addressing is the default.
Command Modes
EXEC
Command History
Release 3.8.2
This command was introduced on the Cisco CRS-1 and 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.
Each line card has an individual Multicast Forwarding Information Base (MFIB) table. The MFIB table maintains a subset of entries and flags updated from MRIB. The flags determine the forwarding and signaling behavior according to a set of forwarding rules for multicast packets. In addition to the list of interfaces and flags, each route entry shows various counters. Byte count is the number of total bytes forwarded. Packet count is the number of packets received for this entry.
The show mfib counter command displays global counters independent of the routes.
Task ID
Examples
The following is sample output from the show mrib route command (the output fields are described in the header):
RP/0/RP0/CPU0:router# show mrib routeIP Multicast Routing Information BaseEntry flags: L - Domain-Local Source, E - External Source to the Domain,C - Directly-Connected Check, S - Signal, IA - Inherit Accept,IF - Inherit From, D - Drop, MA - MDT Address, ME - MDT Encap,MD - MDT Decap, MT - MDT Threshold Crossed, MH - MDT interface handleCD - Conditional DecapInterface flags: F - Forward, A - Accept, IC - Internal Copy,NS - Negate Signal, DP - Don't Preserve, SP - Signal Present,II - Internal Interest, ID - Internal Disinterest, LI - Local Interest,LD - Local Disinterest, DI - Decapsulation InterfaceEI - Encapsulation Interface, MI - MDT Interface(*,224.0.0.0/4) RPF nbr: 10.11.1.20 Flags: L COutgoing Interface ListDecapstunnel0 Flags: NS(*,224.0.0.0/24) Flags: D(*,224.0.1.39) Flags: S(*,224.0.1.40) Flags: SOutgoing Interface ListPOS0/3/0/0 Flags: II LI(*,238.1.1.1) RPF nbr: 10.11.1.20 Flags: COutgoing Interface ListPOS0/3/0/0 Flags: F NS LIDecapstunnel0 Flags: A(*,239.1.1.1) RPF nbr: 10.11.1.20 Flags: COutgoing Interface ListPOS0/3/0/0 Flags: F NSDecapstunnel0 Flags: AThe following example shows the output when the vrf and detail keywords are used:
RP/0/RP0/CPU0:router# show mrib vrf vrf1 route detailIP Multicast Routing Information BaseEntry flags: L - Domain-Local Source, E - External Source to the Domain,C - Directly-Connected Check, S - Signal, IA - Inherit Accept,IF - Inherit From, D - Drop, MA - MDT Address, ME - MDT Encap,MD - MDT Decap, MT - MDT Threshold Crossed, MH - MDT interface handleCD - Conditional Decap, MPLS - MPLS Decap, MF - MPLS Encap, EX - ExtranetInterface flags: F - Forward, A - Accept, IC - Internal Copy,NS - Negate Signal, DP - Don't Preserve, SP - Signal Present,II - Internal Interest, ID - Internal Disinterest, LI - Local Interest,LD - Local Disinterest, DI - Decapsulation InterfaceEI - Encapsulation Interface, MI - MDT Interface, LVIF - MPLS Encap,EX - Extranet(*,0.0.0.101) Ver: 0x818 Flags: MA, FMA: 0x0MDT Address: 5.5.5.5Up: 6d01h(*,0.0.0.102) Ver: 0x5337 Flags: MA, FMA: 0x0MDT Address: 225.101.1.1Up: 6d01h(*,0.0.0.103) Ver: 0x6cea Flags: ML, FMA: 0x0Master Linecard Slot: 0/3/CPU0Up: 6d01h(*,0.0.0.104) Ver: 0x7ca Flags: MBH, FMA: 0x0BGP IFH: 0x9000180Up: 6d01h(*,0.0.0.105) Ver: 0x5b67 Flags: MLF, FMA: 0x0Master Linecard Fallback Slot: 0/3/CPU0Up: 6d01h(*,0.0.0.107) Ver: 0x382c Flags: MDT_IFH, FMA: 0x0Up: 6d01hMDT IFH: 0x9043d80...The following example shows the detailed output for a source VRF route in a receiver on the source PE router in an MVPN extranet topology) with the core multicast distribution tree (MDT) ID of the receiver VRF displayed:
RP/0/RP0/CPU0:router# show mrib vrf vrf15 route 18.18.15.2 225.0.0.1 detailIP Multicast Routing Information BaseEntry flags: L - Domain-Local Source, E - External Source to the Domain,C - Directly-Connected Check, S - Signal, IA - Inherit Accept,IF - Inherit From, D - Drop, MA - MDT Address, ME - MDT Encap,MD - MDT Decap, MT - MDT Threshold Crossed, MH - MDT interface handleCD - Conditional Decap, MPLS - MPLS Decap, MF - MPLS Encap, EX - ExtranetInterface flags: F - Forward, A - Accept, IC - Internal Copy,NS - Negate Signal, DP - Don't Preserve, SP - Signal Present,II - Internal Interest, ID - Internal Disinterest, LI - Local Interest,LD - Local Disinterest, DI - Decapsulation InterfaceEI - Encapsulation Interface, MI - MDT Interface, LVIF - MPLS Encap,EX - ExtranetRelated Commands
Modified Commands
This section contains the multicast commands that were modified in Cisco IOS XR Software Release 3.8.2. These commands are supported on the Cisco CRS-1 and the Cisco XR 12000 Series Router.
show pim summary
To display configured Protocol Independent Multicast (PIM) out-of-resource (OOR) limits and current counts, use the show pim summary command in EXEC mode.
show pim [global | vrf vrf-name] [ipv4 | ipv6] summary
Syntax Description
Defaults
IPv4 addressing is the default. If no VRF is specified, the default VRF is operational.
Command Modes
EXEC
Command History
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. For detailed information about user groups and task IDs, refer to the Configuring AAA Services on Cisco IOS-XR Software module of the Cisco IOS-XR System Security Configuration Guide.
The show pim summary command is used to identify configured OOR information for the PIM protocol, such as number of current and maximum routes.
Task ID
Examples
The following example shows the PIM summary for vrf-1:
RP/0/RP0/CPU0:router# show pim vrf vrf-1 summaryThu Jun 4 07:18:37.290 UTCPIM Summary for VRF:vrf-1Current Maximum Warning-thresholdRoutes 20001 100000 100000Routes x Interfaces 20001 300000 300000SM Registers 0 20000 20000Group Ranges from AutoRP 0 100Table 11 describes the significant fields shown in the display.
Important Notes
•
pw-class class1 encapsulation mpls control-word•
•
Configuration prior to Cisco IOS XR Software Release 3.6.0:
Policy-map wred_exampleClass class-defaultrandom-detect exp 0 384 packets 484 packetsrandom-detect exp 1 384 packets 484 packetsrandom-detect exp 2 384 packets 484 packetsrandom-detect exp 3 484 packets 584 packetsrandom-detect exp 4 484 packets 584 packetsrandom-detect discard-class 0 384 packets 484 packetsrandom-detect discard-class 1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth remaining percent 20!!Cisco IOS XR Software Release 3.6.0 and later releases:
policy-map wred_exampleclass class-defaultrandom-detect exp 0,1,2 384 packets 484 packetsrandom-detect exp 3,4 484 packets 584 packetsrandom-detect discard-class 0,1 384 packets 484 packetsrandom-detect discard-class 2 484 packets 584 packetsbandwidth remaining percent 20!end-policy-map!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
•
•
•
•
•
•
•
–
–
show l2tp session sequence
show l2vpn forwarding detail - This command does not show the sequence number for L2VPNs.
show l2tp session detail - The sequence numbers are not displayed.
clear l2vpn forwarding table
–
show controllers atm <> traffic vc <>—This command prints the CID.
show hw-module subslot <> memory sar cid <>—Use the CID obtained in the previous command.
•
•
•
Due to this change, when downgrading from Cisco IOS XR Release 3.8.2 to earlier releases, the multicast-routing and router pim MVPN (VRF) configurations are rejected. This failure is shown in the output of the show configuration failed startup command.
Multicast-routing and router pim MVPN (VRF) configurations need to be corrected and reapplied manually. Since a downgrade is typically done following an upgrade, save a copy of the older-release running-configuration before doing the upgrade.
In Cisco IOS XR Release 3.8.2, the following multicast routing configurations are on separate lines:
multicast-routingvrf vrf1address-family ipv4interface all enable!!!To correct the multicast-routing configurations, the vrf <> and address-family <> lines should be combined into the same line as shown in the following example:
multicast-routingvrf vrf1 address-family ipv4interface all enable!In Cisco IOS XR Release 3.8.2, the following router pim configurations are on separate lines:
router pimvrf vrf1address-family ipv4interface Loopback0!!!To correct the router pim configurations, the vrf <> and address-family <> lines should be combined into the same line as the router pim shown in the following example:
router pim vrf vrf1 address-family ipv4interface Loopback0!!•
–
–
–
–
•
LDP session hold time <= (Hello hold time - Hello interval) * 3
This means that for default values of 15/5 seconds respectively for the link Hello hold time and the Hello interval, the LDP session hold time should be set to 30 seconds or less.
For more information, refer to the "Implementing MPLS Label Distribution Protocol on Cisco IOS XR Software" section of the Cisco IOS XR MPLS Configuration Guide, Release 3.8.2.
Minimum Flash Disk Requirements When Upgrading to Release 3.8.2
Cisco IOS XR Software Release 3.8.2 requires a 2-GB flash disk as a minimum, so if your Cisco CRS-1 or 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.8.2.
The PCMCIA 1-GB flash disk was the default size for the Cisco CRS-1 running Cisco IOS XR Software Release 3.6 and earlier and for the Cisco XR 12000 Series Router running Cisco IOS XR Software Release 3.5 and earlier.
A 4-GB flash disk is available for both platforms and can be installed instead of the 2-GB for greater disk storage for Cisco IOS XR Software Release 3.4 and later.
To upgrade from a 1-GB flash disk to a 2-GB or greater flash disk, refer to the Cisco XR12000 and CRS-1 Flash Disk Upgrade Tasks document at: http://www.cisco.com/en/US/docs/routers/xr12000/xr_line_cards/flashdisk/flashdisk.pdf
Additional upgrade instructions for the Cisco CRS-1 router are available from: http://www.cisco.com/web/Cisco_IOS_XR_Software/pdf/ReplacingPCMCIACardOnCRS-1.pdf
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious.
The following caveats are open for Cisco IOS XR Software Release 3.8.2 on the router platforms indicated:
•
•
Cisco IOS XR Caveats
The following caveats apply to both platforms:
•
Basic Description:
devc_conaux crash—multiple triggers.
Symptom:
Under specific circumstances, the Devc-conaux process could crash and automatically restart. Sessions on the console or auxiliary port are terminated as a result.
Note
Conditions:
This issue may occur during the following scenarios:
1.
2.
Workaround:
Avoid the use of this break sequence on the active or standby route processor console or auxiliary port.
•
Basic Description:
FR subinterface counters are taken from the engine, while main interface counters are taken from the SPA. This can result in a mismatch of counters at the sub interface and main interface levels.
Symptom:
o/p of show interface main interface and show interface sub interface may not match. Total sub interface counts (for all sub interfaces under the main interface) may be larger on the side or smaller on the ingress side.
Conditions:
This mismatch is seen between FR sub interface and main interface counts. Mismatch occurs when the packet rate becomes more than what the queuing ASIC can handle. This results in a queuing ASIC drop and a difference in the main interface and sub interface counts.
Workaround:
No workaround is available (recommended). This is an expected behavior.
•
Basic Description:
Some processes not reoptimized are router reload.
Symptom:
If a router reloads, upon bootup, some processes may not be placed on the same nodes as they were before the reload. This is due to timing variations in the bootup sequence of the various nodes (cards).
Conditions:
This issue occurs during a router reload.
Workaround:
None.
Recovery:
Use the placement reoptimize command, which places processes on their optimal cards.
•
Basic Description:
Field diag on an LC with SPA-IPSEC-2G-2 SPA goes into Field Diag timeout.
Symptom:
Field diag is declared as failed and the card goes into Field Diag timeout state on an LC with a SPA-IPSEC-2G-2 SPA.
Conditions:
This behavior is observed when one of the SPAs is a SPA-IPSEC-2G-2 SPA. The total test time for the SPA-IPSEC-2G-2 SPAs is more than the current field diags timeout value. Even though all the tests pass, as the total test time exceeds the timeout the field diags reports a timeout.
Workaround:
None. When this is observed on a setup, if none of the actual tests have reported any failures, this issue can be safely ignored and the hardware under test can be considered to be good.
Recovery:
The card that went into "FDIAG TIMEOUT" state has to be reloaded to get it back to the normal state. Issue the following command:
hw-module location <R/S/I> reload
•
Basic Description:
Pie deactivation failed with one of the Rack1 RP not ready.
Symptom:
Software package activation and deactivation fail because a node is not ready.
RP/0/RP1/CPU0:CRS(admin)#install deactivate disk0:hfr-mpls-3.8.2 synchronousInstall operation 14 '(admin) install deactivate disk0:hfr-mpls-3.8.2synchronous' started by user 'lab' via CLI.Error: Cannot proceed with the deactivation because the following node isnot ready:Error: 1/RP1/CPU0Error: Suggested steps to resolve this:Error: - repeat the operation after waiting for a while.Install operation 14 failedConditions:
After a node reload (as part of LR uncarving), the insthelper process on the affected RP does not complete its initialization correctly. Install operations fail subsequently.
Workaround:
None.
Recovery:
Reloading the failing node.
•
Basic Description:
Not able to modify RPL and delete prefix-set in a single commit.
Symptom:
When a policy that is attached directly or indirectly to an attach point needs to be modified, a single commit operation cannot be performed when:
–
–
Workaround:
The commit must be performed in two steps:
1.
2.
Caveats Specific to the Cisco CRS-1 Router
The following caveats are specific to the Cisco CRS-1 platform:
•
Basic Description:
Verifier call back not getting called on configuration.
Symptom:
The system accepts an invalid SNMP MIB configuration.
Conditions:
When an SNMP MIB configuration is committed with invalid information, the system is accepts it, rather than rejecting it. Such configuration does not have any adverse effect to the system, but shows up in the running configuration. This issue is only in Cisco IOS XR Release 3.8 and subsequest Release 3.8 maintenance releases.
Workaround:
Upon committing a MIB configuration with invalid information, the system generates a syslog indicating the nature of problem.
Recovery:
Remove the invalid configuration and reapply with valid information.
Further Problem Description:
A configuration verification step which is supposed to verify the validity of MIB configuration does not function correctly, and proceeds to apply the configuration. This results in system accepting an invalid MIB configuration.
•
Basic Description:
The FabricMulticast ping health monitoring diagnostic test on a Cisco CRS-1 multi-chassis system does not reliably report which specific fabric plane or planes are at fault when the test indicates a failure. Failure detection is accurate. The FabricMulticast ping health monitoring diagnostic test is reliable in identifying the affected plane or plane when performed on a Cisco CRS-1 single chassis system.
Symptom:
FabricMulticast ping health monitoring diagnostic test does not identify the affected plane or planes.
Conditions:
This issue occurs when running the FabricMulticast ping health monitoring diagnostic test on a Cisco CRS-1 multi-chassis system and a fault is detected.
Workaround:
There is no known workaround.
Recovery:
Please contact your technical representative for technical support.
Caveats Specific to the Cisco XR 12000 Series Router
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
Basic Description:
show run with "/controller T1" shows T1''s out of order, not contiguous.
Symptom:
RP/0/0/CPU0:router#show runBuilding configuration...!! Last configuration change at Tue Jun 19 16:18:58 2007 by lab!....controller T1 0/1/0/0/0/0channel-group 0timeslots 1-24!!controller T1 0/1/0/0/1/0channel-group 0timeslots 1-24!!controller T1 0/1/0/0/2/0channel-group 0timeslots 1-24!!controller T1 0/1/0/0/0/1 /* This controller instace not in order */channel-group 0timeslots 1-24!Conditions:
The only issue is with showing the controller slots in sorted order. There is no other impact.
Workaround:
None.
•
Basic Description:
E5 LC clock is disrupted during boot.
Symptom:
Doing periodic show clock sync from RP during the Engine 5 boot reveals that when the LC becomes IOX-RUN, its clock is drifted by few seconds compared to the RP clock. The clock syncs and becomes accurate without user intervention 5-10 minutes after boot.
Conditions:
This issue is specific to Engine 5 and is not seen on Engine 3.
Workaround:
None.
•
Basic Description:
Bundle ether members flap on process restart netio on E5.
Symptom:
LACP protocol flaps and links are detached and then reattached to their bundles when NetIO on the linecard where the links are located is restarted. A message such as one of the following is seen:
RP/0/7/CPU0:Aug 11 02:59:54.030 : BM-DISTRIB[133]: %L2-BM-6-DISTRIBUTING : GigabitEthernet0/0/0/9 is no longer in Distributing state as part of Bundle-Ether14000 (Link is in InSync state)Or
RP/0/7/CPU0:Aug 11 02:59:54.030 : BM-DISTRIB[133]: %L2-BM-6-DISTRIBUTING : GigabitEthernet0/0/0/9 is no longer in Distributing state as part of Bundle-Ether14000 (Link is marked individual by partner)Conditions:
Links are running LACP using the short period (lacp period short) in one or both directions. The NetIO process is restarted on the card where the links are present.
Workaround:
Configure LACP on both connected devices to be running using the default long period (no lacp period short) before restarting NetIO.
•
Basic Description:
XBMA interrupts not getting reported to CPU and no action
Symptom:
XBMA interrupts not getting reported to CPU and no action
Conditions:
XBMA error interrupts can occur because of the following reasons:
1.
2.
Such errors do not get notified to the CPU, leading to a silent failure within XBMA ASICS.
Workaround:
None.
Resolved Cisco IOS XR Software PSIRT-Related 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.shtm
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
Product Life Cycle of Cisco IOS XR Software Release 3.8.2
The Cisco IOS XR Software release strategy is time-based with a fixed release date and life cycle, as opposed to being a feature-based release strategy with a variable release date.
Table 12 lists the major milestones of Cisco IOS XR Software Release 3.8.2.
Note
For official End-of-Life and End-of-Sale announcements for Cisco IOS XR software, please visit: http://www.cisco.com/en/US/products/ps5845/prod_eol_notices_list.html or contact your local account representative.
Troubleshooting
For information on troubleshooting Cisco IOS XR software, see Cisco IOS XR Getting Started Guide and Cisco IOS XR Troubleshooting Guide.
Related Documentation
Hardware Documents
You can find the most current hardware documentation at the following URLs:
Cisco CRS-1 Router:
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
Cisco XR 12000 Series Router:
http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html
Software Documents
The Cisco IOS XR software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. See About Cisco IOS XR Software Documentation for Release 3.8 for a list of Cisco IOS XR Release 3.8.2 software documentation.
You can find the most current software documentation for the Cisco CRS-1 and Cisco XR 12000 Series Router at the following URL:
http://www.cisco.com/en/US/products/ps5845/tsd_products_support_series_home.html
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Obtaining Documentation and Submitting a Service Request
For information on obtaining documentation, submitting a service request, and gathering additional information, see What's New in Cisco Product Documentation at: http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html.
Subscribe to What's New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
© 2010 Cisco Systems, Inc. All rights reserved.
