Table Of Contents
Cisco ASR 9000 Series Right-To-Use (RTU) Licensing
Determining Your Software Version
Multiple Spanning Tree Access Gateway
MSTP Supported Features on the Cisco ASR 9000 Series Router
Restrictions for MSTP on the Cisco ASR 9000 Series Router
Configuring MSTP and MSTAG on the Cisco ASR 9000 Series Router
Configuring VID to MSTI Mapping
spanning-tree ring-termination
debug spanning-tree mst packet
debug spanning-tree mst protocol-state
EFP Egress Filtering Feature Overview
Requirements for Egress EFP Filtering on Cisco ASR 9000 Series Router
Defining Data-Forwarding Behavior
Configuring Egress EFP Filtering on the Cisco ASR 9000 Series Router
flood mode convergence-optimized (VPLS)
Open Cisco IOS XR Software Caveats
Open Caveats Specific to the Cisco ASR 9000 Series Router
Resolved Cisco IOS XR Software Release 3.7.2 Caveats
Upgrading Cisco IOS XR Software
Upgrading from IOS XR 3.7.2 to IOS XR 3.7.3
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco ASR 9000 Series Aggregation Services Routers for Cisco IOS XR Software Release 3.7.3
September 18, 2009
Cisco IOS XR software Release 3.7.3
Text Part Number OL-19942-01
Note
For information on the Cisco ASR 9000 Series Router running Cisco IOS XR Software Release 3.7.3, see the "Important Notes" section.
These release notes describe the features provided in the Cisco ASR 9000 Series Router running Cisco IOS XR Software Release 3.7.3 and are updated as needed.
For a list of software caveats that apply to Cisco ASR 9000 Series Router Software Release 3.7.3, see the "Caveats" section. The caveats are updated for every release and are described on the World Wide Web at www.cisco.com.
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 running on the Cisco ASR 9000 Series Router provides the following features and benefits:
•
•
–
–
–
–
–
–
–
–
•
•
•
•
–
–
–
–
–
–
•
•
•
•
•
•
•
–
–
–
For more information about new features provided on the Cisco ASR 9000 Series Router platform for Cisco IOS XR Software Release 3.7.3, see the "Features Introduced on the Cisco ASR 9000 Series Router Platform With Cisco IOS XR Software Release 3.7.3" section in this document.
System Requirements
This section describes the system requirements for Cisco ASR 9000 Series Router Software Release 3.7.3. The system requirements include the following information:
Feature Set Table
The Cisco ASR 9000 Series Router software is packaged in feature sets (also called software images). Each feature set contains a specific set of Cisco ASR 9000 Series Router Software Release 3.7.3 features.
Table 1 lists the Cisco ASR 9000 Series Router software feature set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 3.7.3 supported on the Cisco ASR 9000 Series Router.
Table 1 Cisco ASR 9000 Series Router Supported Feature Sets
(Cisco IOS XR Software Release 3.7.3 PIE Files)Cisco IOS XR IP Unicast Routing Core Bundle
comp-asr9k-mini.pie-3.7.3
Contains the required core packages, including OS, Admin, Base, Forwarding, Forwarding Processor Card 40G, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR IP Unicast Routing Core Bundle
comp-asr9k-mini.vm-3.7.3
Contains the required core packages including OS, Admin, Base, Forwarding, Forwarding Processor Card 40G, Routing, SNMP Agent, and Alarm Correlation.
Cisco IOS XR Manageability Package
asr9k-mgbl.pie-3.7.3
XML2 Parser, and HTTP server packages.This PIE also contains some SNMP MIB infrastructure. Certain MIBs won't work if this PIE is not installed.
Cisco IOS XR MPLS Package
asr9k-mpls.pie-3.7.3
MPLS-TE,3 LDP,4 MPLS Forwarding, MPLS OAM,5 LMP,6 OUNI,7 RSVP,8 and Layer-3 VPN.
Cisco IOS XR Multicast Package
asr9k-mcast.pie-3.7.3
Multicast Routing Protocols (PIM, MSDP,9 IGMP,10 Auto-RP), Tools (SAP, MTrace), and Infrastructure (MRIB,11 MURIB12 , MFWD13 ), and BIDIR-PIM.14
Cisco IOS XR Security Package
asr9k-k9sec.pie-3.7.3
Support for Encryption, Decryption, IPSec,15 SSH,16 SSL,17 and PKI18 (Software based IPSec support—maximum of 500 tunnels)
Cisco IOS XR FPD Package
asr9k-fpd.pie-3.7.3
Firmware for ROMMON19 images for Cisco ASR 9000 Series chassis.
Cisco IOS XR Diagnostic Package
asr9k-diags.pie-3.7.3
Diagnostic utilities for Cisco IOS XR Cisco ASR 9000 Series Routers.
1 Packages are installed individually
2 Extensible Markup Language
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 Multicast Source Discovery Protocol
10 Internet Group Management Protocol
11 Multicast Routing Information Base
12 Multicast-Unicast RIB
13 Multicast forwarding
14 Bidirectional Protocol Independent Multicast
15 IP Security
16 Secure Shell
17 Secure Socket Layer
18 Public-key infrastructure
19 ROM monitor
Table 1 lists the Cisco ASR 9000 Series Router TAR files.
Memory Requirements
Caution
The minimum memory requirement for Cisco ASR 9000 Series Router running Cisco IOS XR Software Release 3.7.3 consists of the following:
•
This minimum memory requirement is met with the base board design. There are no optional memory or storage upgrades available or required.
Hardware Supported
Cisco IOS XR Software Release 3.7.3 supports Cisco ASR 9000 Series Routers. All hardware features are supported on Cisco IOS XR software, subject to the memory requirements specified in the "Memory Requirements" section.
Table 3 lists the supported hardware components on the Cisco ASR 9000 Series Router and the minimum required software versions. For more information, see the "Other Firmware Support" section.
Software Compatibility
Cisco IOS XR Software Release 3.7.3 is compatible with the following Cisco ASR 9000 Series Router systems:
•
•
Table 4 lists the supported hardware components on the Cisco ASR 9000 Series Router and the minimum required software versions.
Cisco ASR 9000 Series Right-To-Use (RTU) Licensing
Here are on-line locations of the Cisco ASR 9000 Series Right-To-Use (RTU) licensing docs:
http://www.cisco.com/en/US/docs/routers/asr9000/hardware/Prodlicense/A9k-AIP-LIC-B.html
http://www.cisco.com/en/US/docs/routers/asr9000/hardware/Prodlicense/A9k-AIP-LIC-E.html
Note that Layer 3 VPNs are only to be used after you have purchased a license. Cisco will enforce the RTU of L3VPNs in follow on releases. You should contact Cisco, or check the release notes for the follow on release before upgrading for directions on how to install the license as part of the upgrade - otherwise the L3VPN feature may be affected.
Other Firmware Support
The Cisco ASR 9000 Series Router supports the following firmware code:
•
Note that in upgrading from Release 3.7.2 or earlier releases, you may be expected to do a one-time FPD upgrade for any firmware images that may have changed since last release.
Determining Your Software Version
To determine the version of Cisco IOS XR software running on your router, log in to the router and enter the show version command:
Step 1
Step 2
RP/0/RSP0/CPU0:PE44_ASR-9010#show versionCisco IOS XR Software, Version 3.7.3.28I[FCI_DT_IMAGE]Copyright (c) 2009 by Cisco Systems, Inc.ROM: System Bootstrap, Version 1.0(20081208:173612) [ASR9K ROMMON],PE44_ASR-9010 uptime is 2 days, 3 hours, 11 minutesSystem image file is "bootflash:disk0/asr9k-os-mbi-3.7.3.28I/mbiasr9k-rp.vm"cisco ASR9K Series (MPC8641D) processor with 4194304K bytes of memory.MPC8641D processor at 1333MHz, Revision 2.240 GigabitEthernet/IEEE 802.3 interface(s)2 Ethernet/IEEE 802.3 interface(s)12 TenGigabitEthernet/IEEE 802.3 interface(s)219k bytes of non-volatile configuration memory.975M bytes of compact flash card.33994M bytes of hard disk.1605616k bytes of disk0: (Sector size 512 bytes).1605616k bytes of disk1: (Sector size 512 bytes).Configuration register on node 0/RSP0/CPU0 is 0x102Boot device on node 0/RSP0/CPU0 is disk0:Package active on node 0/RSP0/CPU0:asr9k-scfclient, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-scfclient-3.7.3.28IBuilt on Fri Jul 31 09:31:21 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fpd, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fpd-3.7.3.28IBuilt on Fri Jul 31 10:50:01 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-diags, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-diags-3.7.3.28IBuilt on Fri Jul 31 09:31:26 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mgbl, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mgbl-3.7.3.28IBuilt on Fri Jul 31 10:53:55 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mcast, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mcast-3.7.3.28IBuilt on Fri Jul 31 09:42:25 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mpls, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mpls-3.7.3.28IBuilt on Fri Jul 31 09:38:43 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-rout, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-rout-3.7.3.28IBuilt on Fri Jul 31 09:31:41 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-k9sec, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-k9sec-3.7.3.28IBuilt on Fri Jul 31 10:49:41 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-lc, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-lc-3.7.3.28IBuilt on Fri Jul 31 09:25:46 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fwdg, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fwdg-3.7.3.28IBuilt on Fri Jul 31 09:23:33 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-admin, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-admin-3.7.3.28IBuilt on Fri Jul 31 09:15:47 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-base, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-base-3.7.3.28IBuilt on Fri Jul 31 09:17:08 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-os-mbi, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-os-mbi-3.7.3.28IBuilt on Fri Jul 31 08:45:10 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8Boot device on node 0/1/CPU0 is mem:Package active on node 0/1/CPU0:asr9k-scfclient, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-scfclient-3.7.3.28IBuilt on Fri Jul 31 09:31:21 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fpd, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fpd-3.7.3.28IBuilt on Fri Jul 31 10:50:01 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-diags, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-diags-3.7.3.28IBuilt on Fri Jul 31 09:31:26 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mcast, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mcast-3.7.3.28IBuilt on Fri Jul 31 09:42:25 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mpls, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mpls-3.7.3.28IBuilt on Fri Jul 31 09:38:43 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-lc, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-lc-3.7.3.28IBuilt on Fri Jul 31 09:25:46 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fwdg, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fwdg-3.7.3.28IBuilt on Fri Jul 31 09:23:33 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-admin, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-admin-3.7.3.28IBuilt on Fri Jul 31 09:15:47 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-base, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-base-3.7.3.28IBuilt on Fri Jul 31 09:17:08 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-os-mbi, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-os-mbi-3.7.3.28IBuilt on Fri Jul 31 08:45:10 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8Boot device on node 0/4/CPU0 is mem:Package active on node 0/4/CPU0:asr9k-scfclient, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-scfclient-3.7.3.28IBuilt on Fri Jul 31 09:31:21 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fpd, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fpd-3.7.3.28IBuilt on Fri Jul 31 10:50:01 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-diags, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-diags-3.7.3.28IBuilt on Fri Jul 31 09:31:26 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mcast, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mcast-3.7.3.28IBuilt on Fri Jul 31 09:42:25 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mpls, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mpls-3.7.3.28IBuilt on Fri Jul 31 09:38:43 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-lc, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-lc-3.7.3.28IBuilt on Fri Jul 31 09:25:46 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fwdg, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fwdg-3.7.3.28IBuilt on Fri Jul 31 09:23:33 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-admin, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-admin-3.7.3.28IBuilt on Fri Jul 31 09:15:47 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-base, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-base-3.7.3.28IBuilt on Fri Jul 31 09:17:08 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-os-mbi, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-os-mbi-3.7.3.28IBuilt on Fri Jul 31 08:45:10 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8Boot device on node 0/6/CPU0 is mem:Package active on node 0/6/CPU0:asr9k-scfclient, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-scfclient-3.7.3.28IBuilt on Fri Jul 31 09:31:21 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fpd, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fpd-3.7.3.28IBuilt on Fri Jul 31 10:50:01 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-diags, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-diags-3.7.3.28IBuilt on Fri Jul 31 09:31:26 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mcast, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mcast-3.7.3.28IBuilt on Fri Jul 31 09:42:25 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-mpls, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-mpls-3.7.3.28IBuilt on Fri Jul 31 09:38:43 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-lc, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-lc-3.7.3.28IBuilt on Fri Jul 31 09:25:46 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-fwdg, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-fwdg-3.7.3.28IBuilt on Fri Jul 31 09:23:33 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-admin, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-admin-3.7.3.28IBuilt on Fri Jul 31 09:15:47 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-base, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-base-3.7.3.28IBuilt on Fri Jul 31 09:17:08 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8asr9k-os-mbi, V 3.7.3.28I[FCI_DT_IMAGE], Cisco Systems, at disk0:asr9k-os-mbi-3.7.3.28IBuilt on Fri Jul 31 08:45:10 DST 2009By iox-view1 in /auto/ioxbuild9/production/3.7.3.28I.FCI_DT_IMAGE/asr9k/workspace for c2.95.3-p8RP/0/RSP0/CPU0:PE44_ASR-9010#
Features Introduced on the Cisco ASR 9000 Series Router Platform With Cisco IOS XR Software Release 3.7.3
Cisco IOS XR Software Release 3.7.3 added support for the following features on the Cisco ASR 9000 Series Router platform:
•
Cisco IOS XR Software Release 3.7.3 introduces multiple spanning tree access gateway (MSTAG) topology control.
The multiple spanning tree protocol (MSTP) permits mapping of multiple VLANs to one spanning tree instance, to reduce the spanning tree scaling problem. MSTP introduces the concept of regions, which is a group of bridges under the same administrative control and having the similar configuration.
All bridges in a MST region have the same configuration attributes (name, revision, and VLAN to instance mapping). A digest of the VLAN map is embedded in the bridge protocol data units (BPDUs) sent by the bridges. This is used by receiving bridges to verify the region membership.
Figure 1 shows the interaction of MST regions, when bridges running MSTP get connected to bridges running standard spanning tree protocol (STP) or rapid spanning tree protocol (RSTP). Here, switches SW1, SW2, SW3, SW4 support MSTP, while switches SW5 and SW6 do not support MSTP.
Figure 1 MST Interaction with Non-MST Regions
To connect MST regions with non-MST aware networks, an internal spanning tree (IST) instance is used. In case of MSTP, the whole MST region is represented as a single switch to non-MST aware bridges. The logical IST topology for this case is shown in Figure 2.
Figure 2 Logical Topology in MST Region Interacting Non-MST Bridges
Multiple Spanning Tree Access Gateway
The Cisco ASR 9000 Series Router serves as an nPE device terminating uPE access rings and providing connectivity to the aggregation network. As these access rings have redundant connections, they are required to run some variant of STP in order to maintain loop-free connectivity. A basic solution to this problem is to tunnel the BPDUs between the legs of the access ring. This solution results in loop-free topologies, but it has a number of serious limitations for deployment in a service provider network:
•
•
The multiple spanning tree access gateway (MSTAG) topology control is designed to address the BPDUs sent by the nPEs, which do not take the connectivity of the nPE into account when advertising their status. However, it is possible that the failed bridge recovers to the point where it is able to resend BPDUs before the VPLS and IGMP states have been fully restored, at which point the access ring traffic will be redirected to the failed bridge.
This problem is solved by allowing the user to exercise some measure of control over the timing of topology changes, by configuring initial BPDUs to be sent for some period, while the system stabilizes after a bridge or LC reloads. On each bridge in the pair, these initial BPDUs are configured with a priority lower than the standard BPDUs sent by the opposite member of the pair (but still higher than any other bridge in the ring). Sending these in place of standard BPDUs while the system stabilizes, ensures that traffic is not prematurely directed to a bridge, giving it time to recover.
Note
MSTP Supported Features on the Cisco ASR 9000 Series Router
Beginning in Cisco IOS XR Release 3.7.3, support for the following features is added to MSTP on Cisco ASR 9000 Series Router:
•
•
•
•
•
•
MSTP Architecture
This section provides an overview of the architecture of the MSTP implementation. It covers the major components, their responsibilities, and their interactions with other components of the system. Figure 3 shows the interaction of MSTP components.
Figure 3 MSTP Architecture
MSTP Controller
The MSTP controller is a single-threaded, placeable, config-started process, containing the main protocol implementation, including all per-tree and per-port information. The MSTP controller is responsible for:
•
•
•
•
•
•
MSTP I/O
The MSTP I/O processes are single-threaded and feature-started by the controller process. They run on all nodes, on which the control planes for STP enabled ports reside, and are responsible for all BPDU packet I/O. In particular, the MSTP I/O processes are responsible for sending and handling all periodic HELLO packets. In detail, MSTP I/O processes are responsible for:
•
•
•
•
Restrictions for MSTP on the Cisco ASR 9000 Series Router
The following restrictions apply when you configure the MSTP feature on the Cisco ASR 9000 Series Router.
•
EFPs that match any of the following criteria, qualify as "simple":–
–
–
–
•
•
•
•
•
•
Configuring MSTP and MSTAG on the Cisco ASR 9000 Series Router
This section describes the procedures for configuring the MSTP and MSTAG features on the Cisco ASR 9000 Series Router.
•
•
•
•
Enabling STP
By default, STP is disabled on all ports. For MSTP to run over an interface, it should be explicitly configured on the physical port. When a port has STP configured on it, all EFPs configured on that port automatically become STP enabled. A bridge domain (BD) is STP enabled, when all the EFPs in that BD are on ports with STP configured. If a BD is not STP enabled, then all the EFPs in that BD that are on STP enabled ports are placed in STP blocking state.
Configuring VID to MSTI Mapping
To configure VID to MSTI mapping, following models can be used:
•
•
•
The first model is used here as it is consistent with IOS XR software, and follows the deployment model.
Configuring MSTP Parameters
The MSTP specification defines a number of configurable parameters as listed below:
The first set of parameters are global parameters, and are configurable in the shared-plane:
•
•
•
•
•
•
The next set of parameters is configurable on a per-port basis:
•
•
•
•
•
Per-port configuration is entered in an interface submode within the MST configuration submode. This model is similar to the IS-IS and OSPF configuration models, and keeps all the relevant configuration in one place.
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
DETAILED STEPS
Configuring MSTAG
Two aspects of the configuration required for MSTP on nPE.
First, the standard L2VPN configuration required to forward the appropriate BPDUs to all appropriate egress ports.
Second, the configuration required in order to enable MSTAG on the appropriate ports.
The following items are configurable on per-port basis:
•
•
•
•
•
•
SUMMARY STEPS
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
DETAILED STEPS
MSTP Command Reference
This module describes the Cisco IOS XR commands used to configure the MSTP interfaces on the Cisco ASR 9000 Series Router.
spanning-tree mst
To enter the MSTP configuration submode, use the spanning-tree mst command in global configuration mode.
spanning-tree mst protocol instance identifier
Syntax Description
protocol instance identifier
String of a maximum of 25 characters that identifies the protocol instance.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enter the MSTP configuration submode:
RP/0/RSP0/CPU0:PE44_ASR-9010(config)# spanning-tree mst aRP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)#name
To set the name of the MSTP region, use the name command in MSTP configuration submode.
name name
Syntax Description
Defaults
The MAC address of the switch, formatted as a text string using the hexadecimal representation specified in IEEE Std 802.
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the name of the MSTP region to m1:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# name m1revision
To set the revision level of the MSTP region, use the revision command in MSTP configuration submode.
revision revision-number
Syntax Description
Defaults
revision-number: 0
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the revision level of the MSTP region to 10:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# revision 10forward-delay
To set the forward-delay parameter for the bridge, use the forward-delay command in MSTP configuration submode.
forward-delay seconds
Syntax Description
Defaults
seconds: 15
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the forward-delay parameter for the bridge to 20:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# forward-delay 20maximum
To set the maximum age and maximum hops performance parameters for the bridge, use the maximum command in MSTP configuration submode.
maximum {age seconds | hops hops}
Syntax Description
seconds
Maximum age time for the bridge in seconds. Range is 6 to 40.
hops
Maximum number of hops for the bridge in seconds. Range is 6 to 40.
Defaults
seconds: 20, hops: 20
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the maximum age time for the bridge to 40:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# max age 40The following example shows how to set the maximum number of hops for the bridge to 30:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# max hops 30transmit hold-count
To set the transmit hold count performance parameter, use the transmit hold-count command in MSTP configuration submode.
transmit hold-count count
Syntax Description
Defaults
count: 6
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the bridge transmit hold-count parameter to 8:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# transmit hold-count 8provider-bridge
To place the current instantiation of the protocol to 802.1ad mode, use the provider-bridge command in MSTP configuration submode.
provider-bridge
Syntax Description
This command has no arguments or keywords.
Defaults
Default value is FALSE.
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to use the provider-bridge command:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# provider-bridgeinstance
To enter the MSTI configuration submode, use the instance command in MSTP configuration submode.
instance id
Syntax Description
Defaults
No default behavior or values
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Note
Task ID
Examples
The following example shows how to enter the MSTI configuration submode:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# instance 101RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-inst)#priority
To set the bridge priority for the current MSTI, use the priority command in MSTI configuration submode.
priority priority
Syntax Description
Defaults
priority: 32768
Command Modes
MSTI configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the bridge priority to 8192 for the current MSTI:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-inst)# priority 8192vlan-id
To associate a set of VLAN IDs with the current MSTI, use the vlan-id command in MSTI configuration submode.
vlan-id vlan-range [,vlan-range] [,vlan-range] [,vlan-range]
Syntax Description
Defaults
No default behavior or values
Command Modes
MSTI configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to use the vlan-id command:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-inst)# vlan-id 2-1005interface
To enter the MSTP interface configuration submode, and to enable STP for the specified port, use the interface command in MSTP configuration submode.
interface {GigabitEthernet | TenGigE | FastEthernet} instance
Syntax Description
Defaults
No default behavior or values
Command Modes
MSTP configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enter the MSTP interface configuration submode:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp)# interface FastEthernet 0/0/0/1RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)#instance port-priority
To set the port priority performance parameter for the MSTI, use the instance port-priority command in MSTP interface configuration submode.
instance id port-priority priority
Syntax Description
Defaults
priority: 128
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Note
Task ID
Examples
The following example shows how to set the port priority to 160 for the instance id 101:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# instance 101 port-priority 160instance cost
To set the internal path cost for a given instance on the current port, use the instance cost command in MSTP interface configuration submode.
instance id cost cost
Syntax Description
Defaults
Default path cost depends on the speed of the link.
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the port cost to 10000 for the instance id 101:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# instance 101 cost 10000external-cost
To set the external path cost on the current port, use the external-cost command in MSTP interface configuration submode.
external-cost cost
Syntax Description
Defaults
Default path cost depends on the speed of the link.
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the external cost to 10000:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# external-cost 10000link-type
To set the link type of the port to point-to-point or multipoint, use the link-type command in MSTP interface configuration submode.
link-type {point-to-point | multi-point}
Syntax Description
This command has no arguments.
Defaults
The default value is derived from the duplexity of the link. A full-duplex link is considered point-to-point, while all others are considered multipoint.
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the link type of the port to point-to-point link:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# link-type point-to-pointhello-time
To set the port hello-time, use the hello-time command in MSTP interface configuration submode.
hello-time seconds
Syntax Description
Defaults
seconds: 2
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the port hello-time to 1:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# hello-time 1portfast
To enable PortFast on the port, and optionally enable BPDU guard, use the portfast command in MSTP interface configuration submode.
portfast [bpduguard]
Syntax Description
This command has no arguments.
Defaults
PortFast is disabled.
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enable PortFast and BPDU guard on the port:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# portfastRP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# portfast bpduguardguard root
To enable RootGuard on the port, use the guard root command in MSTP interface configuration submode.
guard root
Syntax Description
This command has no arguments or keywords.
Defaults
RootGuard is disabled.
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enable RootGuard on the port:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# guard rootguard topology-change
To enable TopologyChangeGuard on the port, use the guard topology-change command in MSTP interface configuration submode.
guard topology-change
Syntax Description
This command has no arguments or keywords.
Defaults
TopologyChangeGuard is disabled.
Command Modes
MSTP interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enable TopologyChangeGuard on the port:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-mstp-if)# guard topology-changeshow spanning-tree mst
To display the multiple spanning tree protocol status and configuration information, use the show spanning-tree mst command in EXEC mode. It also includes interface information about that interface which applies to all MSTIs:
•
•
•
•
•
•
•
and information specific to each MSTI:
•
•
•
•
show spanning-tree mst protocol instance identifier [interface {FastEthernet | GigabitEthernet | TenGigE} [instance msti]] | [instance msti] | [brief] | [blocked-ports] | [errors] | [configuration] | [bpdu interface {FastEthernet | GigabitEthernet | TenGigE} [direction {receive | transmit}]]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows the output from the show spanning-tree mst command, which produces an overview of the spanning tree protocol state:
# show spanning-tree mst a instance 0Operating in Provider Bridge modeMSTI 0 (CIST):VLANS Mapped: 1-100, 500-1000, 1017Root ID Priority 4097Address 0004.9b78.0800This bridge is the rootHello Time 2 sec Max Age 20 sec Forward Delay 15 secBridge ID Priority 4097 (priority 4096 sys-id-ext 1)Address 0004.9b78.0800Hello Time 2 sec Max Age 20 sec Forward Delay 15 secInterface Port ID Designated Port IDName Prio.Nbr Cost Role State Cost Bridge ID Prio.Nbr---------------------- -------- ------ --------- ------------------------ --------GigabitEthernet0/1/2/1 128.65 20000 DSGN FWD 0 4097 0004.9b78.0800 128.65GigabitEthernet0/1/2/2 128.66 20000 DSGN FWD 0 4097 0004.9b78.0800 128.66FastEthernet0/0/4/3 128.195 200000 DSGN FWD 0 4097 0004.9b78.0800 128.195FastEthernet0/0/4/4 128.196 200000 ALT BLK 0 4097 0004.9b78.0800 128.195...The following example shows the output from the show spanning-tree mst command while brief and blocked-ports keywords are used:
# show spanning-tree mst a briefMSTI 0 (CIST):VLAN IDs: 1-100, 500-1000, 1017This is the Root BridgeMSTI 1:VLAN IDS: 101-499Root Port GigabitEthernet0/1/2/2 , Root Bridge ID 0002.9b78.0812...# show spanning-tree mst blocked-portsMSTI 0 (CIST):Interface Port ID Designated Port IDName Prio.Nbr Cost Role State Cost Bridge ID Prio.Nbr---------------------- -------- ------ --------- ------------------------ --------FastEthernet0/0/4/4 128.196 200000 ALT BLK 0 4097 0004.9b78.0800 128.195...The following example shows the output from the show spanning-tree mst command, which produces more detailed information regarding interface state than the standard command as described above:
# show spanning-tree mst a interface GigabitEthernet0/1/2/1 instance 3GigabitEthernet0/1/2/1Cost: 20000link-type: point-to-pointhello-time 1Portfast: noBPDU Guard: noGuard root: noGuard topology change: noBPDUs sent 492, received 3MST 3:Edge port:Boundary : internalDesignated forwardingVlans mapped to MST 3: 1-2,4-2999,4000-4094Port info port id 128.193 cost 200000Designated root address 0050.3e66.d000 priority 8193 cost 20004Designated bridge address 0002.172c.f400 priority 49152 port id 128.193Timers: message expires in 0 sec, forward delay 0, forward transitions 1Transitions to reach this state: 12The following example shows the output from the show spanning-tree mst command, which produces information about which configured interfaces have not had MSTP enabled on them, and the reason why. Primarily this will show information about interfaces which do not exist:
# show spanning-tree mst a errorsInterface Error-------------------------------FastEthernet0/0/4/7 Interface does not exist.GigabitEthernet1/2/3/4 Interface does not exist.The following example shows the output from the show spanning-tree mst command, which displays the VLAN ID to MSTI mapping table:
# show spanning-tree mst a configurationName leoRevision 2702Config Digest 9D-14-5C-26-7D-BE-9F-B5-D8-93-44-1B-E3-BA-08-CEInstance Vlans mapped-------- -------------------------------0 1-9,11-19,21-29,31-39,41-40941 10,20,30,40------------------------------------------The following example shows the output from the show spanning-tree mst command, which produces details on the BPDUs being output and received on a given local interface:
Note
# show spanning-tree mst a bpdu interface GigabitEthernet0/1/2/2 direction transmitMSTI 0 (CIST):Root ID : 0004.9b78.0800Path Cost : 83Bridge ID : 0004.9b78.0800Port ID : 12Hello Time : 2...MSTAG Command Reference
This module describes the Cisco IOS XR commands used to configure the MSTAG interfaces on the Cisco ASR 9000 Series Router.
spanning-tree ring-termination
To enter the ring-termination configuration submode, use the spanning-tree ring-termination command in global configuration mode.
spanning-tree ring-termination protocol instance identifier
Syntax Description
protocol instance identifier
String of a maximum of 25 characters that identifies the protocol instance.
Defaults
No default behavior or values
Command Modes
Global configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Note
Task ID
Examples
The following example shows how to enter the ring-termination configuration submode:
RP/0/RSP0/CPU0:PE44_ASR-9010(config)# spanning-tree ring-termination aRP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp)#interface
To enter the MSTAG interface configuration submode, and to enable MSTAG for the specified port, use the interface command in MSTAG configuration submode.
interface {GigabitEthernet | TenGigE | FastEthernet} instance.subinterface
Syntax Description
Defaults
No default behavior or values
Command Modes
MSTAG configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enter the MSTAG interface configuration submode:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp)# interface GigabitEthernet0/2/0/30.1RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)#name
To set the name of the MSTP region, use the name command in MSTAG interface configuration submode.
name name
Syntax Description
Defaults
The MAC address of the switch, formatted as a text string using the hexadecimal representation specified in IEEE Std 802.
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the name of the MSTP region to leo:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# name leorevision
To set the revision level of the MSTP region, use the revision command in MSTAG interface configuration submode.
revision revision-number
Syntax Description
Defaults
revision-number: 0
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the revision level of the MSTP region to 1:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# revision 1max age
To set the maximum age performance parameters for the bridge, use the max age command in MSTAG interface configuration submode.
max age seconds
Syntax Description
Defaults
seconds: 20
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the maximum age time for the bridge to 20:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# max age 20provider-bridge
To place the current instantiation of the protocol to 802.1ad mode, use the provider-bridge command in MSTAG interface configuration submode.
provider-bridge
Syntax Description
This command has no arguments or keywords.
Defaults
Default value is FALSE.
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to use the provider-bridge command:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# provider-bridgebridge-id
To set the bridge id for the current switch, use the bridge-id command in MSTAG interface configuration submode.
bridge-id id
Syntax Description
Defaults
The MAC address of the switch.
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the bridge id:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# bridge-id 001c.0000.0011port-id
To set the port id for the current switch, use the port-id command in MSTAG interface configuration submode.
port-id id
Syntax Description
Defaults
A unique value from the valid range allocated dynamically.
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the port id:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# port-id 111external-cost
To set the external path cost on the current port, use the external-cost command in MSTAG interface configuration submode.
external-cost cost
Syntax Description
Defaults
Default path cost depends on the speed of the link.
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the external cost to 10000:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# external-cost 10000hello-time
To set the port hello-time, use the hello-time command in MSTAG interface configuration submode.
hello-time seconds
Syntax Description
Defaults
seconds: 2
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the port hello-time to 1:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# hello-time 1instance
To enter the MSTI configuration submode, use the instance command in MSTAG interface configuration submode.
instance id
Syntax Description
Defaults
No default behavior or values
Command Modes
MSTAG interface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Note
Task ID
Examples
The following example shows how to enter the MSTI configuration submode:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if)# instance 1RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if-inst)#vlan-id
To associate a set of VLAN IDs with the current MSTI, use the vlan-id command in MSTAG interface instance configuration submode.
vlan-id vlan-range [,vlan-range] [,vlan-range] [,vlan-range]
Syntax Description
Defaults
No default behavior or values
Command Modes
MSTAG interface instance configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to use the vlan-id command:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if-inst)# vlan-id 2-1005priority
To set the bridge priority for the current MSTI, use the priority command in MSTAG interface instance configuration submode.
priority priority
Syntax Description
Defaults
priority: 32768
Command Modes
MSTAG interface instance configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the bridge priority to 4096 for the current MSTI:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if-inst)# priority 4096port-priority
To set the port priority performance parameter for the MSTI, use the port-priority command in MSTAG interface instance configuration submode.
port-priority priority
Syntax Description
Defaults
priority: 128
Command Modes
MSTAG interface instance configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Note
Task ID
Examples
The following example shows how to set the port priority to 160:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if-inst)# port-priority 160cost
To set the internal path cost for a given instance on the current port, use the cost command in MSTAG interface instance configuration submode.
cost cost
Syntax Description
Defaults
Default path cost depends on the speed of the link.
Command Modes
MSTAG interface instance configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the port cost to 10000:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if-inst)# cost 10000root-id
To set the root bridge id for the BPDUs sent from the current port, use the root-id command in MSTAG interface instance configuration submode.
root-id id
Syntax Description
Defaults
The Bridge ID of the current bridge.
Command Modes
MSTAG interface instance configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to set the root-id of the bridge:
RP/0/RSP0/CPU0:PE44_ASR-9010(config-rl2gp-if-inst)# root-id 001c.0000.0011Debug Commands
This module describes the debug commands used on MSTP interfaces on the Cisco ASR 9000 Series Router running Cisco IOS XR software.
debug spanning-tree mst packet
To turn on debugging of BPDUs, use the debug spanning-tree mst packet command in EXEC mode.
debug spanning-tree mst packet [brief | full | raw] [sent | received] [interface {FastEthernet | GigabitEthernet | TenGigE}] [location loc]
Syntax Description
brief
Minimal details of each packet, such as packet type, source or destination MAC address, etc.
full
Full decode of each packet
raw
Hex dump of each packet
Defaults
Default value is brief.
Command Modes
EXEC
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco ASR 9000 Series Aggregation Services Router.
Task ID
Examples
The following example shows how to turn on the debug messages for BPDUs:
RP/0/RSP0/CPU0:PE44_ASR-9010# debug spanning-tree mst packet full sentdebug spanning-tree mst protocol-state
To turn on debugging for protocol state changes such as port role or state changes, topology change notifications, use the debug spanning-tree mst protocol-state command in EXEC mode.
debug spanning-tree mst protocol-state [instance id]
Syntax Description
Defaults
No default behavior or values
Command Modes
EXEC
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Debugging output is assigned high priority in the CPU process and, therefore, can affect system performance. For more information about the impact on system performance when using debug commands, refer to Using Debug Commands on Cisco ASR 9000 Series Aggregation Services Router.
Task ID
Examples
The following example shows how to turn on the debug messages for protocol state changes:
RP/0/RSP0/CPU0:PE44_ASR-9010# debug spanning-tree mst protocol-state instance 101•
Cisco IOS XR Software Release 3.7.3 introduces EFP Egress Filtering on the Cisco ASR 9000 Series Router.
For more information on configuring the EFP Egress Filtering feature including the associated EFP Egress Filtering commands on the Cisco ASR 9000 Series router, refer to the Egress EFP Filtering on the Cisco ASR 9000 Series Router feature module below.
EFP Egress Filtering Feature Overview
An Ethernet flow point (EFP) represents a logical demarcation point of an Ethernet virtual connection (EVC) on an interface. That means, for an EVC associating two or more UNIs, there is a flow point on each interface of every device, through which that EVC passes.
An EFP serves four purposes:
•
•
•
•
A variety of operations can be performed on the traffic flows, when a router is configured with EFPs on various interfaces. Also, there are a number of means to bridge or tunnel the traffic from one or more of the router's ingress EFPs to one or more egress EFPs. This traffic is a mixture of VLAN IDs, single or double (QinQ) encapsulation, and ethertypes.
Figure 4 shows the EFP model:
Figure 4 EFP Model
An EFP subinterface is configured to specify which traffic on ingress will get vectored to that EFP. This is done by specifying a VLAN, range of VLANs, or QinQ tagging to match against on ingress. All traffic on ingress is compared to the matching criterion on each EFP, and is then processed by that EFP if a match occurs. The processing performed by an EFP can change VLAN IDs, add or remove VLAN tags, and change ethertypes. When this traffic is switched in a bridge domain or sent through a local tunnel, finally destined for an EFP on the same router, to be sent out that EFP's parent physical port. An ingress EFP is one in the same as an egress EFP. The router is configured in such a way that the traffic sent out an EFP matches that EFP's ingress matching criterion. It is also possible to configure a router in such a way that this does not occur, and there is no safeguard to prevent such mismatching egress EFP traffic from exiting the router.
The Cisco ASR 9000 Series Router allows for different VLANs on different ports within the same bridge domain. This allows a bridge to forward a packet out of a port not configured for the VLAN tag on the packet. Egress EFP filtering checks this and drops invalid packets at the egress port instead of sending it out the line.
The purpose of egress EFP filtering feature is to implement a means of filtering EFP egress traffic, insuring that all the egress traffic on a given EFP complies with the ingress matching criterion.
Requirements for Egress EFP Filtering on Cisco ASR 9000 Series Router
EFPs use the same container object as Layer 2 subinterfaces, but offer a more flexible match and rewrite semantics. The requirements are categorized into following three categories:
•
•
Identifying Frames of a Service Instance
The EFP identifies frames belonging to a particular flow on a given port, independent of their Ethernet encapsulation. An EFP can flexibly map frames into a flow or service instance based on the fields in the frame header.
The frames can be matched to an EFP using:
•
•
•
•
•
•
The frames can not be matched to an EFP using any of the following:
•
–
–
•
The specific match criteria are covered in more details in the following sections:
VLAN Tag Matching
Table 5 describes the different encapsulation types and the native service identifier corresponding to each.
It is possible to use wildcards, as well as VLAN ranges when defining frames that map to a given EFP. EFPs can distinguish flows based on a single VLAN tag, a range of VLAN tags, a stack of VLAN tags or a combination of both (VLAN stack with wildcards). It provides the EFP model, a flexibility of being encapsulation agnostic, and allows it to be extensible as new tagging or tunneling schemes added.
MAC Address Matching
Either the source MAC address, destination MAC address, or both MAC addresses can be matched. In all cases, the MAC address requires an exact match. A wildcard match or partial match is not required.
802.1p CoS Bits Matching
A list of one or more exact CoS matches is specified. Since, CoS is only 3 bits, this limits it to 8 possible choices.
Logical Conjunction
All of the match criteria above can selectively be combined together to match those frames that match all of the separate criteria.
Default Match
A single EFP can be defined that matches all other traffic that has not been matched by a more specific EFP.
Match Precedence and Config Verification
Overlapping EFPs are allowed to be configured, where it is possible to determine an order in which they should be used for matching. But EFPs that conflict with other EFPs or subinterfaces on the parent trunk interface should be blocked at config verification.
To support this, an ordering precedence for how EFP matches are applied in hardware is used. The model is for most specific matches to be processed before less specific matches.
Egress Behavior
The EFP matching criteria can also be used on egress to police the frames that can egress out of the EFP, depending on platform support. Frames that do not match the criteria (source/destination MAC match criteria are reversed) are dropped.
Applying Features
After the frames are matched to a particular EFP, any appropriate features can be applied. In this context, `features' means any frame manipulations specified by the configuration as well as things such as QoS and ACLs. The Ethernet infrastructure provides an appropriate interface to allow the feature owners to apply their features to an EFP. Hence, IM interface handles are used to represent EFPs, allowing feature owners to manage their features on EFPs in the same way the features are managed on regular interfaces or subinterfaces.
The only Layer 2 features that can be applied on an EFP that is part of the Ethernet infrastructure are the Layer 2 header encapsulation modifications. These features are described in the following section:
Encapsulation Modifications
EFP supports various Layer 2 header encapsulation modifications on both ingress and egress. The following manipulations are supported on both ingress and egress:
•
•
Note
•
–
–
–
–
For each of the VLAN id manipulations, the following can be specified:
•
•
Note
Defining Data-Forwarding Behavior
The EFP can be used to designate the frames belonging to a particular Ethernet flow, to be forwarded in the data-path. The following forwarding cases are supported for EFPs in Cisco IOS XR software:
•
–
–
•
–
•
–
–
•
Configuring Egress EFP Filtering on the Cisco ASR 9000 Series Router
This section describes the procedures for configuring the egress EFP filtering feature on the Cisco ASR 9000 Series Router.
Egress EFP filtering is an Layer 2 subinterface specific feature that controls how strictly subinterface encapsulation filtering is performed in the egress direction.
According to the EFP behavior and model, all packets transmitted out of a subinterface should match the subinterface encapsulation or rewrite criteria if the same packet to be received on the subinterface (with the source and destination MAC addresses swapped).
By using the ethernet egress-filter command, you can configure egress EFP filtering in either global or Layer 2 subinterface mode as follows:
•
•
SUMMARY STEPS
1.
2.
Or
interface {GigabitEthernet | TenGigE | FastEthernet | Bundle-Ether} instance.subinterface
ethernet egress-filter {strict | disabled}
3.
DETAILED STEPS
Command Reference
This module describes the Cisco IOS XR command used to configure the Egress EFP Filtering feature on the Cisco ASR 9000 Series Router.
Syntax Descriptionethernet egress-filter
To enable strict egress filtering on all subinterfaces on the device by default, use the ethernet egress-filter command in global configuration mode.
ethernet egress-filter strict
To enable or disable egress filtering explicitly on any Layer 2 subinterface, use the ethernet egress-filter command in Layer 2 subinterface mode.
ethernet egress-filter {strict | disabled}
Syntax Description
Defaults
For platforms that support this command, the global default is that subinterface egress encapsulation filtering is disabled.
Command Modes
Global configuration and Layer 2 subinterface configuration
Command History
Release 3.7.3
This command was first introduced on the Cisco ASR 9000 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 assistance.
Task ID
Examples
The following example shows how to enable the strict egress filtering on all subinterfaces in global configuration mode:
RP/0/RSP0/CPU0:PE44_ASR-9010# configThu Jun 4 07:50:02.660 PSTRP/0/RSP0/CPU0:PE44_ASR-9010(config)#RP/0/RSP0/CPU0:PE44_ASR-9010(config)# ethernet egress-filter strictThe following example shows how to enable the strict egress filtering on any Layer 2 subinterface in Layer 2 subinterface mode:
RP/0/RSP0/CPU0:PE44_ASR-9010# configThu Jun 4 07:50:02.660 PSTRP/0/RSP0/CPU0:PE44_ASR-9010(config)#RP/0/RSP0/CPU0:PE44_ASR-9010(config)# interface GigabitEthernet 0/1/0/1.1RP/0/RSP0/CPU0:PE44_ASR-9010(config-subif)#RP/0/RSP0/CPU0:PE44_ASR-9010(config-subif)# ethernet egress-filter strict•
In prior releases the Cisco ASR 9000 Series Router acting as a bridge flooded broadcast and unknown unicast traffic to all the forwarding engines on all the linecards.
Command syntax:
RP/0/RSP0/CPU0:router# configureRP/0/RSP0/CPU0:router(config)# l2vpnRP/0/RSP0/CPU0:router(config-l2vpn)# bridge group xxxRP/0/RSP0/CPU0:router(config-l2vpn-bg)# bridge-domain yyyRP/0/RSP0/CPU0:router(config-l2vpn-bg-bd)# flood mode convergence-optimizedIn Cisco IOS XR Software Release 3.7.2 if a pseudowire is configured in a bridge domain all broadcast and unknown unicast traffic is flooded to all line cards in the system in order to attain fast convergence. With Cisco IOS XR Software Release 3.7.3 the flood optimization feature changes this default behavior. FGID will get programmed based on the primary paths on which the pseudowire is going out and traffic will get flooded only to the line cards on which the pseudowire resides. This mode is called Bandwidth Optimization mode.
But if an Fast ReRoute event occurs when fast convergence is set up it will take a longer time to complete the reroute as more hardware programming such as adding bridge ports etc. needs to be done. So for customers who are sensitive to this increased delay a command called flood mode convergence-optimized is provided in Cisco IOS XR Software Release 3.7.3. Use this flood mode convergence-optimized command to switch back to the convergence optimized mode where traffic gets flooded to all the line cards.
With this flood mode convergence-optimized command users are able to turn on/off the bandwidth optimized mode.
flood mode convergence-optimized (VPLS)
This command allows users to configure flooding into convergence optimized mode where traffic gets flooded to all the line cards. To configure flooding into convergence optimized mode (all unknown unicast packets, all broadcast packets, and all multicast packets are flooded over all other bridge domain network interfaces), use the flood mode convergence-optimized command in l2vpn bridge group bridge domain configuration mode. To return the bridge to normal flooding behavior when all unknown unicast packets, all broadcast packets, and all multicast packets are flooded over all other bridge domain network interfaces, use the no form of this command.
flood mode convergence-optimized
no flood mode convergence-optimized
Syntax Description
This command has no arguments or keywords.
Defaults
The default behavior is that packets are flooded when their destination MAC address is not found.
Command Modes
l2vpn bridge group bridge domain 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 for assistance.
Use the flood mode convergence-optimized command to override the parent bridge configuration.
By default, bridge ports inherit the flooding behavior of the bridge domain.
When flooding is configured into convergence optimized mode, all unknown unicast packets, all broadcast packets, and all multicast packets are flooded over all other bridge domain network interfaces.
Task ID
Examples
The following example shows how to disable flooding on the bridge domain called bar:
RP/0/RSP0/CPU0:router# configureRP/0/RSP0/CPU0:router(config)# l2vpnRP/0/RSP0/CPU0:router(config-l2vpn)# bridge group 1RP/0/RSP0/CPU0:router(config-l2vpn-bg)# bridge-domain barRP/0/RSP0/CPU0:router(config-l2vpn-bg-bd)# flood mode convergence-optimizedRelated Commands
For more information on the flooding disable command and other Layer 2 VPLS commands on the Cisco ASR 9000 Series router, refer to the Multipoint Layer 2 Bridging Services (VPLS) Commands on Cisco ASR 9000 Series Routers section in the Cisco ASR 9000 Series Aggregation Services Router MPLS Command Reference here:
http://www.cisco.com/en/US/docs/routers/asr9000/software/mpls/command/reference/grasr9kvpls.html
•
In Cisco IOS XR software Release 3.7.3 as part of pseudowire flood optimization, the Layer 3 interface list for a pseudowire is now based on Virtual Connection labels. By using ECMP Link Bundle hashing, the Layer 3 interface list for a pseudowire can be condensed to a single Layer 3 interface. This Layer 3 interface (slot and network protocol flood mask) is derived from the ordered array of Layer 3 interface list (masks).
•
Cisco IOS XR software Release 3.7.3 adds support for the Early Fast Discard command. This command was added to process all high priority packets
Command syntax:
(config)# hw-module location <loc> early-fast-discard(config-early-fast-discard)# mode [outer-encap-only | include-inner-encap](config-early-fast-discard)# vlan-cos <0-8> vlan-op [lt | ge]The defaults are 6 and ge (greater than or equal to)(config-early-fast-discard)# ip-prec <0-8> ip-op [lt | ge]The defaults are 6 and ge (greater than or equal to)(config-early-fast-discard)# mpls-exp <0-8> mpls-op [lt | ge]The defaults are 6 and ge (greater than or equal to)(config)# no hw-module location <loc> early-fast-discard•
Cisco IOS XR software Release 3.7.3 adds support for the user to override the Power Management feature in order to configure extra line cards without full power supply redundancy.
This feature allows a card to be forced to power up, regardless of an unprogrammed EEPROM power draw value. As with the ROMMON variable, this feature is intended for temporary use. After the cookie value has been programmed, remove this configuration by repeating the CLI command with the ''no'' option.
Command example:
RP/0/RSP0/CPU0:ios(admin-config)# hw-mod power override location <loc>•
Starting with Cisco IOS XR software Release 3.7.3, mrouter and membership states on the Cisco ASR 9000 Series Router no longer need to be relearned after a port goes down. Once a port goes down, the IGMP Snooping feature immediately removes all group membership states from that port. Once an mrouter port goes down, the IGMP Snooping feature removes the port from the list of mrouter ports and removes that port from the flood set of all multicast routes.
New CLI:
tcn_relearning [cisco | rfc4541 | none]
For more information on the IGMP Snooping feature on the Cisco ASR 9000 Series router, refer to the Implementing Layer 2 Multicast using IGMP Snooping on Cisco ASR 9000 Series Routers section in the Cisco ASR 9000 Series Aggregation Services Router Multicast Configuration Guide here:
•
Cisco IOS XR software Release 3.7.3 improves the Cisco ASR 9000 Series Router VRRP & FRR failover time after a hardware module reload to less than or equal to one second.
•
Layer 2 VPNs can provide pseudowire resiliency through their routing protocols. When the connectivity between end-to-end PE routers fails, an alternative path to the directed LDP session and the user data takes over. With Cisco IOS XR software Release 3.7.3, the user can fall-back to the preferred path once it has been restored.
•
•
RP/0/RSP0/CPU0:Green_RO(admin)#show environment power-supplyThu Jul 23 17:01:08.829 pstR/S/I Modules Sensor Watts Status0/PM0/*host PM 3000 Ok0/PM1/*host PM 3000 Ok0/PM4/*host PM 3000 Ok0/PM5/*host PM 3000 OkPower Shelves Type: ACTotal Power Capacity: 12000WUsable Power Capacity: 9000WSupply Failure Protected Capacity: 9000WFeed Failure Protected Capacity: 6000WWorst Case Power Used: 3010WSlot Max Watts---- ---------0/0/CPU0 3750/1/CPU0 3950/RSP0/CPU0 2500/RSP1/CPU0 2500/4/CPU0 3750/6/CPU0 3750/FT0/SP 495 (default)0/FT1/SP 495 (default)Worst Case Power Available: 5990WSupply Protected Capacity Available: 5990WFeed Protected Capacity Available: 2990WFeatures Introduced on the Cisco ASR 9000 Series Router Platform With Cisco IOS XR Software Release 3.7.2
Cisco IOS XR Software Release 3.7.2 introduced support for the following features on the Cisco ASR 9000 Series Router platform:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Important Notes
For Cisco IOS XR Software Release 3.7.3, the Cisco ASR 9000 Series Router does not support the following inventory schemas:
–
–
–
•
•
•
•
•
Limitations
The Cisco IOS XR software Release 3.7.3 Traffic Engineering/Fast ReRoute features will not reroute Layer 2VPN flood, unknown unicast, multicast or broadcast traffic in under 50ms.
Cisco ASR 9000 Series Routers running Cisco IOS XR software Release 3.7.2 or Cisco IOS XR software Release 3.7.3 with large configurations (32K CFM Maintenance points on 32K EFPs and 8K L2vpn Bridge domains) will occasionally remain in MBI BOOTING stage. The workaround is to reload the line card again.
The Cisco ASR 9000 Series Router running Cisco IOS XR software Release 3.7.2 or Cisco IOS XR software Release 3.7.3 does not support the GRE protocol.
Mixing port level MAC learn limits and a bridge-wide MAC learn limit on the same bridge domain is not supported on Cisco ASR 9000 Series Routers. When a MAC limit is configured on a bridge port, MAC addresses learnt on the bridge port are counted against the bridge port only and not against the bridge's bridge-wide MAC limit.
For the Cisco ASR 9000 Series Router running Cisco IOS XR software Release 3.7.3, packet loss may be observed during TE tunnel reoptimization for Layer 2VPN flood and multicast traffic types.
With the Cisco ASR 9000 Series Router running Cisco IOS XR software Release 3.7.3, the bridge-domain name length has been reduced from 32 characters to 27 characters.
For the Cisco ASR 9000 Series Router running Cisco IOS XR software Release 3.7.3 or Cisco IOS XR software Release 3.7.2, configuring an EFP sub-interface with "encapsulation default" breaks Layer 3 functionality at the main interface.
With the Cisco ASR 9000 Series Router running Cisco IOS XR software Release 3.7.3 and beyond, the Attachment Circuit to VLAN (type4) pseudowire does not work properly under certain rewrite conditions, usually accompanied by the following config commit error:
4 PW causes unsupported num tag pops on egress AC'
This error message does not always appear when expected. Sometimes the pseudowire comes up, but the error message does not appear until the interface is reconfigured or a process is restarted.
Caveats
Caveats describe unexpected behavior in Cisco IOS XR software releases. Severity-1 caveats are the most serious caveats; severity-2 caveats are less serious.
This section lists the caveats for Cisco ASR 9000 Series Router Software Release 3.7.3 and the Cisco ASR 9000 Series platform.
Open Cisco IOS XR Software Caveats
The following open caveats apply to Release 3.7.3 of the Cisco IOS XR software:
Open Caveats Specific to the Cisco ASR 9000 Series Router
The following open caveats are specific to the Cisco ASR 9000 Series platform:
•
Basic Description:
3.7.3:stp_io process crash on LC on replacing config with empty config
Symptom:
The stp_io process crashes on all the LC's. The crash decode points to unconfiguration of MSTP access gateway (a.k.a R-L2GP).
Conditions:
Commit replace an existing full configuration with an empty configuration.
Workaround:
None.
•
Basic Description:
Standby RSP reboots with KD during Image upgrade
Symptoms:
The standby RSP generates a kernel dump (not a crash) during Install mini pie upgrade.
Condition:
The problem is seen when upgrading the software (comp-asr9k-mini.pie) using the install activate command.
Workaround:
The user can upgrade to the new version of the software doing a fresh turboboot with the new software version.
Further Problem Description:
During an Install reload upgrade to a new version of the software Install helper sets the standby not ready flag and then reboots the active RSP. This results in a failover to the standby which is not ready. This in turn triggers the redundancy controller (Redcon) process to reboot the standby RSP with a kernel dump. The root cause of the problem is Install helper setting the standby not ready flag during the upgrade.
Resolved Cisco IOS XR Software Release 3.7.2 Caveats
The following open caveats from Release 3.7.2 have been resolved in Release 3.7.3 of the Cisco IOS XR software:
•
•
•
•
•
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. Refer to Table 1 for a list of the Cisco ASR 9000 Series Router software feature set matrix (PIE files) and associated filenames available for the Cisco IOS XR Software Release 3.7.3 supported on the Cisco ASR 9000 Series Router.
The following section contains information about how to upgrade Cisco IOS XR software.
Note
Upgrading from IOS XR 3.7.2 to IOS XR 3.7.3
Note
Step 1
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install add <source>/<path>/<pie> sync
Note
The above step must be repeated for each PIE file, or all of the PIEs can be added together in a single install add .. command.
To add all PIEs using a single command, list all of the PIEs (including their source) within the install add .. command in the following manner:
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install add <source>/comp-asr9k-mini.pie-3.7.3<source>/asr9k-mcast-p.pie-3.7.3 <source>/asr9k-mgbl-p.pie-3.7.3<source>/asr9k-mpls-p.pie-3.7.3 <source>/asr9k-k9sec-p.pie-3.7.3disk0:asr9k-fpd-3.7.3 sync
Note
The variable source can be specified just once rather than for each package. This simplifies the command:
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install add source <source_path> comp-asr9k-mini.pie-3.7.3 asr9k-mcastp. pie-3.7.3 asr9k-mgbl-p.pie-3.7.3 asr9k-mpls-p.pie-3.7.3 asr9k-k9sec-p.pie-3.7.3 sync
Note
Note
Step 2
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install activate disk0:comp-asr9k-mini-3.7.3 disk0:asr9k-mcast- 3.7.3 disk0:asr9k-mgbl-3.7.3 disk0:asr9k-k9sec-3.7.3 disk0:asr9k-mpls-3.7.3 disk0:asr9k-fpd-3.7.3 sync test
Note
Step 3
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install activate disk0:comp-asr9k-mini-3.7.3 disk0:asr9k-mcast- 3.7.3 disk0:asr9k-mgbl-3.7.3 disk0:asr9k-k9sec-3.7.3 disk0:asr9k-mpls-3.7.3 disk0:asr9k-fpd-3.7.3 sync
Note
Note
Note
Note
Note
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install activate *3.7.3*Step 4
–
–
–
If system issues are detected or if the upgrade needs to be backed out for any reason, please follow the steps described in the Downgrade section to rollback the software configuration.
Step 5
To fix the failed configurations, browse both the admin and non-admin failed configuration, address syntax and semantics errors and re-apply the failed configuration as required.
To display the failed configurations, execute the following command in both admin and non-admin mode:
RP/0/RSP0/CPU0:PE44_ASR-9010# show config failed startuporRP/0/RSP0/CPU0:PE44_ASR-9010(admin)# show config failed startupStep 6
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install commit
Note
Note
Note
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install add tar <source>/<path>/<tar_file> syncFrom release 3.7 onward PIE files can also be activated using the install activate id command. The install operation ID is generated after each install command:
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install activate id <install_operation_id> syncThe install operation ID can also be obtained by executing the show install log command.
After activating the 3.7.3 packages by executing the install activate <3.7.3 packages> command, commit the new software, if there is no issue in router functionality, by executing the install commit command.
Upgrading Firmware
After running the install commit command, run the show hw-module fpd location all command to check which FPGA/ROMMON/CPLD files need to be upgraded. The following is a sample show hw-module fpd location all command display:
RP/0/RSP0/CPU0:router(admin)# sh hw-module fpd location all===================================== ==========================================Existing Field Programmable Devices==========================================HW Current SW Upg/Location Card Type Version Type Subtype Inst Version Dng?============ ======================== ======= ==== ======= ==== =========== ====0/RSP0/CPU0 A9K-RSP-4G 4.8 lc fpga3 0 1.13 Nolc fpga 0 1.4 Nolc fpga2 0 1.14 Nolc cbc 0 1.1 Yeslc fpga4 0 1.6 Nolc hsbi 0 1.0 Nolc rommon 0 1.0 No--------------------------------------------------------------------------------0/RSP0/CPU0 ASR-9006-FAN 1.0 lc cbc 1 5.0 No--------------------------------------------------------------------------------0/RSP0/CPU0 ASR-9006-FAN 1.0 lc cbc 2 5.0 No--------------------------------------------------------------------------------0/RSP1/CPU0 A9K-RSP-4G 5.0 lc fpga3 0 1.13 Nolc fpga 0 1.4 Nolc fpga2 0 1.14 Nolc cbc 0 1.1 Yeslc fpga4 0 1.6 Nolc hsbi 0 1.0 Nolc rommon 0 1.0 No--------------------------------------------------------------------------------0/1/CPU0 A9K-40GE-E 1.0 lc fpga 0 0.38 Nolc fpga2 0 0.8 Nolc cbc 0 2.1 Yeslc hsbi 0 1.0 Nolc cpld1 0 0.15 Nolc rommon 0 1.0 No--------------------------------------------------------------------------------0/1/CPU0 A9K-40GE-E 1.0 lc fpga 1 0.38 No--------------------------------------------------------------------------------NOTES:1. One or more FPD needs an upgrade or a downgrade. This can be accomplishedusing the ''admin upgrade hw-module fpd'' CLI.RP/0/RSP0/CPU0:router(admin)#In the example above, the CBC firmware needs to be upgraded (from version 2.1 to version 2.2).
Note
Since the 3.7.3 FPD PIE was already installed and activated with the install activate and install commit commands during the upgrade, issue the following command to check the latest versions of all FPGA/ROMMON/CPLDs:
RP/0/RSP0/CPU0:router(admin)# sh fpd package=============================== ================================================Field Programmable Device Package================================================SW Min ReqCard Type FPD Description Type Subtype Version HW Vers==================== ========================== ==== ======= =========== =======A9K-40GE-B Can Bus Ctrl (CBC) LC2 lc cbc 2.2 0.1CPUCtrl LC2 lc cpld1 0.15 0.1PHYCtrl LC2 lc cpld2 0.6 0.1Issue the following command to upgrade the CBC:
RP/0/RSP0/CPU0:router(admin)# upgrade hw-module fpd cbc location allVerify the upgrade by executing the show hw-module fpd location all command.
Note
Rollback from 3.7.3 to 3.7.2
Before actually preforming the rollback to the prior release of software, use the show install rollback command to display the software set associated with a saved installation point.
Step 1
RP/0/RSP0/CPU0:router(admin)# show install rollback ?
0 ID of the rollback point to show package information for
2 ID of the rollback point to show package information for
Step 2
RP/0/RSP0/CPU0:router(admin)# show install rollback 0
Secure Domain Router: Owner
Node 0/1/SP [SP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/sp/mbiasr9k-sp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/1/CPU0 [LC] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/lc/mbiasr9k-lc.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/6/SP [SP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/sp/mbiasr9k-sp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/6/CPU0 [LC] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/lc/mbiasr9k-lc.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/RSP0/CPU0 [RSP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/mbiasr9k-rp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/RP1/CPU0 [RSP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/mbiasr9k-rp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/SM0/SP [SP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/sp/mbiasr9k-sp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/SM1/SP [SP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/sp/mbiasr9k-sp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/SM2/SP [SP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/sp/mbiasr9k-sp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Node 0/SM3/SP [SP] [SDR: Owner]
Boot Image: /disk0/asr9k-os-mbi-3.7.2/sp/mbiasr9k-sp.vm
Rollback Packages:
disk0:comp-asr9k-mini-3.7.2
Step 3
RP/0/RSP0/CPU0:router(admin)# install rollback to ?
0 Specify the id for the install point to rollback to
1 Specify the id for the install point to rollback to
12 Specify the id for the install point to rollback to
15 Specify the id for the install point to rollback to
2 Specify the id for the install point to rollback to
4 Specify the id for the install point to rollback to
6 Specify the id for the install point to rollback to
7 Specify the id for the install point to rollback to
8 Specify the id for the install point to rollback to
9 Specify the id for the install point to rollback to
committed Rollback to the last committed installation point
Step 4
RP/0/RSP0/CPU0:router(admin)# process shutdown sfe_drvr location allRP/0/RSP0/CPU0:router(admin)# install rollback to <point-id> sync testStep 5
RP/0/RSP0/CPU0:router(admin)# install rollback to <point-id> synchronous
Step 6
When a software configuration is committed with the install commit command, that configuration is also saved as the last committed installation point. Use the committed keyword for the point-id argument to roll back to the last committed installation point.
The following example shows how to roll back to a saved installation point:
RP/0/RSP0/CPU0:router# adminRP/0/RSP0/CPU0:router(admin)# install rollback to 8Install operation 10 'install rollback to 8' started by user 'user_b' at 07:49:26PST Sat Jul 18 2009.The install operation will continue asynchronously.RP/0/RSP0/CPU0:router(admin)#Info: The changes made to software configurations willnot be persistentInfo: across system reloads. Use the command 'admin install commit' to makeInfo: changes persistent.Info: Please verify that the system is consistent following the softwareInfo: change using the following commands:Info: show system verifyInfo: install verifyThe currently active software is the same as the committed software.Install operation 10 completed successfully at 07:51:24 PST Sat Jul 18 2009.Step 7
RP/0/RSP0/CPU0:PE44_ASR-9010(admin)# install commit
Troubleshooting
For information on troubleshooting Cisco IOS XR software, see the Cisco ASR 9000 Series Aggregation Services Routers Getting Started Guide and the Cisco ASR 9000 Series Router Troubleshooting Feature Module.
Resolving Upgrade File Issues
Note
a.
RP/0/RSP0/CPU0:PE44_ASR-9010# run nvgen -F 1b.
RP/0/RSP0/CPU0:PE44_ASR-9010# configRP/0/RSP0/CPU0:PE44_ASR-9010(config)# hostname <hostname>RP/0/RSP0/CPU0:PE44_ASR-9010(config)# commitRP/0/RSP0/CPU0:PE44_ASR-9010(config)# endc.
RP/0/RSP0/CPU0:PE44_ASR-9010# reloadUpdating Commit Database. Please wait...[OK]Proceed with reload? [confirm]d.
In some cases other activity may preclude a reload. The following message may display:
RP/0/RSP0/CPU0:PE44_ASR-9010# reloadPreparing system for backup. This may take a few minutes ............System configuration backup in progress [Retry later]If you receive this message wait and then retry the command after some time.
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 Lumin, Cisco Nexus, Cisco Nurse Connect, Cisco Stackpower, Cisco StadiumVision, Cisco TelePresence, Cisco Unified Computing System, Cisco WebEx, DCE, Flip Channels, Flip for Good, Flip Mino, Flip Video, Flip Video (Design), Flipshare (Design), Flip Ultra, and Welcome to the Human Network are trademarks; Changing the Way We Work, Live, Play, and Learn, Cisco Store, and Flip Gift Card are service marks; and Access Registrar, Aironet, AsyncOS, Bringing the Meeting To You, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, CCVP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Collaboration Without Limitation, EtherFast, EtherSwitch, Event Center, Fast Step, Follow Me Browsing, FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, iQuick Study, IronPort, the IronPort logo, LightStream, Linksys, MediaTone, MeetingPlace, MeetingPlace Chime Sound, MGX, Networkers, Networking Academy, Network Registrar, PCNow, PIX, PowerPanels, ProConnect, ScriptShare, SenderBase, SMARTnet, Spectrum Expert, StackWise, The Fastest Way to Increase Your Internet Quotient, TransPath, WebEx, and the WebEx logo are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0907R)
© 2009 Cisco Systems, Inc. All rights reserved.
Guest
