Table Of Contents
Release Notes for Cisco IOS XR Software Release 3.8.1
Key Changes from Previous Releases in Cisco IOS XR Release 3.8.1
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.1
New Software Features Supported on All Platforms
LACP Short Period Time Intervals
Cisco CRS-1 Router-Specific Software Features
Enhanced Process Distribution to Improve Load-Balancing Across Cisco CRS-1 RPs
Cisco XR 12000 Series Router-Specific Software Features
ATM Support for Layer 2 Tunnel Protocol Version 3 on Engine-5 Line Cards
New Hardware Features for Cisco IOS XR Software Release 3.8.1
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.1
Caveats Specific to the Cisco CRS-1 Router
Caveats Specific to the Cisco XR 12000 Series Router
Upgrading Cisco IOS XR Software
Product Life Cycle of Cisco IOS XR Software Release 3.8.1
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco IOS XR Software Release 3.8.1
November 23, 2009
Cisco IOS XR Software Release 3.8.1
Text Part Number OL-19620-02
These release notes describe the features provided in the Cisco IOS XR Software Release 3.8.1 and are updated as needed.
Note
For information about Cisco IOS XR Software Release 3.8.1, 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 25.
For a list of software caveats that apply to Cisco IOS XR Software Release 3.8.1, 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.1
Cisco IOS XR Software Release 3.8.1 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.1. For more information, see the "Minimum Flash Disk Requirements When Upgrading to Release 3.8.1" 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.1, see the "New Software Features in Cisco IOS XR Software Release 3.8.1" section in this document.
System Requirements
Cisco IOS XR Software Release 3.8.1 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
This section describes the system requirements for Cisco IOS XR Software Release 3.8.1 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.1 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.1 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
comp-hfr-mini.pie-3.8.1
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.1
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.1
Cisco IOS XR MPLS Package
hfr-mpls-p.pie-3.8.1
MPLS-TE,4 LDP,5 MPLS Forwarding, MPLS OAM,6 LMP,7 OUNI,8 RSVP,9 and Layer-2 VPN and Layer-3 VPN.
Cisco IOS XR Multicast Package
hfr-mcast-p.pie-3.8.1
Multicast Routing Protocols (PIM, MSDP,10 IGMP,11 Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB,12 MURIB13 , MFWD14 ), and BIDIR-PIM.15
Cisco IOS XR Security Package
hfr-k9sec-p.pie-3.8.1
Support for Encryption, Decryption, IPSec,16 SSH,17 SSL,18 and PKI19 (Software based IPSec support—maximum of 500 tunnels)
Cisco IOS XR Documentation Package
hfr-doc.pie-3.8.1
Man pages for Cisco IOS XR CLI commands
Cisco IOS XR FPD Package
hfr-fpd.pie-3.8.1
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.1
Diagnostic utilities for Cisco IOS XR routers.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 Extensible Markup Language
4 MPLS Traffic Engineering
5 Label Distribution Protocol
6 Operations, Administration, and Maintenance
7 Link Manager Protocol
8 Optical User Network Interface
9 Resource Reservation Protocol
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Multicast Routing Information Base
13 Multicast-Unicast RIB
14 Multicast forwarding
15 Bidirectional Protocol Independent Multicast
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Public-key infrastructure
20 Physical layer interface module
21 Shared port adapters
22 ROM monitor
Table 2 lists the Cisco CRS-1 TAR files.
Memory Requirements
Caution
The minimum memory requirements for Cisco CRS-1 running Cisco IOS XR Software Release 3.8.1 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.1 is compatible with the following Cisco CRS-1 systems:
•
•
•
•
Other Firmware Support
The Cisco CRS-1 router supports the following firmware code:
•
•
Cisco XR 12000 Series Router
This section describes the system requirements for Cisco IOS XR Software Release 3.8.1 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.1 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.1, 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.1 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
c12k-mini.pie-3.8.1
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.1
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.1
CORBA2 agent, XML Parser, and HTTP server packages.
Cisco IOS XR MPLS Package
c12k-mpls.pie-3.8.1
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.8.1
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.8.1
Support for Encryption, Decryption, IPSec16 , SSH,17 SSL,18 and PKI.19
Software based IPSec support: maximum of 500 tunnels or Hardware based IPSec: maximum of 64K tunnels using the SPA-IPSEC-2G-2Cisco IOS XR Standby RP Boot Image
mbiprp-rp.vm-3.8.1
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.1
Support for service-ipsec and service-gre interfaces in Cisco IOS XR software.
Cisco IOS XR Firewall Package
c12k-firewall.pie-3.8.1
Support for Virtual Firewall (vFW) on a Cisco XR 12000 Series Router.
Cisco IOS XR Documentation Package
c12k-doc.pie-3.8.1
Man pages for Cisco IOS XR CLI commands.
Cisco IOS XR FPD Package
c12k-fpd.pie-3.8.1
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.1
Diagnostic utilities for Cisco IOS XR routers.
1 Packages are installed individually
2 Common Object Request Broker Architecture
3 MPLS Traffic Engineering
4 Label Distribution Protocol
5 Operations, Administration, and Maintenance
6 Link Manager Protocol
7 Optical User Network Interface
8 Resource Reservation Protocol
9 Protocol Independent Multicast
10 Multicast Source Discovery Protocol
11 Internet Group Management Protocol
12 Bootstrap router
13 Multicast Routing Information Base
14 Multicast-Unicast RIB
15 Multicast forwarding
16 IP Security
17 Secure Shell
18 Secure Socket Layer
19 Physical layer interface module
Table 5 lists the Cisco XR 12000 Series Router TAR files.
Memory Requirements
Caution
The minimum memory requirements for Cisco XR 12000 Series Routers running Cisco IOS XR Software Release 3.8.1 consist of the following:
•
Note
•
•
•
•
•
–
•
–
Note
•
Note
Hardware Supported
Cisco IOS XR Software Release 3.8.1 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.1 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.1:
•
However, the recommended Cisco IOS image level to support migration to Release 3.8.1 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.1.
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 Jul 30 14:27:41.521 PSTCisco IOS XR Software, Version 3.8.1[00]Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.53(20090311:225342) [CRS-1 ROMMON],MPLS-PE5 uptime is 11 hours, 48 minutesSystem image file is "bootflash:disk0/hfr-os-mbi-3.8.1/mbihfr-rp.vm"cisco CRS-16/S (7457) processor with 4194304K bytes of memory.7457 processor at 1197Mhz, Revision 1.22 Management Ethernet5 TenGigE29 SONET/SDH28 Packet over SONET/SDH1 WANPHY controller(s)8 GigabitEthernet1 Asynchronous Transfer Mode1019k bytes of non-volatile configuration memory.38079M bytes of hard disk.2052832k bytes of disk0: (Sector size 512 bytes).Boot device on node 0/0/CPU0 is bootflash:Package active on node 0/0/CPU0:hfr-fpd, V 3.8.1[00], Cisco Systems, at disk0:hfr-fpd-3.8.1Built on Wed Jul 29 03:41:40 PST 2009By edde-bld1 in /auto/srcarchive3/production/3.8.1/hfr/workspace for c4.2.1-p0...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 versionRP/0/10/CPU0:PE1-E5#sh ver Thu Jul 30 21:30:25.653 UTCCisco IOS XR Software, Version 3.8.1[00] Copyright (c) 2009 by Cisco Systems, Inc.ROM: ROMMON System Bootstrap, Version 1.0(0), RELEASE SOFTWAREPE1-E5 uptime is 2 hours, 38 minutes System image file is "disk0:c12k-os-mbi-3.8.1/mbiprp-rp.vm"cisco 12416/PRP (8641D) processor with 4194304K bytes of memory. 8641D processor at 1330Mhz, Revision 2.18 Cisco 12000 Series SPA Interface Processor-601/501/401 2 Cisco 12000 Series Performance Route Processor 3s 4 Management Ethernet 32 PLIM_QOS 8 MgmtMultilink 10 SONET/SDH 124 T3 200 Multilink network interface(s) 596 T1 2690 Serial network interface(s) 2 Packet over SONET/SDH 7 Serial network interface(s) 4 E3 21 E1 15 GigabitEthernet/IEEE 802.3 interface(s) 2 TenGigE 895k bytes of non-volatile configuration memory. 1947M bytes of compact flash card. 76170M bytes of hard disk. 1993912k bytes of disk0: (Sector size 512 bytes)....
New Software Features in Cisco IOS XR Software Release 3.8.1
The following sections contain information on new features and enhancements in Cisco IOS XR Software Release 3.8.1:
•
•
•
New Software Features Supported on All Platforms
The following new software feature in Cisco IOS XR Software Release 3.8.1 is supported on both the Cisco CRS-1 and the Cisco XR 12000 Series Router:
•
Note
LACP Short Period Time Intervals
The Link Aggregation Control Protocol (LACP) Short Period Time Interval feature is supported in Cisco IOS XR Software Release 3.8.1 on the Cisco CRS-1 Router and Cisco XR 12000 Series Router.
Note
LACP packets are exchanged periodically across bundle-member links to verify the link's stability and reliability. Configuring short period time intervals in which LACP packets are sent enables faster detection and recovery from link failures.
Note
Short period time intervals are configured as follows:
•
•
•
•
•
•
After six missed packets, the link is detached from the bundle.
When the short period time interval is not configured, LACP packets are transmitted over a member link every 30 seconds by default.
When the short period time interval is configured, LACP packets are transmitted over a member link once every 1000 milliseconds (1 second) by default. Optionally, both the transmit and receive intervals can be configured to less than 1000 milliseconds, independently or together, in increments of 100 milliseconds (100, 200, 300, and so on).
When you configure a custom LACP short period transmit interval at one end of a link, you must configure the same time period for the receive interval at the other end of the link.
Note
Configuring the Default LACP Short Period Time Interval
This section describes how to configure the default short period time interval for sending and receiving LACP packets on a Gigabit Ethernet interface. This procedure also enables the LACP short period.
SUMMARY STEPS
To enable an LACP short period time interval, using the default time of 1 second, perform the following steps.
1.
2.
3.
4.
5.
DETAILED STEPS
Configuring Custom LACP Short Period Time Intervals
This section describes how to configure custom short period time intervals (less than 1000 milliseconds) for sending and receiving LACP packets on a Gigabit Ethernet interface.
Note
SUMMARY STEPS
To configure custom receive and transmit intervals for LACP packets, perform the following steps.
Router A
1.
2.
3.
4.
5.
Router B
6.
7.
8.
9.
Router A
10.
11.
12.
13.
Router B
14.
15.
16.
17.
Router A
18.
19.
20.
21.
Router B
22.
23.
24.
25.
DETAILED STEPS
Configuration Examples for LACP Short Period
The following example shows how to configure the LACP short period time interval to the default time of 1000 milliseconds (1 second):
configinterface gigabitethernet 0/0/0/1bundle id 1 mode activelacp period shortcommitThe following example shows how to configure custom LACP short period transmit and receive intervals to less than the default of 1000 milliseconds (1 second):
Router A
configinterface gigabitethernet 0/0/0/1bundle id 1 mode activelacp period shortcommitRouter B
configinterface gigabitethernet 0/0/0/1lacp period shortcommitRouter A
configinterface gigabitethernet 0/0/0/1lacp period short transmit 100commitRouter B
configinterface gigabitethernet 0/0/0/1lacp period short transmit 100commitRouter A
configinterface gigabitethernet 0/0/0/1lacp period short receive 100commitRouter B
configinterface gigabitethernet 0/0/0/1lacp period short receive 100commitLACP Commands
This section includes the following commands associated with the LACP Short Period Time Interval feature:
lacp period short
To enable a short period time interval for the transmission and reception of Link Aggregation Control Protocol (LACP) packets, use the lacp period short command in interface configuration mode. To return to the default short period, use the no form of this command.
lacp period short [receive interval] [transmit interval]
no lacp period short [receive interval] [transmit interval]
Syntax Description
Defaults
The default is 1000.
Command Modes
Interface configuration
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. If you suspect user group assignment is preventing you from using a command, contact your AAA administrator.
Note
When you configure a custom LACP short period transmit interval at one end of a link, you must configure the same time period for the receive interval at the other end of the link.
Note
Task ID
Examples
The following example shows how to enable a default Link Aggregation Control Protocol (LACP) short period on a Gigabit Ethernet interface:
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period shortRP/0/RP0/CPU0:router(config-if)# commitThe following example shows how to configure custom Link Aggregation Control Protocol (LACP) short period transmit and receive intervals at both ends of a connection:
Router A
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period shortRP/0/RP0/CPU0:router(config-if)# commitRouter B
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period shortRP/0/RP0/CPU0:router(config-if)# commitRouter A
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500RP/0/RP0/CPU0:router(config-if)# commitRouter B
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period short transmit 500RP/0/RP0/CPU0:router(config-if)# commitRouter A
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500RP/0/RP0/CPU0:router(config-if)# commitRouter B
RP/0/RP0/CPU0:router# configRP/0/RP0/CPU0:router(config)# interface gigabitethernet 0/1/0/0RP/0/RP0/CPU0:router(config-if)# lacp period short receive 500RP/0/RP0/CPU0:router(config-if)# commitRelated Commands
show lacp io
To display the Link Aggregation Control Protocol (LACP) transmission information that used by the transmitting device for sending packets on an interface, use the show lacp io command in EXEC mode.
show lacp io [Bundle-Ether bundle-id] [Bundle-POS bundle-id] [GigabitEthernet interface-path-id] [POS interface-path-id] [TenGigE interface-path-id]
Syntax Description
Defaults
The default takes no parameters and displays information for all actively transmitting interfaces.
Command Modes
EXEC
Command History
Release 3.8.1
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.
This command displays information only for interfaces that are actively transmitting packets.
Task ID
Examples
The following example shows how to display Link Aggregation Control Protocol (LACP) information for the Ethernet bundle interface with bundle ID 28.
RP/0/RP0/CPU0:router# show lacp io bundle-ether 28Thu Jun 18 16:28:54.068 PSTBundle-Ether28Interface GigabitEthernet0/1/5/6================================Interface handle: 0x01180100Interface media type: EthernetFast periodic interval: 1000msSource MAC address: 0015.63c0.b3b8Actor system: 0x8000, 00-15-63-c0-b0-04Actor key: 0x001cActor port: 0x8000, 0x0001Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Partner system: 0x8000, 00-15-63-58-b9-04Partner key: 0x001cPartner port: 0x0001, 0x0003Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Interface GigabitEthernet0/1/5/7================================Interface handle: 0x01180120Interface media type: EthernetFast periodic interval: 1000msSource MAC address: 0015.63c0.b3b9Actor system: 0x8000, 00-15-63-c0-b0-04Actor key: 0x001cActor port: 0x8000, 0x0002Actor state: Act (T/o) Agg Sync (Coll) (Dist) (Def) (Exp)Partner system: 0x8000, 00-15-63-58-b9-04Partner key: 0x001cPartner port: 0x0002, 0x0004Partner state: Act (T/o) Agg (Sync) (Coll) (Dist) (Def) (Exp)RP/0/RP0/CPU0:router#The following example shows how to display Link Aggregation Control Protocol (LACP) information for all actively transmitting interfaces:
RP/0/RP0/CPU0:router# show lacp ioThu Jun 18 16:33:57.330 PSTBundle-Ether28Interface GigabitEthernet0/1/5/6================================Interface handle: 0x01180100Interface media type: EthernetFast periodic interval: 1000msSource MAC address: 0015.63c0.b3b8Actor system: 0x8000, 00-15-63-c0-b0-04Actor key: 0x001cActor port: 0x8000, 0x0001Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Partner system: 0x8000, 00-15-63-58-b9-04Partner key: 0x001cPartner port: 0x0001, 0x0003Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Interface GigabitEthernet0/1/5/7================================Interface handle: 0x01180120Interface media type: EthernetFast periodic interval: 1000msSource MAC address: 0015.63c0.b3b9Actor system: 0x8000, 00-15-63-c0-b0-04Actor key: 0x001cActor port: 0x8000, 0x0002Actor state: Act (T/o) Agg Sync (Coll) (Dist) (Def) (Exp)Partner system: 0x8000, 00-15-63-58-b9-04Partner key: 0x001cPartner port: 0x0002, 0x0004Partner state: Act (T/o) Agg (Sync) (Coll) (Dist) (Def) (Exp)Bundle-POS24Interface POS0/1/4/0====================Interface handle: 0x011804c0Interface media type: POSFast periodic interval: 1000msActor system: 0x8000, 00-15-63-c0-b0-04Actor key: 0x0018Actor port: 0x8000, 0x0003Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Partner system: 0x8000, 00-15-63-58-b9-04Partner key: 0x0018Partner port: 0x8000, 0x0001Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Interface POS0/1/4/1====================Interface handle: 0x011804e0Interface media type: POSFast periodic interval: 1000msActor system: 0x8000, 00-15-63-c0-b0-04Actor key: 0x0018Actor port: 0x8000, 0x0004Actor state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Partner system: 0x8000, 00-15-63-58-b9-04Partner key: 0x0018Partner port: 0x8000, 0x0002Partner state: Act (T/o) Agg Sync Coll Dist (Def) (Exp)Related Commands
lacp packet-capture
To capture LACP packets so that their information can be displayed by the show lacp packet-capture command, use the lacp packet-capture command in EXEC mode.
lacp packet-capture gigabitethernet interface-path-id | pos interface-path-id | tengige interface-path-id number-of-packets
To stop capturing packets or to clear captured packets, use the lacp packet-capture command in EXEC mode.
lacp packet-capture [bundle-ether bundle-id | bundle-pos bundle-id gigabitethernet interface-path-id | pos interface-path-id | tengige interface-path-id] clear | stop
Syntax Description
Defaults
The default (no parameters) executes globally for all interfaces on the line card.
Command Modes
EXEC
Command History
Release 3.8.1
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.
The lacp packet-capture command captures transmitted and received LACP packets on a single bundle member interface. The contents of these packets can then be displayed by the show lacp packet-capture command. If the lacp packet-capture command is not issued, the show lacp packet-capture command does not display any information.
The lacp packet-capture command continues capturing packets until the stop keyword is issued for that port or that bundle. Captured packets are stored and continue to be displayed until the clear keyword is issued for that port or that bundle.
Packets can be only captured for one port on a line card at a time. Starting a packet capture on a port implicitly stops and clears all packet captures on all other ports on that line card.
To stop capturing packets before the specified number of packets has been captured, issue the stop keyword.
If stop is specified for a single interface, packet capturing is stopped only on that interface.
If stop is specified for a bundle interface, packet capturing is stopped on all members of that bundle.
If stop is specified globally (the default—no parameters), packet capturing is stopped on all bundle interfaces on the router.
To clear all captured packets that are stored for an interface, issue the clear keyword.
If clear is specified for a single interface, packets are cleared only on that interface.
If clear is specified for a bundle interface, packets are cleared on all members of that bundle.
If clear is specified globally (the default—no parameters), packets are cleared on all bundle interfaces on the router.
Task ID
Examples
The following example shows how to capture LACP packets on a POS interface:
RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 100The following example shows how to stop capturing LACP packets on a POS interface:
RP/0/RP0/CPU0:router# lacp packet-capture pos 0/1/0/0 stopRelated Commands
show lacp packet-capture
To display the contents of Link Aggregation Control Protocol (LACP) packets that are sent and received on an interface, use the show lacp packet-capture command in EXEC mode.
show lacp packet-capture [decoded] [in | out] GigabitEthernet interface-path-id | POS interface-path-id | TenGigE interface-path-id
Syntax Description
Defaults
The default displays both in and out information.
Command Modes
EXEC
Command History
Release 3.8.1
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.
Note
Task ID
Examples
Example 1
The following example shows how to display raw LACP packet contents in hexadecimal format for a Gigabit Ethernet interface:
Note
RP/0/RP0/CPU0:router# lacp packet-capture gigabitethernet 0/1/0/0 100RP/0/RP0/CPU0:router# show lacp packet-capture gigabitethernet 0/1/0/0Wed Apr 29 16:27:40.996 GMTOUT Apr 29 17:05:50.123========================01 01 01 14 80 00 02 a7 4c 81 95 04 00 01 80 00 00 01 45 0000 00 02 14 ff ff 00 00 00 00 00 00 00 00 ff ff 00 00 40 0000 00 03 10 ff ff 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0000 00 00 00 00 00 00 00 00 00OUT Apr 29 17:35:50.124========================...Example 2
The following example shows how to display the LACP parameters decoded from individual packets that are transmitted and received on a Gigabit Ethernet interface:
Note
RP/0/RP0/CPU0:router# lacp packet-capture gigabitethernet 0/1/0/0 100RP/0/RP0/CPU0:router# show lacp packet-capture decoded gigabitethernet 0/1/0/0Wed Apr 29 16:27:54.748 GMTOUT Apr 29 17:06:03.008========================Subtype: 0x01 - LACP Version: 1TLV: 0x01 - Actor Information Length: 20System: Priority: 32768, ID: 02-a7-4c-81-95-04Key: 0x0001, Port priority: 32768, Port ID: 1State: Act (T/o) Agg (Sync) (Coll) (Dist) Def (Exp)TLV: 0x02 - Partner Information Length: 20System: Priority: 65535, ID: 00-00-00-00-00-00Key: 0x0000, Port priority: 65535, Port ID: 0State: (Act) (T/o) (Agg) (Sync) (Coll) (Dist) Def (Exp)TLV: 0x03 - Collector Information Length: 16Max delay: 65535TLV: 0x00 - Terminator Length: 0Related Commands
Cisco CRS-1 Router-Specific Software Features
The following new features in Cisco IOS XR Software Release 3.8.1 are supported only on the Cisco CRS-1 platform:
•
Multicast Fabric Test
A new test, Multicast Fabric Test, has been added to the standard diagnostics tests as test number 11. There are no visible changes to the CLI. This test runs automatically with the standard diagnostics tests configured on the router or when the diagnostic start command is issued. This is supported on the Cisco CRS-1 Series Router.
Enhanced Process Distribution to Improve Load-Balancing Across Cisco CRS-1 RPs
This feature was introduced in Cisco IOS XR Release 3.6.3.
The default Cisco IOS XR process placement policy has changed to improve the distribution of processing load across active Cisco CRS-1 route processors (RPs). These changes affect systems with more than one active RP, such as Cisco CRS-1 multichassis systems and Cisco CRS-1 single-chassis systems with optional, distributed route processors (DRPs) installed.
Highlights of the New Process Distribution Feature
The new default process placement policy creates three groups of placeable processes:
•
•
•
Each group is placed as a unit, with all processes within a group placed together on the same node.
The CSI group is, by definition, always placed on the dLRSC node. The only placement variation that can occur is in regard to the IPv4 and IPv6 groups.
If a single active non-dLRSC RP pair exists, the IPv4 and IPv6 groups are placed on that pair.
If more than one active non-dLRSC RP pair exists, the IPv4 group is placed on one such pair and the IPv6 group on another. The placement of each group occurs when that group starts.
If no non-dLRSC pairs exist, but an unpaired active non-dLRSC RP does, then, the first placeable group to start (IPv4/MPLS or IPv6) is placed on the dLRSC, with the other group being placed on the non-dLRSC RP pair.
Information About How Process Placement Works
•
•
•
•
•
•
•
•
Note
•
Cisco XR 12000 Series Router-Specific Software Features
The following new features in Cisco IOS XR Software Release 3.8.1 are supported only on the Cisco XR 12000 Series Router platform:
•
Power Manager
The Power Manager software manages the following types of power requirements for the chassis components:
•
•
•
•
With this software, newly discovered or inserted modules are prevented from powering up unless sufficient power is available to operate them.
The Power Manager software performs the following functions:
•
•
•
•
•
•
Note
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
–
–
DETAILED STEPS
1
show power-mgr Output: Example
The following example shows sample output from the show power-mgr command.
RP/0/5/CPU0:router(admin)# show power-mgr traceSun Jun 28 12:25:40.763 PST97 wrapping entries (1152 possible, 0 filtered, 97 total)Jun 12 04:27:12.426 power_manager/debug 0/5/CPU0 t33 -------power_manager starting--------Jun 12 04:27:12.426 power_manager/debug 0/5/CPU0 t33 PM Spawning main ProcessJun 12 04:27:12.426 power_manager/debug 0/5/CPU0 t33 Performing pre-config monvar parsingJun 12 04:27:12.626 power_manager/debug 0/5/CPU0 t35 Power Manager EDM Bind successfulJun 12 04:27:12.658 power_manager/debug 0/5/CPU0 t35 Power Manager Bag registration doneJun 12 04:27:12.715 power_manager/debug 0/5/CPU0 t35 Power Manager EDM Registration is doneJun 12 04:27:14.516 power_manager/debug 0/5/CPU0 t1 Event: DISCOVERY_DONE on zone=2 withdata 0x00000000Jun 12 04:27:14.517 power_manager/debug 0/5/CPU0 t33 PM Dequeued Event = DISCOVERY_DONEJun 12 04:27:14.520 power_manager/debug 0/5/CPU0 t36 Running on primary RPJun 12 04:27:14.539 power_manager/debug 0/5/CPU0 t36 MBus path to PEMs now availableJun 12 04:27:14.539 power_manager/debug 0/5/CPU0 t36 Attempting to discover powershelf typeJun 12 04:27:15.073 power_manager/debug 0/5/CPU0 t36 PEM FAMILY determined to be =0Jun 12 04:27:15.240 power_manager/debug 0/5/CPU0 t36 Successfully discovered powershelftype=2Jun 12 04:27:15.240 power_manager/debug 0/5/CPU0 t36 Discovering installed PEMsJun 12 04:27:19.550 power_manager/debug 0/5/CPU0 t22 Discarding LC_OIR_INSERTED for slot25; in DISCOVERY_PHASEJun 12 04:27:19.551 power_manager/debug 0/5/CPU0 t16 Discarding LC_OIR_INSERTED for slot16; in DISCOVERY_PHASEJun 12 04:27:19.551 power_manager/debug 0/5/CPU0 t19 Discarding LC_OIR_INSERTED for slot19; in DISCOVERY_PHASEJun 12 04:27:19.552 power_manager/debug 0/5/CPU0 t25 Discarding LC_OIR_INSERTED for slot28; in DISCOVERY_PHASEJun 12 04:27:19.562 power_manager/debug 0/5/CPU0 t20 Discarding LC_OIR_INSERTED for slot20; in DISCOVERY_PHASEJun 12 04:27:19.564 power_manager/debug 0/5/CPU0 t12 Discarding LC_OIR_INSERTED for slot2; in DISCOVERY_PHASEJun 12 04:27:19.565 power_manager/debug 0/5/CPU0 t15 Discarding LC_OIR_INSERTED for slot5; in DISCOVERY_PHASEJun 12 04:27:19.565 power_manager/debug 0/5/CPU0 t10 Discarding LC_OIR_INSERTED for slot0; in DISCOVERY_PHASEJun 12 04:27:19.566 power_manager/debug 0/5/CPU0 t13 Discarding LC_OIR_INSERTED for slot3; in DISCOVERY_PHASEJun 12 04:27:19.575 power_manager/debug 0/5/CPU0 t21 Discarding LC_OIR_INSERTED for slot24; in DISCOVERY_PHASEJun 12 04:27:19.577 power_manager/debug 0/5/CPU0 t14 Discarding LC_OIR_INSERTED for slot4; in DISCOVERY_PHASEJun 12 04:27:19.583 power_manager/debug 0/5/CPU0 t11 Discarding LC_OIR_INSERTED for slot1; in DISCOVERY_PHASEJun 12 04:27:19.598 power_manager/debug 0/5/CPU0 t18 Discarding LC_OIR_INSERTED for slot18; in DISCOVERY_PHASEJun 12 04:27:23.418 power_manager/debug 0/5/CPU0 t36 PEM 2 open part failed ; retry count=25Jun 12 04:27:31.335 power_manager/debug 0/5/CPU0 t36 PEM 2 open part failed ; retry count=25Jun 12 04:27:31.536 power_manager/err 0/5/CPU0 t36 Intelligence check for pem 2 failed with result =4Jun 12 04:27:31.536 power_manager/debug 0/5/CPU0 t36 PEM2 discovered as GSR6 legacy ACJun 12 04:27:31.683 power_manager/debug 0/5/CPU0 t36 PEM2 can supply up to 1600 wattsJun 12 04:27:31.683 power_manager/debug 0/5/CPU0 t36 Zone discovery found 1 power zone forthis chassisJun 12 04:27:31.683 power_manager/debug 0/5/CPU0 t36 Discovering cards present and populating slot dataJun 12 04:27:36.684 power_manager/debug 0/5/CPU0 t36 Cardtype 150 found in slot 0, needing134 WJun 12 04:27:36.684 power_manager/debug 0/5/CPU0 t36 Cardtype 150 found in slot 1, needing134 WJun 12 04:27:36.702 power_manager/debug 0/5/CPU0 t36 Cardtype 149 found in slot 2, needing240 WJun 12 04:27:36.717 power_manager/debug 0/5/CPU0 t36 Cardtype 149 found in slot 3, needing240 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 149 found in slot 4, needing240 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 96 found in slot 5, needing60 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 6; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 7; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 8; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 9; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 10; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 11; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 12; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 13; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 14; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 15; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 29 found in slot 16, needing56 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 17; markingphantomJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 30 found in slot 18, needing45 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 30 found in slot 19, needing45 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 30 found in slot 20, needing45 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 21; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 22; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 23; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 15 found in slot 24, needing26 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 15 found in slot 25, needing26 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 26; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 27; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Cardtype 112 found in slot 28, needing178 WJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 29; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 30; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 No card present in slot 31; skippingJun 12 04:27:36.735 power_manager/debug 0/5/CPU0 t36 Changing phase to INIT_DECISION_PHASEJun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Powershelf capacity at 1600 wattszone1, 0 watts zone2Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Reserved chassis power is 477 W zone1,0 W zone2Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Available power for chassis is 1123 Wzone1,0 W zone2,Jun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Starting power-on decision processwith 1123/0 WJun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 Starting power-on decision processwith 5/60 WJun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 After accounting for RPs, 1063/0 WavailJun 12 04:27:36.738 power_manager/debug 0/5/CPU0 t36 After accounting for priority slots,1063/0 W availJun 12 04:28:46.718 power_manager/debug 0/5/CPU0 t36 slot 0 needs 134 W, 929 avail;Jun 12 04:28:46.718 power_manager/debug 0/5/CPU0 t36 slot 1 needs 134 W, 795 avail;Jun 12 04:28:46.735 power_manager/debug 0/5/CPU0 t36 slot 2 needs 240 W, 555 avail;Jun 12 04:28:46.750 power_manager/debug 0/5/CPU0 t36 slot 3 needs 240 W, 315 avail;Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 slot 4 needs 240 W, 75 avail;Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 After accounting for normal slots,75/0 W availJun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 RP in-use power is 60 W zone1, 0 Wzone2Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 Linecard in-use power is 988 W zone1,0 W zone2Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 Available power for chassis is 75 Wzone1,0 W zone2,Jun 12 04:28:46.777 power_manager/debug 0/5/CPU0 t36 Starting periodic task to monitor PEMsJun 12 04:28:46.778 power_manager/debug 0/5/CPU0 t36 Changing phase to RUNNING_PHASEJun 12 04:28:47.706 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringupslot 1Jun 12 04:28:47.711 power_manager/debug 0/5/CPU0 t10 Sufficient power available to bringupslot 0Jun 12 04:28:47.713 power_manager/debug 0/5/CPU0 t12 Sufficient power available to bringupslot 2Jun 12 04:28:47.715 power_manager/debug 0/5/CPU0 t14 Sufficient power available to bringupslot 4Jun 12 04:28:47.718 power_manager/debug 0/5/CPU0 t13 Sufficient power available to bringupslot 3Jun 12 04:28:59.467 power_manager/debug 0/5/CPU0 t33 PEM2 busy; skipping pollingJun 12 04:29:10.161 power_manager/debug 0/5/CPU0 t33 PEM2 no longer busy; resuming pollingJun 12 04:36:30.950 power_manager/debug 0/5/CPU0 t10 Sufficient power available to bringupslot 0Jun 12 04:36:54.291 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringupslot 1Jun 12 09:13:43.219 power_manager/debug 0/5/CPU0 t10 Sufficient power available to bringupslot 0Jun 12 09:13:44.514 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringupslot 1Jun 12 09:14:29.463 power_manager/debug 0/5/CPU0 t11 Sufficient power available to bringupslot 1ATM Support for Layer 2 Tunnel Protocol Version 3 on Engine-5 Line Cards
In Cisco IOS XR Software Release 3.8.1, the Cisco XR 12000 Series Router supports the following Layer 2 Tunnel Protocol Version 3 (L2TPv3) features on the Engine-5 line cards:
•
The following modes are supported:
–
–
–
•
The following modes support interworking:
–
–
For detailed information about L2TPv3, see the Implementing Layer 2 Tunnel Protocol Version 3 on Cisco IOS XR Software module of Cisco IOS XR MPLS Configuration Guide.
New Hardware Features for Cisco IOS XR Software Release 3.8.1
The following new hardware features were introduced in Cisco IOS XR Software Release 3.8.1:
•
•
Cisco CRS-1 Router-Specific Hardware Features
The following new features in Cisco IOS XR Software Release 3.8.1 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.1 are supported on the Cisco XR 12000 Series Router platform:
•
–
–
•
•
–
–
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 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
•
•
•
•
•
•
Minimum Flash Disk Requirements When Upgrading to Release 3.8.1
Cisco IOS XR Software Release 3.8.1 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.1.
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.1 on the router platforms indicated:
•
•
Caveats Specific to the Cisco CRS-1 Router
The following caveats are specific to the Cisco CRS-1 platform:
•
Symptom:
Cisco CRS-1 systems might not reload successfully due to fabric planes remaining in MCAST DOWN state until manually recovered.
Description:
Occasionally on CRS-1 Multi-chassis systems with greater than 2 active planes the system may come up with one or more fabric planes in the MCAST DOWN state following a system reload.
The fabric plane state is found by issuing the show controllers fabric plane all admin command as shown in Example 1. If all odd or all even planes are in the MCAST DOWN state, the system does not come up and eventually reloads.
Example 1 Fabric Plane States in a Failed Condition
RP/0/RP0/CPU0:router# adminRP/0/RP0/CPU0:router(admin)# show controllers fabric plane allPlane Admin Oper up->dn Down Total DownId State State counter Flags Bundles Bundles------------------------------------------------------------0 UP MCAST_DOWN 0 m 27 181 UP UP 0 27 152 UP MCAST_DOWN 0 m 27 183 UP UP 0 27 154 UP UP 0 27 155 UP UP 0 27 156 UP UP 0 27 157 UP UP 0 27 15Conditions:
This issue might occur after a system reload.
Workaround:
None.
Recovery:
Use the following procedure to recover from this problem:
1.
The affected planes report the operating state as MCAST_ DOWN.
2.
Each line card chassis rack that is present in the system has an associated S13 card for each plane. For example, if a system that has three LCCs, the S13 cards for plane 0 are: 0/SM0/SP, 1/SM0/SP and 2/SM0/SP.
3.
show controllers backplane ethernet clients 25 statistics location [R]/sm[P]/sp]where:
[R] is for each rack in the system, and [P] is for each affected plane in the system.
The following example shows LCC0 if plane 0 is MCAST_DOWN:
show controllers backplane ethernet clients 25 statistics location 0/sm0/spRepeat this command for all LCCs for each affected plane.
4.
Rx mem score 264, alloc fails 0, free fails 0If the Rx mem score is 0 or any value other than 264, the card is OK.
If the Rx mem score is 264, this card is affected.
5.
hw-module location [R]/SM[P]/SP reloadwhere:
[R] is the rack of the affected card and [P] is the affected plane.
For example, if 2/SM0/SP had an Rx mem score of 264, apply the following reload command:
admin hw-module location 2/SM0/SP reloadCisco IOS XR Caveats
The following caveats apply to both platforms:
•
Basic Description:
ipv4_mfwd_partner: %ROUTING-IPV4_MFWD-5-IP_ADDR_RETRY
Symptom:
Multicast packets dropped.
Conditions:
This issue could happen due to SPA/LC OIR or commit replace.
After LC OIRed ARM updates to MFWD for non existent interface, MFWD attempts to update TYPE_ADD/TYPE_CHANGE for a non-existent interface handle. For these event types, MFWD checks with the IFH server to determine the interface type to see if this is a multicast supported interface.
The IFH server does not have any information for this OIRed interface. If this error occurs, ARM update for address does not process. The MFWD retries this failure every 30 seconds. The retry always fails since IFH does not know about the interface.
Workaround:
None.
Recovery:
Clear the mfib database location.
•
Basic Description:
Bundle members with LACP short flap once during RP fail over
Symptom:
Bundle members flap once and traffic loss occurs when LACP short is configured on members.
Conditions:
This issue occurs when RP FO with LACP short is configured on the members.
Workaround:
None.
Impact:
Traffic loss occurs during failover until the members come up. This issue does not have any impact on the router bring-up time.
Recovery:
No manual recovery is necessary. Traffic resumes automatically when the bundle members recover.
•
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:
Process on crashing silently.
Symptom:
Process crash on is seen in named SDR.
Conditions:
The trigger is to issue the show process or show memory command on a non-existing node.
Workaround:
Workaround is not needed because there is no impact on the functionality of the router. However, the show command does not work on a non-existing node.
System Impact:
This issue does not have a functional impact. The show process command does not work on a non-existing node, and an error message displays.
•
Basic Description:
ATM L2 PVCs remain in AIS OUT state after LC OIR.
Symptom:
AIS cells injected on a L2 VC event though L2VPN UP.
Conditions:
Programming the SAR sometimes misses while configuring the subinterface in L2 transport and sometimes with RP FO.
Workaround:
None.
Recovery:
Reload the affected SPA.
Caveats Specific to the Cisco XR 12000 Series Router
The following caveats are specific to the Cisco XR 12000 Series Router platform:
•
Basic Description:
Removing and adding back PRP-3 to a client LR results in its looped reset.
Symptom:
A PRP-3 RP resets continuously after using an SDR command to add the RP to a named SDR. The functionality of the owner SDR is not affected.
Conditions:
This issue occurs if a PRP-3 RP is removed from a named SDR and added back to the same SDR as part of the same commit.
For example, the router has the following configuration:
0/0/CPU0—Owner LR Active
0/1/CPU0—Owner LR Standby
0/2/CPU0—E5 LC in Owner
0/3/CPU0—Client LR1
0/4/CPU0—Client LR1
0/5/CPU0—E3 LC in LR1
The following command sequence causes 0/3 to start continuously resetting:
RP/0/0/CPU0:ios(admin-config)#logical-router lr1 RP/0/0/CPU0:ios(admin-config-lr:lr1)#loc 0/3/* RP/0/0/CPU0:ios(admin-config-lr:lr1)#no loc 0/3/* RP/0/0/CPU0:ios(admin-config-lr:lr1)#logical-router lr2 RP/0/0/CPU0:ios(admin-config-lr:lr2)#loc 0/3/* RP/0/0/CPU0:ios(admin-config-lr:lr2)#en Uncommitted changes found, commit them before exiting(yes/no/cancel)? [cancel]:yWorkaround:
Avoid triggering this issue by splitting the commit into two commits:
1.
2.
Recovery:
To recover from the issue after it is triggered:
1.
2.
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.1
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 11 lists the major milestones of Cisco IOS XR Software Release 3.8.1.
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
The following sections describe the documentation available for the Cisco CRS-1 router and the Cisco XR 12000 Series Router. Documentation is available in the form of PDF and HTML files and is available on www.cisco.com:
Hardware Documents
You can find the most current hardware documentation at the following URLs:
Cisco CRS-1:
http://www.cisco.com/en/US/products/ps5763/tsd_products_support_series_home.html
Cisco XR 12000 Series Router:
http://www.cisco.com/en/US/products/ps6342/tsd_products_support_series_home.html
Software Documents
The Cisco IOS XR software documentation set includes the Cisco IOS XR software configuration guides and command references, as well as a getting started guide. See About Cisco IOS XR Software Documentation for Release 3.8 for a list of Cisco IOS XR Release 3.8.1 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 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.
CCDE, CCENT, CCSI, Cisco Eos, Cisco HealthPresence, Cisco IronPort, the Cisco logo, Cisco Nurse Connect, Cisco Pulse, Cisco SensorBase, Cisco StackPower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flipshare (Design), Flip Ultra, Flip Video, Flip Video (Design), Instant Broadband, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Capital, Cisco Capital (Design), Cisco:Financed (Stylized), Cisco Store, Flip Gift Card, and One Million Acts of Green are service marks; and Access Registrar, Aironet, AllTouch, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Lumin, Cisco Nexus, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, Continuum, EtherFast, EtherSwitch, Event Center, Explorer, Follow Me Browsing, GainMaker, iLYNX, IOS, iPhone, IronPort, the IronPort logo, Laser Link, LightStream, Linksys, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, PCNow, PIX, PowerKEY, PowerPanels, PowerTV, PowerTV (Design), PowerVu, Prisma, ProConnect, ROSA, SenderBase, SMARTnet, Spectrum Expert, StackWise, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0910R)
© 2009 Cisco Systems, Inc. All rights reserved.
Guest
