Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide Release 12.2 (18) SXF

Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide
Release 12.2(18)SXF and Rebuilds and Earlier Releases
Corporate Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 526-4100
Text Part Number: OL-3999-08
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCBs public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R)
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide, Release 12.2SXF and Rebuilds and Erarlier Releases 20012009, Cisco Systems, Inc. All rights reserved.
C O N T E N T S
Preface
30 30 30
Audience Conventions
Related Documentation
31 1
Product Overview User Interfaces
Supported Hardware and Software

1
Configuring Embedded CiscoView Support 2 Understanding Embedded CiscoView 2 Installing and Configuring Embedded CiscoView 2 Displaying Embedded CiscoView Information 3 Software Features Supported in Hardware by the PFC and DFC Command-Line Interfaces
1 3
Accessing the CLI 2 Accessing the CLI through the EIA/TIA-232 Console Interface Accessing the CLI through Telnet 2 Performing Command Line Processing Performing History Substitution Cisco IOS Command Modes Securing the CLI
6 7 1 4 5 4 3
Displaying a List of Cisco IOS Commands and Syntax ROM-Monitor Command-Line Interface Configuring the Switch for the First Time Default Configuration
2
Configuring the Switch 2 Using the Setup Facility or the setup Command 2 Using Configuration Mode 10 Checking the Running Configuration Before Saving 10 Saving the Running Configuration Settings 11
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide, Release 12.2SXF OL-3999-08
Contents
Reviewing the Configuration 11 Configuring a Default Gateway 12 Configuring a Static Route 12 Configuring a BOOTP Server 14 Protecting Access to Privileged EXEC Commands 15 Setting or Changing a Static Enable Password 15 Using the enable password and enable secret Commands 15 Setting or Changing a Line Password 16 Setting TACACS+ Password Protection for Privileged EXEC Mode Encrypting Passwords 17 Configuring Multiple Privilege Levels 17 Recovering a Lost Enable Password
19
16
Modifying the Supervisor Engine Startup Configuration 20 Understanding the Supervisor Engine Boot Configuration Configuring the Software Configuration Register 21 Specifying the Startup System Image 24 Understanding Flash Memory 24 CONFIG_FILE Environment Variable 25 Controlling Environment Variables 26 Configuring a Supervisor Engine 720
1 2
20
Using the Bootflash or Bootdisk on a Supervisor Engine 720 Using the Slots on a Supervisor Engine 720 Configuring Supervisor Engine 720 Ports
2 2
Configuring and Monitoring the Switch Fabric Functionality 2 Understanding How the Switch Fabric Functionality Works Configuring the Switch Fabric Functionality 4 Monitoring the Switch Fabric Functionality 4 Configuring a Supervisor Engine 32 Supervisor Engine 32 Ports
2 1 2
Flash Memory on a Supervisor Engine 32
Configuring the Supervisor Engine 2 and the Switch Fabric Module Using the Slots on a Supervisor Engine 2
1 2
Understanding How the Switch Fabric Module Works
Contents
Switch Fabric Module Overview 2 Switch Fabric Module Slots 2 Switch Fabric Redundancy 2 Forwarding Decisions for Layer 3-Switched Traffic Switching Modes 3 Configuring the Switch Fabric Module 3 Configuring the Switching Mode 4 Configuring Fabric-Required Mode 4 Configuring an LCD Message 5
Monitoring the Switch Fabric Module 5 Displaying the Module Information 7 Displaying the Switch Fabric Module Redundancy Status Displaying Fabric Channel Switching Modes 7 Displaying the Fabric Status 8 Displaying the Fabric Utilization 8 Displaying Fabric Errors 8 Configuring NSF with SSO Supervisor Engine Redundancy
Understanding NSF with SSO Supervisor Engine Redundancy 2 NSF with SSO Supervisor Engine Redundancy Overview 2 SSO Operation 3 NSF Operation 3 Cisco Express Forwarding 3 Multicast MLS NSF with SSO 4 Routing Protocols 4 NSF Benefits and Restrictions 8 Supervisor Engine Configuration Synchronization 9 Supervisor Engine Redundancy Guidelines and Restrictions 10 Redundancy Configuration Guidelines and Restrictions 10 Hardware Configuration Guidelines and Restrictions 10 Configuration Mode Restrictions 11 NSF Configuration Tasks 11 Configuring SSO 12 Configuring Multicast MLS NSF with SSO Verifying Multicast NSF with SSO 13 Configuring CEF NSF 13 Verifying CEF NSF 13 Configuring BGP NSF 14
12
Contents
Verifying BGP NSF 14 Configuring OSPF NSF 15 Verifying OSPF NSF 15 Configuring IS-IS NSF 16 Verifying IS-IS NSF 17 Configuring EIGRP NSF 19 Verifying EIGRP NSF 19 Synchronizing the Supervisor Engine Configurations Copying Files to the Redundant Supervisor Engine
20
20
Configuring RPR and RPR+ Supervisor Engine Redundancy Understanding RPR and RPR+ 2 Supervisor Engine Redundancy Overview 2 RPR Operation 2 RPR+ Operation 3 Supervisor Engine Configuration Synchronization
Supervisor Engine Redundancy Guidelines and Restrictions 4 Redundancy Guidelines and Restrictions 4 RPR+ Guidelines and Restrictions 5 Hardware Configuration Guidelines and Restrictions 5 Configuration Mode Restrictions 6 Configuring Supervisor Engine Redundancy 6 Configuring Redundancy 6 Synchronizing the Supervisor Engine Configurations Displaying the Redundancy States 7 Performing a Fast Software Upgrade Copying Files to an MSFC Configuring Interfaces
1 2 9 8
Understanding Interface Configuration Using the Interface Command

2 4
Configuring a Range of Interfaces
Defining and Using Interface-Range Macros
Configuring Optional Interface Features 6 Configuring Ethernet Interface Speed and Duplex Mode Configuring Jumbo Frame Support 10
Contents
Configuring IEEE 802.3x Flow Control Configuring the Port Debounce Timer Adding a Description for an Interface
13 15 16 16
Understanding Online Insertion and Removal Monitoring and Maintaining Interfaces 17 Monitoring Interface Status 17 Clearing Counters on an Interface 18 Resetting an Interface 18 Shutting Down and Restarting an Interface Checking the Cable Status Using the TDR
19
19
Configuring LAN Ports for Layer 2 Switching
Understanding How Layer 2 Switching Works 1 Understanding Layer 2 Ethernet Switching 2 Understanding VLAN Trunks 3 Layer 2 LAN Port Modes 4 Default Layer 2 LAN Interface Configuration
5 5
Layer 2 LAN Interface Configuration Guidelines and Restrictions Configuring LAN Interfaces for Layer 2 Switching 6 Configuring a LAN Port for Layer 2 Switching 7 Configuring a Layer 2 Switching Port as a Trunk 8 Configuring a LAN Interface as a Layer 2 Access Port 14 Configuring a Custom IEEE 802.1Q EtherType Field Value 15 Configuring Flex Links
1 1
Understanding Flex Links
Configuring Flex Links 2 Flex Links Default Configuration 2 Flex Links Configuration Guidelines and Restrictions Configuring Flex Links 3 Monitoring Flex Links
4 1
Configuring EtherChannels
Understanding How EtherChannels Work 1 EtherChannel Feature Overview 2 Understanding How EtherChannels Are Configured
Contents
Understanding Port Channel Interfaces Understanding Load Balancing 5
EtherChannel Feature Configuration Guidelines and Restrictions
Configuring EtherChannels 7 Configuring Port Channel Logical Interfaces for Layer 3 EtherChannels Configuring Channel Groups 8 Configuring the LACP System Priority and System ID 10 Configuring EtherChannel Load Balancing 11 Configuring the EtherChannel Min-Links Feature 12 Configuring VTP
1
Understanding How VTP Works 1 Understanding the VTP Domain 2 Understanding VTP Modes 2 Understanding VTP Advertisements Understanding VTP Version 2 3 Understanding VTP Pruning 4 VTP Default Configuration
5
VTP Configuration Guidelines and Restrictions Configuring VTP 6 Configuring VTP Global Parameters Configuring the VTP Mode 9 Displaying VTP Statistics 10 Configuring VLANs
1 6
Understanding How VLANs Work 1 VLAN Overview 2 VLAN Ranges 2 Configurable VLAN Parameters 3 Understanding Token Ring VLANs 3 VLAN Default Configuration
6 8
VLAN Configuration Guidelines and Restrictions
Configuring VLANs 9 VLAN Configuration Options 9 Creating or Modifying an Ethernet VLAN 10 Assigning a Layer 2 LAN Interface to a VLAN 12
Contents
Configuring the Internal VLAN Allocation Policy Configuring VLAN Translation 13 Mapping 802.1Q VLANs to ISL VLANs 16 Saving VLAN Information 17 Configuring Private VLANs
1
12
Understanding How Private VLANs Work 1 Private VLAN Domains 2 Private VLAN Ports 3 Primary, Isolated, and Community VLANs 3 Private VLAN Port Isolation 4 IP Addressing Scheme with Private VLANs 4 Private VLANs Across Multiple Switches 5 Private VLAN Interaction with Other Features 5 Private VLAN Configuration Guidelines and Restrictions Secondary and Primary VLAN Configuration 7 Private VLAN Port Configuration 9 Limitations with Other Features 9
6
Configuring Private VLANs 11 Configuring a VLAN as a Private VLAN 11 Associating Secondary VLANs with a Primary VLAN 12 Mapping Secondary VLANs to the Layer 3 VLAN Interface of a Primary VLAN Configuring a Layer 2 Interface as a Private VLAN Host Port 14 Configuring a Layer 2 Interface as a Private VLAN Promiscuous Port 15 Monitoring Private VLANs
17 1
13
Configuring Cisco IP Phone Support
Understanding Cisco IP Phone Support 1 Cisco IP Phone Connections 2 Cisco IP Phone Voice Traffic 2 Cisco IP Phone Data Traffic 3 Cisco IP Phone Power Configurations 3 Other Cisco IP Phone Features 4 Default Cisco IP Phone Support Configuration Configuring Cisco IP Phone Support
6 5 5
Cisco IP Phone Support Configuration Guidelines and Restrictions
Contents
Configuring Voice Traffic Support 6 Configuring Data Traffic Support 7 Configuring Inline Power Support 8 Configuring IEEE 802.1Q Tunneling
1 1 3
Understanding How 802.1Q Tunneling Works
802.1Q Tunneling Configuration Guidelines and Restrictions Configuring 802.1Q Tunneling 6 Configuring 802.1Q Tunnel Ports 6 Configuring the Switch to Tag Native VLAN Traffic Configuring Layer 2 Protocol Tunneling
1 1
Understanding How Layer 2 Protocol Tunneling Works Configuring Support for Layer 2 Protocol Tunneling Configuring Standard-Compliant IEEE MST
1 2
Understanding MST 1 MST Overview 2 MST Regions 2 IST, CIST, and CST 3 Hop Count 6 Boundary Ports 6 Standard-Compliant MST Implementation 7 Interoperability with IEEE 802.1D-1998 STP 9 Understanding RSTP 9 Port Roles and the Active Topology 10 Rapid Convergence 11 Synchronization of Port Roles 12 Bridge Protocol Data Unit Format and Processing Topology Changes 15
13
Configuring MST 15 Default MST Configuration 16 MST Configuration Guidelines and Restrictions 16 Specifying the MST Region Configuration and Enabling MST Configuring the Root Bridge 19 Configuring a Secondary Root Bridge 20 Configuring Port Priority 21 Configuring Path Cost 22
17
Contents
Configuring the Switch Priority 23 Configuring the Hello Time 24 Configuring the Forwarding-Delay Time 25 Configuring the Transmit Hold Count 25 Configuring the Maximum-Aging Time 26 Configuring the Maximum-Hop Count 26 Specifying the Link Type to Ensure Rapid Transitions Designating the Neighbor Type 27 Restarting the Protocol Migration Process 28 Displaying the MST Configuration and Status
28 1
26
Configuring STP and Prestandard IEEE 802.1s MST Understanding How STP Works 2 STP Overview 2 Understanding the Bridge ID 2 Understanding Bridge Protocol Data Units Election of the Root Bridge 4 STP Protocol Timers 5 Creating the Spanning Tree Topology 5 STP Port States 6 STP and IEEE 802.1Q Trunks 12 Understanding How IEEE 802.1w RSTP Works IEEE 802.1w RSTP Overview 13 RSTP Port Roles 13 RSTP Port States 14 Rapid-PVST 14
13
Understanding How Prestandard IEEE 802.1s MST Works IEEE 802.1s MST Overview 15 MST-to-PVST Interoperability 16 Common Spanning Tree 18 MST Instances 18 MST Configuration Parameters 18 MST Regions 19 Message Age and Hop Count 20 Default STP Configuration Configuring STP 22 Enabling STP 22
21
14
STP and MST Configuration Guidelines and Restrictions
21
Contents
Enabling the Extended System ID 24 Configuring the Root Bridge 24 Configuring a Secondary Root Bridge 26 Configuring STP Port Priority 26 Configuring STP Port Cost 28 Configuring the Bridge Priority of a VLAN 30 Configuring the Hello Time 31 Configuring the Forward-Delay Time for a VLAN 32 Configuring the Maximum Aging Time for a VLAN 32 Enabling Rapid-PVST 33 Configuring Prestandard IEEE 802.1s MST 33 Enabling MST 34 Displaying MST Configurations 35 Configuring MST Instance Parameters 39 Configuring MST Instance Port Parameters 40 Restarting Protocol Migration 40 Configuring Optional STP Features Understanding How PortFast Works
1 2 2 2
Understanding How BPDU Guard Works Understanding How UplinkFast Works

3
Understanding How PortFast BPDU Filtering Works Understanding How BackboneFast Works Understanding How Root Guard Works Understanding How Loop Guard Works Enabling PortFast
8 10 7 7 4 6
Understanding How EtherChannel Guard Works
Enabling PortFast BPDU Filtering Enabling BPDU Guard Enabling UplinkFast Enabling BackboneFast Enabling Root Guard Enabling Loop Guard
14 15 12 12 13 14
Enabling EtherChannel Guard
10
Contents
Configuring Layer 3 Interfaces
1 2
Layer 3 Interface Configuration Guidelines and Restrictions Configuring Subinterfaces on Layer 3 Interfaces Configuring IPv4 Routing and Addresses
4 8 9 2
Configuring IPX Routing and Network Numbers Configuring Other Protocols on Layer 3 Interfaces Configuring UDE and UDLR
1
Configuring AppleTalk Routing, Cable Ranges, and Zones

10
Understanding UDE and UDLR 1 UDE and UDLR Overview 2 Supported Hardware 2 Understanding UDE 2 Understanding UDLR 3 Configuring UDE and UDLR Configuring UDE 4 Configuring UDLR 6
3
Configuring PFC3BXL and PFC3B Mode Multiprotocol Label Switching PFC3BXL and PFC3B Mode MPLS Label Switching 1 Understanding MPLS 2 Understanding PFC3BXL and PFC3B Mode MPLS Label Switching Supported Hardware Features 5 Supported Cisco IOS Features 5 MPLS Guidelines and Restrictions 7 PFC3BXL and PFC3B Mode MPLS Supported Commands 7 Configuring MPLS 8 MPLS Per-Label Load Balancing 8 MPLS Configuration Examples 8 PFC3BXL or PFC3B Mode VPN Switching 10 PFC3BXL or PFC3B Mode VPN Switching Operation 10 MPLS VPN Guidelines and Restrictions 11 PFC3BXL or PFC3B Mode MPLS VPN Supported Commands Configuring MPLS VPN 12 MPLS VPN Sample Configuration 12 Any Transport over MPLS 13 AToM Load Balancing 14
11
11
Contents
Understanding EoMPLS 14 EoMPLS Guidelines and Restrictions Configuring EoMPLS 16 Configuring IPv4 Multicast VPN Support
14
Understanding How MVPN Works 1 MVPN Overview 2 Multicast Routing and Forwarding and Multicast Domains Multicast Distribution Trees 2 Multicast Tunnel Interfaces 5 PE Router Routing Table Support for MVPN 6 Multicast Distributed Switching Support 6 Hardware-Assisted IPv4 Multicast 6 MVPN Configuration Guidelines and Restrictions
7
Configuring MVPN 8 Forcing Ingress Multicast Replication Mode (Optional) 8 Configuring a Multicast VPN Routing and Forwarding Instance Configuring Multicast VRF Routing 15 Configuring Interfaces for Multicast Routing to Support MVPN Sample Configurations for MVPN 22 MVPN Configuration with Default MDTs Only 22 MVPN Configuration with Default and Data MDTs 24 Configuring IP Unicast Layer 3 Switching
1
20
Understanding How Layer 3 Switching Works 2 Understanding Hardware Layer 3 Switching 2 Understanding Layer 3-Switched Packet Rewrite Default Hardware Layer 3 Switching Configuration Configuration Guidelines and Restrictions Configuring Hardware Layer 3 Switching
5 6 4 4
Displaying Hardware Layer 3 Switching Statistics
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching Features that Support IPv6 Multicast
2 2 3 3
IPv6 Multicast Guidelines and Restrictions New or Changed IPv6 Multicast Commands Configuring IPv6 Multicast Layer 3 Switching
12
Contents
Using show Commands to Verify IPv6 Multicast Layer 3 Switching 3 Verifying MFIB Clients 4 Displaying the Switching Capability 5 Verifying the (S,G) Forwarding Capability 5 Verifying the (*,G) Forwarding Capability 5 Verifying the Subnet Entry Support Status 5 Verifying the Current Replication Mode 5 Displaying the Replication Mode Auto Detection Status 6 Displaying the Replication Mode Capabilities 6 Displaying Subnet Entries 6 Displaying the IPv6 Multicast Summary 6 Displaying the NetFlow Hardware Forwarding Count 7 Displaying the FIB Hardware Bridging and Drop Counts 7 Displaying the Shared and Well-Known Hardware Adjacency Counters Configuring IPv4 Multicast Layer 3 Switching
1 2
Understanding How IPv4 Multicast Layer 3 Switching Works IPv4 Multicast Layer 3 Switching Overview 2 Multicast Layer 3 Switching Cache 2 Layer 3-Switched Multicast Packet Rewrite 3 Partially and Completely Switched Flows 4 Non-RPF Traffic Processing 5 Multicast Boundary 7 Understanding How IPv4 Bidirectional PIM Works
7 7
Default IPv4 Multicast Layer 3 Switching Configuration
IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions Restrictions 8 Unsupported Features 9 Configuring IPv4 Multicast Layer 3 Switching 9 Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD 10 Enabling IPv4 Multicast Routing Globally 10 Enabling IPv4 PIM on Layer 3 Interfaces 10 Enabling IP Multicast Layer 3 Switching Globally 11 Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces 11 Configuring the Replication Mode 12 Enabling Local Egress Replication 14 Configuring the Layer 3 Switching Global Threshold 15 Enabling Installation of Directly Connected Subnets 15
13
Contents
Specifying the Flow Statistics Message Interval 16 Enabling Shortcut-Consistency Checking 16 Configuring ACL-Based Filtering of RPF Failures 17 Displaying RPF Failure Rate-Limiting Information 17 Configuring Multicast Boundary 18 Displaying IPv4 Multicast Layer 3 Hardware Switching Summary Displaying the IPv4 Multicast Routing Table 21 Displaying IPv4 Multicast Layer 3 Switching Statistics 22 Configuring IPv4 Bidirectional PIM 23 Enabling IPv4 Bidirectional PIM Globally 23 Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups Setting the IPv4 Bidirectional PIM Scan Interval 24 Displaying IPv4 Bidirectional PIM Information 25 Using IPv4 Debug Commands 27 Clearing IPv4 Multicast Layer 3 Switching Statistics 27 Redundancy for Multicast Traffic 28 Configuring MLDv2 Snooping for IPv6 Multicast Traffic Understanding How MLDv2 Snooping Works 2 MLDv2 Snooping Overview 2 MLDv2 Messages 3 Source-Based Filtering 3 Explicit Host Tracking 3 MLDv2 Snooping Proxy Reporting 4 Joining an IPv6 Multicast Group 4 Leaving a Multicast Group 6 Understanding the MLDv2 Snooping Querier Default MLDv2 Snooping Configuration
8 8 8 1
18
24
MLDv2 Snooping Configuration Guidelines and Restrictions Enabling the MLDv2 Snooping Querier
9
MLDv2 Snooping Querier Configuration Guidelines and Restrictions Configuring MLDv2 Snooping 10 Enabling MLDv2 Snooping 10 Configuring a Static Connection to a Multicast Receiver Configuring a Multicast Router Port Statically 11 Configuring the MLD Snooping Query Interval 12 Enabling Fast-Leave Processing 13
11
Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide, Release 12.2SXF
14
OL-3999-08
Contents
Enabling SSM Safe Reporting 13 Configuring Explicit Host Tracking 14 Configuring Report Suppression 14 Displaying MLDv2 Snooping Information
15 1
Configuring IGMP Snooping for IPv4 Multicast Traffic Understanding How IGMP Snooping Works 2 IGMP Snooping Overview 2 Joining a Multicast Group 2 Leaving a Multicast Group 4 Understanding the IGMP Snooping Querier 5 Understanding IGMP Version 3 Support 5 Default IGMP Snooping Configuration
7
IGMP Snooping Configuration Guidelines and Restrictions Enabling the IGMP Snooping Querier
9
8 8
IGMP Snooping Querier Configuration Guidelines and Restrictions Configuring IGMP Snooping 9 Enabling IGMP Snooping 10 Configuring a Static Connection to a Multicast Receiver 11 Configuring a Multicast Router Port Statically 11 Configuring the IGMP Snooping Query Interval 11 Enabling IGMP Fast-Leave Processing 12 Configuring Source Specific Multicast (SSM) Mapping 12 Enabling SSM Safe Reporting 13 Configuring IGMPv3 Explicit Host Tracking 13 Displaying IGMP Snooping Information 14 Configuring PIM Snooping
1 1
Understanding How PIM Snooping Works Default PIM Snooping Configuration

4
PIM Snooping Configuration Guidelines and Restrictions Configuring PIM Snooping 5 Enabling PIM Snooping Globally 5 Enabling PIM Snooping in a VLAN 5 Disabling PIM Snooping Designated-Router Flooding
15
Contents
Configuring RGMP
1 1
Understanding How RGMP Works Default RGMP Configuration

2
RGMP Configuration Guidelines and Restrictions Enabling RGMP on Layer 3 Interfaces Configuring Network Security Configuring TCP Intercept
2 1 3
Configuring MAC Address-Based Traffic Blocking
Configuring Unicast Reverse Path Forwarding Check 2 Understanding PFC3 Unicast RPF Check Support 2 Understanding PFC2 Unicast RPF Check Support 3 Unicast RPF Check Guidelines and Restrictions 3 Configuring Unicast RPF Check 3 Understanding Cisco IOS ACL Support Hardware and Software ACL Support Configuring IPv6 Address Compression Optimized ACL Logging with a PFC3 5 Understanding OAL 5 OAL Guidelines and Restrictions 5 Configuring OAL 6 Guidelines and Restrictions for Using Layer 4 Operators in ACLs Determining Layer 4 Operation Usage 8 Determining Logical Operation Unit Usage 8 Configuring VLAN ACLs
1 7 1 1
Cisco IOS ACL Configuration Guidelines and Restrictions

2 3
Understanding VACLs 1 VACL Overview 2 Bridged Packets 2 Routed Packets 3 Multicast Packets 4 Configuring VACLs 4 VACL Configuration Overview 5 Defining a VLAN Access Map 5 Configuring a Match Clause in a VLAN Access Map Sequence 6 Configuring an Action Clause in a VLAN Access Map Sequence 7
16
OL-3999-08
Contents
Applying a VLAN Access Map 8 Verifying VLAN Access Map Configuration 8 VLAN Access Map Configuration and Verification Examples Configuring a Capture Port 9 Configuring VACL Logging
11 1 2
Configuring Denial of Service Protection Understanding How DoS Protection Works DoS Protection with a PFC2 2 DoS Protection with a PFC3 10 DoS Protection Default Configuration
22
DoS Protection Configuration Guidelines and Restrictions PFC2 23 PFC3 23 Monitoring Packet Drop Statistics 24 Displaying Rate-Limiter Information 27 Understanding How Control Plane Policing Works CoPP Default Configuration Configuring CoPP Monitoring CoPP
30 31 29 29 28
23
CoPP Configuration Guidelines and Restrictions
Defining Traffic Classification 32 Traffic Classification Overview 32 Traffic Classification Guidelines 34 Sample Basic ACLs for CoPP Traffic Classification Configuring Sticky ARP
35 1
34
Configuring DHCP Snooping
Understanding DHCP Snooping 1 Overview of DHCP Snooping 2 Trusted and Untrusted Sources 2 DHCP Snooping Binding Database 2 Packet Validation 3 DHCP Snooping Option-82 Data Insertion 3 Overview of the DHCP Snooping Database Agent Default Configuration for DHCP Snooping
6
17
Contents
DHCP Snooping Configuration Restrictions and Guidelines DHCP Snooping Configuration Restrictions 7 DHCP Snooping Configuration Guidelines 7 Minimum DHCP Snooping Configuration 8
Configuring DHCP Snooping 9 Enabling DHCP Snooping Globally 9 Enabling DHCP Option-82 Data Insertion 10 Enabling the DHCP Option-82 on Untrusted Port Feature 10 Enabling DHCP Snooping MAC Address Verification 11 Enabling DHCP Snooping on VLANs 12 Configuring the DHCP Trust State on Layer 2 LAN Interfaces 13 Configuring DHCP Snooping Rate Limiting on Layer 2 LAN Interfaces Configuring the DHCP Snooping Database Agent 14 Configuration Examples for the Database Agent 15 Displaying a Binding Table 18 Configuring Dynamic ARP Inspection
1
14
Understanding DAI 1 Understanding ARP 2 Understanding ARP Spoofing Attacks 2 Understanding DAI and ARP Spoofing Attacks 2 Interface Trust States and Network Security 3 Rate Limiting of ARP Packets 4 Relative Priority of ARP ACLs and DHCP Snooping Entries Logging of Dropped Packets 5 Default DAI Configuration
5 6
DAI Configuration Guidelines and Restrictions
Configuring DAI 6 Enabling DAI on VLANs 7 Configuring the DAI Interface Trust State 8 Applying ARP ACLs for DAI Filtering 8 Configuring ARP Packet Rate Limiting 9 Enabling DAI Error-Disabled Recovery 11 Enabling Additional Validation 11 Configuring DAI Logging 13 Displaying DAI Information 15 DAI Configuration Samples
16
18
OL-3999-08
Contents
Sample One: Two Switches Support DAI 16 Sample Two: One Switch Supports DAI 21 Configuring Traffic Storm Control
1 1 3 3
Understanding Traffic Storm Control
Default Traffic Storm Control Configuration Enabling Traffic Storm Control

4 5
Traffic Storm Control Guidelines and Restrictions Displaying Traffic Storm Control Settings
Unknown Unicast and Multicast Flood Blocking Understanding UUFB or UMFB Configuring UUFB Configuring PFC QoS
2 1 1
Understanding How PFC QoS Works 2 Port Types Supported by PFC QoS 2 Overview 2 Component Overview 6 Understanding Classification and Marking 17 Policers 20 Understanding Port-Based Queue Types 23 PFC QoS Default Configuration 30 PFC QoS Global Settings 30 Default Values With PFC QoS Enabled 31 Default Values With PFC QoS Disabled 50 PFC QoS Configuration Guidelines and Restrictions 50 General Guidelines 51 PFC3 Guidelines 53 PFC2 Guidelines 53 Class Map Command Restrictions 54 Policy Map Command Restrictions 54 Policy Map Class Command Restrictions 54 Supported Granularity for CIR and PIR Rate Values 55 Supported Granularity for CIR and PIR Token Bucket Sizes IP Precedence and DSCP Values 56 Configuring PFC QoS
56
55
19
Contents
Enabling PFC QoS Globally 57 Enabling Ignore Port Trust 58 Configuring DSCP Transparency 59 Enabling Queueing-Only Mode 60 Enabling Microflow Policing of Bridged Traffic 60 Enabling VLAN-Based PFC QoS on Layer 2 LAN Ports 61 Enabling Egress ACL Support for Remarked DSCP 62 Creating Named Aggregate Policers 63 Configuring a PFC QoS Policy 65 Configuring Egress DSCP Mutation on a PFC3 83 Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports 85 Configuring DSCP Value Maps 87 Configuring the Trust State of Ethernet LAN and OSM Ports 91 Configuring the Ingress LAN Port CoS Value 93 Configuring Standard-Queue Drop Threshold Percentages 93 Mapping QoS Labels to Queues and Drop Thresholds 99 Allocating Bandwidth Between Standard Transmit Queues 109 Setting the Receive-Queue Size Ratio 111 Configuring the Transmit-Queue Size Ratio 112 Common QoS Scenarios 113 Sample Network Design Overview 113 Classifying Traffic from PCs and IP Phones in the Access Layer Accepting the Traffic Priority Value on Interswitch Links 117 Prioritizing Traffic on Interswitch Links 118 Using Policers to Limit the Amount of Traffic from a PC 121 PFC QoS Glossary
123 1
114
Configuring PFC3BXL or PFC3B Mode MPLS QoS Terminology

2 3
PFC3BXL or PFC3B Mode MPLS QoS Features MPLS Experimental Field 3 Trust 3 Classification 4 Policing and Marking 4 Preserving IP ToS 4 EXP Mutation 4 MPLS DiffServ Tunneling Modes 4
20
OL-3999-08
Contents
PFC3BXL or PFC3B Mode MPLS QoS Overview 5 Specifying the QoS in the IP Precedence Field
PFC3BXL or PFC3B Mode MPLS QoS 5 LERs at the Input Edge of an MPLS Network 6 LSRs in the Core of an MPLS Network 7 LERs at the Output Edge of an MPLS Network 7 Understanding PFC3BXL or PFC3B Mode MPLS QoS LERs at the EoMPLS Edge 8 LERs at the IP Edge (MPLS, MPLS VPN) 9 LSRs at the MPLS Core 13 PFC3BXL or PFC3B MPLS QoS Default Configuration MPLS QoS Commands
16 17 8
15
PFC3BXL or PFC3B Mode MPLS QoS Restrictions and Guidelines
Configuring PFC3BXL or PFC3B Mode MPLS QoS 18 Enabling QoS Globally 18 Enabling Queueing-Only Mode 19 Configuring a Class Map to Classify MPLS Packets 20 Configuring the MPLS Packet Trust State on Ingress Ports 22 Configuring a Policy Map 23 Displaying a Policy Map 28 Configuring PFC3BXL or PFC3B Mode MPLS QoS Egress EXP Mutation Configuring EXP Value Maps 31 MPLS DiffServ Tunneling Modes 32 Short Pipe Mode 32 Uniform Mode 33 MPLS DiffServ Tunneling Restrictions and Usage Guidelines Configuring Short Pipe Mode 35 Ingress PE RouterCustomer Facing Interface 36 Configuring Ingress PE RouterP Facing Interface 37 Configuring the P RouterOutput Interface 38 Configuring the Egress PE RouterCustomer Facing Interface
29
35
39
Configuring Uniform Mode 40 Configuring the Ingress PE RouterCustomer Facing Interface 40 Configuring the Ingress PE RouterP Facing Interface 41 Configuring the Egress PE RouterCustomer Facing Interface 42
21
Contents
Configuring PFC QoS Statistics Data Export Understanding PFC QoS Statistics Data Export Configuring PFC QoS Statistics Data Export
1 1 2
PFC QoS Statistics Data Export Default Configuration

2 1 1 2
Configuring the Cisco IOS Firewall Feature Set Cisco IOS Firewall Feature Set Support Overview Cisco IOS Firewall Guidelines and Restrictions Additional CBAC Configuration
3 1
Configuring Network Admission Control Understanding NAC 1 NAC Overview 1 NAC Device Roles 2 AAA Down Policy 3 NAC Layer 2 IP Validation
Configuring NAC 11 Default NAC Configuration 11 NAC Layer 2 IP Guidelines, Limitations, and Restrictions Configuring NAC Layer 2 IP Validation 13 Configuring EAPoUDP 16 Configuring Identity Profiles and Policies 17 Configuring a NAC AAA Down Policy 17 Displaying NAC
21
11
Monitoring and Maintaining NAC 21 Clearing Table Entries 21 Displaying NAC Information 21 Configuring IEEE 802.1X Port-Based Authentication Understanding 802.1X Port-Based Authentication 1 Device Roles 2 Authentication Initiation and Message Exchange Ports in Authorized and Unauthorized States 4 Supported Topologies 5 Default 802.1X Port-Based Authentication Configuration
1
6 6
802.1X Port-Based Authentication Guidelines and Restrictions
22
OL-3999-08
Contents
Configuring 802.1X Port-Based Authentication 7 Enabling 802.1X Port-Based Authentication 7 Configuring Switch-to-RADIUS-Server Communication 9 Enabling Periodic Reauthentication 10 Manually Reauthenticating the Client Connected to a Port 11 Initializing Authentication for the Client Connected to a Port 11 Changing the Quiet Period 12 Changing the Switch-to-Client Retransmission Time 12 Setting the Switch-to-Client Retransmission Time for EAP-Request Frames 13 Setting the Switch-to-Authentication-Server Retransmission Time for Layer 4 Packets Setting the Switch-to-Client Frame Retransmission Number 14 Enabling Multiple Hosts 15 Resetting the 802.1X Configuration to the Default Values 15 Displaying 802.1X Status Configuring Port Security
1 16
14
Understanding Port Security 1 Port Security with Dynamically Learned and Static MAC Addresses Port Security with Sticky MAC Addresses 3 Default Port Security Configuration
3 3
Port Security Guidelines and Restrictions
Configuring Port Security 4 Enabling Port Security 5 Configuring the Port Security Violation Mode on a Port 7 Configuring the Port Security Rate Limiter 8 Configuring the Maximum Number of Secure MAC Addresses on a Port Enabling Port Security with Sticky MAC Addresses on a Port 10 Configuring a Static Secure MAC Address on a Port 11 Configuring Secure MAC Address Aging on a Port 12 Displaying Port Security Settings Configuring CDP
1 1 13
Understanding How CDP Works
Configuring CDP 2 Enabling CDP Globally 2 Displaying the CDP Global Configuration Enabling CDP on a Port 3
23
Contents
Displaying the CDP Interface Configuration Monitoring and Maintaining CDP 3 Configuring UDLD
1 1
Understanding How UDLD Works UDLD Overview 2 UDLD Aggressive Mode 3 Default UDLD Configuration
3
Configuring UDLD 3 Enabling UDLD Globally 4 Enabling UDLD on Individual LAN Interfaces 4 Disabling UDLD on Fiber-Optic LAN Interfaces 5 Configuring the UDLD Probe Message Interval 5 Displaying Disabled LAN Interfaces 5 Displaying UDLD Neighbor Interfaces 5 Resetting Disabled LAN Interfaces 6 Configuring NetFlow
1
Understanding NetFlow 1 NetFlow Overview 2 NetFlow on the MSFC 2 NetFlow on the PFC 3 Default NetFlow Configuration
5 5
NetFlow Configuration Guidelines and Restrictions Configuring NetFlow 6 Configuring NetFlow on the PFC 6 Configuring NetFlow on the MSFC 10 Configuring NDE
1
Understanding NDE 1 NDE Overview 1 NDE on the MSFC 2 NDE on the PFC 2 Default NDE Configuration
10 10
NDE Configuration Guidelines and Restrictions Configuring NDE 10 Configuring NDE on the PFC 11 Configuring NDE on the MSFC 13
24
OL-3999-08
Contents
Enabling NDE for Ingress-Bridged IP Traffic 15 Displaying the NDE Address and Port Configuration Configuring NDE Flow Filters 16 Displaying the NDE Configuration 18 Configuring Local SPAN, RSPAN, and ERSPAN
1
15
Understanding How Local SPAN, RSPAN, and ERSPAN Work Local SPAN, RSPAN, and ERSPAN Overview 2 Local SPAN, RSPAN, and ERSPAN Sources 5 Local SPAN, RSPAN, and ERSPAN Destination Ports 6
Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions General Guidelines and Restrictions 6 Feature Incompatiblities 7 Local SPAN, RSPAN, and ERSPAN Session Limits 8 Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions 10 VSPAN Guidelines and Restrictions 11 RSPAN Guidelines and Restrictions 11 ERSPAN Guidelines and Restrictions 12 Configuring Local SPAN, RSPAN, and ERSPAN 14 Configuring Destination Port Permit Lists (Optional) 14 Configuring Local SPAN 15 Configuring RSPAN 16 Configuring ERSPAN 19 Configuring Source VLAN Filtering for Local SPAN and RSPAN Configuring a Destination Port as an Unconditional Trunk 24 Configuring Destination Trunk Port VLAN Filtering 25 Verifying the Configuration 26 Configuration Examples 27 Configuring SNMP IfIndex Persistence Understanding SNMP IfIndex Persistence
1 1
24
Configuring SNMP IfIndex Persistence 2 Enabling SNMP IfIndex Persistence Globally 2 Disabling SNMP IfIndex Persistence Globally 2 Enabling and Disabling SNMP IfIndex Persistence on Specific Interfaces 3 Clearing SNMP IfIndex Persistence Configuration from a Specific Interface 3
25
Contents
Power Management and Environmental Monitoring Understanding How Power Management Works 1 Enabling or Disabling Power Redundancy 2 Powering Modules Off and On 4 Viewing System Power Status 4 Power Cycling Modules 5 Determining System Power Requirements 5 Determining System Hardware Capacity 5 Determining Sensor Temperature Threshold 9
Understanding How Environmental Monitoring Works 10 Monitoring System Environmental Status 10 Understanding LED Environmental Indications 12 Configuring Generic Online Diagnostics
1 1
Understanding How Online Diagnostics Work
Configuring Online Diagnostics 2 Setting Bootup Online Diagnostics Level 2 Configuring On-Demand Online Diagnostics 3 Scheduling Online Diagnostics 4 Configuring Health-Monitoring Diagnostics 5 Running Online Diagnostic Tests 5 Starting and Stopping Online Diagnostic Tests 6 Displaying Online Diagnostic Tests and Test Results Performing Memory Tests Using the Top N Utility
1 10
Understanding the Top N Utility 1 Top N Utility Overview 1 Understanding Top N Utility Operation
Using the Top N Utility 2 Enabling Top N Utility Report Creation 3 Displaying the Top N Utility Reports 3 Clearing Top N Utility Reports 4 Using the Layer 2 Traceroute Utility Usage Guidelines
2 3 1 1
Understanding the Layer 2 Traceroute Utility Using the Layer 2 Traceroute Utility
26
OL-3999-08
Contents
APPENDIX
Online Diagnostic Tests
1 2
Global Health-Monitoring Tests TestSPRPInbandPing 2 TestScratchRegister 3 TestMacNotification 3
Per-Port Tests 3 TestNonDisruptiveLoopback 4 TestLoopback 4 TestActiveToStandbyLoopback 5 TestTransceiverIntegrity 5 TestNetflowInlineRewrite 6 PFC Layer 2 Forwarding Engine Tests TestNewIndexLearn 7 TestDontConditionalLearn 7 TestBadBpduTrap 8 TestMatchCapture 8 TestStaticEntry 9 DFC Layer 2 Forwarding Engine Tests TestDontLearn 9 TestNewLearn 10 TestIndexLearn 10 TestConditionalLearn 11 TestTrap 11 TestBadBpdu 12 TestProtocolMatchChannel 13 TestCapture 13 TestStaticEntry 14 PFC Layer 3 Forwarding Engine Tests TestFibDevices 14 TestIPv4FibShortcut 15 TestIPv6FibShortcut 15 TestMPLSFibShortcut 16 TestNATFibShortcut 16 TestL3Capture2 17 TestAclPermit 17 TestAclDeny 18 TestNetflowShortcut 18 TestQoS 18 DFC Layer 3 Forwarding Engine Tests
7
14
19
27
Contents
TestFibDevices 19 TestIPv4FibShortcut TestIPv6FibShortcut TestMPLSFibShortcut TestNATFibShortcut TestL3Capture2 22 TestAclPermit 22 TestAclDeny 23 TestQoS 23 TestNetflowShortcut TestAclFpgaMonitor
20 20 21 21
24 24
Replication Engine Tests 25 TestL3VlanMet 25 TestIngressSpan 25 TestEgressSpan 26 Fabric Tests 26 TestFabricSnakeForward 27 TestFabricSnakeBackward 27 TestSynchedFabChannel 28 TestFabricCh0Health 28 TestFabricCh1Health 28 Exhaustive Memory Tests 29 TestFibTcamSSRAM 29 TestAsicMemory 30 TestAclQosTcam 30 TestNetflowTcam 31 TestQoSTcam 31 IPSEC Services Modules Tests 32 TestIPSecClearPkt 32 TestHapiEchoPkt 32 TestIPSecEncryptDecryptPkt 33 Stress Tests 33 TestTrafficStress 33 TestEobcStressPing 34 Critical Recovery Tests 34 TestL3HealthMonitoring 34 TestTxPathMonitoring 35 TestSynchedFabChannel 35 General Tests
36
28
OL-3999-08
Contents
ScheduleSwitchover 36 TestFirmwareDiagStatus 36
B
APPENDIX
Acronyms
INDEX
29
Preface
This preface describes who should read the Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide, Release 12.2SXF, how it is organized, and its document conventions.
Tip
For additional information about Cisco Catalyst 6500 Series Switches (including configuration examples and troubleshooting information), see the documents listed on this page: http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.html Participate in the Technical Documentation Ideas forum
Audience
This guide is for experienced network administrators who are responsible for configuring and maintaining Catalyst 6500 series switches.
Related Documentation
The following publications are available for the Catalyst 6500 series switches:

Catalyst 6500 Series Switch Installation Guide Catalyst 6500 Series Switch Module Installation Guide Cisco IOS Master Command List, Release 12.2SX Catalyst 6500 Series Switch Cisco IOS System Message Guide, Release 12.2SX Release Notes for Cisco IOS Release 12.2SXF and Rebuilds Cisco IOS Configuration Guides and Command ReferencesUse these publications to help you configure Cisco IOS software features not described in the Catalyst 6500 series switch publications:
Configuration Fundamentals Configuration Guide Configuration Fundamentals Command Reference Bridging and IBM Networking Configuration Guide Bridging and IBM Networking Command Reference Interface Configuration Guide
30
Preface Conventions
Interface Command Reference Network Protocols Configuration Guide, Part 1, 2, and 3 Network Protocols Command Reference, Part 1, 2, and 3 Security Configuration Guide Security Command Reference Switching Services Configuration Guide Switching Services Command Reference Voice, Video, and Home Applications Configuration Guide Voice, Video, and Home Applications Command Reference Software Command Summary Software System Error Messages Debug Command Reference Internetwork Design Guide Internetwork Troubleshooting Guide Configuration Builder Getting Started Guide
The Cisco IOS Configuration Guides and Command References are located at this URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configuratio n_guides_list.html
For information about MIBs, go to this URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml
Conventions
This document uses the following conventions: Convention boldface font italic font [ ] {x|y|z} [x|y|z] string
screen
Description Commands, command options, and keywords are in boldface. Arguments for which you supply values are in italics. Elements in square brackets are optional. Alternative keywords are grouped in braces and separated by vertical bars. Optional alternative keywords are grouped in brackets and separated by vertical bars. A nonquoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.
font
Terminal sessions and information the system displays are in screen font. Information you must enter is in boldface
screen
boldface screen
font.
font
italic screen
font
Arguments for which you supply values are in italic screen font.
This pointer highlights an important line of text in an example.
31
Preface Conventions
Convention ^
Description The symbol ^ represents the key labeled Controlfor example, the key combination ^D in a screen display means hold down the Control key while you press the D key. Nonprinting characters, such as passwords are in angle brackets.
< >
Notes use the following conventions:
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the publication. Cautions use the following conventions:
Caution
Means reader be careful. In this situation, you might do something that could result in equipment damage or loss of data.
Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly Whats 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 Whats 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.
Tip
32
OL-3999-08
C H A P T E R
Product Overview
This chapter consists of these sections:

Supported Hardware and Software, page 1-1 User Interfaces, page 1-1 Configuring Embedded CiscoView Support, page 1-2 Software Features Supported in Hardware by the PFC and DFC, page 1-3
Tip
Supported Hardware and Software

For complete information about the chassis, modules, and software features supported by the Catalyst 6500 series switches, refer to the Release Notes for Cisco IOS Release 12.2SXF and Rebuilds:
User Interfaces
Release 12.2SX supports configuration using the following interfaces:

CLISee Chapter 2, Command-Line Interfaces. SNMPRefer to the Release 12.2 IOS Configuration Fundamentals Configuration Guide and Command Reference at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html
Cisco IOS web browser interfaceRefer to Using the Cisco Web Browser in the IOS Configuration Fundamentals Configuration Guide at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf005.html Embedded CiscoViewSee the Configuring Embedded CiscoView Support section on page 1-2.
1-1
Chapter 1 Configuring Embedded CiscoView Support
Product Overview
Configuring Embedded CiscoView Support

These sections describe configuring Embedded CiscoView support:

Understanding Embedded CiscoView, page 1-2 Installing and Configuring Embedded CiscoView, page 1-2 Displaying Embedded CiscoView Information, page 1-3
Understanding Embedded CiscoView

The Embedded CiscoView network management system is a web-based interface that uses HTTP and SNMP to provide a graphical representation of the switch and to provide a GUI-based management and configuration interface.
Installing and Configuring Embedded CiscoView

To install and configure Embedded CiscoView, perform this task: Command
Step 1
Router# dir device_name
Purpose Displays the contents of the device. If you are installing Embedded CiscoView for the first time, or if the CiscoView directory is empty, skip to Step 4.
Step 2 Step 3 Step 4
Router# delete device_name:cv/* Router# squeeze device_name: Router# archive tar /xtract tftp:// ip_address_of_tftp_server/ciscoview.tar device_name:cv Router# dir device_name:
Removes existing files from the CiscoView directory. Recovers the space in the file system. Extracts the CiscoView files from the tar file on the TFTP server to the CiscoView directory. Displays the contents of the device. In a redundant configuration, repeat Step 1 through Step 5 for the file system on the redundant supervisor engine.
Step 5
Step 6 Step 7 Step 8 Step 9
Router# configure terminal Router(config)# ip http server Router(config)# snmp-server community string ro Router(config)# snmp-server community string rw
Enters global configuration mode. Enables the HTTP web server. Configures the SNMP password for read-only operation. Configures the SNMP password for read/write operation.
Note
The default password for accessing the switch web page is the enable-level password of the switch. For more information about web access to the switch, refer to Using the Cisco Web Browser in the IOS Configuration Fundamentals Configuration Guide at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf005.html
1-2
OL-3999-08
Chapter 1
Product Overview Software Features Supported in Hardware by the PFC and DFC
Displaying Embedded CiscoView Information

To display the Embedded CiscoView information, enter the following EXEC commands: Command
Router# show ciscoview package Router# show ciscoview version
Purpose Displays information about the Embedded CiscoView files. Displays the Embedded CiscoView version.
Software Features Supported in Hardware by the PFC and DFC

These sections describe the hardware support provided by Policy Feature Card 3 (PFC3), Policy Feature Card 2 (PFC2), Distributed Forwarding Card 3 (DFC3) and Distributed Forwarding Card (DFC):

Software Features Supported in Hardware by the PFC3, PFC2, DFC3, and DFC, page 1-3 Software Features Supported in Hardware by the PFC3 and DFC3, page 1-4
Software Features Supported in Hardware by the PFC3, PFC2, DFC3, and DFC
The PFC3, PFC2, DFC3, and DFC provide hardware support for these Cisco IOS software features:
Access Control Lists (ACLs) for Layer 3 ports and VLAN interfaces
Permit and deny actions of input and output standard and extended ACLs
Note
Flows that require ACL logging are processed in software on the MSFC.
Except on MPLS interfaces, reflexive ACL flows after the first packet in a session is processed
in software on the MSFC

Dynamic ACL flows
Note
Idle timeout is processed in software on the MSFC.
For more information about PFC and DFC support for ACLs, see Chapter 34, Understanding Cisco IOS ACL Support. For complete information about configuring ACLs, refer to the Cisco IOS Security Configuration Guide, Release 12.2, Traffic Filtering and Firewalls, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfacls.html
VLAN ACLs (VACLs)To configure VACLs, see Chapter 35, Configuring VLAN ACLs.
1-3
Chapter 1 Software Features Supported in Hardware by the PFC and DFC
Product Overview
Policy-based routing (PBR) for route-map sequences that use the match ip address , set ip next-hop, and ip default next-hop PBR keywords. To configure PBR, refer to the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2, Classification, Configuring Policy-Based Routing, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfpbr_ps1835_TSD_Products_C onfiguration_Guide_Chapter.html
Note
If the MSFC3 address falls within the range of a PBR ACL, traffic addressed to the MSFC3 is policy routed in hardware instead of being forwarded to the MSFC3. To prevent policy routing of traffic addressed to the MSFC3, configure PBR ACLs to deny traffic addressed to the MSFC3.
Except on MPLS interfaces, TCP interceptTo configure TCP intercept, see the Configuring TCP Intercept section on page 33-2. Firewall feature set images provide these features:
Context-Based Access Control (CBAC) The PFC installs entries in the NetFlow table to
direct flows that require CBAC to the MSFC where the CBAC is applied in software on the MSFC.
Authentication ProxyAfter authentication on the MSFC, the PFC provides TCAM support for
the authentication policy.

Port-to-Application Mapping (PAM)PAM is done in software on the MSFC.
To configure firewall features, see Chapter 44, Configuring the Cisco IOS Firewall Feature Set.
Hardware-assisted NetFlow AggregationSee Understanding NDE section on page 51-1.
Software Features Supported in Hardware by the PFC3 and DFC3

The PFC3 and DFC3 provide hardware support for these Cisco IOS software features:

Bidirectional Protocol Independent Multicast (PIM) in hardwareSee Understanding How IPv4 Bidirectional PIM Works section on page 28-7. Multiple-path Unicast Reverse Path Forwarding (RPF) CheckTo configure Unicast RPF Check, see the Configuring Unicast Reverse Path Forwarding Check section on page 33-2. Except on MPLS interfaces, Network Address Translation (NAT) for IPv4 unicast and multicast traffic. Note the following information about hardware-assisted NAT:
NAT of UDP traffic is supported only in PFC3BXL or PFC3B mode. The PFC3 does not support NAT of multicast traffic. The PFC3 does not support NAT configured with a route-map that specifies length. When you configure NAT and NDE on an interface, the PFC3 sends all traffic in fragmented
packets to the MSFC3 to be processed in software. (CSCdz51590) To configure NAT, refer to the Cisco IOS IP Configuration Guide, Release 12.2, IP Addressing and Services, Configuring IP Addressing, Configuring Network Address Translation, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfipadr.html
1-4
OL-3999-08
Chapter 1
Product Overview Software Features Supported in Hardware by the PFC and DFC
To prevent a significant volume of NAT traffic from being sent to the MSFC3, due to either a DoS attack or a misconfiguration, enter the mls rate-limit unicast acl {ingress | egress} command described at this URL: http://www.cisco.com/en/US/docs/ios/security/command/reference/sec_m2.html#mls_rate-limit_u nicast_acl (CSCea23296)
With Release 12.2(18)SXE and later releases, IPv4 Multicast over point-to-point generic route encapsulation (GRE) TunnelsRefer to the publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/interface/configuration/guide/icflogin.html Releases earlier than Release 12.2(18)SXE support IPv4 multicast over point-to-point GRE tunnels in software on the MSFC.
Note
The PFC3 does not provide hardware acceleration for tunnels configured with the tunnel key command.
GRE Tunneling and IP in IP TunnelingThe PFC3 and DFC3s support the following tunnel commands:
tunnel destination tunnel mode gre tunnel mode ipip tunnel source tunnel ttl tunnel tos
Other supported types of tunneling run in software on the MSFC3. The tunnel ttl command (default 255) sets the TTL of encapsulated packets. The tunnel tos command, if present, sets the ToS byte of a packet when it is encapsulated. If the tunnel tos command is not present and QoS is not enabled, the ToS byte of a packet sets the ToS byte of the packet when it is encapsulated. If the tunnel tos command is not present and QoS is enabled, the ToS byte of a packet as modified by PFC QoS sets the ToS byte of the packet when it is encapsulated. To configure GRE Tunneling and IP in IP Tunneling, refer to these publications: http://www.cisco.com/en/US/docs/ios/12_2/interface/configuration/guide/icflogin.html http://www.cisco.com/en/US/docs/ios/12_2/interface/command/reference/irfshoip.html To configure the tunnel tos and tunnel ttl commands, refer to this publication: http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/12s_tos.html
1-5
Chapter 1 Software Features Supported in Hardware by the PFC and DFC
Product Overview
Note the following information about tunnels:

Each hardware-assisted tunnel must have a unique source. Hardware-assisted tunnels cannot
share a source even if the destinations are different. Use secondary addresses on loopback interfaces or create multiple loopback interfaces. (CSCdy72539)
Each tunnel interface uses one internal VLAN. Each tunnel interface uses one additional router MAC address entry per router MAC address. The PFC3A does not support any PFC QoS features on tunnel interfaces. The PFC3B and PFC3BXL support PFC QoS features on tunnel interfaces. The MSFC3 supports tunnels configured with egress features on the tunnel interface. Examples
of egress features are output Cisco IOS ACLs, NAT (for inside to outside translation), TCP intercept, CBAC, and encryption.
Tip
1-6
OL-3999-08
C H A P T E R
Command-Line Interfaces
This chapter describes the command-line interfaces (CLIs) you use to configure the switches supported by Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see these publications:
The Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html The Release 12.2 publications at this URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configuratio n_guides_list.html

Accessing the CLI, page 2-2 Performing Command Line Processing, page 2-3 Performing History Substitution, page 2-4 Cisco IOS Command Modes, page 2-4 Displaying a List of Cisco IOS Commands and Syntax, page 2-5 Securing the CLI, page 2-6 ROM-Monitor Command-Line Interface, page 2-7
Tip
2-1
Chapter 2 Accessing the CLI
Accessing the CLI

These sections describe accessing the CLI:

Accessing the CLI through the EIA/TIA-232 Console Interface, page 2-2 Accessing the CLI through Telnet, page 2-2
Accessing the CLI through the EIA/TIA-232 Console Interface

Note
EIA/TIA-232 was known as recommended standard 232 (RS-232) before its acceptance as a standard by the Electronic Industries Alliance (EIA) and Telecommunications Industry Association (TIA). Perform initial configuration over a connection to the EIA/TIA-232 console interface. See the Catalyst 6500 Series Switch Module Installation Guide for console interface cable connection procedures. To make a console connection, perform this task:
Command
Purpose Brings up the prompt. Initiates enable mode enable. Completes enable mode enable. Exits the session when finished. After making a console connection, you see this display:
Press Return for Console prompt Router> enable Password: Router#
Press Return.
Router> enable Password: password Router# Router# quit
Accessing the CLI through Telnet

Note
Before you can make a Telnet connection to the switch, you must configure an IP address (see the Configuring IPv4 Routing and Addresses section on page 22-4). The switch supports up to eight simultaneous Telnet sessions. Telnet sessions disconnect automatically after remaining idle for the period specified with the exec-timeout command. To make a Telnet connection to the switch, perform this task:
2-2
OL-3999-08
Chapter 2
Command-Line Interfaces Performing Command Line Processing
Command
Step 1 Step 2
telnet {hostname | ip_addr}
Purpose Makes a Telnet connection from the remote host to the switch you want to access. Initiates authentication.
Note
Password: password Router#
If no password has been configured, press Return.
Router> enable Password: password Router# Router# quit
Initiates enable mode enable. Completes enable mode enable. Exits the session when finished.
This example shows how to open a Telnet session to the switch:

unix_host% telnet Router_1 Trying 172.20.52.40... Connected to 172.20.52.40. Escape character is '^]'. User Access Verification Password: Router_1> enable Password: Router_1#
Performing Command Line Processing

Commands are not case sensitive. You can abbreviate commands and parameters if the abbreviations contain enough letters to be different from any other currently available commands or parameters. You can scroll through the last 20 commands stored in the history buffer, and enter or edit the command at the prompt. Table 2-1 lists the keyboard shortcuts for entering and editing commands.
Table 2-1 Keyboard Shortcuts
Keystrokes Press Ctrl-B or press the left arrow key1 Press Ctrl-F or press the right arrow key1 Press Ctrl-A Press Ctrl-E Press Esc B Press Esc F
Purpose Moves the cursor back one character. Moves the cursor forward one character. Moves the cursor to the beginning of the command line. Moves the cursor to the end of the command line. Moves the cursor back one word. Moves the cursor forward one word.
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
2-3
Chapter 2 Performing History Substitution
Performing History Substitution

The history buffer stores the last 20 commands you entered. History substitution allows you to access these commands without retyping them, by using special abbreviated commands. Table 2-2 lists the history substitution commands.
Table 2-2 History Substitution Commands
Command Ctrl-P or the up arrow key.

1
Purpose Recalls commands in the history buffer, beginning with the most recent command. Repeat the key sequence to recall successively older commands. Returns to more recent commands in the history buffer after recalling commands with Ctrl-P or the up arrow key. Repeat the key sequence to recall successively more recent commands. While in EXEC mode, lists the last several commands you have just entered.
Ctrl-N or the down arrow key.1
Router# show history
1. The arrow keys function only on ANSI-compatible terminals such as VT100s.
Cisco IOS Command Modes

Note
For complete information about Cisco IOS command modes, see the Cisco IOS Configuration Fundamentals Configuration Guide at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html
The Cisco IOS user interface is divided into many different modes. The commands available to you depend on which mode you are currently in. To get a list of the commands in a given mode, type a question mark (?) at the system prompt. See the Displaying a List of Cisco IOS Commands and Syntax section on page 2-5. When you start a session on the switch, you begin in user mode, often called user EXEC mode. Only a limited subset of the commands are available in EXEC mode. To have access to all commands, you must enter privileged EXEC mode. Normally, you must type in a password to access privileged EXEC mode. From privileged EXEC mode, you can type in any EXEC command or access global configuration mode. The configuration modes allow you to make changes to the running configuration. If you later save the configuration, these commands are stored across reboots. You must start at global configuration mode. From global configuration mode, you can enter interface configuration mode, subinterface configuration mode, and a variety of protocol-specific modes.
Note
With Release 12.1(11b)E and later, when you are in configuration mode you can enter EXEC mode-level commands by entering the do keyword before the EXEC mode-level command.
2-4
OL-3999-08
Chapter 2
Command-Line Interfaces Displaying a List of Cisco IOS Commands and Syntax
ROM-monitor mode is a separate mode used when the switch cannot boot properly. For example, the switch might enter ROM-monitor mode if it does not find a valid system image when it is booting, or if its configuration file is corrupted at startup. See the ROM-Monitor Command-Line Interface section on page 2-7. Table 2-3 lists and describes frequently used Cisco IOS modes.
Table 2-3 Frequently Used Cisco IOS Command Modes
Mode User EXEC
Description of Use
How to Access
Prompt
Router>
Connect to remote devices, change Log in. terminal settings on a temporary basis, perform basic tests, and display system information. From the user EXEC mode, enter the enable command and the enable password.
Privileged EXEC (enable) Set operating parameters. The privileged command set includes the commands in user EXEC mode, as well as the configure command. Use this command to access the other command modes. Global configuration Configure features that affect the system as a whole. Many features are enabled for a particular interface. Interface commands enable or modify the operation of an interface. From the directly connected console or the virtual terminal used with Telnet, use this configuration mode to configure the console interface.
Router#
From the privileged EXEC mode, enter the configure terminal command. From global configuration mode, enter the interface type slot/port command. From global configuration mode, enter the line console 0 command.
Router(config)#
Interface configuration
Router(config-if)#
Console configuration
Router(config-line)#
The Cisco IOS command interpreter, called the EXEC, interprets and executes the commands you enter. You can abbreviate commands and keywords by entering just enough characters to make the command unique from other commands. For example, you can abbreviate the show command to sh and the configure terminal command to config t. When you type exit, the switch backs out one level. To exit configuration mode completely and return to privileged EXEC mode, press Ctrl-Z .
Displaying a List of Cisco IOS Commands and Syntax

In any command mode, you can display a list of available commands by entering a question mark (?).
Router> ?
To display a list of commands that begin with a particular character sequence, type in those characters followed by the question mark (?). Do not include a space. This form of help is called word help because it completes a word for you.
Router# co? collect configure connect copy
2-5
Chapter 2 Securing the CLI
To display keywords or arguments, enter a question mark in place of a keyword or argument. Include a space before the question mark. This form of help is called command syntax help because it reminds you which keywords or arguments are applicable based on the command, keywords, and arguments you have already entered. For example:
Router# configure ? memory network overwrite-network terminal <cr> Configure Configure Overwrite Configure from NV memory from a TFTP network host NV memory from TFTP network host from the terminal
To redisplay a command you previously entered, press the up arrow key or Ctrl-P. You can continue to press the up arrow key to see the last 20 commands you entered.
Tip
If you are having trouble entering a command, check the system prompt, and enter the question mark (?) for a list of available commands. You might be in the wrong command mode or using incorrect syntax. Enter exit to return to the previous mode. Press Ctrl-Z or enter the end command in any mode to immediately return to privileged EXEC mode.
Securing the CLI

Securing access to the CLI prevents unauthorized users from viewing configuration settings or making configuration changes that can disrupt the stability of your network or compromise your network security. You can create a strong and flexible security scheme for your switch by configuring one or more of these security features:
Protecting access to privileged EXEC commands At a minimum, you should configure separate passwords for the user EXEC and privileged EXEC (enable) IOS command modes. You can further increase the level of security by configuring username and password pairs to limit access to CLI sessions to specific users. For more information, see Configuring Security with Passwords, Privilege Levels, and Login Usernames for CLI Sessions on Networking Devices at this URL: http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_sec_4cli.html
Controlling switch access with RADIUS, TACACS+, or Kerberos For a centralized and scalable security scheme, you can require users to be authenticated and authorized by an external security server running either Remote Authentication Dial-In User Service (RADIUS), Terminal Access Controller Access-Control System Plus (TACACS+), or Kerberos. For more information about RADIUS, see Configuring RADIUS at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfrad.html For more information about TACACS+, see Configuring TACACS+ at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scftplus.html For more information about Kerberos, see Configuring Kerberos at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfkerb.html Configuring a secure connection with SSH or HTTPS
2-6
OL-3999-08
Chapter 2
Command-Line Interfaces ROM-Monitor Command-Line Interface
To prevent eavesdropping of your configuration session, you can use a Secure Shell (SSH) client or a browser that supports HTTP over Secure Socket Layer (HTTPS) to make an encrypted connection to the switch. For more information about SSH, see Configuring Secure Shell at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_ssh/configuration/12-2sx/sec-secure-copy.h tml For more information about HTTPS, see HTTPS - HTTP Server and Client with SSL 3.0 at this URL: http://www.cisco.com/en/US/docs/ios/sec_user_services/configuration/guide/sec_cfg_sec_4cli.ht ml
Copying configuration files securely with SCP To prevent eavesdropping when copying configuration files or image files to or from the switch, you can use the Secure Copy Protocol (SCP) to perform an encrypted file transfer. For more information about SCP, see Secure Copy at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/sec_usr_ssh/configuration/12-2sx/sec-secure-copy.h tml
For additional information about securing the CLI, see Cisco IOS Security Configuration Guide: Securing User Services, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/security/config_library/12-2sx/secuser-12-2sx-library.ht ml
ROM-Monitor Command-Line Interface

The ROM-monitor is a ROM-based program that executes upon platform power-up, reset, or when a fatal exception occurs. The switch enters ROM-monitor mode if it does not find a valid software image, if the NVRAM configuration is corrupted, or if the configuration register is set to enter ROM-monitor mode. From the ROM-monitor mode, you can load a software image manually from flash memory, from a network server file, or from bootflash. You can also enter ROM-monitor mode by restarting and pressing the Break key during the first 60 seconds of startup.
Note
The Break key is always enabled for 60 seconds after rebooting, regardless of whether the Break key is configured to be off by configuration register settings. To access the ROM-monitor mode through a terminal server, you can escape to the Telnet prompt and enter the send break command for your terminal emulation program to break into ROM-monitor mode. Once you are in ROM-monitor mode, the prompt changes to rommon 1>. Enter a question mark ( ?) to see the available ROM-monitor commands. For more information about the ROM-monitor commands, see the Cisco IOS Master Command List, Release 12.2SX.
2-7
Chapter 2 ROM-Monitor Command-Line Interface
Tip
2-8
OL-3999-08
C H A P T E R
Configuring the Switch for the First Time

This chapter contains information about how to initially configure the Catalyst 6500 series switch, which supplements the administration information and procedures in these publications:
Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html
Cisco IOS Configuration Fundamentals Configuration Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_book.html
Note
For complete syntax and usage information for the commands used in this chapter, refer to these publications:


Default Configuration, page 3-2 Configuring the Switch, page 3-2 Protecting Access to Privileged EXEC Commands, page 3-15 Recovering a Lost Enable Password, page 3-19 Modifying the Supervisor Engine Startup Configuration, page 3-20
Tip
3-1
Chapter 3 Default Configuration
Default Configuration
Table 3-1 shows the default configuration.
Table 3-1 Default Configuration
Feature Administrative connection Global information
Default Value Normal mode No value for the following:

System name System contact Location
System clock Passwords Prompt
No value for system clock time No passwords configured for normal mode or enable mode (press the Return key)
Router>
Configuring the Switch

These sections describe how to configure the switch:

Using the Setup Facility or the setup Command, page 3-2 Using Configuration Mode, page 3-10 Checking the Running Configuration Before Saving, page 3-10 Saving the Running Configuration Settings, page 3-11 Reviewing the Configuration, page 3-11 Configuring a Default Gateway, page 3-12 Configuring a Static Route, page 3-12 Configuring a BOOTP Server, page 3-14
Using the Setup Facility or the setup Command

These sections describe the setup facility and the setup command:

Setup Overview, page 3-2 Configuring the Global Parameters, page 3-3 Configuring Interfaces, page 3-8
Setup Overview
At initial startup, the switch automatically defaults to the setup facility. (The setup command facility functions exactly the same as a completely unconfigured system functions when you first boot it up.) You can run the setup facility by entering the setup command at the enable prompt (#).
3-2
OL-3999-08
Chapter 3
Configuring the Switch for the First Time Configuring the Switch
When you enter the setup command, current system configuration defaults are displayed in square brackets [ ] as you move through the setup command process and are queried by the system to make changes. For example, you will see this display when you use the setup facility:
Configuring interface FastEtherent3/1: Is this interface in use?: yes Configure IP on this interface?: yes
When you use the setup command, you see this display:
Configuring interface FastEthernet4/1: Is this interface in use?[yes]: yes Configure IP on this interface?[yes]: yes
Configuring the Global Parameters

When you first start the setup facility or enter the setup command, you are queried by the system to configure the global parameters, which are used for controlling system-wide settings. To boot the switch and enter the global parameters, follow these steps:
Step 1
Connect a console terminal to the console interface on the supervisor engine, and then boot the system to the user EXEC prompt ( Router>). The following display appears after you boot the Catalyst 6500 series switch (depending on your configuration, your display might not exactly match the example):
System Bootstrap, Version 6.1(2) Copyright (c) 1994-2000 by cisco Systems, Inc. c6k_sup2 processor with 131072 Kbytes of main memory rommon 1 > boot disk0:c6sup22-jsv-mz.121-5c.EX.bin Self decompressing the image : ################################################# ################################################################################ ################################################################################ ################################################################################ ################################################################################ [OK] Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013. cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706
Cisco Internetwork Operating System Software IOS (tm) c6sup2_sp Software (c6sup2_sp-SPV-M), Version 12.1(5c)EX, EARLY DEPLOYM ENT RELEASE SOFTWARE (fc1) Synced to mainline version: 12.1(5c) TAC:Home:Software:Ios General:CiscoIOSRoadmap:12.1
3-3
Chapter 3 Configuring the Switch
Copyright (c) 1986-2001 by cisco Systems, Inc. Compiled Wed 28-Mar-01 18:36 by hqluong Image text-base: 0x30020980, data-base: 0x306B8000 Start as Primary processor 00:00:05: %SYS-3-LOGGER_FLUSHING: System pausing to ensure console debugging out put. 00:00:03: Currently running ROMMON from S (Gold) region 00:00:05: %OIR-6-CONSOLE: Changing console ownership to route processor
System Bootstrap, Version 12.1(3r)E2, RELEASE SOFTWARE (fc1) Copyright (c) 2000 by cisco Systems, Inc. Cat6k-MSFC2 platform with 131072 Kbytes of main memory rommon 1 > boot Self decompressing the image : ################################################# ################################################################################ ## [OK] Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c) of the Commercial Computer Software - Restricted Rights clause at FAR sec. 52.227-19 and subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software clause at DFARS sec. 252.227-7013. cisco Systems, Inc. 170 West Tasman Drive San Jose, California 95134-1706
Cisco Internetwork Operating System Software IOS (tm) MSFC2 Software (C6MSFC2-BOOT-M), Version 12.1(3a)E4, EARLY DEPLOYMENT R ELEASE SOFTWARE (fc1) Copyright (c) 1986-2000 by cisco Systems, Inc. Compiled Sat 14-Oct-00 05:33 by eaarmas Image text-base: 0x30008980, data-base: 0x303B6000 cisco Cat6k-MSFC2 (R7000) processor with 114688K/16384K bytes of memory. Processor board ID SAD04430J9K R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache Last reset from power-on X.25 software, Version 3.0.0. 509K bytes of non-volatile configuration memory. 16384K bytes of Flash internal SIMM (Sector size 512K).
Press RETURN to get started!
Note
The first two sections of the configuration script (the banner and the installed hardware) appear only at initial system startup. On subsequent uses of the setup command facility, the setup script begins with the following System Configuration Dialog.
3-4
OL-3999-08
Chapter 3
--- System Configuration Dialog --Continue with configuration dialog? [yes/no]: y At any point you may enter a question mark '?' for help. Use ctrl-c to abort configuration dialog at any prompt. Default settings are in square brackets '[]'.
Basic management setup configures only enough connectivity for management of the system, extended setup will ask you to configure each interface on the system
Note
The examples in this section are intended as examples only. Your configuration might look differently depending on your system configuration.
Step 2
Enter yes or press Return when asked if you want to enter the configuration dialog and if you want to see the current interface summary. Press Return to accept the default (yes):
Would you like to enter the initial configuration dialog? [yes]: First, would you like to see the current interface summary? [yes]:
This example of a yes response (displayed during the setup facility) shows a switch at first-time startup; that is, nothing has been configured:
Current interface summary Interface Vlan1 GigabitEthernet1/1 GigabitEthernet1/2 GigabitEthernet3/1 GigabitEthernet3/2 GigabitEthernet3/3 GigabitEthernet3/4 GigabitEthernet3/5 GigabitEthernet3/6 GigabitEthernet3/7 GigabitEthernet3/8 IP-Address unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned OK? Method Status Protocol YES TFTP administratively down down YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down
(Additional displayed text omitted from this example.)
This example of a yes response (displayed during the setup command facility) shows a switch with some interfaces already configured:
Current interface summary Interface Vlan1 IP-Address unassigned OK? Method Status Protocol YES TFTP administratively down down
3-5
GigabitEthernet1/1 GigabitEthernet1/2 GigabitEthernet3/1 GigabitEthernet3/2 GigabitEthernet3/3 GigabitEthernet3/4 GigabitEthernet3/5 GigabitEthernet3/6 GigabitEthernet3/7 GigabitEthernet3/8 <...output truncated...>
172.20.52.34 unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned unassigned
YES NVRAM YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP YES TFTP
up
up
administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down administratively down down
Step 3
Choose which protocols to support on your interfaces. On IP installations only, you can accept the default values for most of the questions. A typical minimal configuration using IP follows and continues through Step 8:
Configuring global parameters: Enter host name [Router]: Router
Step 4
Enter the enable secret password when the following is displayed (remember this password for future reference):
The enable secret is a password used to protect access to privileged EXEC and configuration modes. This password, after entered, becomes encrypted in the configuration. Enter enable secret: barney
Step 5
Enter the enable password when the following is displayed (remember this password for future reference):
The enable password is used when you do not specify an enable secret password, with some older software versions, and some boot images. Enter enable password: wilma
The commands available at the user EXEC level are a subset of those available at the privileged EXEC level. Because many privileged EXEC commands are used to set operating parameters, you should protect these commands with passwords to prevent unauthorized use. You must enter the correct password to gain access to privileged EXEC commands. When you are running from the boot ROM monitor, the enable password might be the correct one to use, depending on your boot ROM level. The enable and enable secret passwords need to be different for effective security. You can enter the same password for both enable and enable secret during the setup script, but you receive a warning message indicating that you should enter a different password.
3-6
OL-3999-08
Chapter 3
Note
An enable secret password can contain from 1 to 25 uppercase and lowercase alphanumeric characters; an enable password can contain any number of uppercase and lowercase alphanumeric characters. In both cases, a number cannot be the first character. Spaces are also valid password characters; for example, two words is a valid password. Leading spaces are ignored; trailing spaces are recognized.
Step 6
Enter the virtual terminal password when the following is displayed (remember this password for future reference):
The virtual terminal password is used to protect access to the router over a network interface. Enter virtual terminal password: bambam
Step 7
In most cases you will use IP routing. If so, you must also select an interior routing protocol, for example, the Enhanced Interior Gateway Routing Protocol (EIGRP). Enter yes (the default) or press Return to configure IP, and then select EIGRP:
Configure IP? [yes]: Configure EIGRP routing? [yes]: Your IGRP autonomous system number [1]: 301
Step 8
Enter yes or no to accept or refuse SNMP management:

Configure SNMP Network Management? [yes]: Community string [public]:
For complete SNMP information and procedures, refer to these publications:
Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2, Cisco IOS System Management, Configuring SNMP Support, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf014.html Cisco IOS Configuration Fundamentals Configuration Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/fundamentals/command/reference/cf_book.html
To provide a review of what you have done, a display similar to the following appears and lists all of the configuration parameters you selected in Steps 3 through 8. These parameters and their defaults are shown in the order in which they appeared on your console terminal:
The following configuration command script was created: hostname router enable secret 5 $1$S3Lx$uiTYg2UrFK1U0dgWdjvxw. enable password lab line vty 0 4 password lab no snmp-server ! ip routing eigrp 301 ! interface Vlan1 shutdown no ip address ! interface GigabitEthernet1/1
3-7
shutdown no ip address ! interface GigabitEthernet1/2 shutdown no ip address ! . <...output truncated...> .! end
[0] Go to the IOS command prompt without saving this config. [1] Return back to the setup without saving this config. [2] Save this configuration to nvram and exit. Enter your selection [2]: 2 % You can enter the setup, by typing setup at IOS command prompt Router#
This completes the procedure on how to configure global parameters. The setup facility continues with the process to configure interfaces in the next section Configuring Interfaces.
Configuring Interfaces
This section provides steps for configuring installed interfaces (using the setup facility or setup command facility) to allow communication over your external networks. To configure the interface parameters, you need your interface network addresses, subnet mask information, and which protocols you want to configure. (For additional interface configuration information on each of the modules available, refer to the individual configuration notes that shipped with your modules.)
Note
The examples in this section are intended as examples only. Your configuration might look differently depending on your system configuration. To configure interfaces, follow these steps:
Step 1
At the prompt for the Gigabit Ethernet interface configuration, enter the appropriate responses for your requirements, using your own address and subnet mask:
Do you want to configure GigabitEthernet1/1 interface? [no]: yes Configure IP on this interface? [no]: yes IP address for this interface: 172.20.52.34 Subnet mask for this interface [255.255.0.0] : 255.255.255.224 Class B network is 172.20.0.0, 27 subnet bits; mask is /27
Step 2
At the prompt for all other interface types, enter the appropriate responses for your requirements:
Do you want to configure FastEthernet5/1 interface? [no]: y Configure IP on this interface? [no]: y IP address for this interface: 172.20.52.98 Subnet mask for this interface [255.255.0.0] : 255.255.255.248 Class B network is 172.20.0.0, 29 subnet bits; mask is /29
Repeat this step for each interface you need to configure. Proceed to Step 3 to check and verify your configuration parameters.
3-8
OL-3999-08
Chapter 3
When you reach and respond to the configuration dialog for the last installed interface, your interface configuration is complete.
Step 3
Check and verify the entire list of configuration parameters, which should display on your console terminal and end with the following query:
Use this configuration? [yes/no]:
A no response returns you to the enable prompt (#). You will need to reenter the setup command to reenter your configuration. A yes response saves the running configuration to NVRAM as follows:
Use this configuration? [yes/no]: yes [OK] Use the enabled mode configure command to modify this configuration. Press RETURN to get started!
After you press the Return key, this prompt appears:

Router>
This completes the procedures for configuring global parameters and interface parameters in your system. Your interfaces are now available for limited use. If you want to modify the currently saved configuration parameters after the initial configuration, enter the setup command. To perform more complex configurations, enter configuration mode and use the configure command. Check the current state of the switch using the show version command, which displays the software version and the interfaces, as follows:
Router# show version Cisco Internetwork Operating System Software IOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(5c)EX, EARLY DEPLOY) Synced to mainline version: 12.1(5c) TAC:Home:Software:Ios General:CiscoIOSRoadmap:12.1 Copyright (c) 1986-2001 by cisco Systems, Inc. Compiled Wed 28-Mar-01 17:52 by hqluong Image text-base: 0x30008980, data-base: 0x315D0000 ROM: System Bootstrap, Version 12.1(3r)E2, RELEASE SOFTWARE (fc1) BOOTFLASH: c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(5c)EX, EARLY DEPL) Router uptime is 2 hours, 33 minutes System returned to ROM by power-on (SP by power-on) Running default software cisco Catalyst 6000 (R7000) processor with 114688K/16384K bytes of memory. Processor board ID SAD04430J9K R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache Last reset from power-on Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. 1 Virtual Ethernet/IEEE 802.3 interface(s) 48 FastEthernet/IEEE 802.3 interface(s) 2 Gigabit Ethernet/IEEE 802.3 interface(s) 381K bytes of non-volatile configuration memory. 16384K bytes of Flash internal SIMM (Sector size 512K). Configuration register is 0x2 Router#
3-9
For detailed interface configuration information, refer to the Cisco IOS Interface Configuration Guide at this URL: http://www.cisco.com/en/US/docs/ios/12_2/interface/configuration/guide/finter_c.html
Using Configuration Mode

If you prefer not to use the setup facility, you can configure the switch from configuration mode as follows:
Step 1 Step 2
Connect a console terminal to the console interface of your supervisor engine. When you are asked if you want to enter the initial dialog, answer no to enter the normal operating mode as follows:
Would you like to enter the initial dialog? [yes]: no
Step 3
After a few seconds you will see the user EXEC prompt (Router>). Type enable to enter enable mode:
Router> enable
Note
Configuration changes can only be made in enable mode.
The prompt will change to the privileged EXEC prompt (#) as follows:
Router#
Step 4
At the prompt (#), enter the configure terminal command to enter configuration mode as follows:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
At the prompt, enter the interface type slot/interface command to enter interface configuration mode as follows:
Router(config)# interface fastethernet 5/1 Router(config-if)#
In either of these configuration modes, you can enter any changes to the configuration. Enter the end command to exit configuration mode.
Step 5
Save your settings. (See the Saving the Running Configuration Settings section on page 3-11.)
Your switch is now minimally configured and can boot with the configuration you entered. To see a list of the configuration commands, enter ? at the prompt or press the help key in configuration mode.
Checking the Running Configuration Before Saving

You can check the configuration settings you entered or changes you made by entering the show running-config command at the privileged EXEC prompt (#) as follows:
Router# show running-config Building configuration...
3-10
OL-3999-08
Chapter 3
Current configuration: Current configuration : 3441 bytes ! version 12.1 service timestamps debug datetime localtime service timestamps log datetime localtime no service password-encryption ! hostname Router ! boot buffersize 522200 boot system flash disk0:c6sup22-jsv-mz.121-5c.EX.bin enable password lab ! redundancy main-cpu auto-sync standard ip subnet-zero no ip finger ! cns event-service server ! <...output truncated...> ! interface FastEthernet3/3 ip address 172.20.52.19 255.255.255.224 ! <...output truncated...> ! line con 0 exec-timeout 0 0 transport input none line vty 0 4 exec-timeout 0 0 password lab login transport input lat pad mop telnet rlogin udptn nasi ! end Router#
Saving the Running Configuration Settings

To store the configuration or changes to your startup configuration in NVRAM, enter the copy running-config startup-config command at the privileged EXEC prompt (#) as follows:
Router# copy running-config startup-config
This command saves the configuration settings that you created in configuration mode. If you fail to do this step, your configuration will be lost the next time you reload the system.
Reviewing the Configuration

To display information stored in NVRAM, enter the show startup-config EXEC command. The display should be similar to the display from the show running-config EXEC command.
3-11
Configuring a Default Gateway

Note
The switch uses the default gateway only when it is not configured to route. To send data to another subnet when the switch is not configured with a routing protocol, configure a default gateway. The default gateway must be the IP address of an interface on a router in the same subnet. To configure a default gateway, perform this task:
Command
Step 1 Step 2
Router(config)# ip default-gateway A.B.C.D Router# show ip route
Purpose Configures a default gateway. Verifies that the default gateway appears correctly in the IP routing table.
This example shows how to configure a default gateway and how to verify the configuration:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip default-gateway 172.20.52.35 Router(config)# end 3d17h: %SYS-5-CONFIG_I: Configured from console by console Router# show ip route Default gateway is 172.20.52.35 Host Gateway ICMP redirect cache is empty Router# Last Use Total Uses Interface
Configuring a Static Route

If your Telnet station or SNMP network management workstation is on a different network from your switch and a routing protocol has not been configured, you might need to add a static routing table entry for the network where your end station is located. To configure a static route, perform this task: Command
Step 1 Step 2
Router(config)# ip route dest_IP_address mask {forwarding_IP | vlan vlan_ID} Router# show running-config
Purpose Configures a static route. Verifies the static route configuration.
This example shows how to use the ip route command to configure a static route to a workstation at IP address 171.10.5.10 on the switch with a subnet mask and IP address 172.20.3.35 of the forwarding router:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip route 171.10.5.10 255.255.255.255 172.20.3.35 Router(config)# end Router#
3-12
OL-3999-08
Chapter 3
This example shows how to use the show running-config command to confirm the configuration of the previously configured static route:
Router# show running-config Building configuration... . <...output truncated...> . ip default-gateway 172.20.52.35 ip classless ip route 171.10.5.10 255.255.255.255 172.20.3.35 no ip http server ! line con 0 transport input none line vty 0 4 exec-timeout 0 0 password lab login transport input lat pad dsipcon mop telnet rlogin udptn nasi ! end Router#
This example shows how to use the ip route command to configure a static route to a workstation at IP address 171.20.5.3 on the switch with subnet mask and connected over VLAN 1:
Router# configure terminal Router(config)# ip route 171.20.5.3 255.255.255.255 vlan 1 Router(config)# end Router#
This example shows how to use the show running-config command to confirm the configuration of the previously configured static route:
Router# show running-config Building configuration... . <...output truncated...> . ip default-gateway 172.20.52.35 ip classless ip route 171.20.52.3 255.255.255.255 Vlan1 no ip http server ! ! x25 host z ! line con 0 transport input none line vty 0 4 exec-timeout 0 0 password lab login transport input lat pad dsipcon mop telnet rlogin udptn nasi ! end Router#
3-13
Configuring a BOOTP Server

The Bootstrap Protocol (BOOTP) automatically assigns an IP address by adding the MAC and IP addresses of the interface to the BOOTP server configuration file. When the switch boots, it automatically retrieves the IP address from the BOOTP server. The switch performs a BOOTP request only if the current IP address is set to 0.0.0.0. (This address is the default address for a new switch or a switch that has had its startup-config file cleared using the erase command.) To allow your switch to retrieve its IP address from a BOOTP server, you must first determine the MAC address of the switch and add that MAC address to the BOOTP configuration file on the BOOTP server. To create a BOOTP server configuration file, follow these steps:
Install the BOOTP server code on the workstation, if it is not already installed. Determine the MAC address from the label on the chassis. Add an entry in the BOOTP configuration file (usually /usr/etc/bootptab) for each switch. Press Return after each entry to create a blank line between each entry. See the example BOOTP configuration file that follows in Step 4. Enter the reload command to reboot and automatically request the IP address from the BOOTP server. This example BOOTP configuration file shows the added entry:
# /etc/bootptab: database for bootp server (/etc/bootpd) # # Blank lines and lines beginning with '#' are ignored. # # Legend: # # first field -- hostname # (may be full domain name and probably should be) # # hd -- home directory # bf -- bootfile # cs -- cookie servers # ds -- domain name servers # gw -- gateways # ha -- hardware address # ht -- hardware type # im -- impress servers # ip -- host IP address # lg -- log servers # lp -- LPR servers # ns -- IEN-116 name servers # rl -- resource location protocol servers # sm -- subnet mask # tc -- template host (points to similar host entry) # to -- time offset (seconds) # ts -- time servers # <information deleted> # ######################################################################### # Start of individual host entries ######################################################################### Router: tc=netcisco0: ha=0000.0ca7.ce00: ip=172.31.7.97: dross: tc=netcisco0: ha=00000c000139: ip=172.31.7.26: <information deleted>
Step 4
3-14
OL-3999-08
Chapter 3
Configuring the Switch for the First Time Protecting Access to Privileged EXEC Commands
Protecting Access to Privileged EXEC Commands

The following tasks provide a way to control access to the system configuration file and privileged EXEC commands:

Setting or Changing a Static Enable Password, page 3-15 Using the enable password and enable secret Commands, page 3-15 Setting or Changing a Line Password, page 3-16 Setting TACACS+ Password Protection for Privileged EXEC Mode, page 3-16 Encrypting Passwords, page 3-17 Configuring Multiple Privilege Levels, page 3-17
Setting or Changing a Static Enable Password

To set or change a static password that controls access to the privileged EXEC mode, perform this task: Command
Router(config)# enable password password
Purpose Sets a new password or changes an existing password for the privileged EXEC mode.
This example shows how to configure an enable password as lab at the privileged EXEC mode:
Router# configure terminal Router(config)# enable password lab Router(config)#
To display the password or access level configuration, see the Displaying the Password, Access Level, and Privilege Level Configuration section on page 3-19.
Using the enable password and enable secret Commands

To provide an additional layer of security, particularly for passwords that cross the network or that are stored on a TFTP server, you can use either the enable password or enable secret commands. Both commands configure an encrypted password that you must enter to access enable mode (the default) or to access a specified privilege level. We recommend that you use the enable secret command. If you configure the enable secret command, it takes precedence over the enable password command; the two commands cannot be in effect simultaneously. To configure the switch to require an enable password, perform either of these tasks: Command
Router(config)# enable password [level level] {password | encryption-type encrypted-password} Router(config)# enable secret [level level] {password | encryption-type encrypted-password}
Purpose Establishes a password for the privileged EXEC mode. Specifies a secret password, saved using a nonreversible encryption method. (If enable password and enable secret commands are both set, users must enter the enable secret password.)
3-15
Chapter 3 Protecting Access to Privileged EXEC Commands
Use either of these commands with the level option to define a password for a specific privilege level. After you specify the level and set a password, give the password only to users who need to have access at this level. Use the privilege level configuration command to specify commands accessible at various levels. If you enable the service password-encryption command, the password you enter is encrypted. When you display it with the more system:running-config command, it displays in encrypted form. If you specify an encryption type, you must provide an encrypted password that you copy from another Catalyst 6500 series switch configuration.
Note
You cannot recover a lost encrypted password. You must clear NVRAM and set a new password. See the Recovering a Lost Enable Password section on page 3-19 if you lose or forget your password. To display the password or access level configuration, see the Displaying the Password, Access Level, and Privilege Level Configuration section on page 3-19.
Setting or Changing a Line Password

To set or change a password on a line, perform this task: Command
Router(config-line)# password password
Purpose Sets a new password or change an existing password for the privileged level.
Setting TACACS+ Password Protection for Privileged EXEC Mode

For complete information about TACACS+, refer to these publications:
Cisco IOS Security Configuration Guide, Release 12.2, Authentication, Authorization, and Accounting (AAA), at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfaaa.html Cisco IOS Security Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
To set the TACACS+ protocol to determine whether or not a user can access privileged EXEC mode, perform this task: Command
Router(config)# enable use-tacacs
Purpose Sets the TACACS-style user ID and password-checking mechanism for the privileged EXEC mode.
3-16
OL-3999-08
Chapter 3
Configuring the Switch for the First Time Protecting Access to Privileged EXEC Commands
When you set TACACS password protection at the privileged EXEC mode, the enable EXEC command prompts for both a new username and a password. This information is then sent to the TACACS+ server for authentication. If you are using the extended TACACS+, it also sends any existing UNIX user identification code to the TACACS+ server.
Caution
If you enter the enable use-tacacs command, you must also enter tacacs-server authenticate enable, or you are locked out of the privileged EXEC mode.
Note
When used without extended TACACS, the enable use-tacacs command allows anyone with a valid username and password to access the privileged EXEC mode, creating a potential security problem. This problem occurs because the switch cannot tell the difference between a query resulting from entering the enable command and an attempt to log in without extended TACACS.
Encrypting Passwords
Because protocol analyzers can examine packets (and read passwords), you can increase access security by configuring the Cisco IOS software to encrypt passwords. Encryption prevents the password from being readable in the configuration file. To configure the Cisco IOS software to encrypt passwords, perform this task: Command
Router(config)# service password-encryption
Purpose Encrypts a password.
Encryption occurs when the current configuration is written or when a password is configured. Password encryption is applied to all passwords, including authentication key passwords, the privileged command password, console and virtual terminal line access passwords, and Border Gateway Protocol (BGP) neighbor passwords. The service password-encryption command keeps unauthorized individuals from viewing your password in your configuration file.
Caution
The service password-encryption command does not provide a high level of network security. If you use this command, you should also take additional network security measures. Although you cannot recover a lost encrypted password (that is, you cannot get the original password back), you can regain control of the switch after you lose or forget the encrypted password. See the Recovering a Lost Enable Password section on page 3-19 if you lose or forget your password. To display the password or access level configuration, see the Displaying the Password, Access Level, and Privilege Level Configuration section on page 3-19.
Configuring Multiple Privilege Levels

By default, the Cisco IOS software has two modes of password security: user EXEC mode and privileged EXEC mode. You can configure up to 16 hierarchical levels of commands for each mode. By configuring multiple passwords, you can allow different sets of users to have access to specified commands.
3-17
Chapter 3 Protecting Access to Privileged EXEC Commands
For example, if you want many users to have access to the clear line command, you can assign it level 2 security and distribute the level 2 password widely. If you want more restricted access to the configure command, you can assign it level 3 security and distribute that password to more restricted users. These tasks describe how to configure additional levels of security:

Setting the Privilege Level for a Command, page 3-18 Changing the Default Privilege Level for Lines, page 3-18 Logging In to a Privilege Level, page 3-18 Exiting a Privilege Level, page 3-19 Displaying the Password, Access Level, and Privilege Level Configuration, page 3-19
Setting the Privilege Level for a Command

To set the privilege level for a command, perform this task: Command
Step 1 Step 2
Router(config)# privilege mode level level command Router(config)# enable password level level [encryption-type] password
Purpose Sets the privilege level for a command. Specifies the enable password for a privilege level.
Changing the Default Privilege Level for Lines

To change the default privilege level for a given line or a group of lines, perform this task: Command
Router(config-line)# privilege level level
Purpose Changes the default privilege level for the line.
Logging In to a Privilege Level

To log in at a specified privilege level, perform this task: Command
Router# enable level
Purpose Logs into a specified privilege level.
3-18
OL-3999-08
Chapter 3
Configuring the Switch for the First Time Recovering a Lost Enable Password
Exiting a Privilege Level

To exit to a specified privilege level, perform this task: Command
Router# disable level
Purpose Exits to a specified privilege level.
Displaying the Password, Access Level, and Privilege Level Configuration

To display the password, access level, and privilege level configuration, perform this task: Command
Step 1 Step 2
Router# show running-config Router# show privilege
Purpose Displays the password and the access level configuration. Shows the privilege level configuration.
This example shows how to display the password and access level configuration:
Router# show running-config <...output truncated...> enable password lab <...output truncated...>
This example shows how to display the privilege level configuration:

Router# show privilege Current privilege level is 15 Router#
Recovering a Lost Enable Password

To recover a lost enable password, follow these steps:
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7
Connect to the console interface. Configure the switch to boot up without reading the configuration memory (NVRAM). Reboot the system. Access enable mode (which can be done without a password when one is not configured). View or change the password, or erase the configuration. Reconfigure the switch to boot up and read the NVRAM as it normally does. Reboot the system.
Note
Password recovery requires the Break signal. You must be familiar with how your terminal or PC terminal emulator issues this signal. For example, in ProComm, the Alt-B keys generate the Break signal. In a Windows terminal session, you press the Break or Ctrl and Break keys simultaneously.
3-19
Chapter 3 Modifying the Supervisor Engine Startup Configuration
Modifying the Supervisor Engine Startup Configuration

These sections describe how the startup configuration on the supervisor engine works and how to modify the configuration register and BOOT variable:

Understanding the Supervisor Engine Boot Configuration, page 3-20 Configuring the Software Configuration Register, page 3-21 Specifying the Startup System Image, page 3-24 Understanding Flash Memory, page 3-24 CONFIG_FILE Environment Variable, page 3-25 Controlling Environment Variables, page 3-26
Understanding the Supervisor Engine Boot Configuration

These next sections describe how the boot configuration works on the supervisor engine.
Understanding the Supervisor Engine Boot Process

The supervisor engine boot process involves two software images: ROM monitor and supervisor engine software. When the switch is powered up or reset, the ROM-monitor code is executed. Depending on the NVRAM configuration, the supervisor engine either stays in ROM-monitor mode or loads the supervisor engine software. Two user-configurable parameters determine how the switch boots: the configuration register and the BOOT environment variable. The configuration register is described in the Modifying the Boot Field and Using the boot Command section on page 3-22. The BOOT environment variable is described in the Specifying the Startup System Image section on page 3-24.
Understanding the ROM Monitor

The ROM monitor executes upon power-up, reset, or when a fatal exception occurs. The switch enters ROM-monitor mode if the switch does not find a valid software image, if the NVRAM configuration is corrupted, or if the configuration register is set to enter ROM-monitor mode. From ROM-monitor mode, you can manually load a software image from bootflash or a Flash PC card.
Note
For complete syntax and usage information for the ROM monitor commands, refer to the Cisco IOS Master Command List, Release 12.2SX publication. You can also enter ROM-monitor mode by restarting and then pressing the Break key during the first 60 seconds of startup. If you are connected through a terminal server, you can escape to the Telnet prompt and enter the send break command to enter ROM-monitor mode.
Note
The Break key is always enabled for 60 seconds after rebooting, regardless of whether the configuration-register setting has the Break key disabled.
3-20
OL-3999-08
Chapter 3
Configuring the Switch for the First Time Modifying the Supervisor Engine Startup Configuration
The ROM monitor has these features:

Power-on confidence test Hardware initialization Boot capability (manual boot and autoboot) Debug utility and crash analysis Monitor call interface (EMT callsthe ROM monitor provides information and some functionality to the running software images through EMT calls) File system (the ROM monitor knows the simple file system and supports the newly developed file system through the dynamic linked file system library [MONLIB]) Exception handling
Configuring the Software Configuration Register

The switch uses a 16-bit software configuration register, which allows you to set specific system parameters. Settings for the software configuration register are written into NVRAM. Following are some reasons for changing the software configuration register settings:

To select a boot source and default boot filename. To enable or disable the Break function. To control broadcast addresses. To set the console terminal baud rate. To load operating software from flash memory. To recover a lost password. To allow you to manually boot the system using the boot command at the bootstrap program prompt. To force an automatic boot from the system bootstrap software (boot image) or from a default system image in onboard flash memory, and read any boot system commands that are stored in the configuration file in NVRAM.
Table 3-2 lists the meaning of each of the software configuration memory bits, and Table 3-3 defines the boot field.
Caution
The recommended configuration register setting is 0x2102. If you configure a setting that leaves break enabled and you send a break sequence over a console connection, the switch drops into ROMMON.
Table 3-2 Software Configuration Register Bit Meaning
Bit Number1 Hexadecimal 00 to 03 06 07 08 09 10 0x0040 0x0080 0x0100 0x0200 0x0400
Meaning Causes system software to ignore NVRAM contents OEM2 bit enabled Break disabled Use secondary bootstrap Internet Protocol (IP) broadcast with all zeros
0x0000 to 0x000F Boot field (see Table 3-3)
3-21
Table 3-2
Software Configuration Register Bit Meaning (continued)
Bit Number1 Hexadecimal 11 to 12 13 14 15 0x2000 0x4000 0x8000
Meaning Boot default flash software if network boot fails IP broadcasts do not have network numbers Enable diagnostic messages and ignore NVRAM contents
0x0800 to 0x1000 Console line speed (default is 9600 baud)
1. The factory default value for the configuration register is 0x2102. 2. OEM = original equipment manufacturer.
Table 3-3
Explanation of Boot Field (Configuration Register Bits 00 to 03)
Boot Field Meaning 00 01 02 to 0F Stays at the system bootstrap prompt Boots the first system image in onboard flash memory Specifies a default filename for booting over the network; enables boot system commands that override the default filename
Modifying the Boot Field and Using the boot Command

The configuration register boot field determines whether or not the switch loads an operating system image, and if so, where it obtains this system image. The following sections describe using and setting the configuration register boot field, and the tasks you must perform to modify the configuration register boot field. Bits 0 through 3 of the software configuration register form the boot field.
Note
The factory default configuration register setting for systems and spares is 0x2102. When the boot field is set to either 0 or 1 (0-0-0-0 or 0-0-0-1), the system ignores any boot instructions in the system configuration file and the following occurs:

When the boot field is set to 0, you must boot the operating system manually by entering the boot command to the system bootstrap program or ROM monitor. When the boot field is set to 1, the system boots the first image in the onboard bootflash single in-line memory module (SIMM). When the entire boot field equals a value between 0-0-1-0 and 1-1-1-1, the switch loads the system image specified by boot system commands in the startup configuration file.
You can enter the boot command only, or enter the command and include additional boot instructions, such as the name of a file stored in flash memory, or a file that you specify for booting from a network server. If you use the boot command without specifying a file or any other boot instructions, the system boots from the default flash image (the first image in onboard flash memory). Otherwise, you can instruct the system to boot from a specific flash image (using the boot system flash filename command). You can also use the boot command to boot images stored in the Flash PC cards located in Flash PC card slot 0 or slot 1 on the supervisor engine. If you set the boot field to any bit pattern other than 0 or 1, the system uses the resulting number to form a filename for booting over the network. You must set the boot field for the boot functions you require.
3-22
OL-3999-08
Chapter 3
Modifying the Boot Field

You modify the boot field from the software configuration register. To modify the software configuration register boot field, perform this task: Command
Router# show version Router# configure terminal Router(config)# config-register value
Purpose Determines the current configuration register setting. Enters configuration mode, selecting the terminal option. Modifies the existing configuration register setting to reflect the way in which you want the switch to load a system image. Exits configuration mode. Reboots to make your changes take effect.
Step 4 Step 5
Router(config)# end Router# reload
To modify the configuration register while the switch is running Cisco IOS, follow these steps:
Step 1
Enter the enable command and your password to enter privileged level as follows:
Router> enable Password: Router#
Step 2
Enter the configure terminal command at the EXEC mode prompt (#) as follows:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)#
Step 3
Configure the configuration register to0x2102 as follows:

Router(config)# config-register 0x2102
Set the contents of the configuration register by entering the config-register value configuration command, where value is a hexadecimal number preceded by 0x (see Table 3-2 on page 3-21).
Step 4
Enter the end command to exit configuration mode. The new value settings are saved to memory; however, the new settings do not take effect until the system software is reloaded by rebooting the system. Enter the show version EXEC command to display the configuration register value currently in effect and that will be used at the next reload. The value is displayed on the last line of the screen display, as in this example:
Configuration register is 0x141 (will be 0x2102 at next reload)
Step 5
Step 6
Save your settings. See the Saving the Running Configuration Settings section on page 3-11. However, note that configuration register changes take effect only after the system reloads, such as when you enter a reload command from the console.
Step 7
Reboot the system. The new configuration register value takes effect with the next system boot.
3-23
Verifying the Configuration Register Setting

Enter the show version EXEC command to verify the current configuration register setting. In ROM-monitor mode, enter the o command to verify the value of the configuration register boot field. To verify the configuration register setting, perform this task: Command
Router# show version | include Configuration register
Purpose Displays the configuration register setting.
In this example, the show version command indicates that the current configuration register is set so that the switch does not automatically load an operating system image. Instead, it enters ROM-monitor mode and waits for user-entered ROM monitor commands. The new setting instructs the switch to load a system image from commands in the startup configuration file or from a default system image stored on a network server.
Router1# show version | include Configuration register Configuration register is 0x2102 Router#
Specifying the Startup System Image

You can enter multiple boot commands in the startup configuration file or in the BOOT environment variable to provide backup methods for loading a system image.
Note
Store the system software image in the sup-bootflash:, disk0: , or disk1: device (only Supervisor Engine 720 has disk1: ). A non-ATA Flash PC card in a Supervisor Engine 2 is slot0:. Non-ATA Flash PC cards are too small for Release 12.2SX images. Do not store the system software image in the bootflash: device, which is on the MSFC and is not accessible at boot time.
The BOOT environment variable is also described in the Specify the Startup System Image in the Configuration File section in the Loading and Maintaining System Images and Microcode chapter of the Cisco IOS Configuration Fundamentals Configuration Guide.
Understanding Flash Memory

The following sections describe flash memory:

Flash Memory Features, page 3-25 Security Features, page 3-25 Flash Memory Configuration Process, page 3-25
Note
The descriptions in the following sections applies to both the bootflash device and to removable flash memory cards.
3-24
OL-3999-08
Chapter 3
Flash Memory Features

The flash memory components allow you to do the following:

Copy the system image to flash memory using TFTP. Copy the system image to flash memory using rcp. Boot the system from flash memory either automatically or manually. Copy the flash memory image to a network server using TFTP or rcp. Boot manually or automatically from a system software image stored in flash memory.
Security Features
The flash memory components support the following security features:

Flash memory cards contain a write-protect switch that you can use to protect data. You must set the switch to unprotected to write data to the Flash PC card. The system image stored in flash memory can be changed only from privileged EXEC level on the console terminal.
Flash Memory Configuration Process

To configure your switch to boot from flash memory, follow these steps:
Step 1
Copy a system image to flash memory using TFTP or rcp (refer to the Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2, Cisco IOS File Management, Loading and Maintaining System Images, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf008.html Configure the system to boot automatically from the file in flash memory. You might need to change the configuration register value. See the Modifying the Boot Field and Using the boot Command section on page 3-22, for more information on modifying the configuration register. Save your configurations. Power cycle and reboot your system to ensure that all is working as expected.
Step 2
Step 3 Step 4
CONFIG_FILE Environment Variable

For class A flash file systems, the CONFIG_FILE environment variable specifies the file system and filename of the configuration file to use for initialization (startup). Valid file systems can include nvram:, disk0: , and sup-bootflash:. For detailed file management configuration information, refer to the Cisco IOS Configuration Fundamentals Configuration Guide at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/ffun_c.html After you save the CONFIG_FILE environment variable to your startup configuration, the switch checks the variable upon startup to determine the location and filename of the configuration file to use for initialization.
3-25
The switch uses the NVRAM configuration during initialization when the CONFIG_FILE environment variable does not exist or when it is null (such as at first-time startup). If the switch detects a problem with NVRAM or a checksum error, the switch enters setup mode. See the Using the Setup Facility or the setup Command section on page 3-2 for more information on the setup command facility.
Controlling Environment Variables

Although the ROM monitor controls environment variables, you can create, modify, or view them with certain commands. To create or modify the BOOT environment variable, use the boot system global configuration command. Refer to the Specify the Startup System Image in the Configuration File section in the Loading and Maintaining System Images and Microcode chapter of the Configuration Fundamentals Configuration Guide for details on setting the BOOT environment variable. Refer to the Specify the Startup Configuration File section in the Modifying, Downloading, and Maintaining Configuration Files chapter of the Configuration Fundamentals Configuration Guide for details on setting the CONFIG_FILE variable.
Note
When you use the boot system global configuration command, you affect only the running configuration. You must save the environment variable setting to your startup configuration to place the information under ROM monitor control and for the environment variables to function as expected. Enter the copy system:running-config nvram:startup-config command to save the environment variables from your running configuration to your startup configuration. You can view the contents of the BOOT environment variable using the show bootvar command. This command displays the settings for these variables as they exist in the startup configuration as well as in the running configuration if a running configuration setting differs from a startup configuration setting. This example shows how to check the environment variables:
Router# show bootvar BOOT variable = disk0:,1;sup-bootflash:,1; CONFIG_FILE variable = BOOTLDR variable = Configuration register is 0x2102 Router#
Tip
3-26
OL-3999-08
C H A P T E R
Configuring a Supervisor Engine 720

This chapter describes how to configure a Supervisor Engine 720 in a Catalyst 6500 series switch. This chapter contains these sections:

Using the Bootflash or Bootdisk on a Supervisor Engine 720, page 4-2 Using the Slots on a Supervisor Engine 720, page 4-2 Configuring Supervisor Engine 720 Ports, page 4-2 Configuring and Monitoring the Switch Fabric Functionality, page 4-2
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
With a 3-slot chassis, install the Supervisor Engine 720 in either slot 1 or 2. With a 6-slot or a 9-slot chassis, install the Supervisor Engine 720 in either slot 5 or 6. With a 13-slot chassis, install the Supervisor Engine 720 in either slot 7 or 8.
Tip
4-1
Chapter 4 Using the Bootflash or Bootdisk on a Supervisor Engine 720
Using the Bootflash or Bootdisk on a Supervisor Engine 720

All 12.2SX releases support the Supervisor Engine 720 64-MB bootflash device (sup-bootflash:). Release 12.2(18)SXE5 and rebuilds and Release 12.2(18)SXF and rebuilds support WS-CF-UPG=, which replaces the bootflash device with a CompactFlash adapter and 512 MB CompactFlash card (sup-bootdisk:). Refer to this publication: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/hardware/Config_Notes/78_17277.html
Using the Slots on a Supervisor Engine 720

The Supervisor Engine 720 has two CompactFlash Type II slots. The CompactFlash Type II slots support CompactFlash Type II Flash PC cards sold by Cisco Systems, Inc. The keywords for the slots on the active Supervisor Engine 720 are disk0: and disk1: . The keywords for the slots on a redundant Supervisor Engine 720 are slavedisk0: and slavedisk1:.
Configuring Supervisor Engine 720 Ports

Supervisor Engine 720 port 1 has a small form-factor pluggable (SFP) connector and has no unique configuration options. Supervisor Engine 720 port 2 has an RJ-45 connector and an SFP connector (default). To use the RJ-45 connector, you must change the configuration. To configure port 2 on a Supervisor Engine 720 to use either the RJ-45 connector or the SFP connector, perform this task: Command
Step 1 Step 2
Router(config)# interface gigabitethernet slot/2 Router(config-if)# media-type {rj45 | sfp} Router(config-if)# no media-type
Purpose Selects the Ethernet port to be configured. Selects the connector to use. Reverts to the default configuration (SFP).
This example shows how to configure port 2 on a Supervisor Engine 720 in slot 5 to use the RJ-45 connector:
Router(config)# interface gigabitethernet 5/2 Router(config-if)# media-type rj45
Configuring and Monitoring the Switch Fabric Functionality

These sections describe how to configure the switching mode and monitor the switch fabric functionality that is included on a Supervisor Engine 720:

Understanding How the Switch Fabric Functionality Works, page 4-3 Configuring the Switch Fabric Functionality, page 4-4 Monitoring the Switch Fabric Functionality, page 4-4
4-2
OL-3999-08
Chapter 4
Configuring a Supervisor Engine 720 Configuring and Monitoring the Switch Fabric Functionality
Understanding How the Switch Fabric Functionality Works

These sections describe how the switch fabric functionality works:

Switch Fabric Functionality Overview, page 4-3 Forwarding Decisions for Layer 3-Switched Traffic, page 4-3 Switching Modes, page 4-3
Switch Fabric Functionality Overview

The switch fabric functionality is built into the Supervisor Engine 720 and creates a dedicated connection between fabric-enabled modules and provides uninterrupted transmission of frames between these modules. In addition to the direct connection between fabric-enabled modules provided by the switch fabric funtionality, fabric-enabled modules also have a direct connection to the 32-Gbps forwarding bus.
Forwarding Decisions for Layer 3-Switched Traffic

Either a PFC3 or a Distributed Feature Card 3 (DFC3) makes the forwarding decision for Layer 3-switched traffic as follows:

A PFC3 makes all forwarding decisions for each packet that enters the switch through a module without a DFC3. A DFC3 makes all forwarding decisions for each packet that enters the switch on a DFC3-enabled module in these situations:
If the egress port is on the same module as the ingress port, the DFC3 forwards the packet
locally (the packet never leaves the module).

If the egress port is on a different fabric-enabled module, the DFC3 sends the packet to the
egress module, which sends it out the egress port.

If the egress port is on a different nonfabric-enabled module, the DFC3 sends the packet to the
Supervisor Engine 720. The Supervisor Engine 720 fabric interface transfers the packet to the 32-Gbps switching bus where it is received by the egress module and is sent out the egress port.
Switching Modes
With a Supervisor Engine 720, traffic is forwarded to and from modules in one of the following modes:
Compact modeThe switch uses this mode for all traffic when only fabric-enabled modules are installed. In this mode, a compact version of the DBus header is forwarded over the switch fabric channel, which provides the best possible performance. Truncated modeThe switch uses this mode for traffic between fabric-enabled modules when there are both fabric-enabled and nonfabric-enabled modules installed. In this mode, the switch sends a truncated version of the traffic (the first 64 bytes of the frame) over the switch fabric channel. Bus mode (also called flow-through mode)The switch uses this mode for traffic between nonfabric-enabled modules and for traffic between a nonfabric-enabled module and a fabric-enabled module. In this mode, all traffic passes between the local bus and the supervisor engine bus.
Table 4-1 shows the switching modes used with fabric-enabled and nonfabric-enabled modules installed.
4-3
Chapter 4 Configuring and Monitoring the Switch Fabric Functionality
Table 4-1
Switch Fabric Functionality Switching Modes
Modules Between fabric-enabled modules (when no nonfabric-enabled modules are installed) Between fabric-enabled modules (when nonfabric-enabled modules are also installed) Between fabric-enabled and nonfabric-enabled modules Between non-fabric-enabled modules
Switching Modes Compact1 Truncated2 Bus Bus
1. In show commands, displayed as dcef mode for fabric-enabled modules with DFC3 installed; displayed as fabric mode for other fabric-enabled modules. 2. Displayed as fabric mode in show commands.
Configuring the Switch Fabric Functionality

To configure the switching mode, perform this task: Command
Router(config)# [no] fabric switching-mode allow {bus-mode | {truncated [{threshold [number]}]}
Purpose Configures the switching mode.
When configuring the switching mode, note the following information:

To allow use of nonfabric-enabled modules or to allow fabric-enabled modules to use bus mode, enter the fabric switching-mode allow bus-mode command. To prevent use of nonfabric-enabled modules or to prevent fabric-enabled modules from using bus mode, enter the no fabric switching-mode allow bus-mode command.
Caution
When you enter the no fabric switching-mode allow bus-mode command, power is removed from any nonfabric-enabled modules installed in the switch.

To allow fabric-enabled modules to use truncated mode, enter the fabric switching-mode allow truncated command. To prevent fabric-enabled modules from using truncated mode, enter the no fabric switching-mode allow truncated command. To configure how many fabric-enabled modules must be installed before they use truncated mode instead of bus mode, enter the fabric switching-mode allow truncated threshold number command. To return to the default truncated-mode threshold, enter the no fabric switching-mode allow truncated threshold command.
Monitoring the Switch Fabric Functionality

The switch fabric functionality supports a number of show commands for monitoring purposes. A fully automated startup sequence brings the module online and runs the connectivity diagnostics on the ports.
4-4
OL-3999-08
Chapter 4
These sections describe how to monitor the switch fabric functionality:

Displaying the Switch Fabric Redundancy Status, page 4-5 Displaying Fabric Channel Switching Modes, page 4-5 Displaying the Fabric Status, page 4-6 Displaying the Fabric Utilization, page 4-6 Displaying Fabric Errors, page 4-7
Displaying the Switch Fabric Redundancy Status

To display the switch fabric redundancy status, perform this task: Command
Router# show fabric active
Purpose Displays switch fabric redundancy status.
Router# show fabric active Active fabric card in slot 5 No backup fabric card in the system Router#
Displaying Fabric Channel Switching Modes

To display the fabric channel switching mode of one or all modules, perform this task: Command
Router# show fabric switching-mode [module {slot_number | all]
Purpose Displays fabric channel switching mode of one or all modules.
This example shows how to display the fabric channel switching mode of module 2:
Router# show fabric switching-mode module 2 Module Slot Switching Mode 2 dCEF Router#
This example shows how to display the fabric channel switching mode of all modules:
Router# show fabric switching-mode Global switching mode is Compact dCEF mode is not enforced for system to operate Fabric module is not required for system to operate Modules are allowed to operate in bus mode Truncated mode is allowed Module Slot 1 2 3 4 5 6 Switching Mode Crossbar dCEF dCEF dCEF Crossbar dCEF
4-5
Router#
Displaying the Fabric Status

To display the fabric status of one or all switching modules, perform this task: Command
Router# show fabric status [slot_number | all]
Purpose Displays fabric status.
This example shows how to display the fabric status of all modules:
Router# show fabric status slot channel speed 1 5 6 8 8 9 Router# 0 0 0 0 1 0 8G 8G 20G 8G 8G 8G module status OK OK OK OK OK Down- DDRsync fabric status OK Up- Timeout Up- BufError OK OK OK
Displaying the Fabric Utilization

To display the fabric utilization of one or all modules, perform this task: Command
Router# show fabric utilization [slot_number | all]
Purpose Displays fabric utilization.
This example shows how to display the fabric utilization of all modules:
Router# show fabric utilization all Lo% Percentage of Low-priority traffic. Hi% Percentage of High-priority traffic. slot 5 9 Router# channel 0 0 speed 20G 8G Ingress Lo% 0 0 Egress Lo% 0 0 Ingress Hi% Egress Hi% 0 0 0 0
4-6
OL-3999-08
Chapter 4
Displaying Fabric Errors

To display fabric errors of one or all modules, perform this task: Command
Router# show fabric errors [slot_number | all]
Purpose Displays fabric errors.
This example shows how to display fabric errors on all modules:

Router# show fabric errors Module errors: slot channel 1 0 8 0 8 1 9 0 Fabric errors: slot channel 1 0 8 0 8 1 9 0 Router#
crc 0 0 0 0
hbeat 0 0 0 0
sync 0 0 0 0
DDR sync 0 0 0 0
sync 0 0 0 0
buffer 0 0 0 0
timeout 0 0 0 0
Tip
4-7
4-8
OL-3999-08
C H A P T E R

This chapter describes how to configure a Supervisor Engine 32 in a Catalyst 6500 series switch. This chapter contains these sections:

Flash Memory on a Supervisor Engine 32, page 5-2 Supervisor Engine 32 Ports, page 5-2
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html With Cisco IOS software, this is the minimum required Supervisor Engine 32 memory:
512 MB DRAM on the Supervisor Engine 32 512 MB DRAM on the MSFC2A
Supervisor Engine 32 has a PFC3B and operates in PFC3B mode. The Supervisor Engine 32 is supported in the WS-6503 and WS-6503-E (3-slot) chassis, but not the CISCO7603 chassis. With a 3-slot or a 4-slot chassis, install the Supervisor Engine 32 in either slot 1 or 2. With a 6-slot or a 9-slot chassis, install the Supervisor Engine 32 in either slot 5 or 6. With a 13-slot chassis, install the Supervisor Engine 32 in either slot 7 or 8. Supervisor Engine 32 does not support switch fabric connectivity. For information about the hardware and software features supported by the Supervisor Engine 32, see the Release Notes for Cisco IOS Release 12.2SXF and Rebuilds.
Tip
5-1
Chapter 5 Flash Memory on a Supervisor Engine 32
Flash Memory on a Supervisor Engine 32

The Supervisor Engine 32 supports the following flash memory:

disk0:One external CompactFlash Type II slot (supports CompactFlash Type II Flash PC cards) sup-bootdisk: 256 MB internal CompactFlash memory (from ROMMON, it is bootdisk:)
Supervisor Engine 32 Ports

The console port for the Supervisor Engine 32 port is an EIA/TIA-232 (RS-232) port. The Supervisor Engine 32 also has two Universal Serial Bus (USB) 2.0 ports that are not currently enabled. WS-SUP32-GE-3B ports 1 through 8 have small form-factor pluggable (SFP) connectors and port 9 is a 10/100/1000 Mbps RJ-45 port. WS-SUP32-10GE ports 1 and 2 are 10 Gigabit Ethernet ports that accept XENPAKs and port 3 is a 10/100/1000 Mbps RJ-45 port.
Tip
5-2
OL-3999-08
C H A P T E R
Configuring the Supervisor Engine 2 and the Switch Fabric Module

This chapter describes how to configure the Supervisor Engine 2 and the Switch Fabric Module (SFM) for the Catalyst 6500 series switches.
Note
Release 12.2(18)SXE and rebuilds of Release 12.2(18)SXE do not support Supervisor Engine 2. For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SXat this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html

Using the Slots on a Supervisor Engine 2, page 6-1 Understanding How the Switch Fabric Module Works, page 6-2 Configuring the Switch Fabric Module, page 6-3 Monitoring the Switch Fabric Module, page 6-5
Tip
Using the Slots on a Supervisor Engine 2

The Supervisor Engine 2 has one Flash PC card (PCMCIA) slot. With PCMCIA Advanced Technology Attachment (ATA) FlashDisk devices, the keyword for the slot on the active Supervisor Engine 2 is disk0: and the keyword for the slot on a redundant Supervisor Engine 2 is slavedisk0:. With non-ATA Flash PC cards, the keyword for the slot on the active Supervisor Engine 2 is slot0: and the keyword for the slot on a redundant Supervisor Engine 2 is slaveslot0:.
6-1
Chapter 6 Understanding How the Switch Fabric Module Works
Understanding How the Switch Fabric Module Works

These sections describe how the Switch Fabric Module works:

Switch Fabric Module Overview, page 6-2 Switch Fabric Module Slots, page 6-2 Switch Fabric Redundancy, page 6-2 Forwarding Decisions for Layer 3-Switched Traffic, page 6-2 Switching Modes, page 6-3
Switch Fabric Module Overview

The Switch Fabric Module creates a dedicated connection between fabric-enabled modules and provides uninterrupted transmission of frames between these modules. In addition to the direct connection between fabric-enabled modules provided by the Switch Fabric Module, fabric-enabled modules also have a direct connection to the 32-Gbps forwarding bus. The Switch Fabric Module does not have a console. A two-line LCD display on the front panel shows fabric utilization, software revision, and basic system information.
Switch Fabric Module Slots

With a 13-slot chassis, install the Switch Fabric Modules in either slot 7 or 8.
Note
In a 13-slot chassis, only slots 9 through 13 support dual switch fabric interface switching modules (for example, WS-X6816-GBIC). With all other chassis, install the Switch Fabric Modules in either slot 5 or 6.
Switch Fabric Redundancy

The Switch Fabric Module first installed functions as the primary module. For redundancy, you can install a redundant Switch Fabric Module. When two Switch Fabric Modules are installed at the same time, the module in the upper slot functions as the primary module, and the one in the lower slot functions as the backup. If you reset the module installed in the upper slot, the one in the lower slot becomes active. No configuration is required for Switch Fabric Module redundancy. The module in the upper slot functions as the primary module and a redundant Switch Fabric Module in the lower slot automatically takes over if the primary module fails.
Forwarding Decisions for Layer 3-Switched Traffic

Either a PFC2 or a Distributed Feature Card (DFC) makes the forwarding decision for Layer 3-switched traffic as follows:
6-2
OL-3999-08
Chapter 6
Configuring the Supervisor Engine 2 and the Switch Fabric Module Configuring the Switch Fabric Module
A PFC2 makes all forwarding decisions for each packet that enter the switch through a module without a DFC. A DFC makes all forwarding decisions for each packet that enters the switch on a DFC-enabled module in these situations:
If the egress port is on the same module as the ingress port, the DFC forwards the packet locally
(the packet never leaves the module).

If the egress port is on a different fabric-enabled module, the DFC sends the packet across the
SFM to the egress module, which sends it out the egress port.
If the egress port is on a different nonfabric-enabled module, the DFC sends the packet across
the SFM to the Supervisor Engine 2. The Supervisor Engine 2 fabric interface transfers the packet to the 32-Gbps switching bus where it is received by the egress module and is sent out the egress port.
Switching Modes
When you install a Switch Fabric Module, the traffic is forwarded to and from modules in one of the following modes:
Compact modeThe switch uses this mode for all traffic when only fabric-enabled modules are installed. In this mode, a compact version of the DBus header is forwarded over the switch fabric channel, which provides the best possible performance. Truncated modeThe switch uses this mode for traffic between fabric-enabled modules when there are both fabric-enabled and nonfabric-enabled modules installed. In this mode, the switch sends a truncated version of the traffic (the first 64 bytes of the frame) over the switch fabric channel. Bus mode (also called flow-through mode)The switch uses this mode for traffic between nonfabric-enabled modules and for traffic between a nonfabric-enabled module and a fabric-enabled module. In this mode, all traffic passes between the local bus and the supervisor engine bus.
Table 6-1 shows the switching modes used with fabric-enabled and nonfabric-enabled modules installed.
Table 6-1 Switching Modes with Switch Fabric Module Installed
Modules Between fabric-enabled modules (when no nonfabric-enabled modules are installed) Between fabric-enabled modules (when nonfabric-enabled modules are also installed) Between fabric-enabled and nonfabric-enabled modules Between non-fabric-enabled modules
Switching Modes Compact1 Truncated2 Bus Bus
1. In show commands, displayed as dcef mode for fabric-enabled modules with DFC installed; displayed as fabric mode for other fabric-enabled modules. 2. Displayed as fabric mode in show commands.
Configuring the Switch Fabric Module

These section describe configuring the Switch Fabric Module:
Configuring the Switching Mode, page 6-4
6-3
Chapter 6 Configuring the Switch Fabric Module
Configuring Fabric-Required Mode, page 6-4 Configuring an LCD Message, page 6-5
Note
When you are in configuration mode you can enter EXEC mode-level commands by entering the do keyword before the EXEC mode-level command.
Configuring the Switching Mode

To configure the switching mode, perform this task: Command
Router(config)# [no] fabric switching-mode allow {bus-mode | {truncated [{threshold [number]}]}
Purpose Configures the switching mode.
When configuring the switching mode, note the following information:

To allow use of nonfabric-enabled modules or to allow fabric-enabled modules to use bus mode, enter the fabric switching-mode allow bus-mode command. To prevent use of nonfabric-enabled modules or to prevent fabric-enabled modules from using bus mode, enter the no fabric switching-mode allow bus-mode command.
Caution
When you enter the no fabric switching-mode allow bus-mode command, power is removed from any nonfabric-enabled modules installed in the switch.

To allow fabric-enabled modules to use truncated mode, enter the fabric switching-mode allow truncated command. To prevent fabric-enabled modules from using truncated mode, enter the no fabric switching-mode allow truncated command. To configure how many fabric-enabled modules must be installed before they use truncated mode instead of bus mode, enter the fabric switching-mode allow truncated threshold number command. To return to the default truncated-mode threshold, enter the no fabric switching-mode allow truncated threshold command.
Configuring Fabric-Required Mode

To configure fabric-required mode, which prevents all switching modules from operating unless there is a Switch Fabric Module installed, perform this task: Command
Router(config)# fabric required
Purpose Configures fabric-required mode, which prevents switching modules from operating without a switch fabric module. Clears fabric-required mode.
Router(config)# no fabric required
6-4
OL-3999-08
Chapter 6
Configuring the Supervisor Engine 2 and the Switch Fabric Module Monitoring the Switch Fabric Module
Caution
If you enter the fabric required command on a switch that does not have a Switch Fabric Module installed, all modules except the supervisor engine turn off. When configuring fabric-required mode, note the following information:

If you boot the switch with fabric-required mode configured but without a Switch Fabric Module installed, only the supervisor engine receives power; no switching modules power up. When the switch is operating with fabric-required mode configured and a Switch Fabric Module installed, if you remove the switch fabric module or if it fails, the switch removes power from all switching modules; only the supervisor engine remains active. When the switch is operating with fabric-required mode configured and with redundant Switch Fabric Modules installed, if you remove both switch fabric modules or if both fail, the switch removes power from all switching modules; only the supervisor engine remains active.
Configuring an LCD Message

To configure a message for display on the LCD, perform this task: Command
Router(config)# fabric lcd-banner d message d Router(config)# no fabric lcd-banner
Purpose Configures a message for display on the LCD. Clears the message displayed on the LCD.
When configuring a message for display on the LCD, note the following information:

The d parameter is a delimiting character. You cannot use the delimiting character in the message. The delimiter is a character of your choicea pound sign (#), for example. You can use the following tokens, in the form $(token), in the message text:
$(hostname)Displays the switchs host name. $(domain)Displays the switchs domain name.
Monitoring the Switch Fabric Module

The Switch Fabric Module supports a number of show commands for monitoring purposes. A fully automated startup sequence brings the module online and runs the connectivity diagnostics on the ports. These sections describe how to monitor the Switch Fabric Module:

Displaying the Module Information, page 6-7 Displaying the Switch Fabric Module Redundancy Status, page 6-7 Displaying Fabric Channel Switching Modes, page 6-7 Displaying the Fabric Status, page 6-8 Displaying the Fabric Utilization, page 6-8 Displaying Fabric Errors, page 6-8
6-5
Chapter 6 Monitoring the Switch Fabric Module
Note
The Switch Fabric Module does not require any user configuration.
6-6
OL-3999-08
Chapter 6
Displaying the Module Information

To display the module information, perform this task: Command
Router# show module {5 | 6 | 7 | 8}
Purpose Displays module information.
This example shows how to display module information:

Router# show module 5 Mod Ports Card Type Model Serial No. --- ----- -------------------------------------- ------------------ ----------5 0 Switching Fabric Module WS-C6500-SFM SAD04420JR5 Mod MAC addresses Hw Fw Sw Status --- ---------------------------------- ------ ------------ ------------ ------5 0001.0002.0003 to 0001.0002.0003 1.0 6.1(3) 6.2(0.97) Ok
Displaying the Switch Fabric Module Redundancy Status

To display the switch fabric module redundancy status, perform this task: Command
Router# show fabric active
Purpose Displays switch fabric module redundancy status.
This example shows how to display the switch fabric module redundancy status:
Router# show fabric active Active fabric card in slot 5 No backup fabric card in the system Router#
Displaying Fabric Channel Switching Modes

To display the fabric channel switching mode of one or all modules, perform this task: Command
Router# show fabric switching-mode [module {slot_number | all]
Purpose Displays fabric channel switching mode of one or all modules.
This example shows how to display the fabric channel switching mode of all modules:
Router# show fabric switching-mode all bus-only mode is allowed Module Slot Switching Mode 1 Bus 2 Bus 3 DCEF 4 DCEF 5 No Interfaces 6 DCEF
6-7
Displaying the Fabric Status

To display the fabric status of one or all switching modules, perform this task: Command
Router# show fabric status [slot_number | all]
Purpose Displays fabric status.
This example shows how to display the fabric status of all modules:
Router# show fabric status all slot channel module status status 1 0 OK 3 0 OK 3 1 OK 4 0 OK Router# fabric OK OK OK OK
Displaying the Fabric Utilization

To display the fabric utilization of one or all modules, perform this task: Command
Router# show fabric utilization [slot_number | all]
Purpose Displays fabric utilization.
This example shows how to display the fabric utilization of all modules:
Router# show fabric utilization all slot channel Ingress % Egress 1 0 0 3 0 0 3 1 0 4 0 0 4 1 0 6 0 0 6 1 0 7 0 0 7 1 0 Router# % 0 0 0 0 0 0 0 0 0
Displaying Fabric Errors

To display fabric errors of one or all modules, perform this task: Command
Router# show fabric errors [slot_number | all]
Purpose Displays fabric errors.
6-8
OL-3999-08
Chapter 6
This example shows how to display fabric errors on all modules:

Router# show fabric errors slot channel module crc 1 0 0 3 0 0 3 1 0 4 0 0 4 1 0 6 0 0 6 1 0 7 0 0 7 1 0 Router# module hbeat 0 0 0 0 0 0 0 0 0 module sync 0 0 0 0 0 0 0 0 0 fabric sync 0 0 0 0 0 0 0 0 0
Tip
6-9
6-10
OL-3999-08
C H A P T E R
Configuring NSF with SSO Supervisor Engine Redundancy

This chapter describes how to configure supervisor engine redundancy using Cisco nonstop forwarding (NSF) with stateful switchover (SSO).
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html Release 12.2(18)SXD and later releases support nonstop forwarding (NSF) with stateful switchover (SSO) on all supervisor engines. All releases support RPR and RPR+ (see Chapter 8, Configuring RPR and RPR+ Supervisor Engine Redundancy) NSF with SSO does not support IPv6 multicast traffic.

Understanding NSF with SSO Supervisor Engine Redundancy, page 7-2 Supervisor Engine Configuration Synchronization, page 7-9 NSF Configuration Tasks, page 7-11 Copying Files to the Redundant Supervisor Engine, page 7-20
Tip
7-1
Chapter 7 Understanding NSF with SSO Supervisor Engine Redundancy
Understanding NSF with SSO Supervisor Engine Redundancy

These sections describe supervisor engine redundancy using NSF with SSO:

NSF with SSO Supervisor Engine Redundancy Overview, page 7-2 SSO Operation, page 7-3 NSF Operation, page 7-3 Cisco Express Forwarding, page 7-3 Multicast MLS NSF with SSO, page 7-4 Routing Protocols, page 7-4 NSF Benefits and Restrictions, page 7-8
NSF with SSO Supervisor Engine Redundancy Overview

Note
With Release 12.2(18)SXD and earlier releases, when a redundant supervisor engine is in standby mode, the two Gigabit Ethernet interfaces on the redundant supervisor engine are always active. With a Supervisor Engine 720 and Release 12.2(18)SXE and later releases, if all the installed switching modules have DFCs, enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on both supervisor engines, which ensures that all modules are operating in dCEF mode and simplifies switchover to the redundant supervisor engine. (CSCec05612) With a Supervisor Engine 2 and Release 12.2(18)SXD1 and later releases, if all the installed switching modules have DFCs, enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on the redundant supervisor engine, which ensures that all modules are operating in dCEF mode. (CSCec05612)
Catalyst 6500 series switches support fault resistance by allowing a redundant supervisor engine to take over if the primary supervisor engine fails. Cisco NSF works with SSO to minimize the amount of time a network is unavailable to its users following a switchover while continuing to forward IP packets. Catalyst 6500 series switches also support route processor redundancy (RPR), route processor redundancy plus (RPR+), and single router mode with stateful switchover (SRM with SSO) for redundancy. For information about these redundancy modes, see Chapter 8, Configuring RPR and RPR+ Supervisor Engine Redundancy. The following events cause a switchover:

A hardware failure on the active supervisor engine Clock synchronization failure between supervisor engines A manual switchover
7-2
OL-3999-08
Chapter 7
Configuring NSF with SSO Supervisor Engine Redundancy Understanding NSF with SSO Supervisor Engine Redundancy
SSO Operation
SSO establishes one of the supervisor engines as active while the other supervisor engine is designated as standby, and then SSO synchronizes information between them. A switchover from the active to the redundant supervisor engine occurs when the active supervisor engine fails, or is removed from the switch, or is manually shut down for maintenance. This type of switchover ensures that Layer 2 traffic is not interrupted. In networking devices running SSO, both supervisor engines must be running the same configuration so that the redundant supervisor engine is always ready to assume control following a fault on the active supervisor engine. SSO switchover also preserves FIB and adjacency entries and can forward Layer 3 traffic after a switchover. Configuration information and data structures are synchronized from the active to the redundant supervisor engine at startup and whenever changes to the active supervisor engine configuration occur. Following an initial synchronization between the two supervisor engines, SSO maintains state information between them, including forwarding information. During switchover, system control and routing protocol execution is transferred from the active supervisor engine to the redundant supervisor engine. The switch requires between 0 and 3 seconds to switchover from the active to the redundant supervisor engine.
NSF Operation
Cisco NSF always runs with SSO and provides redundancy for Layer 3 traffic. NSF works with SSO to minimize the amount of time that a network is unavailable to its users following a switchover. The main purpose of NSF is to continue forwarding IP packets following a supervisor engine switchover. Cisco NSF is supported by the BGP, OSPF, and IS-IS protocols for routing and is supported by Cisco Express Forwarding (CEF) for forwarding. The routing protocols have been enhanced with NSF-capability and awareness, which means that routers running these protocols can detect a switchover and take the necessary actions to continue forwarding network traffic and to recover route information from the peer devices. The IS-IS protocol can be configured to use state information that has been synchronized between the active and the redundant supervisor engine to recover route information following a switchover instead of information received from peer devices. A networking device is NSF-aware if it is running NSF-compatible software. A device is NSF-capable if it has been configured to support NSF; it will rebuild routing information from NSF-aware or NSF-capable neighbors. Each protocol depends on CEF to continue forwarding packets during switchover while the routing protocols rebuild the Routing Information Base (RIB) tables. After the routing protocols have converged, CEF updates the FIB table and removes stale route entries. CEF then updates the line cards with the new FIB information.
Cisco Express Forwarding

A key element of NSF is packet forwarding. In a Cisco networking device, packet forwarding is provided by Cisco Express Forwarding (CEF). CEF maintains the FIB, and uses the FIB information that was current at the time of the switchover to continue forwarding packets during a switchover. This feature reduces traffic interruption during the switchover. During normal NSF operation, CEF on the active supervisor engine synchronizes its current FIB and adjacency databases with the FIB and adjacency databases on the redundant supervisor engine. Upon switchover of the active supervisor engine, the redundant supervisor engine initially has FIB and adjacency databases that are mirror images of those that were current on the active supervisor engine.
7-3
For platforms with intelligent line cards, the line cards will maintain the current forwarding information over a switchover. For platforms with forwarding engines, CEF will keep the forwarding engine on the redundant supervisor engine current with changes that are sent to it by CEF on the active supervisor engine. The line cards or forwarding engines will be able to continue forwarding after a switchover as soon as the interfaces and a data path are available. As the routing protocols start to repopulate the RIB on a prefix-by-prefix basis, the updates will cause prefix-by-prefix updates to CEF, which it uses to update the FIB and adjacency databases. Existing and new entries will receive the new version (epoch) number, indicating that they have been refreshed. The forwarding information is updated on the line cards or forwarding engine during convergence. The supervisor engine signals when the RIB has converged. The software removes all FIB and adjacency entries that have an epoch older than the current switchover epoch. The FIB now represents the newest routing protocol forwarding information.
Multicast MLS NSF with SSO

Note
NSF with SSO does not support IPv6 multicast traffic. If you configure support for IPv6 multicast traffic, configure RPR or RPR+ redundancy. Multicast multilayer switching (MMLS) NSF with SSO is required so that Layer 3 multicast traffic that is switched by the router is not dropped during switchover. Without MMLS NSF with SSO, the Layer 3 multicast traffic is dropped until the multicast protocols converge. During the switchover process, traffic is forwarded using the old database (from the previously active supervisor engine). After multicast routing protocol convergence has taken place, the shortcuts downloaded by the newly active MSFC will be merged with the existing flows and marked as new shortcuts. Stale entries will slowly be purged from the database allowing NSF to function during the switchover while ensuring a smooth transition to the new cache. Because multicast routing protocols such as Protocol Independent Multicast (PIM) sparse mode and PIM dense mode are data driven, multicast packets are leaked to the router during switchover so that the protocols can converge. Because the traffic does not need to be forwarded by software for control-driven protocols such as bidirectional PIM, the switch will continue to leak packets using the old cache for these protocols. The router builds the mroute cache and installs the shortcuts in hardware. After the new routes are learned, a timer is triggered to go through the database and purge the old flows.
Note
Multicast MLS NSF with SSO requires NSF support in the unicast protocols.
Routing Protocols
The routing protocols run only on the MSFC of the active supervisor engine, and they receive routing updates from their neighbor routers. Routing protocols do not run on the MSFC of the redundant supervisor engine. Following a switchover, the routing protocols request that the NSF-aware neighbor devices send state information to help rebuild the routing tables. Alternately, the IS-IS protocol can be configured to synchronize state information from the active to the redundant supervisor engine to help rebuild the routing table on the NSF-capable device in environments where neighbor devices are not NSF-aware. Cisco NSF supports the BGP, OSPF, IS-IS, and EIGRP protocols
7-4
OL-3999-08
Chapter 7
Note
For NSF operation, the routing protocols depend on CEF to continue forwarding packets while the routing protocols rebuild the routing information.
BGP Operation
When an NSF-capable router begins a BGP session with a BGP peer, it sends an OPEN message to the peer. Included in the message is a statement that the NSF-capable device has graceful restart capability. Graceful restart is the mechanism by which BGP routing peers avoid a routing flap following a switchover. If the BGP peer has received this capability, it is aware that the device sending the message is NSF-capable. Both the NSF-capable router and its BGP peers need to exchange the graceful restart capability in their OPEN messages at the time of session establishment. If both the peers do not exchange the graceful restart capability, the session will not be graceful restart capable. If the BGP session is lost during the supervisor engine switchover, the NSF-aware BGP peer marks all the routes associated with the NSF-capable router as stale; however, it continues to use these routes to make forwarding decisions for a set period of time. This functionality prevents packets from being lost while the newly active supervisor engine is waiting for convergence of the routing information with the BGP peers. After a supervisor engine switchover occurs, the NSF-capable router reestablishes the session with the BGP peer. In establishing the new session, it sends a new graceful restart message that identifies the NSF-capable router as having restarted. At this point, the routing information is exchanged between the two BGP peers. After this exchange is complete, the NSF-capable device uses the routing information to update the RIB and the FIB with the new forwarding information. The NSF-aware device uses the network information to remove stale routes from its BGP table; the BGP protocol then is fully converged. If a BGP peer does not support the graceful restart capability, it will ignore the graceful restart capability in an OPEN message but will establish a BGP session with the NSF-capable device. This function will allow interoperability with non-NSF-aware BGP peers (and without NSF functionality), but the BGP session with non-NSF-aware BGP peers will not be graceful restart capable.
Note
BGP support in NSF requires that neighbor networking devices be NSF-aware; that is, the devices must have the graceful restart capability and advertise that capability in their OPEN message during session establishment. If an NSF-capable router discovers that a particular BGP neighbor does not have graceful restart capability, it will not establish an NSF-capable session with that neighbor. All other neighbors that have graceful restart capability will continue to have NSF-capable sessions with this NSF-capable networking device.
OSPF Operation
When an OSPF NSF-capable router performs a supervisor engine switchover, it must perform the following tasks in order to resynchronize its link state database with its OSPF neighbors:

Relearn the available OSPF neighbors on the network without causing a reset of the neighbor relationship Reacquire the contents of the link state database for the network
7-5
As quickly as possible after a supervisor engine switchover, the NSF-capable router sends an OSPF NSF signal to neighboring NSF-aware devices. Neighbor networking devices recognize this signal as an indicator that the neighbor relationship with this router should not be reset. As the NSF-capable router receives signals from other routers on the network, it can begin to rebuild its neighbor list. After neighbor relationships are reestablished, the NSF-capable router begins to resynchronize its database with all of its NSF-aware neighbors. At this point, the routing information is exchanged between the OSPF neighbors. Once this exchange is complete, the NSF-capable device uses the routing information to remove stale routes, update the RIB, and update the FIB with the new forwarding information. The OSPF protocols are then fully converged.
Note
OSPF NSF requires that all neighbor networking devices be NSF-aware. If an NSF-capable router discovers that it has non-NSF-aware neighbors on a particular network segment, it will disable NSF capabilities for that segment. Other network segments composed entirely of NSF-capable or NSF-aware routers will continue to provide NSF capabilities.
IS-IS Operation
When an IS-IS NSF-capable router performs a supervisor engine switchover, it must perform the following tasks in order to resynchronize its link state database with its IS-IS neighbors:

Relearn the available IS-IS neighbors on the network without causing a reset of the neighbor relationship Reacquire the contents of the link state database for the network Internet Engineering Task Force (IETF) IS-IS Cisco IS-IS
The IS-IS NSF feature offers two options when you configure NSF:

If neighbor routers on a network segment are running a software version that supports the IETF Internet draft for router restartability, they will assist an IETF NSF router that is restarting. With IETF, neighbor routers provide adjacency and link-state information to help rebuild the routing information following a switchover. A benefit of IETF IS-IS configuration is operation between peer devices based on a proposed standard.
Note
If you configure IETF on the networking device, but neighbor routers are not IETF-compatible, NSF will abort following a switchover. If the neighbor routers on a network segment are not NSF-aware, you must use the Cisco configuration option. The Cisco IS-IS configuration transfers both protocol adjacency and link-state information from the active to the redundant supervisor engine. An advantage of Cisco configuration is that it does not rely on NSF-aware neighbors.
IETF IS-IS Configuration

As quickly as possible after a supervisor engine switchover, the NSF-capable router sends IS-IS NSF restart requests to neighboring NSF-aware devices using the IETF IS-IS configuration. Neighbor networking devices recognize this restart request as an indicator that the neighbor relationship with this router should not be reset, but that they should initiate database resynchronization with the restarting router. As the restarting router receives restart request responses from routers on the network, it can begin to rebuild its neighbor list.
7-6
OL-3999-08
Chapter 7
After this exchange is complete, the NSF-capable device uses the link-state information to remove stale routes, update the RIB, and update the FIB with the new forwarding information; IS-IS is then fully converged. The switchover from one supervisor engine to the other happens within seconds. IS-IS reestablishes its routing table and resynchronizes with the network within a few additional seconds. At this point, IS-IS waits for a specified interval before it will attempt a second NSF restart. During this time, the new redundant supervisor engine will boot up and synchronize its configuration with the active supervisor engine. The IS-IS NSF operation waits for a specified interval to ensure that connections are stable before attempting another restart of IS-IS NSF. This functionality prevents IS-IS from attempting back-to-back NSF restarts with stale information.
Cisco IS-IS Configuration

Using the Cisco configuration option, full adjacency and LSP information is saved, or checkpointed, to the redundant supervisor engine. Following a switchover, the newly active supervisor engine maintains its adjacencies using the check-pointed data, and can quickly rebuild its routing tables.
Note
Following a switchover, Cisco IS-IS NSF has complete neighbor adjacency and LSP information; however, it must wait for all interfaces to come on line that had adjacencies prior to the switchover. If an interface does not come on line within the allocated interface wait time, the routes learned from these neighbor devices are not considered in routing table recalculation. IS-IS NSF provides a command to extend the wait time for interfaces that, for whatever reason, do not come on line in a timely fashion. The switchover from one supervisor engine to the other happens within seconds. IS-IS reestablishes its routing table and resynchronizes with the network within a few additional seconds. At this point, IS-IS waits for a specified interval before it will attempt a second NSF restart. During this time, the new redundant supervisor engine will boot up and synchronize its configuration with the active supervisor engine. After this synchronization is completed, IS-IS adjacency and LSP data is check-pointed to the redundant supervisor engine; however, a new NSF restart will not be attempted by IS-IS until the interval time expires. This functionality prevents IS-IS from attempting back-to-back NSF restarts.
EIGRP Operation
When an EIGRP NSF-capable router initially comes back up from an NSF restart, it has no neighbor and its topology table is empty. The router is notified by the redundant (now active) supervisor engine when it needs to bring up the interfaces, reacquire neighbors, and rebuild the topology and routing tables. The restarting router and its peers must accomplish these tasks without interrupting the data traffic directed toward the restarting router. EIGRP peer routers maintain the routes learned from the restarting router and continue forwarding traffic through the NSF restart process. To prevent an adjacency reset by the neighbors, the restarting router will use a new Restart (RS) bit in the EIGRP packet header to indicate a restart. The RS bit will be set in the hello packets and in the initial INIT update packets during the NSF restart period. The RS bit in the hello packets allows the neighbors to be quickly notified of the NSF restart. Without seeing the RS bit, the neighbor can only detect an adjacency reset by receiving an INIT update or by the expiration of the hello hold timer. Without the RS bit, a neighbor does not know if the adjacency reset should be handled using NSF or the normal startup method.
7-7
When the neighbor receives the restart indication, either by receiving the hello packet or the INIT packet, it will recognize the restarting peer in its peer list and will maintain the adjacency with the restarting router. The neighbor then sends it topology table to the restarting router with the RS bit set in the first update packet indicating that it is NSF-aware and is helping out the restarting router. The neighbor does not set the RS bit in their hello packets, unless it is also a NSF restarting neighbor.
Note
A router may be NSF-aware but may not be participating in helping out the NSF restarting neighbor because it is coming up from a cold start. If at least one of the peer routers is NSF-aware, the restarting router would then receive updates and rebuild its database. The restarting router must then find out if it had converged so that it can notify the routing information base (RIB). Each NSF-aware router is required to send an end of table (EOT) marker in the last update packet to indicate the end of the table content. The restarting router knows it has converged when it receives the EOT marker. The restarting router can then begin sending updates. An NSF-aware peer would know when the restarting router had converged when it receives an EOT indication from the restarting router. The peer then scans its topology table to search for the routes with the restarted neighbor as the source. The peer compares the route timestamp with the restart event timestamp to determine if the route is still available. The peer then goes active to find alternate paths for the routes that are no longer available through the restarted router. When the restarting router has received all EOT indications from its neighbors or when the NSF converge timer expires, EIGRP will notify the RIB of convergence. EIGRP waits for the RIB convergence signal and then floods its topology table to all awaiting NSF-aware peers.
NSF Benefits and Restrictions

Cisco NSF provides these benefits:
Improved network availability NSF continues forwarding network traffic and application state information so that user session information is maintained after a switchover.
Overall network stability Network stability may be improved with the reduction in the number of route flaps that had been created when routers in the network failed and lost their routing tables.
Neighboring routers do not detect a link flap Because the interfaces remain up throughout a switchover, neighboring routers do not detect a link flap (the link does not go down and come back up).
Prevents routing flaps Because SSO continues forwarding network traffic in the event of a switchover, routing flaps are avoided.
No loss of user sessions User sessions established before the switchover are maintained.
Cisco NSF with SSO has these restrictions:

For NSF operation, you must have SSO configured on the device. NSF with SSO supports IP Version 4 traffic and protocols only.
7-8
OL-3999-08
Chapter 7
Configuring NSF with SSO Supervisor Engine Redundancy Supervisor Engine Configuration Synchronization
Enhanced Object Tracking is not SSO-aware and cannot be used with Hot Standby Routing Protocol (HSRP), Virtual Router Redundancy Protocol (VRRP), or Gateway Load Balancing Protocol (GLBP) in SSO mode. The HSRP is not SSO-aware, meaning state information is not maintained between the active and standby supervisor engine during normal operation. HSRP and SSO can coexist but both features work independently. Traffic that relies on HSRP may switch to the HSRP standby in the event of a supervisor switchover. The Gateway Load Balancing Protocol (GLBP) is not SSO-aware, meaning state information is not maintained between the active and standby supervisor engine during normal operation. GLBP and SSO can coexist but both features work independently. Traffic that relies on GLBP may switch to the GLBP standby in the event of a Supervisor switchover. The Virtual Redundancy Routing Protocols (VRRP) is not SSO-aware, meaning state information is not maintained between the active and standby supervisor engine during normal operation. VRRP and SSO can coexist but both features work independently. Traffic that relies on VRRP may switch to the VRRP standby in the event of a supervisor switchover. Multiprotocol Label Switching (MPLS) is not suported with Cisco NSF with SSO; however, MPLS and NSF with SSO can coexist. If NSF with SSO is configured in the same chassis with MPLS, the failover performance of MPLS protocols will be at least equivalent to RPR+ while the supported NSF with SSO protocols still retain the additional benefits of NSF with SSO. All neighboring devices participating in BGP NSF must be NSF-capable and configured for BGP graceful restart. OSPF NSF for virtual links is not supported. All OSPF networking devices on the same network segment must be NSF-aware (running an NSF software image). For IETF IS-IS, all neighboring devices must be running an NSF-aware software image. IPv4 Multicast NSF with SSO is supported by the PFC3 only. The underlying unicast protocols must be NSF-aware in order to use multicast NSF with SSO. Bidirectional forwarding detection (BFD) is not SSO-aware and is not supported by NSF with SSO.
Supervisor Engine Configuration Synchronization

These sections describe supervisor engine configuration synchronization:

Supervisor Engine Redundancy Guidelines and Restrictions, page 7-10 Redundancy Configuration Guidelines and Restrictions, page 7-10
Note
Configuration changes made through SNMP are not synchronized to the redundant supervisor engine. After you configure the switch through SNMP, copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine.
7-9
Chapter 7 Supervisor Engine Configuration Synchronization
Supervisor Engine Redundancy Guidelines and Restrictions

These sections describe supervisor engine redundancy guidelines and restrictions:

Redundancy Configuration Guidelines and Restrictions, page 7-10 Hardware Configuration Guidelines and Restrictions, page 7-10 Configuration Mode Restrictions, page 7-11
Redundancy Configuration Guidelines and Restrictions

These guidelines and restrictions apply to all redundancy modes:

With Release 12.2(18)SXD and earlier releases, when a redundant supervisor engine is in standby mode, the two Gigabit Ethernet interfaces on the redundant supervisor engine are always active. With a Supervisor Engine 720 and Release 12.2(18)SXE and later releases, if all the installed switching modules have DFCs, enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on both supervisor engines, which ensures that all modules are operating in dCEF mode and simplifies switchover to the redundant supervisor engine. With a Supervisor Engine 2 and Release 12.2(18)SXD1 and later releases, if all the installed switching modules have DFCs, enter the fabric switching-mode allow dcef-only command to disable the Ethernet ports on the redundant supervisor engine, which ensures that all modules are operating in dCEF mode. Supervisor engine redundancy does not provide supervisor engine mirroring or supervisor engine load balancing. Only one supervisor engine is active. Configuration changes made through SNMP are not synchronized to the redundant supervisor engine. After you configure the switch through SNMP, copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine. Supervisor engine switchover takes place after the failed supervisor engine completes a core dump. A core dump can take up to 15 minutes. To get faster switchover time, disable core dump on the supervisor engines. With a Supervisor Engine 720 and Release 12.2(18)SXF and later releases, if a fabric synchronization error occurs, the default behavior is to switchover to the redundant supervisor engine. In some cases, a switchover to the redundant supervisor engine is more disruptive than powering down the module that caused the fabric synchronization error. Enter the no fabric error-recovery fabric-switchover command to disable the switchover and power down the module with the fabric synchronization error.
Hardware Configuration Guidelines and Restrictions

For redundant operation, the following guidelines and restrictions must be met:
Cisco IOS running on the supervisor engine and the MSFC supports redundant configurations where the supervisor engines and MSFC routers are identical. If they are not identical, one will boot first and become active and hold the other supervisor engine and MSFC in a reset condition. Each supervisor engine must have the resources to run the switch on its own, which means all supervisor engine resources are duplicated, including all flash devices.
7-10
OL-3999-08
Chapter 7
Configuring NSF with SSO Supervisor Engine Redundancy NSF Configuration Tasks
Make separate console connections to each supervisor engine. Do not connect a Y cable to the console ports. Both supervisor engines must have the same system image (see the Copying Files to the Redundant Supervisor Engine section on page 7-20).
Note
If a newly installed redundant supervisor engine has the Catalyst operating system installed, remove the active supervisor engine and boot the switch with only the redundant supervisor engine installed. Follow the procedures in the current release notes to convert the redundant supervisor engine from the Catalyst operating system.
The configuration register in the startup-config must be set to autoboot.
Note
There is no support for booting from the network.
Configuration Mode Restrictions

The following configuration restrictions apply during the startup synchronization process:
You cannot perform configuration changes during the startup (bulk) synchronization. If you attempt to make configuration changes during this process, the following message is generated:
Config mode locked out till standby initializes
If configuration changes occur at the same time as a supervisor engine switchover, these configuration changes are lost.
NSF Configuration Tasks

The following sections describe the configuration tasks for the NSF feature:

Configuring SSO, page 7-12 Configuring Multicast MLS NSF with SSO, page 7-12 Verifying Multicast NSF with SSO, page 7-13 Configuring CEF NSF, page 7-13 Verifying CEF NSF, page 7-13 Configuring BGP NSF, page 7-14 Verifying BGP NSF, page 7-14 Configuring OSPF NSF, page 7-15 Verifying OSPF NSF, page 7-15 Configuring IS-IS NSF, page 7-16 Verifying IS-IS NSF, page 7-17
7-11
Chapter 7 NSF Configuration Tasks
Configuring SSO
You must configure SSO in order to use NSF with any supported protocol. To configure SSO, perform this task: Command
Step 1 Step 2
Router(config)# redundancy Router(config-red)# mode sso
Purpose Enters redundancy configuration mode. Configures SSO. When this command is entered, the redundant supervisor engine is reloaded and begins to work in SSO mode. Verifies that SSO is enabled. Displays the operating redundancy mode.
Step 3 Step 4
Router# show running-config Router# show redundancy states
Note
The sso keyword is supported in Release 12.2(17b)SXA and later releases. This example shows how to configure the system for SSO and display the redundancy state:
Router> enable Router# configure terminal Enter configuration commands, one per line. Router(config)# redundancy Router(config-red)# mode sso Router(config-red)# end Router# show redundancy states my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Primary Unit ID = 5 Redundancy Mode Redundancy Mode Split Mode Manual Swact Communications (Operational) = sso (Configured) = sso = Disabled = Enabled = Up
End with CNTL/Z.
client count = 29 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask Router#
= = = = =
30000 milliseconds 9000 milliseconds 1 18 0x0
Configuring Multicast MLS NSF with SSO

Note
The commands in this section are optional and can be used to customize your configuration. For most users, the default settings are adequate.
7-12
OL-3999-08
Chapter 7
Multicast MLS NSF with SSO is on by default when SSO is selected as the redundancy mode. To configure multicast NSF with SSO parameters, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# mls ip multicast sso convergence-time time
Purpose Enters global configuration mode. Specifies the maximum time to wait for protocol convergence; valid values are from 0 to 3600 seconds. Specifies the packet leak interval; valid values are from 0 to 3600 seconds. For PIM sparse mode and PIM dense mode this is the period of time after which packet leaking for existing PIM sparse mode and PIM dense mode mutlitcast forwarding entries should be completed. Specifies the percentage of multicast flows; valid values are from 1 to 100 percent. The value represents the percentage of the total number of existing PIM sparse mode and PIM dense mode multicast flows that should be flagged for packet leaking.
Step 3
Router(config)# mls ip multicast sso leak interval
Step 4
Router(config)# mls ip multicast sso leak percentage
Verifying Multicast NSF with SSO

To verify the multicast NSF with SSO settings, enter the show mls ip multicast sso command:
router# show mls ip multicast sso Multicast SSO is enabled Multicast HA Parameters ---------------------------------------------------+------+ protocol convergence timeout 120 secs flow leak percent 10 flow leak interval 60 secs
Configuring CEF NSF

The CEF NSF feature operates by default while the networking device is running in SSO mode. No configuration is necessary.
Verifying CEF NSF

To verify that CEF is NSF-capable, enter the show cef state command:
router# show cef state CEF Status [RP] CEF enabled/running dCEF enabled/running CEF switching enabled/running CEF default capabilities: Always FIB switching: yes Default CEF switching: yes
7-13
Default dCEF switching: Update HWIDB counters: Drop multicast packets: . . . CEF NSF capable: IPC delayed func on SSO: RRP state: I am standby RRP: My logical slot: RF PeerComm:
yes no no
yes no no 0 no
Configuring BGP NSF

Note
You must configure BGP graceful restart on all peer devices participating in BGP NSF. To configure BGP for NSF, perform this task (repeat this procedure on each of the BGP NSF peer devices):
Command
Router# configure terminal Router(config)# router bgp as-number
Purpose Enters global configuration mode. Enables a BGP routing process, which places the router in router configuration mode. Enables the BGP graceful restart capability, starting BGP NSF. If you enter this command after the BGP session has been established, you must restart the session for the capability to be exchanged with the BGP neighbor. Use this command on the restarting router and all of its peers.
Router(config-router)# bgp graceful-restart
Verifying BGP NSF

To verify BGP NSF, you must check that the graceful restart function is configured on the SSO-enabled networking device and on the neighbor devices. To verify, follow these steps:
Step 1
Verify that bgp graceful-restart appears in the BGP configuration of the SSO-enabled router by entering the show running-config command:
Router# show running-config . . . router bgp 120 . . .
7-14
OL-3999-08
Chapter 7
bgp graceful-restart neighbor 10.2.2.2 remote-as 300 . . .
Step 2 Step 3
Repeat step 1 on each of the BGP neighbors. On the SSO device and the neighbor device, verify that the graceful restart function is shown as both advertised and received, and confirm the address families that have the graceful restart capability. If no address families are listed, then BGP NSF also will not occur:
router# show ip bgp neighbors x.x.x.x BGP neighbor is 192.168.2.2, remote AS YY, external link BGP version 4, remote router ID 192.168.2.2 BGP state = Established, up for 00:01:18 Last read 00:00:17, hold time is 180, keepalive interval is 60 seconds Neighbor capabilities: Route refresh:advertised and received(new) Address family IPv4 Unicast:advertised and received Address famiiy IPv4 Multicast:advertised and received Graceful Restart Capabilty:advertised and received Remote Restart timer is 120 seconds Address families preserved by peer: IPv4 Unicast, IPv4 Multicast Received 1539 messages, 0 notifications, 0 in queue Sent 1544 messages, 0 notifications, 0 in queue Default minimum time between advertisement runs is 30 seconds
Configuring OSPF NSF

Note
All peer devices participating in OSPF NSF must be made OSPF NSF-aware, which happens automatically once you install an NSF software image on the device. To configure OSPF NSF, perform this task:
Command
Router# configure terminal Router(config)# router ospf processID
Purpose Enters global configuration mode. Enables an OSPF routing process, which places the router in router configuration mode. Enables NSF operations for OSPF.
Router(config-router)# nsf
Verifying OSPF NSF

To verify OSPF NSF, you must check that the NSF function is configured on the SSO-enabled networking device. To verify OSPF NSF, follow these steps:
Step 1
Verify that nsf appears in the OSPF configuration of the SSO-enabled device by entering the show running-config command:
7-15
Router# show running-config router ospf 120 log-adjacency-changes nsf network 192.168.20.0 0.0.0.255 area 0 network 192.168.30.0 0.0.0.255 area 1 network 192.168.40.0 0.0.0.255 area 2 . . .
Step 2
Enter the show ip ospf command to verify that NSF is enabled on the device:
router> show ip ospf Routing Process "ospf 1" with ID 192.168.2.1 and Domain ID 0.0.0.1 Supports only single TOS(TOS0) routes Supports opaque LSA SPF schedule delay 5 secs, Hold time between two SPFs 10 secs Minimum LSA interval 5 secs. Minimum LSA arrival 1 secs Number of external LSA 0. Checksum Sum 0x0 Number of opaque AS LSA 0. Checksum Sum 0x0 Number of DCbitless external and opaque AS LSA 0 Number of DoNotAge external and opaque AS LSA 0 Number of areas in this router is 1. 1 normal 0 stub 0 nssa External flood list length 0 Non-Stop Forwarding enabled, last NSF restart 00:02:06 ago (took 44 secs) Area BACKBONE(0) Number of interfaces in this area is 1 (0 loopback) Area has no authentication SPF algorithm executed 3 times
Configuring IS-IS NSF

To configure IS-IS NSF, perform this task: Command
Router# configure terminal Router(config)# router isis [tag]
Purpose Enters global configuration mode. Enables an IS-IS routing process, which places the router in router configuration mode. Enables NSF operation for IS-IS. Enter the ietf keyword to enable IS-IS in a homogeneous network where adjacencies with networking devices supporting IETF draft-based restartability is guaranteed. Enter the cisco keyword to run IS-IS in heterogeneous networks that might not have adjacencies with NSF-aware networking devices.
Router(config-router)# nsf [cisco | ietf]
Step 4
Router(config-router)# nsf interval [minutes]
(Optional) Specifies the minimum time between NSF restart attempts. The default time between consecutive NSF restart attempts is 5 minutes.
7-16
OL-3999-08
Chapter 7
Command
Step 5
Router(config-router)# nsf t3 {manual [seconds] | adjacency}
Purpose (Optional) Specifies the time IS-IS will wait for the IS-IS database to synchronize before generating overloaded link-state information for itself and flooding that information out to its neighbors. The t3 keyword applies only if you selected IETF operation. When you specify adjacency, the router that is restarting obtains its wait time from neighboring devices.
Step 6
Router(config-router)# nsf interface wait seconds
(Optional) Specifies how long an IS-IS NSF restart will wait for all interfaces with IS-IS adjacencies to come up before completing the restart. The default is 10 seconds.
Verifying IS-IS NSF

To verify IS-IS NSF, you must check that the NSF function is configured on the SSO-enabled networking device. To verify IS-IS NSF, follow these steps:
Step 1
Verify that nsf appears in the IS-IS configuration of the SSO-enabled device by entering the show running-config command. The display will show either the Cisco IS-IS or the IETF IS-IS configuration. The following display indicates that the device uses the Cisco implementation of IS-IS NSF:
Router# show running-config <...Output Truncated...> router isis nsf cisco <...Output Truncated...>
Step 2
If the NSF configuration is set to cisco, enter the show isis nsf command to verify that NSF is enabled on the device. Using the Cisco configuration, the display output will be different on the active and redundant RPs. The following display shows sample output for the Cisco configuration on the active RP. In this example, note the presence of NSF restart enabled:
router# show isis nsf NSF is ENABLED, mode 'cisco' RP is ACTIVE, standby ready, bulk sync complete NSF interval timer expired (NSF restart enabled) Checkpointing enabled, no errors Local state:ACTIVE, Peer state:STANDBY HOT, Mode:SSO
The following display shows sample output for the Cisco configuration on the standby RP. In this example, note the presence of NSF restart enabled:
router# show isis nsf NSF enabled, mode 'cisco' RP is STANDBY, chkpt msg receive count:ADJ 2, LSP 7 NSF interval timer notification received (NSF restart enabled) Checkpointing enabled, no errors Local state:STANDBY HOT, Peer state:ACTIVE, Mode:SSO
7-17
Step 3
If the NSF configuration is set to ietf, enter the show isis nsf command to verify that NSF is enabled on the device. The following display shows sample output for the IETF IS-IS configuration on the networking device:
router# show isis nsf NSF is ENABLED, mode IETF NSF pdb state:Inactive NSF L1 active interfaces:0 NSF L1 active LSPs:0 NSF interfaces awaiting L1 CSNP:0 Awaiting L1 LSPs: NSF L2 active interfaces:0 NSF L2 active LSPs:0 NSF interfaces awaiting L2 CSNP:0 Awaiting L2 LSPs: Interface:Serial3/0/2 NSF L1 Restart state:Running NSF p2p Restart retransmissions:0 Maximum L1 NSF Restart retransmissions:3 L1 NSF ACK requested:FALSE L1 NSF CSNP requested:FALSE NSF L2 Restart state:Running NSF p2p Restart retransmissions:0 Maximum L2 NSF Restart retransmissions:3 L2 NSF ACK requested:FALSE Interface:GigabitEthernet2/0/0 NSF L1 Restart state:Running NSF L1 Restart retransmissions:0 Maximum L1 NSF Restart retransmissions:3 L1 NSF ACK requested:FALSE L1 NSF CSNP requested:FALSE NSF L2 Restart state:Running NSF L2 Restart retransmissions:0 Maximum L2 NSF Restart retransmissions:3 L2 NSF ACK requested:FALSE L2 NSF CSNP requested:FALSE Interface:Loopback1 NSF L1 Restart state:Running NSF L1 Restart retransmissions:0 Maximum L1 NSF Restart retransmissions:3 L1 NSF ACK requested:FALSE L1 NSF CSNP requested:FALSE NSF L2 Restart state:Running NSF L2 Restart retransmissions:0 Maximum L2 NSF Restart retransmissions:3 L2 NSF ACK requested:FALSE L2 NSF CSNP requested:FALSE
7-18
OL-3999-08
Chapter 7
Configuring EIGRP NSF

To configure EIGRP NSF, perform this task: Command
Router# configure terminal Router(config)# router eigrp as-number
Purpose Enters global configuration mode. Enables an EIGRP routing process, which places the router in router configuration mode. Enables EIGRP NSF. Use this command on the restarting router and all of its peers.
Router(config-router)# nsf
Verifying EIGRP NSF

To verify EIGRP NSF, you must check that the NSF function is configured on the SSO-enabled networking device. To verify EIGRP NSF, follow these steps:
Step 1
Verify that nsf appears in the EIGRP configuration of the SSO-enabled device by entering the show running-config command:
Router# show running-config . . . router eigrp 100 auto-summary nsf . . .
Step 2
Enter the show ip protocols command to verify that NSF is enabled on the device:
Router# show ip protocols *** IP Routing is NSF aware *** Routing Protocol is "eigrp 100" Outgoing update filter list for all interfaces is not set Incoming update filter list for all interfaces is not set Default networks flagged in outgoing updates Default networks accepted from incoming updates EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0 EIGRP maximum hopcount 100 EIGRP maximum metric variance 1 Redistributing: eigrp 100 EIGRP NSF-aware route hold timer is 240s EIGRP NSF enabled NSF signal timer is 20s NSF converge timer is 120s Automatic network summarization is in effect Maximum path: 4 Routing for Networks: Routing Information Sources: Gateway Distance Last Update Distance: internal 90 external 170
7-19
Chapter 7 Copying Files to the Redundant Supervisor Engine
Synchronizing the Supervisor Engine Configurations

During normal operation, the startup-config and config-registers configurations are synchronized by default between the two supervisor engines. In a switchover, the new active supervisor engine uses the current configuration.
Copying Files to the Redundant Supervisor Engine

Enter this command to copy a file to the disk0: device on a redundant supervisor engine:
Router# copy source_device:source_filename slavedisk0:target_filename
Enter this command to copy a file to the bootflash: device on a redundant supervisor engine:
Router# copy source_device:source_filename slavesup-bootflash:target_filename
Enter this command to copy a file to the bootflash: device on a redundant MSFC:
Router# copy source_device:source_filename slavebootflash:target_filename
Tip
7-20
OL-3999-08
C H A P T E R
Configuring RPR and RPR+ Supervisor Engine Redundancy

This chapter describes how to configure supervisor engine redundancy using route processor redundancy (RPR) and RPR+.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html All releases support RPR and RPR+. With Release 12.2(18)SXE and later releases, RPR and RPR+ support IPv6 multicast traffic. Release 12.2(18)SXD and later releases support nonstop forwarding (NSF) with stateful switchover (SSO) on all supervisor engines (see Chapter 7, Configuring NSF with SSO Supervisor Engine Redundancy).

Understanding RPR and RPR+, page 8-2 Supervisor Engine Redundancy Guidelines and Restrictions, page 8-4 Configuring Supervisor Engine Redundancy, page 8-6 Performing a Fast Software Upgrade, page 8-8 Copying Files to an MSFC, page 8-9
Tip
8-1
Chapter 8 Understanding RPR and RPR+
Understanding RPR and RPR+

These sections describe supervisor engine redundancy using RPR and RPR+:

Supervisor Engine Redundancy Overview, page 8-2 RPR Operation, page 8-2 RPR+ Operation, page 8-3 Supervisor Engine Configuration Synchronization, page 8-3
Supervisor Engine Redundancy Overview

Catalyst 6500 series switches support fault resistance by allowing a redundant supervisor engine to take over if the primary supervisor engine fails. Catalyst 6500 series switches support these redundancy modes:

RPRSupports a switchover time of 2 or more minutes. Route processor redundancy plus (RPR+)Supports a switchover time of 30 or more seconds. A hardware failure on the active supervisor engine Clock synchronization failure between supervisor engines A manual switchover
The following events cause a switchover:

RPR Operation
RPR supports the following features:

Auto-startup and bootvar synchronization between active and redundant supervisor engines Hardware signals that detect and decide the active or redundant status of supervisor engines Clock synchronization every 60 seconds from the active to the redundant supervisor engine A redundant supervisor engine that is booted but not all subsystems are up: if the active supervisor engine fails, the redundant supervisor engine become fully operational An operational supervisor engine present in place of the failed unit becomes the redundant supervisor engine Support for fast software upgrade (FSU) (See the Performing a Fast Software Upgrade section on page 8-8.)
When the switch is powered on, RPR runs between the two supervisor engines. The supervisor engine that boots first becomes the RPR active supervisor engine. The Multilayer Switch Feature Card and Policy Feature Card become fully operational. The MSFC and PFC on the redundant supervisor engine come out of reset but are not operational. In a switchover, the redundant supervisor engine become fully operational and the following occurs:

All switching modules power up again Remaining subsystems on the MSFC (including Layer 2 and Layer 3 protocols) are brought up Access control lists (ACLs) are reprogrammed into supervisor engine hardware
8-2
OL-3999-08
Chapter 8
Configuring RPR and RPR+ Supervisor Engine Redundancy Understanding RPR and RPR+
Note
In a switchover, there is a disruption of traffic because some address states are lost and then restored after they are dynamically redetermined.
RPR+ Operation
When RPR+ mode is used, the redundant supervisor engine is fully initialized and configured, which shortens the switchover time. The active supervisor engine checks the image version of the redundant supervisor engine when the redundant supervisor engine comes online. If the image on the redundant supervisor engine does not match the image on the active supervisor engine, RPR redundancy mode is used. With RPR+, the redundant supervisor engine is fully initialized and configured, which shortens the switchover time if the active supervisor engine fails or if a manual switchover is performed. When the switch is powered on, RPR+ runs between the two supervisor engines. The supervisor engine that boots first becomes the active supervisor engine. The Multilayer Switch Feature Card and Policy Feature Card become fully operational. The MSFC and PFC on the redundant supervisor engine come out of reset but are not operational. RPR+ enhances RPR by providing the following additional benefits:
Reduced switchover time Depending on the configuration, the switchover time is 30 or more seconds. Installed modules are not reloaded Because both the startup configuration and the running configuration are continually synchronized from the active to the redundant supervisor engine, installed modules are not reloaded during a switchover.
Online insertion and removal (OIR) of the redundant supervisor engine RPR+ allows OIR of the redundant supervisor engine for maintenance. When the redundant supervisor engine is inserted, the active supervisor engine detects its presence and begins to transition the redundant supervisor engine to fully initialized state.
Synchronization of OIR events Manual user-initiated switchover using the redundancy force-switchover command
Supervisor Engine Configuration Synchronization

These sections describe supervisor engine configuration synchronization:

RPR Supervisor Engine Configuration Synchronization, page 8-4 RPR+ Supervisor Engine Configuration Synchronization, page 8-4
Note
Configuration changes made through SNMP are not synchronized to the redundant supervisor engine. After you configure the switch through SNMP, copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine and with RPR+, reload the redundant supervisor engine and MSFC.
8-3
Chapter 8 Supervisor Engine Redundancy Guidelines and Restrictions
RPR Supervisor Engine Configuration Synchronization

During RPR mode operation, the startup-config files and the config-register configurations are synchronized by default between the two supervisor engines. In a switchover, the new active supervisor engine uses the current configuration.
RPR+ Supervisor Engine Configuration Synchronization

With RPR+ mode, the following operations trigger configuration synchronization:
When a redundant supervisor engine first comes online, the startup-config file is copied from the active supervisor engine to the redundant supervisor engine. This synchronization overwrites any existing startup configuration file on the redundant supervisor engine. When configuration changes occur during normal operation, redundancy performs an incremental synchronization from the active supervisor engine to the redundant supervisor engine. Redundancy synchronizes user-entered CLI commands incrementally line-by-line from the active supervisor engine to the redundant supervisor engine.
Even though the redundant supervisor engine is fully initialized, it only interacts with the active supervisor engine to receive incremental changes to the configuration files as they occur. You cannot enter CLI commands on the redundant supervisor engine.
Supervisor Engine Redundancy Guidelines and Restrictions

These sections describe supervisor engine redundancy guidelines and restrictions:

Redundancy Guidelines and Restrictions, page 8-4 RPR+ Guidelines and Restrictions, page 8-5 Hardware Configuration Guidelines and Restrictions, page 8-5 Configuration Mode Restrictions, page 8-6
Redundancy Guidelines and Restrictions

These guidelines and restrictions apply to RPR and RPR+ redundancy modes:

The two Gigabit Ethernet interfaces on the redundant supervisor engine are always active. Supervisor engine redundancy does not provide supervisor engine mirroring or supervisor engine load balancing. Only one supervisor engine is active. Configuration changes made through SNMP are not synchronized to the redundant supervisor engine. After you configure the switch through SNMP, copy the running-config file to the startup-config file on the active supervisor engine to trigger synchronization of the startup-config file on the redundant supervisor engine and with RPR+, reload the redundant supervisor engine and MSFC. Supervisor engine switchover takes place after the failed supervisor engine completes a core dump. A core dump can take up to 15 minutes. To get faster switchover time, disable core dump on the supervisor engines.
8-4
OL-3999-08
Chapter 8
Configuring RPR and RPR+ Supervisor Engine Redundancy Supervisor Engine Redundancy Guidelines and Restrictions
RPR+ Guidelines and Restrictions

These guidelines and restrictions apply to RPR+:

Network services are disrupted until the redundant supervisor engine takes over and the switch recovers. The Forwarding Information Base (FIB) tables are cleared on a switchover. As a result, routed traffic is interrupted until route tables reconverge. Static IP routes are maintained across a switchover because they are configured from entries in the configuration file. Information about dynamic states maintained on the active supervisor engine is not synchronized to the redundant supervisor engine and is lost on switchover. These are examples of dynamic state information that is lost at switchover:
Frame Relay Switched Virtual Circuits (SVCs)
Note
Frame Relay-switched DLCI information is maintained across a switchover because Frame Relay-switched DLCI configuration is in the configuration file.
All terminated PPP sessions All ATM SVC information All terminated TCP and other connection-oriented Layer 3 and Layer 4 sessions BGP sessions All Automatic Protection System (APS) state information
Both supervisor engines must run the same version of Cisco IOS software. If the supervisor engines are not running the same version of Cisco IOS software, the redundant supervisor engine comes online in RPR mode. Supervisor engine redundancy does not support nondefault VLAN data file names or locations. Do not enter the vtp file file_name command on a switch that has a redundant supervisor engine. Before installing a redundant supervisor engine, enter the no vtp file command to return to the default configuration. Supervisor engine redundancy does not support configuration entered in VLAN database mode. Use global configuration mode with RPR+ redundancy (see Chapter 14, Configuring VLANs).
Hardware Configuration Guidelines and Restrictions

For redundant operation, the following guidelines and restrictions must be met:
Cisco IOS running on the supervisor engine and the MSFC supports redundant configurations where the supervisor engines and MSFC routers are identical. If they are not identical, one will boot first and become active and hold the other supervisor engine and MSFC in a reset condition. Each supervisor engine must have the resources to run the switch on its own, which means all supervisor engine resources are duplicated, including all flash devices. Make separate console connections to each supervisor engine. Do not connect a Y cable to the console ports.
8-5
Chapter 8 Configuring Supervisor Engine Redundancy
Both supervisor engines must have the same system image (see the Copying Files to an MSFC section on page 8-9).
Note
If a newly installed redundant supervisor engine has the Catalyst operating system installed, remove the active supervisor engine and boot the switch with only the redundant supervisor engine installed. Follow the procedures in the current release notes to convert the redundant supervisor engine from the Catalyst operating system.
The configuration register in the startup-config must be set to autoboot (see the Modifying the Boot Field section on page 3-23).
Note
There is no support for booting from the network. With releases earlier than Release 12.2(17b)SXA, if these requirements are met, the switch functions in RPR+ mode by default.
Configuration Mode Restrictions

The following configuration restrictions apply during the startup synchronization process:
You cannot perform configuration changes during the startup (bulk) synchronization. If you attempt to make configuration changes during this process, the following message is generated:
Config mode locked out till standby initializes
If configuration changes occur at the same time as a supervisor engine switchover, these configuration changes are lost.
Configuring Supervisor Engine Redundancy

These sections describe how to configure supervisor engine redundancy:

Configuring Redundancy, page 8-6 Synchronizing the Supervisor Engine Configurations, page 8-7 Displaying the Redundancy States, page 8-7
Configuring Redundancy
To configure redundancy, perform this task: Command
Step 1 Step 2
Router(config)# redundancy Router(config-red)# mode { rpr | rpr-plus}
Purpose Enters redundancy configuration mode. Configures RPR or RPR+. When this command is entered, the redundant supervisor engine is reloaded and begins to work in RPR or RPR+ mode.
8-6
OL-3999-08
Chapter 8
Configuring RPR and RPR+ Supervisor Engine Redundancy Configuring Supervisor Engine Redundancy
Command
Step 3 Step 4
Router# show running-config Router# show redundancy states
Purpose Verifies that RPR or RPR+ is enabled. Displays the operating redundancy mode.
This example shows how to configure the system for RPR+ and display the redundancy state:
Router> enable Router# configure terminal Enter configuration commands, one per line. Router(config)# redundancy Router(config-red)# mode rpr-plus Router(config-red)# end Router# show redundancy states my state = 13 -ACTIVE peer state = 1 -DISABLED Mode = Simplex Unit = Primary Unit ID = 1 Redundancy Mode Redundancy Mode Split Mode Manual Swact Communications
End with CNTL/Z.
(Operational) = Route Processor Redundancy Plus (Configured) = Route Processor Redundancy Plus = Disabled = Disabled Reason: Simplex mode = Down Reason: Simplex mode
= = = = =
Synchronizing the Supervisor Engine Configurations

During normal operation, the startup-config and config-registers configuration are synchronized by default between the two supervisor engines. In a switchover, the new active supervisor engine uses the current configuration.
Note
Do not change the default auto-sync configuration.
Displaying the Redundancy States

To display the redundancy states, perform this task: Command
Router# show redundancy states
Purpose Displays the redundancy states.
This example shows how to display the redundancy states:

Router# show redundancy states
8-7
Chapter 8 Performing a Fast Software Upgrade
my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Primary Unit ID = 1 Redundancy Mode Redundancy Mode Split Mode Manual Swact Communications (Operational) = Route Processor Redundancy Plus (Configured) = Route Processor Redundancy Plus = Disabled = Enabled = Up
= = = = =
Performing a Fast Software Upgrade

The fast software upgrade (FSU) procedure supported by RPR allows you to upgrade the Cisco IOS image on the supervisor engines without reloading the system.
Note
If you are performing a first-time upgrade to RPR from EHSA, you must reload both supervisor engines. FSU from EHSA is not supported. To perform an FSU, perform this task:
Command
Step 1
Router# copy source_device:source_filename {disk0 | disk1}:target_filename
Purpose Copies the new Cisco IOS image to the disk0: device or the disk1: device on the active supervisor engine. Copies the new Cisco IOS image to the bootflash: device on the active supervisor engine. Copies the new Cisco IOS image to the disk0: device or the disk1: device on the redundant supervisor engine. Copies the new Cisco IOS image to the bootflash: device on the redundant supervisor engine. Configures the supervisor engines to boot the new image.
Or:
Router# copy source_device:source_filename sup-bootflash:target_filename
Or:
Router# copy source_device:source_filename {slavedisk0 | slavedisk1}:target_filename
Or:
Step 2
Router# config terminal Router(config)# config-register 0x2102 Router(config)# boot system flash device:file_name Router# copy running-config start-config
Step 3
Saves the configuration.
8-8
OL-3999-08
Chapter 8
Configuring RPR and RPR+ Supervisor Engine Redundancy Copying Files to an MSFC
Command
Step 1
Router# copy source_device:source_filename {disk0 | disk1}:target_filename
Purpose Copies the new Cisco IOS image to the disk0: device or the disk1: device on the active supervisor engine. Copies the new Cisco IOS image to the bootflash: device on the active supervisor engine. Copies the new Cisco IOS image to the disk0: device or the disk1: device on the redundant supervisor engine. Copies the new Cisco IOS image to the bootflash: device on the redundant supervisor engine. Reloads the redundant supervisor engine and brings it back online (running the new version of the Cisco IOS software).
Note
Or:
Router# copy source_device:source_filename sup-bootflash:target_filename
Or:
Router# copy source_device:source_filename {slavedisk0 | slavedisk1}:target_filename
Or:
Step 4
Router# hw-module {module num} reset
Before reloading the redundant supervisor engine, make sure you wait long enough to ensure that all configuration synchronization changes have completed.
Step 5
Router# redundancy force-switchover
Conducts a manual switchover to the redundant supervisor engine. The redundant supervisor engine becomes the new active supervisor engine running the new Cisco IOS image. The modules are reloaded and the module software is downloaded from the new active supervisor engine. The old active supervisor engine reboots with the new image and becomes the redundant supervisor engine.
Note
To perform an EHSA to RPR FSU, use the reload command in Step 5.
This example shows how to perform an FSU:

Router# config terminal Router(config)# config-register 0x2102 Router(config)# boot system flash disk0:image_name Router# copy running-config start-config Router# hw-module reset Router# redundancy force-switchover Router#
Copying Files to an MSFC

Use the following command to copy a file to the bootflash: device on an active MSFC:
Router# copy source_device:source_filename bootflash:target_filename
Use the following command to copy a file to the bootflash: device on a redundant MSFC:
Router# copy source_device:source_filename slavebootflash:target_filename
8-9
Chapter 8 Copying Files to an MSFC
Tip
8-10
OL-3999-08
C H A P T E R
This chapter describes how to configure interfaces on the Catalyst 6500 series switches. This chapter consists of these sections:

Understanding Interface Configuration, page 9-2 Using the Interface Command, page 9-2 Configuring a Range of Interfaces, page 9-4 Defining and Using Interface-Range Macros, page 9-6 Configuring Optional Interface Features, page 9-6 Understanding Online Insertion and Removal, page 9-16 Monitoring and Maintaining Interfaces, page 9-17 Checking the Cable Status Using the TDR, page 9-19
Note
Tip
9-1
Chapter 9 Understanding Interface Configuration
Understanding Interface Configuration

Many features in the software are enabled on a per-interface basis. When you enter the interface command, you must specify the following information:
Interface type:
Ethernet (use the ethernet keyword) Fast Ethernet (use the fastethernet keyword) Gigabit Ethernet (use the gigabitethernet keyword) 10-Gigabit Ethernet (use the tengigabitethernet keyword)
Note
For WAN interfaces, refer to the configuration note for the WAN module.
Slot numberThe slot in which the module is installed. On the Catalyst 6500 series switch, slots are numbered starting with 1, from top to bottom. Port numberThe physical port number on the module. On the Catalyst 6500 series switch, the port numbers always begin with 1. When facing the rear of the switch, ports are numbered from the left to the right.
You can identify ports from the physical location. You also can use show commands to display information about a specific port, or all the ports.
Using the Interface Command

Note
You use the commands described in this section to configure both physical ports and logical interfaces. These procedures apply to all interface configuration processes. Begin the interface configuration process in global configuration mode. To use the interface command, follow these steps:
Step 1
Enter the configure terminal command at the privileged EXEC prompt to enter global configuration mode:
Router# configure terminal Enter configuration commands, one per line. Router(config)# End with CNTL/Z.
Step 2
In the global configuration mode, enter the interfaces command. Identify the interface type and the number of the connector or interface card. The following example shows how to select Fast Ethernet, slot 5, interface 1:
Router(config)# interfaces fastethernet 5/1 Router(config-if)#
Step 3
Enter the show interfaces EXEC command to see a list of all interfaces that are installed. A report is provided for each interface that the device supports, as shown in this display:
Router# show interfaces fastethernet 5/48 FastEthernet5/48 is up, line protocol is up Hardware is C6k 100Mb 802.3, address is 0050.f0ac.3083 (bia 0050.f0ac.3083) Internet address is 172.20.52.18/27
9-2
OL-3999-08
Chapter 9
Configuring Interfaces Using the Interface Command
MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Half-duplex, 100Mb/s ARP type: ARPA, ARP Timeout 04:00:00 Last clearing of "show interface" counters never Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 1000 bits/sec, 1 packets/sec 5 minute output rate 1000 bits/sec, 1 packets/sec 4834677 packets input, 329545368 bytes, 0 no buffer Received 4796465 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 51926 packets output, 15070051 bytes, 0 underruns 0 output errors, 2 collisions, 2 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Router#
Step 4
Enter the show hardware EXEC command to see a list of the system software and hardware:
Router# show hardware Cisco Internetwork Operating System Software IOS (tm) c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(5c)EX, EARLY DEPLOY) Synced to mainline version: 12.1(5c) TAC:Home:Software:Ios General:CiscoIOSRoadmap:12.1 Copyright (c) 1986-2001 by cisco Systems, Inc. Compiled Wed 28-Mar-01 17:52 by hqluong Image text-base: 0x30008980, data-base: 0x315D0000 ROM: System Bootstrap, Version 12.1(3r)E2, RELEASE SOFTWARE (fc1) BOOTFLASH: c6sup2_rp Software (c6sup2_rp-JSV-M), Version 12.1(5c)EX, EARLY DEPL) Router uptime is 2 hours, 55 minutes System returned to ROM by power-on (SP by power-on) Running default software cisco Catalyst 6000 (R7000) processor with 114688K/16384K bytes of memory. Processor board ID SAD04430J9K R7000 CPU at 300Mhz, Implementation 39, Rev 2.1, 256KB L2, 1024KB L3 Cache Last reset from power-on Bridging software. X.25 software, Version 3.0.0. SuperLAT software (copyright 1990 by Meridian Technology Corp). TN3270 Emulation software. 1 Virtual Ethernet/IEEE 802.3 interface(s) 48 FastEthernet/IEEE 802.3 interface(s) 2 Gigabit Ethernet/IEEE 802.3 interface(s) 381K bytes of non-volatile configuration memory. 16384K bytes of Flash internal SIMM (Sector size 512K). Configuration register is 0x2 Router#
Step 5
To begin configuring Fast Ethernet port 5/5, enter the interface keyword, interface type, and slot number/port number at the privileged EXEC prompt, as shown in the following example:
Router# configure terminal Enter configuration commands, one per line. Router(config)# interface fastethernet 5/5 Router(config-if)# End with CNTL/Z.
9-3
Chapter 9 Configuring a Range of Interfaces
Note
You do not need to add a space between the interface type and interface number. For example, in the preceding line you can specify either fastethernet 5/5 or fastethernet5/5 .
Step 6
After each interface command, enter the interface configuration commands your particular interface requires. The commands you enter define the protocols and applications that will run on the interface. The commands are collected and applied to the interface command until you enter another interface command or press Ctrl-Z to get out of interface configuration mode and return to privileged EXEC mode.
Step 7
After you configure an interface, check its status by using the EXEC show commands listed in Monitoring and Maintaining Interfaces section on page 9-17.
Configuring a Range of Interfaces

The interface-range configuration mode allows you to configure multiple interfaces with the same configuration parameters. After you enter the interface-range configuration mode, all command parameters you enter are attributed to all interfaces within that range until you exit out of the interface-range configuration mode. To configure a range of interfaces with the same configuration, perform this task: Command
Router(config)# [no] interface range {{vlan vlan_ID - vlan_ID [, vlan vlan_ID - vlan_ID]} | {type1 slot/port - port [, type1 slot/port - port]} | {macro_name [, macro_name]}} 1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
Purpose Selects the range of interfaces to be configured.
When configuring a range of interfaces, note the following information:

For information about macros, see the Defining and Using Interface-Range Macros section on page 9-6. You can enter up to five comma-separated ranges. You are not required to enter spaces before or after the comma. With releases earlier than Release 12.2(18)SXE, you must add a space between the interface numbers and the dash when using the interface range command. For example, interface range fastethernet 1 - 5 is valid syntax; interface range fastethernet 1-5 is invalid. With Release 12.2(18)SXE and later releases, you do not need to add a space between the interface numbers and the dash when using the interface range command. With releases earlier than Release 12.2(18)SXD, the no interface range command does not support VLAN interfaces. With Release 12.2(18)SXD and later releases, the no interface range command supports VLAN interfaces.
9-4
OL-3999-08
Chapter 9
Configuring Interfaces Configuring a Range of Interfaces
With releases earlier than Release 12.2(18)SXD, for VLAN interfaces, the interface range command supports only those VLAN interfaces for which Layer 2 VLANs have been created with the interface vlan command (the show running-configuration command displays the configured VLAN interfaces). The interface range command does not support VLAN interfaces that are not displayed by the show running-configuration command. With Release 12.2(18)SXD and later releases, the interface range command supports VLAN interfaces for which Layer 2 VLANs have not been created with the interface vlan command.
Note
The link state messages (LINK-3-UPDOWN and LINEPROTO-5-UPDOWN) are disabled by default. Enter the logging event link status command on each interface where you want the messages enabled. This example shows how to reenable all Fast Ethernet ports 5/1 to 5/5:
Router(config)# interface range fastethernet 5/1 - 5 Router(config-if)# no shutdown Router(config-if)# *Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/1, changed state to up *Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/2, changed state to up *Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/3, changed state to up *Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/4, changed state to up *Oct 6 08:24:35: %LINK-3-UPDOWN: Interface FastEthernet5/5, changed state to up *Oct 6 08:24:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/ 5, changed state to up *Oct 6 08:24:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/ 3, changed state to up *Oct 6 08:24:36: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/ 4, changed state to up Router(config-if)#
This example shows how to use a comma to add different interface type strings to the range to reenable all Fast Ethernet ports in the range 5/1 to 5/5 and both Gigabit Ethernet ports (1/1 and 1/2):
Router(config-if)# interface range fastethernet 5/1 - 5, gigabitethernet 1/1 - 2 Router(config-if)# no shutdown Router(config-if)# *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/1, changed state to up *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/2, changed state to up *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/3, changed state to up *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/4, changed state to up *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface FastEthernet5/5, changed state to up *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface GigabitEthernet1/1, changed state to up *Oct 6 08:29:28: %LINK-3-UPDOWN: Interface GigabitEthernet1/2, changed state to up *Oct 6 08:29:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/ 5, changed state to up *Oct 6 08:29:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/ 3, changed state to up *Oct 6 08:29:29: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet5/ 4, changed state to up Router(config-if)#
If you enter multiple configuration commands while you are in interface-range configuration mode, each command is executed as it is entered (they are not batched together and executed after you exit interface-range configuration mode). If you exit interface-range configuration mode while the commands are being executed, some commands may not be executed on all interfaces in the range. Wait until the command prompt reappears before exiting interface-range configuration mode.
9-5
Chapter 9 Defining and Using Interface-Range Macros
Defining and Using Interface-Range Macros

You can define an interface-range macro to automatically select a range of interfaces for configuration. Before you can use the macro keyword in the interface range macro command string, you must define the macro. To define an interface-range macro, perform this task: Command
Router(config)# define interface-range macro_name {vlan vlan_ID - vlan_ID} | {type1 slot/port - port} [, {type1 slot/port - port}] Router(config)# no define interface-range macro_name 1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
Purpose Defines the interface-range macro and save it in NVRAM.
Deletes a macro.
This example shows how to define an interface-range macro named enet_list to select Fast Ethernet ports 5/1 through 5/4:
Router(config)# define interface-range enet_list fastethernet 5/1 - 4
To show the defined interface-range macro configuration, perform this task: Command
Router# show running-config
Purpose Shows the defined interface-range macro configuration.
This example shows how to display the defined interface-range macro named enet_list:
Router# show running-config | include define define interface-range enet_list FastEthernet5/1 - 4 Router#
To use an interface-range macro in the interface range command, perform this task: Command
Router(config)# interface range macro macro_name
Purpose Selects the interface range to be configured using the values saved in a named interface-range macro.
This example shows how to change to the interface-range configuration mode using the interface-range macro enet_list:
Router(config)# interface range macro enet_list Router(config-if)#
Configuring Optional Interface Features

These sections describe optional interface features:

Configuring Ethernet Interface Speed and Duplex Mode, page 9-7 Configuring Jumbo Frame Support, page 9-10
9-6
OL-3999-08
Chapter 9
Configuring Interfaces Configuring Optional Interface Features
Configuring IEEE 802.3x Flow Control, page 9-13 Configuring the Port Debounce Timer, page 9-15 Adding a Description for an Interface, page 9-16
Configuring Ethernet Interface Speed and Duplex Mode

These sections describe how to configure Ethernet port speed and duplex mode:

Speed and Duplex Mode Configuration Guidelines, page 9-7 Configuring the Ethernet Interface Speed, page 9-7 Setting the Interface Duplex Mode, page 9-8 Configuring Link Negotiation on Gigabit Ethernet Ports, page 9-8 Displaying the Speed and Duplex Mode Configuration, page 9-9
Speed and Duplex Mode Configuration Guidelines

You usually configure Ethernet port speed and duplex mode parameters to auto and allow the Catalyst 6500 series switch to negotiate the speed and duplex mode between ports. If you decide to configure the port speed and duplex modes manually, consider the following information:

If you set the Ethernet port speed to auto, the switch automatically sets the duplex mode to auto. If you enter the no speed command, the switch automatically configures both speed and duplex to auto. If you configure an Ethernet port speed to a value other than auto (for example, 10, 100, or 1000 Mbps), configure the connecting port to match. Do not configure the connecting port to negotiate the speed. If you manually configure the Ethernet port speed to either 10 Mbps or 100 Mbps, the switch prompts you to also configure the duplex mode on the port.
Note
Catalyst 6500 series switches cannot automatically negotiate Ethernet port speed and duplex mode if the connecting port is configured to a value other than auto.
Caution
Changing the Ethernet port speed and duplex mode configuration might shut down and reenable the interface during the reconfiguration.
Configuring the Ethernet Interface Speed

Note
If you configure the Ethernet port speed to auto on a 10/100-Mbps or 10/100/1000-Mbps Ethernet port, both speed and duplex are autonegotiated.
9-7
Chapter 9 Configuring Optional Interface Features
To configure the port speed for a 10/100 or a 10/100/1000-Mbps Ethernet port, perform this task: Command
Step 1 Step 2
Router(config)# interface fastethernet slot/port Router(config-if)# speed {10 | 100 | 1000 | {auto [10 100 [1000]]}} Router(config-if)# no speed
Purpose Selects the Ethernet port to be configured. Configures the speed of the Ethernet interface. Reverts to the default configuration (speed auto).
Release 12.2(17a)SX and later releases support the 10 100 1000 keywords after the auto keyword. When configuring the port speed for a 10/100/1000-Mbps Ethernet port with Release 12.2(17a)SX and later releases, note the following:

Enter the auto 10 100 keywords to restrict the negotiated speed to 10-Mbps or 100-Mbps. The auto 10 100 1000 keywords have the same effect as the auto keyword by itself.
This example shows how to configure the speed to 100 Mbps on the Fast Ethernet port 5/4:
Router(config)# interface fastethernet 5/4 Router(config-if)# speed 100
Setting the Interface Duplex Mode

Note
10-Gigabit Ethernet and Gigabit Ethernet are full duplex only. You cannot change the duplex mode on 10-Gigabit Ethernet or Gigabit Ethernet ports or on a 10/100/1000-Mps port configured for Gigabit Ethernet. If you set the port speed to auto on a 10/100-Mbps or a 10/100/1000-Mbps Ethernet port, both speed and duplex are autonegotiated. You cannot change the duplex mode of autonegotiation ports.
To set the duplex mode of an Ethernet or Fast Ethernet port, perform this task: Command
Step 1 Step 2
Router(config)# interface fastethernet slot/port Router(config-if)# duplex [auto | full | half] Router(config-if)# no duplex
Purpose Selects the Ethernet port to be configured. Sets the duplex mode of the Ethernet port. Reverts to the default configuration (duplex auto).
This example shows how to set the duplex mode to full on Fast Ethernet port 5/4:
Router(config)# interface fastethernet 5/4 Router(config-if)# duplex full
Configuring Link Negotiation on Gigabit Ethernet Ports

Note
Link negotiation does not negotiate port speed. On Gigabit Ethernet ports, link negotiation exchanges flow-control parameters, remote fault information, and duplex information. Link negotiation is enabled by default.
9-8
OL-3999-08
Chapter 9
The ports on both ends of a link must have the same setting. The link will not come up if the ports at each end of the link are set inconsistently (link negotiation enabled on one port and disabled on the other port). Table 9-1 shows the four possible link negotiation configurations and the resulting link status for each configuration.
Table 9-1 Link Negotiation Configuration and Possible Link Status
Link Negotiation State Local Port Off On Off On Remote Port Off On On Off
Link Status Local Port Up Up Up Down Remote Port Up Up Down Up
To configure link negotiation on a port, perform this task: Command

Step 1 Step 2
Router(config)# interface gigabitethernet slot/port Router(config-if)# speed nonegotiate Router(config-if)# no speed nonegotiate
Purpose Selects the port to be configured. Disables link negotiation. Reverts to the default configuration (link negotiation enabled).
This example shows how to enable link negotiation on Gigabit Ethernet port 5/4:
Router(config)# interface gigabitethernet 5/4 Router(config-if)# no speed nonegotiate
Displaying the Speed and Duplex Mode Configuration

To display the speed and duplex mode configuration for a port, perform this task: Command
Router# show interfaces type
1
Purpose
slot/port
Displays the speed and duplex mode configuration.
1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
This example shows how to display the speed and duplex mode of Fast Ethernet port 5/4:
Router# show interfaces fastethernet 5/4 FastEthernet5/4 is up, line protocol is up Hardware is Cat6K 100Mb Ethernet, address is 0050.f0ac.3058 (bia 0050.f0ac.3058) MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set Keepalive set (10 sec) Full-duplex, 100Mb/s ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:33, output never, output hang never
9-9
Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 1238 packets input, 273598 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 1380 packets output, 514382 bytes, 0 underruns 0 output errors, 0 collisions, 2 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Router#
Configuring Jumbo Frame Support

These sections describe jumbo frame support:

Understanding Jumbo Frame Support, page 9-10 Configuring MTU Sizes, page 9-12
Caution
The following switching modules support a maximum ingress frame size of 8,092 bytes:
WS-X6516-GE-TX when operating at 100 Mbps WS-X6148-RJ-45, WS-X6148-RJ-45V and WS-X6148-RJ21, WS-X6148-RJ21V WS-X6248-RJ-45 and WS-X6248-TEL WS-X6248A-RJ-45 and WS-X6248A-TEL WS-X6348-RJ-45, WS-X6348-RJ45V and WS-X6348-RJ-21, WX-X6348-RJ21V
When jumbo frame support is configured, these modules drop ingress frames larger than 8092 bytes.
Note
The WS-X6548-GE-TX, WS-X6548V-GE-TX, WS-X6148-GE-TX, and WS-X6148V-GE-TX do not support jumbo frames.
Understanding Jumbo Frame Support

These sections describe jumbo frame support:

Jumbo Frame Support Overview, page 9-10 Ethernet Ports, page 9-11 VLAN Interfaces, page 9-12
Jumbo Frame Support Overview

A jumbo frame is a frame larger than the default Ethernet size. You enable jumbo frame support by configuring a larger-than-default maximum transmission unit (MTU) size on a port or VLAN interface and configuring the global LAN port MTU size.
9-10
OL-3999-08
Chapter 9
Note
Jumbo frame support fragments routed traffic in software on the MSFC. Jumbo frame support does not fragment bridged traffic.
Bridged and Routed Traffic Size Check at Ingress 10, 10/100, and 100 Mbps Ethernet and 10-Gigabit Ethernet Ports
Jumbo frame support compares ingress traffic size with the global LAN port MTU size at ingress 10, 10/100, and 100 Mbps Ethernet and 10-Gigabit Ethernet LAN ports that have a nondefault MTU size configured. The port drops traffic that is oversized. You can configure the global LAN port MTU size (see the Configuring the Global Egress LAN Port MTU Size section on page 9-13).
Bridged and Routed Traffic Size Check at Ingress Gigabit Ethernet Ports
Gigabit Ethernet LAN ports configured with a nondefault MTU size accept frames containing packets of any size larger than 64 bytes. With a nondefault MTU size configured, Gigabit Ethernet LAN ports do not check for oversize ingress frames.
Routed Traffic Size Check on the PFC
For traffic that needs to be routed, Jumbo frame support on the PFC compares traffic sizes to the configured MTU sizes and provides Layer 3 switching for jumbo traffic between interfaces configured with MTU sizes large enough to accommodate the traffic. Between interfaces that are not configured with large enough MTU sizes, if the do not fragment bit is not set, the PFC sends the traffic to the MSFC to be fragmented and routed in software. If the do not fragment bit is set, the PFC drops the traffic.
Bridged and Routed Traffic Size Check at Egress 10, 10/100, and 100 Mbps Ethernet Ports
10, 10/100, and 100 Mbps Ethernet LAN ports configured with a nondefault MTU size transmit frames containing packets of any size larger than 64 bytes. With a nondefault MTU size configured, 10, 10/100, and 100 Mbps Ethernet LAN ports do not check for oversize egress frames.
Bridged and Routed Traffic Size Check at Egress Gigabit Ethernet and 10-Gigabit Ethernet Ports
Jumbo frame support compares egress traffic size with the global egress LAN port MTU size at egress Gigabit Ethernet and 10-Gigabit Ethernet LAN ports that have a nondefault MTU size configured. The port drops traffic that is oversized. You can configure the global LAN port MTU size (see the Configuring the Global Egress LAN Port MTU Size section on page 9-13).
Ethernet Ports
These sections describe configuring nondefault MTU sizes on Ethernet ports:

Ethernet Port Overview, page 9-11 Layer 3 Ethernet Ports, page 9-12 Layer 2 Ethernet Ports, page 9-12
Ethernet Port Overview
Configuring a nondefault MTU size on a 10, 10/100, or 100 Mbps Ethernet port limits ingress packets to the global LAN port MTU size and permits egress traffic of any size larger than 64 bytes. Configuring a nondefault MTU size on a Gigabit Ethernet port permits ingress packets of any size larger than 64 bytes and limits egress traffic to the global LAN port MTU size.
9-11
Configuring a nondefault MTU size on a 10-Gigabit Ethernet port limits ingress and egress packets to the global LAN port MTU size. Configuring a nondefault MTU size on an Ethernet port limits routed traffic to the configured MTU size. You can configure the MTU size on any Ethernet port.
Layer 3 Ethernet Ports
On a Layer 3 port, you can configure an MTU size on each Layer 3 Ethernet port that is different than the global LAN port MTU size.
Note
Traffic through a Layer 3 Ethernet LAN port that is configured with a nondefault MTU size is also subject to the global LAN port MTU size (see the Configuring the Global Egress LAN Port MTU Size section on page 9-13).
Layer 2 Ethernet Ports
On a Layer 2 port, you can only configure an MTU size that matches the global LAN port MTU size (see the Configuring the Global Egress LAN Port MTU Size section on page 9-13).
VLAN Interfaces
You can configure a different MTU size on each Layer 3 VLAN interface. Configuring a nondefault MTU size on a VLAN interface limits traffic to the nondefault MTU size. You can configure the MTU size on VLAN interfaces to support jumbo frames.
Configuring MTU Sizes

These sections describe how to configure MTU sizes:

Configuring MTU Sizes, page 9-12 Configuring the Global Egress LAN Port MTU Size, page 9-13
Configuring the MTU Size

To configure the MTU size, perform this task: Command
Step 1
Router(config)# interface {{vlan vlan_ID} | {{type1 slot/port} | {port-channel port_channel_number} slot/port}} Router(config-if)# mtu mtu_size Router(config-if)# no mtu
Purpose Selects the interface to configure.
Step 2
Configures the MTU size. Reverts to the default MTU size (1500 bytes). Exits configuration mode. Displays the running configuration.
Step 3 Step 4
Router(config-if)# end Router# show running-config interface [{gigabitethernet | tengigabitethernet} slot/port] 1.
type = ethernet , fastethernet, gigabitethernet , tengigabitethernet , or ge-wan
When configuring the MTU size, note the following information:
9-12
OL-3999-08
Chapter 9
For VLAN interfaces and Layer 3 Ethernet ports, supported MTU values are from 64 to 9216 bytes. For Layer 2 Ethernet ports, you can configure only the global egress LAN port MTU size (see the Configuring the Global Egress LAN Port MTU Size section on page 9-13).
This example shows how to configure the MTU size on Gigabit Ethernet port 1/2:
Router# configure terminal Router(config)# interface gigabitethernet 1/2 Router(config-if)# mtu 9216 Router(config-if)# end
This example shows how to verify the configuration:

Router# show interface gigabitethernet 1/2 GigabitEthernet1/2 is administratively down, line protocol is down Hardware is C6k 1000Mb 802.3, address is 0030.9629.9f88 (bia 0030.9629.9f88) MTU 9216 bytes, BW 1000000 Kbit, DLY 10 usec, <...Output Truncated...> Router#
Configuring the Global Egress LAN Port MTU Size

To configure the global egress LAN port MTU size, perform this task: Command
Step 1
Router(config)# system jumbomtu mtu_size
Purpose Configures the global egress LAN port MTU size.

Note
Because it would change all the interface MTU sizes to the default (1500), rather than to any configured nondefault interface MTU size, do not use the system jumbomtu command to set the MTU size to 1500. (CSCtq52016)
Step 2
Router(config)# end
Exits configuration mode.
Configuring IEEE 802.3x Flow Control

Gigabit Ethernet and 10-Gigabit Ethernet ports on the Catalyst 6500 series switches use flow control to stop the transmission of frames to the port for a specified time; other Ethernet ports use flow control to respond to flow-control requests. If a Gigabit Ethernet or 10-Gigabit Ethernet port receive buffer becomes full, the port transmits an IEEE 802.3x pause frame that requests remote ports to delay sending frames for a specified time. All Ethernet ports (10 Gbps, 1 Gbps, 100 Mbps, and 10 Mbps) can receive and respond to IEEE 802.3x pause frames from other devices. To configure flow control on an Ethernet port, perform this task: Command
Step 1
Router(config)# interface type
1
Purpose
slot/port
Selects the port to configure.
9-13
Command
Step 2
Router(config-if)# flowcontrol {receive | send} {desired | off | on} Router(config-if)# no flowcontrol {receive | send}
Purpose Configures a port to send or respond to pause frames. Reverts to the default flow control settings. Displays the flow-control configuration for all ports.
Step 3
Router# show interfaces [type1 slot/port] flowcontrol 1.
type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
When configuring flow control, note the following information:
Because auto negotiation does not work on 10 Gigbit Ethernet fiber optic ports, they respond to pause frames by default. On 10 Gigbit Ethernet fiber optic ports, the flow-control operational mode is always the same as administrative mode. You cannot configure how WS-X6502-10GE 10-Gigabit Ethernet ports respond to pause frames. WS-X6502-10GE 10-Gigabit Ethernet ports are permanently configured to respond to pause frames. When configuring how a port responds to pause frames, note the following information:
For a Gigabit Ethernet port, when the configuration of a remote port is unknown, you can use
the receive desired keywords to configure the Gigabit Ethernet port to respond to received pause frames. (Supported only on Gigabit Ethernet ports.)
Use the receive on keywords to configure a port to respond to received pause frames. Use the receive off keywords to configure a port to ignore received pause frames.
When configuring transmission of pause frames on a port, note the following information:
For a Gigabit Ethernet port, when the configuration of the remote ports is unknown, you can use
the send desired keywords to configure the Gigabit Ethernet port to send pause frames. (Supported only on Gigabit Ethernet ports.)
Use the send on keywords to configure a port to send pause frames. Use the send off keywords to configure a port not to send pause frames.
This example shows how to turn on receive flow control and how to verify the flow-control configuration:
Router# configure terminal Router(config)# interface gigabitethernet 1/2 Router(config-if)# flowcontrol receive on Router(config-if)# end Router# show interfaces flowcontrol Interface Send Gi1/1 Desired Gi1/2 Desired Fa5/1 Not capable <output truncated> Receive OFF ON OFF
9-14
OL-3999-08
Chapter 9
Configuring the Port Debounce Timer

The port debounce timer delays notification of a link change, which can decrease traffic loss due to network reconfiguration. The delay in notification allows a quick port status change and recovery to occur without triggering any of the STP topology changes that are necessary when a port goes down. You can configure the port debounce timer separately on each LAN port.
Caution
Enabling the port debounce timer causes link down detections to be delayed, resulting in loss of traffic during the debouncing period. This situation might affect the convergence and reconvergence of some Layer 2 and Layer 3 protocols. To configure the debounce timer on a port, perform this task:
Command
Step 1 Step 2
1
Purpose
slot/port
Selects the port to configure. Configures the debounce timer. Reverts to the default setting. Verifies the configuration.
Router(config-if)# link debounce [time debounce_time] Router(config-if)# no link debounce
Step 3
Router# show interfaces debounce 1.
When configuring the debounce timer on a port, note the following information:

The time keyword is supported only on fiber Gigabit Ethernet ports. You can increase the port debounce timer value in increments of 100 milliseconds up to 5000 milliseconds on ports operating at 1000 Mpbs over copper media. Only releases earlier than Release 12.2(17a)SX support WS-X6502-10GE. Releases earlier than Release 12.2(18)SXD assume that 10 Gbps ports use fiber media. Release 12.2(18)SXD and later releases recognize 10 Gbps copper media. Releases earlier than Release 12.2(18)SXD do not detect media-only changes. Release 12.2(18)SXD and later releases detect media-only changes.
Table 9-2 lists the time delay that occurs before notification of a link change.
9-15
Chapter 9 Understanding Online Insertion and Removal
Table 9-2
Default Port Debounce Timer Delay Times
Port Type Ports operating at 10 Mpbs or 100 Mbps Ports operating at 1000 Mpbs or 10 Gbps over copper media Ports operating at 1000 Mpbs or 10 Gbps over fiber media WS-X6502-10GE 10-Gigabit ports
1. 10 milliseconds with Release 12.2(18)SXF13 and later releases.
Debounce Timer Disabled Debounce Timer Enabled 300 milliseconds 300 milliseconds 10 milliseconds
1
3100 milliseconds 3100 milliseconds 100 milliseconds 3100 milliseconds
1000 milliseconds
Note
On all 10-Gigabit Ethernet ports, the Debounce Timer Disabled is 10 milliseconds and the Debounce Timer Enabled is 1 second. This example shows how to enable the port debounce timer on Fast Ethernet port 5/12:
Router(config)# interface fastethernet 5/12 Router(config-if)# link debounce Router(config-if)# end
This example shows how to display the port debounce timer settings:
Router# show interfaces debounce | include enable Fa5/12 enable 3100
Adding a Description for an Interface

You can add a description about an interface to help you remember its function. The description appears in the output of the following commands: show configuration, show running-config, and show interfaces . To add a description for an interface, perform this task: Command
Router(config-if)# description string Router(config-if)# no description
Purpose Adds a description for an interface. Deletes a description from an interface.
This example shows how to add a description on Fast Ethernet port 5/5:
Router(config)# interface fastethernet 5/5 Router(config-if)# description Channel-group to "Marketing"
Understanding Online Insertion and Removal

The online insertion and removal (OIR) feature supported on the Catalyst 6500 series switches allows you to remove and replace modules while the system is online. You can shut down the modules before removal and restart it after insertion without causing other software or interfaces to shut down.
9-16
OL-3999-08
Chapter 9
Configuring Interfaces Monitoring and Maintaining Interfaces
Note
Do not remove or install more than one module at a time. After you remove or install a module, check the LEDs before continuing. For module LED descriptions, refer to the Catalyst 6500 Series Switch Installation Guide. When a module has been removed or installed, the Catalyst 6500 series switch stops processing traffic for the module and scans the system for a configuration change. Each interface type is verified against the system configuration, and then the system runs diagnostics on the new module. There is no disruption to normal operation during module insertion or removal. The switch can bring only an identical replacement module online. To support OIR of an identical module, the module configuration is not removed from the running-config file when you remove a module. If the replacement module is different from the removed module, you must configure it before the switch can bring it online. Layer 2 MAC addresses are stored in an EEPROM, which allows modules to be replaced online without requiring the system to update switching tables and data structures. Regardless of the types of modules installed, the Layer 2 MAC addresses do not change unless you replace the supervisor engine. If you do replace the supervisor engine, the Layer 2 MAC addresses of all ports change to those specified in the address allocator on the new supervisor engine.
Monitoring and Maintaining Interfaces

You can perform the tasks in the following sections to monitor and maintain interfaces:

Monitoring Interface Status, page 9-17 Clearing Counters on an Interface, page 9-18 Resetting an Interface, page 9-18 Shutting Down and Restarting an Interface, page 9-19
Monitoring Interface Status

The software contains commands that you can enter at the EXEC prompt to display information about the interface including the version of the software and the hardware and statistics about interfaces. The following table lists some of the interface monitoring commands. (You can display the complete list of show commands by using the show ? command at the EXEC prompt.) These commands are described in the Cisco IOS Interface Command Reference publication. To display information about the interface, perform these tasks: Command
Router# show ibc Router# show eobc Router# show interfaces [type slot/port]
Purpose Displays current internal status information. Displays current internal out-of-band information. Displays the status and configuration of all or a specific interface. Displays the currently running configuration.
Router# show running-config
9-17
Chapter 9 Monitoring and Maintaining Interfaces
Command
Router# show rif
Purpose Displays the current contents of the routing information field (RIF) cache. Displays the global (system-wide) and interface-specific status of any configured protocol. Displays the hardware configuration, software version, the names and sources of configuration files, and the boot images.
Router# show protocols [type slot/port]
Router# show version
This example shows how to display the status of Fast Ethernet port 5/5:
Router# show protocols fastethernet 5/5 FastEthernet5/5 is up, line protocol is up Router#
Clearing Counters on an Interface

To clear the interface counters shown with the show interfaces command, perform this task: Command
Router# clear counters {{vlan vlan_ID} | {type1 slot/port} | {port-channel channel_ID}} 1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
Purpose Clears interface counters.
This example shows how to clear and reset the counters on Fast Ethernet port 5/5:
Router# clear counters fastethernet 5/5 Clear "show interface" counters on this interface [confirm] y Router# *Sep 30 08:42:55: %CLEAR-5-COUNTERS: Clear counter on interface FastEthernet5/5
The clear counters command clears all the current counters from the interface unless the optional arguments specify a specific interface. The clear counters command clears counters displayed with the EXEC show interfaces command, not counters retrieved using SNMP.
Note
Resetting an Interface
To reset an interface, perform this task: Command
Router# clear interface type
1
Purpose
slot/port
Resets an interface.
This example shows how to reset Fast Ethernet port 5/5:

Router# clear interface fastethernet 5/5
9-18
OL-3999-08
Chapter 9
Configuring Interfaces Checking the Cable Status Using the TDR
Router#
Shutting Down and Restarting an Interface

You can shut down an interface, which disables all functions on the specified interface and shows the interface as unavailable on all monitoring command displays. This information is communicated to other network servers through all dynamic routing protocols. The interface is not included in any routing updates. To shut down an interface and then restart it, perform this task: Command
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel channel_ID}} Router(config-if)# shutdown Router(config-if)# no shutdown 1.
Purpose Selects the interface to be configured. Shuts down the interface. Reenables the interface.
This example shows how to shut down Fast Ethernet port 5/5:
Router(config)# interface fastethernet 5/5 Router(config-if)# shutdown Router(config-if)# *Sep 30 08:33:47: %LINK-5-CHANGED: Interface FastEthernet5/5, changed state to administratively down
This example shows how to reenable Fast Ethernet port 5/5:

Router(config-if)# no shutdown Router(config-if)# *Sep 30 08:36:00: %LINK-3-UPDOWN: Interface FastEthernet5/5, changed state to up
To check if an interface is disabled, enter the EXEC show interfaces command. An interface that has been shut down is shown as administratively down in the show interfaces command display.
Checking the Cable Status Using the TDR

You can check the status of copper cables using the time domain reflectometer (TDR). The TDR detects a cable fault by sending a signal through the cable and reading the signal that is reflected back to it. All or part of the signal can be reflected back by any number of cable defects or by the end of the cable itself. Use the TDR to determine if the cabling is at fault if you cannot establish a link. This test is especially important when replacing an existing switch, upgrading to Gigabit Ethernet, or installing new cables. The port must be up before running the TDR test. If the port is down, you cannot enter the test cable-diagnostics tdr command successfully, and the following message is displayed:
Router# test cable-diagnostics tdr interface gigabitethernet2/12 % Interface Gi2/12 is administratively down % Use 'no shutdown' to enable interface before TDR test start.
Note
TDR can test cables up to a maximum length of 115 meters.
9-19
Chapter 9 Checking the Cable Status Using the TDR
See the Release Notes for Cisco IOS Release 12.2SXF and Rebuilds for information about which modules support the TDR.
To start or stop the TDR test, perform this task: Command

test cable-diagnostics tdr interface {interface interface-number}
Purpose Starts or stops the TDR test.
This example shows how to run the TDR-cable diagnostics:

Router # test cable-diagnostics tdr interface gigabitethernet2/1 TDR test started on interface Gi2/1 A TDR test can take a few seconds to run on an interface Use 'show cable-diagnostics tdr' to read the TDR results. Router #
Tip
9-20
OL-3999-08
C H A P T E R
10

This chapter describes how to use the command-line interface (CLI) to configure Ethernet, Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet LAN ports for Layer 2 switching on the Catalyst 6500 series switches. The configuration tasks in this chapter apply to LAN ports on LAN switching modules and to the LAN ports on the supervisor engine.
Note
To configure Layer 3 interfaces, see Chapter 22, Configuring Layer 3 Interfaces.

Understanding How Layer 2 Switching Works, page 10-1 Default Layer 2 LAN Interface Configuration, page 10-5 Layer 2 LAN Interface Configuration Guidelines and Restrictions, page 10-5 Configuring LAN Interfaces for Layer 2 Switching, page 10-6
Tip
Understanding How Layer 2 Switching Works

These sections describe how Layer 2 switching works on the Catalyst 6500 series switches:

Understanding Layer 2 Ethernet Switching, page 10-2 Understanding VLAN Trunks, page 10-3 Layer 2 LAN Port Modes, page 10-4
10-1
Chapter 10 Understanding How Layer 2 Switching Works
Understanding Layer 2 Ethernet Switching

These sections describe Layer 2 Ethernet switching:

Layer 2 Ethernet Switching Overview, page 10-2 Switching Frames Between Segments, page 10-2 Building the Address Table, page 10-2
Layer 2 Ethernet Switching Overview

Catalyst 6500 series switches support simultaneous, parallel connections between Layer 2 Ethernet segments. Switched connections between Ethernet segments last only for the duration of the packet. New connections can be made between different segments for the next packet. Catalyst 6500 series switches solve congestion problems caused by high-bandwidth devices and by a large number of users by assigning each device (for example, a server) to its own 10-, 100-, or 1000-Mbps collision domain. Because each LAN port connects to a separate Ethernet collision domain, servers in a properly configured switched environment achieve full access to the bandwidth. Because collisions cause significant congestion in Ethernet networks, an effective solution is full-duplex communication. Normally, Ethernet operates in half-duplex mode, which means that stations can either receive or transmit. In full-duplex mode, two stations can transmit and receive at the same time. When packets can flow in both directions simultaneously, the effective Ethernet bandwidth doubles.
Switching Frames Between Segments

Each LAN port on a Catalyst 6500 series switch can connect to a single workstation or server, or to a hub through which workstations or servers connect to the network. On a typical Ethernet hub, all ports connect to a common backplane within the hub, and the bandwidth of the network is shared by all devices attached to the hub. If two stations establish a session that uses a significant level of bandwidth, the network performance of all other stations attached to the hub is degraded. To reduce degradation, the switch considers each LAN port to be an individual segment. When stations connected to different LAN ports need to communicate, the switch forwards frames from one LAN port to the other at wire speed to ensure that each session receives full bandwidth. To switch frames between LAN ports efficiently, the switch maintains an address table. When a frame enters the switch, it associates the MAC address of the sending network device with the LAN port on which it was received.
Building the Address Table

Catalyst 6500 series switches build the address table by using the source address of the frames received. When the switch receives a frame for a destination address not listed in its address table, it floods the frame to all LAN ports of the same VLAN except the port that received the frame. When the destination station replies, the switch adds its relevant source address and port ID to the address table. The switch then forwards subsequent frames to a single LAN port without flooding to all LAN ports. The address table can store at least 32,000 address entries without flooding any entries. The switch uses an aging mechanism, defined by a configurable aging timer, so if an address remains inactive for a specified number of seconds, it is removed from the address table.
10-2
OL-3999-08
Chapter 10
Configuring LAN Ports for Layer 2 Switching Understanding How Layer 2 Switching Works
Understanding VLAN Trunks

These sections describe VLAN trunks on the Catalyst 6500 series switches:

Trunking Overview, page 10-3 Encapsulation Types, page 10-3
Trunking Overview
Note
For information about VLANs, see Chapter 14, Configuring VLANs. A trunk is a point-to-point link between the switch and another networking device. Trunks carry the traffic of multiple VLANs over a single link and allow you to extend VLANs across an entire network. Two trunking encapsulations are available on all Ethernet ports:
Inter-Switch Link (ISL)ISL is a Cisco-proprietary trunking encapsulation. The following switching modules do not support ISL encapsulation:
Note
WS-X6502-10GE WS-X6548-GE-TX, WS-X6548V-GE-TX, WS-X6548-GE-45AF WS-X6148-GE-TX, WS-X6148V-GE-TX, WS-X6148-GE-45AF
802.1Q802.1Q is an industry-standard trunking encapsulation.
You can configure a trunk on a single Ethernet port or on an EtherChannel. For more information about EtherChannel, see Chapter 12, Configuring EtherChannels. Ethernet trunk ports support several trunking modes (see Table 10-2 on page 10-4). You can specify whether the trunk uses ISL or 802.1Q encapsulation, and if the encapsulation type is autonegotiated.
Note
You can configure LAN ports to negotiate the encapsulation type. You cannot configure WAN interfaces to negotiate the encapsulation type. The Dynamic Trunking Protocol (DTP) manages trunk autonegotiation on LAN ports. DTP supports autonegotiation of both ISL and 802.1Q trunks within a VTP domain. To autonegotiate trunking, the LAN ports must be in the same VTP domain. Use the trunk or nonegotiate keywords to force LAN ports in different domains to trunk. For more information on VTP domains, see Chapter 13, Configuring VTP.
Encapsulation Types
Table 10-1 lists the Ethernet trunk encapsulation types.
10-3
Table 10-1 Ethernet Trunk Encapsulation Types
Encapsulation switchport trunk encapsulation isl
Function Specifies ISL encapsulation on the trunk link.

Note
Some modules do not support ISL encapsulation (see the Trunking Overview section on page 10-3).
switchport trunk encapsulation dot1q switchport trunk encapsulation negotiate
Specifies 802.1Q encapsulation on the trunk link. Specifies that the LAN port negotiate with the neighboring LAN port to become an ISL (preferred) or 802.1Q trunk, depending on the configuration and capabilities of the neighboring LAN port.
The trunking mode, the trunk encapsulation type, and the hardware capabilities of the two connected LAN ports determine whether a link becomes an ISL or 802.1Q trunk.
Layer 2 LAN Port Modes

Table 10-2 lists the Layer 2 LAN port modes and describes how they function on LAN ports.
Table 10-2 Layer 2 LAN Port Modes
Mode switchport mode access
Function Puts the LAN port into permanent nontrunking mode and negotiates to convert the link into a nontrunk link. The LAN port becomes a nontrunk port even if the neighboring LAN port does not agree to the change. Makes the LAN port actively attempt to convert the link to a trunk link. The LAN port becomes a trunk port if the neighboring LAN port is set to trunk, desirable, or auto mode. This is the default mode for all LAN ports. Makes the LAN port willing to convert the link to a trunk link. The LAN port becomes a trunk port if the neighboring LAN port is set to trunk or desirable mode. Puts the LAN port into permanent trunking mode and negotiates to convert the link into a trunk link. The LAN port becomes a trunk port even if the neighboring port does not agree to the change. Puts the LAN port into permanent trunking mode but prevents the port from generating DTP frames. You must configure the neighboring port manually as a trunk port to establish a trunk link.
switchport mode dynamic desirable
switchport mode dynamic auto switchport mode trunk
switchport nonegotiate
Note
DTP is a point-to-point protocol. However, some internetworking devices might forward DTP frames improperly. To avoid this problem, ensure that LAN ports connected to devices that do not support DTP are configured with the access keyword if you do not intend to trunk across those links. To enable trunking to a device that does not support DTP, use the nonegotiate keyword to cause the LAN port to become a trunk but not generate DTP frames.
10-4
OL-3999-08
Chapter 10
Configuring LAN Ports for Layer 2 Switching Default Layer 2 LAN Interface Configuration
Default Layer 2 LAN Interface Configuration

Table 10-3 shows the Layer 2 LAN port default configuration.
Table 10-3 Layer 2 LAN Interface Default Configuration
Feature Interface mode:

Default
Before entering the switchport command Layer 3 (unconfigured) After entering the switchport command switchport mode dynamic desirable switchport trunk encapsulation negotiate VLANs 1 to 4094, except reserved VLANs (see Table 14-1 on page 14-2) VLANs 2 to 1001 VLAN 1 VLAN 1 Enabled for all VLANs 128

Trunk encapsulation Allowed VLAN range VLAN range eligible for pruning Default access VLAN Native VLAN (for 802.1Q trunks) Spanning Tree Protocol (STP) STP port priority STP port cost
100 for 10-Mbps Ethernet LAN ports 19 for 10/100-Mbps Fast Ethernet LAN ports 19 for 100-Mbps Fast Ethernet LAN ports 4 for 1,000-Mbps Gigabit Ethernet LAN ports 2 for 10,000-Mbps 10-Gigabit Ethernet LAN ports
Layer 2 LAN Interface Configuration Guidelines and Restrictions

When configuring Layer 2 LAN ports, follow these guidelines and restrictions:
The following switching modules do not support ISL encapsulation:

10-5
Chapter 10 Configuring LAN Interfaces for Layer 2 Switching
The following configuration guidelines and restrictions apply when using 802.1Q trunks and impose some limitations on the trunking strategy for a network. Note these restrictions when using 802.1Q trunks:
When connecting Cisco switches through an 802.1q trunk, make sure the native VLAN for an
802.1Q trunk is the same on both ends of the trunk link. If the native VLAN on one end of the trunk is different from the native VLAN on the other end, spanning tree loops might result.
Disabling spanning tree on the native VLAN of an 802.1Q trunk without disabling spanning tree
on every VLAN in the network can cause spanning tree loops. We recommend that you leave spanning tree enabled on the native VLAN of an 802.1Q trunk. If this is not possible, disable spanning tree on every VLAN in the network. Make sure your network is free of physical loops before disabling spanning tree.
When you connect two Cisco switches through 802.1Q trunks, the switches exchange spanning
tree BPDUs on each VLAN allowed on the trunks. The BPDUs on the native VLAN of the trunk are sent untagged to the reserved IEEE 802.1d spanning tree multicast MAC address (01-80-C2-00-00-00). The BPDUs on all other VLANs on the trunk are sent tagged to the reserved Cisco Shared Spanning Tree (SSTP) multicast MAC address (01-00-0c-cc-cc-cd).
Non-Cisco 802.1Q switches maintain only a single instance of spanning tree that defines the
spanning tree topology for all VLANs. When you connect a Cisco switch to a non-Cisco switch through an 802.1Q trunk, the MST of the non-Cisco switch and the native VLAN spanning tree of the Cisco switch combine to form a single spanning tree topology known as the Common Spanning Tree (CST).
Because Cisco switches transmit BPDUs to the SSTP multicast MAC address on VLANs other
than the native VLAN of the trunk, non-Cisco switches do not recognize these frames as BPDUs and flood them on all ports in the corresponding VLAN. Other Cisco switches connected to the non-Cisco 802.1q cloud receive these flooded BPDUs. This allows Cisco switches to maintain a per-VLAN spanning tree topology across a cloud of non-Cisco 802.1Q switches. The non-Cisco 802.1Q cloud separating the Cisco switches is treated as a single broadcast segment between all switches connected to the non-Cisco 802.1q cloud through 802.1q trunks.
Make certain that the native VLAN is the same on all of the 802.1q trunks connecting the Cisco
switches to the non-Cisco 802.1q cloud.

If you are connecting multiple Cisco switches to a non-Cisco 802.1q cloud, all of the
connections must be through 802.1q trunks. You cannot connect Cisco switches to a non-Cisco 802.1q cloud through ISL trunks or through access ports. Doing so causes the switch to place the ISL trunk port or access port into the spanning tree port inconsistent state and no traffic will pass through the port.
Configuring LAN Interfaces for Layer 2 Switching

These sections describe how to configure Layer 2 switching on the Catalyst 6500 series switches:

Configuring a LAN Port for Layer 2 Switching, page 10-7 Configuring a Layer 2 Switching Port as a Trunk, page 10-8 Configuring a LAN Interface as a Layer 2 Access Port, page 10-14 Configuring a Custom IEEE 802.1Q EtherType Field Value, page 10-15
10-6
OL-3999-08
Chapter 10
Configuring LAN Ports for Layer 2 Switching Configuring LAN Interfaces for Layer 2 Switching
Note
Use the default interface {ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port command to revert an interface to its default configuration.
Configuring a LAN Port for Layer 2 Switching

To configure a LAN port for Layer 2 switching, perform this task: Command
Router(config)# interface type Router(config-if)# shutdown
1
Purpose
slot/port
Selects the LAN port to configure. (Optional) Shuts down the interface to prevent traffic flow until configuration is complete. Configures the LAN port for Layer 2 switching.
Note
Router(config-if)# switchport
You must enter the switchport command once without any keywords to configure the LAN port as a Layer 2 port before you can enter additional switchport commands with keywords.
Router(config-if)# no switchport
Clears Layer 2 LAN port configuration. Activates the interface. (Required only if you shut down the interface.) Exits configuration mode. Displays the running configuration of the interface. Displays the switch port configuration of the interface. Displays the trunk configuration of the interface.
Step 4 Step 5 Step 6 Step 7 Step 8
Router(config-if)# no shutdown
Router(config-if)# end Router# show running-config interface [type1 slot/port] Router# show interfaces [type1 slot/port] switchport Router# show interfaces [type1 slot/port] trunk 1.
After you enter the switchport command, the default mode is switchport mode dynamic desirable. If the neighboring port supports trunking and is configured to allow trunking, the link becomes a Layer 2 trunk when you enter the switchport command. By default, LAN trunk ports negotiate encapsulation. If the neighboring port supports ISL and 802.1Q encapsulation and both ports are set to negotiate the encapsulation type, the trunk uses ISL encapsulation (10-Gigabit Ethernet ports do not support ISL encapsulation).
Note
When using the switchport command, if a port configured for Layer 3 is now configured for Layer 2, the configuration for Layer 3 is retained in the memory but not in the running configuration and is applied to the port whenever the port switches back to Layer 3. Also, if a port configured for Layer 2 is now configured for Layer 3, the configuration for Layer 2 is retained in the memory but not in the running configuration and is applied to the port whenever the port switches back to Layer 2. To restore the default configuration of the port in the memory and in the running configuration, use the default interface command. To avoid potential issues while changing the role of a port using the switchport command, shut down the interface before applying the switchport command.
10-7
Configuring a Layer 2 Switching Port as a Trunk

These section describe configuring a Layer 2 switching port as a trunk:

Configuring the Layer 2 Switching Port as an ISL or 802.1Q Trunk, page 10-8 Configuring the Layer 2 Trunk to Use DTP, page 10-9 Configuring the Layer 2 Trunk Not to Use DTP, page 10-9 Configuring the Access VLAN, page 10-10 Configuring the 802.1Q Native VLAN, page 10-10 Configuring the List of VLANs Allowed on a Trunk, page 10-11 Configuring the List of Prune-Eligible VLANs, page 10-11 Completing Trunk Configuration, page 10-12 Verifying Layer 2 Trunk Configuration, page 10-12 Configuration and Verification Examples, page 10-13
Configuring the Layer 2 Switching Port as an ISL or 802.1Q Trunk

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section. When you enter the switchport command with no other keywords (Step 3 in the previous section), the default mode is switchport mode dynamic desirable and switchport trunk encapsulation negotiate.
To configure the Layer 2 switching port as an ISL or 802.1Q trunk, perform this task: Command
Router(config-if)# switchport trunk encapsulation {isl | dot1q | negotiate} Router(config-if)# no switchport trunk encapsulation
Purpose (Optional) Configures the encapsulation, which configures the Layer 2 switching port as either an ISL or 802.1Q trunk. Reverts to the default trunk encapsulation mode ( negotiate).
When configuring the Layer 2 switching port as an ISL or 802.1Q trunk, note the following information:
The switchport mode trunk command (see the Configuring the Layer 2 Trunk Not to Use DTP section on page 10-9) is not compatible with the switchport trunk encapsulation negotiate command. To support the switchport mode trunk command, you must configure the encapsulation as either ISL or 802.1Q. The following switching modules do not support ISL encapsulation:
10-8
OL-3999-08
Chapter 10
Note
Complete the steps in the Completing Trunk Configuration section on page 10-12 after performing the tasks in this section.
Configuring the Layer 2 Trunk to Use DTP

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section. To configure the Layer 2 trunk to use DTP, perform this task:
Command
Router(config-if)# switchport mode dynamic {auto | desirable} Router(config-if)# no switchport mode
Purpose (Optional) Configures the trunk to use DTP. Reverts to the default trunk trunking mode (switchport mode dynamic desirable).
When configuring the Layer 2 trunk to use DTP, note the following information:

Required only if the interface is a Layer 2 access port or to specify the trunking mode. See Table 10-2 on page 10-4 for information about trunking modes.
Note
Configuring the Layer 2 Trunk Not to Use DTP

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section. To configure the Layer 2 trunk not to use DTP, perform this task:
Command
Step 1
Router(config-if)# switchport mode trunk Router(config-if)# no switchport mode
Purpose (Optional) Configures the port to trunk unconditionally. Reverts to the default trunk trunking mode ( switchport mode dynamic desirable). (Optional) Configures the trunk not to use DTP. Enables DTP on the port.
Step 2
Router(config-if)# switchport nonegotiate Router(config-if)# no switchport nonegotiate
When configuring the Layer 2 trunk not to use DTP, note the following information:
Before entering the switchport mode trunk command, you must configure the encapsulation (see the Configuring the Layer 2 Switching Port as an ISL or 802.1Q Trunk section on page 10-8).
10-9
To support the switchport nonegotiate command, you must enter the switchport mode trunk command. Enter the switchport mode dynamic trunk command. See Table 10-2 on page 10-4 for information about trunking modes. Before entering the switchport nonegotiate command, you must configure the encapsulation (see the Configuring the Layer 2 Switching Port as an ISL or 802.1Q Trunk section on page 10-8) and configure the port to trunk unconditionally with the switchport mode trunk command (see the Configuring the Layer 2 Trunk to Use DTP section on page 10-9).
Note
Configuring the Access VLAN

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section. To configure the access VLAN, perform this task:
Command
Router(config-if)# switchport access vlan vlan_ID
Purpose (Optional) Configures the access VLAN, which is used if the interface stops trunking. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default value (VLAN 1).
Router(config-if)# no switchport access vlan
Note
Configuring the 802.1Q Native VLAN

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section. To configure the 802.1Q native VLAN, perform this task:
Command
Router(config-if)# switchport trunk native vlan vlan_ID Router(config-if)# no switchport trunk native vlan
Purpose (Optional) Configures the 802.1Q native VLAN. Reverts to the default value (VLAN 1).
10-10
OL-3999-08
Chapter 10
When configuring the native VLAN, note the following information:

The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). The access VLAN is not automatically used as the native VLAN.
Note
Configuring the List of VLANs Allowed on a Trunk

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section. To configure the list of VLANs allowed on a trunk, perform this task:
Command
Router(config-if)# switchport trunk allowed vlan {add | except | none | remove} vlan [,vlan[,vlan[,...]] Router(config-if)# no switchport trunk allowed vlan
Purpose (Optional) Configures the list of VLANs allowed on the trunk. Reverts to the default value (all VLANs allowed).
When configuring the list of VLANs allowed on a trunk, note the following information:
The vlan parameter is either a single VLAN number from 1 through 4094, or a range of VLANs described by two VLAN numbers, the lesser one first, separated by a dash. Do not enter any spaces between comma-separated vlan parameters or in dash-specified ranges. All VLANs are allowed by default. You can remove VLAN 1. If you remove VLAN 1 from a trunk, the trunk interface continues to send and receive management traffic, for example, Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), Port Aggregation Protocol (PAgP), and DTP in VLAN 1.
Note
Configuring the List of Prune-Eligible VLANs

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 10-7 before performing the tasks in this section.
10-11
To configure the list of prune-eligible VLANs on the Layer 2 trunk, perform this task: Command
Router(config-if)# switchport trunk pruning vlan {none |{{add | except | remove} vlan[,vlan[,vlan[,...]]}} Router(config-if)# no switchport trunk pruning vlan
Purpose (Optional) Configures the list of prune-eligible VLANs on the trunk (see the Understanding VTP Pruning section on page 13-4). Reverts to the default value (all VLANs prune-eligible).
When configuring the list of prune-eligible VLANs on a trunk, note the following information:
The vlan parameter is either a single VLAN number from 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2), or a range of VLANs described by two VLAN numbers, the lesser one first, separated by a dash. Do not enter any spaces between comma-separated vlan parameters or in dash-specified ranges. The default list of VLANs allowed to be pruned contains all VLANs. Network devices in VTP transparent mode do not send VTP Join messages. On Catalyst 6500 series switches with trunk connections to network devices in VTP transparent mode, configure the VLANs used by the transparent-mode network devices or that need to be carried across the transparent-mode network devices as pruning ineligible.
Note
Completing Trunk Configuration

To complete Layer 2 trunk configuration, perform this task: Command
Step 1 Step 2
Purpose Activates the interface. (Required only if you shut down the interface.) Exits configuration mode.
Router(config-if)# end
Verifying Layer 2 Trunk Configuration

To verify Layer 2 trunk configuration, perform this task: Command
Router# show running-config interface type slot/port Router# show interfaces [type1 slot/port] switchport Router# show interfaces [type1 slot/port] trunk 1.
1
Purpose Displays the running configuration of the interface. Displays the switch port configuration of the interface. Displays the trunk configuration of the interface.
10-12
OL-3999-08
Chapter 10
Configuration and Verification Examples

This example shows how to configure the Fast Ethernet port 5/8 as an 802.1Q trunk. This example assumes that the neighbor port is configured to support 802.1Q trunking:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/8 Router(config-if)# shutdown Router(config-if)# switchport Router(config-if)# switchport mode dynamic desirable Router(config-if)# switchport trunk encapsulation dot1q Router(config-if)# no shutdown Router(config-if)# end Router# exit

Router# show running-config interface fastethernet 5/8 Building configuration... Current configuration: ! interface FastEthernet5/8 no ip address switchport switchport trunk encapsulation dot1q end Router# show interfaces fastethernet 5/8 switchport Name: Fa5/8 Switchport: Enabled Administrative Mode: dynamic desirable Operational Mode: trunk Administrative Trunking Encapsulation: negotiate Operational Trunking Encapsulation: dot1q Negotiation of Trunking: Enabled Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Trunking VLANs Enabled: ALL Pruning VLANs Enabled: ALL Router# show interfaces fastethernet 5/8 trunk Port Fa5/8 Mode desirable Encapsulation n-802.1q Status trunking Native vlan 1
Port Vlans allowed on trunk Fa5/8 1-1005 Port Vlans allowed and active in management domain Fa5/8 1-6,10,20,50,100,152,200,300,303-305,349-351,400,500,521,524,570,801-8 02,850,917,999,1002-1005 Port Vlans in spanning tree forwarding state and not pruned Fa5/8 1-6,10,20,50,100,152,200,300,303-305,349-351,400,500,521,524,570,801-8 02,850,917,999,1002-1005 Router#
10-13
Configuring a LAN Interface as a Layer 2 Access Port

Note
If you assign a LAN port to a VLAN that does not exist, the port is shut down until you create the VLAN in the VLAN database (see the Creating or Modifying an Ethernet VLAN section on page 14-10). To configure a LAN port as a Layer 2 access port, perform this task:
Command
Router(config)# interface type Router(config-if)# shutdown
1
Purpose
slot/port
Selects the LAN port to configure. (Optional) Shuts down the interface to prevent traffic flow until configuration is complete. Configures the LAN port for Layer 2 switching.
Note
Router(config-if)# switchport
You must enter the switchport command once without any keywords to configure the LAN port as a Layer 2 port before you can enter additional switchport commands with keywords.
Step 4 Step 5
Router(config-if)# no switchport Router(config-if)# switchport mode access Router(config-if)# no switchport mode
Clears Layer 2 LAN port configuration. Configures the LAN port as a Layer 2 access port. Reverts to the default switchport mode (switchport mode dynamic desirable). Places the LAN port in a VLAN. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default access VLAN (VLAN 1). Activates the interface. (Required only if you shut down the interface.) Exits configuration mode. Displays the running configuration of the interface. Displays the switch port configuration of the interface.
Step 6
Router(config-if)# switchport access vlan vlan_ID
Router(config-if)# no switchport access vlan
Router(config-if)# end Router# show running-config interface [type1 slot/port] switchport 1.
Step 10 Router# show interfaces [type1 slot/port]
This example shows how to configure the Fast Ethernet port 5/6 as an access port in VLAN 200:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/6 Router(config-if)# shutdown Router(config-if)# switchport Router(config-if)# switchport mode access Router(config-if)# switchport access vlan 200 Router(config-if)# no shutdown Router(config-if)# end Router# exit
10-14
OL-3999-08
Chapter 10

Router# show running-config interface fastethernet 5/6 Building configuration... ! Current configuration: interface FastEthernet5/6 no ip address switchport access vlan 200 switchport mode access end Router# show interfaces fastethernet 5/6 switchport Name: Fa5/6 Switchport: Enabled Administrative Mode: static access Operational Mode: static access Administrative Trunking Encapsulation: negotiate Operational Trunking Encapsulation: native Negotiation of Trunking: Enabled Access Mode VLAN: 200 (VLAN0200) Trunking Native Mode VLAN: 1 (default) Trunking VLANs Enabled: ALL Pruning VLANs Enabled: ALL Router#
Configuring a Custom IEEE 802.1Q EtherType Field Value

With Release 12.2(17a)SX and later releases, you can configure a custom EtherType field value on a port to support network devices that do not use the standard 0x8100 EtherType field value on 802.1Q-tagged or 802.1p-tagged frames. To configure a custom value for the EtherType field, perform this task: Command
Router(config-if)# switchport dot1q ethertype value Router(config-if)# no switchport dot1q ethertype
Purpose Configures the 802.1Q EtherType field value for the port. Reverts to the default 802.1Q EtherType field value (0x8100).
When configuring a custom EtherType field value, note the following information:

To use a custom EtherType field value, all network devices in the traffic path across the network must support the custom EtherType field value. You can configure a custom EtherType field value on trunk ports, access ports, and tunnel ports. You can configure a custom EtherType field value on the member ports of an EtherChannel. You cannot configure a custom EtherType field value on a port-channel interface. Each port supports only one EtherType field value. A port that is configured with a custom EtherType field value does not recognize frames that have any other EtherType field value as tagged frames. For example, a trunk port that is configured with a custom EtherType field value does not recognize the standard 0x8100 EtherType field value on 802.1Q-tagged frames and cannot put the frames into the VLAN to which they belong.
10-15
Caution
A port that is configured with a custom EtherType field value considers frames that have any other EtherType field value to be untagged frames. A trunk port with a custom EtherType field value places frames with any other EtherType field value into the native VLAN. An access port or tunnel port with a custom EtherType field value places frames that are tagged with any other EtherType field value into the access VLAN. If you misconfigure a custom EtherType field value, frames might be placed into the wrong VLAN.
See the Release Notes for Cisco IOS Release 12.2SXF and Rebuilds for a list of the modules that support custom IEEE 802.1Q EtherType field values.
This example shows how to configure the EtherType field value to 0x1234:
Router (config-if)# switchport dot1q ethertype 1234 Router (config-if)#
Tip
10-16
OL-3999-08
C H A P T E R
11
Configuring Flex Links

This chapter describes how to configure Flex Links on the Catalyst 6500 series switch. Release 12.2(18)SXF and later releases support Flex Links.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
The chapter consists of these sections:

Understanding Flex Links, page 11-1 Configuring Flex Links, page 11-2 Monitoring Flex Links, page 11-4
Tip
Understanding Flex Links

Flex Links are a pair of a Layer 2 interfaces (switchports or port channels), where one interface is configured to act as a backup to the other. Flex Links are typically configured in service-provider or enterprise networks where customers do not want to run STP. Flex Links provide link-level redundancy that is an alternative to Spanning Tree Protocol (STP). STP is automatically disabled on Flex Links interfaces. The Catalyst 6500 series switches support a maximum of 16 Flex Links. To configure the Flex Links feature, you configure one Layer 2 interface as the standby link for the link that you want to be primary. With Flex Links configured for a pair of interfaces, only one of the interfaces is in the linkup state and is forwarding traffic. If the primary link shuts down, the standby link starts forwarding traffic. When the inactive link comes back up, it goes into standby mode.
11-1
Chapter 11 Configuring Flex Links
In Figure 11-1, ports 1 and 2 on switch A are connected to uplink switches B and C. Because they are configured as Flex Links, only one of the interfaces is forwarding traffic and the other one is in standby mode. If port 1 is the active link, it begins forwarding traffic between port 1 and switch B; the link between port 2 (the backup link) and switch C is not forwarding traffic. If port 1 goes down, port 2 comes up and starts forwarding traffic to switch C. When port 1 comes back up, it goes into standby mode and does not forward traffic; port 2 continues to forward traffic.
Figure 11-1 Flex Links Configuration Example
Port 1 A
Port 2
140036
If a primary (forwarding) link goes down, a trap notifies the network management stations. If the standby link goes down, a trap notifies the users. Flex Links are supported only on Layer 2 ports and port channels, not on VLANs or on Layer 3 ports.

These sections contain this configuration information:

Flex Links Default Configuration, page 11-2 Flex Links Configuration Guidelines and Restrictions, page 11-2 Configuring Flex Links, page 11-3
Flex Links Default Configuration

There is no default Flex Links configuration.
Flex Links Configuration Guidelines and Restrictions

When configuring Flex Links, follow these guidelines and restrictions:

You can configure only one Flex Links backup link for any active link, and it must be a different interface from the active interface. An interface can belong to only one Flex Links pair. An interface can be a backup link for only one active link. An active link cannot belong to another Flex Links pair. Neither of the links can be a port that belongs to an EtherChannel. However, you can configure two port channels (EtherChannel logical interfaces) as Flex Links, and you can configure a port channel and a physical interface as Flex Links, with either the port channel or the physical interface as the active link.
11-2
OL-3999-08
Chapter 11
Configuring Flex Links Configuring Flex Links
A backup link does not have to be the same type as the active link (Fast Ethernet, Gigabit Ethernet, or port channel). However, you should configure both Flex Links with similar characteristics so that there are no loops or changes in operation if the standby link becomes active. STP is disabled on Flex Links ports. If STP is disabled on the switch, be sure that there are no Layer 2 loops in the network topology. Do not configure the following STP features on Flex Links ports or the ports to which the links connect:
Bridge Assurance UplinkFast BackboneFast EtherChannel Guard Root Guard Loop Guard PVST Simulation
Configured MAC addresses should be different on active and backup ports. The current CLI disallows configuring of the same address on two ports. Therefore, users have to reconfigure those addresses after Flex Links failover. Port security on Flex Links ports may trigger false violations during Flex Links switchover which in turn triggers a port security shutdown or restrict action. We do not recommend configuring port security on Flex Links ports.

To configure Flex Links, perform this task: Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Router# configure terminal Router(conf)# interface {{type {port-channel number}}
1
Purpose Enters global configuration mode.

slot/port} |
Specifies a Layer 2 interface. Configures the interface as part of a Flex Links pair. Exits configuration mode.
Router(conf-if)# switchport backup interface {{type1 slot/port} | {port-channel number}} Router(conf-if)# exit Router# show interface [{type slot/port} | {port-channel number}] switchport backup Router# copy running-config startup config
1
Verifies the configuration. (Optional) Saves your entries in the switch startup configuration file.
1.
type = ethernet, fastethernet, gigabitethernet , or tengigabitethernet
This example shows how to configure an interface with a backup interface and how to verify the configuration:
Router# configure terminal Router(conf)# interface fastethernet1/1 Router(conf-if)# switchport backup interface fastethernet1/2 Router(conf-if)# exit Router# show interface switchport backup
11-3
Chapter 11 Monitoring Flex Links
Router Backup Interface Pairs: Active Interface Backup Interface State -----------------------------------------------------------------------------------------FastEthernet1/1 FastEthernet1/2 Active Up/Backup Standby FastEthernet1/3 FastEthernet2/4 Active Up/Backup Standby Port-channel1 GigabitEthernet7/1 Active Up/Backup Standby
Monitoring Flex Links

Table 11-1 shows the privileged EXEC command for monitoring the Flex Links configuration.
Table 11-1 Flex Links Monitoring Command
Command
show interface [{type1 slot/port} | {port-channel number}] switchport backup
Purpose Displays the Flex Links backup interface configured for an interface, or displays all Flex Links configured on the switch and the state of each active and backup interface (up or standby mode).
Tip
11-4
OL-3999-08
C H A P T E R
12
This chapter describes how to configure EtherChannels on the Catalyst 6500 series switch Layer 2 or Layer 3 LAN ports.
Note

Understanding How EtherChannels Work, page 12-1 EtherChannel Feature Configuration Guidelines and Restrictions, page 12-5 Configuring EtherChannels, page 12-7
Tip
Understanding How EtherChannels Work

These sections describe how EtherChannels work:

EtherChannel Feature Overview, page 12-2 Understanding How EtherChannels Are Configured, page 12-2 Understanding Port Channel Interfaces, page 12-5 Understanding Load Balancing, page 12-5
12-1
Chapter 12 Understanding How EtherChannels Work
EtherChannel Feature Overview

An EtherChannel bundles individual Ethernet links into a single logical link that provides the aggregate bandwidth of up to eight physical links. With Release 12.2(18)SXE and later releases, a Catalyst 6500 series switch supports a maximum of 128 EtherChannels. With releases earlier than Release 12.2(18)SXE, a Catalyst 6500 series switch supports a maximum of 64 EtherChannels. You can form an EtherChannel with up to eight compatibly configured LAN ports on any module in a Catalyst 6500 series switch. All LAN ports in each EtherChannel must be the same speed and must all be configured as either Layer 2 or Layer 3 LAN ports.
Note
The network device to which a Catalyst 6500 series switch is connected may impose its own limits on the number of ports in an EtherChannel. If a segment within an EtherChannel fails, traffic previously carried over the failed link switches to the remaining segments within the EtherChannel. When a failure occurs, the EtherChannel feature sends a trap that identifies the switch, the EtherChannel, and the failed link. Inbound broadcast and multicast packets on one segment in an EtherChannel are blocked from returning on any other segment of the EtherChannel.
Understanding How EtherChannels Are Configured

These sections describe how EtherChannels are configured:

EtherChannel Configuration Overview, page 12-2 Understanding Manual EtherChannel Configuration, page 12-3 Understanding PAgP EtherChannel Configuration, page 12-3 Understanding IEEE 802.3ad LACP EtherChannel Configuration, page 12-4
EtherChannel Configuration Overview

You can configure EtherChannels manually or you can use the Port Aggregation Control Protocol (PAgP) or the Link Aggregation Control Protocol (LACP) to form EtherChannels. The EtherChannel protocols allow ports with similar characteristics to form an EtherChannel through dynamic negotiation with connected network devices. PAgP is a Cisco-proprietary protocol and LACP is defined in IEEE 802.3ad. PAgP and LACP do not interoperate with each other. Ports configured to use PAgP cannot form EtherChannels with ports configured to use LACP. Ports configured to use LACP cannot form EtherChannels with ports configured to use PAgP. Neither interoperates with ports configured manually. Table 12-1 lists the user-configurable EtherChannel modes.
12-2
OL-3999-08
Chapter 12
Configuring EtherChannels Understanding How EtherChannels Work
Table 12-1 EtherChannel Modes
Mode on
Description Mode that forces the LAN port to channel unconditionally. In the on mode, a usable EtherChannel exists only when a LAN port group in the on mode is connected to another LAN port group in the on mode. Because ports configured in the on mode do not negotiate, there is no negotiation traffic between the ports. You cannot configure the on mode with an EtherChannel protocol. If one end uses the on mode, the other end must also. PAgP mode that places a LAN port into a passive negotiating state, in which the port responds to PAgP packets it receives but does not initiate PAgP negotiation. (Default) PAgP mode that places a LAN port into an active negotiating state, in which the port initiates negotiations with other LAN ports by sending PAgP packets. LACP mode that places a port into a passive negotiating state, in which the port responds to LACP packets it receives but does not initiate LACP negotiation. (Default) LACP mode that places a port into an active negotiating state, in which the port initiates negotiations with other ports by sending LACP packets.
auto desirable passive active
Understanding Manual EtherChannel Configuration

Manually configured EtherChannel ports do not exchange EtherChannel protocol packets. A manually configured EtherChannel forms only when you configure all ports in the EtherChannel compatibly.
Understanding PAgP EtherChannel Configuration

PAgP supports the automatic creation of EtherChannels by exchanging PAgP packets between LAN ports. PAgP packets are exchanged only between ports in auto and desirable modes. The protocol learns the capabilities of LAN port groups dynamically and informs the other LAN ports. Once PAgP identifies correctly matched Ethernet links, it facilitates grouping the links into an EtherChannel. The EtherChannel is then added to the spanning tree as a single bridge port. Both the auto and desirable modes allow PAgP to negotiate between LAN ports to determine if they can form an EtherChannel, based on criteria such as port speed and trunking state. Layer 2 EtherChannels also use VLAN numbers. LAN ports can form an EtherChannel when they are in different PAgP modes if the modes are compatible. For example:

A LAN port in desirable mode can form an EtherChannel successfully with another LAN port that is in desirable mode. A LAN port in desirable mode can form an EtherChannel with another LAN port in auto mode. A LAN port in auto mode cannot form an EtherChannel with another LAN port that is also in auto mode, because neither port will initiate negotiation.
12-3
Chapter 12 Understanding How EtherChannels Work
Understanding IEEE 802.3ad LACP EtherChannel Configuration

LACP supports the automatic creation of EtherChannels by exchanging LACP packets between LAN ports. LACP packets are exchanged only between ports in passive and active modes. The protocol learns the capabilities of LAN port groups dynamically and informs the other LAN ports. Once LACP identifies correctly matched Ethernet links, it facilitates grouping the links into an EtherChannel. The EtherChannel is then added to the spanning tree as a single bridge port. Both the passive and active modes allow LACP to negotiate between LAN ports to determine if they can form an EtherChannel, based on criteria such as port speed and trunking state. Layer 2 EtherChannels also use VLAN numbers. LAN ports can form an EtherChannel when they are in different LACP modes as long as the modes are compatible. For example:

A LAN port in active mode can form an EtherChannel successfully with another LAN port that is in active mode. A LAN port in active mode can form an EtherChannel with another LAN port in passive mode. A LAN port in passive mode cannot form an EtherChannel with another LAN port that is also in passive mode, because neither port will initiate negotiation. LACP system priorityYou must configure an LACP system priority on each switch running LACP. The system priority can be configured automatically or through the CLI (see the Configuring the LACP System Priority and System ID section on page 12-10). LACP uses the system priority with the switch MAC address to form the system ID and also during negotiation with other systems.
LACP uses the following parameters:
Note
The LACP system ID is the combination of the LACP system priority value and the MAC address of the switch.
LACP port priorityYou must configure an LACP port priority on each port configured to use LACP. The port priority can be configured automatically or through the CLI (see the Configuring Channel Groups section on page 12-8). LACP uses the port priority with the port number to form the port identifier. LACP uses the port priority to decide which ports should be put in standby mode when there is a hardware limitation that prevents all compatible ports from aggregating. LACP administrative keyLACP automatically configures an administrative key value equal to the channel group identification number on each port configured to use LACP. The administrative key defines the ability of a port to aggregate with other ports. A ports ability to aggregate with other ports is determined by these factors:
Port physical characteristics, such as data rate, duplex capability, and point-to-point or shared
medium
Configuration restrictions that you establish
On ports configured to use LACP, LACP tries to configure the maximum number of compatible ports in an EtherChannel, up to the maximum allowed by the hardware (eight ports). If LACP cannot aggregate all the ports that are compatible (for example, the remote system might have more restrictive hardware limitations), then all the ports that cannot be actively included in the channel are put in hot standby state and are used only if one of the channeled ports fails. You can configure an additional 8 standby ports (total of 16 ports associated with the EtherChannel).
12-4
OL-3999-08
Chapter 12
Configuring EtherChannels EtherChannel Feature Configuration Guidelines and Restrictions
Understanding Port Channel Interfaces

Each EtherChannel has a numbered port channel interface. With Release 12.2(18)SXE and later releases, you can configure a maximum of 128 port-channel interfaces, numbered from 1 to 256. With releases earlier than Release 12.2(18)SXE, you can configure a maximum of 64 port-channel interfaces, numbered from 1 to 256. The configuration that you apply to the port channel interface affects all LAN ports assigned to the port channel interface. After you configure an EtherChannel, the configuration that you apply to the port channel interface affects the EtherChannel; the configuration that you apply to the LAN ports affects only the LAN port where you apply the configuration. To change the parameters of all ports in an EtherChannel, apply the configuration commands to the port channel interface, for example, Spanning Tree Protocol (STP) commands or commands to configure a Layer 2 EtherChannel as a trunk.
Understanding Load Balancing

An EtherChannel balances the traffic load across the links in an EtherChannel by reducing part of the binary pattern formed from the addresses in the frame to a numerical value that selects one of the links in the channel. EtherChannel load balancing can use MAC addresses or IP addresses. EtherChannel load balancing can also use Layer 4 port numbers. EtherChannel load balancing can use either source or destination or both source and destination addresses or ports. The selected mode applies to all EtherChannels configured on the switch. EtherChannel load balancing can use MPLS Layer 2 information. Use the option that provides the balance criteria with the greatest variety in your configuration. For example, if the traffic on an EtherChannel is going only to a single MAC address and you use the destination MAC address as the basis of EtherChannel load balancing, the EtherChannel always chooses the same link in the EtherChannel; using source addresses or IP addresses might result in better load balancing.
EtherChannel Feature Configuration Guidelines and Restrictions

When EtherChannel interfaces are configured improperly, they are disabled automatically to avoid network loops and other problems. To avoid configuration problems, observe these guidelines and restrictions:

The commands in this chapter can be used on all LAN ports in Catalyst 6500 series switches, including the ports on the supervisor engine and a redundant supervisor engine. Release 12.2(17b)SXA and later releases provide support for more than 1 Gbps of traffic per EtherChannel on the WS-X6548-GE-TX and WS-X6548V-GE-TX switching modules. With Release 12.2(17a)SX and Release 12.2(17a)SX1, the WS-X6548-GE-TX and WS-X6548V-GE-TX fabric-enabled switching modules do not support more than 1 Gbps of traffic per EtherChannel. The WS-X6148-GE-TX and WS-X6148V-GE-TX switching modules do not support more than 1 Gbps of traffic per EtherChannel.
12-5
Chapter 12 EtherChannel Feature Configuration Guidelines and Restrictions
When you add a member port that does not support ISL trunking to an EtherChannel, Cisco IOS software automatically adds a switchport trunk encapsulation dot1q command to the port-channel interface to prevent configuration of the EtherChannel as an ISL trunk. The switchport trunk encapsulation dot1q command is inactive when the EtherChannel is not a trunk. All Ethernet LAN ports on all modules, including those on a redundant supervisor engine, support EtherChannels (maximum of eight LAN ports) with no requirement that the LAN ports be physically contiguous or on the same module. Configure all LAN ports in an EtherChannel to use the same EtherChannel protocol; you cannot run two EtherChannel protocols in one EtherChannel. Configure all LAN ports in an EtherChannel to operate at the same speed and in the same duplex mode. LACP does not support half-duplex. Half-duplex ports in an LACP EtherChannel are put in the suspended state. Enter no shutdown commands for all the LAN ports in an EtherChannel. If you shut down a LAN port in an EtherChannel, it is treated as a link failure and its traffic is transferred to one of the remaining ports in the EtherChannel. An EtherChannel will not form if one of the LAN ports is a Switched Port Analyzer (SPAN) destination port. For Layer 3 EtherChannels, assign Layer 3 addresses to the port channel logical interface, not to the LAN ports in the channel. For Layer 2 EtherChannels:
Assign all LAN ports in the EtherChannel to the same VLAN or configure them as trunks. If you configure an EtherChannel from trunking LAN ports, verify that the trunking mode is the
same on all the trunks. LAN ports in an EtherChannel with different trunk modes can operate unpredictably.
An EtherChannel supports the same allowed range of VLANs on all the LAN ports in a trunking
Layer 2 EtherChannel. If the allowed range of VLANs is not the same, the LAN ports do not form an EtherChannel.
LAN ports with different STP port path costs can form an EtherChannel as long they are
compatibly configured with each other. If you set different STP port path costs, the LAN ports are not incompatible for the formation of an EtherChannel.
An EtherChannel will not form if protocol filtering is set differently on the LAN ports. Configure static MAC addresses on the EtherChannel only and not on physical member ports
of the EtherChannel.
After you configure an EtherChannel, the configuration that you apply to the port channel interface affects the EtherChannel. The configuration that you apply to the LAN ports affects only the LAN port where you apply the configuration. When QoS is enabled, enter the no mls qos channel-consistency port-channel interface command to support EtherChannels that have ports with and without strict-priority queues.
Caution
Serious traffic problems can result from mixing manual mode with PAgP or LACP modes, or with a port with no EtherChannel configured. For example, if a port configured in on mode is connected to another port configured in desirable mode, or to a port not configured for EtherChannel, a bridge loop is created and a broadcast storm can occur. If one end uses the on mode, the other end must also.
12-6
OL-3999-08
Chapter 12
Configuring EtherChannels Configuring EtherChannels
Serious traffic problems can result if an EtherChannel forms from ports that pass data through the switch in significantly different ways. For example, ports on modules with and without DFCs, or when enabled with the no mls qos channel-consistency port-channel interface command, ports that have significantly different QoS port parameters (buffers sizes and queue types). Be prepared to disable such EtherChannels.
These sections describe how to configure EtherChannels:

Configuring Port Channel Logical Interfaces for Layer 3 EtherChannels, page 12-7 Configuring Channel Groups, page 12-8 Configuring EtherChannel Load Balancing, page 12-11 Configuring the EtherChannel Min-Links Feature, page 12-12
Note
Make sure that the LAN ports are configured correctly (see the EtherChannel Feature Configuration Guidelines and Restrictions section on page 12-5).
Configuring Port Channel Logical Interfaces for Layer 3 EtherChannels

Note
When configuring Layer 2 EtherChannels, you cannot put Layer 2 LAN ports into manually created port channel logical interfaces. If you are configuring a Layer 2 EtherChannel, do not perform the procedures in this section (see the Configuring Channel Groups section on page 12-8). When configuring Layer 3 EtherChannels, you must manually create the port channel logical interface as described in this section, and then put the Layer 3 LAN ports into the channel group (see the Configuring Channel Groups section on page 12-8). To move an IP address from a Layer 3 LAN port to an EtherChannel, you must delete the IP address from the Layer 3 LAN port before configuring it on the port channel logical interface.
To create a port channel interface for a Layer 3 EtherChannel, perform this task: Command
Step 1
Router(config)# interface port-channel group_number Router(config)# no interface port-channel group_number
Purpose Creates the port channel interface. Deletes the port channel interface. Assigns an IP address and subnet mask to the EtherChannel. Exits configuration mode. Verifies the configuration.
Router(config-if)# ip address ip_address mask
Router(config-if)# end Router# show running-config interface port-channel group_number
12-7
Chapter 12 Configuring EtherChannels
With Release 12.2(18)SXE and later releases, the group_number can be 1 through 256, up to a maximum of 128 port-channel interfaces. With releases earlier than Release 12.2(18)SXE, the group_number can be 1 through 256, up to a maximum of 64 port-channel interfaces. This example shows how to create port channel interface 1:
Router# configure terminal Router(config)# interface port-channel 1 Router(config-if)# ip address 172.32.52.10 255.255.255.0 Router(config-if)# end
This example shows how to verify the configuration of port channel interface 1:
Router# show running-config interface port-channel 1 Building configuration... Current configuration: ! interface Port-channel1 ip address 172.32.52.10 255.255.255.0 no ip directed-broadcast end Router#
Configuring Channel Groups

Note
When configuring Layer 3 EtherChannels, you must manually create the port channel logical interface first (see the Configuring Port Channel Logical Interfaces for Layer 3 EtherChannels section on page 12-7), and then put the Layer 3 LAN ports into the channel group as described in this section. When configuring Layer 2 EtherChannels, configure the LAN ports with the channel-group command as described in this section, which automatically creates the port channel logical interface. You cannot put Layer 2 LAN ports into a manually created port channel interface. For Cisco IOS to create port channel interfaces for Layer 2 EtherChannels, the Layer 2 LAN ports must be connected and functioning.
To configure channel groups, perform this task for each LAN port: Command
1
Purpose
slot/port
Selects a LAN port to configure. Ensures that there is no IP address assigned to the LAN port. (Optional) On the selected LAN port, restricts the channel-group command to the EtherChannel protocol configured with the channel-protocol command. Removes the restriction.
Router(config-if)# no ip address
Router(config-if)# channel-protocol (lacp | pagp}
Router(config-if)# no channel-protocol
12-8
OL-3999-08
Chapter 12
Command
Step 4
Router(config-if)# channel-group group_number mode {active | auto | desirable | on | passive}
Purpose Configures the LAN port in a port channel and specifies the mode (see Table 12-1 on page 12-3). PAgP supports only the auto and desirable modes. LACP supports only the active and passive modes. Removes the LAN port from the channel group. (Optional for LACP) Valid values are 1 through 65535. Higher numbers have lower priority. The default is 32768. Reverts to the default. Exits configuration mode.
1
Router(config-if)# no channel-group
Step 5
Router(config-if)# lacp port-priority priority_value Router(config-if)# no lacp port-priority
Step 6 Step 7
Router(config-if)# end Router# show running-config interface type slot/port Router# show interfaces type1 slot/port etherchannel 1.
Verifies the configuration.
This example shows how to configure Fast Ethernet ports 5/6 and 5/7 into port channel 2 with PAgP mode desirable:
Router# configure terminal Router(config)# interface range fastethernet 5/6 -7 Router(config-if)# channel-group 2 mode desirable Router(config-if)# end
Note
See the Configuring a Range of Interfaces section on page 9-4 for information about the range keyword. This example shows how to verify the configuration of port channel interface 2:
Router# show running-config interface port-channel 2 Building configuration... Current configuration: ! interface Port-channel2 no ip address switchport switchport access vlan 10 switchport mode access end Router#
This example shows how to verify the configuration of Fast Ethernet port 5/6:
Router# show running-config interface fastethernet 5/6 Building configuration... Current configuration: ! interface FastEthernet5/6 no ip address switchport switchport access vlan 10 switchport mode access channel-group 2 mode desirable end
12-9
Router# show interfaces fastethernet 5/6 etherchannel Port state = Down Not-in-Bndl Channel group = 12 Mode = Desirable-Sl Gcchange = 0 Port-channel = null GC = 0x00000000 Pseudo port-channel = Po1 2 Port index = 0 Load = 0x00 Protocol = PAgP Flags: S A d Timers: H S Device is sending Slow hello. Device is in Auto mode. PAgP is down. Hello timer is running. Switching timer is running. C - Device is in Consistent state. P - Device learns on physical port. Q - Quit timer is running. I - Interface timer is running.
Local information: Port Fa5/2 Flags State d U1/S1 Timers Hello Partner PAgP Interval Count Priority 1s 0 128 Learning Group Method Ifindex Any 0
Age of the port in the current state: 04d:18h:57m:19s
This example shows how to verify the configuration of port channel interface 2 after the LAN ports have been configured:
Router# show etherchannel 12 port-channel Port-channels in the group: ---------------------Port-channel: Po12 -----------Age of the Port-channel = 04d:18h:58m:50s Logical slot/port = 14/1 Number of ports = 0 GC = 0x00000000 HotStandBy port = null Port state = Port-channel Ag-Not-Inuse Protocol = PAgP Router#
Configuring the LACP System Priority and System ID

The LACP system ID is the combination of the LACP system priority value and the MAC address of the switch. To configure the LACP system priority and system ID, perform this task: Command
Step 1
Router(config)# lacp system-priority priority_value Router(config)# no lacp system-priority
Purpose (Optional for LACP) Valid values are 1 through 65535. Higher numbers have lower priority. The default is 32768. Reverts to the default. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show lacp sys-id
This example shows how to configure the LACP system priority:

Router# configure terminal Router(config)# lacp system-priority 23456 Router(config)# end
12-10
OL-3999-08
Chapter 12
Router(config)#

Router# show lacp sys-id 23456,0050.3e8d.6400 Router#
The system priority is displayed first, followed by the MAC address of the switch.
Configuring EtherChannel Load Balancing

To configure EtherChannel load balancing, perform this task: Command
Step 1
Router(config)# port-channel load-balance {src-mac | dst-mac | src-dst-mac | src-ip | dst-ip | src-dst-ip | src-port | dst-port | src-dst-port} Router(config)# no port-channel load-balance
Purpose Configures EtherChannel load balancing.
Reverts to default EtherChannel load balancing. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show etherchannel load-balance
The load-balancing keywords indicate the following information:

dst-ip Destination IP addresses dst-macDestination MAC addresses dst-portDestination Layer 4 port mplsLoad balancing for MPLS packets src-dst-ipSource and destination IP addresses src-dst-macSource and destination MAC addresses src-dst-portSource and destination Layer 4 port src-ipSource IP addresses src-macSource MAC addresses src-portSource Layer 4 port
This example shows how to configure EtherChannel to use source and destination IP addresses:
Router# configure terminal Router(config)# port-channel load-balance src-dst-ip Router(config)# end Router(config)#

Router# show etherchannel load-balance Source XOR Destination IP address Router#
12-11
Configuring the EtherChannel Min-Links Feature

Note
Release 12.2(18)SXF and later releases support the EtherChannel Min-Links feature. The EtherChannel Min-Links feature is supported on LACP EtherChannels. This feature allows you to configure the minimum number of member ports that must be in the link-up state and bundled in the EtherChannel for the port channel interface to transition to the link-up state. You can use the EtherChannel Min-Links feature to prevent low-bandwidth LACP EtherChannels from becoming active. This feature also causes LACP EtherChannels to become inactive if they have too few active member ports to supply your required minimum bandwidth. To configure the EtherChannel Min-Links feature, perform this task:
Command
Step 1 Step 2
Router(config)# interface port-channel group_number Router(config-if)# port-channel min-links number
Purpose Selects an LACP port channel interface. Configures the minimum number of member ports that must be in the link-up state and bundled in the EtherChannel for the port channel interface to transition to the link-up state. Reverts to the default number of active member ports (one). Exits configuration mode. Verifies the configuration.
Router(config-if)# no port-channel min-links
Step 3 Step 4
Router(config-if)# end Router# show running-config interface type1 slot/port Router# show interfaces type1 slot/port etherchannel
Note
Although the EtherChannel Min-Links feature works correctly when configured only on one end of an EtherChannel, for best results, configure the same number of minimum links on both ends of the EtherChannel. This example shows how to configure port channel interface 1 to be inactive if fewer than 2 member ports are active in the EtherChannel:
Router# configure terminal Router(config)# interface port-channel 1 Router(config-if)# port-channel min-links 2 Router(config-if)# end
Tip
12-12
OL-3999-08
C H A P T E R
13
Configuring VTP
This chapter describes how to configure the VLAN Trunking Protocol (VTP) on the Catalyst 6500 series switches.
Note

Understanding How VTP Works, page 13-1 VTP Default Configuration, page 13-5 VTP Configuration Guidelines and Restrictions, page 13-5 Configuring VTP, page 13-6
Tip
Understanding How VTP Works

VTP is a Layer 2 messaging protocol that maintains VLAN configuration consistency by managing the addition, deletion, and renaming of VLANs within a VTP domain. A VTP domain (also called a VLAN management domain) is made up of one or more network devices that share the same VTP domain name and that are interconnected with trunks. VTP minimizes misconfigurations and configuration inconsistencies that can result in a number of problems, such as duplicate VLAN names, incorrect VLAN-type specifications, and security violations. Before you create VLANs, you must decide whether to use VTP in your network. With VTP, you can make configuration changes centrally on one or more network devices and have those changes automatically communicated to all the other network devices in the network.
13-1
Chapter 13 Understanding How VTP Works
Configuring VTP
Note
For complete information on configuring VLANs, see Chapter 14, Configuring VLANs. These sections describe how VTP works:

Understanding the VTP Domain, page 13-2 Understanding VTP Modes, page 13-2 Understanding VTP Advertisements, page 13-3 Understanding VTP Version 2, page 13-3 Understanding VTP Pruning, page 13-4
Understanding the VTP Domain

A VTP domain (also called a VLAN management domain) is made up of one or more interconnected network devices that share the same VTP domain name. A network device can be configured to be in one and only one VTP domain. You make global VLAN configuration changes for the domain using either the command-line interface (CLI) or Simple Network Management Protocol (SNMP). By default, the Catalyst 6500 series switch is in VTP server mode and is in the no-management domain state until the switch receives an advertisement for a domain over a trunk link or you configure a management domain. If the switch receives a VTP advertisement over a trunk link, it inherits the management domain name and the VTP configuration revision number. The switch ignores advertisements with a different management domain name or an earlier configuration revision number. If you configure the switch as VTP transparent, you can create and modify VLANs but the changes affect only the individual switch. When you make a change to the VLAN configuration on a VTP server, the change is propagated to all network devices in the VTP domain. VTP advertisements are transmitted out all trunk connections. VTP maps VLANs dynamically across multiple LAN types with unique names and internal index associations. Mapping eliminates excessive device administration required from network administrators.
Understanding VTP Modes

You can configure a Catalyst 6500 series switch to operate in any one of these VTP modes:
ServerIn VTP server mode, you can create, modify, and delete VLANs and specify other configuration parameters (such as VTP version and VTP pruning) for the entire VTP domain. VTP servers advertise their VLAN configuration to other network devices in the same VTP domain and synchronize their VLAN configuration with other network devices based on advertisements received over trunk links. VTP server is the default mode. ClientVTP clients behave the same way as VTP servers, but you cannot create, change, or delete VLANs on a VTP client. TransparentVTP transparent network devices do not participate in VTP. A VTP transparent network device does not advertise its VLAN configuration and does not synchronize its VLAN configuration based on received advertisements. However, in VTP version 2, transparent network devices do forward VTP advertisements that they receive out their trunking LAN ports.
13-2
OL-3999-08
Chapter 13
Configuring VTP Understanding How VTP Works
Note
Catalyst 6500 series switches automatically change from VTP server mode to VTP client mode if the switch detects a failure while writing configuration to NVRAM. If this happens, the switch cannot be returned to VTP server mode until the NVRAM is functioning.
Understanding VTP Advertisements

Each network device in the VTP domain sends periodic advertisements out each trunking LAN port to a reserved multicast address. VTP advertisements are received by neighboring network devices, which update their VTP and VLAN configurations as necessary. The following global configuration information is distributed in VTP advertisements:

VLAN IDs (ISL and 802.1Q) Emulated LAN names (for ATM LANE) 802.10 SAID values (FDDI) VTP domain name VTP configuration revision number VLAN configuration, including maximum transmission unit (MTU) size for each VLAN Frame format
Understanding VTP Version 2

If you use VTP in your network, you must decide whether to use VTP version 1 or version 2.
Note
If you are using VTP in a Token Ring environment, you must use version 2. VTP version 2 supports the following features not supported in version 1:
Token Ring supportVTP version 2 supports Token Ring LAN switching and VLANs (Token Ring Bridge Relay Function [TrBRF] and Token Ring Concentrator Relay Function [TrCRF]). For more information about Token Ring VLANs, see the Understanding How VLANs Work section on page 14-1. Unrecognized Type-Length-Value (TLV) SupportA VTP server or client propagates configuration changes to its other trunks, even for TLVs it is not able to parse. The unrecognized TLV is saved in NVRAM. Version-Dependent Transparent ModeIn VTP version 1, a VTP transparent network device inspects VTP messages for the domain name and version, and forwards a message only if the version and domain name match. Because only one domain is supported in the supervisor engine software, VTP version 2 forwards VTP messages in transparent mode without checking the version. Consistency ChecksIn VTP version 2, VLAN consistency checks (such as VLAN names and values) are performed only when you enter new information through the CLI or SNMP. Consistency checks are not performed when new information is obtained from a VTP message, or when information is read from NVRAM. If the digest on a received VTP message is correct, its information is accepted without consistency checks.
13-3
Chapter 13 Understanding How VTP Works
Configuring VTP
Understanding VTP Pruning

VTP pruning enhances network bandwidth use by reducing unnecessary flooded traffic, such as broadcast, multicast, unknown, and flooded unicast packets. VTP pruning increases available bandwidth by restricting flooded traffic to those trunk links that the traffic must use to access the appropriate network devices. By default, VTP pruning is disabled. For VTP pruning to be effective, all devices in the management domain must support VTP pruning. On devices that do not support VTP pruning, you must manually configure the VLANs allowed on trunks. Figure 13-1 shows a switched network without VTP pruning enabled. Interface 1 on network Switch 1 and port 2 on Switch 4 are assigned to the Red VLAN. A broadcast is sent from the host connected to Switch 1. Switch 1 floods the broadcast, and every network device in the network receives it, even though Switches 3, 5, and 6 have no ports in the Red VLAN. You enable pruning globally on the Catalyst 6500 series switch (see the Enabling VTP Pruning section on page 13-7). You configure pruning on Layer 2 trunking LAN ports (see the Configuring a Layer 2 Switching Port as a Trunk section on page 10-8).
Figure 13-1 Flooding Traffic without VTP Pruning
Catalyst series Switch 4 Interface 2
Catalyst series Switch 5
Catalyst series Switch 2 Red VLAN
Interface 1
31074
Figure 13-2 shows the same switched network with VTP pruning enabled. The broadcast traffic from Switch 1 is not forwarded to Switches 3, 5, and 6 because traffic for the Red VLAN has been pruned on the links indicated (port 5 on Switch 2 and port 4 on Switch 4).
13-4
OL-3999-08
Chapter 13
Configuring VTP VTP Default Configuration
Figure 13-2 Flooding Traffic with VTP Pruning

Switch 4 Interface 2 Interface 4 Flooded traffic is pruned. Switch 2 Red VLAN Switch 5 Interface 5
Interface 1
31075
Switch 6
Switch 3
Switch 1
Enabling VTP pruning on a VTP server enables pruning for the entire management domain. VTP pruning takes effect several seconds after you enable it. By default, VLANs 2 through 1000 are pruning eligible. VTP pruning does not prune traffic from pruning-ineligible VLANs. VLAN 1 is always pruning ineligible; traffic from VLAN 1 cannot be pruned. To configure VTP pruning on a trunking LAN port, use the switchport trunk pruning vlan command (see the Configuring a Layer 2 Switching Port as a Trunk section on page 10-8). VTP pruning operates when a LAN port is trunking. You can set VLAN pruning eligibility when VTP pruning is enabled or disabled for the VTP domain, when any given VLAN exists or not, and when the LAN port is currently trunking or not.
VTP Default Configuration

Table 13-1 shows the default VTP configuration.
Table 13-1 VTP Default Configuration
Feature VTP domain name VTP mode VTP version 2 enable state VTP password VTP pruning
Default Value Null Server Version 2 is disabled None Disabled
VTP Configuration Guidelines and Restrictions

When implementing VTP in your network, follow these guidelines and restrictions:

Supervisor engine redundancy does not support nondefault VLAN data file names or locations. Do not enter the vtp file file_name command on a switch that has a redundant supervisor engine. Before installing a redundant supervisor engine, enter the no vtp file command to return to the default configuration.
13-5
Chapter 13 Configuring VTP
Configuring VTP
All network devices in a VTP domain must run the same VTP version. You must configure a password on each network device in the management domain when in secure mode.
Caution
If you configure a VTP password, the management domain will not function properly if you do not assign a management domain password to each network device in the domain.
A VTP version 2-capable network device can operate in the same VTP domain as a network device running VTP version 1 provided VTP version 2 is disabled on the VTP version 2-capable network device (VTP version 2 is disabled by default). Do not enable VTP version 2 on a network device unless all of the network devices in the same VTP domain are version 2-capable. When you enable VTP version 2 on a network device, all of the version 2-capable network devices in the domain enable VTP version 2. In a Token Ring environment, you must enable VTP version 2 for Token Ring VLAN switching to function properly. When you enable or disable VTP pruning on a VTP server, VTP pruning for the entire management domain is enabled or disabled. The pruning-eligibility configuration applies globally to all trunks on the switch. You cannot configure pruning-eligibility separately for each trunk. When you configure VLANs as pruning eligible or pruning ineligible, pruning eligibility for those VLANs is affected on that switch only, not on all network devices in the VTP domain. VTPv1 and VTPv2 do not propagate configuration information for extended-range VLANs (VLAN numbers 1006 to 4094). You must configure extended-range VLANs manually on each network device. If there is insufficient DRAM available for use by VTP, the VTP mode changes to transparent. Network devices in VTP transparent mode do not send VTP Join messages. On Catalyst 6500 series switches with trunk connections to network devices in VTP transparent mode, configure the VLANs that are used by the transparent-mode network devices or that need to be carried across trunks as pruning ineligible. For information about configuring prune eligibility, see the Configuring the List of Prune-Eligible VLANs section on page 10-11.
Configuring VTP
These sections describe how to configure VTP:

Configuring VTP Global Parameters, page 13-6 Configuring the VTP Mode, page 13-9 Displaying VTP Statistics, page 13-10
Configuring VTP Global Parameters

These sections describe configuring the VTP global parameters:

Configuring a VTP Password, page 13-7 Enabling VTP Pruning, page 13-7 Enabling VTP Version 2, page 13-8
13-6
OL-3999-08
Chapter 13
Configuring VTP Configuring VTP
Note
You can enter the VTP global parameters in either global configuration mode or in EXEC mode.
Configuring a VTP Password

To configure the VTP global parameters, perform this task: Command
Router(config)# vtp password password_string
Purpose Sets a password, which can be from 1 to 64 characters long, for the VTP domain. Clears the password.
Router(config)# no vtp password
This example shows one way to configure a VTP password in global configuration mode:
Router# configure terminal Router(config)# vtp password WATER Setting device VLAN database password to WATER. Router#
This example shows how to configure a VTP password in EXEC mode:

Router# vtp password WATER Setting device VLAN database password to WATER. Router#
Note
The password is not stored in the running-config file.
Enabling VTP Pruning

To enable VTP pruning in the management domain, perform this task: Command
Step 1
Router(config)# vtp pruning Router(config)# no vtp pruning
Purpose Enables VTP pruning in the management domain. Disables VTP pruning in the management domain. Verifies the configuration.
Step 2
Router# show vtp status
This example shows one way to enable VTP pruning in the management domain:
Router# configure terminal Router(config)# vtp pruning Pruning switched ON
This example shows how to enable VTP pruning in the management domain with any release:
Router# vtp pruning Pruning switched ON

Router# show vtp status | include Pruning VTP Pruning Mode: Enabled Router#
13-7
Configuring VTP
For information about configuring prune eligibility, see the Configuring the List of Prune-Eligible VLANs section on page 10-11.
Enabling VTP Version 2

VTP version 2 is disabled by default on VTP version 2-capable network devices. When you enable VTP version 2 on a network device, every VTP version 2-capable network device in the VTP domain enables version 2.
Caution
VTP version 1 and VTP version 2 are not interoperable on network devices in the same VTP domain. Every network device in the VTP domain must use the same VTP version. Do not enable VTP version 2 unless every network device in the VTP domain supports version 2.
Note
In a Token Ring environment, you must enable VTP version 2 for Token Ring VLAN switching to function properly on devices that support Token Ring interfaces. To enable VTP version 2, perform this task:
Command
Step 1
Router(config)# vtp version {1 | 2} Router(config)# no vtp version
Purpose Enables VTP version 2. Reverts to the default (VTP version 1). Verifies the configuration.
Step 2
Router# show vtp status
This example shows one way to enable VTP version 2:

Router# configure terminal Router(config)# vtp version 2 V2 mode enabled. Router(config)#
This example shows how to enable VTP version 2 with any release:
Router# vtp version 2 V2 mode enabled. Router#

Router# show vtp status | include V2 VTP V2 Mode: Enabled Router#
13-8
OL-3999-08
Chapter 13
Configuring the VTP Mode

To configure the VTP mode, perform this task: Command
Step 1
Router(config)# vtp mode {client | server | transparent} Router(config)# no vtp mode
Purpose Configures the VTP mode. Reverts to the default VTP mode (server). (Optional for server mode) Defines the VTP domain name, which can be up to 32 characters long. VTP server mode requires a domain name. If the switch has a trunk connection to a VTP domain, the switch learns the domain name from the VTP server in the domain.
Note
Step 2
Router(config)# vtp domain domain_name
You cannot clear the domain name.
Step 3 Step 4
Router(config)# end Router# show vtp status
Exits VLAN configuration mode. Verifies the configuration.
Note
In VTP transparent mode, the VLAN configuration is stored in the startup configuration file. This example shows how to configure the switch as a VTP server:
Router# configuration terminal Router(config)# vtp mode server Setting device to VTP SERVER mode. Router(config)# vtp domain Lab_Network Setting VTP domain name to Lab_Network Router(config)# end Router#

Router# show vtp status VTP Version : 2 Configuration Revision : 247 Maximum VLANs supported locally : 1005 Number of existing VLANs : 33 VTP Operating Mode : Server VTP Domain Name : Lab_Network VTP Pruning Mode : Enabled VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 digest : 0x45 0x52 0xB6 0xFD 0x63 0xC8 0x49 0x80 Configuration last modified by 0.0.0.0 at 8-12-99 15:04:49 Local updater ID is 172.20.52.34 on interface Gi1/1 (first interface found) Router#
This example shows how to configure the switch as a VTP client:

Router# configuration terminal Router(config)# vtp mode client Setting device to VTP CLIENT mode. Router(config)# exit Router#
13-9
Configuring VTP

Router# show vtp status VTP Version : 2 Configuration Revision : 247 Maximum VLANs supported locally : 1005 Number of existing VLANs : 33 VTP Operating Mode : Client VTP Domain Name : Lab_Network VTP Pruning Mode : Enabled VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 digest : 0x45 0x52 0xB6 0xFD 0x63 0xC8 0x49 0x80 Configuration last modified by 0.0.0.0 at 8-12-99 15:04:49 Router#
This example shows how to disable VTP on the switch:

Router# configuration terminal Router(config)# vtp mode transparent Setting device to VTP TRANSPARENT mode. Router(config)# end Router#

Router# show vtp status VTP Version : 2 Configuration Revision : 247 Maximum VLANs supported locally : 1005 Number of existing VLANs : 33 VTP Operating Mode : Transparent VTP Domain Name : Lab_Network VTP Pruning Mode : Enabled VTP V2 Mode : Disabled VTP Traps Generation : Disabled MD5 digest : 0x45 0x52 0xB6 0xFD 0x63 0xC8 0x49 0x80 Configuration last modified by 0.0.0.0 at 8-12-99 15:04:49 Router#
Displaying VTP Statistics

To display VTP statistics, including VTP advertisements sent and received and VTP errors, perform this task: Command
Router# show vtp counters
Purpose Displays VTP statistics.
This example shows how to display VTP statistics:

Router# show vtp counters VTP statistics: Summary advertisements received Subset advertisements received Request advertisements received Summary advertisements transmitted Subset advertisements transmitted Request advertisements transmitted Number of config revision errors
: : : : : : :
7 5 0 997 13 3 0
13-10
OL-3999-08
Chapter 13
Number of config digest errors Number of V1 summary errors VTP pruning statistics: Trunk
: 0 : 0
Summary advts received from non-pruning-capable device ---------------- ---------------- ---------------- --------------------------Fa5/8 43071 42766 5
Join Transmitted Join Received
Tip
13-11
Configuring VTP
13-12
OL-3999-08
C H A P T E R
14
Configuring VLANs
This chapter describes how to configure VLANs on the Catalyst 6500 series switches.
Note

Understanding How VLANs Work, page 14-1 VLAN Default Configuration, page 14-6 VLAN Configuration Guidelines and Restrictions, page 14-8 Configuring VLANs, page 14-9
Tip
Understanding How VLANs Work

The following sections describe how VLANs work:

VLAN Overview, page 14-2 VLAN Ranges, page 14-2 Configurable VLAN Parameters, page 14-3 Understanding Token Ring VLANs, page 14-3
14-1
Chapter 14 Understanding How VLANs Work
Configuring VLANs
VLAN Overview
A VLAN is a group of end stations with a common set of requirements, independent of physical location. VLANs have the same attributes as a physical LAN but allow you to group end stations even if they are not located physically on the same LAN segment. VLANs are usually associated with IP subnetworks. For example, all the end stations in a particular IP subnet belong to the same VLAN. Traffic between VLANs must be routed. LAN port VLAN membership is assigned manually on an port-by-port basis.
VLAN Ranges
Note
You must enable the extended system ID to use 4096 VLANs (see the Understanding the Bridge ID section on page 20-2). Catalyst 6500 series switches support 4096 VLANs in accordance with the IEEE 802.1Q standard. These VLANs are organized into several ranges; you use each range slightly differently. Some of these VLANs are propagated to other switches in the network when you use the VLAN Trunking Protocol (VTP). The extended-range VLANs are not propagated, so you must configure extended-range VLANs manually on each network device. Table 14-1 describes the VLAN ranges.
Table 14-1 VLAN Ranges
VLANs 0, 4095 1 21001
Range Reserved Normal Normal
Usage For system use only. You cannot see or use these VLANs. For Ethernet VLANs; you can create, use, and delete these VLANs. Cisco defaults for FDDI and Token Ring. You cannot delete VLANs 10021005. For Ethernet VLANs only.
Propagated by VTP Yes Yes No
Cisco default. You can use this VLAN but you cannot delete it. Yes
10021005 Normal 10064094 Extended
The following information applies to VLAN ranges:
Layer 3 LAN ports, WAN interfaces and subinterfaces, and some software features use internal VLANs in the extended range. You cannot use an extended range VLAN that has been allocated for internal use. To display the VLANs used internally, enter the show vlan internal usage command. With earlier releases, enter the show vlan internal usage and show cwan vlans commands. You can configure ascending internal VLAN allocation (from 1006 and up) or descending internal VLAN allocation (from 4094 and down). You must enable the extended system ID to use extended range VLANs (see the Understanding the Bridge ID section on page 20-2).
14-2
OL-3999-08
Chapter 14
Configuring VLANs Understanding How VLANs Work
Configurable VLAN Parameters

Note
Ethernet VLAN 1 uses only default values. Except for the VLAN name, Ethernet VLANs 1006 through 4094 use only default values. You can configure the VLAN name for Ethernet VLANs 1006 through 4094.
You can configure the following parameters for VLANs 2 through 1001:

VLAN name VLAN type (Ethernet, FDDI, FDDI network entity title [NET], TrBRF, or TrCRF) VLAN state (active or suspended) Security Association Identifier (SAID) Bridge identification number for TrBRF VLANs Ring number for FDDI and TrCRF VLANs Parent VLAN number for TrCRF VLANs Spanning Tree Protocol (STP) type for TrCRF VLANs
Understanding Token Ring VLANs

The following section describes the two Token Ring VLAN types supported on network devices running VTP version 2:

Token Ring TrBRF VLANs, page 14-3 Token Ring TrCRF VLANs, page 14-4
Note
Catalyst 6500 series switches do not support Inter-Switch Link (ISL)-encapsulated Token Ring frames. When a Catalyst 6500 series switch is configured as a VTP server, you can configure Token Ring VLANs from the switch.
Token Ring TrBRF VLANs

Token Ring Bridge Relay Function (TrBRF) VLANs interconnect multiple Token Ring Concentrator Relay Function (TrCRF) VLANs in a switched Token Ring network (see Figure 14-1). The TrBRF can be extended across a network devices interconnected via trunk links. The connection between the TrCRF and the TrBRF is referred to as a logical port.
14-3
Chapter 14 Understanding How VLANs Work
Configuring VLANs
Figure 14-1 Interconnected Token Ring TrBRF and TrCRF VLANs

SRB or SRT BRF
CRF SRS SRS SRS
Token Ring 001
Token Ring 001
Token Ring 011
Token Ring 002
Token Ring 002
Token Ring 002
For source routing, the Catalyst 6500 series switch appears as a single bridge between the logical rings. The TrBRF can function as a source-route bridge (SRB) or a source-route transparent (SRT) bridge running either the IBM or IEEE STP. If an SRB is used, you can define duplicate MAC addresses on different logical rings. The Token Ring software runs an instance of STP for each TrBRF VLAN and each TrCRF VLAN. For TrCRF VLANs, STP removes loops in the logical ring. For TrBRF VLANs, STP interacts with external bridges to remove loops from the bridge topology, similar to STP operation on Ethernet VLANs.
Caution
Certain parent TrBRF STP and TrCRF bridge mode configurations can place the logical ports (the connection between the TrBRF and the TrCRF) of the TrBRF in a blocked state. For more information, see the VLAN Configuration Guidelines and Restrictions section on page 14-8. To accommodate IBM System Network Architecture (SNA) traffic, you can use a combination of SRT and SRB modes. In a mixed mode, the TrBRF determines that some ports (logical ports connected to TrCRFs) operate in SRB mode while other ports operate in SRT mode
Token Ring TrCRF VLANs

Token Ring Concentrator Relay Function (TrCRF) VLANs define port groups with the same logical ring number. You can configure two types of TrCRFs in your network: undistributed and backup. TrCRFs typically are undistributed, which means each TrCRF is limited to the ports on a single network device. Multiple undistributed TrCRFs on the same or separate network devices can be associated with a single parent TrBRF (see Figure 14-2). The parent TrBRF acts as a multiport bridge, forwarding traffic between the undistributed TrCRFs.
Note
To pass data between rings located on separate network devices, you can associate the rings to the same TrBRF and configure the TrBRF for an SRB.
14-4
S6624
OL-3999-08
Chapter 14
Configuring VLANs Understanding How VLANs Work
Figure 14-2 Undistributed TrCRFs

Switch A ISL Switch B
TrBRF 3
S6813 S6812
TrCRF 400
TrCRF 350
TrCRF 200
By default, Token Ring ports are associated with the default TrCRF (VLAN 1003, trcrf-default), which has the default TrBRF (VLAN 1005, trbrf-default) as its parent. In this configuration, a distributed TrCRF is possible (see Figure 14-3), and traffic is passed between the default TrCRFs located on separate network devices if the network devices are connected through an ISL trunk.
Figure 14-3 Distributed TrCRF
TrBRF 2 TrCRF 300 TrCRF 300 TrCRF 300
Within a TrCRF, source-route switching forwards frames based on either MAC addresses or route descriptors. The entire VLAN can operate as a single ring, with frames switched between ports within a single TrCRF. You can specify the maximum hop count for All-Routes and Spanning Tree Explorer frames for each TrCRF. When you specify the maximum hop count, you limit the maximum number of hops an explorer is allowed to traverse. If a port determines that the explorer frame it is receiving has traversed more than the number of hops specified, it does not forward the frame. The TrCRF determines the number of hops an explorer has traversed by the number of bridge hops in the route information field. If the ISL connection between network devices fails, you can use a backup TrCRF to configure an alternate route for traffic between undistributed TrCRFs. Only one backup TrCRF for a TrBRF is allowed, and only one port per network device can belong to a backup TrCRF. If the ISL connection between the network devices fails, the port in the backup TrCRF on each affected network device automatically becomes active, rerouting traffic between the undistributed TrCRFs through the backup TrCRF. When the ISL connection is reestablished, all but one port in the backup TrCRF is disabled. Figure 14-4 illustrates the backup TrCRF.
14-5
Chapter 14 VLAN Default Configuration
Configuring VLANs
Figure 14-4 Backup TrCRF

TrBRF 1 TrCRF 600 Backup TrCRF 612 TrCRF 601
VLAN Default Configuration

Tables 14-2 through 14-6 show the default configurations for the different VLAN media types.
Table 14-2 Ethernet VLAN Defaults and Ranges
Parameter VLAN ID VLAN name
Default 1 default for VLAN 1 VLANvlan_ID for other Ethernet VLANs 10vlan_ID 1500 0 0 active
S6811
Range 14094
802.10 SAID MTU size Translational bridge 1 Translational bridge 2 VLAN state Pruning eligibility
100001104094 150018190 01005 01005 active, suspend
VLANs 21001 are pruning eligible; VLANs 10064094 are not pruning eligible.
Table 14-3 FDDI VLAN Defaults and Ranges
Parameter VLAN ID VLAN name 802.10 SAID MTU size Ring number Parent VLAN Translational bridge 1
Default 1002 fddi-default 101002 1500 0 0 0
Range 11005 14294967294 150018190 14095 01005 01005
14-6
OL-3999-08
Chapter 14
Configuring VLANs VLAN Default Configuration
Table 14-3 FDDI VLAN Defaults and Ranges (continued)
Parameter Translational bridge 2 VLAN state
Default 0 active
Range 01005 active, suspend
Table 14-4
Token Ring (TrCRF) VLAN Defaults and Ranges
Parameter VLAN ID VLAN name 802.10 SAID Ring Number MTU size Translational bridge 1 Translational bridge 2 VLAN state Bridge mode ARE max hops STE max hops Backup CRF
Default 1003 token-ring-default 101003 0 VTPv1 default 1500 VTPv2 default 4472 0 0 active srb 7 7 disabled
Range 11005 14294967294 14095 150018190 01005 01005 active, suspend srb, srt 013 013 disable; enable
Table 14-5 FDDI-Net VLAN Defaults and Ranges
Parameter VLAN ID VLAN name 802.10 SAID MTU size Bridge number STP type VLAN state
Default 1004 fddinet-default 101004 1500 1 ieee active
Range 11005 14294967294 150018190 015 auto, ibm, ieee active, suspend
Table 14-6 Token Ring (TrBRF) VLAN Defaults and Ranges
Parameter VLAN ID VLAN name 802.10 SAID
Default 1005 trnet-default 101005
Range 11005 14294967294
14-7
Chapter 14 VLAN Configuration Guidelines and Restrictions
Configuring VLANs
Table 14-6 Token Ring (TrBRF) VLAN Defaults and Ranges (continued)
Parameter MTU size Bridge number STP type VLAN state
Default VTPv1 1500; VTPv2 4472 1 ibm active
Range 150018190 015 auto, ibm, ieee active, suspend
VLAN Configuration Guidelines and Restrictions

When creating and modifying VLANs in your network, follow these guidelines and restrictions:

Supervisor engine redundancy does not support nondefault VLAN data file names or locations. Do not enter the vtp file file_name command on a switch that has a redundant supervisor engine. Before installing a redundant supervisor engine, enter the no vtp file command to return to the default configuration. RPR+ redundancy (see Chapter 8, Configuring RPR and RPR+ Supervisor Engine Redundancy) does not support a configuration entered in VLAN database mode. Use global configuration mode with RPR+ redundancy. You can configure extended-range VLANs only in global configuration mode. You cannot configure extended-range VLANs in VLAN database mode. See the VLAN Configuration Options section on page 14-9. Before you can create a VLAN, the Catalyst 6500 series switch must be in VTP server mode or VTP transparent mode. For information on configuring VTP, see Chapter 13, Configuring VTP. The VLAN configuration is stored in the vlan.dat file, which is stored in nonvolatile memory. You can cause inconsistency in the VLAN database if you manually delete the vlan.dat file. If you want to modify the VLAN configuration or VTP, use the commands described in this guide and in the Cisco IOS Master Command List, Release 12.2SX publication. To do a complete backup of your configuration, include the vlan.dat file in the backup. The Cisco IOS end command is not supported in VLAN database mode. You cannot enter Ctrl-Z to exit VLAN database mode. Catalyst 6500 series switches do not support Token Ring or FDDI media. The switch does not forward FDDI, FDDI-Net, TrCRF, or TrBRF traffic, but it can propagate the VLAN configuration through VTP. When a Catalyst 6500 series switch is configured as a VTP server, you can configure FDDI and Token Ring VLANs from the switch. You must configure a TrBRF before you configure the TrCRF (the parent TrBRF VLAN you specify must exist). In a Token Ring environment, the logical interfaces (the connection between the TrBRF and the TrCRF) of the TrBRF are placed in a blocked state if either of these conditions exists:
The TrBRF is running the IBM STP, and the TrCRF is in SRT mode. The TrBRF is running the IEEE STP, and the TrCRF is in SRB mode.
14-8
OL-3999-08
Chapter 14
Configuring VLANs Configuring VLANs
Configuring VLANs
These sections describe how to configure VLANs:

VLAN Configuration Options, page 14-9 Creating or Modifying an Ethernet VLAN, page 14-10 Assigning a Layer 2 LAN Interface to a VLAN, page 14-12 Configuring the Internal VLAN Allocation Policy, page 14-12 Configuring VLAN Translation, page 14-13 Mapping 802.1Q VLANs to ISL VLANs, page 14-16 Saving VLAN Information, page 14-17
Note
VLANs support a number of parameters that are not discussed in detail in this section. For complete information, refer to the Cisco IOS Master Command List, Release 12.2SX publication.
VLAN Configuration Options

These sections describe the VLAN configuration options:

VLAN Configuration in Global Configuration Mode, page 14-9 VLAN Configuration in VLAN Database Mode, page 14-10
VLAN Configuration in Global Configuration Mode

If the switch is in VTP server or transparent mode (see the Configuring VTP section on page 13-6), you can configure VLANs in global and config-vlan configuration modes. When you configure VLANs in global and config-vlan configuration modes, the VLAN configuration is saved in the vlan.dat file. To display the VLAN configuration, enter the show vlan command. If the switch is in VLAN transparent mode, the VLAN configuration is saved in the running-config file. Use the copy running-config startup-config command to save the VLAN configuration to the startup-config file. After you save the running configuration as the startup configuration, use the show running-config and show startup-config commands to display the VLAN configuration.
Note
When the switch boots, if the VTP domain name and VTP mode in the startup-config and vlan.dat files do not match, the switch uses the configuration in the vlan.dat file. You can configure extended-range VLANs only in global configuration mode. You cannot configure extended-range VLANs in VLAN database mode.
14-9
Chapter 14 Configuring VLANs
Configuring VLANs
VLAN Configuration in VLAN Database Mode

Note
VLAN database mode is supported in releases earlier than Release 12.2(18)SXD. You cannot configure extended-range VLANs in VLAN database mode. You can configure extended-range VLANs only in global configuration mode. RPR+ redundancy does not support configuration entered in VLAN database mode. Use global configuration mode with RPR+ redundancy.
If the switch is in VTP server or transparent mode, you can configure VLANs in the VLAN database mode. When you configure VLANs in VLAN database mode, the VLAN configuration is saved in the vlan.dat files. To display the VLAN configuration, enter the show vlan command. You use the interface configuration command mode to define the port membership mode and add and remove ports from a VLAN. The results of these commands are written to the running-config file, and you can display the file by entering the show running-config command.
Creating or Modifying an Ethernet VLAN

User-configured VLANs have unique IDs from 1 to 4094, except for reserved VLANs (see Table 14-1 on page 14-2). Enter the vlan command with an unused ID to create a VLAN. Enter the vlan command for an existing VLAN to modify the VLAN (you cannot modify an existing VLAN that is being used by a Layer 3 port or a software feature). See the VLAN Default Configuration section on page 14-6 for the list of default parameters that are assigned when you create a VLAN. If you do not specify the VLAN type with the media keyword, the VLAN is an Ethernet VLAN. To create or modify a VLAN, perform this task: Command
Step 1
Router# configure terminal
Purpose Enters VLAN configuration mode.
or
Router# vlan database
Step 2
Router(config)# vlan vlan_ID{[-vlan_ID]|[,vlan_ID]) Router(config-vlan)#
or
Router(vlan)# vlan vlan_ID Router(config)# no vlan vlan_ID Router(config-vlan)#
Creates or modifies an Ethernet VLAN, a range of Ethernet VLANs, or several Ethernet VLANs specified in a comma-separated list (do not enter space characters).
Deletes a VLAN.
or
Router(vlan)# no vlan vlan_ID
Step 3
Router(config-vlan)# end
or
Router(vlan)# exit
Updates the VLAN database and returns to privileged EXEC mode. Verifies the VLAN configuration.
Step 4
Router# show vlan [id | name] vlan
14-10
OL-3999-08
Chapter 14
When you create or modify an Ethernet VLAN, note the following information:

RPR+ redundancy does not support a configuration entered in VLAN database mode. Use global configuration mode with RPR+ redundancy. Because Layer 3 ports and some software features require internal VLANs allocated from 1006 and up, configure extended-range VLANs starting with 4094. You can configure extended-range VLANs only in global configuration mode. You cannot configure extended-range VLANs in VLAN database mode. Layer 3 ports and some software features use extended-range VLANs. If the VLAN you are trying to create or modify is being used by a Layer 3 port or a software feature, the switch displays a message and does not modify the VLAN configuration. You cannot delete the default VLANs for the different media types: Ethernet VLAN 1 and FDDI or Token Ring VLANs 1002 to 1005. When you delete a VLAN, any LAN ports configured as access ports assigned to that VLAN become inactive. The ports remain associated with the VLAN (and inactive) until you assign them to a new VLAN.
When deleting VLANs, note the following information:

This example shows how to create an Ethernet VLAN in global configuration mode and verify the configuration:
Router# configure terminal Router(config)# vlan 3 Router(config-vlan)# end Router# show vlan id 3 VLAN Name Status Ports ---- -------------------------------- --------- ------------------------------3 VLAN0003 active VLAN Type SAID MTU Parent RingNo BridgeNo Stp BrdgMode Trans1 Trans2 ---- ----- ---------- ----- ------ ------ -------- ---- -------- ------ -----3 enet 100003 1500 0 0 Primary Secondary Type Interfaces ------- --------- ----------------- ------------------------------------------
This example shows how to create an Ethernet VLAN in VLAN database mode:
Router# vlan database Router(vlan)# vlan 3 VLAN 3 added: Name: VLAN0003 Router(vlan)# exit APPLY completed. Exiting....

Router# show vlan name VLAN0003 VLAN Name Status Ports ---- -------------------------------- --------- --------------------3 VLAN0003 active VLAN Type SAID MTU Parent RingNo BridgeNo Stp Trans1 Trans2 ---- ----- ---------- ----- ------ ------ -------- ---- ------ -----3 enet 100003 1500 0 0 Router#
14-11
Configuring VLANs
Assigning a Layer 2 LAN Interface to a VLAN

A VLAN created in a management domain remains unused until you assign one or more LAN ports to the VLAN.
Note
Make sure you assign LAN ports to a VLAN of the appropriate type. Assign Ethernet ports to Ethernet-type VLANs. To assign one or more LAN ports to a VLAN, complete the procedures in the Configuring LAN Interfaces for Layer 2 Switching section on page 10-6.
Configuring the Internal VLAN Allocation Policy

For more information about VLAN allocation, see the VLAN Ranges section on page 14-2.
Note
The internal VLAN allocation policy is applied only following a reload. To configure the internal VLAN allocation policy, perform this task:
Command
Step 1
Router(config)# vlan internal allocation policy {ascending | descending} Router(config)# no vlan internal allocation policy
Purpose Configures the internal VLAN allocation policy. Returns to the default (ascending). Exits configuration mode. Applies the new internal VLAN allocation policy.
Step 2 Step 3
Router(config)# end Router# reload
Caution
You do not need to enter the reload command immediately. Enter the reload command during a planned maintenance window.
When you configure the internal VLAN allocation policy, note the following information:

Enter the ascending keyword to allocate internal VLANs from 1006 and up. Enter the descending keyword to allocate internal VLAN from 4094 and down.
This example shows how to configure descending as the internal VLAN allocation policy:
Router# configure terminal Router(config)# vlan internal allocation policy descending
14-12
OL-3999-08
Chapter 14
Configuring VLAN Translation

On trunk ports, you can translate one VLAN number to another VLAN number, which transfers all traffic received in one VLAN to the other VLAN. These sections describe VLAN translation:

VLAN Translation Guidelines and Restrictions, page 14-13 Configuring VLAN Translation on a Trunk Port, page 14-15 Enabling VLAN Translation on Other Ports in a Port Group, page 14-15
Note
Release 12.2(17b)SXA and later releases support VLAN translation. To avoid spanning tree loops, be careful not to misconfigure the VLAN translation feature.
VLAN Translation Guidelines and Restrictions

When translating VLANs, follow these guidelines and restrictions:

A VLAN translation configuration is inactive if it is applied to ports that are not Layer 2 trunks. Do not configure translation of ingress native VLAN traffic on an 802.1Q trunk. Because 802.1Q native VLAN traffic is untagged, it cannot be recognized for translation. You can translate traffic from other VLANs to the native VLAN of an 802.1Q trunk. Do not remove the VLAN to which you are translating from the trunk. The VLAN translation configuration applies to all ports in a port group. VLAN translation is disabled by default on all ports in a port group. Enable VLAN translation on ports as needed. The following table lists:
The modules that support VLAN translation The port groups to which VLAN translation configuration applies The number of VLAN translations supported by the port groups The trunk types supported by the modules
Note
LAN ports on OSMs support VLAN translation. LAN ports on OSMs are in a single port group.
Product Number WS-SUP720-3BXL WS-SUP720-3B WS-SUP720 WS-SUP32-10GE
Port Ranges Number of Number of per Ports Port Groups Port Group 2 1 12
Translations per VLAN Translation Port Group Trunk-Type Support 32 802.1Q
1, 23
16
ISL 802.1Q
14-13
Configuring VLANs
Product Number WS-SUP32-GE
Port Ranges Number of Number of per Ports Port Groups Port Group 9 1 1 4 1 2 2 2 2 4 19 12 1 port in each group 1 port in 1 group 112 1324 18 916 18 916 18 916 112 1324 2536 3748 18 916 124 148 148
Translations per VLAN Translation Port Group Trunk-Type Support 16 32 128 32 128 32 32 32 128 ISL 802.1Q 802.1Q ISL 802.1Q 802.1Q ISL 802.1Q 802.1Q 802.1Q 802.1Q ISL 802.1Q
WS-X6K-S2U-MSFC2 2 WS-X6K-S2-MSFC2 WS-X6704-10GE WS-X6502-10GE WS-X6724-SFP WS-X6816-GBIC WS-X6516A-GBIC WS-X6516-GBIC WS-X6748-GE-TX 4 1 24 16 16 16 48
WS-X6516-GE-TX
16
2 1 1 1
32 32 32 32
802.1Q ISL 802.1Q ISL 802.1Q ISL 802.1Q
WS-X6524-100FX-MM 24 WS-X6548-RJ-45 WS-X6548-RJ-21 48 48
Note
To configure a port as a trunk, see the Configuring a Layer 2 Switching Port as a Trunk section on page 10-8.
14-14
OL-3999-08
Chapter 14
Configuring VLAN Translation on a Trunk Port

To translate VLANs on a trunk port, perform this task: Command
1
Purpose
slot/port
Selects the Layer 2 trunk port to configure. Enables VLAN translation. Translates a VLAN to another VLAN. The valid range is 1 to 4094. When you configure a VLAN mapping from the original VLAN to the translated VLAN on a port, traffic arriving on the original VLAN gets mapped or translated to the translated VLAN at the ingress of the switch port, and the traffic internally tagged with the translated VLAN gets mapped to the original VLAN before leaving the switch port. This method of VLAN mapping is a two-way mapping.
Router(config-if)# switchport vlan mapping enable Router(config-if)# switchport vlan mapping original_vlan_ID translated_vlan_ID
Router(config-if)# no switchport vlan mapping {all | original_vlan_ID translated_vlan_ID}
Deletes the mapping. Exits configuration mode. Verifies the VLAN mapping.
Step 4 Step 5
Router(config-if)# end Router# show interface type1 slot/port vlan mapping 1.
This example shows how to map VLAN 1649 to VLAN 755 Gigabit Ethernet port 5/2:
Router# configure terminal Router(config)# interface gigabitethernet 5/2 Router(config-if)# switchport vlan mapping 1649 755 Router(config-if)# end Router#

Router# show interface gigabitethernet 5/2 vlan mapping State: enabled Original VLAN Translated VLAN ------------- --------------1649 755
Enabling VLAN Translation on Other Ports in a Port Group

To enable VLAN translation on other ports in a port group, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# switchport vlan mapping enable Router(config-if)# no switchport vlan mapping enable
Purpose Selects the LAN port to configure. Enables VLAN translation. Disables VLAN translation.
14-15
Configuring VLANs
Command
Step 3 Step 4
Router(config-if)# end Router# show interface type1 slot/port vlan mapping 1.
Purpose Exits configuration mode. Verifies the VLAN mapping.
This example shows how to enable VLAN translation on a port:

Router# configure terminal Router(config)# interface gigabitethernet 5/2 Router(config-if)# switchport vlan mapping enable Router(config-if)# end Router#
Mapping 802.1Q VLANs to ISL VLANs

The valid range of user-configurable ISL VLANs is 1 through 1001 and 1006 through 4094. The valid range of VLANs specified in the IEEE 802.1Q standard is 1 to 4094. You can map 802.1Q VLAN numbers to ISL VLAN numbers. 802.1Q VLANs in the range 1 through 1001 and 1006 through 4094 are automatically mapped to the corresponding ISL VLAN. 802.1Q VLAN numbers corresponding to reserved VLAN numbers must be mapped to an ISL VLAN in order to be recognized and forwarded by Cisco network devices. These restrictions apply when mapping 802.1Q VLANs to ISL VLANs:

You can configure up to eight 802.1Q-to-ISL VLAN mappings on the Catalyst 6500 series switch. You can only map 802.1Q VLANs to Ethernet-type ISL VLANs. Do not enter the native VLAN of any 802.1Q trunk in the mapping table. When you map an 802.1Q VLAN to an ISL VLAN, traffic on the 802.1Q VLAN corresponding to the mapped ISL VLAN is blocked. For example, if you map 802.1Q VLAN 1007 to ISL VLAN 200, traffic on 802.1Q VLAN 200 is blocked. VLAN mappings are local to each Catalyst 6500 series switch. Make sure you configure the same VLAN mappings on all appropriate network devices.
To map an 802.1Q VLAN to an ISL VLAN, perform this task: Command

Step 1
Router(config)# vlan mapping dot1q dot1q_vlan_ID isl isl_vlan_ID
Purpose Maps an 802.1Q VLAN to an ISL Ethernet VLAN. The valid range for dot1q_vlan_ID is 1001 to 4094. The valid range for isl_vlan_ID is the same. Deletes the mapping. Exits configuration mode. Verifies the VLAN mapping.
Router(config)# no vlan mapping dot1q {all | dot1q_vlan_ID}
Step 2 Step 3
Router(config)# end Router# show vlan
14-16
OL-3999-08
Chapter 14
This example shows how to map 802.1Q VLAN 1003 to ISL VLAN 200:
Router# configure terminal Router(config)# vlan mapping dot1q 1003 isl 200 Router(config)# end Router#

Router# show vlan <...output truncated...> 802.1Q Trunk Remapped VLANs: 802.1Q VLAN ISL VLAN --------------------1003 200
Saving VLAN Information

The VLAN database is stored in the vlan.dat file. You should create a backup of the vlan.dat file in addition to backing up the running-config and startup-config files. If you replace the existing supervisor engine, copy the startup-config file as well as the vlan.dat file to restore the system. The vlan.dat file is read on bootup and you will have to reload the supervisor engine after uploading the file. To view the file location, use the dir vlan.dat command. To copy the file (binary), use the copy vlan.dat tftp command.
Tip
14-17
Configuring VLANs
14-18
OL-3999-08
C H A P T E R
15
Configuring Private VLANs

This chapter describes how to configure private VLANs on the Catalyst 6500 series switches.
Note

Understanding How Private VLANs Work, page 15-1 Private VLAN Configuration Guidelines and Restrictions, page 15-6 Configuring Private VLANs, page 15-11 Monitoring Private VLANs, page 15-17
Tip
Understanding How Private VLANs Work

These sections describe how private VLANs work:

Private VLAN Domains, page 15-2 Private VLAN Ports, page 15-3 Primary, Isolated, and Community VLANs, page 15-3 Private VLAN Port Isolation, page 15-4 IP Addressing Scheme with Private VLANs, page 15-4 Private VLANs Across Multiple Switches, page 15-5 Private VLAN Interaction with Other Features, page 15-5
15-1
Chapter 15 Understanding How Private VLANs Work
Private VLAN Domains

The private VLAN feature addresses two problems that service providers encounter when using VLANs:

The switch supports up to 4096 VLANs. If a service provider assigns one VLAN per customer, the number of customers that service provider can support is limited. To enable IP routing, each VLAN is assigned a subnet address space or a block of addresses, which can result in wasting the unused IP addresses and creating IP address management problems.
Using private VLANs solves the scalability problem and provides IP address management benefits for service providers and Layer 2 security for customers. The private VLAN feature partitions the Layer 2 broadcast domain of a VLAN into subdomains. A subdomain is represented by a pair of private VLANs: a primary VLAN and a secondary VLAN. A private VLAN domain can have multiple private VLAN pairs, one pair for each subdomain. All VLAN pairs in a private VLAN domain share the same primary VLAN. The secondary VLAN ID differentiates one subdomain from another (see Figure 15-1).
Figure 15-1 Private VLAN Domain
Private VLAN domain Subdomain
Primary VLAN
Subdomain
Secondary community VLAN
Secondary isolated VLAN
A private VLAN domain has only one primary VLAN. Every port in a private VLAN domain is a member of the primary VLAN. In other words, the primary VLAN is the entire private VLAN domain. Secondary VLANs provide Layer 2 isolation between ports within the same private VLAN domain. There are two types of secondary VLANs:

Isolated VLANsPorts within an isolated VLAN cannot communicate with each other at the Layer 2 level. Community VLANsPorts within a community VLAN can communicate with each other but cannot communicate with ports in other communities at the Layer 2 level.
15-2
116083
OL-3999-08
Chapter 15
Configuring Private VLANs Understanding How Private VLANs Work
Private VLAN Ports

There are three types of private VLAN ports:
PromiscuousA promiscuous port belongs to the primary VLAN and can communicate with all interfaces, including the community and isolated host ports that belong to the secondary VLANs that are associated with the primary VLAN. IsolatedAn isolated port is a host port that belongs to an isolated secondary VLAN. This port has complete Layer 2 isolation from other ports within the same private VLAN domain, except for the promiscuous ports. Private VLANs block all traffic to isolated ports except traffic from promiscuous ports. Traffic received from an isolated port is forwarded only to promiscuous ports. CommunityA community port is a host port that belongs to a community secondary VLAN. Community ports communicate with other ports in the same community VLAN and with promiscuous ports. These interfaces are isolated at Layer 2 from all other interfaces in other communities and from isolated ports within their private VLAN domain.
Note
Because trunks can support the VLANs carrying traffic between isolated, community, and promiscuous ports, isolated and community port traffic might enter or leave the switch through a trunk interface.
Primary, Isolated, and Community VLANs

Primary VLANs and the two types of secondary VLANs, isolated VLANs and community VLANs, have these characteristics:

Primary VLAN The primary VLAN carries unidirectional traffic downstream from the promiscuous ports to the (isolated and community) host ports and to other promiscuous ports. Isolated VLAN A private VLAN domain has only one isolated VLAN. An isolated VLAN is a secondary VLAN that carries unidirectional traffic upstream from the hosts toward the promiscuous ports and the gateway. Community VLANA community VLAN is a secondary VLAN that carries upstream traffic from the community ports to the promiscuous port gateways and to other host ports in the same community. You can configure multiple community VLANs in a private VLAN domain.
A promiscuous port can serve only one primary VLAN, one isolated VLAN, and multiple community VLANs. Layer 3 gateways are connected typically to the switch through a promiscuous port. With a promiscuous port, you can connect a wide range of devices as access points to a private VLAN. For example, you can use a promiscuous port to monitor or back up all the private VLAN servers from an administration workstation. In a switched environment, you can assign an individual private VLAN and associated IP subnet to each individual or common group of end stations. The end stations need to communicate only with a default gateway to communicate outside the private VLAN.
15-3
Chapter 15 Understanding How Private VLANs Work
Private VLAN Port Isolation

You can use private VLANs to control access to end stations in these ways:
Configure selected interfaces connected to end stations as isolated ports to prevent any communication at Layer 2. For example, if the end stations are servers, this configuration prevents Layer 2 communication between the servers. Configure interfaces connected to default gateways and selected end stations (for example, backup servers) as promiscuous ports to allow all end stations access to a default gateway.
You can extend private VLANs across multiple devices by trunking the primary, isolated, and community VLANs to other devices that support private VLANs. To maintain the security of your private VLAN configuration and to avoid other use of the VLANs configured as private VLANs, configure private VLANs on all intermediate devices, including devices that have no private VLAN ports.
IP Addressing Scheme with Private VLANs

When you assign a separate VLAN to each customer, an inefficient IP addressing scheme is created as follows:

Assigning a block of addresses to a customer VLAN can result in unused IP addresses. If the number of devices in the VLAN increases, the number of assigned addresses might not be large enough to accommodate them.
These problems are reduced by using private VLANs, where all members in the private VLAN share a common address space, which is allocated to the primary VLAN. Hosts are connected to secondary VLANs, and the DHCP server assigns them IP addresses from the block of addresses allocated to the primary VLAN. Subsequent IP addresses can be assigned to customer devices in different secondary VLANs, but in the same primary VLAN. When new devices are added, the DHCP server assigns them the next available address from a large pool of subnet addresses.
15-4
OL-3999-08
Chapter 15
Configuring Private VLANs Understanding How Private VLANs Work
Private VLANs Across Multiple Switches

As with regular VLANs, private VLANs can span multiple switches. A trunk port carries the primary VLAN and secondary VLANs to a neighboring switch. The trunk port deals with the private VLAN as any other VLAN. A feature of private VLANs across multiple switches is that traffic from an isolated port in switch A does not reach an isolated port on Switch B. (See Figure 15-2.)
Figure 15-2 Private VLANs Across Switches
Trunk ports
VLAN 100 Switch A Switch B
VLAN 100
VLAN 201
VLAN 202
VLAN 201 Carries VLAN 100, 201, and 202 traffic
VLAN 202
116084
VLAN 100 = Primary VLAN VLAN 201 = Secondary isolated VLAN VLAN 202 = Secondary community VLAN
Because VTP does not support private VLANs, you must manually configure private VLANs on all switches in the Layer 2 network. If you do not configure the primary and secondary VLAN association in some switches in the network, the Layer 2 databases in these switches are not merged. This situation can result in unnecessary flooding of private VLAN traffic on those switches.
Private VLAN Interaction with Other Features

These sections describe how private VLANs interact with some other features:

Private VLANs and Unicast, Broadcast, and Multicast Traffic, page 15-6 Private VLANs and SVIs, page 15-6
See also the Private VLAN Configuration Guidelines and Restrictions section on page 15-6.
15-5
Chapter 15 Private VLAN Configuration Guidelines and Restrictions
Private VLANs and Unicast, Broadcast, and Multicast Traffic

In regular VLANs, devices in the same VLAN can communicate with each other at the Layer 2 level, but devices connected to interfaces in different VLANs must communicate at the Layer 3 level. In private VLANs, the promiscuous ports are members of the primary VLAN, while the host ports belong to secondary VLANs. Because the secondary VLAN is associated to the primary VLAN, members of the these VLANs can communicate with each other at the Layer 2 level. In a regular VLAN, broadcasts are forwarded to all ports in that VLAN. Private VLAN broadcast forwarding depends on the port sending the broadcast:

An isolated port sends a broadcast only to the promiscuous ports or trunk ports. A community port sends a broadcast to all promiscuous ports, trunk ports, and ports in the same community VLAN. A promiscuous port sends a broadcast to all ports in the private VLAN (other promiscuous ports, trunk ports, isolated ports, and community ports).
Multicast traffic is routed or bridged across private VLAN boundaries and within a single community VLAN. Multicast traffic is not forwarded between ports in the same isolated VLAN or between ports in different secondary VLANs.
Private VLANs and SVIs

A switch virtual interface (SVI) is the Layer 3 interface of a Layer 2 VLAN. Layer 3 devices communicate with a private VLAN only through the primary VLAN and not through secondary VLANs. Configure Layer 3 VLAN SVIs only for primary VLANs. Do not configure Layer 3 VLAN interfaces for secondary VLANs. SVIs for secondary VLANs are inactive while the VLAN is configured as a secondary VLAN.

If you try to configure a VLAN with an active SVI as a secondary VLAN, the configuration is not allowed until you disable the SVI. If you try to create an SVI on a VLAN that is configured as a secondary VLAN, and the secondary VLAN is already mapped at Layer 3, the SVI is not created, and an error is returned. If the SVI is not mapped at Layer 3, the SVI is created, but it is automatically shut down.
When the primary VLAN is associated with and mapped to the secondary VLAN, any configuration on the primary VLAN is propagated to the secondary VLAN SVIs. For example, if you assign an IP subnet to the primary VLAN SVI, this subnet is the IP subnet address of the entire private VLAN.
Private VLAN Configuration Guidelines and Restrictions

The guidelines for configuring private VLANs are described in the following sections:

Secondary and Primary VLAN Configuration, page 15-7 Private VLAN Port Configuration, page 15-9 Limitations with Other Features, page 15-9
15-6
OL-3999-08
Chapter 15
Configuring Private VLANs Private VLAN Configuration Guidelines and Restrictions
Secondary and Primary VLAN Configuration

When configuring private VLANs consider these guidelines:

After you configure a private VLAN and set VTP to transparent mode, you are not allowed to change the VTP mode to client or server. For information about VTP, see Chapter 13, Configuring VTP. You must use VLAN configuration (config-vlan) mode to configure private VLANs. You cannot configure private VLANs in VLAN database configuration mode. For more information about VLAN configuration, see VLAN Configuration Options section on page 14-9. After you have configured private VLANs, use the copy running-config startup config privileged EXEC command to save the VTP transparent mode configuration and private VLAN configuration in the startup-config file. If the switch resets it must default to VTP transparent mode to support private VLANs. VTP does not propagate a private VLAN configuration. You must configure private VLANs on each device where you want private VLAN ports. You cannot configure VLAN 1 or VLANs 1002 to 1005 as primary or secondary VLANs. Extended VLANs (VLAN IDs 1006 to 4094) can belong to private VLANs. Only Ethernet VLANs can be private VLANs. A primary VLAN can have one isolated VLAN and multiple community VLANs associated with it. An isolated or community VLAN can have only one primary VLAN associated with it. When a secondary VLAN is associated with the primary VLAN, the STP parameters of the primary VLAN, such as bridge priorities, are propagated to the secondary VLAN. However, STP parameters do not necessarily propagate to other devices. You should manually check the STP configuration to ensure that the primary, isolated, and community VLANs spanning tree topologies match so that the VLANs can properly share the same forwarding database. If you enable MAC address reduction on the switch, we recommend that you enable MAC address reduction on all the devices in your network to ensure that the STP topologies of the private VLANs match. In a network where private VLANs are configured, if you enable MAC address reduction on some devices and disable it on others (mixed environment), use the default bridge priorities to make sure that the root bridge is common to the primary VLAN and to all its associated isolated and community VLANs. Be consistent with the ranges employed by the MAC address reduction feature regardless of whether it is enabled on the system. MAC address reduction allows only discrete levels and uses all intermediate values internally as a range. You should disable a root bridge with private VLANs and MAC address reduction, and configure the root bridge with any priority higher than the highest priority range used by any nonroot bridge. You cannot apply VACLs to secondary VLANs. (See Chapter 35, Configuring VLAN ACLs.) You can enable DHCP snooping on private VLANs. When you enable DHCP snooping on the primary VLAN, it is propagated to the secondary VLANs. If you configure DHCP on a secondary VLAN, the configuration does not take effect if the primary VLAN is already configured. We recommend that you prune the private VLANs from the trunks on devices that carry no traffic in the private VLANs. You can apply different quality of service (QoS) configurations to primary, isolated, and community VLANs. (See Chapter 41, Configuring PFC QoS.) When you configure private VLANs, sticky Address Resolution Protocol (ARP) is enabled by default, and ARP entries learned on Layer 3 private VLAN interfaces are sticky ARP entries. For security reasons, private VLAN port sticky ARP entries do not age out. For information about configuring sticky ARP, see the Configuring Sticky ARP section on page 36-35.
15-7
We recommend that you display and verify private VLAN interface ARP entries. Sticky ARP prevents MAC address spoofing by ensuring that ARP entries (IP address, MAC address, and source VLAN) do not age out. With Release 12.2(18)SXF and later releases, you can configure sticky ARP on a per-interface basis. For information about configuring sticky ARP, see the Configuring Sticky ARP section on page 36-35. The following guidelines and restrictions apply to private VLAN sticky ARP:
ARP entries learned on Layer 3 private VLAN interfaces are sticky ARP entries. Connecting a device with a different MAC address but with the same IP address generates a
message and the ARP entry is not created.

Because the private VLAN port sticky ARP entries do not age out, you must manually remove
private VLAN port ARP entries if a MAC address changes. You can add or remove private VLAN ARP entries manually as follows:
Router(config)# no arp 11.1.3.30 IP ARP:Deleting Sticky ARP entry 11.1.3.30 Router(config)# arp 11.1.3.30 0000.5403.2356 arpa IP ARP:Overwriting Sticky ARP entry 11.1.3.30, hw:00d0.bb09.266e by hw:0000.5403.2356
You can configure VLAN maps on primary and secondary VLANs. (See the Applying a VLAN Access Map section on page 35-8.) However, we recommend that you configure the same VLAN maps on private VLAN primary and secondary VLANs. When a frame is Layer 2 forwarded within a private VLAN, the same VLAN map is applied at the ingress side and at the egress side. When a frame is routed from inside a private VLAN to an external port, the private VLAN map is applied at the ingress side.
For frames going upstream from a host port to a promiscuous port, the VLAN map configured
on the secondary VLAN is applied.

For frames going downstream from a promiscuous port to a host port, the VLAN map
configured on the primary VLAN is applied. To filter out specific IP traffic for a private VLAN, you should apply the VLAN map to both the primary and secondary VLANs.

To apply Cisco IOS output ACLs to all outgoing private VLAN traffic, configure them on the Layer 3 VLAN interface of the primary VLAN. (See Chapter 33, Configuring Network Security.) Cisco IOS ACLs applied to the Layer 3 VLAN interface of a primary VLAN automatically apply to the associated isolated and community VLANs. Do not apply Cisco IOS ACLs to isolated or community VLANs. Cisco IOS ACL configuration applied to isolated and community VLANs is inactive while the VLANs are part of the private VLAN configuration. Although private VLANs provide host isolation at Layer 2, hosts can communicate with each other at Layer 3. Private VLANs support these Switched Port Analyzer (SPAN) features:
You can configure a private VLAN port as a SPAN source port. You can use VLAN-based SPAN (VSPAN) on primary, isolated, and community VLANs or use
SPAN on only one VLAN to separately monitor egress or ingress traffic.

For more information about SPAN, see Chapter 52, Configuring Local SPAN, RSPAN, and
ERSPAN.
15-8
OL-3999-08
Chapter 15
Configuring Private VLANs Private VLAN Configuration Guidelines and Restrictions
Private VLAN Port Configuration

When configuring private VLAN ports follow these guidelines:
Use only the private VLAN configuration commands to assign ports to primary, isolated, or community VLANs. Layer 2 access ports assigned to the VLANs that you configure as primary, isolated, or community VLANs are inactive while the VLAN is part of the private VLAN configuration. Layer 2 trunk interfaces remain in the STP forwarding state. Do not configure ports that belong to a PAgP or LACP EtherChannel as private VLAN ports. While a port is part of the private VLAN configuration, any EtherChannel configuration for it is inactive. Enable PortFast and BPDU guard on isolated and community host ports to prevent STP loops due to misconfigurations and to speed up STP convergence. (See Chapter 21, Configuring Optional STP Features.) When enabled, STP applies the BPDU guard feature to all PortFast-configured Layer 2 LAN ports. Do not enable PortFast and BPDU guard on promiscuous ports. If you delete a VLAN used in the private VLAN configuration, the private VLAN ports associated with the VLAN become inactive. Private VLAN ports can be on different network devices if the devices are trunk-connected and the primary and secondary VLANs have not been removed from the trunk. All primary, isolated, and community VLANs associated within a private VLAN must maintain the same topology across trunks. You are highly recommended to configure the same STP bridge parameters and trunk port parameters on all associated VLANs in order to maintain the same topology.
Limitations with Other Features

When configuring private VLANs, consider these configuration limitations with other features:
Note
In some cases, the configuration is accepted with no error messages, but the commands have no effect.

Do not configure fallback bridging on switches with private VLANs. A port is only affected by the private VLAN feature if it is currently in private VLAN mode and its private VLAN configuration indicates that it is a primary, isolated, or community port. If a port is in any other mode, such as Dynamic Trunking Protocol (DTP), it does not function as a private port. Do not configure private VLAN ports on interfaces configured for these other features:
Port Aggregation Protocol (PAgP) Link Aggregation Control Protocol (LACP) Voice VLAN
You can configure IEEE 802.1x port-based authentication on a private VLAN port, but do not configure 802.1x with port security, voice VLAN, or per-user ACL on private VLAN ports. IEEE 802.1q mapping works normally. Traffic is remapped to or from dot1Q ports as configured, as if received from the ISL VLANs. With releases earlier than Release 12.2(18)SXE, you cannot configure port security on ports that are in a private VLAN.
15-9
Do not configure a remote SPAN (RSPAN) VLAN as a private VLAN primary or secondary VLAN. For more information about SPAN, see Chapter 52, Configuring Local SPAN, RSPAN, and ERSPAN. A private VLAN host or promiscuous port cannot be a SPAN destination port. If you configure a SPAN destination port as a private VLAN port, the port becomes inactive. A destination SPAN port should not be an isolated port. (However, a source SPAN port can be an isolated port.) VSPAN could be configured to span both primary and secondary VLANs or, alternatively, to span either one if the user is interested only in ingress or egress traffic. When protocol filtering is enabled on a Supervisor Engine 1, all the required Local Target Logic (LTL) buckets of a private VLAN port should be programmed with the appropriate secondary VLAN indexes. If using the shortcuts between different VLANs (if any of these VLANs is private) consider both primary and isolated and community VLANs. The primary VLAN should be used both as the destination and as the virtual source, because the secondary VLAN (the real source) is always remapped to the primary VLAN in the Layer 2 FID table. If you configure a static MAC address on a promiscuous port in the primary VLAN, you must add the same static address to all associated secondary VLANs. If you configure a static MAC address on a host port in a secondary VLAN, you must add the same static MAC address to the associated primary VLAN. When you delete a static MAC address from a private VLAN port, you must remove all instances of the configured MAC address from the private VLAN.
Note
Dynamic MAC addresses learned in one VLAN of a private VLAN are replicated in the associated VLANs. For example, a MAC address learned in a secondary VLAN is replicated in the primary VLAN. When the original dynamic MAC address is deleted or aged out, the replicated addresses are removed from the MAC address table.
Do not configure private VLAN ports as EtherChannels. A port can be part of the private VLAN configuration, but any EtherChannel configuration for the port is inactive. These restrictions apply when you configure groups of 12 ports as secondary ports: In all releases, the 12-port restriction applies to these 10 Mb, 10/100 Mb, and 100 Mb Ethernet switching modules: WS-X6324-100FX, WS-X6348-RJ-45, WS-X6348-RJ-45V, WS-X6348-RJ-21V, WS-X6248-RJ-45, WS-X6248A-TEL, WS-X6248-TEL, WS-X6148-RJ-45, WS-X6148-RJ-45V, WS-X6148-45AF, WS-X6148-RJ-21, WS-X6148-RJ-21V, WS-X6148-21AF, WS-X6024-10FL-MT. In releases earlier than Release 12.2(17a)SX, the 12-port restriction applies to these Ethernet switching modules: WS-X6548-RJ-45, WS-X6548-RJ-21, WS-X6524-100FX-MM. In Release 12.2(17a)SX and later releases, the 12-port restriction does not apply to these Ethernet switching modules: WS-X6548-RJ-45, WS-X6548-RJ-21, WS-X6524-100FX-MM (CSCea67876). Within groups of 12 ports (112, 1324, 2536, and 3748), do not configure ports as isolated ports or community VLAN ports when one port within the group of 12 ports is any of these:
A trunk port A SPAN destination port A promiscuous private VLAN port In releases where CSCsb44185 is resolved, a port that has been configured with the switchport
mode dynamic auto or switchport mode dynamic desirable command.
15-10
OL-3999-08
Chapter 15
Configuring Private VLANs Configuring Private VLANs
If one port within the group of 12 ports is one of these ports listed and has the above properties, any isolated or community VLAN configuration for other ports within the 12 ports is inactive. To reactivate the ports, remove the isolated or community VLAN port configuration and enter the shutdown and no shutdown commands.
These restrictions apply when you configure groups of 24 ports as secondary ports: In all releases, this 24-port restriction applies to the WS-X6548-GE-TX and WS-X6148-GE-TX 10/100/1000 Mb Ethernet switching modules. Within groups of 24 ports (124, 2548), do not configure ports as isolated ports or community VLAN ports when one port within the group of 24 ports is any of these:
A trunk port A SPAN destination port A promiscuous private VLAN port In releases where CSCsb44185 is resolved, a port that has been configured with the switchport
mode dynamic auto or switchport mode dynamic desirable command. If one port within the group of 24 ports is one of these ports listed and has the above properties, any isolated or community VLAN configuration for other ports within the 24 ports is inactive. To reactivate the ports, remove the isolated or community VLAN port configuration and enter the shutdown and no shutdown commands.

These sections contain configuration information:

Configuring a VLAN as a Private VLAN, page 15-11 Associating Secondary VLANs with a Primary VLAN, page 15-12 Mapping Secondary VLANs to the Layer 3 VLAN Interface of a Primary VLAN, page 15-13 Configuring a Layer 2 Interface as a Private VLAN Host Port, page 15-14 Configuring a Layer 2 Interface as a Private VLAN Promiscuous Port, page 15-15
Note
If the VLAN is not defined already, the private VLAN configuration process defines it.
Configuring a VLAN as a Private VLAN

To configure a VLAN as a private VLAN, perform this task: Command
Step 1 Step 2
Router(config)# vlan vlan_ID Router(config-vlan)# private-vlan {community | isolated | primary} Router(config-vlan)# no private-vlan {community | isolated | primary}
Purpose Enters VLAN configuration submode. Configures a VLAN as a private VLAN. Clears the private VLAN configuration.
Note
These commands do not take effect until you exit VLAN configuration submode.
15-11
Chapter 15 Configuring Private VLANs
Command
Step 3 Step 4
Router(config-vlan)# end Router# show vlan private-vlan [type]
Purpose Exits configuration mode. Verifies the configuration.
This example shows how to configure VLAN 202 as a primary VLAN and verify the configuration:
Router# configure terminal Router(config)# vlan 202 Router(config-vlan)# private-vlan primary Router(config-vlan)# end Router# show vlan private-vlan Primary Secondary Type Interfaces ------- --------- ----------------- -----------------------------------------202 primary
This example shows how to configure VLAN 303 as a community VLAN and verify the configuration:
Router# configure terminal Router(config)# vlan 303 Router(config-vlan)# private-vlan community Router(config-vlan)# end Router# show vlan private-vlan Primary Secondary Type Interfaces ------- --------- ----------------- -----------------------------------------202 primary 303 community
This example shows how to configure VLAN 440 as an isolated VLAN and verify the configuration:
Router# configure terminal Router(config)# vlan 440 Router(config-vlan)# private-vlan isolated Router(config-vlan)# end Router# show vlan private-vlan Primary Secondary Type Interfaces ------- --------- ----------------- -----------------------------------------202 primary 303 community 440 isolated
Associating Secondary VLANs with a Primary VLAN

To associate secondary VLANs with a primary VLAN, perform this task: Command
Step 1 Step 2
Router(config)# vlan primary_vlan_ID
Purpose Enters VLAN configuration submode for the primary VLAN. Associates the secondary VLANs with the primary VLAN. Clears all secondary VLAN associations. Exits VLAN configuration mode. Verifies the configuration.
Router(config-vlan)# private-vlan association {secondary_vlan_list | add secondary_vlan_list | remove secondary_vlan_list} Router(config-vlan)# no private-vlan association
Step 3 Step 4
Router(config-vlan)# end Router# show vlan private-vlan [type]
15-12
OL-3999-08
Chapter 15
When you associate secondary VLANs with a primary VLAN, note the following information:

The secondary_vlan_list parameter cannot contain spaces. It can contain multiple comma-separated items. Each item can be a single private VLAN ID or a hyphenated range of private VLAN IDs. The secondary_vlan_list parameter can contain multiple community VLAN IDs. The secondary_vlan_list parameter can contain only one isolated VLAN ID. Enter a secondary_vlan_list or use the add keyword with a secondary_vlan_list to associate secondary VLANs with a primary VLAN. Use the remove keyword with a secondary_vlan_list to clear the association between secondary VLANs and a primary VLAN. The command does not take effect until you exit VLAN configuration submode. When you exit the VLAN configuration submode, only the last specified configuration takes effect.
This example shows how to associate community VLANs 303 through 307 and 309 and isolated VLAN 440 with primary VLAN 202 and verify the configuration:
Router# configure terminal Router(config)# vlan 202 Router(config-vlan)# private-vlan association 303-307,309,440 Router(config-vlan)# end Router# show vlan private-vlan Primary ------202 202 202 202 202 202 202 Secondary --------303 304 305 306 307 309 440 308 Type Interfaces ----------------- -----------------------------------------community community community community community community isolated community
Mapping Secondary VLANs to the Layer 3 VLAN Interface of a Primary VLAN

Note
Isolated and community VLANs are both called secondary VLANs. To map secondary VLANs to the Layer 3 VLAN interface of a primary VLAN to allow Layer 3 switching of private VLAN ingress traffic, perform this task:
Command
Step 1 Step 2
Router(config)# interface vlan primary_vlan_ID
Purpose Enters interface configuration mode for the primary VLAN. Maps the secondary VLANs to the Layer 3 VLAN interface of a primary VLAN to allow Layer 3 switching of private VLAN ingress traffic. Clears the mapping between the secondary VLANs and the primary VLAN.
Router(config-if)# private-vlan mapping {secondary_vlan_list | add secondary_vlan_list | remove secondary_vlan_list} Router(config-if)# [no] private-vlan mapping
15-13
Command
Step 3 Step 4
Router(config-if)# end Router# show interface private-vlan mapping
When you map secondary VLANs to the Layer 3 VLAN interface of a primary VLAN, note the following information:

The private-vlan mapping interface configuration command only affects private VLAN ingress traffic that is Layer 3-switched. The secondary_vlan_list parameter cannot contain spaces. It can contain multiple comma-separated items. Each item can be a single private VLAN ID or a hyphenated range of private VLAN IDs. Enter a secondary_vlan_list parameter or use the add keyword with a secondary_vlan_list parameter to map the secondary VLANs to the primary VLAN. Use the remove keyword with a secondary_vlan_list parameter to clear the mapping between secondary VLANs and the primary VLAN.
This example shows how to permit routing of secondary VLAN ingress traffic from private VLANs 303 through 307, 309, and 440 and verify the configuration:
Router# configure terminal Router(config)# interface vlan 202 Router(config-if)# private-vlan mapping add 303-307,309,440 Router(config-if)# end Router# show interfaces private-vlan mapping Interface Secondary VLAN Type --------- -------------- ----------------vlan202 303 community vlan202 304 community vlan202 305 community vlan202 306 community vlan202 307 community vlan202 309 community vlan202 440 isolated Router#
Configuring a Layer 2 Interface as a Private VLAN Host Port

To configure a Layer 2 interface as a private VLAN host port, perform this task: Command
Step 1 Step 2
Router(config)# interface type Router(config-if)# switchport
1
Purpose
slot/port
Selects the LAN port to configure. Configures the LAN port for Layer 2 switching:
You must enter the switchport command once without any keywords to configure the LAN port as a Layer 2 interface before you can enter additional switchport commands with keywords. Required only if you have not entered the switchport command already for the interface.
15-14
OL-3999-08
Chapter 15
Command
Step 3
Router(config-if)# switchport mode private-vlan {host | promiscuous} Router(config-if)# no switchport mode private-vlan
Purpose Configures the Layer 2 port as a private VLAN host port. Clears private VLAN port configuration. Associates the Layer 2 port with a private VLAN.
Step 4
Router(config-if)# switchport private-vlan host-association primary_vlan_ID secondary_vlan_ID Router(config-if)# no switchport private-vlan host-association
Clears the association. Exits configuration mode. Verifies the configuration.
Step 5 Step 6
Router(config-if)# end Router# show interfaces [type1 slot/port] switchport 1.
This example shows how to configure interface FastEthernet 5/1 as a private VLAN host port and verify the configuration:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# switchport mode private-vlan host Router(config-if)# switchport private-vlan host-association 202 303 Router(config-if)# end Router# show interfaces fastethernet 5/1 switchport Name: Fa5/1 Switchport: Enabled Administrative Mode: private-vlan host Operational Mode: down Administrative Trunking Encapsulation: negotiate Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Administrative private-vlan host-association: 202 (VLAN0202) 303 (VLAN0303) Administrative private-vlan mapping: none Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled
Configuring a Layer 2 Interface as a Private VLAN Promiscuous Port

To configure a Layer 2 interface as a private VLAN promiscuous port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN interface to configure. Configures the LAN interface for Layer 2 switching:
You must enter the switchport command once without any keywords to configure the LAN interface as a Layer 2 interface before you can enter additional switchport commands with keywords. Required only if you have not entered the switchport command already for the interface.
15-15
Command
Step 3
Router(config-if)# switchport mode private-vlan {host | promiscuous} Router(config-if)# no switchport mode private-vlan
Purpose Configures the Layer 2 port as a private VLAN promiscuous port. Clears the private VLAN port configuration. Maps the private VLAN promiscuous port to a primary VLAN and to selected secondary VLANs. Clears all mapping between the private VLAN promiscuous port and the primary VLAN and any secondary VLANs. Exits configuration mode.
1
Step 4
Router(config-if)# switchport private-vlan mapping primary_vlan_ID {secondary_vlan_list | add secondary_vlan_list | remove secondary_vlan_list} Router(config-if)# no switchport private-vlan mapping
Step 5 Step 6
Router(config-if)# end Router# show interfaces [type switchport 1.
slot/port]
When you configure a Layer 2 interface as a private VLAN promiscuous port, note the following information:

The secondary_vlan_list parameter cannot contain spaces. It can contain multiple comma-separated items. Each item can be a single private VLAN ID or a hyphenated range of private VLAN IDs. Enter a secondary_vlan_list value or use the add keyword with a secondary_vlan_list value to map the secondary VLANs to the private VLAN promiscuous port. Use the remove keyword with a secondary_vlan_list value to clear the mapping between secondary VLANs and the private VLAN promiscuous port.
This example shows how to configure interface FastEthernet 5/2 as a private VLAN promiscuous port and map it to a private VLAN:
Router# configure terminal Router(config)# interface fastethernet 5/2 Router(config-if)# switchport mode private-vlan promiscuous Router(config-if)# switchport private-vlan mapping 202 303,440 Router(config-if)# end

Router# show interfaces fastethernet 5/2 switchport Name: Fa5/2 Switchport: Enabled Administrative Mode: private-vlan promiscuous Operational Mode: down Administrative Trunking Encapsulation: negotiate Negotiation of Trunking: On Access Mode VLAN: 1 (default) Trunking Native Mode VLAN: 1 (default) Administrative private-vlan host-association: none ((Inactive)) Administrative private-vlan mapping: 202 (VLAN0202) 303 (VLAN0303) 440 (VLAN0440) Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled
15-16
OL-3999-08
Chapter 15
Configuring Private VLANs Monitoring Private VLANs
Monitoring Private VLANs

Table 15-1 shows the privileged EXEC commands for monitoring private VLAN activity.
Table 15-1 Private VLAN Monitoring Commands
Command show interfaces status show vlan private-vlan [type] show interface switchport show interface private-vlan mapping
Purpose Displays the status of interfaces, including the VLANs to which they belong. Displays the private VLAN information for the switch. Displays private VLAN configuration on interfaces. Displays information about the private VLAN mapping for VLAN SVIs.
This is an example of the output from the show vlan private-vlan command:
Switch(config)# show vlan private-vlan Primary Secondary Type Ports ------- --------- ----------------- -----------------------------------------10 501 isolated Fa2/1, Gi3/1, Gi3/2 10 502 community Fa2/11, Gi3/1, Gi3/4 10 503 non-operational
Tip
15-17
Chapter 15 Monitoring Private VLANs
15-18
OL-3999-08
C H A P T E R
16

This chapter describes how to configure support for Cisco IP phones on the Catalyst 6500 series switches.
Note

Understanding Cisco IP Phone Support, page 16-1 Default Cisco IP Phone Support Configuration, page 16-5 Cisco IP Phone Support Configuration Guidelines and Restrictions, page 16-5 Configuring Cisco IP Phone Support, page 16-6
Tip
Understanding Cisco IP Phone Support

These sections describe Cisco IP phone support:

Cisco IP Phone Connections, page 16-2 Cisco IP Phone Voice Traffic, page 16-2 Cisco IP Phone Data Traffic, page 16-3 Cisco IP Phone Power Configurations, page 16-3 Other Cisco IP Phone Features, page 16-4
16-1
Chapter 16 Understanding Cisco IP Phone Support
Cisco IP Phone Connections

The Cisco IP phone contains an integrated 3-port 10/100 switch. The ports are dedicated connections to these devices:

Port 1 connects to the switch. Port 2 is an internal 10/100 interface that carries the Cisco IP phone traffic. Port 3 connects to a PC or other device.
Figure 16-1 shows a Cisco IP phone connected between a switch and a PC.
Figure 16-1 Cisco IP Phone Connected to a Switch
Cisco IP Phone 7960
Phone ASIC
P2 P1 10/100 module 3-port switch P3 Access port
Workstation/PC
Catalyst switch or Cisco Router
Cisco IP Phone Voice Traffic

The Cisco IP phone transmits voice traffic with Layer 3 IP precedence and Layer 2 CoS values, which are both set to 5 by default. The sound quality of a Cisco IP phone call can deteriorate if the voice traffic is transmitted unevenly. To provide more predictable voice traffic flow, you can configure QoS to trust the Layer 3 IP precedence or Layer 2 CoS value in the voice traffic (refer to Chapter 41, Configuring PFC QoS).
Note
You can configure the ports on WS-X6548-RJ-45 and WS-X6548-RJ-21 switching modules to trust received Layer 2 CoS values (QoS port architecture 1p1q0t/1p3q1t). The WS-X6548-RJ-45 and WS-X6548-RJ-21 switching modules cannot supply power to Cisco IP phones. Configure QoS policies that use the Layer 3 IP precedence value on other switching modules. You can configure a Layer 2 access port with an attached Cisco IP phone to use one VLAN for voice traffic and another VLAN for data traffic from a device attached to the Cisco IP phone. You can configure Layer 2 access ports on the switch to send Cisco Discovery Protocol (CDP) packets that instruct an attached Cisco IP phone to transmit voice traffic to the switch in any of the following ways:

In the voice VLAN, tagged with a Layer 2 CoS priority value In the access VLAN, tagged with a Layer 2 CoS priority value
16-2
79490
OL-3999-08
Chapter 16
Configuring Cisco IP Phone Support Understanding Cisco IP Phone Support
In the access VLAN, untagged (no Layer 2 CoS priority value)
Note
In all configurations, the voice traffic carries a Layer 3 IP precedence value (the default is 5 for voice traffic and 3 for voice control traffic). You cannot use Cisco IOS software commands to configure the frame type used by data traffic sent from a device attached to the access port on the Cisco IP phone.
Cisco IP Phone Data Traffic

Note
Untagged traffic from the device attached to the Cisco IP phone passes through the Cisco IP phone unchanged, regardless of the trust state of the access port on the Cisco IP phone. To process tagged data traffic (traffic in 802.1Q or 802.1p frame types) from the device attached to the access port on the Cisco IP phone (see Figure 16-1), you can configure Layer 2 access ports on the switch to send CDP packets that instruct an attached Cisco IP phone to configure the access port on the Cisco IP phone to either of these two modes:

Trusted modeAll traffic received through the access port on the Cisco IP phone passes through the Cisco IP phone unchanged. Untrusted modeAll traffic in 802.1Q or 802.1p frames received through the access port on the Cisco IP phone is marked with a configured Layer 2 CoS value. The default Layer 2 CoS value is 0. Untrusted mode is the default.
Cisco IP Phone Power Configurations

These sections describe Cisco IP phone power configurations:

Locally Powered Cisco IP Phones, page 16-3 Inline-Powered Cisco IP Phones, page 16-4
Locally Powered Cisco IP Phones

There are two varieties of local power:

From a power supply connected to the Cisco IP phone From a power supply through a patch panel over the twisted-pair Ethernet cable to the Cisco IP phone
When a locally powered Cisco IP phone is present on a switching module port, the switching module cannot detect its presence. The supervisor engine discovers the Cisco IP phone through CDP messaging with the Cisco IP phone. If a locally powered Cisco IP phone loses local power and the mode is set to auto, the switching module discovers the Cisco IP phone and informs the supervisor engine, which then supplies inline power to the Cisco IP phone.
16-3
Chapter 16 Understanding Cisco IP Phone Support
Inline-Powered Cisco IP Phones

Inline power is from switching modules that support an inline power daughtercard. Inline power is sent over the twisted-pair Ethernet cable to the Cisco IP phone.
Note
For information about switching modules that support inline power, refer to the Release Notes for Cisco IOS Release 12.2SXF and Rebuilds. When a switching module port detects an unpowered Cisco IP phone, the switching module reports to the supervisor engine that an unpowered Cisco IP phone is present and on which module and port. If the port is configured in auto mode, the supervisor engine determines if there is enough system power available to power up the Cisco IP phone. If there is sufficient power available, the supervisor engine removes the default-allocated power required by a Cisco IP phone from the total available system power and sends a message to the switching module instructing it to provide power to the port. If there is not enough available power for the Cisco IP phone, the supervisor engine sends a message to the switching module indicating that power is denied to the port. Cisco IP phones may have different power requirements. The supervisor engine initially allocates the configured default of 7 W (167 mA at 42 V) to the Cisco IP phone. When the correct amount of power is determined from the CDP messaging with the Cisco IP phone, the supervisor engine reduces or increases the allocated power. For example, the default allocated power is 7 W. A Cisco IP phone requiring 6.3 W is plugged into a port. The supervisor engine allocates 7 W for the Cisco IP phone and powers it up. Once the Cisco IP phone is operational, it sends a CDP message with the actual power requirement to the supervisor engine. The supervisor engine then decreases the allocated power to the required amount. When you power off the Cisco IP phone through the CLI or SNMP or remove it, the supervisor engine sends a message to the switching module to turn off the power on the port. That power is then returned to the available system power.
Caution
When a Cisco IP phone cable is plugged into a port and the power is turned on, the supervisor engine has a 4-second timeout waiting for the link to go up on the line. During those 4 seconds, if the Cisco IP phone cable is unplugged and a network device is plugged in, the network device could be damaged. We recommend that you wait at least 10 seconds between unplugging a network device and plugging in another network device.
Other Cisco IP Phone Features

The Catalyst 6500 series switch provides support for authentication, authorization, and accounting (AAA) for Cisco IP phones, as described in Chapter 46, Configuring IEEE 802.1X Port-Based Authentication. The Catalyst 6500 series switch also supports automatic tracking for Cisco Emergency Responder (Cisco ER) to help you manage emergency calls in your telephony network. For further information, see this URL: http://www.cisco.com/en/US/products/sw/voicesw/ps842/tsd_products_support_series_home.html
16-4
OL-3999-08
Chapter 16
Configuring Cisco IP Phone Support Default Cisco IP Phone Support Configuration
Default Cisco IP Phone Support Configuration

Cisco IP phone support is disabled by default. When the voice VLAN feature is enabled, all untagged traffic is sent with the default CoS priority of the port. The CoS is not trusted for 802.1P or 802.1Q tagged traffic.
Cisco IP Phone Support Configuration Guidelines and Restrictions

The following guidelines and restrictions apply when configuring Cisco IP phone support:

You must enable the Cisco Discovery Protocol (CDP) on the Catalyst 6500 series switch port connected to the Cisco IP phone to send configuration information to the Cisco IP phone. You can configure a voice VLAN only on a Layer 2 LAN port. You can configure the ports on WS-X6548-RJ-45 and WS-X6548-RJ-21 switching modules to trust received Layer 2 CoS values (QoS port architecture 1p1q0t/1p3q1t). The WS-X6548-RJ-45 and WS-X6548-RJ-21 switching modules cannot supply power to Cisco IP phones. You cannot configure 10/100 Mbps ports with QoS port architecture 1p4t/2q2t to trust received Layer 2 CoS values. Configure policies to trust the Layer 3 IP precedence value on switching modules with QoS port architecture 1p4t/2q2t. The following conditions indicate that the Cisco IP phone and a device attached to the Cisco IP phone are in the same VLAN and must be in the same IP subnet:
If they both use 802.1p or untagged frames If the Cisco IP phone uses 802.1p frames and the device uses untagged frames If the Cisco IP phone uses untagged frames and the device uses 802.1p frames If the Cisco IP phone uses 802.1Q frames and the voice VLAN is the same as the access VLAN
The Cisco IP phone and a device attached to the Cisco IP phone cannot communicate if they are in the same VLAN and subnet but use different frame types, because traffic between devices in the same subnet is not routed (routing would eliminate the frame type difference). You cannot use Cisco IOS software commands to configure the frame type used by traffic sent from a device attached to the access port on the Cisco IP phone. If you enable port security on a port configured with a voice VLAN and if there is a PC connected to the Cisco IP phone, set the maximum allowed secure addresses on the port to at least 2. You cannot configure static secure MAC addresses in the voice VLAN. Ports configured with a voice VLAN can be secure ports (refer to Chapter 47, Configuring Port Security). In all configurations, the voice traffic carries a Layer 3 IP precedence value (the default is 5 for voice traffic and 3 for voice control traffic).
16-5
Chapter 16 Configuring Cisco IP Phone Support

These sections describe how to configure Cisco IP phone support:

Configuring Voice Traffic Support, page 16-6 Configuring Data Traffic Support, page 16-7 Configuring Inline Power Support, page 16-8
Note
Voice VLANs are referred to as auxiliary VLANs in the Catalyst software publications.
Configuring Voice Traffic Support

To configure the way in which the Cisco IP phone transmits voice traffic, perform this task: Command
Step 1 Step 2
Router(config)# interface fastethernet slot/port Router(config-if)# switchport voice vlan {voice_vlan_ID | dot1p | none | untagged} Router(config-if)# no switchport voice vlan
Purpose Selects the port to configure. Configures the way in which the Cisco IP phone transmits voice traffic. Clears the configuration. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config)# end Router# show interfaces fastethernet slot/port switchport Router# show running-config interface fastethernet slot/port
When configuring the way in which the Cisco IP phone transmits voice traffic, note the following information:
Enter a voice VLAN ID to send CDP packets that configure the Cisco IP phone to transmit voice traffic in 802.1Q frames, tagged with the voice VLAN ID and a Layer 2 CoS value (the default is 5). Valid VLAN IDs are from 1 to 4094. The switch puts the 802.1Q voice traffic into the voice VLAN. Enter the dot1p keyword to send CDP packets that configure the Cisco IP phone to transmit voice traffic in 802.1p frames, tagged with VLAN ID 0 and a Layer 2 CoS value (the default is 5 for voice traffic and 3 for voice control traffic). The switch puts the 802.1p voice traffic into the access VLAN. Enter the untagged keyword to send CDP packets that configure the Cisco IP phone to transmit untagged voice traffic. The switch puts the untagged voice traffic into the access VLAN. Enter the none keyword to allow the Cisco IP phone to use its own configuration and transmit untagged voice traffic. The switch puts the untagged voice traffic into the access VLAN. In all configurations, the voice traffic carries a Layer 3 IP precedence value (the default is 5). Refer to Chapter 41, Configuring PFC QoS, for information about how to configure QoS. Refer to the Configuring a LAN Interface as a Layer 2 Access Port section on page 10-14 for information about how to configure the port as a Layer 2 access port and configure the access VLAN.
16-6
OL-3999-08
Chapter 16
Configuring Cisco IP Phone Support Configuring Cisco IP Phone Support
This example shows how to configure Fast Ethernet port 5/1 to send CDP packets that tell the Cisco IP phone to use VLAN 101 as the voice VLAN:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# switchport voice vlan 101 Router(config-if)# exit
Router# show interfaces fastethernet 5/1 switchport Name: Fa5/1 Switchport: Enabled Administrative Mode: access Operational Mode: access Administrative Trunking Encapsulation: dot1q Operational Trunking Encapsulation: dot1q Negotiation of Trunking: off Access Mode VLAN: 100 Voice VLAN: 101 Trunking Native Mode VLAN: 1 (default) Administrative private-vlan host-association: none Administrative private-vlan mapping: 900 ((Inactive)) 901 ((Inactive)) Operational private-vlan: none Trunking VLANs Enabled: ALL Pruning VLANs Enabled: 2-1001 Capture Mode Disabled Capture VLANs Allowed: ALL
Configuring Data Traffic Support

To configure the way in which the Cisco IP phone transmits data traffic, perform this task: Command
Step 1 Step 2
Router(config)# interface fastethernet slot/port Router(config-if)# mls qos trust extend [cos cos_value] Router(config-if)# no mls qos trust extend
Purpose Selects the port to configure. Configures the way in which the Cisco IP phone transmits data traffic. Clears the configuration. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config)# end Router# show interfaces fastethernet slot/port switchport Router# show running-config interface fastethernet slot/port
When configuring the way in which the Cisco IP phone transmits data traffic, note the following information:

To send CDP packets that configure the Cisco IP phone to trust tagged traffic received from a device connected to the access port on the Cisco IP phone, do not enter the cos keyword and CoS value. To send CDP packets that configure the Cisco IP phone to mark tagged ingress traffic received from a device connected to the access port on the Cisco IP phone, enter the cos keyword and CoS value (valid values are 0 through 7). You cannot use Cisco IOS software commands to configure whether or not traffic sent from a device attached to the access port on the Cisco IP phone is tagged.
16-7
This example shows how to configure Fast Ethernet port 5/1 to send CDP packets that tell the Cisco IP phone to configure its access port as untrusted and to mark all tagged traffic received from a device connected to the access port on the Cisco IP phone with CoS 3:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# mls qos trust extend cos 3
This example shows how to configure Fast Ethernet port 5/1 to send CDP packets that tell the Cisco IP phone to configure its access port as trusted:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# mls qos trust extend
This example shows how to verify the configuration on Fast Ethernet port 5/1:
Router# show queueing interface fastethernet 5/1 | include Extend Extend trust state: trusted
Configuring Inline Power Support

To configure inline power support, perform this task: Command
Step 1 Step 2
Router(config)# interface fastethernet slot/port Router(config-if)# power inline {auto | never} Router(config-if)# no power inline
Purpose Selects the port to configure. Configures inline power support. Clears the configuration. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config)# end Router# show power inline [fastethernet slot/port]
When configuring inline power support, note the following information:

To configure auto-detection of a Cisco IP phone, enter the auto keyword. To disable auto-detection of a Cisco IP phone, enter the never keyword.
This example shows how to disable inline power on Fast Ethernet port 5/1:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# power inline never
This example shows how to enable inline power on Fast Ethernet port 5/1:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# power inline auto
This example shows how to verify the inline power configuration on Fast Ethernet port 5/1:
Router# show power inline fastethernet 5/1 Interface Admin Oper Power Device (Watts) ---------- ----- ---------- ------- ------------------Fa5/1 auto on 6.3 cisco phone device
16-8
OL-3999-08
Chapter 16
Configuring Cisco IP Phone Support Configuring Cisco IP Phone Support
Tip
16-9
16-10
OL-3999-08
C H A P T E R
17
Configuring IEEE 802.1Q Tunneling

This chapter describes how to configure IEEE 802.1Q tunneling on the Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html The WS-X6548-GE-TX, WS-X6548V-GE-TX, WS-X6148-GE-TX, and WS-X6148V-GE-TX switching modules do not support IEEE 802.1Q tunneling.

Understanding How 802.1Q Tunneling Works, page 17-1 802.1Q Tunneling Configuration Guidelines and Restrictions, page 17-3 Configuring 802.1Q Tunneling, page 17-6
Tip
Understanding How 802.1Q Tunneling Works

802.1Q tunneling enables service providers to use a single VLAN to support customers who have multiple VLANs, while preserving customer VLAN IDs and keeping traffic in different customer VLANs segregated. A port configured to support 802.1Q tunneling is called a tunnel port. When you configure tunneling, you assign a tunnel port to a VLAN that you dedicate to tunneling, which then becomes a tunnel VLAN. To keep customer traffic segregated, each customer requires a separate tunnel VLAN, but that one tunnel VLAN supports all of the customers VLANs. 802.1Q tunneling is not restricted to point-to-point tunnel configurations. Any tunnel port in a tunnel VLAN is a tunnel entry and exit point. An 802.1Q tunnel can have as many tunnel ports as are needed to connect customer switches.
17-1
Chapter 17 Understanding How 802.1Q Tunneling Works
The customer switches are trunk connected, but with 802.1Q tunneling, the service provider switches only use one service provider VLAN to carry all the customer VLANs, instead of directly carrying all the customer VLANs. With 802.1Q tunneling, tagged customer traffic comes from an 802.1Q trunk port on a customer device and enters the service-provider edge switch through a tunnel port. The link between the 802.1Q trunk port on a customer device and the tunnel port is called an asymmetrical link because one end is configured as an 802.1Q trunk port and the other end is configured as a tunnel port. You assign the tunnel port to an access VLAN ID unique to each customer. See Figure 17-1 on page 17-2 and Figure 17-2 on page 17-3.
Figure 17-1 IEEE 802.1Q Tunnel Ports in a Service-Provider Network
Customer A VLANs 1 to 100 Customer A VLANs 1 to 100 802.1Q trunk port 802.1Q trunk port Service provider 802.1Q 802.1Q trunk trunk port port Tunnel port VLAN 30 Tunnel port VLAN 30 Trunk ports Tunnel port VLAN 40 802.1Q trunk port Trunk ports Tunnel port VLAN 40 802.1Q trunk port 802.1Q trunk port
74016
802.1Q trunk port 802.1Q trunk port Tunnel port VLAN 30
Customer B VLANs 1 to 200
Trunk Asymmetric link
Customer B VLANs 1 to 200
17-2
OL-3999-08
Chapter 17
Configuring IEEE 802.1Q Tunneling 802.1Q Tunneling Configuration Guidelines and Restrictions
Figure 17-2 Untagged, 802.1Q-Tagged, and Double-Tagged Ethernet Frames
Source address Destination Length/ address EtherType DA SA Len/Etype Data
Frame Check Sequence FCS Original Ethernet frame
DA
SA
Etype
Tag
Len/Etype
Data
FCS
802.1Q frame from customer network
DA
SA
Etype
Tag
Etype
Tag
Len/Etype
Data
FCS Double-tagged frame on trunk links between service provider network devices
When a tunnel port receives tagged customer traffic from an 802.1Q trunk port, it does not strip the received 802.1Q tag from the frame header; instead, the tunnel port leaves the 802.1Q tag intact, adds a 2-byte Ethertype field (0x8100) followed by a 2-byte field containing the priority (CoS) and the VLAN. The received customer traffic is then put into the VLAN to which the tunnel port is assigned. This Ethertype 0x8100 traffic, with the received 802.1Q tag intact, is called tunnel traffic. A VLAN carrying tunnel traffic is an 802.1Q tunnel. The tunnel ports in the VLAN are the tunnels ingress and egress points. The tunnel ports do not have to be on the same network device. The tunnel can cross other network links and other network devices before reaching the egress tunnel port. A tunnel can have as many tunnel ports as required to support the customer devices that need to communicate through the tunnel. An egress tunnel port strips the 2-byte Ethertype field (0x8100) and the 2-byte length field and transmits the traffic with the 802.1Q tag still intact to an 802.1Q trunk port on a customer device. The 802.1Q trunk port on the customer device strips the 802.1Q tag and puts the traffic into the appropriate customer VLAN.
Note
Tunnel traffic carries a second 802.1Q tag only when it is on a trunk link between service-provider network devices, with the outer tag containing the service-provider-assigned VLAN ID and the inner tag containing the customer-assigned VLAN IDs.
802.1Q Tunneling Configuration Guidelines and Restrictions

When configuring 802.1Q tunneling in your network, follow these guidelines and restrictions:

Use asymmetrical links to put traffic into a tunnel or to remove traffic from a tunnel. Configure tunnel ports only to form an asymmetrical link.
17-3
79831
Chapter 17 802.1Q Tunneling Configuration Guidelines and Restrictions
Dedicate one VLAN for each tunnel. Assign only tunnel ports to VLANs used for tunneling. Trunks require no special configuration to carry tunnel VLANs. Tunnel ports are not trunks. Any commands to configure trunking are inactive while the port is configured as a tunnel port. Tunnel ports learn customer MAC addresses. We recommend that you use ISL trunks to carry tunnel traffic between devices that do not have tunnel ports. Because of the 802.1Q native VLAN feature, using 802.1Q trunks requires that you be very careful when you configure tunneling: a mistake might direct tunnel traffic to a non-tunnel port. By default, the native VLAN traffic of a dot1q trunk is sent untagged, which cannot be double-tagged in the service provider network. Because of this situation, the native VLAN traffic might not be tunneled correctly. Be sure that the native VLAN traffic is always sent tagged in an asymmetrical link. To tag the native VLAN egress traffic and drop all untagged ingress traffic, enter the global vlan dot1q tag native command. Configure jumbo frame support on tunnel ports:
See the Configuring Jumbo Frame Support section on page 9-10. Take note of the modules listed in the Configuring Jumbo Frame Support section that do not
support jumbo frames.

Jumbo frames can be tunneled as long as the jumbo frame length combined with the 802.1Q tag does not exceed the maximum frame size. Because tunnel traffic has the added ethertype and length field and retains the 802.1Q tag within the switch, the following restrictions exist:
The Layer 3 packet within the Layer 2 frame cannot be identified in tunnel traffic. Layer 3 and higher parameters cannot be identified in tunnel traffic (for example, Layer 3
destination and source addresses).

Because the Layer 3 addresses cannot be identified within the packet, tunnel traffic cannot be
routed.
The switch can provide only MAC-layer filtering for tunnel traffic (VLAN IDs and source and
destination MAC addresses).

The switch can provide only MAC-layer access control and QoS for tunnel traffic. QoS cannot detect the received CoS value in the 802.1Q 2-byte Tag Control Information field.
On an asymmetrical link, the Cisco Discovery Protocol (CDP) reports a native VLAN mismatch if the VLAN of the tunnel port does not match the native VLAN of the 802.1Q trunk. The 802.1Q tunnel feature does not require that the VLANs match. Ignore the messages if your configuration requires nonmatching VLANs. Asymmetrical links do not support the Dynamic Trunking Protocol (DTP) because only one port on the link is a trunk. Configure the 802.1Q trunk port on an asymmetrical link to trunk unconditionally. The 802.1Q tunneling feature cannot be configured on ports configured to support private VLANs. The following Layer 2 protocols work between devices connected by an asymmetrical link:
CDP UniDirectional Link Detection (UDLD) Port Aggregation Protocol (PAgP) Link Aggregation Control Protocol (LACP)
17-4
OL-3999-08
Chapter 17
Configuring IEEE 802.1Q Tunneling 802.1Q Tunneling Configuration Guidelines and Restrictions
Spanning-tree BPDU filtering is enabled automatically on tunnel ports. CDP is automatically disabled on tunnel ports. VLAN Trunk Protocol (VTP) does not work between the following devices:
Devices connected by an asymmetrical link Devices communicating through a tunnel
Note
VTP works between tunneled devices if Layer 2 protocol tunneling is enabled. See Chapter 18, Configuring Layer 2 Protocol Tunneling, for configuration details.
To configure an EtherChannel as an asymmetrical link, all ports in the EtherChannel must have the same tunneling configuration. Because the Layer 3 packet within the Layer 2 frame cannot be identified, you must configure the EtherChannel to use MAC-address-based frame distribution.
The following configuration guidelines are required for your Layer 2 protocol tunneling configuration:
On all the service provider edge switches, PortFast BPDU filtering must be enabled on the 802.1Q tunnel ports as follows:
Router(config-if)# spanning-tree bpdufilter enable Router(config-if)# spanning-tree portfast
Note
Spanning-tree BPDU filtering is enabled automatically on tunnel ports.
At least one VLAN must be available for Native VLAN tagging (vlan dot1q tag native option). If you use all the available VLANs and then try to enable the vlan dot1q tag native option, the option will not be enabled. On all the service provider core switches, tag native VLAN egress traffic and drop untagged native VLAN ingress traffic by entering the following command:
Router(config)# vlan dot1q tag native
On all the customer switches, either enable or disable the global vlan dot1q tag native option.
Note
If this option is enabled on one switch and disabled on another switch, all traffic is dropped; all customer switches must have this option configured the same on each switch.
The following configuration guidelines are optional for your Layer 2 protocol tunneling configuration:
Because all the BPDUs are being dropped, spanning tree PortFast can be enabled on Layer 2 protocol tunnel ports as follows:
Router(config-if)# spanning-tree portfast trunk
If the service provider does not want the customer to see its switches, CDP should be disabled on the 802.1Q tunnel port as follows:
Router(config-if)# no cdp enable
17-5
Chapter 17 Configuring 802.1Q Tunneling
Configuring 802.1Q Tunneling

These sections describe 802.1Q tunneling configuration:

Configuring 802.1Q Tunnel Ports, page 17-6 Configuring the Switch to Tag Native VLAN Traffic, page 17-6
Caution
Ensure that only the appropriate tunnel ports are in any VLAN used for tunneling and that one VLAN is used for each tunnel. Incorrect assignment of tunnel ports to VLANs can forward traffic inappropriately.
Configuring 802.1Q Tunnel Ports

To configure 802.1Q tunneling on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Configures the LAN port for Layer 2 switching:
Step 3
Router(config-if)# switchport mode dot1q-tunnel Router(config-if)# no switchport mode dot1q-tunnel
Configures the Layer 2 port as a tunnel port. Clears the tunnel port configuration. Exits configuration mode. Verifies the configuration.
Step 4 Step 5
Router(config-if)# end Router# show dot1q-tunnel [{interface type interface-number}] 1.
This example shows how to configure tunneling on port 4/1 and verify the configuration:
Router# configure terminal Router(config)# interface fastethernet 4/1 Router(config-if)# switchport mode dot1q-tunnel Router(config-if)# end Router# show dot1q-tunnel interface
Configuring the Switch to Tag Native VLAN Traffic

The vlan dot1q tag native command is a global command that configures the switch to tag native VLAN traffic, and admit only 802.1Q tagged frames on 802.1Q trunks, dropping any untagged traffic, including untagged traffic in the native VLAN.
17-6
OL-3999-08
Chapter 17
Configuring IEEE 802.1Q Tunneling Configuring 802.1Q Tunneling
To configure the switch to tag traffic in the native VLAN, perform this task: Command
Step 1
Router(config)# vlan dot1q tag native Router(config)# no vlan dot1q tag native
Purpose Configures the switch to tag native VLAN traffic. Clears the configuration. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show vlan dot1q tag native
This example shows how to configure the switch to tag native VLAN traffic and verify the configuration:
Router# configure terminal Router(config)# vlan dot1q tag native Router(config)# end Router# show vlan dot1q tag native
Tip
17-7
Chapter 17 Configuring 802.1Q Tunneling
17-8
OL-3999-08
C H A P T E R
18
Configuring Layer 2 Protocol Tunneling

This chapter describes how to configure Layer 2 protocol tunneling on the Catalyst 6500 series switches.
Note
The WS-X6548-GE-TX, WS-X6548V-GE-TX, WS-X6148-GE-TX, and WS-X6148V-GE-TX switching modules do not support Layer 2 protocol tunneling.

Understanding How Layer 2 Protocol Tunneling Works, page 18-1 Configuring Support for Layer 2 Protocol Tunneling, page 18-2
Tip
Understanding How Layer 2 Protocol Tunneling Works

Layer 2 protocol tunneling allows Layer 2 protocol data units (PDUs) (CDP, STP, and VTP) to be tunneled through a network. This section uses the following terminology:

Edge switchThe switch connected to the customer switch and placed on the boundary of the service provider network (see Figure 18-1). Layer 2 protocol tunnel portA port on the edge switch on which a specific tunneled protocol can be encapsulated or deencapsulated. The Layer 2 protocol tunnel port is configured through CLI commands. Tunneled PDUA CDP, STP, or VTP PDU.
18-1
Chapter 18 Configuring Support for Layer 2 Protocol Tunneling
Without Layer 2 protocol tunneling, tunnel ports drop STP and VTP packets and process CDP packets. This handling of the PDUs creates different spanning tree domains (different spanning tree roots) for the customer switches. For example, STP for a VLAN on switch 1 (see Figure 18-1) builds a spanning tree topology on switches 1, 2, and 3 without considering convergence parameters based on switches 4 and 5. To provide a single spanning tree domain for the customer, a generic scheme to tunnel BPDUs was created for control protocol PDUs (CDP, STP, and VTP). This process is referred to as Generic Bridge PDU Tunneling (GBPT).
Figure 18-1 Layer 2 Protocol Tunneling Network Configuration
Customer switches
Switch 1
Customer switches Service provider network Edge switches Switch B

77066
Switch 4
Switch 2
Switch A
Switch 3
Switch 5
GBPT provides a scalable approach to PDU tunneling by software encapsulating the PDUs in the ingress edge switches and then multicasting them in hardware. All switches inside the service provider network treat these encapsulated frames as data packets and forward them to the other end. The egress edge switch listens for these special encapsulated frames and deencapsulates them; they are then forwarded out of the tunnel. The encapsulation involves rewriting the destination media access control (MAC) address in the PDU. An ingress edge switch rewrites the destination MAC address of the PDUs received on a Layer 2 tunnel port with the Cisco proprietary multicast address (01-00-0c-cd-cd-d0). The PDU is then flooded to the native VLAN of the Layer 2 tunnel port. If you enable Layer 2 protocol tunneling on a port, PDUs of an enabled protocol are not sent out. If you disable Layer 2 protocol tunneling on a port, the disabled protocols function the same way they were functioning before Layer 2 protocol tunneling was enabled on the port.
Configuring Support for Layer 2 Protocol Tunneling

Note
Encapsulated PDUs received by an 802.1Q tunnel port are transmitted from other tunnel ports in the same VLAN on the switch. Configure jumbo frame support on Layer 2 protocol tunneling ports:
See the Configuring Jumbo Frame Support section on page 9-10. Take note of the modules listed in the Configuring Jumbo Frame Support section that do not
support jumbo frames.
18-2
OL-3999-08
Chapter 18
Configuring Layer 2 Protocol Tunneling Configuring Support for Layer 2 Protocol Tunneling
To configure Layer 2 protocol tunneling on a port, perform this task: Command

Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# switchport
Purpose Selects the LAN port to configure. Configures the LAN port for Layer 2 switching:
Step 3
Router(config-if)# l2protocol-tunnel [cdp|drop-threshold [packets|shutdown-threshold [packets]|stp|vtp] Router(config-if)# no l2protocol-tunnel [cdp| drop-threshold|shutdown-threshold|stp|vtp]
Configures the Layer 2 port as a Layer 2 protocol tunnel port for the protocols specified. Clears the configuration. Exits configuration mode. Verifies the configuration.
Step 4 Step 5
Router(config)# end Router# show l2protocol-tunnel [interface type1 slot/port|summary] 1.
When you configure a Layer 2 port as a Layer 2 protocol tunnel port, note the following information:
Optionally, you may specify a drop threshold for the port. The drop threshold value, from 1 to 4096, determines the number of packets to be processed for that protocol on that interface in one second. When the drop threshold is exceeded, PDUs for the specified protocol are dropped for the remainder of the 1-second period. If a shutdown threshold is not specified, the value is 0 (shutdown threshold disabled). Optionally, you may specify a shutdown threshold for the port. The shutdown threshold value, from 1 to 4096, determines the number of packets to be processed for that protocol on that interface in one second. When the shutdown threshold is exceeded, the port is put in errdisable state. If a shutdown threshold is not specified, the value is 0 (shutdown threshold disabled).
Note
Refer to the Cisco IOS Master Command List, Release 12.2SX for more information about the l2ptguard keyword for the following commands:
errdisable detect cause
errdisable recovery cause This example shows how to configure Layer 2 protocol tunneling and shutdown thresholds on port 5/1 for CDP, STP, and VTP, and verify the configuration:
Router# configure terminal Router(config)# interface fastethernet 5/1 Router(config-if)# switchport Router(config-if)# l2protocol-tunnel shutdown-threshold cdp 10 Router(config-if)# l2protocol-tunnel shutdown-threshold stp 10 Router(config-if)# l2protocol-tunnel shutdown-threshold vtp 10 Router(config-if)# end
18-3
Chapter 18 Configuring Support for Layer 2 Protocol Tunneling
Router# show l2protocol-tunnel summary Port Protocol Threshold (cos/cdp/stp/vtp) ---------------------------------------Fa5/1 cdp stp vtp 0/10 /10 /10 Router#
down trunk
This example shows how to display counter information for port 5/1:
Router# show l2protocol-tunnel interface fastethernet 5/1 Port Protocol Threshold Counters (cos/cdp/stp/vtp) (cdp/stp/vtp/decap) -------------------------------------------------------------Router#
This example shows how to clear the Layer 2 protocol tunneling configuration from port 5/1:
Router(config-if)# no l2protocol-tunnel shutdown-threshold cdp 10 Router(config-if)# no l2protocol-tunnel shutdown-threshold stp 10 Router(config-if)# no l2protocol-tunnel shutdown-threshold vtp 10 Router(config-if)# no l2protocol-tunnel cdp Router(config-if)# no l2protocol-tunnel stp Router(config-if)# no l2protocol-tunnel vtp Router(config-if)# end Router# show l2protocol-tunnel summary Port Protocol Threshold (cos/cdp/stp/vtp) ---------------------------------------Router#
This example shows how to clear Layer 2 protocol tunneling port counters:
Router# clear l2protocol-tunnel counters Router#
Tip
18-4
OL-3999-08
C H A P T E R
19
Configuring Standard-Compliant IEEE MST

This chapter describes how to configure the standard-compliant IEEE Multiple Spanning Tree (MST) protocol on Catalyst 6500 series switches.
Note
The IEEE MST protocol has transitioned from a prestandard state to a released state. This chapter describes the standard-compliant MST implementation supported in Release 12.2(18)SXF and later releases. Chapter 20, Configuring STP and Prestandard IEEE 802.1s MST, describes the prestandard MST implementation supported in releases earlier than Release 12.2(18)SXF. For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html

Understanding MST, page 19-1 Understanding RSTP, page 19-9 Configuring MST, page 19-15 Displaying the MST Configuration and Status, page 19-28
Tip
Understanding MST
These sections describe MST:

MST Overview, page 19-2 MST Regions, page 19-2 IST, CIST, and CST, page 19-3
19-1
Chapter 19 Understanding MST
Hop Count, page 19-6 Boundary Ports, page 19-6 Standard-Compliant MST Implementation, page 19-7 Interoperability with IEEE 802.1D-1998 STP, page 19-9
MST Overview
MST maps multiple VLANs into a spanning tree instance, with each instance having a spanning tree topology independent of other spanning tree instances. This architecture provides multiple forwarding paths for data traffic, enables load balancing, and reduces the number of spanning tree instances required to support a large number of VLANs. MST improves the fault tolerance of the network because a failure in one instance (forwarding path) does not affect other instances (forwarding paths). The most common initial deployment of MST is in the backbone and distribution layers of a Layer 2 switched network. This deployment provides the kind of highly available network that is required in a service-provider environment. MST provides rapid spanning tree convergence through explicit handshaking, which eliminates the 802.1D forwarding delay and quickly transitions root bridge ports and designated ports to the forwarding state. MST improves spanning tree operation and maintains backward compatibility with these STP versions:

Original 802.1D spanning tree Existing Cisco-proprietary Multiple Instance STP (MISTP) Existing Cisco per-VLAN spanning tree plus (PVST+) Rapid per-VLAN spanning tree plus (rapid PVST+)
For information about PVST+ and rapid PVST+, see Chapter 20, Configuring STP and Prestandard IEEE 802.1s MST. For information about other spanning tree features such as Port Fast, UplinkFast, root guard, and so forth, see Chapter 21, Configuring Optional STP Features.
Note
IEEE 802.1w defined the Rapid Spanning Tree Protocol (RSTP) and was incorporated into IEEE 802.1D. IEEE 802.1s defined MST and was incorporated into IEEE 802.1Q.
MST Regions
For switches to participate in MST instances, you must consistently configure the switches with the same MST configuration information. A collection of interconnected switches that have the same MST configuration comprises an MST region as shown in Figure 19-1 on page 19-5. The MST configuration controls to which MST region each switch belongs. The configuration includes the name of the region, the revision number, and the MST VLAN-to-instance assignment map.
19-2
OL-3999-08
Chapter 19
Configuring Standard-Compliant IEEE MST Understanding MST
A region can have one or multiple members with the same MST configuration; each member must be capable of processing RSTP bridge protocol data units (BPDUs). There is no limit to the number of MST regions in a network, but each region can support up to 65 spanning tree instances. Instances can be identified by any number in the range from 0 to 4094. You can assign a VLAN to only one spanning tree instance at a time.
IST, CIST, and CST

These sections describe internal spanning tree (IST), common and internal spanning tree (CIST), and common spanning tree (CST):

IST, CIST, and CST Overview, page 19-3 Spanning Tree Operation Within an MST Region, page 19-4 Spanning Tree Operations Between MST Regions, page 19-4 IEEE 802.1s Terminology, page 19-5
IST, CIST, and CST Overview

Unlike other spanning tree protocols, in which all the spanning tree instances are independent, MST establishes and maintains IST, CIST, and CST spanning trees:
An IST is the spanning tree that runs in an MST region. Within each MST region, MST maintains multiple spanning tree instances. Instance 0 is a special instance for a region, known as the IST. All other MST instances are numbered from 1 to 4094. The IST is the only spanning tree instance that sends and receives BPDUs. All of the other spanning tree instance information is contained in MSTP records (M-records), which are encapsulated within MST BPDUs. Because the MST BPDU carries information for all instances, the number of BPDUs that need to be processed to support multiple spanning tree instances is significantly reduced. All MST instances within the same region share the same protocol timers, but each MST instance has its own topology parameters, such as root bridge ID, root path cost, and so forth. By default, all VLANs are assigned to the IST. An MST instance is local to the region; for example, MST instance 1 in region A is independent of MST instance 1 in region B, even if regions A and B are interconnected.
A CIST is a collection of the ISTs in each MST region. The CST interconnects the MST regions and single spanning trees.
The spanning tree computed in a region appears as a subtree in the CST that encompasses the entire switched domain. The CIST is formed by the spanning tree algorithm running among switches that support the 802.1w, 802.1s, and 802.1D standards. The CIST inside an MST region is the same as the CST outside a region. For more information, see the Spanning Tree Operation Within an MST Region section on page 19-4 and the Spanning Tree Operations Between MST Regions section on page 19-4.
19-3
Spanning Tree Operation Within an MST Region

The IST connects all the MST switches in a region. When the IST converges, the root of the IST becomes the CIST regional root (called the IST master before the implementation of the 802.1s standard) as shown in Figure 19-1 on page 19-5. The CIST regional root is also the CIST root if there is only one region in the network. If the CIST root is outside the region, one of the MST switches at the boundary of the region is selected as the CIST regional root. When an MST switch initializes, it sends BPDUs that identify itself as the root of the CIST and the CIST regional root, with both of the path costs to the CIST root and to the CIST regional root set to zero. The switch also initializes all of its MST instances and claims to be the root for all of them. If the switch receives superior MST root information (lower switch ID, lower path cost, and so forth) than currently stored for the port, it relinquishes its claim as the CIST regional root. During initialization, a region might have many subregions, each with its own CIST regional root. As switches receive superior IST information from a neighbor in the same region, they leave their old subregions and join the new subregion that contains the true CIST regional root, which causes all subregions to shrink except for the one that contains the true CIST regional root. For correct operation, all switches in the MST region must agree on the same CIST regional root. Therefore, any two switches in the region only synchronize their port roles for an MST instance if they converge to a common CIST regional root.
Spanning Tree Operations Between MST Regions

If there are multiple regions or 802.1D switches within the network, MST establishes and maintains the CST, which includes all MST regions and all 802.1D STP switches in the network. The MST instances combine with the IST at the boundary of the region to become the CST. The IST connects all the MST switches in the region and appears as a subtree in the CIST that encompasses the entire switched domain. The root of the subtree is the CIST regional root. The MST region appears as a virtual switch to adjacent STP switches and MST regions. Figure 19-1 shows a network with three MST regions and an 802.1D switch (D). The CIST regional root for region 1 (A) is also the CIST root. The CIST regional root for region 2 (B) and the CIST regional root for region 3 (C) are the roots for their respective subtrees within the CIST.
19-4
OL-3999-08
Chapter 19
Figure 19-1 MST Regions, CIST Regional Roots, and CST Root
A CIST Regional Root and CST root
D Legacy 802.1D MST Region 1
CIST Regional Root
CIST Regional Root
Only the CST instance sends and receives BPDUs, and MST instances add their spanning tree information into the BPDUs to interact with neighboring switches and compute the final spanning tree topology. Because of this, the spanning tree parameters related to BPDU transmission (for example, hello time, forward time, max-age, and max-hops) are configured only on the CST instance but affect all MST instances. Parameters related to the spanning tree topology (for example, switch priority, port VLAN cost, and port VLAN priority) can be configured on both the CST instance and the MST instance. MST switches use Version 3 BPDUs or 802.1D STP BPDUs to communicate with 802.1D switches. MST switches use MST BPDUs to communicate with MST switches.
IEEE 802.1s Terminology

Some MST naming conventions used in the prestandard implementation have been changed to include identification of some internal and regional parameters. These parameters are used only within an MST region, compared to external parameters that are used throughout the whole network. Because the CIST is the only spanning tree instance that spans the whole network, only the CIST parameters require the external qualifiers and not the internal or regional qualifiers.

The CIST root is the root bridge for the the CIST, which is the unique instance that spans the whole network. The CIST external root path cost is the cost to the CIST root. This cost is left unchanged within an MST region. Remember that an MST region looks like a single switch to the CIST. The CIST external root path cost is the root path cost calculated between these virtual switches and switches that do not belong to any region.
19-5
92720
MST Region 2
MST Region 3
The CIST regional root was called the IST master in the prestandard implementation. If the CIST root is in the region, the CIST regional root is the CIST root. Otherwise, the CIST regional root is the closest switch to the CIST root in the region. The CIST regional root acts as a root bridge for the IST. The CIST internal root path cost is the cost to the CIST regional root in a region. This cost is only relevant to the IST, instance 0.
Table 19-1 compares the IEEE standard and the Cisco prestandard terminology.
Table 19-1 Prestandard and Standard Terminology
IEEE Standard Definition CIST regional root CIST internal root path cost CIST external root path cost MSTI regional root MSTI internal root path cost
Cisco Prestandard Implementation IST master IST master path cost Root path cost Instance root Root path cost
Cisco Standard Implementation CIST regional root CIST internal path cost Root path cost Instance root Root path cost
Hop Count
MST does not use the message-age and maximum-age information in the configuration BPDU to compute the spanning tree topology. Instead, they use the path cost to the root and a hop-count mechanism similar to the IP time-to-live (TTL) mechanism. By using the spanning-tree mst max-hops global configuration command, you can configure the maximum hops inside the region and apply it to the IST and all MST instances in that region. The hop count achieves the same result as the message-age information (triggers a reconfiguration). The root bridge of the instance always sends a BPDU (or M-record) with a cost of 0 and the hop count set to the maximum value. When a switch receives this BPDU, it decrements the received remaining hop count by one and propagates this value as the remaining hop count in the BPDUs it generates. When the count reaches zero, the switch discards the BPDU and ages the information held for the port. The message-age and maximum-age information in the RSTP portion of the BPDU remain the same throughout the region, and the same values are propagated by the region-designated ports at the boundary.
Boundary Ports
In the Cisco prestandard implementation, a boundary port connects an MST region to one of these STP regions:

A single spanning tree region running RSTP A single spanning tree region running PVST+ or rapid PVST+ Another MST region with a different MST configuration
A boundary port also connects to a LAN, the designated switch of which is either a single spanning tree switch or a switch with a different MST configuration. There is no definition of a boundary port in the 802.1s standard. The 802.1Q-2002 standard identifies two kinds of messages that a port can receive: internal (coming from the same region) and external. When a message is external, it is received only by the CIST. If the CIST role is root or alternate, or if
19-6
OL-3999-08
Chapter 19
the external BPDU is a topology change, it could have an impact on the MST instances. When a message is internal, the CIST part is received by the CIST, and each MST instance receives its respective M-record. The Cisco prestandard implementation treats a port that receives an external message as a boundary port, which means a port cannot receive a mix of internal and external messages. An MST region includes both switches and LANs. A segment belongs to the region of its designated port. Therefore, a port in a different region from the designated port for a segment is a boundary port. This definition allows two ports internal to a region to share a segment with a port belonging to a different region, creating the possibility of receiving both internal and external messages on a port. The primary change from the Cisco prestandard implementation is that a designated port is not defined as boundary unless it is running in an STP-compatible mode.
Note
If there is an 802.1D STP switch on the segment, messages are always considered external. The other change from the prestandard implementation is that the CIST regional root bridge ID field is now inserted where an RSTP or legacy 802.1s switch has the sender switch ID. The whole region performs like a single virtual switch by sending a consistent sender switch ID to neighboring switches. In this example, switch C would receive a BPDU with the same consistent sender switch ID of root, whether or not A or B is designated for the segment.
Standard-Compliant MST Implementation

The standard-compliant MST implementation includes features required to meet the standard, as well as some of the desirable prestandard functionality that is not yet incorporated into the published standard. These sections describe the standard-compliant MST implementation:

Changes in Port-Role Naming, page 19-7 Spanning Tree Interoperation Between Legacy and Standard-Compliant Switches, page 19-8 Detecting Unidirectional Link Failure, page 19-8
Changes in Port-Role Naming

The boundary role was deleted from the final MST standard, but this boundary concept is maintained in the standard-compliant implementation. However, an MST instance (MSTI) port at a boundary of the region might not follow the state of the corresponding CIST port. The following two situations currently exist:
The boundary port is the root port of the CIST regional rootWhen the CIST instance port is proposed and is synchronized, it can send back an agreement and move to the forwarding state only after all the corresponding MSTI ports are synchronized (and thus forwarding). The MSTI ports now have a special master role. The boundary port is not the root port of the CIST regional rootThe MSTI ports follow the state and role of the CIST port. The standard provides less information, and it might be difficult to understand why an MSTI port can be alternately blocking when it receives no BPDUs (M-records). In this situation, although the boundary role no longer exists, when you enter the show commands, they identify a port as boundary in the type column of the output.
19-7
Spanning Tree Interoperation Between Legacy and Standard-Compliant Switches

Because automatic detection of prestandard switches can fail, you can use an interface configuration command to identify prestandard ports. A region cannot be formed between a standard and a prestandard switch, but they can interoperate before using the CIST. Only the capability of load balancing over different instances is lost in this specific situation. The CLI displays different flags depending on the port configuration when the port receives prestandard BPDUs. A syslog message also appears the first time a switch receives a prestandard BPDU on a port that has not been configured for prestandard BPDU transmission. Figure 19-2 illustrates a standard-compliant switch connected to a prestandard switch. Assume that A is the standard-compliant switch and B is a prestandard switch, both configured to be in the same region. A is the root bridge for the CIST, and so B has a root port (BX) on segment X and an alternate port (BY) on segment Y. If segment Y flaps, and the port on BY becomes the alternate before sending out a single prestandard BPDU, AY cannot detect that a prestandard switch is connected to Y and continues to send standard BPDUs. The port BY is fixed in a boundary, and no load balancing is possible between A and B. The same problem exists on segment X, but B might transmit topology changes.
Figure 19-2 Standard-Compliant and Prestandard Switch Interoperation
Segment X
MST Region
Switch A Switch B
Segment Y
Note
We recommend that you minimize the interaction between standard and prestandard MST implementations.
Detecting Unidirectional Link Failure

This feature is not yet present in the IEEE MST standard, but it is included in the standard-compliant implemtation. The software checks the consistency of the port role and state in the received BPDUs to detect unidirectional link failures that could cause bridging loops. When a designated port detects a conflict, it keeps its role, but reverts to a discarding state because disrupting connectivity in case of inconsistency is preferable to opening a bridging loop. Figure 19-3 illustrates a unidirectional link failure that typically creates a bridging loop. Switch A is the root bridge, and its BPDUs are lost on the link leading to switch B. RSTP and MST BPDUs include the role and state of the sending port. With this information, switch A can detect that switch B does not react to the superior BPDUs it sends and that switch B is the designated, not root bridge. As a result, switch A blocks (or keeps blocking) its port, thus preventing the bridging loop.
19-8
92721
OL-3999-08
Chapter 19
Configuring Standard-Compliant IEEE MST Understanding RSTP
Figure 19-3 Detecting Unidirectional Link Failure
Switch A
Superior BPDU
Switch B
Inferior BPDU, Designated + Learning bit set
Interoperability with IEEE 802.1D-1998 STP

A switch running MST supports a built-in protocol migration feature that enables it to interoperate with 802.1D switches. If this switch receives an 802.1D configuration BPDU (a BPDU with the protocol version set to 0), it sends only 802.1D BPDUs on that port. An MST switch also can detect that a port is at the boundary of a region when it receives an 802.1D BPDU, an MST BPDU (Version 3) associated with a different region, or an RSTP BPDU (Version 2). However, the switch does not automatically revert to the MST mode if it no longer receives 802.1D BPDUs because it cannot detect whether the 802.1D switch has been removed from the link unless the 802.1D switch is the designated switch. A switch might also continue to assign a boundary role to a port when the switch to which this switch is connected has joined the region. To restart the protocol migration process (force the renegotiation with neighboring switches), use the clear spanning-tree detected-protocols privileged EXEC command. If all the 802.1D switches on the link are RSTP switches, they can process MST BPDUs as if they are RSTP BPDUs. Therefore, MST switches send either a Version 0 configuration and topology change notification (TCN) BPDUs or Version 3 MST BPDUs on a boundary port. A boundary port connects to a LAN, the designated switch of which is either a single spanning tree switch or a switch with a different MST configuration.
Understanding RSTP
RSTP takes advantage of point-to-point wiring and provides rapid convergence of the spanning tree. Reconfiguration of the spanning tree can occur in less than 1 second (in contrast to 50 seconds with the default settings in the 802.1D spanning tree). These section describes how the RSTP works:

Port Roles and the Active Topology, page 19-10 Rapid Convergence, page 19-11 Synchronization of Port Roles, page 19-12 Bridge Protocol Data Unit Format and Processing, page 19-13
92722
19-9
Chapter 19 Understanding RSTP
Port Roles and the Active Topology

The RSTP provides rapid convergence of the spanning tree by assigning port roles and by learning the active topology. The RSTP builds upon the 802.1D STP to select the switch with the highest switch priority (lowest numerical priority value) as the root bridge as described in the Election of the Root Bridge section on page 20-4. The RSTP then assigns one of these port roles to individual ports:

Root portProvides the best path (lowest cost) when the switch forwards packets to the root bridge. Designated portConnects to the designated switch, which incurs the lowest path cost when forwarding packets from that LAN to the root bridge. The port through which the designated switch is attached to the LAN is called the designated port. Alternate portOffers an alternate path toward the root bridge to that provided by the current root port. Backup portActs as a backup for the path provided by a designated port toward the leaves of the spanning tree. A backup port can exist only when two ports are connected in a loopback by a point-to-point link or when a switch has two or more connections to a shared LAN segment. Disabled portHas no role within the operation of the spanning tree.
A port with the root or a designated port role is included in the active topology. A port with the alternate or backup port role is excluded from the active topology. In a stable topology with consistent port roles throughout the network, the RSTP ensures that every root port and designated port immediately transition to the forwarding state while all alternate and backup ports are always in the discarding state (equivalent to blocking in 802.1D). The port state controls the operation of the forwarding and learning processes. Table 19-2 provides a comparison of 802.1D and RSTP port states.
Table 19-2 Port State Comparison
Operational Status Enabled Enabled Enabled Enabled Disabled
STP Port State (IEEE 802.1D) Blocking Listening Learning Forwarding Disabled
RSTP Port State Discarding Discarding Learning Forwarding Discarding
Is Port Included in the Active Topology? No No Yes Yes No
To be consistent with Cisco STP implementations, this guide defines the port state as blocking instead of discarding. Designated ports start in the listening state.
19-10
OL-3999-08
Chapter 19
Rapid Convergence
The RSTP provides for rapid recovery of connectivity following the failure of a switch, a switch port, or a LAN. It provides rapid convergence for edge ports, new root ports, and ports connected through point-to-point links as follows:
Edge portsIf you configure a port as an edge port on an RSTP switch by using the spanning-tree portfast interface configuration command, the edge port immediately transitions to the forwarding state. An edge port is the same as a Port Fast-enabled port, and you should enable it only on ports that connect to a single end station. Root portsIf the RSTP selects a new root port, it blocks the old root port and immediately transitions the new root port to the forwarding state. Point-to-point linksIf you connect a port to another port through a point-to-point link and the local port becomes a designated port, it negotiates a rapid transition with the other port by using the proposal-agreement handshake to ensure a loop-free topology. As shown in Figure 19-4, switch A is connected to switch B through a point-to-point link, and all of the ports are in the blocking state. Assume that the priority of switch A is a smaller numerical value than the priority of switch B. Switch A sends a proposal message (a configuration BPDU with the proposal flag set) to switch B, proposing itself as the designated switch. After receiving the proposal message, switch B selects as its new root port the port from which the proposal message was received, forces all nonedge ports to the blocking state, and sends an agreement message (a BPDU with the agreement flag set) through its new root port. After receiving switch Bs agreement message, switch A also immediately transitions its designated port to the forwarding state. No loops in the network are formed because switch B blocked all of its nonedge ports and because there is a point-to-point link between switches A and B. When switch C is connected to switch B, a similar set of handshaking messages are exchanged. Switch C selects the port connected to switch B as its root port, and both ends immediately transition to the forwarding state. With each iteration of this handshaking process, one more switch joins the active topology. As the network converges, this proposal-agreement handshaking progresses from the root toward the leaves of the spanning tree. The switch learns the link type from the port duplex mode: a full-duplex port is considered to have a point-to-point connection and a half-duplex port is considered to have a shared connection. You can override the default setting that is controlled by the duplex setting by using the spanning-tree link-type interface configuration command.
19-11
Figure 19-4 Proposal and Agreement Handshaking for Rapid Convergence
Switch A
Proposal
Switch B
Root F DP Root F DP Root F DP
Agreement
Designated switch F RP Designated switch F RP Designated switch F RP F DP Switch C
Proposal
Agreement
F RP
DP = designated port RP = root port F = forwarding
Synchronization of Port Roles

When the switch receives a proposal message on one of its ports and that port is selected as the new root port, the RSTP forces all other ports to synchronize with the new root information. The switch is synchronized with superior root information received on the root port if all other ports are synchronized. An individual port on the switch is synchronized if:

That port is in the blocking state. It is an edge port (a port configured to be at the edge of the network).
If a designated port is in the forwarding state and is not configured as an edge port, it transitions to the blocking state when the RSTP forces it to synchronize with new root information. In general, when the RSTP forces a port to synchronize with root information and the port does not satisfy any of the above conditions, its port state is set to blocking. After ensuring that all of the ports are synchronized, the switch sends an agreement message to the designated switch corresponding to its root port. When the switches connected by a point-to-point link are in agreement about their port roles, the RSTP immediately transitions the port states to forwarding. The sequence of events is shown in Figure 19-5.
19-12
88760
OL-3999-08
Chapter 19
Figure 19-5 Sequence of Events During Rapid Convergence
4. Agreement
1. Proposal
5. Forward Edge port
2. Block 9. Forward
3. Block 11. Forward
8. Agreement
6. Proposal
7. Proposal Root port Designated port
10. Agreement
88761
Bridge Protocol Data Unit Format and Processing

These sections describe bridge protocol data unit (BPDU) format and processing:

BPDU Format and Processing Overview, page 19-13 Processing Superior BPDU Information, page 19-14 Processing Inferior BPDU Information, page 19-14
BPDU Format and Processing Overview

The RSTP BPDU format is the same as the 802.1D BPDU format except that the protocol version is set to 2. A new 1-byte Version 1 Length field is set to zero, which means that no Version 1 protocol information is present. Table 19-3 describes the RSTP flag fields.
Table 19-3 RSTP BPDU Flags
Bit 0 1 23: 00 01 10 11 4 5
Function Topology change (TC) Proposal Port role: Unknown Alternate port or backup port Root port Designated port Learning Forwarding
19-13
Table 19-3 RSTP BPDU Flags (continued)
Bit 6 7
Function Agreement Topology change acknowledgement (TCA)
The sending switch sets the proposal flag in the RSTP BPDU to propose itself as the designated switch on that LAN. The port role in the proposal message is always set to the designated port. The sending switch sets the agreement flag in the RSTP BPDU to accept the previous proposal. The port role in the agreement message is always set to the root port. The RSTP does not have a separate TCN BPDU. It uses the topology change (TC) flag to show the topology changes. However, for interoperability with 802.1D switches, the RSTP switch processes and generates TCN BPDUs. The learning and forwarding flags are set according to the state of the sending port.
Processing Superior BPDU Information

A superior BPDU is a BPDU with root information (such as lower switch ID or lower path cost) that is superior to what is currently stored for the port. If a port receives a superior BPDU, the RSTP triggers a reconfiguration. If the port is proposed and is selected as the new root port, RSTP forces all the other ports to synchronize. If the BPDU received is an RSTP BPDU with the proposal flag set, the switch sends an agreement message after all of the other ports are synchronized. If the BPDU is an 802.1D BPDU, the switch does not set the proposal flag and starts the forward-delay timer for the port. The new root port requires twice the forward-delay time to transition to the forwarding state. If the superior information received on the port causes the port to become a backup port or an alternate port, RSTP sets the port to the blocking state and sends an agreement message. The designated port continues sending BPDUs with the proposal flag set until the forward-delay timer expires, at which time the port transitions to the forwarding state.
Processing Inferior BPDU Information

An inferior BPDU is a BPDU with root information (such as higher switch ID or higher path cost) that is inferior to what is currently stored for the port. If a designated port receives an inferior BPDU, it immediately replies with its own information.
19-14
OL-3999-08
Chapter 19
Configuring Standard-Compliant IEEE MST Configuring MST
Topology Changes
These are the differences between the RSTP and the 802.1D in handling spanning tree topology changes:
DetectionUnlike 802.1D in which any transition between the blocking and the forwarding state causes a topology change, only transitions from the blocking to the forwarding state cause a topology change with RSTP (only an increase in connectivity is considered a topology change). State changes on an edge port do not cause a topology change. When an RSTP switch detects a topology change, it deletes the learned information on all of its nonedge ports except on those from which it received the TC notification. NotificationThe RSTP does not use TCN BPDUs, unlike 802.1D. However, for 802.1D interoperability, an RSTP switch processes and generates TCN BPDUs. AcknowledgementWhen an RSTP switch receives a TCN message on a designated port from an 802.1D switch, it replies with an 802.1D configuration BPDU with the TCA bit set. However, if the TC-while timer (the same as the TC timer in 802.1D) is active on a root port connected to an 802.1D switch and a configuration BPDU with the TCA set is received, the TC-while timer is reset. This method of operation is only required to support 802.1D switches. The RSTP BPDUs never have the TCA bit set.
PropagationWhen an RSTP switch receives a TC message from another switch through a designated or root port, it propagates the change to all of its nonedge, designated ports and to the root port (excluding the port on which it is received). The switch starts the TC-while timer for all such ports and flushes the information learned on them. Protocol migrationFor backward compatibility with 802.1D switches, RSTP selectively sends 802.1D configuration BPDUs and TCN BPDUs on a per-port basis. When a port is initialized, the migrate-delay timer is started (specifies the minimum time during which RSTP BPDUs are sent), and RSTP BPDUs are sent. While this timer is active, the switch processes all BPDUs received on that port and ignores the protocol type. If the switch receives an 802.1D BPDU after the port migration-delay timer has expired, it assumes that it is connected to an 802.1D switch and starts using only 802.1D BPDUs. However, if the RSTP switch is using 802.1D BPDUs on a port and receives an RSTP BPDU after the timer has expired, it restarts the timer and starts using RSTP BPDUs on that port.
Configuring MST
These sections describe how to configure MST:

Default MST Configuration, page 19-16 MST Configuration Guidelines and Restrictions, page 19-16 Specifying the MST Region Configuration and Enabling MST, page 19-17 (required) Configuring the Root Bridge, page 19-19 (optional) Configuring a Secondary Root Bridge, page 19-20 (optional) Configuring Port Priority, page 19-21 (optional) Configuring Path Cost, page 19-22 (optional) Configuring the Switch Priority, page 19-23 (optional) Configuring the Hello Time, page 19-24 (optional)
19-15
Chapter 19 Configuring MST
Configuring the Transmit Hold Count, page 19-25 (optional) Configuring the Maximum-Aging Time, page 19-26 (optional) Configuring the Maximum-Hop Count, page 19-26 (optional) Specifying the Link Type to Ensure Rapid Transitions, page 19-26 (optional) Designating the Neighbor Type, page 19-27 (optional) Restarting the Protocol Migration Process, page 19-28 (optional)
Default MST Configuration

Table 19-4 shows the default MST configuration.
Table 19-4 Default MST Configuration
Feature spanning tree mode Switch priority (configurable on a per-CIST port basis) spanning tree port priority (configurable on a per-CIST port basis) spanning tree port cost (configurable on a per-CIST port basis)
Default Setting PVST+ (Rapid PVST+ and MST are disabled) 32768 128 1000 Mbps: 4 100 Mbps: 19 10 Mbps: 100
Hello time Forward-delay time Maximum-aging time Maximum hop count
2 seconds 15 seconds 20 seconds 20 hops
MST Configuration Guidelines and Restrictions

When configuring MST, follow these guidelines and restrictions:

The 802.1s MST standard allows up to 65 MST instances. You can map an unlimited number of VLANs to an MST instance. PVST+, rapid PVST+, and MST are supported, but only one version can be active at any time. VTP does not propagate the MST configuration. You must manually configure the MST configuration (region name, revision number, and VLAN-to-instance mapping) on each switch within the MST region through the command-line interface (CLI) or SNMP. For load balancing across redundant paths in the network to work, all VLAN-to-instance mapping assignments must match; otherwise, all traffic flows on a single link. All MST boundary ports must be forwarding for load balancing between a PVST+ and an MST cloud or between a rapid-PVST+ and an MST cloud. For this to occur, the CIST regional root of the MST cloud must be the root of the CST. If the MST cloud consists of multiple MST regions, one of the MST regions must contain the CST root, and all of the other MST regions must have a better path to the root contained within the MST cloud than a path through the PVST+ or rapid-PVST+ cloud.
19-16
OL-3999-08
Chapter 19
Partitioning the network into a large number of regions is not recommended. However, if this situation is unavoidable, we recommend that you partition the switched LAN into smaller LANs interconnected by non-Layer 2 devices. Adding or removing VLANs to an existing MST instance will trigger spanning tree recalculation for that MST instance, and the traffic of all the VLANs for that MST instance will be disrupted.
Specifying the MST Region Configuration and Enabling MST

For two or more switches to be in the same MST region, they must have the same VLAN-to-instance mapping, the same configuration revision number, and the same MST name. A region can have one member or multiple members with the same MST configuration; each member must be capable of processing RSTP BPDUs. There is no limit to the number of MST regions in a network, but each region can only support up to 65 spanning tree instances. You can assign a VLAN to only one spanning tree instance at a time. To specify the MST region configuration and enable MST, perform this task: Command
Router# configure terminal Router(config)# spanning-tree mst configuration Router(config-mst)# instance instance_id vlan vlan_range
Purpose Enters global configuration mode. Enters MST configuration mode. Maps VLANs to an MST instance.

For instance_id, the range is 0 to 4094. For vlan vlan_range, the range is 1 to 4094. When you map VLANs to an MST instance, the mapping is incremental, and the VLANs specified in the command are added to or removed from the VLANs that were previously mapped.
To specify a VLAN range, use a hyphen; for example, instance 1 vlan 1-63 maps VLANs 1 through 63 to MST instance 1. To specify a VLAN series, use a comma; for example, instance 1 vlan 10, 20, 30 maps VLANs 10, 20, and 30 to MST instance 1.
Router(config-mst)# name instance_name
Specifies the instance name. The name string has a maximum length of 32 characters and is case sensitive. Specifies the configuration revision number. The range is 0 to 65535. Verifies your configuration by displaying the pending configuration. Applies all changes, and return to global configuration mode.
Router(config-mst)# revision version
Router(config-mst)# show pending
Router(config)# exit
19-17
Command
Step 8
Router(config)# spanning-tree mode mst
Purpose Enables MST and RSTP.
Caution
Changing the spanning tree mode can disrupt traffic because all spanning tree instances are stopped for the previous mode and restarted in the new mode.
You cannot run both MST and PVST+ or both MST and rapid PVST+ at the same time.
Router(config)# end Router# show running-config Router# copy running-config startup-config
Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
To return to defaults, do the following:

To return to the default MST region configuration, use the no spanning-tree mst configuration global configuration command. To return to the default VLAN-to-instance map, use the no instance instance_id [vlan vlan_range] MST configuration command. To return to the default name, use the no name MST configuration command. To return to the default revision number, use the no revision MST configuration command. To reenable PVST+, use the no spanning-tree mode or the spanning-tree mode pvst global configuration command.
This example shows how to enter MST configuration mode, map VLANs 10 to 20 to MST instance 1, name the region region1, set the configuration revision to 1, display the pending configuration, apply the changes, and return to global configuration mode:
Router(config)# spanning-tree mst configuration Router(config-mst)# instance 1 vlan 10-20 Router(config-mst)# name region1 Router(config-mst)# revision 1 Router(config-mst)# show pending Pending MST configuration Name [region1] Revision 1 Instances configured 2 Instance Vlans Mapped -------- --------------------0 1-9,21-4094 1 10-20 ------------------------------Router(config-mst)# exit Router(config)#
19-18
OL-3999-08
Chapter 19
Configuring the Root Bridge

The switch maintains a spanning tree instance for the group of VLANs mapped to it. A switch ID, consisting of the switch priority and the switch MAC address, is associated with each instance. For a group of VLANs, the switch with the lowest switch ID becomes the root bridge. To configure a switch to become the root bridge, use the spanning-tree mst instance_id root global configuration command to modify the switch priority from the default value (32768) to a significantly lower value so that the switch becomes the root bridge for the specified spanning tree instance. When you enter this command, the switch checks the switch priorities of the root bridges. Because of the extended system ID support, the switch sets its own priority for the specified instance to 24576 if this value will cause this switch to become the root bridge for the specified spanning tree instance. If any root bridge for the specified instance has a switch priority lower than 24576, the switch sets its own priority to 4096 less than the lowest switch priority. (4096 is the value of the least-significant bit of a 4-bit switch priority value as shown in Table 20-2 on page 20-3.) If your network consists of switches that both do and do not support the extended system ID, it is unlikely that the switch with the extended system ID support will become the root bridge. The extended system ID increases the switch priority value every time the VLAN number is greater than the priority of the connected switches running older software. The root bridge for each spanning tree instance should be a backbone or distribution switch. Do not configure an access switch as the spanning tree primary root bridge. Use the diameter keyword, which is available only for MST instance 0, to specify the Layer 2 network diameter (that is, the maximum number of Layer 2 hops between any two end stations in the Layer 2 network). When you specify the network diameter, the switch automatically sets an optimal hello time, forward-delay time, and maximum-age time for a network of that diameter, which can significantly reduce the convergence time. You can use the hello keyword to override the automatically calculated hello time.
Note
With the switch configured as the root bridge, do not manually configure the hello time, forward-delay time, and maximum-age time with the spanning-tree mst hello-time, spanning-tree mst forward-time, and spanning-tree mst max-age global configuration commands.
19-19
To configure a switch as the root bridge, perform this task: Command

Step 1 Step 2
Router(config)# configure terminal Router(config-config)# spanning-tree mst instance_id root primary [diameter net_diameter [hello-time seconds]]
Purpose Enters global configuration mode. (Optional) Configures a switch as the root bridge.
For instance_id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is 0 to 4094. (Optional) For diameter net_diameter, specify the maximum number of Layer 2 hops between any two end stations. The range is 2 to 7. This keyword is available only for MST instance 0. (Optional) For hello-time seconds, specify the interval in seconds between the generation of configuration messages by the root bridge. The range is 1 to 10 seconds; the default is 2 seconds.
Router(config-config)# end Router# show spanning-tree mst instance_id Router# copy running-config startup-config
To return the switch to its default setting, use the no spanning-tree mst instance_id root global configuration command.
Configuring a Secondary Root Bridge

When you configure a switch with the extended system ID support as the secondary root, the switch priority is modified from the default value (32768) to 28672. The switch is then likely to become the root bridge for the specified instance if the primary root bridge fails. This is assuming that the other network switches use the default switch priority of 32768 and therefore are unlikely to become the root bridge. You can execute this command on more than one switch to configure multiple backup root bridges. Use the same network diameter and hello-time values that you used when you configured the primary root bridge with the spanning-tree mst instance_id root primary global configuration command.
19-20
OL-3999-08
Chapter 19
To configure a switch as the secondary root bridge, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree mst instance_id root secondary [ diameter net_diameter [hello-time seconds]]
Purpose Enters global configuration mode. (Optional) Configures a switch as the secondary root bridge.
For instance_id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is 0 to 4094. (Optional) For diameter net_diameter, specify the maximum number of switches between any two end stations. The range is 2 to 7. This keyword is available only for MST instance 0. (Optional) For hello-time seconds , specify the interval in seconds between the generation of configuration messages by the root bridge. The range is 1 to 10 seconds; the default is 2 seconds.
Use the same network diameter and hello-time values that you used when configuring the primary root bridge. See the Configuring the Root Bridge section on page 19-19.
Router(config)# end Router# show spanning-tree mst instance_id Router# copy running-config startup-config
To return the switch to its default setting, use the no spanning-tree mst instance_id root global configuration command.
Configuring Port Priority

If a loop occurs, MST uses the port priority when selecting an interface to put into the forwarding state. You can assign higher priority values (lower numerical values) to interfaces that you want selected first and lower priority values (higher numerical values) that you want selected last. If all interfaces have the same priority value, MST puts the interface with the lowest interface number in the forwarding state and blocks the other interfaces. To configure the MST port priority of an interface, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# interface {{type {port-channel number}}
1

slot/port} |
(Optional) Specifies an interface to configure, and enters interface configuration mode.
19-21
Command
Step 3
Router(config-if)# spanning-tree mst instance_id port-priority priority
Purpose Configures the port priority.
For instance_id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is 0 to 4094. For priority, the range is 0 to 240 in increments of 16. The default is 128. The lower the number, the higher the priority. The priority values are 0, 16, 32, 48, 64, 80, 96, 112, 128, 144, 160, 176, 192, 208, 224, and 240. All other values are rejected.
Step 4 Step 5
Router(config-if)# end Router# show spanning-tree mst interface interface_id or Router# show spanning-tree mst instance_id Router# copy running-config startup-config 1.
Returns to privileged EXEC mode. Verifies your entries.
Step 6
(Optional) Saves your entries in the configuration file.
Note
The show spanning-tree mst interface interface_id privileged EXEC command displays information only if the port is in a link-up operative state. Otherwise, you can use the show running-config interface privileged EXEC command to confirm the configuration. To return the interface to its default setting, use the no spanning-tree mst instance_id port-priority interface configuration command.
Configuring Path Cost

The MST path cost default value is derived from the media speed of an interface. If a loop occurs, MST uses cost when selecting an interface to put in the forwarding state. You can assign lower cost values to interfaces that you want selected first and higher cost values that you want selected last. If all interfaces have the same cost value, MST puts the interface with the lowest interface number in the forwarding state and blocks the other interfaces. To configure the MST cost of an interface, perform this task: Command
Step 1 Step 2
1

slot/port} |
(Optional) Specifies an interface to configure, and enters interface configuration mode.
19-22
OL-3999-08
Chapter 19
Command
Step 3
Router(config-if)# spanning-tree mst instance_id cost cost
Purpose Configures the cost. If a loop occurs, MST uses the path cost when selecting an interface to place into the forwarding state. A lower path cost represents higher-speed transmission.
For instance_id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is 0 to 4094. For cost, the range is 1 to 200000000; the default value is derived from the media speed of the interface.
Step 4 Step 5
Router(config-if)# end Router# show spanning-tree mst interface interface_id
Returns to privileged EXEC mode. Verifies your entries.
or
Router# show spanning-tree mst instance_id
Step 6
Router# copy running-config startup-config 1.
Note
The show spanning-tree mst interface interface_id privileged EXEC command displays information only for ports that are in a link-up operative state. Otherwise, you can use the show running-config privileged EXEC command to confirm the configuration. To return the interface to its default setting, use the no spanning-tree mst instance_id cost interface configuration command.
Configuring the Switch Priority

You can configure the switch priority so that it is more likely that a switch is chosen as the root bridge.
Note
Exercise care when using this command. For most situations, we recommend that you use the spanning-tree mst instance_id root primary and the spanning-tree mst instance_id root secondary global configuration commands to modify the switch priority.
19-23
To configure the switch priority, perform this task: Command

Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree mst instance_id priority priority
Purpose Enters global configuration mode. (Optional) Configures the switch priority.
For instance_id, you can specify a single instance, a range of instances separated by a hyphen, or a series of instances separated by a comma. The range is 0 to 4094. For priority, the range is 0 to 61440 in increments of 4096; the default is 32768. The lower the number, the more likely the switch will be chosen as the root bridge. Priority values are 0, 4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, and 61440. All other values are rejected.
Router(config)# end Router# show spanning-tree mst instance_id Router# copy running-config startup-config
To return the switch to its default setting, use the no spanning-tree mst instance_id priority global configuration command.
Configuring the Hello Time

You can configure the interval between the generation of configuration messages by the root bridge by changing the hello time.
Note
Exercise care when using this command. For most situations, we recommend that you use the spanning-tree mst instance_id root primary and the spanning-tree mst instance_id root secondary global configuration commands to modify the hello time. To configure the hello time for all MST instances, perform this task:
Command
Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree mst hello-time seconds
Purpose Enters global configuration mode. (Optional) Configures the hello time for all MST instances. The hello time is the interval between the generation of configuration messages by the root bridge. These messages mean that the switch is alive. For seconds, the range is 1 to 10; the default is 2. Returns to privileged EXEC mode.
Step 3
end
19-24
OL-3999-08
Chapter 19
Command
Step 4 Step 5
Router# show spanning-tree mst Router# copy running-config startup-config
Purpose Verifies your entries. (Optional) Saves your entries in the configuration file.
To return the switch to its default setting, use the no spanning-tree mst hello-time global configuration command.
Configuring the Forwarding-Delay Time

To configure the forwarding-delay time for all MST instances, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree mst forward-time seconds
Purpose Enters global configuration mode. (Optional) Configures the forward time for all MST instances. The forward delay is the number of seconds a port waits before changing from its spanning-tree learning and listening states to the forwarding state. For seconds, the range is 4 to 30; the default is 15. Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
Router(config)# end Router# show spanning-tree mst Router# copy running-config startup-config
To return the switch to its default setting, use the no spanning-tree mst forward-time global configuration command.
Configuring the Transmit Hold Count

To configure the transmit hold count for all MST instances, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree transmit hold-count hold_count_value
Purpose Enters global configuration mode. Configures the transmit hold count for all MST instances. For hold_count_value, the range is 1 to 20; the default is 6.
To return the switch to its default setting, use the no spanning-tree transmit hold-count global configuration command.
19-25
Configuring the Maximum-Aging Time

To configure the maximum-aging time for all MST instances, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree mst max-age seconds
Purpose Enters global configuration mode. (Optional) Configures the maximum-aging time for all MST instances. The maximum-aging time is the number of seconds a switch waits without receiving spanning-tree configuration messages before attempting a reconfiguration. For seconds, the range is 6 to 40; the default is 20. Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
To return the switch to its default setting, use the no spanning-tree mst max-age global configuration command.
Configuring the Maximum-Hop Count

To configure the maximum-hop count for all MST instances, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# spanning-tree mst max-hops hop_count
Purpose Enters global configuration mode. (Optional) Specifies the number of hops in a region before the BPDU is discarded, and the information held for a port is aged. For hop_count, the range is 1 to 255; the default is 20. Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
To return the switch to its default setting, use the no spanning-tree mst max-hops global configuration command.
Specifying the Link Type to Ensure Rapid Transitions

If you connect a port to another port through a point-to-point link and the local port becomes a designated port, the RSTP negotiates a rapid transition with the other port by using the proposal-agreement handshake to ensure a loop-free topology as described in the Rapid Convergence section on page 19-11.
19-26
OL-3999-08
Chapter 19
By default, the link type is controlled from the duplex mode of the interface: a full-duplex port is considered to have a point-to-point connection; a half-duplex port is considered to have a shared connection. If you have a half-duplex link physically connected point-to-point to a single port on a remote switch running MST, you can override the default setting of the link type and enable rapid transitions to the forwarding state. To override the default link-type setting, perform this task: Command
1

slot/port} |
(Optional) Specifies an interface to configure, and enters interface configuration mode. Specifies that the link type of a port is point-to-point. Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
Router(config)# spanning-tree link-type point-to-point Router(config)# end Router# show spanning-tree mst interface interface_id Router# copy running-config startup-config 1.
To return the port to its default setting, use the no spanning-tree link-type interface configuration command.
Designating the Neighbor Type

A topology could contain both prestandard and 802.1s standard compliant devices. By default, ports can automatically detect prestandard devices, but they can still receive both standard and prestandard BPDUs. When there is a mismatch between a device and its neighbor, only the CIST runs on the interface. You can choose to set a port to send only prestandard BPDUs. The prestandard flag appears in all the show commands, even if the port is in STP compatibility mode. To override the default link-type setting, perform this task: Command
1

slot/port} |
(Optional) Specifies an interface to configure, and enters interface configuration mode. Specifies that the port can send only prestandard BPDUs. Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
Router(config)# spanning-tree mst pre-standard Router(config)# end Router# show spanning-tree mst interface interface_id Router# copy running-config startup-config 1.
19-27
Chapter 19 Displaying the MST Configuration and Status
To return the port to its default setting, use the no spanning-tree mst prestandard interface configuration command.
Restarting the Protocol Migration Process

A switch running MST supports a built-in protocol migration feature that enables it to interoperate with 802.1D switches. If this switch receives an 802.1D configuration BPDU (a BPDU with the protocol version set to 0), it sends only 802.1D BPDUs on that port. An MST switch also can detect that a port is at the boundary of a region when it receives an 802.1D BPDU, an MST BPDU (Version 3) associated with a different region, or an RST BPDU (Version 2). However, the switch does not automatically revert to the MST mode if it no longer receives 802.1D BPDUs because it cannot detect whether the 802.1D switch has been removed from the link unless the 802.1D switch is the designated switch. A switch also might continue to assign a boundary role to a port when the switch to which it is connected has joined the region. To restart the protocol migration process (force the renegotiation with neighboring switches) on the switch, use the clear spanning-tree detected-protocols privileged EXEC command. To restart the protocol migration process on a specific interface, use the clear spanning-tree detected-protocols interface interface_id privileged EXEC command.
Displaying the MST Configuration and Status

To display the spanning-tree status, use one or more of the privileged EXEC commands that are described in Table 19-5.
Table 19-5 Commands for Displaying MST Status
Command
show spanning-tree mst configuration show spanning-tree mst configuration digest show spanning-tree mst instance_id show spanning-tree mst interface interface_id
Purpose Displays the MST region configuration. Displays the MD5 digest included in the current MSTCI. Displays MST information for the specified instance. Displays MST information for the specified interface.
Tip
19-28
OL-3999-08
C H A P T E R
20
Configuring STP and Prestandard IEEE 802.1s MST

This chapter describes how to configure the Spanning Tree Protocol (STP) and prestandard IEEE 802.1s Multiple Spanning Tree (MST) protocol on Catalyst 6500 series switches.
Note
The IEEE 802.1s MST protocol has transitioned from a prestandard state to a released state. Chapter 19, Configuring Standard-Compliant IEEE MST, describes the standard-compliant MST implementation supported in Release 12.2(18)SXF and later releases. This chapter describes the prestandard MST implementation supported in releases earlier than Release 12.2(18)SXF. For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
For information on configuring the PortFast, UplinkFast, and BackboneFast STP enhancements, see Chapter 21, Configuring Optional STP Features.

Understanding How STP Works, page 20-2 Understanding How IEEE 802.1w RSTP Works, page 20-13 Understanding How Prestandard IEEE 802.1s MST Works, page 20-14 Default STP Configuration, page 20-21 STP and MST Configuration Guidelines and Restrictions, page 20-21 Configuring STP, page 20-22 Configuring Prestandard IEEE 802.1s MST, page 20-33
Tip
20-1
Chapter 20 Understanding How STP Works
Understanding How STP Works

These sections describe how STP works:

STP Overview, page 20-2 Understanding the Bridge ID, page 20-2 Understanding Bridge Protocol Data Units, page 20-4 Election of the Root Bridge, page 20-4 STP Protocol Timers, page 20-5 Creating the Spanning Tree Topology, page 20-5 STP Port States, page 20-6 STP and IEEE 802.1Q Trunks, page 20-12
STP Overview
STP is a Layer 2 link-management protocol that provides path redundancy while preventing undesirable loops in the network. For a Layer 2 Ethernet network to function properly, only one active path can exist between any two stations. STP operation is transparent to end stations, which cannot detect whether they are connected to a single LAN segment or a switched LAN of multiple segments. Catalyst 6500 series switches use STP (the IEEE 802.1D bridge protocol) on all VLANs. By default, a single instance of STP runs on each configured VLAN (provided you do not manually disable STP). You can enable and disable STP on a per-VLAN basis. When you create fault-tolerant internetworks, you must have a loop-free path between all nodes in a network. The STP algorithm calculates the best loop-free path throughout a switched Layer 2 network. Layer 2 LAN ports send and receive STP frames at regular intervals. Network devices do not forward these frames, but use the frames to construct a loop-free path. Multiple active paths between end stations cause loops in the network. If a loop exists in the network, end stations might receive duplicate messages and network devices might learn end station MAC addresses on multiple Layer 2 LAN ports. These conditions result in an unstable network. STP defines a tree with a root bridge and a loop-free path from the root to all network devices in the Layer 2 network. STP forces redundant data paths into a standby (blocked) state. If a network segment in the spanning tree fails and a redundant path exists, the STP algorithm recalculates the spanning tree topology and activates the standby path. When two Layer 2 LAN ports on a network device are part of a loop, the STP port priority and port path cost setting determine which port is put in the forwarding state and which port is put in the blocking state. The STP port priority value represents the location of a port in the network topology and how efficiently that location allows the port to pass traffic. The STP port path cost value represents media speed.
Understanding the Bridge ID

Each VLAN on each network device has a unique 64-bit bridge ID consisting of a bridge priority value, an extended system ID, and an STP MAC address allocation. This section contains these topics:
Bridge Priority Value, page 20-3
20-2
OL-3999-08
Chapter 20
Configuring STP and Prestandard IEEE 802.1s MST Understanding How STP Works
Extended System ID, page 20-3 STP MAC Address Allocation, page 20-3
Bridge Priority Value

The bridge priority is a 4-bit value when the extended system ID is enabled (see Table 20-2 on page 20-3 and the Configuring the Bridge Priority of a VLAN section on page 20-30).
Extended System ID
A 12-bit extended system ID field is part of the bridge ID (see Table 20-2 on page 20-3). Chassis that support only 64 MAC addresses always use the 12-bit extended system ID. On chassis that support 1024 MAC addresses, you can enable use of the extended system ID. STP uses the VLAN ID as the extended system ID. See the Enabling the Extended System ID section on page 20-24.
Table 20-1 Bridge Priority Value with the Extended System ID Disabled
Bridge Priority Value Bit 16 32768 Bit 15 16384 Bit 14 8192 Bit 13 4096 Bit 12 2048 Bit 11 1024 Bit 10 512 Bit 9 256 Bit 8 128 Bit 7 64 Bit 6 32 Bit 5 16 Bit 4 8 Bit 3 4 Bit 2 2 Bit 1 1
Table 20-2 Bridge Priority Value and Extended System ID with the Extended System ID Enabled
Bridge Priority Value Bit 16 32768 Bit 15 16384 Bit 14 8192 Bit 13 4096
Extended System ID (Set Equal to the VLAN ID) Bit 12 2048 Bit 11 1024 Bit 10 512 Bit 9 256 Bit 8 128 Bit 7 64 Bit 6 32 Bit 5 16 Bit 4 8 Bit 3 4 Bit 2 2 Bit 1 1
STP MAC Address Allocation

Catalyst 6500 series switch chassis have either 64 or 1024 MAC addresses available to support software features such as STP. To view the MAC address range on your chassis, enter the show catalyst6000 chassis-mac-address command. For chassis with 64 MAC addresses, STP uses the extended system ID plus a MAC address to make the bridge ID unique for each VLAN. When the extended system ID is not enabled, STP uses one MAC address per VLAN to make the bridge ID unique for each VLAN. If you have a network device in your network with the extended system ID enabled, you should also enable the extended system ID on all other Layer 2 connected network devices to avoid undesirable root bridge election and spanning tree topology issues. When the extended system ID is enabled, the root bridge priority becomes a multiple of 4096 plus the VLAN ID. With the extended system ID enabled, a switch bridge ID (used by the spanning tree algorithm to determine the identity of the root bridge, the lowest being preferred) can only be specified as a multiple of 4096. Only the following values are possible: 0, 4096, 8192, 12288, 16384, 20480, 24576, 28672, 32768, 36864, 40960, 45056, 49152, 53248, 57344, and 61440. If another bridge in the same spanning tree domain does not have the extended system ID enabled, it could win root bridge ownership because of the finer granularity in the selection of its bridge ID.
20-3
Understanding Bridge Protocol Data Units

Bridge protocol data units (BPDUs) are transmitted in one direction from the root bridge. Each network device sends configuration BPDUs to communicate and compute the spanning tree topology. Each configuration BPDU contains the following minimal information:

The unique bridge ID of the network device that the transmitting network device believes to be the root bridge The STP path cost to the root The bridge ID of the transmitting bridge Message age The identifier of the transmitting port Values for the hello, forward delay, and max-age protocol timers
When a network device transmits a BPDU frame, all network devices connected to the LAN on which the frame is transmitted receive the BPDU. When a network device receives a BPDU, it does not forward the frame but instead uses the information in the frame to calculate a BPDU, and, if the topology changes, initiate a BPDU transmission. A BPDU exchange results in the following:

One network device is elected as the root bridge. The shortest distance to the root bridge is calculated for each network device based on the path cost. A designated bridge for each LAN segment is selected. This is the network device closest to the root bridge through which frames are forwarded to the root. A root port is selected. This is the port providing the best path from the bridge to the root bridge. Ports included in the spanning tree are selected.
Election of the Root Bridge

For each VLAN, the network device with the highest-priority bridge ID (the lowest numerical ID value) is elected as the root bridge. If all network devices are configured with the default priority (32768), the network device with the lowest MAC address in the VLAN becomes the root bridge. The bridge priority value occupies the most significant bits of the bridge ID. When you change the bridge priority value, you change the probability that the switch will be elected as the root bridge. Configuring a higher-priority value increases the probability; a lower-priority value decreases the probability. The STP root bridge is the logical center of the spanning tree topology in a Layer 2 network. All paths that are not needed to reach the root bridge from anywhere in the Layer 2 network are placed in STP blocking mode. BPDUs contain information about the transmitting bridge and its ports, including bridge and MAC addresses, bridge priority, port priority, and path cost. STP uses this information to elect the root bridge for the Layer 2 network, to elect the root port leading to the root bridge, and to determine the designated port for each Layer 2 segment.
20-4
OL-3999-08
Chapter 20
STP Protocol Timers

Table 20-3 describes the STP protocol timers that affect STP performance.
Table 20-3 STP Protocol Timers
Variable Hello timer Forward delay timer Maximum age timer
Description Determines how often the network device broadcasts hello messages to other network devices. Determines how long each of the listening and learning states last before the port begins forwarding. Determines the amount of time protocol information received on an port is stored by the network device.
Creating the Spanning Tree Topology

In Figure 20-1, Switch A is elected as the root bridge because the bridge priority of all the network devices is set to the default (32768) and Switch A has the lowest MAC address. However, due to traffic patterns, number of forwarding ports, or link types, Switch A might not be the ideal root bridge. By increasing the priority (lowering the numerical value) of the ideal network device so that it becomes the root bridge, you force an STP recalculation to form a new spanning tree topology with the ideal network device as the root.
Figure 20-1 Spanning Tree Topology
DP DP DP RP B A DP RP D DP DP
RP C
DP
S5688
RP = Root Port DP = Designated Port
When the spanning tree topology is calculated based on default parameters, the path between source and destination end stations in a switched network might not be ideal. For instance, connecting higher-speed links to a port that has a higher number than the current root port can cause a root-port change. The goal is to make the fastest link the root port. For example, assume that one port on Switch B is a fiber-optic link, and another port on Switch B (an unshielded twisted-pair [UTP] link) is the root port. Network traffic might be more efficient over the high-speed fiber-optic link. By changing the STP port priority on the fiber-optic port to a higher priority (lower numerical value) than the root port, the fiber-optic port becomes the new root port.
20-5
STP Port States

These sections describe the STP port states:

STP Port State Overview, page 20-6 Blocking State, page 20-8 Listening State, page 20-9 Learning State, page 20-10 Forwarding State, page 20-11 Disabled State, page 20-12
STP Port State Overview

Propagation delays can occur when protocol information passes through a switched LAN. As a result, topology changes can take place at different times and at different places in a switched network. When a Layer 2 LAN port transitions directly from nonparticipation in the spanning tree topology to the forwarding state, it can create temporary data loops. Ports must wait for new topology information to propagate through the switched LAN before starting to forward frames. They must allow the frame lifetime to expire for frames that have been forwarded using the old topology. Each Layer 2 LAN port on a Catalyst 6500 series switch using STP exists in one of the following five states:

BlockingThe Layer 2 LAN port does not participate in frame forwarding. ListeningFirst transitional state after the blocking state when STP determines that the Layer 2 LAN port should participate in frame forwarding. LearningThe Layer 2 LAN port prepares to participate in frame forwarding. ForwardingThe Layer 2 LAN port forwards frames. DisabledThe Layer 2 LAN port does not participate in STP and is not forwarding frames.
A Layer 2 LAN port moves through these five states as follows:

From initialization to blocking From blocking to listening or to disabled From listening to learning or to disabled From learning to forwarding or to disabled From forwarding to disabled
Figure 20-2 illustrates how a Layer 2 LAN port moves through the five states.
20-6
OL-3999-08
Chapter 20
Figure 20-2 STP Layer 2 LAN Interface States

Boot-up initialization
Blocking state
Listening state
Disabled state
Learning state
When you enable STP, every port in the Catalyst 6500 series switch, VLAN, and network goes through the blocking state and the transitory states of listening and learning at power up. If properly configured, each Layer 2 LAN port stabilizes to the forwarding or blocking state. When the STP algorithm places a Layer 2 LAN port in the forwarding state, the following process occurs:
1. 2. 3. 4.
The Layer 2 LAN port is put into the listening state while it waits for protocol information that suggests it should go to the blocking state. The Layer 2 LAN port waits for the forward delay timer to expire, moves the Layer 2 LAN port to the learning state, and resets the forward delay timer. In the learning state, the Layer 2 LAN port continues to block frame forwarding as it learns end station location information for the forwarding database. The Layer 2 LAN port waits for the forward delay timer to expire and then moves the Layer 2 LAN port to the forwarding state, where both learning and frame forwarding are enabled.
S5691
Forwarding state
20-7
Blocking State
A Layer 2 LAN port in the blocking state does not participate in frame forwarding, as shown in Figure 20-3. After initialization, a BPDU is sent out to each Layer 2 LAN port. A network device initially assumes it is the root until it exchanges BPDUs with other network devices. This exchange establishes which network device in the network is the root or root bridge. If only one network device is in the network, no exchange occurs, the forward delay timer expires, and the ports move to the listening state. A port always enters the blocking state following initialization.
Figure 20-3 Interface 2 in Blocking State
Segment frames
Forwarding
Port 1 Station addresses Network management and data frames
BPDUs
Filtering database
System module
Frame forwarding
BPDUs
Network management frames

S5692
Data frames
Port 2
Blocking
Segment frames
A Layer 2 LAN port in the blocking state performs as follows:

Discards frames received from the attached segment. Discards frames switched from another port for forwarding. Does not incorporate end station location into its address database. (There is no learning on a blocking Layer 2 LAN port, so there is no address database update.) Receives BPDUs and directs them to the system module. Does not transmit BPDUs received from the system module. Receives and responds to network management messages.
20-8
OL-3999-08
Chapter 20
Listening State
The listening state is the first transitional state a Layer 2 LAN port enters after the blocking state. The Layer 2 LAN port enters this state when STP determines that the Layer 2 LAN port should participate in frame forwarding. Figure 20-4 shows a Layer 2 LAN port in the listening state.
Figure 20-4 Interface 2 in Listening State
All segment frames
Forwarding
BPDUs
Filtering database
System module
Frame forwarding
BPDUs Data frames Port 2

S5693
Listening
All segment frames
BPDU and network management frames
A Layer 2 LAN port in the listening state performs as follows:

Discards frames received from the attached segment. Discards frames switched from another LAN port for forwarding. Does not incorporate end station location into its address database. (There is no learning at this point, so there is no address database update.) Receives BPDUs and directs them to the system module. Receives, processes, and transmits BPDUs received from the system module. Receives and responds to network management messages.
20-9
Learning State
A Layer 2 LAN port in the learning state prepares to participate in frame forwarding. The Layer 2 LAN port enters the learning state from the listening state. Figure 20-5 shows a Layer 2 LAN port in the learning state.
Figure 20-5 Interface 2 in Learning State
All segment frames
Forwarding
BPDUs
Filtering database
System module
Frame forwarding
Station addresses Data frames
BPDUs

S5694
Port 2
Learning
All segment frames
BPDU and network management frames
A Layer 2 LAN port in the learning state performs as follows:

Discards frames received from the attached segment. Discards frames switched from another port for forwarding. Incorporates end station location into its address database. Receives BPDUs and directs them to the system module. Receives, processes, and transmits BPDUs received from the system module. Receives and responds to network management messages.
20-10
OL-3999-08
Chapter 20
Forwarding State
A Layer 2 LAN port in the forwarding state forwards frames, as shown in Figure 20-6. The Layer 2 LAN port enters the forwarding state from the learning state.
Figure 20-6 Interface 2 in Forwarding State
All segment frames
Forwarding
BPDUs
Filtering database
System module
Frame forwarding
Station addresses
BPDUs
Network management and data frames

S5695
Port 2
Forwarding
All segment frames
A Layer 2 LAN port in the forwarding state performs as follows:

Forwards frames received from the attached segment. Forwards frames switched from another port for forwarding. Incorporates end station location information into its address database. Receives BPDUs and directs them to the system module. Processes BPDUs received from the system module. Receives and responds to network management messages.
20-11
Disabled State
A Layer 2 LAN port in the disabled state does not participate in frame forwarding or STP, as shown in Figure 20-7. A Layer 2 LAN port in the disabled state is virtually nonoperational.
Figure 20-7 Interface 2 in Disabled State
All segment frames
Forwarding
BPDUs
Filtering database
System module
Frame forwarding
Network management frames Port 2

S5696
Data frames
Disabled
All segment frames
A disabled Layer 2 LAN port performs as follows:

Discards frames received from the attached segment. Discards frames switched from another port for forwarding. Does not incorporate end station location into its address database. (There is no learning, so there is no address database update.) Does not receive BPDUs. Does not receive BPDUs for transmission from the system module.
STP and IEEE 802.1Q Trunks

802.1Q trunks impose some limitations on the STP strategy for a network. In a network of Cisco network devices connected through 802.1Q trunks, the network devices maintain one instance of STP for each VLAN allowed on the trunks. However, non-Cisco 802.1Q network devices maintain only one instance of STP for all VLANs allowed on the trunks. When you connect a Cisco network device to a non-Cisco device through an 802.1Q trunk, the Cisco network device combines the STP instance of the 802.1Q VLAN of the trunk with the STP instance of the non-Cisco 802.1Q network device. However, all per-VLAN STP information is maintained by Cisco network devices separated by a cloud of non-Cisco 802.1Q network devices. The non-Cisco 802.1Q cloud separating the Cisco network devices is treated as a single trunk link between the network devices.
20-12
OL-3999-08
Chapter 20
Configuring STP and Prestandard IEEE 802.1s MST Understanding How IEEE 802.1w RSTP Works
For more information on 802.1Q trunks, see Chapter 10, Configuring LAN Ports for Layer 2 Switching.
Understanding How IEEE 802.1w RSTP Works

Note
RSTP is available as a standalone protocol in Rapid-Per-VLAN-Spanning Tree (Rapid-PVST) mode. In this mode, the switch runs an RSTP instance on each VLAN, which follows the usual PVST+ approach. These sections describe Rapid Spanning Tree Protocol (RSTP):

IEEE 802.1w RSTP Overview, page 20-13 RSTP Port Roles, page 20-13 RSTP Port States, page 20-14 Rapid-PVST, page 20-14
IEEE 802.1w RSTP Overview

RSTP significantly reduces the time to reconfigure the active topology of the network when changes occur to the physical topology or its configuration parameters. RSTP selects one switch as the root of a spanning tree-connected active topology and assigns port roles to individual ports of the switch, depending on whether that port is part of the active topology. RSTP provides rapid connectivity following the failure of a switch, switch port, or a LAN. A new root port and the designated port on the other side of the bridge transition to forwarding using an explicit handshake between them. RSTP allows switch port configuration so that the ports can transition to forwarding directly when the switch reinitializes. RSTP as specified in 802.1w supersedes STP specified in 802.1D, but remains compatible with STP. RSTP provides backward compatibility with 802.1D bridges as follows:

RSTP selectively sends 802.1D-configured BPDUs and topology change notification (TCN) BPDUs on a per-port basis. When a port initializes, the migration-delay timer starts and RSTP BPDUs are transmitted. While the migration-delay timer is active, the bridge processes all BPDUs received on that port. If the bridge receives an 802.1D BPDU after a ports migration-delay timer expires, the bridge assumes it is connected to an 802.1D bridge and starts using only 802.1D BPDUs. When RSTP uses 802.1D BPDUs on a port and receives an RSTP BPDU after the migration-delay expires, RSTP restarts the migration-delay timer and begins using RSTP BPDUs on that port.
RSTP Port Roles

RSTP uses the following definitions for port roles:

RootA forwarding port elected for the spanning tree topology. DesignatedA forwarding port elected for every switched LAN segment. AlternateAn alternate path to the root bridge to that provided by the current root port.
20-13
Chapter 20 Understanding How Prestandard IEEE 802.1s MST Works
BackupA backup for the path provided by a designated port toward the leaves of the spanning tree. Backup ports can exist only where two ports are connected together in a loopback by a point-to-point link or bridge with two or more connections to a shared LAN segment. DisabledA port that has no role within the operation of spanning tree. A root port or designated port role includes the port in the active topology. An alternate port or backup port role excludes the port from the active topology.
Port roles are assigned as follows:

RSTP Port States

The port state controls the forwarding and learning processes and provides the values of discarding, learning, and forwarding. Table 20-4 provides a comparison between STP port states and RSTP port states.
Table 20-4 Comparison Between STP and RSTP Port States
Operational Status Enabled Enabled Enabled Enabled Disabled
STP Port State Blocking Learning Forwarding Disabled

1
RSTP Port State Discarding Discarding Learning Forwarding Discarding

2
Port Included in Active Topology No No Yes Yes No
Listening
1. IEEE 802.1D port state designation. 2. IEEE 802.1w port state designation. Discarding is the same as blocking in RSTP and MST.
In a stable topology, RSTP ensures that every root port and designated port transition to forwarding, and ensures that all alternate ports and backup ports are always in the discarding state.
Rapid-PVST
Rapid-PVST uses the existing configuration for PVST+; however, Rapid-PVST uses RSTP to provide faster convergence. Independent VLANs run their own RSTP instance. Dynamic entries are flushed immediately on a per-port basis upon receiving a topology change. UplinkFast and BackboneFast configurations are ignored in Rapid-PVST mode; both features are included in RSTP.
Understanding How Prestandard IEEE 802.1s MST Works

These sections describe Multiple Spanning Tree (MST):

IEEE 802.1s MST Overview, page 20-15 MST-to-PVST Interoperability, page 20-16 Common Spanning Tree, page 20-18
20-14
OL-3999-08
Chapter 20
Configuring STP and Prestandard IEEE 802.1s MST Understanding How Prestandard IEEE 802.1s MST Works
MST Instances, page 20-18 MST Configuration Parameters, page 20-18 MST Regions, page 20-19 Message Age and Hop Count, page 20-20 Default STP Configuration, page 20-21
IEEE 802.1s MST Overview

MST in this release is based on the draft version of the IEEE standard. 802.1s for MST is an amendment to 802.1Q. MST extends the IEEE 802.1w rapid spanning tree (RST) algorithm to multiple spanning trees. This extension provides both rapid convergence and load balancing in a VLAN environment. MST converges faster than PVST+. MST is backward compatible with 802.1D STP, 802.1w (rapid spanning tree protocol [RSTP]), and the Cisco PVST+ architecture. MST allows you to build multiple spanning trees over trunks. You can group and associate VLANs to spanning tree instances. Each instance can have a topology independent of other spanning tree instances. This new architecture provides multiple forwarding paths for data traffic and enables load balancing. Network fault tolerance is improved because a failure in one instance (forwarding path) does not affect other instances (forwarding paths). In large networks, you can more easily administer the network and use redundant paths by locating different VLAN and spanning tree instance assignments in different parts of the network. A spanning tree instance can exist only on bridges that have compatible VLAN instance assignments. You must configure a set of bridges with the same MST configuration information, which allows them to participate in a specific set of spanning tree instances. Interconnected bridges that have the same MST configuration are referred to as an MST region . MST uses the modified RSTP version called the Multiple Spanning Tree Protocol (MSTP). The MST feature has these characteristics:
MST runs a variant of spanning tree called internal spanning tree (IST). IST augments the common spanning tree (CST) information with internal information about the MST region. The MST region appears as a single bridge to adjacent single spanning tree (SST) and MST regions. A bridge running MST provides interoperability with single spanning tree bridges as follows:
MST bridges run IST, which augments the common spanning tree (CST) information with
internal information about the MST region.

IST connects all the MST bridges in the region and appears as a subtree in the CST that includes
the whole bridged domain. The MST region appears as a virtual bridge to adjacent SST bridges and MST regions.
The common and internal spanning tree (CIST) is the collection of ISTs in each MST region,
the CST that interconnects the MST regions, and the SST bridges. CIST is the same as an IST inside an MST region and the same as CST outside an MST region. The STP, RSTP, and MSTP together elect a single bridge as the root of the CIST.
20-15
MST establishes and maintains additional spanning trees within each MST region. These spanning trees are referred to as MST instances (MSTIs). The IST is numbered 0, and the MSTIs are numbered 1,2,3, and so on. Any MSTI is local to the MST region that is independent of MSTIs in another region, even if the MST regions are interconnected. MST instances combine with the IST at the boundary of MST regions to become the CST as follows: Spanning tree information for an MSTI is contained in an MSTP record (M-record). M-records are always encapsulated within MST BPDUs (MST BPDUs). The original spanning trees computed by MSTP are called M-trees. M-trees are active only within the MST region. M-trees merge with the IST at the boundary of the MST region and form the CST.
MST provides interoperability with PVST+ by generating PVST+ BPDUs for the non-CST VLANs. MST supports some of the PVST+ extensions in MSTP as follows:
UplinkFast and BackboneFast are not available in MST mode; they are included in RSTP. PortFast is supported. BPDU filter and BPDU guard are supported in MST mode. Loop guard and root guard are supported in MST. MST preserves the VLAN 1 disabled
functionality except that BPDUs are still transmitted in VLAN 1.

MST switches operate as if MAC reduction is enabled. For private VLANs (PVLANs), secondary VLANs must be mapped to the same instance as the
primary.
MST-to-PVST Interoperability
A virtual bridged LAN may contain interconnected regions of single spanning tree (SST) and MST bridges. Figure 20-8 shows this relationship.
20-16
OL-3999-08
Chapter 20
Figure 20-8 Network with Interconnected SST and MST Regions
MST Region r B F B
B B
F r SST b Region r F F F/f = Forwarding B/b = Blocking R = Root Bridge r = Root port F R MST Region F F r F F F F r
F r
F r b SST Region
An MST region appears as an SST or pseudobridge to STP running in the SST region. Pseudobridges operate as follows:
The same values for root identifiers and root path costs are sent in all BPDUs of all the pseudobridge ports. Pseudobridges differ from a single SST bridge as follows:
The pseudobridge BPDUs have different bridge identifiers. This difference does not affect STP
operation in the neighboring SST regions because the root identifier and root cost are the same.
BPDUs sent from the pseudobridge ports may have significantly different message ages.
Because the message age increases by 1 second for each hop, the difference in the message age is in the order of seconds.

Data traffic from one port of a pseudobridge (a port at the edge of a region) to another port follows a path entirely contained within the pseudobridge or MST region. Data traffic belonging to different VLANs may follow different paths within the MST regions established by MST. Loop prevention is achieved by either of the following:
Blocking the appropriate pseudobridge ports by allowing one forwarding port on the boundary
and blocking all other ports.

Setting the CST partitions to block the ports of the SST regions.
A pseudobridge differs from a single SST bridge because the BPDUs sent from the pseudobridges ports have different bridge identifiers. The root identifier and root cost are the same for both bridges.
These guidelines apply in a topology where you configure MST switches (all in the same region) to interact with PVST+ switches:
Configure the root for all VLANs inside the MST region as shown in this example:
Router# show spanning-tree mst interface gigabitethernet 1/1 GigabitEthernet1/1 of MST00 is root forwarding
68285
20-17
Edge port: Link type: Boundary : Bpdus sent Instance -------0 3
no (trunk) point-to-point (auto) boundary (PVST) 10, received 310 Sts --FWD FWD Cost --------20000 20000 Prio.Nbr -------128.1 128.1
port guard : none bpdu filter: disable bpdu guard : disable
(default) (default) (default)
Role ---Root Boun
Vlans mapped ------------------------------1-2,4-2999,4000-4094 3,3000-3999
The ports that belong to the MST switch at the boundary simulate PVST+ and send PVST+ BPDUs for all the VLANs. If you enable loop guard on the PVST+ switches, the ports might change to a loop-inconsistent state when the MST switches change their configuration. To correct the loop-inconsistent state, you must disable and reenable loop guard on that PVST+ switch.
Do not locate the root for some or all of the VLANs inside the PVST+ side of the MST switch because when the MST switch at the boundary receives PVST+ BPDUs for all or some of the VLANs on its designated ports, root guard sets the port to the blocking state. Do not designate switches with a slower CPU running PVST+ as a switch running MST.
When you connect a PVST+ switch to two different MST regions, the topology change from the PVST+ switch does not pass beyond the first MST region. In this case, the topology changes are only propagated in the instance to which the VLAN is mapped. The topology change stays local to the first MST region and the CAM entries in the other region are not flushed. To make the topology change visible throughout other MST regions, you can map that VLAN to IST or connect the PVST+ switch to the two regions through access links.
Common Spanning Tree

CST (802.1Q) is a single spanning tree for all the VLANs. In a Catalyst 6500 series switch running PVST+, the VLAN 1 spanning tree corresponds to CST. In a Catalyst 6500 series switch running MST, IST (instance 0) corresponds to CST.
MST Instances
This release supports up to 16 instances; each spanning tree instance is identified by an instance ID that ranges from 0 to 15. Instance 0 is mandatory and is always present. Instances 1 through 15 are optional.
MST Configuration Parameters

MST configuration includes these three parts:

NameA 32-character string (null padded) identifying the MST region. Revision numberAn unsigned 16-bit number that identifies the revision of the current MST configuration.
Note
You must set the revision number when required as part of the MST configuration. The revision number is not incremented automatically each time you commit the MST configuration.
20-18
OL-3999-08
Chapter 20
MST configuration tableAn array of 4096 bytes. Each byte, interpreted as an unsigned integer, corresponds to a VLAN. The value is the instance number to which the VLAN is mapped. The first byte that corresponds to VLAN 0 and the 4096th byte that corresponds to VLAN 4095 are unused and always set to zero.
You must configure each byte manually. You can use SNMP or the CLI to perform the configuration. MST BPDUs contain the MST configuration ID and the checksum. An MST bridge accepts an MST BPDU only if the MST BPDU configuration ID and the checksum match its own MST region configuration ID and checksum. If one value is different, the MST BPDU is considered to be an SST BPDU.
MST Regions
These sections describe MST regions:

MST Region Overview, page 20-19 Boundary Ports, page 20-19 IST Master, page 20-20 Edge Ports, page 20-20 Link Type, page 20-20
MST Region Overview

Interconnected bridges that have the same MST configuration are referred to as an MST region. There is no limit on the number of MST regions in the network. To form an MST region, bridges can be either of the following:

An MST bridge that is the only member of the MST region. An MST bridge interconnected by a LAN. A LANs designated bridge has the same MST configuration as an MST bridge. All the bridges on the LAN can process MST BPDUs.
If you connect two MST regions with different MST configurations, the MST regions do the following:

Load balance across redundant paths in the network. If two MST regions are redundantly connected, all traffic flows on a single connection with the MST regions in a network. Provide an RSTP handshake to enable rapid connectivity between regions. However, the handshaking is not as fast as between two bridges. To prevent loops, all the bridges inside the region must agree upon the connections to other regions. This situation introduces a delay. We do not recommend partitioning the network into a large number of regions.
Boundary Ports
A boundary port is a port that connects to a LAN, the designated bridge, of which is either an SST bridge, or a bridge with a different MST configuration. A designated port knows that it is on the boundary if it detects an STP bridge or receives an agreement message from an RST or MST bridge with a different configuration. At the boundary, the role of MST ports do not matter; their state is forced to be the same as the IST port state. If the boundary flag is set for the port, the MSTP port-role selection process assigns a port role to the boundary and assigns the same state as the state of the IST port. The IST port at the boundary can take up any port role except a backup port role.
20-19
IST Master
The IST master of an MST region is the bridge with the lowest bridge identifier and the least path cost to the CST root. If an MST bridge is the root bridge for CST, then it is the IST master of that MST region. If the CST root is outside the MST region, then one of the MST bridges at the boundary is selected as the IST master. Other bridges on the boundary that belong to the same region eventually block the boundary ports that lead to the root. If two or more bridges at the boundary of a region have an identical path to the root, you can set a slightly lower bridge priority to make a specific bridge the IST master. The root path cost and message age inside a region stay constant, but the IST path cost is incremented and the IST remaining hops are decremented at each hop. To display the information about the IST master, path cost, and remaining hops for the bridge, enter the show spanning-tree mst command.
Edge Ports
An edge port is a port that is a port that is connected to a nonbridging device (for example, a host or a router). A port that connects to a hub is also an edge port if the hub or any LAN that is connected by it does not have a bridge. An edge port can start forwarding as soon as the link is up. MST requires that you configure all ports for each host or router. To establish rapid connectivity after a failure, you need to block the non-edge designated ports of an intermediate bridge. If the port connects to another bridge that can send back an agreement, then the port starts forwarding immediately. Otherwise, the port needs twice the forward delay time to start forwarding again. You must explicitly configure the ports that are connected to the hosts and routers as edge ports while using MST. To prevent a misconfiguration, the PortFast operation is turned off if the port receives a BPDU. To display the configured and operational status of PortFast, enter the show spanning-tree mst interface command.
Link Type
Rapid connectivity is established only on point-to-point links. You must configure ports explicitly to a host or router. However, cabling in most networks meets this requirement, and you can avoid explicit configuration by treating all full-duplex links as point-to-point links by entering the spanning-tree linktype command.
Message Age and Hop Count

IST and MST instances do not use the message age and maximum age timer settings in the BPDU. IST and MST use a separate hop-count process that is very similar to the IP TTL process. You can configure each MST bridge with a maximum hop count. The root bridge of the instance sends a BPDU (or M-record) with the remaining hop count that is equal to the maximum hop count. When a bridge receives a BPDU (or M-record), it decrements the received remaining hop count by one. The bridge discards the BPDU (M-record) and ages out the information held for the port if the count reaches zero after decrementing. The nonroot bridges propagate the decremented count as the remaining hop count in the BPDUs (M-records) they generate. The message age and maximum age timer settings in the RST portion of the BPDU remain the same throughout the region, and the same values are propagated by the regions designated ports at the boundary.
20-20
OL-3999-08
Chapter 20
Configuring STP and Prestandard IEEE 802.1s MST Default STP Configuration
Default STP Configuration

Table 20-5 shows the default STP configuration.
Table 20-5 STP Default Configuration
Feature Enable state Bridge priority STP port priority (configurable on a per-port basisused on LAN ports configured as Layer 2 access ports) STP port cost (configurable on a per-port basisused on LAN ports configured as Layer 2 access ports)
Default Value STP enabled for all VLANs 32768 128
10-Gigabit Ethernet: 2 Gigabit Ethernet: 4 Fast Ethernet: 19 Ethernet: 100
STP VLAN port priority (configurable on a per-VLAN basisused on LAN ports configured as Layer 2 trunk ports) STP VLAN port cost (configurable on a per-VLAN basisused on LAN ports configured as Layer 2 trunk ports)
128
10-Gigabit Ethernet: 2 Gigabit Ethernet: 4 Fast Ethernet: 19 Ethernet: 100
Hello time Forward delay time Maximum aging time Mode
2 seconds 15 seconds 20 seconds PVST
STP and MST Configuration Guidelines and Restrictions

When configuring MST, follow these guidelines and restrictions:

Do not disable spanning tree on any VLAN in any of the PVST bridges. Do not use PVST bridges as the root of CST. Ensure that all PVST spanning tree root bridges have lower (numerically higher) priority than the CST root bridge. Ensure that trunks carry all of the VLANs mapped to an instance or do not carry any VLANs at all for this instance. Do not connect switches with access links because access links may partition a VLAN. Any MST configuration involving a large number of either existing or new logical VLAN ports should be completed during a maintenance window because the complete MST database gets reinitialized for any incremental change (such as adding new VLANs to instances or moving VLANs across instances).
20-21
Chapter 20 Configuring STP
Configuring STP
These sections describe how to configure STP on VLANs:

Enabling STP, page 20-22 Enabling the Extended System ID, page 20-24 Configuring the Root Bridge, page 20-24 Configuring a Secondary Root Bridge, page 20-26 Configuring STP Port Priority, page 20-26 Configuring STP Port Cost, page 20-28 Configuring the Bridge Priority of a VLAN, page 20-30 Configuring the Hello Time, page 20-31 Configuring the Forward-Delay Time for a VLAN, page 20-32 Configuring the Maximum Aging Time for a VLAN, page 20-32 Enabling Rapid-PVST, page 20-33
Note
The STP commands described in this chapter can be configured on any LAN port, but they are in effect only on LAN ports configured with the switchport keyword.
Caution
We do not recommend disabling spanning tree, even in a topology that is free of physical loops. Spanning tree serves as a safeguard against misconfigurations and cabling errors. Do not disable spanning tree in a VLAN without ensuring that there are no physical loops present in the VLAN.
Enabling STP
Note
STP is enabled by default on VLAN 1 and on all newly created VLANs. You can enable STP on a per-VLAN basis. The Catalyst 6500 series switch maintains a separate instance of STP for each VLAN (except on VLANs on which you disable STP). To enable STP on a per-VLAN basis, perform this task:
Command
Step 1
Router(config)# spanning-tree vlan vlan_ID
Purpose Enables STP on a per-VLAN basis. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 20-5 on page 20-21). Reverts all STP parameters to default values for the specified VLAN. Disables STP on the specified VLAN; see the following Cautions for information regarding this command.
Router(config)# default spanning-tree vlan vlan_ID Router(config)# no spanning-tree vlan vlan_ID
20-22
OL-3999-08
Chapter 20
Configuring STP and Prestandard IEEE 802.1s MST Configuring STP
Command
Step 2 Step 3
Router(config)# end Router# show spanning-tree vlan vlan_ID
Purpose Exits configuration mode. Verifies that STP is enabled.
Caution
Do not disable spanning tree on a VLAN unless all switches and bridges in the VLAN have spanning tree disabled. You cannot disable spanning tree on some switches and bridges in a VLAN and leave it enabled on other switches and bridges in the VLAN. This action can have unexpected results because switches and bridges with spanning tree enabled will have incomplete information regarding the physical topology of the network.
Caution
We do not recommend disabling spanning tree, even in a topology that is free of physical loops. Spanning tree serves as a safeguard against misconfigurations and cabling errors. Do not disable spanning tree in a VLAN without ensuring that there are no physical loops present in the VLAN. This example shows how to enable STP on VLAN 200:
Router# configure terminal Router(config)# spanning-tree vlan 200 Router(config)# end Router#
Note
Because STP is enabled by default, entering a show running command to view the resulting configuration does not display the command you entered to enable STP. This example shows how to verify the configuration:
Router# show spanning-tree vlan 200 VLAN0200 Spanning tree enabled protocol ieee Root ID Priority 32768 Address 00d0.00b8.14c8 This bridge is the root Hello Time 2 sec Max Age 20 sec Bridge ID Priority 32768 Address 00d0.00b8.14c8 Hello Time 2 sec Max Age 20 sec Aging Time 300 Role ---Desg Back Sts --FWD BLK Cost --------200000 200000 Prio.Nbr -------128.196 128.197
Forward Delay 15 sec
Interface ---------------Fa4/4 Fa4/5 Router#
Status -------------------------------P2p P2p
Note
You must have at least one interface that is active in VLAN 200 to create a VLAN 200 spanning tree. In this example, two interfaces are active in VLAN 200.
20-23
Enabling the Extended System ID

Note
The extended system ID is enabled permanently on chassis that support 64 MAC addresses. You can enable the extended system ID on chassis that support 1024 MAC addresses (see the Understanding the Bridge ID section on page 20-2). To enable the extended system ID, perform this task:
Command
Step 1
Router(config)# spanning-tree extend system-id Router(config)# no spanning-tree extend system-id
Purpose Enables the extended system ID. Disables the extended system ID.
Note
You cannot disable the extended system ID on chassis that support 64 MAC addresses or when you have configured extended range VLANs (see STP Default Configuration section on page 20-21).
Step 2 Step 3
Exits configuration mode. Verifies the configuration.
Note
When you enable or disable the extended system ID, the bridge IDs of all active STP instances are updated, which might change the spanning tree topology. This example shows how to enable the extended system ID:
Router# configure terminal Router(config)# spanning-tree extend system-id Router(config)# end Router#

Router# show spanning-tree summary | include Extended Extended system ID is enabled.
Configuring the Root Bridge

Catalyst 6500 series switches maintain a separate instance of STP for each active VLAN. A bridge ID, consisting of the bridge priority and the bridge MAC address, is associated with each instance. For each VLAN, the network device with the highest-priority (lowest-numerical) bridge ID becomes the root bridge for that VLAN. To configure a VLAN instance to become the root bridge, enter the spanning-tree vlan vlan_ID root command to modify the bridge priority from the default value (32768) to a significantly lower value. When you enter the spanning-tree vlan vlan_ID root command, the switch checks the bridge priority of the current root bridges for each VLAN. When the extended system ID is disabled, the switch sets the bridge priority for the specified VLANs to 8192 if this value will cause the switch to become the root
20-24
OL-3999-08
Chapter 20
for the specified VLANs. When the extended system ID is enabled, the switch sets the bridge priority for the specified VLANs to 24576 if this value will cause the switch to become the root for the specified VLANs. If the extended system ID is disabled and if any root bridge for the specified VLANs has a bridge priority lower than 8192, the switch sets the bridge priority for the specified VLANs to 1 less than the lowest bridge priority. If the extended system ID is enabled and if any root bridge for the specified VLANs has a bridge priority lower than 24576, the switch sets the bridge priority for the specified VLANs to 4096 less than the lowest bridge priority. (4096 is the value of the least significant bit of a 4-bit bridge priority value; see Table 20-2 on page 20-3.)
Note
The spanning-tree vlan vlan_ID root command fails if the value required to be the root bridge is less than 1. The spanning-tree vlan vlan_ID root command can cause the following effects:
If the extended system ID is disabled, and if all network devices in VLAN 100 have the default priority of 32768, entering the spanning-tree vlan 100 root primary command on the switch sets the bridge priority for VLAN 100 to 8192, which causes the switch to become the root bridge for VLAN 100. If the extended system ID is enabled, and if all network devices in, for example, VLAN 20 have the default priority of 32768, entering the spanning-tree vlan 20 root primary command on the switch sets the bridge priority to 24576, which causes the switch to become the root bridge for VLAN 20.
Caution
The root bridge for each instance of STP should be a backbone or distribution switch. Do not configure an access switch as the STP primary root. Use the diameter keyword to specify the Layer 2 network diameter (that is, the maximum number of bridge hops between any two end stations in the Layer 2 network). When you specify the network diameter, the Catalyst 6500 series switch automatically selects an optimal hello time, forward delay time, and maximum age time for a network of that diameter, which can significantly reduce the STP convergence time. You can use the hello keyword to override the automatically calculated hello time.
Note
To preserve a stable STP topology, we recommend that you avoid configuring the hello time, forward delay time, and maximum age time manually after configuring the Catalyst 6500 series switch as the root bridge. To configure a Catalyst 6500 series switch as the root bridge, perform this task:
Command
Step 1
Router(config)# spanning-tree vlan vlan_ID root primary [diameter hops [hello-time seconds]]
Purpose Configures a Catalyst 6500 series switch as the root bridge. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 20-5 on page 20-21). Clears the root bridge configuration. Exits configuration mode.
Router(config)# no spanning-tree vlan vlan_ID root
Step 2
Router(config)# end
20-25
This example shows how to configure the Catalyst 6500 series switch as the root bridge for VLAN 10, with a network diameter of 4:
Router# configure terminal Router(config)# spanning-tree vlan 10 root primary diameter 4 Router(config)# end Router#
Configuring a Secondary Root Bridge

When you configure a Catalyst 6500 series switch as the secondary root, the STP bridge priority is modified from the default value (32768) so that the switch is likely to become the root bridge for the specified VLANs if the primary root bridge fails (assuming the other network devices in the network use the default bridge priority of 32768). If the extended system ID is enabled, STP sets the bridge priority to 28672. If the extended system ID is disabled, STP sets the bridge priority to 16384. You can run this command on more than one Catalyst 6500 series switch to configure multiple backup root bridges. Use the same network diameter and hello time values as you used when configuring the primary root bridge. To configure a Catalyst 6500 series switch as the secondary root bridge, perform this task: Command
Step 1
Router(config)# [no] spanning-tree vlan vlan_ID root secondary [diameter hops [hello-time seconds]] Router(config)# no spanning-tree vlan vlan_ID root
Purpose Configures a Catalyst 6500 series switch as the secondary root bridge. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Clears the root bridge configuring. Exits configuration mode.
Step 2
Router(config)# end
This example shows how to configure the Catalyst 6500 series switch as the secondary root bridge for VLAN 10, with a network diameter of 4:
Router# configure terminal Router(config)# spanning-tree vlan 10 root secondary diameter 4 Router(config)# end Router#
Configuring STP Port Priority

If a loop occurs, STP considers port priority when selecting a LAN port to put into the forwarding state. You can assign higher priority values to LAN ports that you want STP to select first and lower priority values to LAN ports that you want STP to select last. If all LAN ports have the same priority value, STP puts the LAN port with the lowest LAN port number in the forwarding state and blocks other LAN ports. The possible priority range is 0 through 240 (default 128), configurable in increments of 16. When the LAN port is configured as a trunk port, you can specify a different port priority for each VLAN carried by the trunk. VLANs not configured with a VLAN port priority default to using the spanning-tree port priority. Do not configure VLAN port priority for access ports.
20-26
OL-3999-08
Chapter 20
To configure the STP port priority of a Layer 2 LAN interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type1 slot/port} | {port-channel port_channel_number}} Router(config-if)# spanning-tree port-priority port_priority
Purpose Selects an interface to configure. Configures the port priority for the LAN interface. The port_priority value can be from 0 to 240 in increments of 16. Reverts to the default port priority value. Configures the VLAN port priority for the LAN interface. The port_priority value can be from 0 to 240 in increments of 16. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default VLAN port priority value. Exits configuration mode.
1
Router(config-if)# no spanning-tree port-priority
Step 3
Router(config-if)# spanning-tree vlan vlan_ID port-priority port_priority
Router(config-if)# [no] spanning-tree vlan vlan_ID port-priority
Step 4 Step 5
Router(config-if)# end Router# show spanning-tree interface {type slot/port} | {port-channel port_channel_number} Router# show spanning-tree vlan vlan_ID 1.
This example shows how to configure the STP port priority of Fast Ethernet port 4/4:
Router# configure terminal Router(config)# interface fastethernet 4/4 Router(config-if)# spanning-tree port-priority 160 Router(config-if)# end Router#
Router# show spanning-tree interface fastethernet 4/4 Vlan Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------VLAN0001 Back BLK 200000 160.196 P2p VLAN0006 Back BLK 200000 160.196 P2p ... VLAN0198 Back BLK 200000 160.196 P2p VLAN0199 Back BLK 200000 160.196 P2p VLAN0200 Back BLK 200000 160.196 P2p Router#
Fastethernet 4/4 is a trunk. Several VLANs are configured and active as shown in the example. The port priority configuration applies to all VLANs on this interface.
Note
The show spanning-tree interface command only displays information if the port is connected and operating. If this condition is not met, enter a show running-config interface command to verify the configuration.
20-27
This example shows how to configure the VLAN port priority of Fast Ethernet port 4/4:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree vlan 200 port-priority 64 Router(config-if)# ^Z Router#
The configuration entered in the example only applies to VLAN 200. All VLANs other than 200 still have a port priority of 160. This example shows how to verify the configuration:
Router# show spanning-tree interface fastethernet 4/4 Vlan Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------VLAN0001 Back BLK 200000 160.196 P2p VLAN0006 Back BLK 200000 160.196 P2p ... VLAN0199 Back BLK 200000 160.196 P2p VLAN0200 Desg FWD 200000 64.196 P2p Router#
You also can display spanning tree information for VLAN 200 using the following command:
Router# show spanning-tree vlan 200 interface fastEthernet 4/4 Interface Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------Fa4/4 Desg LRN 200000 64.196 P2p
Configuring STP Port Cost

The STP port path cost default value is determined from the media speed of a LAN interface. If a loop occurs, STP considers port cost when selecting a LAN interface to put into the forwarding state. You can assign lower cost values to LAN interfaces that you want STP to select first and higher cost values to LAN interfaces that you want STP to select last. If all LAN interfaces have the same cost value, STP puts the LAN interface with the lowest LAN interface number in the forwarding state and blocks other LAN interfaces. The possible cost range is 0 through 200000000 (the default is media specific). STP uses the port cost value when the LAN interface is configured as an access port and uses VLAN port cost values when the LAN interface is configured as a trunk port. To configure the STP port cost of a Layer 2 LAN interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type1 slot/port} | {port-channel port_channel_number}} Router(config-if)# spanning-tree cost port_cost
Purpose Selects an interface to configure. Configures the port cost for the LAN interface. The port_cost value can be from 1 to 200000000 (1 to 65535 in Release 12.1(2)E and earlier releases). Reverts to the default port cost. Configures the VLAN port cost for the LAN interface. The port_cost value can be from 1 to 200000000. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2).
Router(config-if)# no spanning-tree cost
Step 3
Router(config-if)# [no] spanning-tree vlan vlan_ID cost port_cost
20-28
OL-3999-08
Chapter 20
Command
Router(config-if)# no spanning-tree vlan vlan_ID cost Router(config-if)# end Router# show spanning-tree interface {type1 slot/port} | {port-channel port_channel_number} show spanning-tree vlan vlan_ID 1.
Purpose Reverts to the default VLAN port cost. Exits configuration mode. Verifies the configuration.
This example shows how to change the STP port cost of Fast Ethernet port 4/4:
Router# configure terminal Enter configuration commands, one per line. Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree cost 1000 Router(config-if)# ^Z Router# End with CNTL/Z.

Router# show spanning-tree interface fastEthernet 4/4 Vlan Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------VLAN0001 Back BLK 1000 160.196 P2p VLAN0006 Back BLK 1000 160.196 P2p VLAN0007 Back BLK 1000 160.196 P2p VLAN0008 Back BLK 1000 160.196 P2p VLAN0009 Back BLK 1000 160.196 P2p VLAN0010 Back BLK 1000 160.196 P2p Router#
This example shows how to configure the port priority at an individual port VLAN cost for VLAN 200:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree vlan 200 cost 2000 Router(config-if)# ^Z Router#

Router# show spanning-tree vlan 200 interface fastEthernet 4/4 Interface Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------Fa4/4 Desg FWD 2000 64.196 P2p
Note
In the following output other VLANs (VLAN 1 for example) have not been affected by this configuration.
Router# show spanning-tree vlan 1 interface fastEthernet 4/4 Interface Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------Fa4/4 Back BLK 1000 160.196 P2p Router#
20-29
Note
The show spanning-tree command only displays information for ports that are in link-up operative state and are appropriately configured for DTP. If these conditions are not met, you can enter a show running-config command to confirm the configuration.
Configuring the Bridge Priority of a VLAN

Note
Be careful when using this command. For most situations, we recommend that you enter the spanning-tree vlan vlan_ID root primary and the spanning-tree vlan vlan_ID root secondary commands to modify the bridge priority. To configure the STP bridge priority of a VLAN when the extended system ID is disabled, perform this task:
Command
Step 1
Router(config)# spanning-tree vlan vlan_ID priority bridge_priority
Purpose Configures the bridge priority of a VLAN when the extended system ID is disabled. The bridge_priority value can be from 1 to 65535. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default bridge priority value. Exits configuration mode. Verifies the configuration.
Router(config)# no spanning-tree vlan vlan_ID priority
Step 2 Step 3
Router(config)# end Router# show spanning-tree vlan vlan_ID bridge [detail]
To configure the STP bridge priority of a VLAN when the extended system ID is enabled, perform this task: Command
Step 1
Router(config)# [no] spanning-tree vlan vlan_ID priority {0 | 4096 | 8192 | 12288 | 16384 | 20480 | 24576 | 28672 | 32768 | 36864 | 40960 | 45056 | 49152 | 53248 | 57344 | 61440} Router(config)# no spanning-tree vlan vlan_ID priority
Purpose Configures the bridge priority of a VLAN when the extended system ID is enabled. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default bridge priority value. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to configure the bridge priority of VLAN 200 to 33792 when the extended system ID is disabled:
Router# configure terminal Router(config)# spanning-tree vlan 200 priority 33792 Router(config)# end Router#
20-30
OL-3999-08
Chapter 20

Router# show spanning-tree vlan 200 bridge Hello Max Fwd Vlan Bridge ID Time Age Delay ---------------- -------------------- ---- ---- ----VLAN200 33792 0050.3e8d.64c8 2 20 15 Router#
Protocol -------ieee
Configuring the Hello Time

Note
Be careful when using this command. For most situations, we recommend that you use the spanning-tree vlan vlan_ID root primary and spanning-tree vlan vlan_ID root secondary commands to modify the hello time. To configure the STP hello time of a VLAN, perform this task:
Command
Step 1
Router(config)# spanning-tree vlan vlan_ID hello-time hello_time
Purpose Configures the hello time of a VLAN. The hello_time value can be from 1 to 10 seconds. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default hello time. Exits configuration mode. Verifies the configuration.
Router(config)# no spanning-tree vlan vlan_ID hello-time
Step 2 Step 3
This example shows how to configure the hello time for VLAN 200 to 7 seconds:
Router# configure terminal Router(config)# spanning-tree vlan 200 hello-time 7 Router(config)# end Router#

20-31
Configuring the Forward-Delay Time for a VLAN

To configure the STP forward delay time for a VLAN, perform this task: Command
Step 1
Router(config)# spanning-tree vlan vlan_ID forward-time forward_time
Purpose Configures the forward time of a VLAN. The forward_time value can be from 4 to 30 seconds. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default forward time. Exits configuration mode. Verifies the configuration.
Router(config)# no spanning-tree vlan vlan_ID forward-time
Step 2 Step 3
This example shows how to configure the forward delay time for VLAN 200 to 21 seconds:
Router# configure terminal Router(config)# spanning-tree vlan 200 forward-time 21 Router(config)# end Router#

Configuring the Maximum Aging Time for a VLAN

To configure the STP maximum aging time for a VLAN, perform this task: Command
Step 1
Router(config)# spanning-tree vlan vlan_ID max-age max_age
Purpose Configures the maximum aging time of a VLAN. The max_age value can be from 6 to 40 seconds. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 14-1 on page 14-2). Reverts to the default maximum aging time. Exits configuration mode. Verifies the configuration.
Router(config)# no spanning-tree vlan vlan_ID max-age
Step 2 Step 3
This example shows how to configure the maximum aging time for VLAN 200 to 36 seconds:
Router# configure terminal Router(config)# spanning-tree vlan 200 max-age 36 Router(config)# end Router#
20-32
OL-3999-08
Chapter 20
Configuring STP and Prestandard IEEE 802.1s MST Configuring Prestandard IEEE 802.1s MST

Enabling Rapid-PVST
Rapid-PVST uses the existing PVST+ framework for configuration and interaction with other features. It also supports some of the PVST+ extensions. To enable Rapid-PVST mode on the switch, enter the spanning-tree mode rapid-pvst command in privileged mode. To configure the switch in Rapid-PVST mode, see the Configuring STP section on page 20-22.
Specifying the Link Type

Rapid connectivity is established only on point-to-point links. Spanning tree views a point-to-point link as a segment connecting only two switches running the spanning tree algorithm. Because the switch assumes that all full-duplex links are point-to-point links and that half-duplex links are shared links, you can avoid explicitly configuring the link type. To configure a specific link type, enter the spanning-tree linktype command.
Restarting Protocol Migration

A switch running both MSTP and RSTP supports a built-in protocol migration process that enables the switch to interoperate with legacy 802.1D switches. If this switch receives a legacy 802.1D configuration BPDU (a BPDU with the protocol version set to 0), it sends only 802.1D BPDUs on that port. An MSTP switch can also detect that a port is at the boundary of a region when it receives a legacy BPDU, or an MST BPDU (version 3) associated with a different region, or an RST BPDU (version 2). However, the switch does not automatically revert to the MSTP mode if it no longer receives 802.1D BPDUs because it cannot determine whether the legacy switch has been removed from the link unless the legacy switch is the designated switch. A switch also might continue to assign a boundary role to a port when the switch to which it is connected has joined the region. To restart the protocol migration process (force the renegotiation with neighboring switches) on the entire switch, you can use the clear spanning-tree detected-protocols privileged EXEC command. To restart the protocol migration process on a specific interface, enter the clear spanning-tree detected-protocols interface interface-id privileged EXEC command.
Configuring Prestandard IEEE 802.1s MST

Release 12.2SX supports MST. These sections describe how to configure MST:

Enabling MST, page 20-34 Displaying MST Configurations, page 20-35 Configuring MST Instance Parameters, page 20-39 Configuring MST Instance Port Parameters, page 20-40
20-33
Chapter 20 Configuring Prestandard IEEE 802.1s MST
Restarting Protocol Migration, page 20-40
Enabling MST
To enable and configure MST, perform these tasks in privileged mode: Command
Router# show spanning-tree mst configuration Router(config)# spanning-tree mode mst Router(config)# spanning-tree mst configuration
Purpose Displays the current MST configuration. Configures MST mode. Configures the MST region by entering the MST configuration submode. Clears the MST configuration. Displays the current MST configuration from within the MST configuration submode. Enters the MST configuration.
Router(config)# no spanning-tree mst configuration
Step 4 Step 5
Router(config-mst)# show current
Router(config-mst)# name name revision revision_number instance instance_number vlan vlan_range Router(config-mst)# no instance instance_number
(Optional) Unmaps all VLANs that were mapped to an instance. (Optional) Unmaps a VLAN from an instance. Applies the configuration and exit configuration mode. Shows the MST configuration from the global configuration mode.
Router(config-mst)# no instance instance_number vlan vlan_number Router(config-mst)# end Router# show spanning-tree mst config
These examples show how to enable MST:

Router# show spanning-tree mst configuration % Switch is not in mst mode Name [] Revision 0 Instance Vlans mapped -------- --------------------------------------------------------------------0 1-4094 ------------------------------------------------------------------------------Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# spanning-tree mode mst Router(config)# spanning-tree mst configuration Router(config-mst)# show current Current MST configuration Name [] Revision 0 Instance Vlans mapped -------- --------------------------------------------------------------------0 1-4094 ------------------------------------------------------------------------------Router(config-mst)# name cisco Router(config-mst)# revision 2 Router(config-mst)# instance 1 vlan 1 Router(config-mst)# instance 2 vlan 1-1000
20-34
OL-3999-08
Chapter 20
Router(config-mst)# show pending Pending MST configuration Name [cisco] Revision 2 Instance Vlans mapped -------- --------------------------------------------------------------------0 1001-4094 2 1-1000 ------------------------------------------------------------------------------Router(config-mst)# no instance 2 Router(config-mst)# show pending Pending MST configuration Name [cisco] Revision 2 Instance Vlans mapped -------- --------------------------------------------------------------------0 1-4094 ------------------------------------------------------------------------------Router(config-mst)# instance 1 vlan 2000-3000 Router(config-mst)# no instance 1 vlan 2500 Router(config-mst)# show pending Pending MST configuration Name [cisco] Revision 2 Instance Vlans mapped -------- --------------------------------------------------------------------0 1-1999,2500,3001-4094 1 2000-2499,2501-3000 ------------------------------------------------------------------------------Router(config)# exit Router(config)# no spanning-tree mst configuration Router(config)# do show spanning-tree mst configuration Name [] Revision 0 Instance Vlans mapped -------- --------------------------------------------------------------------0 1-4094 -------------------------------------------------------------------------------
Displaying MST Configurations

To display MST configurations, perform these tasks in MST mode: Command
Router# show spanning-tree mst configuration Router# show spanning-tree mst [detail]
Purpose Displays the active configuration. Displays information about the MST instances currently running. Displays information about a specific MST instance. Displays information for a given port. Displays MST information for a given port and a given instance. Displays detailed MST information. Displays VLAN information in MST mode.
Router# show spanning-tree mst instance-id [detail] Router# show spanning-tree mst interface interface name [detail] Router# show spanning-tree mst number interface interface name [detail] Router# show spanning-tree mst [x] [interface Y] detail Router# show spanning-tree vlan vlan_ID
20-35
These examples show how to display spanning tree VLAN configurations in MST mode:
Router(config)# spanning-tree mst configuration Router(config-mst)# instance 1 vlan 1-10 Router(config-mst)# name cisco Router(config-mst)# revision 1 Router(config-mst)# ^Z Router# show spanning-tree mst configuration Name [cisco] Revision 1 Instance Vlans mapped -------- --------------------------------------------------------------------0 11-4094 1 1-10 -------------------------------------------------------------------------------
20-36
OL-3999-08
Chapter 20
Router# show spanning-tree mst ###### MST00 vlans mapped: 11-4094 Bridge address 00d0.00b8.1400 priority 32768 (32768 sysid Root address 00d0.004a.3c1c priority 32768 (32768 sysid port Fa4/48 path cost 203100 IST master this switch Operational hello time 2, forward delay 15, max age 20, max hops Configured hello time 2, forward delay 15, max age 20, max hops Interface ---------------Fa4/4 Fa4/5 Fa4/48 Role ---Back Desg Root Sts --BLK FWD FWD Cost --------1000 200000 200000 Prio.Nbr -------160.196 128.197 128.240
0) 0)
20 20
Status -------------------------------P2p P2p P2p Bound(STP)
###### MST01 vlans mapped: 1-10 Bridge address 00d0.00b8.1400 priority Root this switch for MST01 Interface ---------------Fa4/4 Fa4/5 Fa4/48 Role ---Back Desg Boun Sts --BLK FWD FWD Cost --------1000 200000 200000 Prio.Nbr -------160.196 128.197 128.240
32769 (32768 sysid 1)
Router# show spanning-tree mst 1 ###### MST01 vlans mapped: 1-10 Bridge address 00d0.00b8.1400 priority Root this switch for MST01 Interface ---------------Fa4/4 Fa4/5 Fa4/48 Role ---Back Desg Boun Sts --BLK FWD FWD Cost --------1000 200000 200000 Prio.Nbr -------160.196 128.197 128.240
32769 (32768 sysid 1)
Router# show spanning-tree mst interface fastEthernet 4/4 FastEthernet4/4 of MST00 is backup blocking Edge port:no (default) port guard :none Link type:point-to-point (auto) bpdu filter:disable Boundary :internal bpdu guard :disable Bpdus sent 2, received 368 Instance -------0 1 Role ---Back Back Sts --BLK BLK Cost --------1000 1000 Prio.Nbr -------160.196 160.196
Vlans mapped ------------------------------11-4094 1-10
Router# show spanning-tree mst 1 interface fastEthernet 4/4 FastEthernet4/4 of MST01 Edge port:no Link type:point-to-point Boundary :internal Bpdus (MRecords) sent 2, is backup blocking (default) port guard :none (auto) bpdu filter:disable bpdu guard :disable received 364
Instance Role Sts Cost Prio.Nbr Vlans mapped -------- ---- --- --------- -------- ------------------------------1 Back BLK 1000 160.196 1-10
20-37
Router# show spanning-tree mst 1 detail ###### MST01 vlans mapped: 1-10 Bridge address 00d0.00b8.1400 priority Root this switch for MST01
32769 (32768 sysid 1)
FastEthernet4/4 of MST01 is backup blocking Port info port id 160.196 priority 160 cost 1000 Designated root address 00d0.00b8.1400 priority 32769 cost 0 Designated bridge address 00d0.00b8.1400 priority 32769 port id 128.197 Timers:message expires in 5 sec, forward delay 0, forward transitions 0 Bpdus (MRecords) sent 123, received 1188 FastEthernet4/5 of MST01 is designated forwarding Port info port id 128.197 priority 128 cost 200000 Designated root address 00d0.00b8.1400 priority 32769 cost 0 Designated bridge address 00d0.00b8.1400 priority 32769 port id 128.197 Timers:message expires in 0 sec, forward delay 0, forward transitions 1 Bpdus (MRecords) sent 1188, received 123 FastEthernet4/48 of MST01 is boundary forwarding Port info port id 128.240 priority 128 cost 200000 Designated root address 00d0.00b8.1400 priority 32769 cost 0 Designated bridge address 00d0.00b8.1400 priority 32769 port id 128.240 Timers:message expires in 0 sec, forward delay 0, forward transitions 1 Bpdus (MRecords) sent 78, received 0 Router# show spanning-tree vlan 10 MST01 Spanning tree enabled protocol mstp Root ID Priority 32769 Address 00d0.00b8.1400 This bridge is the root Hello Time 2 sec Max Age 20 sec Bridge ID Priority Address Hello Time Role ---Back Desg Sts --BLK FWD
32769 (priority 32768 sys-id-ext 1) 00d0.00b8.1400 2 sec Max Age 20 sec Forward Delay 15 sec Cost --------1000 200000 Prio.Nbr -------160.196 128.197 Status -------------------------------P2p P2p
Interface ---------------Fa4/4 Fa4/5
Router# show spanning-tree summary Root bridge for:MST01 EtherChannel misconfiguration guard Extended system ID is enabled Portfast is disabled by PortFast BPDU Guard is disabled by Portfast BPDU Filter is disabled by Loopguard is disabled by UplinkFast is disabled BackboneFast is disabled Pathcost method used is long
is enabled default default default default
Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------MST00 1 0 0 2 3 MST01 1 0 0 2 3 ---------------------- -------- --------- -------- ---------- ---------2 msts 2 0 0 4 6 Router#
20-38
OL-3999-08
Chapter 20
Configuring MST Instance Parameters

To configure MST instance parameters, perform these tasks: Command
Router(config)# spanning-tree mst X priority Y Router(config)# spanning-tree mst X root [primary | secondary] Router# show spanning-tree mst
Purpose Configures the priority for an MST instance. Configures the bridge as root for an MST instance. Verifies the configuration.
This example shows how to configure MST instance parameters:

Router(config)# spanning-tree mst 1 priority ? <0-61440> bridge priority in increments of 4096 Router(config)# spanning-tree mst 1 priority 1 % Bridge Priority must be in increments of 4096. % Allowed values are: 0 4096 8192 12288 16384 20480 24576 28672 32768 36864 40960 45056 49152 53248 57344 61440 Router(config)# spanning-tree mst 1 priority 49152 Router(config)# Router(config)# spanning-tree mst 0 root primary mst 0 bridge priority set to 24576 mst bridge max aging time unchanged at 20 mst bridge hello time unchanged at 2 mst bridge forward delay unchanged at 15 Router(config)# ^Z Router# Router# show spanning-tree mst ###### MST00 vlans mapped: 11-4094 Bridge address 00d0.00b8.1400 priority 24576 (24576 sysid 0) Root this switch for CST and IST Configured hello time 2, forward delay 15, max age 20, max hops 20 Interface ---------------Fa4/4 Fa4/5 Fa4/48 Role ---Back Desg Desg Sts --BLK FWD FWD Cost --------1000 200000 200000 Prio.Nbr -------160.196 128.197 128.240 Status -------------------------------P2p P2p P2p Bound(STP)
###### MST01 vlans mapped: 1-10 Bridge address 00d0.00b8.1400 priority Root this switch for MST01 Interface ---------------Fa4/4 Fa4/5 Fa4/48 Router# Role ---Back Desg Boun Sts --BLK FWD FWD Cost --------1000 200000 200000 Prio.Nbr -------160.196 128.197 128.240
49153 (49152 sysid 1)
20-39
Configuring MST Instance Port Parameters

To configure MST instance port parameters, perform these tasks: Command
Router(config-if)# spanning-tree mst x cost y Router(config-if)# spanning-tree mst x port-priority y Router# show spanning-tree mst x interface y
Purpose Configures the MST instance port cost. Configures the MST instance port priority. Verifies the configuration.
This example shows how to configure MST instance port parameters:

Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree mst 1 ? cost Change the interface spanning tree path cost for an instance port-priority Change the spanning tree port priority for an instance Router(config-if)# spanning-tree mst 1 cost 1234567 Router(config-if)# spanning-tree mst 1 port-priority 240 Router(config-if)# ^Z Router# show spanning-tree mst 1 interface fastEthernet 4/4 FastEthernet4/4 of MST01 is backup blocking Edge port:no (default) port guard :none Link type:point-to-point (auto) bpdu filter:disable Boundary :internal bpdu guard :disable Bpdus (MRecords) sent 125, received 1782
Instance Role Sts Cost Prio.Nbr Vlans mapped -------- ---- --- --------- -------- ------------------------------1 Back BLK 1234567 240.196 1-10 Router#
Restarting Protocol Migration

A switch running both MSTP and RSTP supports a built-in protocol migration mechanism that enables the switch to interoperate with legacy 802.1D switches. If this switch receives a legacy 802.1D configuration BPDU (a BPDU with the protocol version set to 0), it sends only 802.1D BPDUs on that port. An MSTP switch can also detect that a port is at the boundary of a region when it receives a legacy BPDU, an MST BPDU (version 3) associated with a different region, or an RST BPDU (version 2). However, the switch does not automatically revert to the MSTP mode if it no longer receives 802.1D BPDUs because it cannot determine whether the legacy switch has been removed from the link unless the legacy switch is the designated switch. A switch also might continue to assign a boundary role to a port when the switch to which it is connected has joined the region. To restart the protocol migration process (force the renegotiation with neighboring switches) on the entire switch, you can use the clear spanning-tree detected-protocols privileged EXEC command. Use the clear spanning-tree detected-protocols interface interface-id privileged EXEC command to restart the protocol migration process on a specific interface.
20-40
OL-3999-08
Chapter 20
This example shows how to restart protocol migration:

Router# clear spanning-tree detected-protocols interface fastEthernet 4/4 Router#
Tip
20-41
20-42
OL-3999-08
C H A P T E R
21
Configuring Optional STP Features

This chapter describes how to configure optional STP features.
Note
For information on configuring the spanning tree protocol (STP), see Chapter 20, Configuring STP and Prestandard IEEE 802.1s MST.

Understanding How PortFast Works, page 21-2 Understanding How BPDU Guard Works, page 21-2 Understanding How PortFast BPDU Filtering Works, page 21-2 Understanding How UplinkFast Works, page 21-3 Understanding How BackboneFast Works, page 21-4 Understanding How EtherChannel Guard Works, page 21-6 Understanding How Root Guard Works, page 21-7 Understanding How Loop Guard Works, page 21-7 Enabling PortFast, page 21-8 Enabling PortFast BPDU Filtering, page 21-10 Enabling BPDU Guard, page 21-12 Enabling UplinkFast, page 21-12 Enabling BackboneFast, page 21-13 Enabling EtherChannel Guard, page 21-14 Enabling Root Guard, page 21-14 Enabling Loop Guard, page 21-15
21-1
Chapter 21 Understanding How PortFast Works
Tip
Understanding How PortFast Works

STP PortFast causes a Layer 2 LAN port configured as an access port to enter the forwarding state immediately, bypassing the listening and learning states. You can use PortFast on Layer 2 access ports connected to a single workstation or server to allow those devices to connect to the network immediately, instead of waiting for STP to converge. Interfaces connected to a single workstation or server should not receive bridge protocol data units (BPDUs). When configured for PortFast, a port is still running the spanning tree protocol. A PortFast enabled port can immediately transition to the blocking state if necessary (this could happen on receipt of a superior BPDU). PortFast can be enabled on trunk ports. PortFast can have an operational value that is different from the configured value.
Caution
Because the purpose of PortFast is to minimize the time that access ports must wait for STP to converge, it should only be used on access ports. If you enable PortFast on a port connected to a switch, you might create a temporary bridging loop.
Understanding How BPDU Guard Works

When enabled on a port, BPDU Guard shuts down a port that receives a BPDU. When configured globally, BPDU Guard is only effective on ports in the operational PortFast state. In a valid configuration, PortFast Layer 2 LAN interfaces do not receive BPDUs. Reception of a BPDU by a PortFast Layer 2 LAN interface signals an invalid configuration, such as connection of an unauthorized device. BPDU Guard provides a secure response to invalid configurations, because the administrator must manually put the Layer 2 LAN interface back in service. BPDU Guard can be configured at the interface level. When configured at the interface level, BPDU Guard shuts the port down as soon as the port receives a BPDU, regardless of the PortFast configuration.
Note
When enabled globally, BPDU Guard applies to all interfaces that are in an operational PortFast state.
Understanding How PortFast BPDU Filtering Works

PortFast BPDU filtering allows the administrator to prevent the system from sending or even receiving BPDUs on specified ports. When configured globally, PortFast BPDU filtering applies to all operational PortFast ports. Ports in an operational PortFast state are supposed to be connected to hosts, that typically drop BPDUs. If an operational PortFast port receives a BPDU, it immediately loses its operational PortFast status. In that case, PortFast BPDU filtering is disabled on this port and STP resumes sending BPDUs on this port.
21-2
OL-3999-08
Chapter 21
Configuring Optional STP Features Understanding How UplinkFast Works
PortFast BPDU filtering can also be configured on a per-port basis. When PortFast BPDU filtering is explicitly configured on a port, it does not send any BPDUs and drops all BPDUs it receives.
Caution
Configuring PortFast BPDU filtering on a port that is not connected to a host can result in bridging loops. When you enable PortFast BPDU filtering globally and set the port configuration as the default for PortFast BPDU filtering (see the Enabling PortFast BPDU Filtering section on page 21-10), then PortFast enables or disables PortFast BPDU filtering. If the port configuration is not set to default, then the PortFast configuration will not affect PortFast BPDU filtering. Table 21-1 lists all the possible PortFast BPDU filtering combinations. PortFast BPDU filtering allows access ports to move directly to the forwarding state as soon as the end hosts are connected.
Table 21-1 PortFast BPDU Filtering Port Configurations
Per-Port Configuration Default Default Default Disable Enable
Global Configuration Enable Enable Disable Not applicable Not applicable
PortFast State Enable Disable Not applicable Not applicable Not applicable
PortFast BPDU Filtering State Enable1 Disable Disable Disable Enable
1. The port transmits at least 10 BPDUs. If this port receives any BPDUs, then PortFast and PortFast BPDU filtering are disabled.
Understanding How UplinkFast Works

UplinkFast provides fast convergence after a direct link failure and achieves load balancing between redundant Layer 2 links using uplink groups. An uplink group is a set of Layer 2 LAN interfaces (per VLAN), only one of which is forwarding at any given time. Specifically, an uplink group consists of the root port (which is forwarding) and a set of blocked ports, except for self-looping ports. The uplink group provides an alternate path in case the currently forwarding link fails.
Note
UplinkFast is most useful in wiring-closet switches. This feature may not be useful for other types of applications. Figure 21-1 shows an example topology with no link failures. Switch A, the root bridge, is connected directly to Switch B over link L1 and to Switch C over link L2. The Layer 2 LAN interface on Switch C that is connected directly to Switch B is in the blocking state.
21-3
Chapter 21 Understanding How BackboneFast Works
Figure 21-1 UplinkFast Example Before Direct Link Failure
Switch A (Root) L1
Switch B
L2
L3 Blocked port Switch C

11241
If Switch C detects a link failure on the currently active link L2 on the root port (a direct link failure), UplinkFast unblocks the blocked port on Switch C and transitions it to the forwarding state without going through the listening and learning states, as shown in Figure 21-2. This switchover takes approximately one to five seconds.
Figure 21-2 UplinkFast Example After Direct Link Failure
Switch A (Root) L1
Switch B
L2 Link failure
L3 UplinkFast transitions port directly to forwarding state Switch C

11242
Understanding How BackboneFast Works

BackboneFast is initiated when a root port or blocked port on a network device receives inferior BPDUs from its designated bridge. An inferior BPDU identifies one network device as both the root bridge and the designated bridge. When a network device receives an inferior BPDU, it indicates that a link to which the network device is not directly connected (an indirect link) has failed (that is, the designated bridge has lost its connection to the root bridge). Under normal STP rules, the network device ignores inferior BPDUs for the configured maximum aging time, as specified by the STP max-age command. The network device tries to determine if it has an alternate path to the root bridge. If the inferior BPDU arrives on a blocked port, the root port and other blocked ports on the network device become alternate paths to the root bridge. (Self-looped ports are not considered alternate paths to the root bridge.) If the inferior BPDU arrives on the root port, all blocked ports become alternate paths to the root bridge. If the inferior BPDU arrives on the root port and there are no blocked ports, the network device assumes that it has lost connectivity to the root bridge, causes the maximum aging time on the root to expire, and becomes the root bridge according to normal STP rules.
21-4
OL-3999-08
Chapter 21
Configuring Optional STP Features Understanding How BackboneFast Works
If the network device has alternate paths to the root bridge, it uses these alternate paths to transmit a new kind of Protocol Data Unit (PDU) called the Root Link Query PDU. The network device sends the Root Link Query PDU out all alternate paths to the root bridge. If the network device determines that it still has an alternate path to the root, it causes the maximum aging time to expire on the ports on which it received the inferior BPDU. If all the alternate paths to the root bridge indicate that the network device has lost connectivity to the root bridge, the network device causes the maximum aging times on the ports on which it received an inferior BPDU to expire. If one or more alternate paths can still connect to the root bridge, the network device makes all ports on which it received an inferior BPDU its designated ports and moves them out of the blocking state (if they were in the blocking state), through the listening and learning states, and into the forwarding state. Figure 21-3 shows an example topology with no link failures. Switch A, the root bridge, connects directly to Switch B over link L1 and to Switch C over link L2. The Layer 2 LAN interface on Switch C that connects directly to Switch B is in the blocking state.
Figure 21-3 BackboneFast Example Before Indirect Link Failure
Switch A (Root) L1
Switch B
L2
L3 Blocked port Switch C

11241
If link L1 fails, Switch C cannot detect this failure because it is not connected directly to link L1. However, because Switch B is directly connected to the root bridge over L1, it detects the failure and elects itself the root and begins sending BPDUs to Switch C indicating itself as the root. When Switch C receives the inferior BPDUs from Switch B, Switch C infers that an indirect failure has occurred. At that point, BackboneFast allows the blocked port on Switch C to move immediately to the listening state without waiting for the maximum aging time for the port to expire. BackboneFast then transitions the Layer 2 LAN interface on Switch C to the forwarding state, providing a path from Switch B to Switch A. This switchover takes approximately 30 seconds, twice the Forward Delay time if the default Forward Delay time of 15 seconds is set. Figure 21-4 shows how BackboneFast reconfigures the topology to account for the failure of link L1.
21-5
Chapter 21 Understanding How EtherChannel Guard Works
Figure 21-4 BackboneFast Example After Indirect Link Failure
Switch A (Root) L1 Link failure L2 L3
Switch B
Switch C
If a new network device is introduced into a shared-medium topology as shown in Figure 21-5, BackboneFast is not activated because the inferior BPDUs did not come from the recognized designated bridge (Switch B). The new network device begins sending inferior BPDUs that indicate that it is the root bridge. However, the other network devices ignore these inferior BPDUs and the new network device learns that Switch B is the designated bridge to Switch A, the root bridge.
Figure 21-5 Adding a Network Device in a Shared-Medium Topology
Switch A (Root)
Switch C
Blocked port
Switch B (Designated Bridge)
Added switch
11245
Understanding How EtherChannel Guard Works

EtherChannel guard detects a misconfigured EtherChannel where interfaces on the Catalyst 6500 series switch are configured as an EtherChannel while interfaces on the other device are not, or not all the interfaces on the other device are in the same EtherChannel. In response to misconfiguration detected on the other device, EtherChannel guard puts interfaces on the Catalyst 6500 series switch into the errdisabled state.
21-6
11244
BackboneFast transitions port through listening and learning states to forwarding state
OL-3999-08
Chapter 21
Configuring Optional STP Features Understanding How Root Guard Works
Understanding How Root Guard Works

The STP root guard feature prevents a port from becoming root port or blocked port. If a port configured for root guard receives a superior BPDU, the port immediately goes to the root-inconsistent (blocked) state.
Understanding How Loop Guard Works

Loop guard helps prevent bridging loops that could occur because of a uni-directional link failure on a point-to-point link. When enabled globally, the loop guard applies to all point-to-point ports on the system. Loop guard detects root ports and blocked ports and ensures that they keep receiving BPDUs from their designated port on the segment. If a loop guard enabled root or blocked port stop a receiving BPDUs from its designated port, it transitions to the loop-inconsistent blocking state, assuming there is a physical link error on this port. The port recovers from this loop-inconsistent state as soon as it receives a BPDU. You can enable loop guard on a per-port basis. When you enable loop guard, it is automatically applied to all of the active instances or VLANs to which that port belongs. When you disable loop guard, it is disabled for the specified ports. Disabling loop guard moves all loop-inconsistent ports to the listening state. If you enable loop guard on a channel and the first link becomes unidirectional, loop guard blocks the entire channel until the affected port is removed from the channel. Figure 21-6 shows loop guard in a triangle switch configuration.
Figure 21-6 Triangle Switch Configuration with Loop Guard
A 3/1 3/2 3/1
3/2
3/1
3/2
C Designated port
55772
Root port Alternate port
Figure 21-6 illustrates the following configuration:

Switches A and B are distribution switches. Switch C is an access switch. Loop guard is enabled on ports 3/1 and 3/2 on Switches A, B, and C.
Enabling loop guard on a root switch has no effect but provides protection when a root switch becomes a nonroot switch. When using loop guard, follow these guidelines:
21-7
Chapter 21 Enabling PortFast
You cannot enable loop guard on PortFast-enabled ports. You cannot enable loop guard if root guard is enabled. Loop guard does not affect the functionality of UplinkFast or BackboneFast. Enabling loop guard on ports that are not connected to a point-to-point link will not work. Root guard forces a port to be always designated as the root port. Loop guard is effective only if the port is a root port or an alternate port. You cannot enable loop guard and root guard on a port at the same time. Loop guard uses the ports known to spanning tree. Loop guard can take advantage of logical ports provided by the Port Aggregation Protocol (PAgP). However, to form a channel, all the physical ports grouped in the channel must have compatible configurations. PAgP enforces uniform configurations of root guard or loop guard on all the physical ports to form a channel. These caveats apply to loop guard:
Spanning tree always chooses the first operational port in the channel to send the BPDUs. If that
Loop guard interacts with other features as follows:

link becomes unidirectional, loop guard blocks the channel, even if other links in the channel are functioning properly.
If a set of ports that are already blocked by loop guard are grouped together to form a channel,
spanning tree loses all the state information for those ports and the new channel port may obtain the forwarding state with a designated role.
If a channel is blocked by loop guard and the channel breaks, spanning tree loses all the state
information. The individual physical ports may obtain the forwarding state with the designated role, even if one or more of the links that formed the channel are unidirectional.
Note
You can enable UniDirectional Link Detection (UDLD) to help isolate the link failure. A loop may occur until UDLD detects the failure, but loop guard will not be able to detect it.
Loop guard has no effect on a disabled spanning tree instance or a VLAN.
Enabling PortFast
Caution
Use PortFast only when connecting a single end station to a Layer 2 access port. Otherwise, you might create a network loop. To enable PortFast on a Layer 2 access port, perform this task:
Command
Router(config)# interface {type slot/port} | {port-channel port_channel_number} Router(config-if)# spanning-tree portfast
1
Purpose Selects a port to configure. Enables PortFast on a Layer 2 access port connected to a single workstation or server. Enables PortFast.
Router(config-if)# spanning-tree portfast default
21-8
OL-3999-08
Chapter 21
Configuring Optional STP Features Enabling PortFast
Command
Step 4 Step 5
Router(config-if)# end Router# show running interface {type1 slot/port} | {port-channel port_channel_number} 1.
This example shows how to enable PortFast on Fast Ethernet interface 5/8:
Router# configure terminal Router(config)# interface fastethernet 5/8 Router(config-if)# spanning-tree portfast Router(config-if)# end Router#

Router# show running-config interface fastethernet 5/8 Building configuration... Current configuration: ! interface FastEthernet5/8 no ip address switchport switchport access vlan 200 switchport mode access spanning-tree portfast end Router#
To enable the default PortFast configuration, perform this task: Command

Router(config)# spanning-tree portfast default Router(config)# show spanning-tree summary totals Router(config)# show spanning-tree interface x detail Router(config-if)# spanning-tree portfast trunk Router# show spanning-tree interface fastEthernet x detail
Purpose Configures the PortFast default. Verifies the global configuration. Verifies the effect on a specific port. Enables the PortFast trunk on a port Verifies the configuration.
This example shows how to enable the default PortFast configuration:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# spanning-tree portfast default Router(config)# ^Z Root bridge for:VLAN0010 EtherChannel misconfiguration guard is enabled Extended system ID is disabled Portfast is enabled by default PortFast BPDU Guard is disabled by default Portfast BPDU Filter is disabled by default Loopguard is disabled by default UplinkFast is disabled BackboneFast is disabled Pathcost method used is long
21-9
Chapter 21 Enabling PortFast BPDU Filtering
Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------VLAN0001 0 0 0 1 1 VLAN0010 0 0 0 2 2 ---------------------- -------- --------- -------- ---------- ---------2 vlans 0 0 0 3 3 Router# Router# show spanning-tree interface fastEthernet 4/4 detail Port 196 (FastEthernet4/4) of VLAN0010 is forwarding Port path cost 1000, Port priority 160, Port Identifier 160.196. Designated root has priority 32768, address 00d0.00b8.140a Designated bridge has priority 32768, address 00d0.00b8.140a Designated port id is 160.196, designated path cost 0 Timers:message age 0, forward delay 0, hold 0 Number of transitions to forwarding state:1 The port is in the portfast mode by default Link type is point-to-point by default BPDU:sent 10, received 0 Router(config-if)# spanning-tree portfast trunk %Warning:portfast should only be enabled on ports connected to a single host. Connecting hubs, concentrators, switches, bridges, etc... to this interface when portfast is enabled, can cause temporary bridging loops. Use with CAUTION Router(config-if)# ^Z Router# show spanning-tree interface fastEthernet 4/4 detail Port 196 (FastEthernet4/4) of VLAN0010 is forwarding Port path cost 1000, Port priority 160, Port Identifier 160.196. Designated root has priority 32768, address 00d0.00b8.140a Designated bridge has priority 32768, address 00d0.00b8.140a Designated port id is 160.196, designated path cost 0 Timers:message age 0, forward delay 0, hold 0 Number of transitions to forwarding state:1 The port is in the portfast mode by portfast trunk configuration Link type is point-to-point by default BPDU:sent 30, received 0 Router#
Enabling PortFast BPDU Filtering

These sections describe how to configure PortFast BPDU filtering. To enable PortFast BPDU filtering globally, perform this task: Command
Step 1 Step 2
Router(config)# spanning-tree portfast bpdufilter default Router# show spanning-tree summary totals
Purpose Enables BPDU filtering globally on the switch. Verifies the configuration.
BPDU filtering is set to default on each port. This example shows how to enable PortFast BPDU filtering on the port and verify the configuration in PVST+ mode:
21-10
OL-3999-08
Chapter 21
Configuring Optional STP Features Enabling PortFast BPDU Filtering
Note
For PVST+ information, see Chapter 20, Configuring STP and Prestandard IEEE 802.1s MST.
Router(config)# spanning-tree portfast bpdufilter default Router(config)# ^Z Router# show spanning-tree summary totals Root bridge for:VLAN0010 EtherChannel misconfiguration guard is enabled Extended system ID is disabled Portfast is enabled by default PortFast BPDU Guard is disabled by default Portfast BPDU Filter is enabled by default Loopguard is disabled by default UplinkFast is disabled BackboneFast is disabled Pathcost method used is long Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------2 vlans 0 0 0 3 3 Router#
To enable PortFast BPDU filtering on a nontrunking port, perform this task: Command
Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree bpdufilter enable Router# show spanning-tree interface fastEthernet 4/4
Purpose Selects the interface to configure. Enables BPDU filtering. Verifies the configuration.
This example shows how to enable PortFast BPDU filtering on a nontrunking port:
Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree bpdufilter enable Router(config-if)# ^Z Router# show spanning-tree interface fastEthernet 4/4 Vlan Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------VLAN0010 Desg FWD 1000 160.196 Edge P2p Router# show spanning-tree interface fastEthernet 4/4 detail Router# show spanning-tree interface fastEthernet 4/4 detail Port 196 (FastEthernet4/4) of VLAN0010 is forwarding Port path cost 1000, Port priority 160, Port Identifier 160.196. Designated root has priority 32768, address 00d0.00b8.140a Designated bridge has priority 32768, address 00d0.00b8.140a Designated port id is 160.196, designated path cost 0 Timers:message age 0, forward delay 0, hold 0 Number of transitions to forwarding state:1 The port is in the portfast mode by portfast trunk configuration Link type is point-to-point by default Bpdu filter is enabled BPDU:sent 0, received 0 Router#
21-11
Chapter 21 Enabling BPDU Guard
Enabling BPDU Guard

To enable BPDU Guard globally, perform this task: Command
Step 1
Router(config)# spanning-tree portfast bpduguard default Router(config)# no spanning-tree portfast bpduguard default Router(config)# end Router# show spanning-tree summary totals
Purpose Enables BPDU Guard globally. Disables BPDU Guard globally. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to enable BPDU Guard:

Router# configure terminal Router(config)# spanning-tree portfast bpduguard Router(config)# end Router#

Router# show spanning-tree summary totals default Root bridge for:VLAN0010 EtherChannel misconfiguration guard is enabled Extended system ID is disabled Portfast is enabled by default PortFast BPDU Guard is disabled by default Portfast BPDU Filter is enabled by default Loopguard is disabled by default UplinkFast is disabled BackboneFast is disabled Pathcost method used is long Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------2 vlans 0 0 0 3 3 Router#
Enabling UplinkFast
UplinkFast increases the bridge priority to 49152 and adds 3000 to the STP port cost of all Layer 2 LAN interfaces on the Catalyst 6500 series switch, decreasing the probability that the switch will become the root bridge. UplinkFast cannot be enabled on VLANs that have been configured for bridge priority. To enable UplinkFast on a VLAN with bridge priority configured, restore the bridge priority on the VLAN to the default value by entering a no spanning-tree vlan vlan_ID priority command in global configuration mode.
Note
When you enable UplinkFast, it affects all VLANs on the Catalyst 6500 series switch. You cannot configure UplinkFast on an individual VLAN. To enable UplinkFast, perform this task:
21-12
OL-3999-08
Chapter 21
Configuring Optional STP Features Enabling BackboneFast
Command
Step 1
Router(config)# spanning-tree uplinkfast Router(config)# spanning-tree uplinkfast [max-update-rate max_update_rate] Router(config)# no spanning-tree uplinkfast max-update-rate Router(config)# no spanning-tree uplinkfast
Purpose Enables UplinkFast. Enables UplinkFast with an update rate in seconds. Reverts to the default rate. Disables UplinkFast. Exits configuration mode. Verifies that UplinkFast is enabled.
Step 2 Step 3
This example shows how to enable UplinkFast:

Router# configure terminal Router(config)# spanning-tree uplinkfast Router(config)# exit Router#
This example shows how to enable UplinkFast with an update rate of 400 packets per second:
Router# configure terminal Router(config)# spanning-tree uplinkfast Router(config)# spanning-tree uplinkfast max-update-rate 400 Router(config)# exit Router#
This example shows how to verify that UplinkFast is enabled:

Router# show spanning-tree uplinkfast UplinkFast is enabled Router#
Enabling BackboneFast
Note
BackboneFast operates correctly only when enabled on all network devices in the network. BackboneFast is not supported on Token Ring VLANs. This feature is supported for use with third-party network devices. To enable BackboneFast, perform this task:
Command
Step 1
Router(config)# spanning-tree backbonefast Router(config)# no spanning-tree backbonefast
Purpose Enables BackboneFast. Disables BackboneFast. Exits configuration mode. Verifies that BackboneFast is enabled.
Step 2 Step 3
This example shows how to enable BackboneFast:

21-13
Chapter 21 Enabling EtherChannel Guard
Router(config)# spanning-tree backbonefast Router(config)# end Router#
This example shows how to verify that BackboneFast is enabled:

Router# show spanning-tree backbonefast BackboneFast is enabled BackboneFast statistics ----------------------Number of transition via backboneFast (all VLANs) Number of inferior BPDUs received (all VLANs) Number of RLQ request PDUs received (all VLANs) Number of RLQ response PDUs received (all VLANs) Number of RLQ request PDUs sent (all VLANs) Number of RLQ response PDUs sent (all VLANs) Router#
: : : : : :
0 0 0 0 0 0
Enabling EtherChannel Guard

To enable EtherChannel guard, perform this task: Command
Step 1
Router(config)# spanning-tree etherchannel guard misconfig Router(config)# no spanning-tree etherchannel guard misconfig
Purpose Enables EtherChannel guard. Disables EtherChannel guard. Exits configuration mode. Verifies that EtherChannel guard is enabled.
Step 2 Step 3
Router(config)# end Router# show spanning-tree summary | include EtherChannel
This example shows how to enable EtherChannel guard:

Router# configure terminal Router(config)# spanning-tree etherchannel guard misconfig Router(config)# end Router#

Router# show spanning-tree summary | include EtherChannel EtherChannel misconfiguration guard is enabled
To display the interfaces that are in the errdisable state, enter the show interface status err-disable command. After the misconfiguration has been cleared, interfaces in the errdisable state might automatically recover. To manually return a port to service, enter a shutdown and then a no shutdown command for the interface.
Enabling Root Guard

To enable root guard, perform this task:
21-14
OL-3999-08
Chapter 21
Configuring Optional STP Features Enabling Loop Guard
Command
Step 1 Step 2
Router(config)# interface {type slot/port} | {port-channel port_channel_number} Router(config-if)# spanning-tree guard root Router(config-if)# no spanning-tree guard root
1
Purpose Selects a port to configure. Enables root guard. Disables root guard. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show spanning-tree Router# show running interface {type1 slot/port} | {port-channel port_channel_number} 1.
To display ports that are in the root-inconsistent state, enter the show spanning-tree inconsistentports command.
Enabling Loop Guard

To enable loop guard globally on the switch, perform this task: Command
Router(config)# spanning-tree loopguard default Router(config)# end Router# show spanning-tree interface 4/4 detail
Purpose Enables loop guard globally on the switch. Exits configuration mode. Verifies the configuration impact on a port.
This example shows how to enable loop guard globally:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# spanning-tree loopguard default Router(config)# ^Z Router# show spanning-tree interface fastEthernet 4/4 detail Port 196 (FastEthernet4/4) of VLAN0010 is forwarding Port path cost 1000, Port priority 160, Port Identifier 160.196. Designated root has priority 32768, address 00d0.00b8.140a Designated bridge has priority 32768, address 00d0.00b8.140a Designated port id is 160.196, designated path cost 0 Timers:message age 0, forward delay 0, hold 0 Number of transitions to forwarding state:1 The port is in the portfast mode by portfast trunk configuration Link type is point-to-point by default Bpdu filter is enabled Loop guard is enabled by default on the port BPDU:sent 0, received 0
To enable loop guard on a port, perform this task:
21-15
Chapter 21 Enabling Loop Guard
Command
Router(config)# interface {type slot/port} | {port-channel port_channel_number} Router(config-if)# spanning-tree guard loop Router(config)# end Router# show spanning-tree interface 4/4 detail 1.
1
Purpose Selects a port to configure. Configures loop guard. Exits configuration mode. Verifies the configuration impact on that port.
This example shows how to enable loop guard:

Router# configure terminal Enter configuration commands, one per line. Router(config)# interface fastEthernet 4/4 Router(config-if)# spanning-tree guard loop Router(config-if)# ^Z End with CNTL/Z.

Router# show spanning-tree interface fastEthernet 4/4 detail Port 196 (FastEthernet4/4) of VLAN0010 is forwarding Port path cost 1000, Port priority 160, Port Identifier 160.196. Designated root has priority 32768, address 00d0.00b8.140a Designated bridge has priority 32768, address 00d0.00b8.140a Designated port id is 160.196, designated path cost 0 Timers:message age 0, forward delay 0, hold 0 Number of transitions to forwarding state:1 The port is in the portfast mode by portfast trunk configuration Link type is point-to-point by default Bpdu filter is enabled Loop guard is enabled on the port BPDU:sent 0, received 0 Router#
Tip
21-16
OL-3999-08
C H A P T E R
22

This chapter contains information about how to configure Layer 3 interfaces on the Catalyst 6500 series switches. For complete syntax and usage information for the commands used in this chapter, refer to these publications:
Note

Layer 3 Interface Configuration Guidelines and Restrictions, page 22-2 Configuring Subinterfaces on Layer 3 Interfaces, page 22-2 Configuring IPv4 Routing and Addresses, page 22-4 Configuring IPX Routing and Network Numbers, page 22-8 Configuring AppleTalk Routing, Cable Ranges, and Zones, page 22-9 Configuring Other Protocols on Layer 3 Interfaces, page 22-10
Tip
22-1
Chapter 22 Layer 3 Interface Configuration Guidelines and Restrictions
Layer 3 Interface Configuration Guidelines and Restrictions

When configuring Layer 3 interfaces, follow these guidelines and restrictions:

We recommend that you configure no more than 2,000 Layer 3 VLAN interfaces. Release 12.2(18)SXE and later releases supports the ip unnumbered command on Layer 3 VLAN interfaces. Release 12.2(18)SXE and later releases supports the [no] ip dhcp route [connected | static ] command. To support VLAN interfaces, create and configure VLANs and assign VLAN membership to Layer 2 LAN ports. For more information, see Chapter 14, Configuring VLANs and Chapter 13, Configuring VTP. Catalyst 6500 series switches do not support:
Integrated routing and bridging (IRB) Concurrent routing and bridging (CRB) Remote source-route bridging (RSRB)
Use bridge groups on VLAN interfaces, sometimes called fall-back bridging, to bridge nonrouted protocols. Bridge groups on VLAN interfaces are supported in software on the MSFC. Catalyst 6500 series switches do not support the IEEE bridging protocol for bridge groups. Configure bridge groups to use the VLAN-bridge or the DEC spanning-tree protocol.
Configuring Subinterfaces on Layer 3 Interfaces

When configuring Layer 3 subinterfaces, follow these guidelines and restrictions:
With a PFC3, Release 12.2(18)SXE and later releases support these features on LAN port subinterfaces:
IPv4 unicast forwarding, including MPLS VPN IPv4 multicast forwarding, including MPLS VPN 6PE EoMPLS IPv4 unnumbered Counters for subinterfaces in MIBS and with the show vlans command iBGP and eBGP OSPF EIGRP RIPv1/v2 RIPv2 ISIS Static routing Unidirectional link routing (UDLR) IGMPv1, IGMPv2, IGMPv3
22-2
OL-3999-08
Chapter 22
Configuring Layer 3 Interfaces Configuring Subinterfaces on Layer 3 Interfaces
PIMv1, PIMv2 SSM IGMPv3lite and URD Stub IP multicast routing IGMP join IGMP static group Multicast routing monitor (MRM) Multicast source discovery protocol (MSDP) SSM IPv4 Ping IPv6 Ping
These restrictions apply to releases earlier than Release 12.2(18)SXE:

Configure subinterfaces only to support MPLS. Do not configure ISL encapsulation.
Always use the native keyword when the VLAN ID is the ID of the IEEE 802.1Q native VLAN. Do not configure encapsulation on the native VLAN of an IEEE 802.1Q trunk without the native keyword. Because VLAN IDs are global to the switch, you can use a VLAN internally, on a subinterface, or with a Layer 3 VLAN interface.
You cannot configure an internal VLAN on a subinterface or a Layer 3 VLAN interface. You cannot configure a subinterface VLAN on a Layer 3 VLAN interface. You cannot configure a VLAN used with a Layer 3 VLAN interface on a subinterface.
Note
You cannot configure a VLAN used on one interface or subinterface on another interface or subinterface.
You can configure subinterfaces with any normal range or extended range VLAN ID in VTP transparent mode. Because VLAN IDs 1 to 1005 are global in the VTP domain and can be defined on other network devices in the VTP domain, you can use only extended range VLANs with subinterfaces in VTP client or server mode. In VTP client or server mode, normal range VLANs are excluded from subinterfaces.
Note
If you configure normal range VLANs on subinterfaces, you cannot change the VTP mode from transparent.
To configure a subinterface, perform this task: Command

Router> enable Router# configure terminal Router(config)# interface {{type1 slot/port.subinterface} | {port-channel port_channel_number.subinterface}}
Purpose Enters privileged EXEC mode. Enters global configuration mode. Selects an interface and enters subinterface configuration mode.
22-3
Chapter 22 Configuring IPv4 Routing and Addresses
Command
Step 4 Step 5
Router(config-subif)# encapsulation dot1q vlan_ID [native] Router(config-if)# exit 1.
Purpose Configures 802.1Q encapsulation for the subinterface. Returns to global configuration mode.
Configuring IPv4 Routing and Addresses

For complete information and procedures, refer to these publications:
Cisco IOS IP and IP Routing Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/fipr_c.html
Cisco IOS IP and IP Routing Command Reference , Release 12.2, at these URLs: http://www.cisco.com/en/US/docs/ios/12_2/ipaddr/command/reference/fipras_r.html http://www.cisco.com/en/US/docs/ios/12_2/iproute/command/reference/fiprrp_r.html
When configuring IPv4 routing and addresses, follow these guidelines and restrictions:

For information about the maximum paths command, refer to the Cisco IOS Master Command List, Release 12.2SX publication. The Policy Feature Card (PFC) and any Distributed Feature Cards (DFCs) provide hardware support for policy-based routing (PBR) for route-map sequences that use the match ip address , set ip next-hop, and ip default next-hop PBR keywords. When configuring PBR, follow these guidelines and restrictions:
The PFC provides hardware support for PBR configured on a tunnel interface. The PFC does not provide hardware support for PBR configured with the set ip next-hop
keywords if the next hop is a tunnel interface.

If the MSFC address falls within the range of a PBR ACL, traffic addressed to the MSFC is
policy routed in hardware instead of being forwarded to the MSFC. To prevent policy routing of traffic addressed to the MSFC, configure PBR ACLs to deny traffic addressed to the MSFC.
Any options in Cisco IOS ACLs that provide filtering in a PBR route-map that would cause
flows to be sent to the MSFC to be switched in software are ignored. For example, logging is not supported in ACEs in Cisco IOS ACLs that provide filtering in PBR route-maps.
PBR traffic through switching module ports where PBR is configured is routed in software if
the switching module resets. (CSCee92191)

Any permit route-map sequence with no set statement will cause matching traffic to be
processed by the MSFC.

In Cisco IOS Release 12.2(33)SXF16 and later releases, for efficient use of hardware resources,
enter the platform ipv4 pbr optimize tcam command in global configuration mode when configuring multiple PBR sequences (or a single PBR sequence with multiple ACLs) in which more than one PBR ACL contains DENY entries. In earlier releases, we recommend avoiding this type of configuration. (CSCsr45495)
In Cisco IOS Release 12.2(33)SXH4 and later releases, the BOOTP/DHCP traffic will be
dropped unless explicitly permitted. In Cisco IOS Release 12.2(18)SXF, BOOTP/DHCP packets are not subjected to a PBR configured in the ingress interfaces and the BOOTP/DHCP packets are forwarded to the BOOTP/DHCP server, although they are not explicitly permitted.
22-4
OL-3999-08
Chapter 22
Configuring Layer 3 Interfaces Configuring IPv4 Routing and Addresses
To configure PBR, refer to the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2, Classification, Configuring Policy-Based Routing, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/qcfpbr_ps1835_TSD_Products_C onfiguration_Guide_Chapter.html
22-5
Chapter 22 Configuring IPv4 Routing and Addresses
To configure IPv4 routing and an IPv4 address on a Layer 3 interface, perform this task: Command
Router(config)# ip routing
Purpose Enables IPv4 routing. (Required only if IPv4 routing is disabled.) Specifies an IPv4 routing protocol. Configures the IPv4 routing protocol. Exists IPv4 routing protocol configuration mode. Selects an interface to configure.
Router(config)# router ip_routing_protocol Router(config-router)# ip_routing_protocol_commands Router(config-router)# exit Router(config)# interface {vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number} Router(config-if)# ip address ip_address subnet_mask Router(config-if)# no shutdown Router(config-if)# end Router# show interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] Router# show ip interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] Router# show running-config interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] 1.
Configures the IPv4 address and IPv4 subnet. Enables the interface. Exits configuration mode. Verifies the configuration.
This example shows how to enable IPv4 Routing Information Protocol (RIP) routing:
Router# configure terminal Enter configuration commands, one per line. Router(config)# ip routing Router(config)# router rip Router(config-router)# network 10.0.0.0 Router(config-router)# end Router# End with CNTL/Z.
This example shows how to configure an IPv4 address on Fast Ethernet port 5/4:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/4 Router(config-if)# ip address 172.20.52.106 255.255.255.248 Router(config-if)# no shutdown Router(config-if)# end Router#
This example uses the show interfaces command to display the interface IPv4 address configuration and status of Fast Ethernet port 5/4:
Router# show interfaces fastethernet 5/4 FastEthernet5/4 is up, line protocol is up Hardware is Cat6K 100Mb Ethernet, address is 0050.f0ac.3058 (bia 0050.f0ac.3058) Internet address is 172.20.52.106/29 MTU 1500 bytes, BW 100000 Kbit, DLY 100 usec, reliability 255/255, txload 1/255, rxload 1/255 Encapsulation ARPA, loopback not set
22-6
OL-3999-08
Chapter 22
Configuring Layer 3 Interfaces Configuring IPv4 Routing and Addresses
Keepalive set (10 sec) Full-duplex, 100Mb/s ARP type: ARPA, ARP Timeout 04:00:00 Last input 00:00:01, output never, output hang never Last clearing of "show interface" counters never Queueing strategy: fifo Output queue 0/40, 0 drops; input queue 0/75, 0 drops 5 minute input rate 0 bits/sec, 0 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 7 packets input, 871 bytes, 0 no buffer Received 0 broadcasts, 0 runts, 0 giants, 0 throttles 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 8 packets output, 1658 bytes, 0 underruns 0 output errors, 0 collisions, 4 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Router#
This example uses the show ip interface command to display the detailed configuration and status of Fast Ethernet port 5/4:
Router# show ip interface fastethernet 5/4 FastEthernet5/4 is up, line protocol is up Internet address is 172.20.52.106/29 Broadcast address is 255.255.255.255 Address determined by setup command MTU is 1500 bytes Helper address is not set Directed broadcast forwarding is disabled Multicast reserved groups joined: 224.0.0.10 Outgoing access list is not set Inbound access list is not set Proxy ARP is enabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is disabled IP Flow switching is disabled IP CEF switching is enabled IP Fast switching turbo vector IP Normal CEF switching turbo vector IP multicast fast switching is enabled IP multicast distributed fast switching is disabled Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Probe proxy name replies are disabled Policy routing is disabled Network address translation is disabled WCCP Redirect outbound is disabled WCCP Redirect exclude is disabled BGP Policy Mapping is disabled IP multicast multilayer switching is disabled IP mls switching is enabled Router#
22-7
Chapter 22 Configuring IPX Routing and Network Numbers
This example uses the show running-config command to display the interface IPv4 address configuration of Fast Ethernet port 5/4:
Router# show running-config interfaces fastethernet 5/4 Building configuration... Current configuration: ! interface FastEthernet5/4 description "Router port" ip address 172.20.52.106 255.255.255.248 no ip directed-broadcast !
Configuring IPX Routing and Network Numbers

Note
The MSFC supports IPX with fast switching. For complete information and procedures, refer to these publications:
Cisco IOS AppleTalk and Novell IPX Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/atipx/configuration/guide/fatipx_c.html Cisco IOS AppleTalk and Novell IPX Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/atipx/command/reference/fatipx_r.html
To configure routing for Internetwork Packet Exchange (IPX) and configure IPX on a Layer 3 interface, perform this task: Command
Step 1 Step 2
Router(config)# ipx routing Router(config)# router ipx_routing_protocol
Purpose Enables IPX routing. Specifies an IP routing protocol. This step might include other commands, such as specifying the networks to route with the network command. Selects an interface to configure.
Step 3
Router(config)# interface {vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number} Router(config-if)# ipx network [network | unnumbered] encapsulation encapsulation_type
Step 4
Configures the IPX network number. This enables IPX routing on the interface. When you enable IPX routing on the interface, you can also specify an encapsulation type. Enables the interface. Exits configuration mode. Verifies the configuration.
Router(config-if)# no shutdown Router(config-if)# end Router# show interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] Router# show ipx interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] Router# show running-config interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}]
22-8
OL-3999-08
Chapter 22
Configuring Layer 3 Interfaces Configuring AppleTalk Routing, Cable Ranges, and Zones
1.
type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet , or ge-wan
This example shows how to enable IPX routing and assign an IPX network address to interface VLAN 100:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ipx routing Router(config)# ipx router rip Router(config-ipx-router)# network all Router(config-ipx-router)# interface vlan 100 Router(config-if)# ipx network 100 encapsulation snap Router(config-if)# no shutdown Router(config-if)# end Router# copy running-config startup-config
Configuring AppleTalk Routing, Cable Ranges, and Zones

For complete information and procedures, refer to these publications:
Cisco IOS AppleTalk and Novell IPX Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/atipx/configuration/guide/fatipx_c.html
Cisco IOS AppleTalk and Novell IPX Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/atipx/command/reference/fatipx_r.html
To configure routing for AppleTalk, perform this task beginning in global configuration mode: Command
Step 1 Step 2
Router(config)# appletalk routing Router(config)# interface {vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number} Router(config-if)# appletalk cable-range cable_range Router(config-if)# appletalk zone zone_name Router(config-if)# no shutdown Router(config-if)# end Router# show interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] Router# show appletalk interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] Router# show running-config interfaces [{vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number}] 1.
Purpose Enables AppleTalk routing. Selects an interface to configure.
Assigns a cable range to the interface. Assigns a zone name to the interface. Enables the interface. Exits configuration mode. Verifies the configuration.
type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet , or ge-wan
This example shows how to enable AppleTalk routing and assign an AppleTalk cable-range and zone name to interface VLAN 100:
22-9
Chapter 22 Configuring Other Protocols on Layer 3 Interfaces
Enter configuration commands, one per line. End with CNTL/Z. Router(config)# appletalk routing Router(config)# interface vlan 100 Router(config-if)# appletalk cable-range 100-100 Router(config-if)# appletalk zone Engineering Router(config-if)# no shutdown Router(config-if)# end Router# copy running-config startup-config
Configuring Other Protocols on Layer 3 Interfaces

Refer to these publications for information about configuring other protocols on Layer 3 interfaces:
Cisco IOS Apollo Domain, VINES, DECnet, ISO CLNS, and XNS Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/apollo/configuration/guide/fapolo_c.html Cisco IOS Apollo Domain, VINES, DECnet, ISO CLNS, and XNS Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/apollo/command/reference/fapolo_r.html
Tip
22-10
OL-3999-08
C H A P T E R
23
Configuring UDE and UDLR

This chapter describes how to configure unidirectional Ethernet (UDE) and unidirectional link routing (UDLR) on the Catalyst 6500 series switch. Release 12.2(18)SXE and later releases support UDE and UDLR.
Note
These sections describe UDE and UDLR:

Understanding UDE and UDLR, page 23-1 Configuring UDE and UDLR, page 23-3
Tip
Understanding UDE and UDLR

These sections describe UDE and UDLR:

UDE and UDLR Overview, page 23-2 Supported Hardware, page 23-2 Understanding UDE, page 23-2 Understanding UDLR, page 23-3
23-1
Chapter 23 Understanding UDE and UDLR
UDE and UDLR Overview

Routing protocols support unidirectional links only if the unidirectional links emulate bidirectional links because routing protocols expect to send and receive traffic through the same interface. Unidirectional links are advantageous because when you transmit mostly unacknowledged unidirectional high-volume traffic (for example, a video broadcast stream) over a high-capacity full-duplex bidirectional link, you use both the link from the source to the receiver and the equally high-capacity reverse-direction link, called the back channel, that carries the few acknowledgements from the receiver back to the source. UDE and UDLR support use of a high-capacity unidirectional link for the high-volume traffic without consuming a similar high-capacity link for the back channel. UDE provides a high-capacity unidirectional link. UDLR provides the back channel through a tunnel that is configured over a regular-capacity link, and also provides bidirectional link emulation by transparently making the back channel appear to be on the same interface as the high-capacity unidirectional link.
Supported Hardware
On Catalyst 6500 series switches, UDE and UDLR are supported on the interfaces of these switching modules:

WS-X6704-10GE 4-port 10-Gigabit Ethernet WS-X6816-GBIC 16-port Gigabit Ethernet WS-X6516A-GBIC 16-port Gigabit Ethernet WS-X6516-GBIC 16-port Gigabit Ethernet
Understanding UDE
These sections describe UDE:

UDE Overview, page 23-2 Understanding Hardware-Based UDE, page 23-3 Understanding Software-Based UDE, page 23-3
UDE Overview
On Catalyst 6500 series switches, you can implement UDE with hardware or in software. Hardware-based UDE and software-based UDE both use only one strand of fiber instead of the two strands of fiber required by bidirectional traffic. The unidirectional transceiver determines whether hardware-based UDE is receive-only or transmit-only. You can configure software-based UDE as either transmit-only or receive-only. You do not need to configure software-based UDE on ports where you implement hardware-based UDE.
Note
Refer to the Supported Hardware section on page 23-2 for a list of the module with interfaces that support hardware-based UDE and software-based UDE.
23-2
OL-3999-08
Chapter 23
Configuring UDE and UDLR Configuring UDE and UDLR
Understanding Hardware-Based UDE

You can create a unidirectional link by using a unidirectional transceiver. Unidirectional transceivers are less expensive than bidirectional transceivers. Release 12.2(18)SXE and later releases support these unidirectional transceivers:

Receive-only WDM GBIC (WDM-GBIC-REC=) Receive-only XENPAK (WDM-XENPAK-REC=)
Understanding Software-Based UDE

You can create a unidirectional link by configuring ports equipped with bidirectional transceivers to unidirectionally transmit or receive traffic. You can use software-based UDE when there is no appropriate unidirectional transceiver available. For example, with no support for any transmit-only transceivers, you must configure transmit-only links with software-based UDE.
Understanding UDLR
UDLR provides a unidirectional tunnel as the back channel of a unidirectional high-capacity link, and transparently emulates a single bidirectional link for unicast and multicast traffic. UDLR intercepts packets that need to be sent on receive-only interfaces and sends them on UDLR back-channel tunnels. When routers receive these packets over UDLR back-channel tunnels, UDLR makes the packets appear as if received on send-only interfaces. UDLR back-channel tunnels support these IPv4 features:

Address Resolution Protocol (ARP) Next Hop Resolution Protocol (NHRP) Emulation of a bidirectional link for all IPv4 traffic (as opposed to only broadcast and multicast control traffic) IPv4 GRE multipoint at a receive-only tunnels
Note
UDLR back-channel tunnels do not support IPv6 or MPLS.

These sections describe how to configure UDE and UDLR:

Configuring UDE, page 23-4 Configuring UDLR, page 23-6
Note
This caveat is open in releases that support UDLR: Neighboring ISIS routers are not seen through a UDLR topology. (CSCee56596)
23-3
Chapter 23 Configuring UDE and UDLR
Configuring UDE
These sections describe how to configure UDE:

UDE Configuration Guidelines, page 23-4 Configuring Hardware-Based UDE, page 23-5 Configuring Software-Based UDE, page 23-5
UDE Configuration Guidelines

When configuring UDE, follow these guidelines:

UDE is supported on the Supervisor Engine 720. UDE is not supported on the Supervisor Engine 2. STP cannot prevent Layer 2 loops in topologies that include unidirectional links. Send-only ports always transition to the STP forwarding state, because send-only ports never receive BPDUs. Receive-only ports cannot send BPDUs. Unidirectional ports do not support any features or protocols that require negotiation with the port at the other end of the link, including these:
Speed and duplex mode autonegotiation Link negotiation IEEE 802.3Z flow control Dynamic trunking protocol (DTP)
You must manually configure the parameters that are typically controlled by Layer 2 protocols.

A topology that includes unidirectional links only supports the VLAN Trunking Protocol (VTP) when the VTP server can send VTP frames to all switches in the VTP domain. Disable VTP pruning on switches that have send-only ports, because VTP pruning depends on a bidirectional exchange of information. Unidirectional EtherChannels cannot support PAgP or LACP. To create a unidirectional EtherChannel, you must configure the EtherChannel on mode. You can configure software-based UDE on the physical ports in an EtherChannel. You cannot configure software-based UDE on any nonphysical interfaces (for example, port-channel interfaces). When you implement hardware-based UDE on a port or configure software-based UDE on a port, UDLD is automatically disabled on the port. CDP sends CDP frames from send-only ports and receives CDP frames from receive-only ports, which means that the switch on the send-only side of a unidirectional link never receives CDP information. SPAN does not restrict configuration of unidirectional ports as sources or destinations.
Send-only ports can be SPAN destinations. Receive-only ports can be SPAN sources.
Unidirectional ports do not support IEEE 802.1X port-based authentication. IGMP snooping does not support topologies where there are unidirectional links between the switch and the hosts that are receiving multicast traffic.
23-4
OL-3999-08
Chapter 23
Configure UDLR with UDE to support communication over unidirectional links between IGMP snooping on the switch and a multicast router. Unidirectional links do not support ARP.
Configuring Hardware-Based UDE

There are no software configuration procedures required to support hardware-based UDE. Install a unidirectional transceiver to implement hardware-based UDE. To verify hardware-based UDE on a port, perform this task: Command
Router# show interfaces [{gigabitethernet | tengigabitethernet} slot/interface}] status
Purpose Verifies the configuration.
This example shows how to verify the configuration of Gigabit Ethernet port 1/1:
Router# show interfaces gigabitethernet 1/1 status Port Gi1/1 Name Status notconnect Vlan 1 Duplex full Speed Type 1000 WDM-RXONLY
Configuring Software-Based UDE

To configure software-based UDE on a port, perform this task: Command
Step 1 Step 2
Router(config)# interface {{gigabitethernet | tengigabitethernet} slot/interface} Router(config-if)# unidirectional {send-only | receive-only} Router(config-if)# no unidirectional
Purpose Selects the interface to configure. Configures software-based UDE. Removes the software-based UDE configuration. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show interface {{gigabitethernet | tengigabitethernet} slot/interface} unidirectional
This example shows how to configure 10 Gigabit Ethernet port 1/1 as a UDE send-only port:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 1/1 Router(config-if)# unidirectional send-only Router(config-if)# end Warning! Enable port unidirectional mode will automatically disable port udld. You must manually ensure that the unidirectional link does not create a spanning tree loop in the network. Enable l3 port unidirectional mode will automatically disable ip routing on the port. You must manually configure static ip route and arp entry in order to route ip traffic.
23-5
This example shows how to configure 10 Gigabit Ethernet port 1/2 as a UDE receive-only port:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 1/2 Router(config-if)# unidirectional receive-only Router(config-if)# end Warning! Enable port unidirectional mode will automatically disable port udld. You must manually ensure that the unidirectional link does not create a spanning tree loop in the network. Enable l3 port unidirectional mode will automatically disable ip routing on the port. You must manually configure static ip route and arp entry in order to route ip traffic.

Router> show interface tengigabitethernet 1/1 unidirectional Unidirectional configuration mode: send only CDP neighbour unidirectional configuration mode: receive only
This example shows how to disable UDE on 10 Gigabit Ethernet interface 1/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 1/1 Router(config-if)# no unidirectional Router(config-if)# end
This example shows the result of entering the show interface command for a port that does not support unidirectional Ethernet:
Router# show interface fastethernet 6/1 unidirectional Unidirectional Ethernet is not supported on FastEthernet6/1
Configuring UDLR
These sections describe how to configure UDLR:

UDLR Back-Channel Tunnel Configuration Guidelines, page 23-6 Configuring a Receive-Only Tunnel Interface for a UDE Send-Only Port, page 23-7 Configuring a Send-Only Tunnel Interface for a UDE Receive-Only Port, page 23-7
UDLR Back-Channel Tunnel Configuration Guidelines

When configuring UDLR back-channel tunnels, follow these guidelines:

The PFC3 does not provide hardware support for UDLR back-channel tunnels. The MSFC3 supports UDLR back-channel tunnels in software. Configure a UDLR back-channel tunnel for each unidirectional link. On UDE send-only interfaces, configure the UDLR back-channel tunnel interface to receive. On UDE receive-only interfaces, configure the UDLR back-channel tunnel interface to send. You must configure IPv4 addresses on UDLR back-channel tunnel interfaces. You must configure source and destination IPv4 addresses on UDLR back-channel tunnel interfaces. The UDLR back-channel tunnel default mode is GRE.
23-6
OL-3999-08
Chapter 23
UDLR back-channel tunnels do not support IPv6 or MPLS.
Configuring a Receive-Only Tunnel Interface for a UDE Send-Only Port

To configure a receive-only tunnel interface for a UDE send-only port, perform this task: Command
Router(config)# interface tunnel number Router(config-if)# tunnel udlr receive-only ude_send_only_port Router(config-if)# ip address ipv4_address Router(config-if)# tunnel source {ipv4_address | type number} Router(config-if)# tunnel destination {hostname | ipv4_address}
Purpose Selects the tunnel interface. Associates the tunnel receive-only interface with the UDE send-only port. Configures the tunnel IPv4 address. Configures the tunnel source. Configures the tunnel destination.
Configuring a Send-Only Tunnel Interface for a UDE Receive-Only Port

To configure a send-only tunnel interface for a UDE receive-only port, perform this task: Command
Router(config)# interface tunnel number Router(config-if)# tunnel udlr send-only ude_receive_only_port Router(config-if)# ip address ipv4_address Router(config-if)# tunnel source {ipv4_address | type number} Router(config-if)# tunnel destination {hostname | ipv4_address} Router(config-if)# tunnel udlr address-resolution
Purpose Selects the tunnel interface. Associates the tunnel send-only interface with the UDE receive-only port. Configures the tunnel IPv4 address. Configures the tunnel source. Configures the tunnel destination. Enables ARP and NHRP.
In the following UDE and UDLR sample configuration:
On Router A:
Open Shortest Path First (OSPF) and PIM are configured. 10 Gigabit Ethernet port 1/1 is a send-only UDE port. The UDLR back-channel tunnel is configured as receive only and is associated with 10 Gigabit
Ethernet port 1/1.
On Router B:
OSPF and PIM are configured. 10 Gigabit Ethernet port 1/2 is a receive-only UDE port. The UDLR back-channel tunnel is configured as send-only and is associated with 10 Gigabit
Ethernet port 1/2.

ARP and NHRP are enabled.
23-7
Router A Configuration
ip multicast-routing ! ! tengigabitethernet 1/1 is send-only ! interface tengigabitethernet 1/1 unidirectional send-only ip address 10.1.0.1 255.255.0.0 ip pim sparse-dense-mode ! ! Configure tunnel as receive-only UDLR tunnel. ! interface tunnel 0 tunnel source 11.0.0.1 tunnel destination 11.0.0.2 tunnel udlr receive-only tengigabitethernet 1/1 ! ! Configure OSPF. ! router ospf <pid> network 10.0.0.0 0.255.255.255 area 0
Router B Configuration
ip multicast-routing ! ! tengigabitethernet 1/2 is receive-only ! interface tengigabitethernet 1/2 unidirectional receive-only ip address 10.1.0.2 255.255.0.0 ip pim sparse-dense-mode ! ! Configure tunnel as send-only UDLR tunnel. ! interface tunnel 0 tunnel source 11.0.0.2 tunnel destination 11.0.0.1 tunnel udlr send-only tengigabitethernet 1/2 tunnel udlr address-resolution ! ! Configure OSPF. ! router ospf <pid> network 10.0.0.0 0.255.255.255 area 0
Tip
23-8
OL-3999-08
C H A P T E R
24
Configuring PFC3BXL and PFC3B Mode Multiprotocol Label Switching

This chapter describes how to configure PFC3BXL and PFC3B mode Multiprotocol Label Switching (MPLS) on a Catalyst 6500 series switch.
Note
The Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
The Release 12.2 publications at this URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configuratio n_guides_list.html

PFC3BXL and PFC3B Mode MPLS Label Switching, page 24-1 PFC3BXL or PFC3B Mode VPN Switching, page 24-10 Any Transport over MPLS, page 24-13
Tip
PFC3BXL and PFC3B Mode MPLS Label Switching

These sections describe PFC3BXL and PFC3B mode MPLS label switching:

Understanding MPLS, page 24-2 Understanding PFC3BXL and PFC3B Mode MPLS Label Switching, page 24-2
24-1
Chapter 24 PFC3BXL and PFC3B Mode MPLS Label Switching
Supported Hardware Features, page 24-5 Supported Cisco IOS Features, page 24-5 MPLS Guidelines and Restrictions, page 24-7 Configuring MPLS, page 24-8 MPLS Per-Label Load Balancing, page 24-8 MPLS Configuration Examples, page 24-8
Understanding MPLS
MPLS uses label switching to forward packets over various link-level technologies such as Packet-over-SONET (POS), Frame Relay, ATM, and Ethernet. Labels are assigned to packets based on groupings or forwarding equivalence classes (FECs). The label is added between the Layer 2 and the Layer 3 header. In an MPLS network, the label edge router (LER) performs a label lookup of the incoming label, swaps the incoming label with an outgoing label, and sends the packet to the next hop at the label switch router (LSR). Labels are imposed (pushed) on packets only at the ingress edge of the MPLS network and are removed (popped) at the egress edge. The core network LSRs (provider, or P routers) read the labels, apply the appropriate services, and forward the packets based on the labels. Incoming labels are aggregate or nonaggregate. The aggregate label indicates that the arriving MPLS packet must be switched through an IP lookup to find the next hop and the outgoing interface. The nonaggregate label indicates that the packet contains the IP next hop information. Figure 24-1 shows an MPLS network of a service provider that connects two sites of a customer network.
Figure 24-1 MPLS Network
MPLS network MPLS network
IP network
IP network
Host A CE1 PE1 P1 P2 PE2 CE2
Host B
Owned by service provider
For additional information on MPLS, see this publication: http://www.cisco.com/en/US/docs/ios/12_2/switch/configuration/guide/xcftagov_ps1835_TSD_Produc ts_Configuration_Guide_Chapter.html
Understanding PFC3BXL and PFC3B Mode MPLS Label Switching

PFC3BXL or PFC3B mode supports Layer 3 Multiprotocol Label Switching (MPLS) virtual private networks (VPNs), and Layer 2 Ethernet over MPLS (EoMPLS), with quality of service (QoS) and security.
24-2
OL-3999-08
119118
Chapter 24
Configuring PFC3BXL and PFC3B Mode Multiprotocol Label Switching PFC3BXL and PFC3B Mode MPLS Label Switching
The MSFC on the supervisor engine performs Layer 3 control-plane functions, including address resolution and routing protocols. The MSFC processes information from the Routing and Label Distribution Protocols and builds the IP forwarding (FIB) table and the label forwarding (LFIB) table. The MSFC distributes the information in both tables to the PFC3BXL or PFC3B. The PFC3BXL or PFC3B receives the information and creates its own copies of the FIB and LFIB tables. Together, these tables comprise the FIB TCAM. The DFC looks up incoming IP packets and labeled packets against the FIB TCAM table. The lookup result is the pointer to a particular adjacency entry. It is the adjacency entry that contains appropriate information for label pushing (for IP to MPLS path), label swapping (for MPLS to MPLS path), label popping (for MPLS to IP path), and encapsulation. Figure 24-2 shows the various functional blocks that support PFC3BXL and PFC3B mode MPLS label switching. Routing protocol generates a routing information base (RIB) that is used for forwarding IP and MPLS data packets. For Cisco Express Forwarding (CEF), necessary routing information from the RIB is extracted and built into a forwarding information base (FIB). The label distribution protocol (LDP) obtains routes from the RIB and distributes the label across a label switch path to build a label forwarding information base (LFIB) in each of the LSRs and LERs.
Figure 24-2 MPLS Forwarding, Control and Data Planes
Route updates/ adjacency
Label updates/ adjacency Control
IP routing processes
Route table (RIB)
MPLS process
Label bindings (LIB)
Data
119193
IP forwarding table (FIB)
Label forwarding table (LFIB)
IP to MPLS
At the ingress to the MPLS network, the PFC3BXL or PFC3B examines the IP packets and performs a route lookup in the FIB TCAM. The lookup result is the pointer to a particular adjacency entry. The adjacency entry contains the appropriate information for label pushing (for IP to MPLS path) and encapsulation. The PFC3BXL or PFC3B generates a result containing the imposition label(s) needed to switch the MPLS packet.
Note
If MPLS load sharing is configured, the adjacency may point to a load-balanced path. See Basic MPLS Load Balancing section on page 24-8.
24-3
MPLS to MPLS
At the core of an MPLS network, the PFC3BXL or PFC3B uses the topmost label to perform a lookup in the FIB TCAM. The successful lookup points to an adjacency that swaps the top label in the packet with a new label as advertised by the downstream label switch router (LSR). If the router is the penultimate hop LSR router (the upstream LSR next to the egress LER), the adjacency instructs the PFCBXL to pop the topmost label, resulting in either an MPLS packet with the remaining label for any VPN or AToM use or a native IP packet.
MPLS to IP
At the egress of the MPLS network there are several possibilities. For a native IP packet (when the penultimate router has popped the label), the PFC3BXL or PFC3B performs a route lookup in the FIB TCAM. For a MPLS VPN packet, after the Interior Gateway Protocol (IGP) label is popped at penultimate router, the VPN label remains. The operation that the PFC3BXL or PFC3B performs depends on the VPN label type. Packets carrying aggregate labels require a second lookup based on the IP header after popping the aggregate label. For a nonaggregate label, the PFC3BXL or PFC3B performs a route lookup in the FIB TCAM to obtain the IP next hop information. For the case of a packet with an IGP label and a VPN label, when there is no penultimate hop popping (PHP), the packet carries the explicit-null label on top of the VPN label. The PFC3BXL or PFC3B looks up the top label in the FIB TCAM and recirculates the packet. Then the PFC3BXL or PFC3B handles the remaining label as described in the preceding paragraph, depending on whether it is an aggregate or nonaggregate label. Packets with the explicit-null label for the cases of EoMPLS, MPLS, and MPLS VPN an MPLS are handled the same way.
MPLS VPN Forwarding

There are two types of VPN labels: aggregate labels for directly connected network or aggregate routes, and nonaggregate labels. Packets carrying aggregate labels require a second lookup based on the IP header after popping the aggregate label. The VPN information (VPN-IPv4 address, extended community, and label) is distributed through the Multiprotocol-Border Gateway Protocol (MP-BGP).
Recirculation
In certain cases, the PFC3BXL or PFC3B provides the capability to recirculate the packets. Recirculation can be used to perform additional lookups in the ACL or QoS TCAMs, the NetFlow table, or the FIB TCAM table. Recirculation is necessary in these situations:

To push more than three labels on imposition To pop more than two labels on disposition To pop an explicit null top label When the VPN Routing and Forwarding (VRF) number is more than 511 For IP ACL on the egress interface (for nonaggregate (per-prefix) labels only)
Packet recirculation occurs only on a particular packet flow; other packet flows are not affected.The rewrite of the packet occurs on the modules; the packets are then forwarded back to the PFC3BXL or PFC3B for additional processing.
24-4
OL-3999-08
Chapter 24
Supported Hardware Features

The following hardware features are supported:

Label operation Any number of labels can be pushed or popped, although for best results, up to three labels can be pushed, and up to two labels can be popped in the same operation. IP to MPLS pathIP packets can be received and sent to the MPLS path. MPLS to IP pathLabeled packets can be received and sent to the IP path. MPLS to MPLS pathLabeled packets can be received and sent to the label path. MPLS Traffic Engineering (MPLS TE)Enables an MPLS backbone to replicate and expand the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks. Time to live (TTL) operationAt the ingress edge of the MPLS network, the TTL value in the MPLS frame header can be received from either the TTL field of the IP packet header or the user-configured value from the adjacency entry. At the egress of the MPLS network, the final TTL equals the minimum (label TTL and IP TTL)-1.
Note
With the Uniform mode, the TTL is taken from the IP TTL; with the Pipe mode, a value of 255, taken from the hardware register, is used for the outgoing label.
QoSInformation on Differentiated Services (DiffServ) and ToS from IP packets can be mapped to MPLS EXP field. MPLS/VPN SupportUp to 1024 VRFs can be supported (over 511 VRFs requires recirculation). Ethernet over MPLSThe Ethernet frame can be encapsulated at the ingress to the MPLS domain and the Ethernet frame can be decapsulated at the egress. Packet recirculationThe PFC3BXL or PFC3B provides the capability to recirculate the packets. See the Recirculation section on page 24-4. Configuration of MPLS switching is supported on VLAN interfaces with the mpls ip command.
Supported Cisco IOS Features

The following Cisco IOS software features are supported in PFC3BXL or PFC3B mode:
Note
Multi-VPN Routing and Forwarding (VRF) for CE Routers (VRF Lite) is supported with the following features: IPv4 forwarding between VRFs interfaces, IPv4 ACLs, and IPv4 HSRP. IPv4 multicast is not supported.
Multi-VRF for CE Routers (VRF Lite)VRF-lite is a feature that enables a service provider to support two or more VPNs (using only VRF-based IPv4), where IP addresses can be overlapped among the VPNs. See this publication: http://www.cisco.com/en/US/products/hw/routers/ps259/prod_bulletin09186a00800921d7.html. MPLS on Cisco routersThis feature provides basic MPLS support for imposing and removing labels on IP packets at label edge routers (LERs) and switching labels at label switch routers (LSRs). See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/mpls/config_library/12-2sx/mp-12-2sx-library.html.
24-5
MPLS TEMPLS traffic engineering software enables an MPLS backbone to replicate and expand upon the traffic engineering capabilities of Layer 2 ATM and Frame Relay networks. MPLS traffic engineering thereby makes traditional Layer 2 features available to Layer 3 traffic flows. For more information, see these publications: http://www.cisco.com/en/US/docs/ios/12_2/switch/configuration/guide/xcftagc_ps1835_TSD_Products _Configuration_Guide_Chapter.html http://www.cisco.com/en/US/tech/tk436/tk428/technologies_configuration_example09186a008009 3fcb.shtml http://www.cisco.com/en/US/tech/tk436/tk428/technologies_configuration_example09186a008009 3fd0.shtml
MPLS TE DiffServ Aware (DS-TE)This feature provides extensions made to MPLS TE to make it DiffServ aware, allowing constraint-based routing of guaranteed traffic. See this publication: http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsdserv3.html
MPLS TE Forwarding AdjacencyThis feature allows a network administrator to handle a traffic engineering, label-switched path (LSP) tunnel as a link in an Interior Gateway Protocol (IGP) network based on the Shortest Path First (SPF) algorithm. For information on forwarding adjacency with Intermediate System-to-Intermediate System (IS-IS) routing, see this publication: http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fstefa_3.html MPLS TE Interarea TunnelsThis feature allows the router to establish MPLS TE tunnels that span multiple Interior Gateway Protocol (IGP) areas and levels, removing the restriction that had required the tunnel head-end and tail-end routers to be in the same area. See this publication: http://www.cisco.com/en/US/docs/ios/12_2s/feature/guide/fsiarea3.html MPLS virtual private networks (VPNs)This feature allows you to deploy scalable IPv4 Layer 3 VPN backbone services over a Cisco IOS network. See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_l3_vpns/configuration/12-2sx/mp-l3-vpns-12-2 sx-book.html
MPLS VPN Carrier Supporting Carrier (CSC)This feature enables one MPLS VPN-based service provider to allow other service providers to use a segment of its backbone network. See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_ias_and_csc/configuration/12-2sx/mp-carrier-ldp-ig p.html
MPLS VPN Carrier Supporting Carrier IPv4 BGP Label DistributionThis feature allows you to configure your CSC network to enable Border Gateway Protocol (BGP) to transport routes and MPLS labels between the backbone carrier provider edge (PE) routers and the customer carrier customer edge (CE) routers. See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_l3_vpns/configuration/12-2sx/mp-l3-vpns-12-2 sx-book.html
MPLS VPN Interautonomous System (InterAS) Support This feature allows an MPLS VPN to span service providers and autonomous systems. See this publication: http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/fsias24.html
MPLS VPN Inter-AS IPv4 BGP label distributionThis feature enables you to set up a VPN service provider network so that the autonomous system boundary routers (ASBRs) exchange IPv4 routes with MPLS labels of the PE routers. See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_ias_and_csc/configuration/12-2sx/mp-carrier-bgp.ht ml
24-6
OL-3999-08
Chapter 24
MPLS VPN Hot Standby Router Protocol (HSRP) SupportThis feature ensures that the HSRP virtual IP address is added to the correct IP routing table and not to the global routing table. See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/ipapp_fhrp/configuration/12-2sx/fhp-hsrp.html
OSPF Sham-Link Support for MPLS VPNThis feature allows you to use a sham-link to connect VPN client sites that run the Open Shortest Path First (OSPF) protocol and share OSPF links in a MPLS VPN configuration. See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/iproute_ospf/configuration/15-sy/iro-sham-link.html Any Transport over MPLS (AToM)Transports Layer 2 packets over an MPLS backbone. See the Any Transport over MPLS section on page 24-13.
MPLS Guidelines and Restrictions

When configuring PFC3BXL or PFC3B MPLS, follow these guidelines and restrictions:

PFC3BXL or PFC3B mode supports up to 8 load-shared paths. Cisco IOS releases for other platforms support only 8 load-shared paths. PFC3BXL or PFC3B mode supports MTU checking and fragmentation.
Note
Fragmentation is supported with software (for IP to MPLS path). See the mtu command in the Cisco IOS Master Command List, Release 12.2SX.
Note
For information on other limitations and restrictions, see the MPLS VPN Guidelines and Restrictions section on page 24-11 and the EoMPLS Guidelines and Restrictions section on page 24-14.
PFC3BXL and PFC3B Mode MPLS Supported Commands

PFC3BXL and PFC3B mode MPLS supports these commands:

mpls ip default route mpls ip propagate-ttl mpls ip ttl-expiration pop mpls label protocol mpls label range mpls ip mpls label protocol mpls mtu
For information about these commands, see these publications: http://www.cisco.com/en/US/docs/ios/12_2/switch/command/reference/fswtch_r.html
24-7
Configuring MPLS
For information about configuring MPLS, see the Multiprotocol Label Switching on Cisco Routers publication at the following URL: http://www.cisco.com/en/US/docs/ios/12_2/switch/configuration/guide/xcftagc_ps1835_TSD_Product s_Configuration_Guide_Chapter.html
MPLS Per-Label Load Balancing

The following sections provide information on basic MPLS, MLPS Layer 2 VPN, and MPLS Layer 3 VPN load balancing.
Basic MPLS Load Balancing

The maximum number of load balancing paths is 8. The PFC3BXL or PFC3B forwards MPLS labeled packets without explicit configuration. If the packet has three labels or less and the underlying packet is IPv4, then the PFC3BXL or PFC3B uses the source and destination IPv4 address. If the underlying packet is not IPv4 or more than three labels are present, the PFC3BXL or PFC3B parses down as deep as the fifth or lowest label and uses it for hashing.
MPLS Layer 2 VPN Load Balancing

Load balancing is based on the VC label in the MPLS core if the first nibble of the MAC address in the customer Ethernet frame is not 4.
Note
Load balancing is not supported at the ingress PE for Layer 2 VPNs.
MPLS Layer 3 VPN Load Balancing

MPLS Layer 3 VPN load balancing is similar to basic MPLS load balancing. For more information, see the Basic MPLS Load Balancing section on page 24-8.
MPLS Configuration Examples

The following is an example of a basic MPLS configuration:
***** Basic MPLS *****
IP ingress interface: Router# mpls label protocol ldp interface GigabitEthernet6/2 ip address 75.0.77.1 255.255.255.0 media-type rj45 speed 1000 end
24-8
OL-3999-08
Chapter 24
Label egress interface: interface GigabitEthernet7/15 mtu 9216 ip address 75.0.67.2 255.255.255.0 logging event link-status mpls ip
Router# show ip route 188.0.0.0 Routing entry for 188.0.0.0/24, 1 known subnets O IA 188.0.0.0 [110/1] via 75.0.77.2, 00:00:10, GigabitEthernet6/2
Router#sh ip ro 88.0.0.0 Routing entry for 88.0.0.0/24, 1 known subnets O E2 Router# 88.0.0.0 [110/0] via 75.0.67.1, 00:00:24, GigabitEthernet7/15 [110/0] via 75.0.21.2, 00:00:24, GigabitEthernet7/16
Router# show mpls forwarding-table 88.0.0.0 Local Outgoing Prefix Bytes tag Outgoing Next Hop tag tag or VC or Tunnel Id switched interface 30 50 88.0.0.0/24 0 Gi7/15 75.0.67.1 50 88.0.0.0/24 0 Gi7/16 75.0.21.2
Router# show mls cef 88.0.0.0 detail Codes: M - mask entry, V - value entry, A - adjacency index, P - priority bit D - full don't switch, m - load balancing modnumber, B - BGP Bucket sel V0 - Vlan 0,C0 - don't comp bit 0,V1 - Vlan 1,C1 - don't comp bit 1 RVTEN - RPF Vlan table enable, RVTSEL - RPF Vlan table select Format: IPV4_DA - (8 | xtag vpn pi cr recirc tos prefix) Format: IPV4_SA - (9 | xtag vpn pi cr recirc prefix) M(3223 ): E | 1 FFF 0 0 0 0 255.255.255.0 V(3223 ): 8 | 1 0 0 0 0 0 88.0.0.0 (A:344105 ,P:1,D:0,m:1 ,B:0 ) M(3223 ): E | 1 FFF 0 0 0 255.255.255.0 V(3223 ): 9 | 1 0 0 0 0 88.0.0.0 (V0:0 ,C0:0 ,V1:0 ,C1:0 ,RVTEN:0 ,RVTSEL:0 Router# show mls cef adj ent 344105 Index: 344105 smac: 0005.9a39.a480, dmac: 000a.8ad8.2340 mtu: 9234, vlan: 1031, dindex: 0x0, l3rw_vld: 1 packets: 109478260, bytes: 7006608640
Router# show mls cef adj ent 344105 de Index: 344105 smac: 0005.9a39.a480, dmac: 000a.8ad8.2340 mtu: 9234, vlan: 1031, dindex: 0x0, l3rw_vld: 1 format: MPLS, flags: 0x1000008418 label0: 0, exp: 0, ovr: 0 label1: 0, exp: 0, ovr: 0 label2: 50, exp: 0, ovr: 0 op: PUSH_LABEL2 packets: 112344419, bytes: 7190042816
24-9
Chapter 24 PFC3BXL or PFC3B Mode VPN Switching
PFC3BXL or PFC3B Mode VPN Switching

These sections describe PFC3BXL or PFC3B mode VPN switching:

PFC3BXL or PFC3B Mode VPN Switching Operation, page 24-10 MPLS VPN Guidelines and Restrictions, page 24-11 PFC3BXL or PFC3B Mode MPLS VPN Supported Commands, page 24-11 MPLS VPN Sample Configuration, page 24-12
PFC3BXL or PFC3B Mode VPN Switching Operation

The IP VPN feature for MPLS allows a Cisco IOS network to deploy scalable IP Layer 3 VPN backbone services to multiple sites deployed on a shared infrastructure while also providing the same access or security policies as a private network. VPN based on MPLS technology provides the benefits of routing isolation and security, as well as simplified routing and better scalability. Refer to the Cisco IOS software documentation for a conceptual MPLS VPN overview and configuration details at this URL: http://www.cisco.com/en/US/docs/ios/12_2/switch/configuration/guide/xcftagov_ps1835_TSD_Produc ts_Configuration_Guide_Chapter.html A typical MPLS VPN network topology is shown in Figure 24-3.
Figure 24-3 VPNs with Service Provider Backbone
VPN 1 Site 1 PE Service provider backbone P P PE
VPN 2 Site 1
CE
CE Site 2
PE P P VPN 1 Site 2
119122
CE
CE
At the ingress PE, the PFC3BXL or PFC3B makes a forwarding decision based on the packet headers. The PFC3BXL or PFC3B contains a table that maps VLANs to VPNs. In the Catalyst 6500 series switch architecture, all physical ingress interfaces in the system are associated with a specific VPN. The
24-10
OL-3999-08
Chapter 24
Configuring PFC3BXL and PFC3B Mode Multiprotocol Label Switching PFC3BXL or PFC3B Mode VPN Switching
PFC3BXL or PFC3B looks up the IP destination address in the CEF table but only against prefixes that are in the specific VPN. (The table entry points to a specific set of adjacencies and one is chosen as part of the load-balancing decision if multiple parallel paths exist.) The table entry contains the information on the Layer 2 header that the packet needs, as well as the specific MPLS labels to be pushed onto the frame. The information to rewrite the packet goes back to the ingress line card where it is rewritten and forwarded to the egress line interface. VPN traffic is handled at the egress from the PE based upon the per-prefix labels or aggregate labels. If per-prefix labels are used, then each VPN prefix has a unique label association; this allows the PE to forward the packet to the final destination based upon a label lookup in the FIB.
Note
The PFC3BXL or PFC3B allocates only one aggregate label per VRF. If aggregate labels are used for disposition in an egress PE, many prefixes on the multiple interfaces may be associated with the label. In this case, the PFC3BXL or PFC3B must perform an IP lookup to determine the final destination. The IP lookup may require recirculation.
MPLS VPN Guidelines and Restrictions

When configuring MPLS VPN, follow these guidelines and restrictions:

PFC3BXL or PFC3B mode supports a total of 1024 VRFs per chassis a with enhanced OSMs; using a nonenhanced OSM causes the system to default to 511 VRFs. In PFC3BXL or PFC3B mode, VPNs are recirculated when the number of VPNs is over 511.
PFC3BXL or PFC3B Mode MPLS VPN Supported Commands

PFC3BXL or PFC3B mode MPLS VPN supports these commands:

address-family exit-address-family import map ip route vrf ip route forwarding ip vrf neighbor activate rd route-target
For information about these commands, see these publications: http://www.cisco.com/en/US/docs/ios/12_2/switch/command/reference/fswtch_r.html
24-11
Chapter 24 PFC3BXL or PFC3B Mode VPN Switching
Configuring MPLS VPN

For information on configuring MPLS VPN, refer to the MPLS Virtual Private Networks feature module at this URL: http://www.cisco.com/en/US/docs/ios/12_2/switch/configuration/guide/xcftagc_ps1835_TSD_Product s_Configuration_Guide_Chapter.html.
Note
If you use a Layer 3 VLAN interface as the MPLS uplink through a Layer 2 port peering with another MPLS device, then you can use another Layer 3 VLAN interface as the VRF interface.
MPLS VPN Sample Configuration

This sample configuration shows LAN, OSM, and FlexWAN CE-facing interfaces. PFC3BXL or PFC3B mode MPLS switching configuration is identical to configuration on other platforms.
!ip vrf blues rd 100:10 route-target export 100:1 route-target import 100:1 ! mpls label protocol ldp mpls ldp logging neighbor-changes mls mpls tunnel-recir ! interface Loopback0 ip address 10.4.4.4 255.255.255.255 ! interface GigabitEthernet4/2 description Catalyst link to P2 no ip address mls qos trust dscp ! interface GigabitEthernet4/2.42 encapsulation dot1Q 42 ip address 10.0.3.2 255.255.255.0 tag-switching ip ! interface GigabitEthernet7/3 description Catalyst link to CE2 no ip address mls qos trust dscp ! interface GigabitEthernet7/3.73 encapsulation dot1Q 73 ip vrf forwarding blues ip address 10.19.7.1 255.255.255.0 ! interface POS8/1 description OSM link to CE3 ip vrf forwarding blues ip address 10.19.8.1 255.255.255.252 encapsulation ppp mls qos trust dscp pos scramble-atm pos flag c2 22 ! interface POS9/0/0
24-12
OL-3999-08
Chapter 24
Configuring PFC3BXL and PFC3B Mode Multiprotocol Label Switching Any Transport over MPLS
description FlexWAN link to CE1 ip vrf forwarding blues ip address 10.19.9.1 255.255.255.252 encapsulation ppp pos scramble-atm pos flag c2 22 ! router ospf 100 log-adjacency-changes network 10.4.4.4 0.0.0.0 area 0 network 10.0.0.0 0.0.255.255 area 0 ! router ospf 65000 vrf blues log-adjacency-changes redistribute bgp 100 subnets network 10.19.0.0 0.0.255.255 area 0 ! router bgp 100 no synchronization bgp log-neighbor-changes neighbor 10.3.3.3 remote-as 100 neighbor 10.3.3.3 description MP-BGP to PE1 neighbor 10.3.3.3 update-source Loopback0 no auto-summary ! address-family vpnv4 neighbor 10.3.3.3 activate neighbor 10.3.3.3 send-community extended exit-address-family ! address-family ipv4 vrf blues redistribute connected redistribute ospf 65000 match internal external 1 external 2 no auto-summary no synchronization exit-address-family !
Any Transport over MPLS

Any Transport over MPLS (AToM) transports Layer 2 packets over an MPLS backbone. AToM uses a directed Label Distribution Protocol (LDP) session between edge routers for setting up and maintaining connections. Forwarding occurs through the use of two level labels that provide switching between the edge routers. The external label (tunnel label) routes the packet over the MPLS backbone to the egress PE at the ingress PE. The VC label is a demuxing label that determines the connection at the tunnel endpoint (the particular egress interface on the egress PE as well as the VLAN identifier for an Ethernet frame). AToM supports the following like-to-like transport types in PFC3BXL or PFC3B mode:

Ethernet over MPLS (EoMPLS) (VLAN mode and port mode) Frame Relay over MPLS with DLCI-to-DLCI connections ATM AAL5 over MPLS ATM Cell Relay over MPLS
Note
Additional AToM types are planned in future releases.
24-13
Chapter 24 Any Transport over MPLS
PFC3BXL or PFC3B mode supports both hardware-based EoMPLS as well as OSM-, FlexWAN, or FlexWAN2-based EoMPLS. For more information, see this publication: http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/mpls.html#Ethern et_over_MPLS For information on requirements for Supervisor Engine 2-based EoMPLS, see this publication: http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/mpls.html#Super visor_Engine_2-Based_EoMPLS For information on other AToM implementations (ATM AAL5 over MPLS, ATM Cell Relay over MPLS, Frame Relay over MPLS), see this publication: http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/mpls.html#Any_ Transport_over_MPLS These sections describe AToM:

AToM Load Balancing, page 24-14 Understanding EoMPLS, page 24-14 EoMPLS Guidelines and Restrictions, page 24-14 Configuring EoMPLS, page 24-16
AToM Load Balancing

PFC3BXL or PFC3B mode EoMPLS does not support load balancing at the tunnel ingress; only one Interior Gateway Protocol (IGP) path is selected even if multiple IGP paths are available, but load balancing is available at the MPLS core.
Understanding EoMPLS
EoMPLS is one of the AToM transport types. AToM transports Layer 2 packets over a MPLS backbone using a directed LDP session between edge routers for setting up and maintaining connections. Forwarding occurs through the use of two level labels that provide switching between the edge routers. The external label (tunnel label) routes the packet over the MPLS backbone to the egress PE at the ingress PE. The VC label is a demuxing label that determines the connection at the tunnel endpoint (the particular egress interface on the egress PE as well as the VLAN identifier for an Ethernet frame). EoMPLS works by encapsulating Ethernet PDUs in MPLS packets and forwarding them across the MPLS network. Each PDU is transported as a single packet.
Note
Use OSM-based EoMPLS when you want local Layer 2 switching and EoMPLS on the same VLAN. You need to configure EoMPLS on the SVI; the core-facing card must be an OSM. When local Layer 2 switching is not required, use PFC-based EoMPLS configured on the subinterface or physical interface.
EoMPLS Guidelines and Restrictions

When configuring EoMPLS, follow these guidelines and restrictions:
Ensure that the maximum transmission unit (MTU) of all intermediate links between endpoints is sufficient to carry the largest Layer 2 packet received.
24-14
OL-3999-08
Chapter 24
EoMPLS supports VLAN packets that conform to the IEEE 802.1Q standard. The 802.1Q specification establishes a standard method for inserting VLAN membership information into Ethernet frames. If QoS is disabled globally, both the 802.1p and IP precedence bits are preserved. When the QoS is enabled on a Layer 2 port, either 802.1q P bits or IP precedence bits can be preserved with the trusted configuration. However, by default the unpreserved bits are overwritten by the value of preserved bits. For instance, if you preserve the P bits, the IP precedence bits are overwritten with the value of the P bits. PFC3BXL or PFC3B mode provides a new command that allows you to trust the P bits while preserving the IP precedence bits. To preserve the IP precedence bits, use the no mls qos rewrite ip dscp command.
Note
The no mls qos rewrite ip dscp command is not compatible with the MPLS and MPLS VPN features. See Chapter 41, Configuring PFC QoS.
Note
Do not use the no mls qos rewrite ip dscp command if you have PFC-based EoMPLS and PXF-based EoMPLS services in the same system. EoMPLS is not supported with private VLANs. The following restrictions apply to using trunks with EoMPLS:
To support Ethernet spanning tree bridge protocol data units (BPDUs) across an EoMPLS cloud,
you must disable the supervisor engine spanning tree for the Ethernet-over-MPLS VLAN. This ensures that the EoMPLS VLANs are carried only on the trunk to the customer switch. Otherwise, the BPDUs are directed to the supervisor engine and not to the EoMPLS cloud.
The native VLAN of a trunk must not be configured as an EoMPLS VLAN.
In PFC3BXL or PFC3B mode, all protocols (for example, CDP, VTP, BPDUs) are tunneled across the MPLS cloud without conditions. ISL encapsulation is not supported for the interface that receives EoMPLS packets. Unique VLANs are required across interfaces. You cannot use the same VLAN ID on different interfaces. EoMPLS tunnel destination route in the routing table and the CEF table must be a /32 address (host address where the mask is 255.255.255.255) to ensure that there is a label-switched path (LSP) from PE to PE. For a particular EoMPLS connection, both the ingress EoMPLS interface on the ingress PE and the egress EoMPLS interface on the egress PE have to be subinterfaces with dot1Q encapsulation or neither is a subinterface. 802.1Q in 802.1Q over EoMPLS is supported if the outgoing interface connecting to MPLS network is a port on an Layer 2 card. Shaping EoMPLS traffic is not supported if the egress interface connecting to an MPLS network is a Layer 2 LAN port (a mode known as PFC-based EoMPLS). EoMPLS based on a PFC3BXL or PFC3B does not perform any Layer 2 lookup to determine if the destination MAC address resides on the local or remote segment and does not perform any Layer 2 address learning (as traditional LAN bridging does). This functionality (local switching) is available only when using OSM and FlexWAN modules as uplinks.
24-15
In previous releases of AToM, the command used to configure AToM circuits was mpls l2 transport route. This command has been replaced with the xconnect command. You can use the xconnect command to configure EoMPLS circuits. The AToM control word is not supported. EoMPLS is not supported on Layer 3 VLAN interfaces. Point-to-point EoMPLS works with a physical interface and subinterfaces.
Configuring EoMPLS
These sections describe how to configure EoMPLS:

Prerequisites, page 24-16 Configuring PFC3BXL or PFC3B Mode VLAN-Based EoMPLS, page 24-17 Configuring PFC3BXL or PFC3B Mode Port-Based EoMPLS, page 24-20
Prerequisites
Before you configure EoMPLS, ensure that the network is configured as follows:

Configure IP routing in the core so that the PE routers can reach each other through IP. Configure MPLS in the core so that a label switched path (LSP) exists between the PE routers.
EoMPLS works by encapsulating Ethernet PDUs in MPLS packets and forwarding them across the MPLS network. Each PDU is transported as a single packet. Two methods are available to configure EoMPLS in PFC3BXL or PFC3B mode:
VLAN modeTransports Ethernet traffic from a source 802.1Q VLAN to a destination 802.1Q VLAN through a single VC over an MPLS network. VLAN mode uses VC type 5 as default (no dot1q tag) and VC type 4 (transport dot1 tag) if the remote PE does not support VC type 5 for subinterface (VLAN) based EoMPLS. Port modeAllows all traffic on a port to share a single VC across an MPLS network. Port mode uses VC type 5.
Note
For both VLAN mode and port mode, PFC3BXL and PFC3B mode EoMPLS does not allow local switching of packets between interfaces unless you use loopback ports. A system can have both an OSM or FlexWAN configuration and PFC3BXL or PFC3B mode configuration enabled at the same time. Cisco supports this configuration but does not recommend it. Unless the uplinks to the MPLS core are through OSM or FlexWAN-enabled interfaces, OSM or FlexWAN-based EoMPLS connections will not be active; this causes packets for OSM or FlexWAN-based EoMPLS arriving on non-WAN interfaces to be dropped. For information on WAN (FlexWAN and OSM) EoMPLS, see this publication: http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/mpls.html#Et hernet_over_MPLS
PFC3BXL or PFC3B mode supports MPLS. In PFC3BXL or PFC3B mode, LAN ports can receive Layer 2 traffic, impose labels, and switch the frames into the MPLS core without using an OSM or FlexWAN module.
24-16
OL-3999-08
Chapter 24
In PFC3BXL or PFC3B mode, you can configure an OSM or a FlexWAN module to face the core of MPLS network and use either the OSM configuration, the FlexWAN configuration, or the PFC3BXL or PFC3B mode configuration. For more information, see this publication: http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/mpls.html#Ethern et_over_MPLS
Configuring PFC3BXL or PFC3B Mode VLAN-Based EoMPLS

When configuring PFC3BXL or PFC3B mode VLAN-based EoMPLS, follow these guidelines and restrictions:

The AToM control word is not supported. Ethernet packets with hardware-level cyclic redundancy check (CRC) errors, framing errors, and runt packets are discarded on input. You must configure VLAN-based EoMPLS on subinterfaces.
To configure PFC3BXL or PFC3B mode VLAN-based EoMPLS, perform this task on the provider edge (PE) routers. Command
Step 1 Step 2
Router# configure terminal Router(config)# interface gigabitethernetslot/interface.subinterface
Purpose Enters global configuration mode. Specifies the Gigabit Ethernet subinterface. Make sure that the subinterface on the adjoining CE router is on the same VLAN as this PE router. Enables the subinterface to accept 802.1Q VLAN packets. The subinterfaces between the CE and PE routers that are running Ethernet over MPLS must be in the same subnet. All other subinterfaces and backbone routers do not need to be on the same subnet.
Step 3
Router(config-if)# encapsulation dot1q vlan_id
Step 4
Router(config-if)# xconnect peer_router_id vcid encapsulation mpls
Binds the attachment circuit to a pseudowire VC. The syntax for this command is the same as for all other Layer 2 transports.
This is a PFC3BXL or PFC3B mode VLAN-based EoMPLS configuration sample:

! interface GigabitEthernet7/4.2 encapsulation dot1Q 3 xconnect 13.13.13.13 3 encapsulation mpls no shut
Note
The IP address is configured on subinterfaces of the CE devices.
24-17
Verifying the Configuration

To verify and display the configuration of Layer 2 VLAN transport over MPLS tunnels, perform the following:
To display a single line for each VLAN, naming the VLAN, status, and ports, enter the show vlan brief command.
Router# show vlan brief VLAN ---1 2 3 1002 1003 1004 1005 Name -------------------------------default VLAN0002 VLAN0003 fddi-default token-ring-default fddinet-default trnet-default Status Ports --------- ------------------------active active active act/unsup act/unsup act/unsup act/unsup
To make sure that the PE router endpoints have discovered each other, enter the show mpls ldp discovery command. When an PE router receives an LDP Hello message from another PE router, it considers that router and the specified label space to be discovered.
Router# show mpls ldp discovery Local LDP Identifier: 13.13.13.13:0 Discovery Sources: Interfaces: GE-WAN3/3 (ldp): xmit/recv LDP Id: 12.12.12.12:0 Targeted Hellos: 13.13.13.13 -> 11.11.11.11 (ldp): active/passive, xmit/recv LDP Id: 11.11.11.11:0
To make sure that the label distribution session has been established, enter the show mpls ldp neighbor command. The third line of the output shows that the state of the LDP session is operational and shows that messages are being sent and received.
Router# show mpls ldp neighbor Peer LDP Ident: 12.12.12.12:0; Local LDP Ident 13.13.13.13:0 TCP connection: 12.12.12.12.646 - 13.13.13.13.11010 State: Oper; Msgs sent/rcvd: 1649/1640; Downstream Up time: 23:42:45 LDP discovery sources: GE-WAN3/3, Src IP addr: 34.0.0.2 Addresses bound to peer LDP Ident: 23.2.1.14 37.0.0.2 12.12.12.12 34.0.0.2 99.0.0.1 Peer LDP Ident: 11.11.11.11:0; Local LDP Ident 13.13.13.13:0 TCP connection: 11.11.11.11.646 - 13.13.13.13.11013 State: Oper; Msgs sent/rcvd: 1650/1653; Downstream Up time: 23:42:29 LDP discovery sources: Targeted Hello 13.13.13.13 -> 11.11.11.11, active, passive Addresses bound to peer LDP Ident: 11.11.11.11 37.0.0.1 23.2.1.13
To ensure that the label forwarding table is built correctly, enter the show mpls forwarding-table command to verify that a label has been learned for the remote PE and that the label is going from the correct interface to the correct next-hop.
24-18
OL-3999-08
Chapter 24
Router# show mpls forwarding-table Local Outgoing Prefix tag tag or VC or Tunnel Id 16 Untagged 223.255.254.254/32 20 Untagged 21 Untagged 24 Pop tag 25 17 26 Pop tag Router# l2ckt(2) l2ckt(3) 37.0.0.0/8 11.11.11.11/32 12.12.12.12/32
Bytes tag switched \ 0 133093 185497 0 0 0
Outgoing interface Gi2/1 Vl2 Vl3 GE3/3 GE3/3 GE3/3
Next Hop
23.2.0.1 point2point point2point 34.0.0.2 34.0.0.2 34.0.0.2
The output shows the following data:

Local tagLabel assigned by this router. Outgoing tag or VCLabel assigned by next hop. Prefix or Tunnel IdAddress or tunnel to which packets with this label are going. Bytes tag switched Number of bytes switched out with this incoming label. Outgoing interfaceInterface through which packets with this label are sent. Next HopIP address of neighbor that assigned the outgoing label.
To view the state of the currently routed VCs, enter the show mpls l2transport vc command.
Router# show mpls l2transport vc Local intf ------------Vl2 Vl3 Local circuit -------------------Eth VLAN 2 Eth VLAN 3 Dest address --------------11.11.11.11 11.11.11.11 VC ID ---------2 3 Status ---------UP UP
To see detailed information about each VC, add the keyword detail.
Router# show mpls l2transport vc detail Local interface: Vl2 up, line protocol up, Eth VLAN 2 up Destination address: 11.11.11.11, VC ID: 2, VC status: up Tunnel label: 17, next hop 34.0.0.2 Output interface: GE3/3, imposed label stack {17 18} Create time: 01:24:44, last status change time: 00:10:55 Signaling protocol: LDP, peer 11.11.11.11:0 up MPLS VC labels: local 20, remote 18 Group ID: local 71, remote 89 MTU: local 1500, remote 1500 Remote interface description: Sequencing: receive disabled, send disabled VC statistics: packet totals: receive 1009, send 1019 byte totals: receive 133093, send 138089 packet drops: receive 0, send 0 Local interface: Vl3 up, line protocol up, Eth VLAN 3 up Destination address: 11.11.11.11, VC ID: 3, VC status: up Tunnel label: 17, next hop 34.0.0.2 Output interface: GE3/3, imposed label stack {17 19} Create time: 01:24:38, last status change time: 00:10:55 Signaling protocol: LDP, peer 11.11.11.11:0 up MPLS VC labels: local 21, remote 19 Group ID: local 72, remote 90 MTU: local 1500, remote 1500 Remote interface description: Sequencing: receive disabled, send disabled
24-19
VC statistics: packet totals: receive 1406, send 1414 byte totals: receive 185497, send 191917 packet drops: receive 0, send 0
Configuring PFC3BXL or PFC3B Mode Port-Based EoMPLS

When configuring PFC3BXL or PFC3B mode port-based EoMPLS, follow these guidelines and restrictions:

The AToM control word is not supported. Ethernet packets with hardware-level cyclic redundancy check (CRC) errors, framing errors, and runt packets are discarded on input. Port-based EoMPLS and VLAN-based EoMPLS are mutually exclusive. If you enable a main interface for port-to-port transport, you also cannot enter commands on a subinterface.
To support 802.1Q-in-802.1Q traffic and Ethernet traffic over EoMPLS in PFC3BXL or PFC3B mode, configure port-based EoMPLS by performing this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# interface gigabitethernetslot/interface
Purpose Enters global configuration mode. Specifies the Gigabit Ethernet interface. Make sure that the interface on the adjoining CE router is on the same VLAN as this PE router. Binds the attachment circuit to a pseudowire VC. The syntax for this command is the same as for all other Layer 2 transports.
Step 3
Router(config-if)# xconnect peer_router_id vcid encapsulation mpls
The following is an example of a port-based configuration:

! EoMPLS: router# show mpls l2transport vc Local intf ------------Fa8/48 Gi7/11.2000 Local circuit -------------------Ethernet Eth VLAN 2000 Dest address --------------75.0.78.1 75.0.78.1 VC ID ---------1 2000 Status ---------UP UP
Port-Based EoMPLS Config: router# show run interface f8/48 Building configuration... Current configuration : 86 bytes ! interface FastEthernet8/48 no ip address xconnect 75.0.78.1 1 encapsulation mpls end Sub-Interface Based Mode: router# show run interface g7/11 Building configuration...
24-20
OL-3999-08
Chapter 24
Current configuration : 118 bytes ! interface GigabitEthernet7/11 description Traffic-Generator no ip address logging event link-status speed nonegotiate end router# show run int g7/11.2000 Building configuration... Current configuration : 112 bytes ! interface GigabitEthernet7/11.2000 encapsulation dot1Q 2000 xconnect 75.0.78.1 2000 encapsulation mpls end kb7606# show mpls l2transport vc 1 detail Local interface: Gi7/47 up, line protocol up, Ethernet up Destination address: 75.0.80.1, VC ID: 1, VC status: up Tunnel label: 5704, next hop 75.0.83.1 Output interface: Te8/3, imposed label stack {5704 10038} Create time: 00:30:33, last status change time: 00:00:43 Signaling protocol: LDP, peer 75.0.80.1:0 up MPLS VC labels: local 10579, remote 10038 Group ID: local 155, remote 116 MTU: local 1500, remote 1500 Remote interface description: Sequencing: receive disabled, send disabled VC statistics: packet totals: receive 26, send 0 byte totals: receive 13546, send 0 packet drops: receive 0, send 0
To obtain the VC type:

kb7606# remote command switch show mpls l2transport vc 1 de Local interface: GigabitEthernet7/47, Ethernet Destination address: 75.0.80.1, VC ID: 1 VC status: receive UP, send DOWN VC type: receive 5, send 5 Tunnel label: not ready, destination not in LFIB Output interface: unknown, imposed label stack {} MPLS VC label: local 10579, remote 10038 Linecard VC statistics: packet totals: receive: 0 send: 0 byte totals: receive: 0 send: 0 packet drops: receive: 0 send: 0 Control flags: receive 1, send: 31 !

To verify and display the configuration of Layer 2 VLAN transport over MPLS tunnels, perform the following:
To display a single line for each VLAN, naming the VLAN, status, and ports, enter the show vlan brief command.
Router# show vlan brief
24-21
VLAN ---1 2 1002 1003 1004 1005
Name -------------------------------default VLAN0002 fddi-default token-ring-default fddinet-default trnet-default
Status Ports --------- ------------------------------active active Gi1/4 act/unsup act/unsup act/unsup act/unsup
To make sure the PE router endpoints have discovered each other, enter the show mpls ldp discovery command. When an PE router receives an LDP Hello message from another PE router, it considers that router and the specified label space to be discovered.
Router# show mpls ldp discovery Local LDP Identifier: 13.13.13.13:0 Discovery Sources: Interfaces: GE-WAN3/3 (ldp): xmit/recv LDP Id: 12.12.12.12:0 Targeted Hellos: 13.13.13.13 -> 11.11.11.11 (ldp): active/passive, xmit/recv LDP Id: 11.11.11.11:0
To make sure the label distribution session has been established, enter the show mpls ldp neighbor command. The third line of the output shows that the state of the LDP session is operational and shows that messages are being sent and received.
Router# show mpls ldp neighbor Peer LDP Ident: 12.12.12.12:0; Local LDP Ident 13.13.13.13:0 TCP connection: 12.12.12.12.646 - 13.13.13.13.11010 State: Oper; Msgs sent/rcvd: 1715/1706; Downstream Up time: 1d00h LDP discovery sources: GE-WAN3/3, Src IP addr: 34.0.0.2 Addresses bound to peer LDP Ident: 23.2.1.14 37.0.0.2 12.12.12.12 34.0.0.2 99.0.0.1 Peer LDP Ident: 11.11.11.11:0; Local LDP Ident 13.13.13.13:0 TCP connection: 11.11.11.11.646 - 13.13.13.13.11013 State: Oper; Msgs sent/rcvd: 1724/1730; Downstream Up time: 1d00h LDP discovery sources: Targeted Hello 13.13.13.13 -> 11.11.11.11, active, passive Addresses bound to peer LDP Ident: 11.11.11.11 37.0.0.1 23.2.1.13
To make sure the label forwarding table is built correctly, enter the show mpls forwarding-table command.
Router# show mpls forwarding-table Local Outgoing Prefix tag tag or VC or Tunnel Id 16 Untagged 223.255.254.254/32 20 24 25 26 Untagged Pop tag 17 Pop tag l2ckt(2) 37.0.0.0/8 11.11.11.11/32 12.12.12.12/32 Bytes tag switched \ 0 55146580 0 0 0 Outgoing interface Gi2/1 Vl2 GE3/3 GE3/3 GE3/3 Next Hop
23.2.0.1 point2point 34.0.0.2 34.0.0.2 34.0.0.2
The output shows the following data:

Local tagLabel assigned by this router.
24-22
OL-3999-08
Chapter 24
Outgoing tag or VCLabel assigned by next hop. Prefix or Tunnel IdAddress or tunnel to which packets with this label are going. Bytes tag switched Number of bytes switched out with this incoming label. Outgoing interfaceInterface through which packets with this label are sent. Next HopIP address of neighbor that assigned the outgoing label.
To view the state of the currently routed VCs, enter the show mpls l2transport vc command:
Router# show mpls l2transport vc Local intf ------------Vl2 Local circuit Dest address VC ID Status -------------------- --------------- ---------- ---------Eth VLAN 2 11.11.11.11 2 UP
Tip
24-23
24-24
OL-3999-08
C H A P T E R
25
Configuring IPv4 Multicast VPN Support

This chapter describes how to configure IPv4 Multicast Virtual Private Network (MVPN) support on Catalyst 6500 series switches. Release 12.2(18)SXE and later releases support MVPN when the switch is operating in PFC3B mode or PFC3BXL mode.
Note
This chapter contains these sections:

Understanding How MVPN Works, page 25-1 MVPN Configuration Guidelines and Restrictions, page 25-7 Configuring MVPN, page 25-8
Tip
Understanding How MVPN Works

These sections describe MVPN:

MVPN Overview, page 25-2 Multicast Routing and Forwarding and Multicast Domains, page 25-2 Multicast Distribution Trees, page 25-2 Multicast Tunnel Interfaces, page 25-5 PE Router Routing Table Support for MVPN, page 25-6 Multicast Distributed Switching Support, page 25-6 Hardware-Assisted IPv4 Multicast, page 25-6
25-1
Chapter 25 Understanding How MVPN Works
MVPN Overview
MVPN is a standards-based feature that transmits IPv4 multicast traffic across an MPLS VPN cloud. MVPN on Catalyst 6500 series switches uses the existing PFC hardware support for IPv4 multicast traffic to forward multicast traffic over VPNs at wire speeds. MVPN adds support for IPv4 multicast traffic over Layer 3 IPv4 VPNs to the existing IPv4 unicast support. MVPN routes and forwards multicast packets for each individual VPN routing and forwarding (VRF) instance, as well as transmitting the multicast packets through VPN tunnels across the service provider backbone. MVPN is an alternative to IP-in-IP generic route encapsulation (GRE) tunnels. GRE tunnels are not a readily scalable solution and they are limited in the granularity they provide to customers.
Multicast Routing and Forwarding and Multicast Domains

MVPN adds multicast routing information to the VPN routing and forwarding table. When a provider-edge (PE) router receives multicast data or control packets from a customer-edge (CE) router, forwarding is performed according to the information in the multicast VRF (MVRF).
Note
MVRF is also commonly referred to as multicast over VRF-lite. Each MVRF maintains the routing and forwarding information that is needed for its particular VRF instance. An MVRF is created and configured in the same way as existing VRFs, except multicast routing is also enabled on each MVRF. A multicast domain constitutes the set of hosts that can send multicast traffic to each other within the MPLS network. For example, the multicast domain for a customer that wanted to send certain types of multicast traffic to all global employees would consist of all CE routers associated with that enterprise.
Multicast Distribution Trees

The MVPN feature establishes at least one multicast distribution tree (MDT) for each multicast domain. The MDT provides the information needed to interconnect the same MVRFs that exist on the different PE routers. MVPN supports two MDT types:
Default MDTThe default MDT is a permanent channel for PIM control messages and low-bandwidth streams between all PE routers in a particular multicast domain. All multicast traffic in the default MDT is replicated to every other PE router in the domain. Each PE router is logically seen as a PIM neighbor (one hop away) from every other PE router in the domain. Data MDTData MDTs are optional. If enabled, they are dynamically created to provide optimal paths for high-bandwidth transmissions, such as full-motion video, that do not need to be sent to every PE router. This allows for on-demand forwarding of high-bandwidth traffic between PE routers, so as to avoid flooding every PE router with every high-bandwidth stream that might be created.
25-2
OL-3999-08
Chapter 25
Configuring IPv4 Multicast VPN Support Understanding How MVPN Works
To create data MDTs, each PE router that is forwarding multicast streams to the backbone periodically examines the traffic being sent in each default MDT as follows:
1.
Each PE router periodically samples the multicast traffic (approximately every 10 seconds for software switching, and 90 seconds for hardware switching) to determine whether a multicast stream has exceeded the configured threshold. (Depending on when the stream is sampled, this means that in a worst-case scenario, it could take up to 180 seconds before a high-bandwidth stream is detected.)
Note
Data MDTs are created only for (S, G) multicast route entries within the VRF multicast routing table. They are not created for (*, G) entries.
2. 3. 4.
If a particular multicast stream exceeds the defined threshold, the sending PE router dynamically creates a data MDT for that particular multicast traffic. The sending PE router then transmits a DATA-MDT JOIN request (which is a User Datagram Protocol (UDP) message to port 3232) to the other PE routers, informing them of the new data MDT. Receiving PE routers examine their VRF routing tables to determine if they have any customers interested in receiving this data stream. If so, they use the PIM protocol to transmit a PIM JOIN message for this particular data MDT group (in the global table PIM instance) to accept the stream. Routers that do not currently have any customers for this stream still cache the information, in case any customers request it later on. Three seconds after sending the DATA-MDT JOIN message, the sending PE router removes the high-bandwidth multicast stream from the default MDT and begins transmitting it over the new data MDT. The sending PE router continues to send a DATA-MDT JOIN message every 60 seconds, as long as the multicast stream continues to exceed the defined threshold. If the stream falls below the threshold for more than 60 seconds, the sending PE router stops sending the DATA-MDT JOIN messages, and moves the stream back to the default MDT. Receiving routers age out the cache information for the default MDT when they do not receive a DATA-MDT JOIN message for more than three minutes.
5.
6.
7.
Data MDTs allow for high-bandwidth sources inside the VPN while still ensuring optimal traffic forwarding in the MPLS VPN core.
Note
For technical information about the DATA-MDT JOIN message and other aspects of the data MDT creation and usage, see the Internet-Draft, Multicast in MPLS/BGP IP VPNs, by Eric C. Rosen et al. In the following example, a service provider has a multicast customer with offices in San Jose, New York, and Dallas. The San Jose site is transmitting a one-way multicast presentation. The service provider network supports all three sites associated with this customer, in addition to the Houston site of a different enterprise customer. The default MDT for the enterprise customer consists of provider routers P1, P2, and P3 and their associated PE routers. Although PE4 is interconnected to these other routers in the MPLS core, PE4 is associated with a different customer and is therefore not part of the default MDT. Figure 25-1 shows the situation in this network when no one outside of San Jose has joined the multicast broadcast, which means that no data is flowing along the default MDT. Each PE router maintains a PIM relationship with the other PE routers over the default MDT, as well as a PIM relationship with its directly attached PE routers.
25-3
Figure 25-1 Default Multicast Distribution Tree Overview
Multicast sender
Local multicast recipient
CE1a
CE1b
CE2
Customer 1 San Jose Site
PE1
PE2
Customer 1 New York Site
P1 MPLS Core P4 PE4
P2 PIM (SM/bidir/SSM) in Core P3 PE3
CE4
If an employee in New York joins the multicast session, the PE router associated for the New York site sends a join request that flows across the default MDT for the multicast domain. The PE router associated with the multicast session source (PE1) receives the request. Figure 25-2 shows how the PE router forwards the request to the CE router associated with the multicast source (CE1a).
25-4
72756
Customer 2 Houston Site
Customer 1 Dallas Site
CE3
OL-3999-08
Chapter 25
Configuring IPv4 Multicast VPN Support Understanding How MVPN Works
Figure 25-2 Initializing the Data MDT
Multicast sender
Local multicast recipient
1. Remote enterprise client issues join request 2. PE2 sends join request along default MDT PE2
CE1a
CE1b
CE2
Customer 1 San Jose Site
PE1
3. PE1 receives join request and asks CE1a to begin sending data
Customer 1 New York Site
P1 MPLS Core P4 PE4
P2
P3 PE3
CE4
The CE router (CE1a) starts sending the multicast data to the associated PE router (PE1), which recognizes that the multicast data exceeds the bandwidth threshold at which a data MDT should be created. PE1 then creates a data MDT and sends a message to all routers using the default MDT that contains information about the data MDT. Approximately three seconds later, PE1 begins sending the multicast data for that particular stream using the data MDT. Because only PE2 has receivers who are interested in this source, only PE2 joins the data MDT and receives traffic on it.
Multicast Tunnel Interfaces

The PE router creates a multicast tunnel interface (MTI) for each multicast VRF (MVRF) in the multicast domain. The MVRF uses the tunnel interface to access the multicast domain to provide a conduit that connects an MVRF and the global MVRF. On the router, the MTI is a tunnel interface (created with the interface tunnel command) with a class D multicast address. All PE routers that are configured with a default MDT for this MVRF create a logical network in which each PE router appears as a PIM neighbor (one hop away) to every other PE router in the multicast domain, regardless of the actual physical distance between them. The MTI is automatically created when an MVRF is configured. The BGP peering address is assigned as the MTI interface source address, and the PIM protocol is automatically enabled on each MTI.
72757
Customer 2 Houston Site
Customer 1 Dallas Site
CE3
25-5
When the router receives a multicast packet from the customer side of the network, it uses the incoming interfaces VRF to determine which MVRFs should receive it. The router then encapsulates the packet using GRE encapsulation. When the router encapsulates the packet, it sets the source address to that of the BGP peering interface and sets the destination address to the multicast address of the default MDT, or to the source address of the data MDT if configured. The router then replicates the packet as needed for forwarding on the appropriate number of MTI interfaces. When the router receives a packet on the MTI interface, it uses the destination address to identify the appropriate default MDT or data MDT, which in turn identifies the appropriate MVRF. It then decapsulates the packet and forwards it out the appropriate interfaces, replicating it as many times as are necessary.
Note
Unlike other tunnel interfaces that are commonly used on Cisco routers, the MVPN MTI is classified as a LAN interface, not a point-to-point interface. The MTI interface is not configurable, but you can use the show interface tunnel command to display its status. The MTI interface is used exclusively for multicast traffic over the VPN tunnel. The tunnel does not carry unicast routed traffic.
PE Router Routing Table Support for MVPN

Each PE router that supports the MVPN feature uses the following routing tables to ensure that the VPN and MVPN traffic is routed correctly:
Default routing tableStandard routing table used in all Cisco routers. This table contains the routes that are needed for backbone traffic and for non-MPLS VPN unicast and multicast traffic (including Generic Routing Encapsulation (GRE) multicast traffic). VPN routing/forwarding (VRF) tableRouting table created for each VRF instance. Responsible for routing the unicast traffic between VPNs in the MPLS network. Multicast VRF (MVRF) tableMulticast routing table and multicast routing protocol instance created for each VRF instance. Responsible for routing the multicast traffic in the multicast domain of the network. This table also includes the multicast tunnel interfaces that are used to access the multicast domain.
Multicast Distributed Switching Support

MVPN supports multicast distributed switching (MDS) for multicast support on a per-interface and a per-VRF basis. When configuring MDS, you must make sure that no interface (including loopback interfaces) has the no ip mroute-cache command configured.
Hardware-Assisted IPv4 Multicast

PFC3BXL or PFC3B mode supports hardware acceleration for IPv4 multicast over VPN traffic, which forwards multicast traffic to the appropriate VPNs at wire speed without increased MSFC3 CPU utilization. In a customer VRF, PFC3BXL or PFC3B mode hardware acceleration supports multicast traffic in PIM dense, PIM sparse, PIM bidirectional, and PIM Source Specific Multicast (SSM) modes.
25-6
OL-3999-08
Chapter 25
Configuring IPv4 Multicast VPN Support MVPN Configuration Guidelines and Restrictions
In the service provider core, PFC3BXL or PFC3B mode hardware acceleration supports multicast traffic in PIM sparse, PIM bidirectional, and PIM SSM modes. In the service provider core, PFC3BXL or PFC3B mode hardware acceleration does not support multicast traffic in PIM dense mode.
MVPN Configuration Guidelines and Restrictions

When configuring MVPN, follow these guidelines and restrictions:

Release 12.2(18)SXE and later releases support MVPN when the switch is operating in PFC3B mode or PFC3BXL mode. Supervisor Engine 2 does not support MVPN. All PE routers in the multicast domain need to be running a Cisco IOS software image that supports the MVPN feature. There is no requirement for MVPN support on the P and CE routers. Support for IPv4 multicast traffic must also be enabled on all backbone routers. The Border Gateway Protocol (BGP) routing protocol must be configured and operational on all routers supporting multicast traffic. In addition, BGP extended communities must be enabled (using the neighbor send-community both or neighbor send-community extended command) to support the use of MDTs in the network. Only ingress replication is supported when MVPN is configured. If the switch is currently configured for egress replication, it is forced into ingress replication when the first MVRF is configured. When the switch is acting as a PE, and receives a multicast packet from a customer router with a time-to-live (TTL) value of 2, it drops the packet instead of encapsulating it and forwarding it across the MVPN link. Because such packets would normally be dropped by the PE at the other end of the MVPN link, this does not affect traffic flow. If the core multicast routing uses SSM, then the data and default multicast distribution tree (MDT) groups must be configured within the SSM range of IPv4 addresses. The update source interface for the BGP peerings must be the same for all BGP peerings configured on the router in order for the default MDT to be configured properly. If you use a loopback address for BGP peering, then PIM sparse mode must be enabled on the loopback address. The ip mroute-cache command must be enabled on the loopback interface used as the BGP peering interface in order for distributed multicast switching to function on the platforms that support it. The no ip mroute-cache command must not be present on these interfaces. Data MDTs are not created for VRF PIM dense mode multicast streams because of the flood and prune nature of dense mode multicast flows and the resulting periodic bring-up and tear-down of such data MDTs. Data MDTs are not created for VRF PIM bidirectional mode because source information is not available. MVPN does not support multiple BGP peering update sources, and configuring them can break MVPN RPF checking. The source IPv4 address of the MVPN tunnels is determined by the highest IPv4 address used for the BGP peering update source. If this IPv4 address is not the IPv4 address used as the BGP peering address with the remote PE router, MVPN will not function properly. MDT tunnels do not carry unicast traffic. Although MVPN uses the infrastructure of MPLS VPN networks, you cannot apply MPLS tags or labels to multicast traffic over the VPNs.
25-7
Chapter 25 Configuring MVPN
Each MVRF that is configured with a default MDT uses three hidden VLANs (one each for encapsulation, decapsulation, and interface), in addition to external, user-visible VLANs. This means that an absolute maximum of 1,000 MVRFs are supported on each router. (MVRFs without a configured MDT still use one internal VLAN, so unused MVRFs should be deleted to conserve VLAN allocation.) Because MVPN uses MPLS, MVPN supports only the RPR and RPR+ redundancy modes. In Release 12.2(18)SXD and rebuilds, MPLS can coexist with NSF with SSO redundancy mode, but there is no support for stateful MPLS switchover. If your MPLS VPN network already contains a network of VRFs, you do not need to delete them or recreate them to be able to support MVRF traffic. Instead, configure the mdt default and mdt data commands, as listed in the following procedure, to enable multicast traffic over the VRF. BGP should be already configured and operational on all routers that are sending or receiving multicast traffic. In addition, BGP extended communities must be enabled (using the neighbor send-community both or neighbor send-community extended command) to support the use of MDTs in the network. The same MVRF must be configured on each PE router that is to support a particular VPN connection. Each PE router that supports a particular MVRF must be configured with the same mdt default command. The switch supports only ingress replication when MVPN is configured. If a switch is currently configured for egress replication, it is forced into ingress replication when the first MVRF is configured. If a switch is currently configured for egress replication, we recommend performing this task only during scheduled maintenance periods, so that traffic disruption can be kept to a minimum.
Configuring MVPN
These sections describe how to configure MVPN:

Forcing Ingress Multicast Replication Mode (Optional), page 25-8 Configuring a Multicast VPN Routing and Forwarding Instance, page 25-9 Configuring Multicast VRF Routing, page 25-15 Configuring Interfaces for Multicast Routing to Support MVPN, page 25-20
Note
These configuration tasks assume that BGP is already configured and operational on all routers that are sending or receiving the multicast traffic. In addition, BGP extended communities must be enabled (using the neighbor send-community both or neighbor send-community extended command) to support the use of MDTs in the network.
Forcing Ingress Multicast Replication Mode (Optional)

The MVPN feature supports only ingress multicast replication mode. If the switch is currently configured for egress replication, it is forced into ingress replication when the first MVRF is configured. This change in replication mode automatically purges all forwarding entries in the hardware, temporarily forcing the switch into software switching until the table entries can be rebuilt.
25-8
OL-3999-08
Chapter 25
Configuring IPv4 Multicast VPN Support Configuring MVPN
To avoid disrupting customer traffic, we recommend verifying that the switch is already in ingress multicast replication mode before configuring any MVRFs. This example shows how to verify the multicast replication mode:
Router# show mls ip multicast capability Current mode of replication is Ingress auto replication mode detection is ON Slot 2 5 6 8 9 Router# Multicast replication capability Egress Egress Egress Ingress Ingress
If the current replication mode is egress or if any of the switching modules are capable of egress replication mode, configure ingress replication mode during a scheduled maintenance period to minimize the disruption of customer traffic. To configure ingress multicast replication mode, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# mls ip multicast replication-mode ingress
Purpose Enters global configuration mode. Configures ingress multicast replication mode and disables automatic detection of the replication mode (enabled by default). Enables automatic detection of the replication mode. Verifies the configuration.
Router(config)# no mls ip multicast replication-mode ingress
Step 3
Router(config)# do show mls ip multicast capability | include Current
This example shows how to configure ingress multicast replication mode and verify the configuration:
Router(config)# mls ip multicast replication-mode ingress Router(config)# do show mls ip multicast capability | include Current Current mode of replication is Ingress
Configuring a Multicast VPN Routing and Forwarding Instance

These sections describe how to configure a multicast VPN routing and forwarding (MVRF) instance for each VPN connection on each PE router that is to handle the traffic for each particular VPN connection that is to transmit or receive multicast traffic:

Configuring a VRF Entry, page 25-10 Configuring the Route Distinguisher, page 25-10 Configuring the Route-Target Extended Community, page 25-11 Configuring the Default MDT, page 25-11 Configuring Data MDTs (Optional), page 25-12 Enabling Data MDT Logging, page 25-12
25-9
Sample Configuration, page 25-13 Displaying VRF Information, page 25-13
Configuring a VRF Entry

To configure a VRF entry, perform this task: Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# ip vrf vrf_name
Purpose Enters global configuration mode. Configures a VRF routing table entry and a Cisco Express Forwarding (CEF) table entry and enters VRF configuration mode. Deletes the VRF entry. Verifies the configuration.
Router(config)# no ip vrf vrf_name
Step 3
Router(config-vrf)# do show ip vrf vrf_name
This example show how to configure a VRF named blue and verify the configuration:
Router# configure terminal Router(config)# ip vrf blue Router(config-vrf)# do show ip vrf blue Name Default RD blue <not set>
Interfaces
Configuring the Route Distinguisher

To configure the route distinguisher, perform this task: Command or Action
Step 1
Router(config-vrf)# rd route_distinguisher Router(config-vrf)# no rd route_distinguisher
Purpose Specifies the route distinguisher for a VPN IPv4 prefix. Deletes the route distinguisher. Verifies the configuration.
Step 2
Router(config-vrf)# do show ip vrf vrf_name
When configuring the route distinguisher, enter the route distinguisher in one of the following formats:

16-bit AS number:your 32-bit number (101:3) 32-bit IPv4 address:your 16-bit number (192.168.122.15:1)
This example show how to configure 55:1111 as the route distinguisher and verify the configuration:
Router(config-vrf)# rd 55:1111 Router(config-vrf)# do show ip vrf blue Name Default RD blue 55:1111
Interfaces
25-10
OL-3999-08
Chapter 25
Configuring the Route-Target Extended Community

To configure the route-target extended community, perform this task: Command or Action
Step 1
Router(config-vrf)# route-target [import | export | both] route_target_ext_community Router(config-vrf)# no route-target [[import | export | both] route_target_ext_community]
Purpose Configures a route-target extended community for the VRF. Deletes the route-target extended community. Verifies the configuration.
Step 2
Router(config-vrf)# do show ip vrf detail
When configuring the route-target extended community, note the following information:

importImports routing information from the target VPN extended community. exportExports routing information to the target VPN extended community. both Imports and exports. route_target_ext_communityAdds the 48-bit route-target extended community to the VRF. Enter the number in one of the following formats:
16-bit AS number:your 32-bit number (101:3) 32-bit IPv4 address:your 16-bit number (192.168.122.15:1)
This example shows how to configure 55:1111 as the import and export route-target extended community and verify the configuration:
Router(config-vrf)# route-target both 55:1111 Router(config-vrf)# do show ip vrf detail VRF blue; default RD 55:1111; default VPNID <not set> VRF Table ID = 1 No interfaces Connected addresses are not in global routing table Export VPN route-target communities RT:55:1111 Import VPN route-target communities RT:55:1111 No import route-map No export route-map CSC is not configured.
Configuring the Default MDT

To configure the default MDT, perform this task: Command or Action
Router(config-vrf)# mdt default group_address Router(config-vrf)# no mdt default
Purpose Configures the default MDT. Deletes the default MDT.
25-11
When configuring the default MDT, note the following information:
The group_address is the multicast IPv4 address of the default MDT group. This address serves as an identifier for the MVRF community, because all provider-edge (PE) routers configured with this same group address become members of the group, which allows them to receive the PIM control messages and multicast traffic that are sent by other members of the group. This same default MDT must be configured on each PE router to enable the PE routers to receive multicast traffic for this particular MVRF.
This example shows how to configure 239.1.1.1 as the default MDT:

Router(config-vrf)# mdt default 239.1.1.1
Configuring Data MDTs (Optional)

To configure optional data MDTs, perform this task: Command or Action
Router(config-vrf)# mdt data group_address wildcard_bits [threshold threshold_value] [list access_list] Router(config-vrf)# no mdt data
Purpose (Optional) Configures a data MDTs for the specified range of multicast addresses. Deletes the data MDT.
When configuring optional data MDTs, note the following information:

group_address1 Multicast group address. The address can range from 224.0.0.1 to 239.255.255.255, but cannot overlap the address that has been assigned to the default MDT. wildcard_bits Wildcard bitmask to be applied to the multicast group address to create a range of possible addresses. This allows you to limit the maximum number of data MDTs that each MVRF can support. threshold threshold_value(Optional) Defines the threshold value in kilobits, at which multicast traffic should be switched from the default MDT to the data MDT. The threshold_value parameter can range from 1 through 4294967 kilobits. list access_list(Optional) Specifies an access list name or number to be applied to this traffic.
This example shows how to configure a data MDT:

Router(config-vrf)# mdt data 239.1.2.0 0.0.0.3 threshold 10
Enabling Data MDT Logging

To enable data MDT logging, perform this task: Command or Action
Router(config-vrf)# mdt log-reuse
Purpose (Optional) Enables the recording of data MDT reuse information, by generating a SYSLOG message whenever a data MDT is reused. Frequent reuse of a data MDT might indicate a need to increase the number of allowable data MDTs by increasing the size of the wildcard bitmask that is used in the mdt data command. Disables data MDT logging.
Router(config-vrf)# no log-reuse
25-12
OL-3999-08
Chapter 25
This example shows how to enable data MDT logging:

Router(config-vrf)# mdt log-reuse
Sample Configuration
The following excerpt from a configuration file shows typical VRF configurations for a range of VRFs. To simplify the display, only the starting and ending VRFs are shown.
! ip vrf mvpn-cus1 rd 200:1 route-target export 200:1 route-target import 200:1 mdt default 239.1.1.1 ! ip vrf mvpn-cus2 rd 200:2 route-target export 200:2 route-target import 200:2 mdt default 239.1.1.2 ! ip vrf mvpn-cus3 rd 200:3 route-target export 200:3 route-target import 200:3 mdt default 239.1.1.3 ! ... ip vrf mvpn-cus249 rd 200:249 route-target export 200:249 route-target import 200:249 mdt default 239.1.1.249 mdt data 239.1.1.128 0.0.0.7
Displaying VRF Information

To display all of the VRFs that are configured on the switch, use the show ip vrf command:
Router# show ip vrf Name green red Default RD 1:52 200:1 Interfaces GigabitEthernet6/1 GigabitEthernet1/1 GigabitEthernet3/16 Loopback2
Router#
To display information about the MDTs that are currently configured for all MVRFs, use the show ip pim mdt command. The following example shows typical output for this command:
Router# show ip pim mdt MDT Group 227.1.0.1 227.2.0.1 228.1.0.1 228.2.0.1 Interface Tunnel1 Tunnel2 Tunnel3 Tunnel4 Source Loopback0 Loopback0 Loopback0 Loopback0 VRF BIDIR01 BIDIR02 SPARSE01 SPARSE02
* * * *
25-13
Note
To display information about a specific tunnel interface, use the show interface tunnel command. The IPv4 address for the tunnel interface is the multicast group address for the default MDT of the MVRF. To display additional information about the MDTs, use the show mls ip multicast mdt command. The following example shows typical output for this command:
Router# show mls ip multicast mdt State: H - Hardware Installed, I - Install Pending, D - Delete Pending, Z - Zombie MMLS VPN-ID 1 2 3 4 5 5 5 5 5
VRF BIDIR01HWRP BIDIR01SWRP SPARSE01HWRP SPARSE01SWRP red red red red red Router#
MDT INFO (10.10.10.9, 227.1.0.1) (10.10.10.9, 227.2.0.1) (10.10.10.9, 228.1.0.1) (10.10.10.9, 228.2.0.1) (6.6.6.6, 234.1.1.1) (131.2.1.2, 228.1.1.75) (131.2.1.2, 228.1.1.76) (131.2.1.2, 228.1.1.77) (131.2.1.2, 228.1.1.78)
MDT Type default default default default default data (send) data (send) data (send) data (send)
State H H H H H H H H H
To display routing information for a particular VRF, use the show ip route vrf command:
Router# show ip route vrf red Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2 E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area * - candidate default, U - per-user static route, o - ODR P - periodic downloaded static route Gateway of last resort is not set 2.0.0.0/32 2.2.2.2 3.0.0.0/32 3.3.3.3 21.0.0.0/8 22.0.0.0/8 is subnetted, 1 subnets is directly connected, Loopback2 is subnetted, 1 subnets [200/0] via 3.1.1.3, 00:20:09 is directly connected, GigabitEthernet3/16 [200/0] via 3.1.1.3, 00:20:09
C B C B
Router#
25-14
OL-3999-08
Chapter 25
To display information about the multicast routing table and tunnel interface for a particular MVRF, use the show ip mroute vrf command. The following example shows typical output for a MVRF named BIDIR01:
Router# show ip mroute vrf BIDIR01 IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing interface flags: H - Hardware switched Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 228.1.0.1), 00:16:25/stopped, RP 10.10.10.12, flags: SJCF Incoming interface: Tunnel1, RPF nbr 10.10.10.12, Partial-SC Outgoing interface list: GigabitEthernet3/1.3001, Forward/Sparse-Dense, 00:16:25/00:02:49, H (6.9.0.100, 228.1.0.1), 00:14:13/00:03:29, flags: FT Incoming interface: GigabitEthernet3/1.3001, RPF nbr 0.0.0.0, RPF-MFD Outgoing interface list: Tunnel1, Forward/Sparse-Dense, 00:14:13/00:02:46, H Router#
Note
In this example, the show ip mroute vrf command shows that Tunnel1 is the MDT tunnel interface (MTI) being used by this VRF.
Configuring Multicast VRF Routing

These sections describe how to configure multicast routing to support MVPN:

Enabling IPv4 Multicast Routing Globally, page 25-16 Enabling IPv4 Multicast VRF Routing, page 25-16 Configuring a PIM VRF Register Message Source Address, page 25-16 Specifying the PIM VRF Rendezvous Point (RP) Address, page 25-17 Configuring a Multicast Source Discovery Protocol (MSDP) Peer, page 25-17 Enabling IPv4 Multicast Header Storage, page 25-18 Configuring the Maximum Number of Multicast Routes, page 25-18 Sample Configuration, page 25-19 Displaying IPv4 Multicast VRF Routing Information, page 25-20
Note
BGP should be already configured and operational on all routers that are sending or receiving multicast traffic. In addition, BGP extended communities must be enabled (using the neighbor send-community both or neighbor send-community extended command) to support the use of MDTs in the network.
25-15
Enabling IPv4 Multicast Routing Globally

To enable IPv4 multicast routing globally, perform this task: Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# ip multicast-routing Router(config)# no ip multicast-routing
Purpose Enters global configuration mode. Enables IPv4 multicast routing globally. Disables IPv4 multicast routing globally.
This example show how to enable IPv4 multicast routing globally:

Router# configure terminal Router(config)# ip multicast-routing
Enabling IPv4 Multicast VRF Routing

To enable IPv4 multicast VRF routing, perform this task: Command or Action
Router(config)# ip multicast-routing vrf vrf_name [distributed] Router(config)# no ip multicast-routing
Purpose Enables IPv4 multicast VRF routing. Disables IPv4 multicast VRF routing.
When enabling IPv4 multicast VRF routing, note the following information:
vrf_nameSpecifies a particular VRF for multicast routing. The vrf_name should refer to a VRF that has been previously created, as specified in the Configuring a Multicast VPN Routing and Forwarding Instance section on page 25-9. distributed(Optional) Enables Multicast Distributed Switching (MDS).
This example show how to enable IPv4 multicast VRF routing:

Router# configure terminal Router(config)# ip multicast-routing vrf blue
Configuring a PIM VRF Register Message Source Address

To configure a PIM VRF register message source address, perform this task: Command or Action
Router(config)# ip pim vrf vrf_name register-source interface_type interface_number
Purpose (Optional) Configures a PIM VRF register message source address. You can configure a loopback interface as the source of the register messages. Disables IPv4 multicast VRF routing.
Router(config)# no ip pim vrf vrf_name register-source
This example show how to configure a PIM VRF register message source address:
Router(config)# ip pim vrf blue register-source loopback 3
25-16
OL-3999-08
Chapter 25
Specifying the PIM VRF Rendezvous Point (RP) Address

To specify the PIM VRF RP address, perform this task: Command or Action
Router(config)# ip pim vrf vrf_name rp-address rp_address [access_list] [override] [bidir] Router(config)# no ip pim vrf vrf_name rp-address rp_address
Purpose Specifies the PIM RP IPv4 address for a (required for sparse PIM networks): Clears the PIM RP IPv4 address.
When specifying the PIM VRF RP address, note the following information:

vrf vrf_name(Optional) Specifies a particular VRF instance to be used. rp_addressUnicast IP address for the PIM RP router. access_list(Optional) Number or name of an access list that defines the multicast groups for the RP. override(Optional) In the event of conflicting RP addresses, this particular RP overrides any RP that is learned through Auto-RP. bidir(Optional) Specifies that the multicast groups specified by the access_list argument are to operate in bidirectional mode. If this option is not specified, the groups operate in PIM sparse mode. Use bidirectional mode whenever possible, because it offers better scalability.
This example show how to specify the PIM VRF RP address:

Router(config)# ip pim vrf blue rp-address 198.196.100.33
Configuring a Multicast Source Discovery Protocol (MSDP) Peer

To configure an MSDP peer, perform this task: Command or Action
Router(config)# ip msdp vrf vrf_name peer {peer_name | peer_address} [connect-source interface_type interface_number] [remote-as ASN] Router(config)# no ip msdp vrf vrf_name peer {peer_name | peer_address} [connect-source interface_type interface_number] [remote-as ASN]
Purpose (Optional) Configures an MSDP peer.
Clears the PIM RP IPv4 address.
When configuring an MSDP peer, note the following information:

vrf vrf_nameSpecifies a particular VRF instance to be used. {peer_name | peer_address}Domain Name System (DNS) name or IP address of the MSDP peer router. connect-source interface_type interface_numberInterface name and number for the interface whose primary address is used as the source IP address for the TCP connection. remote-as ASN (Optional) Autonomous system number of the MSDP peer. This is for display-only purposes.
25-17
This example show how to configure an MSDP peer:

Router(config)# ip msdp peer router.cisco.com connect-source fastethernet 1/1 remote-as 109
Enabling IPv4 Multicast Header Storage

To enable IPv4 multicast header storage, perform this task: Command or Action
Router(config)# ip multicast vrf vrf_name cache-headers [rtp] Router(config)# no ip multicast vrf vrf_name cache-headers [rtp]
Purpose (Optional) Enables a circular buffer to store IPv4 multicast packet headers. Disables IPv4 multicast header storage.
When enabling IPv4 multicast header storage, note the following information:

vrf vrf_nameAllocates a buffer for the specified VRF. rtp(Optional) Also caches Real-Time Transport Protocol (RTP) headers. The buffers can be displayed with the show ip mpacket command.
This example show how to enable IPv4 multicast header storage:

Router(config)# ip multicast vrf blue cache-headers
Configuring the Maximum Number of Multicast Routes

To configure the maximum number of multicast routes, perform this task: Command or Action
Router(config)# ip multicast vrf vrf_name route-limit limit [threshold] Router(config)# no ip multicast vrf vrf_name route-limit limit [threshold]
Purpose (Optional) Configures the maximum number of multicast routes that can be added for multicast traffic. Clears the configured maximum number of routes.
When configuring the maximum number of routes, note the following information:

vrf vrf_name Enables route limiting for the specified VRF. limitThe number of multicast routes that can be added. The range is from 1 to 2147483647, with a default of 2147483647. threshold (Optional) Number of multicast routes that can be added before a warning message occurs. The valid range is from 1 to the value of the limit parameter.
This example show how to configure the maximum number of multicast routes:
Router(config)# ip multicast vrf blue route-limit 200000 20000
25-18
OL-3999-08
Chapter 25
Configuring IPv4 Multicast Route Filtering

To configure IPV4 multicast route filtering, perform this task: Command or Action
Router(config)# ip multicast mrinfo-filter access_list
Purpose (Optional) Configures IPV4 multicast route filtering with an access list. The access_list parameter can be the name or number of a access list. Clears the configured maximum number of routes.
Router(config)# no ip multicast mrinfo-filter
This example show how to configure IPV4 multicast route filtering:

Router(config)# ip multicast mrinfo-filter 101
The following excerpt from a configuration file shows the minimum configuration that is needed to support multicast routing for a range of VRFs. To simplify the display, only the starting and ending VRFs are shown.
! ip ip ip ip ... ip multicast-routing vrf vpn249 ip multicast-routing vrf vpn250 ip multicast cache-headers multicast-routing multicast-routing vrf lite multicast-routing vrf vpn201 multicast-routing vrf vpn202
... ip ip ip ip ... ip pim vrf vpn249 rp-address 192.200.49.6 ip pim vrf vpn250 rp-address 192.200.50.6 ... pim pim pim pim rp-address 192.0.1.1 vrf lite rp-address 104.1.1.2 vrf vpn201 rp-address 192.200.1.1 vrf vpn202 rp-address 192.200.2.1
25-19
Displaying IPv4 Multicast VRF Routing Information

To display the known PIM neighbors for a particular MVRF, use the show ip pim vrf neighbor command:
Router# show ip pim vrf 98 neighbor PIM Neighbor Table Neighbor Interface Address 40.60.0.11 Tunnel96 40.50.0.11 Tunnel96 Router#
Uptime/Expires
Ver
00:00:31/00:01:13 v2 00:00:54/00:00:50 v2
DR Prio/Mode 1 / S 1 / S
Configuring Interfaces for Multicast Routing to Support MVPN

These sections describe how to configure interfaces for multicast routing to support MVPN:

Multicast Routing Configuration Overview, page 25-20 Configuring PIM on an Interface, page 25-20 Configuring an Interface for IPv4 VRF Forwarding, page 25-21 Sample Configuration, page 25-22
Multicast Routing Configuration Overview

Protocol Independent Multicast (PIM) must be configured on all interfaces that are being used for IPv4 multicast traffic. In a VPN multicast environment, you should enable PIM on at least all of the following interfaces:

Physical interface on a provider edge (PE) router that is connected to the backbone. Loopback interface that is used for BGP peering. Loopback interface that is used as the source for the sparse PIM rendezvous point (RP) router address.
In addition, you must also associate MVRFs with those interfaces over which they are going to forward multicast traffic. BGP should be already configured and operational on all routers that are sending or receiving multicast traffic. In addition, BGP extended communities must be enabled (using the neighbor send-community both or neighbor send-community extended command) to support the use of MDTs in the network.
Configuring PIM on an Interface

To configure PIM on an interface, perform this task: Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# interface type {slot/port | number}
Purpose Enters global configuration mode. Enters interface configuration mode for the specified interface.
25-20
OL-3999-08
Chapter 25
Command or Action
Step 3
Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode} Router(config)# no ip pim [dense-mode | sparse-mode | sparse-dense-mode]
Purpose Enables PIM on the interface. Disables PIM.
When configuring PIM on an interface, note the following information:
You can use one of these interface types:

A physical interface on a provider edge (PE) router that is connected to the backbone. A loopback interface that is used for BGP peering. A loopback interface that is used as the source for the sparse PIM network rendezvous point
(RP) address.
These are the PIM modes:

dense-modeEnables dense mode of operation. sparse-modeEnables sparse mode of operation. sparse-dense-modeEnables sparse mode if the multicast group has an RP router defined, or
enables dense mode if an RP router is not defined.
Use sparse-mode for the physical interfaces of all PE routers that are connected to the backbone, and on all loopback interfaces that are used for BGP peering or as the source for RP addressing.
This example shows how to configure PIM sparse mode on a physical interface:
Router# configure terminal interface gigabitethernet 10/1 Router(config-if)# ip pim sparse-mode
This example shows how to configure PIM sparse mode on a loopback interface:
Router# configure terminal Router(config)# interface loopback 2 Router(config-if)# ip pim sparse-mode
Configuring an Interface for IPv4 VRF Forwarding

To configure an interface for IPv4 VRF forwarding, perform this task: Command or Action
Router(config-if)# ip vrf forwarding vrf_name
Purpose (Optional) Associates the specified VRF routing and forwarding tables with the interface. If this is not specified, the interface defaults to using the global routing table.
Note
Entering this command on an interface removes the IP address, so reconfigure the IP address.
Router(config-if)# no ip vrf forwarding [vrf_name]
Disables IPv4 VRF forwarding.
This example shows how to configure the interface for VRF blue forwarding:
Router(config-if)# ip vrf forwarding blue
25-21
Chapter 25 Sample Configurations for MVPN
The following excerpt from a configuration file shows the interface configuration, along with the associated MVRF configuration, to enable multicast traffic over a single MVRF:
ip multicast-routing vrf blue ip multicast-routing ip vrf blue rd 100:27 route-target export 100:27 route-target import 100:27 mdt default 239.192.10.2 interface GigabitEthernet1/1 description blue connection ip vrf forwarding blue ip address 192.168.2.26 255.255.255.0 ip pim sparse-mode interface GigabitEthernet1/15 description Backbone connection ip address 10.8.4.2 255.255.255.0 ip pim sparse-mode ip pim vrf blue rp-address 192.7.25.1 ip pim rp-address 10.1.1.1
Sample Configurations for MVPN

This section contains the following sample configurations for the MVPN feature:

MVPN Configuration with Default MDTs Only, page 25-22 MVPN Configuration with Default and Data MDTs, page 25-24
MVPN Configuration with Default MDTs Only

The following excerpt from a configuration file shows the lines that are related to the MVPN configuration for three MVRFs. (The required BGP configuration is not shown.)
! version 12.2 service timestamps debug datetime msec service timestamps log datetime msec service password-encryption service compress-config ! hostname MVPN Router ! boot system flash slot0: logging snmp-authfail ! ip subnet-zero ! ! no ip domain-lookup ip host tftp 223.255.254.238 !
25-22
OL-3999-08
Chapter 25
Configuring IPv4 Multicast VPN Support Sample Configurations for MVPN
ip vrf mvpn-cus1 rd 200:1 route-target export 200:1 route-target import 200:1 mdt default 239.1.1.1 ! ip vrf mvpn-cus2 rd 200:2 route-target export 200:2 route-target import 200:2 mdt default 239.1.1.2 ! ip vrf mvpn-cus3 rd 200:3 route-target export 200:3 route-target import 200:3 mdt default 239.1.1.3 ! ip multicast-routing ip multicast-routing vrf mvpn-cus1 ip multicast-routing vrf mvpn-cus2 ip multicast-routing vrf mvpn-cus3 ip multicast multipath frame-relay switching mpls label range 4112 262143 mpls label protocol ldp mpls ldp logging neighbor-changes mpls ldp explicit-null mpls traffic-eng tunnels tag-switching tdp discovery directed-hello accept from 1 tag-switching tdp router-id Loopback0 force mls ip multicast replication-mode ingress mls ip multicast flow-stat-timer 9 mls ip multicast bidir gm-scan-interval 10 mls flow ip destination no mls flow ipv6 mls rate-limit unicast cef glean 10 10 mls qos mls cef error action freeze ... vlan internal allocation policy ascending vlan access-log ratelimit 2000 ! vlan 2001-2101,3501-3700,4001,4051-4080,4093 ! ! ! interface Loopback0 ip address 201.252.1.14 255.255.255.255 ip pim sparse-dense-mode ! interface Loopback1 ip address 209.255.255.14 255.255.255.255 ! interface Loopback10 ip vrf forwarding mvpn-cus1 ip address 210.101.255.14 255.255.255.255 ! interface Loopback11 ip vrf forwarding mvpn-cus1 ip address 210.111.255.14 255.255.255.255 ip pim sparse-dense-mode
25-23
! interface Loopback12 ip vrf forwarding mvpn-cus1 ip address 210.112.255.14 255.255.255.255 ... ! interface GigabitEthernet3/3 mtu 9216 ip vrf forwarding mvpn-cus3 ip address 172.10.14.1 255.255.255.0 ip pim sparse-dense-mode ! ... ! interface GigabitEthernet3/19 ip vrf forwarding mvpn-cus2 ip address 192.16.4.1 255.255.255.0 ip pim sparse-dense-mode ip igmp static-group 229.1.1.1 ip igmp static-group 229.1.1.2 ip igmp static-group 229.1.1.4 ! interface GigabitEthernet3/20 ip vrf forwarding mvpn-cus1 ip address 192.16.1.1 255.255.255.0 ip pim sparse-dense-mode ! ...
MVPN Configuration with Default and Data MDTs

The following sample configuration includes three MVRFs that have been configured for both default and data MDTs. Only the configuration that is relevant to the MVPN configuration is shown.
... ! ip vrf v1 rd 1:1 route-target export 1:1 route-target import 1:1 mdt default 226.1.1.1 mdt data 226.1.1.128 0.0.0.7 threshold 1 ! ip vrf v2 rd 2:2 route-target export 2:2 route-target import 2:2 mdt default 226.2.2.1 mdt data 226.2.2.128 0.0.0.7 ! ip vrf v3 rd 3:3 route-target export 3:3 route-target import 3:3 mdt default 226.3.3.1 mdt data 226.3.3.128 0.0.0.7 ! ip vrf v4
25-24
OL-3999-08
Chapter 25
rd 155.255.255.1:4 route-target export 155.255.255.1:4 route-target import 155.255.255.1:4 mdt default 226.4.4.1 mdt data 226.4.4.128 0.0.0.7 ! ip multicast-routing ip multicast-routing vrf v1 ip multicast-routing vrf v2 ip multicast-routing vrf v3 ip multicast-routing vrf v4 mpls label protocol ldp mpls ldp logging neighbor-changes tag-switching tdp router-id Loopback1 mls ip multicast replication-mode ingress mls ip multicast bidir gm-scan-interval 10 no mls flow ip no mls flow ipv6 mls cef error action freeze ! ! ! ! ! ... vlan internal allocation policy ascending vlan access-log ratelimit 2000 ! ! interface Loopback1 ip address 155.255.255.1 255.255.255.255 ip pim sparse-mode ! interface Loopback4 ip vrf forwarding v4 ip address 155.255.4.4 255.255.255.255 ip pim sparse-mode ! interface Loopback11 ip vrf forwarding v1 ip address 155.255.255.11 255.255.255.255 ip pim sparse-dense-mode ! interface Loopback22 ip vrf forwarding v2 ip address 155.255.255.22 255.255.255.255 ip pim sparse-mode ! interface Loopback33 ip vrf forwarding v3 ip address 155.255.255.33 255.255.255.255 ip pim sparse-mode ! interface Loopback44 no ip address ! interface Loopback111 ip vrf forwarding v1 ip address 1.1.1.1 255.255.255.252 ip pim sparse-dense-mode ip ospf network point-to-point !
25-25
interface GigabitEthernet1/1 description Gi1/1 - 155.50.1.155 255.255.255.0 - peer dut50 - mpls mtu 9216 ip address 155.50.1.155 255.255.255.0 ip pim sparse-mode tag-switching ip ! interface GigabitEthernet1/2 ip vrf forwarding v1 ip address 155.1.2.254 255.255.255.0 ip pim sparse-mode ! interface GigabitEthernet1/3 description Gi1/3 - 185.155.1.155/24 - vrf v1 stub peer 185.Gi1/3 ip vrf forwarding v1 ip address 185.155.1.155 255.255.255.0 ip pim sparse-mode ! ... ! interface GigabitEthernet1/48 ip vrf forwarding v1 ip address 157.155.1.155 255.255.255.0 ip pim bsr-border ip pim sparse-dense-mode ! interface GigabitEthernet6/1 no ip address shutdown ! interface GigabitEthernet6/2 ip address 9.1.10.155 255.255.255.0 media-type rj45 ! interface Vlan1 no ip address shutdown ! router ospf 11 vrf v1 router-id 155.255.255.11 log-adjacency-changes redistribute connected subnets tag 155 redistribute bgp 1 subnets tag 155 network 1.1.1.0 0.0.0.3 area 155 network 155.255.255.11 0.0.0.0 area 155 network 155.0.0.0 0.255.255.255 area 155 network 157.155.1.0 0.0.0.255 area 0 ! router ospf 22 vrf v2 router-id 155.255.255.22 log-adjacency-changes network 155.255.255.22 0.0.0.0 area 155 network 155.0.0.0 0.255.255.255 area 155 network 157.155.1.0 0.0.0.255 area 0 ! router ospf 33 vrf v3 router-id 155.255.255.33 log-adjacency-changes network 155.255.255.33 0.0.0.0 area 155 ! router ospf 1 log-adjacency-changes
25-26
OL-3999-08
Chapter 25
network 155.50.1.0 0.0.0.255 area 0 network 155.255.255.1 0.0.0.0 area 155 ! router bgp 1 bgp router-id 155.255.255.1 no bgp default ipv4-unicast bgp log-neighbor-changes neighbor 175.255.255.1 remote-as 1 neighbor 175.255.255.1 update-source Loopback1 neighbor 185.255.255.1 remote-as 1 neighbor 185.255.255.1 update-source Loopback1 ! address-family vpnv4 neighbor 175.255.255.1 activate neighbor 175.255.255.1 send-community extended neighbor 185.255.255.1 activate neighbor 185.255.255.1 send-community extended exit-address-family ! address-family ipv4 vrf v4 no auto-summary no synchronization exit-address-family ! address-family ipv4 vrf v3 redistribute ospf 33 no auto-summary no synchronization exit-address-family ! address-family ipv4 vrf v2 redistribute ospf 22 no auto-summary no synchronization exit-address-family ! address-family ipv4 vrf v1 redistribute ospf 11 no auto-summary no synchronization exit-address-family ! ip classless ip route 9.255.254.1 255.255.255.255 9.1.10.254 no ip http server ip pim bidir-enable ip pim rp-address 50.255.2.2 MCAST.MVPN.MDT.v2 override bidir ip pim rp-address 50.255.3.3 MCAST.MVPN.MDT.v3 override bidir ip pim rp-address 50.255.1.1 MCAST.MVPN.MDT.v1 override bidir ip pim vrf v1 spt-threshold infinity ip pim vrf v1 send-rp-announce Loopback11 scope 16 group-list MCAST.GROUP.BIDIR bidir ip pim vrf v1 send-rp-discovery Loopback11 scope 16 ip pim vrf v1 bsr-candidate Loopback111 0 ip msdp vrf v1 peer 185.255.255.11 connect-source Loopback11 ip msdp vrf v1 cache-sa-state ! ! ip access-list standard MCAST.ANYCAST.CE permit 2.2.2.2 ip access-list standard MCAST.ANYCAST.PE permit 1.1.1.1 ip access-list standard MCAST.BOUNDARY.VRF.v1 deny 226.192.1.1 permit any
25-27
ip access-list standard MCAST.GROUP.BIDIR permit 226.192.0.0 0.0.255.255 ip access-list standard MCAST.GROUP.SPARSE permit 226.193.0.0 0.0.255.255 ip access-list standard MCAST.MVPN.BOUNDARY.DATA.MDT deny 226.1.1.128 permit any ip access-list standard MCAST.MVPN.MDT.v1 permit 226.1.0.0 0.0.255.255 ip access-list standard MCAST.MVPN.MDT.v2 permit 226.2.0.0 0.0.255.255 ip access-list standard MCAST.MVPN.MDT.v3 permit 226.3.0.0 0.0.255.255 ip access-list standard MCAST.MVPN.RP.v4 permit 227.0.0.0 0.255.255.255 ! access-list 1 permit 226.1.1.1 access-list 2 deny 226.1.1.1 access-list 2 permit any ...
Tip
25-28
OL-3999-08
C H A P T E R
26
Configuring IP Unicast Layer 3 Switching

This chapter describes how to configure IP unicast Layer 3 switching on the Catalyst 6500 series switches.
Note
IPX traffic is fast switched on the MSFC. For more information, refer to this URL: http://www.cisco.com/en/US/docs/ios/12_2/atipx/configuration/guide/fatipx_c.html For information about IP multicast Layer 3 switching, see Chapter 28, Configuring IPv4 Multicast Layer 3 Switching.

Understanding How Layer 3 Switching Works, page 26-2 Default Hardware Layer 3 Switching Configuration, page 26-4 Configuration Guidelines and Restrictions, page 26-4 Configuring Hardware Layer 3 Switching, page 26-5 Displaying Hardware Layer 3 Switching Statistics, page 26-6
Tip
26-1
Understanding How Layer 3 Switching Works

These sections describe Layer 3 switching:

Understanding Hardware Layer 3 Switching, page 26-2 Understanding Layer 3-Switched Packet Rewrite, page 26-2
Understanding Hardware Layer 3 Switching

Hardware Layer 3 switching allows the PFC and DFCs, instead of the MSFC, to forward IP unicast traffic between subnets. Hardware Layer 3 switching provides wire-speed forwarding on the PFC and DFCs, instead of in software on the MSFC. Hardware Layer 3 switching requires minimal support from the MSFC. The MSFC routes any traffic that cannot be hardware Layer 3 switched. Hardware Layer 3 switching supports the routing protocols configured on the MSFC. Hardware Layer 3 switching does not replace the routing protocols configured on the MSFC. Hardware Layer 3 switching runs equally on the PF3 and DFCs to provide IP unicast Layer 3 switching locally on each module. Hardware Layer 3 switching provides the following functions:

Hardware access control list (ACL) switching for policy-based routing (PBR) Hardware NetFlow switching for TCP intercept, reflexive ACL forwarding decisions Hardware Cisco Express Forwarding (CEF) switching for all other IP unicast traffic
Hardware Layer 3 switching on the PFC supports modules that do not have a DFC. The MSFC forwards traffic that cannot be Layer 3 switched. Traffic is hardware Layer 3 switched after being processed by access lists and quality of service (QoS). Hardware Layer 3 switching makes a forwarding decision locally on the ingress-port module for each packet and sends the rewrite information for each packet to the egress port, where the rewrite occurs when the packet is transmitted from the Catalyst 6500 series switch. Hardware Layer 3 switching generates flow statistics for Layer 3-switched traffic. Hardware Layer 3 flow statistics can be used for NetFlow Data Export (NDE). (See Chapter 51, Configuring NDE.)
Understanding Layer 3-Switched Packet Rewrite

When a packet is Layer 3 switched from a source in one subnet to a destination in another subnet, the Catalyst 6500 series switch performs a packet rewrite at the egress port based on information learned from the MSFC so that the packets appear to have been routed by the MSFC. Packet rewrite alters five fields:

Layer 2 (MAC) destination address Layer 2 (MAC) source address Layer 3 IP Time to Live (TTL) Layer 3 checksum Layer 2 (MAC) checksum (also called the frame checksum or FCS)
Note
Packets are rewritten with the encapsulation appropriate for the next-hop subnet.
26-2
OL-3999-08
Chapter 26
Configuring IP Unicast Layer 3 Switching Understanding How Layer 3 Switching Works
If Source A and Destination B are in different subnets and Source A sends a packet to the MSFC to be routed to Destination B, the switch recognizes that the packet was sent to the Layer 2 (MAC) address of the MSFC. To perform Layer 3 switching, the switch rewrites the Layer 2 frame header, changing the Layer 2 destination address to the Layer 2 address of Destination B and the Layer 2 source address to the Layer 2 address of the MSFC. The Layer 3 addresses remain the same. In IP unicast and IP multicast traffic, the switch decrements the Layer 3 TTL value by 1 and recomputes the Layer 3 packet checksum. The switch recomputes the Layer 2 frame checksum and forwards (or, for multicast packets, replicates as necessary) the rewritten packet to Destination Bs subnet. A received IP unicast packet is formatted (conceptually) as follows: Layer 2 Frame Header Destination MSFC MAC Source Source A MAC Layer 3 IP Header Destination Destination B IP Source Source A IP TTL n Checksum calculation1 Data FCS
After the switch rewrites an IP unicast packet, it is formatted (conceptually) as follows: Layer 2 Frame Header Destination Source Destination B MAC MSFC MAC Layer 3 IP Header Destination Source TTL Checksum calculation2 Destination B IP Source A IP n-1 Data FCS
Hardware Layer 3 Switching Examples

Figure 26-1 on page 26-4 shows a simple network topology. In this example, Host A is on the Sales VLAN (IP subnet 171.59.1.0), Host B is on the Marketing VLAN (IP subnet 171.59.3.0), and Host C is on the Engineering VLAN (IP subnet 171.59.2.0). When Host A initiates an HTTP file transfer to Host C, Hardware Layer 3 switching uses the information in the local forwarding information base (FIB) and adjacency table to forward packets from Host A to Host C.
26-3
Chapter 26 Default Hardware Layer 3 Switching Configuration
Figure 26-1 Hardware Layer 3 Switching Example Topology
Source IP Address 171.59.1.2 171.59.1.2 171.59.2.2
Destination IP Address 171.59.3.1 171.59.2.2 171.59.1.2
Rewrite Src/Dst MAC Address Dd:Bb Dd:Cc Dd:Aa
Destination VLAN Marketing Engineering Sales MAC = Bb
MAC = Dd MSFC MAC = Aa Subnet 1/Sales Host A 171.59.1.2
Sub
Sub
ne
a t 3/M
rket
ing
Host B 171.59.3.1
net
2/E
ngin
eeri
ng MAC = Cc
Data 171.59.1.2:171.59.2.2 Aa:Dd
Default Hardware Layer 3 Switching Configuration

Table 26-1 shows the default hardware Layer 3 switching configuration.
Table 26-1 Default Hardware Layer 3 Switching Configuration
Feature Hardware Layer 3 switching enable state Cisco IOS CEF enable state on MSFC Cisco IOS dCEF enable state on MSFC
1. dCEF = Distributed Cisco Express Forwarding
1
Default Value Enabled (cannot be disabled) Enabled (cannot be disabled) Enabled (cannot be disabled)
Configuration Guidelines and Restrictions

Follow these guidelines and restrictions when configuring hardware Layer 3 switching:
Hardware Layer 3 switching supports the following ingress and egress encapsulations:
Ethernet V2.0 (ARPA) 802.3 with 802.2 with 1 byte control (SAP1)
26-4
44610
Host C 171.59.2.2 Data 171.59.1.2:171.59.2.2 Dd:Cc
OL-3999-08
Chapter 26
Configuring IP Unicast Layer 3 Switching Configuring Hardware Layer 3 Switching
Configuring Hardware Layer 3 Switching

Note
For information on configuring unicast routing on the MSFC, see Chapter 22, Configuring Layer 3 Interfaces. Hardware Layer 3 switching is permanently enabled. No configuration is required. To display information about Layer 3-switched traffic, perform this task:
Command
Router# show interface {{type slot/port} | {port-channel number}} | begin L3 1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
1
Purpose Displays a summary of Layer 3-switched traffic.
This example shows how to display information about hardware Layer 3-switched traffic on Fast Ethernet port 3/3:
Router# show interface fastethernet 3/3 | begin L3 L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 12 pkt, 778 bytes mcast L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes 4046399 packets input, 349370039 bytes, 0 no buffer Received 3795255 broadcasts, 2 runts, 0 giants, 0 throttles <...output truncated...> Router#
Note
The Layer 3 switching packet count is updated approximately every five seconds. Cisco IOS CEF and dCEF are permanently enabled. No configuration is required to support hardware Layer 3 switching. With a PFC (and DFCs, if present), hardware Layer 3 switching uses per-flow load balancing based on IP source and destination addresses. Per-flow load balancing avoids the packet reordering that can be necessary with per-packet load balancing. For any given flow, all PFC- and DFC-equipped switches make exactly the same load-balancing decision, which can result in nonrandom load balancing. The Cisco IOS CEF ip load-sharing per-packet, ip cef accounting per-prefix, and ip cef accounting non-recursive commands on the MSFC apply only to traffic that is CEF-switched in software on the MSFC. The commands do not affect traffic that is hardware Layer 3 switched on the PFC or on DFC-equipped switching modules. For information about Cisco IOS CEF and dCEF on the MSFC, refer to these publications:
The Cisco Express Forwarding sections at this URL: http://www.cisco.com/en/US/docs/ios/12_2/switch/configuration/guide/xcfcef.html The Cisco IOS Switching Services Command Reference publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/switch/command/reference/fswtch_r.html
26-5
Chapter 26 Displaying Hardware Layer 3 Switching Statistics
Displaying Hardware Layer 3 Switching Statistics

Hardware Layer 3 switching statistics are obtained on a per-VLAN basis. To display hardware Layer 3 switching statistics, perform this task: Command
Router# show interfaces {{type {port-channel number}}
1
Purpose
slot/port} |
Displays hardware Layer 3 switching statistics.
This example shows how to display hardware Layer 3 switching statistics:

Router# show interfaces gigabitethernet 9/5 | include Switched L2 Switched: ucast: 8199 pkt, 1362060 bytes - mcast: 6980 pkt, 371952 bytes L3 in Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes mcast L3 out Switched: ucast: 0 pkt, 0 bytes - mcast: 0 pkt, 0 bytes
To display adjacency table information, perform this task: Command

Router# show adjacency [{{type slot/port} | {port-channel number}} | detail | internal | summary]
1
Purpose Displays adjacency table information. The optional detail keyword displays detailed adjacency information, including Layer 2 information.
This example shows how to display adjacency statistics:

Router# show adjacency gigabitethernet 9/5 detail Protocol Interface Address IP GigabitEthernet9/5 172.20.53.206(11) 504 packets, 6110 bytes 00605C865B82 000164F83FA50800 ARP 03:49:31
Note
Adjacency statistics are updated approximately every 60 seconds.
Tip
26-6
OL-3999-08
C H A P T E R
27
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching

With Release 12.2(18)SXE and later releases, the PFC3 and DFC3 provide hardware support for IPv6 multicast traffic. Use these publications to configure IPv6 multicast on Catalyst 6500 series switches:
The Cisco IOS IPv6 Configuration Library, Implementing IPv6 Multicast: http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/configuration/12-2sx/ipv6-12-2sx-book.html The Cisco IOS IPv6 Command Reference: http://www.cisco.com/en/US/docs/ios/ipv6/command/reference/ipv6_book.html
These sections provide additional information about IPv6 multicast support on Catalyst 6500 series switches:

Features that Support IPv6 Multicast, page 27-2 IPv6 Multicast Guidelines and Restrictions, page 27-2 New or Changed IPv6 Multicast Commands, page 27-3 Configuring IPv6 Multicast Layer 3 Switching, page 27-3 Using show Commands to Verify IPv6 Multicast Layer 3 Switching, page 27-3
Tip
27-1
Chapter 27 Features that Support IPv6 Multicast
Features that Support IPv6 Multicast

These features support IPv6 multicast:

RPR and RPR+ redundancy modeSee Chapter 8, Configuring RPR and RPR+ Supervisor Engine Redundancy. Multicast Listener Discovery version 2 (MLDv2) snoopingSee Chapter 29, Configuring MLDv2 Snooping for IPv6 Multicast Traffic.
Note
MLDv1 snooping is not supported.
IPv6 Multicast rate limitersSee Chapter 36, Configuring Denial of Service Protection. IPv6 Multicast: Bootstrap Router (BSR)See the BSR information in the Cisco IOS IPv6 Configuration Library and Cisco IOS IPv6 Command Reference. IPv6 Access ServicesSee DHCPv6 Prefix DelegationSee this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/config_library/15-sy/ipv6-15-sy-library.html SSM mapping for IPv6See this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/config_library/15-sy/ipv6-15-sy-library.html
IPv6 Multicast Guidelines and Restrictions

These guidelines and restrictions apply to IPv6 multicast support on Catalyst 6500 series switches:
With Release 12.2(18)SXE and later releases, the PFC3 and DFC3 provide hardware support for the following:
Completely switched IPv6 multicast flows IPv6 PIM-Sparse Mode (PIM-SM) (S,G) forwarding Multicast RPF check for IPv6 PIM-SM (S,G) traffic using the NetFlow table Rate limiting of IPv6 PIM-SM (S,G) traffic that fails the multicast RPF check Static IPv6 multicast routes SSM Mapping for IPv6 (PIM-SSM) IPv6 multicast forwarding information base (MFIB) using the NetFlow table IPv6 distributed MFIB (dMFIB) using the NetFlow table Link-local and link-global IPv6 multicast scopes Egress multicast replication with the ipv6 mfib hardware-switching command Ingress interface statistics for multicast routes (egress interface statistics not available) RPR and RPR+ redundancy mode (see Chapter 8, Configuring RPR and RPR+
Supervisor Engine Redundancy)

Ingress and egress PFC QoS (see Chapter 41, Configuring PFC QoS) Input and output Cisco access-control lists (ACLs)
27-2
OL-3999-08
Chapter 27
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching New or Changed IPv6 Multicast Commands
The PFC3 and DFC3 do not provide hardware support for the following:
Partially switched IPv6 multicast flows PIM-SM (*,G) forwarding Multicast RPF check for PIM-SM (*,G) traffic Multicast helper maps Site-local multicast scopes Manually configured IPv6 over IPv4 tunnels IPv6 multicast 6to4 tunnels IPv6 multicast automatic tunnels IPv6 over GRE tunnels IPv6-in-IPv6 PIM register tunnels IPv6 multicast basic ISATAP tunnels ISATAP tunnels with embedded 6to4 tunnels
New or Changed IPv6 Multicast Commands

Refer to the Cisco IOS Master Command List, Release 12.2SX for information about these IPv6 multicast commands, which are new or changed in Release 12.2(18)SXE:

ipv6 mfib hardware-switching mls rate-limit multicast ipv6 (see Chapter 36, Configuring Denial of Service Protection) show ipv6 mfib show mls rate-limit (see Chapter 36, Configuring Denial of Service Protection) show platform software ipv6-multicast show tcam interface
Configuring IPv6 Multicast Layer 3 Switching

To configure IPv6 multicast Layer 3 switching, perform this task: Command
Router(config)# ipv6 unicast-routing Router(config)# ipv6 multicast-routing Router(config)# ipv6 mfib hardware-switching
Purpose Enables unicast routing on all Layer 3 interfaces. Enables PIM-SM on all Layer 3 interfaces. Enables MFIB hardware switching globally.
Using show Commands to Verify IPv6 Multicast Layer 3 Switching

These sections describe how to use show commands to verify IPv6 multicast Layer 3 switching:
Verifying MFIB Clients, page 27-4
27-3
Chapter 27 Using show Commands to Verify IPv6 Multicast Layer 3 Switching
Displaying the Switching Capability, page 27-5 Verifying the (S,G) Forwarding Capability, page 27-5 Verifying the (*,G) Forwarding Capability, page 27-5 Verifying the Subnet Entry Support Status, page 27-5 Verifying the Current Replication Mode, page 27-5 Displaying the Replication Mode Auto Detection Status, page 27-6 Displaying the Replication Mode Capabilities, page 27-6 Displaying Subnet Entries, page 27-6 Displaying the IPv6 Multicast Summary, page 27-6 Displaying the NetFlow Hardware Forwarding Count, page 27-7 Displaying the FIB Hardware Bridging and Drop Counts, page 27-7 Displaying the Shared and Well-Known Hardware Adjacency Counters, page 27-8
Note
The show commands in the following sections are for a switch with a DFC3-equipped switching module in slot 1 and a Supervisor Engine 720 with a PFC3 in slot 6.
Verifying MFIB Clients

This example shows the complete output of the show ipv6 mrib client command:
Router# show ipv6 mrib client IP MRIB client-connections mfib ipv6:81 (connection id 0) igmp:124 (connection id 1) pim:281 (connection id 2) slot 1 mfib ipv6 rp agent:15 (connection id 3) slot 6 mfib ipv6 rp agent:15 (connection id 4)
This example shows how to display the MFIB client running on the MSFC:
Router# show ipv6 mrib client | include ^mfib ipv6 mfib ipv6:81 (connection id 0)
This example shows how to display the MFIB clients running on the PFC3 and any DFC3s:
Router# show ipv6 mrib client | include slot slot 1 mfib ipv6 rp agent:15 (connection id 3) slot 6 mfib ipv6 rp agent:15 (connection id 4)
27-4
OL-3999-08
Chapter 27
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching Using show Commands to Verify IPv6 Multicast Layer 3 Switching
Displaying the Switching Capability

This example displays the complete output of the show platform software ipv6-multicast capability command:
Router# show platform software ipv6-multicast capability Hardware switching for IPv6 is enabled (S,G) forwarding for IPv6 supported using Netflow (*,G) bridging for IPv6 is supported using FIB Directly-connected entries for IPv6 is supported using ACL-TCAM. Current System HW Replication Mode : Ingress Auto-detection of Replication Mode : ON Slot 1 2 6 8 Replication-Capability Ingress Egress Egress Ingress Replication-Mode Ingress Ingress Ingress Ingress
Verifying the (S,G) Forwarding Capability

This example shows how to verify the (S,G) forwarding:
Router# show platform software ipv6-multicast capability | include (S,G) (S,G) forwarding for IPv6 supported using Netflow
Verifying the (*,G) Forwarding Capability

This example shows how to verify the (*,G) forwarding:
Router# show platform software ipv6-multicast capability | include (\*,G) (*,G) bridging for IPv6 is supported using FIB
Verifying the Subnet Entry Support Status

This example shows how to verify the subnet entry support status:
Router# show platform software ipv6-multicast capability | include entries Directly-connected entries for IPv6 is supported using ACL-TCAM.
Verifying the Current Replication Mode

This example shows how to verify the current replication mode:
Router# show platform software ipv6-multicast capability | include Current Current System HW Replication Mode : Ingress
Note
Enter the no ipv6 mfib hardware-switching replication-mode ingress command to enable replication mode auto detection.
27-5
Displaying the Replication Mode Auto Detection Status

This example shows how to display the replication mode auto detection status:
Router# show platform software ipv6-multicast capability | include detection Auto-detection of Replication Mode : ON
Displaying the Replication Mode Capabilities

This example shows how to display the replication mode capabilities of the installed modules:
Router# show platform software ipv6-multicast capability | begin ^Slot Slot Replication-Capability Replication-Mode 1 Ingress Ingress 2 Egress Ingress 6 Egress Ingress 8 Ingress Ingress
Displaying Subnet Entries

This example shows how to display subnet entries:
Router# show platform software ipv6-multicast connected IPv6 Multicast Subnet entries Flags : H - Installed in ACL-TCAM X - Not installed in ACL-TCAM due to label-full exception Interface: Vlan20 [ H ] S:20::1 G:FF00:: Interface: Vlan10 [ H ] S:10::1 G:FF00::
Note
In this example, there are subnet entries for VLAN 10 and VLAN 20.
Displaying the IPv6 Multicast Summary

This example shows how to display the IPv6 multicast summary:
Router# show platform software ipv6-multicast summary IPv6 Multicast Netflow SC summary on Slot[1]: Shortcut Type Shortcut count ---------------------------+-------------(S, G) 100 (*, G) 0 IPv6 Multicast FIB SC summary on Slot[1]: Shortcut Type Shortcut count ---------------------------+-------------(*, G/128) 10 (*, G/m) 47 IPv6 Multicast Netflow SC summary on Slot[6]: Shortcut Type Shortcut count ---------------------------+-------------(S, G) 100 (*, G) 0
27-6
OL-3999-08
Chapter 27
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching Using show Commands to Verify IPv6 Multicast Layer 3 Switching
IPv6 Multicast FIB SC summary on Slot[6]: Shortcut Type Shortcut count ---------------------------+-------------(*, G/128) 10 (*, G/m) 47
Displaying the NetFlow Hardware Forwarding Count

This example shows how to display the NetFlow hardware forwarding count:
Router# show platform software ipv6-multicast summary IPv6 Multicast Netflow SC summary on Slot[1]: Shortcut Type Shortcut count ---------------------------+-------------(S, G) 100 (*, G) 0 <...Output deleted...> IPv6 Multicast Netflow SC summary on Slot[6]: Shortcut Type Shortcut count ---------------------------+-------------(S, G) 100 (*, G) 0 <...Output truncated...>
Note
The NetFlow (*, G) count is always zero because PIM-SM (*,G) forwarding is supported in software on the MSFC3.
Displaying the FIB Hardware Bridging and Drop Counts

This example shows how to display the FIB hardware bridging and drop hardware counts:
Router# show platform software ipv6-multicast summary | begin FIB IPv6 Multicast FIB SC summary on Slot[1]: Shortcut Type Shortcut count ---------------------------+-------------(*, G/128) 10 (*, G/m) 47 <...Output deleted...> IPv6 Multicast FIB SC summary on Slot[6]: Shortcut Type Shortcut count ---------------------------+-------------(*, G/128) 10 (*, G/m) 47
Note
The (*, G/128) value is a hardware bridge entry count. The (*, G/m) value is a hardware bridge/drop entry count.
27-7
Displaying the Shared and Well-Known Hardware Adjacency Counters

The show platform software ipv6-multicast shared-adjacencies command displays the shared and well-known hardware adjacency counters used for IPv6 multicast by entries in FIB and ACL-TCAM.
Router# show platform software ipv6-multicast shared-adjacencies ---- SLOT [1] ---Shared IPv6 Mcast Adjacencies ----------------------------Subnet bridge adjacency Control bridge adjacency StarG_M bridge adjacency S_G bridge adjacency Default drop adjacency StarG (spt == INF) adjacency StarG (spt != INF) adjacency ---- SLOT [6] ---Shared IPv6 Mcast Adjacencies ----------------------------Subnet bridge adjacency Control bridge adjacency StarG_M bridge adjacency S_G bridge adjacency Default drop adjacency StarG (spt == INF) adjacency StarG (spt != INF) adjacency Index Packets Bytes ------ ------------- -----------------0x7F802 0 0 0x7 0 0 0x8 0 0 0x9 0 0 0xA 28237 3146058 0xB 0 0 0xC 0 0 Index Packets Bytes ------ ------------- -----------------0x7F802 0 0 0x7 0 0 0x8 0 0 0x9 0 0 0xA 0 0 0xB 0 0 0xC 0 0
Tip
27-8
OL-3999-08
C H A P T E R
28

This chapter describes how to configure IPv4 multicast Layer 3 switching on the Catalyst 6500 series switches.
Note

Understanding How IPv4 Multicast Layer 3 Switching Works, page 28-2 Understanding How IPv4 Bidirectional PIM Works, page 28-7 Default IPv4 Multicast Layer 3 Switching Configuration, page 28-7 IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions, page 28-8 Configuring IPv4 Multicast Layer 3 Switching, page 28-9 Configuring IPv4 Bidirectional PIM, page 28-23
Tip
28-1
Chapter 28 Understanding How IPv4 Multicast Layer 3 Switching Works
Understanding How IPv4 Multicast Layer 3 Switching Works

These sections describe how IPv4 multicast Layer 3 switching works:

IPv4 Multicast Layer 3 Switching Overview, page 28-2 Multicast Layer 3 Switching Cache, page 28-2 Layer 3-Switched Multicast Packet Rewrite, page 28-3 Partially and Completely Switched Flows, page 28-4 Non-RPF Traffic Processing, page 28-5 Multicast Boundary, page 28-7 Understanding How IPv4 Bidirectional PIM Works, page 28-7
IPv4 Multicast Layer 3 Switching Overview

The Policy Feature Card (PFC) provides Layer 3 switching for IP multicast flows using the hardware replication table and hardware Cisco Express Forwarding (CEF), which uses the forwarding information base (FIB) and the adjacency table on the PFC. In systems with Distributed Forwarding Cards (DFCs), IP multicast flows are Layer 3 switched locally using Multicast Distributed Hardware Switching (MDHS). MDHS uses local hardware CEF and replication tables on each DFC to perform Layer 3 switching and rate limiting of reverse path forwarding (RPF) failures locally on each DFC-equipped switching module. The PFC and the DFCs support hardware switching of (*,G) state flows. The PFC and the DFCs support rate limiting of non-RPF traffic. Multicast Layer 3 switching forwards IP multicast data packet flows between IP subnets using advanced application-specific integrated circuit (ASIC) switching hardware, which offloads processor-intensive multicast forwarding and replication from network routers. Layer 3 flows that cannot be hardware switched are still forwarded in the software by routers. Protocol Independent Multicast (PIM) is used for route determination. The PFC and the DFCs all use the Layer 2 multicast forwarding table to determine on which ports Layer 2 multicast traffic should be forwarded (if any). The multicast forwarding table entries are populated in conjunction with Internet Group Management Protocol (IGMP) snooping (see Chapter 30, Configuring IGMP Snooping for IPv4 Multicast Traffic).
Multicast Layer 3 Switching Cache

This section describes how the PFC and the DFCs maintain Layer 3 switching information in hardware tables. The PFC and DFC populate the (S,G) or (*,G) flows in the hardware FIB table with the appropriate masks; for example, (S/32, G/32) and (*/0, G/32). The RPF interface and the adjacency pointer information is also stored in each entry. The adjacency table contains the rewrite and a pointer to the replication entries. If a flow matches a FIB entry, the RPF check compares the incoming interface/VLAN with the entry. A mismatch is an RPF failure, which can be rate limited if this feature is enabled. The MSFC updates its multicast routing table and forwards the new information to the PFC whenever it receives traffic for a new flow. In addition, if an entry in the multicast routing table on the MSFC ages out, the MSFC deletes the entry and forwards the updated information to the PFC. In systems with DFCs, flows are populated symmetrically on all DFCs and on the PFC.
28-2
OL-3999-08
Chapter 28
Configuring IPv4 Multicast Layer 3 Switching Understanding How IPv4 Multicast Layer 3 Switching Works
The Layer 3 switching cache contains flow information for all active Layer 3-switched flows. After the switching cache is populated, multicast packets identified as belonging to an existing flow can be Layer 3 switched based on the cache entry for that flow. For each cache entry, the PFC maintains a list of outgoing interfaces for the IP multicast group. From this list, the PFC determines onto which VLANs traffic from a given multicast flow should be replicated. These commands affect the Layer 3 switching cache entries:

When you clear the multicast routing table using the clear ip mroute command, all multicast Layer 3 switching cache entries are cleared. When you disable IP multicast routing on the MSFC using the no ip multicast-routing command, all multicast Layer 3 switching cache entries on the PFC are purged. When you disable multicast Layer 3 switching on an individual interface basis using the no mls ipmulticast command, flows that use this interface as the RPF interface are routed only by the MSFC in software.
Layer 3-Switched Multicast Packet Rewrite

When a multicast packet is Layer 3 switched from a multicast source to a destination multicast group, the PFC and the DFCs perform a packet rewrite that is based on information learned from the MSFC and stored in the adjacency table. For example, Server A sends a multicast packet addressed to IP multicast group G1. If there are members of group G1 on VLANs other than the source VLAN, the PFC must perform a packet rewrite when it replicates the traffic to the other VLANs (the switch also bridges the packet in the source VLAN). When the PFC receives the multicast packet, it is (conceptually) formatted as follows: Layer 2 Frame Header Destination Group G1 MAC
1
Layer 3 IP Header Source Source A MAC Destination Group G1 IP Source Source A IP TTL n Checksum calculation1
Data
FCS
1. In this example, Destination B is a member of Group G1.
The PFC rewrites the packet as follows:
Changes the source MAC address in the Layer 2 frame header from the MAC address of the host to the MAC address of the MSFC (This is the burned-in MAC address of the system. This MAC address will be the same for all outgoing interfaces and cannot be modified. This MAC address can be displayed using the show mls multicast statistics command.) Decrements the IP header Time to Live (TTL) by one and recalculates the IP header checksum
The result is a rewritten IP multicast packet that appears to have been routed. The PFC replicates the rewritten packet onto the appropriate destination VLANs, where it is forwarded to members of IP multicast group G1. After the PFC performs the packet rewrite, the packet is (conceptually) formatted as follows: Frame Header Destination Group G1 MAC Source MSFC MAC IP Header Destination Group G1 IP Source Source A IP TTL n1 Checksum calculation2 Data FCS
28-3
Partially and Completely Switched Flows

When at least one outgoing Layer 3 interface for a given flow is multilayer switched and at least one outgoing interface is not multilayer switched, that flow is considered partially switched. When a partially switched flow is created, all multicast traffic belonging to that flow still reaches the MSFC and is forwarded by software on those outgoing interfaces that are not multilayer switched. These sections describe partially and completely switched flow:

Partially Switched Flows, page 28-4 Completely Switched Flows, page 28-5
Partially Switched Flows

A flow might be partially switched instead of completely switched in these situations:

If the switch is configured as a member of the IP multicast group on the RPF interface of the multicast source (using the ip igmp join-group command). During the registering state, if the switch is the first-hop router to the source in PIM sparse mode (in this case, the switch must send PIM-register messages to the rendezvous point [RP]). If the multicast TTL threshold is configured on an outgoing interface for the flow (using the ip multicast ttl-threshold command). If the multicast helper is configured on the RPF interface for the flow, and multicast to broadcast translation is required. With a PFC2, if the outgoing interface is a generic routing encapsulation (GRE) tunnel interface. With a PFC3 and releases earlier than Release 12.2(18)SXE, if the outgoing interface is a generic routing encapsulation (GRE) tunnel interface. If the outgoing interface is a Distance Vector Multicast Routing Protocol (DVMRP) tunnel interface. If Network Address Translation (NAT) is configured on an interface and source address translation is required for the outgoing interface. Flows are partially switched if any of the outgoing interfaces for a given flow are not Layer 3 switched. (S,G) flows are partially switched if the (S,G) entry has the RPT-bit (R bit) set. (S,G) flows are partially switched if the (S,G) entry does not have the SPT bit (T flag) set and the Prune bit (P flag) set. (*,G) flows are partially switched on the last-hop leaf router if the shared-tree to shortest-path-tree (SPT) threshold is not equal to infinity. This allows the flow to transition from the SPT. (*,G) flows are partially switched if at least one (S,G) entry has the same RPF as a (*,g) entry but any of these is true:
The RPT flag (R bit) is not set. The SPT flag (T bit) is not set. The Prune-flag (P bit) is not set.
(S,G) flows are partially switched instead of completely switched in these situations:

(*,G) flows are partially switched instead of completely switched in these situations:

28-4
OL-3999-08
Chapter 28
Configuring IPv4 Multicast Layer 3 Switching Understanding How IPv4 Multicast Layer 3 Switching Works
(*,G) flows are partially switched if a DVMRP neighbor is detected on the input interface of a (*,G) entry. (*,G) flows are partially switched if the interface and mask entry is not installed for the RPF-interface of a (*,G) entry and the RPF interface is not a point-to-point interface. In PFC2 systems, (*,G) flows will be partially switched on the last-hop leaf router if the shared-tree to shortest-path-tree (SPT) threshold is not equal to infinity. This allows the flow to transition from SPT.
Note
With a PFC2, flows matching an output ACL on an outgoing interface are routed in software.
Completely Switched Flows

When all the outgoing interfaces for a given flow are Layer 3 switched, and none of the above situations apply to the flow, that flow is considered completely switched. When a completely switched flow is created, the PFC prevents multicast traffic bridged on the source VLAN for that flow from reaching the MSFC interface in that VLAN, freeing the MSFC of the forwarding and replication load for that flow. One consequence of a completely switched flow is that multicast statistics on a per-packet basis for that flow cannot be recorded. Therefore, the PFC periodically sends multicast packet and byte count statistics for all completely switched flows to the MSFC. The MSFC updates the corresponding multicast routing table entry and resets the expiration timer for that multicast route.
Note
A (*,G) state is created on the PIM-RP or for PIM-dense mode but is not used for forwarding the flows, and Layer 3 switching entries are not created for these flows.
Non-RPF Traffic Processing

These sections describe non-RPF traffic processing:

Non-RPF Traffic Overview, page 28-5 Filtering of RPF Failures for Stub Networks, page 28-6 Rate Limiting of RPF Failure Traffic, page 28-6
Non-RPF Traffic Overview

In a redundant configuration where multiple routers connect to the same LAN segment, only one router forwards the multicast traffic from the source to the receivers on the outgoing interfaces (see Figure 28-1). In this kind of topology, only the PIM designated router (PIM DR) forwards the data in the common VLAN, but the non-PIM DR receives the forwarded multicast traffic. The redundant router (non-PIM DR) must drop this traffic because it has arrived on the wrong interface and fails the RPF check. Traffic that fails the RPF check is called non-RPF traffic. The Catalyst 6500 series switch processes non-RPF traffic in hardware on the PFC by filtering (dropping) or rate limiting the non-RPF traffic.
28-5
Figure 28-1 Redundant Multicast Router Configuration in a Stub Network
Rest of network
Router A Network A, B, C.0 Network A, B, D.0 Mulitcast traffic non-RPF traffic
Router B
Filtering of RPF Failures for Stub Networks

The PFC and the DFCs support ACL-based filtering of RPF failures for sparse mode stub networks. When you enable the ACL-based method of filtering RPF failures by entering the mls ip multicast stub command on the redundant router, the following ACLs automatically download to the PFC and are applied to the interface you specify:
access-list access-list access-list access-list access-list 100 100 100 100 100 permit ip A.B.C.0 0.0.0.255 any permit ip A.B.D.0 0.0.0.255 any permit ip any 224.0.0.0 0.0.0.255 permit ip any 224.0.1.0 0.0.0.255 deny ip any 224.0.0.0 15.255.255.255
The ACLs filter RPF failures and drop them in hardware so that they are not forwarded to the router. Use the ACL-based method of filtering RPF failures only in sparse mode stub networks where there are no downstream routers. For dense mode groups, RPF failure packets have to be seen on the router for the PIM assert mechanism to function properly. Use CEF-based or NetFlow-based rate limiting to limit the rate of RPF failures in dense mode networks and sparse mode transit networks. For information on configuring ACL-based filtering of RPF failures, see the Configuring ACL-Based Filtering of RPF Failures section on page 28-17.
Rate Limiting of RPF Failure Traffic

When you enable rate limiting of packets that fail the RPF check (non-RPF packets), most non-RPF packets are dropped in hardware. According to the multicast protocol specification, the router needs to receive the non-RPF packets for the PIM assert mechanism to function properly, so all non-RPF packets cannot be dropped in hardware. When a non-RPF packet is received, a NetFlow entry is created for each non-RPF flow. When the first non-RPF packet arrives, the PFC bridges the packet to the MSFC and to any bridged ports and creates a NetFlow entry that contains source, group, and ingress interface information, after which the NetFlow entry handles all packets for that source and group, sending packets only to bridged ports and not to the MSFC. To support the PIM assert mechanism, the PFC periodically forwards a percentage of the non-RPF flow packets to the MSFC.
28-6
55645
OL-3999-08
Chapter 28
Configuring IPv4 Multicast Layer 3 Switching Understanding How IPv4 Bidirectional PIM Works
The first packets for directly connected sources in PIM sparse mode are also rate-limited and are processed by the CPU. Rate limiting of RPF failures is disabled by default.
Multicast Boundary
The multicast boundary feature allows you to configure an administrative boundary for multicast group addresses. By restricting the flow of multicast data packets, you can reuse the same multicast group address in different administrative domains. You configure the multicast boundary on an interface. A multicast data packet is blocked from flowing across the interface if the packets multicast group address matches the access control list (ACL) associated with the multicast boundary feature. Multicast boundary ACLs can be processed in hardware by the Policy Feature Card (PFC), a Distributed Forwarding Card (DFC), or in software by the Multilayer Switch Feature Card (MSFC). The multicast boundary ACLs are programmed to match the destination address of the packet. These ACLs are applied to traffic on the interface in both directions (input and output). To support multicast boundary ACLs in hardware, the switch creates new ACL TCAM entries or modifies existing ACL TCAM entries (if other ACL-based features are active on the interface). To verify TCAM resource utilization, enter the show tcam counts ip command. If you configure the filter-autorp keyword, the administrative boundary also examines auto-RP discovery and announcement messages and removes any auto-RP group range announcements from the auto-RP packets that are denied by the boundary ACL.
Understanding How IPv4 Bidirectional PIM Works

The PFC3 supports hardware forwarding of IPv4 bidirectional PIM groups. To support IPv4 bidirectional PIM groups, the PFC3 implements a new mode called designated forwarder (DF) mode. The designated forwarder is the router elected to forward packets to and from a segment for a IPv4 bidirectional PIM group. In DF mode, the supervisor engine accepts packets from the RPF and from the DF interfaces. When the supervisor engine is forwarding IPv4 bidirectional PIM groups, the RPF interface is always included in the outgoing interface list of (*,G) entry, and the DF interfaces are included depending on IGMP/PIM joins. If the route to the RP becomes unavailable, the group is changed to dense mode. Should the RPF link to the RP become unavailable, the IPv4 bidirectional PIM flow is removed from the hardware FIB. For information on configuring IPv4 bidirectional PIM, see the Configuring IPv4 Bidirectional PIM section on page 28-23.
Default IPv4 Multicast Layer 3 Switching Configuration

Table 28-1 shows the default IP multicast Layer 3 switching configuration.
28-7
Chapter 28 IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions
Table 28-1 Default IP Multicast Layer 3 Switching Configuration
Feature ACL for stub networks Installing of directly connected subnet entries Multicast routing PIM routing IP multicast Layer 3 switching Shortcut consistency checking
Default Value Disabled on all interfaces Enabled globally Disabled globally Disabled on all interfaces Enabled when multicast routing is enabled and PIM is enabled on the interface Enabled
Internet Group Management Protocol (IGMP) snooping is enabled by default on all VLAN interfaces. If you disable IGMP snooping on an interface, multicast Layer 3 flows are still switched by the hardware. Bridging of the flow on an interface with IGMP snooping disabled causes flooding to all forwarding interfaces of the VLAN. For details on configuring IGMP snooping, see Chapter 30, Configuring IGMP Snooping for IPv4 Multicast Traffic.
IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions

These sections describe IP Multicast Layer 3 switching configuration restrictions:

Restrictions, page 28-8 Unsupported Features, page 28-9
Restrictions
IP multicast Layer 3 switching is not provided for an IP multicast flow in the following situations:
For IP multicast groups that fall into the range 224.0.0.* (where * is in the range 0 to 255), which is used by routing protocols. Layer 3 switching is supported for groups 224.0.2.* to 239.*.*.*.
Note
Groups in the 224.0.0.* range are reserved for routing control packets and must be flooded to all forwarding ports of the VLAN. These addresses map to the multicast MAC address range 01-00-5E-00-00-xx, where xx is in the range 00xFF.
For PIM auto-RP multicast groups (IP multicast group addresses 224.0.1.39 and 224.0.1.40). For packets with IP options. However, packets in the flow that do not specify IP options are hardware switched. For source traffic received on tunnel interfaces (such as MBONE traffic). If a (S,G) entry for sparse mode does not have the SPT-bit, RPT-bit, or Pruned flag set. A (*,G) entry is not hardware switched if at least one (S,G) entry has an RPF different from the (*,G) entrys RPF and the (S,G) is not hardware switched.
28-8
OL-3999-08
Chapter 28
Configuring IPv4 Multicast Layer 3 Switching Configuring IPv4 Multicast Layer 3 Switching
If the ingress interface of a (S,G) or (*,G) entry is null, except if the (*,G) entry is a IPv4 bidirectional PIM entry and the switch is the RP for the group. For IPv4 bidirectional PIM entries when a DF interface or RPF interface is a tunnel. With a PFC2, NAT translations for multicast packets is handled in software. With a PFC2, GRE tunnel encapsulation and de-encapsulation for multicast packets is handled in software. With a PFC3 and releases earlier than Release 12.2(18)SXE, GRE tunnel encapsulation and de-encapsulation for multicast packets is handled in software. Supervisor Engine 32 does not support egress multicast replication and cannot detect the multicast replication mode.
Unsupported Features
If you enable IP multicast Layer 3 switching, IP accounting for Layer 3 interfaces does not report accurate values. The show ip accounting command is not supported.

These sections describe how to configure IP multicast Layer 3 switching:

Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD, page 28-10 Enabling IPv4 Multicast Routing Globally, page 28-10 Enabling IPv4 PIM on Layer 3 Interfaces, page 28-10 Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces, page 28-11 Configuring the Replication Mode, page 28-12 Enabling Local Egress Replication, page 28-14 Configuring the Layer 3 Switching Global Threshold, page 28-15 Enabling Installation of Directly Connected Subnets, page 28-15 Specifying the Flow Statistics Message Interval, page 28-16 Configuring IPv4 Bidirectional PIM, page 28-23 Setting the IPv4 Bidirectional PIM Scan Interval, page 28-24 Enabling Shortcut-Consistency Checking, page 28-16 Configuring ACL-Based Filtering of RPF Failures, page 28-17 Displaying RPF Failure Rate-Limiting Information, page 28-17 Configuring Multicast Boundary, page 28-18 Displaying IPv4 Multicast Layer 3 Hardware Switching Summary, page 28-18 Displaying the IPv4 Multicast Routing Table, page 28-21 Displaying IPv4 Multicast Layer 3 Switching Statistics, page 28-22 Displaying IPv4 Bidirectional PIM Information, page 28-25 Using IPv4 Debug Commands, page 28-27
28-9
Chapter 28 Configuring IPv4 Multicast Layer 3 Switching
Clearing IPv4 Multicast Layer 3 Switching Statistics, page 28-27 Redundancy for Multicast Traffic, page 28-28
Note
When you are in configuration mode you can enter EXEC mode commands by entering the do keyword before the EXEC mode command.
Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD

For complete information and procedures about source-specific multicast with IGMPv3, IGMP v3lite, and URL Rendezvous Directory (URD), refer to this URL: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfssm.html
Enabling IPv4 Multicast Routing Globally

You must enable IP multicast routing globally before you can enable IP multicast Layer 3 switching on Layer 3 interfaces. For complete information and procedures, refer to these publications:
Cisco IOS IP and IP Routing Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/fipr_c.html
Cisco IOS IP and IP Routing Command Reference , Release 12.1, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/ipaddr/command/reference/fipras_r.html
To enable IP multicast routing globally, perform this task: Command

Router(config)# ip multicast-routing Router(config)# no ip multicast-routing
Purpose Enables IP multicast routing globally. Disables IP multicast routing globally.
This example shows how to enable multicast routing globally:

Router(config)# ip multicast-routing Router(config)#
Enabling IPv4 PIM on Layer 3 Interfaces

You must enable PIM on the Layer 3 interfaces before IP multicast Layer 3 switching functions on those interfaces.
28-10
OL-3999-08
Chapter 28
To enable IP PIM on a Layer 3 interface, perform this task: Command

Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port}} Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode} Router(config-if)# no ip pim [dense-mode | sparse-mode | sparse-dense-mode] 1.
Purpose Selects an interface to configure. Enables IP PIM on a Layer 3 interface. Disables IP PIM on a Layer 3 interface.
This example shows how to enable PIM on an interface using the default mode (sparse-dense-mode):
Router(config-if)# ip pim Router(config-if)#
This example shows how to enable PIM sparse mode on an interface:

Router(config-if)# ip pim sparse-mode Router(config-if)#
Enabling IP Multicast Layer 3 Switching Globally

To enable hardware switching of multicast routes globally on your system, perform this task: Command
Step 1 Step 2
Router(config)# mls ip multicast Router# show mls ip multicast
Purpose Globally enables hardware switching of multicast routes. Displays MLS IP multicast configuration.
This example shows how to globally enable hardware switching of multicast routes:
Router(config)# mls ip multicast Router(config)#
Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces

IP multicast Layer 3 switching is enabled by default on the Layer 3 interface when you enable PIM on the interface. Perform this task only if you disabled IP multicast Layer 3 switching on the interface and you want to reenable it. PIM can be enabled on any Layer 3 interface, including VLAN interfaces.
Note
You must enable PIM on all participating Layer 3 interfaces before IP multicast Layer 3 switching will function. For information on configuring PIM on Layer 3 interfaces, see the Enabling IPv4 PIM on Layer 3 Interfaces section on page 28-10.
28-11
To enable IP multicast Layer 3 switching on a Layer 3 interface, perform this task: Command
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port}} Router(config-if)# mls ip multicast
Purpose Selects an interface to configure. Enables IP multicast Layer 3 switching on a Layer 3 interface. Disables IP multicast Layer 3 switching on a Layer 3 interface.
Router(config-if)# no mls ip multicast
1.
This example shows how to enable IP multicast Layer 3 switching on a Layer 3 interface:
Router(config-if)# mls ip multicast Router(config-if)#
Configuring the Replication Mode

Note
Supervisor Engine 32 and Supervisor Engine 2 support only ingress replication mode. With a Supervisor Engine 720, Release 12.2(18)SXF and later releases support the egress keyword. Support for the egress keyword is called Multicast Enhancement - Replication Mode Detection in the release notes and Feature Navigator. By default, a Supervisor Engine 720 automatically detects the replication mode based on the module types installed in the system. If all modules are capable of egress replication, the system uses egress-replication mode. If the supervisor engine detects modules that are not capable of egress replication, the replication mode automatically changes to ingress replication. You can override this action by entering the mls ip multicast replication-mode egress command so that the system continues to work in egress-replication mode even if there are fabric-enabled modules installed that do not support egress replication (for example, OSMs). You can also configure the system to operate only in ingress-replication mode. If the system is functioning in automatic detection mode, and you install a module that cannot perform egress replication, the following occurs:

The system reverts to ingress mode A system log is generated
If the system is functioning in forced egress mode, a system log is created that will display the presence of modules that are not capable of egress replication mode.
Note
If you configure forced egress mode in a system that has fabric-enabled modules that are not capable of egress replication, you must make sure that these modules are not sourcing or receiving multicast traffic.
28-12
OL-3999-08
Chapter 28
Note
Egress mode is not compatible with QoS or SPAN. When QoS is configured, egress replication can result in the incorrect COS or DSCP marking of packets. When SPAN is configured, egress replication can result in multicast packets not being sent to the SPAN destination port. If you are using QoS or SPAN and your switching modules are capable of egress replication, enter the mls ip multicast replication-mode ingress command to force ingress replication. During a change from egress- to ingress-replication mode, traffic interruptions may occur because the shortcuts will be purged and reinstalled. To avoid interruptions in traffic forwarding, enter the mls ip multicast replication-mode ingress command in global configuration mode. This command forces the system to operate in ingress-replication mode. The no form of the mls ip multicast replication-mode ingress command restores the system to automatic detection mode. To enable IP multicast Layer 3 switching, perform this task:
Command
Step 1
Router(config)# mls ip multicast replication-mode [egress | ingress]
Purpose Specifies the replication mode.

Note
Release 12.2(18)SXF and later releases support the egress keyword.
Step 2 Step 3
Router# show mls ip multicast capability Router# show mls ip multicast summary
Displays the configured replication mode. Displays the replication mode and if automatic detection is enabled or disabled.
This example shows how to enable the replication mode:

Router (config)# mls ip multicast replication-mode egress Router# show mlp ip multicast capability Current mode of replication is Ingress Configured replication mode is Egress Slot 2 3 4 5 6 Multicast replication capability Egress Egress Ingress Egress Egress
Router# show mls ip multicast summary 4 MMLS entries using 656 bytes of memory Number of partial hardware-switched flows:2 Number of complete hardware-switched flows:2 Directly connected subnet entry install is enabled Current mode of replication is Ingress Auto-detection of replication mode is enabled Consistency checker is enabled Router (config)#
28-13
Enabling Local Egress Replication

Note
Supervisor Engine 32 and Supervisor Engine 2 support only ingress replication mode. With a Supervisor Engine 720, Release 12.2(18)SXF and later releases allow you to unconditionally enable local egress replication. This feature is called Multicast enhancement - egress replication performance improvement in the release notes and Feature Navigator. DFC-equipped modules with dual switch-fabric connections host two packet replication engines, one per fabric connection. Each replication engine is responsible for forwarding packets to and from the interfaces associated with the switch-fabric connections. The interfaces that are associated with a switch-fabric connection are considered to be local from the perspective of the packet replication engine. With Release 12.2(18)SXF and later releases, you can prevent redundant replication of multicast packets across the switch-fabric connection by entering a command that instructs the two replication engines on these modules to forward packets only to local interfaces which are associated with the switch-fabric connection that the replication engine supports. When you enable this feature, the multicast expansion table (MET) for each replication engine is populated with the local Layer 3 interfaces only. This action prevents replication for interfaces that are not supported by the replication engine (nonlocal interfaces) and increases replication performance. Local egress replication is supported with the following software configuration and hardware:

IPv4 egress replication mode Dual fabric-connection DFC-equipped modules Layer 3-routed interfaces and subinterfaces that are not part of a port channel Egress internal VLAN Partial-shortcut internal VLAN Internal VLAN for Multicast VPN Multicast Distribution Tree (MDT) tunnel Point-to-point tunnel internal VLAN QoS internal VLAN
The local egress replication feature is not supported for the following internal VLANs:

Note
The local egress replication feature is not supported with IPv6 multicast or in a system that has a mix of IPv4 and IPv6 multicast enabled. To enable local egress replication, perform this task:
Command
Step 1
Router(config)# mls ip multicast egress local
Purpose Enables local egress replication.

Note
This command requires a system reset for the configuration to take effect.
Step 2 Step 3
Router # reload Router# show mls ip multicast capability Router# show mls cef ip multicast detail
Reloads the system. Displays the configured replication mode.
28-14
OL-3999-08
Chapter 28
This example shows how to enable local egress replication:

Router (config)# mls ip multicast egress local Router (config)# exit Router # reload Router # show mls ip multicast capability Current mode of replication is Ingress Configured replication mode is Egress Egress Local is Enabled Slot Multicast replication capability Egress Local 2 Egress No 3 Egress Yes 4 Ingress No 5 Egress No 6 Egress No
Configuring the Layer 3 Switching Global Threshold

You can configure a global multicast rate threshold (specified in packets per second) below which all multicast traffic is routed by the MSFC. This configuration prevents creation of switching cache entries for low-rate Layer 3 flows.
Note
This command does not affect flows that are already being routed. To apply the threshold to existing routes, clear the route and let it reestablish. To configure the Layer 3 switching threshold, perform this task:
Command
Router(config)# mls ip multicast threshold ppsec Router(config)# no mls ip multicast threshold
Purpose Configures the IP MMLS threshold. Reverts to the default IP MMLS threshold.
This example shows how to configure the Layer 3 switching threshold to 10 packets per second:
Router(config)# mls ip multicast threshold 10 Router(config)#
Enabling Installation of Directly Connected Subnets

In PIM sparse mode, a first-hop router that is the designated router for the interface may need to encapsulate the source traffic in a PIM register message and unicast it to the rendezvous point. To prevent new sources for the group from being learned in the routing table, the (*,G) flows should remain as completely hardware-switched flows. When (subnet/mask, 224/4) entries are installed in the hardware, the FIB allows both (*,G) flows to remain completely hardware-switched flows, and new, directly connected sources to be learned correctly. The installation of directly connected subnets is enabled globally by default. One (subnet/mask, 224/4) is installed per PIM-enabled interface. To view FIB entries, enter the show mls ip multicast connected command. To enable installation of directly connected subnets, perform this task:
28-15
Command
Router(config)# mls ip multicast connected Router(config)# no mls ip multicast connected
Purpose Enables installation of directly connected subnets. Disables installation of directly connected subnets.
This example shows how to enable installation of directly connected subnets:

Router(config)# mls ip multicast connected Router(config)#
Specifying the Flow Statistics Message Interval

By default, the supervisor engine forwards flow statistics messages to the MSFC every 25 seconds. The messages are forwarded in batches, and each batch of messages contains statistics for 25 percent of all flows. If you leave the interval at the default of 25 seconds, it will take 100 seconds to forward statistics for all flows to the MSFC. To specify how often flow statistics messages forwarded from the supervisor engine to the MSFC, perform this task: Command
Router(config)# mls ip multicast flow-stat-timer num
Purpose Specifies how the supervisor engine forwards flow statistics messages to the MSFC. Restores the default.
Router(config)# no mls ip multicast flow-stat-timer num
This example shows how to configure the supervisor engine to forward flow statistics messages to the MSFC every 10 seconds:
Router(config)# mls ip multicast flow-stat-timer 10 Router(config)#
Enabling Shortcut-Consistency Checking

When you enable the shortcut-consistency checking feature, the multicast route table and the multicast-hardware entries are checked for consistency, and any inconsistencies are corrected. You can view inconsistencies by entering the show mls ip multicast consistency-check command. If consistency checking is enabled, the multicast route table will be scanned every two seconds and a full scan is completed within 4 minutes. To enable shortcut-consistency checking, perform this task: Command
Router(config)# mls ip multicast consistency-check Router(config)# no mls ip multicast consistency-check num
Purpose Enables shortcut-consistency checking. Restores the default.
28-16
OL-3999-08
Chapter 28
This example shows how to enable the hardware shortcut-consistency checker:

Router (config)# mls ip multicast consistency-check Router (config)#
Configuring ACL-Based Filtering of RPF Failures

When you configure ACL-based filtering of RPF failures, ACLs that filter RPF failures in hardware are downloaded to the hardware-based ACL engine and applied on the interface you specify. To enable ACL-based filtering of RPF failures on an interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} Router(config-if)# mls ip multicast stub
Purpose Selects an interface to configure. Enables ACL-based filtering of RPF failures on an interface. Disables ACL-based filtering of RPF failures on an interface.
Router(config-if)# no mls ip multicast stub
1.
Displaying RPF Failure Rate-Limiting Information

To display RPF failure rate-limiting information, perform this task: Command
Router# show mls ip multicast summary
Purpose Displays RPF failure rate-limiting information.
This example shows how to display RPF failure rate-limiting information:

Router# show mls ip multicast summary 10004 MMLS entries using 1280464 bytes of memory Number of partial hardware-switched flows:4 Number of complete hardware-switched flows:10000 Router#
28-17
Configuring Multicast Boundary

To configure a multicast boundary, perform this task: Command
Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} Router(config-if)# ip multicast boundary access_list [filter-autorp]
Purpose Selects an interface to configure. Enables an administratively scoped boundary on an interface.

For access_list, specify the access list that you have configured to filter the traffic at this boundary. (Optional) Specify filter-autorp to filter auto-RP messages at this boundary.
Router(config-if)# no ip multicast boundary 1.
Disables the multicast boundary for this interface.
Note
If you configure the filter-autorp keyword, the administrative boundary examines auto-RP discovery and announcement messages and removes any auto-RP group range announcements from the auto-RP packets that are denied by the boundary ACL. An auto-RP group range announcement is permitted and passed by the boundary only if all addresses in the auto-RP group range are permitted by the boundary ACL. If any address is not permitted, the entire group range is filtered and removed from the auto-RP message before the auto-RP message is forwarded.
The following example sets up a multicast boundary for all administratively scoped addresses:
Router Router Router Router (config)# access-list 1 deny 239.0.0.0 0.255.255.255 (config)# access-list 1 permit 224.0.0.0 15.255.255.255 (config)# interface gigabitethernet 5/2 (config-if)# ip multicast boundary 1
Displaying IPv4 Multicast Layer 3 Hardware Switching Summary

Note
The show interface statistics command does not display hardware-switched packets, only packets switched by software. The show ip pim interface count command displays the IP multicast Layer 3 switching enable state on IP PIM interfaces and the number of packets received and sent on the interface.
28-18
OL-3999-08
Chapter 28
To display IP multicast Layer 3 switching information for an IP PIM Layer 3 interface, perform one of these tasks: Command
Router# show ip pim interface [{{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}] count Router# show ip interface
Purpose Displays IP multicast Layer 3 switching enable state information for all MSFC IP PIM Layer 3 interfaces. Displays the IP multicast Layer 3 switching enable state on the Layer 3 interfaces.
These examples show how to display the IP PIM configuration of the interfaces:
Router# show ip pim interface count State:* - Fast Switched, D - Distributed Fast Switched H - Hardware Switching Enabled Address Interface FS Mpackets In/Out 10.15.1.20 GigabitEthernet4/8 * H 952/4237130770 10.20.1.7 GigabitEthernet4/9 * H 1385673757/34 10.25.1.7 GigabitEthernet4/10* H 0/34 10.11.1.30 FastEthernet6/26 * H 0/0 10.37.1.1 FastEthernet6/37 * H 0/0 1.22.33.44 FastEthernet6/47 * H 514/68
The * flag indicates that this interface can be fast switched and the H flag indicates that this interface is hardware switched. The In flag indicates the number of multicast packet bytes that have been received on the interface. The Out flag indicates the number of multicast packet bytes that have been forwarded from this interface.
Router# show ip mroute count IP Multicast Statistics 56 routes using 28552 bytes of memory 13 groups, 3.30 average sources per group Forwarding Counts:Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second Other counts:Total/RPF failed/Other drops(OIF-null, rate-limit etc) Group:224.2.136.89, Source count:1, Group pkt count:29051 Source:132.206.72.28/32, Forwarding:29051/-278/1186/0, Other:85724/8/56665 Router#
Note
The -tive counter means that the outgoing interface list of the corresponding entry is NULL, and this indicates that this flow is still active. This example shows how to display the IP multicast Layer 3 switching configuration of interface VLAN 10:
Router# show ip interface vlan 10 Vlan10 is up, line protocol is up Internet address is 10.0.0.6/8 Broadcast address is 255.255.255.255 Address determined by non-volatile memory MTU is 1500 bytes Helper address is not set Directed broadcast forwarding is disabled Multicast reserved groups joined: 224.0.0.1 224.0.0.2 224.0.0.13 224.0.0.10 Outgoing access list is not set Inbound access list is not set
28-19
Proxy ARP is enabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are never sent ICMP mask replies are never sent IP fast switching is enabled IP fast switching on the same interface is disabled IP Flow switching is disabled IP CEF switching is enabled IP Fast switching turbo vector IP Normal CEF switching turbo vector IP multicast fast switching is enabled IP multicast distributed fast switching is disabled IP route-cache flags are Fast, CEF Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Probe proxy name replies are disabled Policy routing is disabled Network address translation is disabled WCCP Redirect outbound is disabled WCCP Redirect exclude is disabled BGP Policy Mapping is disabled IP multicast multilayer switching is enabled IP mls switching is enabled Router#
This example shows how to display the IP multicast Layer 3 switching configuration of Gigabit Ethernet interface 1/2:
Router# show interfaces gigabitEthernet 1/2 GigabitEthernet1/2 is up, line protocol is up (connected) Hardware is C6k 1000Mb 802.3, address is 0001.c9db.2441 (bia 0001.c9db.2441) MTU 1500 bytes, BW 1000000 Kbit, DLY 10 usec, Last clearing of "show interface" counters 00:05:13 . Input queue: 0/2000/0/0 (size/max/drops/flushes); Total output drops: 0 Queueing strategy: fifo Output queue :0/40 (size/max) 5 minute input rate 10000 bits/sec, 1 packets/sec 5 minute output rate 0 bits/sec, 0 packets/sec 284 packets input, 113104 bytes, 0 no buffer Received 284 broadcasts (284 multicast) 0 runts, 41 giants, 0 throttles 41 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored 0 input packets with dribble condition detected 198 packets output, 14732 bytes, 0 underruns 0 output errors, 0 collisions, 0 interface resets 0 babbles, 0 late collision, 0 deferred 0 lost carrier, 0 no carrier 0 output buffer failures, 0 output buffers swapped out Router#
28-20
OL-3999-08
Chapter 28
Displaying the IPv4 Multicast Routing Table

The show ip mroute command displays the IP multicast routing table. To display the IP multicast routing table, perform this task: Command
Router# show ip mroute partical-sc [hostname | group_number]
Purpose Displays the IP multicast routing table and the hardware-switched interfaces.
This example shows how to display the IP multicast routing table:

Router# show ip mroute 230.13.13.1 IP Multicast Routing Table Flags:D - Dense, S - Sparse, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running A - Advertised via MSDP, U - URD, I - Received Source Specific Host Report Outgoing interface flags:H - Hardware switched Timers:Uptime/Expires Interface state:Interface, Next-Hop or VCD, State/Mode (*, 230.13.13.1), 00:16:41/00:00:00, RP 10.15.1.20, flags:SJC Incoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20 Outgoing interface list: GigabitEthernet4/9, Forward/Sparse-Dense, 00:16:41/00:00:00, H (*, 230.13.13.2), 00:16:41/00:00:00, RP 10.15.1.20, flags:SJC Incoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20, RPF-MFD Outgoing interface list: GigabitEthernet4/9, Forward/Sparse-Dense, 00:16:41/00:00:00, H (10.20.1.15, 230.13.13.1), 00:14:31/00:01:40, flags:CJT Incoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20, RPF-MFD Outgoing interface list: GigabitEthernet4/9, Forward/Sparse-Dense, 00:14:31/00:00:00, H (132.206.72.28, 224.2.136.89), 00:14:31/00:01:40, flags:CJT Incoming interface:GigabitEthernet4/8, RPF nbr 10.15.1.20, RPF-MFD Outgoing interface list:Null Router#
Note
The RPF-MFD flag indicates that the flow is completely switched by the hardware. The H flag indicates the flow is switched by the hardware on the outgoing interface.
28-21
Displaying IPv4 Multicast Layer 3 Switching Statistics

The show mls ip multicast command displays detailed information about IP multicast Layer 3 switching. To display detailed IP multicast Layer 3 switching information, perform one of these tasks: Command
Router# show mls ip multicast group ip_address [interface type slot/port | statistics] Router# show mls ip multicast interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} [statistics | summary] Router# show mls ip multicast source ip_address [interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} | statistics] Router# show mls ip multicast summary
Purpose Displays IP multicast Layer 3 switching group information. Displays IP multicast Layer 3 switching details for all interfaces. Displays IP multicast Layer 3 switching source information.
Displays a summary of IP multicast Layer 3 switching information. Displays IP multicast Layer 3 switching statistics.
Router# show mls ip multicast statistics 1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
This example shows how to display information on a specific IP multicast Layer 3 switching entry:
Router# show mls ip multicast group 10.1.0.11 Multicast hardware switched flows: Total shortcut installed: 0
This example shows how to display IP multicast group information:

Router# show mls ip multicast group 230.13.13.1 source 10.20.1.15 Multicast hardware switched flows: (10.20.1.15, 230.13.13.1) Incoming interface:Gi4/8, Packets switched:0 Hardware switched outgoing interfaces:Gi4/9 RPF-MFD installed Total hardware switched flows :1 Router#
This example shows how to display IP multicast Layer 3 switching information for VLAN 10:
Router# show mls ip multicast interface vlan 10 Multicast hardware switched flows: (10.1.0.15, 224.2.2.15) Incoming interface: Vlan10, Packets switched: 0 Hardware switched outgoing interfaces: MFD installed: Vlan10 (10.1.0.19, 224.2.2.19) Incoming interface: Vlan10, Packets switched: 1970 Hardware switched outgoing interfaces: MFD installed: Vlan10 (10.1.0.11, 224.2.2.11) Incoming interface: Vlan10, Packets switched: 0 Hardware switched outgoing interfaces: MFD installed: Vlan10 (10.1.0.10, 224.2.2.10) Incoming interface: Vlan10, Packets switched: 2744 Hardware switched outgoing interfaces: MFD installed: Vlan10
28-22
OL-3999-08
Chapter 28
Configuring IPv4 Multicast Layer 3 Switching Configuring IPv4 Bidirectional PIM
(10.1.0.17, 224.2.2.17) Incoming interface: Vlan10, Packets switched: 3340 Hardware switched outgoing interfaces: MFD installed: Vlan10 (10.1.0.13, 224.2.2.13) Incoming interface: Vlan10, Packets switched: 0 Hardware switched outgoing interfaces:
This example shows how to display the IP multicast Layer 3 switching statistics:
Router# show mls ip multicast statistics MLS Multicast Operation Status: MLS Multicast configuration and state: Router Mac: 00e0.b0ff.7b00, Router IP: 33.0.33.24 MLS multicast operating state: ACTIVE Shortcut Request Queue size 4 Maximum number of allowed outstanding messages: 1 Maximum size reached from feQ: 3096 Feature Notification sent: 1 Feature Notification Ack received: 1 Unsolicited Feature Notification received: 0 MSM sent: 205170 MSM ACK received: 205170 Delete notifications received: 0 Flow Statistics messages received: 35211 MLS Multicast statistics: Flow install Ack: 996508 Flow install Nack: 1 Flow update Ack: 1415959 Flow update Nack: 0 Flow delete Ack: 774953 Complete flow install Ack: 958469 Router#
Configuring IPv4 Bidirectional PIM

These sections describe how to configure IPv4 bidirectional protocol independent multicast (PIM):

Enabling IPv4 Bidirectional PIM Globally, page 28-23 Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups, page 28-24 Setting the IPv4 Bidirectional PIM Scan Interval, page 28-24 Displaying IPv4 Bidirectional PIM Information, page 28-25
Enabling IPv4 Bidirectional PIM Globally

To enable IPv4 bidirectional PIM, perform this task: Command
Router(config)# ip pim bidir-enable Router(config)# no ip pim bidir-enable
Purpose Enables IPv4 bidirectional PIM globally on the switch. Disables IPv4 bidirectional PIM globally on the switch.
This example shows how to enable IPv4 bidirectional PIM on the switch:
Router(config)# ip pim bidir-enable Router(config)#
28-23
Chapter 28 Configuring IPv4 Bidirectional PIM
Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups

To statically configure the rendezvous point for an IPv4 bidirectional PIM group, perform this task: Command
Step 1
Router(config)# ip pim rp-adress ip_address access_list [override]
Purpose Statically configures the IP address of the rendezvous point for the group. When you specify the override option, the static rendezvous point is used. Configures an access list. Configures the system to use auto-RP to configure groups for which the router will act as a rendezvous point (RP). Configures a standard IP access list. Enables MLS IP multicast.
Step 2 Step 3
Router(config)# access-list access-list permit | deny ip_address Router(config)# ip pim send-rp-announce type number scope ttl_value [group-list access-list] [interval seconds] [bidir] Router(config)# ip access-list standard access-list-name permit | deny ip_address Router(config)# mls ip multicast
Step 4 Step 5
This example shows how to configure a static rendezvous point for an IPv4 bidirectional PIM group:
Router(config)# Router(config)# Router(config)# Router(config)# ip pim rp-address 10.0.0.1 10 bidir override access-list 10 permit 224.1.0.0 0.0.255.255 ip pim send-rp-announce Loopback0 scope 16 group-list c21-rp-list-0 bidir ip access-list standard c21-rp-list-0 permit 230.31.31.1 0.0.255.255
Setting the IPv4 Bidirectional PIM Scan Interval

You can specify the interval between the IPv4 bidirectional PIM RP Reverse Path Forwarding (RPF) scans. To set the IPv4 bidirectional PIM RP RPF scan interval, perform this task: Command
Router(config)# mls ip multicast bidir gm-scan-interval interval
Purpose Specifies the IPv4 bidirectional PIM RP RPF scan interval; valid values are from 1 to 1000 seconds. The default is 10 seconds. Restores the default.
Router(config)# no mls ip multicast bidir gm-scan-interval
This example shows how to set the IPv4 bidirectional PIM RP RPF scan interval:
Router(config)# mls ip multicast bidir gm-scan-interval 30 Router(config)#
28-24
OL-3999-08
Chapter 28
Displaying IPv4 Bidirectional PIM Information

To display IPv4 bidirectional PIM information, perform one of these tasks: Command
Router# show ip pim rp mapping [in-use]
Purpose Displays mappings between PIM groups and rendezvous points and shows learned rendezvous points in use. [rp_address] Displays PIM group to active rendezvous points mappings. Displays information based on the group/mask ranges in the RP mapping cache. Displays information based on the DF list in RP mapping cache. Displays IPv4 bidirectional PIM information. Displays information about the multicast routing table.
Router# show mls ip multicast rp-mapping
Router# show mls ip multicast rp-mapping gm-cache
Router# show mls ip multicast rp-mapping df-cache
Router# show mls ip multicast bidir Router# show ip mroute
This example shows how to display information about the PIM group and rendezvous point mappings:
Router# show ip pim rp mapping PIM Group-to-RP Mappings This system is an RP (Auto-RP) This system is an RP-mapping agent Group(s) 230.31.0.0/16 RP 60.0.0.60 (?), v2v1, bidir Info source:60.0.0.60 (?), elected via Auto-RP Uptime:00:03:47, expires:00:02:11 RP 50.0.0.50 (?), v2v1, bidir Info source:50.0.0.50 (?), via Auto-RP Uptime:00:03:04, expires:00:02:55 RP 40.0.0.40 (?), v2v1, bidir Info source:40.0.0.40 (?), via Auto-RP Uptime:00:04:19, expires:00:02:38
This example shows how to display information in the IP multicast routing table that is related to IPv4 bidirectional PIM:
Router# show ip mroute bidirectional (*, 225.1.3.0), 00:00:02/00:02:57, RP 3.3.3.3, flags:BC Bidir-Upstream:GigabitEthernet2/1, RPF nbr 10.53.1.7, RPF-MFD Outgoing interface list: GigabitEthernet2/1, Bidir-Upstream/Sparse-Dense, 00:00:02/00:00:00,H Vlan30, Forward/Sparse-Dense, 00:00:02/00:02:57, H (*, 225.1.2.0), 00:00:04/00:02:55, RP 3.3.3.3, flags:BC Bidir-Upstream:GigabitEthernet2/1, RPF nbr 10.53.1.7, RPF-MFD Outgoing interface list: GigabitEthernet2/1, Bidir-Upstream/Sparse-Dense, 00:00:04/00:00:00,H Vlan30, Forward/Sparse-Dense, 00:00:04/00:02:55, H (*, 225.1.4.1), 00:00:00/00:02:59, RP 3.3.3.3, flags:BC Bidir-Upstream:GigabitEthernet2/1, RPF nbr 10.53.1.7, RPF-MFD Outgoing interface list: GigabitEthernet2/1, Bidir-Upstream/Sparse-Dense, 00:00:00/00:00:00,H Vlan30, Forward/Sparse-Dense, 00:00:00/00:02:59, H
28-25
This example show how to display information related to a specific multicast route. In the output below, the arrow in the margin points to information about a partical short cut:
Router# show ip mroute 239.1.1.2 4.4.4.4 IP Multicast Routing Table Flags:D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel Y - Joined MDT-data group, y - Sending to MDT-data group Outgoing interface flags:H - Hardware switched Timers:Uptime/Expires Interface state:Interface, Next-Hop or VCD, State/Mode (4.4.4.4, 239.1.1.2), 1d02h/00:03:20, flags:FTZ Incoming interface:Loopback0, RPF nbr 0.0.0.0, Partial-SC Outgoing interface list: Vlan10, Forward/Sparse-Dense, 1d02h/00:02:39 (ttl-threshold 5)
This example shows how to display the entries for a specific multicast group address:
Router# show mls ip multicast group 230.31.31.1 Multicast hardware switched flows: (*, 230.31.31.1) Incoming interface:Vlan611, Packets switched:1778 Hardware switched outgoing interfaces:Vlan131 Vlan151 Vlan415 Gi4/16 Vlan611 RPF-MFD installed
This example shows how to display PIM group to active rendezvous points mappings:
Router# show mls ip multicast rp-mapping State:H - Hardware Switched, I - Install Pending, D - Delete Pending, Z - Zombie RP Address 60.0.0.60 State H RPF Vl611 DF-count 4 GM-count 1
This example shows how to display information based on the group/mask ranges in the RP mapping cache:
Router# show mls ip multicast rp-mapping gm-cache State:H - Hardware Switched, I - Install Pending, D - Delete Pending, Z - Zombie RP Address 60.0.0.60 State H Group 230.31.0.0 Mask 255.255.0.0 State H Packet/Byte-count 100/6400
This example shows how to display information about specific MLS IP multicasting groups:
Router# show mls ip multicast rp-mapping df-cache State:H - Hardware Switched, I - Install Pending, D - Delete Pending, Z - Zombie RP Address 60.0.0.60 60.0.0.60 60.0.0.60 60.0.0.60 State H H H H DF Vl131 Vl151 Vl415 Gi4/16 State H H H H
28-26
OL-3999-08
Chapter 28
Using IPv4 Debug Commands

Table 28-2 describes IPv4 multicast Layer 3 switching debug commands that you can use to troubleshoot IP multicast Layer 3 switching problems.
Table 28-2 IP Multicast Layer 3 Switching Debug Commands
Command
[no] debug mls ip multicast events [no] debug mls ip multicast errors [no] debug mls ip multicast group group_id group_mask [no] debug mls ip multicast messages
Description Displays IP multicast Layer 3 switching events. Turns on debug messages for multicast MLS-related errors. Turns on debugging for a subset of flows. Displays IP multicast Layer 3 switching messages from and to hardware switching engine. Turns on all IP multicast Layer 3 switching messages. Turns on MDSS1 error messages. Displays MDSS-related events for debugging. Displays IPv4 bidirectional PIM MDSS events for debugging. Displays all MDSS messages. Displays the DF election for a given rendezvous point for debug purposes.
[no] debug mls ip multicast all [no] debug mdss errors [no] debug mdss events [no] debug mdss events mroute-bidir [no] debug mdss all [no] debug ip pim df ip_address
1. MDSS = Multicast Distributed Switching Services
Clearing IPv4 Multicast Layer 3 Switching Statistics

To clear IP multicast Layer 3 switching statistics, perform this task: Command
Router# clear mls ip multicast statistics
Purpose Clears IP multicast Layer 3 switching statistics.
This example shows how to clear IP multicast Layer 3 switching statistics:

Router# clear mls ip multicast statistics
The show mls multicast statistics command displays a variety of information about the multicast flows being handled by the PFC. You can display entries based on any combination of the participating MSFC, the VLAN, the multicast group address, or the multicast traffic source. For an example of the show mls ip multicast statistics command, see the Displaying IPv4 Multicast Layer 3 Switching Statistics section on page 28-22.
28-27
Redundancy for Multicast Traffic

Redundancy for multicast traffic requires the following conditions:
Unicast routing protocol such as OSPF or EIGRP PIM uses RPF checks on the unicast routing table to determine the proper paths for multicast data to traverse. If a unicast routing path changes, PIM relies upon the unicast routing protocol (OSPF) to properly converge, so that the RPF checks used by PIM continue to work and show valid unicast paths to and from the source IP address of the server sourcing the multicast stream.
PIM configured on all related Layer 3 interfaces The unicast routing table is used to do path selection for PIM. PIM uses RPF checks to ultimately determine the shortest path tree (SPT) between the client (receiver VLAN) and the source (multicast VLAN). Therefore, the objective of PIM is to find the shortest unicast path between the receiver subnet and the source subnet. You do not need to configure anything else for multicast when the unicast routing protocol is working as expected and PIM is configured on all the Layer 3 links associated with the unicast routing protocol.
Tip
28-28
OL-3999-08
C H A P T E R
29
Configuring MLDv2 Snooping for IPv6 Multicast Traffic

This chapter describes how to configure Multicast Listener Discovery version 2 (MLDv2) snooping for IPv6 multicast traffic on the Catalyst 6500 series switches. Release 12.2(18)SXE and later releases support MLDv2 snooping on all versions of the PFC3.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html To constrain IPv4 Multicast traffic, see Chapter 30, Configuring IGMP Snooping for IPv4 Multicast Traffic. MLD version 1 is not supported.

Understanding How MLDv2 Snooping Works, page 29-2 Default MLDv2 Snooping Configuration, page 29-8 MLDv2 Snooping Configuration Guidelines and Restrictions, page 29-8 MLDv2 Snooping Querier Configuration Guidelines and Restrictions, page 29-8 Enabling the MLDv2 Snooping Querier, page 29-9 Configuring MLDv2 Snooping, page 29-10
Tip
29-1
Chapter 29 Understanding How MLDv2 Snooping Works
Understanding How MLDv2 Snooping Works

These sections describe MLDv2 snooping:

MLDv2 Snooping Overview, page 29-2 MLDv2 Messages, page 29-3 Source-Based Filtering, page 29-3 Explicit Host Tracking, page 29-3 MLDv2 Snooping Proxy Reporting, page 29-4 Joining an IPv6 Multicast Group, page 29-4 Leaving a Multicast Group, page 29-6 Understanding the MLDv2 Snooping Querier, page 29-7
MLDv2 Snooping Overview

MLDv2 snooping allows Catalyst 6500 series switches to examine MLDv2 packets and make forwarding decisions based on their content. You can configure the switch to use MLDv2 snooping in subnets that receive MLDv2 queries from either MLDv2 or the MLDv2 snooping querier. MLDv2 snooping constrains IPv6 multicast traffic at Layer 2 by configuring Layer 2 LAN ports dynamically to forward IPv6 multicast traffic only to those ports that want to receive it. MLDv2, which runs at Layer 3 on a multicast router, generates Layer 3 MLDv2 queries in subnets where the multicast traffic needs to be routed. For information about MLDv2, see this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/ipv6/configuration/12-2sx/ipv6-12-2sx-book.html You can configure the MLDv2 snooping querier on the switch to support MLDv2 snooping in subnets that do not have any multicast router interfaces. For more information about the MLDv2 snooping querier, see the Enabling the MLDv2 Snooping Querier section on page 29-9. MLDv2 (on a multicast router) or the MLDv2 snooping querier (on the supervisor engine) sends out periodic general MLDv2 queries that the switch forwards through all ports in the VLAN, and to which hosts respond. MLDv2 snooping monitors the Layer 3 MLDv2 traffic.
Note
PFC/DFC 3B/3BXL does not support source-only Layer 2 entries and therefore IPv6 multicast flooding cannot be prevented in a source-only network.
Note
If a multicast group has only sources and no receivers in a VLAN, MLDv2 snooping constrains the multicast traffic to only the multicast router ports.
29-2
OL-3999-08
Chapter 29
Configuring MLDv2 Snooping for IPv6 Multicast Traffic Understanding How MLDv2 Snooping Works
MLDv2 Messages
MLDv2 uses these messages:
Multicast listener queries:

General querySent by a multicast router to learn which multicast addresses have listeners. Multicast address specific querySent by a multicast router to learn if a particular multicast
address has any listeners.

Multicast address and source specific querySent by a multicast router to learn if any of the
sources from the specified list for the particular multicast address has any listeners.
Multicast listener reports:

Current state record (solicited)Sent by a host in response to a query to specify the INCLUDE
or EXCLUDE mode for every multicast group in which the host is interested.
Filter mode change record (unsolicited)Sent by a host to change the INCLUDE or EXCLUDE
mode of one or more multicast groups.

Source list change record (unsolicited)Sent by a host to change information about multicast
sources.
Source-Based Filtering
MLDv2 uses source-based filtering, which enables hosts and routers to specify which multicast sources should be allowed or blocked for a specific multicast group. Source-based filtering either allows or blocks traffic based on the following information in MLDv2 messages:

Source lists INCLUDE or EXCLUDE mode
Because the Layer 2 table is (MAC-group, VLAN) based, with MLDv2 hosts it is preferable to have only a single multicast source per MAC-group.
Note
Source-based filtering is not supported in hardware. The states are maintained only in software and used for explicit host tracking and statistics collection.
Explicit Host Tracking

MLDv2 supports explicit tracking of membership information on any port. The explicit-tracking database is used for fast-leave processing, proxy reporting, and statistics collection. When explicit tracking is enabled on a VLAN, the MLDv2 snooping software processes the MLDv2 report it receives from a host and builds an explicit-tracking database that contains the following information:

The port connected to the host The channels reported by the host The filter mode for each group reported by the host The list of sources for each group reported by the hosts The router filter mode of each group For each group, the list of hosts requesting the source
29-3
Note
Disabling explicit host tracking disables fast-leave processing and proxy reporting. When explicit tracking is enabled and the switch is in report-suppression mode, the multicast router might not be able to track all the hosts accessed through a VLAN interface.
MLDv2 Snooping Proxy Reporting

Because MLDv2 does not have report suppression, all the hosts send their complete multicast group membership information to the multicast router in response to queries. The switch snoops these responses, updates the database and forwards the reports to the multicast router. To prevent the multicast router from becoming overloaded with reports, MLDv2 snooping does proxy reporting. Proxy reporting forwards only the first report for a multicast group to the router and suppresses all other reports for the same multicast group. Proxy reporting processes solicited and unsolicited reports. Proxy reporting is enabled and cannot be disabled.
Note
Disabling explicit host tracking disables fast-leave processing and proxy reporting.
Joining an IPv6 Multicast Group

Hosts join IPv6 multicast groups either by sending an unsolicited MLDv2 report or by sending an MLDv2 report in response to a general query from an IPv6 multicast router (the switch forwards general queries from IPv6 multicast routers to all ports in a VLAN). The switch snoops these reports. In response to a snooped MLDv2 report, the switch creates an entry in its Layer 2 forwarding table for the VLAN on which the report was received. When other hosts that are interested in this multicast traffic send MLDv2 reports, the switch snoops their reports and adds them to the existing Layer 2 forwarding table entry. The switch creates only one entry per VLAN in the Layer 2 forwarding table for each multicast group for which it snoops an MLDv2 report. MLDv2 snooping suppresses all but one of the host reports per multicast group and forwards this one report to the IPv6 multicast router. The switch forwards multicast traffic for the multicast group specified in the report to the interfaces where reports were received (see Figure 29-1). Layer 2 multicast groups learned through MLDv2 snooping are dynamic. However, you can statically configure Layer 2 multicast groups using the mac-address-table static command. When you specify group membership for a multicast group address statically, the static setting supersedes any MLDv2 snooping learning. Multicast group membership lists can consist of both static and MLDv2 snooping-learned settings.
29-4
OL-3999-08
Chapter 29
Figure 29-1 Initial MLDv2 Listener Report
Router A
1 MLDv2 report PFC CPU 0 VLAN
Forwarding table 2 3 4 5
Host 1
Host 2
Host 3
Host 4
Multicast router A sends an MLDv2 general query to the switch, which forwards the query to ports 2 through 5 (all members of the same VLAN). Host 1 wants to join an IPv6 multicast group and multicasts an MLDv2 report to the group with the equivalent MAC destination address of 0x0100.5E01.0203. When the switch snoops the MLDv2 report multicast by Host 1, the switch uses the information in the MLDv2 report to create a forwarding-table entry, as shown in Table 29-1, that includes the port numbers of Host 1, the multicast router, and the switch.
Table 29-1 MLDv2 Snooping Forwarding Table
Destination MAC Address 0100.5exx.xxxx 0100.5e01.0203
Type of Packet MLDv2 !MLDv2
Ports 0 1, 2
The switch hardware can distinguish MLDv2 information packets from other packets for the multicast group. The first entry in the table tells the switch to send only MLDv2 packets to the CPU. This prevents the switch from becoming overloaded with multicast frames. The second entry tells the switch to send frames addressed to the 0x0100.5E01.0203 multicast MAC address that are not MLDv2 packets (!MLDv2) to the multicast router and to the host that has joined the group. If another host (for example, Host 4) sends an unsolicited MLDv2 report for the same group (Figure 29-2), the switch snoops that message and adds the port number of Host 4 to the forwarding table as shown in Table 29-2. Because the forwarding table directs MLDv2 messages only to the switch, the message is not flooded to other ports. Any known multicast traffic is forwarded to the group and not to the switch.
130143
29-5
Figure 29-2 Second Host Joining a Multicast Group
Router A
1 VLAN
PFC CPU 0
Host 1
Host 2
Host 3
Host 4
Table 29-2 Updated MLDv2 Snooping Forwarding Table
Destination MAC Address 0100.5exx.xxxx 0100.5e01.0203
Type of Packet MLDv2 !MLDv2
Leaving a Multicast Group

These sections describe leaving a multicast group:

Normal Leave Processing, page 29-6 Fast-Leave Processing, page 29-7
Normal Leave Processing

Interested hosts must continue to respond to the periodic MLDv2 general queries. As long as at least one host in the VLAN responds to the periodic MLDv2 general queries, the multicast router continues forwarding the multicast traffic to the VLAN. When hosts want to leave a multicast group, they can either ignore the periodic MLDv2 general queries (called a silent leave), or they can send an MLDv2 filter mode change record. When MLDv2 snooping receives a filter mode change record from a host that configures the EXCLUDE mode for a group, MLDv2 snooping sends out a MAC-addressed general query to determine if any other hosts connected to that interface are interested in traffic for the specified multicast group. If MLDv2 snooping does not receive an MLDv2 report in response to the general query, MLDv2 snooping assumes that no other hosts connected to the interface are interested in receiving traffic for the specified multicast group, and MLDv2 snooping removes the interface from its Layer 2 forwarding table entry for the specified multicast group.
29-6
45751
Forwarding table
Ports 0 1, 2, 5
OL-3999-08
Chapter 29
If the filter mode change record was from the only remaining interface with hosts interested in the group, and MLDv2 snooping does not receive an MLDv2 report in response to the general query, MLDv2 snooping removes the group entry and relays the MLDv2 filter mode change record to the multicast router. If the multicast router receives no reports from a VLAN, the multicast router removes the group for the VLAN from its MLDv2 cache. The interval for which the switch waits before updating the table entry is called the last member query interval. To configure the interval, enter the ipv6 mld snooping last-member-query-interval interval command.
Fast-Leave Processing
Fast-leave processing is enabled by default. To disable fast-leave processing, turn off explicit-host tracking. Fast-leave processing is implemented by maintaining source-group based membership information in software while also allocating LTL indexes on a MAC GDA basis. When fast-leave processing is enabled, hosts send BLOCK_OLD_SOURCES{src-list} messages for a specific group when they no longer want to receive traffic from that source. When the switch receives such a message from a host, it parses the list of sources for that host for the given group. If this source list is exactly the same as the source list received in the leave message, the switch removes the host from the LTL index and stops forwarding this multicast group traffic to this host. If the source lists do not match, the switch does not remove the host from the LTL index until the host is no longer interested in receiving traffic from any source.
Note
Disabling explicit host tracking disables fast-leave processing and proxy reporting.
Understanding the MLDv2 Snooping Querier

Use the MLDv2 snooping querier to support MLDv2 snooping in a VLAN where PIM and MLDv2 are not configured because the multicast traffic does not need to be routed. In a network where IP multicast routing is configured, the IP multicast router acts as the MLDv2 querier. If the IP-multicast traffic in a VLAN only needs to be Layer 2 switched, an IP-multicast router is not required, but without an IP-multicast router on the VLAN, you must configure another switch as the MLDv2 querier so that it can send queries. When enabled, the MLDv2 snooping querier sends out periodic MLDv2 queries that trigger MLDv2 report messages from the switch that wants to receive IP multicast traffic. MLDv2 snooping listens to these MLDv2 reports to establish appropriate forwarding. You can enable the MLDv2 snooping querier on all the Catalyst 6500 series switches in the VLAN, but for each VLAN that is connected to switches that use MLDv2 to report interest in IP multicast traffic, you must configure at least one switch as the MLDv2 snooping querier. You can configure a switch to generate MLDv2 queries on a VLAN regardless of whether or not IP multicast routing is enabled.
29-7
Chapter 29 Default MLDv2 Snooping Configuration
Default MLDv2 Snooping Configuration

Table 29-3 shows the default MLDv2 snooping configuration.
Table 29-3 MLDv2 Snooping Default Configuration
Feature MLDv2 snooping querier MLDv2 snooping Multicast routers MLDv2 report suppression MLDv2 snooping router learning method Fast-Leave Processing MLDv2 Explicit Host Tracking
Default Values Disabled Enabled None configured Enabled Learned automatically through PIM or MLDv2 packets Enabled Enabled
MLDv2 Snooping Configuration Guidelines and Restrictions

When configuring MLDv2 snooping, follow these guidelines and restrictions:
MLDv2 is derived from Internet Group Management Protocol version 3 (IGMPv3). MLDv2 protocol operations and state transitions, host and router behavior, query and report message processing, message forwarding rules, and timer operations are exactly same as IGMPv3. See draft-vida-mld-v2.02.txt for detailed information on MLDv2 protocol. MLDv2 protocol messages are Internet Control Message Protocol version 6 (ICMPv6) messages. MLDv2 message formats are almost identical to IGMPv3 messages. IPv6 multicast for Cisco IOS software uses MLD version 2. This version of MLD is fully backward-compatible with MLD version 1 (described in RFC 2710). Hosts that support only MLD version 1 interoperate with a router running MLD version 2. Mixed LANs with both MLD version 1 and MLD version 2 hosts are supported. MLDv2 snooping supports private VLANs. Private VLANs do not impose any restrictions on MLDv2 snooping. MLDv2 snooping constrains traffic in MAC multicast groups 0100.5e00.0001 to 0100.5eff.ffff. MLDv2 snooping does not constrain Layer 2 multicasts generated by routing protocols.
MLDv2 Snooping Querier Configuration Guidelines and Restrictions

When configuring the MLDv2 snooping querier, follow these guidelines and restrictions:

Configure the VLAN in global configuration mode (see Chapter 14, Configuring VLANs). Configure an IPv6 address on the VLAN interface (see Chapter 22, Configuring Layer 3 Interfaces). When enabled, the MLDv2 snooping querier uses the IPv6 address as the query source address.
29-8
OL-3999-08
Chapter 29
Configuring MLDv2 Snooping for IPv6 Multicast Traffic Enabling the MLDv2 Snooping Querier
If there is no IPv6 address configured on the VLAN interface, the MLDv2 snooping querier does not start. The MLDv2 snooping querier disables itself if the IPv6 address is cleared. When enabled, the MLDv2 snooping querier restarts if you configure an IPv6 address. When enabled, the MLDv2 snooping querier does not start if it detects MLDv2 traffic from an IPv6 multicast router. When enabled, the MLDv2 snooping querier starts after 60 seconds with no MLDv2 traffic detected from an IPv6 multicast router. When enabled, the MLDv2 snooping querier disables itself if it detects MLDv2 traffic from an IPv6 multicast router. QoS does not support MLDv2 packets when MLDv2 snooping is enabled. You can enable the MLDv2 snooping querier on all the Catalyst 6500 series switches in the VLAN that support it. One switch is elected as the querier.
Enabling the MLDv2 Snooping Querier

Use the MLDv2 snooping querier to support MLDv2 snooping in a VLAN where PIM and MLDv2 are not configured because the multicast traffic does not need to be routed. To enable the MLDv2 snooping querier in a VLAN, perform this task: Command
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 address prefix/prefix_length Router(config-if)# ipv6 mld snooping querier Router(config-if)# no ipv6 mld snooping querier
Purpose Selects the VLAN interface. Configures the IPv6 address and subnet. Enables the MLDv2 snooping querier. Disables the MLDv2 snooping querier. Exits configuration mode. Verifies the configuration.
Step 4 Step 5
Router(config-if)# end Router# show ipv6 mld interface vlan vlan_ID | include querier
This example shows how to enable the MLDv2 snooping querier on VLAN 200 and verify the configuration:
Router# interface vlan 200 Router(config-if)# ipv6 address 2001:0DB8:0:1::/64 eui-64 Router(config-if)# ipv6 mld snooping querier Router(config-if)# end Router# show ipv6 mld interface vlan 200 | include querier MLD snooping fast-leave is enabled and querier is enabled Router#
29-9
Chapter 29 Configuring MLDv2 Snooping
Configuring MLDv2 Snooping

Note
To use MLDv2 snooping, configure a Layer 3 interface in the subnet for IPv6 multicast routing or enable the MLDv2 snooping querier in the subnet (see the Enabling the MLDv2 Snooping Querier section on page 29-9). These sections describe how to configure MLDv2 snooping:

Enabling MLDv2 Snooping, page 29-10 Configuring a Static Connection to a Multicast Receiver, page 29-11 Enabling Fast-Leave Processing, page 29-13 Configuring Explicit Host Tracking, page 29-14 Configuring Report Suppression, page 29-14 Displaying MLDv2 Snooping Information, page 29-15
Note
Except for the global enable command, all MLDv2 snooping commands are supported only on VLAN interfaces.
Enabling MLDv2 Snooping

To enable MLDv2 snooping globally, perform this task: Command
Step 1
Router(config)# ipv6 mld snooping Router(config)# no ipv6 mld snooping
Purpose Enables MLDv2 snooping. Disables MLDv2 snooping. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show ipv6 mld interface vlan vlan_ID | include globally
This example shows how to enable MLDv2 snooping globally and verify the configuration:
Router(config)# ipv6 mld snooping Router(config)# end Router# show ipv6 mld interface vlan 200 | include globally MLD snooping is globally enabled Router#
To enable MLDv2 snooping in a VLAN, perform this task: Command

Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping Router(config-if)# no ipv6 mld snooping
Purpose Selects a VLAN interface. Enables MLDv2 snooping. Disables MLDv2 snooping.
29-10
OL-3999-08
Chapter 29
Configuring MLDv2 Snooping for IPv6 Multicast Traffic Configuring MLDv2 Snooping
Command
Step 3 Step 4
Router(config-if)# end Router# show ipv6 mld interface vlan vlan_ID | include snooping
This example shows how to enable MLDv2 snooping on VLAN 25 and verify the configuration:
Router# interface vlan 25 Router(config-if)# ipv6 mld snooping Router(config-if)# end Router# show ipv6 mld interface vlan 25 | include snooping MLD snooping is globally enabled MLD snooping is enabled on this interface MLD snooping fast-leave is enabled and querier is enabled MLD snooping explicit-tracking is enabled MLD snooping last member query response interval is 1000 ms MLD snooping report-suppression is disabled Router#
Configuring a Static Connection to a Multicast Receiver

To configure a static connection to a multicast receiver, perform this task: Command
Step 1
Router(config)# mac-address-table static mac_addr vlan vlan_id interface type1 slot/port [disable-snooping] Router(config)# no mac-address-table static mac_addr vlan vlan_id
Purpose Configures a static connection to a multicast receiver.
Clears a static connection to a multicast receiver. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config-if)# end Router# show mac-address-table address mac_addr 1.
When you configure a static connection, enter the disable-snooping keyword to prevent multicast traffic addressed to the statically configured multicast MAC address from also being sent to other ports in the same VLAN. This example shows how to configure a static connection to a multicast receiver:
Router(config)# mac-address-table static 0050.3e8d.6400 vlan 12 interface fastethernet 5/7
Configuring a Multicast Router Port Statically

To configure a static connection to a multicast router, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping mrouter interface type1 slot/port
Purpose Selects the VLAN interface. Configures a static connection to a multicast router.
29-11
Command
Step 3 Step 4
Router(config-if)# end Router# show ipv6 mld snooping mrouter 1.
The interface to the router must be in the VLAN where you are entering the command, the interface must be administratively up, and the line protocol must be up. This example shows how to configure a static connection to a multicast router:
Router(config-if)# ipv6 mld snooping mrouter interface fastethernet 5/6 Router(config-if)#
Configuring the MLD Snooping Query Interval

You can configure the interval for which the switch waits after sending a group-specific query to determine if hosts are still interested in a specific multicast group.
Note
When both MLD snooping fast-leave processing and the MLD snooping query interval are configured, fast-leave processing takes precedence. To configure the interval for the MLD snooping queries sent by the switch, perform this task:
Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping last-member-query-interval interval
Purpose Selects a VLAN interface. Configures the interval for the IGMP queries sent by the switch. Default is 1 second. Valid range is 1000 to 9990 milliseconds. Reverts to the default value. Verifies the configuration.
Router(config-if)# no ipv6 mld snooping last-member-query-interval
Step 3
Router# show ipv6 mld interface vlan vlan_ID | include last
This example shows how to configure the MLD snooping query interval:
Router(config-if)# ipv6 mld snooping last-member-query-interval 1000 Router(config-if)# exit Router# show ipv6 mld interface vlan 200 | include last MLD snooping last member query response interval is 1000 ms
29-12
OL-3999-08
Chapter 29
Enabling Fast-Leave Processing

To enable fast-leave processing in a VLAN, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping fast-leave Router(config-if)# no ipv6 mld snooping fast-leave
Purpose Selects a VLAN interface. Enables fast-leave processing in the VLAN. Disables fast-leave processing in the VLAN. Verifies the configuration.
Step 3
Router# show ipv6 mld interface vlan vlan_ID | include fast-leave
This example shows how to enable fast-leave processing on the VLAN 200 interface and verify the configuration:
Router# interface vlan 200 Router(config-if)# ipv6 mld snooping fast-leave Configuring fast leave on vlan 200 Router(config-if)# end Router# show ipv6 mld interface vlan 200 | include fast-leave MLD snooping fast-leave is enabled and querier is enabled Router#
Enabling SSM Safe Reporting

To enable source-specific multicast (SSM) safe reporting, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping ssm-safe-reporting Router(config-if)# no ipv6 mld snooping ssm-safe-reporting
Purpose Selects a VLAN interface. Enables SSM safe reporting. Clears the configuration.
This example shows how to SSM safe reporting:

Router(config)# interface vlan 10 Router(config-if)# ipv6 mld snooping ssm-safe-reporting
29-13
Configuring Explicit Host Tracking

Note
Disabling explicit host tracking disables fast-leave processing and proxy reporting. To enable explicit host tracking on a VLAN, perform this task:
Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping explicit-tracking Router(config-if)# no ipv6 mld snooping explicit-tracking
Purpose Selects a VLAN interface. Enables explicit host tracking. Clears the explicit host tracking configuration. Displays the status of explicit host tracking.
Step 3
Router# show ipv6 mld snooping explicit-tracking vlan vlan_ID
This example shows how to enable explicit host tracking:

Router(config)# interface vlan 25 Router(config-if)# ipv6 mld snooping explicit-tracking Router(config-if)# end Router# show ipv6 mld snooping explicit-tracking vlan 25 Source/Group Interface Reporter Filter_mode -----------------------------------------------------------------------10.1.1.1/226.2.2.2 Vl25:1/2 16.27.2.3 INCLUDE 10.2.2.2/226.2.2.2 Vl25:1/2 16.27.2.3 INCLUDE
Configuring Report Suppression

To enable report suppression on a VLAN, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping report-suppression Router(config-if)# no ipv6 mld snooping report-suppression
Purpose Selects a VLAN interface. Enables report suppression. Clears the report suppression configuration. Displays the status of report suppression.
Step 3
Router# show ipv6 mld interface vlan_ID | include report-suppression

Router(config)# interface vlan 25 Router(config-if)# ipv6 mld snooping report-suppression Router(config-if)# end Router# Router# show ipv6 mld interface vlan 25 | include report-suppression MLD snooping report-suppression is enabled
29-14
OL-3999-08
Chapter 29
Displaying MLDv2 Snooping Information

These sections describe displaying MLDv2 snooping information:

Displaying Multicast Router Interfaces, page 29-15 Displaying MAC Address Multicast Entries, page 29-15 Displaying MLDv2 Snooping Information for a VLAN Interface, page 29-16
Displaying Multicast Router Interfaces

When you enable IGMP snooping, the switch automatically learns to which interface the multicast routers are connected. To display multicast router interfaces, perform this task: Command
Router# show ipv6 mld snooping mrouter vlan_ID
Purpose Displays multicast router interfaces.
This example shows how to display the multicast router interfaces in VLAN 1:
Router# show ipv6 mld snooping mrouter vlan 1 vlan ports -----+---------------------------------------1 Gi1/1,Gi2/1,Fa3/48,Router Router#
Displaying MAC Address Multicast Entries

To display MAC address multicast entries for a VLAN, perform this task: Command
Router# show mac-address-table multicast vlan_ID [count]
Purpose Displays MAC address multicast entries for a VLAN.
This example shows how to display MAC address multicast entries for VLAN 1:
Router# show mac-address-table multicast vlan 1 vlan mac address type qos ports -----+---------------+--------+---+-------------------------------1 0100.5e02.0203 static -- Gi1/1,Gi2/1,Fa3/48,Router 1 0100.5e00.0127 static -- Gi1/1,Gi2/1,Fa3/48,Router 1 0100.5e00.0128 static -- Gi1/1,Gi2/1,Fa3/48,Router 1 0100.5e00.0001 static -- Gi1/1,Gi2/1,Fa3/48,Router,Switch Router#
This example shows how to display a total count of MAC address entries for a VLAN:
Router# show mac-address-table multicast 1 count Multicast MAC Entries for vlan 1: Router# 4
29-15
Displaying MLDv2 Snooping Information for a VLAN Interface

To display MLDv2 snooping information for a VLAN interface, perform this task: Command
Router# show ipv6 mld snooping {{explicit-tracking vlan_ID}| {mrouter [vlan vlan_ID]} | {report-suppression vlan vlan_ID} | {statistics vlan vlan_ID}
Purpose Displays MLDv2 snooping information on a VLAN interface.
This example shows how to display explicit tracking information on VLAN 25:
Router# show ipv6 mld snooping explicit-tracking vlan 25 Source/Group Interface Reporter Filter_mode -----------------------------------------------------------------------10.1.1.1/226.2.2.2 Vl25:1/2 16.27.2.3 INCLUDE 10.2.2.2/226.2.2.2 Vl25:1/2 16.27.2.3 INCLUDE
Router# show ipv6 mld snooping mrouter vlan 1 vlan ports -----+---------------------------------------1 Gi1/1,Gi2/1,Fa3/48,Router
This example shows IGMP snooping statistics information for VLAN 25:
Router# show ipv6 mld snooping statistics interface vlan 25 Snooping staticstics for Vlan25 #channels:2 #hosts :1 Source/Group 10.1.1.1/226.2.2.2 10.2.2.2/226.2.2.2 Interface Gi1/2:Vl25 Gi1/2:Vl25 Reporter 16.27.2.3 16.27.2.3 Uptime 00:01:47 00:01:47 Last-Join 00:00:50 00:00:50 Last-Leave -
Tip
29-16
OL-3999-08
C H A P T E R
30
Configuring IGMP Snooping for IPv4 Multicast Traffic

This chapter describes how to configure Internet Group Management Protocol (IGMP) snooping for IPv4 multicast traffic on the Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html To constrain IPv6 Multicast traffic, see Chapter 29, Configuring MLDv2 Snooping for IPv6 Multicast Traffic.

Understanding How IGMP Snooping Works, page 30-2 Default IGMP Snooping Configuration, page 30-7 IGMP Snooping Configuration Guidelines and Restrictions, page 30-8 IGMP Snooping Querier Configuration Guidelines and Restrictions, page 30-8 Enabling the IGMP Snooping Querier, page 30-9 Configuring IGMP Snooping, page 30-9
Tip
30-1
Chapter 30 Understanding How IGMP Snooping Works
Understanding How IGMP Snooping Works

These sections describe IGMP snooping:

IGMP Snooping Overview, page 30-2 Joining a Multicast Group, page 30-2 Leaving a Multicast Group, page 30-4 Understanding the IGMP Snooping Querier, page 30-5 Understanding IGMP Version 3 Support, page 30-5
IGMP Snooping Overview

You can configure the switch to use IGMP snooping in subnets that receive IGMP queries from either IGMP or the IGMP snooping querier. IGMP snooping constrains IPv4 multicast traffic at Layer 2 by configuring Layer 2 LAN ports dynamically to forward IPv4 multicast traffic only to those ports that want to receive it. IGMP, which runs at Layer 3 on a multicast router, generates Layer 3 IGMP queries in subnets where the multicast traffic needs to be routed. For information about IGMP, see Chapter 28, Configuring IPv4 Multicast Layer 3 Switching. You can configure the IGMP snooping querier on the switch to support IGMP snooping in subnets that do not have any multicast router interfaces. For more information about the IGMP snooping querier, see the Enabling the IGMP Snooping Querier section on page 30-9. IGMP (on a multicast router) or the IGMP snooping querier (on the supervisor engine) sends out periodic general IGMP queries that the switch forwards through all ports in the VLAN and to which hosts respond. IGMP snooping monitors the Layer 3 IGMP traffic.
Note
If a multicast group has only sources and no receivers in a VLAN, IGMP snooping constrains the multicast traffic to only the multicast router ports.
Joining a Multicast Group

Hosts join multicast groups either by sending an unsolicited IGMP join message or by sending an IGMP join message in response to a general query from a multicast router (the switch forwards general queries from multicast routers to all ports in a VLAN). In response to an IGMP join request, the switch creates an entry in its Layer 2 forwarding table for the VLAN on which the join request was received. When other hosts that are interested in this multicast traffic send IGMP join requests, the switch adds them to the existing Layer 2 forwarding table entry. The switch creates only one entry per VLAN in the Layer 2 forwarding table for each multicast group for which it receives an IGMP join request. IGMP snooping suppresses all but one of the host join messages per multicast group and forwards this one join message to the multicast router. The switch forwards multicast traffic for the multicast group specified in the join message to the interfaces where join messages were received (see Figure 30-1).
30-2
OL-3999-08
Chapter 30
Configuring IGMP Snooping for IPv4 Multicast Traffic Understanding How IGMP Snooping Works
Layer 2 multicast groups learned through IGMP snooping are dynamic. However, you can statically configure Layer 2 multicast groups using the mac-address-table static command. When you specify group membership for a multicast group address statically, the static setting supersedes any IGMP snooping learning. Multicast group membership lists can consist of both static and IGMP snooping-learned settings.
Figure 30-1 Initial IGMP Join Message
Router A
1 IGMP report 224.1.2.3 PFC CPU 0 VLAN
Host 1
Host 2
Host 3
Host 4
Multicast router A sends a general query to the switch, which forwards the query to ports 2 through 5 (all members of the same VLAN). Host 1 wants to join multicast group 224.1.2.3 and multicasts an IGMP membership report (IGMP join message) to the group with the equivalent MAC destination address of 0x0100.5E01.0203. When the CPU receives the IGMP report multicast by Host 1, the CPU uses the information in the IGMP report to set up a forwarding-table entry, as shown in Table 30-1, that includes the port numbers of Host 1, the multicast router, and the switch internal CPU.
Table 30-1 IGMP Snooping Forwarding Table
Destination Address 0100.5exx.xxxx 0100.5e01.0203
Type of Packet IGMP !IGMP
Ports 0 1, 2
The switch hardware can distinguish IGMP information packets from other packets for the multicast group. The first entry in the table tells the switching engine to send only IGMP packets to the CPU. This prevents the CPU from becoming overloaded with multicast frames. The second entry tells the switching engine to send frames addressed to the 0x0100.5E01.0203 multicast MAC address that are not IGMP packets (!IGMP) to the multicast router and to the host that has joined the group. If another host (for example, Host 4) sends an unsolicited IGMP join message for the same group (Figure 30-2), the CPU receives that message and adds the port number of Host 4 to the forwarding table as shown in Table 30-2. Because the forwarding table directs IGMP messages only to the CPU, the message is not flooded to other ports. Any known multicast traffic is forwarded to the group and not to the CPU.
45750
Forwarding table
30-3
Figure 30-2 Second Host Joining a Multicast Group
Router A
1 VLAN
PFC CPU 0
Host 1
Host 2
Host 3
Host 4
Table 30-2 Updated IGMP Snooping Forwarding Table
Destination Address 0100.5exx.xxxx 0100.5e01.0203
Type of Packet IGMP !IGMP
Leaving a Multicast Group

These sections describe leaving a multicast group:

Normal Leave Processing, page 30-4 Fast-Leave Processing, page 30-5
Normal Leave Processing

Interested hosts must continue to respond to the periodic general IGMP queries. As long as at least one host in the VLAN responds to the periodic general IGMP queries, the multicast router continues forwarding the multicast traffic to the VLAN. When hosts want to leave a multicast group, they can either ignore the periodic general IGMP queries (called a silent leave), or they can send a group-specific IGMPv2 leave message. When IGMP snooping receives a group-specific IGMPv2 leave message from a host, it sends out a MAC-based general query to determine if any other devices connected to that interface are interested in traffic for the specific multicast group. If IGMP snooping does not receive an IGMP Join message in response to the general query, it assumes that no other devices connected to the interface are interested in receiving traffic for this multicast group, and it removes the interface from its Layer 2 forwarding table entry for that multicast group. If the leave message was from the only remaining interface with hosts interested in the group and IGMP snooping does not receive an IGMP Join in response to the general
30-4
45751
Forwarding table
Ports 0 1, 2, 5
OL-3999-08
Chapter 30
Configuring IGMP Snooping for IPv4 Multicast Traffic Understanding How IGMP Snooping Works
query, it removes the group entry and relays the IGMP leave to the multicast router. If the multicast router receives no reports from a VLAN, the multicast router removes the group for the VLAN from its IGMP cache. The interval for which the switch waits before updating the table entry is called the last member query interval. To configure the interval, enter the ip igmp snooping last-member-query-interval interval command.
Fast-Leave Processing
IGMP snooping fast-leave processing allows IGMP snooping to remove a Layer 2 LAN interface from the forwarding-table entry without first sending out IGMP group-specific queries to the interface. Upon receiving a group-specific IGMPv2 leave message, IGMP snooping immediately removes the interface from the Layer 2 forwarding table entry for that multicast group, unless a multicast router was learned on the port. Fast-leave processing improves bandwidth management for all hosts on a switched network.
Note
Use fast-leave processing only on VLANs where only one host is connected to each Layer 2 LAN port. If fast-leave is enabled in VLANs where more than one host is connected to a Layer 2 LAN port, some hosts might be dropped inadvertently. Fast-leave processing is supported only with IGMP version 2 hosts.
Understanding the IGMP Snooping Querier

Use the IGMP snooping querier to support IGMP snooping in a VLAN where PIM and IGMP are not configured because the multicast traffic does not need to be routed. In a network where IP multicast routing is configured, the IP multicast router acts as the IGMP querier. If the IP-multicast traffic in a VLAN only needs to be Layer 2 switched, an IP-multicast router is not required, but without an IP-multicast router on the VLAN, you must configure another switch as the IGMP querier so that it can send queries. When enabled, the IGMP snooping querier sends out periodic IGMP queries that trigger IGMP report messages from the switch that wants to receive IP multicast traffic. IGMP snooping listens to these IGMP reports to establish appropriate forwarding. Configure one switch as the IGMP snooping querier in each VLAN that is supported on switches that use IGMP to report interest in IP multicast traffic.
Note
Enable the IGMP snooping querier on only one switch in the VLAN.
You can configure a switch to generate IGMP queries on a VLAN regardless of whether or not IP multicast routing is enabled.
Understanding IGMP Version 3 Support

These sections describe IGMP version 3 support:

IGMP Version 3 Support Overview, page 30-6 IGMPv3 Fast-Leave Processing, page 30-6 Proxy Reporting, page 30-6
30-5
Explicit Host Tracking, page 30-7
IGMP Version 3 Support Overview

IGMP snooping supports IGMP version 3. IGMP version 3 uses source-based filtering, which enables hosts and routers to specify which source addresses should be allowed or blocked for a specific multicast group. When you enable IGMP version 3 snooping on a Catalyst 6500 series switch, the system maintains IGMP version 3 states based on messages it receives for a particular group in a particular VLAN and either allows or blocks traffic based on the following information in these messages:

Source lists Allow (include) or block (exclude) filtering options
Because the Layer 2 table is (MAC-group, VLAN) based, with IGMPv3 hosts it is preferable to have only a single multicast source per MAC-group.
Note
Source-based filtering for IGMP version 3 reports is not supported in hardware. The states are maintained only in software and used for explicit host tracking and statistics collection. The source-only entries are deleted every 5 minutes and relearned to ensure that they are still valid.
IGMPv3 Fast-Leave Processing

IGMP version 3 fast-leave processing is enabled by default. To disable IGMP version 3 fast-leave processing you must turn off explicit-host tracking. Fast-leave processing with IGMPv3 is implemented by maintaining source-group based membership information in software while also allocating LTL indexes on a MAC GDA basis. When fast-leave processing is enabled, hosts send BLOCK_OLD_SOURCES{src-list} messages for a specific group when they no longer want to receive traffic from that source. When the switch receives such a message from a host, it parses the list of sources for that host for the given group. If this source list is exactly the same as the source list received in the leave message, the switch removes the host from the LTL index and stops forwarding this multicast group traffic to this host. If the source lists do not match, the switch does not remove the host from the LTL index until the host is no longer interested in receiving traffic from any source.
Proxy Reporting
IGMP supports proxy reporting for IGMPv1 and IGMPv2 messages to handle group-specific queries. These queries are not sent downstream, but the switch does respond to them directly. When the switch recieves a group-specific query, the switch terminates the query and sends an IGMP proxy report if there is a receiver for the group. There is no proxy reporting for IGMPv3 messages. For IGMPv3, a group-specific query or a group source-specific query is flooded to all VLAN member ports. The database for the IGMPv3 membership report is built based on the reports received. Host reports responding to a specific query can be suppressed by the report suppression feature. Report suppression is supported for IGMPv1, IGMPv2 and IGMPv3 messages. With report suppression enabled (by default), when the switch recieves a general query, the switch starts a suppression cycle for reports from all hosts to each group or channel (S,G). Only the first report to the discovered multicast routers are forwarded; the rest of the reports are suppressed. For IGMPv1 and IGMPv2, the time of suppression is the report response time indicated in the general query message. For IGMPv3, suppression occurs for the entire general query interval.
30-6
OL-3999-08
Chapter 30
Configuring IGMP Snooping for IPv4 Multicast Traffic Default IGMP Snooping Configuration
Note
Source-based filtering for IGMP version 3 reports is not supported in hardware. The states are maintained only in software and used for explicit host tracking and statistics collection. The source-only entries are deleted every 5 minutes and relearned to ensure that they are still valid. Turning off explicit host tracking disables fast-leave processing and proxy reporting.
Explicit Host Tracking

IGMPv3 supports explicit tracking of membership information on any port. The explicit-tracking database is used for fast-leave processing for IGMPv3 hosts, proxy reporting, and statistics collection. When explicit tracking is enabled on a VLAN, the IGMP snooping software processes the IGMPv3 report it receives from a host and builds an explicit-tracking database that contains the following information:

The port connected to the host The channels reported by the host The filter mode for each group reported by the host The list of sources for each group reported by the hosts The router filter mode of each group For each group, the list of hosts requesting the source
Note
Turning off explicit host tracking disables fast-leave processing and proxy reporting. When explicit tracking is enabled and the switch is working in proxy-reporting mode, the router may not be able to track all the hosts behind a VLAN interface.
Default IGMP Snooping Configuration

Table 30-3 shows the default IGMP snooping configuration.
Table 30-3 IGMP Snooping Default Configuration
Feature IGMP snooping querier IGMP snooping Multicast routers IGMPv3 proxy reporting IGMP snooping router learning method Fast-Leave Processing IGMPv3 Explicit Host Tracking IGMPv3 SSM Safe Reporting
Default Values Disabled Enabled None configured Enabled Learned automatically through PIM or IGMP packets Disabled Enabled Disabled; deprecated in Release 12.2(18)SXE and later releases
30-7
Chapter 30 IGMP Snooping Configuration Guidelines and Restrictions
IGMP Snooping Configuration Guidelines and Restrictions

When configuring IGMP snooping, follow these guidelines and restrictions:
To support Cisco Group Management Protocol (CGMP) client devices, configure the Multilayer Switch Feature Card (MSFC) as a CGMP server. Refer to the Cisco IOS IP and IP Routing Configuration Guide, Release 12.2, IP Multicast, Configuring IP Multicast Routing, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfmulti.html
For more information on IP multicast and IGMP, refer to RFC 1112 and RFC 2236. IGMP snooping supports private VLANs. Private VLANs do not impose any restrictions on IGMP snooping. IGMP snooping constrains traffic in MAC multicast groups 0100.5e00.0001 to 0100.5eff.ffff. IGMP snooping does not constrain Layer 2 multicasts generated by routing protocols.
IGMP Snooping Querier Configuration Guidelines and Restrictions

When configuring the IGMP snooping querier, follow these guidelines and restrictions:

The IGMP snooping querier does not support querier elections. Enable the IGMP snooping querier on only one switch in the VLAN. (CSCsk48795) Configure the VLAN in global configuration mode (see Chapter 14, Configuring VLANs). Configure an IP address on the VLAN interface (see Chapter 22, Configuring Layer 3 Interfaces). When enabled, the IGMP snooping querier uses the IP address as the query source address. If there is no IP address configured on the VLAN interface, the IGMP snooping querier does not start. The IGMP snooping querier disables itself if the IP address is cleared. When enabled, the IGMP snooping querier restarts if you configure an IP address. The IGMP snooping querier supports IGMP version 2. When enabled, the IGMP snooping querier does not start if it detects IGMP traffic from a multicast router. When enabled, the IGMP snooping querier starts after 60 seconds with no IGMP traffic detected from a multicast router. When enabled, the IGMP snooping querier disables itself if it detects IGMP traffic from a multicast router. QoS does not support IGMP packets when IGMP snooping is enabled.
Note
When you are in configuration mode you can enter EXEC mode commands by entering the do keyword before the EXEC mode command.
30-8
OL-3999-08
Chapter 30
Configuring IGMP Snooping for IPv4 Multicast Traffic Enabling the IGMP Snooping Querier
Enabling the IGMP Snooping Querier

Use the IGMP snooping querier to support IGMP snooping in a VLAN where PIM and IGMP are not configured because the multicast traffic does not need to be routed. To enable the IGMP snooping querier in a VLAN, perform this task: Command
Router(config)# interface vlan vlan_ID Router(config-if)# ip address ip_address subnet_mask Router(config-if)# ip igmp snooping querier Router(config-if)# no ip igmp snooping querier
Purpose Selects the VLAN interface. Configures the IP address and IP subnet. Enables the IGMP snooping querier. Disables the IGMP snooping querier. Exits configuration mode. Verifies the configuration.
Step 4 Step 5
Router(config-if)# end Router# show ip igmp interface vlan vlan_ID | include querier
This example shows how to enable the IGMP snooping querier on VLAN 200 and verify the configuration:
Router# interface vlan 200 Router(config-if)# ip address 172.20.52.106 255.255.255.248 Router(config-if)# igmp snooping querier Router(config-if)# end Router# show ip igmp interface vlan 200 | include querier IGMP snooping fast-leave (for v2) is disabled and querier is enabled Router#
Configuring IGMP Snooping

Note
To use IGMP snooping, configure a Layer 3 interface in the subnet for multicast routing (see Chapter 28, Configuring IPv4 Multicast Layer 3 Switching) or enable the IGMP snooping querier in the subnet (see the Enabling the IGMP Snooping Querier section on page 30-9). IGMP snooping allows Catalyst 6500 series switches to examine IGMP packets and make forwarding decisions based on their content. These sections describe how to configure IGMP snooping:

Enabling IGMP Snooping, page 30-10 Configuring a Static Connection to a Multicast Receiver, page 30-11 Configuring a Multicast Router Port Statically, page 30-11 Configuring the IGMP Snooping Query Interval, page 30-11 Enabling IGMP Fast-Leave Processing, page 30-12 Configuring Source Specific Multicast (SSM) Mapping, page 30-12 Enabling SSM Safe Reporting, page 30-13
30-9
Chapter 30 Configuring IGMP Snooping
Configuring IGMPv3 Explicit Host Tracking, page 30-13 Displaying IGMP Snooping Information, page 30-14
Note
Except for the global enable command, all IGMP snooping commands are supported only on VLAN interfaces.
Enabling IGMP Snooping

To enable IGMP snooping globally, perform this task: Command
Step 1
Router(config)# ip igmp snooping Router(config)# no ip igmp snooping
Purpose Enables IGMP snooping. Disables IGMP snooping. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show ip igmp interface vlan vlan_ID | include globally
This example shows how to enable IGMP snooping globally and verify the configuration:
Router(config)# Router(config)# Router# show ip IGMP snooping Router# ip igmp snooping end igmp interface vlan 200 | include globally is globally enabled
To enable IGMP snooping in a VLAN, perform this task: Command

Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping Router(config-if)# no ip igmp snooping
Purpose Selects a VLAN interface. Enables IGMP snooping. Disables IGMP snooping. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show ip igmp interface vlan vlan_ID | include snooping
This example shows how to enable IGMP snooping on VLAN 25 and verify the configuration:
Router# interface vlan 25 Router(config-if)# ip igmp snooping Router(config-if)# end Router# show ip igmp interface vl25 | include snooping IGMP snooping is globally enabled IGMP snooping is enabled on this interface IGMP snooping fast-leave is disabled and querier is disabled IGMP snooping explicit-tracking is enabled on this interface IGMP snooping last member query interval on this interface is 1000 ms Router#
30-10
OL-3999-08
Chapter 30
Configuring IGMP Snooping for IPv4 Multicast Traffic Configuring IGMP Snooping
Configuring a Static Connection to a Multicast Receiver

To configure a static connection to a multicast receiver, perform this task: Command
Step 1
Router(config)# mac-address-table static mac_addr vlan vlan_id interface type1 slot/port [disable-snooping] Router(config)# no mac-address-table static mac_addr vlan vlan_id
Purpose Configures a static connection to a multicast receiver.
Clears a static connection to a multicast receiver. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config-if)# end Router# show mac-address-table address mac_addr 1.
When you configure a static connection, enter the disable-snooping keyword to prevent multicast traffic addressed to the statically configured multicast MAC address from also being sent to other ports in the same VLAN. This example shows how to configure a static connection to a multicast receiver:
Router(config)# mac-address-table static 0050.3e8d.6400 vlan 12 interface fastethernet 5/7
Configuring a Multicast Router Port Statically

To configure a static connection to a multicast router, perform this task: Command
Router(config-if)# ip igmp snooping mrouter interface type1 slot/port Router(config-if)# end Router# show ip igmp snooping mrouter 1.
Purpose Configures a static connection to a multicast router. Exits configuration mode. Verifies the configuration.
The interface to the router must be in the VLAN where you are entering the command, the interface must be administratively up, and the line protocol must be up. This example shows how to configure a static connection to a multicast router:
Router(config-if)# ip igmp snooping mrouter interface fastethernet 5/6 Router(config-if)#
Configuring the IGMP Snooping Query Interval

You can configure the interval for which the switch waits after sending a group-specific query to determine if hosts are still interested in a specific multicast group.
Note
When both IGMP fast-leave processing and the IGMP query interval are configured, fast-leave processing takes precedence.
30-11
To configure the interval for the IGMP snooping queries sent by the switch, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping last-member-query-interval interval
Purpose Selects a VLAN interface. Configures the interval for the IGMP snooping queries sent by the switch. Default is 1 second. Valid range is 100 to 999 milliseconds. Reverts to the default value.
Router(config-if)# no ip igmp snooping last
This example shows how to configure the IGMP snooping query interval:
Router(config-if)# ip igmp snooping last-member-query-interval 200 Router(config-if)# exit Router# show ip igmp interface vlan 200 | include last IGMP snooping last member query interval on this interface is 200 ms
Enabling IGMP Fast-Leave Processing

To enable IGMP fast-leave processing in a VLAN, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping fast-leave Router(config-if)# no ip igmp snooping fast-leave
Purpose Selects a VLAN interface. Enables IGMP fast-leave processing in the VLAN. Disables IGMP fast-leave processing in the VLAN.
This example shows how to enable IGMP fast-leave processing on the VLAN 200 interface and verify the configuration:
Router# interface vlan 200 Router(config-if)# ip igmp snooping fast-leave Configuring fast leave on vlan 200 Router(config-if)# end Router# show ip igmp interface vlan 200 | include fast-leave IGMP snooping fast-leave is enabled on this interface Router(config-if)#
Configuring Source Specific Multicast (SSM) Mapping

Note
Release 12.2(18)SXD3 and later releases support SSM mapping. Do not configure SSM mapping in a VLAN that supports IGMPv3 multicast receivers.
To configure SSM mapping, refer to this publication: http://www.cisco.com/en/US/docs/ios-xml/ios/ipmulti_igmp/configuration/12-2sx/imc_ssm_mapping. html
30-12
OL-3999-08
Chapter 30
Enabling SSM Safe Reporting

Note
Source-specific multicast (SSM) safe reporting is deprecated in Release 12.2(18)SXE and later releases. When you configure SSM safe reporting, the group mode is IGMPv3 even in the presence of IGMPv1 and IGMPv2 hosts. To make sure the switch is able to support both IGMPv1, IGMPv2, and IGMPv3 hosts in the same VLAN, perform this task:
Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping ssm-safe-reporting Router(config-if)# no ip igmp snooping ssm-safe-reporting
Purpose Selects a VLAN interface. Enables support for both IGMPv2 and IGMPv3 hosts. Clears the configuration.
This example shows how to configure the switch to support both IGMPv2 and IGMPv3 hosts:
Router(config)# interface vlan 10 Router(config-if)# ip igmp snooping ssm-safe-reporting
Configuring IGMPv3 Explicit Host Tracking

To enable explicit host tracking on a VLAN, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping explicit-tracking Router(config-if)# no ip igmp snooping explicit-tracking
Purpose Selects a VLAN interface. Enables explicit host tracking. Clears the explicit host tracking configuration. Displays information about the explicit host tracking status for IGMPv3 hosts.
Step 3
Router# show ip igmp snooping explicit-tracking {vlan vlan-id}

Router(config)# interface vlan 25 Router(config-if)# ip igmp snooping explicit-tracking Router(config-if)# end Router# show ip igmp snooping explicit-tracking vlan 25
Source/Group Interface Reporter Filter_mode -----------------------------------------------------------------------10.1.1.1/226.2.2.2 Vl25:1/2 16.27.2.3 INCLUDE 10.2.2.2/226.2.2.2 Vl25:1/2 16.27.2.3 INCLUDE
30-13
Displaying IGMP Snooping Information

These sections describe displaying IGMP snooping information:

Displaying Multicast Router Interfaces, page 30-14 Displaying MAC Address Multicast Entries, page 30-14 Displaying IGMP Snooping Information for a VLAN Interface, page 30-15 Displaying IGMP Snooping Statistics, page 30-15
Displaying Multicast Router Interfaces

When you enable IGMP snooping, the switch automatically learns to which interface the multicast routers are connected. To display multicast router interfaces, perform this task: Command
Router# show ip igmp snooping mrouter vlan_ID
Purpose Displays multicast router interfaces.
Router# show ip igmp snooping mrouter vlan 1 vlan ports -----+---------------------------------------1 Gi1/1,Gi2/1,Fa3/48,Router Router#
Displaying MAC Address Multicast Entries

To display MAC address multicast entries for a VLAN, perform this task: Command
Router# show mac-address-table multicast vlan_ID [count]
Purpose Displays MAC address multicast entries for a VLAN.
This example shows how to display MAC address multicast entries for VLAN 1:
Router# show mac-address-table multicast vlan 1 vlan mac address type qos ports -----+---------------+--------+---+-------------------------------1 0100.5e02.0203 static -- Gi1/1,Gi2/1,Fa3/48,Router 1 0100.5e00.0127 static -- Gi1/1,Gi2/1,Fa3/48,Router 1 0100.5e00.0128 static -- Gi1/1,Gi2/1,Fa3/48,Router 1 0100.5e00.0001 static -- Gi1/1,Gi2/1,Fa3/48,Router,Switch Router#
This example shows how to display a total count of MAC address entries for a VLAN:
Router# show mac-address-table multicast 1 count Multicast MAC Entries for vlan 1: Router# 4
30-14
OL-3999-08
Chapter 30
Displaying IGMP Snooping Information for a VLAN Interface

To display IGMP snooping information for a VLAN interface, perform this task: Command
Router# show ip igmp interface vlan_ID
Purpose Displays IGMP snooping information on a VLAN interface.
This example shows how to display IGMP snooping information on the VLAN 200 interface:
Router# show ip igmp interface vlan 43 Vlan43 is up, line protocol is up Internet address is 43.0.0.1/24 IGMP is enabled on interface Current IGMP host version is 2 Current IGMP router version is 2 IGMP query interval is 60 seconds IGMP querier timeout is 120 seconds IGMP max query response time is 10 seconds Last member query count is 2 Last member query response interval is 1000 ms Inbound IGMP access group is not set IGMP activity:1 joins, 0 leaves Multicast routing is enabled on interface Multicast TTL threshold is 0 Multicast designated router (DR) is 43.0.0.1 (this system) IGMP querying router is 43.0.0.1 (this system) Multicast groups joined by this system (number of users): 224.0.1.40(1) IGMP snooping is globally enabled IGMP snooping is enabled on this interface IGMP snooping fast-leave is disabled and querier is disabled IGMP snooping explicit-tracking is enabled on this interface IGMP snooping last member query interval on this interface is 1000 ms Router#
Displaying IGMP Snooping Statistics

The show ip igmp snooping statistics interface vlan_ID command displays the following information:

The list of ports that are members of a group The filter mode The reporter-address behind the port The last-join and last-leave information collected since the last time a clear ip igmp snooping statistics command was entered
To display IGMP snooping statistics, perform this task: Command

Router# show ip igmp snooping statistics interface vlan_ID
Purpose Displays IGMP snooping information on a VLAN interface.
30-15
This example shows IGMP snooping statistics information for interface VLAN 25:
Router# show ip igmp snooping statistics interface vlan 25 Snooping statistics for Vlan25 #channels:2 #hosts :1 Source/Group 10.1.1.1/226.2.2.2 10.2.2.2/226.2.2.2 Router# Interface Gi1/2:Vl25 Gi1/2:Vl25 Reporter 16.27.2.3 16.27.2.3 Uptime 00:01:47 00:01:47 Last-Join 00:00:50 00:00:50 Last-Leave -
Tip
30-16
OL-3999-08
C H A P T E R
31
Configuring PIM Snooping

This chapter describes how to configure protocol independent multicast (PIM) snooping on the Catalyst 6500 series switches. Release 12.2(17a)SX and later releases support PIM snooping.
Note

Understanding How PIM Snooping Works, page 31-1 Default PIM Snooping Configuration, page 31-4 PIM Snooping Configuration Guidelines and Restrictions, page 31-4 Configuring PIM Snooping, page 31-5
Tip
Understanding How PIM Snooping Works

In networks where a Layer 2 switch interconnects several routers, such as an Internet exchange point (IXP), the switch floods IP multicast packets on all multicast router ports by default, even if there are no multicast receivers downstream. With PIM snooping enabled, the switch restricts multicast packets for each IP multicast group to only those multicast router ports that have downstream receivers joined to that group. When you enable PIM snooping, the switch learns which multicast router ports need to receive the multicast traffic within a specific VLAN by listening to the PIM hello messages, PIM join and prune messages, and bidirectional PIM designated forwarder-election messages.
31-1
Chapter 31 Understanding How PIM Snooping Works
Note
To use PIM snooping, you must enable IGMP snooping on the Catalyst 6500 series switch. IGMP snooping restricts multicast traffic that exits through the LAN ports to which hosts are connected. IGMP snooping does not restrict traffic that exits through the LAN ports to which one or more multicast routers are connected. The following illustrations show the flow of traffic and flooding that results in networks without PIM snooping enabled and the flow of traffic and traffic restriction when PIM snooping is enabled. Figure 31-1 shows the flow of a PIM join message without PIM snooping enabled. In the figure, the switches flood the PIM join message intended for Router B to all connected routers.
Figure 31-1 PIM Join Message Flow without PIM Snooping
Router C
Router D
SP network
(*, G) PIM join Router A Receiver IGMP join Router B RP Source

99473
Figure 31-2 shows the flow of a PIM join message with PIM snooping enabled. In the figure, the switches restrict the PIM join message and forward it only to the router that needs to receive it (Router B).
31-2
OL-3999-08
Chapter 31
Configuring PIM Snooping Understanding How PIM Snooping Works
Figure 31-2 PIM Join Message Flow with PIM Snooping
Router C
Router D
SP network
(*, G) PIM join Router A Receiver IGMP join Router B RP Source

99474
Figure 31-3 shows the flow of data traffic without PIM snooping enabled. In the figure, the switches flood the data traffic intended for Router A to all connected routers.
Figure 31-3 Data Traffic Flow without PIM Snooping
Router C
Router D
SP network
G traffic
Router A Receiver
Router B RP Source Data

99472
Figure 31-4 shows the flow of data traffic with PIM snooping enabled. In the figure, the switches forward the data traffic only to the router that needs to receive it (Router A).
31-3
Chapter 31 Default PIM Snooping Configuration
Figure 31-4 Data Traffic Flow with PIM Snooping
Router C
Router D
SP network
G traffic
Router A Receiver
Router B RP Source Data

99475
Default PIM Snooping Configuration

PIM snooping is disabled by default.
PIM Snooping Configuration Guidelines and Restrictions

When configuring PIM snooping, follow these guidelines and restrictions:
When you use the PIM-sparse mode (PIM-SM) feature, downstream routers only see traffic if they previously indicated interest through a PIM join or prune message. An upstream router only sees traffic if it was used as an upstream router during the PIM join or prune process. Join or prune messages are not flooded on all router ports but are sent only to the port corresponding to the upstream router mentioned in the payload of the join or prune message. Directly connected sources are supported for bidirectional PIM groups. Traffic from directly connected sources is forwarded to the designated router and designated forwarder for a VLAN. In some cases, a nondesignated router (NDR) can receive a downstream (S, G) join. For source-only networks, the initial unknown traffic is flooded only to the designated routers and designated forwarders. Dense group mode traffic is seen as unknown traffic and is dropped. The AUTO-RP groups (224.0.1.39 and 224.0.1.40) are always flooded. The switch snoops on designated forwarder election and maintains a list of all designated forwarder routers for various RPs for the VLAN. All traffic is sent to all designated forwarders which ensures that bidirectional functionality works properly. PIM snooping and IGMP snooping can be enabled at the same time in a VLAN. Either RGMP or PIM snooping can be enabled in a VLAN but not both.
31-4
OL-3999-08
Chapter 31
Configuring PIM Snooping Configuring PIM Snooping
Any non-PIMv2 multicast router will receive all traffic. You can enable or disable PIM snooping on a per-VLAN basis. All mroute and router information is timed out based on the hold-time indicated in the PIM hello and join/prune control packets. All mroute state and neighbor information is maintained per VLAN.

These sections describe how to configure PIM snooping:

Enabling PIM Snooping Globally, page 31-5 Enabling PIM Snooping in a VLAN, page 31-5 Disabling PIM Snooping Designated-Router Flooding, page 31-6
Enabling PIM Snooping Globally

To enable PIM snooping globally, perform this task: Command
Step 1
Router(config)# ip pim snooping Router(config)# no ip pim snooping
Purpose Enables PIM snooping. Disables PIM snooping. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show ip pim snooping
This example shows how to enable PIM snooping globally and verify the configuration:
Router(config)# ip pim snooping Router(config)# end Router# show ip pim snooping Global runtime mode: Enabled Global admin mode : Enabled Number of user enabled VLANs: 1 User enabled VLANs: 10 Router#
Note
You do not need to configure an IP address or IP PIM in order to run PIM snooping.
Enabling PIM Snooping in a VLAN

To enable PIM snooping in a VLAN, perform this task: Command
Step 1 Step 2
Router(config)# interface vlan vlan_ID Router(config-if)# ip pim snooping Router(config-if)# no ip pim snooping
Purpose Selects a VLAN interface. Enables PIM snooping. Disables PIM snooping.
31-5
Chapter 31 Configuring PIM Snooping
Command
Step 3 Step 4
Router(config-if)# end Router# show ip pim snooping
This example shows how to enable PIM snooping on VLAN 10 and verify the configuration:
Router# interface vlan 10 Router(config-if)# ip pim snooping Router(config-if)# end Router# show ip pim snooping vlan 10 3 neighbors (0 DR priority incapable, 0 Bi-dir incapable) 6 mroutes, 3 mac entries DR is 10.10.10.4 RP DF Set Router#
Disabling PIM Snooping Designated-Router Flooding

Note
The PIM snooping DR flooding enhancement is supported with:

Release 12.2(18)SXF and later releases on Supervisor Engine 720 Release 12.2(18)SXF2 and later releases on Supervisor Engine 32 and Supervisor Engine 2
Do not disable designated-router flooding on switches in a Layer 2 broadcast domain that supports multicast sources.
By default, switches that have PIM snooping enabled will flood multicast traffic to the designated router (DR). This method of operation can send unnecessary multicast packets to the designated router. The network must carry the unnecessary traffic, and the designated router must process and drop the unnecessary traffic. To reduce the traffic sent over the network to the designated router, disable designated-router flooding. With designated-router flooding disabled, PIM snooping only passes to the designated-router traffic that is in multicast groups for which PIM snooping receives an explicit join from the link towards the designated router. To disable PIM snooping designated-router flooding, perform this task: Command
Router(config)# no ip pim snooping dr-flood Router(config)# end Router# show running-config | include dr-flood
Purpose Disables PIM snooping designated-router flooding. Exits configuration mode. Verifies the configuration.
This example shows how to disable PIM snooping designated-router flooding:

Router(config)# no ip pim snooping dr-flood Router(config)# end
31-6
OL-3999-08
Chapter 31
Configuring PIM Snooping Configuring PIM Snooping
Tip
31-7
Chapter 31 Configuring PIM Snooping
31-8
OL-3999-08
C H A P T E R
32
Configuring RGMP
This chapter supplements the information and procedures about Router-Port Group Management Protocol (RGMP) in the Release 12.2 publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfrgmp.html This chapter consists of these sections:

Understanding How RGMP Works, page 32-1 Default RGMP Configuration, page 32-2 RGMP Configuration Guidelines and Restrictions, page 32-2 Enabling RGMP on Layer 3 Interfaces, page 32-3
Tip
Understanding How RGMP Works

RGMP constrains multicast traffic that exits the Catalyst 6500 series switch through ports to which only disinterested multicast routers are connected. RGMP reduces network congestion by forwarding multicast traffic to only those routers that are configured to receive it.
Note
To use RGMP, you must enable IGMP snooping on the Catalyst 6500 series switch. IGMP snooping constrains multicast traffic that exits through LAN ports to which hosts are connected. IGMP snooping does not constrain traffic that exits through LAN ports to which one or more multicast routers are connected. You must enable Protocol Independent Multicast (PIM) on all routers and switches for RGMP to work. Only PIM sparse mode is currently supported.
32-1
Chapter 32 Default RGMP Configuration
Configuring RGMP
All routers on the network must be RGMP-capable. RGMP-capable routers send RGMP hello messages periodically. The RGMP hello message tells the Catalyst 6500 series switch not to send multicast data to the router unless an RGMP join message has also been sent to the Catalyst 6500 series switch from that router. When an RGMP join message is sent, the router is able to receive multicast data. To stop receiving multicast data, a router must send an RGMP leave message to the Catalyst 6500 series switch. To disable RGMP on a router, the router must send an RGMP bye message to the Catalyst 6500 series switch. Table 32-1 provides a summary of the RGMP packet types.
Table 32-1 RGMP Packet Types
Description Hello Bye Join
Action When RGMP is enabled on the router, no multicast data traffic is sent to the router by the Catalyst 6500 series switch unless an RGMP join is specifically sent for a group. When RGMP is disabled on the router, all multicast data traffic is sent to the router by the Catalyst 6500 series switch. Multicast data traffic for a multicast MAC address from the Layer 3 group address G is sent to the router. These packets have group G in the Group Address field of the RGMP packet. Multicast data traffic for the group G is not sent to the router. These packets have group G in the group address field of the RGMP packet.
Leave
Default RGMP Configuration

RGMP is permanently enabled on Layer 2 LAN ports. RGMP is disabled by default on Layer 3 interfaces.
RGMP Configuration Guidelines and Restrictions

When configuring RGMP, follow these guidelines and restrictions:

Either RGMP or PIM snooping can be enabled in a VLAN but not both. RGMP supports PIM sparse mode. RGMP does not support PIM dense mode. RGMP explicitly supports the two AutoRP groups in dense mode by not restricting traffic to those groups but by flooding it to all router ports. For this reason, you should configure PIM sparse-dense mode. If you configure groups other than the AutoRP groups for dense mode, their traffic will not be correctly forwarded through router ports that have been enabled for RGMP. To effectively constrain multicast traffic with RGMP, connect RGMP-enabled routers to separate ports on RGMP-enabled Catalyst 6500 series switches. (VLAN interfaces satisfy this restriction.) RGMP only constrains traffic that exits through LAN ports on which it detects an RGMP-enabled router. If a non-RGMP enabled router is detected on a LAN port, that port receives all multicast traffic. RGMP does not support directly connected multicast sources in the network. A directly connected multicast source will send multicast traffic into the network without signaling through RGMP or PIM. This multicast traffic will not be received by an RGMP-enabled router unless the router already
32-2
OL-3999-08
Chapter 32
Configuring RGMP Enabling RGMP on Layer 3 Interfaces
requested receipt of that multicast group through RGMP. This restriction applies to hosts and to functions in routers that source multicast traffic, such as the ping and mtrace commands and multicast applications that source multicast traffic, such as UDPTN.

RGMP supports directly connected receivers in the network. Traffic to these receivers will be constrained by IGMP snooping, or if the receiver is a router itself, by PIM and RGMP. CGMP is not supported in networks where RGMP is enabled on routers. You cannot enable both RGMP and CGMP on a Layer 3 interface. If RGMP is enabled on a Layer 3 interface, CGMP is silently disabled and vice versa. The following properties of RGMP are the same as for IGMP snooping:
RGMP constrains traffic based on the multicast group, not on the senders IP address. If spanning tree topology changes occur in the network, the state is not flushed as it is with
Cisco Group Management Protocol (CGMP).

RGMP does not constrain traffic for multicast groups 224.0.0.x (x = 0...255), which allows use
of PIMv2 bootstrap router (BSR) in an RGMP-controlled network.

RGMP in Cisco network devices operates on MAC addresses, not on IP multicast addresses.
Because multiple IP multicast addresses can map to one MAC address (see RFC 1112), RGMP cannot differentiate between the IP multicast groups that might map to a MAC address.
The capability of the Catalyst 6500 series switch to constrain traffic is limited by its
content-addressable memory (CAM) table capacity.
Enabling RGMP on Layer 3 Interfaces

To enable RGMP on a Layer 3 interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} Router(config-if)# ip rgmp Router(config-if)# no ip rgmp
Purpose Selects an interface to configure. Enables RGMP on the Layer 3 interface. Disables RGMP on the Layer 3 interface. Exits configuration mode. (Optional) Monitors RGMP.
Step 3 Step 4
Router(config-if)# end Router# debug ip rgmp [name_or_group_address] 1.
This example shows how to configure RGMP on FastEthernet port 3/3:

Router# configure terminal Enter configuration commands, one per line. Router(config)# interface fastethernet 3/3 Router(config-if)# ip rgmp Router(config-if)# end Router# End with CNTL/Z.
32-3
Chapter 32 Enabling RGMP on Layer 3 Interfaces
Configuring RGMP
Tip
32-4
OL-3999-08
C H A P T E R
33
Configuring Network Security

This chapter contains network security information unique to the Catalyst 6500 series switches, which supplements the network security information and procedures in these publications:
Cisco IOS Security Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html
Cisco IOS Security Command Reference, Release 12.2, at this URL http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
Note

Configuring MAC Address-Based Traffic Blocking, page 33-2 Configuring TCP Intercept, page 33-2 Configuring Unicast Reverse Path Forwarding Check, page 33-2
Tip
33-1
Chapter 33 Configuring MAC Address-Based Traffic Blocking
Configuring MAC Address-Based Traffic Blocking

To block all traffic to or from a MAC address in a specified VLAN, perform this task: Command
Router(config)# mac-address-table static mac_address vlan vlan_ID drop Router(config)# no mac-address-table static mac_address vlan vlan_ID
Purpose Blocks all traffic to or from the configured MAC address in the specified VLAN. Clears MAC address-based blocking.
This example shows how to block all traffic to or from MAC address 0050.3e8d.6400 in VLAN 12:
Router# configure terminal Router(config)# mac-address-table static 0050.3e8d.6400 vlan 12 drop
Configuring TCP Intercept

TCP intercept flows are processed in hardware. For configuration procedures, refer to the Cisco IOS Security Configuration Guide, Release 12.2, Traffic Filtering and Firewalls, Configuring TCP Intercept (Preventing Denial-of-Service Attacks), at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfdenl.html
Configuring Unicast Reverse Path Forwarding Check

These sections describe configuring Cisco IOS Unicast Reverse Path Forwarding check (Unicast RPF check):

Understanding PFC3 Unicast RPF Check Support, page 33-2 Understanding PFC2 Unicast RPF Check Support, page 33-3 Unicast RPF Check Guidelines and Restrictions, page 33-3 Configuring Unicast RPF Check, page 33-3
Understanding PFC3 Unicast RPF Check Support

For a complete explanation of how Unicast RPF check works, refer to the Cisco IOS Security Configuration Guide, Release 12.2, Other Security Features, Configuring Unicast Reverse Path Forwarding at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfrpf.html The PFC3 provides hardware support for RPF check of traffic from multiple interfaces. With strict-method Unicast RPF check, the PFC3 supports two parallel paths for all prefixes in the routing table, and up to four parallel paths for prefixes reached through any of four user-configurable RPF interface groups (each interface group can contain four interfaces).
33-2
OL-3999-08
Chapter 33
Configuring Network Security Configuring Unicast Reverse Path Forwarding Check
With loose-method Unicast RPF check (also known as exist-only method), the PFC3 supports up to eight reverse-path interfaces (the Cisco IOS software is limited to eight reverse paths in the routing table). There are four methods of performing Unicast RPF check in Cisco IOS:

Strict Unicast RPF check Strict Unicast RPF check with allow-default Loose Unicast RPF check Loose Unicast RPF check with allow-default
You configure Unicast RPF check on a per-interface basis, but the PFC3 supports only one Unicast RPF method for all interfaces that have Unicast RPF check enabled. When you configure an interface to use a Unicast RPF method that is different from the currently configured method, all other interfaces in the system that have Unicast RPF check enabled use the new method.
Understanding PFC2 Unicast RPF Check Support

The PFC2 supports Unicast RPF check with hardware processing for packets that have a single return path. The MSFC2 processes traffic in software that has multiple return paths (for example, load sharing).
Unicast RPF Check Guidelines and Restrictions

When configuring Unicast RPF check, follow these guidelines and restrictions:
If you configure Unicast RPF check to filter with an ACL, the PFC determines whether or not traffic matches the ACL. The PFC sends the traffic denied by the RPF ACL to the MSFC for the Unicast RPF check. Packets permitted by the ACL are forwarded in hardware without a Unicast RPF check (CSCdz35099). Because the packets in a denial-of-service attack typically match the deny ACE and are sent to the MSFC for the Unicast RPF check, they can overload the MSFC. The PFC provides hardware support for traffic that does not match the Unicast RPF check ACL, but that does match an input security ACL. The PFC does not provide hardware support Unicast RPF check for policy-based routing (PBR) traffic. (CSCea53554).
Configuring Unicast RPF Check

These sections describe how to configure Unicast RPF check:

Configuring the Unicast RPF Check Mode, page 33-3 Configuring the Multiple-Path Unicast RPF Check Mode on a PFC3, page 33-5 Enabling Self-Pinging, page 33-6
Configuring the Unicast RPF Check Mode

There are two Unicast RPF check modes:
Strict check mode, which verifies that the source IP address exists in the FIB table and verifies that the source IP address is reachable through the input port.
33-3
Chapter 33 Configuring Unicast Reverse Path Forwarding Check
Exist-only check mode, which only verifies that the source IP address exists in the FIB table.
Note
The most recently configured mode is automatically applied to all ports configured for Unicast RPF check. To configure Unicast RPF check mode, perform this task:
Command
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}
Purpose Selects an interface to configure.

Note
Based on the input port, Unicast RPF check verifies the best return path before forwarding the packet on to the next destination.
Step 2
Router(config-if)# ip verify unicast source reachable-via {rx | any} [allow-default] [list] Router(config-if)# no ip verify unicast
Configures the Unicast RPF check mode. Reverts to the default Unicast RPF check mode. Exits interface configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# exit Router# show mls cef ip rpf 1.
When configuring the Unicast RPF check mode, note the following information:

Use the rx keyword to enable strict check mode. Use the any keyword to enable exist-only check mode. Use the allow-default keyword to allow use of the default route for RPF verification. Use the list option to identify an access list.
If the access list denies network access, spoofed packets are dropped at the port. If the access list permits network access, spoofed packets are forwarded to the destination
address. Forwarded packets are counted in the interface statistics.

If the access list includes the logging action, information about the spoofed packets is sent to
the log server.
Note
When you enter the ip verify unicast source reachable-via command, the Unicast RPF check mode changes on all ports in the switch. This example shows how to enable Unicast RPF exist-only check mode on Gigabit Ethernet port 4/1:
Router(config)# interface gigabitethernet 4/1 Router(config-if)# ip verify unicast source reachable-via any Router(config-if)# end Router#
This example shows how to enable Unicast RPF strict check mode on Gigabit Ethernet port 4/2:
Router(config)# interface gigabitethernet 4/2 Router(config-if)# ip verify unicast source reachable-via rx Router(config-if)# end Router#
33-4
OL-3999-08
Chapter 33
Configuring Network Security Configuring Unicast Reverse Path Forwarding Check

Router# show running-config interface gigabitethernet 4/2 Building configuration... Current configuration : 114 bytes ! interface GigabitEthernet4/2 ip address 42.0.0.1 255.0.0.0 ip verify unicast reverse-path no cdp enable end Router# show running-config interface gigabitethernet 4/1 Building configuration... Current configuration : 114 bytes ! interface GigabitEthernet4/1 ip address 41.0.0.1 255.0.0.0 ip verify unicast reverse-path (RPF mode on g4/1 also changed to strict-check RPF mode) no cdp enable end Router#
Configuring the Multiple-Path Unicast RPF Check Mode on a PFC3

To configure the multiple-path Unicast RPF check mode on a PFC3, perform this task: Command
Step 1
Router(config)# mls ip cef rpf multipath {punt | pass | interface-group} Router(config)# no mls ip cef rpf multipath {punt | interface-group}
Purpose Configures the multiple path RPF check mode on a PFC3. Returns to the default (mls ip cef rpf multipath punt). Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls cef ip rpf
When configuring multiple path RPF check, note the following information:
punt (default)The PFC3 performs the Unicast RPF check in hardware for up to two interfaces per prefix. Packets arriving on any additional interfaces are redirected (punted) to the MSFC3 for Unicast RPF check in software. passThe PFC3 performs the Unicast RPF check in hardware for single-path and two-path prefixes. Unicast RPF check is disabled for packets coming from multipath prefixes with three or more reverse-path interfaces (these packets always pass the Unicast RPF check). interface-group The PFC3 performs the Unicast RPF check in hardware for single-path and two-path prefixes. The PFC3 also performs the Unicast RPF check for up to four additional interfaces per prefix through user-configured multipath Unicast RPF check interface groups. Unicast RPF check is disabled for packets coming from other multipath prefixes that have three or more reverse-path interfaces (these packets always pass the Unicast RPF check).
This example shows how to configure multiple path RPF check:

Router(config)# mls ip cef rpf multipath punt
33-5
Chapter 33 Configuring Unicast Reverse Path Forwarding Check
Configuring Multiple-Path Interface Groups on a PFC3

To configure multiple-path Unicast RPF interface groups on a PFC3, perform this task: Command
Step 1
Router(config)# mls ip cef rpf interface-group [0 | 1 | 2 | 3] interface1 [interface2 [interface3 [interface4]]] Router(config)# mls ip cef rpf interface-group group_number Router(config)# end Router# show mls cef ip rpf
Purpose Configures a multiple path RPF interface group on a PFC3. Removes an interface group. Exits configuration mode. Verifies the configuration.
This example shows how to configure interface group 2:

Router(config)# mls ip cef rpf interface-group 2 fastethernet 3/3 fastethernet 3/4 fastethernet 3/5 fastethernet 3/6
Enabling Self-Pinging
With Unicast RPF check enabled, by default the switch cannot ping itself. To enable self-pinging, perform this task: Command
Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} Router(config-if)# ip verify unicast source reachable-via any allow-self-ping Router(config-if)# no ip verify unicast source reachable-via any allow-self-ping
Purpose Selects the interface to configure. Enables the switch to ping itself or a secondary address. Disables self-pinging. Exits interface configuration mode.
Step 3
Router(config-if)# exit 1.
This example shows how to enable self-pinging:

Router(config)# interface gigabitethernet 4/1 Router(config-if)# ip verify unicast source reachable-via any allow-self-ping Router(config-if)# end
Tip
33-6
OL-3999-08
C H A P T E R
34
Understanding Cisco IOS ACL Support

This chapter describes Cisco IOS ACL support on the Catalyst 6500 series switches:

Cisco IOS ACL Configuration Guidelines and Restrictions, page 34-1 Hardware and Software ACL Support, page 34-2 Configuring IPv6 Address Compression, page 34-3 Optimized ACL Logging with a PFC3, page 34-5 Guidelines and Restrictions for Using Layer 4 Operators in ACLs, page 34-7
Note
For complete information about configuring Cisco IOS ACLs, see the Cisco IOS Security Configuration Guide, Release 12.2, Traffic Filtering and Firewalls, at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/sec_data_acl/configuration/12-2sx/sec-data-acl-12-2sx-book. html
Tip
Cisco IOS ACL Configuration Guidelines and Restrictions

The following guidelines and restrictions apply to Cisco IOS ACL configurations:

You can apply Cisco IOS ACLs directly to Layer 3 ports and to VLAN interfaces. You can apply VLAN ACLs (VACLs) to VLANs (refer to Chapter 35, Configuring VLAN ACLs). Each type of ACL (IP, IPX, and MAC) filters only traffic of the corresponding type. A Cisco IOS MAC ACL never matches IP or IPX traffic. The PFC does not provide hardware support for Cisco IOS IPX ACLs. Cisco IOS IPX ACLs are supported in software on the MSFC. By default, the MSFC sends Internet Control Message Protocol (ICMP) unreachable messages when a packet is denied by an access group.
34-1
Chapter 34 Hardware and Software ACL Support
With the ip unreachables command enabled (which is the default), the supervisor engine drops most of the denied packets in hardware and sends only a small number of packets to the MSFC to be dropped (10 packets per second, maximum), which generates ICMP-unreachable messages. To eliminate the load imposed on the MSFC CPU by the task of dropping denied packets and generating ICMP-unreachable messages, you can enter the no ip unreachables interface configuration command to disable ICMP unreachable messages, which allows all access group-denied packets to be dropped in hardware.

ICMP unreachable messages are not sent if a packet is denied by a VACL. We strongly recommend that you use named ACLs (rather than numbered ACLs) as this conserves CPU usage when creating or modifying ACL configurations and during system restarts. When you create ACL entries (or modify existing ACL entries), the software performs a CPU-intensive operation called an ACL merge to load the ACL configurations into the PFC hardware. An ACL merge also occurs when the startup configuration is applied during a system restart. With named ACLs, the ACL Merge is triggered only when the user exits the named-acl configuration mode. However with numbered ACLs, the ACL Merge is triggered for every ACE definition and results in a number of intermediate merges during ACL configuration.
Hardware and Software ACL Support

Access control lists (ACLs) can be processed in hardware by the Policy Feature Card (PFC), a Distributed Forwarding Card (DFC), or in software by the Multilayer Switch Feature Card (MSFC). The following behavior describes software and hardware handling of ACLs:

ACL flows that match a deny statement in standard and extended ACLs (input and output) are dropped in hardware if ip unreachables is disabled. ACL flows that match a permit statement in standard and extended ACLs (input and output) are processed in hardware. VLAN ACL (VACL) flows are processed in hardware. If a field specified in the VACL match clause statement is not supported by hardware processing the field is ignored (for example the log keyword in and ACL used for the match clause statement), or the whole configuration is rejected (for example, a VACL containing IPX ACL parameters). VACL logging is processed in software, using the action clause. VACL logging is processed in software. Dynamic ACL flows are processed in hardware. Idle timeout is processed in software.
Note
Idle timeout is not configurable. Catalyst 6500 series switches do not support the access-enable host timeout command.
Except on MPLS interfaces, reflexive ACL flows are processed in hardware after the first packet in a session is processed in software on the RP. IP accounting for an ACL access violation on a given port is supported by forwarding all denied packets for that port to the MSFC for software processing without impacting other flows. The PFC does not provide hardware support for Cisco IOS IPX ACLs. Cisco IOS IPX ACLs are supported in software on the MSFC. Extended name-based MAC address ACLs are supported in hardware.
34-2
OL-3999-08
Chapter 34
Understanding Cisco IOS ACL Support Configuring IPv6 Address Compression
The following ACL types are processed in software:

Internetwork Packet Exchange (IPX) access lists Standard XNS access list Extended XNS access list DECnet access list Extended MAC address access list Protocol type-code access list
Note
IP packets with a header length of less than five will not be access controlled.
Unless you configure optimized ACL logging (OAL), flows that require logging are processed in software without impacting nonlogged flow processing in hardware (see the Optimized ACL Logging with a PFC3 section on page 34-5). The forwarding rate for software-processed flows is substantially less than for hardware-processed flows. When you enter the show ip access-list command, the match count displayed does not include packets processed in hardware. When you enter the show policy-map interface command, sometimes the counters that are displayed do not include all of the hardware switching platform counters.
Configuring IPv6 Address Compression

Access control lists (ACLs) are implemented in hardware in the Policy Feature Card (PFC), which uses the source or destination IP address and port number in the packet to index the ACL table. The index has a maximum address length of 128 bits. The IP address field in an IPv6 packet is 128 bits, and the port field is 16 bits. To use full IPv6 addresses in the ACL hardware table, you can turn on compression of IPv6 addresses using the mls ipv6 acl compress address unicast command. This feature compresses the IPv6 address (including port) into 128 bits by removing 16 unused bits from the IPv6 address. Compressible address types can be compressed without losing any information. See Table 34-1 for details about the compression methods. Release 12.2(17a)SX and later releases support the IPv6 compression command on the Supervisor Engine 720. The command is not supported on Supervisor Engine 2. By default, the command is set for no compression.
Caution
Do not enable the compression mode if you have noncompressible address types in your network. A list of compressible address types and the address compression method are listed in Table 34-1.
34-3
Chapter 34 Configuring IPv6 Address Compression
Table 34-1 Compressible Address Types and Methods
Address Type EUI-64 based on MAC address
Compression Method This address is compressed by removing 16 bits from bit locations [39:24]. No information is lost when the hardware compresses these addresses. This address is compressed by removing the upper 16 bits. No information is lost when the hardware compresses these addresses. These addresses are compressed by removing the zeros in bits [95:80] and are identified using the same packet type as the embedded IPv4 address. No information is lost when the hardware compresses these addresses. If the IPv6 address does not fall into any of the above categories, it is classified as other. If the IPv6 address is classified as other, the following occurs:
Embedded IPv4 address
Link Local
Others
If the compress mode is on, the IPv6 address is compressed similarly to the EUI-64 compression method (removal of bits [39:24]) to allow for the Layer 4 port information to be used as part of the key used to look up the QoS TCAM, but Layer 3 information is lost. If the global compression mode is off, the entire 128 bits of the IPv6 address are used. The Layer 4 port information cannot be included in the key to look up the QoS TCAM because of the size constraints on the IPv6 lookup key.
To turn on the compression of IPv6 addresses, enter the mls ipv6 acl compress address unicast command. To turn off the compression of IPv6 addresses, enter the no form of this command. This example shows how to turn on address compression for IPv6 addresses:
Router(config)# mls ipv6 acl compress address unicast Router(config)#
This example shows how to turn off address compression for IPv6 addresses:
Router(config)# no mls ipv6 acl compress address unicast Router(config)#
34-4
OL-3999-08
Chapter 34
Understanding Cisco IOS ACL Support Optimized ACL Logging with a PFC3
Optimized ACL Logging with a PFC3

Note
Supervisor Engine 2 does not support optimized ACL logging (OAL). Release 12.2(17d)SXB and later releases support OAL with a PFC3. These sections describe OAL:

Understanding OAL, page 34-5 OAL Guidelines and Restrictions, page 34-5 Configuring OAL, page 34-6
Understanding OAL
Optimized ACL Logging (OAL) provides hardware support for ACL logging. Unless you configure OAL, packets that require logging are processed completely in software on the MSFC. OAL permits or drops packets in hardware on the PFC3 and uses an optimized routine to send information to the MSFC3 to generate the logging messages.
OAL Guidelines and Restrictions

The following guidelines and restrictions apply to OAL:

OAL and VACL capture are incompatible. Do not configure both features on the switch. With OAL configured, use SPAN to capture traffic. OAL is supported only on the PFC3. OAL supports only IPv4 unicast packets. OAL supports VACL logging of permitted ingress traffic. OAL does not support port ACLs (PACLs). OAL does not provide hardware support for the following:
Reflexive ACLs ACLs used to filter traffic for other features (for example, QoS) ACLs for unicast reverse path forwarding (uRPF) check exceptions Exception packets (for example, TTL failure and MTU failure) Packets with IP options Packets addressed at Layer 3 to the router Packets sent to the MSFC3 to generate ICMP unreachable messages Packets being processed by features not accelerated in hardware
To provide OAL support for denied packets, enter the mls rate-limit unicast ip icmp unreachable acl-drop 0 command. OAL and the mls verify ip length minimum command are incompatible. Do not configure both.
34-5
Chapter 34 Optimized ACL Logging with a PFC3
Configuring OAL
These sections describe how to configure OAL:

Configuring OAL Global Parameters, page 34-6 Configuring OAL on an Interface, page 34-7 Displaying OAL Information, page 34-7 Clearing Cached OAL Entries, page 34-7
Note
For complete syntax and usage information for the commands used in this section, refer to the Cisco IOS Master Command List, Release 12.2SX. To provide OAL support for denied packets, enter the mls rate-limit unicast ip icmp unreachable acl-drop 0 command.
Configuring OAL Global Parameters

To configure global OAL parameters, perform this task: Command
Router(config)# logging ip access-list cache {{entries number_of_entries} | {interval seconds} | {rate-limit number_of_packets} | {threshold number_of_packets}} Router(config)# no logging ip access-list cache {entries | interval | rate-limit | threshold}
Purpose Sets OAL global parameters.
Reverts OAL global parameters to defaults.
When configuring OAL global parameters, note the following information:
entries number_of_entries:
Sets the maximum number of entries cached. Range: 01,048,576 (entered without commas). Default: 8192.
interval seconds:
Sets the maximum time interval before an entry is sent to be logged. Also if the entry is inactive
for this duration it is removed from the cache.

Range: 586,400 (1440 minutes or 24 hours, entered without commas). Default: 300 seconds (5 minutes).
rate-limit number_of_packets:
Sets the number of packets logged per second in software. Range: 101,000,000 (entered without commas). Default: 0 (rate limiting is off and all packets are logged).
34-6
OL-3999-08
Chapter 34
Understanding Cisco IOS ACL Support Guidelines and Restrictions for Using Layer 4 Operators in ACLs
threshold number_of_packets:
Sets the number of packet matches before an entry is logged. Range: 11,000,000 (entered without commas). Default: 0 (logging is not triggered by the number of packet matches).
Configuring OAL on an Interface

To configure OAL on an interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type
1
Purpose
slot/port}
Specifies the interface to configure. Enables OAL for ingress traffic on the interface. Disables OAL on the interface. Enables OAL for egress traffic on the interface. Disables OAL on the interface.
Router(config-if)# logging ip access-list cache in Router(config-if)# no logging ip access-list cache
Step 3
Router(config-if)# logging ip access-list cache out Router(config-if)# no logging ip access-list cache 1. type = any that supports Layer 3-switched traffic.
Displaying OAL Information

To display OAL information, perform this task: Command
Router # show logging ip access-list cache
Purpose Displays OAL information.
Clearing Cached OAL Entries

To clear cached OAL entries, perform this task: Command
Router # clear logging ip access-list cache
Purpose Clears cached OAL entries.
Guidelines and Restrictions for Using Layer 4 Operators in ACLs

These sections describe guidelines and restrictions when configuring ACLs that include Layer 4 port operations:

Determining Layer 4 Operation Usage, page 34-8 Determining Logical Operation Unit Usage, page 34-8
34-7
Chapter 34 Guidelines and Restrictions for Using Layer 4 Operators in ACLs
Determining Layer 4 Operation Usage

You can specify these types of operations:

gt (greater than) lt (less than) neq (not equal) eq (equal) range (inclusive range)
We recommend that you do not specify more than nine different operations on the same ACL. If you exceed this number, each new operation might cause the affected ACE to be translated into more than one ACE. Use the following two guidelines to determine Layer 4 operation usage:
Layer 4 operations are considered different if the operator or the operand differ. For example, in this ACL there are three different Layer 4 operations (gt 10 and gt 11 are considered two different Layer 4 operations):
... gt 10 permit ... lt 9 deny ... gt 11 deny
Note
There is no limit to the use of eq operators as the eq operator does not use a logical operator unit (LOU) or a Layer 4 operation bit. See the Determining Logical Operation Unit Usage section on page 34-8 for a description of LOUs.
Layer 4 operations are considered different if the same operator/operand couple applies once to a source port and once to a destination port. For example, in this ACL there are two different Layer 4 operations because one ACE applies to the source port and one applies to the destination port.
... Src gt 10 ... ... Dst gt 10
Determining Logical Operation Unit Usage

Logical operation units (LOUs) are registers that store operator-operand couples. All ACLs use LOUs. There can be up to 32 LOUs; each LOU can store two different operator-operand couples with the exception of the range operator. LOU usage per Layer 4 operation is as follows:

gt uses 1/2 LOU lt uses 1/2 LOU neq uses 1/2 LOU range uses 1 LOU eq does not require a LOU
For example, this ACL would use a single LOU to store two different operator-operand couples:
... Src gt 10 ... ... Dst gt 10
34-8
OL-3999-08
Chapter 34
Understanding Cisco IOS ACL Support Guidelines and Restrictions for Using Layer 4 Operators in ACLs
A more detailed example follows:

ACL1 ... (dst ... (dst ... (dst ... (dst ... (src ... (dst ACL2 ... (dst ... (src ... (src ... (dst port) port) port) port) port) port) gt 10 permit lt 9 deny gt 11 deny neq 6 permit neq 6 deny gt 10 deny
port) port) port) port)
gt 20 deny lt 9 deny range 11 13 deny neq 6 permit
The Layer 4 operations and LOU usage is as follows:

ACL1 Layer 4 operations: 5 ACL2 Layer 4 operations: 4 LOUs: 4 LOU 1 stores gt 10 and lt 9 LOU 2 stores gt 11 and neq 6 LOU 3 stores gt 20 (with space for one more) LOU 4 stores range 11 13 (range needs the entire LOU)
An explanation of the LOU usage follows:

Tip
34-9
Chapter 34 Guidelines and Restrictions for Using Layer 4 Operators in ACLs
34-10
OL-3999-08
C H A P T E R
35
Configuring VLAN ACLs

This chapter describes how to configure VLAN ACLs (VACLs) on Catalyst 6500 series switches.
Note
With a Supervisor Engine 720 and releases earlier than Release 12.2(17d)SXB, VACL capture is supported only for use with the WS-SVC-IDSM2-K9 Intrusion Detection System Module 2 and the WS-SVC-NAM-2 and WS-SVC-NAM-1 network analysis modules. This restriction is removed in Release 12.2(17d)SXB and later releases. OAL and VACL capture are incompatible. Do not configure both features on the switch. With OAL configured (see the Optimized ACL Logging with a PFC3 section on page 34-5), use SPAN to capture traffic.

Understanding VACLs, page 35-1 Configuring VACLs, page 35-4 Configuring VACL Logging, page 35-11
Tip
Understanding VACLs
These sections describe VACLs:

VACL Overview, page 35-2 Bridged Packets, page 35-2
35-1
Chapter 35 Understanding VACLs
Routed Packets, page 35-3 Multicast Packets, page 35-4
VACL Overview
VACLs can provide access control for all packets that are bridged within a VLAN or that are routed into or out of a VLAN or a WAN interface for VACL capture. Unlike regular Cisco IOS standard or extended ACLs that are configured on router interfaces only and are applied on routed packets only, VACLs apply to all packets and can be applied to any VLAN or WAN interface. VACLS are processed in hardware. VACLs use Cisco IOS ACLs. VACLs ignore any Cisco IOS ACL fields that are not supported in hardware. You can configure VACLs for IP, IPX, and MAC-Layer traffic. VACLs applied to WAN interfaces support only IP traffic for VACL capture. When you configure a VACL and apply it to a VLAN, all packets entering the VLAN are checked against this VACL. If you apply a VACL to the VLAN and an ACL to a routed interface in the VLAN, a packet coming in to the VLAN is first checked against the VACL and, if permitted, is then checked against the input ACL before it is handled by the routed interface. When the packet is routed to another VLAN, it is first checked against the output ACL applied to the routed interface and, if permitted, the VACL configured for the destination VLAN is applied. If a VACL is configured for a packet type and a packet of that type does not match the VACL, the default action is deny.
Note
TCP Intercepts and Reflexive ACLs take precedence over a VACL action if these are configured on the same interface. VACLs and CBAC cannot be configured on the same interface. IGMP packets are not checked against VACLs. When VACL capture is configured with Policy Based Routing (PBR) on the same interface, do not select BDD as the ACL merge algorithm. We recommend using ODM, the default ACL merge algorithm for the Supervisor Engine 720.
Bridged Packets
Figure 35-1 shows a VACL applied on bridged packets.
Figure 35-1 Applying VACLs on Bridged Packets
VACL MSFC Supervisor Engine Host A (VLAN 10) Host B (VLAN 20)
120528
Bridged
35-2
OL-3999-08
Chapter 35
Configuring VLAN ACLs Understanding VACLs
Routed Packets
Figure 35-2 shows how ACLs are applied on routed and Layer 3-switched packets. For routed or Layer 3-switched packets, the ACLs are applied in the following order:
1. 2. 3. 4.
VACL for input VLAN Input Cisco IOS ACL Output Cisco IOS ACL VACL for output VLAN
Figure 35-2 Applying VACLs on Routed Packets
Routed
Input IOS ACL Bridged VACL
Output IOS ACL MSFC VACL Bridged
Supervisor Engine
120554
Host A (VLAN 10)
Host B (VLAN 20)
35-3
Chapter 35 Configuring VACLs
Multicast Packets
Figure 35-3 shows how ACLs are applied on packets that need multicast expansion. For packets that need multicast expansion, the ACLs are applied in the following order:
1.
Packets that need multicast expansion:

a. VACL for input VLAN b. Input Cisco IOS ACL
2.
Packets after multicast expansion:

a. Output Cisco IOS ACL b. VACL for output VLAN
3.
Packets originating from routerVACL for output VLAN
Figure 35-3 Applying VACLs on Multicast Packets
IOS ACL for output VLAN for packets originating from router Routed Input IOS ACL Bridged VACL Supervisor Engine Host B (VLAN 20)
120555
MSFC
Output IOS ACL VACL (Not supported on PFC2)
Host A (VLAN 10)
Bridged Host D (VLAN 20)
Host C (VLAN 10)
Configuring VACLs
These sections describe how to configure VACLs:

VACL Configuration Overview, page 35-5 Defining a VLAN Access Map, page 35-5 Configuring a Match Clause in a VLAN Access Map Sequence, page 35-6 Configuring an Action Clause in a VLAN Access Map Sequence, page 35-7 Applying a VLAN Access Map, page 35-8
35-4
OL-3999-08
Chapter 35
Configuring VLAN ACLs Configuring VACLs
Verifying VLAN Access Map Configuration, page 35-8 VLAN Access Map Configuration and Verification Examples, page 35-9 Configuring a Capture Port, page 35-9
VACL Configuration Overview

VACLs use standard and extended Cisco IOS IP and IPX ACLs, and MAC Layer-named ACLs (see the Configuring MAC ACLs section on page 41-67) and VLAN access maps. VLAN access maps can be applied to VLANs or to WAN interfaces for VACL capture. VACLs attached to WAN interfaces support only standard and extended Cisco IOS IP ACLs. Each VLAN access map can consist of one or more map sequences, each sequence with a match clause and an action clause. The match clause specifies IP, IPX, or MAC ACLs for traffic filtering and the action clause specifies the action to be taken when a match occurs. When a flow matches a permit ACL entry, the associated action is taken and the flow is not checked against the remaining sequences. When a flow matches a deny ACL entry, it will be checked against the next ACL in the same sequence or the next sequence. If a flow does not match any ACL entry and at least one ACL is configured for that packet type, the packet is denied. To use access control for both bridged and routed traffic, you can use VACLs alone or a combination of VACLs and ACLs. You can define ACLs on the VLAN interfaces to use access control for both the input and output routed traffic. You can define a VACL to use access control for the bridged traffic. The following caveats apply to ACLs when used with VACLs:

Packets that require logging on the outbound ACLs are not logged if they are denied by a VACL. VACLs are applied on packets before NAT translation. If the translated flow is not subject to access control, the flow might be subject to access control after the translation because of the VACL configuration.
The action clause in a VACL can be forward, drop, capture, or redirect. Traffic can also be logged. VACLs applied to WAN interfaces do not support the redirect or log actions.
Note
VACLs have an implicit deny at the end of the map; a packet is denied if it does not match any ACL entry, and at least one ACL is configured for the packet type. If an empty or undefined ACL is specified in a VACL, any packets will match the ACL and the associated action is taken. VACLs cannot be applied to IGMP, MLD, or PIM traffic.
Defining a VLAN Access Map

To define a VLAN access map, perform this task: Command
Router(config)# vlan access-map map_name [0-65535]
Purpose Defines the VLAN access map. Optionally, you can specify the VLAN access map sequence number.
35-5
Command
Router(config)# no vlan access-map map_name 0-65535 Router(config)# no vlan access-map map_name
Purpose Deletes a map sequence from the VLAN access map. Deletes the VLAN access map.
When defining a VLAN access map, note the following information:

To insert or modify an entry, specify the map sequence number. If you do not specify the map sequence number, a number is automatically assigned. You can specify only one match clause and one action clause per map sequence. Use the no keyword with a sequence number to remove a map sequence. Use the no keyword without a sequence number to remove the map.
See the VLAN Access Map Configuration and Verification Examples section on page 35-9.
Configuring a Match Clause in a VLAN Access Map Sequence

To configure a match clause in a VLAN access map sequence, perform this task: Command
Router(config-access-map)# match {ip address {1-199 | 1300-2699 | acl_name} | ipx address {800-999 | acl_name}| mac address acl_name} Router(config-access-map)# no match {ip address {1-199 | 1300-2699 | acl_name} | ipx address {800-999 | acl_name}| mac address acl_name}
Purpose Configures the match clause in a VLAN access map sequence.
Deletes the match clause in a VLAN access map sequence.
When configuring a match clause in a VLAN access map sequence, note the following information:

You can select one or more ACLs. VACLs attached to WAN interfaces support only standard and extended Cisco IOS IP ACLs. Use the no keyword to remove a match clause or specified ACLs in the clause. For information about named MAC-Layer ACLs, refer to the Configuring MAC ACLs section on page 41-67. For information about Cisco IOS ACLs, refer to the Cisco IOS Security Configuration Guide, Release 12.2, Traffic Filtering and Firewalls, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html
35-6
OL-3999-08
Chapter 35
Configuring an Action Clause in a VLAN Access Map Sequence

To configure an action clause in a VLAN access map sequence, perform this task: Command
Router(config-access-map)# action {drop [log]} | {forward [capture]} | {redirect {{ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port} | {port-channel channel_id}} Router(config-access-map)# no action {drop [log]} | {forward [capture]} | {redirect {{ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port} | {port-channel channel_id}}
Purpose Configures the action clause in a VLAN access map sequence. Deletes the action clause in from the VLAN access map sequence.
When configuring an action clause in a VLAN access map sequence, note the following information:

You can set the action to drop, forward, forward capture, or redirect packets. VACLs applied to WAN interfaces support only the forward capture action. VACLs applied to WAN interfaces do not support the drop, forward, or redirect actions. Forwarded packets are still subject to any configured Cisco IOS security ACLs. The capture action sets the capture bit for the forwarded packets so that ports with the capture function enabled can receive the packets. Only forwarded packets can be captured. For more information about the capture action, see the Configuring a Capture Port section on page 35-9. VACLs applied to WAN interfaces do not support the log action. When the log action is specified, dropped packets are logged in software. Only dropped IP packets can be logged. The redirect action allows you to specify up to five interfaces, which can be physical interfaces or EtherChannels. You cannot specify packets to be redirected to an EtherChannel member or a VLAN interface. The redirect interface must be in the VLAN for which the VACL access map is configured. With a PFC3, if a VACL is redirecting traffic to an egress SPAN source port, SPAN does not copy the VACL-redirected traffic. With a PFC2, if a VACL is redirecting traffic to an egress SPAN source port, SPAN copies the VACL-redirected traffic. SPAN and RSPAN destination ports transmit VACL-redirected traffic. Use the no keyword to remove an action clause or specified redirect interfaces.
35-7
Applying a VLAN Access Map

To apply a VLAN access map, perform this task: Command
Router(config)# vlan filter map_name {vlan-list vlan_list | interface type1 number2} 1. type = pos, atm , or serial 2. number = slot/port or slot/port_adapter /port; can include a subinterface or channel group descriptor
Purpose Applies the VLAN access map to the specified VLANs or WAN interfaces.
When applying a VLAN access map, note the following information:

You can apply the VLAN access map to one or more VLANs or WAN interfaces. The vlan_list parameter can be a single VLAN ID or a comma-separated list of VLAN IDs or VLAN ID ranges (vlan_IDvlan_ID). If you delete a WAN interface that has a VACL applied, the VACL configuration on the interface is also removed. You can apply only one VLAN access map to each VLAN or WAN interface. VACLs applied to VLANs are active only for VLANs with a Layer 3 VLAN interface configured. Applying a VLAN access map to a VLAN without a Layer 3 VLAN interface creates an administratively down Layer 3 VLAN interface to support the VLAN access map. VACLs applied to VLANs are inactive if the Layer 2 VLAN does not exist or is not operational. You cannot apply a VACL to a secondary private VLAN. VACLs applied to primary private VLANs also apply to secondary private VLANs. Use the no keyword to clear VLAN access maps from VLANs or WAN interfaces.
Verifying VLAN Access Map Configuration

To verify VLAN access map configuration, perform this task: Command
Router# show vlan access-map [map_name]
Purpose Verifies VLAN access map configuration by displaying the content of a VLAN access map. Verifies VLAN access map configuration by displaying the mappings between VACLs and VLANs.
Router# show vlan filter [access-map map_name | vlan vlan_id | interface type1 number2] 1. type = pos, atm , or serial
2. number = slot/port or slot/port_adapter /port; can include a subinterface or channel group descriptor
35-8
OL-3999-08
Chapter 35
VLAN Access Map Configuration and Verification Examples

Assume IP-named ACL net_10 and any_host are defined as follows:
Router# show ip access-lists net_10 Extended IP access list net_10 permit ip 10.0.0.0 0.255.255.255 any Router# show ip access-lists any_host Standard IP access list any_host permit any
This example shows how to define and apply a VLAN access map to forward IP packets. In this example, IP traffic matching net_10 is forwarded and all other IP packets are dropped due to the default drop action. The map is applied to VLAN 12 to 16.
Router(config)# vlan access-map thor 10 Router(config-access-map)# match ip address net_10 Router(config-access-map)# action forward Router(config-access-map)# exit Router(config)# vlan filter thor vlan-list 12-16
This example shows how to define and apply a VLAN access map to drop and log IP packets. In this example, IP traffic matching net_10 is dropped and logged and all other IP packets are forwarded:
Router(config)# vlan access-map ganymede 10 Router(config-access-map)# match ip address net_10 Router(config-access-map)# action drop log Router(config-access-map)# exit Router(config)# vlan access-map ganymede 20 Router(config-access-map)# match ip address any_host Router(config-access-map)# action forward Router(config-access-map)# exit Router(config)# vlan filter ganymede vlan-list 7-9
This example shows how to define and apply a VLAN access map to forward and capture IP packets. In this example, IP traffic matching net_10 is forwarded and captured and all other IP packets are dropped:
Router(config)# vlan access-map mordred 10 Router(config-access-map)# match ip address net_10 Router(config-access-map)# action forward capture Router(config-access-map)# exit Router(config)# vlan filter mordred vlan-list 2, 4-6
Configuring a Capture Port

A port configured to capture VACL-filtered traffic is called a capture port.
Note
To apply IEEE 802.1Q or ISL tags to the captured traffic, configure the capture port to trunk unconditionally (see the Configuring the Layer 2 Switching Port as an ISL or 802.1Q Trunk section on page 10-8 and the Configuring the Layer 2 Trunk Not to Use DTP section on page 10-9).
35-9
To configure a capture port, perform this task: Command

Step 1 Step 2
Router(config)# interface {{type
1
Purpose
slot/port}
Specifies the interface to configure. (Optional) Filters the captured traffic on a per-destination-VLAN basis. The default is all. Clears the configured destination VLAN list and returns to the default value (all). Configures the port to capture VACL-filtered traffic. Disables the capture function on the interface.
Router(config-if)# switchport capture allowed vlan {add | all | except | remove} vlan_list Router(config-if)# no switchport capture allowed vlan
Step 3
Router(config-if)# switchport capture Router(config-if)# no switchport capture 1.
When configuring a capture port, note the following information:

You can configure any port as a capture port. The vlan_list parameter can be a single VLAN ID or a comma-separated list of VLAN IDs or VLAN ID ranges (vlan_IDvlan_ID). To encapsulate captured traffic, configure the capture port with the switchport trunk encapsulation command (see the Configuring a Layer 2 Switching Port as a Trunk section on page 10-8) before you enter the switchport capture command. For unencapsulated captured traffic, configure the capture port with the switchport mode access command (see the Configuring a LAN Interface as a Layer 2 Access Port section on page 10-14) before you enter the switchport capture command. The capture port supports only egress traffic. No traffic can enter the switch through a capture port.
This example shows how to configure a Fast Ethernet interface 5/1 as a capture port:
Router(config)# interface gigabitEthernet 5/1 Router(config-if)# switchport capture Router(config-if)# end
This example shows how to display VLAN access map information:

Router# show vlan access-map mordred Vlan access-map "mordred" 10 match: ip address net_10 action: forward capture Router#
This example shows how to display mappings between VACLs and VLANs. For each VACL map, there is information about the VLANs that the map is configured on and the VLANs that the map is active on. A VACL is not active if the VLAN does not have an interface.
Router# show vlan filter VLAN Map mordred: Configured on VLANs: Active on VLANs: Router#
2,4-6 2,4-6
35-10
OL-3999-08
Chapter 35
Configuring VLAN ACLs Configuring VACL Logging
Configuring VACL Logging

When you configure VACL logging, IP packets that are denied generate log messages in these situations:

When the first matching packet is received For any matching packets received during the last 5-minute interval If the threshold is reached before the 5-minute interval
Log messages are generated on a per-flow basis. A flow is defined as packets with the same IP addresses and Layer 4 (UDP or TCP) port numbers. When a log message is generated, the timer and packet count is reset. These restrictions apply to VACL logging:

Because of the rate-limiting function for redirected packets, VACL logging counters may not be accurate. Only denied IP packets are logged.
To configure VACL logging, use the action drop log command action in VLAN access map submode (see the Configuring VACLs section on page 35-4 for configuration information) and perform this task in global configuration mode to specify the global VACL logging parameters: Command
Step 1
Router(config)# vlan access-log maxflow max_number
Purpose Sets the log table size. The content of the log table can be deleted by setting the maxflow number to 0. The default is 500 with a valid range of 0 to 2048. When the log table is full, logged packets from new flows are dropped by the software. Sets the maximum redirect VACL logging packet rate. The default packet rate is 2000 packets per second with a valid range of 0 to 5000. Packets exceeding the limit are dropped by the hardware. Sets the logging threshold. A logging message is generated if the threshold for a flow is reached before the 5-minute interval. By default, no threshold is set. Exits VLAN access map configuration mode. (Optional) Displays the configured VACL logging properties. (Optional) Displays the content of the VACL log table.
Step 2
Router(config)# vlan access-log ratelimit pps
Step 3
Router(config)# vlan access-log threshold pkt_count
Router(config)# exit Router# show vlan access-log config
Router# show vlan access-log flow protocol {{src_addr src_mask} | any | {host {hostname | host_ip}}} {{dst_addr dst_mask} | any | {host {hostname | host_ip}}} [vlan vlan_id] Router# show vlan access-log statistics
Step 7
(Optional) Displays packet and message counts and other statistics.
This example shows how to configure global VACL logging in hardware:

Router(config)# vlan access-log maxflow 800 Router(config)# vlan access-log ratelimit 2200 Router(config)# vlan access-log threshold 4000
35-11
Chapter 35 Configuring VACL Logging
Tip
35-12
OL-3999-08
C H A P T E R
36
Configuring Denial of Service Protection

This chapter contains information on how to protect your Catalyst 6500 series switch against Denial of Service (DoS) attacks. The information covered in this chapter is unique to the Catalyst 6500 series switches, and it supplements the network security information and procedures in the Configuring Network Security chapter in this publication as well as the network security information and procedures in these publications:
Cisco IOS Security Configuration Guide, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html Cisco IOS Security Command Reference, Release 12.2, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
Note

Understanding How DoS Protection Works, page 36-2 DoS Protection Default Configuration, page 36-22 DoS Protection Configuration Guidelines and Restrictions, page 36-23 Understanding How Control Plane Policing Works, page 36-28 CoPP Default Configuration, page 36-29 CoPP Configuration Guidelines and Restrictions, page 36-29 Configuring CoPP, page 36-30 Monitoring CoPP, page 36-31 Defining Traffic Classification, page 36-32
36-1
Chapter 36 Understanding How DoS Protection Works
Tip
Understanding How DoS Protection Works

The following sections contain an overview of the DoS protection on the Catalyst 6500 series switch and describe some types of DoS attack scenarios:

DoS Protection with a PFC2, page 36-2 DoS Protection with a PFC3, page 36-10
DoS Protection with a PFC2

This section contains information about the available methods to counteract DoS attacks with a PFC2 and includes configuration examples. The following sections describe these protection methods:

Security ACLs, page 36-2 Security ACLs, page 36-2 QoS ACLs, page 36-3 FIB Rate Limiting, page 36-4 ARP Throttling, page 36-5 uRPF Check, page 36-5 TCP Intercept, page 36-6
Security ACLs
The Catalyst 6500 series switch can deny DoS packets in hardware using security access control lists (ACLs). Security ACLs are applied in hardware using the TCAM to traffic that can be easily identified using Layer 3 or Layer 4 data. You can apply security ACLs preventively before a DoS attack occurs or after an attack has been identified. This example shows how a security ACL is used to drop DoS packets:
Router# clear mls ip mod 9 Router# show mls ip mod 9 Displaying Netflow entries in module 9 DstIP SrcIP Prot:SrcPort:DstPort Src i/f:AdjPtr -------------------------------------------------------------------Pkts Bytes Age LastSeen Attributes --------------------------------------------------192.168.0.0 192.168.1.0 0 :0 :0 0 : 0 1843 84778 2 02:30:17 L3 - Dynamic 192.168.1.0 192.168.0.0 0 :0 :0 0 : 0 2742416 126151136 2 02:30:17 L3 - Dynamic <== Note: traffic flow identified Router# configure terminal
36-2
OL-3999-08
Chapter 36
Configuring Denial of Service Protection Understanding How DoS Protection Works
Enter configuration commands, one per line. End with CNTL/Z. Router(config)# no access-list 199 Router(config)# access-list 199 deny ip host 192.168.0.0 any Router(config)# access-list 199 permit ip any any Router(config)# interface g9/1 Router(config-if)# ip access 199 in <======== Note: security ACL applied Router(config-if)# end Router# 1w6d: %SYS-5-CONFIG_I: Configured from console by console Router# clear mls ip mod 9 Router# show mls ip mod 9 Displaying Netflow entries in module 9 DstIP SrcIP Prot:SrcPort:DstPort Src i/f:AdjPtr -------------------------------------------------------------------Pkts Bytes Age LastSeen Attributes --------------------------------------------------192.168.0.0 192.168.1.0 0 :0 :0 0 : 0 1542 70932 2 02:31:56 L3 - Dynamic 192.168.1.0 192.168.0.0 0 :0 :0 0 : 0 0 0 2 02:31:56 L3 - Dynamic <======== Note: hardware-forwarded <======== Note: traffic stopped Extended IP access list 199 deny ip host 192.168.0.0 any (100 matches) permit ip any any Router# show access-list 199 Extended IP access list 199 deny ip host 192.168.0.0 any (103 matches permit ip any any Router #
Security VACLs
Security virtual access lists (VACLs) are security-enforcement tools based on Layer 2, Layer 3, and Layer 4 information. The result of a security VACL lookup against a packet can be a permit, a deny, a permit and capture, or a redirect. When you associate a security VACL with a particular VLAN, all traffic must be permitted by the security VACL before the traffic is allowed into the VLAN. Security VACLs are enforced in hardware, so there is no performance penalty for applying security VACLs to a VLAN on the Catalyst 6500 series switches.
QoS ACLs
Unlike security ACLs, QoS ACLs can be used to limit the rate of traffic without denying access to all the traffic in a flow. This example shows how to use a QoS ACL to prevent a ping attack on a switch. A QoS ACL is configured and applied on all interfaces to limit the rate of incoming ICMP echo packets.
Router# show ip ospf neighbors Neighbor ID Pri State Dead Time Address Interface 6.6.6.122 1 FULL/BDR 00:00:30 6.6.6.122 Vlan46 Router# show ip eigrp neighbors IP-EIGRP neighbors for process 200 H Address Interface Hold Uptime SRTT RTO Q Seq Type (sec) (ms) Cnt Num 0 4.4.4.122 Vl44 11 00:06:07 4 200 0 6555 Router# <======== Note: ping attack starts Router# show proc cpu | include CPU utilization CPU utilization for five seconds: 99%/90%; one minute: 48%; five minutes: 25% Router#
36-3
2w0d: %OSPF-5-ADJCHG: Process 100, Nbr 6.6.6.122 on Vlan46 from FULL to DOWN, Neighbor Down: Dead timer expired Router# show ip eigrp neighbors IP-EIGRP neighbors for process 200 Router# Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# access-list 199 permit icmp any any echo Router(config)# class-map match-any icmp Router(config-cmap)# match access-group 199 Router(config-cmap)# exit Router(config)# policy-map icmp Router(config-pmap)# class icmp Router(config-pmap-c)# police 96000 16000 16000 conform-action transmit exceed-action drop Router(config-pmap-c)# exit Router(config-pmap)# exit Router(config)# interface range g4/1 - 9 Router(config-if-range)# service-policy input icmp <======== Note: policy applied Router(config-if-range)# end 2w0d: %SYS-5-CONFIG_I: Configured from console by console 2w0d: %OSPF-5-ADJCHG: Process 100, Nbr 6.6.6.122 on Vlan46 from LOADING to FULL, Loading Done Router# show ip eigrp neighbors IP-EIGRP neighbors for process 200 H Address Interface Hold Uptime SRTT RTO Q Seq Type (sec) (ms) Cnt Num 0 4.4.4.122 Vl44 13 00:00:48 8 200 0 6565 Router#
FIB Rate Limiting

Note
The PFC2 CPU rate limiters are off by default. The forwarding information base (FIB) rate-limiting feature allows all packets that require software processing to be rate limited. This example shows traffic destined for a nonexistent host address on a locally connected subnet. Normally, the ARP request would result in an ARP reply and the installation of a FIB adjacency for this traffic. However, the adjacency in the FIB for the destination subnet would continue to receive traffic that would be forwarded for software processing. By applying rate-limiting to this traffic, the rate of traffic forwarded for software processing can be limited to a manageable amount.
Router# show ip eigrp neighbors IP-EIGRP neighbors for process 200 H Address Interface 0 4.4.4.122 Vl44 Router# show ip ospf neighbors
Hold Uptime SRTT (sec) (ms) 11 00:00:26 8
RTO
Q Seq Type Cnt Num 200 0 6534
Neighbor ID Pri State Dead Time Address Interface 6.6.6.122 1 FULL/BDR 00:00:36 6.6.6.122 Vlan46 Router# <===================== Note: attack starts Router# show arp | include 199.2.250.250 Internet 199.2.250.250 0 Incomplete ARPA Router# 1w6d: %OSPF-5-ADJCHG: Process 100, Nbr 6.6.6.122 on Vlan46 from FULL to DOWN, Neighbor Down: Dead timer expired Router# show ip eigrp neighbors IP-EIGRP neighbors for process 200 Router#
36-4
OL-3999-08
Chapter 36
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls rate-limit unicast cef receive 1000 <====== Note: traffic rate limited to 1000 pps Router(config)# end Router# 1w6d: %SYS-5-CONFIG_I: Configured from console by console Router# 1w6d: %OSPF-5-ADJCHG: Process 100, Nbr 6.6.6.122 on Vlan46 from LOADING to FULL, Loading Done Router# show ip eigrp neighbors IP-EIGRP neighbors for process 200 H Address Interface Hold Uptime SRTT RTO Q Seq Type (sec) (ms) Cnt Num 0 4.4.4.122 Vl44 12 00:00:07 12 200 0 6536 Router#
Traffic Storm Control

A traffic storm occurs when packets flood the LAN, which creates excessive traffic and degrades network performance. The traffic storm control feature prevents LAN ports from being disrupted by a broadcast, multicast, or unicast traffic storm on physical interfaces from either mistakes in network configurations or from users issuing a DoS attack. Traffic storm control (also called traffic suppression) monitors incoming traffic levels over a 1-second traffic storm control interval. During the interval, traffic storm control compares the traffic level with the configured traffic storm control level. The traffic storm control level is a percentage of the total available bandwidth of the port. Each port has a single traffic storm control level that is used for all types of traffic (broadcast, multicast, and unicast). Traffic storm control is configured on an interface and is disabled by default. The configuration example here enables broadcast address storm control on interface FastEthernet 2/3 to a level of 20 percent. When the broadcast traffic exceeds the configured level of 20 percent of the total available bandwidth of the port within a 1-second traffic-storm-control interval, traffic storm control will drop all broadcast traffic until the end of the traffic-storm-control interval.
Router(config-if)# storm-control broadcast level 20
The Catalyst 6500 series switch supports broadcast storm control on all LAN ports and multicast and unicast storm control on Gigabit Ethernet ports. When two or three suppression modes are configured simultaneously, they share the same level settings. If broadcast suppression is enabled, and if multicast suppression is also enabled and configured at a 70-percent threshold, the broadcast suppression will also have a setting for 70 percent. For more information about configuring traffic storm control see Chapter 39, Configuring Traffic Storm Control.
ARP Throttling
ARP throttling can be used to automatically install hardware-based FIB and adjacency entries to drop packets during ARP resolution. Most of these packets are dropped, but a small number are sent to the MSFC (rate limited).
uRPF Check
When you enable the unicast reverse path forwarding (uRPF) check, packets that lack a verifiable source IP address, such as spoofed IP source addresses, are discarded. Cisco Express Forwarding (CEF) tables are used to verify that the source addresses and the interfaces on which they were received are consistent with the FIB tables on the supervisor engine.
36-5
After you enable uRPF check on an interface (per-VLAN basis), the incoming packet is compared to the CEF tables through a reverse lookup. If the packet is received from one of the reverse path routes, the packet is forwarded. If there is no reverse path route on the interface on which the packet was received, the packet fails the uRPF check and is either dropped or forwarded, depending on whether an ACL is applied to the uRPF check fail traffic. If no ACL is specified in the CEF tables, then the forged packets are immediately dropped. You can only specify an ACL for the uRPF check for packets that fail the uRPF check. The ACL checks whether the packet should immediately be dropped or forwarded. The uRPF check with ACL is not supported in any PFC3 in hardware. Packets that are denied in the uRPF ACL are forwarded in hardware. Packets that are permitted are sent to the CPU. The uRPF check with a PFC2 is supported in hardware but with only one return path. However, all packets that fail the uRPF check, and are forwarded because of an applied ACL, can be sent and rate limited to the MSFC to generate ICMP unreachable messages; these actions are all software driven. The uRPF check in hardware is supported for routes with up to two return paths (interfaces) and up to six return paths with interface groups configured (two from the FIB table and four from the interface groups)
TCP Intercept
TCP intercept protects recipients of TCP traffic from TCP SYN-flooding DoS attacks. A normal TCP connection starts with a three-way handshake. Host A sends a SYN request to Host B requesting the start of a new TCP session. Host B responds with a SYN ACK acknowledging the receipt of the SYN request. Host A then returns an ACK for Host Bs SYN ACK, and the session commences. A SYN-flooding attack occurs when hackers flood servers with requests for connections that have unreachable return addresses. The three-way handshake is never completed, and the connections cannot be established. The amount of session requests to which the server host is responding can overwhelm the server host and prevent legitimate users from connecting to legitimate services, such as web sites and email servers. TCP intercept prevents the SYN flooding by intercepting and validating TCP requests. TCP intercept supports the following modes:
Intercept modeThe TCP intercept software intercepts TCP synchronization (SYN) packets from clients to servers that match an extended access list. The software establishes a connection with the client on behalf of the destination server, and if successful, establishes the connection with the server on behalf of the client and connects the two half-connections together transparently. Connection attempts from unreachable hosts will never reach the server. The software continues to intercept and forward packets throughout the duration of the connection. In the case of illegitimate requests from potential hackers, the softwares aggressive timeouts on half-open connections and its thresholds on TCP connection requests protect destination servers while still allowing valid requests. When establishing the network security policy using TCP intercept, you can choose to intercept all requests or only those coming from specific networks or destined for specific servers. You also can configure the connection rate and threshold of outstanding connections.
Watch modeThe software passively watches the connection requests flowing through the switch. If a connection fails to get established in a configurable interval, the software intervenes and terminates the connection attempt.
Because TCP intercept can operate in either active intercept mode or passive watch mode, it is important to decide which mode is suitable for the network, and to configure your network accordingly. TCP intercept is hardware-assisted on the PFC2 and PFC3 (all types). Configuring many sources and destinations for active intercept mode may overrun the CPU, so it is recommended that only critical servers be protected with active intercept mode.
36-6
OL-3999-08
Chapter 36
The default mode of operation is intercept mode. In intercept mode, the software actively intercepts each incoming connection request (SYN) and responds on behalf of the server with the SYN-ACK, and then waits for the ACK from the client. After the preparation is complete, the original SYN is sent to the server, and the software performs the three-way handshake with the server. The two halves are connected together. In Watch mode, the connection requests pass through the switch to the server, but are watched until they become established. If they fail to become established within 30 seconds (this value is configurable), the software sends a reset to the server to clear up its state. Configuring switches for watch mode has less CPU impact than intercept mode. In watch mode, the CPU is not performing checks and connects on both halves of the connection. The CPU is passively monitoring the connection and acting on failed connections after the fact. TCP intercept is configured globally by first creating the extended access list for the traffic to be intercepted, and then creating the TCP intercept list. The type of traffic to be intercepted must be one of the following:

All requests Only the requests that come from specific networks Only the requests that are destined for specific servers
This example defines the source in the access list as any; it does not attempt to filter the source address because it is difficult to know exactly who to intercept packets from. The destination, is specified to protect the destination servers from the TCP SYN-flood attack. If an access list match is not found, traffic is permitted to pass without further action.
Router(config)# access-list 101 permit tcp any 10.1.1.1 0.0.0.255 Router(config)# ip tcp intercept list 101
Table 36-1 lists the command used to configure the TCP intercept.
Table 36-1 TCP Intercept Configuration
Command
Router(config)# access-list access-list-number {deny | permit} tcp any destination destination-wildcard Router(config)# ip tcp intercept list access-list-number Router(config)# ip tcp intercept mode {intercept | watch} Router(config)# ip tcp intercept drop-mode {oldest | random} Router(config)# ip tcp intercept watch-timeout seconds Router(config)# ip tcp intercept finrst-timeout seconds
Purpose Defines an IP extended access list.
Enables TCP intercept. Sets the TCP intercept mode. Sets the drop mode. Changes the time allowed to reach established state; valid values are from 1 to 2147483 seconds. Changes the time between receipt of a reset or FIN-exchange and dropping the connection; valid values are from 1 to 2147483 seconds. Changes the time the software will manage a connection after no activity; valid values are from 1 to 2147483 seconds.
Router(config)# ip tcp intercept connection-timeout seconds
36-7
Table 36-1 TCP Intercept Configuration (continued)
Command
Router(config)# ip tcp intercept max-incomplete low number
Purpose Defines the number of incomplete connections below which the software leaves aggressive mode; valid values are from 1 to 2147483647 connections. Defines the maximum number of incomplete connections allowed before the software enters aggressive mode; valid values are from 1 to 2147483647 connections. Defines the number of connection requests below which the software leaves aggressive mode; valid values are from 1 to 2147483647 connections. Defines the number of connection requests received in the last one-minutes sample period before the software enters aggressive mode; valid values are from 1 to 2147483647 connections. Displays incomplete connections and established connections. Displays TCP intercept statistics.
Router(config)# ip tcp intercept max-incomplete high number
Router(config)# ip tcp intercept one-minute low number
Router(config)# ip tcp intercept one-minute high number
Router# show tcp intercept connections
Router# show tcp intercept statistics
Hardware-Based Rate Limiters on the PFC2

The PFC2 supports additional hardware-based rate limiters. The PFC2 provides four rate-limiter registers for the new rate limiters, which are configured globally on the switch. These rate-limiter registers are present in the Layer 3 forwarding engine (PFC) and are responsible for containing rate-limiting information for result packets that match the various available configured rate limiters. Because four rate-limiter registers are present on the Layer 3 forwarding engine only, these registers can force different rate-limiting scenarios to share the same register. The registers are assigned on a first-come, first-serve basis. If all registers are being utilized, the only way to configure another rate limiter is to free one register. The hardware-based rate limiters available on the PFC2 are as follows:

Ingress and egress ACL bridged packets FIB receive and FIB glean cases VACL log Layer 3 features
Ingress-Egress ACL Bridged Packets (Unicast Only)

This rate limiter rate limits packets sent to the MSFC because of an ingress/egress ACL bridge result. The switch accomplishes this by altering existing and new ACL TCAM entries with a TCAM bridge result to a Layer 3 redirect result pointing to the MSFC. Packets hitting the TCAM entries with the altered Layer 3 redirect rate limit result will be rate limited according to the instructions set in CLI by the network administrator. Both the ingress and egress values will be the same, as they both share the same rate-limiter register. If the ACL bridge ingress/egress rate limiting is disabled, the Layer 3 redirect rate limit results are converted to the bridge result.
36-8
OL-3999-08
Chapter 36
Ingress or egress ACL-bridged packet cases share a single rate-limiter register. If the feature is turned on, ingress and egress ACLs use the same rate-limiter value. This example shows how to rate limit the unicast packets from an ingress ACL bridge result to 50000 packets per second, and 50 packets in burst:
Router(config)# mls rate-limit unicast acl input 50000 50
This example shows how to rate limit the unicast packets from an ingress ACL bridge result to the same rate (50000 pps and 50 packets in burst) for egress ACL bridge results:
Router(config)# mls rate-limit unicast acl output 50000 50
If the values of the rate limiter are altered on either the ingress or the egress when both are enabled, both values are changed to that new value. In the following example, the output rate is changed to 40000 pps:
When you enter the show mls rate-limit command, both the ACL bridged in and the ACL bridged out display the new value of 40000 pps:
Router# sh mls rate-limit Load for five secs: 0%/0%; one minute: 0%; five minutes: 0% Time source is NTP, 10:32:15.584 PDT Fri Aug 5 2005 Rate Limiter Type ----------------ACL BRIDGE IN ACL BRIDGE OUT L3_SEC_FEATURES VACL LOG FIB RECEIVE FIB GLEAN Status ---------Off Off Off Off Off Off Packets/s ---------
FIB (CEF) Receive and FIB Glean Cases (Unicast Only)

The FIB receive rate limiter provides the capability to rate limit all packets that contain the MSFC IP address as the destination address. The rate limiters do not discriminate between good frames and bad frames.
Note
Do not enable the FIB receive rate limiter if you are using CoPP. The FIB receive rate limiter overrides the CoPP policies. This example shows how to rate limit the traffic to 25000 pps with a burst of 60:
Router(config)# mls rate-limit unicast cef receive 25000 60
The FIB glean rate limiter does not limit ARP traffic, but provides the capability to rate limit traffic that requires address resolution (ARP) and requires that it be sent to the MSFC. This situation occurs when traffic enters a port and contains the destination of a host on a subnet that is locally connected to the MSFC, but no ARP entry exists for that destination host. In this case, because the MAC address of the destination host will not be answered by any host on the directly connected subnet that is unknown, the glean adjacency is hit and the traffic is sent directly to the MSFC for ARP resolution. This rate limiter limits the possibility of an attacker overloading the CPU with such ARP requests. This example shows how to rate limit the rate at which this traffic is sent to the MSFC to 20000 pps and a burst of 60:
Router(config)# mls rate-limit unicast cef glean 20000 60
36-9
VACL Log (Unicast Only)

Packets that are sent to the MSFC because of VLAN-ACL logging can be rate limited to ensure that the CPU is not overwhelmed with logging tasks. VACLs are processed in hardware, but the MSFC does the logging. When VACL logging is configured on the switch, IP packets that are denied in the VACL generate log messages. This example shows how to rate limit logging requests to 5000 pps (the range for this rate limiter is from 10 to 5000 pps):
Router(config)# mls rate-limit unicast acl vacl-log 5000
Layer 3 Security Features (Unicast Only)

Some security features are processed by first being sent to the MSFC. For these security features, you need to rate limit the number of these packets being sent to the MSFC to reduce any potential overloading. The security features include authentication proxy (auth-proxy), IPSEC, and inspection. Authentication proxy is used to authenticate inbound or outbound users or both. These users are normally blocked by an access list, but with auth-proxy, the users can bring up a browser to go through the firewall and authenticate on a terminal access controller access control system plus (TACACS+) or RADIUS server (based on the IP address). The server passes additional access list entries down to the switch to allow the users through after authentication. These ACLs are stored and processed in software, and if there are many users utilizing auth-proxy, the MSFC may be overwhelmed. Rate limiting would be advantageous in this situation. IPSec and inspection are also done by the MSFC and may require rate limiting. When the Layer 3 security feature rate limiter is enabled, all Layer 3 rate limiters for auth-proxy, IPSec and inspection are enabled at the same rate. This example shows how to rate limit the security features to the MSFC to 100000 pps with a burst of 10 packets:
Router(config)# mls rate-limit unicast ip features 100000 10
DoS Protection with a PFC3

This section contains information about the available methods to counteract DoS attacks with a PFC3 and includes configuration examples. The PFC3 provides a layered defense against DoS attacks using the following methods:

CPU rate limitersControls traffic types. Control plane policing (CoPP)Filters and rate limits control plane traffic. For information about CoPP, see the Understanding How Control Plane Policing Works section on page 36-28. Security ACLs and VACLs, page 36-11 QoS Rate Limiting, page 36-12 uRPF Check, page 36-12 Traffic Storm Control, page 36-13 Network Under SYN Attack, page 36-13 ARP Policing, page 36-14 Recommended Rate-Limiter Configuration, page 36-14
These sections describe DoS protection with a PFC3:

36-10
OL-3999-08
Chapter 36
Hardware-Based Rate Limiters on the PFC3, page 36-15

Ingress-Egress ACL Bridged Packets (Unicast Only), page 36-15 uRPF Check Failure, page 36-16 TTL Failure, page 36-16 ICMP Unreachable (Unicast Only), page 36-17 FIB (CEF) Receive Cases (Unicast Only), page 36-17 FIB Glean (Unicast Only), page 36-17 Layer 3 Security Features (Unicast Only), page 36-18 ICMP Redirect (Unicast Only), page 36-18 VACL Log (Unicast Only), page 36-18 MTU Failure, page 36-19 Layer 2 PDU, page 36-19 Layer 2 Protocol Tunneling, page 36-19 IP Errors, page 36-20 Layer 2 Multicast IGMP Snooping, page 36-19 IPv4 Multicast, page 36-20 IPv6 Multicast, page 36-21
Security ACLs and VACLs

If the network is under a DoS attack, ACLs can be an efficient method for dropping the DoS packets before they reach the intended target. Use security ACLs if an attack is detected from a particular host. In this example, the host 10.1.1.10 and all traffic from that host is denied:
Router(config)# access-list 101 deny ip host 10.1.1.10 any Router(config)# access-list 101 permit ip any any
Security ACLs also protect against the spoofing of addresses. For example, assume that a source address A is on the inside of a network and a switch interface that is pointing to the Internet. You can apply an inbound ACL on the switch Internet interface that denies all addresses with a source of A (the inside address). This action stops attacks where the attackers spoof inside source addresses. When the packet arrives at the switch interface, it matches on that ACL and drops the packet before it causes damage. When the Catalyst 6500 series switch is used with a Cisco Intrusion Detection Module (CIDM), you can dynamically install the security ACL as a response to the detection of the attack by the sensing engine. VACLs are a security enforcement tool based on Layer 2, Layer 3, and Layer 4 information. The result of a VACL lookup against a packet can be a permit, a deny, a permit and capture, or a redirect. When you associate a VACL with a particular VLAN, all traffic must be permitted by the VACL before the traffic is allowed into the VLAN. VACLs are enforced in hardware, so there is no performance penalty for applying VACLs to a VLAN on the Catalyst 6500 series switches.
36-11
QoS Rate Limiting

QoS ACLs limit the amount of a particular type of traffic that is processed by the MSFC3. If a DoS attack is initiated against the MSFC, QoS ACLs can prevent the DoS traffic from reaching the MSFC data path and congesting it. The PFC3 performs QoS in hardware, which offers an efficient means of limiting DoS traffic (once that traffic has been identified) to protect the switch from impacting the MSFC. For example, if the network is experiencing ping-of-death or smurf attacks, the administrator should rate limit the ICMP traffic to counteract the DoS attack and still allow legitimate traffic through the processor, or allow it to be forwarded to the MSFC or host. This rate limiting configuration must be done for each flow that should be rate limited and the rate-limiting policy action should be applied to the interface. In the following example, the access-list 101 permits and identifies ping (echo) ICMP messages from any source to any destination as traffic. Within the policy map, a policing rule defines a specified committed information rate (CIR) and burst value (96000 bps and 16000 bps) to rate limit the ping (ICMP) traffic through the chassis. The policy map then is applied to an interface or VLAN. If the ping traffic exceeds the specified rate on the VLAN or interface where the policy map is applied, it is dropped as specified in the markdown map (the markdown map for the normal burst configurations is not shown in the example).
Router(config)# access-list 101 permit icmp any any echo Router(config)# class-map match-any icmp_class Router(config-cmap)# match access-group 101 Router(config-cmap)# exit Router(config)# policy-map icmp_policer Router(config-pmap)# class icmp_class Router(config-pmap-c)# police 96000 16000 conform-action transmit exceed-action policed-dscp-transmit drop Router(config-pmap-c)# exit Router(config-pmap)# exit
uRPF Check
When you enable the unicast reverse path forwarding (uRPF) check, packets that lack a verifiable source IP address, such as spoofed IP source addresses, are discarded. Cisco Express Forwarding (CEF) tables are used to verify that the source addresses and the interfaces on which they were received are consistent with the FIB tables on the supervisor engine. After you enable uRPF check on an interface (per-VLAN basis), the incoming packet is compared to the CEF tables through a reverse lookup. If the packet is received from one of the reverse path routes, the packet is forwarded. If there is no reverse path route on the interface on which the packet was received, the packet fails the uRPF check and is either dropped or forwarded, depending on whether an ACL is applied to the uRPF check fail traffic. If no ACL is specified in the CEF tables, then the forged packets are immediately dropped. You can only specify an ACL for the uRPF check for packets that fail the uRPF check. The ACL checks whether the packet should immediately be dropped or forwarded. The uRPF check with ACL is not supported in any PFC3 in hardware. Packets that are denied in the uRPF ACL are forwarded in hardware. Packets that are permitted are sent to the CPU. The uRPF check with a PFC3 is supported in hardware; it is also supported in hardware with a PFC2, but with only one return path. However, all packets that fail the uRPF check, and are forwarded because of an applied ACL, can be sent and rate limited to the MSFC to generate ICMP unreachable messages; these actions are all software driven. The uRPF check in hardware is supported for routes with up to two return paths (interfaces) and up to six return paths with interface groups configured (two from the FIB table and four from the interface groups).
36-12
OL-3999-08
Chapter 36
Traffic Storm Control

A traffic storm occurs when packets flood the LAN, which creates excessive traffic and degrades network performance. The traffic storm control feature prevents LAN ports from being disrupted by a broadcast, multicast, or unicast traffic storm on physical interfaces from either mistakes in network configurations or from users issuing a DoS attack. Traffic storm control (also called traffic suppression) monitors incoming traffic levels over a 1-second traffic storm control interval. During the interval, traffic storm control compares the traffic level with the configured traffic storm control level. The traffic storm control level is a percentage of the total available bandwidth of the port. Each port has a single traffic storm control level that is used for all types of traffic (broadcast, multicast, and unicast). Traffic storm control is configured on an interface and is disabled by default. The configuration example here enables broadcast address storm control on interface FastEthernet 2/3 to a level of 20 percent. When the broadcast traffic exceeds the configured level of 20 percent of the total available bandwidth of the port within a 1-second traffic-storm-control interval, traffic storm control will drop all broadcast traffic until the end of the traffic-storm-control interval.
Router(config-if)# storm-control broadcast level 20
The Catalyst 6500 series switch supports broadcast storm control on all LAN ports and multicast and unicast storm control on Gigabit Ethernet ports. When two or three suppression modes are configured simultaneously, they share the same level settings. If broadcast suppression is enabled, and if multicast suppression is also enabled and configured at a 70-percent threshold, the broadcast suppression will also have a setting for 70 percent.
Network Under SYN Attack

A network under a SYN attack is easily recognized. The target host becomes unusually slow, crashes, or suspends operation. Traffic returned from the target host can also cause trouble on the MSFC because return traffic goes to randomized source addresses of the original packets, lacks the locality of real IP traffic, and may overflow route caches, or CEF tables. When the network is under a SYN attack, the TCP intercept feature becomes aggressively defensive. Two factors determine when aggressive behavior on the switch begins and ends:

The total incomplete connections Connection requests during the last one-minute sample period
Both factors are configured with low and high values. If the number of incomplete connections exceed 1,100, or the number of connections arriving in the last one-minute period exceed 1,100, each new arriving connection causes the oldest partial connection (or a random connection) to be deleted. These are the default values, which can be altered. When either of the thresholds is exceeded, the TCP intercept assumes the server is under attack and goes into aggressive mode with the following reactions:

Each new arriving connection causes the oldest partial (or random partial) to be deleted. The initial retransmission timeout is reduced by half to 0.5 seconds, and so the total time trying to establish the connection is cut in half. In watch mode, the watch timeout is reduced by half.
36-13
Note
When both thresholds fall below the configured low value, the aggressive behavior ceases (default value is 900 in both factors). See Table 36-1 for information about TCP intercept configuration.
TCP flows are hardware assisted on both the PFC2 and PFC3 (all PFC3 types).
ARP Policing
During an attack, malicious users may try to overwhelm the MSFC CPU with control packets such as routing protocol or ARP packets. These special control packets can be hardware rate limited using a specific routing protocol and an ARP policing mechanism configurable with the mls qos protocol command. The routing protocols supported include RIP, BGP, LDP, OSPF, IS-IS, IGRP, and EIGRP. For example, the command mls qos protocol arp police 32000 rate limits ARP packets in hardware at 32,000 bps. Although this policing mechanism effectively protects the MSFC CPU against attacks such as line-rate ARP attacks, it does not only police routing protocols and ARP packets to the switch but also polices traffic through the box with less granularity than CoPP. The policing mechanism shares the root configuration with a policing-avoidance mechanism. The policing-avoidance mechanism lets the routing protocol and ARP packets flow through the network when they reach a QoS policer. This mechanism can be configured using the mls qos protocol protocol pass-through command. This example shows how to display the available protocols to use with ARP policing.
Router(config)# mls qos protocol ? isis eigrp ldp ospf rip bgp ospfv3 bgpv2 ripng neigh-discover wlccp arp
This example shows how to display the available keywords to use with the mls qos protocol arp command:
Router(config)# pass-through police precedence mls qos protocol arp ? pass-through keyword police keyword change ip-precedence(used to map the dscp to cos value)
Recommended Rate-Limiter Configuration

The recommended rate-limiter configuration is as follows:

Enable the rate limiters for the traffic types most likely to be used in a DoS attack. Do not use a rate limiter on VACL logging unless you configure VACL logging. Disable redirects because a platform that supports hardware forwarding, such as the Catalyst 6500 series switch, reduces the need for redirects.
36-14
OL-3999-08
Chapter 36
Disable unreachables because a platform that supports hardware unreachables, such as the Catalyst 6500 series switch, reduces the need for unreachables. Do not enable the MTU rate limiter if all interfaces have the same MTU. When configuring the Layer 2 PDU rate limiter, note the following information:
Calculate the expected or possible number of valid PDUs and double or triple the number. PDUs include BPDUs, DTP, VTP, PAgP, LACP, UDLD, etc. Rate limiters do not discriminate between good frames or bad frames.
Hardware-Based Rate Limiters on the PFC3

The PFC3 supports additional hardware-based rate limiters. The PFC3 provides eight rate-limiter registers for the new rate limiters, which are configured globally on the switch. These rate-limiter registers are present in the Layer 3 forwarding engine (PFC) and are responsible for containing rate-limiting information for result packets that match the various available configured rate limiters. Because eight rate-limiter registers are present on the PFC3, these registers can force different rate-limiting scenarios to share the same register. The registers are assigned on a first-come, first-serve basis. If all registers are being utilized, the only way to configure another rate limiter is to free one register. The hardware-based rate limiters available on the PFC3 are as follows:

Ingress and egress ACL bridged packets uRPF check failures FIB receive cases FIB glean cases Layer 3 security features ICMP redirects ICMP unreachable (ACL drop) No-route (FIB miss) VACL log TTL failure MTU failure Multicast IPv4 Multicast IPv6
Ingress-Egress ACL Bridged Packets (Unicast Only)

This rate limiter rate limits packets sent to the MSFC because of an ingress/egress ACL bridge result. The switch accomplishes this by altering existing and new ACL TCAM entries with a TCAM bridge result to a Layer 3 redirect result pointing to the MSFC. Packets hitting the TCAM entries with the altered Layer 3 redirect rate limit result will be rate limited according to the instructions set in CLI by the network administrator. Both the ingress and egress values will be the same, as they both share the same rate-limiter register. If the ACL bridge ingress/egress rate limiting is disabled, the Layer 3 redirect rate limit results are converted to the bridge result. Ingress or egress ACL-bridged packet cases share a single rate-limiter register. If the feature is turned on, ingress and egress ACLs use the same rate-limiter value.
36-15
Burst values regulate how many packets can be allowed in a burst. Each allowed packet consumes a token and a token must be available for a packet to be allowed. One token is generated per millisecond. When packets are not coming in, tokens can be accumulated up to the burst value. For example, if the burst value is set to 50, the switch can accumulate up to 50 tokens and absorb a burst of 50 packets. This example shows how to rate limit the unicast packets from an ingress ACL bridge result to 50000 packets per second, and 50 packets in burst:
Router(config)# mls rate-limit unicast acl input 50000 50
This example shows how to rate limit the unicast packets from an ingress ACL bridge result to the same rate (50000 pps and 50 packets in burst) for egress ACL bridge results:
If the values of the rate limiter are altered on either the ingress or the egress when both are enabled, both values are changed to that new value. In the following example, the output rate is changed to 40000 pps:
When you enter the show mls rate-limit command, both the ACL bridged in and the ACL bridged out display the new value of 40000 pps:
Router# show mls rate-limit Rate Limiter Type Status -----------------------------MCAST NON RPF Off MCAST DFLT ADJ On MCAST DIRECT CON Off ACL BRIDGED IN On ACL BRIDGED OUT On IP FEATURES Off Packets/s --------100000 40000 40000 Burst ----100 50 50
uRPF Check Failure

The uRPF check failure rate limiter allows you to configure a rate for the packets that need to be sent to the MSFC because they failed the uRPF check. The uRPF checks validate that incoming packets on an interface are from a valid source, which minimizes the potential threat of DoS attacks from users using spoofed addresses. When spoofed packets fail the uRPF check, those failures can be sent to the MSFC. The uRPF check rate limiters allow you to rate limit the packets per second that are bridged to the MSFC CPU when a uRPF check failure occurs. This example shows how to rate limit the uRPF check failure packets sent to the MSFC to 100000 pps with a burst of 100 packets:
Router(config)# mls rate-limit unicast ip rpf-failure 100000 100
TTL Failure
This rate limiter rate limits packets sent to the MSFC because of a time-to-live (TTL) check failure. As indicated by the all keyword in the following example, this rate limiter applies to both multicast and unicast traffic.
Note
The TTL failure rate limiter is not supported for IPv6 multicast. This example shows how to rate limit the TTL failures to 70000 pps with a burst of 150:
Router(config)# mls rate-limit all ttl-failure 70000 150
36-16
OL-3999-08
Chapter 36
For packets having TTL value equal to 1, configure MLS ttl-failure rate-limiter for CPU protection. The following are a few exceptions:

When the incoming traffic also requires ARP resolution (known network, unknown host), use glean rate-limiter. When the incoming traffic is also destined to the IP of the router, use receive-rate limiter. When the incoming traffic is also receiving input ACL bridged (for example, ACL log), use acl bridge input rate-limiter.
ICMP Unreachable (Unicast Only)

In an ICMP unreachable attack, a device is flooded with a large number of packets that contain a destination address that is unreachable from the flooded device (in this case, the MSFC). The ICMP unreachable rate limiter allows you to rate limit the packets that are sent to the MSFC containing unreachable addresses. This example shows how to rate limit the packets that are sent to the MSFC because of an ACL drop to 10000 pps and a burst of 100:
Router(config)# mls rate-limit unicast ip icmp unreachable acl-drop 10000 100
This example shows how to rate limit the packets that require generation of ICMP-unreachable messages because of a FIB miss to 80000 pps and burst to 70:
Router(config)# mls rate-limit unicast ip icmp unreachable no-route 80000 70
The four rate limiters, ICMP unreachable no route, ICMP unreachable ACL drop, IP errors, and IP RPF failure, share a single rate-limiter register. If any of these limiters are enabled, all of the limiters in this group will share the same value and sometimes the same state (for example, ON/ON/ON). When verifying the rate limiters, if the members of this register are enabled through another feature, an ON-Sharing status (instead of an ON status) is displayed. The exception is the TTL failure rate limiter: its value shares the same value as the other members in the register if you have manually enabled the feature.
FIB (CEF) Receive Cases (Unicast Only)

The FIB receive rate limiter provides the capability to rate limit all packets that contain the MSFC IP address as the destination address. The rate limiters do not discriminate between good frames and bad frames.
Note
Do not enable the FIB receive rate limiter if you are using CoPP. The FIB receive rate limiter overrides the CoPP policies. This example shows how to rate limit the traffic to 25000 pps with a burst of 60:
Router(config)# mls rate-limit unicast cef receive 25000 60
FIB Glean (Unicast Only)

The FIB glean rate limiter does not limit ARP traffic, but provides the capability to rate limit traffic that requires address resolution (ARP) and requires that it be sent to the MSFC. This situation occurs when traffic enters a port and contains the destination of a host on a subnet that is locally connected to the MSFC, but no ARP entry exists for that destination host. In this case, because the MAC address of the
36-17
destination host will not be answered by any host on the directly connected subnet that is unknown, the glean adjacency is hit and the traffic is sent directly to the MSFC for ARP resolution. This rate limiter limits the possibility of an attacker overloading the CPU with such ARP requests. This example shows how to rate limit the rate at which this traffic is sent to the MSFC to 20000 pps and a burst of 60:
Router(config)# mls rate-limit unicast cef glean 20000 60
Layer 3 Security Features (Unicast Only)

Some security features are processed by first being sent to the MSFC. For these security features, you need to rate limit the number of these packets being sent to the MSFC to reduce any potential overloading. The security features include authentication proxy (auth-proxy), IPSEC, and inspection. Authentication proxy is used to authenticate inbound or outbound users or both. These users are normally blocked by an access list, but with auth-proxy, the users can bring up a browser to go through the firewall and authenticate on a terminal access controller access control system plus (TACACS+) or RADIUS server (based on the IP address). The server passes additional access list entries down to the switch to allow the users through after authentication. These ACLs are stored and processed in software, and if there are many users utilizing auth-proxy, the MSFC may be overwhelmed. Rate limiting would be advantageous in this situation. IPSec and inspection are also done by the MSFC and may require rate limiting. When the Layer 3 security feature rate limiter is enabled, all Layer 3 rate limiters for auth-proxy, IPSec and inspection are enabled at the same rate. This example shows how to rate limit the security features to the MSFC to 100000 pps with a burst of 10 packets:
Router(config)# mls rate-limit unicast ip features 100000 10
ICMP Redirect (Unicast Only)

The ICMP-redirect rate limiter allows you to rate limit ICMP traffic. For example, when a host sends packets through a nonoptimal switch, the MSFC sends ICMP-redirect messages to the host to correct its sending path. If this traffic occurs continuously, and is not rate limited, the MSFC will continuously generate ICMP-redirect messages. This example shows how to rate limit the ICMP redirects to 20000 pps, with a burst of 20 packets:
Router(config)# mls rate-limit unicast ip icmp redirect 20000 20
VACL Log (Unicast Only)

Packets that are sent to the MSFC because of VLAN-ACL logging can be rate limited to ensure that the CPU is not overwhelmed with logging tasks. VACLs are processed in hardware, but the MSFC does the logging. When VACL logging is configured on the switch, IP packets that are denied in the VACL generate log messages. This example shows how to rate limit logging requests to 5000 pps (the range for this rate limiter is from 10 to 5000 pps):
Router(config)# mls rate-limit unicast acl vacl-log 5000
36-18
OL-3999-08
Chapter 36
MTU Failure
Similar to the TTL failure rate limiter, the rate limiter for MTU failures is supported for both unicast and multicast traffic. Packets that fail an MTU check are sent to the MSFC CPU. This might cause the MSFC to be overwhelmed. This example shows how to rate limit packets failing the MTU failures from being sent to the MSFC to 10000 pps with a burst of 10:
Router(config)# mls rate-limit all mtu 10000 10
Layer 2 Multicast IGMP Snooping

The IGMP snooping rate limiter limits the number of Layer 2 IGMP packets destined for the supervisor engine. IGMP snooping listens to IGMP messages between the hosts and the supervisor engine. You cannot enable the Layer 2 PDU rate limiter if the Catalyst 6500 series switch is operating in truncated mode. The switch uses truncated mode for traffic between fabric-enabled modules when there are both fabric-enabled and nonfabric-enabled modules installed. In this mode, the switch sends a truncated version of the traffic (the first 64 bytes of the frame) over the switch fabric channel. This example shows how to rate limit IGMP-snooping traffic:
Router(config)# mls rate-limit multicast ipv4 igmp 20000 40
Layer 2 PDU
The Layer 2 protocol data unit (PDU) rate limiter allows you to limit the number of Layer 2 PDU protocol packets (including BPDUs, DTP, PAgP, CDP, STP, and VTP packets) destined for the supervisor engine and not the MSFC CPU. You cannot enable the Layer 2 PDU rate limiter if the Catalyst 6500 series switch is operating in truncated mode. The switch uses truncated mode for traffic between fabric-enabled modules when there are both fabric-enabled and nonfabric-enabled modules installed. In this mode, the switch sends a truncated version of the traffic (the first 64 bytes of the frame) over the switch fabric channel. This example shows how to rate limit Layer 2 PDUs to 20000 pps with a burst of 20 packets.
Router(config)# mls rate-limit layer2 pdu 20000 20
Layer 2 Protocol Tunneling

This rate limiter limits the Layer 2 protocol tunneling packets, which include control PDUs, CDP, STP, and VTP packets destined for the supervisor engine. These packets are encapsulated in software (rewriting the destination MAC address in the PDU), and then forwarded to a proprietary multicast address (01-00-0c-cd-cd-d0). You cannot enable the Layer 2 PDU rate limiter if the Catalyst 6500 series switch is operating in truncated mode. The switch uses truncated mode for traffic between fabric-enabled modules when there are both fabric-enabled and nonfabric-enabled modules installed. In this mode, the switch sends a truncated version of the traffic (the first 64 bytes of the frame) over the switch fabric channel. This example shows how to rate limit Layer 2 protocol tunneling packets to 10000 pps with a burst of 10 packets:
Router(config)# mls rate-limit layer2 l2pt 10000 10
36-19
IP Errors
This rate limiter limits the packets with IP checksum and length errors. When a packet reaches the PFC3 with an IP checksum error or a length inconsistency error, it must be sent to the MSFC for further processing. An attacker might use the malformed packets to carry out a DoS attack, but the network administrator can configure a rate for these types of packets to protect the control path. This example shows how to rate limit IP errors sent to the MSFC to 1000 pps with a burst of 20 packets:
Router(config)# mls rate-limit unicast ip errors 1000 20
IPv4 Multicast
This rate limiter limits the IPv4 multicast packets. The rate limiters can rate limit the packets that are sent from the data path in the hardware up to the data path in the software. The rate limiters protect the control path in the software from congestion and drop the traffic that exceeds the configured rate. Within the IPv4 multicast rate limiter, there are three rate limiters that you can also configure: the FIB-miss rate limiter, the multicast partially switched flows rate limiter, and the multicast directly connected rate limiter. The FIB-miss rate limiter allows you to rate limit the multicast traffic that does not match an entry in the mroute table. The partially switched flow rate limiter allows you to rate limit the flows destined to the MSFC3 for forwarding and replication. For a given multicast traffic flow, if at least one outgoing Layer 3 interface is multilayer switched, and at least one outgoing interface is not multilayer switched (no H-bit set for hardware switching), the particular flow is considered partially switched, or partial-SC (partial shortcut). The outgoing interfaces that have the H-bit flag are switched in hardware and the remaining traffic is switched in software through the MSFC3. For this reason, it may be desirable to rate limit the flow destined to the MSFC3 for forwarding and replication, which might otherwise increase CPU utilization. The multicast directly connected rate limiter limits the multicast packets from directly connected sources. This example shows how to rate limit the multicast packets to 30000 pps with a burst of 30:
Router(config)# mls rate-limit multicast ipv4 connected 30000 30
The ip-option keyword and the ip-option rate limiter are supported in PFC3B or PFC3BXL mode only. This example shows how to set the rate limiters for the IPv4 multicast packets failing the uRPF check:
Router(config)# mls rate-limit multicast ipv4 non-rpf 100
This example shows how to rate limit the multicast FIB miss packets to 10000 pps with a burst of 10:
Router(config)# mls rate-limit multicast ipv4 fib-miss 10000 10
This example shows how to rate limit the partial shortcut flows to 20000 pps with a burst of 20 packets:
Router(config)# mls rate-limit multicast ipv4 partial 20000 20
This example shows how to rate limit the multicast packets to 30000 pps with a burst of 20:
This example shows how to rate limit IGMP-snooping traffic:

Router(config)# mls rate-limit multicast ipv4 igmp 20000 40
36-20
OL-3999-08
Chapter 36
IPv6 Multicast
This rate limiter limits the IPv6 multicast packets. Table 36-2 lists the IPv6 rate limiters and the class of traffic that each rate limiter serves.
Table 36-2 IPv6 Rate Limiters
Rate Limiter Connected Default-drop Route-control Starg-bridge Starg-M-bridge
Traffic Classes to be Rate Limited Directly connected source traffic * (*, G/m) SSM * (*, G/m) SSM non-rpf * (*, FF02::X/128) * (*, G/128) SM * SM non-rpf traffic when (*, G) exists * (*, G/m) SM * (*, FF/8) * SM non-rpf traffic when (*, G) doesnt exist
You can configure rate limiters for IPv6 multicast traffic using one of the following methods:
Direct association of the rate limiters for a traffic classSelect a rate and associate the rate with a rate limiter. This example shows how to pick a rate of 1000 pps and 20 packets per burst and associate the rate with the default-drop rate limiter:
Router(config)# mls rate-limit multicast ipv6 default-drop 1000 20
Static sharing of a rate limiter with another preconfigured rate limiterWhen there are not enough adjacency-based rate limiters available, you can share a rate limiter with an already configured rate limiter (target rate limiter). This example shows how to share the route-cntl rate limiter with the default-drop target rate limiter:
Router(config)# mls rate-limit multicast ipv6 route-cntl share default-drop
If the target rate limiter is not configured, a message is displayed that indicates that the target rate limiter must be configured for it to be shared with other rate limiters.
Dynamic sharing of rate limitersIf you are not sure about which rate limiter to share with, use the share auto keywords to enable dynamic sharing. When you enable dynamic sharing, the system selects a preconfigured rate limiter and shares the given rate limiter with the preconfigured rate limiter. This example shows how to choose dynamic sharing for the route-cntrl rate limiter:
Router(config)# mls rate-limit multicast ipv6 route-cntl share auto
This example shows how to set the rate limiters for the IPv6 multicast packets from a directly connected source:
This example shows how to configure a direct association of the rate limiters for a traffic class:
Router(config)# mls rate-limit multicast ipv6 default-drop 1000 20
36-21
Chapter 36 DoS Protection Default Configuration
This example shows how to configure the static sharing of a rate limiter with another preconfigured rate limiter:
Router(config)# mls rate-limit multicast ipv6 route-cntl share default-drop
This example shows how to enable dynamic sharing for the route control rate limiter:
Router(config)# mls rate-limit multicast ipv6 route-cntl share auto
DoS Protection Default Configuration

Table 36-3 shows the DoS protection default configuration for the PFC3 hardware-based rate limiters.
Table 36-3 PFC3 Hardware-based Rate Limiter Default Setting
Rate Limiter Ingress/Egress ACL Bridged Packets RPF Failures FIB Receive cases FIB Glean Cases Layer 3 Security features ICMP Redirect ICMP Unreachable VACL Log TTL Failure MTU Failure Layer 2 PDU Layer 2 Protocol Tunneling IP Errors Multicast IGMP Multicast FIB-Miss Multicast Partial-SC Multicast Directly Connected Multicast Non-RPF Multicast IPv6
Default Status (ON/OFF) OFF ON OFF OFF OFF OFF ON ON OFF OFF OFF OFF ON OFF ON ON OFF OFF ON
Default Value
100 pps, burst of 10 packets
100 pps, burst of 10 packets 2000 pps, burst of 10 packets
100 pps, burst of 10 packets 100000 pps, burst of 100 packets 100000 pps, burst of 100 packets
If the packets-in-burst is not set, a default of 100 is programmed for multicast cases.
36-22
OL-3999-08
Chapter 36
Configuring Denial of Service Protection DoS Protection Configuration Guidelines and Restrictions
DoS Protection Configuration Guidelines and Restrictions

The section contains these configuration guidelines and restrictions:

PFC2, page 36-23 PFC3, page 36-23
PFC2
When configuring DoS protection on systems configured with a PFC2, follow these guidelines and restrictions:
When using security ACLs to drop DoS packets, note the following information:
The security ACL must specify the traffic flow to be dropped. Security ACLs need to be configured on all external interfaces that require protection. Use the
interface range command to configure a security ACL on multiple interfaces.
When using QoS ACLs to limit the rate of packets, note the following information:
The QoS ACL must specify the traffic flow to be rate limited. When adding a QoS ACL to limit the rate of packets to an interface that already has a QoS ACL
configured, you can perform one of the following: * Merge the rate-limiting ACL with the existing QoS ACL. * Define a separate class that matches the DoS ACL and tie the class to the policy map.
QoS ACLs need to be configured on all external interfaces that require protection. Use the
interface range command to configure an ACL on multiple interfaces.

The CPU rate limiters limit the traffic in aggregate only and do not distinguish between good and bad packets. The following FIB rate-limiting usage guidelines apply:
FIB rate limiting does not limit the rate of broadcast or some multicast traffic in hardware.
The PFC3 has separate multicast rate limiters. The Supervisor Engine 2 does not have separate multicast rate limiters.
FIB rate limiting does not differentiate between legitimate and illegitimate traffic (for example,
tunnels, Telnet).
FIB rate limiting applies aggregate rate limiting and not per-flow rate limiting.
PFC3
When configuring DoS protection on systems configured with a PFC3, follow these CPU rate limiter guidelines and restrictions:
Note
For the CoPP guidelines and restrictions, see the CoPP Configuration Guidelines and Restrictions section on page 36-29.
36-23
Chapter 36 DoS Protection Configuration Guidelines and Restrictions
Do not use these rate limiters if multicast is enabled in systems configured with a PFC3A:
TTL failure MTU failure
These rate limiters are supported only in PFC3B or PFC3BXL mode:

Unicast IP options Multicast IP options
These are Layer 2 rate limiters:

Layer 2 PDUs Layer 2 protocol tunneling Layer 2 Multicast IGMP
There are eight Layer 3 registers and two Layer 2 registers that can be used as CPU rate limiters. Do not use the CEF receive limiter if CoPP is being used. The CEF receive limiter will override the CoPP traffic. Rate limiters override the CoPP traffic. Configured rate limits is applied to each forwarding engine (except for the Layer 2 hardware rate limiter which is applied globally). Layer 2 rate limiters are not supported in truncated mode. The following restrictions apply when using the ingress and egress ACL-bridged packet rate limiters:
The ingress and egress ACL-bridged packet rate limiter is available for unicast traffic only. The ingress and egress ACL-bridged packet rate limiters share a single rate-limiter register. If
you enable the ACL-bridge ingress and egress rate limiters, both the ingress and the egress ACLs must share the same rate-limiter value.

Use the mls rate-limit unicast command to rate limit unicast traffic. Use the mls rate-limit multicast command to rate limit multicast traffic. Use the mls rate-limit multicast layer 2 command to rate limit Layer 2 multicast traffic.
Monitoring Packet Drop Statistics

You can capture the incoming or outgoing traffic on an interface and send a copy of this traffic to an external interface for monitoring by a traffic analyzer. To capture traffic and forward it to an external interface, use the monitor session command. When capturing traffic, these restrictions apply:

The incoming captured traffic is not filtered. The incoming captured traffic is not rate limited to the capture destination.
36-24
OL-3999-08
Chapter 36
Monitoring Dropped Packets Using Monitor Session Commands

This example shows how to use the monitor session command to capture and forward traffic to an external interface:
Router# configure terminal Enter configuration commands, one Router(config)# monitor session 1 Router(config)# monitor session 1 Router(config)# end Router# 2w0d: %SYS-5-CONFIG_I: Configured per line. End with CNTL/Z. source vlan 44 both destination interface g9/1
from console by console
This example shows how to use the show monitor session command to display the destination port location:
Router# show monitor session 1 Session 1 --------Source Ports: RX Only: None TX Only: None Both: None Source VLANs: RX Only: None TX Only: None Both: 44 Destination Ports: Gi9/1 Filter VLANs: None
Monitoring Dropped Packets Using show tcam interface Command

PFC3B and PFC3BXL mode supports ACL hit counters in hardware. You can use the show tcam interface command to display each entry in the ACL TCAM. This example shows how to use the show tcam interface command to display the number of times the entry was hit:
Router# show tcam interface fa5/2 acl in ip detail ------------------------------------------------------------------------------------------------------------DPort - Destination Port SPort - Source Port TCP-F - U -URG Pro - Protocol I - Inverted LOU TOS - TOS Value - A -ACK rtr - Router MRFM - M -MPLS Packet TN - T -Tcp Control - P -PSH COD - C -Bank Care Flag - R -Recirc. Flag - N -Non-cachable - R -RST - I -OrdIndep. Flag - F -Fragment Flag CAP - Capture Flag - S -SYN - D -Dynamic Flag - M -More Fragments F-P - FlowMask-Prior. - F -FIN T - V(Value)/M(Mask)/R(Result) X - XTAG (*) - Bank Priority -------------------------------------------------------------------------------------------------------------
Interface: 1018 label: 1 lookup_type: 0 protocol: IP packet-type: 0 +-+-----+---------------+---------------+---------------+---------------+-------+---+----+-+---+--+---+---+ |T|Index| Dest Ip Addr | Source Ip Addr| DPort | SPort | TCP-F|Pro|MRFM|X|TOS|TN|COD|F-P| +-+-----+---------------+---------------+---------------+---------------+------+---+----+-+---+--+---+---+ V 18396 0.0.0.0 0.0.0.0 P=0 P=0 -----0 ---- 0 0 -- --- 0-0 M 18404 0.0.0.0 0.0.0.0 0 0 0 ---- 0 0 R rslt: L3_DENY_RESULT rtr_rslt: L3_DENY_RESULT
V 36828
0.0.0.0
0.0.0.0
P=0
P=0
------
0 ---- 0
0 -- --- 0-0
36-25
Chapter 36 DoS Protection Configuration Guidelines and Restrictions
M 36836 0.0.0.0 R rslt: L3_DENY_RESULT (*) Router#
0.0.0.0 0 0 rtr_rslt: L3_DENY_RESULT (*)
0 ---- 0
You can also use the TTL and IP options counters to monitor the performance of the Layer 3 forwarding engine. This example shows how to use the show mls statistics command to display packet statistics and errors associated with the Layer 3 forwarding engine:
Router# show mls statistics Statistics for Earl in Module 6 L2 Forwarding Engine Total packets Switched L3 Forwarding Engine Total packets L3 Switched Total Total Total Total Total Total Total Total Total Total Packets Bridged Packets FIB Switched Packets ACL Routed Packets Netflow Switched Mcast Packets Switched/Routed ip packets with TOS changed ip packets with COS changed non ip packets COS changed packets dropped by ACL packets dropped by Policing
: 25583421
: 25433414 @ 24 pps : : : : : : : : : : 937860 23287640 0 0 96727 2 2 0 33 0
Errors MAC/IP length inconsistencies Short IP packets received IP header checksum errors TTL failures <----------------- TTL counters MTU failures <------------------MTU failure counters
: : : :
0 0 0 0
: 0
Total packets L3 Switched by all Modules: 25433414 @ 24 pps
Monitoring Dropped Packets Using VACL Capture

The VACL capture feature allows you to direct traffic to ports configured to forward captured traffic. The capture action sets the capture bit for the forwarded packets so that ports with the capture function enabled can receive the packets. Only forwarded packets can be captured. You can use VACL capture to assign traffic from each VLAN to a different interface. VACL capture does not allow you to send one type of traffic, such as HTTP, to one interface and another type of traffic, such as DNS, to another interface. Also, VACL capture granularity is only applicable to traffic switched locally; you cannot preserve the granularity if you direct traffic to a remote switch.
36-26
OL-3999-08
Chapter 36
This example shows how to use VACL capture to capture and forward traffic to a local interface:
Router(config-if)# switchport capture Router(config-if)# switchport capture allowed vlan add 100
Displaying Rate-Limiter Information

The show mls rate-limit command displays information about the configured rate limiters. The show mls rate-limit usage command displays the hardware register that is used by a rate-limiter type. If the register is not used by any rate-limiter type, Free is displayed in the output. If the register is used by a rate-limiter type, Used and the rate-limiter type are displayed. In the command output, the rate-limit status could be one of the following:

On indicates that a rate for that particular case has been set. Off indicates that the rate-limiter type has not been configured, and the packets for that case are not rate limited. On/Sharing indicates that a particular case (not manually configured) is affected by the configuration of another rate limiter belonging to the same sharing group. A hyphen indicates that the multicast partial-SC rate limiter is disabled. Whether sharing is static or dynamic Group dynamic sharing codes
In the command output, the rate-limit sharing indicates the following information:

To display the configured rate limiters, use the show mls rate-limit command:
Router# show mls rate-limit Sharing Codes: S - static, D - dynamic Codes dynamic sharing: H - owner (head) of the group, g - guest of the group Rate Limiter Type --------------------MCAST NON RPF MCAST DFLT ADJ MCAST DIRECT CON ACL BRIDGED IN ACL BRIDGED OUT IP FEATURES ACL VACL LOG CEF RECEIVE CEF GLEAN MCAST PARTIAL SC IP RPF FAILURE TTL FAILURE ICMP UNREAC. NO-ROUTE ICMP UNREAC. ACL-DROP ICMP REDIRECT MTU FAILURE MCAST IP OPTION UCAST IP OPTION LAYER_2 PDU LAYER_2 PT IP ERRORS CAPTURE PKT MCAST IGMP MCAST IPv6 DIRECT CON MCAST IPv6 *G M BRIDG Status ---------Off On Off Off Off Off On Off Off On On Off On On Off Off Off Off Off Off On Off Off Off Off Packets/s --------100000 2000 100000 100 100 100 100 Burst ----100 1 100 10 10 10 10 Sharing ------Not sharing Not sharing Not sharing Group:0 S Group:0 S Group:0 S Group:0 S -
36-27
Chapter 36 Understanding How Control Plane Policing Works
MCAST IPv6 *G BRIDGE MCAST IPv6 SG BRIDGE MCAST IPv6 ROUTE CNTL MCAST IPv6 DFLT DROP MCAST IPv6 SECOND. DR Router#
Off Off Off Off Off
To display the usage of the hardware rate limiters, use the show mls rate-limit usage command:
Router# show mls rate-limit usage Rate Limiter Type --------------------Layer3 Rate Limiters: RL# 0: Free RL# 1: Free RL# 2: Free RL# 3: Used MCAST DFLT ADJ RL# 4: Free RL# 5: Free RL# 6: Used IP RPF FAILURE ICMP UNREAC. NO-ROUTE ICMP UNREAC. ACL-DROP IP ERRORS RL# 7: Used ACL VACL LOG RL# 8: Rsvd for capture Layer2 Rate Limiters: RL# 9: Reserved RL#10: Reserved RL#11: Free RL#12: Free Router# Packets/s --------100000 100 100 100 100 2000 Burst ----100 10 10 10 10 1 -
Understanding How Control Plane Policing Works

The control plane policing (CoPP) feature increases security on the Catalyst 6500 series switch by protecting the MSFC from unnecessary or DoS traffic and giving priority to important control plane and management traffic. The PFC3 and DFC3 provide hardware support for CoPP. CoPP works with the PFC3 rate limiters.
Note
The Supervisor Engine 2 does not support CoPP. The PFC3 supports the built-in special case rate limiters that can be used when an ACL cannot classify particular scenarios, such as IP options cases, TTL and MTU failure cases, packets with errors, and multicast packets. When enabling the special-case rate limiters, the special-case rate limiters override the CoPP policy for packets matching the rate-limiter criteria. The traffic managed by the MSFC is divided into three functional components or planes:

Data plane Management plane Control plane
36-28
OL-3999-08
Chapter 36
Configuring Denial of Service Protection CoPP Default Configuration
The majority of traffic managed by the MSFC is handled by way of the control and management planes. You can use CoPP to protect the control and management planes, and ensure routing stability, reachability, and packet delivery. CoPP uses a dedicated control plane configuration through the modular QoS CLI (MQC) to provide filtering and rate-limiting capabilities for the control plane packets.
CoPP Default Configuration

CoPP is disabled by default.
CoPP Configuration Guidelines and Restrictions

When configuring CoPP, follow these guidelines and restrictions:
In releases earlier than Release 12.2(18)SXE, the PFC3 does not support the MQC class-default in hardware; the class default is replaced with a normal class map. If you define a catch-all map, the MQC class-default is supported in hardware. Classes that match multicast are not applied in hardware but are applied in software. CPP is not supported in hardware for broadcast packets. The combination of ACLs, traffic storm control, and CPP software protection provides protection against broadcast DoS attacks. CoPP does not support ARP policies. ARP policing mechanisms provide protection against ARP storms. CoPP does not support non-IP classes except for the default non-IP class. ACLs can be used instead of non-IP classes to drop non-IP traffic, and the default non-IP CoPP class can be used to limit to non-IP traffic that reaches the RP CPU. Do not use the log keyword in CoPP policy ACLs. With PFC3A, egress QoS and CoPP cannot be configured at the same time. In this situation, CoPP is performed in the software. A warning message is displayed to inform you that egress QoS and CoPP cannot be configured at the same time. If you have a large QoS configuration, the system may run out of TCAM space. If this is the case, CoPP may be performed in software. When there is a large QoS configuration for other interfaces, you can run out of TCAM space. When this situation occurs, CoPP may be performed entirely in software and result in performance degradation and CPU cycle consumption. You must ensure that the CoPP policy does not filter critical traffic such as routing protocols or interactive access to the switches. Filtering this traffic could prevent remote access to the switch, requiring a console connection. PFC3 supports built-in special-case rate limiters, which are useful for situations where an ACL cannot be used (for example, TTL, MTU, and IP options). When you enable the special-case rate limiters, you should be aware that the special-case rate limiters will override the CoPP policy for packets matching the rate-limiter criteria. CoPP is not enabled in hardware unless MMLS QoS is enabled globally with the mls qos command. If the mls qos command is not entered, CoPP will only work in software and will not provide any benefit to the hardware. Neither egress CoPP nor silent mode is supported. CoPP is only supported on ingress (service-policy output CoPP cannot be applied to the control plane interface).
36-29
Chapter 36 Configuring CoPP
ACE hit counters in hardware are only for ACL logic. You can rely on software ACE hit counters and the show access-list , show policy-map control-plane, and show mls ip qos commands to troubleshoot evaluate CPU traffic. CoPP is performed on a per-forwarding-engine basis and software CoPP is performed on an aggregate basis. CoPP is not supported in hardware for multicast packets. The combination of ACLs, multicast CPU rate limiters and CoPP software protection provides protection against multicast DoS attacks. CoPP does not support ACEs with the log keyword. CoPP uses hardware QoS TCAM resources. Enter the show tcam utilization command to verify the TCAM utilization. CoPP does not support MAC ACLs.
Configuring CoPP
CoPP uses MQC to define traffic classification criteria and to specify the configurable policy actions for the classified traffic. You must first identify the traffic to be classified by defining a class map. The class map defines packets for a particular traffic class. After you have classified the traffic, you can create policy maps to enforce policy actions for the identified traffic. The control-plane global configuration command allows the CoPP service policies to be directly attached to the control plane. For information on how to define the traffic classification criteria, refer to the Defining Traffic Classification section on page 36-32. To configure CoPP, perform this task: Command
Step 1 Step 2
Router(config)# mls qos Router(config)# ip access-list extended access-list-name Router(config-ext-nacl)# {permit | deny} protocol source source-wildcard destination destination-wildcard [precedence precedence] [tos tos] [established] [log | log-input] [time-range time-range-name] [fragments]
Purpose Enables MLS QoS globally. Defines ACLs to match traffic:

Note
permit sets the conditions under which a packet passes a named IP access list. deny sets the conditions under which a packet does not pass a named IP access list. You must configure ACLs in most cases to identify the important or unimportant traffic.
Step 3
Router(config)# class-map traffic-class-name Router(config-cmap)# match {ip precedence} |{ip dscp} | access-group Router(config)# policy-map service-policy-name Router(config-pmap)# class traffic-class-name Router(config-pmap-c)# police {bits-per-second [normal-burst-bytes] [maximum-burst-bytes] [pir peak-rate-bps]} | [conform-action action] [exceed-action action] [violate-action action]
Defines the packet classification criteria. Use the match statements to identify the traffic associated with the class. Defines a service policy map. Use the class traffic-class-name command to associate classes to the service policy map. Use the police statements to associate actions to the service policy map.
Step 4
36-30
OL-3999-08
Chapter 36
Configuring Denial of Service Protection Monitoring CoPP
Command
Step 5 Step 6
Router(config)# control-plane Router(config-cp)# Router(config-cp)# service-policy input service-policy-name
Purpose Enters the control plane configuration mode. Applies the QoS service policy to the control plane.
When defining the packet classification criteria, follow these guidelines and restrictions:
To avoid matching the filtering and policing that are configured in a subsequent class, configure policing in each class. CoPP does not apply the filtering in a class that does not contain a police command. A class without a police command matches no traffic. The ACLs used for classification are QoS ACLs. QoS ACLs supported are IP standard, extended, and named. These are the only match types supported:
ip precedence ip dscp access-group
Only IP ACLs are supported in hardware. MAC-based matching is done in software only. You can enter one match command in a single class map only. In releases earlier than Release 12.2(18)SXE, the MQC class default is not supported.
When defining the service policy, the police policy-map action is the only supported action. When applying the service policy to the control plane, the input direction is only supported.
Monitoring CoPP
You can enter the show policy-map control-plane command for developing site-specific policies, monitoring statistics for the control plane policy, and troubleshooting CoPP. This command displays dynamic information about the actual policy applied, including rate information and the number of bytes (and packets) that conformed or exceeded the configured policies both in hardware and in software. The output of the show policy-map control-plane command is as follows:
Router# show policy-map control-plane Control Plane Interface Service policy CoPP-normal Hardware Counters: class-map: CoPP-normal (match-all) Match: access-group 130 police : 96000 bps 3000 limit 3000 extended limit Earl in slot 3 : 0 bytes 5 minute offered rate 0 bps aggregate-forwarded 0 bytes action: transmit exceeded 0 bytes action: drop aggregate-forward 0 bps exceed 0 bps Earl in slot 5 : 0 bytes 5 minute offered rate 0 bps
36-31
Chapter 36 Defining Traffic Classification
aggregate-forwarded 0 bytes action: transmit exceeded 0 bytes action: drop aggregate-forward 0 bps exceed 0 bps Software Counters: Class-map: CoPP-normal (match-all) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: access-group 130 police: 96000 bps, 3125 limit, 3125 extended limit conformed 0 packets, 0 bytes; action: transmit exceeded 0 packets, 0 bytes; action: drop conformed 0 bps, exceed 0 bps, violate 0 bps Router#
To display the hardware counters for bytes dropped and forwarded by the policy, enter the show mls qos ip command:
Router# show mls qos ip QoS Summary [IP]: (* - shared aggregates, Mod - switch module) Int Mod Dir Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------CPP 5 In CoPP-normal 0 1 dscp 0 505408 83822272 CPP 9 In CoPP-normal 0 4 dscp 0 0 0 Router# Class-map DSCP
To display the CoPP access list information, enter the show access-lists coppacl-bgp command:
Router#show access-lists coppacl-bgp Extended IP access list coppacl-bgp 10 permit tcp host 47.1.1.1 host 10.9.9.9 eq bgp (4 matches) 20 permit tcp host 47.1.1.1 eq bgp host 10.9.9.9 30 permit tcp host 10.86.183.120 host 10.9.9.9 eq bgp (1 match) 40 permit tcp host 10.86.183.120 eq bgp host 10.9.9.9
Defining Traffic Classification

The following sections contain information on how to classify CoPP traffic:

Traffic Classification Overview, page 36-32 Traffic Classification Guidelines, page 36-34 Sample Basic ACLs for CoPP Traffic Classification, page 36-34
Traffic Classification Overview

You can define any number of classes, but typically traffic is grouped into classes that are based on relative importance. The following provides a sample grouping:
Border Gateway Protocol (BGP)Traffic that is crucial to maintaining neighbor relationships for BGP routing protocol, for example, BGP keepalives and routing updates. Maintaining BGP routing protocol is crucial to maintaining connectivity within a network or to a service provider. Sites that do not run BGP do not need to use this class.
36-32
OL-3999-08
Chapter 36
Configuring Denial of Service Protection Defining Traffic Classification
Interior Gateway Protocol (IGP)Traffic that is crucial to maintaining IGP routing protocols, for example, open shortest path first OSPF, enhanced interior gateway routing protocol (EIGRP), and routing information protocol (RIP). Maintaining IGP routing protocols is crucial to maintaining connectivity within a network. ManagementNecessary, frequently used traffic that is required during day-to-day operations. For example, traffic used for remote network access, and Cisco IOS image upgrades and management, such as telnet, secure shell (SSH), network time protocol (NTP), simple network management protocol (SNMP), terminal access controller access control system (TACACS), hypertext transfer protocol (HTTP), trivial file transfer protocol (TFTP), and file transfer protocol (FTP). ReportingTraffic used for generating network performance statistics for the purpose of reporting. For example, using Cisco IOS IP service level agreements (SLAs) to generate ICMP with different DSCP settings in order to report on response times within different QoS data classes. MonitoringTraffic used for monitoring a switch. Traffic should be permitted but should never pose a risk to the switch; with CoPP, this traffic can be permitted but limited to a low rate. For example, ICMP echo request (ping) and traceroute. Critical ApplicationsCritical application traffic that is specific and crucial to a particular customer environment. Traffic included in this class should be tailored specifically to the required application requirements of the user (in other words, one customer may use multicast, while another uses IPSec or generic routing encapsulation (GRE). For example, GRE, hot standby router protocol (HSRP), virtual router redundancy protocol (VRRP), session initiation protocol (SIP), data link switching (DLSw), dynamic host configuration protocol (DHCP), multicast source discovery protocol (MSDP), Internet group management protocol (IGMP), protocol independent multicast (PIM), multicast traffic, and IPsec. Layer 2 ProtocolsTraffic used for address resolution protocol (ARP). Excessive ARP packets can potentially monopolize MSFC resources, starving other important processes; CoPP can be used to rate limit ARP packets to prevent this situation. Currently, ARP is the only Layer 2 protocol that can be specifically classified using the match protocol classification criteria. UndesirableExplicitly identifies bad or malicious traffic that should be unconditionally dropped and denied access to the MSFC.The undesirable classification is particularly useful when known traffic destined for the switch should always be denied and not placed into a default category. If you explicitly deny traffic, then you can enter show commands to collect approximate statistics on the denied traffic and estimate its rate. DefaultAll remaining traffic destined for the MSFC that has not been identified. MQC provides the default class, so the user can specify the treatment to be applied to traffic not explicitly identified in the other user-defined classes. This traffic has a highly reduced rate of access to the MSFC. With a default classification in place, statistics can be monitored to determine the rate of otherwise unidentified traffic destined for the control plane. After this traffic is identified, further analysis can be performed to classify it and, if needed, the other CoPP policy entries can be updated to accomodate this traffic.
After you have classified the traffic, the ACLs build the classes of traffic that are used to define the policies. For sample basic ACLs for CoPP classification, see the Sample Basic ACLs for CoPP Traffic Classification section on page 36-34.
36-33
Chapter 36 Defining Traffic Classification
Traffic Classification Guidelines

When defining traffic classification, follow these guidelines and restrictions:
Before you develop the actual CoPP policy, you must identify and separate the required traffic into different classes. Traffic is grouped into nine classes that are based on relative importance. The actual number of classes needed might differ and should be selected based on your local requirements and security policies. You do not have to define policies that match bidirectionally. You only need to identify traffic unidirectionally (from the network to the MSFC) since the policy is applied on ingress only.
Sample Basic ACLs for CoPP Traffic Classification

This section shows sample basic ACLs for CoPP classification. In the samples, the commonly required traffic is identified with these ACLs:

ACL 120Critical traffic ACL 121Important traffic ACL 122Normal traffic ACL 123Explicitly denies unwanted traffic ACL 124All other traffic
This example shows how to define ACL 120 for critical traffic:
Router(config)# access-list 120 remark CoPP ACL for critical traffic
This example shows how to allow BGP from a known peer to this switchs BGP TCP port:
Router(config)# access-list 120 permit tcp host 47.1.1.1 host 10.9.9.9 eq bgp
This example shows how to allow BGP from a peers BGP port to this switch:
Router(config)# access-list 120 permit tcp host 47.1.1.1 eq bgp host 10.9.9.9 Router(config)# access-list 120 permit tcp host 10.86.183.120 host 10.9.9.9 eq bgp Router(config)# access-list 120 permit tcp host 10.86.183.120 eq bgp host 10.9.9.9
This example shows how to define ACL 121 for the important class:
Router(config)# access-list 121 remark CoPP Important traffic
This example shows how to permit return traffic from TACACS host:
Router(config)# access-list 121 permit tcp host 1.1.1.1 host 10.9.9.9 established
This example shows how to permit SSH access to the switch from a subnet:
Router(config)# access-list 121 permit tcp 10.0.0.0 0.0.0.255 host 10.9.9.9 eq 22
This example shows how to allow full access for Telnet to the switch from a host in a specific subnet and police the rest of the subnet:
Router(config)# access-list 121 deny tcp host 10.86.183.3 any eq telnet Router(config)# access-list 121 permit tcp 10.86.183.0 0.0.0.255 any eq telnet
This example shows how to allow SNMP access from the NMS host to the switch:
Router(config)# access-list 121 permit udp host 1.1.1.2 host 10.9.9.9 eq snmp
This example shows how to allow the switch to receive NTP packets from a known clock source:
36-34
OL-3999-08
Chapter 36
Configuring Denial of Service Protection Configuring Sticky ARP
Router(config)# access-list 121 permit udp host 1.1.1.3 host 10.9.9.9 eq ntp
This example shows how to define ACL 122 for the normal traffic class:
Router(config)# access-list 122 remark CoPP normal traffic
This example shows how to permit switch-originated traceroute traffic:

Router(config)# access-list 122 permit icmp any any ttl-exceeded Router(config)# access-list 122 permit icmp any any port-unreachable
This example shows how to permit receipt of responses to the switch that originated the pings:
Router(config)# access-list 122 permit icmp any any echo-reply
This example shows how to allow pings to the switch:

Router(config)# access-list 122 permit icmp any any echo
This example shows how to define ACL 123 for the undesirable class.
Router(config)# access-list 123 remark explicitly defined "undesirable" traffic
Note
In the following example, ACL 123 is a permit entry for classification and monitoring purposes, and traffic is dropped as a result of the CoPP policy. This example shows how to permit all traffic destined to UDP 1434 for policing:
Router(config)# access-list 123 permit udp any any eq 1434
This example shows how to define ACL 124 for all other traffic:
Router(config)# access-list 124 remark rest of the IP traffic for CoPP Router(config)# access-list 124 permit ip any any
Configuring Sticky ARP

Sticky ARP prevents MAC address spoofing by ensuring that ARP entries (IP address, MAC address, and source VLAN) do not get overridden. The switch maintains ARP entries in order to forward traffic to end devices or other switchs. ARP entries are usually updated periodically or modified when ARP broadcasts are received. During an attack, ARP broadcasts are sent using a spoofed MAC address (with a legitimate IP address) so that the switch learns the legitimate IP address with the spoofed MAC address and begins to forward traffic to that MAC address. With sticky ARP enabled, the switch learns the ARP entries and does not accept modifications received through ARP broadcasts. If you attempt to override the sticky ARP configuration, you will receive an error message. For a complete description of the system error messages, refer to the Catalyst 6500 Series Switch Cisco IOS System Message Guide , Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/12_2sx/system/messages/122sxsms.html
Note
Release 12.2(18)SXF and later releases support sticky ARP configurability.
36-35
Chapter 36 Configuring Sticky ARP
To configure sticky ARP on a Layer 3 interface, perform the following task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# ip sticky-arp Router(config-if)# no ip sticky-arp ignore
Purpose Selects the interface on which sticky ARP is applied. Enables sticky ARP. Removes the previously configured sticky ARP command. Disables sticky ARP.
Step 3
Router(config-if)# ip sticky-arp ignore 1.
This example shows how to enable sticky ARP on interface 5/1:

Router# configure terminal Router(config)# interface gigabitethernet 5/1 Router(config-if)# ip sticky-arp Router(config-if)# end Router#
Tip
36-36
OL-3999-08
C H A P T E R
37

This chapter describes how to configure Dynamic Host Configuration Protocol (DHCP) snooping on Catalyst 6500 series switches.
Note
The DHCP snooping feature requires PFC3 and Release 12.2(18)SXE and later releases. The PFC2 does not support DHCP snooping. For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html
This chapter consists of the following major sections:

Understanding DHCP Snooping, page 37-1 Default Configuration for DHCP Snooping, page 37-6 DHCP Snooping Configuration Restrictions and Guidelines, page 37-7 Configuring DHCP Snooping, page 37-9
Tip
Understanding DHCP Snooping

These sections describe the DHCP snooping feature:

Overview of DHCP Snooping, page 37-2 Trusted and Untrusted Sources, page 37-2 DHCP Snooping Binding Database, page 37-2 Packet Validation, page 37-3 DHCP Snooping Option-82 Data Insertion, page 37-3
37-1
Chapter 37 Understanding DHCP Snooping
Overview of the DHCP Snooping Database Agent, page 37-5
Overview of DHCP Snooping

DHCP snooping is a security feature that acts like a firewall between untrusted hosts and trusted DHCP servers. The DHCP snooping feature performs the following activities:

Validates DHCP messages received from untrusted sources and filters out invalid messages. Rate-limits DHCP traffic from trusted and untrusted sources. Builds and maintains the DHCP snooping binding database, which contains information about untrusted hosts with leased IP addresses. Utilizes the DHCP snooping binding database to validate subsequent requests from untrusted hosts.
Other security features, such as dynamic ARP inspection (DAI), also use information stored in the DHCP snooping binding database. DHCP snooping is enabled on a per-VLAN basis. By default, the feature is inactive on all VLANs. You can enable the feature on a single VLAN or a range of VLANs. The DHCP snooping feature is implemented in software on the MSFC. Therefore, all DHCP messages for enabled VLANs are intercepted in the PFC and directed to the MSFC for processing.
Trusted and Untrusted Sources

The DHCP snooping feature determines whether traffic sources are trusted or untrusted. An untrusted source may initiate traffic attacks or other hostile actions. To prevent such attacks, the DHCP snooping feature filters messages and rate-limits traffic from untrusted sources. In an enterprise network, devices under your administrative control are trusted sources. These devices include the switches, routers and servers in your network. Any device beyond the firewall or outside your network is an untrusted source. Host ports are generally treated as untrusted sources. In a service provider environment, any device that is not in the service provider network is an untrusted source (such as a customer switch). Host ports are untrusted sources. In the Catalyst 6500 series switch, you indicate that a source is trusted by configuring the trust state of its connecting interface. The default trust state of all interfaces is untrusted. You must configure DHCP server interfaces as trusted. You can also configure other interfaces as trusted if they connect to devices (such as switches or routers) inside your network. You usually do not configure host port interfaces as trusted.
Note
For DHCP snooping to function properly, all DHCP servers must be connected to the switch through trusted interfaces, as untrusted DHCP messages will be forwarded only to trusted interfaces.
DHCP Snooping Binding Database

The DHCP snooping binding database is also referred to as the DHCP snooping binding table.
37-2
OL-3999-08
Chapter 37
Configuring DHCP Snooping Understanding DHCP Snooping
The DHCP snooping feature dynamically builds and maintains the database using information extracted from intercepted DHCP messages. The database contains an entry for each untrusted host with a leased IP address if the host is associated with a VLAN that has DHCP snooping enabled. The database does not contain entries for hosts connected through trusted interfaces. The DHCP snooping feature updates the database when the switch receives specific DHCP messages. For example, the feature adds an entry to the database when the switch receives a DHCPACK message from the server. The feature removes the entry in the database when the IP address lease expires or the switch receives a DHCPRELEASE message from the host. Each entry in the DHCP snooping binding database includes the MAC address of the host, the leased IP address, the lease time, the binding type, and the VLAN number and interface information associated with the host.
Packet Validation
The switch validates DHCP packets received on the untrusted interfaces of VLANs with DHCP snooping enabled. The switch forwards the DHCP packet unless any of the following conditions occur (in which case the packet is dropped):

The switch receives a packet (such as a DHCPOFFER, DHCPACK, DHCPNAK, or DHCPLEASEQUERY packet) from a DHCP server outside the network or firewall. The switch receives a packet on an untrusted interface, and the source MAC address and the DHCP client hardware address do not match. This check is performed only if the DHCP snooping MAC address verification option is turned on. The switch receives a DHCPRELEASE or DHCPDECLINE message from an untrusted host with an entry in the DHCP snooping binding table, and the interface information in the binding table does not match the interface on which the message was received. The switch receives a DHCP packet that includes a relay agent IP address that is not 0.0.0.0.
In releases earlier than Release 12.2(18)SXF1, the switch drops DHCP packets that include option-82 information that are received on untrusted ports. With Release 12.2(18)SXF1 and later releases, to support trusted edge switches that are connected to untrusted aggregation-switch ports, you can enable the DHCP option-82 on untrusted port feature, which enables untrusted aggregation-switch ports to accept DHCP packets that include option-82 information. Configure the port on the edge switch that connects to the aggregation switch as a trusted port.
Note
With the DHCP option-82 on untrusted port feature enabled, use dynamic ARP inspection on the aggregation switch to protect untrusted input interfaces.
DHCP Snooping Option-82 Data Insertion

In residential, metropolitan Ethernet-access environments, DHCP can centrally manage the IP address assignments for a large number of subscribers. When the DHCP snooping option-82 feature is enabled on the switch, a subscriber device is identified by the switch port through which it connects to the network (in addition to its MAC address). Multiple hosts on the subscriber LAN can be connected to the same port on the access switch and are uniquely identified.
37-3
Chapter 37 Understanding DHCP Snooping
Figure 37-1 is an example of a metropolitan Ethernet network in which a centralized DHCP server assigns IP addresses to subscribers connected to the switch at the access layer. Because the DHCP clients and their associated DHCP server do not reside on the same IP network or subnet, a DHCP relay agent is configured with a helper address to enable broadcast forwarding and to transfer DHCP messages between the clients and the server.
Figure 37-1 DHCP Relay Agent in a Metropolitan Ethernet Network
DHCP server
Catalyst switch (DHCP relay agent)
Access layer
VLAN 10 Host A (DHCP client) Subscribers Host B (DHCP client)

98813
When you enable the DHCP snooping information option-82 on the switch, this sequence of events occurs:

The host (DHCP client) generates a DHCP request and broadcasts it on the network. When the switch receives the DHCP request, it adds the option-82 information in the packet. The option-82 information contains the switch MAC address (the remote ID suboption) and the port identifier, vlan-mod-port, from which the packet is received (the circuit ID suboption). If the IP address of the relay agent is configured, the switch adds the IP address in the DHCP packet. The switch forwards the DHCP request that includes the option-82 field to the DHCP server. The DHCP server receives the packet. If the server is option-82 capable, it can use the remote ID, or the circuit ID, or both to assign IP addresses and implement policies, such as restricting the number of IP addresses that can be assigned to a single remote ID or circuit ID. The DHCP server then echoes the option-82 field in the DHCP reply. The DHCP server unicasts the reply to the switch if the request was relayed to the server by the switch. When the client and server are on the same subnet, the server broadcasts the reply. The switch verifies that it originally inserted the option-82 data by inspecting the remote ID and possibly the circuit ID fields. The switch removes the option-82 field and forwards the packet to the switch port that connects to the DHCP client that sent the DHCP request.
When the previously described sequence of events occurs, the values in these fields in Figure 37-2 do not change:
Circuit ID suboption fields

Suboption type Length of the suboption type Circuit ID type Length of the circuit ID type
37-4
OL-3999-08
Chapter 37
Configuring DHCP Snooping Understanding DHCP Snooping
Remote ID suboption fields

Suboption type Length of the suboption type Remote ID type Length of the circuit ID type
Figure 37-2 shows the packet formats for the remote ID suboption and the circuit ID suboption. The switch uses the packet formats when DHCP snooping is globally enabled and when the ip dhcp snooping information option global configuration command is entered. For the circuit ID suboption, the module field is the slot number of the module.
Figure 37-2 Suboption Packet Formats
Circuit ID Suboption Frame Format

Suboption Circuit type ID type Length Length 1 6 0 4 VLAN 2 bytes Module Port 1 byte 1 byte
1 byte 1 byte 1 byte 1 byte
Remote ID Suboption Frame Format

Remote Suboption ID type type Length Length 2 8 0 6 MAC address 6 bytes
116300
1 byte 1 byte 1 byte 1 byte
Overview of the DHCP Snooping Database Agent

To retain the bindings across reloads, you must use the DHCP snooping database agent. Without this agent, the bindings established by DHCP snooping are lost upon reload, and connectivity is lost as well. The database agent stores the bindings in a file at a configured location. Upon reload, the switch reads the file to build the database for the bindings. The switch keeps the file current by writing to the file as the database changes. The format of the file that contains the bindings is as follows:
<initial-checksum> TYPE DHCP-SNOOPING VERSION 1 BEGIN <entry-1> <checksum-1> <entry-2> <checksum-1-2> ... ... <entry-n> <checksum-1-2-..-n>
37-5
Chapter 37 Default Configuration for DHCP Snooping
END
Each entry in the file is tagged with a checksum that is used to validate the entries whenever the file is read. The <initial-checksum> entry on the first line helps distinguish entries associated with the latest write from entries that are associated with a previous write. This is a sample bindings file:
3ebe1518 TYPE DHCP-SNOOPING VERSION 1 BEGIN 1.1.1.1 512 0001.0001.0005 3EBE2881 Gi1/1 1.1.1.1 512 0001.0001.0002 3EBE2881 Gi1/1 1.1.1.1 1536 0001.0001.0004 3EBE2881 Gi1/1 1.1.1.1 1024 0001.0001.0003 3EBE2881 Gi1/1 1.1.1.1 1 0001.0001.0001 3EBE2881 Gi1/1 END
e5e1e733 4b3486ec f0e02872 ac41adf9 34b3273e
Each entry holds an IP address, VLAN, MAC address, lease time (in hex), and the interface associated with a binding. At the end of each entry is a checksum that is based on all the bytes from the start of the file through all the bytes associated with the entry. Each entry consists of 72 bytes of data, followed by a space, followed by a checksum. Upon bootup, when the calculated checksum equals the stored checksum, the switch reads entries from the file and adds the bindings to the DHCP snooping database. If the calculated checksum does not equal the stored checksum, the entry read from the file is ignored and so are all the entries following the failed entry. The switch also ignores all those entries from the file whose lease time has expired. (This is possible because the lease time might indicate an expired time.) An entry from the file is also ignored if the interface referred to in the entry no longer exists on the system, or if it is a router port or a DHCP snooping-trusted interface. When the switch learns of new bindings or when it loses some bindings, the switch writes the modified set of entries from the snooping database to the file. The writes are performed with a configurable delay to batch as many changes as possible before the actual write happens. Associated with each transfer is a timeout after which a transfer is aborted if it is not completed. These timers are referred to as the write delay and abort timeout.
Default Configuration for DHCP Snooping

Table 37-1 shows all the default configuration values for each DHCP snooping option.
Table 37-1 Default Configuration Values for DHCP Snooping
Option DHCP snooping DHCP snooping information option DHCP option-82 on untrusted port feature DHCP snooping limit rate DHCP snooping trust DHCP snooping vlan
Default Value/State Disabled Enabled Disabled None Untrusted Disabled
37-6
OL-3999-08
Chapter 37
Configuring DHCP Snooping DHCP Snooping Configuration Restrictions and Guidelines
DHCP Snooping Configuration Restrictions and Guidelines

These sections provide DHCP snooping configuration restrictions and guidelines:

DHCP Snooping Configuration Restrictions, page 37-7 DHCP Snooping Configuration Guidelines, page 37-7 Minimum DHCP Snooping Configuration, page 37-8
DHCP Snooping Configuration Restrictions

When configuring DHCP snooping, note these restrictions:

The PFC2 does not support DHCP snooping. With releases earlier than Release 12.2(18)SXF5, the DHCP snooping database stores a maximum of 512 bindings. If the database attempts to add more than 512 DHCP bindings, all bindings are removed from the database. With Release 12.2(18)SXF5 and later releases, the DHCP snooping database stores at least 8,000 bindings. When DHCP snooping is enabled, these Cisco IOS DHCP commands are not available on the switch:
ip dhcp relay information check global configuration command ip dhcp relay information policy global configuration command ip dhcp relay information trust-all global configuration command ip dhcp relay information option global configuration command ip dhcp relay information trusted interface configuration command
If you enter these commands, the switch returns an error message, and the configuration is not applied.
DHCP Snooping Configuration Guidelines

When configuring DHCP snooping, follow these guidelines:

DHCP snooping is not active until you enable the feature on at least one VLAN, and enable DHCP globally on the switch. Before globally enabling DHCP snooping on the switch, make sure that the devices acting as the DHCP server and the DHCP relay agent are configured and enabled. For DHCP server configuration information, refer to Configuring DHCP in the Cisco IOS IP and IP Routing Configuration Guide at: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfdhcp.html If a Layer 2 LAN port is connected to a DHCP server, configure the port as trusted by entering the ip dhcp snooping trust interface configuration command. If a Layer 2 LAN port is connected to a DHCP client, configure the port as untrusted by entering the no ip dhcp snooping trust interface configuration command.
37-7
Chapter 37 DHCP Snooping Configuration Restrictions and Guidelines
You can enable DHCP snooping on private VLANs:

If DHCP snooping is enabled, any primary VLAN configuration is propagated to its associated
secondary VLANs.
If DHCP snooping is configured on the primary VLAN and you configure DHCP snooping with
different settings on an associated secondary VLAN, the configuration on the secondary VLAN does not take effect.
If DHCP snooping is not configured on the primary VLAN and you configure DHCP snooping
on a secondary VLAN, the configuration takes affect only on the secondary VLAN.
When you manually configure DHCP snooping on a secondary VLAN, this message appears:
DHCP Snooping configuration may not take effect on secondary vlan XXX
The show ip dhcp snooping command displays all VLANs (both primary and secondary) that
have DHCP snooping enabled.
Minimum DHCP Snooping Configuration

The minimum configuration steps for the DHCP snooping feature are as follows:
1.
Define and configure the DHCP server. For DHCP server configuration information, refer to Configuring DHCP in the Cisco IOS IP and IP Routing Configuration Guide at: http://www.cisco.com/en/US/docs/ios/12_2/ip/configuration/guide/1cfdhcp.html Enable DHCP snooping on at least one VLAN. By default, DHCP snooping is inactive on all VLANs. Refer to the Enabling DHCP Snooping on VLANs section on page 37-12
2.
3.
Ensure that DHCP server is connected through a trusted interface. By default, the trust state of all interfaces is untrusted. Refer to the Configuring the DHCP Trust State on Layer 2 LAN Interfaces section on page 37-13
4.
Configure the DHCP snooping database agent. This step ensures that database entries are restored after a restart or switchover. Refer to the Configuring the DHCP Snooping Database Agent section on page 37-14
5.
Enable DHCP snooping globally. The feature is not active until you complete this step. Refer to the Enabling DHCP Snooping Globally section on page 37-9
If you are configuring the switch for DHCP relay, the following additional steps are required:
1.
Define and configure the DHCP relay agent IP address. If the DHCP server is in a different subnet from the DHCP clients, configure the server IP address in the helper address field of the client side VLAN.
2.
Configure DHCP option-82 on untrusted port. Refer to the Enabling the DHCP Option-82 on Untrusted Port Feature section on page 37-10
37-8
OL-3999-08
Chapter 37
Configuring DHCP Snooping Configuring DHCP Snooping

These sections describe how to configure DHCP snooping:

Enabling DHCP Snooping Globally, page 37-9 Enabling DHCP Option-82 Data Insertion, page 37-10 Enabling the DHCP Option-82 on Untrusted Port Feature, page 37-10 Enabling DHCP Snooping MAC Address Verification, page 37-11 Enabling DHCP Snooping on VLANs, page 37-12 Configuring the DHCP Trust State on Layer 2 LAN Interfaces, page 37-13 Configuring DHCP Snooping Rate Limiting on Layer 2 LAN Interfaces, page 37-14 Configuring the DHCP Snooping Database Agent, page 37-14 Configuration Examples for the Database Agent, page 37-15 Displaying a Binding Table, page 37-18
Enabling DHCP Snooping Globally

Note
Configure this command as the last configuration step (or enable the DHCP feature during a scheduled maintenance period) because after you enable DHCP snooping globally, the switch drops DHCP requests until you configure the ports. To enable DHCP snooping globally, perform this task:
Command
Step 1
Router(config)# ip dhcp snooping Router(config)# no ip dhcp snooping
Purpose Enables DHCP snooping globally. Disables DHCP snooping. Verifies the configuration.
Step 2
Router(config)# do show ip dhcp snooping | include Switch
This example shows how to enable DHCP snooping globally:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip dhcp snooping Router(config)# do show ip dhcp snooping | include Switch Switch DHCP snooping is enabled Router(config)#
Note
When DHCP snooping is disabled and DAI is enabled, the switch shuts down all the hosts because all ARP entries in the ARP table will be checked against a nonexistent DHCP database. When DHCP snooping is disabled or in non-DHCP environments, use ARP ACLs to permit or to deny ARP packets.
37-9
Chapter 37 Configuring DHCP Snooping
Enabling DHCP Option-82 Data Insertion

To enable DHCP option-82 data insertion, perform this task: Command
Step 1
Router(config)# ip dhcp snooping information option Router(config)# no ip dhcp snooping information option
Purpose Enables DHCP option-82 data insertion. Disables DHCP option-82 data insertion. Verifies the configuration.
Step 2
Router(config)# do show ip dhcp snooping | include 82
This example shows how to disable DHCP option-82 data insertion:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# no ip dhcp snooping information option Router(config)# do show ip dhcp snooping | include 82 Insertion of option 82 is disabled Router#(config)
This example shows how to enable DHCP option-82 data insertion:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip dhcp snooping information option Router(config)# do show ip dhcp snooping | include 82 Insertion of option 82 is enabled Router#(config)
Enabling the DHCP Option-82 on Untrusted Port Feature

Note
With the DHCP option-82 on untrusted port feature enabled, the switch does not drop DHCP packets that include option-82 information that are received on untrusted ports. Do not enter the ip dhcp snooping information option allowed-untrusted command on an aggregation switch to which any untrusted devices are connected. With Release 12.2(18)SXF1 and later releases, to enable untrusted ports to accept DHCP packets that include option-82 information, perform this task:
Command
Step 1
Router(config)# ip dhcp snooping information option allow-untrusted
Purpose (Optional) Enables untrusted ports to accept incoming DHCP packets with option-82 information. The default setting is disabled. Disables the DHCP option-82 on untrusted port feature. Verifies the configuration.
Router(config)# no ip dhcp snooping information option allow-untrusted
Step 2
Router(config)# do show ip dhcp snooping
37-10
OL-3999-08
Chapter 37
This example shows how to enable the DHCP option-82 on untrusted port feature:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip dhcp snooping information option allow-untrusted Router#(config)
Enabling DHCP Snooping MAC Address Verification

With DHCP snooping MAC address verification enabled, DHCP snooping verifies that the source MAC address and the client hardware address match in DHCP packets that are received on untrusted ports. The source MAC address is a Layer 2 field associated with the packet, and the client hardware address is a Layer 3 field in the DHCP packet. To enable DHCP snooping MAC address verification, perform this task: Command
Step 1
Router(config)# ip dhcp snooping verify mac-address Router(config)# no ip dhcp snooping verify mac-address
Purpose Enables DHCP snooping MAC address verification. Disables DHCP snooping MAC address verification. Verifies the configuration.
Step 2
Router(config)# do show ip dhcp snooping | include hwaddr
This example shows how to disable DHCP snooping MAC address verification:
Router(config)# no ip dhcp snooping verify mac-address Router(config)# do show ip dhcp snooping | include hwaddr Verification of hwaddr field is disabled Router(config)#
This example shows how to enable DHCP snooping MAC address verification:
Router(config)# ip dhcp snooping verify mac-address Router(config)# do show ip dhcp snooping | include hwaddr Verification of hwaddr field is enabled Router(config)#
37-11
Enabling DHCP Snooping on VLANs

By default, the DHCP snooping feature is inactive on all VLANs. You may enable the feature on a single VLAN or a range of VLANs. When enabled on a VLAN, the DHCP snooping feature creates four entries in the VACL table in the MFC3. These entries cause the PFC3 to intercept all DHCP messages on this VLAN and send them to the MSFC. The DHCP snooping feature is implemented in MSFC software. To enable DHCP snooping on VLANs, perform this task: Command
Step 1
Router(config)# ip dhcp snooping vlan {{vlan_ID [vlan_ID]} | {vlan_range} Router(config)# no ip dhcp snooping
Purpose Enables DHCP snooping on a VLAN or VLAN range. Disables DHCP snooping. Verifies the configuration.
Step 2
Router(config)# do show ip dhcp snooping
You can configure DHCP snooping for a single VLAN or a range of VLANs:

To configure a single VLAN, enter a single VLAN number. To configure a range of VLANs, enter a beginning and an ending VLAN number or a dash-separated pair of VLAN numbers. You can enter a comma-separated list of VLAN numbers and dash-separated pairs of VLAN numbers.
This example shows how to enable DHCP snooping on VLANs 10 through 12:
Router# configure terminal Router(config)# ip dhcp snooping vlan 10 12 Router(config)#
This example shows another way to enable DHCP snooping on VLANs 10 through 12:
Router# configure terminal Router(config)# ip dhcp snooping vlan 10-12
This example shows another way to enable DHCP snooping on VLANs 10 through 12:
Router# configure terminal Router(config)# ip dhcp snooping vlan 10,11,12
This example shows how to enable DHCP snooping on VLANs 10 through 12 and VLAN 15:
Router# configure terminal Router(config)# ip dhcp snooping vlan 10-12,15

Router(config)# do show ip dhcp snooping Switch DHCP snooping is enabled DHCP snooping is configured on following VLANs: 10-12,15 DHCP snooping is operational on following VLANs: none
37-12
OL-3999-08
Chapter 37
DHCP snooping is configured on the following Interfaces: Insertion of option 82 is enabled Verification of hwaddr field is enabled Interface Trusted -----------------------------Router#
Rate limit (pps) ----------------
Configuring the DHCP Trust State on Layer 2 LAN Interfaces

To configure DHCP trust state on a Layer 2 LAN interface, perform this task: Command
Step 1
Router(config)# interface {type port-channel number}
1
Purpose
slot/port |
Selects the interface to configure.

Note
Select only LAN ports configured with the switchport command or Layer 2 port-channel interfaces.
Step 2
Router(config-if)# ip dhcp snooping trust Router(config-if)# no ip dhcp snooping trust
Configures the interface as trusted. Reverts to the default (untrusted) state. Verifies the configuration.
Step 3
Router(config-if)# do show ip dhcp snooping | begin pps 1.
This example shows how to configure Fast Ethernet port 5/12 as trusted:
Router# configure terminal Router(config)# interface FastEthernet 5/12 Router(config-if)# ip dhcp snooping trust Router(config-if)# do show ip dhcp snooping | begin pps Interface Trusted Rate limit (pps) --------------------------------------------FastEthernet5/12 yes unlimited Router#
This example shows how to configure Fast Ethernet port 5/12 as untrusted:
Router# configure terminal Router(config)# interface FastEthernet 5/12 Router(config-if)# no ip dhcp snooping trust Router(config-if)# do show ip dhcp snooping | begin pps Interface Trusted Rate limit (pps) --------------------------------------------FastEthernet5/12 no unlimited Router#
37-13
Configuring DHCP Snooping Rate Limiting on Layer 2 LAN Interfaces

To configure DHCP snooping rate limiting on a Layer 2 LAN interface, perform this task: Command
Step 1
Router(config)# interface {type port-channel number}
1
Purpose
slot/port |
Selects the interface to configure.

Note
Select only LAN ports configured with the switchport command or Layer 2 port-channel interfaces.
Router(config-if)# ip dhcp snooping limit rate rate Router(config-if)# no ip dhcp snooping limit rate Router(config-if)# do show ip dhcp snooping | begin pps 1.
Configures DHCP packet rate limiting. Disables DHCP packet rate limiting. Verifies the configuration.
When configuring DHCP snooping rate limiting on a Layer 2 LAN interface, note the following information:

We recommend an untrusted rate limit of not more than 100 packets per second (pps). If you configure rate limiting for trusted interfaces, you might need to increase the rate limit on trunk ports carrying more than one VLAN on which DHCP snooping is enabled. DHCP snooping puts ports where the rate limit is exceeded into the error-disabled state.
This example shows how to configure DHCP packet rate limiting to 100 pps on Fast Ethernet port 5/12:
Router# configure terminal Router(config)# interface FastEthernet 5/12 Router(config-if)# ip dhcp snooping limit rate 100 Router(config-if)# do show ip dhcp snooping | begin pps Interface Trusted Rate limit (pps) --------------------------------------------FastEthernet5/12 no 100 Router#
Configuring the DHCP Snooping Database Agent

To configure the DHCP snooping database agent, perform one or more of the following tasks: Command
Router(config)# ip dhcp snooping database { _url | write-delay seconds | timeout seconds } Router(config)# no ip dhcp snooping database [write-delay | timeout] Router# show ip dhcp snooping database [detail]
Purpose (Required) Configures a URL for the database agent (or file) and the related timeout values. Clears the configuration. (Optional) Displays the current operating state of the database agent and statistics associated with the transfers. (Optional) Clears the statistics associated with the database agent.
Router# clear ip dhcp snooping database statistics
37-14
OL-3999-08
Chapter 37
Command
Router# renew ip dhcp snooping database [validation none] [url] Router# ip dhcp snooping binding mac_address vlan vlan_ID ip_address interface ifname expiry lease_in_seconds Router# no ip dhcp snooping binding mac_address vlan vlan_ID ip_address interface ifname
Purpose (Optional) Requests the read entries from a file at the given URL. (Optional) Adds bindings to the snooping database.
(Optional) Deletes bindings from the snooping database.
When configuring the DHCP snooping database agent, note the following information:
With releases earlier than Release 12.2(18)SXF5, the DHCP snooping database stores a maximum of 512 bindings. If the database attempts to add more than 512 DHCP bindings, all bindings are removed from the database. With Release 12.2(18)SXF5 and later releases, the DHCP snooping database stores at least 8,000 bindings. Store the file on a TFTP server to avoid consuming storage space on the switch storage devices. When a switchover occurs, if the file is stored in a remote location accessible through TFTP, the newly active supervisor engine can use the binding list. Network-based URLs (such as TFTP and FTP) require that you create an empty file at the configured URL before the switch can write the set of bindings for the first time.
Configuration Examples for the Database Agent

These sections provide examples for the database agent:

Example 1: Enabling the Database Agent, page 37-15 Example 2: Reading Binding Entries from a TFTP File, page 37-17 Example 3: Adding Information to the DHCP Snooping Database, page 37-18
Example 1: Enabling the Database Agent

The following example shows how to configure the DHCP snooping database agent to store the bindings at a given location and to view the configuration and operating state:
Router# configure terminal Router(config)# ip dhcp snooping database tftp://10.1.1.1/directory/file Router(config)# end Router# show ip dhcp snooping database detail Agent URL : tftp://10.1.1.1/directory/file Write delay Timer : 300 seconds Abort Timer : 300 seconds Agent Running : No Delay Timer Expiry : 7 (00:00:07) Abort Timer Expiry : Not Running Last Succeded Time : None Last Failed Time : 17:14:25 UTC Sat Jul 7 2001 Last Failed Reason : Unable to access URL. Total Attempts : 21 Startup Failures : 0
37-15
Successful Transfers Successful Reads Successful Writes Media Failures
: : : :
0 0 0 0
Failed Transfers : Failed Reads : Failed Writes :
21 0 21
First successful access: Read Last ignored bindings counters Binding Collisions : Invalid interfaces : Parse failures : Last Ignored Time : None : 0 0 0
Expired leases : Unsupported vlans :
0 0
Total ignored bindings counters: Binding Collisions : 0 Invalid interfaces : 0 Parse failures : 0 Router#
Expired leases : Unsupported vlans :
0 0
The first three lines of output show the configured URL and related timer-configuration values. The next three lines show the operating state and the amount of time left for expiry of write delay and abort timers. Among the statistics shown in the output, startup failures indicate the number of attempts to read or create the file that failed on bootup.
Note
Create a temporary file on the TFTP server with the touch command in the TFTP server daemon directory. With some UNIX implementations, the file should have full read and write access permissions (777). DHCP snooping bindings are keyed on the MAC address and VLAN combination. If an entry in the remote file has an entry for a given MAC address and VLAN set for which the switch already has a binding, the entry from the remote file is ignored when the file is read. This condition is referred to as the binding collision. An entry in a file may no longer be valid because the lease indicated by the entry may have expired by the time it is read. The expired leases counter indicates the number of bindings that are ignored because of this condition. The Invalid interfaces counter refers to the number of bindings that have been ignored when the interface referred by the entry either does not exist on the system or is a router or DHCP snooping trusted interface (if it exists) when the read happened. Unsupported VLANs refers to the number of entries that have been ignored because the indicated VLAN is not supported on the system. The Parse failures counter provides the number of entries that have been ignored when the switch is unable to interpret the meaning of the entries from the file. The switch maintains two sets of counters for these ignored bindings. One provides the counters for a read that has at least one binding ignored by at least one of these conditions. These counters are shown as the Last ignored bindings counters. The total ignored bindings counters provides a sum of the number of bindings that have been ignored because of all the reads since the switch bootup. These two sets of counters are cleared by the clear command. The total counter set may indicate the number of bindings that have been ignored since the last clear.
37-16
OL-3999-08
Chapter 37
Example 2: Reading Binding Entries from a TFTP File

To manually read the entries from a TFTP file, perform this task: Command
Router# show ip dhcp snooping database Router# renew ip dhcp snoop data url Router# show ip dhcp snoop data Router# show ip dhcp snoop bind
Purpose Displays the DHCP snooping database agent statistics. Directs the switch to read the file from the URL. Displays the read status. Verifies whether the bindings were read successfully.
This is an example of how to manually read entries from the tftp://10.1.1.1/directory/file:

Router# show ip dhcp snooping database Agent URL : Write delay Timer : 300 seconds Abort Timer : 300 seconds Agent Running : No Delay Timer Expiry : Not Running Abort Timer Expiry : Not Running Last Succeded Time : None Last Failed Time : None Last Failed Reason : No failure recorded. Total Attempts : 0 Startup Failures : 0 Successful Transfers : 0 Failed Transfers : 0 Successful Reads : 0 Failed Reads : 0 Successful Writes : 0 Failed Writes : 0 Media Failures : 0 Router# renew ip dhcp snoop data tftp://10.1.1.1/directory/file Loading directory/file from 10.1.1.1 (via GigabitEthernet1/1): ! [OK - 457 bytes] Database downloaded successfully. Router# 00:01:29: %DHCP_SNOOPING-6-AGENT_OPERATION_SUCCEEDED: DHCP snooping database Read succeeded. Router# show ip dhcp snoop data Agent URL : Write delay Timer : 300 seconds Abort Timer : 300 seconds Agent Running : No Delay Timer Expiry : Not Running Abort Timer Expiry : Not Running Last Succeded Time : 15:24:34 UTC Sun Jul 8 2001 Last Failed Time : None Last Failed Reason : No failure recorded. Total Attempts : 1 Successful Transfers : 1 Successful Reads : 1 Successful Writes : 0 Media Failures : 0 Router# Router# show ip dhcp snoop bind MacAddress IpAddress Startup Failures Failed Transfers Failed Reads Failed Writes : : : : 0 0 0 0
Lease(sec)
Type
VLAN
Interface
37-17
------------------ --------------00:01:00:01:00:05 1.1.1.1 00:01:00:01:00:02 1.1.1.1 00:01:00:01:00:04 1.1.1.1 00:01:00:01:00:03 1.1.1.1 00:01:00:01:00:01 1.1.1.1 Router# clear ip dhcp snoop bind Router# show ip dhcp snoop bind MacAddress IpAddress ------------------ --------------Router#
---------49810 49810 49810 49810 49810
------------dhcp-snooping dhcp-snooping dhcp-snooping dhcp-snooping dhcp-snooping
---512 512 1536 1024 1
-------------------GigabitEthernet1/1 GigabitEthernet1/1 GigabitEthernet1/1 GigabitEthernet1/1 GigabitEthernet1/1
Lease(sec) ----------
Type -------------
VLAN ----
Interface --------------------
Example 3: Adding Information to the DHCP Snooping Database

To manually add a binding to the DHCP snooping database, perform the following task: Command
Router# show ip dhcp snooping binding Router# ip dhcp snooping binding binding_id vlan vlan_id interface interface expiry lease_time Router# show ip dhcp snooping binding
Purpose Views the DHCP snooping database. Adds the binding using the ip dhcp snooping exec command. Checks the DHCP snooping database.
This example shows how to manually add a binding to the DHCP snooping database:
Router# show ip dhcp snooping binding MacAddress IpAddress Lease(sec) Type VLAN Interface ------------------ --------------- ---------- ------------- ---- -------------------Router# Router# ip dhcp snooping binding 1.1.1 vlan 1 1.1.1.1 interface gi1/1 expiry 1000 Router# show ip dhcp snooping binding MacAddress IpAddress Lease(sec) ------------------ --------------- ---------00:01:00:01:00:01 1.1.1.1 992 Router#
Type ------------dhcp-snooping
VLAN ---1
Interface -------------------GigabitEthernet1/1
Displaying a Binding Table

The DHCP snooping binding table for each switch contains binding entries that correspond to untrusted ports. The table does not contain information about hosts interconnected with a trusted port because each interconnected switch will have its own DHCP snooping binding table. This example shows how to display the DHCP snooping binding information for a switch:
Router# show ip dhcp snooping binding MacAddress IpAddress Lease(sec) ------------------ --------------- ---------00:02:B3:3F:3B:99 55.5.5.2 6943 Type ------------dhcp-snooping VLAN ---10 Interface -------------------FastEthernet6/10
Table 37-2 describes the fields in the show ip dhcp snooping binding command output.
37-18
OL-3999-08
Chapter 37
Table 37-2 show ip dhcp snooping binding Command Output
Field MAC Address IP Address Lease (seconds) Type VLAN Interface
Description Client hardware MAC address Client IP address assigned from the DHCP server IP address lease time Binding type: dynamic binding learned by DHCP snooping or statically-configured binding VLAN number of the client interface Interface that connects to the DHCP client host
Tip
37-19
37-20
OL-3999-08
C H A P T E R
38
Configuring Dynamic ARP Inspection

This chapter describes how to configure dynamic Address Resolution Protocol (ARP) inspection (DAI) on the Catalyst 6500 series switch. The PFC3 supports DAI with Release 12.2(18)SXE and later releases. The PFC2 does not support DAI.
Note

Understanding DAI, page 38-1 Default DAI Configuration, page 38-5 DAI Configuration Guidelines and Restrictions, page 38-6 Configuring DAI, page 38-6 DAI Configuration Samples, page 38-16
Tip
Understanding DAI
These sections describe how DAI helps prevent ARP spoofing attacks:

Understanding ARP, page 38-2 Understanding ARP Spoofing Attacks, page 38-2 Understanding DAI and ARP Spoofing Attacks, page 38-2
38-1
Chapter 38 Understanding DAI
Understanding ARP
ARP provides IP communication within a Layer 2 broadcast domain by mapping an IP address to a MAC address. For example, Host B wants to send information to Host A but does not have the MAC address of Host A in its ARP cache. Host B generates a broadcast message for all hosts within the broadcast domain to obtain the MAC address associated with the IP address of Host A. All hosts within the broadcast domain receive the ARP request, and Host A responds with its MAC address.
Understanding ARP Spoofing Attacks

ARP spoofing attacks and ARP cache poisoning can occur because ARP allows a gratuitous reply from a host even if an ARP request was not received. After the attack, all traffic from the device under attack flows through the attackers computer and then to the router, switch, or host. An ARP spoofing attack can target hosts, switches, and routers connected to your Layer 2 network by poisoning the ARP caches of systems connected to the subnet and by intercepting traffic intended for other hosts on the subnet. Figure 38-1 shows an example of ARP cache poisoning.
Figure 38-1 ARP Cache Poisoning
Host A (IA, MA)
A C
Host B (IB, MB)
Host C (man-in-the-middle) (IC, MC)
Hosts A, B, and C are connected to the switch on interfaces A, B and C, all of which are on the same subnet. Their IP and MAC addresses are shown in parentheses; for example, Host A uses IP address IA and MAC address MA. When Host A needs to communicate to Host B at the IP layer, it broadcasts an ARP request for the MAC address associated with IP address IB. When the switch and Host B receive the ARP request, they populate their ARP caches with an ARP binding for a host with the IP address IA and a MAC address MA; for example, IP address IA is bound to MAC address MA. When Host B responds, the switch and Host A populate their ARP caches with a binding for a host with the IP address IB and the MAC address MB. Host C can poison the ARP caches of the switch, Host A, and Host B by broadcasting forged ARP responses with bindings for a host with an IP address of IA (or IB) and a MAC address of MC. Hosts with poisoned ARP caches use the MAC address MC as the destination MAC address for traffic intended for IA or IB. This means that Host C intercepts that traffic. Because Host C knows the true MAC addresses associated with IA and IB, it can forward the intercepted traffic to those hosts by using the correct MAC address as the destination. Host C has inserted itself into the traffic stream from Host A to Host B, which is the topology of the classic man-in-the middle attack.
Understanding DAI and ARP Spoofing Attacks

DAI is a security feature that validates ARP packets in a network. DAI intercepts, logs, and discards ARP packets with invalid IP-to-MAC address bindings. This capability protects the network from some man-in-the-middle attacks.
38-2
111750
OL-3999-08
Chapter 38
Configuring Dynamic ARP Inspection Understanding DAI
DAI ensures that only valid ARP requests and responses are relayed. The switch performs these activities:

Intercepts all ARP requests and responses on untrusted ports Verifies that each of these intercepted packets has a valid IP-to-MAC address binding before updating the local ARP cache or before forwarding the packet to the appropriate destination Drops invalid ARP packets
DAI determines the validity of an ARP packet based on valid IP-to-MAC address bindings stored in a trusted database, the DHCP snooping binding database. This database is built by DHCP snooping if DHCP snooping is enabled on the VLANs and on the switch. If the ARP packet is received on a trusted interface, the switch forwards the packet without any checks. On untrusted interfaces, the switch forwards the packet only if it is valid. DAI can validate ARP packets against user-configured ARP access control lists (ACLs) for hosts with statically configured IP addresses (see Applying ARP ACLs for DAI Filtering section on page 38-8). The switch logs dropped packets (see the Logging of Dropped Packets section on page 38-5). You can configure DAI to drop ARP packets when the IP addresses in the packets are invalid or when the MAC addresses in the body of the ARP packets do not match the addresses specified in the Ethernet header (see the Enabling Additional Validation section on page 38-11).
Interface Trust States and Network Security

DAI associates a trust state with each interface on the switch. Packets arriving on trusted interfaces bypass all DAI validation checks, and those arriving on untrusted interfaces undergo the DAI validation process. In a typical network configuration, you configure all switch ports connected to host ports as untrusted and configure all switch ports connected to switches as trusted. With this configuration, all ARP packets entering the network from a given switch bypass the security check. No other validation is needed at any other place in the VLAN or in the network. You configure the trust setting by using the ip arp inspection trust interface configuration command.
Caution
Use the trust state configuration carefully. Configuring interfaces as untrusted when they should be trusted can result in a loss of connectivity. In Figure 38-2, assume that both Switch A and Switch B are running DAI on the VLAN that includes Host 1 and Host 2. If Host 1 and Host 2 acquire their IP addresses from the DHCP server connected to Switch A, only Switch A binds the IP-to-MAC address of Host 1. Therefore, if the interface between Switch A and Switch B is untrusted, the ARP packets from Host 1 are dropped by Switch B. Connectivity between Host 1 and Host 2 is lost.
38-3
Chapter 38 Understanding DAI
Figure 38-2 ARP Packet Validation on a VLAN Enabled for DAI
DHCP server
A Port 6/3 Port 3/3
Host 1
Host 2
Configuring interfaces to be trusted when they are actually untrusted leaves a security hole in the network. If Switch A is not running DAI, Host 1 can easily poison the ARP cache of Switch B (and Host 2, if the link between the switches is configured as trusted). This condition can occur even though Switch B is running DAI. DAI ensures that hosts (on untrusted interfaces) connected to a switch running DAI do not poison the ARP caches of other hosts in the network. However, DAI does not prevent hosts in other portions of the network from poisoning the caches of the hosts that are connected to a switch running DAI. In cases in which some switches in a VLAN run DAI and other switches do not, configure the interfaces connecting such switches as untrusted. However, to validate the bindings of packets from switches where DAI is not configured, configure ARP ACLs on the switch running DAI. When you cannot determine such bindings, isolate switches running DAI at Layer 3 from switches not running DAI. For configuration information, see the Sample Two: One Switch Supports DAI section on page 38-21.
Note
Depending on the setup of the DHCP server and the network, it might not be possible to validate a given ARP packet on all switches in the VLAN.
Rate Limiting of ARP Packets

The switch performs DAI validation checks, which rate limits incoming ARP packets to prevent a denial-of-service attack. By default, the rate for untrusted interfaces is 15 packets per second (pps). Trusted interfaces are not rate limited. You can change this setting by using the ip arp inspection limit interface configuration command. When the rate of incoming ARP packets exceeds the configured limit, the switch places the port in the error-disabled state. The port remains in that state until you intervene. You can use the errdisable recovery global configuration command to enable error disable recovery so that ports automatically emerge from this state after a specified timeout period. For configuration information, see the Configuring ARP Packet Rate Limiting section on page 38-9.
Relative Priority of ARP ACLs and DHCP Snooping Entries

DAI uses the DHCP snooping binding database for the list of valid IP-to-MAC address bindings.
38-4
130194
OL-3999-08
Chapter 38
Configuring Dynamic ARP Inspection Default DAI Configuration
ARP ACLs take precedence over entries in the DHCP snooping binding database. The switch uses ACLs only if you configure them by using the ip arp inspection filter global configuration command. The switch first compares ARP packets to user-configured ARP ACLs. If the ARP ACL denies the ARP packet, the switch also denies the packet even if a valid binding exists in the database populated by DHCP snooping.
Logging of Dropped Packets

When the switch drops a packet, it places an entry in the log buffer and then generates system messages on a rate-controlled basis. After the message is generated, the switch clears the entry from the log buffer. Each log entry contains flow information, such as the receiving VLAN, the port number, the source and destination IP addresses, and the source and destination MAC addresses. You use the ip arp inspection log-buffer global configuration command to configure the number of entries in the buffer and the number of entries needed in the specified interval to generate system messages. You specify the type of packets that are logged by using the ip arp inspection vlan logging global configuration command. For configuration information, see the Configuring DAI Logging section on page 38-13.
Default DAI Configuration

Table 38-1 shows the default DAI configuration.
Table 38-1 Default DAI Configuration
Feature DAI Interface trust state Rate limit of incoming ARP packets
Default Setting Disabled on all VLANs. All interfaces are untrusted. The rate is 15 pps on untrusted interfaces, assuming that the network is a Layer 2-switched network with a host connecting to as many as 15 new hosts per second. The rate is unlimited on all trusted interfaces. The burst interval is 1 second.
ARP ACLs for non-DHCP environments Validation checks Log buffer
No ARP ACLs are defined. No checks are performed. When DAI is enabled, all denied or dropped ARP packets are logged. The number of entries in the log is 32. The number of system messages is limited to 5 per second. The logging-rate interval is 1 second.
Per-VLAN logging
All denied or dropped ARP packets are logged.
38-5
Chapter 38 DAI Configuration Guidelines and Restrictions
DAI Configuration Guidelines and Restrictions

When configuring DAI, follow these guidelines and restrictions:

DAI is an ingress security feature; it does not perform any egress checking. DAI is not effective for hosts connected to switches that do not support DAI or that do not have this feature enabled. Because man-in-the-middle attacks are limited to a single Layer 2 broadcast domain, separate the domain with DAI checks from the one with no checking. This action secures the ARP caches of hosts in the domain enabled for DAI. DAI depends on the entries in the DHCP snooping binding database to verify IP-to-MAC address bindings in incoming ARP requests and ARP responses. Make sure to enable DHCP snooping to permit ARP packets that have dynamically assigned IP addresses. For configuration information, see Chapter 37, Configuring DHCP Snooping. When DHCP snooping is disabled or in non-DHCP environments, use ARP ACLs to permit or to deny packets. DAI is supported on access ports, trunk ports, EtherChannel ports, and private VLAN ports. A physical port can join an EtherChannel port channel only when the trust state of the physical port and the channel port match. Otherwise, the physical port remains suspended in the port channel. A port channel inherits its trust state from the first physical port that joins the channel. Consequently, the trust state of the first physical port need not match the trust state of the channel. Conversely, when you change the trust state on the port channel, the switch configures a new trust state on all the physical ports that comprise the channel.
The operating rate for the port channel is cumulative across all the physical ports within the channel. For example, if you configure the port channel with an ARP rate-limit of 400 pps, all the interfaces combined on the channel receive an aggregate 400 pps. The rate of incoming ARP packets on EtherChannel ports is equal to the sum of the incoming rate of packets from all the channel members. Configure the rate limit for EtherChannel ports only after examining the rate of incoming ARP packets on the channel-port members. The rate of incoming packets on a physical port is checked against the port-channel configuration rather than the physical-ports configuration. The rate-limit configuration on a port channel is independent of the configuration on its physical ports. If the EtherChannel receives more ARP packets than the configured rate, the channel (including all physical ports) is placed in the error-disabled state.
Make sure to limit the rate of ARP packets on incoming trunk ports. Configure trunk ports with higher rates to reflect their aggregation and to handle packets across multiple DAI-enabled VLANs. You also can use the ip arp inspection limit none interface configuration command to make the rate unlimited. A high rate-limit on one VLAN can cause a denial-of-service attack to other VLANs when the software places the port in the error-disabled state.
Configuring DAI
These sections describe how to configure DAI:

Enabling DAI on VLANs, page 38-7 Configuring the DAI Interface Trust State, page 38-8 Applying ARP ACLs for DAI Filtering, page 38-8
38-6
OL-3999-08
Chapter 38
Configuring Dynamic ARP Inspection Configuring DAI
Configuring ARP Packet Rate Limiting, page 38-9 Enabling DAI Error-Disabled Recovery, page 38-11 Enabling Additional Validation, page 38-11 Configuring DAI Logging, page 38-13 Displaying DAI Information, page 38-15
Enabling DAI on VLANs

To enable DAI on VLANs, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip arp inspection vlan {vlan_ID | vlan_range} Router(config)# no ip arp inspection vlan {vlan_ID | vlan_range}
Purpose Enters global configuration mode. Enables DAI on VLANs (disabled by default). Disables DAI on VLANs. Verifies the configuration.
Step 3
Router(config-if)# do show ip arp inspection vlan {vlan_ID | vlan_range} | begin Vlan
You can enable DAI on a single VLAN or a range of VLANs:

To enable a single VLAN, enter a single VLAN number. To enable a range of VLANs, enter a dash-separated pair of VLAN numbers. You can enter a comma-separated list of VLAN numbers and dash-separated pairs of VLAN numbers.
This example shows how to enable DAI on VLANs 10 through 12:

Router# configure terminal Router(config)# ip arp inspection vlan 10-12
This example shows another way to enable DAI on VLANs 10 through 12:
Router# configure terminal Router(config)# ip arp inspection vlan 10,11,12
This example shows how to enable DAI on VLANs 10 through 12 and VLAN 15:
Router# configure terminal Router(config)# ip arp inspection vlan 10-12,15

Router(config)# do show ip arp inspection vlan 10-12,15 | begin Vlan Vlan Configuration Operation ACL Match Static ACL ----------------------------------------10 Enabled Inactive 11 Enabled Inactive 12 Enabled Inactive 15 Enabled Inactive
38-7
Chapter 38 Configuring DAI
Vlan ---10 11 12 15
ACL Logging ----------Deny Deny Deny Deny
DHCP Logging -----------Deny Deny Deny Deny
Configuring the DAI Interface Trust State

The switch forwards ARP packets that it receives on a trusted interface, but does not check them. On untrusted interfaces, the switch intercepts all ARP requests and responses. It verifies that the intercepted packets have valid IP-to-MAC address bindings before updating the local cache and before forwarding the packet to the appropriate destination. The switch drops invalid packets and logs them in the log buffer according to the logging configuration specified with the ip arp inspection vlan logging global configuration command. For more information, see the Configuring DAI Logging section on page 38-13. To configure the DAI interface trust state, perform this task: Command
Router# configure terminal Router(config)# interface {type port-channel number}
1

slot/port |
Specifies the interface connected to another switch, and enter interface configuration mode. Configures the connection between switches as trusted (default: untrusted). Configures the connection between switches as untrusted. Verifies the DAI configuration.
Router(config-if)# ip arp inspection trust
Router(config)# no ip arp inspection trust
Step 4
Router(config-if)# do show ip arp inspection interfaces 1.
This example shows how to configure Fast Ethernet port 5/12 as trusted:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/12 Router(config-if)# ip arp inspection trust Router(config-if)# do show ip arp inspection interfaces | include Int|--|5/12 Interface Trust State Rate (pps) Burst Interval --------------- --------------------------------Fa5/12 Trusted None N/A
Applying ARP ACLs for DAI Filtering

Note
See the Cisco IOS Master Command List, Release 12.2SX, for information about the arp access-list command.
38-8
OL-3999-08
Chapter 38
To apply an ARP ACL, perform this task: Command

Router# configure terminal Router# ip arp inspection filter arp_acl_name vlan {vlan_ID | vlan_range} [static] Router(config)# do show ip arp inspection vlan {vlan_ID | vlan_range}
Purpose Enters global configuration mode. Applies the ARP ACL to a VLAN. Verifies your entries.
When applying ARP ACLs, note the following information:
For vlan_range, you can specify a single VLAN or a range of VLANs:

To specify a single VLAN, enter a single VLAN number. To specify a range of VLANs, enter a dash-separated pair of VLAN numbers. You can enter a comma-separated list of VLAN numbers and dash-separated pairs of VLAN
numbers.
(Optional) Specify static to treat implicit denies in the ARP ACL as explicit denies and to drop packets that do not match any previous clauses in the ACL. DHCP bindings are not used. If you do not specify this keyword, it means that there is no explicit deny in the ACL that denies the packet, and DHCP bindings determine whether a packet is permitted or denied if the packet does not match any clauses in the ACL.
ARP packets containing only IP-to-MAC address bindings are compared against the ACL. Packets are permitted only if the access list permits them.
This example shows how to apply an ARP ACL named example_arp_acl to VLANs 10 through 12 and VLAN 15:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection filter example_arp_acl vlan 10-12,15 Router(config)# do show ip arp inspection vlan 10-12,15 | begin Vlan Vlan Configuration Operation ACL Match Static ACL ----------------------------------------10 Enabled Inactive example_arp_acl No 11 Enabled Inactive example_arp_acl No 12 Enabled Inactive example_arp_acl No 15 Enabled Inactive example_arp_acl No Vlan ---10 11 12 15 ACL Logging ----------Deny Deny Deny Deny DHCP Logging -----------Deny Deny Deny Deny
Configuring ARP Packet Rate Limiting

When DAI is enabled, the switch performs ARP packet validation checks, which makes the switch vulnerable to an ARP-packet denial-of-service attack. ARP packet rate limiting can prevent an ARP-packet denial-of-service attack.
38-9
To configure ARP packet rate limiting on a port, perform this task: Command
Router# configure terminal Router(config)# interface {type port-channel number}
1

slot/port |
Selects the interface to be configured. (Optional) Configures ARP packet rate limiting. Clears the ARP packet rate-limiting configuration. Verifies the configuration.
Router(config-if)# ip arp inspection limit {rate pps [burst interval seconds] | none} Router(config-if)# no ip arp inspection limit
Step 4
Router(config-if)# do show ip arp inspection interfaces 1.
When configuring ARP packet rate limiting, note the following information:

The default rate is 15 pps on untrusted interfaces and unlimited on trusted interfaces. For rate pps, specify an upper limit for the number of incoming packets processed per second. The range is 0 to 2048 pps. The rate none keywords specify that there is no upper limit for the rate of incoming ARP packets that can be processed. (Optional) For burst interval seconds (default is 1), specify the consecutive interval, in seconds, over which the interface is monitored for a high rate of ARP packets.The range is 1 to 15. When the rate of incoming ARP packets exceeds the configured limit, the switch places the port in the error-disabled state. The port remains in the error-disabled state until you enable error-disabled recovery, which allows the port to emerge from the error-disabled state after a specified timeout period. Unless you configure a rate-limiting value on an interface, changing the trust state of the interface also changes its rate-limiting value to the default value for the configured trust state. After you configure the rate-limiting value, the interface retains the rate-limiting value even when you change its trust state. If you enter the no ip arp inspection limit interface configuration command, the interface reverts to its default rate-limiting value. For configuration guidelines about limiting the rate of incoming ARP packets on trunk ports and EtherChannel ports, see the DAI Configuration Guidelines and Restrictions section on page 38-6.
This example shows how to configure ARP packet rate limiting on Fast Ethernet port 5/14:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/14 Router(config-if)# ip arp inspection limit rate 20 burst interval 2 Router(config-if)# do show ip arp inspection interfaces | include Int|--|5/14 Interface Trust State Rate (pps) Burst Interval --------------- --------------------------------Fa5/14 Untrusted 20 2
38-10
OL-3999-08
Chapter 38
Enabling DAI Error-Disabled Recovery

To enable DAI error disabled recovery, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# errdisable recovery cause arp-inspection Router(config-if)# no errdisable recovery cause arp-inspection
Purpose Enters global configuration mode. (Optional) Enables DAI error disabled recovery (disabled by default). Disables DAI error disabled recovery. Verifies the configuration.
Step 3
Router(config)# do show errdisable recovery | include Reason|---|arp-
This example shows how to enable DAI error disabled recovery:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# errdisable recovery cause arp-inspection Router(config)# do show errdisable recovery | include Reason|---|arpErrDisable Reason Timer Status -----------------------------arp-inspection Enabled
Enabling Additional Validation

DAI intercepts, logs, and discards ARP packets with invalid IP-to-MAC address bindings. You can enable additional validation on the destination MAC address, the sender and target IP addresses, and the source MAC address. To enable additional validation, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip arp inspection validate {[dst-mac] [ip] [src-mac]} Router(config)# no ip arp inspection validate {[dst-mac] [ip] [src-mac]}
Purpose Enters global configuration mode. (Optional) Enables additional validation (default is none). Disables additional validation. Verifies the configuration.
Step 3
Router(config)# do show ip arp inspection | include abled$
When enabling additional validation, note the following information:

You must specify at least one of the keywords. Each ip arp inspection validate command overrides the configuration from any previous commands. If an ip arp inspection validate command enables src and dst mac validations, and a second ip arp inspection validate command enables IP validation only, the src and dst mac validations are disabled as a result of the second command.
38-11
These are the additional validations:

dst-macChecks the destination MAC address in the Ethernet header against the target MAC
address in ARP body. This check is performed for ARP responses. When enabled, packets with different MAC addresses are classified as invalid and are dropped.
ipChecks the ARP body for invalid and unexpected IP addresses. Addresses include 0.0.0.0,
255.255.255.255, and all IP multicast addresses. Sender IP addresses are checked in all ARP requests and responses, and target IP addresses are checked only in ARP responses.
src-macChecks the source MAC address in the Ethernet header against the sender MAC
address in the ARP body. This check is performed on both ARP requests and responses. When enabled, packets with different MAC addresses are classified as invalid and are dropped. This example shows how to enable src-mac additional validation:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection validate src-mac Router(config)# do show ip arp inspection | include abled$ Source Mac Validation : Enabled Destination Mac Validation : Disabled IP Address Validation : Disabled
This example shows how to enable dst-mac additional validation:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection validate dst-mac Router(config)# do show ip arp inspection | include abled$ Source Mac Validation : Disabled Destination Mac Validation : Enabled IP Address Validation : Disabled
This example shows how to enable ip additional validation:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection validate ip Router(config)# do show ip arp inspection | include abled$ Source Mac Validation : Disabled Destination Mac Validation : Disabled IP Address Validation : Enabled
This example shows how to enable src-mac and dst-mac additional validation:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection validate src-mac dst-mac Router(config)# do show ip arp inspection | include abled$ Source Mac Validation : Enabled Destination Mac Validation : Enabled IP Address Validation : Disabled
This example shows how to enable src-mac, dst-mac, and ip additional validation:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection validate src-mac dst-mac ip Router(config)# do show ip arp inspection | include abled$ Source Mac Validation : Enabled Destination Mac Validation : Enabled IP Address Validation : Enabled
38-12
OL-3999-08
Chapter 38
Configuring DAI Logging

These sections describe DAI logging:

DAI Logging Overview, page 38-13 Configuring the DAI Logging Buffer Size, page 38-13 Configuring the DAI Logging System Messages, page 38-14 Configuring DAI Log Filtering, page 38-14
DAI Logging Overview

When DAI drops a packet, it places an entry in the log buffer and then generates system messages on a rate-controlled basis. After the message is generated, DAI clears the entry from the log buffer. Each log entry contains flow information, such as the receiving VLAN, the port number, the source and destination IP addresses, and the source and destination MAC addresses. A log-buffer entry can represent more than one packet. For example, if an interface receives many packets on the same VLAN with the same ARP parameters, DAI combines the packets as one entry in the log buffer and generates a single system message for the entry. If the log buffer overflows, it means that a log event does not fit into the log buffer, and the display for the show ip arp inspection log privileged EXEC command is affected. Two dashes (--) appear instead of data except for the packet count and the time. No other statistics are provided for the entry. If you see this entry in the display, increase the number of entries in the log buffer or increase the logging rate.
Configuring the DAI Logging Buffer Size

To configure the DAI logging buffer size, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip arp inspection log-buffer entries number Router(config)# no ip arp inspection log-buffer entries
Purpose Enters global configuration mode. Configures the DAI logging buffer size (range is 0 to 1024). Reverts to the default buffer size (32). Verifies the configuration.
Step 3
Router(config)# do show ip arp inspection log | include Size
This example shows how to configure the DAI logging buffer for 64 messages:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection log-buffer entries 64 Router(config)# do show ip arp inspection log | include Size Total Log Buffer Size : 64
38-13
Configuring the DAI Logging System Messages

To configure the DAI logging system messages, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip arp inspection log-buffer logs number_of_messages interval length_in_seconds Router(config)# no ip arp inspection log-buffer logs
Purpose Enters global configuration mode. Configures the DAI logging buffer. Reverts to the default system message configuration. Verifies the configuration.
Step 3
Router(config)# do show ip arp inspection log
When configuring the DAI logging system messages, note the following information:

For logs number_of_messages (default is 5), the range is 0 to 1024. A 0 value means that the entry is placed in the log buffer, but a system message is not generated. For interval length_in_seconds (default is 1), the range is 0 to 86400 seconds (1 day). A 0 value means that a system message is immediately generated (and the log buffer is always empty). An interval setting of 0 overrides a log setting of 0. System messages are sent at the rate of number_of_messages per length_in_seconds.
This example shows how to configure DAI logging to send 12 messages every 2 seconds:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection log-buffer logs 12 interval 2 Router(config)# do show ip arp inspection log | include Syslog Syslog rate : 12 entries per 2 seconds.
This example shows how to configure DAI logging to send 20 messages every 60 seconds.
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection log-buffer logs 20 interval 60 Router(config)# do show ip arp inspection log | include Syslog Syslog rate : 20 entries per 60 seconds.
Configuring DAI Log Filtering

To configure DAI log filtering, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip arp inspection vlan vlan_range logging {acl-match {matchlog | none} | dhcp-bindings {all | none | permit}} Router(config)# do show running-config | include ip arp inspection vlan vlan_range
Purpose Enters global configuration mode. Configures log filtering for each VLAN.
Step 3
38-14
OL-3999-08
Chapter 38
When configuring the DAI log filtering, note the following information:

By default, all denied packets are logged. For vlan_range, you can specify a single VLAN or a range of VLANs:
To specify a single VLAN, enter a single VLAN number. To specify a range of VLANs, enter a dash-separated pair of VLAN numbers. You can enter a comma-separated list of VLAN numbers and dash-separated pairs of VLAN
numbers.
acl-match matchlogLogs packets based on the DAI ACL configuration. If you specify the matchlog keyword in this command and the log keyword in the permit or deny ARP access-list configuration command, ARP packets permitted or denied by the ACL are logged. acl-match noneDoes not log packets that match ACLs. dhcp-bindings allLogs all packets that match DHCP bindings. dhcp-bindings noneDoes not log packets that match DHCP bindings. dhcp-bindings permit Logs DHCP-binding permitted packets.
This example shows how to configure the DAI log filtering for VLAN 100 not to log packets that match ACLs:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip arp inspection vlan 100 logging acl-match none Router(config)# do show running-config | include ip arp inspection vlan 100 ip arp inspection vlan 100 logging acl-match none
Displaying DAI Information

To display DAI information, use the privileged EXEC commands described in Table 38-2.
Table 38-2 Commands for Displaying DAI Information
Command show arp access-list [acl_name]
Description Displays detailed information about ARP ACLs.
show ip arp inspection interfaces [interface_id] Displays the trust state and the rate limit of ARP packets for the specified interface or all interfaces. show ip arp inspection vlan vlan_range Displays the configuration and the operating state of DAI for the specified VLAN. If no VLANs are specified or if a range is specified, displays information only for VLANs with DAI enabled (active).
38-15
Chapter 38 DAI Configuration Samples
To clear or display DAI statistics, use the privileged EXEC commands in Table 38-3.
Table 38-3 Commands for Clearing or Displaying DAI Statistics
Command clear ip arp inspection statistics show ip arp inspection statistics [vlan vlan_range]
Description Clears DAI statistics. Displays statistics for forwarded, dropped, MAC validation failure, IP validation failure, ACL permitted and denied, and DHCP permitted and denied packets for the specified VLAN. If no VLANs are specified or if a range is specified, displays information only for VLANs with DAI enabled (active).
For the show ip arp inspection statistics command, the switch increments the number of forwarded packets for each ARP request and response packet on a trusted DAI port. The switch increments the number of ACL-permitted or DHCP-permitted packets for each packet that is denied by source MAC, destination MAC, or IP validation checks, and the switch increments the appropriate failure count. To clear or display DAI logging information, use the privileged EXEC commands in Table 38-4:
Table 38-4 Commands for Clearing or Displaying DAI Logging Information
Command clear ip arp inspection log show ip arp inspection log
Description Clears the DAI log buffer. Displays the configuration and contents of the DAI log buffer.
DAI Configuration Samples

This section includes these samples:

Sample One: Two Switches Support DAI, page 38-16 Sample Two: One Switch Supports DAI, page 38-21
Sample One: Two Switches Support DAI

This procedure shows how to configure DAI when two switches support this feature. Host 1 is connected to Switch A, and Host 2 is connected to Switch B as shown in Figure 38-2 on page 38-4. Both switches are running DAI on VLAN 1 where the hosts are located. A DHCP server is connected to Switch A. Both hosts acquire their IP addresses from the same DHCP server. Switch A has the bindings for Host 1 and Host 2, and Switch B has the binding for Host 2. Switch A Fast Ethernet port 6/3 is connected to the Switch B Fast Ethernet port 3/3.
Note
DAI depends on the entries in the DHCP snooping binding database to verify IP-to-MAC address bindings in incoming ARP requests and ARP responses. Make sure to enable DHCP snooping to permit ARP packets that have dynamically assigned IP addresses. For configuration information, see Chapter 37, Configuring DHCP Snooping. This configuration does not work if the DHCP server is moved from Switch A to a different location.
38-16
OL-3999-08
Chapter 38
Configuring Dynamic ARP Inspection DAI Configuration Samples
To ensure that this configuration does not compromise security, configure Fast Ethernet port 6/3 on Switch A and Fast Ethernet port 3/3 on Switch B as trusted.
Configuring Switch A
To enable DAI and configure Fast Ethernet port 6/3 on Switch A as trusted, follow these steps:
Step 1
Verify the connection between switches Switch A and Switch B:

SwitchA# show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone Device ID SwitchB SwitchA# Local Intrfce Fas 6/3 Holdtme 177 Capability R S I Platform WS-C6506 Port ID Fas 3/3
Step 2
Enable DAI on VLAN 1 and verify the configuration:

SwitchA# configure terminal Enter configuration commands, one per line. SwitchA(config)# ip arp inspection vlan 1 SwitchA(config)# end SwitchA# show ip arp inspection vlan 1 Source Mac Validation : Disabled Destination Mac Validation : Disabled IP Address Validation : Disabled Vlan ---1 Vlan ---1 SwitchA# Configuration ------------Enabled ACL Logging ----------Deny Operation --------Active DHCP Logging -----------Deny ACL Match --------Static ACL ---------End with CNTL/Z.
Step 3
Configure Fast Ethernet port 6/3 as trusted:

SwitchA# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SwitchA(config)# interface fastethernet 6/3 SwitchA(config-if)# ip arp inspection trust SwitchA(config-if)# end SwitchA# show ip arp inspection interfaces fastethernet 6/3 Interface Trust State --------------- ----------Fa6/3 Trusted SwitchA# Rate (pps) ---------None
Step 4
Verify the bindings:

SwitchA# show ip dhcp snooping binding MacAddress IpAddress Lease(sec) ------------------ --------------- ---------00:02:00:02:00:02 1.1.1.2 4993 SwitchA# Type ------------dhcp-snooping VLAN ---1 Interface -------------------FastEthernet6/4
38-17
Step 5
Check the statistics before and after DAI processes any packets:
SwitchA# show ip arp inspection statistics vlan 1 Vlan ---1 Vlan ---1 Forwarded --------0 DHCP Permits -----------0 Dropped ------0 ACL Permits ----------0 DHCP Drops ---------0 ACL Drops ---------0
Source MAC Failures ------------------0
Vlan Dest MAC Failures -------------------1 0 SwitchA#
IP Validation Failures ---------------------0
If Host 1 then sends out two ARP requests with an IP address of 1.1.1.2 and a MAC address of 0002.0002.0002, both requests are permitted, as reflected in the following statistics:
SwitchA# show ip arp inspection statistics vlan 1 Vlan ---1 Vlan ---1 Forwarded --------2 DHCP Permits -----------2 Dropped ------0 ACL Permits ----------0 DHCP Drops ---------0 ACL Drops ---------0
If Host 1 then tries to send an ARP request with an IP address of 1.1.1.3, the packet is dropped and an error message is logged:
00:12:08: %SW_DAI-4-DHCP_SNOOPING_DENY: 2 Invalid ARPs (Req) on Fa6/4, vlan 1.([0002.0002.0002/1.1.1.3/0000.0000.0000/0.0.0.0/02:42:35 UTC Tue Jul 10 2001]) SwitchA# show ip arp inspection statistics vlan 1 SwitchA#
The statistics will display as follows:

Vlan ---1 Vlan ---1 Forwarded --------2 DHCP Permits -----------2 Dropped ------2 ACL Permits ----------0 DHCP Drops ---------2 ACL Drops ---------0
38-18
OL-3999-08
Chapter 38
Configuring Switch B
To enable DAI and configure Fast Ethernet port 3/3 on Switch B as trusted, follow these steps:
Step 1
Verify the connectivity:

SwitchA# show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone Device ID SwitchB SwitchB# Local Intrfce Fas 3/3 Holdtme 120 Capability R S I Platform WS-C6506 Port ID Fas 6/3
Step 2
Enable DAI on VLAN 1, and verify the configuration:

SwitchB# configure terminal Enter configuration commands, one per line. SwitchB(config)# ip arp inspection vlan 1 SwitchB(config)# end SwitchB# show ip arp inspection vlan 1 Source Mac Validation : Disabled Destination Mac Validation : Disabled IP Address Validation : Disabled Vlan ---1 Vlan ---1 SwitchB# Configuration ------------Enabled ACL Logging ----------Deny Operation --------Active DHCP Logging -----------Deny ACL Match --------Static ACL ---------End with CNTL/Z.
Step 3
Configure Fast Ethernet port 3/3 as trusted:

SwitchB# configure terminal Enter configuration commands, one per line. SwitchB(config)# interface fastethernet 3/3 SwitchB(config-if)# ip arp inspection trust SwitchB(config-if)# end SwitchB# show ip arp inspection interfaces End with CNTL/Z.
Interface Trust State --------------- ----------Gi1/1 Untrusted Gi1/2 Untrusted Gi3/1 Untrusted Gi3/2 Untrusted Fa3/3 Trusted Fa3/4 Untrusted Fa3/5 Untrusted Fa3/6 Untrusted Fa3/7 Untrusted <output truncated> SwitchB#
Rate (pps) ---------15 15 15 15 None 15 15 15 15
Step 4
Verify the list of DHCP snooping bindings:

SwitchB# show ip dhcp snooping binding MacAddress IpAddress Lease(sec) Type VLAN Interface
38-19
-----------------00:01:00:01:00:01 SwitchB#
--------------1.1.1.1
---------4995
------------dhcp-snooping
---1
-------------------FastEthernet3/4
Step 5
Check the statistics before and after DAI processes any packets:
SwitchB# show ip arp inspection statistics vlan 1 Vlan ---1 Vlan ---1 Forwarded --------0 DHCP Permits -----------0 Dropped ------0 ACL Permits ----------0 DHCP Drops ---------0 ACL Drops ---------0
Vlan Dest MAC Failures -------------------1 0 SwitchB#
If Host 2 then sends out an ARP request with the IP address 1.1.1.1 and the MAC address 0001.0001.0001, the packet is forwarded and the statistics are updated appropriately:
If Host 2 attempts to send an ARP request with the IP address 1.1.1.2, DAI drops the request and logs a system message:
00:18:08: %SW_DAI-4-DHCP_SNOOPING_DENY: 1 Invalid ARPs (Req) on Fa3/4, vlan 1.([0001.0001.0001/1.1.1.2/0000.0000.0000/0.0.0.0/01:53:21 UTC Fri May 23 2003]) SwitchB#
The statistics display as follows:

38-20
OL-3999-08
Chapter 38
Sample Two: One Switch Supports DAI

This procedure shows how to configure DAI when Switch B shown in Figure 38-2 on page 38-4 does not support DAI or DHCP snooping. If switch Switch B does not support DAI or DHCP snooping, configuring Fast Ethernet port 6/3 on Switch A as trusted creates a security hole because both Switch A and Host 1 could be attacked by either Switch B or Host 2. To prevent this possibility, you must configure Fast Ethernet port 6/3 on Switch A as untrusted. To permit ARP packets from Host 2, you must set up an ARP ACL and apply it to VLAN 1. If the IP address of Host 2 is not static, which would make it impossible to apply the ACL configuration on Switch A, you must separate Switch A from Switch B at Layer 3 and use a router to route packets between them. To set up an ARP ACL on switch Switch A, follow these steps:
Step 1
Configure the access list to permit the IP address 1.1.1.1 and the MAC address 0001.0001.0001, and verify the configuration:
SwitchA# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SwitchA(config)# arp access-list H2 SwitchA(config-arp-nacl)# permit ip host 1.1.1.1 mac host 1.1.1 SwitchA(config-arp-nacl)# end SwitchA# show arp access-list ARP access list H2 permit ip host 1.1.1.1 mac host 0001.0001.0001
Step 2
Apply the ACL to VLAN 1, and verify the configuration:

SwitchA# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SwitchA(config)# ip arp inspection filter H2 vlan 1 SwitchA(config)# end SwitchA# SwitchA# show ip arp inspection vlan 1 Source Mac Validation : Disabled Destination Mac Validation : Disabled IP Address Validation : Disabled Vlan ---1 Vlan ---1 SwitchA# Configuration ------------Enabled ACL Logging ----------Deny Operation --------Active DHCP Logging -----------Deny ACL Match --------H2 Static ACL ---------No
Step 3
Configure Fast Ethernet port 6/3 as untrusted, and verify the configuration:
SwitchA# configure terminal Enter configuration commands, one per line. End with CNTL/Z. SwitchA(config)# interface fastethernet 6/3 SwitchA(config-if)# no ip arp inspection trust SwitchA(config-if)# end Switch# show ip arp inspection interfaces fastethernet 6/3 Interface --------------Trust State ----------Rate (pps) ----------
38-21
Fa6/3 Switch#
Untrusted
15
When Host 2 sends 5 ARP requests through Fast Ethernet port 6/3 on Switch A and a get is permitted by Switch A, the statistics are updated appropriately:
Switch# show ip arp inspection statistics vlan 1 Vlan Forwarded Dropped DHCP Drops ACL Drops -----------------------------------1 5 0 0 0 Vlan DHCP Permits ACL Permits Source MAC Failures ------------------------------------------1 0 5 0 Vlan Dest MAC Failures IP Validation Failures ----------------------------------------1 0 0 Switch#
Tip
38-22
OL-3999-08
C H A P T E R
39
Configuring Traffic Storm Control

This chapter describes how to configure the traffic storm control feature on the Catalyst 6500 series switches.
Note

Understanding Traffic Storm Control, page 39-1 Default Traffic Storm Control Configuration, page 39-3 Traffic Storm Control Guidelines and Restrictions, page 39-3 Enabling Traffic Storm Control, page 39-4
Tip
Understanding Traffic Storm Control

A traffic storm occurs when packets flood the LAN, creating excessive traffic and degrading network performance. The traffic storm control feature prevents LAN ports from being disrupted by a broadcast, multicast, or unicast traffic storm on physical interfaces. Traffic storm control (also called traffic suppression) monitors incoming traffic levels over a 1-second traffic storm control interval and, during the interval, compares the traffic level with the traffic storm control level that you configure. The traffic storm control level is a percentage of the total available bandwidth of the port. Each port has a single traffic storm control level that is used for all types of traffic (broadcast, multicast, and unicast).
39-1
Chapter 39 Understanding Traffic Storm Control
Traffic storm control monitors the level of each traffic type for which you enable traffic storm control in 1-second traffic storm control intervals. Within an interval, when the ingress traffic for which traffic storm control is enabled reaches the traffic storm control level that is configured on the port, traffic storm control drops the traffic until the traffic storm control interval ends. Figure 39-1 shows the broadcast traffic patterns on a LAN interface over a given interval. In this example, traffic storm control occurs between times T1 and T2 and between T4 and T5. During those intervals, the amount of broadcast traffic exceeded the configured threshold.
Figure 39-1 Broadcast Suppression
The traffic storm control threshold numbers and the time interval combination make the traffic storm control algorithm work with different levels of granularity. A higher threshold allows more packets to pass through. Traffic storm control on the Catalyst 6500 series switches is implemented in hardware. The traffic storm control circuitry monitors packets passing from a LAN interface to the switching bus. Using the Individual/Group bit in the packet destination address, the traffic storm control circuitry determines if the packet is unicast or broadcast, keeps track of the current count of packets within the 1-second interval, and when a threshold is reached, filters out subsequent packets. Because hardware traffic storm control uses a bandwidth-based method to measure traffic, the most significant implementation factor is setting the percentage of total available bandwidth that can be used by controlled traffic. Because packets do not arrive at uniform intervals, the 1-second interval during which controlled traffic activity is measured can affect the behavior of traffic storm control. The following are examples of traffic storm control behavior:
If you enable broadcast traffic storm control, and broadcast traffic exceeds the level within a 1-second traffic storm control interval, traffic storm control drops all broadcast traffic until the end of the traffic storm control interval. If you enable broadcast and multicast traffic storm control, and the combined broadcast and multicast traffic exceeds the level within a 1-second traffic storm control interval, traffic storm control drops all broadcast and multicast traffic until the end of the traffic storm control interval. If you enable broadcast and multicast traffic storm control, and broadcast traffic exceeds the level within a 1-second traffic storm control interval, traffic storm control drops all broadcast and multicast traffic until the end of the traffic storm control interval. If you enable broadcast and multicast traffic storm control, and multicast traffic exceeds the level within a 1-second traffic storm control interval, traffic storm control drops all broadcast and multicast traffic until the end of the traffic storm control interval.
39-2
OL-3999-08
Chapter 39
Configuring Traffic Storm Control Default Traffic Storm Control Configuration
Default Traffic Storm Control Configuration

Traffic storm control is disabled by default.
Traffic Storm Control Guidelines and Restrictions

When configuring traffic storm control, follow these guidelines and restrictions:

FlexWAN Fast Ethernet port adapters and all WAN modules supporting Ethernet SPAs do not support traffic storm control. The following LAN switching modules do not support traffic storm control:
WS-X6148A-GE-45AF WS-X6148A-GE-TX WS-X6148-GE-45AF WS-X6148-GE-TX WS-X6148V-GE-TX WS-X6548-GE-45AF WS-X6548-GE-TX WS-X6548V-GE-TX
The switch supports multicast and unicast traffic storm control on Gigabit and 10 Gigabit Ethernet LAN ports. Most FastEthernet switching modules do not support multicast and unicast traffic storm control, with the exception of WS-X6148A-RJ-45 and the WS-X6148-SFP. The switch supports broadcast traffic storm control on all LAN ports except on those modules previously noted. Except for BPDUs, traffic storm control does not differentiate between control traffic and data traffic. When multicast suppression is enabled, traffic storm control suppresses BPDUs when the multicast suppression threshold is exceeded on these modules:
WS-X6748-SFP WS-X6724-SFP WS-X6748-GE-TX WS-X6748-GE-TX WS-X6704-10GE WS-SUP32-GE-3B WS-SUP32-10GE-3B
When multicast suppression is enabled on the listed modules, do not configure traffic storm control on STP-protected ports that need to receive BPDUs. Except on the listed modules, traffic storm control does not suppress BPDUs.
39-3
Chapter 39 Enabling Traffic Storm Control
Enabling Traffic Storm Control

To enable traffic storm control, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type {port-channel number}}
1
Purpose
slot/port} |
Selects an interface to configure. Enables broadcast traffic storm control on the interface, configures the traffic storm control level, and applies the traffic storm control level to all traffic storm control modes enabled on the interface. Disables broadcast traffic storm control on the interface. Enables multicast traffic storm control on the interface, configures the traffic storm control level, and applies the traffic storm control level to all traffic storm control modes enabled on the interface. Disables multicast traffic storm control on the interface. Enables unicast traffic storm control on the interface, configures the traffic storm control level, and applies the traffic storm control level to all traffic storm control modes enabled on the interface. Disables unicast traffic storm control on the interface. Exits configuration mode. Verifies the configuration.
Router(config-if)# storm-control broadcast level level[.level]
Router(config-if)# no storm-control broadcast level
Step 3
Router(config-if)# storm-control multicast level level[.level]
Note
The storm-control multicast command is supported only on Gigabit Ethernet interfaces.
Router(config-if)# no storm-control multicast level
Step 4
Router(config-if)# storm-control unicast level level[.level]
Note
The storm-control unicast command is supported only on Gigabit Ethernet interfaces.
Router(config-if)# no storm-control unicast level
Step 5 Step 6
Router(config-if)# end Router# show running-config interface 1.
When configuring the traffic storm control level, note the following information:

You can configure traffic storm control on an EtherChannel (a port channel interface). Do not configure traffic storm control on ports that are members of an EtherChannel. Configuring traffic storm control on ports that are configured as members of an EtherChannel puts the ports into a suspended state. Specify the level as a percentage of the total interface bandwidth:
The level can be from 0 to 100. The optional fraction of a level can be from 0 to 99. 100 percent means no traffic storm control. 0.0 percent suppresses all traffic.
On these modules, these levels suppress all traffic:

WS-X6704-10GE: 0.33 percent or less WS-X6724-SFP 10Mbps ports: 0.33 percent or less WS-X6748-SFP 100Mbps ports: 0.03 percent or less
39-4
OL-3999-08
Chapter 39
Configuring Traffic Storm Control Displaying Traffic Storm Control Settings
WS-X6748-GE-TX 100Mbps ports: 0.03 percent or less WS-X6716-10G-3C / 3CXL Oversubscription Mode: 0.29 percent or less
Because of hardware limitations and the method by which packets of different sizes are counted, the level percentage is an approximation. Depending on the sizes of the frames making up the incoming traffic, the actual enforced level might differ from the configured level by several percentage points. This example shows how to enable multicast traffic storm control on Gigabit Ethernet interface 3/16 and how to configure the traffic storm control level at 70.5 percent:
Router# configure terminal Router(config)# interface gigabitethernet 3/16 Router(config-if)# storm-control multicast level 70.5 Router(config-if)# end
This example shows how the traffic storm control level configured for one mode affects all other modes that are already configured on the Gigabit Ethernet interface 4/10:
Router# show run inter gig4/10 Building configuration... Current ! Router# Router# Router# Router# Router# Router# Router# configuration : 176 bytes interface GigabitEthernet4/10 switchport switchport mode access storm-control broadcast level 70.00 storm-control multicast level 70.00 spanning-tree portfast edge end
Router# configure terminal Router(config)# interface gigabitethernet 4/10 Router(config-if)# storm-control unicast level 20 Router(config-if)# end Router# show interfaces gig4/10 counters storm-control Port Gi4/10 Router# UcastSupp % 20.00 McastSupp % 20.00 BcastSupp % 20.00 TotalSuppDiscards 0
Displaying Traffic Storm Control Settings

To display traffic storm control information, use the commands described in Table 39-1.
Table 39-1 Commands for Displaying Traffic Storm Control Status and Configuration
Command
Router# show interfaces [{type slot/port} | {port-channel number}] switchport Router# show interfaces [{type1 slot/port} | {port-channel number}] counters storm-control Router# show interfaces counters storm-control [module slot_number] 1.
1
Purpose Displays the administrative and operational status of all Layer 2 LAN ports or the specified Layer 2 LAN port. Displays the total number of packets discarded for all three traffic storm control modes, on all interfaces or on the specified interface.
39-5
Chapter 39 Displaying Traffic Storm Control Settings
Note
The show interfaces [{interface_type slot/port} | {port-channel number }] counters command does not display the discard count. You must use the storm-control keyword to display the discard count.
Tip
39-6
OL-3999-08
C H A P T E R
40
Unknown Unicast and Multicast Flood Blocking

This chapter describes how to configure the unknown unicast flood blocking (UUFB) and unknown multicast flood blocking (UMFB) features on the Catalyst 6500 series switches.
Note
Tip
Understanding UUFB or UMFB

By default, unknown unicast and multicast traffic is flooded to all Layer 2 ports in a VLAN. You can prevent this behavior by using the UUFB and UMFB features to prevent or limit this traffic. The UUFB and UMFB features block unknown unicast and multicast traffic flooding at a specific port, only permitting egress traffic with MAC addresses that are known to exist on the port. The UUFB and UMFB features are supported on all ports that are configured with the switchport command, including private VLAN (PVLAN) ports.
Note
Entering the switchport block multicast command on nonreceiver (router) ports of the VLAN could disrupt routing protocols. This command could also disrupt ARP functionality and other protocols, such as Network Time Protocol (NTP), that make use of local subnetwork multicast control groups in the 224.0.0.0/24 range.
40-1
Chapter 40 Configuring UUFB
Unknown Unicast and Multicast Flood Blocking
Configuring UUFB
To configure UUFB or UFMB, perform this task: Command
Router# configure terminal Router(config)# interface {{type1 slot/port} | {port-channel number}} Router(config-if)# switchport Router(config-if)# switchport block {unicast | multicast} Router(config-if)# do show interfaces [type1 slot/port] switchport | include Unknown 1. type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet
Purpose Enters global configuration mode. Selects the interface to configure. Configures the port for Layer 2 switching. Enables unknown unicast or multicast flood blocking on the port. Verifies the configuration.
This example shows how to configure UUFB on Fast Ethernet port 5/12 and how to verify the configuration:
Router# configure terminal Router(config)# interface fastethernet 5/12 Router(config-if)# switchport Router(config-if)# switchport block unicast Router(config-if)# do show interface fastethernet 5/12 switchport | include Unknown Unknown unicast blocked: enabled
Tip
40-2
OL-3999-08
C H A P T E R
41
Configuring PFC QoS

This chapter describes how to configure quality of service (QoS) as implemented on the Policy Feature Card (PFC) and Distributed Forwarding Cards (DFCs) on the Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html For information about QoS and MPLS, see Chapter 42, Configuring PFC3BXL or PFC3B Mode MPLS QoS. QoS on the Catalyst 6500 series switches (PFC QoS) uses some Cisco IOS modular QoS CLI (MQC). Because PFC QoS is implemented in hardware, it supports only a subset of the MQC syntax. The PFC3 does not support Network-Based Application Recognition (NBAR). With a Supervisor Engine 2, PFC2, and MSFC2, you can configure NBAR on Layer 3 interfaces instead of PFC QoS:
The PFC2 provides hardware support for input ACLs on ports where you configure NBAR. When PFC QoS is enabled, the traffic through ports where you configure NBAR passes through
the ingress and egress queues and drop thresholds.

When PFC QoS is enabled, the MSFC2 sets egress CoS equal to egress IP precedence in NBAR
traffic.
After passing through an ingress queue, all traffic is processed in software on the MSFC2 on
interfaces where you configure NBAR.

To configure NBAR, refer to this publication:
http://www.cisco.com/en/US/docs/ios/12_4t/qos/configuration/guide/qsnbar1.html

Understanding How PFC QoS Works, page 41-2 PFC QoS Default Configuration, page 41-30 PFC QoS Configuration Guidelines and Restrictions, page 41-50 Configuring PFC QoS, page 41-56 Common QoS Scenarios, page 41-113 PFC QoS Glossary, page 41-123
41-1
Chapter 41 Understanding How PFC QoS Works
Configuring PFC QoS
Tip
Understanding How PFC QoS Works

The term PFC QoS refers to QoS on the Catalyst 6500 series switch. PFC QoS is implemented on various switch components in addition to the PFC and any DFCs. These sections describe how PFC QoS works:

Port Types Supported by PFC QoS, page 41-2 Overview, page 41-2 Component Overview, page 41-6 Understanding Classification and Marking, page 41-17 Understanding Port-Based Queue Types, page 41-23
Port Types Supported by PFC QoS

The PFC does not provide QoS for FlexWAN module ports. Refer to this publication for information about FlexWAN module QoS features: http://www.cisco.com/en/US/docs/routers/7600/install_config/flexwan_config/flexwan-config-guide.ht ml In all releases, PFC QoS supports LAN ports. LAN ports are Ethernet ports on Ethernet switching modules, except for the 4-port Gigabit Ethernet WAN (GBIC) modules (OSM-4GE-WAN and OSM-2+4GE-WAN+). Some OSMs have four Ethernet LAN ports in addition to WAN ports. With Release 12.2(17b)SXA and later releases, PFC QoS supports optical services module (OSM) ports. OSM ports are the WAN ports on OSMs. Refer to the following publication for information about additional OSM QoS features: http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/OSMConfiguratio nNote12.2SX.html
Overview
Typically, networks operate on a best-effort delivery basis, which means that all traffic has equal priority and an equal chance of being delivered in a timely manner. When congestion occurs, all traffic has an equal chance of being dropped. QoS makes network performance more predictable and bandwidth utilization more effective. QoS selects (classifies) network traffic, uses or assigns QoS labels to indicate priority, makes the packets comply with the configured resource usage limits (polices the traffic and marks the traffic), and provides congestion avoidance where resource contention exists.
41-2
OL-3999-08
Chapter 41
Configuring PFC QoS Understanding How PFC QoS Works
PFC QoS classification, policing, marking, and congestion avoidance is implemented in hardware on the PFC, DFCs, and in LAN switching module port Application Specific Integrated Circuits (ASICs).
Note
Catalyst 6500 series switches do not support all of the MQC features (for example, Committed Access Rate (CAR)) for traffic that is Layer 3 switched or Layer 2 switched in hardware. Because queuing is implemented in the port ASICs, Catalyst 6500 series switches do not support MQC-configured queuing. Figure 41-1 shows an overview of QoS processing in a Catalyst 6500 series switch.
Figure 41-1 PFC QoS Feature Processing Overview
MSFC
2 PFC
Switching Module
Switching Module
The PFC QoS features are applied in this order:

1.
Ingress port PFC QoS features:

Port trust stateIn PFC QoS, trust means to accept as valid and use as the basis of the initial
internal DSCP value. Ports are untrusted by default, which sets the initial internal DSCP value to zero. You can configure ports to trust received CoS, IP precedence, or DSCP.
Layer 2 CoS remarkingPFC QoS applies Layer 2 CoS remarking, which marks the incoming
frame with the port CoS value, in these situations: If the traffic is not in an ISL, 802.1Q, or 802.1p frame. If a port is configured as untrusted. On OSM ATM and POS ports, PFC QoS always sets ingress CoS equal to zero.
Congestion avoidanceIf you configure an Ethernet LAN port to trust CoS or DSCP, QoS
classifies the traffic on the basis of its Layer 2 CoS value or its Layer 3 DSCP value and assigns it to an ingress queue to provide congestion avoidance. Layer 3 DSCP-based queue mapping is available only on WS-X6708-10GE ports.
2.
PFC and DFC QoS features:

Internal DSCPOn the PFC and DFCs, QoS associates an internal DSCP value with all traffic
to classify it for processing through the system. There is an initial internal DSCP based on the traffic trust state and a final internal DSCP. The final internal DSCP can be the same as the initial value or an MQC policy map can set it to a different value.
MQC policy mapsMQC policy maps can do one or more of these operations:
Change the trust state of the traffic (bases the internal DSCP value on a different QoS label)
120559
41-3
Configuring PFC QoS
Set the initial internal DSCP value (only for traffic from untrusted ports) Mark the traffic Police the traffic
3.
Egress Ethernet LAN port QoS features:

Layer 3 DSCP marking with the final internal DSCP (always with PFC2, optionally with PFC3) Layer 2 CoS marking mapped from the final internal DSCP Layer 2 CoS-based and Layer 3 DSCP-based congestion avoidance. (Layer 3 DSCP-based
queue mapping is available only on WS-X6708-10GE ports.) These figures provide more detail about the relationship between QoS and the switch components:

Figure 41-2, Traffic Flow and PFC QoS Features with PFC3 Figure 41-3, Traffic Flow and PFC QoS Features with PFC2 Figure 41-4, PFC QoS Features and Component Overview
Figure 41-2 shows traffic flow and PFC QoS features with a PFC3.
Figure 41-2 Traffic Flow and PFC QoS Features with PFC3
FlexWAN traffic enters switch FlexWAN ingress port and QoS features Multilayer Switch Feature Card (MSFC) FlexWAN egress port and QoS features Transmit FlexWAN traffic
CoS = IP precedence for all traffic (not configurable)
LAN traffic enters switch
LAN ingress port and QoS features
Ingress PFC3 QoS
PFC3 Layer 2 or 3 switching
Egress PFC3 QoS
LAN egress port and QoS features
Transmit LAN traffic
CoS = 0 for all ATM and POS traffic (not configurable)
Figure 41-2 shows how traffic flows through the PFC QoS features with PFC3:

Traffic can enter on any type of port and exit on any type of port. DFCs implement PFC QoS locally on switching modules. For FlexWAN module traffic:
Ingress FlexWAN QoS features can be applied to FlexWAN ingress traffic. Ingress FlexWAN traffic can be Layer 3-switched by the PFC3 or routed in software by the MSFC. Egress PFC QoS is not applied to FlexWAN ingress traffic. Egress FlexWAN QoS can be applied to FlexWAN egress traffic.
For LAN-port traffic:

Ingress LAN-port QoS features can be applied to LAN-port ingress traffic. Ingress PFC QoS can be applied to LAN-port ingress traffic.
41-4
OL-3999-08
105757
OSM traffic enters switch
OSM ingress port and QoS freatures
OSM egress port and QoS freatures
Transmit OSM traffic
Chapter 41
Ingress LAN-port traffic can be Layer-2 or Layer-3 switched by the PFC3 or routed in software
by the MSFC.
Egress PFC QoS and egress LAN-port QoS can be applied to LAN-port egress traffic.
For OSM traffic:

Ingress OSM-port QoS features can be applied to OSM-port ingress traffic. Ingress PFC3 QoS can be applied to OSM-port ingress traffic. Ingress OSM-port traffic can be Layer-3 switched by the PFC3 or routed in software by the MSFC. Egress PFC3 QoS and egress OSM-port QoS can be applied to OSM-port egress traffic.
Figure 41-3 shows traffic flow and PFC QoS features with a PFC2.
Figure 41-3 Traffic Flow and PFC QoS Features with PFC2
FlexWAN traffic enters switch FlexWAN ingress port and QoS features Multilayer Switch Feature Card 2 (MSFC2) FlexWAN egress port and QoS features Transmit FlexWAN traffic
CoS = IP precedence for all traffic (not configurable)
LAN traffic enters switch
LAN ingress port and QoS features
Ingress PFC2 QoS
PFC2 Layer 2 or 3 switching
LAN egress port and QoS features
Transmit LAN traffic
CoS = 0 for all ATM and POS traffic (not configurable)
Figure 41-3 shows how traffic flows through the PFC QoS features with PFC2:

Traffic can enter on any type of port and exit on any type of port. DFCs implement PFC QoS locally on switching modules. For FlexWAN module traffic:
Ingress FlexWAN QoS features can be applied to FlexWAN ingress traffic. Ingress FlexWAN traffic can be Layer 3-switched by the PFC2 or routed in software by the
MSFC2.
Egress FlexWAN QoS can be applied to FlexWAN egress traffic.
For LAN-port traffic:

Ingress LAN-port QoS features can be applied to LAN-port ingress traffic. Ingress LAN-port traffic can be Layer-2 or Layer-3 switched by the PFC2 or routed in software
by the MSFC2.
Egress LAN-port QoS can be applied to LAN-port egress traffic.
For OSM traffic:

OSM-port QoS features can be applied to OSM-port ingress traffic. Ingress PFC2 QoS can be applied to OSM-port ingress traffic.
41-5
120185
OSM traffic enters switch
OSM ingress port and QoS freatures
OSM egress port and QoS freatures
Configuring PFC QoS
OSM-port ingress traffic can be Layer-3 switched by the PFC2 or routed in software by the
MSFC2.
Egress OSM-port QoS can be applied to OSM-port egress traffic. Figure 41-4 PFC QoS Features and Component Overview
Identify traffic based on match criteria: - ACL (L2, IP) - DSCP - IP Prec - MPLS Exp - Class-map PFC/DFC C l a s s i f i c a t i o n
Port Trust - CoS - IP Prec - DSCP - MPLS Exp Ingress Port
DSCP map
Final internal DSCP is mapped to CoS
Scheduler operates on WRR, DWRR, SP
Egress Port
Q1 Q2 Policy Result DSCP CoS rewrite CoS determies queue selection Q3 Q4
SP Outgoing WRR DWRR
Incoming ToS CoS
Q1 Q2
Scheduler
CoS set on trunk port DSCP set for IP
Action - policy map Scheduling rules: WRR, PQ Queueing based on CoS Trust - DSCP, IP Prec MPLS Exp Mark - set internal DSCP Police - rate limit; mark; drop
Scheduler queue and threshold are configurable
Component Overview
These sections provide more detail about the role of the following components in PFC QoS decisions and processes:

Ingress LAN Port PFC QoS Features, page 41-7 PFC and DFC QoS Features, page 41-9 PFC QoS Egress Port Features, page 41-13
41-6
OL-3999-08
137031
Chapter 41
Ingress LAN Port PFC QoS Features

These sections provide an overview of the ingress port QoS features:

Flowchart of Ingress LAN Port PFC QoS Features, page 41-8 Port Trust, page 41-9 Ingress Congestion Avoidance, page 41-9
41-7
Configuring PFC QoS
Flowchart of Ingress LAN Port PFC QoS Features

Figure 41-5 shows how traffic flows through the ingress LAN port PFC QoS features.
Figure 41-5 Ingress LAN Port PFC QoS Features
Frame enters switch
ISL or 802.1Q? Yes
No
Apply port CoS
IP traffic with No recognizable ToS byte?
Yes Ignore port trust enabled?
Apply port CoS
Port set to Yes untrusted?
No
No
Port set to trust-ipprec?
Yes
No
No
IP traffic with Yes DSCP-based Yes recognizable queue mapping ToS byte? enabled?
Port set to Yes trust-dscp?
DSCP-to-queue map
No No No CoS-to-queue map Ingress queues and drop thresholds
Port is set to trust-cos
Ingress Yes CoS Mutation?
Mutate CoS
154684
To PFC
Note
Ingress CoS mutation is supported only on 802.1Q tunnel ports. Release 12.2(18)SXF5 and later releases support the ignore port trust feature. DSCP-based queue mapping is supported only on WS-X6708-10GE ports.
41-8
OL-3999-08
Chapter 41
Port Trust
In PFC QoS, trust means to accept as valid and use as the basis of the initial internal DSCP value. You can configure ports as untrusted or you can configure them to trust these QoS values:
Layer 2 CoS
A port configured to trust CoS is called a trust CoS port. Traffic received through a trust CoS port or configured by a policy map to trust CoS is called
trust CoS traffic.
Note
Not all traffic carries a CoS value. Only ISL, 802.1Q, and 802.1P traffic carries a CoS value. PFC QoS applies the port CoS value to any traffic that does not carry a CoS value. On untrusted ports, PFC QoS applies the port CoS value to all traffic, overwriting any received CoS value.
IP precedence
A port configured to trust IP precedence is called a trust IP precedence port. Traffic received through a trust IP precedence port or configured by a policy map to trust
IP precedence is called trust IP precedence traffic.
DSCP
A port configured to trust DSCP is called a trust DSCP port. Traffic received through a trust DSCP port or configured by a policy map to trust DSCP is called
trust DSCP traffic. Traffic received through an untrusted port is called untrusted traffic.
Ingress Congestion Avoidance

PFC QoS implements congestion avoidance on trust CoS ports. On a trust CoS port, QoS classifies the traffic on the basis of its Layer 2 CoS value and assigns it to an ingress queue to provide congestion avoidance. In Release 12.2(18)SXF5 and later releases, you can configure WS-X6708-10GE trust DSCP ports to use received DSCP values for congestion avoidance. See the Ingress Classification and Marking at Trust CoS LAN Ports section on page 41-18 for more information about ingress congestion avoidance.
PFC and DFC QoS Features

These sections describe PFCs and DFCs as they relate to QoS:

Supported Policy Feature Cards, page 41-10 Supported Distributed Forwarding Cards, page 41-10 PFC and DFC QoS Feature List and Flowchart, page 41-10 Internal DSCP Values, page 41-12
41-9
Configuring PFC QoS
Supported Policy Feature Cards

The policy feature card (PFC) is a daughter card that resides on the supervisor engine. The PFC provides QoS in addition to other functionality. The following PFCs are supported on the Catalyst 6500 series switches:

PFC2 on the Supervisor Engine 2 PFC3A on the Supervisor Engine 720 PFC3B on the Supervisor Engine 720 and Supervisor Engine 32 PFC3BXL on the Supervisor Engine 720
Supported Distributed Forwarding Cards

The PFC sends a copy of the QoS policies to the distributed forwarding card (DFC) to provide local support for the QoS policies, which enables the DFCs to support the same QoS features that the PFC supports. The following DFCs are supported on the Catalyst 6500 series switches:

WS-F6K-DFC, for use on dCEF256 and CEF256 modules with a Supervisor Engine 2. WS-F6K-DFC3A, WS-F6K-DFC3B, WS-F6K-DFC3BXL, for use on dCEF256 and CEF256 modules with a Supervisor Engine 720. WS-F6700-DFC3A, WS-F6700-DFC3B, WS-F6700-DFC3BXL, for use on CEF720 modules with a Supervisor Engine 720.
PFC and DFC QoS Feature List and Flowchart

Table 41-1 lists the QoS features supported on the different versions of PFCs and DFCs.
Table 41-1 QoS Features Supported on PFCs and DFCs
Feature Support for DFCs Flow granularity QoS ACLs DSCP transparency
Note
PFC2/DFC Yes Full flow IP, IPX, MAC No
PFC3A/DFC3A Yes Source Destination IP, MAC Optional
PFC3B/DFC3B Yes Source Destination IP, MAC Optional
PFC3BXL/DFC3BXL Yes Source Destination IP, MAC Optional
Enabling DSCP transparency disables egress ToS rewrite. Mandatory Yes No 1022 64 rates 32,000 Packets Optional Yes Yes 1022 64 rates 64,000 Bytes Optional Yes Yes 1022 64 rates 110,000 Bytes Optional Yes Yes 1022 64 rates 240,000 Bytes
Egress ToS rewrite Policing: Ingress aggregate policers Egress aggregate policers Number of aggregate policers Microflow policers Number of flows per Microflow policer Unit of measure for policer statistics Basis of policer operation
Layer 3 length Layer 2 length Layer 2 length Layer 2 length
41-10
OL-3999-08
Chapter 41
Figure 41-6 shows how traffic flows through the QoS features on the PFC and DFCs.
Figure 41-6 QoS Features on the PFC and DFCs
Ingress PFC QoS
For trust CoS traffic: Policy map Map CoS (Received or Port) Initial Internal DSCP Policer Marker (Optional)
For trust DSCP traffic: Policy map Received DSCP Initial Internal DSCP Policer Marker (Optional) Traffic Forwarding MSFC routing or PFC Layer 3 switching or PFC Layer 2 switching Policy map Policer Marker (Optional; only with PFC 3)
Egress PFC QoS

Egress DSCP Mutation
For trust IP precedence traffic: Policy map Received IP Precedence Map Initial Internal DSCP Policer Marker (Optional) For untrusted traffic or for any traffic if ignore port trust is configured When ignore port trust is not configured Policy map Initial Internal DSCP=0 Policer Marker When ignore port trust is configured, received DSCP (if any) is initial internal (Optional) DSCP, otherwise port CoS is mapped to initial internal DSCP
Final Egress Map Internal DSCP DSCP (only on PFC3) Map Egress CoS (LAN ports only)
Note
The DSCP transparency feature makes writing the egress DSCP value into the Layer 3 ToS byte optional.
41-11
154644
Configuring PFC QoS
Internal DSCP Values

During processing, PFC QoS represents the priority of all traffic (including non-IP traffic) with an internal DSCP value.
Initial Internal DSCP Value
On the PFC, before any marking or policing takes place, PFC QoS derives the initial internal DSCP value as follows:

For untrusted traffic, when ignore port trust is not enabled, PFC QoS sets the initial internal DSCP value to zero for both tagged and untagged untrusted traffic. For untrusted traffic, when ignore port trust is enabled, PFC QoS does the following:
For IP traffic, PFC QoS uses the received DSCP value as the initial internal DSCP value. For traffic without a recognizable ToS byte, PFC QoS maps the port CoS value to the initial
internal DSCP value.
For trust CoS traffic, when ignore port trust is enabled, PFC QoS does the following:
For IP traffic, PFC QoS uses the received DSCP value as the initial internal DSCP value.
Note
For trust CoS traffic, when ignore port trust is enabled, PFC QoS does not use the received CoS value in tagged IP traffic. When ignore port trust is disabled, PFC QoS uses the received CoS value in tagged IP traffic.
For tagged traffic without a recognizable ToS byte, PFC QoS maps the received CoS value to
the initial internal DSCP value.

For untagged traffic without a recognizable ToS byte, PFC QoS maps the port CoS value to the
initial internal DSCP value.
For trust IP precedence traffic, PFC QoS does the following:

For IP traffic, PFC QoS maps the received IP precedence value to the initial internal DSCP
value.
For tagged traffic without a recognizable ToS byte, PFC QoS maps the received CoS value to

initial internal DSCP value.
For trust DSCP traffic, PFC QoS, PFC QoS does the following:
For IP traffic, PFC QoS uses the received DSCP value as the initial internal DSCP value. For tagged traffic without a recognizable ToS byte, PFC QoS maps the received CoS value to

initial internal DSCP value. For trust CoS traffic and trust IP precedence traffic, PFC QoS uses configurable maps to derive the initial internal 6-bit DSCP value from CoS or IP precedence, which are 3-bit values.
Final Internal DSCP Value
Policy marking and policing on the PFC can change the initial internal DSCP value to a final internal DSCP value, which is then used for all subsequently applied QoS features.
41-12
OL-3999-08
Chapter 41
Port-Based PFC QoS and VLAN-Based PFC QoS

You can configure each ingress LAN port for either physical port-based PFC QoS (default) or VLAN-based PFC QoS and attach a policy map to the selected interface. On ports configured for port-based PFC QoS, you can attach a policy map to the ingress LAN port as follows:

On a nontrunk ingress LAN port configured for port-based PFC QoS, all traffic received through the port is subject to the policy map attached to the port. On a trunking ingress LAN port configured for port-based PFC QoS, traffic in all VLANs received through the port is subject to the policy map attached to the port.
On a nontrunk ingress LAN port configured for VLAN-based PFC QoS, traffic received through the port is subject to the policy map attached to the ports VLAN. On a trunking ingress LAN port configured for VLAN-based PFC QoS, traffic received through the port is subject to the policy map attached to the traffics VLAN.
PFC QoS Egress Port Features

These sections describe PFC QoS egress port features:

Flowchart of PFC QoS Egress LAN Port Features, page 41-14 Egress CoS Values, page 41-14 Egress DSCP Mutation with a PFC3, page 41-15 Egress ToS Byte, page 41-15 Egress PFC QoS Interfaces, page 41-15 Egress ACL Support for Remarked DSCP, page 41-15 Marking on Egress OSM Ports, page 41-16
41-13
Configuring PFC QoS
Flowchart of PFC QoS Egress LAN Port Features

Figure 41-7 shows how traffic flows through the QoS features on egress LAN ports.
Figure 41-7 Egress LAN Port Scheduling, Congestion Avoidance, and Marking
From PFC or MSFC
PFC3 only Egress queues and drop thresholds IP traffic Yes from PFC? No DSCP rewrite enabled? No Yes Write ToS byte into packet
ISL or 802.1Q? No
Yes
Write CoS into frame
Transmit frame
Egress CoS Values

For all egress traffic, PFC QoS uses a configurable map to derive a CoS value from the final internal DSCP value associated with the traffic. PFC QoS sends the derived CoS value to the egress LAN ports for use in classification and congestion avoidance and to be written into ISL and 802.1Q frames.
Note
With Release 12.2(18)SXF5 and later releases, you can configure WS-X6708-10GE ports to use the final internal DSCP value for egress LAN port classification and congestion avoidance (see the Configuring DSCP-Based Queue Mapping section on page 41-100).
41-14
OL-3999-08
144806
Chapter 41
Egress DSCP Mutation with a PFC3

With a PFC3, you can configure 15 egress DSCP mutation maps to mutate the internal DSCP value before it is written in the egress ToS byte. You can attach egress DSCP mutation maps to any interface that PFC QoS supports.
Note
If you configure egress DSCP mutation, PFC QoS does not derive the egress CoS value from the mutated DSCP value. The PFC2 does not support egress DSCP mutation.
Egress ToS Byte

Except when DSCP transparency is enabled, PFC QoS creates a ToS byte for egress IP traffic from the final internal or mutated DSCP value and sends it to the egress port to be written into IP packets. For trust DSCP and untrusted IP traffic, the ToS byte includes the original two least-significant bits from the received ToS byte. The internal or mutated DSCP value can mimic an IP precedence value (see the IP Precedence and DSCP Values section on page 41-56).
Egress PFC QoS Interfaces

You can attach an output policy map to a Layer 3 interface (either a LAN port configured as a Layer 3 interface or a VLAN interface) to apply a policy map to egress traffic.
Note
Output policies do not support microflow policing. With a PFC3, you cannot apply microflow policing to ARP traffic. You cannot set a trust state in an output policy.
Egress ACL Support for Remarked DSCP
Note
Egress ACL support for remarked DSCP is also known as packet recirculation. With a PFC3, Release 12.2(18)SXE and later releases support egress ACL support for remarked DSCP, which enables IP precedence-based or DSCP-based egress QoS filtering to use any IP precedence or DSCP policing or marking changes made by ingress PFC QoS. Without egress ACL support for remarked DSCP, egress QoS filtering uses received IP precedence or DSCP values; it does not use any IP precedence or DSCP changes made by ingress PFC QoS as the result of policing or marking. The PFC3 provides egress PFC QoS only for Layer 3-switched and routed traffic on egress Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces). You configure egress ACL support for remarked DSCP on ingress Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces).
41-15
Configuring PFC QoS
On interfaces where egress ACL support for remarked DSCP is configured, the PFC3 processes each QoS-filtered IP packet twice: once to apply ingress PFC QoS and once to apply egress PFC QoS.
Caution
If the switch is operating in PFC3A mode with egress ACL support for remarked DSCP configured, when the PFC3 processes traffic to apply ingress PFC QoS, it applies ingress PFC QoS filtering and ingress PFC QoS, and incorrectly applies any egress QoS filtering and egress PFC QoS configured on the ingress interface, which results in unexpected behavior if QoS filtering is configured on an interface where egress ACL support for remarked DSCP is enabled. This problem does not occur in other PFC3 modes. After packets have been processed by ingress PFC QoS and any policing or marking changes have been made, the packets are processed again on the ingress interface by any configured Layer 2 features (for example, VACLs) before being processed by egress PFC QoS. On an interface where egress ACL support for remarked DSCP is configured, if a Layer 2 feature matches the ingress-QoS-modified IP precedence or DSCP value, the Layer 2 feature might redirect or drop the matched packets, which prevents them from being processed by egress QoS. After packets have been processed by ingress PFC QoS and any policing or marking changes have been made, the packets are processed on the ingress interface by any configured Layer 3 features (for example, ingress Cisco IOS ACLs, policy based routing (PBR), etc.) before being processed by egress PFC QoS. The Layer 3 features configured on an interface where egress ACL support for remarked DSCP is configured might redirect or drop the packets that have been processed by ingress PFC QoS, which would prevent them from being processed by egress PFC QoS.
Marking on Egress OSM Ports

Ingress PFC QoS sets DSCP values that can be used by the OSM egress QoS features (see Figure 41-8).
Figure 41-8 Egress OSM Port Marking
From PFC or MSFC OSM switching module marking PFC3 only IP traffic Yes from PFC? No DSCP rewrite enabled? No
113090
Yes
Write ToS byte into packet
OSM QoS Features
41-16
OL-3999-08
Chapter 41
Understanding Classification and Marking

The following sections describe where and how classification and marking occur on the Catalyst 6500 series switches:

Classification and Marking at Trusted and Untrusted Ingress Ports, page 41-17 Classification and Marking at Ingress OSM Ports, page 41-18 Classification and Marking on the PFC Using Service Policies and Policy Maps, page 41-19 Classification and Marking on the MSFC, page 41-20
Classification and Marking at Trusted and Untrusted Ingress Ports

The trust state of an ingress port determines how the port marks, schedules, and classifies received Layer 2 frames, and whether or not congestion avoidance is implemented. These are the port trust states:

Untrusted (default) Trust IP precedence Trust DSCP Trust CoS
In all releases, ingress LAN port classification, marking, and congestion avoidance can use Layer 2 CoS values and do not set Layer 3 IP precedence or DSCP values. In Release 12.2(18)SXF5 and later releases, you can configure WS-X6708-10GE ports to use received DSCP values for ingress LAN port classification and congestion avoidance (see the Configuring DSCP-Based Queue Mapping section on page 41-100) In Releases earlier than Release 12.2(18)SXF5, ingress LAN port classification, marking, and congestion avoidance use Layer 2 CoS values only. The following sections describe classification and marking at trusted and untrusted ingress ports:

Classification and Marking at Untrusted Ingress Ports, page 41-17 Ingress Classification and Marking at Trusted Ports, page 41-17
Classification and Marking at Untrusted Ingress Ports

PFC QoS Layer 2 remarking marks all frames received through untrusted ports with the port CoS value (the default is zero). To map the port CoS value that was applied to untrusted ingress traffic to the initial internal DSCP value, configure a trust CoS policy map that matches the ingress traffic.
Ingress Classification and Marking at Trusted Ports

You should configure ports to trust only if they receive traffic that carries valid QoS labels. QoS uses the received QoS labels as the basis of initial internal DSCP value. After the traffic enters the switch, you can apply a different trust state to traffic with a policy map. For example, traffic can enter the switch through a trust CoS port, and then you can use a policy map to trust IP precedence or DSCP, which uses the trusted value as the basis of the initial internal DSCP value, instead of the QoS label that was trusted at the port.
41-17
Configuring PFC QoS
These sections describe classification and marking at trusted ingress ports:

Ingress Classification and Marking at Trust CoS LAN Ports, page 41-18 Ingress Classification and Marking at Trust IP Precedence Ports, page 41-18 Ingress Classification and Marking at Trust DSCP Ports, page 41-18
Ingress Classification and Marking at Trust CoS LAN Ports
You should configure LAN ports to trust CoS only if they receive traffic that carries valid Layer 2 CoS. When an ISL frame enters the switch through a trusted ingress LAN port, PFC QoS accepts the three least significant bits in the User field as a CoS value. When an 802.1Q frame enters the switch through a trusted ingress LAN port, PFC QoS accepts the User Priority bits as a CoS value. PFC QoS Layer 2 remarking marks all traffic received in untagged frames with the ingress port CoS value. On ports configured to trust CoS, PFC QoS does the following:

PFC QoS maps the received CoS value in tagged trust CoS traffic to the initial internal DSCP value. PFC QoS maps the ingress port CoS value applied to untagged trusted traffic to the initial internal DSCP value. PFC QoS enables the CoS-based ingress queues and thresholds to provide congestion avoidance. See the Understanding Port-Based Queue Types section on page 41-23 for more information about ingress queues and thresholds.
Ingress Classification and Marking at Trust IP Precedence Ports
You should configure ports to trust IP precedence only if they receive traffic that carries valid Layer 3 IP precedence. For traffic from trust IP precedence ports, PFC QoS maps the received IP precedence value to the initial internal DSCP value. Because the ingress port queues and thresholds use Layer 2 CoS, PFC QoS does not implement ingress port congestion avoidance on ports configured to trust IP precedence. PFC does not mark any traffic on ingress ports configured to trust IP precedence.
Ingress Classification and Marking at Trust DSCP Ports
You should configure ports to trust DSCP only if they receive traffic that carries valid Layer 3 DSCP. In Release 12.2(18)SXF5 and later releases, you can enable DSCP-based ingress queues and thresholds on WS-X6708-10GE ports to provide congestion avoidance (see the Configuring DSCP-Based Queue Mapping section on page 41-100). In releases earlier than Release 12.2(18)SXF5, the ingress port queues and thresholds use only Layer 2 CoS, and PFC QoS does not implement ingress port congestion avoidance on ports configured to trust DSCP. For traffic from trust DSCP ports, PFC QoS uses the received DSCP value as the initial internal DSCP value. PFC QoS does not mark any traffic on ingress ports configured to trust received DSCP.
Classification and Marking at Ingress OSM Ports

PFC QoS associates CoS zero with all traffic received through ingress OSM ports. You can configure ingress OSM port trust states that can be used by the PFC to set IP precedence or DSCP values and the CoS value. You can configure the trust state of each ingress OSM port as follows:

Untrusted (default) Trust IP precedence Trust DSCP
41-18
OL-3999-08
Chapter 41
Trust CoS (CoS is always zero for POS and ATM OSM ports because the port CoS value is not configurable on POS and ATM OSM ports.)
Classification and Marking on the PFC Using Service Policies and Policy Maps
PFC QoS supports classification and marking with service policies that attach one policy map to these interface types to apply ingress PFC QoS:

Each ingress port (except FlexWAN interfaces) Each EtherChannel port-channel interface Each VLAN interface
With a PFC3, you can attach one policy map to each Layer 3 interface (except FlexWAN interfaces) to apply egress PFC QoS. Each policy map can contain multiple policy-map classes. You can configure a separate policy-map class for each type of traffic handled by the interface. There are two ways to configure filtering in policy-map classes:

Access control lists (ACLs) Class-map match commands for IP precedence and DSCP values
Policy-map classes specify actions with the following optional commands:
Policy-map set commandsFor untrusted traffic or if ignore port trust is enabled, PFC QoS can use configured IP precedence or DSCP values as the final internal DSCP value. The IP Precedence and DSCP Values section on page 41-56 shows the bit values for IP precedence and DSCP. Policy-map class trust commandsPFC QoS applies the policy-map class trust state to matched ingress traffic, which then uses the trusted value as the basis of its initial internal DSCP value, instead of the QoS label that was trusted at the port (if any). In a policy map, you can trust CoS, IP precedence, or DSCP.
Note
A trust CoS policy map cannot restore received CoS in traffic from untrusted ports. Traffic from untrusted ports always has the port CoS value.
Aggregate and microflow policersPFC QoS can use policers to either mark or drop both conforming and nonconforming traffic.
41-19
Configuring PFC QoS
Classification and Marking on the MSFC

PFC QoS sends IP traffic to the MSFC with the final internal DSCP values. CoS is equal to IP precedence in all traffic sent from the MSFC to egress ports.
Figure 41-9 Marking with PFC2 or PFC3 and MSFC2, MSFC2A, or MSFC3
From PFC Multilayer Switch Feature Card (MSFC) marking
IP traffic Yes from PFC?
Write ToS byte into packet
No
Route traffic
144800
CoS = IP precedence for all traffic (not configurable) To egress port
Note
Traffic that is Layer 3 switched on the PFC does not go through the MSFC and retains the CoS value assigned by the PFC.
Policers
These sections describe policers:

Overview of Policers, page 41-20 Aggregate Policers, page 41-21 Microflow Policers, page 41-22
Overview of Policers
Policing allows you to rate limit incoming and outgoing traffic so that it adheres to the traffic forwarding rules defined by the QoS configuration. Sometimes these configured rules for how traffic should be forwarded through the system are referred to as a contract. If the traffic does not adhere to this contract, it is marked down to a lower DSCP value or dropped. Policing does not buffer out-of-profile packets. As a result, policing does not affect transmission delay. In contrast, traffic shaping works by buffering out-of-profile traffic, which moderates the traffic bursts. (PFC QoS does not support shaping.)
41-20
OL-3999-08
Chapter 41
The PFC2 supports only ingress PFC QoS, which includes ingress policing. The PFC3 supports both ingress and egress PFC QoS, which includes ingress and egress policing. Traffic shaping is supported on some WAN modules. For more information about traffic shaping on the OSM and FlexWAN modules, refer to these FlexWAN and OSM documents: http://www.cisco.com/en/US/docs/routers/7600/install_config/flexwan_config/flexqos.html#wp112415 1 http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/qos.html#Configu ring_Class-Based_Traffic_Shaping http://www.cisco.com/en/US/docs/routers/7600/install_config/12.2SX_OSM_config/qos.html#Configu ring_Hierarchical_Traffic_Shaping
Note
Policers can act on ingress traffic per-port or per-VLAN. With a PFC3, for egress traffic, the policers can act per-VLAN only. You can create policers to do the following:

Mark traffic Limit bandwidth utilization and mark traffic
Aggregate Policers
PFC QoS applies the bandwidth limits specified in an aggregate policer cumulatively to all flows in matched traffic. For example, if you configure an aggregate policer to allow 1 Mbps for all TFTP traffic flows on VLAN 1 and VLAN 3, it limits the TFTP traffic for all flows combined on VLAN 1 and VLAN 3 to 1 Mbps.
You define per-interface aggregate policers in a policy map class with the police command. If you attach a per-interface aggregate policer to multiple ingress ports, it polices the matched traffic on each ingress port separately. You create named aggregate policers with the mls qos aggregate-policer command. If you attach a named aggregate policer to multiple ingress ports, it polices the matched traffic from all the ingress ports to which it is attached. Aggregate policing works independently on each DFC-equipped switching module and independently on the PFC, which supports any non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from different DFC-equipped switching modules. You can display aggregate policing statistics for each DFC-equipped switching module and for the PFC and any non-DFC-equipped switching modules supported by the PFC. Each PFC or DFC polices independently, which might affect QoS features being applied to traffic that is distributed across the PFC and any DFCs. Examples of these QoS feature are:
Policers applied to a port channel interface. Policers applied to a switched virtual interface. Egress policers applied to either a Layer 3 interface or an SVI. Note that PFC QoS performs
egress policing decisions at the ingress interface, on the PFC or ingress DFC. Policers affected by this restriction deliver an aggregate rate that is the sum of all the independent policing rates.
41-21
Configuring PFC QoS
Microflow Policers
PFC QoS applies the bandwidth limit specified in a microflow policer separately to each flow in matched traffic. For example, if you configure a microflow policer to limit the TFTP traffic to 1 Mbps on VLAN 1 and VLAN 3, then 1 Mbps is allowed for each flow in VLAN 1 and 1 Mbps for each flow in VLAN 3. In other words, if there are three flows in VLAN 1 and four flows in VLAN 3, the microflow policer allows each of these flows 1 Mbps. You can configure PFC QoS to apply the bandwidth limits in a microflow policer as follows:

You can create microflow policers with up to 63 different rate and burst parameter combinations. You create microflow policers in a policy map class with the police flow command. You can configure a microflow policer to use only source addresses, which applies the microflow policer to all traffic from a source address regardless of the destination addresses. You can configure a microflow policer to use only destination addresses, which applies the microflow policer to all traffic to a destination address regardless of the source addresses. For MAC-Layer microflow policing, PFC QoS considers MAC-Layer traffic with the same protocol and the same source and destination MAC-Layer addresses to be part of the same flow, including traffic with different EtherTypes. With a PFC3, you can configure MAC ACLs to filter IPX traffic. With a PFC2, you can configure IPX ACLs to filter IPX traffic. For IPX microflow policing, PFC QoS considers IPX traffic with the same source network, destination network, and destination node to be part of the same flow, including traffic with different source nodes or source sockets. By default, microflow policers only affect traffic routed by the MSFC. To enable microflow policing of other traffic, including traffic in bridge groups, enter the mls qos bridged command. With a PFC2, you must enable bridged mircoflow policing for routed traffic as well. With a PFC3, you cannot apply microflow policing to ARP traffic. You cannot apply microflow policing to IPv6 multicast traffic.
You can include both an aggregate policer and a microflow policer in each policy map class to police a flow based on both its own bandwidth utilization and on its bandwidth utilization combined with that of other flows.
Note
If traffic is both aggregate and microflow policed, then the aggregate and microflow policers must both be in the same policy-map class and each must use the same conform-action and exceed-action keyword option: drop, set-dscp-transmit, set-prec-transmit, or transmit. For example, you could create a microflow policer with a bandwidth limit suitable for individuals in a group, and you could create a named aggregate policer with bandwidth limits suitable for the group as a whole. You could include both policers in policy map classes that match the groups traffic. The combination would affect individual flows separately and the group aggregately. For policy map classes that include both an aggregate and a microflow policer, PFC QoS responds to an out-of-profile status from either policer and, as specified by the policer, applies a new DSCP value or drops the packet. If both policers return an out-of-profile status, then if either policer specifies that the packet is to be dropped, it is dropped; otherwise, PFC QoS applies a marked-down DSCP value.
Note
To avoid inconsistent results, ensure that all traffic policed by the same aggregate policer has the same trust state.
41-22
OL-3999-08
Chapter 41
With a PFC3, policing uses the Layer 2 frame size. With a PFC2, policing uses the Layer 3 packet size. You specify the bandwidth utilization limit as a committed information rate (CIR). You can also specify a higher peak information rate (PIR). Packets that exceed a rate are out of profile or nonconforming. In each policer, you specify if out-of-profile packets are to be dropped or to have a new DSCP value applied to them (applying a new DSCP value is called markdown). Because out-of-profile packets do not retain their original priority, they are not counted as part of the bandwidth consumed by in-profile packets. If you configure a PIR, the PIR out-of-profile action cannot be less severe than the CIR out-of-profile action. For example, if the CIR out-of-profile action is to mark down the traffic, then the PIR out-of-profile action cannot be to transmit the traffic. For all policers, PFC QoS uses a configurable global table that maps the internal DSCP value to a marked-down DSCP value. When markdown occurs, PFC QoS gets the marked-down DSCP value from the table. You cannot specify marked-down DSCP values in individual policers.
Note
Policing with the conform-action transmit keywords supersedes the ingress LAN port trust state of matched traffic with trust DSCP or with the trust state defined by a trust policy-map class command. By default, the markdown table is configured so that no markdown occurs: the marked-down DSCP values are equal to the original DSCP values. To enable markdown, configure the table appropriately for your network. When you apply both ingress policing and egress policing to the same traffic, both the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does not support ingress markdown with egress drop or ingress drop with egress markdown.
Understanding Port-Based Queue Types

Port-based queue types are determined by the ASICs that control the ports. The following sections describe the queue types, drop thresholds, and buffers that are supported on the Catalyst 6500 series switch LAN modules:

Ingress and Egress Buffers and Layer 2 CoS-Based Queues, page 41-23 Ingress Queue Types, page 41-25 Egress Queue Types, page 41-26 Module to Queue Type Mappings, page 41-27
Ingress and Egress Buffers and Layer 2 CoS-Based Queues

The Ethernet LAN module port ASICs have buffers that are divided into a fixed number of queues. When congestion avoidance is enabled, PFC QoS uses the traffics Layer 2 CoS value to assign traffic to the queues. The buffers and queues store frames temporarily as they transit the switch. PFC QoS allocates the port ASIC memory as buffers for each queue on each port. The Catalyst 6500 series switch LAN modules support the following types of queues:

Standard queues Strict-priority queues
41-23
Configuring PFC QoS
The Catalyst 6500 series switch LAN modules support the following types of scheduling algorithms between queues:

Shaped round robin (SRR)SRR allows a queue to use only the allocated bandwidth. Deficit weighted round robin (DWRR)DWRR keeps track of any lower-priority queue under-transmission caused by traffic in a higher-priority queue and compensates in the next round. Weighted Round Robin (WRR)WRR does not explicitly reserve bandwidth for the queues. Instead, the amount of bandwidth assigned to each queue is user configurable. The percentage or weight allocated to a queue defines the amount of bandwidth allocated to the queue. Strict-priority queueingStrict priority queueing allows delay-sensitive data such as voice to be dequeued and sent before packets in other queues are dequeued, giving delay-sensitive data preferential treatment over other traffic. The switch services traffic in the strict-priority transmit queue before servicing the standard queues. After transmitting a packet from a standard queue, the switch checks for traffic in the strict-priority queue. If the switch detects traffic in the strict-priority queue, it suspends its service of the standard queue and completes service of all traffic in the strict-priority queue before returning to the standard queue.
The Catalyst 6500 series switch LAN modules provides congestion avoidance with these types of thresholds within a queue:
Weighted Random Early Detection (WRED)On ports with WRED drop thresholds, frames with a given QoS label are admitted to the queue based on a random probability designed to avoid buffer congestion. The probability of a frame with a given QoS label being admitted to the queue or discarded depends on the weight and threshold assigned to that QoS label. For example, if CoS 2 is assigned to queue 1, threshold 2, and the threshold 2 levels are 40 percent (low) and 80 percent (high), then frames with CoS 2 will not be dropped until queue 1 is at least 40 percent full. As the queue depth approaches 80 percent, frames with CoS 2 have an increasingly higher probability of being discarded rather than being admitted to the queue. Once the queue is over 80 percent full, all CoS 2 frames are dropped until the queue is less than 80 percent full. The frames the switch discards when the queue level is between the low and high thresholds are picked out at random, rather than on a per-flow basis or in a FIFO manner. This method works well with protocols such as TCP that can adjust to periodic packet drops by backing off and adjusting their transmission window size.
Tail-drop thresholdsOn ports with tail-drop thresholds, frames with a given QoS label are admitted to the queue until the drop threshold associated with that QoS label is exceeded; subsequent frames of that QoS label are discarded until the threshold is no longer exceeded. For example, if CoS 1 is assigned to queue 1, threshold 2, and the threshold 2 watermark is 60 percent, then frames with CoS 1 will not be dropped until queue 1 is 60 percent full. All subsequent CoS 1 frames will be dropped until the queue is less than 60 percent full. With some port types, you can configure the standard receive queue to use both a tail-drop and a WRED-drop threshold by mapping a CoS value to the queue or to the queue and a threshold. The switch uses the tail-drop threshold for traffic carrying CoS values mapped only to the queue. The switch uses WRED-drop thresholds for traffic carrying CoS values mapped to the queue and a threshold. All LAN ports of the same type use the same drop-threshold configuration.
Note
In Release 12.2(18)SXF5 and later releases, you can enable DSCP-based queues and thresholds on WS-X6708-10GE ports (see the Configuring DSCP-Based Queue Mapping section on page 41-100). The combination of multiple queues and the scheduling algorithms associated with each queue allows the switch to provide congestion avoidance.
41-24
OL-3999-08
Chapter 41
Figure 41-10 illustrates the drop thresholds for a 1q4t ingress LAN port. Drop thresholds in other configurations function similarly.
Figure 41-10 Receive Queue Drop Thresholds
Drop threshold 4: 100% Reserved for CoS 6 and 7 Reserved for CoS 4 and higher Reserved for CoS 2 and higher
Co
S
Drop threshold 3: 80%

Co
d7 an
S
4
Drop threshold 2: 60% Drop threshold 1: 50%
d5 an
Co S
2
d3 an 1 and
CoS
Available for traffic with any CoS value
Traffic is dropped
100% available for CoS 6 and 7 80% available for CoS 4 and 5 60% available for CoS 2 and 3 50% available for CoS 0 and 1
26249
Receive queue
(Default values shown)
Ingress Queue Types

To see the queue structure of a LAN port, enter the show queueing interface {ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port | include type command. The command displays one of the following architectures:

1q2t indicates one standard queue with one configurable tail-drop threshold and one nonconfigurable tail-drop threshold. 1q4t indicates one standard queue with four configurable tail-drop thresholds. 1q8t indicates one standard queue with eight configurable tail-drop thresholds. 2q8t indicates two standard queues, each with eight configurable tail-drop thresholds. 8q4t indicates eight standard queues, each with four thresholds, each configurable as either WRED-drop or tail-drop. 8q8t indicates eight standard queues, each with eight thresholds, each configurable as either WRED-drop or tail-drop. 1p1q4t indicates:
One strict-priority queue One standard queue with four configurable tail-drop thresholds.
41-25
Configuring PFC QoS
1p1q0t indicates:
One strict-priority queue One standard queue with no configurable threshold (effectively a tail-drop threshold at
100 percent).
1p1q8t indicates the following:

One strict-priority queue One standard queue with these thresholds:
Eight thresholds, each configurable as either WRED-drop or tail-drop One non configurable (100 percent) tail-drop threshold
Egress Queue Types

To see the queue structure of an egress LAN port, enter the show queueing interface {ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port | include type command. The command displays one of the following architectures:

2q2t indicates two standard queues, each with two configurable tail-drop thresholds. 1p2q2t indicates the following:
One strict-priority queue Two standard queues, each with two configurable WRED-drop thresholds

One strict-priority queue Three standard queues with these thresholds:
One threshold configurable as either WRED-drop or tail-drop One nonconfigurable (100 percent) tail-drop threshold

One strict-priority queue Two standard queues with these thresholds:
One WRED-drop threshold One non-configurable (100 percent) tail-drop threshold

One strict-priority queue Three standard queues, each with eight thresholds, each threshold configurable as either
WRED-drop or tail-drop

One strict-priority queue Seven standard queues, each with four thresholds, each threshold configurable as either
41-26
OL-3999-08
Chapter 41

One strict-priority queue Seven standard queues, each with eight thresholds, each threshold configurable as either
Module to Queue Type Mappings

The following tables show the module to queue structure mapping:

Supervisor Engine Module QoS Queue Structures Ethernet and Fast Ethernet Module Queue Structures Gigabit and 10/100/1000 Ethernet Modules 10 Gigabit Ethernet Modules
Table 41-2 Supervisor Engine Module QoS Queue Structures
Supervisor Engines WS-SUP720 WS-SUP720-3B WS-SUP720-3BXL WS-SUP32-10GE 10 Gigabit Ethernet ports Gigabit Ethernet port WS-SUP32-GE WS-X6K-S2U-MSFC2 WS-X6K-S2-MSFC2 WS-X6K-S2-PFC2
Ingress Queue and Drop Thresholds 1p1q4t
Ingress Queue Scheduler
Egress Queue and Drop Thresholds 1p2q2t
Egress Queue Scheduler WRR
Total Buffer Ingress Size Buffer Size 512 KB 73 KB
Egress Buffer Size 439 KB
2q8t
WRR
1p3q8t
DWRR SRR
193 MB 17.7 MB 17.7 MB
105 MB 9.6 MB 9.6 MB 73 KB
88 MB 8.1 MB 8.1 MB 439 KB
1p1q4t
1p2q2t
WRR
512 KB
Table 41-3 Ethernet and Fast Ethernet Module Queue Structures
Modules WS-X6524-100FX-MM WS-X6548-RJ-21 WS-X6548-RJ-45
Egress Queue Scheduler DWRR
Total Buffer Ingress Size Buffer Size 1,116 KB 28 KB
Egress Buffer Size 1,088 KB
41-27
Configuring PFC QoS
Table 41-3 Ethernet and Fast Ethernet Module Queue Structures (continued)
Modules WS-X6324-100FX-MM WS-X6324-100FX-SM WS-X6348-RJ-45 WS-X6348-RJ-45V WS-X6348-RJ-21V WS-X6224-100FX-MT WS-X6248-RJ-45 WS-X6248-TEL WS-X6248A-TEL WS-X6148-RJ-45 WS-X6148-RJ-45V WS-X6148-45AF WS-X6148-RJ-21 WS-X6148-RJ-21V WS-X6148-21AF WS-X6148A-RJ45 WS-X6148A-45AF WS-X6148X2-RJ-45 WS-X6148X2-45AF WS-X6196-RJ-21 WS-X6196-21AF WS-X6024-10FL-MT
Ingress Queue and Drop Thresholds 1q4t
Egress Queue and Drop Thresholds 2q2t
64 KB
8 KB
56 KB
128 KB
16 KB
112 KB
1p1q4t 1p1q0t
1p3q8t 1p3q1t
DWRR DWRR
5.3 MB 1,116 KB
60KB 28 KB
5.3 MB 1,088 KB
1q4t
2q2t
WRR
64 KB
8 KB
56 KB
Table 41-4 Gigabit and 10/100/1000 Ethernet Modules
Modules WS-X6816-GBIC
41-28
OL-3999-08
Chapter 41
Table 41-4 Gigabit and 10/100/1000 Ethernet Modules
Modules WS-X6748-GE-TX with CFC WS-X6748-SFP with DFC3 WS-X6748-SFP with CFC WS-X6724-SFP with DFC3 WS-X6724-SFP with CFC WS-X6548-GE-TX WS-X6548V-GE-TX WS-X6548-GE-45AF WS-X6516-GBIC WS-X6516A-GBIC WS-X6516-GE-TX WS-X6408-GBIC WS-X6408A-GBIC WS-X6416-GBIC WS-X6416-GE-MT WS-X6316-GE-TX WS-X6148-GE-TX WS-X6148V-GE-TX WS-X6148-GE-45AF WS-X6148A-GE-TX WS-X6148A-GE-45AF
Ingress Queue and Drop Thresholds 1q8t 2q8t 1q8t 2q8t 1q8t 1q2t
Ingress Queue Scheduler WRR WRR WRR
Egress Queue Scheduler DWRR
Total Buffer Ingress Size Buffer Size 1.3 MB 166 KB
Egress Buffer Size 1.2 MB
WS-X6748-GE-TX with DFC3 2q8t
1p2q2t
WRR
1.4 MB
185 KB
1.2 MB
1p1q4t
1p2q2t
WRR WRR WRR
512 KB 1 MB 512 KB
73 KB 135 KB 73 KB 80 KB 73 KB
439 KB 946 KB 439 KB 432 KB 439 KB
1q4t 1p1q4t
2q2t 1p2q2t
WRR WRR
1q2t
1.4 MB
185 KB
1.2 MB
1p3q8t
DWRR
5.5 MB
120 KB
5.4 MB
Table 41-5 10 Gigabit Ethernet Modules
Modules WS-X6708-10GE WS-X6704-10GE with DFC3 WS-X6704-10GE with CFC WS-X6502-10GE WS-X6501-10GEX4
Ingress Queue and Drop Thresholds 8q4t 8q8t 1q8t 1p1q8t
Ingress Queue Scheduler DWRR WRR
Egress Queue and Drop Thresholds 1p7q4t 1p7q8t 1p2q1t
Egress Queue Scheduler DWRR SRR DWRR DWRR
Total Buffer Ingress Size Buffer Size 200 MB 16 MB 64.2 MB 108 MB 2 MB 256 KB
Egress Buffer Size 90 MB 14 MB 64 MB
41-29
Chapter 41 PFC QoS Default Configuration
Configuring PFC QoS
PFC QoS Default Configuration

These sections describe the PFC QoS default configuration:

PFC QoS Global Settings, page 41-30 Default Values With PFC QoS Enabled, page 41-31 Default Values With PFC QoS Disabled, page 41-50
PFC QoS Global Settings

The following global PFC QoS settings apply: Feature PFC QoS global enable state PFC QoS port enable state Port CoS value Microflow policing IntraVLAN microflow policing Port-based or VLAN-based PFC QoS Received CoS to initial internal DSCP map (initial internal DSCP set from received CoS values) Default Value Disabled Enabled when PFC QoS is globally enabled 0 Enabled Disabled Port-based CoS 0 = DSCP 0 CoS 1 = DSCP 8 CoS 2 = DSCP 16 CoS 3 = DSCP 24 CoS 4 = DSCP 32 CoS 5 = DSCP 40 CoS 6 = DSCP 48 CoS 7 = DSCP 56
Received IP precedence to initial internal DSCP map IP precedence 0 = DSCP 0 IP precedence 1 = DSCP 8 (initial internal DSCP set from received IP IP precedence 2 = DSCP 16 precedence values) IP precedence 3 = DSCP 24 IP precedence 4 = DSCP 32 IP precedence 5 = DSCP 40 IP precedence 6 = DSCP 48 IP precedence 7 = DSCP 56 Final internal DSCP to egress CoS map (egress CoS set from final internal DSCP values) DSCP 07 = CoS 0 DSCP 815 = CoS 1 DSCP 1623 = CoS 2 DSCP 2431 = CoS 3 DSCP 3239 = CoS 4 DSCP 4047 = CoS 5 DSCP 4855 = CoS 6 DSCP 5663 = CoS 7 Marked-down DSCP value equals original DSCP value (no markdown) None
Marked-down DSCP from DSCP map Policers
41-30
OL-3999-08
Chapter 41
Configuring PFC QoS PFC QoS Default Configuration
Feature Policy maps Protocol-independent MAC ACL filtering VLAN-based MAC ACL QoS filtering
Default Value None Disabled Disabled
Default Values With PFC QoS Enabled

These sections list the default values that apply when PFC QoS is enabled:

Receive-Queue Limits, page 41-31 Transmit-Queue Limit s, page 41-31 Bandwidth Allocation Ratios, page 41-32 Default Drop-Threshold Percentages and CoS Value Mappings, page 41-32
Note
The ingress LAN port trust state defaults to untrusted with QoS enabled.
Receive-Queue Limits
Feature 2q8t 8q4t Default Value Low priority: 80% High priority: 20% Low priority: 80% Intermediate queues: 0% High priority: 20% 8q8t Lowest priority: 80% Intermediate queues: 0% Highest priority: 20%
Transmit-Queue Limit s
Feature 2q2t 1p2q2t Default Value Low priority: 80% High priority: 20% Low priority: 70% High priority: 15% Strict priority 15%
41-31
Configuring PFC QoS
Feature 1p2q1t
Default Value Low priority: 70% High priority: 15% Strict priority 15%
1p3q8t
Low priority: 50% Medium priority: 20% High priority: 15% Strict priority 15%
1p7q4t
Standard queue 1 (lowest priority): 50% Standard queue 2: 20% Standard queue 3: 15% Standard queues 4 through 7: 0% Strict priority 15%
1p7q8t
Standard queue 1 (lowest priority): 50% Standard queue 2: 20% Standard queue 3: 15% Standard queues 4 through 7: 0% Strict priority 15%
Bandwidth Allocation Ratios

Feature 2q8t 8q4t 8q8t 1p3q8t 1p7q4t 1p7q8t 1p2q1t 2q2t, 1p2q2t, and 1p2q1t 1p3q1t Default Value 90:10 90:0:0:0:0:0:0:10 90:0:0:0:0:0:0:10 100:150:200 100:150:200:0:0:0:0:0 100:150:200:0:0:0:0 100:255 5:255 100:150:255
Default Drop-Threshold Percentages and CoS Value Mappings

The following tables list the default drop-thresholds values and CoS mappings for different queue types:

1q2t Receive Queues, page 41-33 1q4t Receive Queues, page 41-34 1p1q4t Receive Queues, page 41-34 1p1q0t Receive Queues, page 41-35
41-32
OL-3999-08
Chapter 41
1p1q8t Receive Queues, page 41-35 1q8t Receive Queues, page 41-36 2q8t Receive Queues, page 41-37 8q4t Receive Queues, page 41-38 8q8t Receive Queues, page 41-42 2q2t Transmit Queues, page 41-42 1p2q2t Transmit Queues, page 41-43 1p3q8t Transmit Queues, page 41-44 1p7q4t Transmit Queues, page 41-45 1p7q8t Transmit Queues, page 41-48 1p3q1t Transmit Queues, page 41-49 1p2q1t Transmit Queues, page 41-50
Note
The receive queue values shown are the values in effect when the port is configured to trust CoS or DSCP. When the port is untrusted, the receive queue values are the same as when QoS is globally disabled.
1q2t Receive Queues
Feature Standard receive queue Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop
Default Value 0, 1, 2, 3, and 4 80% 5, 6, and 7 100% (not configurable)
WRED-drop Not supported
41-33
Configuring PFC QoS
1q4t Receive Queues
Feature Standard receive queue Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop
Default Value 0 and 1 50% 2 and 3 60% 4 and 5 80% 6 and 7 100%
1p1q4t Receive Queues
Feature Standard receive queue Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop Strict-priority receive queue CoS Tail-drop
Default Value 0 and 1 50% 2 and 3 60% 4 and 6 80% 7 100% 5 100% (nonconfigurable)
41-34
OL-3999-08
Chapter 41
Feature Standard receive queue CoS Tail-drop Strict-priority receive queue CoS Tail-drop
Default Value 0, 1, 2, 3, 4, 6, and 7 100% (nonconfigurable) 5 100% (nonconfigurable)
Feature Standard receive queue Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop Threshold 5 CoS Tail-drop Threshold 6 CoS Tail-drop Threshold 7 CoS Tail-drop Strict-priority receive queue CoS Tail-drop
Default Value 0 Disabled; 70% 1 Disabled; 70% 2 Disabled; 80% 3 Disabled; 80% 4 Disabled; 90% 6 Disabled; 90% 7 Disabled; 100% 5 100% (nonconfigurable)
WRED-drop Enabled; 40% low, 70% high
WRED-drop Enabled;70% low, 100% high
41-35
Configuring PFC QoS
1q8t Receive Queues
Feature Standard receive queue Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop Threshold 5 CoS Tail-drop Threshold 6 CoS Tail-drop Threshold 7 CoS Tail-drop Threshold 8 CoS Tail-drop
Default Value 0 50% None 50% 1, 2, 3, 4 60% None 60% 6 and 7 80% None 80% 5 100% None 100%
41-36
OL-3999-08
Chapter 41
2q8t Receive Queues
Feature Standard receive queue 1 Threshold 1 (low priority) CoS Tail-drop CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop Thresholds 58 CoS Tail-drop Standard receive queue 2 Threshold 1 (high priority) CoS Tail-drop
Default Value 0 and 1 70% 2 and 3 80% 4 90% 6 and 7 100% None 100% 5 100% None 100%
WRED-drop Not supported Threshold 2
WRED-drop Not supported Thresholds 28 CoS Tail-drop
41-37
Configuring PFC QoS
8q4t Receive Queues
Feature Standard receive queue 1 (lowest priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard receive queue 2 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value 0 and 1 09, 11, 13, 1517, 19, 21, 23, 25, 27, 29, 31, 33, 39, 4145, 47 Disabled; 70% 2 and 3 Disabled; 80% 4 Disabled; 90% 6 and 7 Disabled; 100% None 14 Enabled; 100% None 12 Enabled; 100% None 10 Enabled; 100% None None Enabled; 100%
WRED-drop Disabled; 100% low, 100% high
41-38
OL-3999-08
Chapter 41
Feature (continued) Standard receive queue 3 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard receive queue 4 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value None 22 Enabled; 100% None 20 Enabled; 100% None 18 Enabled; 100% None None Enabled; 100% None 24 and 30 Enabled; 100% None 28 Enabled; 100% None 26 Enabled; 100% None None Enabled; 100%
41-39
Configuring PFC QoS
Feature (continued) Standard receive queue 5 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard receive queue 6 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value None 32, 3438 Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% None 4863 Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100%
41-40
OL-3999-08
Chapter 41
Feature (continued) Standard receive queue 7 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard receive queue 8 (high priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% 5 40 and 46 Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100%
41-41
Configuring PFC QoS
8q8t Receive Queues
Feature Standard receive queue 1 (lowest priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop Thresholds 58 CoS Tail-drop Standard receive queues 27 (intermediate priorities) Thresholds 18 CoS Tail-drop Threshold 1 CoS Tail-drop Thresholds 28 CoS Tail-drop
Default Value 0 and 1 Disabled; 70% 2 and 3 Disabled; 80% 4 Disabled; 90% 6 and 7 Disabled; 100% None Disabled; 100% None Enabled; 100% 5 Enabled; 100% None Enabled; 100%
WRED-drop Disabled; 100% low, 100% high Standard receive queue 8 (highest priority)
2q2t Transmit Queues
Feature Standard transmit queue 1 (low priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop
Default Value 0 and 1 80% 2 and 3 100%
41-42
OL-3999-08
Chapter 41
Feature Standard transmit queue 2 (high priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop
Default Value 4 and 5 80% 6 and 7 100%
1p2q2t Transmit Queues
Feature Standard transmit queue 1 (low priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Standard transmit queue 2 (high priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Strict-priority transmit queue CoS Tail-drop
Default Value 0 and 1 Not supported 2 and 3 Not supported 4 and 6 Not supported 7 Not supported 5 100% (nonconfigurable)
WRED-drop 40% low, 70% high
41-43
Configuring PFC QoS
Feature Standard transmit queue 1 (lowest priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Threshold 3 CoS Tail-drop Threshold 4 CoS Tail-drop Thresholds 58 CoS Tail-drop Standard transmit queue 2 (medium priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Thresholds 38 CoS Tail-drop Standard transmit queue 3 (high priority) Threshold 1 CoS Tail-drop Thresholds 28 CoS Tail-drop Strict-priority transmit queue CoS Tail-drop
Default Value 0 Disabled; 70% 1 Disabled; 100% None Disabled; 100% None Disabled; 100% None Disabled; 100% 2 Disabled; 70% 3 and 4 Disabled; 100% None Disabled; 100% 6 and 7 Disabled; 100% None Disabled; 100% 5 100% (nonconfigurable)
41-44
OL-3999-08
Chapter 41
Feature Standard transmit queue 1 (lowest priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard transmit queue 2 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value 0 and 1 09, 11, 13, 1517, 19, 21, 23, 25, 27, 29, 31, 33, 39, 4145, 47 Disabled; 70% 2 and 3 Disabled; 100% 4 Disabled; 100% 6 and 7 Disabled; 100% None 14 Disabled; 70% None 12 Disabled; 100% None 10 Disabled; 100% None None Disabled; 100%
41-45
Configuring PFC QoS
Feature (continued) Standard transmit queue 3 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard transmit queue 4 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value None 22 Disabled; 100% None 20 Disabled; 100% None 18 Disabled; 100% None None Disabled; 100% None 24 and 30 Enabled; 100% None 28 Enabled; 100% None 26 Enabled; 100% None None Enabled; 100%
41-46
OL-3999-08
Chapter 41
Feature (continued) Standard transmit queue 5 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Standard transmit queue 6 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop
Default Value None 32, 3438 Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% None 4863 Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100%
41-47
Configuring PFC QoS
Feature (continued) Standard transmit queue 7 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Threshold 3 CoS DSCP Tail-drop Threshold 4 CoS DSCP Tail-drop Strict-priority transmit queue CoS DSCP Tail-drop
Default Value None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% 5 40 and 46 100% (nonconfigurable)
Feature Standard transmit queue 1 (lowest priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Thresholds 38 CoS Tail-drop
Default Value 0 Disabled; 70% 1 Disabled; 100% None Disabled; 100%
41-48
OL-3999-08
Chapter 41
Feature (continued) Standard transmit queue 2 (intermediate priority) Threshold 1 CoS Tail-drop Threshold 2 CoS Tail-drop Thresholds 38 CoS Tail-drop Standard transmit queue 3 (intermediate priority) Threshold 1 CoS Tail-drop Thresholds 28 CoS Tail-drop Standard transmit queues 47 (intermediate priorities) Thresholds 18 CoS Tail-drop CoS Tail-drop
Default Value 2 Disabled; 70% 3 and 4 Disabled; 100% None Disabled; 100% 6 and 7 Disabled; 100% None Disabled; 100% None Disabled; 100% 5 100% (nonconfigurable)
WRED-drop Enabled; 100% low, 100% high Strict-priority transmit queue
Feature Standard transmit queue 1 (lowest priority) Threshold 1 CoS Tail-drop Threshold 1 CoS Tail-drop Threshold 1 CoS Tail-drop CoS Tail-drop
Default Value 0 and 1 Disabled; 100% 2, 3, and 4 Disabled; 100% 6 and 7 Disabled; 100% 5 100% (nonconfigurable)
WRED-drop Enabled; 70% low, 100% high Standard transmit queue 2 (medium priority)
WRED-drop Enabled; 70% low, 100% high Standard transmit queue 3 (high priority)
41-49
Chapter 41 PFC QoS Configuration Guidelines and Restrictions
Configuring PFC QoS
Feature Standard transmit queue 1 (lowest priority) Threshold 1 CoS Tail-drop Threshold 1 CoS Tail-drop CoS Tail-drop
Default Value 0, 1, 2, and 3 Not supported 4, 6, and 7 Not supported 5 100% (nonconfigurable)
WRED-drop Enabled; 70% low, 100% high Standard transmit queue 3 (high priority)
Default Values With PFC QoS Disabled

Feature Ingress LAN port trust state Receive-queue drop-threshold percentages Transmit-queue drop-threshold percentages Transmit-queue bandwidth allocation ratio Transmit-queue size ratio CoS value and drop threshold mapping Default Value trust DSCP. All thresholds set to 100%. All thresholds set to 100%. 255:1. Low priority: 100% (other queues not used). All QoS labels mapped to the low-priority queue.
PFC QoS Configuration Guidelines and Restrictions

When configuring PFC QoS, follow these guidelines and restrictions:

General Guidelines, page 41-51 PFC3 Guidelines, page 41-53 PFC2 Guidelines, page 41-53 Class Map Command Restrictions, page 41-54 Policy Map Command Restrictions, page 41-54 Policy Map Class Command Restrictions, page 41-54 Supported Granularity for CIR and PIR Rate Values, page 41-55 Supported Granularity for CIR and PIR Token Bucket Sizes, page 41-55 IP Precedence and DSCP Values, page 41-56
41-50
OL-3999-08
Chapter 41
Configuring PFC QoS PFC QoS Configuration Guidelines and Restrictions
General Guidelines

Configure the same trust mode on all ports supported by an ASIC. Mismatched trust modes cause inconsistent bandwidth and queue-limit ratios. The match ip precedence and match ip dscp commands filter only IPv4 traffic. In Release 12.2(18)SXE and later releases, the match precedence and match dscp commands filter IPv4 and IPv6 traffic. In Release 12.2(18)SXE and later releases, the set ip dscp and set ip precedence commands are saved in the configuration file as set dscp and set precedence commands. In Release 12.2(18)SXE and later releases, PFC QoS supports the set dscp and set precedence policy map class commands for IPv4 and IPv6 traffic. The flowmask requirements of QoS, NetFlow, and NetFlow data export (NDE) might conflict, especially if you configure microflow policing. With egress ACL support for remarked DSCP and VACL capture both configured on an interface, VACL capture might capture two copies of each packet, and the second copy might be corrupt. You cannot configure egress ACL support for remarked DSCP on tunnel interfaces. Egress ACL support for remarked DSCP supports IP unicast traffic. Egress ACL support for remarked DSCP is not relevant to multicast traffic. PFC QoS applies ingress QoS changes to multicast traffic before applying egress QoS. NetFlow and NetFlow data export (NDE) do not support interfaces where egress ACL support for remarked DSCP is configured. When egress ACL support for remarked DSCP is configured on any interface, you must configure an interface-specific flowmask to enable NetFlow and NDE support on interfaces where egress ACL support for remarked DSCP is not configured. Enter either the mls flow ip interface-destination-source or the mls flow ip interface-full global configuration mode command. Interface counters are not accurate on interfaces where egress ACL support for remarked DSCP is configured. You cannot apply microflow policing to IPv6 multicast traffic. You cannot apply microflow policing to traffic that has been permitted by egress ACL support for remarked DSCP. Traffic that has been permitted by egress ACL support for remarked DSCP cannot be tagged as MPLS traffic. (The traffic can be tagged as MPLS traffic on another network device.) When you apply both ingress policing and egress policing to the same traffic, both the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does not support ingress markdown with egress drop or ingress drop with egress markdown. (CSCea23571) If traffic is both aggregate and microflow policed, then the aggregate and microflow policers must both be in the same policy-map class and each must use the same conform-action and exceed-action keyword option: drop, set-dscp-transmit, set-prec-transmit, or transmit. You cannot configure PFC QoS features on tunnel interfaces. PFC QoS does not rewrite the payload ToS byte in tunnel traffic. PFC QoS filters only by ACLs, dscp values, or IP precedence values.
41-51
Configuring PFC QoS
For these commands, PFC QoS applies identical configuration to all LAN ports controlled by the same application-specific integrated circuit (ASIC):
rcv-queue random-detect rcv-queue queue-limit wrr-queue queue-limit wrr-queue bandwidth (except Gigabit Ethernet LAN ports) priority-queue cos-map rcv-queue cos-map wrr-queue cos-map wrr-queue threshold rcv-queue threshold wrr-queue random-detect wrr-queue random-detect min-threshold wrr-queue random-detect max-threshold
Configure these commands only on physical ports. Do not configure these commands on logical interfaces:
priority-queue cos-map wrr-queue cos-map wrr-queue random-detect wrr-queue random-detect max-threshold wrr-queue random-detect min-threshold wrr-queue threshold wrr-queue queue-limit wrr-queue bandwidth rcv-queue cos-map rcv-queue bandwidth rcv-queue random-detect rcv-queue random-detect max-threshold rcv-queue random-detect min-threshold rcv-queue queue-limit rcv-queue cos-map rcv-queue threshold
Note
IP multicast switching using egress packet replication is not compatible with QoS. In some cases, egress replication can result in the incorrect COS or DSCP marking of packets. If you are using QoS and your switching modules are capable of egress replication, enter the mls ip multicast replication-mode ingress command to force ingress replication.
41-52
OL-3999-08
Chapter 41
PFC3 Guidelines

With Release 12.2(18)SXE and later releases, all versions of the PFC3 support QoS for IPv6 unicast and multicast traffic. To display information about IPv6 PFC QoS, enter the show mls qos ipv6 command. The QoS features implemented in the port ASICs (queue architecture and dequeuing algorithms) support IPv4 and IPv6 traffic. The PFC3 supports IPv6 named extended ACLs and named standard ACLs. In Release 12.2(18)SXE and later releases, the PFC3 supports the match protocol ipv6 command. Because of conflicting TCAM lookup flow key bit requirements, you cannot configure IPv6 DSCP-based filtering and IPv6 Layer 4 range-based filtering on the same interface. For example:
If you configure both a DSCP value and a Layer 4 greater than (gt) or less than (lt) operator
in an IPv6 ACE, you cannot use the ACL for PFC QoS filtering.
If you configure a DSCP value in one IPv6 ACL and a Layer 4 greater than (gt) or less than
(lt) operator in another IPv6 ACL, you cannot use both ACLs in different class maps on the same interface for PFC QoS filtering.

In Release 12.2(18)SXE and later releases, you can apply aggregate and microflow policers to IPv6 traffic, but you cannot apply microflow policing to IPv6 multicast traffic. With egress ACL support for remarked DSCP configured, the PFC3 does not provide hardware-assistance for these features:
Cisco IOS reflexive ACLs TCP intercept Context-Based Access Control (CBAC) Network Address Translation (NAT)
With a PFC3, you cannot apply microflow policing to ARP traffic. The PFC3 does not apply egress policing to traffic that is being bridged to the MSFC3. The PFC3 does not apply egress policing or egress DSCP mutation to multicast traffic from the MSFC3. With a PFC2 or PFC3A, PFC QoS does not rewrite the ToS byte in bridged multicast traffic. The PFC3 supports up to 1022 aggregate policers, but some PFC QoS commands other than the police command will be included in this count. By default, any policy using a set or trust command will be included in the aggregate policer count. You can disable the addition of the set or trust commands to the aggregate policer count by entering the no mls qos marking statistics command, but you will then be unable to collect statistics for the classmaps associated with these commands. You can view the aggregate policer count in the QoS Policer Resources section of the output of the show platform hardware capacity qos command.
PFC2 Guidelines
The PFC2 supports the match protocol class map command, which configures NBAR and sends all traffic on the Layer 3 interface, both ingress and egress, to be processed in software on the MSFC2. To configure NBAR, refer to this publication: http://www.cisco.com/en/US/docs/ios/12_4t/qos/configuration/guide/qsnbar1.html
41-53
Configuring PFC QoS
The PFC2 does not support these PFC QoS features:

Egress policing Egress DSCP mutation DSCP Transparency VLAN-based QoS with DFCs installed
The PFC2 does not support the modules that support ingress CoS mutation on IEEE 802.1Q tunnel ports.
Class Map Command Restrictions

With Release 12.2(18)SXE and later releases, PFC QoS supports the match any class map command. PFC QoS supports class maps that contain a single match command. PFC QoS does not support these class map commands:
match cos match classmap match destination-address match input-interface match qos-group match source-address
Policy Map Command Restrictions

PFC QoS does not support these policy map commands:

class class_name destination-address class class_name input-interface class class_name protocol class class_name qos-group class class_name source-address
Policy Map Class Command Restrictions

PFC QoS does not support these policy map class commands:

bandwidth priority queue-limit random-detect set qos-group service-policy
41-54
OL-3999-08
Chapter 41
Supported Granularity for CIR and PIR Rate Values

PFC QoS has the following hardware granularity for CIR and PIR rate values: CIR and PIR Rate Value Range 32768 to 2097152 (2 Mbs) 2097153 to 4194304 (4 Mbs) 4194305 to 8388608 (8 Mbs) 8388609 to 16777216 (16 Mbs) 16777217 to 33554432 (32 Mbs) 33554433 to 67108864 (64 Mbs) 67108865 to 134217728 (128 Mbs) 134217729 to 268435456 (256 Mbs) 268435457 to 536870912 (512 Mbs) 536870913 to 1073741824 (1 Gps) 1073741825 to 2147483648 (2 Gps) 2147483649 to 4294967296 (4 Gps) 4294967296 to 8589934592 (8 Gps) Granularity 32768 (32 Kb) 65536 (64 Kb) 131072 (128 Kb) 262144 (256 Kb) 524288 (512 Kb) 1048576 (1 Mb) 2097152 (2 Mb) 4194304 (4 Mb) 8388608 (8 Mb) 16777216 (16 Mb) 33554432 (32 Mb) 67108864 (64 Mb) 134217728 (128 Mb)
8589934592 to 10000000000 (10 Gps) 268435456 (256 Mb) Within each range, PFC QoS programs the PFC with rate values that are multiples of the granularity values.
Supported Granularity for CIR and PIR Token Bucket Sizes

PFC QoS has the following hardware granularity for CIR and PIR token bucket (burst) sizes: CIR and PIR Token Bucket Size Range Granularity 1 to 32768 (32 KB) 32769 to 65536 (64 KB) 65537 to 131072 (128 KB) 131073 to 262144 (256 KB) 262145 to 524288 (512 KB) 524289 to 1048576 (1 MB) 1048577 to 2097152 (2 MB) 2097153 to 4194304 (4 MB) 4194305 to 8388608 (8 MB) 8388609 to 16777216 (16 MB) 16777217 to 33554432 (32 MB) 1024 (1 KB) 2048 (2 KB) 4096 (4 KB) 8196 (8 KB) 16392 (16 KB) 32768 (32 KB) 65536 (64 KB) 131072 (128 KB) 262144 (256 KB) 524288 (512 KB) 1048576 (1 MB)
41-55
Chapter 41 Configuring PFC QoS
Configuring PFC QoS
Within each range, PFC QoS programs the PFC with token bucket sizes that are multiples of the granularity values.
IP Precedence and DSCP Values

3-bit IP Precedence 6 MSb1 of ToS 8 7 6 5 4 3 6-bit DSCP 3-bit IP Precedence 6 MSb1 of ToS 8 7 6 5 4 3 6-bit DSCP
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1
0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1
0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1
0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0 1 1 1 1 1 1 1 1
0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1 0 0 0 0 1 1 1 1
0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1 0 0 1 1
0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1 0 1
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
1. MSb = most significant bit
Configuring PFC QoS

These sections describe how to configure PFC QoS on the Catalyst 6500 series switches:

Enabling PFC QoS Globally, page 41-57 Enabling Ignore Port Trust, page 41-58
41-56
OL-3999-08
Chapter 41
Configuring PFC QoS Configuring PFC QoS
Configuring DSCP Transparency, page 41-59 Enabling Queueing-Only Mode, page 41-60 Enabling Microflow Policing of Bridged Traffic, page 41-60 Enabling VLAN-Based PFC QoS on Layer 2 LAN Ports, page 41-61 Enabling Egress ACL Support for Remarked DSCP, page 41-62 Creating Named Aggregate Policers, page 41-63 Configuring a PFC QoS Policy, page 41-65 Configuring Egress DSCP Mutation on a PFC3, page 41-83 Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports, page 41-85 Configuring DSCP Value Maps, page 41-87 Configuring the Trust State of Ethernet LAN and OSM Ports, page 41-91 Configuring the Ingress LAN Port CoS Value, page 41-93 Configuring Standard-Queue Drop Threshold Percentages, page 41-93 Mapping QoS Labels to Queues and Drop Thresholds, page 41-99 Allocating Bandwidth Between Standard Transmit Queues, page 41-109 Setting the Receive-Queue Size Ratio, page 41-111 Configuring the Transmit-Queue Size Ratio, page 41-112
Note
PFC QoS processes both unicast and multicast traffic.
Enabling PFC QoS Globally

To enable PFC QoS globally, perform this task: Command
Step 1
Router(config)# mls qos Router(config)# no mls qos
Purpose Enables PFC QoS globally on the switch. Disables PFC QoS globally on the switch. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls qos [ipv6]
This example shows how to enable PFC QoS globally:

Router# configure terminal Router(config)# mls qos Router(config)# end Router#

Router# show mls qos QoS is enabled globally Microflow QoS is enabled globally QoS global counters: Total packets: 544393
41-57
Configuring PFC QoS
IP shortcut packets: 1410 Packets dropped by policing: 0 IP packets with TOS changed by policing: 467 IP packets with COS changed by policing: 59998 Non-IP packets with COS changed by policing: 0 Router#
Enabling Ignore Port Trust

In Release 12.2(18)SXF5 and later releases, the ignore port trust feature allows an ingress policy to apply a configured IP precedence or DSCP value to any traffic, rather than only to untrusted traffic. To enable ignore port trust, perform this task: Command
Step 1
Router(config)# mls qos marking ignore port-trust Router(config)# no mls qos marking ignore port-trust
Purpose Enables ignore port trust globally on the switch. Disables ignore port trust globally on the switch (default). Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls qos | include ignores
Note
For untrusted traffic, when ignore port trust is enabled, PFC QoS does the following:

For IP traffic, PFC QoS uses the received DSCP value as the initial internal DSCP value. For traffic without a recognizable ToS byte, PFC QoS maps the port CoS value to the initial internal DSCP value.
This example shows how to enable ignore port trust and verify the configuration:
Router# configure terminal Router(config)# mls qos marking ignore port-trust Router(config)# end Router# show mls qos | include ignores Policy marking ignores port_trust Router#
41-58
OL-3999-08
Chapter 41
Configuring DSCP Transparency

Note
In addition to support for other IP traffic, PFC3C and PFC3CXL mode support the no mls qos rewrite ip dscp command for these traffic types:
MPLS traffic Traffic in IP in IP tunnels Traffic in GRE tunnels
In addition to support for other IP traffic, PFC3B and PFC3BXL mode support the no mls qos rewrite ip dscp command for these traffic types:
Except on PE routers, MPLS traffic Traffic in IP in IP tunnels Traffic in GRE tunnels
PFC3A mode does not support the no mls qos rewrite ip dscp command for MPLS traffic, traffic in IP in IP tunnels, and traffic in GRE tunnels.
To enable DSCP transparency, which preserves the received Layer 3 ToS byte, perform this task: Command
Step 1
Router(config)# no mls qos rewrite ip dscp Router(config)# mls qos rewrite ip dscp
Purpose Disables egress ToS-byte rewrite globally on the switch. Enables egress ToS-byte rewrite globally on the switch. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls qos | include rewrite
When you preserve the received Layer 3 ToS byte, QoS uses the marked or marked-down CoS value for egress queueing and in egress tagged traffic. This example shows how to preserve the received Layer 3 ToS byte and verify the configuration:
Router# configure terminal Router(config)# no mls qos rewrite ip dscp Router(config)# end Router# show mls qos | include rewrite QoS ip packet dscp rewrite disabled globally Router#
41-59
Configuring PFC QoS
Enabling Queueing-Only Mode

To enable queueing-only mode on the switch, perform this task: Command
Step 1
Router(config)# mls qos queueing-only Router(config)# no mls qos queueing-only
Purpose Enables queueing-only mode on the switch. Disables PFC QoS globally on the switch.
Note
You cannot disable queueing-only mode separately.
Step 2 Step 3
Router(config)# end Router# show mls qos
When you enable queueing-only mode, the switch does the following:

Disables marking and policing globally Configures all ports to trust Layer 2 CoS
Note
The switch applies the port CoS value to untagged ingress traffic and to traffic that is received through ports that cannot be configured to trust CoS.
This example shows how to enable queueing-only mode:

Router# configure terminal Router(config)# mls qos queueing-only Router(config)# end Router#
Enabling Microflow Policing of Bridged Traffic

Note
With a PFC2, to apply microflow policing to multicast traffic, you must enter the mls qos bridged command on the Layer 3 multicast ingress interfaces. By default, microflow policers affect only routed traffic. To enable microflow policing of bridged traffic on specified VLANs, perform this task:
Command
Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port}} Router(config-if)# mls qos bridged
Purpose Selects the interface to configure. Enables microflow policing of bridged traffic, including bridge groups, on the VLAN. Disables microflow policing of bridged traffic. Exits configuration mode. Verifies the configuration.
Router(config-if)# no mls qos bridged
Step 3 Step 4
Router(config-if)# end Router# show mls qos 1.
41-60
OL-3999-08
Chapter 41
This example shows how to enable microflow policing of bridged traffic on VLANs 3 through 5:
Router# configure terminal Enter configuration commands, one per line. Router(config)# interface range vlan 3 - 5 Router(config-if)# mls qos bridged Router(config-if)# end Router# End with CNTL/Z.

Router# show mls qos | begin Bridged QoS Bridged QoS is enabled on the following interfaces: Vl3 Vl4 Vl5 <...output truncated...> Router#
Enabling VLAN-Based PFC QoS on Layer 2 LAN Ports

Note
With a PFC2, PFC QoS does not support VLAN-based QoS with DFCs installed. With a PFC3, PFC QoS supports VLAN-based QoS with DFC3s installed. With a PFC3, you can attach policy maps to Layer 3 interfaces for application of PFC QoS to egress traffic. VLAN-based or port-based PFC QoS on Layer 2 ports is not relevant to application of PFC QoS to egress traffic on Layer 3 interfaces.
By default, PFC QoS uses policy maps attached to LAN ports. For ports configured as Layer 2 LAN ports with the switchport keyword, you can configure PFC QoS to use policy maps attached to a VLAN. Ports not configured with the switchport keyword are not associated with a VLAN. To enable VLAN-based PFC QoS on a Layer 2 LAN port, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type1 slot/port} | {port-channel number}} Router(config-if)# mls qos vlan-based
Purpose Selects the interface to configure. Enables VLAN-based PFC QoS on a Layer 2 LAN port or a Layer 2 EtherChannel. Disables VLAN-based PFC QoS. Exits configuration mode. Verifies the configuration.
Router(config-if)# no mls qos vlan-based
Step 3 Step 4
Router(config-if)# end Router# show mls qos 1.
This example shows how to enable VLAN-based PFC QoS on Fast Ethernet port 5/42:
Router# configure terminal Enter configuration commands, one per line. Router(config)# interface fastethernet 5/42 Router(config-if)# mls qos vlan-based Router(config-if)# end End with CNTL/Z.
41-61
Configuring PFC QoS

Router# show mls qos | begin QoS is vlan-based QoS is vlan-based on the following interfaces: Fa5/42 <...Output Truncated...>
Note
Configuring a Layer 2 LAN port for VLAN-based PFC QoS preserves the policy map port configuration. The no mls qos vlan-based port command reenables any previously configured port commands.
Enabling Egress ACL Support for Remarked DSCP

To enable egress ACL support for remarked DSCP on an ingress interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} Router(config-if)# platform ip features sequential [access-group IP_acl_name_or_number] Router(config-if)# no platform ip features sequential [access-group IP_acl_name_or_number]
Purpose Selects the ingress interface to configure. Enables egress ACL support for remarked DSCP on the ingress interface. Disables egress ACL support for remarked DSCP on the ingress interface. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show running-config interface ({type1 slot/port} | {port-channel number}} 1.
When configuring egress ACL support for remarked DSCP on an ingress interface, note the following information:

To enable egress ACL support for remarked DSCP only for the traffic filtered by a specific standard, extended named, or extended numbered IP ACL, enter the IP ACL name or number. If you do not enter an IP ACL name or number, egress ACL support for remarked DSCP is enabled for all IP ingress IP traffic on the interface.
This example shows how to enable egress ACL support for remarked DSCP on Fast Ethernet port 5/36:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/36 Router(config-if)# platform ip features sequential Router(config-if)# end
41-62
OL-3999-08
Chapter 41
Creating Named Aggregate Policers

To create a named aggregate policer, perform this task: Command
Router(config)# mls qos aggregate-policer policer_name bits_per_second normal_burst_bytes [maximum_burst_bytes] [pir peak_rate_bps] [[[conform-action {drop | set-dscp-transmit1 dscp_value | set-prec-transmit1 ip_precedence_value | transmit}] exceed-action {drop | policed-dscp | transmit}] violate-action {drop | policed-dscp | transmit}] Router(config)# no mls qos aggregate-policer policer_name
Purpose Creates a named aggregate policer.
Deletes a named aggregate policer.
1. The set-dscp-transmit and set-prec-transmit keywords are only supported for IP traffic.
When creating a named aggregate policer, note the following information:
Aggregate policing works independently on each DFC-equipped switching module and independently on the PFC, which supports any non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from different DFC-equipped switching modules. You can display aggregate policing statistics for each DFC-equipped switching module and for the PFC and any non-DFC-equipped switching modules supported by the PFC. Each PFC or DFC polices independently, which might affect QoS features being applied to traffic that is distributed across the PFC and any DFCs. Examples of these QoS feature are:

In Release 12.2(18)SXE and later releases, you can apply aggregate policers to IPv6 traffic. With a PFC3, policing uses the Layer 2 frame size. With a PFC2, policing uses the Layer 3 packet size. See the PFC QoS Configuration Guidelines and Restrictions section on page 41-50 for information about rate and burst size granularity. The valid range of values for the CIR bits_per_second parameter is as follows:
Minimum32 kilobits per second, entered as 32000 Maximum with Release 12.2(18)SXE and later releases:
10 gigabits per second, entered as 10000000000

Maximum with releases earlier than Release 12.2(18)SXE:

The normal_burst_bytes parameter sets the CIR token bucket size. The maximum_burst_bytes parameter sets the PIR token bucket size. When configuring the size of a token bucket, note the following information:
41-63
Configuring PFC QoS
The minimum token bucket size is 1 kilobyte, entered as 1000 (the maximum_burst_bytes
parameter must be set larger than the normal_burst_bytes parameter).

The maximum token bucket size is 512 megabytes, entered as 512000000. To sustain a specific rate, set the token bucket size to be at least the rate value divided by 4000
because tokens are removed from the bucket every 1/4000th of a second (0.25 ms).
Because the token bucket must be large enough to hold at least one frame, set the parameter
larger than the maximum size of the traffic being policed.

For TCP traffic, configure the token bucket size as a multiple of the TCP window size, with a
minimum value at least twice as large as the maximum size of the traffic being policed.
The valid range of values for the pir bits_per_second parameter is as follows:
Minimum32 kilobits per second, entered as 32000 (the value cannot be smaller than the
CIR bits_per_second parameters)

Maximum with Release 12.2(18)SXE and later releases:

(Optional) You can specify a conform action for matched in-profile traffic as follows:
The default conform action is transmit , which sets the policy map class trust state to trust
DSCP unless the policy map class contains a trust command.

To set PFC QoS labels in untrusted traffic, enter the set-dscp-transmit keyword to mark
matched untrusted traffic with a new DSCP value or enter the set-prec-transmit keyword to mark matched untrusted traffic with a new IP precedence value. The set-dscp-transmit and set-prec-transmit keywords are only supported for IP traffic. PFC QoS sets egress ToS and CoS from the configured value.
Enter the drop keyword to drop all matched traffic.
Note
When you configure drop as the conform action, PFC QoS configures drop as the exceed action and the violate action.
(Optional) For traffic that exceeds the CIR, you can specify an exceed action as follows:
The default exceed action is drop, except with a maximum_burst_bytes parameter (drop is not
supported with a maximum_burst_bytes parameter).
Note
When the exceed action is drop , PFC QoS ignores any configured violate action.
Enter the policed-dscp-transmit keyword to cause all matched out-of-profile traffic to be
marked down as specified in the markdown map.
Note
When you create a policer that does not use the pir keyword and the maximum_burst_bytes parameter is equal to the normal_burst_bytes parameter (which is the case if you do not enter the maximum_burst_bytes parameter), the exceed-action policed-dscp-transmit keywords cause PFC QoS to mark traffic down as defined by the policed-dscp max-burst markdown map.
41-64
OL-3999-08
Chapter 41
(Optional) For traffic that exceeds the PIR, you can specify a violate action as follows:
To mark traffic without policing, enter the transmit keyword to transmit all matched
out-of-profile traffic.
The default violate action is equal to the exceed action. Enter the policed-dscp-transmit keyword to cause all matched out-of-profile traffic to be
marked down as specified in the markdown map.

For marking without policing, enter the transmit keyword to transmit all matched out-of-profile
traffic.
Note
When you apply both ingress policing and egress policing to the same traffic, both the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does not support ingress markdown with egress drop or ingress drop with egress markdown. This example shows how to create a named aggregate policer with a 1-Mbps rate limit and a 10-MB burst size that transmits conforming traffic and marks down out-of-profile traffic:
Router(config)# mls qos aggregate-policer aggr-1 1000000 10000000 conform-action transmit exceed-action policed-dscp-transmit Router(config)# end Router#

Router# show mls qos aggregate-policer aggr-1 ag1 1000000 1000000 conform-action transmit exceed-action policed-dscp-transmit AgId=0 [pol4] Router#
The output displays the following:

The AgId parameter displays the hardware policer ID. The policy maps that use the policer are listed in the square brackets ([]).
Configuring a PFC QoS Policy

These sections describe PFC QoS policy configuration:

PFC QoS Policy Configuration Overview, page 41-66 Configuring MAC ACLs, page 41-67 Configuring ARP ACLs for QoS Filtering, page 41-70 Configuring a Class Map, page 41-71 Verifying Class Map Configuration, page 41-74 Configuring a Policy Map, page 41-74 Verifying Policy Map Configuration, page 41-81 Attaching a Policy Map to an Interface, page 41-81
Note
PFC QoS policies process both unicast and multicast traffic.
41-65
Configuring PFC QoS
PFC QoS Policy Configuration Overview

Note
To mark traffic without limiting bandwidth utilization, create a policer that uses the transmit keywords for both conforming and nonconforming traffic. These commands configure traffic classes and the policies to be applied to those traffic classes and attach the policies to ports:
access-list (Optional for IP traffic. You can filter IP traffic with class-map commands.):
PFC QoS supports these ACL types:
Protocol IPv4
Numbered ACLs Yes: 1 to 99 1300 to 1999 Yes: 800 to 899 No No
Extended ACLs Yes: 100 to 199 2000 to 2699 Yes (named) Yes: 900 to 999 No No
Named ACLs Yes
IPv6 IPX (Supported only with PFC2) MAC Layer ARP
Yes Yes Yes Yes
The PFC3 supports IPv6 named extended ACLs and named standard ACLs in Release
12.2(18)SXE and later releases.

The PFC3 supports ARP ACLs in Release 12.2(18)SXD and later releases.
Note
The PFC2 applies IP ACLs to ARP traffic. The PFC3 does not apply IP ACLs to ARP traffic.

With a PFC3, you cannot apply microflow policing to ARP traffic.

The PFC3 does not support IPX ACLs. With the PFC3, you can configure MAC ACLs to filter
IPX traffic.
With a PFC2, PFC QoS supports IPX ACLs that contain a source-network parameter and the
optional destination-network and destination-node parameters. PFC QoS does not support IPX ACLs that contain other parameters (for example, source-node, protocol, source-socket, destination-socket, or service-type).
With a PFC2 or PFC3, PFC QoS supports time-based Cisco IOS ACLs. Except for MAC ACLs and ARP ACLs, refer to the Cisco IOS Security Configuration Guide ,
Release 12.2, Traffic Filtering and Firewalls, at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/scfacls.html

See Chapter 33, Configuring Network Security, for additional information about ACLs on the
Catalyst 6500 series switches.
class-map (optional)Enter the class-map command to define one or more traffic classes by specifying the criteria by which traffic is classified.
41-66
OL-3999-08
Chapter 41
policy-map Enter the policy-map command to define the following:

Policy map class trust mode Aggregate policing and marking Microflow policing and marking
service-policyEnter the service-policy command to attach a policy map to an interface.
Configuring MAC ACLs

These sections describe MAC ACL configuration:

Configuring Protocol-Independent MAC ACL Filtering, page 41-67 Enabling VLAN-Based MAC QoS Filtering, page 41-68 Configuring MAC ACLs, page 41-69
Note
You can use MAC ACLs with VLAN ACLs (VACLs). For more information, see Chapter 35, Configuring VLAN ACLs.
Configuring Protocol-Independent MAC ACL Filtering

With Release 12.2(18)SXD and later releases, PFC3BXL and PFC3B modes support protocol-independent MAC ACL filtering. Protocol-independent MAC ACL filtering applies MAC ACLs to all ingress traffic types (for example, IPv4 traffic, IPv6 traffic, and MPLS traffic, in addition to MAC-layer traffic). You can configure these interface types for protocol-independent MAC ACL filtering:

VLAN interfaces without IP addresses Physical LAN ports configured to support EoMPLS Logical LAN subinterfaces configured to support EoMPLS
Ingress traffic permitted or denied by a MAC ACL on an interface configured for protocol-independent MAC ACL filtering is processed by egress interfaces as MAC-layer traffic. You cannot apply egress IP ACLs to traffic that was permitted or denied by a MAC ACL on an interface configured for protocol-independent MAC ACL filtering. To configure protocol-independent MAC ACL filtering, perform this task: Command
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port[.subinterface]} | {port-channel number[.subinterface]}} Router(config-if)# mac packet-classify
Step 2
Enables protocol-independent MAC ACL filtering on the interface. Disables protocol-independent MAC ACL filtering on the interface.
Router(config-if)# no mac packet-classify
1.
41-67
Configuring PFC QoS
When configuring protocol-independent MAC ACL filtering, note the following information:

Do not configure protocol-independent MAC ACL filtering on VLAN interfaces where you have configured an IP address. Do not configure protocol-independent MAC ACL filtering with microflow policing when the permitted traffic would be bridged or Layer 3 switched in hardware by the PFC3BXL. Protocol-independent MAC ACL filtering supports microflow policing when the permitted traffic is routed in software by the MSFC3.
This example shows how to configure VLAN interface 4018 for protocol-independent MAC ACL filtering and how to verify the configuration:
Router(config)# interface vlan 4018 Router(config-if)# mac packet-classify Router(config-if)# end Router# show running-config interface vlan 4018 | begin 4018 interface Vlan4018 mtu 9216 ipv6 enable mac packet-classify end
This example shows how to configure Gigabit Ethernet interface 6/1 for protocol-independent MAC ACL filtering and how to verify the configuration:
Router(config)# interface gigabitethernet 6/1 Router(config-if)# mac packet-classify Router(config-if)# end Router# show running-config interface gigabitethernet 6/1 | begin 6/1 interface GigabitEthernet6/1 mtu 9216 no ip address mac packet-classify mpls l2transport route 4.4.4.4 4094 end
This example shows how to configure Gigabit Ethernet interface 3/24, subinterface 4000, for protocol-independent MAC ACL filtering and how to verify the configuration:
Router(config)# interface gigabitethernet 3/24.4000 Router(config-if)# mac packet-classify Router(config-if)# end Router# show running-config interface gigabitethernet 3/24.4000 | begin 3/24.4000 interface GigabitEthernet3/24.4000 encapsulation dot1Q 4000 mac packet-classify mpls l2transport route 4.4.4.4 4000 end
Enabling VLAN-Based MAC QoS Filtering

In Release 12.2(18)SXD and later releases in PFC3BXL or PFC3B mode, you can globally enable or disable VLAN-based QoS filtering in MAC ACLs. VLAN-based QoS filtering in MAC ACLs is disabled by default. To enable VLAN-based QoS filtering in MAC ACLs, perform this task: Command
Router(config)# mac packet-classify use vlan
Purpose Enables VLAN-based QoS filtering in MAC ACLs.
41-68
OL-3999-08
Chapter 41
To disable VLAN-based QoS filtering in MAC ACLs, perform this task: Command
Router(config)# no mac packet-classify use vlan
Purpose Disables VLAN-based QoS filtering in MAC ACLs.
Configuring MAC ACLs

You can configure named ACLs that filter IPX, DECnet, AppleTalk, VINES, or XNS traffic based on MAC addresses (IPX filtering with a MAC ACL is supported only with a PFC3). In Release 12.2(17b)SXA and later releases in PFC3BXL or PFC3B mode, you can configure MAC ACLs that do VLAN-based filtering or CoS-based filtering or both. In Release 12.2(18)SXD and later releases, you can globally enable or disable VLAN-based QoS filtering in MAC ACLs (disabled by default). To configure a MAC ACL, perform this task: Command
Step 1
Router(config)# mac access-list extended list_name Router(config)# no mac access-list extended list_name
Purpose Configures a MAC ACL. Deletes a MAC ACL. Configures an access control entry (ACE) in a MAC ACL.
Step 2
Router(config-ext-macl)# {permit | deny} {src_mac_mask | any} {dest_mac_mask | any} [{protocol_keyword | {ethertype_number ethertype_mask}} [vlan vlan_ID] [cos cos_value]] Router(config-ext-macl)# no {permit | deny} {src_mac_mask | any} {dest_mac_mask | any} [{protocol_keyword | {ethertype_number ethertype_mask}} [vlan vlan_ID] [cos cos_value]]
Deletes an ACE from a MAC ACL.
When configuring an entry in a MAC-Layer ACL, note the following information:

The PFC3 supports the ipx-arpa and ipx-non-arpa keywords. The PFC2 does not support the ipx-arpa and ipx-non-arpa keywords. The vlan and cos keywords are supported in PFC3BXL or PFC3B mode with Release 12.2(17b)SXA and later releases. The vlan and cos keywords are not supported in MAC ACLs used for VACL filtering. With Release 12.2(18)SXD and later releases, the vlan keyword for VLAN-based QoS filtering in MAC ACLs can be globally enabled or disabled and is disabled by default. You can enter MAC addresses as three 2-byte values in dotted hexadecimal format. For example, 0030.9629.9f84. You can enter MAC address masks as three 2-byte values in dotted hexadecimal format. Use 1 bits as wildcards. For example, to match an address exactly, use 0000.0000.0000 (can be entered as 0.0.0). You can enter an EtherType and an EtherType mask as hexadecimal values. Entries without a protocol parameter match any protocol.
41-69
Configuring PFC QoS
ACL entries are scanned in the order you enter them. The first matching entry is used. To improve performance, place the most commonly used entries near the beginning of the ACL. An implicit deny any any entry exists at the end of an ACL unless you include an explicit permit any any entry at the end of the list. All new entries to an existing list are placed at the end of the list. You cannot add entries to the middle of a list. This list shows the EtherType values and their corresponding protocol keywords:
0x0600xns-idpXerox XNS IDP 0x0BADvines-ipBanyan VINES IP 0x0bafvines-echoBanyan VINES Echo 0x6000etype-6000DEC unassigned, experimental 0x6001mop-dumpDEC Maintenance Operation Protocol (MOP) Dump/Load Assistance 0x6002mop-consoleDEC MOP Remote Console 0x6003decnet-ivDEC DECnet Phase IV Route 0x6004latDEC Local Area Transport (LAT) 0x6005diagnosticDEC DECnet Diagnostics 0x6007lavc-scaDEC Local-Area VAX Cluster (LAVC), SCA 0x6008amberDEC AMBER 0x6009mumpsDEC MUMPS 0x0800ipMalformed, invalid, or deliberately corrupt IP frames 0x8038dec-spanningDEC LANBridge Management 0x8039dsmDEC DSM/DDP 0x8040netbiosDEC PATHWORKS DECnet NETBIOS Emulation 0x8041msdosDEC Local Area System Transport 0x8042etype-8042DEC unassigned 0x809BappletalkKinetics EtherTalk (AppleTalk over Ethernet) 0x80F3aarpKinetics AppleTalk Address Resolution Protocol (AARP)
This example shows how to create a MAC-Layer ACL named mac_layer that denies dec-phase-iv traffic with source address 0000.4700.0001 and destination address 0000.4700.0009, but permits all other traffic:
Router(config)# mac access-list extended mac_layer Router(config-ext-macl)# deny 0000.4700.0001 0.0.0 0000.4700.0009 0.0.0 dec-phase-iv Router(config-ext-macl)# permit any any
Configuring ARP ACLs for QoS Filtering

Note
The PFC2 applies IP ACLs to ARP traffic. The PFC3 does not apply IP ACLs to ARP traffic. With a PFC3, you cannot apply microflow policing to ARP traffic.
41-70
OL-3999-08
Chapter 41
With a PFC3 and Release 12.2(18)SXD and later releases, you can configure named ACLs that filter ARP traffic (EtherType 0x0806) for QoS. To configure an ARP ACL for QoS filtering, perform this task: Command
Step 1
Router(config)# arp access-list list_name Router(config)# no arp access-list list_name
Purpose Configures an ARP ACL for QoS filtering. Deletes an ARP ACL. Configures an access control entry (ACE) in an ARP ACL for QoS filtering. Deletes an ACE from an ARP ACL.
Step 2
Router(config-arp-nacl)# {permit | deny} {ip {any | host sender_ip | sender_ip sender_ip_wildcardmask} mac any Router(config-arp-nacl)# no {permit | deny} {ip {any | host sender_ip | sender_ip sender_ip_wildcardmask} mac any
When configuring an entry in an ARP ACL for QoS filtering, note the following information:
This publication describes the ARP ACL syntax that is supported in hardware by the PFC3. Any other ARP ACL syntax displayed by the CLI help when you enter a question mark (?) is not supported and cannot be used to filter ARP traffic for QoS. ACLs entries are scanned in the order you enter them. The first matching entry is used. To improve performance, place the most commonly used entries near the beginning of the ACL. An implicit deny ip any mac any entry exists at the end of an ACL unless you include an explicit permit ip any mac any entry at the end of the list. All new entries to an existing list are placed at the end of the list. You cannot add entries to the middle of a list.
This example shows how to create an ARP ACL named arp_filtering that only permits ARP traffic from IP address 1.1.1.1:
Router(config)# arp access-list arp_filtering Router(config-arp-nacl)# permit ip host 1.1.1.1 mac any
Configuring a Class Map

These sections describe class map configuration:

Creating a Class Map, page 41-71 Class Map Filtering Guidelines and Restrictions, page 41-72 Configuring Filtering in a Class Map, page 41-73
Creating a Class Map

To create a class map, perform this task: Command
Router(config)# class-map class_name Router(config)# no class-map class_name
Purpose Creates a class map. Deletes a class map.
41-71
Configuring PFC QoS
Class Map Filtering Guidelines and Restrictions

When configuring class map filtering, follow these guidelines and restrictions:

With Release 12.2(18)SXE and later releases, PFC QoS supports multiple match criteria in class maps configured with the match-any keywords. When multiple match access-group ACLs are included in a match-any class map, and one ACL contains a deny entry, all match criteria after the deny entry (either in the same ACL or in different ACLs) will not be installed in the TCAM. In the following example, ACLs acl4 and acl5 will not be installed because they follow acl3, which contains a deny ip any any entry:
ip access-list ext acl3 deny ip any any class-map cmap1 match access-group match access-group match access-group match access-group match access-group
acl1 acl2 acl3 acl4 acl5
You can use either of the following workarounds to avoid this issue:
Move the deny entry to the end of the ACL and move that ACL to the end of the class map. Configure all ACLs that must follow the deny entry into different class maps.
With releases earlier than Release 12.2(18)SXE, PFC QoS supports class maps that contain a single match command. With Release 12.2(18)SXE and later releases, the PFC3 supports the match protocol ipv6 command. Because of conflicting TCAM lookup flow key bit requirements, you cannot configure IPv6 DSCP-based filtering and IPv6 Layer 4 range-based filtering on the same interface. For example:
If configure both a DSCP value and a Layer 4 greater than (gt) or less than (lt) operator in an
IPv6 ACE, you cannot use the ACL for PFC QoS filtering.
If configure a DSCP value in one IPv6 ACL and a Layer 4 greater than (gt) or less than (lt)
operator in another IPv6 ACL, you cannot use both ACLs in different class maps on the same interface for PFC QoS filtering.
The IPv6 address matching against Layer 4 ports is ignored if the IPv6 address in the ACE is not compressible. The IPv6 source and destination addresses are matched, but the configured source or destination UDP or TCP ports will be ignored. To force Layer 4 port matching, use the mls ipv6 acl compress address unicast command. Release 12.2(18)SXE and later releases support the match protocol ip command for IPv4 traffic. Release 12.2(18)SXE and later releases support the match any class map command. PFC QoS does not support the match cos, match classmap, match destination-address, match input-interface, match qos-group, and match source-address class map commands. Catalyst 6500 series switches do not detect the use of unsupported commands until you attach a policy map to an interface.
41-72
OL-3999-08
Chapter 41
The PFC2 support the match protocol class map command, which configures NBAR and sends all traffic on the Layer 3 interface, both ingress and egress, to be processed in software on the MSFC2. To configure NBAR, refer to this publication: http://www.cisco.com/en/US/docs/ios/12_4t/qos/configuration/guide/qsnbar1.html
Filtering based on IP precedence or DSCP for egress QoS uses the received IP precedence or DSCP. Egress QoS filtering is not based on any IP precedence or DSCP changes made by ingress QoS.
Note
This chapter includes the following ACL documentation:

Configuring MAC ACLs, page 41-67 Configuring ARP ACLs for QoS Filtering, page 41-70
Other ACLs are not documented in this publication. See the references under access-list in the PFC QoS Policy Configuration Overview section on page 41-66.
Configuring Filtering in a Class Map

To configure filtering in a class map, perform one of these tasks: Command
Router(config-cmap)# match access-group name acl_index_or_name Router(config-cmap)# no match access-group name acl_index_or_name Router (config-cmap)# match protocol ipv6
Purpose (Optional) Configures the class map to filter using an ACL. Clears the ACL configuration from the class map. (Optionalfor IPv6 traffic) Configures the class map to filter IPv6 traffic. Clears IPv6 filtering. (Optionalfor IPv4 or IPv6 traffic) Configures the class map to filter based on up to eight IP precedence values.
Note
Router (config-cmap)# no match protocol ipv6 Router (config-cmap)# match precedence ipp_value1 [ipp_value2 [ipp_valueN]]
Does not support source-based or destination-based microflow policing.
Router (config-cmap)# no match precedence ipp_value1 [ipp_value2 [ipp_valueN]] Router (config-cmap)# match dscp dscp_value1 [dscp_value2 [dscp_valueN]]
Clears configured IP precedence values from the class map. (Optionalfor IPv4 or IPv6 traffic only) Configures the class map to filter based on up to eight DSCP values.
Note
Router (config-cmap)# no match dscp dscp_value1 [dscp_value2 [dscp_valueN]] Router (config-cmap)# match ip precedence ipp_value1 [ipp_value2 [ipp_valueN]]
Clears configured DSCP values from the class map. (Optionalfor IPv4 traffic) Configures the class map to filter based on up to eight IP precedence values.
Note
Router (config-cmap)# no match ip precedence ipp_value1 [ipp_value2 [ipp_valueN]]
Clears configured IP precedence values from the class map.
41-73
Configuring PFC QoS
Command
Router (config-cmap)# match ip dscp dscp_value1 [dscp_value2 [dscp_valueN]]
Purpose (Optionalfor IPv4 traffic) Configures the class map to filter based on up to eight DSCP values.
Note
Router (config-cmap)# no match ip dscp dscp_value1 [dscp_value2 [dscp_valueN]]
Clears configured DSCP values from the class map.
Verifying Class Map Configuration

To verify class map configuration, perform this task: Command
Step 1 Step 2
Router (config-cmap)# end Router# show class-map class_name
This example shows how to create a class map named ipp5 and how to configure filtering to match traffic with IP precedence 5:
Router# configure terminal Enter configuration commands, one per line. Router(config)# class-map ipp5 Router(config-cmap)# match ip precedence 5 Router(config-cmap)# end End with CNTL/Z.

Router# show class-map ipp5 Class Map match-all ipp5 (id 1) Match ip precedence 5
Configuring a Policy Map

You can attach only one policy map to an interface. Policy maps can contain one or more policy map classes, each with different policy map commands. Configure a separate policy map class in the policy map for each type of traffic that an interface receives. Put all commands for each type of traffic in the same policy map class. PFC QoS does not attempt to apply commands from more than one policy map class to matched traffic. These sections describe policy map configuration:

Creating a Policy Map, page 41-75 Policy Map Class Configuration Guidelines and Restrictions, page 41-75 Creating a Policy Map Class and Configuring Filtering, page 41-75 Configuring Policy Map Class Actions, page 41-75
41-74
OL-3999-08
Chapter 41
Creating a Policy Map

To create a policy map, perform this task: Command
Router(config)# policy-map policy_name Router(config)# no policy-map policy_name
Purpose Creates a policy map. Deletes the policy map.
Policy Map Class Configuration Guidelines and Restrictions

When you configuring policy map classes, follow the guidelines and restrictions:
The PFC2 support the class class_name protocol policy map command, which configures NBAR and sends all traffic on the Layer 3 interface, both ingress and egress, to be processed in software on the MSFC2. To configure NBAR, refer to this publication: http://www.cisco.com/en/US/docs/ios/12_4t/qos/configuration/guide/qsnbar1.html PFC QoS does not support the class class_name destination-address, class class_name input-interface, class class_name qos-group, and class class_name source-address policy map commands. With Release 12.2(18)SXE and later releases, PFC QoS supports the class default policy map command. PFC QoS does not detect the use of unsupported commands until you attach a policy map to an interface.
Creating a Policy Map Class and Configuring Filtering

To create a policy map class and configure it to filter with a class map, perform this task: Command
Router(config-pmap)# class class_name
Purpose Creates a policy map class and configures it to filter with a class map.
Note
PFC QoS supports class maps that contain a single match command.
Router(config-pmap)# no class class_name
Clears use of the class map.
Configuring Policy Map Class Actions

When configuring policy map class actions, note the following information:

Policy maps can contain one or more policy map classes. Put all trust-state and policing commands for each type of traffic in the same policy map class. PFC QoS only applies commands from one policy map class to traffic. After traffic has matched the filtering in one policy map class, QoS does apply the filtering configured in other policy map classes. For hardware-switched traffic, PFC QoS does not support the bandwidth, priority, queue-limit, or random-detect policy map class commands. You can configure these commands because they can be used for software-switched traffic.
41-75
Configuring PFC QoS
PFC QoS does not support the set qos-group policy map class commands. PFC QoS supports the set ip dscp and set ip precedence policy map class commands for IPv4 traffic.
In Release 12.2(18)SXD and later releases and in Release 12.2(17d)SXB and later releases, you
can use the set ip dscp and set ip precedence commands on non-IP traffic to mark the internal DSCP value, which is the basis of the egress Layer 2 CoS value.
In Release 12.2(18)SXE and later releases, the set ip dscp and set ip precedence commands
are saved in the configuration file as set dscp and set precedence commands.

In Release 12.2(18)SXE and later releases, PFC QoS supports the set dscp and set precedence policy map class commands for IPv4 and IPv6 traffic. You cannot do all three of the following in a policy map class:
Mark traffic with the set commands Configure the trust state Configure policing
In a policy map class, you can either mark traffic with the set commands or do one or both of the following:
Configure the trust state Configure policing
Note
When configure policing, you can mark traffic with policing keywords.
These sections describe policy map class action configuration:

Configuring Policy Map Class Marking, page 41-76 Configuring the Policy Map Class Trust State, page 41-77 Configuring Policy Map Class Policing, page 41-77
Configuring Policy Map Class Marking
In Release 12.2(18)SXF5 and later releases, when the ignore port trust feature is enabled, PFC QoS supports policy map class marking for all traffic with set policy map class commands. In all releases, PFC QoS supports policy map class marking for untrusted traffic with set policy map class commands. To configure policy map class marking, perform this task: Command
Router(config-pmap-c)# set {dscp dscp_value | precedence ip_precedence_value} Router(config-pmap-c)# no set {dscp dscp_value | precedence ip_precedence_value}
Purpose Configures the policy map class to mark matched untrusted traffic with the configured DSCP or IP precedence value. Clears the marking configuration.
Note
Releases earlier than Release 12.2(18)SXE support the set ip dscp and set ip precedence policy map class commands.
41-76
OL-3999-08
Chapter 41
Configuring the Policy Map Class Trust State
Note
You cannot attach a policy map that configures a trust state with the service-policy output command. To configure the policy map class trust state, perform this task:
Command
Router(config-pmap-c)# trust {cos | dscp | ip-precedence}
Purpose Configures the policy map class trust state, which selects the value that PFC QoS uses as the source of the initial internal DSCP value. Reverts to the default policy-map class trust state (untrusted).
Router(config-pmap-c)# no trust
When configuring the policy map class trust state, note the following information:

Enter the no trust command to use the trust state configured on the ingress port (this is the default). With the cos keyword, PFC QoS sets the internal DSCP value from received or ingress port CoS. With the dscp keyword, PFC QoS uses received DSCP. With the ip-precedence keyword, PFC QoS sets DSCP from received IP precedence.
Configuring Policy Map Class Policing
When you configure policy map class policing, note the following information:

PFC QoS does not support the set-qos-transmit policer keyword. PFC QoS does not support the set-dscp-transmit or set-prec-transmit keywords as arguments to the exceed-action keyword. PFC QoS does not detect the use of unsupported keywords until you attach a policy map to an interface.
These sections describe configuration of policy map class policing:

Using a Named Aggregate Policer, page 41-77 Configuring a Per-Interface Policer, page 41-78
Note
Policing with the conform-action transmit keywords sets the port trust state of matched traffic to trust DSCP or to the trust state configured by a trust command in the policy map class.
Using a Named Aggregate Policer
To use a named aggregate policer, perform this task: Command

Router(config-pmap-c)# police aggregate aggregate_name Router(config-pmap-c)# no police aggregate aggregate_name
Purpose Configures the policy map class to use a previously defined named aggregate policer. Clears use of the named aggregate policer.
41-77
Configuring PFC QoS
Configuring a Per-Interface Policer
To configure a per-interface policer, perform this task: Command

Router(config-pmap-c)# police [flow [mask {src-only | dest-only | full-flow}]] bits_per_second normal_burst_bytes [maximum_burst_bytes] [pir peak_rate_bps] [[[conform-action {drop | set-dscp-transmit dscp_value | set-prec-transmit ip_precedence_value | transmit}] exceed-action {drop | policed-dscp | transmit}] violate-action {drop | policed-dscp | transmit}] Router(config-pmap-c)# no police [flow [mask {src-only | dest-only | full-flow}]] bits_per_second normal_burst_bytes [maximum_burst_bytes] [pir peak_rate_bps] [[[conform-action {drop | set-dscp-transmit dscp_value | set-prec-transmit ip_precedence_value | transmit}] exceed-action {drop | policed-dscp | transmit}] violate-action {drop | policed-dscp | transmit}]
Purpose Creates a per-interface policer and configures the policy-map class to use it.
Deletes the per-interface policer from the policy-map class.
When configuring a per-interface policer, note the following information:
Aggregate policing works independently on each DFC-equipped switching module and independently on the PFC, which supports any non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from different DFC-equipped switching modules. You can display aggregate policing statistics for each DFC-equipped switching module and for the PFC and any non-DFC-equipped switching modules supported by the PFC. Each PFC or DFC polices independently, which might affect QoS features being applied to traffic that is distributed across the PFC and any DFCs. Examples of these QoS feature are:
With a PFC3, when you apply both ingress policing and egress policing to the same traffic, both the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does not support ingress markdown with egress drop or ingress drop with egress markdown. With Release 12.2(18)SXE and later releases, you can apply aggregate and microflow policers to IPv6 traffic. With a PFC3, policing uses the Layer 2 frame size. With a PFC2, policing uses the Layer 3 packet size. See the PFC QoS Configuration Guidelines and Restrictions section on page 41-50 for information about rate and burst size granularity. You can enter the flow keyword to define a microflow policer (you cannot apply microflow policing to ARP traffic). When configuring a microflow policer, note the following information:
41-78
OL-3999-08
Chapter 41
With a PFC3, you can enter the mask src-only keywords to base flow identification only on
source addresses, which applies the microflow policer to all traffic from each source address. Release 12.2(17d)SXB and later releases support the mask src-only keywords for both IP traffic and MAC traffic. Releases earlier than Release 12.2(17d)SXB support the mask src-only keywords only for IP traffic.
With a PFC3, you can enter the mask dest-only keywords to base flow identification only on
destination addresses, which applies the microflow policer to all traffic to each source address. Release 12.2(17d)SXB and later releases support the mask dest-only keywords for both IP traffic and MAC traffic. Releases earlier than Release 12.2(17d)SXB support the mask dest-only keywords only for IP traffic.
By default and with the mask full-flow keywords, PFC QoS bases IP flow identification on
source IP address, destination IP address, the Layer 3 protocol, and Layer 4 port numbers.
With a PFC2, PFC QoS considers IPX traffic with same source network, destination network,
and destination node to be part of the same flow, including traffic with different source nodes or sockets.
PFC QoS considers MAC-Layer traffic with the same protocol and the same source and
destination MAC-Layer addresses to be part of the same flow, including traffic with different EtherTypes.
Microflow policers do not support the maximum_burst_bytes parameter, the
pir bits_per_second keyword and parameter, or the violate-action keyword.
Note
The flowmask requirements of microflow policing, NetFlow, and NetFlow data export (NDE) might conflict.
The valid range of values for the CIR bits_per_second parameter is as follows:
Minimum32 kilobits per second, entered as 32000 Maximum with Release 12.2(18)SXE and later releases:


The normal_burst_bytes parameter sets the CIR token bucket size. The maximum_burst_bytes parameter sets the PIR token bucket size (not supported with the flow keyword) When configuring the size of a token bucket, note the following information:
The minimum token bucket size is 1 kilobyte, entered as 1000 (the maximum_burst_bytes
parameter must be set larger than the normal_burst_bytes parameter)

The maximum token bucket size is 512 megabytes, entered as 512000000 To sustain a specific rate, set the token bucket size to be at least the rate value divided by 4000,
because tokens are removed from the bucket every 1/4000th of a second (0.25 ms).
Because the token bucket must be large enough to hold at least one frame, set the parameter
larger than the maximum size of the traffic being policed.

For TCP traffic, configure the token bucket size as a multiple of the TCP window size, with a
minimum value at least twice as large as the maximum size of the traffic being policed.
41-79
Configuring PFC QoS
(Not supported with the flow keyword.) The valid range of values for the pir bits_per_second parameter is as follows:
Minimum32 kilobits per second, entered as 32000 (the value cannot be smaller than the CIR
bits_per_second parameters)
Maximum with Release 12.2(18)SXE and later releases:

(Optional) You can specify a conform action for matched in-profile traffic as follows:
The default conform action is transmit , which sets the policy map class trust state to trust
DSCP unless the policy map class contains a trust command.

To set PFC QoS labels in untrusted traffic, you can enter the set-dscp-transmit keyword to
mark matched untrusted traffic with a new DSCP value or enter the set-prec-transmit keyword to mark matched untrusted traffic with a new IP precedence value. The set-dscp-transmit and set-prec-transmit keywords are only supported for IP traffic. PFC QoS sets egress ToS and CoS from the configured value.
You can enter the drop keyword to drop all matched traffic. Ensure that aggregate and microflow policers that are applied to the same traffic each specify
the same conform-action behavior.
(Optional) For traffic that exceeds the CIR, you can specify an exceed action as follows:
For marking without policing, you can enter the transmit keyword to transmit all matched
The default exceed action is drop, except with a maximum_burst_bytes parameter (drop is not
supported with a maximum_burst_bytes parameter).
Note
When the exceed action is drop , PFC QoS ignores any configured violate action.
You can enter the policed-dscp-transmit keyword to cause all matched out-of-profile traffic to
be marked down as specified in the markdown map.
Note
When you create a policer that does not use the pir keyword and the maximum_burst_bytes parameter is equal to the normal_burst_bytes parameter (which is the case if you do not enter the maximum_burst_bytes parameter), the exceed-action policed-dscp-transmit keywords cause PFC QoS to mark traffic down as defined by the policed-dscp max-burst markdown map.
(OptionalNot supported with the flow keyword) for traffic that exceeds the PIR, you can specify a violate action as follows:
For marking without policing, you can enter the transmit keyword to transmit all matched
The default violate action is equal to the exceed action. You can enter the policed-dscp-transmit keyword to cause all matched out-of-profile traffic to
be marked down as specified in the markdown map.
41-80
OL-3999-08
Chapter 41
This example shows how to create a policy map named max-pol-ipp5 that uses the class-map named ipp5, which is configured to trust received IP precedence values and is configured with a maximum-capacity aggregate policer and with a microflow policer:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# policy-map max-pol-ipp5 Router(config-pmap)# class ipp5 Router(config-pmap-c)# trust ip-precedence Router(config-pmap-c)# police 2000000000 2000000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmit Router(config-pmap-c)# police flow 10000000 10000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmit Router(config-pmap-c)# end
Verifying Policy Map Configuration

To verify policy map configuration, perform this task: Command
Step 1
Router(config-pmap-c)# end
Purpose Exits policy map class configuration mode.

Note
Enter additional class commands to create additional classes in the policy map.
Step 2
Router# show policy-map policy_name

Router# show policy-map max-pol-ipp5 Policy Map max-pol-ipp5 class ipp5 class ipp5 police flow 10000000 10000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmit trust precedence police 2000000000 2000000 2000000 conform-action set-prec-transmit 6 exceed-action policed-dscp-transmit Router#
Attaching a Policy Map to an Interface

To attach a policy map to an interface, perform this task: Command
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port[.subinterface]} | {port-channel number[.subinterface]}} Router(config-if)# service-policy [input | output] policy_map_name Router(config-if)# no service-policy [input | output] policy_map_name
Step 2
Attaches a policy map to the interface. Removes the policy map from the interface.
41-81
Configuring PFC QoS
Command
Step 3 Step 4
Router(config-if)# end Router# show policy-map interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} 1.
When attaching a policy map to an interface, note the following information:

Do not attach a service policy to a port that is a member of an EtherChannel. With DFCs installed, PFC2 does not support VLAN-based QoS: you cannot enter the mls qos vlan-based command or attach service policies to VLAN interfaces. PFC QoS supports the output keyword only with a PFC3 and only on Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces). With a PFC3, you can attach both an input and an output policy map to a Layer 3 interface. VLAN-based or port-based PFC QoS on Layer 2 ports is not relevant to policies attached to Layer 3 interfaces with the output keyword. Policies attached with the output keyword do not support microflow policing. You cannot attach a policy map that configures a trust state with the service-policy output command. Filtering based on IP precedence or DSCP in policies attached with the output keyword uses the received IP precedence or DSCP values. Filtering based on IP precedence or DSCP in policies attached with the output keyword is not based on any IP precedence or DSCP changes made by ingress QoS. Aggregate policing works independently on each DFC-equipped switching module and independently on the PFC, which supports any non-DFC-equipped switching modules. Aggregate policing does not combine flow statistics from different DFC-equipped switching modules. You can display aggregate policing statistics for each DFC-equipped switching module and for the PFC and any non-DFC-equipped switching modules supported by the PFC. Each PFC or DFC polices independently, which might affect QoS features being applied to traffic that is distributed across the PFC and any DFCs. Examples of these QoS feature are:
With a PFC3, when you apply both ingress policing and egress policing to the same traffic, both the input policy and the output policy must either mark down traffic or drop traffic. PFC QoS does not support ingress markdown with egress drop or ingress drop with egress markdown.
This example shows how to attach the policy map named pmap1 to Fast Ethernet port 5/36:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/36 Router(config-if)# service-policy input pmap1 Router(config-if)# end
41-82
OL-3999-08
Chapter 41

Router# show policy-map interface fastethernet 5/36 FastEthernet5/36 service-policy input: pmap1 class-map: cmap1 (match-all) 0 packets, 0 bytes 5 minute rate 0 bps match: ip precedence 5 class cmap1 police 8000 8000 conform-action transmit exceed-action drop class-map: cmap2 (match-any) 0 packets, 0 bytes 5 minute rate 0 bps match: ip precedence 2 0 packets, 0 bytes 5 minute rate 0 bps class cmap2 police 8000 10000 conform-action transmit exceed-action drop Router#
Configuring Egress DSCP Mutation on a PFC3

Note
The PFC2 does not support egress DSCP mutation. These sections describe how to configure egress DSCP mutation on a PFC3:

Configuring Named DSCP Mutation Maps, page 41-83 Attaching an Egress DSCP Mutation Map to an Interface, page 41-84
Configuring Named DSCP Mutation Maps

To configure a named DSCP mutation map, perform this task: Command
Step 1
Router(config)# mls qos map dscp-mutation map_name dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]] to mutated_dscp Router(config)# no mls qos map dscp-mutation map_name
Purpose Configures a named DSCP mutation map.
Reverts to the default map. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls qos maps
When configuring a named DSCP mutation map, note the following information:

You can enter up to 8 DSCP values that map to a mutated DSCP value. You can enter multiple commands to map additional DSCP values to a mutated DSCP value. You can enter a separate command for each mutated DSCP value.
41-83
Configuring PFC QoS
This example shows how to map DSCP 30 to mutated DSCP value 8:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls qos map dscp-mutation mutmap1 30 to 8 Router(config)# end Router#

Router# show mls qos map | begin DSCP mutation DSCP mutation map mutmap1: (dscp= d1d2) d1 : d2 0 1 2 3 4 5 6 7 8 9 ------------------------------------0 : 00 01 02 03 04 05 06 07 08 09 1 : 10 11 12 13 14 15 16 17 18 19 2 : 20 21 22 23 24 25 26 27 28 29 3 : 08 31 32 33 34 35 36 37 38 39 4 : 40 41 42 43 44 45 46 47 48 49 5 : 50 51 52 53 54 55 56 57 58 59 6 : 60 61 62 63 <...Output Truncated...> Router#
Note
In the DSCP mutation map displays, the marked-down DSCP values are shown in the body of the matrix; the first digit of the original DSCP value is in the column labeled d1 and the second digit is in the top row. In the example shown, DSCP 30 maps to DSCP 08.
Attaching an Egress DSCP Mutation Map to an Interface

To attach an egress DSCP mutation map to an interface, perform this task: Command
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port[.subinterface]} | {port-channel number[.subinterface]}} Router(config-if)# mls qos dscp-mutation mutation_map_name Router(config-if)# no mls qos dscp-mutation mutation_map_name
Step 2
Attaches an egress DSCP mutation map to the interface. Removes the egress DSCP mutation map from the interface. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show running-config interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} 1.
This example shows how to attach the egress DSCP mutation map named mutmap1 to Fast Ethernet port 5/36:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/36 Router(config-if)# mls qos dscp-mutation mutmap1 Router(config-if)# end
41-84
OL-3999-08
Chapter 41
Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports

Note
The Supervisor Engine 2 does not support the switching modules that support ingress CoS mutation. Release 12.2(17b)SXA and later releases support ingress CoS mutation on IEEE 802.1Q tunnel ports configured to trust received CoS (see the Ingress CoS Mutation Configuration Guidelines and Restrictions section on page 41-85 for the list of supported modules). When you configure ingress CoS mutation on an IEEE 802.1Q tunnel port that you have configured to trust received CoS, PFC QoS uses the mutated CoS value instead of the received CoS value in the ingress drop thresholds and for any trust CoS marking and policing. These sections describe how to configure ingress CoS mutation:

Ingress CoS Mutation Configuration Guidelines and Restrictions, page 41-85 Configuring Ingress CoS Mutation Maps, page 41-86 Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports, page 41-87
Ingress CoS Mutation Configuration Guidelines and Restrictions

When configuring ingress CoS mutation, follow these guidelines and restrictions:

Release 12.2(17b)SXA and later releases support ingress CoS mutation on WS-X6704-10GE, WS-X6748-SFP, WS-X6724-SFP, and WS-X6748-GE-TX switching modules. Ports that are not configured as IEEE 802.1Q tunnel ports do not support ingress CoS mutation. Ports that are not configured to trust received CoS do not support ingress CoS mutation. Ingress CoS mutation does not change the CoS value carried by the customer frames. When the customer traffic exits the 802.1Q tunnel, the original CoS is intact. Ingress CoS mutation configuration applies to all ports in a port group. The port groups are:
WS-X6704-10GE4 ports, 4 port groups, 1 port in each group WS-X6748-SFP48 ports, 4 port groups: ports 112, 1324, 2536, and 3748 WS-X6724-SFP24 ports, 2 port groups: ports 112 and 1324 WS-X6748-GE-TX48 ports, 4 port groups: ports 112, 1324, 2536, and 3748
To avoid ingress CoS mutation configuration failures, only create EtherChannels where all member ports support ingress CoS mutation or where no member ports support ingress CoS mutation. Do not create EtherChannels with mixed support for ingress CoS mutation. If you configure ingress CoS mutation on a port that is a member of an EtherChannel, the ingress CoS mutation is applied to the port-channel interface. You can configure ingress CoS mutation on port-channel interfaces. With ingress CoS mutation configured on a port-channel interface, the following occurs:
The ingress CoS mutation configuration is applied to the port groups of all member ports of the
EtherChannel. If any member port cannot support ingress CoS mutation, the configuration fails.
If a port in the port group is a member of a second EtherChannel, the ingress CoS mutation
configuration is applied to the second port-channel interface and to the port groups of all member ports of the second EtherChannel. If any member port of the second EtherChannel
41-85
Configuring PFC QoS
cannot support ingress CoS mutation, the configuration fails on the first EtherChannel. If the configuration originated on a nonmember port in a port group that has a member port of the first EtherChannel, the configuration fails on the nonmember port.
The ingress CoS mutation configuration propagates without limit through port groups, member
ports, and port-channel interfaces, regardless of whether or not the ports are configured to trust CoS or are configured as IEEE 802.1Q tunnel ports.
An EtherChannel where you want to configure ingress CoS mutation must not have member ports that are in port groups containing member ports of other EtherChannels that have member ports that do not support ingress CoS mutation. (This restriction extends without limit through all port-group-linked member ports and port-channel-interface-linked ports.) A port where you want to configure ingress CoS mutation must not be in a port group that has a member port of an EtherChannel that has members that do not support ingress CoS mutation. (This restriction extends without limit through all port-group-linked member ports and port-channel-interface-linked ports.) There can be only be one ingress CoS mutation configuration applied to all port-group-linked member ports and port-channel-interface-linked ports.
Configuring Ingress CoS Mutation Maps

To configure an ingress CoS mutation map, perform this task: Command
Step 1
Router(config)# mls qos map cos-mutation mutation_map_name mutated_cos1 mutated_cos2 mutated_cos3 mutated_cos4 mutated_cos5 mutated_cos6 mutated_cos7 mutated_cos8 Router(config)# no mls qos map cos-mutation map_name
Purpose Configures an ingress CoS mutation map. You must enter 8 mutated CoS values to which PFC QoS maps ingress CoS values 0 through 7. Deletes the named map. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls qos maps cos-mutation
This example shows how to configure a CoS mutation map named testmap:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls qos map cos-mutation testmap 4 5 6 7 0 1 2 3 Router(config)# end Router#
This example shows how to verify the map configuration:

Router(config)# show mls qos maps cos-mutation COS mutation map testmap cos-in : 0 1 2 3 4 5 6 7 -----------------------------------cos-out : 4 5 6 7 0 1 2 3 Router#
41-86
OL-3999-08
Chapter 41
Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports

To attach an ingress CoS mutation map to an IEEE 802.1Q tunnel port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port} |
Selects the interface to configure. Attaches an ingress CoS mutation map to the interface. Removes the ingress CoS mutation map from the interface. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos cos-mutation mutation_map_name Router(config-if)# no mls qos cos-mutation mutation_map_name
Step 3 Step 4
Router(config-if)# end Router# show running-config interface {{type1 slot/port} | {port-channel number}} Router# show mls qos maps cos-mutation 1.
type = gigabitethernet or tengigabitethernet
This example shows how to attach the ingress CoS mutation map named testmap to Gigabit Ethernet port 1/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# mls qos cos-mutation testmap Router(config-if)# end Router# show mls qos maps cos-mutation COS mutation map testmap cos-in : 0 1 2 3 4 5 6 7 -----------------------------------cos-out : 4 5 6 7 0 1 2 3 testmap is attached on the following interfaces Gi1/1 Router#
Configuring DSCP Value Maps

These sections describe how DSCP values are mapped to other values:

Mapping Received CoS Values to Internal DSCP Values, page 41-88 Mapping Received IP Precedence Values to Internal DSCP Values, page 41-88 Configuring DSCP Markdown Values, page 41-89 Mapping Internal DSCP Values to Egress CoS Values, page 41-90
41-87
Configuring PFC QoS
Mapping Received CoS Values to Internal DSCP Values

To configure the mapping of received CoS values to the DSCP value that PFC QoS uses internally on the PFC, perform this task: Command
Step 1
Router(config)# mls qos map cos-dscp dscp1 dscp2 dscp3 dscp4 dscp5 dscp6 dscp7 dscp8
Purpose Configures the received CoS to internal DSCP map. You must enter 8 DSCP values to which PFC QoS maps CoS values 0 through 7. Reverts to the default map. Exits configuration mode. Verifies the configuration.
Router(config)# no mls qos map cos-dscp
Step 2 Step 3
This example shows how to configure the received CoS to internal DSCP map:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls qos map cos-dscp 0 1 2 3 4 5 6 7 Router(config)# end Router#

Router# show mls qos maps | begin Cos-dscp map Cos-dscp map: cos: 0 1 2 3 4 5 6 7 ---------------------------------dscp: 0 1 2 3 4 5 6 7 <...Output Truncated...> Router#
Mapping Received IP Precedence Values to Internal DSCP Values

To configure the mapping of received IP precedence values to the DSCP value that PFC QoS uses internally on the PFC, perform this task: Command
Step 1
Router(config)# mls qos map ip-prec-dscp dscp1 dscp2 dscp3 dscp4 dscp5 dscp6 dscp7 dscp8
Purpose Configures the received IP precedence to internal DSCP map. You must enter 8 internal DSCP values to which PFC QoS maps received IP precedence values 0 through 7. Reverts to the default map. Exits configuration mode. Verifies the configuration.
Router(config)# no mls qos map ip-prec-dscp
Step 2 Step 3
This example shows how to configure the received IP precedence to internal DSCP map:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls qos map ip-prec-dscp 0 1 2 3 4 5 6 7 Router(config)# end Router#
41-88
OL-3999-08
Chapter 41

Router# show mls qos maps | begin IpPrecedence-dscp map IpPrecedence-dscp map: ipprec: 0 1 2 3 4 5 6 7 ---------------------------------dscp: 0 1 2 3 4 5 6 7 <...Output Truncated...> Router#
Configuring DSCP Markdown Values

To configure the mapping of DSCP markdown values used by policers, perform this task: Command
Step 1
Router(config)# mls qos map policed-dscp {normal-burst | max-burst} dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]] to markdown_dscp Router(config)# no mls qos map policed-dscp {normal-burst | max-burst}
Purpose Configures a DSCP markdown map.
Step 2 Step 3
When configuring a DSCP markdown map, note the following information:

You can enter the normal-burst keyword to configure the markdown map used by the exceed-action policed-dscp-transmit keywords. You can enter the max-burst keyword to configure the markdown map used by the violate-action policed-dscp-transmit keywords.
Note
When you create a policer that does not use the pir keyword, and the maximum_burst_bytes parameter is equal to the normal_burst_bytes parameter (which occurs if you do not enter the maximum_burst_bytes parameter), the exceed-action policed-dscp-transmit keywords cause PFC QoS to mark traffic down as defined by the policed-dscp max-burst markdown map.
To avoid out-of-sequence packets, configure the markdown maps so that conforming and nonconforming traffic uses the same queue. You can enter up to 8 DSCP values that map to a marked-down DSCP value. You can enter multiple commands to map additional DSCP values to a marked-down DSCP value. You can enter a separate command for each marked-down DSCP value.
Note
Configure marked-down DSCP values that map to CoS values consistent with the markdown penalty.
41-89
Configuring PFC QoS
This example shows how to map DSCP 1 to marked-down DSCP value 0:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls qos map policed-dscp normal-burst 1 to 0 Router(config)# end Router#

Router# show mls qos map Normal Burst Policed-dscp map: d1 : d2 0 1 2 3 4 5 6 7 8 9 ------------------------------------0 : 00 01 02 03 04 05 06 07 08 09 1 : 10 11 12 13 14 15 16 17 18 19 2 : 20 21 22 23 24 25 26 27 28 29 3 : 30 31 32 33 34 35 36 37 38 39 4 : 40 41 42 43 44 45 46 47 48 49 5 : 50 51 52 53 54 55 56 57 58 59 6 : 60 61 62 63 Maximum Burst Policed-dscp map: d1 : d2 0 1 2 3 4 5 6 7 8 9 ------------------------------------0 : 00 01 02 03 04 05 06 07 08 09 1 : 10 11 12 13 14 15 16 17 18 19 2 : 20 21 22 23 24 25 26 27 28 29 3 : 30 31 32 33 34 35 36 37 38 39 4 : 40 41 42 43 44 45 46 47 48 49 5 : 50 51 52 53 54 55 56 57 58 59 6 : 60 61 62 63 <...Output Truncated...> Router# (dscp= d1d2)
(dscp= d1d2)
Note
In the Policed-dscp displays, the marked-down DSCP values are shown in the body of the matrix; the first digit of the original DSCP value is in the column labeled d1 and the second digit is in the top row. In the example shown, DSCP 41 maps to DSCP 41.
Mapping Internal DSCP Values to Egress CoS Values

To configure the mapping of the DSCP value that PFC QoS uses internally on the PFC to the CoS value used for egress LAN port scheduling and congestion avoidance, perform this task: Command
Step 1
Router(config)# mls qos map dscp-cos dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]] to cos_value Router(config)# no mls qos map dscp-cos
Purpose Configures the internal DSCP to egress CoS map.
Step 2 Step 3
41-90
OL-3999-08
Chapter 41
When configuring the internal DSCP to egress CoS map, note the following information:

You can enter up to 8 DSCP values that PFC QoS maps to a CoS value. You can enter multiple commands to map additional DSCP values to a CoS value. You can enter a separate command for each CoS value.
This example shows how to configure internal DSCP values 0, 8, 16, 24, 32, 40, 48, and 54 to be mapped to egress CoS value 0:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls qos map dscp-cos 0 8 16 24 32 40 48 54 to 0 Router(config)# end Router#

Router# show mls qos map | begin Dscp-cos map Dscp-cos map: d1 : d2 0 1 2 3 4 5 6 7 8 9 ------------------------------------0 : 00 00 00 00 00 00 00 00 00 01 1 : 01 01 01 01 01 01 00 02 02 02 2 : 02 02 02 02 00 03 03 03 03 03 3 : 03 03 00 04 04 04 04 04 04 04 4 : 00 05 05 05 05 05 05 05 00 06 5 : 06 06 06 06 00 06 07 07 07 07 6 : 07 07 07 07 <...Output Truncated...> Router# (dscp= d1d2)
Note
In the Dscp-cos map display, the CoS values are shown in the body of the matrix; the first digit of the DSCP value is in the column labeled d1 and the second digit is in the top row. In the example shown, DSCP values 41 through 47 all map to CoS 05.
Configuring the Trust State of Ethernet LAN and OSM Ports

By default, all ports are untrusted. You can configure the port trust state on all Ethernet LAN ports and OSM ports.
Note
On non-Gigabit Ethernet 1q4t/2q2t ports, you must repeat the trust configuration in a class map.
41-91
Configuring PFC QoS
To configure the trust state of a port, perform this task: Command

Step 1 Step 2
Router(config)# interface {{type1 slot/port} | {port-channel number}} Router(config-if)# mls qos trust [dscp | ip-precedence | cos2] Router(config-if)# no mls qos trust
Purpose Selects the interface to configure. Configures the trust state of the port. Reverts to the default trust state (untrusted). Exits configuration mode.
1
Step 3 Step 4
Router(config-if)# end Router# show queueing interface type include Trust state 1. 2.
slot/port |
type = ethernet, fastethernet, gigabitethernet , tengigabitethernet , ge-wan, pos , or atm.

Not supported for serial, pos or atm interface types.
When configuring the trust state of a port, note the following information:

With no other keywords, the mls qos trust command is equivalent to mls qos trust dscp. With Release 12.2(18)SXF5 and later releases, you can use the mls qos trust dscp command to enable DSCP-based receive-queue drop thresholds on WS-X6708-10GE ports (see the Configuring DSCP-Based Queue Mapping section on page 41-100). To avoid dropping traffic because of inconsistent DSCP values when DSCP-based queue mapping is enabled, configure ports with the mls qos trust dscp command only when the received traffic carries DSCP values that you know to be consistent with network policy. The mls qos trust cos command enables CoS-based receive-queue drop thresholds. To avoid dropping traffic because of inconsistent CoS values, configure ports with the mls qos trust cos command only when the received traffic is ISL or 802.1Q frames carrying CoS values that you know to be consistent with network policy. With Release 12.2(17b)SXA and later releases, you can configure IEEE 8021.Q tunnel ports configured with the mls qos trust cos command to use a mutated CoS value instead of the received CoS value (Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports section on page 41-85). Use the no mls qos trust command to set the port state to untrusted.
This example shows how to configure Gigabit Ethernet port 1/1 with the trust cos keywords:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# mls qos trust cos Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/1 | include trust Trust state: trust COS Router#
41-92
OL-3999-08
Chapter 41
Configuring the Ingress LAN Port CoS Value

Note
Whether or not PFC QoS uses the CoS value applied with the mls qos cos command depends on the trust state of the port and the trust state of the traffic received through the port. The mls qos cos command does not configure the trust state of the port or the trust state of the traffic received through the port. To use the CoS value applied with the mls qos cos command as the basis of internal DSCP:

On a port that receives only untagged ingress traffic, configure the ingress port as trusted or configure a trust CoS policy map that matches the ingress traffic. On a port that receives tagged ingress traffic, configure a trust CoS policy map that matches the ingress traffic.
You can configure the CoS value that PFC QoS assigns to untagged frames from ingress LAN ports configured as trusted and to all frames from ingress LAN ports configured as untrusted. To configure the CoS value for an ingress LAN port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port} |
Selects the interface to configure. Configures the ingress LAN port CoS value. Reverts to the default port CoS value. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos cos port_cos Router(config-if)# no mls qos cos port_cos
Step 3 Step 4
Router(config-if)# end Router# show queuing interface {ethernet | fastethernet | gigabitethernet} slot/port 1.
This example shows how to configure the CoS value 5 on Fast Ethernet port 5/24 and verify the configuration:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/24 Router(config-if)# mls qos cos 5 Router(config-if)# end Router# show queueing interface fastethernet 5/24 | include Default COS Default COS is 5 Router#
Configuring Standard-Queue Drop Threshold Percentages

These sections describe configuring standard-queue drop threshold percentages:

Configuring a Tail-Drop Receive Queue, page 41-94 Configuring a WRED-Drop Transmit Queue, page 41-95 Configuring a WRED-Drop and Tail-Drop Receive Queue, page 41-96
41-93
Configuring PFC QoS
Configuring a WRED-Drop and Tail-Drop Transmit Queue, page 41-96 Configuring 1q4t/2q2t Tail-Drop Threshold Percentages, page 41-98
Note
Enter the show queueing interface {ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port | include type command to see the queue structure of a port. 1p1q0t ports have no configurable thresholds. 1p3q1t (transmit), 1p2q1t (transmit), and 1p1q8t (receive) ports also have nonconfigurable tail-drop thresholds.
When configuring thresholds, note the following information:

Queue number 1 is the lowest-priority standard queue. Higher-numbered queues are higher priority standard queues. Receive-queue parameters can be configured only on trusted ports. When configuring minimum and maximum threshold values, you cannot configure minimum values to be larger than maximumvalues. The first percentage that you enter sets the lowest-priority threshold. The second percentage that you enter sets the next highest-priority threshold. The last percentage that you enter sets the highest-priority threshold. The percentages range from 1 to 100. A value of 10 indicates a threshold when the buffer is 10-percent full. Always set highest-numbered threshold to 100 percent. Each WRED-drop threshold has a low-WRED and a high-WRED value. Low-WRED and high-WRED values are a percentage of the queue capacity (the range is from 1 to 100). The low-WRED value is the traffic level under which no traffic is dropped. The low-WRED value must be lower than the high-WRED value. The high-WRED value is the traffic level above which all traffic is dropped. Traffic in the queue between the low- and high-WRED values has an increasing chance of being dropped as the queue fills.
When you configure multiple-threshold standard queues, note the following information:

When configuring the WRED-drop thresholds, note the following information:

Configuring a Tail-Drop Receive Queue

These port types have only tail-drop thresholds in their receive-queues:

1q2t 1p1q4t 2q8t 1q8t
41-94
OL-3999-08
Chapter 41
To configure the drop thresholds, perform this task: Command

Step 1 Step 2
Router(config)# interface {fastethernet | gigabitethernet} slot/port Router(config-if)# rcv-queue threshold queue_id thr1% thr2% thr3% thr4% {thr5% thr6% thr7% thr8%} Router(config-if)# no rcv-queue threshold [queue_id]
Purpose Selects the interface to configure. Configures the receive-queue tail-drop threshold percentages. Reverts to the default receive-queue tail-drop threshold percentages. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface {fastethernet | gigabitethernet} slot/port
This example shows how to configure the receive-queue drop thresholds for Gigabit Ethernet port 1/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# rcv-queue threshold 1 60 75 85 100 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/1 | begin Receive queues Receive queues [type = 1p1q4t]: Queue Id Scheduling Num of thresholds ----------------------------------------1 Standard 4 2 Priority 1 Trust state: trust COS queue tail-drop-thresholds -------------------------1 60[1] 75[2] 85[3] 100[4] <...Output Truncated...> Router#
Configuring a WRED-Drop Transmit Queue

These port types have only WRED-drop thresholds in their transmit queues:

1p2q2t (transmit) 1p2q1t (transmit) Purpose

1
Command
Step 1 Step 2
slot/port
Selects the interface to configure. Configures the low WRED-drop thresholds. Reverts to the default low WRED-drop thresholds.
Router(config-if)# wrr-queue random-detect min-threshold queue_id thr1% [thr2%] Router(config-if)# no wrr-queue random-detect min-threshold [queue_id]
41-95
Configuring PFC QoS
Command
Step 3
Router(config-if)# wrr-queue random-detect max-threshold queue_id thr1% [thr2%] Router(config-if)# no wrr-queue random-detect max-threshold [queue_id]
Purpose Configures the high WRED-drop thresholds. Reverts to the default high WRED-drop thresholds. Exits configuration mode.
1
Step 4 Step 5
Router(config-if)# end Router# show queueing interface type 1.
slot/port
type = fastethernet, gigabitethernet , or tengigabitethernet
Configuring a WRED-Drop and Tail-Drop Receive Queue

These port types have both WRED-drop and tail-drop thresholds in their receive queues:

8q4t (receive) 8q8t (receive) 1p1q8t (receive)

Step 1 Step 2
1
Purpose
slot/port
Selects the interface to configure. Configures the tail-drop thresholds. Reverts to the default tail-drop thresholds. Configures the low WRED-drop thresholds.
Router(config-if)# rcv-queue threshold queue_id thr1% thr2% thr3% thr4% thr5% thr6% thr7% thr8% Router(config-if)# no rcv-queue threshold [queue_id]
Step 3
Router(config-if)# rcv-queue random-detect min-threshold queue_id thr1% thr2% thr3% thr4% thr5% thr6% thr7% thr8% Router(config-if)# no rcv-queue random-detect min-threshold [queue_id]
Reverts to the default low WRED-drop thresholds. Configures the high WRED-drop thresholds.
Step 4
Router(config-if)# rcv-queue random-detect max-threshold queue_id thr1% thr2% thr3% thr4% thr5% thr6% thr7% thr8% Router(config-if)# no rcv-queue random-detect max-threshold [queue_id]
Reverts to the default high WRED-drop thresholds. Enables WRED-drop thresholds. Enables tail-drop thresholds. Exits configuration mode.
Step 5
Router(config-if)# rcv-queue random-detect queue_id Router(config-if)# no rcv-queue random-detect [queue_id]
Step 6 Step 7

1
slot/port
Configuring a WRED-Drop and Tail-Drop Transmit Queue

These port types have both WRED-drop and tail-drop thresholds in their transmit queues:

1p3q1t (transmit) 1p3q8t (transmit)
41-96
OL-3999-08
Chapter 41
1p7q8t (transmit)

Step 1 Step 2
1
Purpose
slot/port
Selects the interface to configure. Configures the tail-drop thresholds. Reverts to the default tail-drop thresholds. Configures the low WRED-drop thresholds.
Router(config-if)# wrr-queue threshold queue_id thr1% [thr2% thr3% thr4% thr5% thr6% thr7% thr8%] Router(config-if)# no wrr-queue threshold [queue_id]
Step 3
Router(config-if)# wrr-queue random-detect min-threshold queue_id thr1% [thr2% thr3% thr4% thr5% thr6% thr7% thr8%] Router(config-if)# no wrr-queue random-detect min-threshold [queue_id]
Reverts to the default low WRED-drop thresholds. Configures the high WRED-drop thresholds.
Step 4
Router(config-if)# wrr-queue random-detect max-threshold queue_id thr1% [thr2% thr3% thr4% thr5% thr6% thr7% thr8%] Router(config-if)# no wrr-queue random-detect max-threshold [queue_id]
Reverts to the default high WRED-drop thresholds. Enables WRED-drop thresholds. Enables tail-drop thresholds. Exits configuration mode.
Step 5
Router(config-if)# wrr-queue random-detect queue_id Router(config-if)# no wrr-queue random-detect [queue_id]
Step 6 Step 7

1
slot/port
This example shows how to configure the low-priority transmit queue high-WRED-drop thresholds for Gigabit Ethernet port 1/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# wrr-queue random-detect max-threshold 1 70 70 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/1 | begin Transmit queues Transmit queues [type = 1p2q2t]: Queue Id Scheduling Num of thresholds ----------------------------------------1 WRR low 2 2 WRR high 2 3 Priority 1 queue random-detect-max-thresholds ---------------------------------1 40[1] 70[2] 2 40[1] 70[2] <...Output Truncated...> Router#
41-97
Configuring PFC QoS
Configuring 1q4t/2q2t Tail-Drop Threshold Percentages

On 1q4t/2q2t ports, the receive- and transmit-queue drop thresholds have this relationship:

Receive queue 1 (standard) threshold 1 = transmit queue 1 (standard low priority) threshold 1 Receive queue 1 (standard) threshold 2 = transmit queue 1 (standard low priority) threshold 2 Receive queue 1 (standard) threshold 3 = transmit queue 2 (standard high priority) threshold 1 Receive queue 1 (standard) threshold 4 = transmit queue 2 (standard high priority) threshold 2
To configure tail-drop threshold percentages for the standard receive and transmit queues on 1q4t/2q2t LAN ports, perform this task: Command
Step 1 Step 2
Router(config)# interface {ethernet | fastethernet | gigabitethernet} slot/port Router(config-if)# wrr-queue threshold queue_id thr1% thr2% Router(config-if)# no wrr-queue threshold [queue_id]
Purpose Selects the interface to configure. Configures the receive- and transmit-queue tail-drop thresholds. Reverts to the default receive- and transmit-queue tail-drop thresholds. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface {ethernet | fastethernet | gigabitethernet} slot/port
When configuring the receive- and transmit-queue tail-drop thresholds, note the following information:

You must use the transmit queue and threshold numbers. The queue_id is 1 for the standard low-priority queue and 2 for the standard high-priority queue. The percentages range from 1 to 100. A value of 10 indicates a threshold when the buffer is 10-percent full. Always set threshold 2 to 100 percent. Ethernet and Fast Ethernet 1q4t ports do not support receive-queue tail-drop thresholds.
This example shows how to configure receive queue 1/threshold 1 and transmit queue 1/threshold 1 for Gigabit Ethernet port 2/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 2/1 Router(config-if)# wrr-queue threshold 1 60 100 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 2/1 Transmit queues [type = 2q2t]: <...Output Truncated...> queue tail-drop-thresholds -------------------------1 60[1] 100[2] 2 40[1] 100[2]
41-98
OL-3999-08
Chapter 41
<...Output Truncated...> Receive queues [type = 1q4t]: <...Output Truncated...> queue tail-drop-thresholds -------------------------1 60[1] 100[2] 40[3] 100[4] <...Output Truncated...> Router#
Mapping QoS Labels to Queues and Drop Thresholds

These sections describe how to map QoS labels to queues and drop thresholds:
Note
Enter the show queueing interface {ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port | include type command to see the queue structure of a port. These sections describe how to map QoS labels to queues and drop thresholds:

Queue and Drop Threshold Mapping Guidelines and Restrictions, page 41-99 Configuring DSCP-Based Queue Mapping, page 41-100 Configuring CoS-Based Queue Mapping, page 41-105
Queue and Drop Threshold Mapping Guidelines and Restrictions

When mapping QoS labels to queues and thresholds, note the following information:

When SRR is enabled, you cannot map any CoS values or DSCP values to strict-priority queues. Queue number 1 is the lowest-priority standard queue. Higher-numbered queues are higher priority standard queues. You can map up to 8 CoS values to a threshold. You can map up to 64 DSCP values to a threshold. Threshold 0 is a nonconfigurable 100-percent tail-drop threshold on these port types:
1p1q0t (receive) 1p1q8t (receive) 1p3q1t (transmit) 1p2q1t (transmit)
The standard queue thresholds can be configured as either tail-drop or WRED-drop thresholds on these port types:
1p1q8t (receive) 1p3q1t (transmit) 1p3q8t (transmit) 1p7q1t (transmit)
41-99
Configuring PFC QoS
Configuring DSCP-Based Queue Mapping

These sections describe how to configure DSCP-based queue mapping:

Configuring Ingress DSCP-Based Queue Mapping, page 41-100 Mapping DSCP Values to Standard Transmit-Queue Thresholds, page 41-103 Mapping DSCP Values to the Transmit Strict-Priority Queue, page 41-104
Note
DSCP-based queue mapping is supported on WS-X6708-10GE ports.
Enabling DSCP-Based Queue Mapping

To enable DSCP-based queue mapping, perform this task: Command
Step 1 Step 2
Router(config)# interface tengigabitethernet slot/port Router(config-if)# mls qos queue-mode mode-dscp Router(config-if)# no mls qos queue-mode mode-dscp
Purpose Selects the interface to configure. Enables DSCP-based queue mapping. Reverts to CoS-based queue mapping. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface tengigabitethernet slot/port | include Queueing Mode
This example shows how to enable DSCP-based queue mapping on 10-Gigabit Ethernet port 6/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 6/1 Router(config-if)# mls qos queue-mode mode-dscp Router(config-if)# end

Router# show queueing interface tengigabitethernet 6/1 | include Queueing Mode Queueing Mode In Tx direction: mode-dscp Queueing Mode In Rx direction: mode-dscp
Configuring Ingress DSCP-Based Queue Mapping

Ingress DSCP-to-queue mapping is supported only on ports configured to trust DSCP. These sections describe how to configure ingress DSCP-based queue mapping:

Enabling DSCP-Based Queue Mapping, page 41-100 Mapping DSCP Values to Standard Receive-Queue Thresholds, page 41-101
41-100
OL-3999-08
Chapter 41
Configuring the Port to Trust DSCP
To configure the port to trust DSCP perform this task: Command

Step 1 Step 2
Router(config)# interface tengigabitethernet slot/port Router(config-if)# mls qos trust dscp Router(config-if)# no mls qos trust
Purpose Selects the interface to configure. Configures the port to trust received DSCP values. Reverts to the default trust state (untrusted). Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface tengigabitethernet slot/port | include Trust state
This example shows how to configure 10-Gigabit Ethernet port 6/1 port 6/1 to trust received DSCP values:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 6/1 Router(config-if)# mls qos trust dscp Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 6/1 | include Trust state Trust state: trust DSCP
Mapping DSCP Values to Standard Receive-Queue Thresholds
To map DSCP values to the standard receive-queue thresholds, perform this task: Command
Step 1 Step 2
Router(config)# interface tengigabitethernet slot/port Router(config-if)# rcv-queue dscp-map queue_# threshold_# dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]] Router(config-if)# no rcv-queue dscp-map
Purpose Selects the interface to configure. Maps DSCP values to the standard receive queue thresholds. Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface tengigabitethernet slot/port
When mapping DSCP values, note the following information:

You can enter up to 8 DSCP values that map to a queue and threshold. You can enter multiple commands to map additional DSCP values to the queue and threshold. You must enter a separate command for each queue and threshold.
41-101
Configuring PFC QoS
This example shows how to map the DSCP values 0 and 1 to threshold 1 in the standard receive queue for 10-Gigabit Ethernet port 6/1 port 6/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 6/1 Router(config-if)# rcv-queue dscp-map 1 1 0 1 Router(config-if)# end Router#
Note
The receive queue mapping is shown in the second queue thresh dscp-map displayed by the show queueing interface command. This example shows how to verify the configuration:
Router# show queueing interface tengigabitethernet 1/1 | begin queue thresh dscp-map <...Output Truncated...> queue thresh dscp-map --------------------------------------1 1 0 1 2 3 4 5 6 7 8 9 11 13 15 16 17 19 21 23 25 27 29 31 33 39 41 42 43 44 45 47 1 2 1 3 1 4 2 1 14 2 2 12 2 3 10 2 4 3 1 22 3 2 20 3 3 18 3 4 4 1 24 30 4 2 28 4 3 26 4 4 5 1 32 34 35 36 37 38 5 2 5 3 5 4 6 1 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 6 2 6 3 6 4 7 1 7 2 7 3 7 4 8 1 40 46 8 2 8 3 8 4 <...Output Truncated...> Router#
41-102
OL-3999-08
Chapter 41
Mapping DSCP Values to Standard Transmit-Queue Thresholds

To map DSCP values to standard transmit-queue thresholds, perform this task: Command
Step 1 Step 2
Router(config)# interface tengigabitethernet slot/port Router(config-if)# wrr-queue dscp-map transmit_queue_# threshold_# dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]] Router(config-if)# no wrr-queue dscp-map
Purpose Selects the interface to configure. Maps DSCP values to a standard transmit-queue threshold. Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
When mapping DSCP values, note the following information:

You can enter up to 8 DSCP values that map to a queue and threshold. You can enter multiple commands to map additional DSCP values to the queue and threshold. You must enter a separate command for each queue and threshold.
This example shows how to map the DSCP values 0 and 1 to standard transmit queue 1/threshold 1 for 10-Gigabit Ethernet port 6/1 port 6/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 6/1 Router(config-if)# wrr-queue dscp-map 1 1 0 1 Router(config-if)# end Router#
41-103
Configuring PFC QoS
Note
The eighth queue is the strict priority queue in the output of the show queueing interface command. This example shows how to verify the configuration:
Router# show queueing interface tengigabitethernet 6/1 | begin queue thresh dscp-map queue thresh dscp-map --------------------------------------1 1 0 1 2 3 4 5 6 7 8 9 11 13 15 16 17 19 21 23 25 27 29 31 33 39 41 42 43 44 45 47 1 2 1 3 1 4 2 1 14 2 2 12 2 3 10 2 4 3 1 22 3 2 20 3 3 18 3 4 4 1 24 30 4 2 28 4 3 26 4 4 5 1 32 34 35 36 37 38 5 2 5 3 5 4 6 1 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 6 2 6 3 6 4 7 1 7 2 7 3 7 4 8 1 40 46 <...Output Truncated...> Router#
Mapping DSCP Values to the Transmit Strict-Priority Queue

To map DSCP values to the transmit strict-priority queue, perform this task: Command
Step 1 Step 2
Router(config)# interface tengigabitethernet slot/port Router(config-if)# priority-queue dscp-map queue_# dscp1 [dscp2 [dscp3 [dscp4 [dscp5 [dscp6 [dscp7 [dscp8]]]]]]]
Purpose Selects the interface to configure. Maps DSCP values to the transmit strict-priority queue. You can enter multiple priority-queue dscp-map commands to map more than 8 DSCP values to the strict-priority queue. Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
Router(config-if)# no priority-queue dscp-map
Step 3 Step 4
41-104
OL-3999-08
Chapter 41
When mapping DSCP values to the strict-priority queue, note the following information:

The queue number is always 1. You can enter up to 8 DSCP values to map to the queue. You can enter multiple commands to map additional DSCP values to the queue.
This example shows how to map DSCP value 7 to the strict-priority queue on 10 Gigabit Ethernet port 6/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface tengigabitethernet 6/1 Router(config-if)# priority-queue dscp-map 1 7 Router(config-if)# end Router#
Note
The strict priority queue is queue 8 in the output of the show queueing interface command. This example shows how to verify the configuration:
Router# show queueing interface tengigabitethernet 6/1 | begin queue thresh dscp-map queue thresh dscp-map --------------------------------------<...Output Truncated...> 8 1 7 40 46 <...Output Truncated...> Router#
Configuring CoS-Based Queue Mapping

These sections describe how to configure CoS-based queue mapping:

Mapping CoS Values to Standard Receive-Queue Thresholds, page 41-105 Mapping CoS Values to Standard Transmit-Queue Thresholds, page 41-106 Mapping CoS Values to Strict-Priority Queues, page 41-107 Mapping CoS Values to Tail-Drop Thresholds on 1q4t/2q2t LAN Ports, page 41-108
Mapping CoS Values to Standard Receive-Queue Thresholds

To map CoS values to the standard receive-queue thresholds, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# rcv-queue cos-map queue_# threshold_# cos1 [cos2 [cos3 [cos4 [cos5 [cos6 [cos7 [cos8]]]]]]] Router(config-if)# no rcv-queue cos-map
Purpose Selects the interface to configure. Maps CoS values to the standard receive queue thresholds. Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface type1 slot/port 1.
41-105
Configuring PFC QoS
This example shows how to map the CoS values 0 and 1 to threshold 1 in the standard receive queue for Gigabit Ethernet port 1/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# rcv-queue cos-map 1 1 0 1 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/1 <...Output Truncated...> queue thresh cos-map --------------------------------------1 1 0 1 1 2 2 3 1 3 4 5 1 4 6 7 <...Output Truncated...> Router#
Mapping CoS Values to Standard Transmit-Queue Thresholds

To map CoS values to standard transmit-queue thresholds, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# wrr-queue cos-map transmit_queue_# threshold_# cos1 [cos2 [cos3 [cos4 [cos5 [cos6 [cos7 [cos8]]]]]]] Router(config-if)# no wrr-queue cos-map
Purpose Selects the interface to configure. Maps CoS values to a standard transmit-queue threshold.
Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface type1 slot/port 1.
This example shows how to map the CoS values 0 and 1 to standard transmit queue 1/threshold 1 for Fast Ethernet port 5/36:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/36 Router(config-if)# wrr-queue cos-map 1 1 0 1 Router(config-if)# end Router#

Router# show queueing interface fastethernet 5/36 | begin queue thresh cos-map queue thresh cos-map --------------------------------------1 1 0 1 1 2 2 3 2 1 4 5 2 2 6 7 <...Output Truncated...> Router#
41-106
OL-3999-08
Chapter 41
Mapping CoS Values to Strict-Priority Queues

To map CoS values to the receive and transmit strict-priority queues, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the interface to configure. Maps CoS values to the receive and transmit strict-priority queues. Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
Router(config-if)# priority-queue cos-map queue_# cos1 [cos2 [cos3 [cos4 [cos5 [cos6 [cos7 [cos8]]]]]]] Router(config-if)# no priority-queue cos-map
Step 3 Step 4

1
slot/port
When mapping CoS values to the strict-priority queues, note the following information:

The queue number is always 1. You can enter up to 8 CoS values to map to the queue. When used, the priority-queue cos-map command changes both ingress and egress priority queue CoS mapping.
This example shows how to map CoS value 7 to the strict-priority queues on Gigabit Ethernet port 1/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# priority-queue cos-map 1 7 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/1 <...Output Truncated...> Transmit queues [type = 1p2q2t]: <...Output Truncated...> queue thresh cos-map --------------------------------------1 1 0 1 1 2 2 3 2 1 4 2 2 6 3 1 5 7 Receive queues [type = 1p1q4t]: <...Output Truncated...> queue thresh cos-map --------------------------------------1 1 0 1 1 2 2 3 1 3 4 6 1 4 7 2 1 5 <...Output Truncated...> Router#
41-107
Configuring PFC QoS
Mapping CoS Values to Tail-Drop Thresholds on 1q4t/2q2t LAN Ports
Note
Enter the show queueing interface {ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port | include type command to see the queue structure of a port. On 1q4t/2q2t LAN ports, the receive- and transmit-queue tail-drop thresholds have this relationship:

Receive queue 1 (standard) threshold 1 = transmit queue 1 (standard low priority) threshold 1 Receive queue 1 (standard) threshold 2 = transmit queue 1 (standard low priority) threshold 2 Receive queue 1 (standard) threshold 3 = transmit queue 2 (standard high priority) threshold 1 Receive queue 1 (standard) threshold 4 = transmit queue 2 (standard high priority) threshold 2
To map CoS values to tail-drop thresholds, perform this task: Command

Step 1 Step 2
1
Purpose
slot/port
Selects the interface to configure. Maps CoS values to a tail-drop threshold.
Router(config-if)# wrr-queue cos-map transmit_queue_# threshold_# cos1 [cos2 [cos3 [cos4 [cos5 [cos6 [cos7 [cos8]]]]]]] Router(config-if)# no wrr-queue cos-map Router(config-if)# end Router# show queueing interface type 1.
1
Reverts to the default mapping. Exits configuration mode. Verifies the configuration.
slot/port
When mapping CoS values to a tail-drop threshold, note the following information:

Use the transmit queue and threshold numbers. Queue 1 is the low-priority standard transmit queue. Queue 2 is the high-priority standard transmit queue. There are two thresholds in each queue. Enter up to 8 CoS values to map to the threshold.
This example shows how to map the CoS values 0 and 1 to standard transmit queue 1/threshold 1 for Fast Ethernet port 5/36:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/36 Router(config-if)# wrr-queue cos-map 1 1 0 1 Router(config-if)# end Router#

Router# show queueing interface fastethernet 5/36 | begin queue thresh cos-map queue thresh cos-map --------------------------------------1 1 0 1 1 2 2 3 2 1 4 5 2 2 6 7 <...Output Truncated...> Router#
41-108
OL-3999-08
Chapter 41
Allocating Bandwidth Between Standard Transmit Queues

The switch transmits frames from one standard queue at a time using one of these dequeuing algorithms, which use percentages or weights to allocate relative bandwidth to each queue as it is serviced in a round-robin fashion:

Shaped round robin (SRR)SRR allows a queue to use only the allocated bandwidth. Supported as an option on Supervisor Engine 32 SFP 1p3q8t ports and on 1p7q4t ports. Deficit weighted round robin (DWRR)DWRR keeps track of any lower-priority queue under-transmission caused by traffic in a higher-priority queue and compensates in the next round. DWRR is the dequeuing algorithm on 1p3q1t, 1p2q1t , 1p3q8t , 1p7q4t, and 1p7q8t ports.
Note
You configure DWRR ports with the same commands that you use on WRR ports.
Weighted round robin (WRR)WRR allows a queue to use more than the allocated bandwidth if the other queues are not using any, up to the total bandwidth of the port. WRR is the dequeuing algorithm on all other ports.
With Release 12.2(18)SXF and later releases, you can enter percentages or weights to allocate bandwidth. With releases earlier than Release 12.2(18)SXF, you enter weights to allocate bandwidth. The higher the percentage or weight that is assigned to a queue, the more transmit bandwidth is allocated to it. If you enter weights, the ratio of the weights divides the total bandwidth of the queue. For example, for three queues on a Gigabit Ethernet port, weights of 25:25:50 provide this division:

Queue 1250 Mbps Queue 2250 Mbps Queue 3500 Mbps
Note
The actual bandwidth allocation depends on the granularity that the port hardware applies to the configured percentages or weights.
41-109
Configuring PFC QoS
To allocate bandwidth between standard transmit queues, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# wrr-queue [bandwidth | shape] percent low_priority_queue_percentage [intermediate_priority_queue_percentages] high_priority_queue_percentage
Purpose Selects the interface to configure. Allocates bandwidth between standard transmit queues:

Enter the bandwidth keyword to configure DWRR or WRR. Enter the shape keyword to configure SRR. Use of SRR prevents use of the strict priority queue. To configure SRR, any CoS or DSCP values mapped to a strict-priority queue must be remapped to a standard queue (see the Mapping QoS Labels to Queues and Drop Thresholds section on page 41-99). Percentages should add up to 100. You must enter percentages for all the standard transmit queues on the port. (Supported with Release 12.2(18)SXF and later releases.) The valid values for weight range from 1 to 255. You must enter weights for all the standard transmit queues on the port.
Or:
Router(config-if)# wrr-queue [bandwidth | shape] low_priority_queue_weight [intermediate_priority_queue_weights] high_priority_queue_weight
Router(config-if)# no wrr-queue [bandwidth | shape]
Reverts to the default bandwidth allocation. Exits configuration mode.
Step 3 Step 4

1
slot/port
This example shows how to allocate a 3-to-1 bandwidth ratio for Gigabit Ethernet port 1/2:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/2 Router(config-if)# wrr-queue bandwidth 3 1 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/2 | include bandwidth WRR bandwidth ratios: 3[queue 1] 1[queue 2] Router#
41-110
OL-3999-08
Chapter 41
Setting the Receive-Queue Size Ratio

You can set the size ratio between the standard receive queues on 2q8t, 8q4t, and 8q8t ports and between the strict-priority and standard receive queues on 1p1q0t or 1p1q8t ports. To set the size ratio between the receive queues, perform this task: Command
Step 1 Step 2
Router(config)# interface {fastethernet | tengigabitethernet} slot/port Router(config-if)# rcv-queue queue-limit low_priority_queue_weight [intermediate_priority_queue_weights] high_priority_queue_weight
Purpose Selects the interface to configure. Sets the size ratio between the receive queues.
Or:
Router(config-if)# rcv-queue queue-limit standard_queue_weight strict_priority_queue_weight Router(config-if)# no rcv-queue queue-limit
Reverts to the default size ratio. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show queueing interface {fastethernet | tengigabitethernet} slot/port
When setting the receive-queue size ratio, note the following information:

The rcv-queue queue-limit command configures ports on a per-ASIC basis. Estimate the mix of differing priority traffic on your network (for example, 80 percent standard traffic and 20 percent strict-priority traffic). Use the estimated percentages as queue weights. Valid values are from 1 to 100 percent, except on 1p1q8t ports, where valid values for the strict priority queue are from 3 to 100 percent.
This example shows how to set the receive-queue size ratio for Fast Ethernet port 2/2:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 2/2 Router(config-if)# rcv-queue queue-limit 75 15 Router(config-if)# end Router#

Router# show queueing interface fastethernet 2/2 | include queue-limit queue-limit ratios: 75[queue 1] 15[queue 2] Router#
41-111
Configuring PFC QoS
Configuring the Transmit-Queue Size Ratio

To configure the transmit-queue size ratio, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the interface to configure. Configures the queue size ratio between transmit queues.
Router(config-if)# wrr-queue queue-limit low_priority_queue_weight [intermediate_priority_queue_weights] high_priority_queue_weight Router(config-if)# priority-queue queue-limit strict_priority_queue_weight Router(config-if)# end Router# show queueing interface type1 slot/port 1.
Step 3
Configures the strict priority queue size.

Note
Not supported on all switching modules.
Step 4 Step 5
When configuring the transmit-queue size ratio between transmit queues, note the following information:

The wrr-queue queue-limit command is not supported on 1p3q1t ports. For ports that have an egress strict priority queue:
With Release 12.2(18)SXF2 and later releases, you can enter the priority-queue queue-limit
interface command to set the size of the egress strict priority queue on these switching modules: WS-X6502-10GE ( 1p2q1t) WS-X6148A-GE-TX ( 1p3q8t) WS-X6148-RJ-45 (1p3q8t) WS-X6148-FE-SFP (1p3q8t) WS-X6748-SFP (1p3q8t) WS-X6724-SFP (1p3q8t) WS-X6748-GE-TX (1p3q8t) WS-X6704-10GE ( 1p7q4t) WS-SUP32-10GE-3B (1p3q8t) WS-SUP32-GE-3B (1p3q8t) WS-X6708-10GE ( 1p7q4t)
With releases earlier than Release 12.2(18)SXF2 and for other modules, PFC QoS sets the
egress strict-priority queue size equal to the high-priority queue size.

Estimate the mix of low priority-to-high priority traffic on your network (for example, 80 percent low-priority traffic and 20 percent high-priority traffic). Use the estimated percentages as queue weights. You must enter weights for all the standard transmit queues on the interface (2, 3, or 7 weights). Valid values are from 1 to 100 percent, except on 1p2q1t egress LAN ports, where valid values for the high priority queue are from 5 to 100 percent.
41-112
OL-3999-08
Chapter 41
Configuring PFC QoS Common QoS Scenarios
This example shows how to set the transmit-queue size ratio for Gigabit Ethernet port 1/2:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/2 Router(config-if)# wrr-queue queue-limit 75 15 Router(config-if)# end Router#

Router# show queueing interface gigabitethernet 1/2 | include queue-limit queue-limit ratios: 75[queue 1] 25[queue 2] Router#
Common QoS Scenarios

This section provides sample configurations for some common QoS scenarios. If you already know how to configure PFC QoS for your network or if you need specific configuration information, see the other sections of this chapter. The scenarios in this section are based on a sample network that is described in the Sample Network Design Overview section on page 41-113. This section uses this sample network to describe some regularly used QoS configurations. These sections describe some common QoS scenarios:

Sample Network Design Overview, page 41-113 Classifying Traffic from PCs and IP Phones in the Access Layer, page 41-114 Accepting the Traffic Priority Value on Interswitch Links, page 41-117 Prioritizing Traffic on Interswitch Links, page 41-118 Using Policers to Limit the Amount of Traffic from a PC, page 41-121
Sample Network Design Overview

This sample network is based on a traditional campus network architecture that uses Catalyst 6500 series switches in the access, distribution, and core layers. The access layer provides 10/100 Ethernet service to desktop users. The network has Gigabit Ethernet links from the access layer to the distribution layer and Gigabit or 10 Gigabit Ethernet links from the distribution layer to the core layer. This is the basic port configuration:
Access Layer
switchport mode access switchport access vlan 10 switchport voice vlan 110
Distribution and Core Interswitch Links

switchport mode trunk
41-113
Chapter 41 Common QoS Scenarios
Configuring PFC QoS
These are the three traffic classes in the sample network:

Voice High-priority application traffic Best-effort traffic
The QoS configuration described in this section identifies and prioritizes each of these traffic classes.
Note
If your network requires more service levels, PFC QoS supports up to 64 traffic classes. These QoS scenarios describe the following three fundamental QoS configurations, which are often a general part of QoS deployment:

Classifying traffic from PCs and IP phones in the access layer Accepting the traffic priority value on interswitch links between layers Prioritizing traffic on interswitch links between layers
These QoS scenarios assume that the network carries only IP traffic and use the IP DSCP values to assign traffic priority. These QoS scenarios do not directly use IP type of service (ToS) or Ethernet 802.1p class of service (CoS). IP packets can carry a priority value, which can be set at various points within the network topology. Best-practice design recommendations are to classify and mark traffic as close to the source of the traffic as possible. If traffic priorities are set correctly at the edge, then intermediate hops do not have to perform detailed traffic identification. Instead, they can administer QoS policies based on these previously set priority values. This approach simplifies policy administration.
Note
You should develop a QoS deployment strategy for assigning packet priorities to your particular network traffic types and applications. For more information on QoS guidelines, refer to RFC 2597 and RFC 2598 as well as the various QoS design guides published by Cisco Systems, Inc. Do not enable PFC QoS globally and leave all other PFC QoS configuration at default values. When you enable PFC QoS globally, it uses its default values. These are two problems that exist with the PFC QoS default configuration:
With PFC QoS globally enabled, the default trust state of the Ethernet ports in the system is
untrusted. The untrusted port state sets the QoS priority of all traffic flowing through the switch to the port CoS value (zero by default): all traffic will be zero-priority traffic.
With PFC QoS globally enabled, the port buffers are allocated into CoS-based queues and only
part of the buffer is available for zero-priority traffic: zero-priority traffic has less buffer available than when PFC QoS is disabled. These problems with the PFC QoS default configuration can have a negative effect on network performance.
Classifying Traffic from PCs and IP Phones in the Access Layer

The access layer switches have a PC daisy-chained to an IP phone on a 100 Mbps link. This section describes how to classify voice traffic from the phone and data traffic from the PC so that they have different priorities.
41-114
OL-3999-08
Chapter 41
This is the QoS classification scheme for the traffic arriving on an access layer port:

Voice traffic: DSCP 46 (highest priority) Voice signaling traffic: DSCP 24 (medium priority) PC SAP traffic: DSCP 25 (medium priority) All other PC traffic: DSCP 0 (best effort) High priority for voice traffic Medium priority for voice signaling and important application traffic Low priority for the remaining traffic
This classification strategy provides a way to support three different classes of service on the network:

You can alter this model to fit other network environments. PFC QoS can trust received priorities or assign new priorities by applying a QoS policy to the traffic. You configure a QoS policy using the Modular QoS CLI (MQC). In the access switches, the traffic is identified using ACLs, which differentiate the various traffic types entering the port. Once identified, a QoS policy marks the traffic with the appropriate DSCP value. These assigned DSCP values will be trusted when the traffic enters the distribution and core switches. The port on the access switch where the phone and PC are attached has been configured for a voice VLAN (VLAN 110), which is used to separate the phone traffic (subnet 10.1.110.0/24) from the PC traffic (10.1.10.0/24). The voice VLAN subnet uniquely identifies the voice traffic. The UDP and TCP port numbers identify the different applications. This is the access port access control list (ACL) configuration:
Identify the Voice Traffic from an IP Phone (VVLAN)
ip access-list extended CLASSIFY-VOICE permit udp 10.1.110.0 0.0.0.255 any range 16384 32767
Identify the Voice Signaling Traffic from an IP Phone (VVLAN)

ip access-list extended CLASSIFY-VOICE-SIGNAL permit udp 10.1.110.0 0.0.0.255 any range 2000 2002
Identify the SAP Traffic from the PC (DVLAN)

ip access-list extended CLASSIFY-PC-SAP permit tcp 10.1.10.0 0.0.0.255 any range 3200 3203 permit tcp 10.1.10.0 0.0.0.255 any eq 3600 any ip access-list extended CLASSIFY-OTHER permit ip any any
The next step in configuring the QoS policy is to define the class maps. These class maps associate the identifying ACLs with the QoS actions that you want to perform (marking, in this case). This is the syntax for the class maps:
class-map match class-map match class-map match class-map match match-all CLASSIFY-VOICE access-group name CLASSIFY-VOICE match-all CLASSIFY-VOICE-SIGNAL access-group name CLASSIFY-VOICE-SIGNAL match-all CLASSIFY-PC-SAP access-group name CLASSIFY-PC-SAP match-all CLASSIFY-OTHER access-group name CLASSIFY-OTHER
41-115
Configuring PFC QoS
After you create the class maps, create a policy map that defines the action of the QoS policy so that it sets a particular DSCP value for each traffic type or traffic class. This example creates one policy map (called IPPHONE-PC), and all the class maps are included in that single policy map, with an action defined in each class map. This is the syntax for the policy map and class maps:
policy-map IPPHONE-PC class CLASSIFY-VOICE set dscp ef class CLASSIFY-VOICE-SIGNAL set dscp cs3 class CLASSIFY-PC-SAP set dscp 25 class CLASSIFY-OTHER set dscp 0
At this point, the QoS policy defined in the policy map still has not taken effect. After you configure a policy map, you must apply it to an interface for it to affect traffic. You use the service-policy command to apply the policy map. Remember that an input service policy can be applied to either a port or to VLAN interfaces, but that an output service policy can only be applied to VLAN interfaces (only the PFC3 supports output policies). In this example, you apply the policy as an input service-policy to each interface that has a PC and IP phone attached. This example uses port-based QoS, which is the default for Ethernet ports.
interface FastEthernet5/1 service-policy input IPPHONE-PC
A QoS policy now has been successfully configured to classify the traffic coming in from both an IP phone and a PC. To ensure that the policy maps are configured properly, enter this command:
Router# show policy-map interface fastethernet 5/1 FastEthernet5/1 Service-policy input:IPPHONE-PC class-map:CLASSIFY-VOICE (match-all) Match:access-group name CLASSIFY-VOICE set dscp 46: class-map:CLASSIFY-PC-SAP (match-all) Match:access-group name CLASSIFY-PC-SAP set dscp 25: class-map:CLASSIFY-OTHER (match-all) Match:access-group name CLASSIFY-OTHER set dscp 0: class-map:CLASSIFY-VOICE-SIGNAL (match-all) Match:access-group name CLASSIFY-VOICE-SIGNAL set dscp 24:
To ensure that the port is using the correct QoS mode, enter this command:
Router# show queueing interface gigabitethernet 5/1 | include Port QoS Port QoS is enabled
To ensure that the class map configuration is correct, enter this command:
Router# show class-map Class Map match-all CLASSIFY-OTHER (id 1) Match access-group name CLASSIFY-OTHER
41-116
OL-3999-08
Chapter 41
Class Map match-any class-default (id 0) Match any Class Map match-all CLASSIFY-PC-SAP (id 2) Match access-group name CLASSIFY-PC-SAP Class Map match-all CLASSIFY-VOICE-SIGNAL (id 4) Match access-group name CLASSIFY-VOICE-SIGNAL Class Map match-all CLASSIFY-VOICE (id 5) Match access-group name CLASSIFY-VOICE
To monitor the byte statistics for each traffic class, enter this command:
Router# show mls qos ip gig 5/1 [In] Policy map is IPPHONE-PC [Out] Default. QoS Summary [IP]: (* - shared aggregates, Mod - switch module) Int Mod Dir Class-map DSCP Agg Id Trust Fl Id AgForward-By AgPoliced-By
-----------------------------------------------------------------------------------Gi5/1 5 In CLASSIFY-V 46 1 No 0 0 0 Gi5/1 5 In CLASSIFY-V 24 2 No 0 0 0 Gi5/1 5 In CLASSIFY-O 0 3 No 0 0 0 Gi5/1 5 In CLASSIFY-P 25 4 No 0 0 0 Router#
Accepting the Traffic Priority Value on Interswitch Links

The previous section described how to configure the marking operation. This section describes how the upstream devices will use the packet marking. You must decide whether the incoming traffic priority should be honored or not. To implement the decision, you configure the trust state of the port. When traffic arrives on a port that is set not to trust incoming traffic priority settings, the priority setting of the incoming traffic is rewritten to the lowest priority (zero). Traffic that arrives on an interface that is set to trust incoming traffic priority settings retains its priority setting. Examples of ports on which it might be valid to trust incoming priority settings are ports that are connected to IP phones and other IP voice devices, video devices, or any device that you trust to send frames with a valid predetermined priority. If you know that appropriate marking is completed when traffic first enters the network, you may also want to set uplink interfaces to trust the incoming priority settings. Configure ports that are connected to workstations or any devices that do not send all traffic with a predetermined valid priority as untrusted (the default). In the previous example, you configured QoS to properly mark the voice, SAP, and other best effort traffic at the access layer. This example configures QoS to honor those values as the traffic passes through other network devices by configuring the interswitch links to trust the packet DSCP values. The previous example had several different traffic classes entering a port and selectively applied different QoS policies to the different traffic types. The configuration was done with the MQC QoS policy syntax, which allows you to apply different marking or trust actions to the different traffic classes arriving on a port.
41-117
Configuring PFC QoS
If you know that all traffic entering a particular port can be trusted (as is the case on access-distribution or distribution-core uplink ports), you can use the port trust configuration. Using port trust does not provide any support for different traffic types entering a port, but it is a much simpler configuration option. This is the command syntax for port trust:
interface gigabitethernet 5/1 mls qos trust dscp
With ports configured to trust received DSCP, the DSCP value for the traffic leaving the switch will be the same as the DSCP value for the traffic entering the trusted ports. After you have configured the trust state, you can use the following commands to verify that the setting has taken effect:
Router# show queueing interface gigabitethernet 5/1 | include Trust Trust state:trust DSCP
Prioritizing Traffic on Interswitch Links

This section describes how the switches operate using trusted values. One of the most fundamental principles of QoS is to protect high-priority traffic in the case of oversubscription. The marking and trusting actions described in the Classifying Traffic from PCs and IP Phones in the Access Layer section on page 41-114 and the Accepting the Traffic Priority Value on Interswitch Links section on page 41-117 prepare the traffic to handle oversubscription, but they do not provide different levels of service. To achieve differing levels of service, the networking device must have an advanced scheduling algorithm to prioritize traffic as it sends traffic from a particular interface. This scheduling function is responsible for transmitting the high-priority traffic with greater frequency than the low-priority traffic. The net effect is a differentiated service for the various traffic classes. These two concepts are fundamental to the provision of differentiated service for various traffic classes:

Assigning the traffic to a particular queue Setting the queue scheduling algorithm
Once QoS has been enabled, default values are applied for both of these features. For many networks, these default values are sufficient to differentiate the network traffic. For other networks, theses values might need to be adjusted to produce the desired result. Only in rare cases should there be a need for significant changes from the default settings for these features. The Catalyst 6500 series switch Ethernet modules support a variety of queue structures, ranging from a single queue up to an eight-queue architecture. You can compare the queue structure to a group of traffic lanes used to service different traffic types. For example, the police get prioritized treatment when driving down the freeway so that they can get to accidents or crime scenes quickly. In an analogous way, the voice traffic on an IP network requires the same prioritized treatment. The switch uses the queue structure to provide these lanes of differentiated service. The exact queue type is specific to the Ethernet module that you are working with. This example uses a module that has four transmit queues, described as 1p3q8t, which indicates:

One strict priority queue (1p) Three regular queues supporting Weighted-Round Robin scheduling (3q), each with eight WRED thresholds (8t, not discussed here)
Catalyst 6500 series switch Ethernet modules also have input queue structures, but these are used less often, and because there probably will not be congestion within the switch fabric, this example does not include them.
41-118
OL-3999-08
Chapter 41
To assign traffic to these queues, you need to configure a mapping of priority values to queues. QoS uses the DSCP-to-CoS map to map the 64 possible outgoing DSCP values to the eight possible 802.1p values, and then uses a CoS-to-queue map to map the CoS values to queues. When the packet enters the switch, QoS is either configured to classify and mark the packet with a configured DSCP value (as in the Classifying Traffic from PCs and IP Phones in the Access Layer section on page 41-114) or to trust the packets incoming DSCP value (as in the Accepting the Traffic Priority Value on Interswitch Links section on page 41-117). These options determine the packets priority as it leaves the switch. This example shows how to display the DSCP-to-CoS mapping:
Router# show mls qos maps dscp-cos Dscp-cos map: d1 : d2 0 1 2 3 4 5 6 7 8 9 ------------------------------------0 : 00 00 00 00 00 00 00 00 01 01 1 : 01 01 01 01 01 01 02 02 02 02 2 : 02 02 02 02 03 03 03 03 03 03 3 : 03 03 04 04 04 04 04 04 04 04 4 : 05 05 05 05 05 05 05 05 06 06 5 : 06 06 06 06 06 06 07 07 07 07 6 : 07 07 07 07 Router# (dscp= d1d2)
The example marked the voice traffic with a DSCP value of 46. You can use the command output to translate DSCP 46 to CoS 5. You can use the command output to translate the other marked DSCP values to CoS values. You can make changes to this mapping table to suit the needs of your particular network. Only minor changes are typically necessary; this example does not make any changes. For queueing purposes, the configuration derives a CoS value from the outgoing DSCP value. This CoS value is used for queue assignment even if the outgoing port is an access port (that is, not a trunk port). However, there will be no 802.1q VLAN tag transmitted on the network if the outgoing port is an access port. Map each derived CoS value to the queue structure. This example shows how to display the default CoS-to-queue mapping, which shows the queue to which each of the eight CoS values is mapped:
Router# show queueing interface gigabitethernet 5/1 | begin cos-map queue thresh cos-map --------------------------------------1 1 0 1 2 1 1 3 1 4 1 5 1 6 1 7 1 8 2 1 2 2 2 3 4 2 3 2 4 2 5 2 6 2 7 2 8 3 1 6 7 3 2 3 3 3 4
41-119
Configuring PFC QoS
3 3 3 3 4
5 6 7 8 1
<output truncated>
You want voice traffic mapped to the strict priority queue, which is queue 4 on 1p3q8t ports. The example maps the DSCP 46 voice traffic to CoS 5, which means that you want the CoS 5 traffic to be mapped to the strict priority queue, and you can use the output of the show queueing interface command to verify that CoS 5 traffic is mapped to the strict priority queue. This is a list of the queue mappings for all of the traffic types in this example: Traffic Type Voice Voice signaling PC SAP Other traffic DSCP 46 24 25 0 CoS (from DSCP-to-CoS map) 5 3 3 0 Output Queue Strict Priority Queue 2, Threshold 2 Queue 2, Threshold 2 Queue 1, Threshold 1
Traffic that is transmitted through the switch is directed to these different queues (or traffic lanes) based on priority. Because there are more CoS values (zero through seven) than egress queues (three per interface in this example), there are drop thresholds in each standard (that is, nonstrict priority) queue. When more than one CoS value is assigned to a given queue, different drop thresholds can be assigned to these CoS values to distinguish between the different priorities. The thresholds specify the maximum percentage of the queue that traffic with a given CoS value can use before additional traffic with that CoS value is dropped. The example only uses three QoS values (high, medium, and low), so you can assign each CoS value to a separate queue and use the default 100-percent drop thresholds. You can change the DCSP-to-CoS and CoS-to-queue mapping to suit the needs of your particular network. Only minor changes are typically necessary, and this example includes no changes. If your network requires different mapping, see the Mapping CoS Values to Standard Transmit-Queue Thresholds section on page 41-106. Now you understand how traffic is assigned to the available queues on the output ports of the switch. The next concept to understand is how the queue weights operate, which is called the queue scheduling algorithm. On the Catalyst 6500 series switch, the scheduling algorithms used on the LAN switching modules are strict priority (SP) queueing and weighted round robin (WRR) queueing. These algorithms determine the order, or the priority, that the various queues on a port are serviced. The strict priority queueing algorithm is simple. One queue has absolute priority over all of the other queues. Whenever there is a packet in the SP queue, the scheduler will service that queue, which ensures the highest possibility of transmitting the packet and the lowest possible latency in transmission even in periods of congestion. The strict priority queue is ideal for voice traffic because voice traffic requires the highest priority and lowest latency on a network, and it also is a relatively low-bandwidth traffic type, which means that voice traffic is not likely to consume all available bandwidth on a port. You would not want to assign a high-bandwidth application (for example, FTP) to the strict priority queue because the FTP traffic could consume all of the bandwidth available to the port, starving the other traffic classes.
41-120
OL-3999-08
Chapter 41
The WRR algorithm uses relative weights that are assigned to the WRR queues. If there are three queues and their weights are 100:150:200 (which are the default settings), then queue 1 gets only 22 percent of the available bandwidth, queue 2 gets 33 percent, and queue 3 gets 45 percent. With WRR, none of the queues are restricted to these percentages. If queue 2 and queue 3 do not have any traffic, queue 1 can use all available bandwidth. In this example, queue 1 has a lower priority than queue 2, and queue 2 has a lower priority than queue 3. The low-priority traffic (phone-other and PC-other) maps to queue 1, and the medium-priority traffic (voice-signaling and PC-SAP) maps to queue 2. The strict-priority queue does not require any configuration after traffic has been mapped to it. The WRR queues have a default bandwidth allocation that might be sufficient for your network; if it is not, then you can change the relative weights to suit your traffic types (see the Allocating Bandwidth Between Standard Transmit Queues section on page 41-109). The best way to verify that the switch is handling oversubscription is to ensure that there is minimal packet drop. Use the show queueing interface command to determine where that packet loss is happening. This command displays the number of dropped packets for each queue.
Using Policers to Limit the Amount of Traffic from a PC

Rate limiting is a useful way of ensuring that a particular device or traffic class does not consume more bandwidth than expected. On the Catalyst 6500 series switch Ethernet ports, the supported rate-limiting method is called policing. Policing is implemented in the PFC hardware with no performance impact. A policer operates by allowing the traffic to flow freely as long as the traffic rate remains below the configured transmission rate. Traffic bursts are allowed, provided that they are within the configured burst size. Any traffic that exceeds the configured rate and burst can be either dropped or marked down to a lower priority. The benefit of policing is that it can constrain the amount of bandwidth that a particular application consumes, which helps ensure quality of service on the network, especially during abnormal network conditions such as a virus or worm attack. This example focuses on a basic per-interface aggregate policer applied to a single interface in the inbound direction, but you can use other policing options to achieve this same result. The configuration of a policer is similar to the marking example provided in the Classifying Traffic from PCs and IP Phones in the Access Layer section on page 41-114 because policing uses the same ACL and MQC syntax. The syntax in that example created a class-map to identify the traffic and then created a policy-map to specify how to mark the traffic. The policing syntax is similar enough that we can use the marking example ACL and modify the marking example class map by replacing the set dscp command with a police command. This example reuses the CLASSIFY-OTHER class-map to identify the traffic with a modified IPPHONE-PC policy map to police the matched traffic to a maximum of 50 Mbps, while continuing to mark the traffic that conforms to this rate. The class maps and the ACL and class-map commands that are used to identify the other traffic are included below for reference; no changes have been made.
ACL commands:
ip access-list extended CLASSIFY-OTHER permit ip any any
Class map commands:

class-map match-all CLASSIFY-OTHER match access-group name CLASSIFY-OTHER
41-121
Configuring PFC QoS
The difference between this policer configuration and the marking configuration is the policy-map action statements. The marking example uses the set dscp command to mark the traffic with a particular DSCP value. This policing example marks the CLASSIFY-OTHER traffic to a DSCP value of zero and polices that traffic to 50 Mbps. To do this, replace the set dscp command with a police command. The police command allows a marking action to take place: it marks all traffic below the 50 Mbps limit to DSCP 0 and drops any traffic above the 50 Mbps threshold. This is the modified IPPHONE-PC policy map, which includes the police command:
policy-map IPPHONE-PC class CLASSIFY-OTHER police 50000000 1562500 conform-action set-dscp-transmit default exceed-action drop
These are the police command parameters:

The 50000000 parameter defines the committed information rate (CIR) for traffic allowed in this traffic class. This example configures the CIR to be 50 Mbps. The 1562500 parameter defines the CIR burst size for traffic in this traffic class; this example uses a default maximum burst size. Set the CIR burst size to the maximum TCP window size used on the network. The conform action keywords define what the policer does with CLASSIFY-OTHER packets transmitted when the traffic level is below the 50Mbps rate. In this example, set-dscp-transmit default applies DSCP 0 to those packets. The exceed action defines what the policer does with CLASSIFY-OTHER packets transmitted when the traffic level is above the 50 Mbps CIR. In this example, exceed action drop drops those packets.
This is a basic example of a single rate per-interface aggregate policer. The Supervisor Engine 2 and Supervisor Engine 720 forwarding engines also support a dual-rate policer for providing both CIR and peak information rate (PIR) granularity. Attach the policy map to the appropriate interface using the service-policy input command:
interface FastEthernet5/1 service-policy input IPPHONE-PC
To monitor the policing operation, use these commands:

show policy-map interface fastethernet 5/1 show class-map show mls qos ip fastethernet 5/1
41-122
OL-3999-08
Chapter 41
Configuring PFC QoS PFC QoS Glossary
PFC QoS Glossary

This section defines some of the QoS terminology used in this chapter:
BuffersA storage area used for handling data in transit. Buffers are used in internetworking to compensate for differences in processing speed between network devices. Bursts of data can be stored in buffers until they can be handled by slower processing devices. Sometimes referred to as a packet buffer. Class of Service (CoS) is a Layer 2 QoS label carried in three bits of either an ISL, 802.1Q, or 802.1p header. CoS values range between zero and seven.
Layer 2 ISL frame ISL header (26 bytes) Encapsulated frame 1... (24.5 KB) 3 bits used for CoS Layer 2 802.1Q and 802.1p frame Preamble Start frame delimiter DA SA Tag PT Data FCS
144803
FCS (4 bytes)
3 bits used for CoS (user priority)
Classification is the process used for selecting traffic to be marked for QoS. Congestion avoidance is the process by which PFC QoS reserves ingress and egress LAN port capacity for Layer 2 frames with high-priority Layer 2 CoS values. PFC QoS implements congestion avoidance with Layer 2 CoS value-based drop thresholds. A drop threshold is the percentage of queue buffer utilization above which frames with a specified Layer 2 CoS value is dropped, leaving the buffer available for frames with higher-priority Layer 2 CoS values. Differentiated Services Code Point (DSCP) is a Layer 3 QoS label carried in the six most-significant bits of the ToS byte in the IP header. DSCP ranges between 0 and 63.
Layer 3 IPv4 packet Len ID Offset TTL Proto FCS IP-SA IP-DA Data
144804 144804
Version length
ToS (1 byte)
3 bits for IP precedence
Frames carry traffic at Layer 2. Layer 2 frames carry Layer 3 packets. IP Precedence is a Layer 3 QoS label carried in the three most-significant bits of the ToS byte in the IP header. IP precedence ranges between zero and seven.
Layer 3 IPv4 packet Version length ToS (1 byte) Len ID Offset TTL Proto FCS IP-SA IP-DA Data
3 bits for IP precedence
LabelsSee QoS labels.
41-123
Chapter 41 PFC QoS Glossary
Configuring PFC QoS
Marking is the process of setting a Layer 3 DSCP value in a packet; in this publication, the definition of marking is extended to include setting Layer 2 CoS values. Marking changes the value of a label. Packets carry traffic at Layer 3. Policing is limiting bandwidth used by a flow of traffic. Policing is done on the PFC and Distributed Forwarding Cards (DFCs). Policing can mark or drop traffic. QueuesQueues are allocations of buffer space used to temporarily store data on a port. QoS labelsPFC QoS uses CoS, DSCP, and IP Precedence as QoS labels. QoS labels are prioritization values carried in Layer 3 packets and Layer 2 frames. Scheduling is the assignment of Layer 2 frames to a queue. PFC QoS assigns frames to a queue based on Layer 2 CoS values. Shaped round robin (SRR) is a dequeuing algorithm. Threshold Percentage of queue capacity above which traffic is dropped. Type of Service (ToS) is a one-byte field that exists in an IP version 4 header that is used to specify the priority value applied to the packet. The ToS field consists of eight bits. The first three bits specify the IP precedence value, which can range from zero to seven, with zero being the lowest priority and seven being the highest priority. The ToS field can also be used to specify a DSCP value. DSCP is defined by the six most significant bits of the ToS. DSCP values can range from 0 to 63. Weightratio of bandwidth allocated to a queue.
Tip
41-124
OL-3999-08
C H A P T E R
42
Configuring PFC3BXL or PFC3B Mode MPLS QoS

This chapter describes how to configure PFC3BXL or PFC3B mode Multiprotocol Label Switching (MPLS) quality of service (QoS) on the Catalyst 6500 series switches.
Note
PFC3BXL or PFC3B mode MPLS QoS extends to MPLS traffic the PFC QoS features described in Chapter 41, Configuring PFC QoS. This chapter provides supplemental information on PFC3BXL or PFC3B mode MPLS QoS features. Be sure that you understand the PFC QoS features before you read this chapter. All policing and marking available for PFC3BXL or PFC3B mode MPLS QoS are managed from the modular QoS command-line interface (CLI). The modular QoS CLI (MQC) is a command-line interface that allows you to define traffic classes, create and configure traffic policies (policy maps), and then attach those traffic policies to interfaces. A detailed description of the modular QoS CLI can be found in the Cisco IOS Quality of Service Solutions Configuration Guide, Release 12.2 at this URL: http://www.cisco.com/en/US/docs/ios/12_2/qos/configuration/guide/fqos_c.html

Terminology, page 42-2 PFC3BXL or PFC3B Mode MPLS QoS Features, page 42-3 PFC3BXL or PFC3B Mode MPLS QoS Overview, page 42-5 PFC3BXL or PFC3B Mode MPLS QoS, page 42-5 Understanding PFC3BXL or PFC3B Mode MPLS QoS, page 42-8 PFC3BXL or PFC3B MPLS QoS Default Configuration, page 42-15 MPLS QoS Commands, page 42-16 PFC3BXL or PFC3B Mode MPLS QoS Restrictions and Guidelines, page 42-17 Configuring PFC3BXL or PFC3B Mode MPLS QoS, page 42-18 MPLS DiffServ Tunneling Modes, page 42-32
42-1
Chapter 42 Terminology
Configuring Short Pipe Mode, page 42-35 Configuring Uniform Mode, page 42-40
Tip
Terminology
This section defines some MPLS QoS terminology:
Class of Service (CoS) refers to three bits in either an Inter-Switch Link (ISL) header or an 802.1Q header that are used to indicate the priority of the Ethernet frame as it passes through a switched network. The CoS bits in the 802.1Q header are commonly referred to as the 802.1p bits. To maintain QoS when a packet traverses both Layer 2 and Layer 3 domains, the type of service (ToS) and CoS values can be mapped to each other. Classification is the process used for selecting traffic to be marked for QoS. Differentiated Services Code Point (DSCP) is the first six bits of the ToS byte in the IP header. DSCP is only present in an IP packet. E-LSP is a label switched path (LSP) on which nodes infer the QoS treatment for MPLS packets exclusively from the experimental (EXP) bits in the MPLS header. Because the QoS treatment is inferred from the EXP (both class and drop precedence), several classes of traffic can be multiplexed onto a single LSP (use the same label). A single LSP can support up to eight classes of traffic because the EXP field is a 3-bit field. The maximum number of classes would be less after reserving some values for control plane traffic or if some of the classes have a drop precedence associated with them. EXP bits define the QoS treatment (per-hop behavior) that a node should give to a packet. It is the equivalent of the DiffServ Code Point (DSCP) in the IP network. A DSCP defines a class and drop precedence. The EXP bits are generally used to carry all the information encoded in the IP DSCP. In some cases, however, the EXP bits are used exclusively to encode the dropping precedence. Frames carry traffic at Layer 2. Layer 2 frames carry Layer 3 packets. IP precedence is the three most significant bits of the ToS byte in the IP header. QoS tags are prioritization values carried in Layer 3 packets and Layer 2 frames. A Layer 2 CoS label can have a value ranging between zero for low priority and seven for high priority. A Layer 3 IP precedence label can have a value ranging between zero for low priority and seven for high priority. IP precedence values are defined by the three most significant bits of the 1-byte ToS byte. A Layer 3 DSCP label can have a value between 0 and 63. DSCP values are defined by the six most significant bits of the 1-byte IP ToS field. LERs (label edge routers) are devices that impose and dispose of labels upon packets; also referred to as Provider Edge (PE) routers. LSRs (label switching routers) are devices that forward traffic based upon labels present in a packet; also referred to as Provider (P) routers.
42-2
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS PFC3BXL or PFC3B Mode MPLS QoS Features
Marking is the process of setting a Layer 3 DSCP value in a packet. Marking is also the process of choosing different values for the MPLS EXP field to mark packets so that they have the priority that they require during periods of congestion. Packets carry traffic at Layer 3. Policing is limiting bandwidth used by a flow of traffic. Policing can mark or drop traffic.
PFC3BXL or PFC3B Mode MPLS QoS Features

QoS enables a network to provide improved service to selected network traffic. This section explains the following PFC3BXL or PFC3B mode MPLS QoS features, which are supported in an MPLS network:

MPLS Experimental Field, page 42-3 Trust, page 42-3 Classification, page 42-4 Policing and Marking, page 42-4 Preserving IP ToS, page 42-4 EXP Mutation, page 42-4 MPLS DiffServ Tunneling Modes, page 42-4
MPLS Experimental Field

Setting the MPLS experimental (EXP) field value satisfies the requirement of service providers who do not want the value of the IP precedence field modified within IP packets transported through their networks. By choosing different values for the MPLS EXP field, you can mark packets so that packets have the priority that they require during periods of congestion. By default, the IP precedence value is copied into the MPLS EXP field during imposition.You can mark the MPLS EXP bits with a PFC3BXL or PFC3B mode MPLS QoS policy.
Trust
For received Layer 3 MPLS packets, the PFC3BXL or PFC3B usually trusts the EXP value in the received topmost label. None of the following have any effect on MPLS packets:

Interface trust state Port CoS value Policy-map trust command
For received Layer 2 MPLS packets, the PFC3BXL or PFC3B can either trust the EXP value in the received topmost label or apply port trust or policy trust to the MPLS packets for CoS and egress queueing purposes.
42-3
Chapter 42 PFC3BXL or PFC3B Mode MPLS QoS Features
Classification
Classification is the process that selects the traffic to be marked. Classification accomplishes this by partitioning traffic into multiple priority levels, or classes of service. Traffic classification is the primary component of class-based QoS provisioning. The PFC3BXL or PFC3B make classification decisions based on the EXP bits in the received topmost label of received MPLS packets (after a policy is installed). See the Configuring a Class Map to Classify MPLS Packets section on page 42-20 for information.
Policing and Marking

Policing causes traffic that exceeds the configured rate to be discarded or marked down to a higher drop precedence. Marking is a way to identify packet flows to differentiate them. Packet marking allows you to partition your network into multiple priority levels or classes of service. The PFC3BXL or PFC3B mode MPLS QoS policing and marking features that you can implement depend on the received traffic type and the forwarding operation applied to the traffic. See Configuring a Policy Map section on page 42-23 for information.
Preserving IP ToS
The PFC3BXL or PFC3B automatically preserves the IP ToS during all MPLS operations including imposition, swapping, and disposition.You do not need to enter a command to save the IP ToS.
EXP Mutation
You can configure a named egress EXP mutation map to mutate the internal DSCP-derived EXP value before it is used as the egress EXP value. You can attach egress EXP mutation maps to these interface types:

Optical service module (OSM) ports LAN or OSM port subinterfaces Layer 3 VLAN interfaces Layer 3 LAN ports Layer 2 LAN ports (switchports) FlexWAN ports or subinterfaces
You cannot attach EXP mutation maps to these interface types:

For configuration information, see the Configuring PFC3BXL or PFC3B Mode MPLS QoS Egress EXP Mutation section on page 42-29.
MPLS DiffServ Tunneling Modes

The PFC3BXL or PFC3B uses MPLS DiffServ tunneling modes. Tunneling provides QoS transparency from one edge of a network to the other edge of the network. See the MPLS DiffServ Tunneling Modes section on page 42-32 for information.
42-4
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS PFC3BXL or PFC3B Mode MPLS QoS Overview
PFC3BXL or PFC3B Mode MPLS QoS Overview

PFC3BXL or PFC3B mode MPLS QoS enables network administrators to provide differentiated types of service across an MPLS network. Differentiated service satisfies a range of requirements by supplying for each transmitted packet the service specified for that packet by its QoS. Service can be specified in different ways, for example, using the IP precedence bit settings in IP packets.
Specifying the QoS in the IP Precedence Field

When you send IP packets from one site to another, the IP precedence field (the first three bits of the DSCP field in the header of an IP packet) specifies the QoS. Based on the IP precedence marking, the packet is given the treatment configured for that quality of service. If the service provider network is an MPLS network, then the IP precedence bits are copied into the MPLS EXP field at the edge of the network. However, the service provider might want to set QoS for an MPLS packet to a different value determined by the service offering. In that case, the service provider can set the MPLS EXP field. The IP header remains available for the customers use; the QoS of an IP packet is not changed as the packet travels through the MPLS network. For more information, see the MPLS DiffServ Tunneling Modes section on page 42-32.
PFC3BXL or PFC3B Mode MPLS QoS

This section describes how PFC3BXL or PFC3B mode MPLS QoS works. Figure 42-1 shows an MPLS network of a service provider that connects two sites of a customer network.
Figure 42-1 MPLS Network Connecting Two Sites of a Customers IP Network
MPLS network MPLS network
IP network
IP network
Host A CE1 PE1 P1 P2 PE2 CE2
Host B
Owned by service provider
The network is bidirectional, but for the purpose of this document the packets move left to right. In Figure 42-1, the symbols have the following meanings:

CE1Customer equipment 1 PE1Service provider ingress label edge router (LER) P1Label switch router (LSR) within the core of the network of the service provider P2LSR within the core of the network of the service provider
41867
42-5
Chapter 42 PFC3BXL or PFC3B Mode MPLS QoS
PE2service provider egress LER CE2Customer equipment 2
Note
PE1 and PE2 are at the boundaries between the MPLS network and the IP network. These sections describe LER and LSR operation in an MPLS network.

LERs at the Input Edge of an MPLS Network, page 42-6 LSRs in the Core of an MPLS Network, page 42-7 LERs at the Output Edge of an MPLS Network, page 42-7
Note
The QoS capabilities at the input interface differ depending on whether the input interface is a LAN port, a WAN port on an OSM, or a port adapter on a FlexWAN or Enhanced FlexWAN module. This section is for LAN ports. For information on OSMs, see the OSM Configuration Note, 12.2SX. For information on a FlexWAN or Enhanced FlexWAN module, see the FlexWAN and Enhanced FlexWAN Installation and Configuration Note.
LERs at the Input Edge of an MPLS Network

Note
Incoming labels are aggregate or nonaggregate. The aggregate label indicates that the arriving MPLS or MPLS VPN packet must be switched through an IP lookup to find the next hop and the outgoing interface. The nonaggregate label indicates that the packet contains the IP next hop information. This section describes how edge LERs can operate at either the ingress or the egress side of an MPLS network. At the ingress side of an MPLS network, LERs process packets as follows:
1. 2.
Layer 2 or Layer 3 traffic enters the edge of the MPLS network at the edge LER (PE1). The PFC3BXL or PFC3B receives the traffic from the input interface and uses the 802.1p bits or the IP ToS bits to determine the EXP bits and to perform any classification, marking, and policing. For classification of incoming IP packets, the input service policy can also use access control lists (ACLs). For each incoming packet, the PFC3BXL or PFC3B performs a lookup on the IP address to determine the next-hop router. The appropriate label is pushed (imposition) into the packet, and the EXP value resulting from the QoS decision is copied into the MPLS EXP field in the label header. The PFC3BXL or PFC3B forwards the labeled packets to the appropriate output interface for processing. The PFC3BXL or PFC3B also forwards the 802.1p bits or the IP ToS bits to the output interface. At the output interface, the labeled packets are differentiated by class for marking or policing. For LAN interfaces, egress classification is still based on IP, not on MPLS. The labeled packets (marked by EXP) are sent to the core MPLS network.
3. 4. 5. 6. 7. 8.
42-6
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS PFC3BXL or PFC3B Mode MPLS QoS
LSRs in the Core of an MPLS Network

This section describes how LSRs used at the core of an MPLS network process packets:
1. 2. 3. 4. 5. 6. 7. 8.
Incoming MPLS-labeled packets (and 802.1p bits or IP ToS bits) from an edge LER (or other core device) arrive at the core LSR. The PFC3BXL or PFC3B receives the traffic from the input interface and uses the EXP bits to perform classification, marking, and policing. The PFC3BXL or PFC3B performs a table lookup to determine the next-hop LSR. An appropriate label is placed (swapped) into the packet and the MPLS EXP bits are copied into the label header. The PFC3BXL or PFC3B forwards the labeled packets to the appropriate output interface for processing. The PFC3BXL or PFC3B also forwards the 802.1p bits or the IP ToS bits to the output interface. The outbound packet is differentiated by the MPLS EXP field for marking or policing. The labeled packets (marked with EXP) are sent to another LSR in the core MPLS network or to an LER at the output edge.
Note
Within the service provider network, there is no IP precedence field for the queueing algorithm to use because the packets are MPLS packets. The packets remain MPLS packets until they arrive at PE2, the provider edge router.
LERs at the Output Edge of an MPLS Network

At the egress side of an MPLS network, LERs process packets as follows:
1. 2.
MPLS-labeled packets (and 802.1p bits or IP ToS bits) from a core LSR arrive at the egress LER (PE2) from the MPLS network backbone. The PFC3BXL or PFC3B pops the MPLS labels (disposition) from the packets. Aggregate labels are classified using the original 802.1p bits or the IP ToS bits. Nonaggregate labels are classified with the EXP value by default. For aggregate labels, the PFC3BXL or PFC3B performs a lookup on the IP address to determine the packets destination; the PFC3BXL or PFC3B then forwards the packet to the appropriate output interface for processing. For non-aggregate labels, forwarding is based on the label. By default, non-aggregate labels are popped at the penultimate-hop router (next to last), not the egress PE router. The PFC3BXL or PFC3B also forwards the 802.1p bits or the IP ToS bits to the output interface. The packets are differentiated according to the 802.1p bits or the IP ToS bits and treated accordingly.
3.
4. 5.
Note
The MPLS EXP bits allow you to specify the QoS for an MPLS packet. The IP precedence and DSCP bits allow you to specify the QoS for an IP packet.
42-7
Chapter 42 Understanding PFC3BXL or PFC3B Mode MPLS QoS
Understanding PFC3BXL or PFC3B Mode MPLS QoS

PFC3BXL or PFC3B mode MPLS QoS supports IP QoS. For MPLS packets, the EXP value is mapped into an internal DSCP so that the PFC3BXL or PFC3B can apply non-MPLS QoS marking and policing. For both the ingress and egress policies, PFC3BXL or PFC3B mode MPLS QoS marking and policing decisions are made on a per-interface basis at an ingress PFC3BXL or PFC3B. The ingress interfaces are physical ports, subinterfaces, or VLANs. The QoS policy ACLs are programmed in QoS TCAM separately for ingress and egress lookup. The ternary content addressable memory (TCAM) egress lookup takes place after the IP forwarding table (FIB) and NetFlow lookups are completed. The results of each QoS TCAM lookup yield an index into RAM that contains policer configuration and policing counters. Additional RAM contains the microflow policer configuration; the microflow policing counters are maintained in the respective NetFlow entries that match the QoS ACL. The results of ingress and egress aggregate and microflow policing are combined into a final policing decision. The out-of-profile packets can be either dropped or marked down in the DSCP. This section describes PFC3BXL or PFC3B mode MPLS QoS for the following:

LERs at the EoMPLS Edge, page 42-8 LERs at the IP Edge (MPLS, MPLS VPN), page 42-9 LSRs at the MPLS Core, page 42-13
Note
The following sections refer to QoS features for LAN ports, OSM ports, and FlexWAN ports. For details about how the different features work, refer to the appropriate documentation.
LERs at the EoMPLS Edge

This section summarizes the Ethernet over MPLS (EoMPLS) QoS features that function on the LERs. EoMPLS QoS support is similar to IP-to-MPLS QoS:

For EoMPLS, if the port is untrusted, the CoS trust state is automatically configured for VC type 4 (VLAN mode), not for VC type 5 (port mode). 802.1q CoS preservation across the tunnel is similar. Packets received on tunnel ingress are treated as untrusted for EoMPLS interfaces, except for VC Type 4 where trust CoS is automatically configured on the ingress port and policy marking is not applied. If the ingress port is configured as trusted, packets received on an EoMPLS interface are never marked by QoS policy in the original IP packet header (marking by IP policy works on untrusted ports). 802.1p CoS is preserved from entrance to exit, if available through the 802.1q header. After exiting the tunnel egress, queueing is based on preserved 802.1p CoS if 1p tag has been tunnelled in the EoMPLS header (VC type 4); otherwise, queuing is based on the CoS derived from the QoS decision.
42-8
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS Understanding PFC3BXL or PFC3B Mode MPLS QoS
Ethernet to MPLS
For Ethernet to MPLS, the ingress interface, PFC3BXL or PFC3B mode MPLS QoS, and egress interface features are similar to corresponding features for IP to MPLS. For more information, see these sections:

Classification for IP-to-MPLS, page 42-9 Classification for IP-to-MPLS PFC3BXL or PFC3B Mode MPLS QoS, page 42-10 Classification at IP-to-MPLS Ingress Port, page 42-10 Classification at IP-to-MPLS Egress Port, page 42-10
MPLS to Ethernet
For MPLS to Ethernet, the ingress interface, PFC3BXL or PFC3B mode MPLS QoS, and egress interface features are similar to corresponding features for MPLS to IP except for the case of EoMPLS decapsulation where egress IP policy cannot be applied (packets can be classified as MPLS only). For more information, see these sections:

Classification for MPLS-to-IP, page 42-11 Classification for MPLS-to-IP PFC3BXL or PFC3B Mode MPLS QoS, page 42-12 Classification at MPLS-to-IP Ingress Port, page 42-12 Classification at MPLS-to-IP Egress Port, page 42-12.
LERs at the IP Edge (MPLS, MPLS VPN)

This section provides information about QoS features for LERs at the ingress (CE-to-PE) and egress (PE-to-CE) edges for MPLS and MPLS VPN networks. Both MPLS and MPLS VPN support general MPLS QoS features. See the MPLS VPN section on page 42-12 for additional MPLS VPN-specific QoS information.
IP to MPLS
The PFC3BXL or PFC3B provides the following MPLS QoS capabilities at the IP-to-MPLS edge:

Assigning an EXP value based on the mls qos trust or policy-map command Marking an EXP value using a policy Policing traffic using a policy
This section provides information about the MPLS QoS classification that the PFC3BXL or PFC3B supports at the IP-to-MPLS edge. Additionally, this section provides information about the capabilities provided by the ingress and egress interface modules.
Classification for IP-to-MPLS

The PFC3BXL or PFC3B ingress and egress policies for IP traffic classify traffic on the original received IP using match commands for IP precedence, IP DSCP, and IP ACLs. Egress policies do not classify traffic on the imposed EXP value nor on a marking done by an ingress policy.
42-9
After the PFC3BXL or PFC3B applies the port trust and QoS policies, it assigns the internal DSCP. The PFC3BXL or PFC3B then assigns the EXP value based on the internal DSCP-to-EXP global map for the labels that it imposes. If more than one label is imposed, the EXP value is the same in each label. The PFC3BXL or PFC3B preserves the original IP ToS when the MPLS labels are imposed. The PFC3BXL or PFC3B assigns the egress CoS based on the internal DSCP-to-CoS global map. If the default internal DSCP-to-EXP and the internal DSCP-to-CoS maps are consistent, then the egress CoS has the same value as the imposed EXP. If the ingress port receives both IP-to-IP and IP-to-MPLS traffic, classification should be used to separate the two types of traffic. For example, if the IP-to-IP and IP-to-MPLS traffic have different destination address ranges, you can classify traffic on the destination address, and then apply IP ToS policies to the IP-to-IP traffic and apply a policy (that marks or sets the EXP value in the imposed MPLS header) to the IP-to-MPLS traffic. See the following two examples:
A PFC3BXL or PFC3B policy to mark IP ToS sets the internal DSCPIf it is applied to all traffic, then for IP-to-IP traffic, the egress port will rewrite the CoS (derived from the internal DSCP) to the IP ToS byte in the egress packet. For IP-to-MPLS traffic, the PFC3BXL or PFC3B will map the internal DSCP to the imposed EXP value. A PFC3BXL or PFC3B policy to mark MPLS EXP sets the internal DSCPIf it is applied to all traffic, then for IP-to-IP traffic, the egress port rewrites the IP ToS according to the ingress IP policy (or trust). The CoS is mapped from the ToS. For IP-to-MPLS traffic, the PFC3BXL or PFC3B will map the internal DSCP to the imposed EXP value.
Classification for IP-to-MPLS PFC3BXL or PFC3B Mode MPLS QoS

PFC3BXL or PFC3B mode MPLS QoS at the ingress to PE1supports:

Matching on IP precedence or DSCP values or filtering with an access group The set mpls experimental imposition and police commands
PFC3BXL or PFC3B mode MPLS QoS at the egress of PE1 supports the mpls experimental topmost command.
Classification at IP-to-MPLS Ingress Port

Classification for IP- to- MPLS is the same as for IP-to-IP. LAN port classification is based on the received Layer 2 802.1Q CoS value. OSM and FlexWAN interfaces classify based on information in the received Layer 3 IP header.
Classification at IP-to-MPLS Egress Port

LAN port classification is based on the received EXP value and the egress CoS values is mapped from that value. OSM and FlexWAN interfaces classify traffic when you use the match mpls experimental command to match on the egress CoS as a proxy for the EXP value. The match mpls experimental command does not match on the EXP value in the topmost label. If the egress port is a trunk,the LAN ports and the OSM GE-WAN ports copy the egress CoS into the egress 802.1Q field.
42-10
OL-3999-08
Chapter 42
MPLS to IP
PFC3BXL or PFC3B mode MPLS QoS supports these capabilities at the MPLS-to-IP edge:

Option to propagate EXP value into IP DSCP on exit from an MPLS domain per egress interface Option to use IP service policy on the MPLS-to-IP egress interface
This section provides information about the MPLS-to-IP MPLS QoS classification. Additionally, this section provides information about the capabilities provided by the ingress and egress modules.
Classification for MPLS-to-IP

The PFC3BXL or PFC3B assigns the internal DSCP (internal priority that the PFC3BXL or PFC3B assigns to each frame) based on the QoS result. The QoS result is affected by the following:

Default trust EXP value Label type (per-prefix or aggregate) Number of VPNs Explicit NULL use QoS policy Regular MPLS classificationFor nonaggregate labels, in the absence of MPLS recirculation, the PFC3BXL or PFC3B classifies the packet based on MPLS EXP ingress or egress policy. The PFC3BXL queues the packet based on COS derived from EXP-to-DSCP-to-CoS mapping. The underlying IP DSCP is either preserved after egress decapsulation, or overwritten from the EXP (through the EXP-to-DSCP map). IP classification for aggregate label hits in VPN CAMThe PFC3BXL or PFC3B does one of the following:
Preserves the underlying IP ToS Rewrites the IP ToS by a value derived from the EXP-to-DSCP global map Changes the IP ToS to any value derived from the egress IP policy
There are three different classification modes:
In all cases, egress queueing is based on the final IP ToS from the DSCP-to-CoS map.
IP classification with aggregate labels not in VPN CAMAfter recirculation, the PFC3BXL or PFC3B differentiates the MPLS-to-IP packets from the regular IP-to-IP packets based on the ingress reserved VLAN specified in the MPLS decapsulation adjacency. The reserved VLAN is allocated per VRF both for VPN and non-VPN cases. The ingress ToS after recirculation can be either the original IP ToS value, or derived from the original EXP value. The egress IP policy can overwrite this ingress ToS to an arbitrary value.
Note
For information about recirculation, see the Recirculation section on page 24-4. For incoming MPLS packets on the PE-to-CE ingress, the PFC3BXL or PFC3B supports MPLS classification only. Ingress IP policies are not supported. PE-to-CE traffic from the MPLS core is classified or policed on egress as IP.
42-11
Classification for MPLS-to-IP PFC3BXL or PFC3B Mode MPLS QoS

PFC3BXL or PFC3B mode MPLS QoS at the ingress to PE2 supports matching on the EXP value and the police command. PFC3BXL or PFC3B mode MPLS QoS at the egress of PE2 supports matching on IP precedence or DSCP values or filtering with an access group and the police command.
Classification at MPLS-to-IP Ingress Port

LAN port classification is based on the EXP value. OSM and FlexWAN interfaces classify traffic using the match mpls experimental command. The match mpls experimental command matches on the EXP value in the received topmost label.
Classification at MPLS-to-IP Egress Port
Note
The egress classification queuing is different for LAN and WAN ports. Classification for MPLS-to-IP is the same as it is for IP-to-IP. The LAN interface classification is based on the egress CoS. The OSM and WAN interfaces classify traffic on information in the transmitted IP header.
Note
You can use PFC3BXL or PFC3B QoS features or OSM QoS features in an output policy; however, you cannot use both in the same output policy. If the egress port is a trunk, the LAN ports and OSM GE-WAN ports copy the egress CoS into the egress 802.1Q field.
Note
For MPLS to IP, egress IP ACL or QoS is not effective on the egress interface if the egress interface has MPLS IP (or tag IP) enabled. The exception is a VPN CAM hit, in which case the packet is classified on egress as IP.
MPLS VPN
The information in this section also applies to an MPLS VPN network. The following PE MPLS QoS features are supported for MPLS VPN:

Classification, policing, or marking of CE-to-PE IP traffic through the VPN subinterface Per-VPN QoS (per-port, per-VLAN, or per-subinterface)
For customer edge (CE)-to-PE traffic, or for CE-to-PE-to-CE traffic, the subinterface support allows you to apply IP QoS ingress or egress policies to subinterfaces and to physical interfaces. Per-VPN policing is also provided for a specific interface or subinterface associated with a given VPN on the CE side. In situations when there are multiple interfaces belonging to the same VPN, you can perform per-VPN policing aggregation using the same shared policer in the ingress or egress service policies for all similar interfaces associated with the same PFC3BXLs or PFC3Bs. For aggregate VPN labels, the EXP propagation in recirculation case may not be supported because MPLS adjacency does not know which egress interface the final packet will use.
42-12
OL-3999-08
Chapter 42
Note
For information on recirculation, see the Recirculation section on page 24-4. The PFC3BXL or PFC3B propagates the EXP value if all interfaces in the VPN have EXP propagation enabled. The following PE MPLS QoS features are supported:

General MPLS QoS features for IP packets Classification, policing, or marking of CE-to-PE IP traffic through the VPN subinterface Per-VPN QoS (per-port, per-VLAN, or per-subinterface)
LSRs at the MPLS Core

This section provides information about MPLS QoS features for LSRs at the core (MPLS-to-MPLS) for MPLS and MPLS VPN networks. Ingress features, egress interface, and PFC3BXL or PFC3B features for Carrier Supporting Carrier (CsC) QoS features are similar to those used with MPLS to MPLS described in the next section. A difference between CsC and MPLS to MPLS is that with CsC labels can be imposed inside the MPLS domain.
MPLS to MPLS
PFC3BXL or PFC3B mode MPLS QoS at the MPLS core supports the following:

Per-EXP policing based on a service policy Copying the input topmost EXP value into the newly imposed EXP value Optional EXP mutation (changing of EXP values on an interface edge between two neighboring MPLS domains) on the egress boundary between MPLS domains Microflow policing based on individual label flows for a particular EXP value Optional propagation of topmost EXP value into the underlying EXP value when popping the topmost label from a multi-label stack.
The following section provides information about MPLS-to-MPLS PFC3BXL or PFC3B mode MPLS QoS classification. Additionally, the section provides information about the capabilities provided by the ingress and egress modules.
Classification for MPLS-to-MPLS

For received MPLS packets, the PFC3BXL or PFC3B ignores the port trust state, the ingress CoS, and any policy-map trust commands. Instead, the PFC3BXL or PFC3B trusts the EXP value in the topmost label.
Note
The PFC3BXL or PFC3B mode MPLS QoS ingress and egress policies for MPLS traffic classify traffic on the EXP value in the received topmost label when you enter the match mpls experimental command.
42-13
PFC3BXL or PFC3B mode MPLS QoS maps the EXP value to the internal DSCP using the EXP-to-DSCP global map. What the PFC3BXL or PFC3B does next depends on whether it is swapping labels, imposing a new label, or popping a label:
Swapping labelsWhen swapping labels, the PFC3BXL or PFC3B preserves the EXP value in the received topmost label and copies it to the EXP value in the outgoing topmost label. The PFC3BXL or PFC3B assigns the egress CoS using the internal DSCP-to-CoS global map. If the DSCP global maps are consistent, then the egress CoS is based on the EXP in the outgoing topmost label. The PFC3BXL or PFC3B can mark down out-of-profile traffic using the police commands exceed and violate actions. It does not mark in-profile traffic, so the conform action must be transmitted and the set command cannot be used. If the PFC3BXL or PFC3B is performing a markdown, it uses the internal DSCP as an index into the internal DSCP markdown map. The PFC3BXL or PFC3B maps the result of the internal DSCP markdown to an EXP value using the internal DSCP-to-EXP global map. The PFC3BXL or PFC3B rewrites the new EXP value to the topmost outgoing label and does not copy the new EXP value to the other labels in the stack. The PFC3BXL or PFC3B assigns the egress CoS using the internal DSCP-to-CoS global map. If the DSCP maps are consistent, then the egress CoS is based on the EXP value in the topmost outgoing label.
Imposing an additional labelWhen imposing a new label onto an existing label stack, the PFC3BXL or PFC3B maps the internal DSCP to the EXP value in the imposed label using the internal DSCP-to-EXP map. It then copies the EXP value in the imposed label to the underlying swapped label. The PFC3BXL or PFC3B assigns the egress CoS using the internal DSCP-to-CoS global map. If the DSCP maps are consistent, the egress CoS is based on the EXP value in the imposed label. The PFC3BXL or PFC3B can mark in-profile and mark down out-of-profile traffic. After it marks the internal DSCP, the PFC3BXL or PFC3B uses the internal DSCP-to-EXP global map to map the internal DSCP to the EXP value in the newly imposed label. The PFC3BXL or PFC3B then copies the EXP in the imposed label to the underlying swapped label. The PFC3BXL or PFC3B assigns the egress CoS using the internal DSCP-to-CoS global map. Therefore, the egress CoS is based on the EXP in the imposed label.
Popping a labelWhen popping a label from a multi-label stack, the PFC3BXL or PFC3B preserves the EXP value in the exposed label. The PFC3BXL or PFC3B assigns the egress CoS using the internal DSCP-to-CoS global map. If the DSCP maps are consistent, then the egress CoS is based on the EXP value in the popped label. If EXP propagation is configured for the egress interface, the PFC3BXL or PFC3B maps the internal DSCP to the EXP value in the exposed label using the DSCP-to-EXP global map. The PFC3BXL or PFC3B assigns the egress CoS using the internal DSCP-to-CoS global map. If the DSCP maps are consistent, the egress CoS is based on the EXP value in the exposed label.
Classification for MPLS-to-MPLS PFC3BXL or PFC3B Mode MPLS QoS

PFC3BXL or PFC3B mode MPLS QoS at the ingress to P1 or P2 supports the following:

Matching with the mpls experimental topmost command The set mpls experimental imposition, police, and police with set imposition commands
PFC3BXL or PFC3B mode MPLS QoS at the egress of P1 or P2 supports matching with the mpls experimental topmost command.
42-14
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS PFC3BXL or PFC3B MPLS QoS Default Configuration
Classification at MPLS-to-MPLS Ingress Port

LAN port classification is based on the egress CoS from the PFC3BXL or PFC3B. OSM and FlexWAN interfaces classify traffic using the match mpls experimental command. The match mpls experimental command matches on the EXP value in the received topmost label.
Classification at MPLS-to-MPLS Egress Port

LAN port classification is based on the egress CoS value from the PFC3BXL or PFC3B. OSM and FlexWAN interfaces classify traffic using the match mpls experimental command. The match mpls experimental command matches on the egress CoS; it does not match on the EXP in the topmost label. If the egress port is a trunk, the LAN ports and OSM GE-WAN ports copy the egress CoS into the egress 802.1Q field.
PFC3BXL or PFC3B MPLS QoS Default Configuration

This section describes the PFC3BXL or PFC3B MPLS QoS default configuration. The following global PFC3BXL or PFC3B MPLS QoS settings apply: Feature PFC QoS global enable state Default Value
Note
With PFC QoS disabled and all other PFC QoS parameters at default values, default EXP is mapped from IP precedence. With PFC QoS enabled and all other PFC QoS parameters at default values, PFC QoS sets Layer 3 DSCP to zero (untrusted ports only), Layer 2 CoS to zero, the imposed EXP to zero in all traffic transmitted from LAN ports (default is untrusted). For trust CoS, the default EXP value is mapped from COS; for trust DSCP, the default EXP value is mapped from IP precedence. For OSM WAN ports, (default is trust DSCP) the DSCP is mapped to the imposed EXP.
Note
PFC QoS port enable state Port CoS value Microflow policing IntraVLAN microflow policing Port-based or VLAN-based PFC QoS EXP to DSCP map (DSCP set from EXP values)
Enabled when PFC QoS is globally enabled 0 Enabled Disabled Port-based EXP 0 = DSCP 0 EXP 1 = DSCP 8 EXP 2 = DSCP 16 EXP 3 = DSCP 24 EXP 4 = DSCP 32 EXP 5 = DSCP 40 EXP 6 = DSCP 48 EXP 7 = DSCP 56
42-15
Chapter 42 MPLS QoS Commands
Feature
Default Value
IP precedence to DSCP map IP precedence 0 = DSCP 0 (DSCP set from IP precedence values) IP precedence 1 = DSCP 8 IP precedence 2 = DSCP 16 IP precedence 3 = DSCP 24 IP precedence 4 = DSCP 32 IP precedence 5 = DSCP 40 IP precedence 6 = DSCP 48 IP precedence 7 = DSCP 56 DSCP to EXP map (EXP set from DSCP values) DSCP 07 = EXP 0 DSCP 815 = EXP 1 DSCP 1623 = EXP 2 DSCP 2431 = EXP 3 DSCP 3239 = EXP 4 DSCP 4047 = EXP 5 DSCP 4855 = EXP 6 DSCP 5663 = EXP 7 Marked-down DSCP value equals original DSCP value (no mark down) No mutation map by default None None Label + EXP value There are four possibilities at the MPLS core QoS:

Marked-down DSCP from DSCP map EXP mutation map Policers Policy maps MPLS flow mask in NetFlow table MPLS core QoS
SwappingIncoming EXP field is copied to outgoing EXP field. Swapping + impositionIncoming EXP field is copied to both the swapped EXP field and the imposed EXP field. If there is a service policy with a set for EXP field, its EXP field will be placed into the imposed label and also into the swapped label. Disposition of topmost labelExposed EXP field is preserved. Disposition of only labelExposed IP DSCP is preserved.
Note
MPLS to IP edge QoS
Preserve the exposed IP DSCP
MPLS QoS Commands

PFC3BXL or PFC3B MPLS QoS on the Catalyst 6500 series switches supports the following MPLS QoS commands:

match mpls experimental topmost set mpls experimental imposition
42-16
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS PFC3BXL or PFC3B Mode MPLS QoS Restrictions and Guidelines
police mls qos map exp-dscp mls qos map dscp-exp mls qos map exp-mutation mls qos exp-mutation show mls qos mpls no mls qos mpls trust exp
Note
For information about supported non-MPLS QoS commands, see Configuring PFC QoS section on page 41-56. The following commands are not supported:

set qos-group set discard-class
PFC3BXL or PFC3B Mode MPLS QoS Restrictions and Guidelines

When configuring PFC3BXL or PFC3B mode MPLS QoS, follow these guidelines and restrictions:
For IP-to-MPLS or EoMPLS imposition when the received packet is an IP packet:

When QoS is disabled, the EXP value is based on the received IP ToS. When QoS is queuing only, the EXP value is based on the received IP ToS.
For EoMPLS imposition when the received packet is a non-IP packet:

When QoS is disabled, the EXP value is based on the ingress CoS. When QoS is queuing only, the EXP value is based on the received IP ToS.
For MPLS-to-MPLS operations:

Swapping when QoS is disabled, the EXP value is based on the original EXP value (in the
absence of EXP mutation).

Swapping when QoS is queuing only, the EXP value is based on the original EXP value (in the

Imposing additional label when QoS is disabled, the EXP value is based on the original EXP
value (in the absence of EXP mutation).

Imposing an additional label when QoS is queuing only, the EXP value is based on the original
EXP value (in the absence of EXP mutation).

Popping one label when QoS is disabled, the EXP value is based on the underlying EXP value. Popping one label when QoS is queuing only, the EXP value is based on the underlying EXP
value.
EXP value is irrelevant to MPLS-to-IP disposition.
42-17
Chapter 42 Configuring PFC3BXL or PFC3B Mode MPLS QoS
The no mls qos rewrite ip dscp command is incompatible with MPLS. The default mls qos rewrite ip dscp command must remain enabled in order for the PFC3BXL or PFC3B to assign the correct EXP value for the labels that it imposes. With Release 12.2(18)SXF2 and later releases, the no mls qos mpls trust exp command allows you to treat MPLS packets simiarly to Layer 2 packets for CoS and egress queueing purposes by applying port trust or policy trust instead of the default EXP value.

These sections describe how to configure PFC3BXL or PFC3B mode MPLS QoS:

Enabling QoS Globally, page 42-18 Enabling Queueing-Only Mode, page 42-19 Configuring a Class Map to Classify MPLS Packets, page 42-20 Configuring the MPLS Packet Trust State on Ingress Ports, page 42-22 Configuring a Policy Map, page 42-23 Displaying a Policy Map, page 42-28 Configuring PFC3BXL or PFC3B Mode MPLS QoS Egress EXP Mutation, page 42-29 Configuring EXP Value Maps, page 42-31
Enabling QoS Globally

Before you can configure QoS on the PFC3BXL or PFC3B, you must enable the QoS functionality globally using the mls qos command. This command enables default QoS conditioning of traffic. When the mls qos command is enabled, the PFC3BXL or PFC3B assigns a priority value to each frame. This value is the internal DSCP. The internal DSCP is assigned based on the contents of the received frame and the QoS configuration. This value is rewritten to the egress frames CoS and ToS fields. To enable QoS globally, perform this task: Command
Step 1
Router(config)# mls qos Router(config)# no mls qos
Purpose Enables PFC QoS globally on the switch. Disables PFC QoS globally on the switch. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to enable QoS globally:

Router(config)# mls qos Router(config)# end Router#
42-18
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS Configuring PFC3BXL or PFC3B Mode MPLS QoS

Router# show mls qos QoS is enabled globally Microflow policing is enabled globally QoS ip packet dscp rewrite enabled globally Qos trust state is DSCP on the following interfaces: Gi4/1 Gi4/1.12 Qos trust state is IP Precedence on the following interfaces: Gi4/2 Gi4/2.42 Vlan or Portchannel(Multi-Earl) policies supported: Yes Egress policies supported: Yes
----- Module [5] ----QoS global counters: Total packets: 5957870 IP shortcut packets: 0 Packets dropped by policing: 0 IP packets with TOS changed by policing: 6 IP packets with COS changed by policing: 0 Non-IP packets with COS changed by policing: 3 MPLS packets with EXP changed by policing: 0
Enabling Queueing-Only Mode

To enable queueing-only mode, perform this task: Command
Step 1
Router(config)# mls qos queueing-only Router(config)# no mls qos queueing-only
Purpose Enables queueing-only mode. Disables PFC QoS globally.

Note
You cannot disable queueing-only mode separately.
Step 2 Step 3
When you enable queueing-only mode, the router does the following:

Disables marking and policing globally Configures all ports to trust Layer 2 CoS
Note
The switch applies the port CoS value to untagged ingress traffic and to traffic that is received through ports that cannot be configured to trust CoS.
This example shows how to enable queueing-only mode:

Router# configure terminal Router(config)# mls qos queueing-only Router(config)# end Router#
42-19
Restrictions and Usage Guidelines

If QoS is disabled ( no mls qos) for the PFC3BXL or PFC3B, the EXP value is determined as follows:
For IP-to-MPLS or EoMPLS imposition when the received packet is an IP packet:

When QoS is disabled ( no mls qos), the EXP value is based on the received IP ToS. When QoS is queuing only (mls qos queueing-only ), the EXP value is based on the received
IP ToS.
For EoMPLS imposition when the received packet is a non-IP packet:

When QoS is disabled, the EXP value is based on the ingress CoS. When QoS is queuing only, the EXP value is based on the received IP ToS.
For MPLS-to-MPLS operations:

Swapping when QoS is disabled, the EXP value is based on the original EXP value (in the

Swapping when QoS is queuing only, the EXP value is based on the original EXP value (in the

Imposing an additional label when QoS is disabled, the EXP value is based on the original EXP
value (in the absence of EXP mutation).

Imposing additional label when QoS is queuing only, the EXP value is based on the original
EXP value (in the absence of EXP mutation).

Popping one label when QoS is disabled, the EXP value is based on the underlying EXP value. Popping one label when QoS is queuing only, the EXP value is based on the underlying EXP
value.
EXP value is irrelevant to MPLS-to-IP disposition.
Configuring a Class Map to Classify MPLS Packets

You can use the match mpls experimental topmost command to define traffic classes inside the MPLS domain by packet EXP values. This allows you to define service policies to police the EXP traffic on a per-interface basis by using the police command. To configure a class map, perform this task beginning in global configuration mode: Command
Router(config)# class-map class_name
Purpose Specifies the class map to which packets will be matched. Specifies the packet characteristics that will be matched to the class. Exits class-map configuration mode.
Router(config-cmap)# match mpls experimental topmost value Router(config-cmap)# exit
42-20
OL-3999-08
Chapter 42
This example shows that all packets that contain MPLS experimental value 3 are matched by the traffic class named exp3:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# class-map exp3 Router(config-cmap)# match mpls experimental topmost 3 Router(config-cmap)# exit Router(config)# policy-map exp3 Router(config-pmap)# class exp3 Router(config-pmap-c)# police 1000000 8000000 conform-action transmit exceed-action drop Router(config-pmap-c)# exit Router(config-pmap)# end Router# show class exp3 Class Map match-all exp3 (id 61) Match mpls experimental topmost 3 Router# show policy-map exp3 Policy Map exp3 Class exp3 police cir 1000000 bc 8000000 be 8000000 conform-action transmit exceed-action drop Router# show running-config interface fastethernet 3/27 Building configuration... Current configuration : 173 bytes ! interface FastEthernet3/27 ip address 47.0.0.1 255.0.0.0 tag-switching ip end Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 3/27 Router(config-if)# service-policy input exp3 Router(config-if)# Router# Enter configuration commands, one per line. End with CNTL/Z. Router# show running-config interface fastethernet 3/27 Building configuration... Current configuration : 173 bytes ! interface FastEthernet3/27 ip address 47.0.0.1 255.0.0.0 tag-switching ip service-policy input exp3 end Router# 1w4d: %SYS-5-CONFIG_I: Configured from console by console Router# show mls qos mpls QoS Summary [MPLS]: (* - shared aggregates, Mod - switch module) Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------Fa3/27 5 In exp3 0 2 dscp 0 0 0 All 5 Default 0 0* No 0 Router# show policy-map interface fastethernet 3/27 FastEthernet3/27 Service-policy input: exp3 3466140423 0 Int Mod Dir Class-map DSCP
42-21
class-map: exp3 (match-all) Match: mpls experimental topmost 3 police : 1000000 bps 8000000 limit 8000000 extended limit Earl in slot 5 : 0 bytes 5 minute offered rate 0 bps aggregate-forwarded 0 bytes action: transmit exceeded 0 bytes action: drop aggregate-forward 0 bps exceed 0 bps Class-map: class-default (match-any) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: any Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 3/27 Router(config-if)# service-policy output ip2tag Router(config-if)# end Router# show mls qos ip QoS Summary [IPv4]: (* - shared aggregates, Mod - switch module) Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------Vl300 5 In x 44 1 No 0 0 0 Fa3/27 5 Out iptcp 24 2 -- 0 0 0 All 5 Default 0 0* No 0 3466610741 0 Int Mod Dir Class-map DSCP

The following restrictions and guidelines apply when classifying MPLS packets:
The match mpls experimental command specifies the name of an EXP field value to be used as the match criterion against which packets are checked to determine if they belong to the class specified by the class map. To use the match mpls experimental command, you must first enter the class-map command to specify the name of the class whose match criteria you want to establish. After you identify the class, you can use the match mpls experimental command to configure its match criteria. If you specify more than one command in a class map, only the last command entered applies. The last command overrides the previously entered commands.
Configuring the MPLS Packet Trust State on Ingress Ports

You can use the no mls qos mpls trust exp command to apply port or policy trust to MPLS packets in the same way that you apply them to Layer 2 packets.
42-22
OL-3999-08
Chapter 42
To configure the MPLS packet trust state of an ingress port, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type slot/port} | {port-channel number}} Router(config-if)# no mls qos mpls trust exp
Purpose Selects the interface to configure. Sets the trust state of an MPLS packet so that all trusted cases (trust cos, trust dscp, trust ip-precedence) are treated as trust-cos. Reverts to the default trust state where only the EXP value in the incoming packet is trusted. Exits interface configuration mode. Verifies the configuration.
Router(config-if)# mls qos mpls trust exp
Step 3 Step 4
Router(config-if)# end Router# show mls qos
This example shows how to set the trusted state of MPLS packets to untrusted so that the incoming MPLS packets operate like incoming Layer 2 packets.
Router(config)# interface fastethernet 3/27 Router(config-if)# no mls qos mpls trust exp Router(config-if)#

The following restrictions and guidelines apply when using the no mls qos mpls trust exp command to configure the MPLS packet trust state on input ports:

This command affects both Layer 2 and Layer 3 packets; use this command only on interfaces with Layer 2 switched packets. The no mls qos mpls trust exp command affects ingress marking; it does not affect classification.
Configuring a Policy Map

You can attach only one policy map to an interface. Policy maps can contain one or more policy map classes, each with different policy map commands. Configure a separate policy map class in the policy map for each type of traffic that an interface receives. Put all commands for each type of traffic in the same policy map class. PFC3BXL or PFC3B MPLS QoS does not attempt to apply commands from more than one policy map class to matched traffic.
Configuring a Policy Map to Set the EXP Value on All Imposed Labels
To set the value of the MPLS EXP field on all imposed label entries, use the set mpls experimental imposition command in QoS policy-map class configuration mode. To disable the setting, use the no form of this command.
Note
The set mpls experimental imposition command replaces the set mpls experimental command.
42-23
Command
Router(config)# policy-map policy_name Router(config-pmap)# class-map name [match-all | match-any] Router(config-pmap-c)# set mpls experimental imposition {mpls-exp-value | from-field [table table-map-name]} Router(config-pmap-c)# exit
Purpose Creates a policy map. Accesses the QoS class-map configuration mode to configure QoS class maps. Sets the value of the MPLS experimental (EXP) field on all imposed label entries. Exits class-map configuration mode.
Step 4
The following example sets the MPLS EXP imposition value according to the DSCP value defined in the MPLS EXP value 3.
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# access-l 101 p tcp any any Router(config)# class-map iptcp Router(config-cmap)# match acc 101 Router(config-cmap)# exit Router(config)# Router(config-cmap)# policy-map ip2tag Router(config-pmap)# class iptcp Router(config-pmap-c)# set mpls exp imposition 3 Router(config-pmap-c)# exit Router(config-pmap)# exit Router(config)# Router# 1w4d: %SYS-5-CONFIG_I: Configured from console by console Router# Router# show policy-map ip2tag Policy Map ip2tag Class iptcp set mpls experimental imposition 3 Router# show class iptcp Class Map match-all iptcp (id 62) Match access-group101 Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 3/27 Router(config-if)# ser in ip2tag Router(config-if)# Routers 1w4d: %SYS-5-CONFIG_I: Configured from console by console Router# show pol ip2tag Policy Map ip2tag Class iptcp set mpls experimental imposition 3 Router# show class-map iptcp Class Map match-all iptcp (id 62) Match access-group 101 Router# show access-l 101 Extended IP access list 101 10 permit tcp any any
42-24
OL-3999-08
Chapter 42
Router# show mls qos ip QoS Summary [IPv4]: Int Mod Dir
(* - shared aggregates, Mod - switch module)
Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------Fa3/27 5 In iptcp 24 2 No 0 0 0 Vl300 5 In x 44 1 No 0 0 0 All 5 Default 0 0* No 0 Router# Router# show policy-map interface fastethernet 3/27 FastEthernet3/27 Service-policy input: ip2tag class-map: iptcp (match-all) Match: access-group 101 set mpls experimental 3: Earl in slot 5 : 0 bytes 5 minute offered rate 0 bps aggregate-forwarded 0 bytes class-map: class-default (match-any) Match: any Class-map: class-default (match-any) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: any 3466448105 0
Class-map DSCP

Router# show policy map ip2tag Policy Map ip2tag Class iptcp set mpls experimental imposition 3
EXP Value Imposition Guidelines and Restrictions

When setting the EXP value on all imposed labels, follow these guidelines and restrictions:

Use the set mpls experimental imposition command during label imposition. This command sets the MPLS EXP field on all imposed label entries. The set mpls experimental imposition command is supported only on input interfaces (imposition). The set mpls experimental imposition command does not mark the EXP value directly; instead, it marks the internal DSCP that is mapped to EXP through the internal DSCP-to-EXP global map. It is important to note that classification (based on the original received IP header) and marking (done to the internal DSCP) do not distinguish between IP-to-IP traffic and IP-to-MPLS traffic. The commands that you use to mark IP ToS and mark EXP have the same result as when you mark the internal DSCP. To set the pushed label entry value to a value different from the default value during label imposition, use the set mpls experimental imposition command.
42-25
You optionally can use the set mpls experimental imposition command with the IP precedence, DSCP field, or QoS IP ACL to set the value of the MPLS EXP field on all imposed label entries. When imposing labels onto the received IP traffic with the PFC3BXL or PFC3B, you can mark the EXP field using the set mpls experimental imposition command.
For more information on this command, see the Cisco IOS Switching Services Command Reference, Release 12.3 located at this URL: http://www.cisco.com/en/US/docs/ios/mpls/command/reference/mp_s1.html#set_mpls_experimental_i mposition
Configuring a Policy Map Using the Police Command

Policing is a function in the PFC3BXL or PFC3B hardware that provides the ability to rate limit a particular traffic class to a specific rate. The PFC3BXL or PFC3B supports aggregate policing and microflow policing. Aggregate policing meters all traffic that ingresses into a port, regardless of different source, destination, protocol, source port, or destination port. Microflow policing meters all traffic that ingresses into a port, on a per flow (per source, destination, protocol, source port, and destination port). For additional information on aggregate and microflow policing, see the Policers section on page 41-20. To configure traffic policing, use the police command. For information on this command, see the Cisco IOS Master Command List, Release 12.2SX. Command
Router(config)# policy-map policy_name Router(config-pmap)# class-map name [match-all | match-any] Router(config-pmap-c)# police {aggregate name} Router(config-pmap-c)# police bps burst_normal burst_max conform-action action exceed-action action violate-action action Router(config-pmap-c)# police flow {bps [burst_normal] | [conform-action action] [exceed-action action] Router(config-pmap-c)# exit
Purpose Creates a policy map. Accesses the QoS class map configuration mode to configure QoS class maps. Adds the class to a shared aggregate policer. Creates a per-class-per-interface policer.
Step 5 Step 6
Creates an ingress flow policer. (Not supported in egress policy.) Exits class-map configuration mode.
This is an example of creating a policy map with a policer:

Router(config)# policy-map ip2tag Router(config-pmap)# class iptcp Router(config-pmap-c)# no set mpls exp topmost 3 Router(config-pmap-c)# police 1000000 1000000 c set-mpls-exp? set-mpls-exp-imposition-transmit Router(config-pmap-c)# police 1000000 1000000 c set-mpls-exp-imposit 3 e d Router(config-pmap-c)# exit Router(config-pmap)# exit Router(config)# interface fastethernet 3/27 Router(config-if)# ser in ip2tag Router(config-if)#
42-26
OL-3999-08
Chapter 42
This is an example of verifying the configuration:

Router# show pol ip2tag Policy Map ip2tag Class iptcp police cir 1000000 bc 1000000 be 1000000 conform-action set-mpls-exp-imposition-transmit 3 exceed-action drop Router# show running-config interface fastethernet 3/27 Building configuration... Current configuration : 202 bytes ! interface FastEthernet3/27 logging event link-status service-policy input ip2tag end Router# show mls qos ip QoS Summary [IPv4]: Int Mod Dir
(* - shared aggregates, Mod - switch module)
Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------Fa3/27 5 In iptcp 24 2 No 0 0 0 Vl300 5 In x 44 1 No 0 0 0 All 5 Default 0 0* No 0 Router# show policy interface fastethernet 3/27 FastEthernet3/27 Service-policy input: ip2tag class-map: iptcp (match-all) Match: access-group 101 police : 1000000 bps 1000000 limit 1000000 extended limit Earl in slot 5 : 0 bytes 5 minute offered rate 0 bps aggregate-forwarded 0 bytes action: set-mpls-exp-imposition-transmit exceeded 0 bytes action: drop aggregate-forward 0 bps exceed 0 bps class-map: class-default (match-any) Match: any Class-map: class-default (match-any) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: any R7# show mls qos ip QoS Summary [IPv4]: (* - shared aggregates, Mod - switch module) Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------Fa3/27 5 In iptcp 24 2 No 0 0 0 Vl300 5 In x 44 1 No 0 0 0 All 5 Default 0 0* No 0 3468161522 0 Int Mod Dir Class-map DSCP 3468105262 0
Class-map DSCP
42-27

The following restrictions and guidelines apply when using the police command to configure a policy map:
With MPLS, the exceed-action action command and the violate-action action command work similarly to IP usage. The packet may get dropped or the EXP value is marked down. For information on how these actions affect IP-to-IP traffic, see the Configuring a Policy Map section on page 41-74. With MPLS, the set-dscp transmit action command and the set-prec-transmit action command set the internal DSCP that is mapped into the CoS bits, which affects queueing, however, they do not change the EXP value, except for imposition. When swapping labels for received MPLS traffic with the PFC3BXL or PFC3B, you can mark down out-of-profile traffic using the police command exceed-action policed-dscp-transmit and violate-action policed-dscp-transmit keywords. The PFC3BXL or PFC3B does not mark in-profile traffic; when marking down out-of-profile traffic, the PFC3BXL or PFC3B marks the outgoing topmost label. The PFC3BXL or PFC3B does not propagate the marking down through the label stack. With MPLS, the flow key is based on the label and EXP value; there is no flowmask option. Otherwise, flow key operation is similar to IP-to-IP. See the Configuring a Policy Map section on page 41-74. You can use the police command to set the pushed label entry value to a value different from the default value during label imposition. When imposing labels onto the received IP traffic with the PFC3BXL or PFC3B, you can mark the EXP field using the conform-action set-mpls-exp-imposition-transmit keywords. During IP-to-MPLS imposition, IP ToS marking is not supported. If you configure a policy to mark IP ToS, the PFC3BXL or PFC3B marks the EXP value.
Displaying a Policy Map

You can display a policy map with an interface summary for MPLS QoS classes or with the configuration of all classes configured for all service policies on the specified interface.
Displaying a PFC3BXL or PFC3B Mode MPLS QoS Policy Map Class Summary
To display a PFC3BXL or PFC3B mode MPLS QoS policy map class summary, perform this task: Command
Router# show mls qos mpls [{interface interface_type interface_number} | {module slot}
Purpose Displays a PFC3BXL or PFC3B mode MPLS QoS policy map class summary.
This example shows how to display a PFC3BXL or PFC3B mode MPLS QoS policy map class summary:
Router# show mls qos mpls QoS Summary [MPLS]: (* - shared aggregates, Mod - switch module) Int Mod Dir Class-map DSCP Agg Trust Fl AgForward-By AgPoliced-By Id Id ------------------------------------------------------------------------------Fa3/27 5 In exp3 0 2 dscp 0 0 0 All 5 Default 0 0* No 0 3466140423 0
42-28
OL-3999-08
Chapter 42
Displaying the Configuration of All Classes

To display the configuration of all classes configured for all service policies on the specified interface, perform this task: Command
Router# show policy interface interface_type interface_number
Purpose Displays the configuration of all classes configured for all policy maps on the specified interface.
This example shows the configurations for all classes on Fast Ethernet interface 3/27:
Router# show policy interface fastethernet 3/27 FastEthernet3/27 Service-policy input: ip2tag class-map: iptcp (match-all) Match: access-group 101 police : 1000000 bps 1000000 limit 1000000 extended limit Earl in slot 5 : 0 bytes 5 minute offered rate 0 bps aggregate-forwarded 0 bytes action: set-mpls-exp-imposition-transmit exceeded 0 bytes action: drop aggregate-forward 0 bps exceed 0 bps class-map: class-default (match-any) Match: any Class-map: class-default (match-any) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: any
Configuring PFC3BXL or PFC3B Mode MPLS QoS Egress EXP Mutation

You can configure a named egress EXP mutation map to mutate the internal DSCP-derived EXP value before it is used as the egress EXP value. You can attach a named egress EXP mutation map to any interface on which PFC QoS supports egress QoS. These sections describe how to configure PFC3BXL or PFC3B mode MPLS QoS egress EXP mutation:

Configuring Named EXP Mutation Maps, page 42-30 Attaching an Egress EXP Mutation Map to an Interface, page 42-30
42-29
Configuring Named EXP Mutation Maps

To configure a named EXP mutation map, perform this task: Command
Step 1
Router(config)# mls qos map exp-mutation name mutated_exp1 mutated_exp2 mutated_exp3 mutated_exp4 mutated_exp5 mutated_exp6 mutated_exp7 mutated_exp8 Router(config)# no mls qos map exp-mutation name
Purpose Configures a named EXP mutation map.
Step 2 Step 3
When configuring a named EXP mutation map, note the following information:

You can configure 7 named EXP mutation maps. You can enter up to eight EXP values that map to a mutated EXP value. You can enter multiple commands to map additional EXP values to a mutated EXP value. You can enter a separate command for each mutated EXP value. You can attach named EXP mutation maps to any interface on which PFC QoS supports egress QoS.
Attaching an Egress EXP Mutation Map to an Interface

To attach an egress EXP mutation map to an interface, perform this task: Command
Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port[.subinterface]} | {port-channel number[.subinterface]}} Router(config-if)# mls qos exp-mutation exp-mutation-table-name Router(config-if)# no mls qos exp-mutation
Step 2
Attaches an egress EXP mutation map to the interface. Removes the egress DSCP mutation map from the interface. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show running-config interface {{vlan vlan_ID} | {type slot/port} | {port-channel number}} 1.
This example shows how to attach the egress EXP mutation map named mutemap2:
Router(config)# interface fastethernet 3/26 Router(config-if)# mls qos exp-mutation mutemap2 Router(config-if)# end
42-30
OL-3999-08
Chapter 42
Configuring EXP Value Maps

These sections describe how EXP values are mapped to other values:

Configuring an Ingress-EXP to Internal-DSCP Map, page 42-31 Configuring a Named Egress-DSCP to Egress-EXP Map, page 42-31
Configuring an Ingress-EXP to Internal-DSCP Map

To configure an ingress-EXP to internal-DSCP map, perform this task: Command
Step 1
Router(config)# mls qos map exp-dscp values
Purpose Configures the ingress-EXP value to internal-DSCP map. You must enter eight DSCP values corresponding to the EXP values. Valid values are 0 through 63. Reverts to the default map. Exits configuration mode. Verifies the configuration.
Router(config)# no mls qos map exp-dscp
Step 2 Step 3
This example shows how to configure an ingress-EXP to internal-DSCP map:

Router(config)# mls qos map exp-dscp 43 43 43 43 43 43 43 43 Router(config)#

Router(config)# show mls qos map exp-dscp Exp-dscp map: exp: 0 1 2 3 4 5 6 7 -----------------------------------dscp: 43 43 43 43 43 43 43 43
Configuring a Named Egress-DSCP to Egress-EXP Map

To configure a named egress-DSCP to egress-EXP map, perform this task: Command
Step 1
Router(config)# mls qos map dscp-exp dscp_values to exp_values
Purpose Configures a named egress-DSCP to egress-EXP map. You can enter up to eight DSCP values at one time to a single EXP value. Valid values are 0 through 7. Reverts to the default map. Exits configuration mode. Verifies the configuration.
Router(config)# no mls qos map dscp-exp
Step 2 Step 3
This example shows how to configure a named egress-DSCP to egress-EXP map:

Router(config)# mls qos map dscp-exp 20 25 to 3 Router(config)#
42-31
Chapter 42 MPLS DiffServ Tunneling Modes
MPLS DiffServ Tunneling Modes

Tunneling provides QoS the ability to be transparent from one edge of a network to the other edge of the network. A tunnel starts where there is label imposition. A tunnel ends where there is label disposition; that is, where the label is removed from the stack, and the packet goes out as an MPLS packet with a different per-hop behavior (PHB) layer underneath or as an IP packet with the IP PHB layer. For the PFC3BXL or PFC3B, there are two ways to forward packets through a network:
Short Pipe modeIn Short Pipe mode, the egress PE router uses the original packet marking instead of the marking used by the intermediate provider (P) routers. EXP marking does not propagate to the packet ToS byte. For a description of this mode, see the Short Pipe Mode section on page 42-32. For the configuration information, see the Configuring Short Pipe Mode section on page 42-35. Uniform modeIn Uniform mode, the marking in the IP packet may be manipulated to reflect the service providers QoS marking in the core. This mode provides consistent QoS classification and marking throughout the network including CE and core routers. EXP marking is propagated to the underlying ToS byte. For a description, see the Uniform Mode section on page 42-33. For the configuration procedure, see the Configuring Uniform Mode section on page 42-40.
Both tunneling modes affect the behavior of edge and penultimate label switching routers (LSRs) where labels are put onto packets and removed from packets. They do not affect label swapping at intermediate routers. A service provider can choose different types of tunneling modes for each customer. For additional information, see MPLS DiffServ Tunneling Modes at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_diffserv/configuration/15-mt/mp-diffserv-tun-m ode.html.
Short Pipe Mode

Short pipe mode is used when the customer and service provider are in different DiffServ domains. It allows the service provider to enforce its own DiffServ policy while preserving customer DiffServ information, which provides a DiffServ transparency through the service provider network. QoS policies implemented in the core do not propagate to the packet ToS byte. The classification based on MPLS EXP value ends at the customer-facing egress PE interface; classification at the customer-facing egress PE interface is based on the original IP packet header and not the MPLS header.
Note
The presence of an egress IP policy (based on the customers PHB marking and not on the providers PHB marking) automatically implies the Short Pipe mode.
42-32
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS MPLS DiffServ Tunneling Modes
Figure 42-2
Short Pipe Mode Operation with VPNs
CE1
PE1
P1
P2
PE2
CE2
MPLS EXP 5 MPLS EXP 5 DSCP 1 1 DSCP 1 2 3
MPLS EXP 5 MPLS EXP 5 DSCP 1 4 5 MPLS EXP 5 DSCP 1 6 7 DSCP 1 8 9 DSCP 1
Short Pipe mode functions as follows:

1. 2. 3. 4. 5. 6. 7. 8. 9.
CE1 transmits an IP packet to PE1 with an IP DSCP value of 1. PE1 sets the MPLS EXP field to 5 in the imposed label entries. PE1 transmits the packet to P1. P1 sets the MPLS EXP field value to 5 in the swapped label entry. P1 transmits the packet to P2. P2 pops the IGP label entry. P2 transmits the packet to PE2. PE2 pops the BGP label. PE2 transmits the packet to CE2, but does QoS based on the IP DSCP value.
For additional information, see MPLS DiffServ Tunneling Modes at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/mp_te_diffserv/configuration/15-mt/mp-diffserv-tun-m ode.html
Short Pipe Mode Restrictions and Guidelines

The following restriction applies to Short Pipe mode:
Short Pipe mode is not supported if the MPLS-to-IP egress interface is EoMPLS (the adjacency has the end of marker (EOM) bit set).
Uniform Mode
In Uniform mode, packets are treated uniformly in the IP and MPLS networks; that is, the IP precedence value and the MPLS EXP bits always correspond to the same PHB. Whenever a router changes or recolors the PHB of a packet, that change must be propagated to all encapsulation markings. The
119121
42-33
Chapter 42 MPLS DiffServ Tunneling Modes
propagation is performed by a router only when a PHB is added or exposed due to label imposition or disposition on any router in the packets path. The color must be reflected everywhere at all levels. For example, if a packets QoS marking is changed in the MPLS network, the IP QoS marking reflects that change.
Figure 42-3 Uniform Mode Operation
Assume something recolors the topmost label here to 0
MPLS CE1 PE1 P1 P2 PE2 CE2
MPLS exp 3 IP dscp 3
*In both the MPLS-to-MPLS and the MPLS-to-IP cases, the PHBs of the topmost popped label is copied into the new top label or the IP DSCP if no label remains
The procedure varies according to whether IP precedence bit markings or DSCP markings are present. The following actions occur if there are IP precedence bit markings:
1. 2. 3.
IP packets arrive in the MPLS network at PE1, the service provider edge router. A label is copied onto the packet. If the MPLS EXP field value is recolored (for example, if the packet becomes out-of-rate because too many packets are being transmitted), that value is copied to the IGP label. The value of the BGP label is not changed. At the penultimate hop, the IGP label is removed. That value is copied into the next lower level label. When all MPLS labels have been removed from the packet that is sent out as an IP packet, the IP precedence or DSCP value is set to the last changed EXP value in the core.
4. 5.
The following is an example when there are IP precedence bit markings:

1. 2. 3.
At CE1 (customer equipment 1), the IP packet has an IP precedence value of 3. When the packet arrives in the MPLS network at PE1 (the service provider edge router), the IP precedence value of 3 is copied to the imposed label entries of the packet. The MPLS EXP field in the IGP label header might be changed within the MPLS core (for example, at P1) by a mark down.
42-34
119209
IP dscp 3
MPLS exp 3
MPLS exp 0
IP dscp 0
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS Configuring Short Pipe Mode
Note
Because the IP precedence bits are 3, the BGP label and the IGP label also contain 3 because in Uniform mode, the labels always are identical. The packet is treated uniformly in the IP and MPLS networks.
Uniform Mode Restrictions and Guidelines

The following restriction applies to the Uniform mode:
If the egress IP ACLs or service policies are configured on the MPLS-to-IP exit point, the Uniform mode is always enforced because of recirculation.
MPLS DiffServ Tunneling Restrictions and Usage Guidelines

The MPLS DiffServ tunneling restrictions and usage guidelines are as follows:

One label-switched path (LSP) can support up to eight classes of traffic (that is, eight PHBs) because the MPLS EXP field is a 3-bit field. MPLS DiffServ tunneling modes support E-LSPs. An E-LSP is an LSP on which nodes determine the QoS treatment for MPLS packet exclusively from the EXP bits in the MPLS header. MPLS per-hop behavior (PHB) layer management. (Layer management is the ability to provide an additional layer of PHB marking to a packet.) Improved scalability of the MPLS layer management by control on managed customer edge (CE) routers. MPLS can tunnel a packets QoS (that is, the QoS is transparent from edge to edge). With QoS transparency, the IP marking in the IP packet is preserved across the MPLS network. The MPLS EXP field can be marked differently and separately from the PHB marked in the IP precedence or DSCP field.
The following features are supported with the MPLS differentiated service (DiffServ) tunneling modes:

Configuring Short Pipe Mode

The following sections describe how to configure the Short Pipe mode:

Ingress PE RouterCustomer Facing Interface, page 42-36 Configuring Ingress PE RouterP Facing Interface, page 42-37 Configuring the P RouterOutput Interface, page 42-38 Configuring the Egress PE RouterCustomer Facing Interface, page 42-39
Note
The steps that follow show one way, but not the only way, to configure Short Pipe mode. The Short Pipe mode on the egress PE (or PHP) is automatically configured when you attach to the interface an egress service policy that includes an IP class.
42-35
Chapter 42 Configuring Short Pipe Mode
Ingress PE RouterCustomer Facing Interface

This procedure configures a policy map to set the MPLS EXP field in the imposed label entries. To set the EXP value, the ingress LAN or OSM port must be untrusted. FlexWAN ports do not have the trust concept, but, as with traditional Cisco IOS routers, the ingress ToS is not changed (unless a marking policy is configured). For MPLS and VPN, the ingress PE supports all ingress PFC3BXL or PFC3B IP policies. For information about the classification for PFC IP policies based on IP ACL/DSCP/precedence, see http://www.cisco.com/en/US/docs/routers/7600/ios/12.2SXF/configuration/guide/qos.html. To configure a policy map to set the MPLS EXP field in the imposed label entries, perform this task: Command
Router(config)# mls qos Router(config)# access-list ipv4_acl_number_or_name permit any Router(config)# class-map class_name Router(config-cmap)# match access-group ipv4_acl_number_or_name Router(config)# policy-map policy_map_name Router(config-pmap)# class class_name Router(config-pmap-c)# police bits_per_second [normal_burst_bytes] conform-action set-mpls-exp-transmit exp_value exceed-action drop
Purpose Enables QoS functionality. Creates an IPv4 access list. Creates a class map. Configures the class map to filter with the ACL created in step 2. Creates a named QoS policy. Configures the policy to use the class map created in step 3. Configures policing, including the following:

Action to take on packets that conform to the rate limit specified in the service level agreement (SLA). Action to take on packets that exceed the rate limit specified in the SLA.
The exp_value sets the MPLS EXP field.

Router(config)# interface type slot/port Router(config-if)# no mls qos trust Router(config-if)# service-policy input policy_map_name
Selects an interface to configure. Configures the interface as untrusted. Attaches the policy map created in step 5 to the interface as an input service policy.
Configuration Example
This example shows how to configure a policy map to set the MPLS EXP field in the imposed label entries:
Router(config)# mls qos Router(config)# access-list 1 permit any Router(config)# class-map CUSTOMER-A Router(config-cmap)# match access-group 1 Router(config)# policy-map set-MPLS-PHB Router(config-pmap)# class CUSTOMER-A Router(config-pmap-c)# police 50000000 conform-action set-mpls-exp-transmit 4 exceed-action drop Router(config)# interface GE-WAN 3/1 Router(config-if)# no mls qos trust Router(config)# interface GE-WAN 3/1.31 Router(config-if)# service-policy input set-MPLS-PHB
42-36
OL-3999-08
Chapter 42
Configuring Ingress PE RouterP Facing Interface

This procedure classifies packets based on their MPLS EXP field and provides appropriate discard and scheduling treatments.
Note
QoS features shown here are available only with OSM and FlexWAN and Enhanced FlexWAN modules. To classify packets based on their MPLS EXP field and provide appropriate discard and scheduling treatments, perform this task:
Command
Router(config)# mls qos Router(config)# class-map class_name
Purpose Enables QoS functionality. Specifies the class map to which packets will be mapped (matched). Creates a traffic class. Specifies the MPLS EXP field values used as a match criteria against which packets are checked to determine if they belong to the class. Configures the QoS policy for packets that match the class or classes. Associates the traffic class with the service policy. Specifies the minimum bandwidth guarantee to a traffic class. You can specify the minimum bandwidth guarantee in kilobits per second or by percent of the overall bandwidth. Specifies the default class so that you can configure or modify its policy. Enables a WRED drop policy for a traffic class that has a bandwidth guarantee. Selects an interface to configure. Attaches a QoS policy to an interface and specifies that policies should be applied on packets leaving the interface.
Router(config-c-map)# match mpls experimental exp_list
Router(config)# policy-map name
Router(config-p-map)# class class_name Router(config-p-map-c)# bandwidth {bandwidth_kbps | percent percent}
Router(config-p-map)# class class-default
Router(config-p-map-c)# random-detect
Router(config)# interface type slot/port Router(config-if)# service-policy output name
Note
The bandwidth command and random-detect command are not supported on LAN ports.
This example shows how to classify packets based on their MPLS EXP field and provide appropriate discard and scheduling treatments:
Router(config)# mls qos Router(config)# class-map MPLS-EXP-4 Router(config-c-map)# match mpls experimental 4 Router(config)# policy-map output-qos Router(config-p-map)# class MPLS-EXP-4 Router(config-p-map-c)# bandwidth percent 40 Router(config-p-map)# class class-default Router(config-p-map-c)# random-detect
42-37
Chapter 42 Configuring Short Pipe Mode
Router(config)# interface pos 4/1 Router(config-if)# service-policy output output-qos
Configuring the P RouterOutput Interface

Note
QoS features shown here are available only with OSM and FlexWAN and Enhanced FlexWAN modules. To classify packets based on their MPLS EXP field and provide appropriate discard and scheduling treatments, perform this task:
Command
Purpose Enables QoS functionality. Specifies the class map to which packets will be mapped (matched). Creates a traffic class. Specifies the MPLS EXP field values used as a match criteria against which packets are checked to determine if they belong to the class. Configures the QoS policy for packets that match the class or classes. Associates the traffic class with the service policy. Specifies the minimum bandwidth guarantee to a traffic class. You can specify the minimum bandwidth guarantee in kilobits per second or by percent of the overall bandwidth. Specifies the default class so that you can configure or modify its policy. Applies WRED to the policy based on the IP precedence or the MPLS EXP field value. Selects an interface to configure. Attaches a QoS policy to an interface and specifies that policies should be applied on packets leaving the interface.
Note
Router(config)# mls qos Router(config)# class-map MPLS-EXP-4 Router(config-c-map)# match mpls experimental 4 Router(config)# policy-map output-qos Router(config-p-map)# class MPLS-EXP-4 Router(config-p-map-c)# bandwidth percent 40 Router(config-p-map)# class class-default
42-38
OL-3999-08
Chapter 42
Router(config-p-map-c)# random-detect Router(config)# interface pos 2/1 Router(config-if)# service-policy output output-qos
Configuring the Egress PE RouterCustomer Facing Interface

Note
QoS features shown here are available only with OSM and FlexWAN and Enhanced FlexWAN modules. To classify a packet based on its IP DSCP value and provide appropriate discard and scheduling treatments, perform this task:
Command
Purpose Enables QoS functionality. Specifies the class map to which packets will be mapped (matched). Creates a traffic class. Uses the DSCP values as the match criteria. Configures the QoS policy for packets that match the class or classes. Associates the traffic class with the service policy. Specifies the minimum bandwidth guarantee to a traffic class. You can specify the minimum bandwidth guarantee in kilobits per second or by percent of the overall bandwidth. Specifies the default class so that you can configure or modify its policy. Enables a WRED drop policy for a traffic class that has a bandwidth guarantee. Selects an interface to configure. Attaches a QoS policy to an interface and specifies that policies should be applied on packets leaving the interface.
Router(config-c-map)# match ip dscp dscp_values Router(config)# policy-map name
Router(config-p-map-c)# random-detect dscp-based Router(config)# interface type slot/port Router(config-if)# service-policy output name
Note
This example shows how to classify a packet based on its IP DSCP value and provide appropriate discard and scheduling treatments:
Router(config)# mls qos Router(config)# class-map IP-PREC-4 Router(config-c-map)# match ip precedence 4 Router(config)# policy-map output-qos Router(config-p-map)# class IP-PREC-4 Router(config-p-map-c)# bandwidth percent 40 Router(config-p-map)# class class-default Router(config-p-map-c)# random-detect
42-39
Chapter 42 Configuring Uniform Mode
Router(config)# interface GE-WAN 3/2.32 Router(config-if)# service-policy output output-qos
Configuring Uniform Mode

This section describes how to configure the following:

Configuring the Ingress PE RouterCustomer Facing Interface, page 42-40 Configuring the Ingress PE RouterP Facing Interface, page 42-41 Configuring the Egress PE RouterCustomer Facing Interface, page 42-42
Note
The steps that follow show one way, but not the only way, to configure the Uniform mode.
Configuring the Ingress PE RouterCustomer Facing Interface

For Uniform mode, setting the trust state to IP precedence or IP DSCP allows the PFC3BXL or PFC3B to copy the IP PHB into the MPLS PHB.
Note
This description applies to PFC3BXL or PFC3B QoS for LAN or OSM ports. For information about FlexWAN and Enhanced FlexWAN QoS, see the FlexWAN and Enhanced FlexWAN Modules Installation and Configuration Guide at this URL: http://www.cisco.com/en/US/docs/routers/7600/install_config/flexwan_config/flexwan-config-guide.ht ml.
To configure a policy map to set the MPLS EXP field in imposed label entries, perform this task: Command
Router(config)# mls qos Router(config)# access-list ipv4_acl_number_or_name permit any Router(config)# class-map class_name Router(config-cmap)# match access-group ipv4_acl_number_or_name Router(config)# policy-map policy_map_name Router(config-pmap)# class class_name Router(config-pmap-c)# police bits_per_second [normal_burst_bytes] conform-action transmit exceed-action drop
Purpose Enables QoS functionality. Creates an IPv4 access list. Creates a class map. Configures the class map to filter with the ACL created in Step 2. Creates a named QoS policy. Configures the policy to use the class map created in step 3. Configures policing, including the following:

Action to take on packets that conform to the rate limit specified in the SLA. Action to take on packets that exceed the rate limit specified in the SLA.
Step 8
Router(config)# interface type slot/port
Selects an interface to configure.
42-40
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS Configuring Uniform Mode
Command
Step 9 Step 10
Router(config-if)# mls qos trust dscp
Purpose Configures received DSCP as the basis of the internal DSCP for all the ports ingress traffic. Attaches the policy map created in step 5 to the interface as an input service policy.
Router(config-if)# service-policy input policy_map_name
This example shows how to configure a policy map to set the MPLS EXP field in imposed label entries:
Router(config)# mls qos Router(config)# access-list 1 permit any Router(config)# class-map CUSTOMER-A Router(config-cmap)# match access-group 1 Router(config)# policy-map SLA-A Router(config-pmap)# class CUSTOMER-A Router(config-pmap-c)# police 50000000 conform-action transmit exceed-action drop Router(config)# interface GE-WAN 3/1 Router(config-if)# mls qos trust dscp Router(config)# interface GE-WAN 3/1.31 Router(config-if)# service-policy input SLA-A
Configuring the Ingress PE RouterP Facing Interface

To classify packets based on their MPLS EXP field and provide appropriate discard and scheduling treatments, perform this task: Command
Purpose Enables QoS functionality. Specifies the class map to which packets will be mapped (matched). Creates a traffic class. Specifies the MPLS EXP field values used as a match criteria against which packets are checked to determine if they belong to the class. Configures the QoS policy for packets that match the class or classes. Associates the traffic class with the service policy. Specifies the minimum bandwidth guarantee to a traffic class. You can specify the minimum bandwidth guarantee in kilobits per second or by percent of the overall bandwidth. Specifies the default class so that you can configure or modify its policy. Enables a WRED drop policy for a traffic class that has a bandwidth guarantee. Selects an interface to configure. Attaches a QoS policy to an interface and specifies that policies should be applied on packets leaving the interface.
42-41
Note
Router(config)# mls qos Router(config)# class-map MPLS-EXP-3 Router(config-c-map)# match mpls experimental 3 Router(config)# policy-map output-qos Router(config-p-map)# class MPLS-EXP-3 Router(config-p-map-c)# bandwidth percent 40 Router(config-p-map)# class class-default Router(config-p-map-c)# random-detect Router(config)# interface pos 4/1 Router(config-if)# service-policy output output-qos
Configuring the Egress PE RouterCustomer Facing Interface

To configure the egress PE router at the customer-facing interface, perform this task: Command
Purpose Enables QoS functionality. Specifies the class map to which packets will be mapped (matched). Creates a traffic class. Identifies IP precedence values as match criteria. Configures the QoS policy for packets that match the class or classes. Associates the traffic class with the service policy. Specifies the minimum bandwidth guarantee to a traffic class. You can specify the minimum bandwidth guarantee in kilobits per second or by percent of the overall bandwidth. Specifies the default class so that you can configure or modify its policy. Applies WRED to the policy based on the IP precedence or the MPLS EXP field value. Selects an interface to configure. Enables propagation of EXP value into the underlying IP DSCP at the MPLS domain exit LER egress port. Attaches a QoS policy to an interface and specifies that policies should be applied on packets coming into the interface.
Router(config-c-map)# match ip precedence precedence-value Router(config)# policy-map name
Router(config)# interface type slot/port Router(config-if) mpls propagate-cos
Router(config-if)# service-policy output name
42-42
OL-3999-08
Chapter 42
Configuring PFC3BXL or PFC3B Mode MPLS QoS Configuring Uniform Mode
Note
This example shows how to configure the egress PE router at the customer-facing interface:
Router(config)# mls qos Router(config)# class-map IP-PREC-4 Router(config-c-map)# match ip precedence 4 Router(config)# policy-map output-qos Router(config-p-map)# class IP-PREC-4 Router(config-p-map-c)# bandwidth percent 40 Router(config-p-map)# class class-default Router(config-p-map-c)# random-detect Router(config)# interface GE-WAN 3/2.32 Router(config-if) mpls propagate-cos Router(config-if)# service-policy output output-qos
Tip
42-43
42-44
OL-3999-08
C H A P T E R
43
Configuring PFC QoS Statistics Data Export

This chapter describes how to configure PFC QoS statistics data export on Catalyst 6500 series switches.
Note

Understanding PFC QoS Statistics Data Export, page 43-1 PFC QoS Statistics Data Export Default Configuration, page 43-2 Configuring PFC QoS Statistics Data Export, page 43-2
Tip
Understanding PFC QoS Statistics Data Export

The PFC QoS statistics data export feature generates per-LAN-port and per-aggregate policer utilization information and forwards this information in UDP packets to traffic monitoring, planning, or accounting applications. You can enable PFC QoS statistics data export on a per-LAN-port or on a per-aggregate policer basis. The statistics data generated per port consists of counts of the input and output packets and bytes. The aggregate policer statistics consist of counts of allowed packets and counts of packets exceeding the policed rate. The PFC QoS statistics data collection occurs periodically at a fixed interval, but you can configure the interval at which the data is exported. PFC QoS statistics collection is enabled by default, and the data export feature is disabled by default for all ports and all aggregate policers configured on the Catalyst 6500 series switch.
43-1
Chapter 43 PFC QoS Statistics Data Export Default Configuration
Note
The PFC QoS statistics data export feature is completely separate from NetFlow Data Export and does not interact with it.
PFC QoS Statistics Data Export Default Configuration

Table 43-1 shows the PFC QoS statistics data export default configuration.
Table 43-1 PFC QoS Default Configuration
Feature PFC QoS Data Export Global PFC QoS data export Per port PFC QoS data export
Default Value Disabled Disabled
Per named aggregate policer PFC QoS data Disabled export Per class map policer PFC QoS data export Disabled PFC QoS data export time interval Export destination PFC QoS data export field delimiter 300 seconds Not configured Pipe character ( | )

These sections describe how to configure PFC QoS statistics data export:

Enabling PFC QoS Statistics Data Export Globally, page 43-2 Enabling PFC QoS Statistics Data Export for a Port, page 43-3 Enabling PFC QoS Statistics Data Export for a Named Aggregate Policer, page 43-4 Enabling PFC QoS Statistics Data Export for a Class Map, page 43-5 Setting the PFC QoS Statistics Data Export Time Interval, page 43-7 Configuring PFC QoS Statistics Data Export Destination Host and UDP Port, page 43-8 Setting the PFC QoS Statistics Data Export Field Delimiter, page 43-9
Enabling PFC QoS Statistics Data Export Globally

To enable PFC QoS statistics data export globally, perform this task: Command
Step 1
Router(config)# mls qos statistics-export Router(config)# no mls qos statistics-export
Purpose Enables PFC QoS statistics data export globally. Disables PFC QoS statistics data export globally.
43-2
OL-3999-08
Chapter 43
Configuring PFC QoS Statistics Data Export Configuring PFC QoS Statistics Data Export
Command
Step 2 Step 3
Router(config)# end Router# show mls qos statistics-export info
This example shows how to enable PFC QoS statistics data export globally and verify the configuration:
Router# configure terminal Router(config)# mls qos statistics-export Router(config)# end % Warning: Export destination not set. % Use 'mls qos statistics-export destination' command to configure the export destination Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 300 seconds Export Delimiter : | Export Destination : Not configured Router#
Note
You must enable PFC QoS statistics data export globally for other PFC QoS statistics data export configuration to take effect.
Enabling PFC QoS Statistics Data Export for a Port

To enable PFC QoS statistics data export for a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the interface to configure. Enables PFC QoS statistics data export for the port. Disables PFC QoS statistics data export for the port. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos statistics-export Router(config-if)# no mls qos statistics-export
Step 3 Step 4
Router(config)# end Router# show mls qos statistics-export info 1.
This example shows how to enable PFC QoS statistics data export on FastEthernet port 5/24 and verify the configuration:
Router# configure terminal Router(config)# interface fastethernet 5/24 Router(config-if)# mls qos statistics-export Router(config-if)# end Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 300 seconds Export Delimiter : | Export Destination : Not configured QoS Statistics Data Export is enabled on following ports: --------------------------------------------------------FastEthernet5/24
43-3
Chapter 43 Configuring PFC QoS Statistics Data Export
Router#
When enabled on a port, PFC QoS statistics data export contains the following fields, separated by the delimiter character:

Export type (1 for a port) Slot/port Number of ingress packets Number of ingress bytes Number of egress packets Number of egress bytes Time stamp
Enabling PFC QoS Statistics Data Export for a Named Aggregate Policer
To enable PFC QoS statistics data export for a named aggregate policer, perform this task: Command
Step 1
Router(config)# mls qos statistics-export aggregate-policer aggregate_policer_name Router(config)# no mls qos statistics-export aggregate-policer aggregate_policer_name
Purpose Enables PFC QoS statistics data export for a named aggregate policer. Disables PFC QoS statistics data export for a named aggregate policer. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to enable PFC QoS statistics data export for an aggregate policer named aggr1M and verify the configuration:
Router# configure terminal Router(config)# mls qos statistics-export aggregate-policer aggr1M Router(config)# end Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 300 seconds Export Delimiter : | Export Destination : Not configured QoS Statistics Data Export is enabled on following ports: --------------------------------------------------------FastEthernet5/24 QoS Statistics Data export is enabled on following shared aggregate policers: ----------------------------------------------------------------------------aggr1M Router#
When enabled for a named aggregate policer, PFC QoS statistics data export contains the following fields, separated by the delimiter character:
Export type (3 for an aggregate policer)
43-4
OL-3999-08
Chapter 43
Aggregate policer name Direction (in) PFC or DFC slot number Number of in-profile bytes Number of bytes that exceed the CIR Number of bytes that exceed the PIR Time stamp
Enabling PFC QoS Statistics Data Export for a Class Map

To enable PFC QoS statistics data export for a class map, perform this task: Command
Step 1
Router(config)# mls qos statistics-export class-map classmap_name Router(config)# no mls qos statistics-export class-map classmap_name
Purpose Enables PFC QoS statistics data export for a class map. Disables PFC QoS statistics data export for a class map. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to enable PFC QoS statistics data export for a class map named class3 and verify the configuration:
Router# configure terminal Router(config)# mls qos statistics-export class-map class3 Router(config)# end Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 300 seconds Export Delimiter : | Export Destination : Not configured QoS Statistics Data Export is enabled on following ports: --------------------------------------------------------FastEthernet5/24 QoS Statistics Data export is enabled on following shared aggregate policers: ----------------------------------------------------------------------------aggr1M QoS Statistics Data Export is enabled on following class-maps: --------------------------------------------------------------class3 Router#
When enabled for a class map, PFC QoS statistics data export contains the following fields, separated by the delimiter character:
For data from a physical port:

Export type (4 for a classmap and port)
43-5
Class map name Direction (in) Slot/port Number of in-profile bytes Number of bytes that exceed the CIR Number of bytes that exceed the PIR Time stamp
For data from a VLAN interface:

Export type (5 for a class map and VLAN) Classmap name Direction (in) PFC or DFC slot number VLAN ID Number of in-profile bytes Number of bytes that exceed the CIR Number of bytes that exceed the PIR Time stamp
For data from a port channel interface:

Export type (6 for a class map and port channel) Class map name Direction (in) PFC or DFC slot number Port channel ID Number of in-profile bytes Number of bytes that exceed the CIR Number of bytes that exceed the PIR Time stamp
43-6
OL-3999-08
Chapter 43
Setting the PFC QoS Statistics Data Export Time Interval

To set the time interval for the PFC QoS statistics data export, perform this task: Command
Step 1
Router(config)# mls qos statistics-export interval interval_in_seconds
Purpose Sets the time interval for the PFC QoS statistics data export.
Note
The interval needs to be short enough to avoid counter wraparound with the activity in your configuration, but because exporting PFC QoS statistic creates a significant load on the switch, be careful when decreasing the interval.
Router(config)# no mls qos statistics-export interval interval_in_seconds
Reverts to the default time interval for the PFC QoS statistics data export. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to set the PFC QoS statistics data export interval and verify the configuration:
Router# configure terminal Router(config)# mls qos statistics-export interval 250 Router(config)# end Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 250 seconds Export Delimiter : | Export Destination : Not configured QoS Statistics Data Export is enabled on following ports: --------------------------------------------------------FastEthernet5/24 QoS Statistics Data export is enabled on following shared aggregate policers: ----------------------------------------------------------------------------aggr1M QoS Statistics Data Export is enabled on following class-maps: --------------------------------------------------------------class3 Router#
43-7
Configuring PFC QoS Statistics Data Export Destination Host and UDP Port
To configure the PFC QoS statistics data export destination host and UDP port number, perform this task: Command
Step 1
Router(config)# mls qos statistics-export destination {host_name | host_ip_address} {port port_number | syslog [facility facility_name] [severity severity_value]} Router(config)# no mls qos statistics-export destination
Purpose Configures the PFC QoS statistics data export destination host and UDP port number.
Clears configured values. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Note
When the PFC QoS data export destination is a syslog server, the exported data is prefaced with a syslog header. Table 43-2 lists the supported PFC QoS data export facility and severity parameter values.
Table 43-2 Supported PFC QoS Data Export Facility Parameter Values
Name kern user mail daemon auth syslog lpr news uucp
Definition kernel messages random user-level messages mail system system daemons security/authentication messages internal syslogd messages line printer subsytem netnews subsytem uucp subsystem
Name cron local0 local1 local2 local3 local4 local5 local6 local7
Definition cron/at subsystem reserved for local use reserved for local use reserved for local use reserved for local use reserved for local use reserved for local use reserved for local use reserved for local use
Table 43-3 lists the supported PFC QoS data export severity parameter values.
Table 43-3 Supported PFC QoS Data Export Severity Parameter Values
Severity Parameter Name emerg alert crit err Number Definition 0 1 2 3 system is unusable action must be taken immediately critical conditions error conditions warning conditions
warning 4
43-8
OL-3999-08
Chapter 43
Table 43-3 Supported PFC QoS Data Export Severity Parameter Values (continued)
Severity Parameter Name notice info debug Number Definition 5 6 7 normal but significant condition informational debug-level messages
This example shows how to configure 172.20.52.3 as the destination host and syslog as the UDP port number and verify the configuration:
Router# configure terminal Router(config)# mls qos statistics-export destination 172.20.52.3 syslog Router(config)# end Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 250 seconds Export Delimiter : | Export Destination : 172.20.52.3, UDP port 514 Facility local6, Severity debug QoS Statistics Data Export is enabled on following ports: --------------------------------------------------------FastEthernet5/24 QoS Statistics Data export is enabled on following shared aggregate policers: ----------------------------------------------------------------------------aggr1M QoS Statistics Data Export is enabled on following class-maps: --------------------------------------------------------------class3
Setting the PFC QoS Statistics Data Export Field Delimiter

To set the PFC QoS statistics data export field delimiter, perform this task: Command
Step 1
Router(config)# mls qos statistics-export delimiter delimiter_character Router(config)# no mls qos statistics-export delimiter
Purpose Sets the PFC QoS statistics data export field delimiter. Reverts to the default PFC QoS statistics data export field delimiter Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to set the PFC QoS statistics data export field delimiter and verify the configuration:
Router# configure terminal Router(config)# mls qos statistics-export delimiter , Router(config)# end
43-9
Router# show mls qos statistics-export info QoS Statistics Data Export Status and Configuration information --------------------------------------------------------------Export Status : enabled Export Interval : 250 seconds Export Delimiter : , Export Destination : 172.20.52.3, UDP port 514 Facility local6, Severity debug QoS Statistics Data Export is enabled on following ports: --------------------------------------------------------FastEthernet5/24 QoS Statistics Data export is enabled on following shared aggregate policers: ----------------------------------------------------------------------------aggr1M QoS Statistics Data Export is enabled on following class-maps: --------------------------------------------------------------class3
Tip
43-10
OL-3999-08
C H A P T E R
44
Configuring the Cisco IOS Firewall Feature Set

This chapter describes how to configure the Cisco IOS firewall feature set on the Catalyst 6500 series switches. This chapter contains these sections:

Cisco IOS Firewall Feature Set Support Overview, page 44-1 Cisco IOS Firewall Guidelines and Restrictions, page 44-2 Additional CBAC Configuration, page 44-3
Tip
Cisco IOS Firewall Feature Set Support Overview

The firewall feature set images support these Cisco IOS firewall features:

Context-Based Access Control (CBAC) The PFC installs entries in the NetFlow table to direct flows that require CBAC to the MSFC where the CBAC is applied in software on the MSFC. Authentication ProxyAfter authentication on the MSFC, the PFC provides TCAM support for the authentication policy. Port-to-Application Mapping (PAM)PAM is done in software on the MSFC. Cisco IOS Security Configuration Guide, Release 12.2, Traffic Filtering and Firewalls chapter and these sections:
Cisco IOS Firewall Overview at this URL:
For more information about Cisco IOS firewall features, refer to the following publications:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_fwall_intrsn.html
Configuring Context-Based Access Control at this URL:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_content_ac.html
Configuring Authentication Proxy at this URL:
http://www.cisco.com/en/US/docs/ios/security/configuration/guide/sec_cfg_authen_prxy.html
44-1
Chapter 44 Cisco IOS Firewall Guidelines and Restrictions
Cisco IOS Security Command Reference publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.html
The following features are supported with and without the use of a Cisco IOS firewall image:

Standard access lists and static extended access lists Lock-and-key (dynamic access lists) IP session filtering (reflexive access lists) TCP intercept Security server support Network address translation Neighbor router authentication Event logging User authentication and authorization
Note
Catalyst 6500 series switches support the Intrusion Detection System Module (IDSM) (WS-X6381-IDS). Catalyst 6500 series switches do not support the Cisco IOS firewall IDS feature, which is configured with the ip audit command.
Cisco IOS Firewall Guidelines and Restrictions

When configuring the Cisco IOS firewall features, follow these guidelines and restrictions:
On other platforms, if you enter the ip inspect command on a port, CBAC modifies ACLs on other ports to permit the inspected traffic to flow through the network device. On Catalyst 6500 series switches, you must enter the mls ip inspect command to permit traffic through any ACLs that would deny the traffic through other ports. Refer to the Additional CBAC Configuration section on page 44-3 for more information. Reflexive ACLs and CBAC have conflicting flow mask requirements. Reflexive ACLs are processed in software on the MSFC. CBAC is incompatible with VACLs. You can configure CBAC and VACLs on the switch but not in the same subnet (VLAN).
Note
The Intrusion Detection System Module (IDSM) uses VACLs to select traffic. To use the IDSM in a subnet where CBAC is configured, enter the mls ip ids acl_name interface command, where acl_name is configured to select traffic for the IDSM.
To inspect Microsoft NetMeeting (2.0 or greater) traffic, turn on both h323 and tcp inspection. To inspect web traffic, turn on tcp inspection. To avoid reduced performance, do not turn on http inspection to block Java. QoS and CBAC do not interact or interfere with each other. You can configure CBAC on physical ports configured as Layer 3 interfaces and on VLAN interfaces. You cannot configure VACLs and CBAC on the same interface.
44-2
OL-3999-08
Chapter 44
Configuring the Cisco IOS Firewall Feature Set Additional CBAC Configuration
Additional CBAC Configuration

You need to do additional CBAC configuration on the Catalyst 6500 series switches. On a network device other than a Catalyst 6500 series switch, when ports are configured to deny traffic, CBAC permits traffic to flow bidirectionally through the port if it is configured with the ip inspect command. The same situation applies to any other port that the traffic needs to go through, as shown in this example:
Router(config)# ip inspect name permit_ftp ftp Router(config)# interface vlan 100 Router(config-if)# ip inspect permit_ftp in Router(config-if)# ip access-group deny_ftp_a in Router(config-if)# ip access-group deny_ftp_b out Router(config-if)# exit Router(config)# interface vlan 200 Router(config-if)# ip access-group deny_ftp_c in Router(config-if)# ip access-group deny_ftp_d out Router(config-if)# exit Router(config)# interface vlan 300 Router(config-if)# ip access-group deny_ftp_e in Router(config-if)# ip access-group deny_ftp_f out Router(config-if)# end
If the FTP session enters on VLAN 100 and needs to leave on VLAN 200, CBAC permits the FTP traffic through ACLs deny_ftp_a, deny_ftp_b, deny_ftp_c, and deny_ftp_d. If another FTP session enters on VLAN 100 and needs to leave on VLAN 300, CBAC permits the FTP traffic through ACLs deny_ftp_a, deny_ftp_b, deny_ftp_e, and deny_ftp_f. On a Catalyst 6500 series switch, when ports are configured to deny traffic, CBAC permits traffic to flow bidirectionally only through the port configured with the ip inspect command. You must configure other ports with the mls ip inspect command. If the FTP session enters on VLAN 100 and needs to leave on VLAN 200, CBAC on a Catalyst 6500 series switch permits the FTP traffic only through ACLs deny_ftp_a and deny_ftp_b. To permit the traffic through ACLs deny_ftp_c and deny_ftp_d, you must enter the mls ip inspect deny_ftp_c and mls ip inspect deny_ftp_d commands, as shown in this example:
Router(config)# mls ip inspect deny_ftp_c Router(config)# mls ip inspect deny_ftp_d
FTP traffic cannot leave on VLAN 300 unless you enter the mls ip inspect deny_ftp_e and mls ip inspect deny_ftp_f commands. Enter the show fm insp [detail] command to verify the configuration. The show fm insp [detail] command displays the list of ACLs and ports on which CBAC is configured and the status (ACTIVE or INACTIVE), as shown in this example:
Router# show fm insp interface:Vlan305(in) status :ACTIVE acl name:deny interfaces: Vlan305(out):status ACTIVE
On VLAN 305, inspection is active in the inbound direction and no ACL exists. ACL deny is applied on VLAN 305 in the outbound direction and inspection is active. To display all of the flow information, use the detail keyword. If a VACL is configured on the port before configuring CBAC, the status displayed is INACTIVE; otherwise, it is ACTIVE. If PFC resources are exhausted, the command displays the word BRIDGE followed by the number of currently active NetFlow requests that failed, which have been sent to the MSFC for processing.
44-3
Chapter 44 Additional CBAC Configuration
Tip
44-4
OL-3999-08
C H A P T E R
45
Configuring Network Admission Control

This chapter describes how to configure Network Admission Control (NAC) on Catalyst 6500 series switches. With a PFC3, Release 12.2(18)SXF2 and later releases support NAC.
Note
For complete syntax and usage information for the commands used in this chapter, refer to this publication: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html

Understanding NAC, page 45-1 Configuring NAC, page 45-11
Tip
Understanding NAC
These sections describe NAC:

NAC Overview, page 45-1 NAC Device Roles, page 45-2 NAC Layer 2 IP Validation, page 45-4
NAC Overview
NAC is part of the Cisco Self-Defending Network Initiative that helps you identify, prevent, and adapt to security threats in your network. Because of the increased threat and impact of worms and viruses to networked businesses, NAC allows you to check and validate the antivirus status of endpoints or clients before granting network access.
45-1
Chapter 45 Understanding NAC
Catalyst 6500 series switches support NAC Layer 2 IP validation. NAC Layer 2 IP validation operates on edge switches but has different methods for validation initiation, message exchange, and policy enforcement from the NAC Layer 2 IEEE 802.1x. LAN Port IP does not require IEEE 802.1x support on the host PCs. For a complete list of devices that support NAC, see the NAC release notes.
Note
Unless otherwise noted, the term switch refers to Catalyst 6500 series switches. Release 12.2(18)SXF does not support NAC Layer 2 IEEE 802.1x.
NAC provides posture validation for routed traffic on Catalyst 6500 series switches. Posture validation reduces the exposure of a virus to the network. This feature allows network access based on the antivirus credentials of the network device that is requesting network access. These credentials may be antivirus software, a virus definitions file, or a particular virus scan engine version. Based on the antivirus credentials of the host, the requesting device is allowed access to the network or is restricted from network access. If the client host fails the credential validation, then partial access to the network can be allowed by using the remediation feature. The remediation process redirects HTTP traffic from the client host to a web page URL that provides access to the latest antivirus files. The URL used by the remediation process resolves to a remediation server address defined as a part of the network access policy. The remediation server is where the latest antivirus files are located. These antivirus files can be downloaded or upgraded from this location.
NAC Device Roles

The devices in the network have specific roles when you use NAC as shown in Figure 45-1.
Figure 45-1 Posture Validation Devices
PC
Workstation
Switch
Cisco Secure ACS
Server
Network Access Device
Authentication Server (RADIUS)
Clients running the Cisco Trust Agent software
45-2
92734
OL-3999-08
Chapter 45
Configuring Network Admission Control Understanding NAC
The following devices that support NAC on the network perform these roles:
Endpoint system or clientThis is a device (host) on the network such as a PC, workstation, or server that is connected to a switch access port through a direct connection, an IP phone, or a wireless access point. The host, which is running the Cisco Trust Agent software, requests access to the LAN and switch services and responds to requests from the switch. This endpoint system is a potential source of virus infections, and its antivirus status needs to be validated before the host is granted network access. The Cisco Trust Agent software is also referred to as the posture agent or the antivirus client. Switch (edge switches)This is the network access device that provides validation services and policy enforcement at the network edge and controls the physical access to the network based on the access policy of the client. The switch relays Extensible Authentication Protocol (EAP) messages between the endpoints and the authentication server. For Catalyst 6500 series switches, the encapsulation information in the EAP messages can be based on the User Datagram Protocol (UDP). When using UDP, the switch uses EAP over UDP (EAPoUDP) frames, which are also referred to as EoU frames.
Authentication serverThis device performs the actual validation of the client. The authentication server validates the antivirus status of the client, determines the access policy, and notifies the switch whether the client is authorized to access the LAN and switch services. Because the switch acts as the proxy, the EAP message exchange between the switch and authentication server is transparent to the switch. In this release, the switch supports the Cisco Secure Access Control Server (ACS) Version 4.0 or later with RADIUS, authentication, authorization, and accounting (AAA), and EAP extensions. The authentication server is also referred to as the posture server.
AAA Down Policy

The AAA down policy is a method of allowing a host to remain connected to the network if the AAA server is not available. Typical deployments of NAC use Cisco Secure ACS to validate the client posture and to pass policies back to the Network Access Device (NAD). If the AAA server cannot be reached when the posture validation occurs, instead of rejecting the user (that is, not providing the access to the network), an administrator can configure a default AAA down policy that can be applied to the host. This policy is advantageous for the following reasons:

While AAA is unavailable, the host will still have connectivity to the network, although it may be restricted. When the AAA server is again available, a user can be revalidated, and the users policies can be downloaded from the ACS.
Note
When the AAA server is down, the AAA down policy is applied only if there is no existing policy associated with the host. Typically, during revalidation when the AAA server goes down, the policies being used for the host are retained.
45-3
NAC Layer 2 IP Validation

You can use NAC Layer 2 IP on an access port on an edge switch to which an endpoint system or client is connected. The device (host or client) can be a PC, a workstation, or a server that is connected to the switch access port through a direct connection, an IP phone, or a wireless access point, as shown in Figure 45-2. When NAC Layer 2 IP is enabled, EAPoUDP only works with IPv4 traffic. The switch checks the antivirus status of the endpoint devices or clients and enforces access control policies.
Figure 45-2 Network Using NAC Layer 2 IP
PC
PC
Hub Workstation Cisco Secure ACS
Switch
IP phone PC IP Network Access Device Authentication Server (RADIUS)
Clients running the Cisco Trust Agent software
These sections describe NAC Layer 2 IP validation:

Posture Validation, page 45-4 Cisco Secure ACS and AV Pairs, page 45-6 Audit Servers, page 45-7 ACLs, page 45-8 NAC Timers, page 45-8 NAC Layer 2 IP Validation and Redundant Supervisor Engines, page 45-11
Posture Validation
NAC Layer 2 IP supports the posture validation of multiple hosts on the same switch port, as shown in Figure 45-2. When you enable NAC Layer 2 IP validation on a switch port to which hosts are connected, the switch can use DHCP snooping and Address Resolution Protocol (ARP) snooping to identify connected hosts. The switch initiates posture validation after receiving an ARP packet or creating a DHCP snooping binding entry. When you enable NAC Layer 2 IP validation, ARP snooping is the default method to detect connected hosts. If you want the switch to detect hosts when a DHCP snooping binding entry is created, you must enable DHCP snooping.
45-4
92735
OL-3999-08
Chapter 45
When DHCP snooping occurs initiating posture validation, it takes precedence over initiating posture validation when ARP snooping occurs. If only dynamic ARP inspection is enabled on the access VLAN assigned to a switch port, posture validation is initiated when ARP packets pass the dynamic ARP inspection validation checks. However, if DHCP snooping and dynamic ARP inspection are enabled, when you create a DHCP snooping binding entry, posture validation is initiated through DHCP. When posture validation is initiated, the switch creates an entry in the session table to track the posture validation status of the host and follows this process to determine the NAC policy:
1. 2.
If the host is in the exception list, the switch applies the user-configured NAC policy to the host. If EoU bypass is enabled, the switch sends a nonresponsive-host request to the Cisco Secure ACS and applies the access policy from the server to the host. The switch inserts a RADIUS AV pair to the request to specify that the request is for a nonresponsive host. If EoU bypass is disabled, the switch sends an EAPoUDP hello packet to the host, requesting the host antivirus condition. If no response is received from the host after the specified number of attempts, the switch classifies the host as clientless, and the host is considered to be a nonresponsive host. The switch sends a nonresponsive-host request to the Cisco Secure ACS and applies the access policy from the server to the host.
3.
Exception Lists
An exception list has local profile and policy configurations. Use the identity profile to statically authorize or validate devices based on the IP address, MAC address, or device type. An identity profile is associated with a local policy that specifies the access control attributes. You can bypass posture validation of specific hosts by specifying those hosts in an exception list and applying a user-configured policy to the hosts. After the entry is added to the EAPoUDP session table, the switch compares the host information to the exception list. If the host is in the exception list, the switch applies the configured NAC policy to the host. The switch also updates the EAPoUDP session table with the validation status of the client as POSTURE ESTAB.
EoU Bypass
The switch can use the EoU bypass feature to speed up posture validation of hosts that are not using the Cisco Trust Agent. If EoU bypass is enabled, the switch does not contact the host to request the antivirus condition. Instead, the switch sends a request to the Cisco Secure ACS that includes the IP address, MAC address, service type, and EAPoUDP session ID of the host. The Cisco Secure ACS makes the access control decision and sends the policy to the switch. If EoU bypass is enabled and the host is nonresponsive, the switch sends a nonresponsive-host request to the Cisco Secure ACS and applies the access policy from the server to the host. If EoU bypass is enabled and the host uses Cisco Trust Agent, the switch also sends a nonresponsive-host request to the Cisco Secure ACS and applies the access policy from the server to the host.
EAPoUDP Sessions
If the EoU bypass is disabled, the switch sends an EAPoUDP packet to initiate posture validation. While posture validation occurs, the switch enforces the default access policy. After the switch sends an EAPoUDP message to the host and the host responds to the antivirus condition request, the switch forwards the EAPoUDP response to the Cisco Secure ACS. If no response is received from the host after the specified number of attempts, the switch classifies the host as nonresponsive. After the ACS validates the credentials, the authentication server returns an Access-Accept message with the posture token and
45-5
the policy attributes to the switch. The switch updates the EAPoUDP session table and enforces the access limitations, which provides segmentation and quarantine of poorly postured clients, or by denying network access. There are two types of policies that apply to ports during posture validation:

Host PolicyThe Host policy consists of an ACL that enforces the access limitations as determined by the outcome of posture validation. URL Redirect PolicyThe URL Redirect policy provides a method to redirect all HTTP or HTTPS traffic to a remediation server that allows a noncompliant host to perform the necessary upgrade actions to become compliant.
The operation of the URL-Redirect deny ACEs (typically to bypass the redirection of the HTTP traffic destined to remediation servers) is that the traffic to these ACEs is forwarded in hardware without applying the default interface and the downloaded host policies. If this traffic (that is, the traffic that matches the deny URL Redirect ACEs) is required to be filtered, you need to define a VLAN ACL on the switch port access VLAN. The URL-Redirect Policy consists of the following:

A URL that points to the remediation server. An ACL on the switch that causes all HTTP or HTTPS packets from the host other than those destined to the remediation server address to be captured and redirected to the switch software for the necessary HTTP redirection.
The ACL name for the host policy, the redirect URL, and the URL redirect ACL are conveyed using RADIUS Attribute-Value objects.
Note
If a DHCP snooping binding entry for a client is deleted, the switch removes the client entry in the session table, and the client is no longer authenticated.
Cisco Secure ACS and AV Pairs

When NAC Layer 2 IP validation is enabled, the Cisco Secure ACS provides NAC AAA services by using RADIUS. Cisco Secure ACS gets information about the antivirus status of the endpoint system and validates the antivirus condition of the endpoint. You can set these Attribute-Value (AV) pairs on the Cisco Secure ACS by using the RADIUS cisco-av-pair vendor-specific attributes (VSAs):
CiscoSecure-Defined-ACLSpecifies the names of the downloadable ACLs on the Cisco Secure ACS. The switch gets the ACL name through the CiscoSecure-Defined-ACL AV pair in this format: #ACL#-IP-name-number name is the ACL name and number is the version number, such as 3f783768. The Auth-Proxy posture code checks if the access control entries (ACEs) of the specified downloadable ACL were previously downloaded. If they were not, the Auth-Proxy posture code sends an AAA request with the downloadable ACL name as the username so that the ACEs are downloaded. The downloadable ACL is then created as a named ACL on the switch. This ACL has ACEs with a source address of any and does not have an implicit deny statement at the end. When the downloadable ACL is applied to an interface after posture validation is complete, the source address is changed from any to the host source IP address. The ACEs are prepended to the downloadable ACL applied to the switch interface to which the endpoint device is connected. If traffic matches the CiscoSecure-Defined-ACL ACEs, the appropriate NAC actions are taken.
45-6
OL-3999-08
Chapter 45
url-redirect and url-redirect-aclSpecifies the local URL policy on the switch. The switches use these cisco-av-pair VSAs as follows:
url-redirect = <HTTP or HTTPS URL> url-redirect-acl = switch ACL name or number
These AV pairs enable the switch to intercept an HTTP or HTTPS request from the endpoint device and forward the client web browser to the specified redirect address from which the latest antivirus files can be downloaded. The url-redirect AV pair on the Cisco Secure ACS contains the URL to which the web browser will be redirected. The url-redirect-acl AV pair contains the name or number of an ACL that specifies the HTTP or HTTPS traffic to be redirected. The ACL must be defined on the switch. Traffic that matches a permit entry in the redirect ACL will be redirected. These AV pairs may be sent if the hosts posture is not healthy.
Note
You can redirect the URL for either HTTP or HTTPS but not for both at the same time. This situation occurs because Cisco IOS on the switch the HTTP server can either listen to the HTTP port or to the HTTPS port but cannot listen to both at the same time.
For more information about AV pairs that are supported by Cisco IOS software, see the ACS configuration and command reference documentation about the software releases running on the AAA clients.
Audit Servers
End devices that do not run a Cisco Trust Agent (CTA) will not be able to provide credentials when challenged by Network Access Devices. These devices are described as agentless or nonresponsive. The NAC architecture has been extended to incorporate audit servers. An audit server is a third-party server that can probe, scan, and determine security compliance of a host without the need for presence of Cisco trust agent on the host. The result of the audit server examination can influence the access servers to make host-specific network access policy decisions instead of enforcing a common restrictive policy for all nonresponsive hosts. You can build more robust host audit and examination functionality by integrating any third-party audit operations into the NAC architecture. Figure 45-3 shows how audit servers fit into the typical topology.
Figure 45-3 NAC Device Roles
Audit server
Endpoint device IP traffic
Audit mechanisms e.g. port scan GAMEP
Radius
140123
NAD Intercept IP traffic from new endpoint
AAA server
45-7
The architecture assumes that the audit server can be reached so that the host can communicate with it. When a host (endpoint device) makes network access through the NAD configured for posture validation, the network access device eventually requests the AAA server (Cisco Secure ACS) for an access policy to be enforced for the host. The AAA server can be configured to trigger a scan of the host with an external audit server. The audit server scan happens asynchronously and can take several seconds to complete. During the time of the audit server scan, the AAA server conveys a minimal restrictive security policy to NAD for enforcement along with a short poll timer (session-timeout). The NAD polls the AAA sever at the specified timer interval until the result is available from the audit server. After the AAA server receives the audit result, it computes an access policy based on the audit result and is sent down to NAD for enforcement on its next request.
ACLs
If you configure NAC Layer 2 IP validation on a switch port, you must also configure a default port ACL on a switch port. You should also apply the default ACL to IP traffic for hosts that have not completed posture validation. If the default ACL is configured on the switch and the Cisco Secure ACS sends a host access policy to the switch, the switch applies the policy to traffic from the host connected to a switch port. If the policy applies to the traffic, the switch forwards the traffic. If the policy does not apply, the switch applies the default ACL. However, if the switch gets an host access policy from the Cisco Secure ACS but the default ACL is not configured, the NAC Layer 2 IP configuration does not take effect. If the Cisco Secure ACS sends the switch an downloadable ACL that specifies a redirect URL as a policy-map action, this ACL takes precedence over the default ACL already configured on the switch port. The redirect URL ACL policy also takes precedence over the policy already configured on the host. If the default port ACL is not configured on the switch, the switch can still apply the downloadable ACL from the Cisco Secure ACS.
NAC Timers
The switch supports these timers:

Hold Timer, page 45-8 Idle Timer, page 45-9 Retransmission Timer, page 45-10 Revalidation Timer, page 45-10 Status-Query Timer, page 45-10
Hold Timer
The hold timer prevents a new EAPoUDP session from immediately starting after the previous attempt to validate the session fails. This timer is used only when the Cisco Secure ACS sends a Accept-Reject message to the switch. The default value of the hold timer is 180 seconds (3 minutes). An EAPoUDP session might not be validated because the posture validation of the host fails, a session timer expires, or the switch or Cisco Secure ACS receives invalid messages. If the switch or authentication server continuously receives invalid messages, a malicious user might be trying to cause a denial-of-service attack.
45-8
OL-3999-08
Chapter 45
Idle Timer
The idle timer controls how long the switch waits for an ARP packet from the postured host or a refreshed entry in the IP device tracking table to verify that the host is still connected. The idle timer works with a list of known hosts to track hosts that have initiated posture validation and the IP device tracking table. The idle timer is reset when the switch receives an ARP packet or when an entry in the IP device tracking table is refreshed. If the idle timer expires, the switch ends the EAPoUDP session on the host, and the host is no longer validated. The default value of the idle timer is calculated as the probe interval times the number of probe retries. By default, the idle timer default is 90 seconds which is the probe interval of 30 seconds times the number of probe retries of 3. The switch maintains a list of known hosts to track hosts that have initiated posture validation. When the switch receives an ARP packet, it resets the aging timers for the list and the idle timer. If the aging time of the list expires, the switch sends an ARP probe to verify that the host is present. If the host is present, it sends a response to the switch. The switch updates the entry in the list of known hosts. The switch then resets the aging timers for the list and the idle timer. If the switch receives no response, the switch ends the session with the Cisco Secure ACS, and the host is no longer validated. The switch uses the IP device tracking table to detect and manage hosts connected to the switch. The switch also uses ARP or DHCP snooping to detect hosts. By default, the IP device tracking feature is disabled on a switch. You must enable the IP device tracking feature to use NAC Layer 2 IP validation. When IP device tracking is enabled, and a host is detected, the switch adds an entry to the IP device tracking table that includes this information:

IP and MAC address of the host Interface on which the switch detected the host Host state that is set to ACTIVE when the host is detected
If NAC Layer 2 IP validation is enabled on an interface, adding an entry to the IP device tracking table initiates posture validation. For the IP device tracking table, you can configure the number of times that the switch sends ARP probes for an entry before removing an entry from the table and you can also configure the number of seconds that the switch waits before resending the ARP probe. If the switch uses the default settings of the IP device tracking table, the switch sends ARP probes every 30 seconds for all the entries. When the host responds to the probe, the host state is refreshed and remains active. The switch can send up to three additional ARP probes at 30-second intervals if the switch does not get a response. After the maximum number of ARP probes are sent, the switch removes the host entry from the table. The switch ends the EAPoUDP session for the host if a session was set up. Using the IP device tracking ensures that hosts are detected in a timely manner, despite the limitations of using DHCP. If an link goes down, the IP device tracking entries associated with the interface are not removed, and the state of entries is changed to inactive. The switch does not limit the number of entries in the IP device tracking table but applies a limit to remove inactive entries. All entries remain in the IP device tracking table until it contains has more than the limit. When the table reaches the limit to start removing inactive entries, the switch removes the inactive entries if the table has inactive entries and adds new entries. If the table does not have inactive entries, the number of entries in the IP device tracking table increases. When a host becomes inactive, the switch ends the host session. For Catalyst 3750, 3560, 3550, 2970, 2960, 2955, 2950, and 2940 switches and for Cisco EtherSwitch service modules, the limit to remove inactive entries is 512. For Cisco 7600 series routers and Catalyst 4000 and 6000 switches, the limit is 2048.
45-9
After an interface link is restored, the switch sends ARP probes for the entry associated with the interface. The switch ages out entries for hosts that do not respond to ARP probes. The switch changes the state of hosts that respond to an active host and initiates posture validation.
Retransmission Timer
The retransmission timer controls the amount of time that the switch waits for a response from the client before resending a request during posture validation. Setting the timer value too low might cause unnecessary transmissions, and setting the timer value too high might cause poor response times. The default value of the retransmission timer is 3 seconds.
Revalidation Timer
The revalidation timer controls the amount of time that a NAC policy is applies to a client that used EAPoUDP messages during posture validation. The timer starts after the initial posture validation is complete. The timer resets when the host is revalidated. The default value of the revalidation timer is 36000 seconds (10 hours). You can specify the revalidation timer value on the switch by using the eou timeout revalidation seconds global configuration command. You can also specify the revalidation timer value on an interface by using the eou timeout revalidation seconds interface configuration command.
Note
The revalidation timer can be configured locally on the switch or it can be downloaded from the control server. The revalidation timer operation is based on Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute[29]) in the Access-Accept message from the Cisco Secure ACS running AAA. If the switch gets the Session-Timeout value, this value overrides the revalidation timer value on the switch. If the revalidation timer expires, the switch action depends on one of these values of the Termination-Action attribute:

If the value of the Termination-Action RADIUS attribute is the default, the session ends. If the switch gets a value for the Termination-Action attribute other than the default, the EAPoUDP session and the current access policy remain in effect during posture revalidation. If the value of the Termination-Action attribute is RADIUS, the switch revalidates the client. If the packet from the server does not include the Termination-Action attribute, the EAPoUDP session ends.
Status-Query Timer
The status-query timer controls the amount of time the switch waits before verifying that the previously validated client is present and that its posture has not changed. Only clients that were authenticated with EAPoUDP messages use this timer, which starts after the client is initially validated. The default value of the status-query timer is 300 seconds (5 minutes). The timer resets when the host is reauthenticated. When the timer expires, the switch checks the host posture validation by sending a Status-Query message to the host. If the host sends a message to the switch that the posture has changed, the switch revalidates the posture of the host.
45-10
OL-3999-08
Chapter 45
Configuring Network Admission Control Configuring NAC
NAC Layer 2 IP Validation and Redundant Supervisor Engines

On Catalyst 6500 series switches with redundant supervisor engines, when RPR mode redundancy is configured, a switchover causes the loss of all information about currently postured hosts. When SSO mode redundancy is configured, a switchover triggers a reposturing of all currently postured hosts.
NAC Layer 2 IP Validation and Redundant Modular Switches

When RPR mode redundancy is configured, a switchover will lose all information regarding currently postured hosts. When SSO mode redundancy is configured, a switchover will trigger a reposturing of all currently postured hosts.
AAA Down Policy for NAC Layer 2 IP Validation

With the AAA down policy feature, the validation process operates in the following order:
1. 2. 3.
A new session is detected. Before posture validation is triggered and provided the AAA server is unreachable, the AAA down policy is applied and session state is maintained as AAA DOWN. When the AAA server is once again available, a revalidation is retriggered for the host.
Note
When the AAA server is down, the AAA down policy is applied only if there is no existing policy associated with the host. During revalidation when the AAA server goes down, the policies being used for the host are retained.
Configuring NAC
This section contains this configuration information:

Default NAC Configuration, page 45-11 NAC Layer 2 IP Guidelines, Limitations, and Restrictions, page 45-11 Configuring EAPoUDP, page 45-16 Configuring EAPoUDP, page 45-16 Configuring Identity Profiles and Policies, page 45-17
Default NAC Configuration

By default, NAC Layer 2 IP validation is disabled.
NAC Layer 2 IP Guidelines, Limitations, and Restrictions

When configuring NAC Layer 2 IP validation, follow these guidelines, limitations, and restrictions:
You must configure Layer 3 routes from the switch to the host for the Layer 2 IP to operate correctly.
45-11
Chapter 45 Configuring NAC
Layer 2 IP is not allowed if the parent VLAN of the port has VACL capture or Cisco IOS firewall (CBAC) is configured. LAN Port IP (LPIP) ARP traffic redirected to the CPU cannot be spanned using the SPAN feature. NAC Layer 2 IP validation is not supported on trunk ports, tunnel ports, EtherChannel members, or routed ports. The Catalyst 6500 series switches support Layer 2 IP on EtherChannels. When NAC Layer 2 IP validation is enabled, you must configure an ACL on the switch port to which hosts are connected. The ACL must permit EAPoUDP traffic for LPIP to function. NAC Layer 2 IP does not validate the posture of IPv6 traffic and does not apply access policies to IPv6 traffic. NAC Layer 2 IP is not supported if the switchport is part of a private VLAN. NAC Layer 2 IP ARP traffic redirected to the CPU cannot be spanned using the SPAN feature. A denial-of-service attack might occur if the switch receives many ARP packets with different source IP addresses. To avoid this problem, you must configure the IP admission MLS rate-limiting feature using the mls rate-limit layer2 ip-admission command. If DAI is also enabled on the parent VLAN of the switch port, the IP admission rate limiting for ARP packets directed to the CPU is ineffective. In this situation, ARP Inspection rate limiting is functional. ARP inspection rate limiting is performed in software and IP admission rate limiting is performed in hardware. When NAC Layer 2 IP and NAC Layer 2 IEEE 802.1x are enabled on the same access port, IEEE 802.1x authentication takes precedence. The posture of the host to which the port is connected might already have been validated, and the switch would have applied the access limitations based on IEEE 802.1x. DHCP snooping must be enabled if the switch wants to use DHCP lease grants to identify connected hosts. DHCP packets are permitted in DHCP environments in both the default interface and the downloaded host policy. If you want the end stations to send DNS requests before posture validation occurs, you must configure the named downloadable ACL on the switch port with ACEs permitting DNS packets. If you want to forward the HTTP and HTTPS requests from an endpoint device to a specific URL, you must enable the HTTP server feature. The url-redirect-acl AV pair should be defined as the URL ACL name. This ACL should contain a deny tcp any remediation server address eq www command followed by the permit ACEs for the HTTP traffic that is being redirected. If NAC Layer 2 IP validation is configured on a switch port that belongs to a voice VLAN, the switch does not validate the posture of the IP phone. Make sure that the IP phone is on the exception list. If NAC Layer 2 IP validation is enabled, the NAC Layer 2 IP configuration takes precedence over VLAN ACLs and router ACLs that are configured on ingress interfaces. For example, when a VLAN ACL and a router ACL are configured, the operation applies the policies serially in the order of the LPIP policy to VLAN ACL to router ACL. The next policy is applied only when the traffic passes through the previous policy check. Any policy in the serial order denying the traffic causes the traffic to be denied. The downloaded LPIP host policy always overrides the default interface policy. The DHCP traffic should be permitted in the interface default ACL and the host policy for DHCP snooping to function. If dynamic ARP inspection is enabled on the ingress VLAN, the switch initiates posture validation only after the ARP packets are validated.
45-12
OL-3999-08
Chapter 45
The traffic sent to the URL-redirect deny ACEs is forwarded in hardware without applying the default interface and the downloaded host policies. If this traffic (that is, the traffic matching the deny URL-redirect ACEs) requires filtering, you should define a VLAN ACL on the switch port access VLAN. This configuration allows you to bypass the redirection of the HTTP traffic destined for the remediation servers. If IEEE 802.1x authentication in single-host mode and NAC Layer 2 IP validation are configured on a switch port and IEEE 802.1x authentication of the connected hosts fails, the switch does not initiate posture validation when it receives DHCP or ARP packets from the host. If IEEE 802.1x authentication is configured on the port, the port cannot send or receive traffic other than EAPOL frames until the client is successfully authenticated.
Configuring NAC Layer 2 IP Validation

To configure NAC Layer 2 IP validation, beginning in privileged EXEC mode, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip admission name rule_name eapoudp
Purpose Enters global configuration mode. Creates and configures an IP NAC rule by specifying the rule name. To remove the IP NAC rule on the switch, use the no ip admission name rule-name eapoudp global configuration command.
Step 3 Step 4
Router(config)# mls ratelimit layer2 ip ip-admission pps (burst) Router(config)# access-list access_list_number {deny | permit} source [source_wildcard] [log]
Enables the rate limiting of the IP admission traffic to the CPU. Defines an ACL by using a source address and wildcard. The access_list_number value is a decimal number from 1 to 99 or 1300 to 1999. Enter deny or permit to specify whether to deny or permit access if conditions are matched. The source value is the source address of the network or host from which the packet is being sent specified as follows:

The 32-bit quantity in dotted-decimal format. The keyword any as an abbreviation for source and source_wildcard of 0.0.0.0 255.255.255.255. You do not need to enter a source_wildcard . The keyword host as an abbreviation for source and source-wildcard of source 0.0.0.0.
(Optional) The source_wildcard applies wildcard bits to the source. (Optional) Enter log to cause an informational logging message about the packet that matches the entry to be sent to the console.
Step 5
Router(config)# interface interface_id
Enters interface configuration mode.
45-13
Command
Step 6 Step 7
Router(config)# ip access-group {access_list_number | name} in Router(config)# ip admission name rule_name
Purpose Controls access to the specified interface. Applies the specified IP NAC rule to the interface. To remove the IP NAC rule that was applied to a specific interface, use the no ip admission rule-name interface configuration command.
Router(config)# exit Router(config)# aaa new-model Router(config)# aaa authentication eou default group radius
Returns to global configuration mode. Enables AAA. Sets authentication methods for EAPoUDP. To remove the EAPoUDP authentication methods, use the no aaa authentication eou default global configuration command.
Step 11
Router(config)# ip device tracking
Enables the IP device tracking table. To disable the IP device tracking table, use the no device tracking global configuration command.
Step 12
Router(config)# ip device tracking probe {count count | interval interval}
(Optional) Configures these parameters for the IP device tracking table:
count countSets the number of times that the switch sends the ARP probe. The range is from 1 to 5. The default is 3. interval intervalSets the number of seconds that the switch waits for a response before resending the ARP probe. The range is from 30 to 300 seconds. The default is 30 seconds.
Step 13
Router(config)# radius-server host { hostname ip_address} key string
(Optional) Configures the RADIUS server parameters. For the hostname | ip_address value, specify the hostname or IP address of the remote RADIUS server. For the key string value, specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server.
Note
Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key. This key must match the encryption used on the RADIUS daemon.
If you want to use multiple RADIUS servers, reenter this command.
45-14
OL-3999-08
Chapter 45
Command
Step 14
Router(config)# radius-server attribute 8 include-in-access-req
Purpose If the switch is connected to nonresponsive hosts, configures the switch to send the Framed-IP-Address RADIUS attribute (Attribute[8]) in access-request or accounting-request packets. Configures the network access server to recognize and use vendor-specific attributes. (Optional) Configures these IP device tracking table parameters:
Step 15 Step 16
Router(config)# radius-server vsa send authentication Router(config)# ip device tracking [probe {count count | interval interval}]
probe count countSets the number of times that the switch sends the ARP probe for an entry before removing an entry from the IP device tracking table. The range is from 1 to 5. The default is 3. probe interval intervalSets the number of seconds that the switch waits before resending the ARP probe. The range is from 30 to 300 seconds. The default is 30 seconds.
Router(config)# eou logging end Router# show ip admission {[cache] [configuration] [eapoudp]} Router# show ip device tracking {all | interface interface_id | ip ip_address | mac mac_address} Router# show ip access lists interface interface
(Optional) Enables EAPoUDP system logging events. Returns to privileged EXEC mode. Displays the NAC configuration or network admission cache entries. Displays information about the entries in the IP device tracking table. Displays the downloaded host policies in the Cisco IOS software configuration. (Optional) Saves your entries in the configuration file.
Router# copy running-config startup-config
To remove the IP NAC rule on the switch, use the no ip admission name rule_name eapoudp global configuration command. To remove the IP NAC rule that was applied to a specific interface, use the no ip admission admission_name interface configuration command. To remove the EAPoUDP authentication methods, use the no aaa authentication eou default global configuration command. To configure the auth-proxy posture code to not obtain security associations from the AAA server, use the no aaa authorization auth-proxy default global configuration command. To disable the IP device tracking table and return the parameters for the table to the default values, use the no device tracking and the no device tracking probe {count | interval} global configuration commands. To configure the switch to not send the Framed-IP-Address attribute, use the no radius-server attribute 8 include-in-access-req global configuration command. To disable the logging of EAPoUDP system events, use the no eou logging global configuration command. To clear all NAC client device entries on the switch or on the specified interface, use the clear eou privileged EXEC command. To clear entries in the IP device tracking table, use the clear ip device tracking privileged EXEC command. This example shows how to configure NAC Layer 2 IP validation on a switch interface:
45-15
Router(config)# ip admission nac eapoudp Router(config)# access-list 5 permit any any Router(config)# interface gigabitethernet 2/0/1 Router(config-if)# ip access-group 5 in Router(config-if)# ip admission name nac Router(config-if)# exit Router(config)# aaa new-model Router(config)# aaa authentication eou default group radius Router(config)# radius-server host admin key rad123 Router(config)# radius-server vsa send authentication Router(config)# ip device tracking probe count 2 Router(config)# eou logging Router(config)# end
If IEEE 802.1x authentication in single-host mode and NAC Layer 2 IP validation are configured on a switch port and IEEE 802.1x authentication of the connected hosts fails, the switch does not initiate posture validation when it receives DHCP or ARP packets from the host. If IEEE 802.1x authentication is configured on the port, the port cannot send or receive traffic other than EAPOL frames until the client is successfully authenticated.
Configuring EAPoUDP
To configure the EAPoUDP, beginning in privileged EXEC mode, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# eou allow {clientless | ip-station-id} eou default eou logging eou max-retry number eou port port_number eou ratelimit number eou timeout {aaa seconds | hold-period seconds | retransmit seconds | revalidation seconds | status-query seconds} eou revalidate Router(config)# interface interface_id Router(config)# eou default eou max-retry number eou timeout {aaa seconds | hold-period seconds | retransmit seconds | revalidation seconds | status-query seconds} eou revalidate
Purpose Enters global configuration mode. Specifies EAPoUDP values. For more information about the allow, default, logging, max-retry, port, rate-limit, revalidate, and timeout keywords, see the command reference for this release and the Network Admission Control feature module.
Step 3 Step 4
Enters interface configuration mode. Enables and configures the EAPoUDP association for the specified interface. For more information about the default, max-retry, revalidate, and timeout keywords, see the command reference for this release and the Network Admission Control feature module. Returns to privileged EXEC mode. Displays information about the EAPoUDP configuration or session cache entries. (Optional) Saves your entries in the configuration file.
Step 5 Step 6
end Router# show eou {all | authentication {clientless | eap | static} | interface interface_id | ip ip_address | mac mac_address | posturetoken name} Router# copy running-config startup-config
Step 7
45-16
OL-3999-08
Chapter 45
To return to the global default EAPoUDP values, use the no forms of the eou global configuration commands. To disable the EAPoUDP associations, use the no forms of the eou interface configuration commands.
Configuring Identity Profiles and Policies

To configure the identity profile and policy beginning in privileged EXEC mode, perform this task: Command
Router# configure terminal Router(config)# identity policy policy_name
Purpose Enters global configuration mode. Creates an identity policy, and enters identity-policy configuration mode. Defines network access attributes for the identity policy. Creates an identity profile, and enters identity-profile configuration mode. Authorizes the specified IP device, and applies the specified policy to the device. Exits from identity-profile configuration mode, and returns to global configuration mode. Returns to privileged EXEC mode. Verifies your entries. (Optional) Saves your entries in the configuration file.
Router(config-identity-policy)# access-group access_group Router(config)# identity profile eapoudp
Router(config-identity-prof)# device {authorize | not-authorize} {ip-address ip_address | mac-address mac_address | type cisco ip phone} [policy policy_name] Router(config)# exit
Router# end Router# show running-config Router# copy running-config startup-config
To remove the identity policy from the switch, use the no identity-policy policy_name global configuration command. To remove the identity profile, use the no identity profile eapoudp global configuration command. To not authorize the specified IP device and remove the specified policy from the device, use the no device {authorize | not-authorize} {ip-address ip_address | mac-address mac_address | type cisco ip phone} [policy policy_name] interface configuration command. This example shows how to configure the identity profile and policy:
Router# configure terminal Router(config)# identity policy policy1 Router(config-identity-policy)# access-group group1 Router(config)# identity profile eapoudp Router(config-identity-prof)# device authorize ip address 10.10.142.25 policy policy1 Router(config-identity-prof)# exit Router(config)# end
Configuring a NAC AAA Down Policy

Note
This feature is only available on the Catalyst 6500 series switch and the Catalyst 7600 router.
45-17
To configure NAC AAA down policy, perform this task: Command

Step 1 Step 2
Router# configure terminal Router(config)# ip admission name rule-name eapoudp event timeout aaa policy identity identity_policy_name
Purpose Enters global configuration mode. Creates a NAC a rule and associates an identity policy to be applied to sessions, when the AAA server is unreachable. To remove the rule on the switch, use the no ip admission name rule-name eapoudp event timeout aaa policy identity global configuration command. Defines the default port ACL by using a source address and wildcard. The access-list-number is a decimal number from 1 to 99 or 1300 to 1999. Enter deny or permit to specify whether to deny or permit access if conditions are matched. The source is the source address of the network or host from which the packet is being sent specified as follows:

Step 3
Router(config)# access-list access-list-number {deny | permit} source [source-wildcard] [log]
The 32-bit quantity in dotted-decimal format. The keyword any as an abbreviation for source and source-wildcard value of 0.0.0.0 255.255.255.255. You do not need to enter a source-wildcard value. The keyword host as an abbreviation for source and source-wildcard of source 0.0.0.0.
(Optional) Applies the source-wildcard wildcard bits to the source. (Optional) Enters log to cause an informational logging message about the packet that matches the entry to be sent to the console.
Router(config-if)# interface interface-id Router(config-if)# ip access-group {access-list-number | name} in Router(config-if)# ip admission name rule-name
Enters interface configuration mode. Controls access to the specified interface. Applies the specified IP NAC rule to the interface. To remove the IP NAC rule that was applied to a specific interface, use the no ip admission rule-name interface configuration command.
Router(config)# exit Router(config)# aaa new-model Router(config)# aaa authentication eou default group radius
Returns to global configuration mode. Enables AAA. Sets authentication methods for EAPoUDP. To remove the EAPoUDP authentication methods, use the no aaa authentication eou default global configuration command.
Step 10 Step 11
Router(config)# aaa authorization network default local Router(config)# ip device tracking
Sets the authorization method to local. To remove the authorization method, use no aaa authorization network default local command. Enables the IP device tracking table. To disable the IP device tracking table, use the no ip device tracking global configuration commands.
45-18
OL-3999-08
Chapter 45
Command
Step 12
Router(config)# ip device tracking [probe {count count | interval interval}]
Purpose (Optional) Configures these parameters for the IP device tracking table:

count countSets the number of times that the switch sends the ARP probe. The range is from 1 to 5. The default is 3. interval intervalSets the number of seconds that the switch waits for a response before resending the ARP probe. The range is from 30 to 300 seconds. The default is 30 seconds.
Step 13
{hostname | ip-address}
Router(config)# radius-server host test username username idle-time 1 key string
(Optional) Configures the RADIUS server parameters. For the hostname or ip-address, specify the hostname or IP address of the remote RADIUS server. For the key string value, specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server.
Note
Always configure the key as the last item in the radius-server host command syntax because leading spaces are ignored, but spaces within and at the end of the key are used. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key. This key must match the encryption used on the RADIUS daemon.
The test username value parameter is used for configuring the dummy username that tests whether the AAA server is active or not. The idle-time parameter is used to set how often the server should be tested to determine its operational status. If there is no traffic to the RADIUS server, the NAD sends dummy radius packets to the RADIUS server based on the idle-time. If you want to use multiple RADIUS servers, reenter this command.
Step 14
Router(config)# radius-server attribute 8 include-in-access-req
(Optional) Configures the switch to send the Framed-IP-Address RADIUS attribute (Attribute[8]) in access-request or accounting-request packets if the switch is connected to nonresponsive hosts. To configure the switch to not send the Framed-IP-Address attribute, use the no radius-server attribute 8 include-in-access-req global configuration command.
Router(config)# radius-server vsa send authentication Router(config)# radius-server dead-criteria {tries | time} value Router(config)# eou logging
Configures the network access server to recognize and use vendor-specific attributes. Forces one or both of the criteria (used to mark a RADIUS server as dead) to be the indicated constant. (Optional) Enables EAPoUDP system logging events. To disable the logging of EAPoUDP system events, use the no eou logging global configuration command.
Step 18 Step 19
Router(config)# end Router# show ip admission {[cache] [configuration] [eapoudp]}
Returns to privileged EXEC mode. Displays the NAC configuration or network admission cache entries.
45-19
Command
Step 20
Router# show ip device tracking {all | interface interface-id | ip ip-address | mac mac-address} Router(# copy running-config startup-config
Purpose Displays information about the entries in the IP device tracking table.
Step 21
The following example illustrates how to apply a AAA down policy:

Router# config t Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip admission name AAA_DOWN eapoudp event timeout aaa policy identity global_policy Router(config)# aaa new-model Router(config)# aaa authorization network default local Router(config)# aaa authentication eou default group radius Router(config)# identity policy global_policy Router(config-identity-policy)# ac Router(config-identity-policy)# access-group global_acl Router(config)# ip access-list extended global_acl Router(config-ext-nacl)# permit ip any any Router(config-ext-nacl)# exit Router(config)# radius-server host 40.0.0.4 test username administrator idle-time 1 key cisco Router(config)# radius-server dead-criteria tries 3 Router(config)# radius-server vsa send authentication Router(config)# radius-server attribute 8 include-in-access-req Router(config)# int fastEthernet 2/13 Router(config-if)# ip admission AAA_DOWN Router(config-if)# exit Router# show ip admission configuration Show running output ------------------aaa new-model aaa authentication eou default group radius aaa authorization network default local ip admission name AAA_DOWN eapoudp event timeout aaa policy identity global_policy
identity policy global_policy access-group global_acl interface FastEthernet2/13 switchport switchport access vlan 222 switchport mode access no ip address ip access-group 115 in ip admission AAA_DOWN ! ip access-list extended global_acl permit ip any any radius-server dead-criteria tries 3 radius-server attribute 8 include-in-access-req radius-server host 40.0.0.4 auth-port 1645 acct-port 1646 test username administrator idle-time 1 key cisco radius-server vsa send authentication
45-20
OL-3999-08
Chapter 45
Configuring Network Admission Control Displaying NAC
Router# show ip admission configuration Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes Authentication global init state time is 2 minutes Auth-proxy name AAA_DOWN eapoudp list not specified auth-cache-time 60 minutes Identity policy name global_policy for AAA fail policy
Displaying NAC
To display information about NAC Layer 2 IEEE 802.1x, use the show dot1x [all | interface interface-id | statistics interface interface-id ] privileged EXEC command.
Monitoring and Maintaining NAC

You can perform the tasks in these sections to monitor and maintain NAC:

Clearing Table Entries, page 45-21 Displaying NAC Information, page 45-21
Clearing Table Entries

To clear client entries in the EAPoUDP session table, use the clear eou privileged EXEC command. After the entries are removed, they are created only after the switch receives an ARP packet from the host or after it creates a DHCP binding entry for the host. To clear entries in the IP device tracking table on the switch, use the clear ip device tracking privileged EXEC command.
Displaying NAC Information

To display NAC information, perform one of the following tasks: Command
Router# show dot1x [all | interface interface_id | statistics interface interface_id] Router# show eou {all | authentication {clientless | eap | static} | interface interface_id | ip ip_address | mac mac_address | posturetoken name} Router# show ip admission {[cache] [configuration] [eapoudp]} Router# show ip device tracking {all | interface interface_id | ip ip_address | mac mac_address}
Purpose Displays IEEE 802.1x statistics, administrative status, and operational status. Displays information about the EAPoUDP configuration or session cache entries. Displays the NAC configuration or network admission cache entries. Displays information about the entries in the IP device tracking table.
45-21
Chapter 45 Monitoring and Maintaining NAC
Tip
45-22
OL-3999-08
C H A P T E R
46
Configuring IEEE 802.1X Port-Based Authentication

This chapter describes how to configure IEEE 802.1X port-based authentication to prevent unauthorized devices (clients) from gaining access to the network.
Note

Understanding 802.1X Port-Based Authentication, page 46-1 Default 802.1X Port-Based Authentication Configuration, page 46-6 802.1X Port-Based Authentication Guidelines and Restrictions, page 46-6 Configuring 802.1X Port-Based Authentication, page 46-7 Displaying 802.1X Status, page 46-16
Tip
Understanding 802.1X Port-Based Authentication

The IEEE 802.1X standard defines a client-server-based access control and authentication protocol that restricts unauthorized clients from connecting to a LAN through publicly accessible ports. The authentication server authenticates each client connected to a switch port and assigns the port to a VLAN before making available any services offered by the switch or the LAN. Until the client is authenticated, 802.1X access control allows only Extensible Authentication Protocol over LAN (EAPOL) traffic through the port to which the client is connected. After authentication is successful, normal traffic can pass through the port. These sections describe IEEE 802.1X port-based authentication:
46-1
Chapter 46 Understanding 802.1X Port-Based Authentication
Device Roles, page 46-2 Authentication Initiation and Message Exchange, page 46-3 Ports in Authorized and Unauthorized States, page 46-4 Supported Topologies, page 46-5
Device Roles
With 802.1X port-based authentication, the devices in the network have specific roles as shown in Figure 46-1.
Figure 46-1 802.1X Device Roles
Catalyst switch or Cisco Router Workstations (clients)
Authentication server (RADIUS)
The specific roles shown in Figure 46-1 are as follows:
ClientThe device (workstation) that requests access to the LAN and switch services and responds to requests from the switch.The workstation must be running 802.1X-compliant client software such as that offered in the Microsoft Windows XP operating system. (The client is the supplicant in the IEEE 802.1X specification.)
Note
To resolve Windows XP network connectivity and 802.1X port-based authentication issues, read the Microsoft Knowledge Base article at this URL: http://support.microsoft.com/kb/q303597/
Authentication serverPerforms the actual authentication of the client. The authentication server validates the identity of the client and notifies the switch whether or not the client is authorized to access the LAN and switch services. Because the switch acts as the proxy, the authentication service is transparent to the client. The Remote Authentication Dial-In User Service (RADIUS) security system with Extensible Authentication Protocol (EAP) extensions is the only supported authentication server; it is available in Cisco Secure Access Control Server, version 3.0. RADIUS uses a client-server model in which secure authentication information is exchanged between the RADIUS server and one or more RADIUS clients. Switch (also called the authenticator and back-end authenticator)Controls the physical access to the network based on the authentication status of the client. The switch acts as an intermediary (proxy) between the client and the authentication server, requesting identity information from the client, verifying that information with the authentication server, and relaying a response to the client. The switch includes the RADIUS client, which is responsible for encapsulating and decapsulating the EAP frames and interacting with the authentication server.
46-2
79549
OL-3999-08
Chapter 46
Configuring IEEE 802.1X Port-Based Authentication Understanding 802.1X Port-Based Authentication
When the switch receives EAPOL frames and relays them to the authentication server, the Ethernet header is stripped and the remaining EAP frame is reencapsulated in the RADIUS format. The EAP frames are not modified or examined during encapsulation, and the authentication server must support EAP within the native frame format. When the switch receives frames from the authentication server, the servers frame header is removed, leaving the EAP frame, which is then encapsulated for Ethernet and sent to the client.
Authentication Initiation and Message Exchange

The switch or the client can initiate authentication. If you enable authentication on a port by using the dot1x port-control auto interface configuration command, the switch must initiate authentication when it determines that the port link state transitions from down to up. The switch then sends an EAP-request/identity frame to the client to request its identity (typically, the switch sends an initial identity/request frame followed by one or more requests for authentication information). When the client receives the frame, it responds with an EAP-response/identity frame. If the client does not receive an EAP-request/identity frame from the switch during bootup, the client can initiate authentication by sending an EAPOL-start frame, which prompts the switch to request the clients identity.
Note
If 802.1X is not enabled or supported on the network access device, any EAPOL frames from the client are dropped. If the client does not receive an EAP-request/identity frame after three attempts to start authentication, the client transmits frames as if the port is in the authorized state. A port in the authorized state effectively means that the client has been successfully authenticated. For more information, see the Ports in Authorized and Unauthorized States section on page 46-4. When the client supplies its identity, the switch begins its role as the intermediary, passing EAP frames between the client and the authentication server until authentication succeeds or fails. If the authentication succeeds, the switch port becomes authorized. For more information, see the Ports in Authorized and Unauthorized States section on page 46-4. The specific exchange of EAP frames depends on the authentication method being used. Figure 46-2 shows a message exchange initiated by the client using the One-Time-Password (OTP) authentication method with a RADIUS server.
46-3
Chapter 46 Understanding 802.1X Port-Based Authentication
Figure 46-2 Message Exchange
Client
EAPOL-Start EAP-Request/Identity EAP-Response/Identity EAP-Request/OTP EAP-Response/OTP EAP-Success RADIUS Access-Request RADIUS Access-Challenge RADIUS Access-Request RADIUS Access-Accept Port Authorized EAPOL-Logoff
79551
Port Unauthorized
Ports in Authorized and Unauthorized States

The switch port state determines whether or not the client is granted access to the network. The port starts in the unauthorized state. While in this state, the port disallows all ingress and egress traffic except for 802.1X protocol packets. When a client is successfully authenticated, the port transitions to the authorized state, allowing all traffic for the client to flow normally. If a client that does not support 802.1X is connected to an unauthorized 802.1X port, the switch requests the clients identity. In this situation, the client does not respond to the request, the port remains in the unauthorized state, and the client is not granted access to the network. In contrast, when an 802.1X-enabled client connects to a port that is not running the 802.1X protocol, the client initiates the authentication process by sending the EAPOL-start frame. When no response is received, the client sends the request for a fixed number of times. Because no response is received, the client begins sending frames as if the port is in the authorized state. You control the port authorization state by using the dot1x port-control interface configuration command and these keywords:
force-authorizedDisables 802.1X port-based authentication and causes the port to transition to the authorized state without any authentication exchange required. The port transmits and receives normal traffic without 802.1X-based authentication of the client. This is the default setting. force-unauthorizedCauses the port to remain in the unauthorized state, ignoring all attempts by the client to authenticate. The switch cannot provide authentication services to the client through the interface. auto Enables 802.1X port-based authentication and causes the port to begin in the unauthorized state, allowing only EAPOL frames to be sent and received through the port. The authentication process begins when the link state of the port transitions from down to up or when an EAPOL-start
46-4
OL-3999-08
Chapter 46
Configuring IEEE 802.1X Port-Based Authentication Understanding 802.1X Port-Based Authentication
frame is received. The switch requests the identity of the client and begins relaying authentication messages between the client and the authentication server. Each client attempting to access the network is uniquely identified by the switch by using the clients MAC address. If the client is successfully authenticated (receives an Accept frame from the authentication server), the port state changes to authorized, and all frames from the authenticated client are allowed through the port. If the authentication fails, the port remains in the unauthorized state, but authentication can be retried. If the authentication server cannot be reached, the switch can retransmit the request. If no response is received from the server after the specified number of attempts, authentication fails, and network access is not granted. When a client logs off, it sends an EAPOL-logoff message, causing the switch port to transition to the unauthorized state. If the link state of a port transitions from up to down, or if an EAPOL-logoff frame is received, the port returns to the unauthorized state.
Supported Topologies
The 802.1X port-based authentication is supported in two topologies:

Point-to-point Wireless LAN
In a point-to-point configuration (see Figure 46-1 on page 46-2), only one client can be connected to the 802.1X-enabled switch port. The switch detects the client when the port link state changes to the up state. If a client leaves or is replaced with another client, the switch changes the port link state to down, and the port returns to the unauthorized state. Figure 46-3 shows 802.1X port-based authentication in a wireless LAN. The 802.1X port is configured as a multiple-host port that becomes authorized as soon as one client is authenticated. When the port is authorized, all other hosts indirectly attached to the port are granted access to the network. If the port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received), the switch denies access to the network to all of the attached clients. In this topology, the wireless access point is responsible for authenticating the clients attached to it, and the wireless access point acts as a client to the switch.
Figure 46-3 Wireless LAN Example
Access point Wireless clients
79550
46-5
Chapter 46 Default 802.1X Port-Based Authentication Configuration
Default 802.1X Port-Based Authentication Configuration

Table 46-1 shows the default 802.1X configuration.
Table 46-1 Default 802.1X Configuration
Feature Authentication, authorization, and accounting (AAA) RADIUS server IP address RADIUS server UDP authentication port RADIUS server key Per-interface 802.1X protocol enable state
Default Setting Disabled None specified 1812 None specified Disabled (force-authorized)
Note
The port transmits and receives normal traffic without 802.1X-based authentication of the client.
Periodic reauthentication Number of seconds between reauthentication attempts Quiet period
Disabled 3600 seconds 60 seconds (number of seconds that the switch remains in the quiet state following a failed authentication exchange with the client) 30 seconds (number of seconds that the switch should wait for a response to an EAP request/identity frame from the client before retransmitting the request) 2 times (number of times that the switch will send an EAP-request/identity frame before restarting the authentication process) Disabled 30 seconds (when relaying a request from the authentication server to the client, the amount of time the switch waits for a response before retransmitting the request to the client) 30 seconds (when relaying a response from the client to the authentication server, the amount of time the switch waits for a reply before retransmitting the response to the server)
Retransmission time
Maximum retransmission number
Multiple host support Client timeout period
Authentication server timeout period
802.1X Port-Based Authentication Guidelines and Restrictions

When configuring 802.1X port-based authentication, follow these guidelines and restrictions:

When 802.1X is enabled, ports are authenticated before any other Layer 2 or Layer 3 features are enabled. The 802.1X protocol is supported on both Layer 2 static-access ports and Layer 3 routed ports, but it is not supported on these port types:
46-6
OL-3999-08
Chapter 46
Configuring IEEE 802.1X Port-Based Authentication Configuring 802.1X Port-Based Authentication
Trunk portIf you try to enable 802.1X on a trunk port, an error message appears, and 802.1X
is not enabled. If you try to change the mode of an 802.1X-enabled port to trunk, the port mode is not changed.
EtherChannel portBefore enabling 802.1X on the port, you must first remove it from the
EtherChannel port-channel interface. If you try to enable 802.1X on an EtherChannel port-channel interface or on an individual active port in an EtherChannel, an error message appears, and 802.1X is not enabled. If you enable 802.1X on a not-yet active individual port of an EtherChannel, the port does not join the EtherChannel.
Secure portYou cannot configure a secure port as an 802.1X port. If you try to enable 802.1X
on a secure port, an error message appears, and 802.1X is not enabled. If you try to change an 802.1X-enabled port to a secure port, an error message appears, and the security settings are not changed.
Switch Port Analyzer (SPAN) destination portYou can enable 802.1X on a port that is a SPAN
destination port; however, 802.1X is disabled until the port is removed as a SPAN destination port. You can enable 802.1X on a SPAN source port.
The 802.1X protocol is not supported on ports configured with voice VLAN.
Configuring 802.1X Port-Based Authentication

These sections describe how to configure 802.1X port-based authentication:

Enabling 802.1X Port-Based Authentication, page 46-7 Configuring Switch-to-RADIUS-Server Communication, page 46-9 Enabling Periodic Reauthentication, page 46-10 Manually Reauthenticating the Client Connected to a Port, page 46-11 Initializing Authentication for the Client Connected to a Port, page 46-11 Changing the Quiet Period, page 46-12 Changing the Switch-to-Client Retransmission Time, page 46-12 Setting the Switch-to-Client Frame Retransmission Number, page 46-14 Enabling Multiple Hosts, page 46-15 Resetting the 802.1X Configuration to the Default Values, page 46-15
Enabling 802.1X Port-Based Authentication

To enable 802.1X port-based authentication, you must enable AAA and specify the authentication method list. A method list describes the sequence and authentication methods to be queried to authenticate a user. The software uses the first method listed to authenticate users; if that method fails to respond, the software selects the next authentication method in the method list. This process continues until there is successful communication with a listed authentication method or until all defined methods are exhausted. If authentication fails at any point in this cycle, the authentication process stops, and no other authentication methods are attempted. To configure 802.1X port-based authentication, perform this task:
46-7
Chapter 46 Configuring 802.1X Port-Based Authentication
Command
Step 1
Router(config)# aaa new-model Router(config)# no aaa new-model
Purpose Enables AAA. Disables AAA. Creates an 802.1X port-based authentication method list. Clears the configured method list. Globally enables 802.1X port-based authentication. Globally disables 802.1X port-based authentication. Enters interface configuration mode and specifies the interface to be enabled for 802.1X port-based authentication. Enables 802.1X port-based authentication on the interface. Disables 802.1X port-based authentication on the interface. Returns to privileged EXEC mode. Verifies your entries. Check the Status column in the 802.1X Port Summary section of the display. An enabled status means the port-control value is set either to auto or to force-unauthorized.
Step 2
Router(config)# aaa authentication dot1x {default} method1 [method2... ] Router(config)# no aaa authentication dot1x {default | list_name}
Step 3
Router(config)# dot1x system-auth-control Router(config)# no dot1x system-auth-control
Step 4
slot/port
Step 5
Router(config-if)# dot1x port-control auto
Router(config-if)# no dot1x port-control auto
Step 6 Step 7
Router(config)# end Router# show dot1x all
1.
When you enable 802.1X port-based authentication, note the following information:
To create a default list that is used when a named list is not specified in the authentication command, use the default keyword followed by the methods that are to be used in default situations. The default method list is automatically applied to all interfaces. Enter at least one of these keywords:
group radiusUse the list of all RADIUS servers for authentication. noneUse no authentication. The client is automatically authenticated by the switch without
using the information supplied by the client. This example shows how to enable AAA and 802.1X on Fast Ethernet port 5/1:
Router# configure terminal Router(config)# aaa new-model Router(config)# aaa authentication dot1x default group radius Router(config)# dot1x system-auth-control Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x port-control auto Router(config-if)# end

Router# show dot1x all Dot1x Info for interface FastEthernet5/1 ----------------------------------------------------
46-8
OL-3999-08
Chapter 46
AuthSM State BendSM State PortStatus MaxReq MultiHosts Port Control QuietPeriod Re-authentication ReAuthPeriod ServerTimeout SuppTimeout TxPeriod
= = = = = = = = = = = =
FORCE UNAUTHORIZED IDLE UNAUTHORIZED 2 Disabled Force UnAuthorized 60 Seconds Disabled 3600 Seconds 30 Seconds 30 Seconds 30 Seconds
Configuring Switch-to-RADIUS-Server Communication

RADIUS security servers are identified by any of the following:

Host name Host IP address Host name and specific UDP port numbers IP address and specific UDP port numbers
The combination of the IP address and UDP port number creates a unique identifier, which enables RADIUS requests to be sent to multiple UDP ports on a server at the same IP address. If two different host entries on the same RADIUS server are configured for the same service (for example, authentication) the second host entry configured acts as the failover backup to the first one. The RADIUS host entries are tried in the order that they were configured. To configure the RADIUS server parameters, perform this task: Command
Step 1
Router(config)# ip radius source-interface interface_name Router(config)# no ip radius source-interface
Purpose Specifies that the RADIUS packets have the IP address of the indicated interface. Prevents the RADIUS packets from having the IP address of the previously indicated interface. Configures the RADIUS server host name or IP address on the switch. If you want to use multiple RADIUS servers, reenter this command.
Step 2
Router(config)# radius-server host {hostname | ip_address}
Router(config)# no radius-server host {hostname | ip_address}
Deletes the specified RADIUS server. Configures the authorization and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. Returns to privileged EXEC mode.
Step 3
Router(config)# radius-server key string
Step 4
Router(config)# end
When you configure the RADIUS server parameters, note the following information:

For hostname or ip_address, specify the host name or IP address of the remote RADIUS server. Specify the key string on a separate command line.
46-9
For key string , specify the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. The key is a text string that must match the encryption key used on the RADIUS server. When you specify the key string, spaces within and at the end of the key are used. If you use spaces in the key, do not enclose the key in quotation marks unless the quotation marks are part of the key. This key must match the encryption used on the RADIUS daemon. You can globally configure the timeout, retransmission, and encryption key values for all RADIUS servers by using the radius-server host global configuration command. If you want to configure these options on a per-server basis, use the radius-server timeout, radius-server retransmit, and the radius-server key global configuration commands. For more information, refer to the Cisco IOS Security Configuration Guide, Release 12.2, publication and the Cisco IOS Security Command Reference, Release 12.2, publication at this URL: http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configuratio n_guides_list.html
Note
You also need to configure some settings on the RADIUS server. These settings include the IP address of the switch and the key string to be shared by both the server and the switch. For more information, refer to the RADIUS server documentation. This example shows how to configure the RADIUS server parameters on the switch:
Router# configure terminal Router(config)# ip radius source-interface Vlan80 Router(config)# radius-server host 172.l20.39.46 Router(config)# radius-server key rad123 Router(config)# end
Enabling Periodic Reauthentication

You can enable periodic 802.1X client reauthentication and specify how often it occurs. If you do not specify a time period before enabling reauthentication, the number of seconds between reauthentication attempts is 3600. Automatic 802.1X client reauthentication is a global setting and cannot be set for clients connected to individual ports. To manually reauthenticate the client connected to a specific port, see the Manually Reauthenticating the Client Connected to a Port section on page 46-11. To enable periodic reauthentication of the client and to configure the number of seconds between reauthentication attempts, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# dot1x reauthentication
Purpose Selects an interface to configure. Enables periodic reauthentication of the client, which is disabled by default. Disables periodic reauthentication of the client.
Router(config-if)# no dot1x reauthentication
46-10
OL-3999-08
Chapter 46
Command
Step 3
Router(config-if)# dot1x timeout reauth-period seconds
Purpose Sets the number of seconds between reauthentication attempts. The range is 1 to 65535; the default is 3600 seconds. This command affects the behavior of the switch only if periodic reauthentication is enabled.
Router(config-if)# no dot1x timeout reauth-period
Returns to the default reauthorization period. Returns to privileged EXEC mode. Verifies your entries.
Step 4 Step 5
Router(config-if)# end Router# show dot1x all 1.
This example shows how to enable periodic reauthentication and set the number of seconds between reauthentication attempts to 4000:
Router(config-if)# dot1x reauthentication Router(config-if)# dot1x timeout reauth-period 4000
Manually Reauthenticating the Client Connected to a Port

Note
Reauthentication does not disturb the status of an already authorized port. To manually reauthenticate the client connected to a port, perform this task:
Command
Step 1 Step 2
Router# dot1x re-authenticate interface type1 slot/port Router# show dot1x all 1.
Purpose Manually reauthenticates the client connected to a port. Verifies your entries.
This example shows how to manually reauthenticate the client connected to Fast Ethernet port 5/1:
Router# dot1x re-authenticate interface fastethernet 5/1 Starting reauthentication on FastEthernet 5/1
Initializing Authentication for the Client Connected to a Port

Note
Initializing authentication disables any existing authentication before authenticating the client connected to the port. To initialize the authentication for the client connected to a port, perform this task:
46-11
Command
Step 1 Step 2
Router# dot1x initialize interface type1 slot/port Router# show dot1x all 1.
Purpose Initializes the authentication for the client connected to a port. Verifies your entries.
This example shows how to initialize the authentication for the client connected to Fast Ethernet port 5/1:
Router# dot1x initialize interface fastethernet 5/1 Starting reauthentication on FastEthernet 5/1
Changing the Quiet Period

When the switch cannot authenticate the client, the switch remains idle for a set period of time, and then tries again. The idle time is determined by the quiet-period value. A failed authentication of the client might occur because the client provided an invalid password. You can provide a faster response time to the user by entering a smaller number than the default. To change the quiet period, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects an interface to configure. Sets the number of seconds that the switch remains in the quiet state following a failed authentication exchange with the client. The range is 0 to 65535 seconds; the default is 60. Returns to the default quiet time. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x timeout quiet-period seconds
Router(config-if)# no dot1x timeout quiet-period
Step 3 Step 4
This example shows how to set the quiet time on the switch to 30 seconds:
Router(config-if)# dot1x timeout quiet-period 30
Changing the Switch-to-Client Retransmission Time

The client responds to the EAP-request/identity frame from the switch with an EAP-response/identity frame. If the switch does not receive this response, it waits a set period of time (known as the retransmission time), and then retransmits the frame.
Note
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers.
46-12
OL-3999-08
Chapter 46
To change the amount of time that the switch waits for client notification, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# dot1x timeout tx-period seconds
Purpose Selects an interface to configure. Sets the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before retransmitting the request. The range is 1 to 65535 seconds; the default is 30. Returns to the default retransmission time. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x timeout tx-period
Step 3 Step 4
This example shows how to set 60 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before retransmitting the request:
Router(config)# dot1x timeout tx-period 60
Setting the Switch-to-Client Retransmission Time for EAP-Request Frames

The client notifies the switch that it received the EAP-request frame. If the switch does not receive this notification, the switch waits a set period of time, and then retransmits the frame. You may set the amount of time that the switch waits for notification from 1 to 65535 seconds. (The default is 30 seconds.) To set the switch-to-client retransmission time for the EAP-request frames, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects an interface to configure. Sets the switch-to-client retransmission time for the EAP-request frame. Returns to the default retransmission time. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x timeout supp-timeout seconds Router(config-if)# no dot1x timeout supp-timeout
Step 3 Step 4
Router# end Router# show dot1x all 1.
This example shows how to set the switch-to-client retransmission time for the EAP-request frame to 25 seconds:
Router(config-if)# dot1x timeout supp-timeout 25
46-13
Setting the Switch-to-Authentication-Server Retransmission Time for Layer 4 Packets

The authentication server notifies the switch each time it receives a Layer 4 packet. If the switch does not receive a notification after sending a packet, the switch waits a set period of time and then retransmits the packet. You may set the amount of time that the switch waits for notification from 1 to 65535 seconds. (The default is 30 seconds.) To set the value for the retransmission of Layer 4 packets from the switch to the authentication server, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects an interface to configure. Sets the switch-to-authentication-server retransmission time for Layer 4 packets. Returns to the default retransmission time. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x timeout server-timeout seconds Router(config-if)# no dot1x timeout server-timeout
Step 3 Step 4
This example shows how to set the switch-to-authentication-server retransmission time for Layer 4 packets to 25 seconds:
Router(config-if)# dot1x timeout server-timeout 25
Setting the Switch-to-Client Frame Retransmission Number

In addition to changing the switch-to-client retransmission time, you can change the number of times that the switch sends an EAP-request/identity frame (assuming no response is received) to the client before restarting the authentication process.
Note
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific behavioral problems with certain clients and authentication servers. To set the switch-to-client frame retransmission number, perform this task:
Command
Step 1 Step 2
1
Purpose
slot/port
Selects an interface to configure. Sets the number of times that the switch sends an EAP-request/identity frame to the client before restarting the authentication process. The range is 1 to 10; the default is 2. Returns to the default retransmission number.
Router(config-if)# dot1x max-req count
Router(config-if)# no dot1x max-req
46-14
OL-3999-08
Chapter 46
Command
Step 3 Step 4
Purpose Returns to privileged EXEC mode. Verifies your entries.
This example shows how to set 5 as the number of times that the switch sends an EAP-request/identity request before restarting the authentication process:
Router(config-if)# dot1x max-req 5
Enabling Multiple Hosts

You can attach multiple hosts to a single 802.1X-enabled port as shown in Figure 46-3 on page 46-5. In this mode, only one of the attached hosts must be successfully authorized for all hosts to be granted network access. If the port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received), all attached clients are denied access to the network. To allow multiple hosts (clients) on an 802.1X-authorized port that has the dot1x port-control interface configuration command set to auto, perform this task: Command
Step 1 Step 2
Router(config)# interface type1 slot/port Router(config-if)# dot1x host-mode multi-host
Purpose Selects an interface to configure. Allows multiple hosts (clients) on an 802.1X-authorized port.
Note
Make sure that the dot1x port-control interface configuration command set is set to auto for the specified interface.
Router(config-if)# dot1x host-mode single-host
Disables multiple hosts on the port. Returns to privileged EXEC mode. Verifies your entries.
Step 3 Step 4
Router(config-if)# end Router# show dot1x interface type 1.

1
slot/port
This example shows how to enable 802.1X on Fast Ethernet interface 5/1 and to allow multiple hosts:
Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x port-control auto Router(config-if)# dot1x host-mode multi-host
Resetting the 802.1X Configuration to the Default Values

To reset the 802.1X configuration to the default values, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects an interface to configure. Resets the configurable 802.1X parameters to the default values.
Router(config-if)# dot1x default
46-15
Chapter 46 Displaying 802.1X Status
Command
Step 3 Step 4
Purpose Returns to privileged EXEC mode. Verifies your entries.
Displaying 802.1X Status

To display global 802.1X administrative and operational status for the switch, use the show dot1x privileged EXEC command. To display the 802.1X administrative and operational status for a specific interface, use the show dot1x interface interface-id privileged EXEC command. For detailed information about the fields in these displays, refer to the Cisco IOS Master Command List, Release 12.2SX.
Tip
46-16
OL-3999-08
C H A P T E R
47
Configuring Port Security

This chapter describes how to configure the port security feature.
Note

Understanding Port Security, page 47-1 Default Port Security Configuration, page 47-3 Port Security Guidelines and Restrictions, page 47-3 Configuring Port Security, page 47-4 Displaying Port Security Settings, page 47-13
Tip
Understanding Port Security

These sections describe port security:

Port Security with Dynamically Learned and Static MAC Addresses, page 47-2 Port Security with Sticky MAC Addresses, page 47-3
47-1
Chapter 47 Understanding Port Security
Port Security with Dynamically Learned and Static MAC Addresses

You can use port security with dynamically learned and static MAC addresses to restrict a ports ingress traffic by limiting the MAC addresses that are allowed to send traffic into the port. When you assign secure MAC addresses to a secure port, the port does not forward ingress traffic that has source addresses outside the group of defined addresses. If you limit the number of secure MAC addresses to one and assign a single secure MAC address, the device attached to that port has the full bandwidth of the port. A security violation occurs in either of these situations:
When the maximum number of secure MAC addresses is reached on a secure port and the source MAC address of the ingress traffic is different from any of the identified secure MAC addresses, port security applies the configured violation mode. If traffic with a secure MAC address that is configured or learned on one secure port attempts to access another secure port in the same VLAN, port security responds to the violation in one of these ways:
In Release 12.2(18)SXF5 and later releases, port security applies the configured violation
mode.
In releases earlier than Release 12.2(18)SXF5, port security applies the shutdown violation
mode.
Note
After a secure MAC address is configured or learned on one secure port, the sequence of events that occurs when port security detects that secure MAC address on a different port in the same VLAN is known as a MAC move violation.
See the Configuring the Port Security Violation Mode on a Port section on page 47-7 for more information about the violation modes. After you have set the maximum number of secure MAC addresses on a port, port security includes the secure addresses in the address table in one of these ways:

You can statically configure all secure MAC addresses by using the switchport port-security mac-address mac_address interface configuration command. You can allow the port to dynamically configure secure MAC addresses with the MAC addresses of connected devices. You can statically configure a number of addresses and allow the rest to be dynamically configured.
If the port has a link-down condition, all dynamically learned addresses are removed. Following bootup, a reload, or a link-down condition, port security does not populate the address table with dynamically learned MAC addresses until the port receives ingress traffic. A security violation occurs if the maximum number of secure MAC addresses have been added to the address table and the port receives traffic from a MAC address that is not in the address table. You can configure the port for one of three violation modes: protect, restrict, or shutdown. See the Configuring Port Security section on page 47-4. To ensure that an attached device has the full bandwidth of the port, set the maximum number of addresses to one and configure the MAC address of the attached device.
47-2
OL-3999-08
Chapter 47
Configuring Port Security Default Port Security Configuration
Port Security with Sticky MAC Addresses

Release 12.2(18)SXE and later releases support port security with sticky MAC addresses. Port security with sticky MAC addresses provides many of the same benefits as port security with static MAC addresses, but sticky MAC addresses can be learned dynamically. Port security with sticky MAC addresses retains dynamically learned MAC addresses during a link-down condition. If you enter a write memory or copy running-config startup-config command, then port security with sticky MAC addresses saves dynamically learned MAC addresses in the startup-config file and the port does not have to learn addresses from ingress traffic after bootup or a restart.
Default Port Security Configuration

Table 47-1 shows the default port security configuration for an interface.
Table 47-1 Default Port Security Configuration
Feature Port security Maximum number of secure MAC addresses Violation mode
Default Setting Disabled. 1. Shutdown. The port shuts down when the maximum number of secure MAC addresses is exceeded, and an SNMP trap notification is sent.
Port Security Guidelines and Restrictions

When configuring port security, follow these guidelines:
With the default port security configuration, to bring all secure ports out of the error-disabled state, enter the errdisable recovery cause psecure-violation global configuration command, or manually reenable it by entering the shutdown and no shut down interface configuration commands. Enter the clear port-security dynamic global configuration command to clear all dynamically learned secure addresses. See the Cisco IOS Master Command List, Release 12.2SX, for complete syntax information. Port security learns unauthorized MAC addresses with a bit set that causes traffic to them or from them to be dropped. The show mac-address-table command displays the unauthorized MAC addresses, but does not display the state of the bit. (CSCeb76844) To preserve dynamically learned sticky MAC addresses and configure them on a port following a bootup or a reload and after the dynamically learned sticky MAC addresses have been learned, you must enter a write memory or copy running-config startup-config command to save them in the startup-config file. With Release 12.2(18)SXE and later releases, port security supports private VLAN (PVLAN) ports. With releases earlier than Release 12.2(18)SXE, port security does not support PVLAN ports. With Release 12.2(18)SXE and later releases, port security supports nonnegotiating trunks.
Port security only supports trunks configured with these commands:
47-3
Chapter 47 Configuring Port Security
switchport switchport trunk encapsulation switchport mode trunk switchport nonegotiate

If you reconfigure a secure access port as a trunk, port security converts all the sticky and static
secure addresses on that port that were dynamically learned in the access VLAN to sticky or static secure addresses on the native VLAN of the trunk. Port security removes all secure addresses on the voice VLAN of the access port.
If you reconfigure a secure trunk as an access port, port security converts all sticky and static
addresses learned on the native VLAN to addresses learned on the access VLAN of the access port. Port security removes all addresses learned on VLANs other than the native VLAN.
Note
Port security uses the VLAN ID configured with the switchport trunk native vlan command for both IEEE 802.1Q trunks and ISL trunks.
With releases earlier than Release 12.2(18)SXE, port security does not support trunks. With Release 12.2(18)SXE and later releases, port security supports IEEE 802.1Q tunnel ports. With releases earlier than Release 12.2(18)SXE, port security does not support IEEE 802.1Q tunnel ports. Port security does not support Switch Port Analyzer (SPAN) destination ports. Port security does not support EtherChannel port-channel interfaces. With releases earlier than Release 12.2(33)SXH, port security and 802.1X port-based authentication cannot both be configured on the same port:
If you try to enable 802.1X port-based authentication on a secure port, an error message appears
and 802.1X port-based authentication is not enabled on the port.

If you try to enable port security on a port configured for 802.1X port-based authentication, an
error message appears and port security is not enabled on the port.
Take care when you enable port security on the ports connected to the adjacent switches when there are redundant links running between the switches because port security might error-disable the ports due to port security violations.

These sections describe how to configure port security:

Enabling Port Security, page 47-5 Configuring the Port Security Violation Mode on a Port, page 47-7 Configuring the Port Security Rate Limiter, page 47-8 Configuring the Maximum Number of Secure MAC Addresses on a Port, page 47-9 Enabling Port Security with Sticky MAC Addresses on a Port, page 47-10 Configuring a Static Secure MAC Address on a Port, page 47-11 Configuring Secure MAC Address Aging on a Port, page 47-12
47-4
OL-3999-08
Chapter 47
Configuring Port Security Configuring Port Security
Enabling Port Security

These sections describe how to enable port security:

Enabling Port Security on a Trunk, page 47-5 Enabling Port Security on an Access Port, page 47-6
Enabling Port Security on a Trunk

With Release 12.2(18)SXE and later releases, port security supports nonnegotiating trunks.
Caution
Because the default number of secure addresses is one and the default violation action is to shut down the port, configure the maximum number of secure MAC addresses on the port before you enable port security on a trunk (see Configuring the Maximum Number of Secure MAC Addresses on a Port section on page 47-9). To enable port security on a trunk, perform this task:
Command
Router(config)# interface type Router(config-if)# switchport Router(config-if)# switchport trunk encapsulation {isl | dot1q} Router(config-if)# switchport mode trunk Router(config-if)# switchport nonegotiate Router(config-if)# switchport port-security Router(config-if)# no switchport port-security
1
Purpose
slot/port
Selects the LAN port to configure. Configures the port as a Layer 2 switchport. Configures the encapsulation, which configures the Layer 2 switching port as either an ISL or 802.1Q trunk. Configures the port to trunk unconditionally. Configures the trunk not to use DTP. Enables port security on the trunk. Disables port security on the trunk. Verifies the configuration.
Step 7
Router(config-if)# do show port-security interface type1 slot/port | include Port Security 1.
This example shows how to configure Fast Ethernet port 5/36 as a nonnegotiating trunk and enable port security:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/36 Router(config-if)# switchport Router(config-if)# switchport mode trunk Router(config-if)# switchport nonegotiate Router(config-if)# switchport port-security Router(config-if)# do show port-security interface fastethernet 5/36 | include Port Security Port Security : Enabled
47-5
Enabling Port Security on an Access Port

To enable port security on an access port, perform this task: Command
Step 1
1
Purpose
slot/port
Selects the LAN port to configure.

Note
With Release 12.2(18)SXE and later releases, the port can be a tunnel port or a PVLAN port.
Step 2 Step 3
Router(config-if)# switchport Router(config-if)# switchport mode access
Configures the port as a Layer 2 switchport. Configures the port as a Layer 2 access port.
Note
A port in the default mode (dynamic desirable) cannot be configured as a secure port.
Step 4
Router(config-if)# switchport port-security Router(config-if)# no switchport port-security
Enables port security on the port. Disables port security on the port. Verifies the configuration.
Step 5
Router(config-if)# do show port-security interface type1 slot/port | include Port Security 1.
This example shows how to enable port security on Fast Ethernet port 5/12:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/12 Router(config-if)# switchport Router(config-if)# switchport mode access Router(config-if)# switchport port-security Router(config-if)# do show port-security interface fastethernet 5/12 | include Port Security Port Security : Enabled
47-6
OL-3999-08
Chapter 47
Configuring the Port Security Violation Mode on a Port

To configure the port security violation mode on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. (Optional) Sets the violation mode and the action to be taken when a security violation is detected. Reverts to the default configuration (shutdown). Verifies the configuration.
Router(config-if)# switchport port-security violation {protect | restrict | shutdown} Router(config-if)# no switchport port-security violation
Step 3
Router(config-if)# do show port-security interface type1 slot/port | include violation_mode2 1. 2.
type = ethernet , fastethernet, gigabitethernet , or tengigabitethernet violation_mode = protect, restrict , or shutdown
When configuring port security violation modes, note the following information:

protectDrops packets with unknown source addresses until you remove a sufficient number of secure MAC addresses to drop below the maximum value. restrictDrops packets with unknown source addresses until you remove a sufficient number of secure MAC addresses to drop below the maximum value and causes the SecurityViolation counter to increment. shutdown Puts the interface into the error-disabled state immediately and sends an SNMP trap notification.
Note
To bring a secure port out of the error-disabled state, enter the errdisable recovery cause violation_mode global configuration command, or you can manually reenable it by entering the shutdown and no shut down interface configuration commands. To protect the CPU against overutilization, when you configure the protect or restrict violation modes, configure the packet drop rate limiter (see the Configuring the Port Security Rate Limiter section on page 47-8).
This example shows how to configure the protect security violation mode on Fast Ethernet port 5/12:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 3/12 Router(config-if)# switchport port-security violation protect Router(config-if)# do show port-security interface fastethernet 5/12 | include Protect Violation Mode : Protect
This example shows how to configure the restrict security violation mode on Fast Ethernet port 5/12:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 3/12 Router(config-if)# switchport port-security violation restrict Router(config-if)# do show port-security interface fastethernet 5/12 | include Restrict Violation Mode : Restrict
47-7
Configuring the Port Security Rate Limiter

Note
The PFC2 does not support the port security rate limiter. The truncated switching mode does not support the port security rate limiter.
Port security examines all traffic received by secure ports to detect violations or to recognize and secure new MAC addresses. When the shutdown violation mode is configured, traffic cannot enter the secure port after a violation has been detected, which removes the possibility that violations might cause excessive CPU load. When the protect or restrict violation modes are configured, port security continues to process traffic after a violation occurs, which might cause excessive CPU load. Configure the port security rate limiter to protect the CPU against excessive load when the protect or restrict violation modes are configured. To configure the port security rate limiter, perform this task: Command
Step 1
Router(config)# mls rate-limit layer2 port-security rate_in_pps [burst_size] Router(config)# no mls rate-limit layer2 port-security
Purpose Configures the port security rate limiter. Reverts to the default configuration. Verifies the configuration.
Step 2
Router(config)# do show mls rate-limit | include PORTSEC
When configuring the port security rate limiter, note the following information:
For the rate_in_pps value:

The range is 10 through 1,000,000 (entered as 1000000). There is no default value. The lower the value, the more the CPU is protected. The rate limiter is applied to traffic both
before and after a security violation occurs. Configure a value high enough to permit nonviolating traffic to reach the port security feature.
Values lower than 1,000 (entered as 1000) should offer sufficient protection.
For the burst_size value:

The range is 1 through 255. The default is 10. The default value should provide sufficient protection.
This example shows how to configure the port security rate limiter:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls rate-limit layer2 port-security 1000 Router(config)# end

Router# show mls rate-limit | include PORTSEC LAYER_2 PORTSEC On 1000 1 Not sharing
47-8
OL-3999-08
Chapter 47
Configuring the Maximum Number of Secure MAC Addresses on a Port

To configure the maximum number of secure MAC addresses on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Sets the maximum number of secure MAC addresses for the port (default is 1).
Note
Router(config-if)# switchport port-security maximum number_of_addresses vlan {vlan_ID | vlan_range}
Per-VLAN configuration is supported only on trunks.
Router(config-if)# no switchport port-security maximum
Reverts to the default configuration. Verifies the configuration.
Step 3
Router(config-if)# do show port-security interface type1 slot/port | include Maximum 1.
When configuring the maximum number of secure MAC addresses on a port, note the following information:

With Release 12.2(18)SXE and later releases, the range for number_of_addresses is 1 to 4,097. With releases earlier than Release 12.2(18)SXE, the range for number_of_addresses is 1 to 1,024. With Release 12.2(18)SXE and later releases, port security supports trunks.
On a trunk, you can configure the maximum number of secure MAC addresses both on the trunk
and for all the VLANs on the trunk.

You can configure the maximum number of secure MAC addresses on a single VLAN or a range
of VLANs.
For a range of VLANs, enter a dash-separated pair of VLAN numbers. You can enter a comma-separated list of VLAN numbers and dash-separated pairs of VLAN
numbers. This example shows how to configure a maximum of 64 secure MAC addresses on Fast Ethernet port 5/12:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 3/12 Router(config-if)# switchport port-security maximum 64 Router(config-if)# do show port-security interface fastethernet 5/12 | include Maximum Maximum MAC Addresses : 64
47-9
Enabling Port Security with Sticky MAC Addresses on a Port

Release 12.2(18)SXE and later releases support port security with sticky MAC addresses. To enable port security with sticky MAC addresses on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Enables port security with sticky MAC addresses on a port. Disables port security with sticky MAC addresses on a port.
Router(config-if)# switchport port-security mac-address sticky Router(config-if)# no switchport port-security mac-address sticky 1.
When enabling port security with sticky MAC addresses, note the following information:
When you enter the switchport port-security mac-address sticky command:

All dynamically learned secure MAC addresses on the port are converted to sticky secure MAC
addresses.
Static secure MAC addresses are not converted to sticky MAC addresses. Secure MAC addresses dynamically learned in a voice VLAN are not converted to sticky MAC
addresses.
New dynamically learned secure MAC addresses are sticky.
When you enter the no switchport port-security mac-address sticky command, all sticky secure MAC addresses on the port are converted to dynamic secure MAC addresses. To preserve dynamically learned sticky MAC addresses and configure them on a port following a bootup or a reload, after the dynamically learned sticky MAC addresses have been learned, you must enter a write memory or copy running-config startup-config command to save them in the startup-config file.
This example shows how to enable port security with sticky MAC addresses on Fast Ethernet port 5/12:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/12 Router(config-if)# switchport port-security mac-address sticky
47-10
OL-3999-08
Chapter 47
Configuring a Static Secure MAC Address on a Port

To configure a static secure MAC address on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Configures a static MAC address as secure on the port.
Note
Router(config-if)# switchport port-security mac-address [sticky] mac_address [vlan vlan_ID]
Per-VLAN configuration is supported only on trunks.
Router(config-if)# no switchport port-security mac-address [sticky] mac_address
Clears a static secure MAC address from the port. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show port-security address 1.
When configuring a static secure MAC address on a port, note the following information:
With Release 12.2(18)SXE and later releases, you can configure sticky secure MAC addresses if port security with sticky MAC addresses is enabled (see the Enabling Port Security with Sticky MAC Addresses on a Port section on page 47-10). The maximum number of secure MAC addresses on the port, configured with the switchport port-security maximum command, defines how many secure MAC addresses you can configure. If you configure fewer secure MAC addresses than the maximum, the remaining MAC addresses are learned dynamically. With Release 12.2(18)SXE and later releases, port security is supported on trunks.
On a trunk, you can configure a static secure MAC address in a VLAN. On a trunk, if you do not configure a VLAN for a static secure MAC address, it is secure in the
VLAN configured with the switchport trunk native vlan command. This example shows how to configure a MAC address 1000.2000.3000 as secure on Fast Ethernet port 5/12 and verify the configuration:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/12 Router(config-if)# switchport port-security mac-address 1000.2000.3000 Router(config-if)# end Router# show port-security address Secure Mac Address Table -----------------------------------------------------------Vlan ---1 Mac Address ----------1000.2000.3000 Type ---SecureConfigured Ports ----Fa5/12
47-11
Configuring Secure MAC Address Aging on a Port

When the aging type is configured with the absolute keyword, all the dynamically learned secure addresses age out when the aging time expires. When the aging type is configured with the inactivity keyword, the aging time defines the period of inactivity after which all the dynamically learned secure addresses age out.
Note
Static secure MAC addresses and sticky secure MAC addresses do not age out. These sections describe how to configure secure MAC address aging on a port:

Configuring the Secure MAC Address Aging Type on a Port, page 47-12 Configuring Secure MAC Address Aging Time on a Port, page 47-13
Configuring the Secure MAC Address Aging Type on a Port

With a PFC3 and Release 12.2(18)SXE and later releases, you can configure the secure MAC address aging type on a port. With a PFC2, you cannot configure the secure MAC address aging type. The PFC2 supports only absolute aging. To configure the secure MAC address aging type on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Configures the secure MAC address aging type on the port (default is absolute). Reverts to the default MAC address aging type. Verifies the configuration.
Router(config-if)# switchport port-security aging type {absolute | inactivity} Router(config-if)# no switchport port-security aging type
Step 3
Router(config-if)# do show port-security interface type1 slot/port | include Time 1.
This example shows how to set the aging type to inactivity on Fast Ethernet Port 5/12:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/12 Router(config-if)# switchport port-security aging type inactivity Router(config-if)# do show port-security interface fastethernet 5/12 | include Type Aging Type : Inactivity
47-12
OL-3999-08
Chapter 47
Configuring Port Security Displaying Port Security Settings
Configuring Secure MAC Address Aging Time on a Port

To configure the secure MAC address aging time on a port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Configures the secure MAC address aging time on the port. The aging_time range is 1 to 1440 minutes (default is 0). Disables secure MAC address aging time. Verifies the configuration.
Router(config-if)# switchport port-security aging time aging_time
Router(config-if)# no switchport port-security aging time
Step 3
Router(config-if)# do show port-security interface type1 slot/port | include Time 1.
This example shows how to configure 2 hours (120 minutes) as the secure MAC address aging time on Fast Ethernet Port 5/1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface fastethernet 5/1 Router(config-if)# switchport port-security aging time 120 Router(config-if)# do show port-security interface fastethernet 5/12 | include Time Aging Time : 120 mins
Displaying Port Security Settings

To display port security settings, enter this command: Command
Router# show port-security [interface {{vlan vlan_ID} | {type1 slot/port}}] [address] 1.
Purpose Displays port security settings for the switch or for the specified interface.
When displaying port security settings, note the following information:

Port security supports the vlan keyword only on trunks. Enter the address keyword to display secure MAC addresses, with aging information for each address, globally for the switch or per interface. The display includes these values:
The maximum allowed number of secure MAC addresses for each interface The number of secure MAC addresses on the interface The number of security violations that have occurred The violation mode.
47-13
Chapter 47 Displaying Port Security Settings
This example displays output from the show port-security command when you do not enter an interface:
Router# show port-security Secure Port MaxSecureAddr CurrentAddr SecurityViolation Security Action (Count) (Count) (Count) ---------------------------------------------------------------------------Fa5/1 11 11 0 Shutdown Fa5/5 15 5 0 Restrict Fa5/11 5 4 0 Protect ---------------------------------------------------------------------------Total Addresses in System: 21 Max Addresses limit in System: 128
This example displays output from the show port-security command for a specified interface:
Router# show port-security interface fastethernet 5/1 Port Security: Enabled Port status: SecureUp Violation mode: Shutdown Maximum MAC Addresses: 11 Total MAC Addresses: 11 Configured MAC Addresses: 3 Aging time: 20 mins Aging type: Inactivity SecureStatic address aging: Enabled Security Violation count: 0
This example displays the output from the show port-security address privileged EXEC command:
Router# show port-security address Secure Mac Address Table ------------------------------------------------------------------Vlan Mac Address Type Ports Remaining Age (mins) --------------------------------1 0001.0001.0001 SecureDynamic Fa5/1 15 (I) 1 0001.0001.0002 SecureDynamic Fa5/1 15 (I) 1 0001.0001.1111 SecureConfigured Fa5/1 16 (I) 1 0001.0001.1112 SecureConfigured Fa5/1 1 0001.0001.1113 SecureConfigured Fa5/1 1 0005.0005.0001 SecureConfigured Fa5/5 23 1 0005.0005.0002 SecureConfigured Fa5/5 23 1 0005.0005.0003 SecureConfigured Fa5/5 23 1 0011.0011.0001 SecureConfigured Fa5/11 25 (I) 1 0011.0011.0002 SecureConfigured Fa5/11 25 (I) ------------------------------------------------------------------Total Addresses in System: 10 Max Addresses limit in System: 128
Tip
47-14
OL-3999-08
C H A P T E R
48
Configuring CDP
This chapter contains information about how to configure Cisco Discovery Protocol (CDP) on the Catalyst 6500 series switches, which supplements the information in these publications:
The Cisco IOS Configuration Fundamentals Configuration Guide, Release 12.2, System Management, Configuring Cisco Discovery Protocol (CDP) at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/configuration/guide/fcf015.html
The Cisco IOS Configuration Fundamentals Command Reference, Release 12.2, System Management Commands, CDP Commands publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/configfun/command/reference/frf015.html

Understanding How CDP Works, page 48-1 Configuring CDP, page 48-2
Tip
Understanding How CDP Works

CDP is a protocol that runs over Layer 2 (the data link layer) on all Cisco routers, bridges, access servers, and switches. CDP allows network management applications to discover Cisco devices that are neighbors of already known devices, in particular, neighbors running lower-layer, transparent protocols. With CDP, network management applications can learn the device type and the SNMP agent address of neighboring devices. This feature enables applications to send SNMP queries to neighboring devices. CDP runs on all LAN and WAN media that support Subnetwork Access Protocol (SNAP). Each CDP-configured device sends periodic messages to a multicast address. Each device advertises at least one address at which it can receive SNMP messages. The advertisements also contain the time-to-live, or holdtime information, which indicates the length of time a receiving device should hold CDP information before discarding it.
48-1
Chapter 48 Configuring CDP
Configuring CDP
Configuring CDP
These sections describe how to configure CDP:

Enabling CDP Globally, page 48-2 Displaying the CDP Global Configuration, page 48-2 Enabling CDP on a Port, page 48-3 Displaying the CDP Interface Configuration, page 48-3 Monitoring and Maintaining CDP, page 48-3
Enabling CDP Globally

To enable CDP globally, perform this task: Command
Router(config)# cdp run Router(config)# no cdp run
Purpose Enables CDP globally. Disables CDP globally.
This example shows how to enable CDP globally:

Router(config)# cdp run
Displaying the CDP Global Configuration

To display the CDP configuration, perform this task: Command
Router# show cdp
Purpose Displays global CDP information. This example shows how to display the CDP configuration:
Router# show cdp Global CDP information: Sending CDP packets every 120 seconds Sending a holdtime value of 180 seconds Sending CDPv2 advertisements is enabled Router#
For additional CDP show commands, see the Monitoring and Maintaining CDP section on page 48-3.
48-2
OL-3999-08
Chapter 48
Configuring CDP Configuring CDP
Enabling CDP on a Port

To enable CDP on a port, perform this task: Command
Step 1 Step 2
Router(config)# interface {{type {port-channel number}} Router(config-if)# cdp enable Router(config-if)# no cdp enable 1.
1
Purpose
slot/port} |
Selects the port to configure. Enables CDP on the port. Disables CDP on the port.
This example shows how to enable CDP on Fast Ethernet port 5/1:
Router(config)# interface fastethernet 5/1 Router(config-if)# cdp enable
Displaying the CDP Interface Configuration

To display the CDP configuration for a port, perform this task: Command
Router# show cdp interface [{{type {port-channel number}}]
1
Purpose
slot/port} |
Displays information about ports where CDP is enabled.
This example shows how to display the CDP configuration of Fast Ethernet port 5/1:
Router# show cdp interface fastethernet 5/1 FastEthernet5/1 is up, line protocol is up Encapsulation ARPA Sending CDP packets every 120 seconds Holdtime is 180 seconds Router#
Monitoring and Maintaining CDP

To monitor and maintain CDP on your device, perform one or more of these tasks: Command
Router# clear cdp counters Router# clear cdp table Router# show cdp
Purpose Resets the traffic counters to zero. Clears information about neighbors from the CDP table. Displays global information such as frequency of transmissions and the holdtime for packets being transmitted. Displays information about a specific neighbor. The display can be limited to protocol or version information.
Router# show cdp entry entry_name [protocol | version]
48-3
Chapter 48 Configuring CDP
Configuring CDP
Command
Router# show cdp interface [type
1
Purpose
slot/port}]
Displays information about interfaces on which CDP is enabled. Displays information about neighbors. The display can be limited to neighbors on a specific interface and expanded to provide more detailed information. Displays CDP counters, including the number of packets sent and received and checksum errors. Displays information about the types of debugging that are enabled. Refer to the Debug Command Reference for more information about CDP debug commands.
Router# show cdp neighbors [type1 slot/port] [detail]
Router# show cdp traffic
Router# show debugging
This example shows how to clear CDP counter configuration:

Router# clear cdp counters
This example shows how to display information about the neighboring equipment:
Router# show cdp neighbors Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge S - Switch, H - Host, I - IGMP, r - Repeater Device ID JAB023807H1 JAB023807H1 JAB023807H1 JAB023807H1 JAB023807H1 JAB03130104 JAB03130104 Local Intrfce Fas 5/3 Fas 5/2 Fas 5/1 Gig 1/2 Gig 1/1 Fas 5/8 Fas 5/9 Holdtme 127 127 127 122 122 167 152 Capability T S T S T S T S T S T S T S Platform WS-C2948 WS-C2948 WS-C2948 WS-C2948 WS-C2948 WS-C4003 WS-C4003 Port ID 2/46 2/45 2/44 2/50 2/49 2/47 2/48
Tip
48-4
OL-3999-08
C H A P T E R
49
Configuring UDLD
This chapter describes how to configure the UniDirectional Link Detection (UDLD) protocol on the Catalyst 6500 series switches.
Note

Understanding How UDLD Works, page 49-1 Default UDLD Configuration, page 49-3 Configuring UDLD, page 49-3
Tip
Understanding How UDLD Works

These sections describe how UDLD works:

UDLD Overview, page 49-2 UDLD Aggressive Mode, page 49-3
49-1
Chapter 49 Understanding How UDLD Works
Configuring UDLD
UDLD Overview
The Cisco-proprietary UDLD protocol allows devices connected through fiber-optic or copper (for example, Category 5 cabling) Ethernet cables connected to LAN ports to monitor the physical configuration of the cables and detect when a unidirectional link exists. When a unidirectional link is detected, UDLD shuts down the affected LAN port and alerts the user. Unidirectional links can cause a variety of problems, including spanning tree topology loops. UDLD is a Layer 2 protocol that works with the Layer 1 protocols to determine the physical status of a link. At Layer 1, autonegotiation takes care of physical signaling and fault detection. UDLD performs tasks that autonegotiation cannot perform, such as detecting the identities of neighbors and shutting down misconnected LAN ports. When you enable both autonegotiation and UDLD, Layer 1 and Layer 2 detections work together to prevent physical and logical unidirectional connections and the malfunctioning of other protocols. Please refer to RFC 5171 for a more detailed description of the algorithm for UDLD. The UDLD algorithm requires that all the devices connected to the same LAN segment be running the protocol in order for a potential misconfiguration to be detected and for a corrective action to be taken promptly. A unidirectional link occurs whenever traffic transmitted by the local device over a link is received by the neighbor but traffic transmitted from the neighbor is not received by the local device. If one of the fiber strands in a pair is disconnected, as long as autonegotiation is active, the link does not stay up. In this case, the logical link is undetermined, and UDLD does not take any action. If both fibers are working normally at Layer 1, then UDLD at Layer 2 determines whether those fibers are connected correctly and whether traffic is flowing bidirectionally between the correct neighbors. This check cannot be performed by autonegotiation, because autonegotiation operates at Layer 1. The Catalyst 6500 series switch periodically transmits UDLD packets to neighbor devices on LAN ports with UDLD enabled. If the packets are echoed back within a specific time frame and they are lacking a specific acknowledgment (echo), the link is flagged as unidirectional and the LAN port is shut down. Devices on both ends of the link must support UDLD in order for the protocol to successfully identify and disable unidirectional links.
Note
By default, UDLD is locally disabled on copper LAN ports to avoid sending unnecessary control traffic on this type of media since it is often used for access ports. Figure 49-1 shows an example of a unidirectional link condition. Switch B successfully receives traffic from Switch A on the port. However, Switch A does not receive traffic from Switch B on the same port. UDLD detects the problem and disables the port.
Figure 49-1 Unidirectional Link
Switch A TX RX
TX
RX
18720
Switch B
49-2
OL-3999-08
Chapter 49
Configuring UDLD Default UDLD Configuration
UDLD Aggressive Mode

UDLD aggressive mode is disabled by default. Configure UDLD aggressive mode only on point-to-point links between network devices that support UDLD aggressive mode. With UDLD aggressive mode enabled, when a port on a bidirectional link that has a UDLD neighbor relationship established stops receiving UDLD packets, UDLD tries to reestablish the connection with the neighbor. After eight failed retries, the port is disabled. To prevent spanning tree loops, nonaggressive UDLD with the default interval of 15 seconds is fast enough to shut down a unidirectional link before a blocking port transitions to the forwarding state (with default spanning tree parameters). When you enable UDLD aggressive mode, you receive additional benefits in the following situations:

One side of a link has a port stuck (both Tx and Rx) One side of a link remains up while the other side of the link has gone down
In these cases, UDLD aggressive mode disables one of the ports on the link, which prevents traffic from being discarding.
Note
In UDLD normal mode, when a unidirectional error is detected, the port is not disabled. In UDLD aggressive mode, when a unidirectional error is detected, the port is disabled.
Default UDLD Configuration

Table 49-1 shows the default UDLD configuration.
Table 49-1 UDLD Default Configuration
Feature UDLD global enable state UDLD aggressive mode UDLD per-port enable state for fiber-optic media UDLD per-port enable state for twisted-pair (copper) media
Default Value Globally disabled Disabled Enabled on all Ethernet fiber-optic LAN ports Disabled on all Ethernet 10/100 and 1000BASE-TX LAN ports
Configuring UDLD
These sections describe how to configure UDLD:

Enabling UDLD Globally, page 49-4 Enabling UDLD on Individual LAN Interfaces, page 49-4 Disabling UDLD on Fiber-Optic LAN Interfaces, page 49-5 Configuring the UDLD Probe Message Interval, page 49-5 Displaying Disabled LAN Interfaces, page 49-5 Displaying UDLD Neighbor Interfaces, page 49-5
49-3
Chapter 49 Configuring UDLD
Configuring UDLD
Resetting Disabled LAN Interfaces, page 49-6
Enabling UDLD Globally

To enable UDLD globally on all fiber-optic LAN ports, perform this task: Command
Router(config)# udld {enable | aggressive}
Purpose Enables UDLD globally on fiber-optic LAN ports.

Note
This command only configures fiber-optic LAN ports. Individual LAN port configuration overrides the setting of this command.
Router(config)# no udld {enable | aggressive}
Disables UDLD globally on fiber-optic LAN ports.
Enabling UDLD on Individual LAN Interfaces

To enable UDLD on individual LAN ports, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Enables UDLD on a specific LAN port. Enter the aggressive keyword to enable aggressive mode. On a fiber-optic LAN port, this command overrides the udld enable global configuration command setting. Disables UDLD on a nonfiber-optic LAN port.
Note
Router(config-if)# udld port [aggressive]
Router(config-if)# no udld port [aggressive]
On fiber-optic LAN ports, the no udld port command reverts the LAN port configuration to the udld enable global configuration command setting.
Step 3
Router# show udld type1 slot/number 1.
49-4
OL-3999-08
Chapter 49
Configuring UDLD Configuring UDLD
Disabling UDLD on Fiber-Optic LAN Interfaces

To disable UDLD on individual fiber-optic LAN ports, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Selects the LAN port to configure. Disables UDLD on a fiber-optic LAN port. Reverts to the udld enable global configuration command setting.
Note
Router(config-if)# udld port disable Router(config-if)# no udld port disable
This command is only supported on fiber-optic LAN ports.
Step 3
Router# show udld type1 slot/number 1.
Configuring the UDLD Probe Message Interval

To configure the time between UDLD probe messages on ports that are in advertisement mode and are currently determined to be bidirectional, perform this task: Command
Step 1
Router(config)# udld message time interval
Purpose Configures the time between UDLD probe messages on ports that are in advertisement mode and are currently determined to be bidirectional; valid values are from 7 to 90 seconds. Returns to the default value (60 seconds). Verifies the configuration.
Router(config)# no udld message
Step 2
Router# show udld type 1.
slot/number
Displaying Disabled LAN Interfaces

To display the status of LAN ports in an error-disabled state, perform this task: Command
Router# show udld neighbors Port Device Name Device ID ---------------------Gi3/1 SAL0734K5R2 1 Gi4/1 SAL0734K5R2 1 Port ID ------Gi4/1 Gi3/1 Neighbor State -------------Bidirectional Bidirectional
Purpose Displays UDLD neighbors.
Displaying UDLD Neighbor Interfaces

To display UDLD-enabled neighbors, perform this task:
49-5
Chapter 49 Configuring UDLD
Configuring UDLD
Command
Router# show udld neighbors Port Device Name Device ID ---------------------Gi3/1 SAL0734K5R2 1 Gi4/1 SAL0734K5R2 1 Port ID ------Gi4/1 Gi3/1 Neighbor State -------------Bidirectional Bidirectional
Purpose Displays UDLD neighbors.
Resetting Disabled LAN Interfaces

To reset all LAN ports that have been shut down by UDLD, perform this task: Command
Router# udld reset
Purpose Resets all LAN ports that have been shut down by UDLD.
Tip
49-6
OL-3999-08
C H A P T E R
50
Configuring NetFlow
This chapter describes how to configure NetFlow statistics collection on the Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, refer to this publication: http://www.cisco.com/en/US/docs/ios/netflow/command/reference/nf_book.html
This chapter contains the following sections:

Understanding NetFlow, page 50-1 Default NetFlow Configuration, page 50-5 NetFlow Configuration Guidelines and Restrictions, page 50-5 Configuring NetFlow, page 50-6
Tip
Understanding NetFlow
These sections describe how NetFlow works:

NetFlow Overview, page 50-2 NetFlow on the MSFC, page 50-2 NetFlow on the PFC, page 50-3
50-1
Chapter 50 Understanding NetFlow
Configuring NetFlow
NetFlow Overview
The NetFlow feature collects traffic statistics about the packets that flow through the switch and stores the statistics in the NetFlow table. The NetFlow table on the MSFC captures statistics for flows routed in software and the NetFlow table on the PFC (and on each DFC) captures statistics for flows routed in hardware. Several features use the NetFlow table: features such as network address translation (NAT) use NetFlow to modify the forwarding result; other features (such as QOS microflow policing) use the statistics from the NetFlow table to apply QOS policies. The NetFlow Data Export (NDE) feature provides the ability to export the statistics to an external device (called a NetFlow collector). In PFC3A mode, NetFlow collects statistics only for routed traffic. With a PFC3B or PFC3BXL, you can configure NetFlow to collect statistics for both routed and bridged traffic. Netflow for bridged traffic requires Release 12.2(18)SXE or later. Collecting and exporting a large volume of statistics can significantly impact supervisor engine and MSFC processor usage, so NetFlow provides configuration options to control the volume of statistics. These options include the following:
NetFlow flow masks determine the granularity of the flows to be measured. Very specific flow masks generate a large number of NetFlow table entries and a large volume of statistics to export. Less specific flow masks aggregate the traffic statistics into fewer NetFlow table entries and generate a lower volume of statistics. Sampled NetFlow exports data for a subset of traffic in a flow, which can greatly reduce the volume of statistics exported. Sampled NetFlow does not reduce the volume of statistics collected. NetFlow aggregation merges the collected statistics prior to export. Aggregation reduces the volume of records exported, but does not reduce the volume of statistics collected. Note that NetFlow aggregation increases switch CPU utilization and reduces the data available at the collector. NetFlow aggregation uses NetFlow version 8.
NetFlow defines three configurable timers to identify stale flows that can be deleted from the table. NetFlow deletes the stale entries to free up table space for new entries.
NetFlow on the MSFC

The NetFlow table on the MSFC captures statistics for flows routed in software. NetFlow on the MSFC supports NetFlow aggregation. For information about the NetFlow aggregation schemes, refer to the following document: Cisco IOS NetFlow Configuration Guide. For information about configuring NetFlow aggregation on the MSFC, refer to the following document: Cisco IOS NetFlow Configuration Guide. NetFlow on the MSFC supports ToS-based router aggregation, described in this document: Cisco IOS NetFlow Configuration Guide. Release 12.2(18)SXF and later releases support NetFlow for multicast IP. For additional information about NetFlow for multicast IP, refer to the NetFlow Multicast Support document, available in this document: Cisco IOS NetFlow Configuration Guide.
50-2
OL-3999-08
Chapter 50
Configuring NetFlow Understanding NetFlow
The NetFlow Multicast Support document contains a prerequisite specifying that you need to configure multicast fast switching or multicast distributed fast switching (MDFS). However, this prerequisite does not apply when configuring NetFlow multicast support with Release 12.2(18)SXF and later releases.
NetFlow on the PFC

The NetFlow table on the PFC captures statistics for flows routed in hardware. The PFC supports sampled NetFlow and NetFlow aggregation. The PFC does not support NetFlow ToS-based router aggregation. These sections describe NetFlow on the PFC in more detail:

Flow Masks, page 50-3 Flow Mask Conflicts, page 50-4
Flow Masks
A flow is a unidirectional stream of packets between a given source and a given destination. A flow mask specifies the fields in the incoming packet that NetFlow uses to identify the flow. NetFlow gathers statistics for each flow defined by the flow mask. The PFC supports the following flow masks:

source-onlyA less-specific flow mask. The PFC maintains one entry for each source IP address. Statistics for all flows from a given source IP address aggregate into this entry. destinationA less-specific flow mask. The PFC maintains one entry for each destination IP address. Statistics for all flows to a given destination IP address aggregate into this entry. destination-sourceA more-specific flow mask. The PFC maintains one entry for each source and destination IP address pair. Statistics for all flows between the same source IP address and destination IP address aggregate into this entry. destination-source-interfaceA more-specific flow mask. Adds the source VLAN SNMP ifIndex to the information in the destination-source flow mask. fullA more-specific flow mask. The PFC creates and maintains a separate table entry for each IP flow. A full entry includes the source IP address, destination IP address, protocol, and protocol ports. full-interfaceThe most-specific flow mask. Adds the source VLAN SNMP ifIndex to the information in the full-flow mask.
The flow mask determines the granularity of the statistics gathered, which controls the size of the NetFlow table. The less-specific flow masks result in fewer entries in the NetFlow table and the most-specific flow masks result in the most NetFlow entries. For example, if the flow mask is set to source-only, the NetFlow table contains only one entry per source IP address. The statistics for all flows from a given source are accumulated in the one entry. However, if the flow mask is configured as full, the NetFlow table contains one entry per full flow. Many entries may exist per source IP address, so the NetFlow table can become very large. See the NetFlow Configuration Guidelines and Restrictions section on page 50-5 for information about NetFlow table capacity.
50-3
Chapter 50 Understanding NetFlow
Configuring NetFlow
Flow Mask Conflicts

Several features use the NetFlow table. Table 50-1 lists the flow mask requirements for each feature.
Table 50-1 Feature Requirements for Flow Masks
Feature Reflexive ACL TCP Intercept Context Based Access Control (CBAC) Web Cache Redirect (WCCP) Server Load Balancing (SLB) Network Address Translation (NAT) NetFlow Data Export (NDE) Sampled NetFlow NetFlow Aggregation Microflow Policing
X X
X X X X X X X X X X X X X X X X X X X X X X X
Because of the variety of feature requirements, potential flow mask conflicts can occur. Note the following flow mask constraints:

With a PFC2, all features share the same global flow mask. With a PFC3, all features must share the same limited set of flow masks. The PFC can apply only one flow mask to each packet lookup.
The Feature Manager software in the MSFC is responsible for resolving feature conflicts. The Feature Managers main strategy is to select a common flow mask that satisfies all the configured NetFlow features. However, the Feature Manager may not find a common flow mask for the configured features, because some features have very specific requirements for the flow mask. To resolve the feature conflict, Feature Manager software may direct one of the features to be processed in software on the MSFC. In the extreme case, Feature Manager software gives priority to the feature that is configured first and rejects configuration requests for subsequent features. When you attempt to configure a subsequent feature that the Feature Manager cannot accommodate, you receive a failure message at the CLI. Follow these guidelines to avoid problems with feature conflicts:

Configure your highest priority features first. If an unresolvable conflict occurs, your lower priority features may be blocked. If possible, configure features only on the interfaces where the feature is required. Pay attention to response messages. If the Feature Manager turns off hardware assist for a feature, you need to ensure that feature processing does not overload the RP processor.
50-4
Non-interface Full Flow

OL-3999-08
Destination Source Interface
Destination Source
Destination
Interface Full Flow
Full Flow
Source
Chapter 50
Configuring NetFlow Default NetFlow Configuration
Note the following specific feature conflicts:

CBAC requires the full flow mask, and is given priority over other flow-based features. If a flow mask conflict occurs, the other flow-based features are processed in the MSFC. In general, NDE is flexible because you configure the minimum flow mask. If you have configured other flow-based features, Feature Manager software may set a more specific flow mask to meet all the feature requirements. Sampled NetFlow requires the dest-source-interface flow mask (PFC2) or full-interface flow mask (PFC2 and PFC3). This may cause conflict with other flow-based features on the same interface. NDE conflicts with QoS. NDE and QoS microflow policing cannot be configured on the same interface. If NAT is configured on a Layer 3 interface with any feature that uses dynamic ACEs (for example, Web Proxy Authentication or NAC Layer 3 IP validation), trailing fragments may not be NAT translated correctly if NAT is configured for overload. For systems equipped with a PFC3B or PFC3BXL, you can use the mls ip nat netflow-frag-l4-zero command to ensure that NAT functions correctly in this case.
Default NetFlow Configuration

Table 50-2 shows the default NetFlow configuration.
Table 50-2 Default NetFlow Configuration
Feature NetFlow of routed IP traffic NetFlow of ingress bridged IP traffic Sampled NetFlow NetFlow Aggregation
Default Value Enabled Disabled Disabled Disabled
NetFlow Configuration Guidelines and Restrictions

When configuring NetFlow, follow these guidelines and restrictions:

The CEF table (and not the NetFlow table) implements Layer 3 switching in hardware. In PFC3B or PFC3BXL mode with Release 12.2(18)SXE and later releases, NetFlow supports bridged IP traffic. PFC3A mode does not support NetFlow bridged IP traffic. In Release 12.2(18)SXF and later releases, NetFlow supports multicast IP traffic. No statistics are available for flows that are switched when the NetFlow table is full. If the NetFlow table utilization exceeds the recommended utilization levels, there is an increased probability that there will be insufficient room to store statistics. Table 50-3 lists the recommended maximum utilization levels.
50-5
Chapter 50 Configuring NetFlow
Configuring NetFlow
Table 50-3 NetFlow table utilization
PFC PFC3BXL PFC3B PFC3A PFC2
Recommended NetFlow Table Utilization 235,520 (230 K) entries 117,760 (115 K) entries 65,536 (64 K) entries 32,768 (32 K) entries
Total NetFlow Table Capacity 262,144 (256 K) entries 131,072 (128 K) entries 131,072 (128 K) entries 131,072 (128 K) entries
Configuring NetFlow
These sections describe how to configure NetFlow:

Configuring NetFlow on the PFC, page 50-6 Configuring NetFlow on the MSFC, page 50-10
Note
When you configure NAT on an interface, the PFC sends all fragmented packets to the MSFC to be processed in software. (CSCdz51590)
Configuring NetFlow on the PFC

These sections describe how to configure NetFlow statistics collection on the PFC:

NetFlow PFC Commands Summary, page 50-6 Enabling NetFlow on the PFC, page 50-7 Setting the Minimum IP MLS Flow Mask, page 50-7 Configuring the MLS Aging Time, page 50-8 Configuring NetFlow Aggregation on the PFC, page 50-9 Enabling NetFlow for Ingress-Bridged IP Traffic, page 50-10 Enabling NetFlow for Multicast IP Traffic, page 50-10 Displaying PFC Netflow Information, page 50-10
NetFlow PFC Commands Summary

Table 50-4 shows a summary of the NetFlow commands available on the PFC.
Table 50-4 Summary of PFC NetFlow commands
Command mls netflow mls flow ip mls aging
Purpose Enables NetFlow on the PFC. Sets the minimum flow mask. Sets the configurable aging parameters.
50-6
OL-3999-08
Chapter 50
Configuring NetFlow Configuring NetFlow
Table 50-4 Summary of PFC NetFlow commands
Command show mls netflow {...} show mls netflow aggregation flowmask
Purpose Displays NetFlow PFC information for unicast and multicast traffic. Displays the NetFlow aggregation flow mask.
Note
When you configure NetFlow aggregation on the MSFC, it is enabled automatically on the PFC. When you configure NetFlow for Layer 2 traffic on the MSFC, it is enabled automatically on the PFC. When you configure multicast NetFlow on the MSFC, it is enabled automatically on the PFC. Multicast NetFLow is supported in Release 12.2(18)SXF and later releases.
Enabling NetFlow on the PFC

To enable NetFlow statistics collection on the PFC, perform this task: Command
Router(config)# mls netflow Router(config)# no mls netflow
Purpose Enables NetFlow on the PFC. Disables NetFlow on the PFC.
This example shows how to disable NetFlow statistics collection on the PFC (the default setting is enabled):
Router(config)# no mls netflow
Setting the Minimum IP MLS Flow Mask

You can set the minimum specificity of the flow mask for the NetFlow table on the PFC. The actual flow mask may be more specific than the level configured in the mls flow ip command, if other configured features need a more specific flow mask (see the Flow Mask Conflicts section on page 50-4). To set the minimum IP MLS flow mask, perform this task: Command
Router(config)# mls flow ip {source | destination | destination-source | interface-destination-source | full | interface-full} Router(config)# no mls flow ip
Purpose Sets the minimum IP MLS flow mask for the protocol.
Reverts to the default IP MLS flow mask (null).
This example shows how to set the minimum IP MLS flow mask:
Router(config)# mls flow ip destination
50-7
Configuring NetFlow
To display the IP MLS flow mask configuration, perform this task: Command
Router# show mls netflow flowmask
Purpose Displays the flow mask configuration.
This example shows how to display the MLS flow mask configuration:
Router# show mls netflow flowmask current ip flowmask for unicast: destination address Router#
Configuring the MLS Aging Time

The MLS aging time (default 300 seconds) applies to all NetFlow table entries. You can configure the normal aging time in the range of 32 to 4092 seconds. Flows can age as much as 4 seconds sooner or later than the configured interval. On average, flows age within 2 seconds of the configured value. Other events might cause MLS entries to be purged, such as routing changes or a change in link state.
Note
If the number of MLS entries exceeds the recommended utilization (see the NetFlow Configuration Guidelines and Restrictions section on page 50-5), only adjacency statistics might be available for some flows. To keep the NetFlow table size below the recommended utilization, enable the following parameters when using the mls aging command:

normalConfigures an inactivity timer. If no packets are received on a flow within the duration of the timer, the flow entry is deleted from the table. fast agingConfigures an efficient process to age out entries created for flows that only switch a few packets, and then are never used again. The fast aging parameter uses the time keyword value to check if at least the threshold keyword value of packets have been switched for each flow. If a flow has not switched the threshold number of packets during the time interval, then the entry is aged out. longConfigures entries for deletion that have been active for the specified value even if the entry is still in use. Long aging is used to prevent counter wraparound, which can cause inaccurate statistics.
A typical table entry that is removed by fast aging is the entry for flows to and from a Domain Name Server (DNS) or TFTP server. If you need to enable MLS fast aging time, initially set the value to 128 seconds. If the size of the NetFlow table continues to grow over the recommended utilization, decrease the setting until the table size stays below the recommended utilization. If the table continues to grow over the recommended utilization, decrease the normal MLS aging time. To configure the MLS aging time, perform this task: Command
Router(config)# mls aging {fast [threshold {1-128} | time {1-128}] | long 64-1920 | normal 32-4092}
Purpose Configures the MLS aging time for a NetFlow table entry.
50-8
OL-3999-08
Chapter 50
Command
Router(config)# no mls aging fast Router(config)# no mls aging {long | normal}
Purpose Disables fast aging. Reverts to the default MLS aging time.
This example displays how to configure the MLS aging time:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mls aging fast threshold 64 time 30
To display the MLS aging-time configuration, perform this task: Command

Router# show mls netflow aging
Purpose Displays the MLS aging-time configuration.
This example shows how to display the MLS aging-time configuration:

Router# show mls netflow aging enable timeout packet threshold ------ ------- ---------------normal aging true 300 N/A fast aging true 32 100 long aging true 900 N/A
Configuring NetFlow Aggregation on the PFC

NetFlow Aggregation is configured automatically on the PFC and DFCs when you configure NetFlow Aggregation on the MSFC (see the Configuring NetFlow Aggregation on the MSFC section on page 50-11). To display NetFlow Aggregation information for the PFC or DFCs, perform this task: Command
Router # show ip cache flow aggregation {as | destination-prefix | prefix | protocol-port | source-prefix) module slot_num Router # show mls netflow aggregation flowmask
Purpose Displays the NetFlow Aggregation cache information and flows. Displays the NetFlow Aggregation flow mask information.
Note
The PFC and DFCs do not support NetFlow ToS-based router Aggregation. This example shows how to display the NetFlow Aggregation cache information:
Router# show ip cache flow aggregation destination-prefix module 1 IPFLOW_DST_PREFIX_AGGREGATION records and statistics for module :1 IP Flow Switching Cache, 278544 bytes 2 active, 4094 inactive, 6 added 236 ager polls, 0 flow alloc failures Active flows timeout in 30 minutes Inactive flows timeout in 15 seconds Dst If Dst Prefix Msk AS Flows Pkts B/Pk Active
50-9
Configuring NetFlow
Gi7/9 9.1.0.0 /16 0 3003 12M 64 1699.8 Gi7/10 11.1.0.0 /16 0 3000 9873K 64 1699.8 Router#
This example shows how to display the NetFlow Aggregation flow mask information:
Router# show mls netflow aggregation flowmask Current flowmask set for netflow aggregation : Vlan Full Flow Netflow aggregations configured/enabled : AS Aggregation PROTOCOL-PORT Aggregation SOURCE-PREFIX Aggregation DESTINATION-PREFIX Aggregation Router#
Enabling NetFlow for Ingress-Bridged IP Traffic

NetFlow for ingress-bridged IP traffic on the PFC is enabled when you configure NetFlow for ingress-bridged IP traffic on the MSFC. See the Enabling NetFlow for Ingress-Bridged IP Traffic section on page 50-12.
Enabling NetFlow for Multicast IP Traffic

NetFlow for multicast IP traffic on the PFC is enabled when you configure NetFlow for multicast IP traffic on the MSFC. NetFlow for multicast IP traffic is supported in Release 12.2(18)SXF and later releases. For additional information, see the Enabling NetFlow for Multicast IP Traffic section on page 50-13.
Displaying PFC Netflow Information

To display information about NetFlow on the PFC, use the following command: Command
Router(config)# show mls netflow {aggregation | aging | creation | flowmask | ip | ipv6 | mpls | table-contention | usage}
Purpose Displays information about NetFlow on the PFC.
Configuring NetFlow on the MSFC

These sections describe how to configure NetFlow on the MSFC:

Summary of NetFlow Commands on the MSFC, page 50-11 Enabling NetFlow on the MSFC, page 50-11 Configuring NetFlow Aggregation on the MSFC, page 50-11 Enabling NetFlow for Ingress-Bridged IP Traffic, page 50-12 Enabling NetFlow for Multicast IP Traffic, page 50-13
50-10
OL-3999-08
Chapter 50
Summary of NetFlow Commands on the MSFC

Table 50-5 shows the NetFlow commands available on the MSFC.
Table 50-5 Summary of MSFC NetFlow commands
Command interface x ip flow ingress ip flow-aggregation cache export version {8|9} mask source minimum x ip flow ingress layer2-switched vlan x interface x ip multicast netflow {ingress|egress} show ip cache flow aggregation show ip cache verbose flow
Purpose Enables NetFlow on the MSFC and the PFC for the specified interface. Configure NetFlow aggregation. Note that configuring aggregation on the MSFC also enables aggregation for the PFC. Specifies aggregation data export format 8 or 9. Specifies the aggregation minimum mask. Enables NetFlow for Layer 2 switched traffic. Enables NetFlow multicast traffic on the specified interface (for MSFC and PFC). Shows the NetFlow aggregation cache information and flows. Shows the NetFlow main cache information and flows.
Enabling NetFlow on the MSFC

To enable NetFlow on the MSFC, perform this task for each Layer 3 interface from which you want NetFlow: Command
Step 1
Router(config)# interface {vlan vlan_ID} | {type slot/port} | {port-channel port_channel_number} Router(config-if)# ip flow ingress1 Router(config-if)# ip route-cache flow2
Purpose Selects a Layer 3 interface to configure.
Step 2
Enables NetFlow on the selected interface, for flows routed in hardware or software. You must also enable Netflow on the PFC to enable NetFlow for flows routed in hardware.
1. Supported in Release 12.2(18)SXD and later releases. 2. Deprecated in Release 12.2(18)SXD.
In Release 12.2(18)SXF and later releases, you need to enter the ip flow ingress command to enable NetFlow for the interface. In releases prior to Release 12.2(18)SXF, NetFlow is enabled by default.
Configuring NetFlow Aggregation on the MSFC

For information on configuring NetFlow aggregation on the MSFC, refer to the following documentation: Cisco IOS netFlow Configuration Guide.
50-11
Configuring NetFlow
For information on configuring NetFlow ToS-based router aggregation on the MSFC, refer to the following documentation: Cisco IOS netFlow Configuration Guide.
Note
When you configure NetFlow aggregation on the MSFC, it is configured automatically on the PFC and DFCs (see the Configuring NetFlow Aggregation on the PFC section on page 50-9). The PFC and DFCs do not support NetFlow ToS-based router aggregation.
Enabling NetFlow for Ingress-Bridged IP Traffic

In PFC3B or PFC3BXL mode with Release 12.2(18)SXE and later releases, NetFlow supports ingress-bridged IP traffic. PFC3A mode does not support NetFlow for bridged IP traffic.
Note
When you enable NetFlow for ingress-bridged IP traffic, the statistics are available to the Sampled NetFlow feature (see the NetFlow Sampling section on page 51-7). To enable NetFlow for bridged IP traffic on a VLAN, you must create a corresponding VLAN interface, assign it an IP address, and enter the no shutdown command to bring up the interface.
To enable NetFlow for ingress-bridged IP traffic in VLANs, perform this task: Command
Router(config)# ip flow ingress layer2-switched vlan vlan_ID[-vlan_ID] [, vlan_ID[-vlan_ID]]
Purpose Enables NetFlow for ingress-bridged IP traffic in the specified VLANs.

Note
NetFlow for ingress-bridged IP traffic in a VLAN requires that NetFlow on the PFC be enabled with the mls netflow command.
Router(config)# no ip flow ingress layer2-switched vlan vlan_ID[-vlan_ID] [, vlan_ID[-vlan_ID]]
Disables NetFlow for ingress-bridged IP traffic in the specified VLANs.
This example shows how to enable NetFlow for ingress-bridged IP traffic in VLAN 200:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip flow ingress layer2-switched vlan 200
50-12
OL-3999-08
Chapter 50
Enabling NetFlow for Multicast IP Traffic

Release 12.2(18)SXF and later releases support NetFlow for multicast IP. To enable NetFlow for multicast IP, perform this task:
:
Command
Step 1
Router(config)# interface {vlan vlan_ID} | {type slot/port} | {port-channel port_channel_number} Router(config-if)# ip flow ingress Router(config-if)# ip multicast netflow {ingress | egress}
Purpose Selects a Layer 3 interface to configure.
Step 2 Step 3
Enables NetFlow on the interface. Enables NetFlow multicast traffic on the specified interface (for MSFC and PFC).

Specify ingress to enable Netflow multicast ingress accounting Specify egress to enable Netflow multicast egress accounting
For additional information about NetFlow for multicast IP, refer to the NetFlow Multicast Support documentation, available in the following document: Cisco IOS NetFlow Configuration Guide. The NetFlow Multicast Support document contains a prerequisite specifying that you need to configure multicast fast switching or multicast distributed fast switching (MDFS). However, this prerequisite does not apply when configuring NetFlow multicast support with Release 12.2(18)SXF and later 12.2SX releases.
Tip
50-13
Configuring NetFlow
50-14
OL-3999-08
C H A P T E R
51
Configuring NDE
This chapter describes how to configure NetFlow Data Export (NDE).
Note
For complete syntax and usage information for the commands used in this chapter, refer to this publication: http://www.cisco.com/en/US/docs/ios/netflow/command/reference/nf_book.html
This chapter contains the following sections:

Understanding NDE, page 51-1 NDE Configuration Guidelines and Restrictions, page 51-10 Configuring NDE, page 51-10
Tip
Understanding NDE
These sections describe how NetFlow Data Export (NDE) works:

NDE Overview, page 51-1 NDE on the MSFC, page 51-2
NDE Overview
NetFlow collects traffic statistics by monitoring packets that flow through the switch and storing the statistics in the NetFlow table. For more information about NetFlow, see Chapter 50, Configuring NetFlow.
51-1
Chapter 51 Understanding NDE
Configuring NDE
NetFlow Data Export (NDE) converts the NetFlow table statistics into records and exports the records to an external device, which is called a NetFlow collector. In PFC3A mode, NDE exports statistics only for routed traffic. With a PFC3B or PFC3BXL, you can configure NDE to export statistics for both routed and bridged traffic. Netflow for bridged traffic requires Release 12.2(18)SXE or later. You can export IP unicast statistics using NDE record format versions 5, 7 or 9. Use NDE version 8 record format for NetFlow aggregation, and version 9 record format for IP multicast. NetFlow version 9 export format is supported in Release 12.2(18)SXF and later. Exporting a large volume of statistics can significantly impact SP and RP CPU utilization. You can control the volume of records exported by configuring NDE flow filters to include or exclude flows from the NDE export. When you configure a filter, NDE exports only the flows that match the filter criteria. You can configure up to two external data collector addresses. A second data collector improves the probability of receiving complete NetFlow data by providing redundant data streams. This feature is available with the following releases and hardware:

A PFC2 and Release 12.2(18)SXD and later releases A PFC3 and Release 12.2(18)SXE and later releases
NDE on the MSFC

NDE on the MSFC exports statistics for flows routed in software. The MSFC supports NetFlow aggregation, described in this document: Cisco IOS NetFlow Configuration Guide. The MSFC also supports NetFlow ToS-based router aggregation, described in this document: Cisco IOS NetFlow Configuration Guide. Release 12.2(18)SXF and later releases support NetFlow sampling on the MSFC, described in this document: Cisco IOS NetFlow Configuration Guide. Release 12.2(18)SXF and later releases support NetFlow version 9, described in this document: Cisco IOS NetFlow Configuration Guide. NetFlow version 9 record formats are described in this document: Cisco IOS NetFlow Configuration Guide.
NDE on the PFC

NDE on the PFC exports statistics for flows routed or bridged in hardware. These sections describe NDE on the PFC in more detail:

NDE Flow Mask, page 51-3 NDE Versions, page 51-3 Exporting NetFlow Data, page 51-7 NetFlow Sampling, page 51-7
51-2
OL-3999-08
Chapter 51
Configuring NDE Understanding NDE
NDE Flow Mask

You can configure the minimum NetFlow flow mask for NDE. The NetFlow flow mask determines the granularity of the statistics gathered, which controls the volume of statistics for NDE to export. For more details about flow masks, refer to Chapter 50, Configuring NetFlow.
Additional NDE Fields

You can configure NDE to populate the following additional fields in the NDE packets:

IP address of the next hop router Egress interface SNMP ifIndex BGP AS
These fields are populated by the software looking up the FIB table entry before sending out the NDE record to the collector. Therefore, these fields are blank when you use the show command to display the hardware NetFlow table.
NDE Versions
Release 12.2(18)SXF and later releases support NetFlow version 9. NDE exports statistics for NetFlow aggregation flows using NDE version 8. See this document for infomation about NetFlow versions 8 and 9: http://www.cisco.com/en/US/docs/ios-xml/ios/netflow/configuration/12-2sx/ios-netflow-ov.html NDE exports IP unicast traffic using NDE versions 5, 7 and 9. Some fields in the flow records might not have values, depending on the current flow mask. Unsupported fields contain a zero (0).
Note
With the WCCP Layer 2 redirect, the nexthop field and the output field might not contain accurate information for all NetFlows. Therefore, the destination interface for traffic returned from the web server has a client interface instead of the cache interface or the ANCS interface. The following tables describe the supported fields for NDE versions 5 and 7:

Table 51-1Version 5 header format Table 51-2Version 7 header format Table 51-3Version 5 flow record format Table 51-4Version 7 flow record format
NetFlow version 9 record formats are described at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/netflow/configuration/12-2sx/ios-netflow-ov.html
51-3
Configuring NDE
Table 51-1 NDE Version 5 Header Format
Bytes 01 23 47 811 1215 1619 2021 2123
Content version count SysUptime unix_secs unix_nsecs flow_sequence engine_type engine_id
Description NetFlow export format version number Number of flows exported in this packet (130) Current time in milliseconds since router booted Current seconds since 0000 UTC 1970 Residual nanoseconds since 0000 UTC 1970 Sequence counter of total flows seen Type of flow switching engine Slot number of the flow switching engine
Table 51-2 NDE Version 7 Header Format
Bytes 01 23 47 811 1215 1619 2023
Content version count SysUptime unix_secs unix_nsecs flow_sequence reserved
Description NetFlow export format version number Number of flows exported in this packet (130) Current time in milliseconds since router booted Current seconds since 0000 UTC 1970 Residual nanoseconds since 0000 UTC 1970 Sequence counter of total flows seen Unused (zero) bytes
51-4
OL-3999-08
Chapter 51
Table 51-3 NDE Version 5 Flow Record Format
Flow masks: X=Populated A=Additional field (see the Populating Additional NDE Fields section on page 51-12) Destination Source Interface Destination Source Destination Full Interface
X X A X A X X X X X4 X 0 0 X X6 X X X X 0
Source
Bytes 03 47 811
Content srcaddr dstaddr nexthop
Description Source IP address Destination IP address Next hop routers IP address1 Ingress interface SNMP ifIndex Egress interface SNMP ifIndex Packets in the flow Octets (bytes) in the flow SysUptime at the time the last packet of the flow was received (milliseconds) Layer 4 source port number or equivalent Unused (zero) byte Cumulative OR of TCP flags
5 3
X 0 0 0 0 X X
0 X A2 0 A X X X X 0 0 0 0 0 X6 0 X 0 X 0
2
X X A 0 A X X X X 0 0 0 0 0 X6 X X X X 0
X X A X A X X X X 0 0 0 0 0 X6 X X X X 0
X X A 0 A X X X X X4 X 0 0 X X6 X X X X 0
1213 input 1415 output 1619 dPkts 2023 dOctets 2427 first 2831 last 3233 srcport 3435 dstport 36 37 38 39 pad1 tcp_flags prot tos
SysUptime at start of the flow (milliseconds) X

X 0
Layer 4 destination port number or equivalent 0

0 0 0 X6 X 0 X 0 0
Layer 4 protocol (for example, 6=TCP, 17=UDP) IP type-of-service byte Autonomous system number of the source, either origin or peer Autonomous system number of the destination, either origin or peer Source address prefix mask bits Destination address prefix mask bits Pad 2
4041 src_as 4243 dst_as 4445 src_mask 4647 dst_mask 48 pad2
1. Always zero when PBR, WCCP, or SLB is configured. 2. With the destination flow mask, the Next hop routers IP address field and the Output interfaces SNMP ifIndex field might not contain information that is accurate for all flows. 3. Always zero when policy-based routing is configured. 4. In PFC3BXL or PFC3B mode, for ICMP traffic, contains the ICMP code and type values. 5. Always zero for hardware-switched flows. 6. Populated in PFC3BXL or PFC3B mode.
Full
51-5
Configuring NDE
Table 51-4 NDE Version 7 Flow Record Format
Flow masks: X=Populated A=Additional field (see the Populating Additional NDE Fields section on page 51-12) Destination Source Interface Destination Source Destination Full Interface
X X A X A X X X X X4 X X 0 X X6 X X X X 0 X
OL-3999-08
Source
Bytes 03 47 811
Content srcaddr dstaddr nexthop
Description Source IP address Destination IP address Next hop routers IP address1 Ingress interface SNMP ifIndex Egress interface SNMP ifIndex Packets in the flow Octets (bytes) in the flow SysUptime at the time the last packet of the flow was received (milliseconds) Layer 4 source port number or equivalent Flow mask in use Cumulative OR of TCP flags
5 3
X 0 0 0 0 X X
0 X A2 0 A X X X X 0 0 X 0 0 X6 0 X 0 X 0 X
2
X X A 0 A X X X X 0 0 X 0 0 X6 X X X X 0 X
X X A X A X X X X 0 0 X 0 0 X6 X X X X 0 X
X X A 0 A X X X X X4 X X 0 X X6 X X X X 0 X
1213 input 1415 output 1619 dPkts 2023 dOctets 2427 First 2831 Last 3233 srcport 3435 dstport 36 37 38 39 flags tcp_flags prot tos
SysUptime at start of the flow (milliseconds) X

X 0
Layer 4 destination port number or equivalent 0

X 0 0 X6 X 0 X 0 0 0
Layer 4 protocol (for example, 6=TCP, 17=UDP) IP type-of-service byte Autonomous system number of the source, either origin or peer Autonomous system number of the destination, either origin or peer Source address prefix mask bits Destination address prefix mask bits Pad 2 IP address of MLS router
4041 src_as 4243 dst_as 44 45 src_mask dst_mask
4647 pad2 4851 MLS RP
1. Always zero when PBR, WCCP, or SLB is configured. 2. With the destination flow mask, the Next hop routers IP address field and the Output interfaces SNMP ifIndex field might not contain information that is accurate for all flows. 3. Always zero when policy-based routing is configured. 4. In PFC3BXL or PFC3B mode, for ICMP traffic, contains the ICMP code and type values. 5. Always zero for hardware-switched flows. 6. Populated with Release 12.2(17b)SXA and later releases in PFC3BXL or PFC3B mode.
51-6
Full
Chapter 51
Exporting NetFlow Data

NetFlow maintains traffic statistics for each active flow in the NetFlow table and increments the statistics when packets within each flow are switched. Periodically, NDE exports summarized traffic statistics for all expired flows, which the external data collector receives and processes. Exported NetFlow data contains statistics for the flow entries in the NetFlow table that have expired since the last export. Flow entries in the NetFlow table expire and are flushed from the NetFlow table when one of the following conditions occurs:

The entry ages out. The entry is cleared by the user. An interface goes down. Route flaps occur.
To ensure periodic reporting of continuously active flows, entries for continuously active flows expire at the end of the interval configured with the mls aging long command (default 32 minutes). NDE packets go to the external data collector either when the number of recently expired flows reaches a predetermined maximum or after:

30 seconds for version 5 export. 10 seconds for version 9 export.
By default, all expired flows are exported unless they are filtered. If you configure a filter, NDE only exports expired and purged flows that match the filter criteria. NDE flow filters are stored in NVRAM and are not cleared when NDE is disabled. See the Configuring NDE Flow Filters section on page 51-16 for NDE filter configuration procedures.
NetFlow Sampling
NetFlow sampling is used when you want to report statistics for a subset of the traffic flowing through your network. The Netflow statistics can be exported to an external collector for further analysis. There are two types of NetFlow sampling; NetFlow traffic sampling and NetFlow flow sampling. The configuration steps for configuring MSFC-based NetFlow traffic sampling for traffic switched in the software path and PFC/DFC-based NetFlow flow sampling for traffic switched in the hardware path on a Cisco 6500 series switch use different commands because they are mutually independent features. The following sections provide additional information on the two types of NetFlow sampling supported by Cisco 6500 series switches:

NetFlow Traffic Sampling, page 51-7 NetFlow Flow Sampling, page 51-8
NetFlow Traffic Sampling

NetFlow traffic sampling provides NetFlow data for a subset of traffic forwarded by a Cisco router or switch by analyzing only one randomly selected packet out of n sequential packets (n is a user-configurable parameter) from the traffic that is processed by the router or switch. NetFlow traffic sampling is used on platforms that perform software-based NetFlow accounting, such as Cisco 7200 series routers and Cisco 6500 series MSFCs, to reduce the CPU overhead of running NetFlow by reducing the number of packets that are analyzed (sampled) by NetFlow. The reduction in the number of packets sampled by NetFlow on platforms that perform software based NetFlow accounting also reduces
51-7
Configuring NDE
the number of packets that need to be exported to an external collector. Reducing the number of packets that need to be exported to an external collector by reducing the number of packets that are analyzed is useful when the volume of exported traffic created by analyzing every packet will overwhelm the collector, or result in an over-subscription of an outbound interface. NetFlow traffic sampling and export for software-based NetFlow accounting behaves in the following manner:

The flows are populated with statistics from a subset of the traffic that is seen by the router. The flows are expired. The statistics are exported.
On Cisco 6500 series switches, NetFlow traffic sampling is supported only on the MSFC for software switched packets. For more information on configuring NetFlow traffic sampling, see the Cisco IOS NetFlow Configuration Guide.
NetFlow Flow Sampling

NetFlow flow sampling does not limit the number of packets that are analyzed by NetFlow. NetFlow flow sampling is used to select a subset of the flows processed by the router for export. Therefore, NetFlow flow sampling is not a solution to reduce oversubscribed CPUs or oversubscribed hardware NetFlow table usage. NetFlow flow sampling can help reduce CPU usage by reducing the amount of data that is exported. Using NetFlow flow sampling to reduce the number of packets that need to be exported to an external collector by reporting statistics on only a subset of the flows is useful when the volume of exported traffic created by reporting statistics for all of the flows will overwhelm the collector, or result in an over-subscription of an outbound interface. NetFlow flow sampling is available on Cisco Catalyst 6500 series switches for hardware-based NetFlow accounting on the PFCs and DFCs installed in the router. NetFlow flow sampling and export for hardware-based NetFlow accounting behaves in the following manner:

Packets arrive at the switch and flows are created/updated to reflect the traffic seen. The flows are expired. The flows are sampled to select a subset of flows for exporting. The statistics for the subset of flows that have been selected by the NetFlow flow sampler are exported.
Note
When NetFlow flow sampling is enabled, aging schemes such as fast, normal, long aging are disabled. You can configure NetFlow flow sampling to use time-based sampling or packet-based sampling. With either the full-interface or destination-source-interface flow masks, you can enable or disable NetFlow Flow Sampling on each Layer 3 interface.
Packet-based NetFlow Flow Sampling
Packet-based NetFlow flow sampling uses a sampling-rate in packets and an interval in milliseconds to select a subset (sample) of flows from the total number of flows processed by the router. The values for the sampling-rate are: 64, 128, 256, 512, 1024, 2048, 4096, 8192. The interval is a user-configurable value in the range 8000-16000 milliseconds. The default for the interval is 16000 milliseconds. The interval value replaces the aging schemes such as fast, normal, long aging for expiring flows from the cache. The command syntax for configuring packet-based NetFlow flow sampling is: mls sampling packet-based rate [interval].
51-8
OL-3999-08
Chapter 51
Packet-based NetFlow flow sampling uses one of these two methods to select flows for sampling and export:
The number of packets in the expired flow exceeds the sampling rate: If in a interval of X - where X is a value in the range of 8000-16000 (inclusive), a flow has a greater number of packets than the value configured for the sampling-rate, the flow is sampled (selected) and then exported. The number of packets in the expired flow is less than the sampling rate: If in a interval of X where X is a value in the range of 8000-16000 (inclusive), a flow has a smaller number of packets than the value configured for the sampling-rate, the packet count for the flow is added to one of eight buckets based on the number of packets in the flow. The eight bucket sizes are 1/8th increments of the sampling rate. The packet count for a flow that contains a quantity of packets that is 01/8th of the sampling rate is assigned to the first bucket. The packet count for a flow that contains a quantity of packets that is 1/8 th2/8 th of the sampling rate is assigned to the second bucket. And so on. When adding the packet count for a flow to a bucket causes the counter for the bucket to exceed the sampling rate, the last flow for which the counters were added to the bucket is sampled and exported. The bucket counter is changed to 0 and the process of increasing the bucket counter is started over. This method ensures that some flows for which the packet count never exceeds the sampling rate are selected for sampling and export.
Time-based Netflow Flow Sampling
Time-based Netflow flow sampling samples flows created in the first sampling time (in milliseconds) of the export interval time (in milliseconds). Each of the sampling rates that you can configure with the mls sampling time-based rate command has fixed values for the sampling time and export interval used by time-based NetFlow flow sampling. For example:

If you configure a sampling rate of 64, NefFlow flow sampling selects flows created within the first 64 milliseconds (sampling time) of every 4096 millisecond export interval. If you configure a sampling rate of 2048, NefFlow flow sampling selects flows created within the first 4 milliseconds (sampling time) of every 8192 millisecond export interval.
Table 51-5 lists the sampling rates and export intervals for time-based NetFlow flow sampling.
Table 51-5 Time-Based Sampling Rates, Sampling Times, and Export Intervals
Sampling Rate (Configurable) 1 in 64 1 in 128 1 in 256 1 in 512 1 in 1024 1 in 2048 1 in 4096 1 in 8192
Sampling Time in Milliseconds (Not Configurable) 64 32 16 8 4 4 4 4
Export Interval Milliseconds (Not Configurable) 4096 4096 4096 4096 4096 8192 16384 32768
51-9
Chapter 51 Default NDE Configuration
Configuring NDE
Default NDE Configuration

Table 51-4 shows the default NDE configuration.
Table 51-6 Default NDE Configuration
Feature NDE NDE of ingress bridged IP traffic NDE source addresses NDE data collector address and UDP port NDE filters Populating additional NDE fields
Default Value Disabled Disabled None None None Enabled
NDE Configuration Guidelines and Restrictions

When configuring NDE, follow these guidelines and restrictions:

NDE supports IP multicast traffic only with NetFlow version 9. NetFlow aggregation must use NDE version 8 or version 9. In PFC3B or PFC3BXL mode with Release 12.2(18)SXE and later releases, NDE supports bridged IP traffic. PFC3A mode does not support NDE for bridged IP traffic. NDE does not support Internetwork Packet Exchange (IPX) traffic or any other non-IP protocol.
Configuring NDE
These sections describe how to configure NDE:

Configuring NDE on the PFC, page 51-11 Configuring NDE on the MSFC, page 51-13 Enabling NDE for Ingress-Bridged IP Traffic, page 51-15 Displaying the NDE Address and Port Configuration, page 51-15 Configuring NDE Flow Filters, page 51-16 Displaying the NDE Configuration, page 51-18
Note
You must enable NetFlow on the MSFC Layer 3 interfaces to support NDE on the PFC and NDE on the MSFC. You must enable NDE on the MSFC to support NDE on the PFC. When you configure NAT and NDE on an interface, the PFC sends all fragmented packets to the MSFC to be processed in software. (CSCdz51590)
51-10
OL-3999-08
Chapter 51
Configuring NDE Configuring NDE
Configuring NDE on the PFC

These sections describe how to configure NDE on the PFC:

Enabling NDE From the PFC, page 51-11 Populating Additional NDE Fields, page 51-12 Configuring NetFlow Flow Sampling, page 51-12
Enabling NDE From the PFC

To enable NDE from the PFC, perform this task: Command
Router(config)# mls nde sender [version {5 | 7}]
Purpose Enables NDE from the PFC using version 7 records or version 5 records. If you enter the mls nde sender command without using the version {5 | 7 } keywords version 7 records are enabled by default.
Note
If you are using NDE for direct export with WS-X6708-10GE ports, enter the mls nde sender version 5 command.
Router(config)# ip flow-export version 9
(Optional) Enables the use of version 9 records1. If you want to enable the use of version 9 records for NDE, you must enter the mls nde sender command first.
Note
Enabling the use of version 9 records overrides the use of either version 5 records or version 7 records.
Router(config)# no ip flow-export version 9 Router(config)# no mls nde sender 1. The ip flow-export version 9 command was integrated into 12.2(18)SXF.
Disables the use of version 9 records. Disables NDE from the PFC.
Note
NDE from the PFC uses the source interface configured for the MSFC (see the Configuring the MSFC NDE Source Layer 3 Interface section on page 51-13). Release 12.2(18)SXF and later releases support NetFlow version 9, described at this URL: http://www.cisco.com/en/US/docs/ios-xml/ios/netflow/configuration/12-2sx/cfg-nflow-data-expt.h tml
This example shows how to enable NDE from the PFC:

Router(config)# mls nde sender
This example shows how to enable NDE from the PFC and configure NDE version 5:
Router(config)# mls nde sender version 5
51-11
Chapter 51 Configuring NDE
Configuring NDE
Populating Additional NDE Fields

You can configure NDE to populate the following additional fields in the NDE packets:

IP address of the next hop router Egress interface SNMP ifIndex BGP AS
Not all of the additional fields are populated with all flow masks. See the NDE Versions section on page 51-3 for additional information. To populate the additional fields in NDE packets, perform this task: Command
Router(config)# mls nde interface Router(config)# no mls nde interface
Purpose Populates additional fields in NDE packets. Disables population of the additional fields.
This example shows how to populate the additional fields in NDE packets:
Router(config)# mls nde interface
Configuring NetFlow Flow Sampling

These sections describe how to configure NetFlow flow sampling on the PFC:

Configuring NetFlow Flow Sampling Globally, page 51-12 Configuring NetFlow Flow Sampling on a Layer 3 Interface, page 51-13
Configuring NetFlow Flow Sampling Globally

To configure NetFlow flow sampling globally, perform this task: Command
Step 1
Router(config)# mls sampling {time-based rate | packet-based rate [interval]}
Purpose Enables sampled NetFlow and configures the rate. For packet-based sampling, optionally configures the export interval. Clears the sampled NetFlow configuration. Exits configuration mode.
Router(config)# no mls sampling
Step 2
Router(config)# end
When you configure NetFlow flow sampling globally, note the following information:

The valid values for rate are 64, 128, 256, 512, 1024, 2048, 4096, and 8192. The valid values for the packet-based export interval are from 8,000 through 16,000. With a PFC3, to export any data, you must also configure sampled NetFlow on a Layer 3 interface.
51-12
OL-3999-08
Chapter 51
Configuring NetFlow Flow Sampling on a Layer 3 Interface
Note
With the full-interface or destination-source-interface flow masks, you can enable or disable NetFlow flow sampling on individual Layer 3 interfaces. With all other flow masks, NetFlow flow sampling is enabled or disabled globally. The Layer 3 interface must be configured with an IP address.
To configure NetFlow flow sampling on a Layer 3 interface, perform this task: Command
Step 1 Step 2
Router(config)# interface {vlan vlan_ID | type slot/port} Router(config-if)# mls netflow sampling Router(config-if)# no mls netflow sampling
Purpose Selects a Layer 3 interface to configure. Enables NetFlow flow sampling on the Layer 3 interface. Disables NetFlow flow sampling on the Layer 3 interface. Exits configuration mode.
Step 3
Router(config)# end
This example shows how to enable NetFlow flow sampling on Fast Ethernet port 5/12:
Router# configure terminal Router(config)# interface fastethernet 5/12 Router(config-if)# mls netflow sampling Router(config)# end Router#
Configuring NDE on the MSFC

These sections describe how to configure NDE on the MSFC:

Configuring the MSFC NDE Source Layer 3 Interface, page 51-13 Configuring the NDE Destination, page 51-14 Configuring Netflow Flow Sampling, page 51-14
Configuring the MSFC NDE Source Layer 3 Interface

To configure the Layer 3 interface used as the source of the NDE packets containing statistics from the MSFC, perform this task: Command
Router(config)# ip flow-export source {{vlan vlan_ID} | {type slot/port} | {port-channel number} | {loopback number}} Router(config)# no ip flow-export source
Purpose Configures the interface used as the source of the NDE packets containing statistics from the MSFC. Clears the NDE source interface configuration.
When configuring the MSFC NDE source Layer 3 interface, note the following information:
You must select an interface configured with an IP address.
51-13
Configuring NDE
You can use a loopback interface.
This example shows how to configure a loopback interface as the NDE flow source:
Router(config)# ip flow-export source loopback 0 Router(config)#
Configuring the NDE Destination

To configure the destination IP address and UDP port to receive the NDE statistics, perform this task: Command
Router(config)# ip flow-export destination ip_address udp_port_number Router(config)# no ip flow-export destination ip_address udp_port_number
Purpose Configures the NDE destination IP address and UDP port. Clears the NDE destination configuration.
Note
NetFlow Multiple Export DestinationsTo configure redundant NDE data streams, which improves the probability of receiving complete NetFlow data, you can enter the ip flow-export destination command twice and configure a different destination IP address in each command. This hardware and these releases support the NetFlow Multiple Export Destinations feature:

PFC3 and Release 12.2(18)SXE and later releases PFC2 and Release 12.2(18)SXD and later releases
Note that configuring two destinations increases the RP CPU utilization, as you are exporting the data records twice.
This example shows how to configure the NDE flow destination IP address and UDP port:
Router(config)# ip flow-export destination 172.20.52.37 200
Note
The destination address and UDP port number are saved in NVRAM and are preserved if NDE is disabled and reenabled or if the switch is power cycled. If you are using the NetFlow FlowCollector application for data collection, verify that the UDP port number you configure is the same port number shown in the FlowCollectors /opt/csconfc/config/nfconfig.file file.
Configuring Netflow Flow Sampling

In 12.2(18)SXF and later releases, the MSFC supports NetFlow sampling for software-routed traffic. For additional information, see the following document: Cisco IOS NetFlow Configuration Guide.
51-14
OL-3999-08
Chapter 51
Enabling NDE for Ingress-Bridged IP Traffic

In PFC3B or PFC3BXL mode with Release 12.2(18)SXE and later releases, NDE supports ingress-bridged IP traffic. PFC3A mode does not support NDE for bridged IP traffic.
Note
To enable NetFlow for bridged IP traffic on a VLAN, you must create a corresponding VLAN interface, assign it an IP address, and enter the no shutdown command to bring up the interface. The exported bridged flows will have ingress and egress VLAN information and not the physical port information. NDE is enabled by default when you enable NetFlow on the VLAN. To disable NDE for ingress-bridged IP traffic in VLANs, perform this task:
Command
Router(config)# ip flow export layer2-switched vlan vlan_ID[-vlan_ID] [, vlan_ID[-vlan_ID]]
Purpose Enables NDE for ingress-bridged IP traffic in the specified VLANs (enabled by default when you enter the ip flow ingress layer2-switched vlan command).
Note
NDE for ingress-bridged IP traffic in a VLAN requires that NDE on the PFC be enabled with the mls nde sender command.
Router(config)# no ip flow export layer2-switched vlan vlan_ID[-vlan_ID] [, vlan_ID[-vlan_ID]]
Disables NDE for ingress-bridged IP traffic in the specified VLANs.
This example shows how to enable NDE for ingress bridged IP traffic in VLAN 200:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip flow export layer2-switched vlan 200
Displaying the NDE Address and Port Configuration

To display the NDE address and port configuration, perform these tasks: Command
Router# show mls nde
Purpose Displays the NDE export flow IP address and UDP port configuration. Displays the NDE export flow IP address, UDP port, and the NDE source interface configuration.
Router# show ip flow export
This example shows how to display the NDE export flow source IP address and UDP port configuration:
Router# show mls nde Netflow Data Export enabled Exporting flows to 10.34.12.245 (9999) Exporting flows from 10.6.58.7 (55425) Version: 7 Include Filter not configured Exclude Filter is: source: ip address 11.1.1.0, mask 255.255.255.0 Total Netflow Data Export Packets are:
51-15
Configuring NDE
49 packets, 0 no packets, 247 records Total Netflow Data Export Send Errors: IPWRITE_NO_FIB = 0 IPWRITE_ADJ_FAILED = 0 IPWRITE_PROCESS = 0 IPWRITE_ENQUEUE_FAILED = 0 IPWRITE_IPC_FAILED = 0 IPWRITE_OUTPUT_FAILED = 0 IPWRITE_MTU_FAILED = 0 IPWRITE_ENCAPFIX_FAILED = 0 Netflow Aggregation Enabled source-prefix aggregation export is disabled destination-prefix aggregation exporting flows to 10.34.12.245 (9999) 10.34.12.246 (9909) exported 84 packets, 94 records prefix aggregation export is disabled Router#
This example shows how to display the NDE export flow IP address, UDP port, and the NDE source interface configuration:
Router# show ip flow export Flow export is enabled Exporting flows to 172.20.52.37 (200) Exporting using source interface FastEthernet5/8 Version 1 flow records 0 flows exported in 0 udp datagrams 0 flows failed due to lack of export packet 0 export packets were sent up to process level 0 export packets were dropped due to no fib 0 export packets were dropped due to adjacency issues Router#
Configuring NDE Flow Filters

These sections describe NDE flow filters:

NDE Flow Filter Overview, page 51-16 Configuring a Port Flow Filter, page 51-17 Configuring a Host and Port Filter, page 51-17 Configuring a Host Flow Filter, page 51-17 Configuring a Protocol Flow Filter, page 51-18
NDE Flow Filter Overview

By default, all expired flows are exported until you configure a filter. After you configure a filter, only expired and purged flows matching the specified filter criteria are exported. Filter values are stored in NVRAM and are not cleared when NDE is disabled. To display the configuration of the NDE flow filters you configure, use the show mls nde command described in the Displaying the NDE Configuration section on page 51-18.
51-16
OL-3999-08
Chapter 51
Configuring a Port Flow Filter

To configure a destination or source port flow filter, perform this task: Command
Router(config)# mls nde flow {exclude | include} {dest-port number | src-port number} Router(config)# no mls nde flow {exclude | include}
Purpose Configures a port flow filter for an NDE flow. Clears the port flow filter configuration.
This example shows how to configure a port flow filter so that only expired flows to destination port 23 are exported (assuming the flow mask is set to full):
Router(config)# mls nde flow include dest-port 23 Router(config)#
Configuring a Host and Port Filter

To configure a host and TCP/UDP port flow filter, perform this task: Command
Router(config)# mls nde flow {exclude | include} {destination ip_address mask | source ip_address mask {dest-port number | src-port number}} Router(config)# no mls nde flow {exclude | include}
Purpose Configures a host and port flow filter for an NDE flow.
Clears the port flow filter configuration.
This example shows how to configure a source host and destination TCP/UDP port flow filter so that only expired flows from host 171.69.194.140 to destination port 23 are exported (assuming the flow mask is set to ip-flow):
Router(config)# mls nde flow include source 171.69.194.140 255.255.255.255 dest-port 23
Configuring a Host Flow Filter

To configure a destination or source host flow filter, perform this task: Command
Router(config)# mls nde flow {exclude | include} {destination ip_address mask | source ip_address mask | protocol {tcp {dest-port number | src-port number} | udp {dest-port number | src-port number}} Router(config)# no mls nde flow {exclude | include}
Purpose Configures a host flow filter for an NDE flow.
Clears port filter configuration.
This example shows how to configure a host flow filter to export only flows to destination host 172.20.52.37:
Router(config)# mls nde flow include destination 172.20.52.37 255.255.255.225 Router(config)#
51-17
Configuring NDE
Configuring a Protocol Flow Filter

To configure a protocol flow filter, perform this task: Command
Router(config)# mls nde flow {exclude | include} protocol {tcp {dest-port number | src-port number} | udp {dest-port number | src-port number}} Router(config)# no mls nde flow {exclude | include}
Purpose Configures a protocol flow filter for an NDE flow.
Clears port filter configuration.
This example shows how to configure a TCP protocol flow filter so that only expired flows from destination port 35 are exported:
Router(config)# mls nde flow include protocol tcp dest-port 35 Router(config)#
To display the status of the NDE flow filters, use the show mls nde command described in the Displaying the NDE Configuration section on page 51-18.
Displaying the NDE Configuration

To display the NDE configuration, perform this task: Command
Router# show mls nde
Purpose Displays the NDE configuration.
This example shows how to display the NDE configuration:

Router# show mls nde Netflow Data Export enabled Exporting flows to 10.34.12.245 (9988) 10.34.12.245 (9999) Exporting flows from 10.6.58.7 (57673) Version: 7 Include Filter not configured Exclude Filter not configured Total Netflow Data Export Packets are: 508 packets, 0 no packets, 3985 records Total Netflow Data Export Send Errors: IPWRITE_NO_FIB = 0 IPWRITE_ADJ_FAILED = 0 IPWRITE_PROCESS = 0 IPWRITE_ENQUEUE_FAILED = 0 IPWRITE_IPC_FAILED = 0 IPWRITE_OUTPUT_FAILED = 0 IPWRITE_MTU_FAILED = 0 IPWRITE_ENCAPFIX_FAILED = 0 Netflow Aggregation Enabled
Tip
51-18
OL-3999-08
Chapter 51
51-19
Configuring NDE
51-20
OL-3999-08
C H A P T E R
52
Configuring Local SPAN, RSPAN, and ERSPAN

This chapter describes how to configure local Switched Port Analyzer (SPAN), remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN) on the Catalyst 6500 series switches. With a PFC3, Release 12.2(18)SXE and later releases support ERSPAN (see the ERSPAN Guidelines and Restrictions section on page 52-12).
Note
OSM WAN ports and FlexWAN ports do not support SPAN, RSPAN or ERSPAN. PFC2 does not support ERSPAN.

Understanding How Local SPAN, RSPAN, and ERSPAN Work, page 52-1 Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions, page 52-6 Configuring Local SPAN, RSPAN, and ERSPAN, page 52-14
Tip
Understanding How Local SPAN, RSPAN, and ERSPAN Work

These sections describe how local SPAN, RSPAN, and ERSPAN work:

Local SPAN, RSPAN, and ERSPAN Overview, page 52-2 Local SPAN, RSPAN, and ERSPAN Sources, page 52-5 Local SPAN, RSPAN, and ERSPAN Destination Ports, page 52-6
52-1
Chapter 52 Understanding How Local SPAN, RSPAN, and ERSPAN Work
Local SPAN, RSPAN, and ERSPAN Overview

Local SPAN, RSPAN, and ERSPAN sessions allow you to monitor traffic on one or more ports, or one or more VLANs, and send the monitored traffic to one or more destination ports. With Release 12.2(18)SXD and later releases, you can configure per-VLAN filtering on destination trunk ports. Local SPAN, RSPAN, and ERSPAN all send traffic to a network analyzer such as a SwitchProbe device or other Remote Monitoring (RMON) probe. SPAN does not affect the switching of traffic on source ports or VLANs. SPAN sends a copy of the packets received or transmitted by the source ports and VLANs to the destination port. You must dedicate the destination port for SPAN use. These sections provide an overview of local SPAN, RSPAN, and ERSPAN:

Local SPAN Overview, page 52-2 RSPAN Overview, page 52-3 ERSPAN Overview, page 52-4 Monitored Traffic, page 52-4
Local SPAN Overview

A local SPAN session is an association of source ports and source VLANs with one or more destination ports. You configure a local SPAN session on a single switch. Local SPAN does not have separate source and destination sessions. Local SPAN sessions do not copy locally sourced RSPAN VLAN traffic from source trunk ports that carry RSPAN VLANs. Local SPAN sessions do not copy locally sourced RSPAN GRE-encapsulated traffic from source ports. Each local SPAN session can have either ports or VLANs as sources, but not both. Local SPAN copies traffic from one or more source ports in any VLAN or from one or more VLANs to a destination port for analysis (see Figure 52-1). For example, as shown in Figure 52-1, all traffic on Ethernet port 5 (the source port) is copied to Ethernet port 10. A network analyzer on Ethernet port 10 receives all traffic from Ethernet port 5 without being physically attached to Ethernet port 5.
Figure 52-1 Example SPAN Configuration
Port 5 traffic mirrored 1 2 3 4 5 6 7 8 9 10 11 12 on port 10
E5 E4 E2 E1 E3
E6 E7
E8 E9
E11 E12 E10
Network analyzer
52-2
S6884
OL-3999-08
Chapter 52
Configuring Local SPAN, RSPAN, and ERSPAN Understanding How Local SPAN, RSPAN, and ERSPAN Work
RSPAN Overview
RSPAN supports source ports, source VLANs, and destination ports on different switches, which provides remote monitoring of multiple switches across your network (see Figure 52-2). RSPAN consists of an RSPAN source session, an RSPAN VLAN, and an RSPAN destination session. You separately configure RSPAN source sessions and destination sessions on different switches. To configure an RSPAN source session on one switch, you associate a set of source ports or VLANs with an RSPAN VLAN. To configure an RSPAN destination session on another switch, you associate the destination ports with the RSPAN VLAN. The traffic for each RSPAN session is carried as Layer 2 nonroutable traffic over a user-specified RSPAN VLAN that is dedicated for that RSPAN session in all participating switches. All participating switches must be trunk-connected at Layer 2. RSPAN source sessions do not copy locally sourced RSPAN VLAN traffic from source trunk ports that carry RSPAN VLANs. RSPAN source sessions do not copy locally sourced RSPAN GRE-encapsulated traffic from source ports. Each RSPAN source session can have either ports or VLANs as sources, but not both. The RSPAN source session copies traffic from the source ports or source VLANs and switches the traffic over the RSPAN VLAN to the RSPAN destination session. The RSPAN destination session switches the traffic to the destination ports.
Figure 52-2 RSPAN Configuration
Switch D D1 Layer 2 trunk
Destination switch (data center) D2 Probe
C3 Switch C C1 Layer 2 trunk A3 Switch A A1 A2 B1 B2 B3

27389
C2 Layer 2 trunk B4 Switch B
Intermediate switch (distribution)
Source switch(es) (access)
52-3
Chapter 52 Understanding How Local SPAN, RSPAN, and ERSPAN Work
ERSPAN Overview
ERSPAN supports source ports, source VLANs, and destination ports on different switches, which provides remote monitoring of multiple switches across your network (see Figure 52-3). ERSPAN consists of an ERSPAN source session, routable ERSPAN GRE-encapsulated traffic, and an ERSPAN destination session. You separately configure ERSPAN source sessions and destination sessions on different switches. To configure an ERSPAN source session on one switch, you associate a set of source ports or VLANs with a destination IP address, ERSPAN ID number, and optionally with a VRF name. To configure an ERSPAN destination session on another switch, you associate the destination ports with the source IP address, ERSPAN ID number, and optionally with a VRF name. ERSPAN source sessions do not copy locally sourced RSPAN VLAN traffic from source trunk ports that carry RSPAN VLANs. ERSPAN source sessions do not copy locally sourced ERSPAN GRE-encapsulated traffic from source ports. Each ERSPAN source session can have either ports or VLANs as sources, but not both. The ERSPAN source session copies traffic from the source ports or source VLANs and forwards the traffic using routable GRE-encapsulated packets to the ERSPAN destination session. The ERSPAN destination session switches the traffic to the destination ports.
Figure 52-3 ERSPAN Configuration
Switch D D1 Routed GRE-encapsulated traffic Routed Network Routed GRE-encapsulated traffic A3 Switch A A1 A2
Destination switch (data center) D2 Probe
Routed GRE-encapsulated traffic B4 Switch B Source switch(es) (access)

120377
B1 B2 B3
Monitored Traffic
These sections describe the traffic that local SPAN, RSPAN, and ERSPAN can monitor:

Monitored Traffic Direction, page 52-5 Monitored Traffic, page 52-5 Duplicate Traffic, page 52-5
52-4
OL-3999-08
Chapter 52
Configuring Local SPAN, RSPAN, and ERSPAN Understanding How Local SPAN, RSPAN, and ERSPAN Work
Monitored Traffic Direction

You can configure local SPAN sessions, RSPAN source sessions, and ERSPAN source sessions to monitor ingress traffic (called ingress SPAN), or to monitor egress traffic (called egress SPAN), or to monitor traffic flowing in both directions. Ingress SPAN copies traffic received by the source ports and VLANs for analysis at the destination port. Egress SPAN copies traffic transmitted from the source ports and VLANs. When you enter the both keyword, SPAN copies the traffic received and transmitted by the source ports and VLANs to the destination port.
Monitored Traffic
By default, local SPAN and ERSPAN monitor all traffic, including multicast and bridge protocol data unit (BPDU) frames. RSPAN does not support BPDU monitoring.
Duplicate Traffic
In some configurations, SPAN sends multiple copies of the same source traffic to the destination port. For example, in a configuration with a bidirectional SPAN session (both ingress and egress) for two SPAN sources, called s1 and s2, to a SPAN destination port, called d1, if a packet enters the switch through s1 and is sent for egress from the switch to s2, ingress SPAN at s1 sends a copy of the packet to SPAN destination d1 and egress SPAN at s2 sends a copy of the packet to SPAN destination d1. If the packet was Layer 2 switched from s1 to s2, both SPAN packets would be the same. If the packet was Layer 3 switched from s1 to s2, the Layer 3 rewrite would alter the source and destination Layer 2 addresses, in which case the SPAN packets would be different.
Local SPAN, RSPAN, and ERSPAN Sources

These sections describe local SPAN, RSPAN, and ERSPAN sources:

Source Ports, page 52-5 Source VLANs, page 52-5
Source Ports
A source port is a port monitored for traffic analysis. You can configure both switched and routed ports as SPAN source ports. SPAN can monitor one or more source ports in a single SPAN session. You can configure source ports in any VLAN. Trunk ports can be configured as source ports and mixed with nontrunk source ports. SPAN does not copy the encapsulation from a source trunk port.
Source VLANs
A source VLAN is a VLAN monitored for traffic analysis. VLAN-based SPAN (VSPAN) uses a VLAN as the SPAN source. All the ports in the source VLANs become source ports.
52-5
Chapter 52 Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
Local SPAN, RSPAN, and ERSPAN Destination Ports

A destination port is a Layer 2 or Layer 3 LAN port to which local SPAN, RSPAN, or ERSPAN sends traffic for analysis. When you configure a port as a destination port, it can no longer receive any traffic. When you configure a port as a destination port, the port is dedicated for use only by the SPAN feature. A SPAN destination port does not forward any traffic except that required for the SPAN session. You can configure trunk ports as destination ports, which allows destination trunk ports to transmit encapsulated traffic. With Release 12.2(18)SXD and later releases, for local SPAN, you can configure per-VLAN filtering on destination trunk ports using allowed VLAN lists (see the Configuring Destination Trunk Port VLAN Filtering section on page 52-25).
Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions

These sections describe local SPAN, RSPAN, and ERSPAN configuration guidelines and restrictions:

General Guidelines and Restrictions, page 52-6 Feature Incompatiblities, page 52-7 Local SPAN, RSPAN, and ERSPAN Session Limits, page 52-8 Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions, page 52-10 VSPAN Guidelines and Restrictions, page 52-11 RSPAN Guidelines and Restrictions, page 52-11 ERSPAN Guidelines and Restrictions, page 52-12
Note
Release 12.2(18)SXE and later releases support ERSPAN.
General Guidelines and Restrictions

Use SPAN for troubleshooting. Except in carefully planned topologies, SPAN consumes too many switch and network resources to enable permanently. Exercise all possible care when enabling and configuring SPAN. The traffic copied by SPAN can impose a significant load on the switch and the network. To minimize the load, configure SPAN to copy only the specific traffic that you want to analyze. Select sources that carry as little unwanted traffic as possible. For example, a port as a SPAN source might carry less unwanted traffic than a VLAN.
Note
To monitor traffic that can be matched with an ACL, consider using VACL capture. Before enabling SPAN, carefully evaluate the SPAN source traffic rates, and consider the performance implications and possible oversubscription points, which include these:
SPAN destination
52-6
OL-3999-08
Chapter 52
Configuring Local SPAN, RSPAN, and ERSPAN Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
Fabric channel Rewrite/replication engine Forwarding engine (PFC/DFC)
To avoid disrupting traffic, do not oversubscribe any of these points in your SPAN topology. Some oversubscription and performance considerations are:

SPAN doubles traffic internally SPAN adds to the traffic being processed by the switch fabric SPAN doubles forwarding engine load The supervisor engine handles the entire load imposed by egress SPAN (also called transmit SPAN).
Note
Egress SPAN should only be enabled for short periods of time during active troubleshooting
The ingress modules handle the load imposed by ingress SPAN sources (also called receive SPAN) on each module. Ingress SPAN adds to rewrite/replication engine load.
Feature Incompatiblities
These feature incompatibilities exist with local SPAN, RSPAN, and ERSPAN:

Egress SPAN is not supported in egress multicast mode. (CSCsa95965) With a PFC3, EoMPLS ports cannot be SPAN sources. (CSCed51245) A port-channel interface (an EtherChannel) can be a SPAN source, but you cannot configure active member ports of an EtherChannel as SPAN source ports. Inactive member ports of an EtherChannel can be configured as SPAN sources but they are put into the suspended state and carry no traffic. With releases earlier than Release 12.2(33)SXH, a port-channel interface (an EtherChannel) cannot be a SPAN destination. You cannot configure active member ports of an EtherChannel as SPAN destination ports. Inactive member ports of an EtherChannel can be configured as SPAN destination ports but they are put into the suspended state and carry no traffic. Because SPAN destination ports drop ingress traffic, these features are incompatible with SPAN destination ports:
Private VLANs IEEE 802.1X port-based authentication Port security Spanning tree protocol (STP) and related features (PortFast, PortFast BPDU Filtering, BPDU
Guard, UplinkFast, BackboneFast, EtherChannel Guard, Root Guard, Loop Guard)

VLAN trunk protocol (VTP) Dynamic trunking protocol (DTP) IEEE 802.1Q tunneling
Note
SPAN destination ports can participate in IEEE 802.3Z Flow Control.
52-7
Note
IP multicast switching using egress packet replication is not compatible with SPAN. In some cases, egress replication can result in multicast packets not being sent to the SPAN destination port. If you are using SPAN and your switching modules are capable of egress replication, enter the mls ip multicast replication-mode ingress command to force ingress replication.
Local SPAN, RSPAN, and ERSPAN Session Limits

These sections describe the local SPAN, RSPAN, and ERSPAN session limits:

PFC3, page 52-8 PFC2, page 52-9
PFC3
These are the PFC3 local SPAN, RSPAN, and ERSPAN session limits: Local SPAN, RSPAN Source, or ERSPAN Source Sessions 2 (ingress or egress or both) RSPAN Destination Sessions 64 ERSPAN Destination Sessions 23
Total Sessions 66
These are the PFC3 local SPAN, RSPAN, and ERSPAN source and destination limits: In Each RSPAN Destination Session 1 128 1 128 64 128 64 128 1 RSPAN VLAN 1 IP address 64 64 In Each ERSPAN Destination Session
In Each Local SPAN Session Egress or both sources With releases earlier than 1 Release 12.2(18)SXE Release 12.2(18)SXE and 128 later releases Ingress sources With releases earlier than 64 Release 12.2(18)SXD Release 12.2(18)SXD and later releases RSPAN and ERSPAN destination session sources Destinations per session 128 64
In Each RSPAN Source Session
In Each ERSPAN Source Session
1 RSPAN VLAN 1 IP address
52-8
OL-3999-08
Chapter 52
PFC2
Note
PFC2 does not support RSPAN if you configure an egress SPAN source for a local SPAN session. PFC2 does not support egress SPAN sources for local SPAN if you configure RSPAN.
These are the PFC2 local SPAN and RSPAN session limits: Total Sessions 66 Local SPAN Sessions 2 (ingress or egress or both) 1 ingress 1 or 2 egress RSPAN Source Sessions 0 1 (ingress or egress or both) 0 RSPAN Destination Sessions 64 64 64
These are the PFC2 local SPAN and RSPAN source and destination limits: In Each RSPAN Source In Each Local SPAN Session Session Egress or both sources With releases earlier than Release 12.2(18)SXF2 Release 12.2(18)SXF2 and later releases Ingress sources With releases earlier than Release 12.2(18)SXD Release 12.2(18)SXD and later releases Destinations per session 64 128 64 128 1 RSPAN VLAN 1 RSPAN VLAN 64 1 (0 with a remote SPAN source session configured) 128 1 (0 with a local SPAN egress source session configured) 128 In Each RSPAN Destination Session
RSPAN destination session source 64
52-9
Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions

These guidelines and restrictions apply to local SPAN, RSPAN, and ERSPAN:
A SPAN destination port that is copying traffic from a single egress SPAN source port sends only egress traffic to the network analyzer. However, in Release 12.2(18)SXE and later releases, if you configure more than one egress SPAN source port, the traffic that is sent to the network analyzer also includes these types of ingress traffic that were received from the egress SPAN source ports:
Any unicast traffic that is flooded on the VLAN Broadcast and multicast traffic
This situation occurs because an egress SPAN source port receives these types of traffic from the VLAN but then recognizes itself as the source of the traffic and drops it instead of sending it back to the source from which it was received. Before the traffic is dropped, SPAN copies the traffic and sends it to the SPAN destination port. (CSCds22021)

Entering additional monitor session commands does not clear previously configured SPAN parameters. You must enter the no monitor session command to clear configured SPAN parameters. Connect a network analyzer to the SPAN destination ports. All the SPAN destination ports receive all of the traffic from all the SPAN sources.
Note
With Release 12.2(18)SXD and later releases, you can configure destination trunk port VLAN filtering using allowed VLAN lists (see the Configuring Destination Trunk Port VLAN Filtering section on page 52-25).
With Release 12.2(18)SXE and later releases, for local SPAN and RSPAN, you can configure Source VLAN Filtering (see the Configuring Source VLAN Filtering for Local SPAN and RSPAN section on page 52-24).
You can configure both Layer 2 LAN ports (LAN ports configured with the switchport command) and Layer 3 LAN ports (LAN ports not configured with the switchport command) as sources or destinations. You cannot mix individual source ports and source VLANs within a single session. If you specify multiple ingress source ports, the ports can belong to different VLANs. You cannot mix source VLANs and filter VLANs within a session. You can have source VLANs or filter VLANs, but not both at the same time. When enabled, local SPAN, RSPAN, and ERSPAN use any previously entered configuration. When you specify sources and do not specify a traffic direction (ingress, egress, or both), both is used by default. SPAN copies Layer 2 Ethernet frames, but SPAN does not copy source trunk port ISL or 802.1Q tags. You can configure destination ports as trunks to send locally tagged traffic to the traffic analyzer.
Note
A destination port configured as a trunk tags traffic from a Layer 3 LAN source port with the internal VLAN used by the Layer 3 LAN port.
Local SPAN sessions, RSPAN source sessions, and ERSPAN source sessions do not copy locally sourced RSPAN VLAN traffic from source trunk ports that carry RSPAN VLANs.
52-10
OL-3999-08
Chapter 52
Local SPAN sessions, RSPAN source sessions, and ERSPAN source sessions do not copy locally sourced ERSPAN GRE-encapsulated traffic from source ports. A port specified as a destination port in one SPAN session cannot be a destination port for another SPAN session. A port configured as a destination port cannot be configured as a source port. Destination ports never participate in any spanning tree instance. Local SPAN includes BPDUs in the monitored traffic, so any BPDUs seen on the destination port are from the source port. RSPAN does not support BPDU monitoring. All packets sent through the switch for transmission from a port configured as an egress source are copied to the destination port, including packets that do not exit the switch through the port because STP has put the port into the blocking state, or on a trunk port because STP has put the VLAN into the blocking state on the trunk port.
VSPAN Guidelines and Restrictions

Note
Local SPAN, RSPAN, and ERSPAN all support VSPAN. These are VSPAN guidelines and restrictions:
For VSPAN sessions with both ingress and egress configured, two packets are forwarded from the destination port if the packets get switched on the same VLAN (one as ingress traffic from the ingress port and one as egress traffic from the egress port). VSPAN only monitors traffic that leaves or enters Layer 2 ports in the VLAN.
If you configure a VLAN as an ingress source and traffic gets routed into the monitored VLAN,
the routed traffic is not monitored because it never appears as ingress traffic entering a Layer 2 port in the VLAN.
If you configure a VLAN as an egress source and traffic gets routed out of the monitored VLAN,
the routed traffic is not monitored because it never appears as egress traffic leaving a Layer 2 port in the VLAN.
RSPAN Guidelines and Restrictions

These are RSPAN guidelines and restrictions:

Supervisor Engine 2 does not support RSPAN if you configure an egress SPAN source for a local SPAN session. Supervisor Engine 2 does not support egress SPAN sources for local SPAN if you configure RSPAN. All participating switches must be trunk-connected at Layer 2. Any network device that supports RSPAN VLANs can be an RSPAN intermediate device. Networks impose no limit on the number of RSPAN VLANs that the networks carry. Intermediate network devices might impose limits on the number of RSPAN VLANs that they can support.
52-11
You must configure the RSPAN VLANs in all source, intermediate, and destination network devices. If enabled, the VLAN Trunking Protocol (VTP) can propagate configuration of VLANs numbered 1 through 1024 as RSPAN VLANs. You must manually configure VLANs numbered higher than 1024 as RSPAN VLANs on all source, intermediate, and destination network devices. If you enable VTP and VTP pruning, RSPAN traffic is pruned in the trunks to prevent the unwanted flooding of RSPAN traffic across the network. RSPAN VLANs can be used only for RSPAN traffic. Do not configure a VLAN used to carry management traffic as an RSPAN VLAN. Do not assign access ports to RSPAN VLANs. RSPAN puts access ports in an RSPAN VLAN into the suspended state. Do not configure any ports in an RSPAN VLAN except trunk ports selected to carry RSPAN traffic. MAC address learning is disabled in the RSPAN VLAN. You can use output access control lists (ACLs) on the RSPAN VLAN in the RSPAN source switch to filter the traffic sent to an RSPAN destination. RSPAN does not support BPDU monitoring. Do not configure RSPAN VLANs as sources in VSPAN sessions. You can configure any VLAN as an RSPAN VLAN as long as all participating network devices support configuration of RSPAN VLANs and you use the same RSPAN VLAN for each RSPAN session in all participating network devices.
ERSPAN Guidelines and Restrictions

These are ERSPAN guidelines and restrictions:

Release 12.2(18)SXE and later releases support ERSPAN. Release 12.2(18)SXF and later releases support ERSPAN when the switch is operating in any switching mode. (CSCec70695) Release 12.2(18)SXE and rebuilds support ERSPAN only when the switch is operating in the compact switching mode: all modules must be fabric-enabled. The following supervisor engines support ERSPAN:
Supervisor engines manufactured with PFC3B and PFC3BXL support ERSPAN. A WS-SUP720 (a Supervisor Engine 720 manufactured with a PFC3A) can only support
ERSPAN if it has hardware version 3.2 or higher. Enter the show module version | include WS-SUP720-BASE command to display the hardware version. For example:
Router# show module version | include WS-SUP720-BASE 7 2 WS-SUP720-BASE SAD075301SZ Hw :3.2
To confirm that your supervisor engine supports ERSPAN, enter the show asic-version slot
slot_number | include ASIC|HYPERION command for the supervisor engine. For example:
Router# show asic-version slot 1 | include ASIC|HYPERION Module in slot 1 has 2 type(s) of ASICs ASIC Name Count Version HYPERION 1 (6.0)
Hyperion version 2.0 and higher supports ERSPAN.
Supervisor engine 2 does not support ERSPAN.
52-12
OL-3999-08
Chapter 52
For ERSPAN packets, the protocol type field value in the GRE header is 0x88BE. The payload of a Layer 3 ERSPAN packet is a copied Layer 2 Ethernet frame, excluding any ISL or 802.1Q tags. ERSPAN adds a 50-byte header to each copied Layer 2 Ethernet frame and replaces the 4-byte cyclic redundancy check (CRC) trailer. ERSPAN supports jumbo frames that contain Layer 3 packets of up to 9,202 bytes. If the length of the copied Layer 2 Ethernet frame is greater than 9,170 (9,152-byte Layer 3 packet), ERSPAN truncates the copied Layer 2 Ethernet frame to create a 9,202-byte ERSPAN Layer 3 packet. Regardless of any configured MTU size, ERSPAN creates Layer 3 packets that can be as long as 9,202 bytes. ERSPAN traffic might be dropped by any interface in the network that enforces an MTU size smaller than 9,202 bytes. With the default MTU size (1,500 bytes), if the length of the copied Layer 2 Ethernet frame is greater than 1,468 bytes (1,450-byte Layer 3 packet), the ERSPAN traffic is dropped by any interface in the network that enforces the 1,500-byte MTU size.
Note
The mtu interface command and the system jumbomtu command (see the Configuring Jumbo Frame Support section on page 9-10) set the maximum Layer 3 packet size (default is 1,500 bytes, maximum is 9,216 bytes).

All participating switches must be connected at Layer 3 and the network path must support the size of the ERSPAN traffic. ERSPAN does not support packet fragmentation. The do not fragment bit is set in the IP header of ERSPAN packets. ERSPAN destination sessions cannot reassemble fragmented ERSPAN packets. ERSPAN traffic is subject to the traffic load conditions of the network. You can set the ERSPAN packet IP precedence or DSCP value to prioritize ERSPAN traffic for QoS. The only supported destination for ERSPAN traffic is an ERSPAN destination session on a PFC3. All ERSPAN source sessions on a switch must use the same origin IP address, configured with the origin ip address command (see the Configuring ERSPAN Source Sessions section on page 52-19). All ERSPAN destination sessions on a switch must use the same IP address on the same destination interface. You enter the destination interface IP address with the ip address command (see the Configuring ERSPAN Destination Sessions section on page 52-22). The ERSPAN source sessions destination IP address, which must be configured on an interface on the destination switch, is the source of traffic that an ERSPAN destination session sends to the destination ports. You configure the same address in both the source and destination sessions with the ip address command. The ERSPAN ID differentiates the ERSPAN traffic arriving at the same destination IP address from various different ERSPAN source sessions.
52-13
Chapter 52 Configuring Local SPAN, RSPAN, and ERSPAN

These sections describe how to configure local SPAN, RSPAN, and ERSPAN:

Configuring Destination Port Permit Lists (Optional), page 52-14 Configuring Local SPAN, page 52-15 Configuring RSPAN, page 52-16 Configuring ERSPAN, page 52-19 Configuring Source VLAN Filtering for Local SPAN and RSPAN, page 52-24 Configuring a Destination Port as an Unconditional Trunk, page 52-24 Configuring Destination Trunk Port VLAN Filtering, page 52-25 Verifying the Configuration, page 52-26 Configuration Examples, page 52-27
Configuring Destination Port Permit Lists (Optional)

To prevent accidental configuration of ports as destinations, you can create a permit list of the ports that are valid for use as destinations. With a destination port permit list configured, you can only configure the ports in the permit list as destinations. To configure a destination port permit list, perform this task: Command
Router# configure terminal Router(config)# monitor permit-list Router(config)# no monitor permit-list Router(config)# monitor permit-list destination interface type1 slot/port[-port] [, type1 slot/port - port] Router(config)# no monitor permit-list destination interface type1 slot/port[-port] [, type1 slot/port - port] Router(config)# do show monitor permit-list
Purpose Enters global configuration mode. Enables use of the destination port permit list. Disables use of the destination port permit list. Configures a destination port permit list or adds to an existing destination port permit list. Deletes from or clears an existing destination port permit list. Verifies the configuration.
Step 5
Step 6
This example shows how to configure a destination port permit list that includes Gigabit Ethernet ports 5/1 through 5/4 and 6/1:
Router# configure terminal Router(config)# monitor permit-list Router(config)# monitor permit-list destination interface gigabitethernet 5/1-4, gigabitethernet 6/1

Router(config)# do show monitor permit-list SPAN Permit-list :Admin Enabled Permit-list ports :Gi5/1-4,Gi6/1
52-14
OL-3999-08
Chapter 52
Configuring Local SPAN, RSPAN, and ERSPAN Configuring Local SPAN, RSPAN, and ERSPAN
Configuring Local SPAN

Local SPAN does not use separate source and destination sessions. To configure a local SPAN session, configure local SPAN sources and destinations with the same session number. To configure a local SPAN session, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session local_span_session_number source {{single_interface | interface_list | interface_range | mixed_interface_list | single_vlan | vlan_list | vlan_range | mixed_vlan_list} [rx | tx | both]}} Router(config)# monitor session local_span_session_number destination {single_interface | interface_list | interface_range | mixed_interface_list} Router(config)# no monitor session {session_number | all | local | range session_range[[,session_range],...]}
Purpose Enters global configuration mode. Associates the local SPAN source session number with the source ports or VLANs and selects the traffic direction to be monitored. Associates the local SPAN session number and the destination ports. Clears the monitor configuration.
Step 3
When configuring local SPAN sessions, note the following information:

local_span_session_number can range from 1 to 66. single_interface is interface type slot/port; type is ethernet, fastethernet, gigabitethernet, or tengigabitethernet. interface_list is single_interface , single_interface , single_interface ...
Note
In lists, you must enter a space before and after the comma. In ranges, you must enter a space before and after the dash.
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ... single_vlan is the ID number of a single VLAN. vlan_list is single_vlan , single_vlan , single_vlan ... vlan_range is first_vlan_ID - last_vlan_ID. mixed_vlan_list is, in any order, single_vlan , vlan_range , ... To tag the monitored traffic as it leaves a destination port, you must configure the destination port to trunk unconditionally before you configure it as a destination (see the Configuring a Destination Port as an Unconditional Trunk section on page 52-24).
52-15
When clearing monitor sessions, note the following information:

The no monitor session number command entered with no other parameters clears session session_number. session_range is first_session_number-last_session_number.
Note
In the no monitor session range command, do not enter spaces before or after the dash. If you enter multiple ranges, do not enter spaces before or after the commas.
This example shows how to configure Fast Ethernet port 5/1 as a bidirectional source for session 1:
Router(config)# monitor session 1 source interface fastethernet 5/1
This example shows how to configure Fast Ethernet port 5/48 as the destination for SPAN session 1:
Router(config)# monitor session 1 destination interface fastethernet 5/48
For additional examples, see the Configuration Examples section on page 52-27.
Configuring RSPAN
RSPAN uses a source session on one switch and a destination session on a different switch. These sections describe how to configure RSPAN sessions:

Configuring RSPAN VLANs, page 52-16 Configuring RSPAN Source Sessions, page 52-17 Configuring RSPAN Destination Sessions, page 52-18
Configuring RSPAN VLANs

To configure a VLAN as an RSPAN VLAN, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# vlan vlan_ID{[-vlan_ID]|[,vlan_ID])
Purpose Enters global configuration mode. Creates or modifies an Ethernet VLAN, a range of Ethernet VLANs, or several Ethernet VLANs specified in a comma-separated list (do not enter space characters). Configures the VLAN as an RSPAN VLAN. Clears the RSPAN VLAN configuration. Updates the VLAN database and returns to privileged EXEC mode.
Step 3
Router(config-vlan)# remote-span Router(config-vlan)# no remote-span
Step 4
Router(config-vlan)# end
52-16
OL-3999-08
Chapter 52
Configuring RSPAN Source Sessions

To configure an RSPAN source session, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session RSPAN_source_session_number source {{single_interface | interface_list | interface_range | mixed_interface_list | single_vlan | vlan_list | vlan_range | mixed_vlan_list} [rx | tx | both]}} Router(config)# monitor session RSPAN_source_session_number destination remote vlan rspan_vlan_ID Router(config)# no monitor session {session_number | all | range session_range[[,session_range],...] | remote}
Purpose Enters global configuration mode. Associates the RSPAN source session number with the source ports or VLANs, and selects the traffic direction to be monitored.
Step 3
Associates the RSPAN source session number session number with the RSPAN VLAN. Clears the monitor configuration.
Step 4
When configuring monitor sessions, note the following information:

To configure RSPAN VLANs, see the Configuring RSPAN VLANs section on page 52-16. RSPAN_source_span_session_number can range from 1 to 66. single_interface is interface type slot/port; type is ethernet, fastethernet, gigabitethernet, or tengigabitethernet. interface_list is single_interface , single_interface , single_interface ...
Note
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ... single_vlan is the ID number of a single VLAN. vlan_list is single_vlan , single_vlan , single_vlan ... vlan_range is first_vlan_ID - last_vlan_ID. mixed_vlan_list is, in any order, single_vlan , vlan_range , ... The no monitor session number command entered with no other parameters clears session session_number. session_range is first_session_number-last_session_number.

Note
52-17
This example shows how to configure Fast Ethernet port 5/2 as the source for session 2:
Router(config)# monitor session 2 source interface fastethernet 5/2
This example shows how to configure RSPAN VLAN 200 as the destination for session 2:
Router(config)# monitor session 2 destination remote vlan 200
Configuring RSPAN Destination Sessions

Note
You can configure an RSPAN destination session on the RSPAN source session switch to monitor RSPAN traffic locally. To configure an RSPAN destination session, perform this task:
Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session RSPAN_destination_session_number source remote vlan rspan_vlan_ID Router(config)# monitor session RSPAN_destination_session_number destination {single_interface | interface_list | interface_range | mixed_interface_list}} Router(config)# no monitor session {session_number | all | range session_range[[,session_range],...] | remote}
Purpose Enters global configuration mode. Associates the RSPAN destination session number with the RSPAN VLAN. Associates the RSPAN destination session number with the destination ports. Clears the monitor configuration.
Step 3
Step 4
To tag the monitored traffic, you must configure the port to trunk unconditionally before you configure it as a destination (see the Configuring a Destination Port as an Unconditional Trunk section on page 52-24). RSPAN_destination_span_session_number can range from 1 to 66. single_interface is interface type slot/port; type is ethernet, fastethernet, gigabitethernet, or tengigabitethernet. interface_list is single_interface , single_interface , single_interface ...
Note
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ...
52-18
OL-3999-08
Chapter 52

Enter the no monitor session number command with no other parameters to clear session session_number. session_range is first_session_number-last_session_number.
Note
This example shows how to configure RSPAN VLAN 200 as the source for session 3:
Router(config)# monitor session 3 source remote vlan 200
This example shows how to configure Fast Ethernet port 5/47 as the destination for session 3:
Router(config)# monitor session 3 destination interface fastethernet 5/47
Configuring ERSPAN
ERSPAN uses separate source and destination sessions. You configure the source and destination sessions on different switches. These sections describe how to configure ERSPAN sessions:

Configuring ERSPAN Source Sessions, page 52-19 Configuring ERSPAN Destination Sessions, page 52-22
Note
With a PFC3, Release 12.2(18)SXE and later releases support ERSPAN (see the ERSPAN Guidelines and Restrictions section on page 52-12).
Configuring ERSPAN Source Sessions

To configure an ERSPAN source session, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session ERSPAN_source_session_number type erspan-source
Purpose Enters global configuration mode. Configures an ERSPAN source session number and enters ERSPAN source session configuration mode for the session. Clears the monitor configuration. (Optional) Describes the ERSPAN source session. (Default) Inactivates the ERSPAN source session. Activates the ERSPAN source session.
Router(config)# no monitor session {session_number | all | range session_range[[,session_range],...]}
Step 3 Step 4
Router(config-mon-erspan-src)# description session_description Router(config-mon-erspan-src)# shutdown Router(config-mon-erspan-src)# no shutdown
52-19
Command
Step 5
Router(config-mon-erspan-src)# source {{single_interface | interface_list | interface_range | mixed_interface_list | single_vlan | vlan_list | vlan_range | mixed_vlan_list} [rx | tx | both]} Router(config-mon-erspan-src)# filter single_vlan | vlan_list | vlan_range | mixed_vlan_list Router(config-mon-erspan-src)# destination
Purpose Associates the ERSPAN source session number with the source ports or VLANs, and selects the traffic direction to be monitored. (Optional) Configures source VLAN filtering when the ERSPAN source is a trunk port. Enters ERSPAN source session destination configuration mode. Configures the ERSPAN flow destination IP address, which must also be configured on an interface on the destination switch and be entered in the ERSPAN destination session configuration (see the Configuring ERSPAN Destination Sessions section on page 52-22, Step 7). Configures the ID number used by the source and destination sessions to identify the ERSPAN traffic, which must also be entered in the ERSPAN destination session configuration (see the Configuring ERSPAN Destination Sessions section on page 52-22, Step 8). Configures the IP address used as the source of the ERSPAN traffic. (Optional) Configures the IP time-to-live (TTL) value of the packets in the ERSPAN traffic. (Optional) Configures the IP precedence value of the packets in the ERSPAN traffic. (Optional) Configures the IP DSCP value of the packets in the ERSPAN traffic. (Optional) Configures the VRF name to use instead of the global routing table. Exits configuration mode.
Router(config-mon-erspan-src-dst)# ip address ip_address
Step 9
Router(config-mon-erspan-src-dst)# erspan-id ERSPAN_flow_id
Router(config-mon-erspan-src-dst)# origin ip address ip_address [force] Router(config-mon-erspan-src-dst)# ip ttl ttl_value
Router(config-mon-erspan-src-dst)# ip prec ipp_value
Router(config-mon-erspan-src-dst)# ip dscp dscp_value Router(config-mon-erspan-src-dst)# vrf vrf_name
Router(config-mon-erspan-src-dst)# end
session_description can be up to 240 characters and cannot contain special characters or spaces.
Note
You can enter 240 characters after the description command.
ERSPAN_source_span_session_number can range from 1 to 66. single_interface is interface type slot/port; type is ethernet, fastethernet, gigabitethernet, or tengigabitethernet.
52-20
OL-3999-08
Chapter 52
interface_list is single_interface , single_interface , single_interface ...
Note
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ... single_vlan is the ID number of a single VLAN. vlan_list is single_vlan , single_vlan , single_vlan ... vlan_range is first_vlan_ID - last_vlan_ID. mixed_vlan_list is, in any order, single_vlan , vlan_range , ... ERSPAN_flow_id can range from 1 to 1023. All ERSPAN source sessions on a switch must use the same source IP address. Enter the origin ip address ip_address force command to change the origin IP address configured in all ERSPAN source sessions on the switch. ttl_value can range from 1 to 255. ipp_value can range from 0 to 7. dscp_value can range from 0 to 63. The no monitor session number command entered with no other parameters clears session session_number. session_range is first_session_number-last_session_number.

Note
This example shows how to configure session 3 to monitor bidirectional traffic from Gigabit Ethernet port 4/1:
Router(config)# monitor session 3 type erspan-source Router(config-mon-erspan-src)# source interface gigabitethernet 4/1 Router(config-mon-erspan-src)# destination Router(config-mon-erspan-src-dst)# ip address 10.1.1.1 Router(config-mon-erspan-src-dst)# origin ip address 20.1.1.1 Router(config-mon-erspan-src-dst)# erspan-id 101
52-21
Configuring ERSPAN Destination Sessions

Note
You cannot monitor ERSPAN traffic locally. To configure an ERSPAN destination session, perform this task:
Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session ERSPAN_destination_session_number type erspan-destination Router(config)# no monitor session {session_number | all | range session_range[[,session_range],...]}
Purpose Enters global configuration mode. Configures an ERSPAN destination session number and enters ERSPAN destination session configuration mode for the session. Clears the monitor configuration.
Step 3 Step 4
Router(config-mon-erspan-dst)# description session_description Router(config-mon-erspan-dst)# shutdown Router(config-mon-erspan-dst)# no shutdown
(Optional) Describes the ERSPAN destination session. (Default) Inactivates the ERSPAN destination session. Activates the ERSPAN destination session. Associates the ERSPAN destination session number with the destination ports. Enters ERSPAN destination session source configuration mode. Configures the ERSPAN flow destination IP address. This must be an address on a local interface and match the address that you entered in the Configuring ERSPAN Source Sessions section on page 52-19, Step 8. Configures the ID number used by the destination and destination sessions to identify the ERSPAN traffic. This must match the ID that you entered in the Configuring ERSPAN Source Sessions section on page 52-19, Step 9. (Optional) Configures the VRF name used instead of the global routing table. Exits configuration mode.
Step 5
Router(config-mon-erspan-dst)# destination {single_interface | interface_list | interface_range | mixed_interface_list}} Router(config-mon-erspan-dst)# source
Step 6 Step 7
Router(config-mon-erspan-dst-src)# ip address ip_address [force]
Step 8
Router(config-mon-erspan-dst-src)# erspan-id ERSPAN_flow_id
Step 9 Step 10
Router(config-mon-erspan-dst-src)# vrf vrf_name
Router(config-mon-erspan-dst-src)# end

ERSPAN_destination_span_session_number can range from 1 to 66. single_interface is interface type slot/port; type is ethernet, fastethernet, gigabitethernet, or tengigabitethernet.
52-22
OL-3999-08
Chapter 52
interface_list is single_interface , single_interface , single_interface ...
Note
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ... All ERSPAN destination sessions on a switch must use the same IP address on the same destination interface. Enter the ip address ip_address force command to change the IP address configured in all ERSPAN destination sessions on the switch.
Note
You must also change all ERSPAN source session destination IP addresses (see the Configuring ERSPAN Source Sessions section on page 52-19, Step 8).
ERSPAN_flow_id can range from 1 to 1023.

The no monitor session number command entered with no other parameters clears session session_number. session_range is first_session_number-last_session_number.
Note
This example shows how to configure an ERSPAN destination session to send ERSPAN ID 101 traffic arriving at IP address 10.1.1.1 to Gigabit Ethernet port 2/1:
Router(config)# monitor session 3 type erspan-destination Router(config-erspan-dst)# destination interface gigabitethernet 2/1 Router(config-erspan-dst)# source Router(config-erspan-dst-src)# ip address 10.1.1.1 Router(config-erspan-dst-src)# erspan-id 101
52-23
Configuring Source VLAN Filtering for Local SPAN and RSPAN

Source VLAN filtering monitors specific VLANs when the source is a trunk port.
Note
To configure source VLAN filtering for ERSPAN, see the Configuring ERSPAN section on page 52-19. To configure source VLAN filtering when the local SPAN or RSPAN source is a trunk port, perform this task:
Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session session_number filter single_vlan | vlan_list | vlan_range | mixed_vlan_list Router(config)# no monitor session session_number filter single_vlan | vlan_list | vlan_range | mixed_vlan_list
Purpose Enters global configuration mode. Configures source VLAN filtering when the local SPAN or RSPAN source is a trunk port. Clears source VLAN filtering.
When configuring source VLAN filtering, note the following information:

single_vlan is the ID number of a single VLAN. vlan_list is single_vlan , single_vlan , single_vlan ... vlan_range is first_vlan_ID - last_vlan_ID. mixed_vlan_list is, in any order, single_vlan , vlan_range , ...
This example shows how to monitor VLANs 1 through 5 and VLAN 9 when the source is a trunk port:
Router(config)# monitor session 2 filter vlan 1 - 5 , 9
Configuring a Destination Port as an Unconditional Trunk

To tag the monitored traffic as it leaves a destination port, configure the destination port as a trunk. To configure the destination port as a trunk, perform this task: Command
Router# configure terminal Router(config)# interface type1 slot/port Router(config-if)# switchport
Purpose Enters global configuration mode. Selects the LAN port to configure. Configures the LAN port for Layer 2 switching (required only if the LAN port is not already configured for Layer 2 switching). Configures the encapsulation, which configures the Layer 2 switching port as either an ISL or 802.1Q trunk. Configures the port to trunk unconditionally. Configures the trunk not to use DTP.
Router(config-if)# switchport trunk encapsulation {isl | dot1q} Router(config-if)# switchport mode trunk Router(config-if)# switchport nonegotiate 1.
52-24
OL-3999-08
Chapter 52
This example shows how to configure a port as an unconditional IEEE 802.1Q trunk:
Router(config)# interface fastethernet 5/12 Router(config-if)# switchport Router(config-if)# switchport trunk encapsulation dot1q Router(config-if)# switchport mode trunk Router(config-if)# switchport nonegotiate
Configuring Destination Trunk Port VLAN Filtering

Note
In addition to filtering VLANs on a trunk, you can also apply the allowed VLAN list to access ports. With Release 12.2(18)SXD and later releases, when a destination port is a trunk, you can use the list of VLANs allowed on the trunk to filter the traffic transmitted from the destination port. (CSCeb01318) Destination trunk port VLAN filtering removes the restriction that all destination ports receive all the traffic from all the sources. Destination trunk port VLAN filtering allows you to select, on a per-VLAN basis, the traffic that is transmitted from each destination trunk port to the network analyzer. To configure destination trunk port VLAN filtering on a destination trunk port, perform this task:
Command
Router# configure terminal Router(config)# interface type1 slot/port Router(config-if)# switchport trunk allowed vlan {add | except | none | remove} vlan [,vlan[,vlan[,...]] 1.
Purpose Enters global configuration mode. Selects the destination trunk port to configure. Configures the list of VLANs allowed on the trunk.
When configuring the list of VLANs allowed on a destination trunk port, note the following information:
The vlan parameter is either a single VLAN number from 1 through 4094, or a range of VLANs described by two VLAN numbers, the lesser one first, separated by a dash. Do not enter any spaces between comma-separated vlan parameters or in dash-specified ranges. All VLANs are allowed by default. To remove all VLANs from the allowed list, enter the switchport trunk allowed vlan none command. To add VLANs to the allowed list, enter the switchport trunk allowed vlan add command. You can modify the allowed VLAN list without removing the SPAN configuration.
This example shows the configuration of a local SPAN session that has several VLANs as sources and several trunk ports as destinations, with destination trunk port VLAN filtering that filters the SPAN traffic so that each destination trunk port transmits the traffic from one VLAN:
interface GigabitEthernet1/1 description SPAN destination interface for VLAN 10 no ip address switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 10 switchport mode trunk switchport nonegotiate
52-25
! interface GigabitEthernet1/2 description SPAN destination interface for VLAN no ip address switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 11 switchport mode trunk switchport nonegotiate ! interface GigabitEthernet1/3 description SPAN destination interface for VLAN no ip address switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 12 switchport mode trunk switchport nonegotiate ! interface GigabitEthernet1/4 description SPAN destination interface for VLAN no ip address switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 13 switchport mode trunk switchport nonegotiate ! monitor session 1 source vlan 10 - 13 monitor session 1 destination interface Gi1/1
11
12
13

To verify the configuration, enter the show monitor session command. This example shows how to verify the configuration of session 2:
Router# show monitor session 2 Session 2 -----------Type : Remote Source Session Source Ports: RX Only: Dest RSPAN VLAN: Router#
Fa3/1 901
52-26
OL-3999-08
Chapter 52
This example shows how to display the full details of session 2:

Router# show monitor session 2 detail Session 2 -----------Type : Remote Source Session Source Ports: RX Only: TX Only: Both: Source VLANs: RX Only: TX Only: Both: Source RSPAN VLAN: Destination Ports: Filter VLANs: Dest RSPAN VLAN:
Fa1/1-3 None None None None None None None None 901
Configuration Examples
This example shows the configuration of RSPAN source session 2:
Router(config)# monitor session 2 source interface fastethernet1/1 - 3 rx Router(config)# monitor session 2 destination remote vlan 901
This example shows how to clear the configuration for sessions 1 and 2:
Router(config)# no monitor session range 1-2
This example shows the configuration of an RSPAN source session with multiple sources:
Router(config)# Router(config)# Router(config)# Router(config)# Router(config)# monitor monitor monitor monitor monitor session session session session session 2 2 2 2 2 source interface fastethernet 5/15 , 7/3 rx source interface gigabitethernet 1/2 tx source interface port-channel 102 source filter vlan 2 - 3 destination remote vlan 901
This example shows how to remove sources for a session:

Router(config)# no monitor session 2 source interface fastethernet 5/15 , 7/3
This example shows how to remove options for sources for a session:
Router(config)# no monitor session 2 source interface gigabitethernet 1/2 Router(config)# no monitor session 2 source interface port-channel 102 tx
This example shows how to remove VLAN filtering for a session:

Router(config)# no monitor session 2 filter vlan 3
This example shows the configuration of RSPAN destination session 8:

Router(config)# monitor session 8 source remote vlan 901 Router(config)# monitor session 8 destination interface fastethernet 1/2 , 2/3
This example shows the configuration of ERSPAN source session 12:

monitor session 12 type erspan-source description SOURCE_SESSION_FOR_VRF_GRAY source interface Gi8/48 rx destination erspan-id 120
52-27
ip address 10.8.1.2 origin ip address 32.1.1.1 vrf gray
This example shows the configuration of ERSPAN destination session 12:

monitor session 12 type erspan-destination description DEST_SESSION_FOR_VRF_GRAY destination interface Gi4/48 source erspan-id 120 ip address 10.8.1.2 vrf gray
This example shows the configuration of ERSPAN source session 13:

monitor session 13 type erspan-source source interface Gi6/1 tx destination erspan-id 130 ip address 10.11.1.1 origin ip address 32.1.1.1
This example shows the configuration of ERSPAN destination session 13:

monitor session 13 type erspan-destination destination interface Gi6/1 source erspan-id 130 ip address 10.11.1.1
Tip
52-28
OL-3999-08
C H A P T E R
53
Configuring SNMP IfIndex Persistence

This chapter describes how to configure the SNMP ifIndex persistence feature on Catalyst 6500 series switches.
Note

Understanding SNMP IfIndex Persistence, page 53-1 Configuring SNMP IfIndex Persistence, page 53-2
Tip
Understanding SNMP IfIndex Persistence

The SNMP ifIndex persistence feature provides an interface index (ifIndex) value that is retained and used when the switch reboots. The ifIndex value is a unique identifying number associated with a physical or logical interface. There is no requirement in the relevant RFCs that the correspondence between particular ifIndex values and their interfaces be maintained when the switch reboots, but many applications (for example, device inventory, billing, and fault detection) require maintenance of this correspondence. You can poll the switch at regular intervals to correlate the interfaces to the ifIndexes, but it is not practical to poll constantly. The SNMP ifIndex persistence feature provides permanent ifIndex values, which eliminates the need to poll interfaces.
53-1
Chapter 53 Configuring SNMP IfIndex Persistence
The following definitions are based on RFC 2233, The Interfaces Group MIB using SMIv2. The following terms are values in the Interfaces MIB (IF-MIB):

ifIndex A unique number (greater than zero) that identifies each interface for SNMP identification of that interface. ifNameThe text-based name of the interface, for example, ethernet 3/1. ifDescrA description of the interface. Recommended information for this description includes the name of the manufacturer, the product name, and the version of the interface hardware and software.

These sections describe how to configure SNMP ifIndex persistence:

Enabling SNMP IfIndex Persistence Globally, page 53-2 (Optional) Enabling and Disabling SNMP IfIndex Persistence on Specific Interfaces, page 53-3 (Optional)
Note
To verify that ifIndex commands have been configured, use the more system:running-config command.
Enabling SNMP IfIndex Persistence Globally

SNMP ifIndex persistence is disabled by default. To globally enableSNMP ifIndex persistence, perform this task: Command
Router(config)# snmp-server ifindex persist
Purpose Globally enables SNMP ifIndex persistence.
In the following example, SNMP ifIndex persistence is enabled for all interfaces:
router(config)# snmp-server ifindex persist
Disabling SNMP IfIndex Persistence Globally

To globally disable SNMP ifIndex persistence after enabling it, perform this task: Command
Router(config)# no snmp-server ifindex persist
Purpose Globally disables SNMP ifIndex persistence.
In the following example, SNMP ifIndex persistence is disabled for all interfaces:
router(config)# no snmp-server ifindex persist
53-2
OL-3999-08
Chapter 53
Configuring SNMP IfIndex Persistence Configuring SNMP IfIndex Persistence
Enabling and Disabling SNMP IfIndex Persistence on Specific Interfaces

To enable SNMP ifIndex persistence only on a specific interface, perform this task: Command
Step 1
Router(config)# interface {vlan vlan_ID} | {type1 slot/port} | {port-channel port_channel_number} Router(config-if)# snmp ifindex persist
Purpose Selects an interface to configure.
Step 2
Enables SNMP ifIndex persistence on the specified interface. Disables SNMP ifIndex persistence on the specified interface. Exits interface configuration mode.
Router(config-if)# no snmp ifindex persist
Step 3
Router(config-if)# exit 1. type = any supported interface type.
Note
The [no] snmp ifindex persistence interface command cannot be used on subinterfaces. A command applied to an interface is automatically applied to all the subinterfaces associated with that interface. In the following example, SNMP ifIndex persistence is enabled for Ethernet interface 3/1 only:
router(config)# interface ethernet 3/1 router(config-if)# snmp ifindex persist router(config-if)# exit
In the following example, SNMP ifIndex persistence is disabled for Ethernet interface 3/1 only:
router(config)# interface ethernet 3/1 router(config-if)# no snmp ifindex persist router(config-if)# exit
Clearing SNMP IfIndex Persistence Configuration from a Specific Interface

To clear the interface-specific SNMP ifIndex persistence setting and configure the interface to use the global configuration setting, perform this task: Command
Step 1
Router(config)# interface type slot/port
Purpose Enters interface configuration mode for the specified interface. Note that the syntax of the interface command will vary depending on the platform you are using. Clears any interface-specific SNMP ifIndex persistence configuration for the specified interface and returns to the global configuration setting. Exits interface configuration mode.
Step 2
Router(config-if)# snmp ifindex clear
Step 3
Router(config-if)# exit
53-3
Chapter 53 Configuring SNMP IfIndex Persistence
In the following example, any previous setting for SNMP ifIndex persistence on Ethernet interface 3/1 is removed from the configuration. If SNMP ifIndex persistence is globally enabled, SNMP ifIndex persistence will be enabled for Ethernet interface 3/1. If SNMP ifIndex persistence is globally disabled, SNMP ifIndex persistence will be disabled for Ethernet interface 3/1.
router(config)# interface ethernet 3/1 router(config-if)# snmp ifindex clear router(config-if)# exit
Tip
53-4
OL-3999-08
C H A P T E R
54
Power Management and Environmental Monitoring

This chapter describes the power management and environmental monitoring features in the Catalyst 6500 series switches.
Note

Understanding How Power Management Works, page 54-1 Understanding How Environmental Monitoring Works, page 54-10
Tip
Understanding How Power Management Works

These sections describe power management in the Catalyst 6500 series switches:

Enabling or Disabling Power Redundancy, page 54-2 Powering Modules Off and On, page 54-4 Viewing System Power Status, page 54-4 Power Cycling Modules, page 54-5 Determining System Power Requirements, page 54-5 Determining System Hardware Capacity, page 54-5 Determining Sensor Temperature Threshold, page 54-9
54-1
Chapter 54 Understanding How Power Management Works
Note
In systems with redundant power supplies, both power supplies must be of the same wattage. The Catalyst 6500 series switches allow you to use both AC-input and DC-input power supplies in the same chassis. For detailed information on supported power supply configurations, refer to the Catalyst 6500 Series Switch Installation Guide. The modules have different power requirements, and some configurations require more power than a single power supply can provide. The power management feature allows you to power all installed modules with two power supplies. However, redundancy is not supported in this configuration because the total power drawn from both power supplies is at no time greater than the capability of one supply. Redundant and nonredundant power configurations are described in the following sections. To determine the power requirements for your system, see the Determining System Power Requirements section on page 54-5.
Enabling or Disabling Power Redundancy

To disable or enable redundancy (redundancy is enabled by default) from global configuration mode, enter the power redundancy-mode combined | redundant commands. You can change the configuration of the power supplies to redundant or nonredundant at any time. To disable redundancy, use the combined keyword. In a nonredundant configuration, the power available to the system is the combined power capability of both power supplies. The system powers up as many modules as the combined capacity allows. However, if one power supply fails and there is not enough power for all of the previously powered-up modules, the system powers down those modules. To enable redundancy, use the redundant keyword. In a redundant configuration, the total power drawn from both power supplies is not greater than the capability of one power supply. If one supply malfunctions, the other supply can take over the entire system load. When you install and power up two power supplies, each concurrently provides approximately half of the required power to the system. Load sharing and redundancy are enabled automatically; no software configuration is required. To view the current state of modules and the total power available for modules, enter the show power command (see the Viewing System Power Status section on page 54-4). Table 54-1 describes how the system responds to changes in the power supply configuration.
Table 54-1 Effects of Power Supply Configuration Changes
Configuration Change Redundant to nonredundant
Effect

System log and syslog messages are generated. System power is increased to the combined power capability of both power supplies. Modules marked power-deny in the show power oper state field are brought up if there is sufficient power. System log and syslog messages are generated. System power is decreased to the power capability of one supply. If there is not enough power for all previously powered-up modules, some modules are powered down and marked as power-deny in the show power oper state field.
Nonredundant to redundant (both power supplies must be of equal wattage)
54-2
OL-3999-08
Chapter 54
Power Management and Environmental Monitoring Understanding How Power Management Works
Table 54-1 Effects of Power Supply Configuration Changes (continued)
Configuration Change Equal wattage power supply is inserted with redundancy enabled
Effect

System log and syslog messages are generated. System power equals the power capability of one supply. No change in module status because the power capability is unchanged. System log and syslog messages are generated. System power is increased to the combined power capability of both power supplies. Modules marked power-deny in the show power oper state field are brought up if there is sufficient power. System log and syslog messages are generated. The system does not allow you to operate a power supply of different wattage even if the wattage is higher than the installed supply. The inserted supply shuts down. System log and syslog messages are generated. System power is increased to the combined power capability of both power supplies. Modules marked power-deny in the show power oper state field are brought up if there is sufficient power. System log and syslog messages are generated. No change in module status because the power capability is unchanged. System log and syslog messages are generated. System power is decreased to the power capability of one supply. If there is not enough power for all previously powered-up modules, some modules are powered down and marked as power-deny in the show power oper state field. System log and syslog messages are generated. The system does not allow you to have power supplies of different wattage installed in a redundant configuration. The lower wattage supply shuts down. System log and syslog messages are generated. System power equals the combined power capability of both power supplies. The system powers up as many modules as the combined capacity allows.
Equal wattage power supply is inserted with redundancy disabled
Higher or lower wattage power supply is inserted with redundancy enabled Higher or lower wattage power supply is inserted with redundancy disabled
Power supply is removed with redundancy enabled Power supply is removed with redundancy disabled
System is booted with power supplies of different wattage installed and redundancy enabled System is booted with power supplies of equal or different wattage installed and redundancy disabled
54-3
Powering Modules Off and On

To power modules off and on from the CLI, perform this task. Command
Step 1 Step 2
Router# configure terminal Router(config)# power enable module slot_number Router(config)# no power enable module slot_number
Purpose Enters global configuration mode. Powers a module on. Powers a module off.
Note
When you enter the no power enable module slot command to power down a module, the modules configuration is not saved. This example shows how to power on the module in slot 3:
Router# configure terminal Router(config)# power enable module 3
Viewing System Power Status

You can view the current power status of system components by entering the show power command as follows:
Router# show system power system power system power system power power redundancy mode = redundant total = 1153.32 Watts (27.46 Amps @ 42V) used = 397.74 Watts ( 9.47 Amps @ 42V) available = 755.58 Watts (17.99 Amps @ 42V) Power-Capacity PS-Fan Output Oper PS Type Watts A @42V Status Status State ---- ------------------ ------- ------ ------ ------ ----1 WS-CAC-2500W 1153.32 27.46 OK OK on 2 none Pwr-Requested Pwr-Allocated Admin Slot Card-Type Watts A @42V Watts A @42V State ---- ------------------ ------- ------ ------- ------ ----1 WS-X6K-SUP2-2GE 142.38 3.39 142.38 3.39 on 2 142.38 3.39 5 WS-X6248-RJ-45 112.98 2.69 112.98 2.69 on Router#
Oper State ----on on
You can view the current power status of a specific power supply by entering the show power command as follows:
Router# show power status power-supply Power-Capacity PS Type Watts A @42V ---- ------------------ ------- -----1 WS-CAC-6000W 2672.04 63.62 2 WS-CAC-9000W-E 2773.68 66.04 Router# 2 PS-Fan Status -----OK OK Output Status -----OK OK Oper State ----on on
54-4
OL-3999-08
Chapter 54
You can display power supply input fields by specifying the power supply number in the command. A new power-output field with operating mode is displayed for power supplies with more than one output mode. Enter the show env status power-supply command as follows:
Router# show env power-supply 1: power-supply 1 power-supply 1 power-supply 1 Router# show env power-supply 2: power-supply 2 power-supply 2 power-supply 2 power-supply 2 power-supply 2 power-supply 2 status power-supply 1 fan-fail: OK power-input 1: AC low power-output-fail: OK status power-supply 2 fan-fail: OK power-input 1: none<<< new power-input 2: AC low<<< new power-input 3: AC high<<< new power-output: low (mode 1)<<< high for highest mode only power-output-fail: OK
Power Cycling Modules

You can power cycle (reset) a module from global configuration mode by entering the power cycle module slot command. The module powers off for 5 seconds, and then powers on.
Determining System Power Requirements

The power supply size determines the system power requirements. When you use the 1000 W and 1300 W power supplies, you might have configuration limitations depending on the size of chassis and type of modules installed. For information about power consumption, refer to the Release Notes for Cisco IOS Release 12.2SXF and Rebuilds .
Determining System Hardware Capacity

With Release 12.2(18)SXF and later releases, you can determine the system hardware capacity by entering the show platform hardware capacity command. This command displays the current system utilization of the hardware resources and displays a list of the currently available hardware capacities, including the following:

Hardware forwarding table utilization Switch fabric utilization CPU(s) utilization Memory device (flash, DRAM, NVRAM) utilization
This example shows how to display CPU capacity and utilization information for the route processor, the switch processor, and the LAN module in the Catalyst 6500 series switch:
Router# show platform hardware capacity cpu CPU Resources CPU utilization: Module 5 seconds 1 RP 0% / 0% 1 SP 5% / 0% 7 69% / 0% 8 78% / 0% Processor memory: Module Bytes: Total
1 minute 1% 5% 69% 74% Used
5 minutes 1% 4% 69% 74% %Used
54-5
1 1 7 8 I/O memory: Module 1 RP 1 SP 7 8 Router#
RP SP
Bytes:
176730048 192825092 195111584 195111584 Total 35651584 35651584 35651584 35651584
51774704 51978936 35769704 35798632 Used 12226672 9747952 9616816 9616816
29% 27% 18% 18% %Used 34% 27% 27% 27%
This example shows how to display EOBC-related statistics for the route processor, the switch processor, and the DFCs in the Catalyst 6500 series switch:
Router# show platform hardware capacity eobc EOBC Resources Module Packets/sec Total packets 1 RP Rx: 61 108982 Tx: 37 77298 1 SP Rx: 34 101627 Tx: 39 115417 7 Rx: 5 10358 Tx: 8 18543 8 Rx: 5 12130 Tx: 10 20317 Router# Dropped packets 0 0 0 0 0 0 0 0
This example shows how to display the current and peak switching utilization:
Router# show platform hardware capacity fabric Switch Fabric Resources Bus utilization: current is 100%, peak was 100% at 12:34 12mar45 Fabric utilization: ingress egress Module channel speed current peak current peak 1 0 20G 100% 100% 12:34 12mar45 100% 100% 12:34 1 1 20G 12% 80% 12:34 12mar45 12% 80% 12:34 4 0 20G 12% 80% 12:34 12mar45 12% 80% 12:34 13 0 8G 12% 80% 12:34 12mar45 12% 80% 12:34 Router#
12mar45 12mar45 12mar45 12mar45
This example shows how to display information about the total capacity, the bytes used, and the percentage that is used for the flash and NVRAM resources present in the system:
Router# show platform hardware capacity flash Flash/NVRAM Resources Usage: Module Device Bytes: Total 1 RP bootflash: 31981568 1 SP disk0: 128577536 1 SP sup-bootflash: 31981568 1 SP const_nvram: 129004 1 SP nvram: 391160 7 dfc#7-bootflash: 15204352 8 dfc#8-bootflash: 15204352 Router#
Used 15688048 105621504 29700644 856 22065 616540 0
%Used 49% 82% 93% 1% 6% 4% 0%
This example shows how to display the capacity and utilization of the EARLs present in the system:
Router# show platform hardware capacity forwarding L2 Forwarding Resources MAC Table usage: Module Collisions Total 6 0 65536 VPN CAM usage: Total 512 L3 Forwarding Resources
Used 11 Used 0
%Used 1% %Used 0%
54-6
OL-3999-08
Chapter 54
FIB TCAM usage: 72 bits (IPv4, MPLS, EoM) 144 bits (IP mcast, IPv6) detail: Protocol IPv4 MPLS EoM IPv6 IPv4 mcast IPv6 mcast Adjacency usage:
Total 196608 32768
Used 36 7 Used 36 0 0 4 3 0
%Used 1% 1% %Used 1% 0% 0% 1% 1% 0% %Used 1%
Total 1048576
Used 175
Forwarding engine load: Module 6 Netflow Resources TCAM utilization: ICAM utilization:
pps 8
peak-pps 1972
peak-time 02:02:17 UTC Thu Apr 21 2005
Module 6 Module 6
Created 1 Created 0
Failed 0 Failed 0
%Used 0% %Used 0%
Flowmasks: Mask# IPv4: 0 IPv4: 1 IPv4: 2 IPv4: 3 IPv6: IPv6: IPv6: IPv6: CPU Rate Limiters Resources Rate limiters: Layer 3 Layer 2 0 1 2 3
Type Features reserved none Intf FulNAT_INGRESS NAT_EGRESS FM_GUARDIAN unused none reserved none reserved unused unused reserved none none none none
Total 9 4
Used 4 2
Reserved 1 2
%Used 44% 50%
ACL/QoS TCAM Resources Key: ACLent - ACL TCAM entries, ACLmsk - ACL TCAM masks, AND - ANDOR, QoSent - QoS TCAM entries, QOSmsk - QoS TCAM masks, OR - ORAND, Lbl-in - ingress label, Lbl-eg - egress label, LOUsrc - LOU source, LOUdst - LOU destination, ADJ - ACL adjacency Module ACLent ACLmsk QoSent QoSmsk Lbl-in Lbl-eg LOUsrc LOUdst 6 1% 1% 1% 1% 1% 1% 0% 0% Router# AND OR 0% 0% ADJ 1%
This example shows how to display the interface resources:

Router# show platform hardware capacity interface Interface Resources Interface drops: Module Total drops: Tx Rx Highest drop port: Tx 9 0 2 0 Interface buffer sizes: Module 1
Rx 48
Bytes:
Tx buffer 12345
Rx buffer 12345
54-7
5 Router#
12345
12345
This example shows how to display SPAN information:

Router# show platform hardware capacity monitor SPAN Resources Source sessions: 2 maximum, 0 used Type Used Local 0 RSPAN source 0 ERSPAN source 0 Service module 0 Destination sessions: 64 maximum, 0 used Type Used RSPAN destination 0 ERSPAN destination (max 24) 0 Router#
This example shows how to display the capacity and utilization of resources for Layer 3 multicast functionality:
Router# show platform hardware capacity multicast L3 Multicast Resources IPv4 replication mode: ingress IPv6 replication mode: ingress Bi-directional PIM Designated Forwarder Table usage: 4 total, 0 (0%) used Replication capability: Module IPv4 IPv6 5 egress egress 9 ingress ingress MET table Entries: Module Total Used %Used 5 65526 6 0% Router#
This example shows how to display information about the system power capacities and utilizations:
Router# show platform hardware capacity power Power Resources Power supply redundancy mode: administratively combined operationally combined System power: 1922W, 0W (0%) inline, 1289W (67%) total allocated Powered devices: 0 total Router#
This example shows how to display the capacity and utilization of QoS policer resources for each EARL in the Catalyst 6500 series switch.
Router# show platform hardware capacity qos QoS Policer Resources Aggregate policers: Module 1 5 Microflow policer configurations: Module 1 5 Router#
Total 1024 1024 Total 64 64
Used 102 1 Used 32 1
%Used 10% 1% %Used 50% 1%
This example shows how to display information about the key system resources:
Router# show platform hardware capacity systems System Resources PFC operating mode: PFC3BXL Supervisor redundancy mode: administratively rpr-plus, operationally rpr-plus Switching Resources: Module Part number Series CEF mode
54-8
OL-3999-08
Chapter 54
5 9 Router#
WS-SUP720-BASE WS-X6548-RJ-45
supervisor CEF256
CEF CEF
This example shows how to display VLAN information:

Router# show platform hardware capacity vlan VLAN Resources VLANs: 4094 total, 10 VTP, 0 extended, 0 internal, 4084 free Router#
Determining Sensor Temperature Threshold

The system sensors set off alarms based on different temperature threshold settings. You can determine the allowed temperatures for the sensors by using the show environment alarm threshold command. This example shows how to determine sensor temperature thresholds:
Router> show environment alarm threshold environmental alarm thresholds: power-supply 1 fan-fail: OK threshold #1 for power-supply 1 fan-fail: (sensor value != 0) is system minor alarm power-supply 1 power-output-fail: OK threshold #1 for power-supply 1 power-output-fail: (sensor value != 0) is system minor alarm fantray fan operation sensor: OK threshold #1 for fantray fan operation sensor: (sensor value != 0) is system minor alarm operating clock count: 2 threshold #1 for operating clock count: (sensor value < 2) is system minor alarm threshold #2 for operating clock count: (sensor value < 1) is system major alarm operating VTT count: 3 threshold #1 for operating VTT count: (sensor value < 3) is system minor alarm threshold #2 for operating VTT count: (sensor value < 2) is system major alarm VTT 1 OK: OK threshold #1 for VTT 1 OK: (sensor value != 0) is system minor alarm VTT 2 OK: OK threshold #1 for VTT 2 OK: (sensor value != 0) is system minor alarm VTT 3 OK: OK threshold #1 for VTT 3 OK: (sensor value != 0) is system minor alarm clock 1 OK: OK threshold #1 for clock 1 OK: (sensor value != 0) is system minor alarm clock 2 OK: OK threshold #1 for clock 2 OK: (sensor value != 0) is system minor alarm module 1 power-output-fail: OK threshold #1 for module 1 power-output-fail: (sensor value != 0) is system major alarm module 1 outlet temperature: 21C threshold #1 for module 1 outlet temperature: (sensor value > 60) is system minor alarm threshold #2 for module 1 outlet temperature: (sensor value > 70) is system major alarm module 1 inlet temperature: 25C threshold #1 for module 1 inlet temperature: (sensor value > 60) is system minor alarm threshold #2 for module 1 inlet temperature: (sensor value > 70) is system major alarm module 1 device-1 temperature: 30C threshold #1 for module 1 device-1 temperature: (sensor value > 60) is system minor alarm threshold #2 for module 1 device-1 temperature: (sensor value > 70) is system major alarm module 1 device-2 temperature: 29C threshold #1 for module 1 device-2 temperature: (sensor value > 60) is system minor alarm threshold #2 for module 1 device-2 temperature: (sensor value > 70) is system major alarm module 5 power-output-fail: OK
54-9
Chapter 54 Understanding How Environmental Monitoring Works
threshold (sensor threshold (sensor threshold (sensor threshold (sensor threshold (sensor threshold (sensor threshold (sensor threshold (sensor threshold (sensor
#1 for module 5 power-output-fail: value != 0) is system major alarm module #1 for module 5 outlet temperature: value > 60) is system minor alarm #2 for module 5 outlet temperature: value > 75) is system major alarm module #1 for module 5 inlet temperature: value > 50) is system minor alarm #2 for module 5 inlet temperature: value > 65) is system major alarm EARL 1 #1 for EARL 1 outlet temperature: value > 60) is system minor alarm #2 for EARL 1 outlet temperature: value > 75) is system major alarm EARL 1 #1 for EARL 1 inlet temperature: value > 50) is system minor alarm #2 for EARL 1 inlet temperature: value > 65) is system major alarm
5 outlet temperature: 26C
5 inlet temperature: 23C
outlet temperature: N/O
inlet temperature: N/O
Understanding How Environmental Monitoring Works

Environmental monitoring of chassis components provides early-warning indications of possible component failures, which ensures a safe and reliable system operation and avoids network interruptions. This section describes the monitoring of these critical system components, which allows you to identify and rapidly correct hardware-related problems in your system.
Note
The power output mode threshold is now dynamic. On bootup, the output mode is set to Mode 1 (minimum capacity) to Mode 4 (maximum capacity) depending on the output power capacity. The power output mode threshold is set to the bootup value of the output mode sensor and is increased when new power inputs are connected after bootup. Whenever the power output mode drops below the power output mode threshold, a POWER_OUTPUT_MODE alarm is generated.
Monitoring System Environmental Status

To display system status information, enter the show environment [alarm | cooling | status | temperature] command. The keywords display the following information:
alarmDisplays environmental alarms.

statusDisplays alarm status. thresholdsDisplays alarm thresholds.
coolingDisplays fan tray status, chassis cooling capacity, ambient temperature, and per-slot cooling capacity. statusDisplays field-replaceable unit (FRU) operational status and power and temperature information. temperatureDisplays FRU temperature information.
To view the system status information, enter the show environment command:
Router# show environment environmental alarms: no alarms
54-10
OL-3999-08
Chapter 54
Power Management and Environmental Monitoring Understanding How Environmental Monitoring Works
Router# show environment alarm environmental alarms: no alarms Router# show environment cooling fan-tray 1: fan-tray 1 fan-fail: failed fan-tray 2: fan 2 type: FAN-MOD-9 fan-tray 2 fan-fail: OK chassis cooling capacity: 690 cfm ambient temperature: 55C chassis per slot cooling capacity: 75 cfm module module module module module module 1 2 5 6 8 9 cooling cooling cooling cooling cooling cooling requirement: requirement: requirement: requirement: requirement: requirement: 70 70 30 70 70 30 cfm cfm cfm cfm cfm cfm
["40C (user-specified)" if temp-controlled]
Router# show environment status backplane: operating clock count: 2 operating VTT count: 3 fan-tray 1: fan-tray 1 type: WS-9SLOT-FAN fan-tray 1 fan-fail: OK VTT 1: VTT 1 OK: OK VTT 1 outlet temperature: 33C VTT 2: VTT 2 OK: OK VTT 2 outlet temperature: 35C VTT 3: VTT 3 OK: OK VTT 3 outlet temperature: 33C clock 1: clock 1 OK: OK, clock 1 clock-inuse: in-use clock 2: clock 2 OK: OK, clock 2 clock-inuse: not-in-use power-supply 1: power-supply 1 fan-fail: OK power-supply 1 power-output-fail: OK module 1: module 1 power-output-fail: OK module 1 outlet temperature: 30C module 1 device-2 temperature: 35C RP 1 outlet temperature: 35C RP 1 inlet temperature: 36C EARL 1 outlet temperature: 33C EARL 1 inlet temperature: 31C module 2: module 2 power-output-fail: OK module 2 outlet temperature: 31C module 2 inlet temperature: 29C module 3: module 3 power-output-fail: OK module 3 outlet temperature: 36C module 3 inlet temperature: 29C module 4: module 4 power-output-fail: OK module 4 outlet temperature: 32C module 4 inlet temperature: 32C
54-11
module 5: module 5 power-output-fail: OK module 5 outlet temperature: 39C module 5 inlet temperature: 34C module 7: module 7 power-output-fail: OK module 7 outlet temperature: 42C module 7 inlet temperature: 29C EARL 7 outlet temperature: 45C EARL 7 inlet temperature: 32C module 9: module 9 power-output-fail: OK module 9 outlet temperature: 41C module 9 inlet temperature: 36C EARL 9 outlet temperature: 33C EARL 9 inlet temperature: N/O
Understanding LED Environmental Indications

The LEDs can indicate two alarm types: major and minor. Major alarms indicate a critical problem that could lead to the system being shut down. Minor alarms are for informational purposes only, giving you notice of a problem that could turn critical if corrective action is not taken. When the system has an alarm (major or minor), that indicates an overtemperature condition, the alarm is not canceled nor is any action taken (such as module reset or shutdown) for 5 minutes. If the temperature falls 5C (41F) below the alarm threshold during this period, the alarm is canceled. Table 54-2 lists the environmental indicators for the supervisor engine and switching modules.
Note
Refer to the Catalyst 6500 Series Switch Module Installation Guide for additional information on LEDs, including the supervisor engine SYSTEM LED.
Table 54-2 Environmental Monitoring for Supervisor Engine and Switching Modules
Component Supervisor engine temperature sensor exceeds major threshold1
Alarm Type Major
LED Indication STATUS LED red

2 3
Action Generates syslog message and an SNMP trap. If there is a redundancy situation, the system switches to a redundant supervisor engine and the active supervisor engine shuts down. If there is no redundancy situation and the overtemperature condition is not corrected, the system shuts down after 5 minutes.
Supervisor engine temperature sensor exceeds minor threshold
Minor
STATUS LED orange
Generates syslog message and an SNMP trap. Monitors the condition.
54-12
OL-3999-08
Chapter 54
Power Management and Environmental Monitoring Understanding How Environmental Monitoring Works
Table 54-2 Environmental Monitoring for Supervisor Engine and Switching Modules (continued)
Component Redundant supervisor engine temperature sensor exceeds major or minor threshold
Alarm Type
LED Indication
Action Generates syslog message and an SNMP trap. If a major alarm is generated and the overtemperature condition is not corrected, the system shuts down after 5 minutes. Monitors the condition if a minor alarm is generated. Generates syslog message and SNMP. Powers down the module4. Generates syslog message and an SNMP trap. Monitors the condition.
Major STATUS LED red
Minor Switching module temperature sensor exceeds major threshold Switching module temperature sensor exceeds minor threshold Major Minor
STATUS LED orange STATUS LED red STATUS LED orange
1. Temperature sensors monitor key supervisor engine components including daughter cards. 2. A STATUS LED is located on the supervisor engine front panel and all module front panels. 3. The STATUS LED is red on the failed supervisor engine. If there is no redundant supervisor, the SYSTEM LED is red also. 4. See the Understanding How Power Management Works section on page 54-1 for instructions.
Tip
54-13
54-14
OL-3999-08
C H A P T E R
55
Configuring Generic Online Diagnostics

This chapter describes how to configure the generic online diagnostics (GOLD) on the Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, refer to the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/allreleasemcl/all_book.html

Understanding How Online Diagnostics Work, page 55-1 Configuring Online Diagnostics, page 55-2 Running Online Diagnostic Tests, page 55-5 Performing Memory Tests, page 55-10
Tip
Understanding How Online Diagnostics Work

With online diagnostics, you can test and verify the hardware functionality of the Catalyst 6500 series switch while the switch is connected to a live network. The online diagnostics contain packet switching tests that check different hardware components and verify the data path and control signals. Disruptive online diagnostic tests, such as the built-in self-test (BIST) and the disruptive loopback test, and nondisruptive online diagnostic tests, such as packet switching, run during bootup, line card online insertion and removal (OIR), and system reset. The nondisruptive online diagnostic tests run as part of background health monitoring or at the users request (on-demand).
55-1
Chapter 55 Configuring Online Diagnostics
The online diagnostics detect problems in the following areas:

Hardware components Interfaces (GBICs, Ethernet ports, and so forth) Connectors (loose connectors, bent pins, and so forth) Solder joints Memory (failure over time)
Online diagnostics is one of the requirements for the high availability feature. High availability is a set of quality standards that seek to limit the impact of equipment failures on the network. A key part of high availability is detecting hardware failures and taking corrective action while the switch runs in a live network. Online diagnostics in high availability detect hardware failures and provide feedback to high availability software components to make switchover decisions. Online diagnostics are categorized as bootup, on-demand, scheduled, or health monitoring diagnostics. Bootup diagnostics run during bootup; on-demand diagnostics run from the CLI; schedule diagnostics run at user-designated intervals or specified times when the switch is connected to a live network; and health-monitoring runs in the background.
Configuring Online Diagnostics

These sections describe how to configure online diagnostics:

Setting Bootup Online Diagnostics Level, page 55-2 Configuring On-Demand Online Diagnostics, page 55-3 Scheduling Online Diagnostics, page 55-4 Configuring Health-Monitoring Diagnostics, page 55-5
Setting Bootup Online Diagnostics Level

You can set the bootup diagnostics level as minimal or complete or you can bypass the bootup diagnostics entirely. Enter the complete keyword to run all bootup diagnostic tests; enter the minimal keyword to run only EARL tests and loopback tests for all ports in the switch. Enter the no form of the command to bypass all diagnostic tests. The default bootup diagnositcs level is minimal. To set the bootup diagnostic level, perform this task: Command
Router(config)# diagnostic bootup level {minimal | complete}
Purpose Sets the bootup diagnostic level.
This example shows how to set the bootup online diagnostic level:
Router(config)# diagnostic bootup level complete Router(config)#
This example shows how to display the bootup online diagnostic level:
Router(config)# do show diagnostic bootup level Router(config)#
55-2
OL-3999-08
Chapter 55
Configuring Generic Online Diagnostics Configuring Online Diagnostics
Configuring On-Demand Online Diagnostics

You can run the on-demand online diagnostic tests from the CLI. You can set the execution action to either stop or continue the test when a failure is detected or to stop the test after a specific number of failures occur by using the failure count setting. You can configure a test to run multiple times using the iteration setting. You should run packet-switching tests before memory tests.
Note
Do not use the diagnostic start all command until all of the following steps are completed. Because some on-demand online diagnostic tests can affect the outcome of other tests, you should perform the tests in the following order:
1. 2. 3. 4. 5.
Run the non-disruptive tests. Run all tests in the relevant functional area. Run the TestTrafficStress test. Run the TestEobcStressPing test. Run the exhaustive memory tests.
To run on-demand online diagnostic tests, perform this task:

Step 1
Run the non disruptive tests. To display the available tests and their attributes, and determine which commands are in the non disruptive category, enter the show diagnostic content command.
Step 2
Run all tests in the relevant functional area. Packet-switching tests fall into specific functional areas. When a problem is suspected in a particular functional area, run all tests in that functional area. If you are unsure about which functional area you need to test, or if you want to run all available tests, enter the complete keyword.
Step 3
Run the TestTrafficStress test. This is a disruptive packet-switching test. This test switches packets between pairs of ports at line rate for the purpose of stress testing. During this test all of the ports are shut down, and you may see link flaps. The link flaps will recover after the test is complete. The test takes several minutes to complete. Disable all health-monitoring tests f before running this test by using the no diagnostic monitor module 1 test all command.
Step 4
Run the TestEobcStressPing test. This is a disruptive test and tests the Ethernet over backplane channel (EOBC) connection for the module. The test takes several minutes to complete. You cannot run any of the packet-switching tests described in previous steps after running this test. However, you can run tests described in subsequent steps after running this test. Disable all health-monitoring tests before running this test by using the no diagnostic monitor module 1 test all command. The EOBC connection is disrupted during this test and will cause the health-monitoring tests to fail and take recovery action.
55-3
Chapter 55 Configuring Online Diagnostics
Step 5
Run the exhaustive-memory tests. Before running the exhaustive memory tests, all health-monitoring tests should be disabled because the tests will fail with health monitoring enabled and the switch will take recovery action. Disable the health-monitoring diagnostic tests by using the no diagnostic monitor module 1 test all command. Perform the exhaustive memory tests in the following order:
1. 2. 3. 4. 5.
TestFibTcamSSRAM TestAclQosTcam TestNetFlowTcam TestAsicMemory TestAsicMemory
You must reboot the after running the exhaustive memory tests before it is operational again. You cannot run any other tests on the switch after running the exhaustive memory tests. Do not save the configuration when rebooting as it will have changed during the tests. After the reboot, reenable the health monitoring tests using the diagnostic monitor module 1 test all command
To set the bootup diagnostic level, perform this task: Command

Router# diagnostic ondemand {iteration iteration_count} | {action-on-error {continue | stop}[error_count]}
Purpose Configures on-demand diagnostic tests to run, how many times to run (iterations), and what action to take when errors are found.
This example shows how to set the on-demand testing iteration count:
Router# diagnostic ondemand iteration 3 Router#
This example shows how to set the execution action when an error is detected:
Router# diagnostic ondemand action-on-error continue 2 Router#
Scheduling Online Diagnostics

You can schedule online diagnostics to run at a designated time of day or on a daily, weekly, or monthly basis. You can schedule tests to run only once or to repeat at an interval. Use the no form of this command to remove the scheduling. To schedule online diagnostics, perform this task: Command
Router(config)# diagnostic schedule module 1 test {test_id | test_id_range | all} [port {num | num_range | all}] {on mm dd yyyy hh:mm} | {daily hh:mm} | {weekly day_of_week hh:mm}
Purpose Schedules on-demand diagnostic tests for a specific date and time, how many times to run (iterations), and what action to take when errors are found.
55-4
OL-3999-08
Chapter 55
Configuring Generic Online Diagnostics Running Online Diagnostic Tests
This example shows how to schedule diagnostic testing on a specific date and time for a specific port:
Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 on january 3 2003 23:32 Router(config)#
This example shows how to schedule diagnostic testing to occur daily at a certain time for a specific port:
Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 daily 12:34 Router(config)#
This example shows how to schedule diagnostic testing to occur weekly on a certain day for a specific port:
Router(config)# diagnostic schedule module 1 test 1,2,5-9 port 3 weekly friday 09:23 Router(config)#
Configuring Health-Monitoring Diagnostics

You can configure health-monitoring diagnostic testing while the switch is connected to a live network. You can configure the execution interval for each health monitoring test, whether or not to generate a system message upon test failure, or to enable or disable an individual test. Use the no form of this command to disable testing. To configure health monitoring diagnostic testing, perform this task: Command
Step 1
Router(config)# diagnostic monitor interval module 1 test {test_id | test_id_range | all} [hour hh] [min mm] [second ss] [millisec ms] [day day] Router(config)#[no] diagnostic monitor module 1 test {test_id | test_id_range | all}
Purpose Configures the health-monitoring interval of the specified tests . The no form of this command will change the interval to the default interval, or zero. Enables or disables health-monitoring diagnostic tests.
Step 2
This example shows how to configure the specified test to run every two minutes:
Router(config)# diagnostic monitor interval module 1 test 1 min 2 Router(config)#
This example shows how to run the test if health monitoring has not previously been enabled:
Router(config)# diagnostic monitor module 1 test 1
This example shows how to enable the generation of a syslog message when any health monitoring test fails:
Router(config)# diagnostic monitor syslog Router(config)#
Running Online Diagnostic Tests

After you configure online diagnostics, you can start or stop diagnostic tests or display the test results. You can also see which tests are configured and what diagnostic tests have already run. These sections describe how to run online diagnostic tests after they have been configured:

Starting and Stopping Online Diagnostic Tests, page 55-6 Displaying Online Diagnostic Tests and Test Results, page 55-7
55-5
Chapter 55 Running Online Diagnostic Tests
Note
We recommend that before you enable any online diagnostics tests that you enable the logging console/monitor to see all warning messages. We recommend that when you are running disruptive tests that you only run the tests when connected through console. When disruptive tests are complete a warning message on the console recommends that that you reload the system to return to normal operation: strictly follow this warning. While tests are running, all ports are shut down as a stress test is being performed with looping ports internally and external traffic might skew the test results. The entire switch must be rebooted to bring the switch to normal operation. When you issure the command to reload the switch, the system will ask you if the configuration should be saved. Do not save the configuration. If you are running the tests on a supervisor engine, after the test is initiated and complete, you must reload or power down and then power up the entire system. If you are running the tests on a module that is not the supervisor engine, after the test is initiated and complete, you must reset the module.
Starting and Stopping Online Diagnostic Tests

After you configure diagnostic tests to run, you can use the start and stop to begin or end a diagnostic test. To start or stop an online diagnostic command, perform one of these tasks: Command
diagnostic start module 1 test {test_id | test_id_range | minimal | complete | basic | per-port | non-disruptive | all} [port {num | port#_range | all}] diagnostic stop module 1
Purpose Starts a diagnostic test on a port or range of ports.
Stops a diagnostic test.
This example shows how to start a diagnostic test:

Router# diagnostic start module 1 test 5 Module 1:Running test(s) 5 may disrupt normal system operation Do you want to run disruptive tests? [no]yes 00:48:14:Running OnDemand Diagnostics [Iteration #1] ... 00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ... 00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully 00:48:14:Running OnDemand Diagnostics [Iteration #2] ... 00:48:14:%DIAG-SP-6-TEST_RUNNING:Module 1:Running TestNewLearn{ID=5} ... 00:48:14:%DIAG-SP-6-TEST_OK:Module 1:TestNewLearn{ID=5} has completed successfully Router#
This example shows how to stop a diagnostic test:

Router# diagnostic stop module 1 Router#
55-6
OL-3999-08
Chapter 55
Displaying Online Diagnostic Tests and Test Results

You can display the online diagnostic tests that are configured and check the results of the tests using the show commands. To display the diagnostic tests that are configured, perform this task: Command
show diagnostic content [module 1]
Purpose Displays the online diagnostics that are configured.
This example shows how to display the online diagnostics that are configured:
Router# show diagnostic content module 1 Module 1: Diagnostics test suite attributes: M/C/* - Minimal bootup level test / Complete bootup level test / NA B/* - Basic ondemand test / NA P/V/* - Per port test / Per device test / NA D/N/* - Disruptive test / Non-disruptive test / NA S/* - Only applicable to standby unit / NA X/* - Not a health monitoring test / NA F/* - Fixed monitoring interval test / NA E/* - Always enabled monitoring test / NA A/I - Monitoring is active / Monitoring is inactive R/* - Power-down line cards and need reset supervisor / NA K/* - Require resetting the line card after the test has completed / NA Testing Interval (day hh:mm:ss.ms) ================= 000 00:00:30.00 000 00:00:15.00 not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured not configured
ID ==== 1) 2) 3) 4) 5) 6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18) 19) 20) 21) 22) 23) 24) 25) 26) 27) 28)
Test Name ================================== TestScratchRegister -------------> TestSPRPInbandPing --------------> TestTransceiverIntegrity --------> TestActiveToStandbyLoopback -----> TestLoopback --------------------> TestNewLearn --------------------> TestIndexLearn ------------------> TestDontLearn -------------------> TestConditionalLearn ------------> TestBadBpdu ---------------------> TestTrap ------------------------> TestMatch -----------------------> TestCapture ---------------------> TestProtocolMatch ---------------> TestChannel ---------------------> TestFibDevices ------------------> TestIPv4FibShortcut -------------> TestL3Capture2 ------------------> TestIPv6FibShortcut -------------> TestMPLSFibShortcut -------------> TestNATFibShortcut --------------> TestAclPermit -------------------> TestAclDeny ---------------------> TestQoSTcam ---------------------> TestL3VlanMet -------------------> TestIngressSpan -----------------> TestEgressSpan ------------------> TestNetflowInlineRewrite -------->
Attributes ============ ***N****A** ***N****A** **PD****I** M*PDS***I** M*PD****I** M**N****I** M**N****I** M**N****I** M**N****I** M**D****I** M**D****I** M**D****I** M**D****I** M**D****I** M**D****I** M**N****I** M**N****I** M**N****I** M**N****I** M**N****I** M**N****I** M**N****I** M**D****I** M**D****I** M**N****I** M**N****I** M**N****I** C*PD****I**
55-7
Chapter 55 Running Online Diagnostic Tests
29) 30) 31) 32)
TestFabricSnakeForward ----------> TestFabricSnakeBackward ---------> TestFibTcamSSRAM ----------------> ScheduleSwitchover -------------->
M**N****I** M**N****I** ***D****IR* ***D****I**
not not not not
configured configured configured configured
Router#
This example shows how to display the online diagnostic results :

Router# show diagnostic result module 1 Current bootup diagnostic level:minimal Module 1: Overall Diagnostic Result for Module 1 :PASS Diagnostic level at card bootup:minimal Test results:(. = Pass, F = Fail, U = Untested) 1) TestScratchRegister -------------> . 2) TestSPRPInbandPing --------------> . 3) TestGBICIntegrity: Port 1 2 ---------U U
4) TestActiveToStandbyLoopback: Port 1 2 ---------U U
5) TestLoopback: Port 1 2 ---------. .
6) 7) 8) 9) 10) 11) 12) 13) 14) 15) 16) 17) 18) 19) 20) 21) 22) 23) 24) 25) 26)
TestNewLearn --------------------> TestIndexLearn ------------------> TestDontLearn -------------------> TestConditionalLearn ------------> TestBadBpdu ---------------------> TestTrap ------------------------> TestMatch -----------------------> TestCapture ---------------------> TestProtocolMatch ---------------> TestChannel ---------------------> TestIPv4FibShortcut -------------> TestL3Capture2 ------------------> TestL3VlanMet -------------------> TestIngressSpan -----------------> TestEgressSpan ------------------> TestIPv6FibShortcut -------------> TestMPLSFibShortcut -------------> TestNATFibShortcut --------------> TestAclPermit -------------------> TestAclDeny ---------------------> TestQoSTcam --------------------->
. . . . . . . . . . . . . . . . . . . . .
55-8
OL-3999-08
Chapter 55
27) TestNetflowInlineRewrite: Port 1 2 ---------U U
28) TestFabricSnakeForward ----------> . 29) TestFabricSnakeBackward ---------> . 30) TestFibTcam - RESET -------------> U Router#
This example shows how to display the detailed online diagnostic results:
Router# show diagnostic result module 1 detail Current bootup diagnostic level:minimal Module 1: Overall Diagnostic Result for Module 1 :PASS Diagnostic level at card bootup:minimal Test results:(. = Pass, F = Fail, U = Untested) ___________________________________________________________________________ 1) TestScratchRegister -------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 330 Last test execution time ----> May 12 2003 14:49:36 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> May 12 2003 14:49:36 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 2) TestSPRPInbandPing --------------> . Error code ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 660 Last test execution time ----> May 12 2003 14:49:38 First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> May 12 2003 14:49:38 Total failure count ---------> 0 Consecutive failure count ---> 0 ___________________________________________________________________________ 3) TestGBICIntegrity: Port 1 2 ---------U U
Error code ------------------> Total run count -------------> Last test execution time ----> First test failure time -----> Last test failure time ------> Last test pass time ---------> Total failure count --------->
0 (DIAG_SUCCESS) 0 n/a n/a n/a n/a 0
55-9
Chapter 55 Performing Memory Tests
Consecutive failure count ---> 0 ________________________________________________________________________ Router#
Performing Memory Tests

Most online diagnostic tests do not need any special setup or configuration. However, the memory tests, which include the TestFibTcamSSRAM and TestLinecardMemory tests, have some required tasks and some recommended tasks that you should complete before running them. Before you run any of the online diagnostic memory tests, perform the following tasks:
Required tasks
Isolate network traffic by disabling all connected ports. Do not send test packets during a memory test. Reset the system before returning the system to normal operating mode.
Turn off all background health monitoring tests using the no diagnostic monitor module 1 test all command.
Tip
55-10
OL-3999-08
C H A P T E R
56
Using the Top N Utility

This chapter describes how to use the Top N utility on the Catalyst 6500 series switches. Release 12.2(18)SXE and later releases support the Top N utility.
Note

Understanding the Top N Utility, page 56-1 Using the Top N Utility, page 56-2
Tip
Understanding the Top N Utility

These sections describe the Top N utility:

Top N Utility Overview, page 56-1 Understanding Top N Utility Operation, page 56-2
Top N Utility Overview

The Top N utility allows you to collect and analyze data for each physical port on a switch. When the Top N utility starts, it obtains statistics from the appropriate hardware counters and then goes into sleep mode for a user-specified interval. When the interval ends, the utility obtains the current statistics from the same hardware counters, compares the current statistics from the earlier statistics, and stores the difference. The statistics for each port are sorted by one of the statistic types that are listed in Table 56-1.
56-1
Chapter 56 Using the Top N Utility
Table 56-1 Valid Top N Statistic Types
Statistic Type broadcast bytes errors multicast overflow packets utilization
Definition Number of input/output broadcast packets Number of input/output bytes Number of input errors Number of input/output multicast packets Number of buffer overflows Number of input/output packets Utilization
Note
When calculating the port utilization, the Top N utility bundles the Tx and Rx lines into the same counter and also looks at the full-duplex bandwidth when calculating the percentage of utilization. For example, a Gigabit Ethernet port would be 2000-Mbps full duplex.
Understanding Top N Utility Operation

When you enter the collect top command, processing begins and the system prompt reappears immediately. When processing completes, the reports are not displayed immediately on the screen; the reports are saved for later viewing. The Top N Utility notifies you when the reports are complete by sending a syslog message to the screen. To view the completed reports, enter the show top counters interface report command. The Top N Utility displays only those reports that are completed. For reports that are not completed, the Top N Utility displays a short description of the Top N process information. To terminate a Top N process, enter the clear top counters interface report command. Pressing Ctrl-C does not terminate Top N processes. The completed reports remain available for viewing until you remove them by entering the clear top counters interface report {all | report_num} command.

These sections describe how to use the Top N Utility:

Enabling Top N Utility Report Creation, page 56-3 Displaying the Top N Utility Reports, page 56-3 Clearing Top N Utility Reports, page 56-4
56-2
OL-3999-08
Chapter 56
Using the Top N Utility Using the Top N Utility
Enabling Top N Utility Report Creation

To enable Top N Utility report creation, perform this task: Command
Router# collect top [number_of_ports] counters interface {interface_type1 | all | layer-2 | layer-3} [sort-by statistic_type2] [interval seconds]
Purpose Enables Top N Utility report creation.
1. interface_type = ethernet , fastethernet , gigabitethernet, tengigabitethernet, port-channel 2. statistic_type = broadcast, bytes, errors , multicast , overflow, packets, utilization
When enabling Top N Utility report creation, note the following information:

You can specify the number of busiest ports for which to create reports (the default is 20). You can specify the statistic type by which ports are determined to be the busiest (the default is utilization). You can specify the interval over which statistics are collected (range: 0 through 999; the default is 30 seconds). Except for a utilization report (configured with the sort-by utilization keywords), you can specify an interval of zero to create a report that displays the current counter values instead of a report that displays the difference between the start-of-interval counter values and the end-of-interval counter values.
This example shows how to enable Top N Utility report creation for an interval of 76 seconds for the four ports with the highest utilization:
Router# collect top 4 counters interface all sort-by utilization interval 76 TopN collection started.
Displaying the Top N Utility Reports

To display the Top N Utility reports, perform this task: Command
Router# show top counters interface report [report_num]
Purpose Displays the Top N Utility reports.

Note
To display information about all the reports, do not enter a report_num value.
Top N Utility statistics are not displayed in these situations:

If a port is not present during the first poll. If a port is not present during the second poll. If a ports speed or duplex changes during the polling interval. If a ports type changes from Layer 2 to Layer 3 during the polling interval. If a ports type changes from Layer 3 to Layer 2 during the polling interval.
56-3
This example shows how to display information about all the Top N Utility reports:
Router# show top counters interface Id Start Time Int -- ---------------------------- --1 08:18:25 UTC Tue Nov 23 2004 76 2 08:19:54 UTC Tue Nov 23 2004 76 3 08:21:34 UTC Tue Nov 23 2004 76 4 08:26:50 UTC Tue Nov 23 2004 90 report N Sort-By --- --------20 util 20 util 20 util 20 util Status ------done done done done Owner ---------------------console console console console
Note
Reports for which statistics are still being obtained are shown with a status of pending. This example shows how to display a specific Top N Utility report:
Router# show top counters interface report 1 Started By : console Start Time : 08:18:25 UTC Tue Nov 23 2004 End Time : 08:19:42 UTC Tue Nov 23 2004 Port Type : All Sort By : util Interval : 76 seconds Port Band Util Bytes Packets Broadcast Multicast In- Bufwidth (Tx + Rx) (Tx + Rx) (Tx + Rx) (Tx + Rx) err ovflw ------- ----- ---- ----------- ----------- ---------- ---------- ---- ----Fa2/5 Fa2/48 Fa2/46 Fa2/47 100 100 100 100 50 35 25 22 726047564 508018905 362860697 323852889 11344488 7937789 5669693 4762539 11344487 0 0 4762495 1 43 43 43 0 0 0 0 0 0 0 0
Clearing Top N Utility Reports

To clear Top N Utility reports, perform one of these tasks: Command
Router# clear top counters interface report
Purpose Clears all the Top N Utility reports that have a status of done. Clears Top N Utility report number report_num regardless of status.
Router# clear top counters interface report [report_num]
This example shows how to remove all reports that have a status of done:
Router# clear top counters interface report 04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 04:00:06: %TOPN_COUNTERS-5-DELETED: TopN report 1 2 3 4 deleted deleted deleted deleted by by by by the the the the console console console console
This example shows how to remove a report number 4:

Router# clear top counters interface report 4 04:52:12: %TOPN_COUNTERS-5-KILLED: TopN report 4 killed by the console
56-4
OL-3999-08
Chapter 56
Using the Top N Utility Using the Top N Utility
Tip
56-5
56-6
OL-3999-08
C H A P T E R
57
Using the Layer 2 Traceroute Utility

This chapter describes how to use the Layer 2 traceroute utility. Release 12.2(18)SXE and later releases support the Layer 2 traceroute utility.
Note

Understanding the Layer 2 Traceroute Utility, page 57-1 Usage Guidelines, page 57-2 Using the Layer 2 Traceroute Utility, page 57-3
Tip
Understanding the Layer 2 Traceroute Utility

The Layer 2 traceroute utility identifies the Layer 2 path that a packet takes from a source device to a destination device. Layer 2 traceroute supports only unicast source and destination MAC addresses. The utility determines the path by using the MAC address tables of the switches in the path. When the Layer 2 traceroute utility detects a device in the path that does not support Layer 2 traceroute, it continues to send Layer 2 trace queries and allows them to time out. The Layer 2 traceroute utility can only identify the path from the source device to the destination device. The utility cannot identify the path that a packet takes from the source host to the source device or from the destination device to the destination host.
57-1
Chapter 57 Usage Guidelines
Usage Guidelines
When using the Layer 2 traceroute utility, follow these guidelines:
Cisco Discovery Protocol (CDP) must be enabled on all the devices in the network. For the Layer 2 traceroute utility to function properly, do not disable CDP. If any devices in the Layer 2 path are transparent to CDP, the Layer 2 traceroute utility cannot identify these devices on the path.
Note
For more information about CDP, see Chapter 48, Configuring CDP.
A switch is defined as reachable from another switch when you can test connectivity by using the ping privileged EXEC command. All devices in the Layer 2 path must be mutually reachable. The maximum number of hops identified in the path is ten. You can enter the traceroute mac or the traceroute mac ip privileged EXEC command on a switch that is not in the Layer 2 path from the source device to the destination device. All devices in the path must be reachable from this switch. The traceroute mac command output shows the Layer 2 path only when the specified source and destination MAC addresses belong to the same VLAN. If you specify source and destination MAC addresses that belong to different VLANs, the Layer 2 path is not identified, and an error message appears. If you specify a multicast source or destination MAC address, the path is not identified, and an error message appears. If the source or destination MAC address belongs to multiple VLANs, you must specify the VLAN to which both the source and destination MAC addresses belong. If the VLAN is not specified, the path is not identified, and an error message appears. The traceroute mac ip command output shows the Layer 2 path when the specified source and destination IP addresses belong to the same subnet. When you specify the IP addresses, the Layer 2 traceroute utility uses the Address Resolution Protocol (ARP) to associate the IP addresses with the corresponding MAC addresses and the VLAN IDs.
If an ARP entry exists for the specified IP address, the Layer 2 traceroute utility uses the
associated MAC address and identifies the Layer 2 path.

If an ARP entry does not exist, the Layer 2 traceroute utility sends an ARP query and tries to
resolve the IP address. If the IP address is not resolved, the path is not identified, and an error message appears.
When multiple devices are attached to one port through hubs (for example, multiple CDP neighbors are detected on a port), the Layer 2 traceroute utility terminates at that hop and displays an error message. The Layer 2 traceroute utility is not supported in Token Ring VLANs.
57-2
OL-3999-08
Chapter 57
Using the Layer 2 Traceroute Utility Using the Layer 2 Traceroute Utility

To display the Layer 2 path that a packet takes from a source device to a destination device, perform one of these tasks in privileged EXEC mode: Command
Router# traceroute mac [interface type interface_number] source_mac_address [interface type interface_number] destination_mac_address [vlan vlan_id] [detail ] Router# traceroute mac ip {source_ip_address | source_hostname} {destination_ip_address | destination_hostname} [ detail ]
Purpose Uses MAC addresses to trace the path that packets take through the network. Uses IP addresses to trace the path that packets take through the network.
57-3
Chapter 57 Using the Layer 2 Traceroute Utility
These examples show how to use the traceroute mac and traceroute mac ip commands to display the physical path a packet takes through the network to reach its destination:
Router# traceroute mac 0000.0201.0601 0000.0201.0201 Source 0000.0201.0601 found on con6[WS-C2950G-24-EI] (2.2.6.6) con6 (2.2.6.6) :Fa0/1 => Fa0/3 con5 (2.2.5.5 ) : Fa0/3 => Gi0/1 con1 (2.2.1.1 ) : Gi0/1 => Gi0/2 con2 (2.2.2.2 ) : Gi0/2 => Fa0/1 Destination 0000.0201.0201 found on con2[WS-C3550-24] (2.2.2.2) Layer 2 trace completed Router# Router# traceroute mac 0001.0000.0204 0001.0000.0304 detail Source 0001.0000.0204 found on VAYU[WS-C6509] (2.1.1.10) 1 VAYU / WS-C6509 / 2.1.1.10 : Gi6/1 [full, 1000M] => Po100 [auto, auto] 2 PANI / WS-C6509 / 2.1.1.12 : Po100 [auto, auto] => Po110 [auto, auto] 3 BUMI / WS-C6509 / 2.1.1.13 : Po110 [auto, auto] => Po120 [auto, auto] 4 AGNI / WS-C6509 / 2.1.1.11 : Po120 [auto, auto] => Gi8/12 [full, 1000M] Destination 0001.0000.0304 found on AGNI[WS-C6509] (2.1.1.11) Layer 2 trace completed. Router#
Tip
57-4
OL-3999-08
A P P E N D I X

This appendix describes the online diagnostic tests and provides recommendations for how to use them.
Note
For information about configuring online diagnostic tests refer to Chapter 55, Configuring Generic Online Diagnostics. We recommend that before you enable any online diagnostics tests that you enable the logging console/monitor to see all warning messages. We recommend that when you are running disruptive tests that you only run the tests when connected through console. When disruptive tests are complete a warning message on the console recommends that that you reload the system to return to normal operation: Strictly follow this warning. While tests are running, all ports are shut down as a stress test is being performed with looping ports internally and external traffic might skew the test results. The entire switch must be rebooted to bring the switch to normal operation. When you issure the command to reload the switch, the system will ask you if the configuration should be saved. Do not save the configuration. If you are running the tests on a supervisor engine, after the test is initiated and complete, you must reload or power down and then power up the entire system. If you are running the tests on a module that is not the supervisor engine, after the test is initiated and complete, you must reset the module.
The online diagnostic tests are included in these categories:

Global Health-Monitoring Tests, page A-2 Per-Port Tests, page A-3 PFC Layer 2 Forwarding Engine Tests, page A-7 DFC Layer 2 Forwarding Engine Tests, page A-9 PFC Layer 3 Forwarding Engine Tests, page A-14 DFC Layer 3 Forwarding Engine Tests, page A-19 Replication Engine Tests, page A-25 Fabric Tests, page A-26 Exhaustive Memory Tests, page A-29
A-1
Appendix A Global Health-Monitoring Tests
IPSEC Services Modules Tests, page A-32 Stress Tests, page A-33 Critical Recovery Tests, page A-34 General Tests, page A-36
Tip
Global Health-Monitoring Tests

The global health monitoring tests consist of the following tests: TestSPRPInbandPing, page A-2 TestMacNotification, page A-3
TestSPRPInbandPing
The TestSPRPIinbandPing test detects most runtime software driver and hardware problems on supervisor engines by running diagnostic packet tests using the Layer 2 forwarding engine, the Layer 3 and 4 forwarding engine, and the replication engine on the path from the switch processor to the route processor. Packets are sent at 15-second intervals. Ten consecutive failures of the test results in failover to the redundant supervisor engine (default) or reload of the supervisor engine if a redundant supervisor engine is not installed.
Table 0-1 TestSPRPInbandPing Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default Release Corrective action Hardware support
Description Nondisruptive. Do not disable. Test is automatically disabled during CPU-usage spikes in order to maintain accuracy. On. 12.1(13)E, 12.2(14)SX to12.2(17d)SXB5, and 12.2(18)SXD. Reset the active supervisor engine. Active and standby supervisor engine.
A-2
OL-3999-08
Appendix A
Online Diagnostic Tests Per-Port Tests
TestScratchRegister
The TestScratchRegister test monitors the health of application-specific integrated circuits (ASICs) by writing values into registers and reading back the values from these registers. The test runs every 30 seconds. Five consecutive failures causes a supervisor engine to switchover (or reset), if you are testing the supervisor engine, or in the module powering down when testing a module.
Table 0-2 TestScratchRegister Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default Release Corrective action
Description Nondisruptive. Do not disable. On. 12.2(14)SX. Reset the malfunctioning supervisor engine or power down the module. Supervisor Engine 720, DFC-equipped modules, WS-X6148-FE-SFP, WS-X6148A-GE-TX, and WS-X6148A-RJ-45 .
Hardware support
TestMacNotification
The TestMacNotification test verifies that the data and control path between DFC modules and supervisor engines is working properly. This test also ensures Layer 2 MAC address consistency across Layer 2 MAC address tables. The test runs every six seconds. Ten consecutive failures causes the module to reset during bootup or runtime (default). After three consecutive resets, the module powers down.
Table 0-3 TestMacNotification Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(14)SX. Reset the module. After the module has ten consecutive failures or three consecutive resets, it powers down. DFC-equipped modules.
Per-Port Tests
The per-port tests consist of the following tests: TestNonDisruptiveLoopback, page A-4 TestLoopback, page A-4
A-3
Appendix A Per-Port Tests
TestActiveToStandbyLoopback, page A-5 TestTransceiverIntegrity, page A-5 TestNetflowInlineRewrite, page A-6
TestNonDisruptiveLoopback
The TestNonDisruptiveLoopback test verifies the data path between the supervisor engine and the network ports of a module. In this test, a Layer 2 packet is flooded onto VLAN that contains a group of test ports. The test port group consists of one port per port ASIC channel. Each port in the test port group nondisruptively loops back the packet and directs it back to the supervisor engines inband port. The ports in the test port group are tested in parallel.
Table 0-4 TestNonDisruptiveLoopback Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default Release
Description Nondisruptive. Do not disable. On. 12.2(18)SXF. Error disable a port after 10 consecutive failures. Error disable a channel if all of its ports failed the test in one test cycle. Reset the module after a failure of all channels. WS-X6148-FE-SFP, WS-X6148A-GE-TX and WS-X6148A-RJ-45.
Corrective action Hardware support
TestLoopback
The TestLoopback test verifies the data path between the supervisor engine and the network ports of a module. In this test, a Layer 2 packet is flooded onto a VLAN that consists of only the test port and the supervisor engines inband port. The packet loops back in the port and returns to the supervisor engine on that same VLAN.
Table 0-5 TestLoopback Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. Runs at bootup or after online insertion and removal (OIR). 12.1(13)E, 12.2(14)SX.
Disruptive/Nondisruptive Recommendation Default Release
A-4
OL-3999-08
Appendix A
Online Diagnostic Tests Per-Port Tests
Table 0-5
TestLoopback Test Attributes (continued)
Error disable a port if the loopback test fails on the port. Reset the module if all of the ports fail. All modules including supervisor engines.
TestActiveToStandbyLoopback
The TestActiveToStandbyLoopback test verifies the data path between the active supervisor engine and the network ports of the standby supervisor engine. In this test, a Layer 2 packet is flooded onto a VLAN that consists of only the test port and the supervisor engines inband port. The test packets are looped back in the targeted port and are flooded back onto the bus with only the active supervisor enginess inband port listening in on the flooded VLAN.
Table 0-6 TestActiveToStandbyLoopback Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of loopback port (for example, Spanning Tree Protocol.). Schedule during downtime. Runs at bootup or after OIR. 12.1(13)E, 12.2(14)SX. Error disable a port if the loopback test fails on the port. Reset the supervisor engine if all of the ports fail. Standby supervisor engine only.
Disruptive/Nondisruptive Recommendation Default Release Corrective action Hardware support
TestTransceiverIntegrity
The TestTransceiverIntegrity test is a security test performed on the transceiver during transceiver online insertion and removal (OIR) or module bootup to make sure that the transceiver is supported.
Table 0-7 TestTransceiverIntegrity Test Attributes
Description Nondisruptive. Not applicable. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. Error disable the port. All modules with transceivers.
A-5
Appendix A Per-Port Tests
TestNetflowInlineRewrite
The TestNetflowInlineRewrite test verifies the NetFlow lookup operation, the ACL permit and deny functionality, and the inline rewrite capabilities of the port ASIC. The test packet will undergo a NetFlow table lookup to obtain the rewrite information. The VLAN and the source and destination MAC addresses are rewritten when the packet reaches the targeted port.
Table 0-8 TestNetflowInlineRewrite Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on configuration of loopback port (for example, Spanning Tree Protocol). Schedule during downtime. Run this test during bootup only. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. All modules including supervisor engines.
A-6
OL-3999-08
Appendix A
Online Diagnostic Tests PFC Layer 2 Forwarding Engine Tests
PFC Layer 2 Forwarding Engine Tests

The PFC Layer 2 Forwarding Engine tests consist of the following tests: TestNewIndexLearn, page A-7 TestDontConditionalLearn, page A-7 TestBadBpduTrap, page A-8 TestMatchCapture, page A-8 TestStaticEntry, page A-9
TestNewIndexLearn
The TestNewIndexLearn test is a combination of the TestNewLearn and the TestIndexLearn tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-9.
Table 0-9 TestNewIndexLearn Test Attributes
Attribute Disruptive/Nondisruptive
Description Nondisruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines only.
Recommendation Default Release Corrective action Hardware support
TestDontConditionalLearn
The TestDontConditionalLearn test is a combination of the TestDontLearn and the TestConditionalLearn tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-9.
Table 0-10 TestDontConditionalLearn Test Attributes
Description Nondisruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX.
Recommendation Default Release
A-7
Appendix A PFC Layer 2 Forwarding Engine Tests
Table 0-10
TestDontConditionalLearn Test Attributes (continued)
None. See the system message guide for more information. Supervisor engines only.
TestBadBpduTrap
The TestBadBpduTrap test is a combination of the TestTrap and the TestBadBpdu tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-9.
Table 0-11 TestBadBpduTrap Test Attributes
Description Disruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines only.
TestMatchCapture
The TestMatchCapture test is a combination of the TestProtocolMatchChannel and the TestCapture tests, which are described in the DFC Layer 2 Forwarding Engine Tests section on page A-9.
Table 0-12 TestMatchCapture Test Attributes
Description Disruptive. If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines only.
A-8
OL-3999-08
Appendix A
Online Diagnostic Tests DFC Layer 2 Forwarding Engine Tests
TestStaticEntry
The TestStaticEntry test verifies that static entries are populated in the Layer 2 MAC address table. This functionality is verified during diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-13 TestStaticEntry Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of looped-back port (for example, Spanning Tree Protocol). If you experience problems with the Layer 2 forwarding engine learning capability, run this test on-demand to verify the Layer 2 learning functionality. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
Disruptive/Nondisruptive
DFC Layer 2 Forwarding Engine Tests

The DFC Layer 2 Forwarding Engine tests consists of the following tests: TestDontLearn, page A-9 TestNewLearn, page A-10 TestIndexLearn, page A-10 TestConditionalLearn, page A-11 TestTrap, page A-11 TestBadBpdu, page A-12 TestProtocolMatchChannel, page A-13 TestCapture, page A-13 TestStaticEntry, page A-14
TestDontLearn
The TestDontLearn test verifies that new source MAC addresses are not populated in the MAC address table when they should not be learned. This test verifies that the don't learn feature of the Layer 2 forwarding engine is working properly. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engine inband port through the switch fabric and looped back from one of the ports on the DFC-enabled module. The don't learn feature is verified during diagnostic packet lookup by the Layer 2 forwarding engine.
A-9
Appendix A DFC Layer 2 Forwarding Engine Tests
Table 0-14
TestDontLearn Test Attributes
Attribute
Description Disruptive for looped back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestNewLearn
The TestNewLearn test verifies the Layer 2 source MAC address learning functionality of the Layer 2 forwarding engine. For supervisor engines, a diagnostic packet is sent from the supervisor engine inband port to verify that the Layer 2 forwarding engine is learning the new source MAC address from the diagnostic packet. For DFC-enabled modules, a diagnostic packet is sent from the supervisor engine inband port through the switch fabric and looped backed from one of the ports on the DFC-enabled module. The Layer 2 learning functionality is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-15 TestNewLearn Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestIndexLearn
The TestIndexLearn test ensures that existing MAC address table entries can be updated. This test verifies the Index Learn feature of the Layer 2 forwarding engine is working properly. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engine Layer 2 forwarding engine. For DFC-enabled
A-10
OL-3999-08
Appendix A
modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Index Learn feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-16 TestIndexLearn Test Attributes
Attribute
TestConditionalLearn
The TestConditionalLearn test verifies the ability to learn a Layer 2 source MAC address under specific conditions. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engine Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Conditional Learn feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-17 TestConditionalLearn Test Attributes
Attribute
Description Disruptive for looped back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
TestTrap
The TestTrap test verifies the ability to trap or redirect packets to the switch processor. This test verifies that the Trap feature of the Layer 2 forwarding engine is working properly. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs
A-11
a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Trap feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-18 TestTrap Test Attributes
Attribute
TestBadBpdu
The TestBadBpdu test verifies the ability to trap or redirect packets to the switch processor. This test verifies that the Trap feature of the Layer 2 forwarding engine is working properly. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The BPDU feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-19 TestBadBpdu Test Attributes
Attribute
A-12
OL-3999-08
Appendix A
TestProtocolMatchChannel
The TestProtocolMatchChannel test verifies the ability to match specific Layer 2 protocols in the Layer 2 forwarding engine. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. T he Match feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-20 TestProtocolMatchChannel Test Attributes
Attribute
TestCapture
The TestCapture test verifies that the capture feature of Layer 2 forwarding engine is working properly. The capture functionality is used for multicast replication. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Capture feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-21 TestCapture Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. DFC-enabled modules.
A-13
TestStaticEntry
The TestStaticEntry test verifies the ability to populate static entries in the Layer 2 MAC address table. When running the test on the supervisor engine, the diagnostic packet is sent from the supervisor engines inband port and performs a packet lookup using the supervisor engines Layer 2 forwarding engine. For DFC-enabled modules, the diagnostic packet is sent from the supervisor engines inband port through the switch fabric and looped back from one of the DFC ports. The Static Entry feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table 0-22 TestStaticEntry Test Attributes
Attribute
PFC Layer 3 Forwarding Engine Tests

The PFC Layer 3 Forwarding Engine tests consists of the following tests: TestFibDevices, page A-14 TestIPv4FibShortcut, page A-15 TestIPv6FibShortcut, page A-15 TestMPLSFibShortcut, page A-16 TestNATFibShortcut, page A-16 TestL3Capture2, page A-17 TestAclPermit, page A-17 TestAclDeny, page A-18 TestQoS, page A-18
TestFibDevices
The TestFibDevices test verifies whether the FIB TCAM and adjacency devices are functional. One FIB entry is installed on each FIB TCAM device. A diagnostic packet is sent to make sure that the diagnostic packet is switched by the FIB TCAM entry installed on the TCAM device. This is not an exhaustive TCAM device test; only one entry is installed on each TCAM device.
A-14
OL-3999-08
Appendix A
Note
Compared to the IPv4FibShortcut and IPv6FibShortcut tests, this test tests all FIB and adjacency devices using IPv4 or IPv6 packets, depending on your configuration.
Table 0-23
TestFibDevices Test Attributes
Description Nondisruptive. Run this test on-demand to verify the Layer 3 forwarding functionality if you experience problems with the routing capability. This test can also be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestIPv4FibShortcut
The TestIPv4FibShortcut test verifies the IPV4 FIB forwarding of the Layer 3 forwarding engine is working properly. One diagnostic IPV4 FIB and adjacency entry is installed and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
Table 0-24 TestIPv4FibShortcut Test Attributes
TestIPv6FibShortcut
The TestIPv6FibShortcut test verifies that the IPV6 FIB forwarding of the Layer 3 forwarding engine is working properly. One diagnostic IPV6 FIB and adjacency entry is installed and a diagnostic IPv6 packet is sent to make sure the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
A-15
Table 0-25
TestIPv6FibShortcut Test Attributes
TestMPLSFibShortcut
The TestMPLSFibShortcut test verifies that the MPLS forwarding of the Layer 3 forwarding engine is working properly. One diagnostic MPLS FIB and adjacency entry is installed and a diagnostic MPLS packet is sent to make sure that the diagnostic packet is forwarded according to the MPLS label from the adjacency entry.
Table 0-26 TestMPLSFibShortcut Test Attributes
Description Nondisruptive. This test can also be used as a health-monitoring test. Use as a health-monitoring test if you are routing MPLS traffic. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestNATFibShortcut
The TestNATFibShortcut test verifies the ability to rewrite a packet based on the NAT adjacency information (rewrite destination IP address). One diagnostic NAT FIB and adjacency entry is installed and the diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to the rewritten IP address.
Table 0-27 TestNATFibShortcut Test Attributes
Description Nondisruptive.
A-16
OL-3999-08
Appendix A
Table 0-27
TestNATFibShortcut Test Attributes (continued)
This test can also be used as a health-monitoring test. Use as a health-monitoring test if the destination IP address is being rewritten (for example, if you are using NAT). This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestL3Capture2
The TestL3Capture2 test verifies that the Layer 3 capture (capture 2) feature of the Layer 3 forwarding engine is working properly. This capture feature is used for ACL logging and VACL logging. One diagnostic FIB and adjacency entry with a capture 2 bit set is installed and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to the capture bit information.
Table 0-28 TestL3Capture2 Test Attributes
Description Disruptive. This test can not be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestAclPermit
The TestAclPermit test verifies that the ACL permit functionality is working properly. An ACL entry permitting a specific diagnostics packet is installed in the ACL TCAM. The corresponding diagnostic packet is sent from the supervisor engine and looked up by the Layer 3 forwarding engine to make sure that it hits the ACL TCAM entry and gets permitted and forwarded appropriately.
Table 0-29 TestACLPermit Test Attributes
Description Disruptive. This test can not be used as a health-monitoring test. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
A-17
TestAclDeny
The TestAclDeny test verifies that the ACL deny feature of the Layer 2 and Layer 3 forwarding engine is working properly. The test uses different ACL deny scenarios such as input, output, Layer 2 redirect, Layer 3 redirect, and Layer 3 bridges to determine whether or not the ACL deny feature is working properly.
Table 0-30 TestACLDeny Test Attributes
Description Disruptive. Do not disable. On. 12.1(13)E, 12.2(14)SX. Automatic ASIC reset for recovery. Supervisor engines and DFC-enabled modules.
TestNetflowShortcut
The TestNetflowShortcut test verifies that the NetFlow forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic NetFlow entry and adjacency entry is installed, and a diagnostic packet is sent to make sure it is forwarded according to the rewritten MAC and VLAN information.
Table 0-31 TestNetflowShortcut Test Attributes
Attributes Disruptive/Nondisruptive Recommendation Default Release Corrective action Hardware support
Description Disruptive for looped back ports. The disruption is 500 ms. Run this test on-demand if you suspect that NetFlow is not working properly. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestQoS
The TestQoS test verifies whether or not the QoS input and output TCAM is functional by programming the QoS input and output TCAM so that the ToS value of the diagnostic packet is changed to reflect either input or output.
A-18
OL-3999-08
Appendix A
Table 0-32
TestQoS Test Attributes
Attributes Disruptive/Nondisruptive Recommendation Default Release Corrective action Hardware support
Description Disruptive for looped back ports. The disruption is 500 ms. Schedule during downtime. This test runs by default during bootup or after a reset or OIR 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
DFC Layer 3 Forwarding Engine Tests

The DFC Layer 3 Forwarding Engine tests consists of the following tests: TestFibDevices, page A-19 TestIPv4FibShortcut, page A-20 TestIPv6FibShortcut, page A-20 TestMPLSFibShortcut, page A-21 TestNATFibShortcut, page A-21 TestL3Capture2, page A-22 TestAclPermit, page A-22 TestAclDeny, page A-23 TestQoS, page A-23 TestNetflowShortcut, page A-24 TestAclFpgaMonitor, page A-24
TestFibDevices
The TestFibDevices test verifies that the FIB TCAM and adjacency devices are functional. One FIB entry is installed on each FIBTCAM device and a diagnostic packet is sent to make sure that the diagnostic packet is switched by the FIB TCAM entry installed on the TCAM device. This is not an exhaustive TCAM device test. Only one entry is installed on each TCAM device.
Note
Compared to the IPv4FibShortcut and IPv6FibShortcut tests, the TestFibDevices test tests all FIB and adjacency devices using IPv4 or IPv6 packets, depending on your configuration.
A-19
Table 0-33
TestFibDevices Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestIPv4FibShortcut
The TestIPv4FibShortcut test verifies that the IPv4 FIB forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic IPv4 FIB and adjacency entry is installed and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
Table 0-34 TestIPv4FibShortcut Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestIPv6FibShortcut
The TestIPv6FibShortcut test verifies that the IPv6 FIB forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic IPv6 FIB and adjacency entry is installed and a diagnostic IPv6 packet is sent to make sure that the diagnostic packet is forwarded according to rewritten MAC and VLAN information.
A-20
OL-3999-08
Appendix A
Table 0-35
TestIPv6FibShortcut Test Attributes
Attribute
TestMPLSFibShortcut
The TestMPLSFibShortcut test verifies that the MPLS forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic MPLS FIB and adjacency entry is installed and a diagnostic MPLS packet is sent to make sure that the diagnostic packet is forwarded using the MPLS label from the adjacency entry.
Table 0-36 TestMPLSFibShortcut Test Attributes
Attribute
TestNATFibShortcut
The TestNATFibShortcut test verifies the ability to rewrite a packet based on NAT adjacency information, such as the rewrite destination IP address. One diagnostic NAT FIB and adjacency entry is installed and a diagnostic packet is sent to make sure the diagnostic packet is forwarded according to the rewritten IP address.
A-21
Table 0-37
TestNATFibShortcut Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). This test runs by default during bootup or after a reset or OIR. Off. 12.1(13)E, 12.2(14)SX None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestL3Capture2
The TestL3Capture2 test verifies that the Layer 3 capture (capture 2) feature of the Layer 3 forwarding engine is working properly. This capture feature is used for ACL logging and VACL logging. One diagnostic FIB and adjacency entry with a capture 2-bit set is installed, and a diagnostic packet is sent to make sure that the diagnostic packet is forwarded according to capture bit information.
Table 0-38 TestL3Capture2 Test Attributes
Attribute
TestAclPermit
The TestAclPermit test verifies that the ACL permit functionality is working properly. An ACL entry permitting a specific diagnostics packet is installed in the ACL TCAM. The corresponding diagnostic packet is sent from the supervisor engine and is looked up by the Layer 3 forwarding engine to make sure it hits the ACL TCAM entry and gets permitted and forwarded correctly.
A-22
OL-3999-08
Appendix A
Table 0-39
TestACLPermit Test Attributes
Attribute
TestAclDeny
The TestAclDeny test verifies that the ACL deny feature of the Layer 2 and Layer 3 forwarding engine is working properly. The test uses different ACL deny scenarios such as input and output Layer 2 redirect, Layer 3 redirect, and Layer 3 bridges.
Table 0-40 TestACLDeny Test Attributes
Attribute
Description Disruptive for looped-back ports. Disruption is typically less than one second. Duration of the disruption depends on the configuration of the looped-back port (for example, Spanning Tree Protocol). Schedule during downtime if you are using ACLs. Off. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestQoS
The TestQoS test verifies whether or not the QoS input and output TCAM is functional by programming the QoS input and output TCAM so that the ToS value of the diagnostic packet is changed to reflect either input or output.
Table 0-41 TestQoS Test Attributes
Description Disruptive for looped-back ports. The disruption is typically less than one second.
A-23
Table 0-41
TestQoS Test Attributes (continued)
Schedule during downtime. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestNetflowShortcut
The TestNetFlowShortcut test verifies that the NetFlow forwarding functionality of the Layer 3 forwarding engine is working properly. One diagnostic NetFlow entry and adjacency entry is installed and a diagnostic packet is sent to make sure it is forwarded according to the rewritten MAC and VLAN information.
Table 0-42 TestNetflowShortcut Test Attributes
Description Disruptive for looped-back ports. Disruption is typically less than one second. Run this test on-demand if you suspect that NetFlow is not working properly. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and DFC-enabled modules.
TestAclFpgaMonitor
The TestAclFpgaMonitor test monitors the ACL FPGA for an invalid ACL TCAM reply status in the following linecards: WS-X6704-10GE, WS-X6724-SFP, WS-X6748-SFP, WS-X6748-GE-TX and takes recovery action if an invalid reply is detected.
Table A-43 TestAclFpgaMonitor Test Attributes
Description NonDisruptive. Do not disable. On. 12.2(18)SXF17a, 12.2(33)SXI4.
A-24
OL-3999-08
Appendix A
Online Diagnostic Tests Replication Engine Tests
Table A-43
TestAclFpgaMonitor Test Attributes (continued)
Attribute Corrective action Hardware support
Description Reset the linecard and optionally admin-down all the ports on the linecard. DFC-equipped WS-X6748-GE-TX, WS-X6704-10GE, WS-X6724-SFP, WS-X6748-SFP modules with WS-F6700-DFC3B or WS-F6700-DFC3BXL DFC.
Replication Engine Tests

The Replication Engine tests consists of the following tests: TestL3VlanMet, page A-25 TestIngressSpan, page A-25 TestEgressSpan, page A-26
TestL3VlanMet
The TestL3VlanMet test verifies that the multicast functionality of the replication engine is working properly. The replication engine is configured to perform multicast replication of a diagnostic packet onto two different VLANs. After the diagnostic packet is sent out from the supervisor engines inband port, the test verifies that two packets are received back in the inband port on the two VLANs configured in the replication engine.
Table 1-44 TestL3VlanMet Test Attributes
Description Disruptive for DFC-equipped modules. Disruption is typically less than one second on looped-back ports. Run this test on-demand to test the multicast replication abilities of the replication engine. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and WS-65xx, WS-67xx, and WS-68xx modules.
TestIngressSpan
The TestIngressSpan test ensures that the port ASIC is able to tag packets for ingress SPAN. This test also verifies that the ingress SPAN operation of the rewrite engine for both SPAN queues is working properly.
A-25
Appendix A Fabric Tests
Table 1-45
TestIngressSpan Test Attributes
Attribute
Description Disruptive for both SPAN sessions. Also disruptive for the loopback port on modules. Duration of the disruption depends on the configuration of the loopback port (for example, Spanning Tree Protocol). Run this test on-demand. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and WS-65xx and WS-67xx modules.
TestEgressSpan
The TestEgressSpan test verifies that the egress SPAN replication functionality of the rewrite engine for both SPAN queues is working properly.
Table 1-46 TestEgressSpan Test Attributes
Description Disruptive for both SPAN sessions. Disruption is typically less than one second. Run this test on-demand. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. Supervisor engines and WS-65xx and WS-67xx modules.
Fabric Tests
The Fabric tests consists of the following tests: TestFabricSnakeForward, page A-27 TestFabricSnakeBackward, page A-27 TestSynchedFabChannel, page A-28 TestFabricCh0Health, page A-28 TestFabricCh1Health, page A-28
A-26
OL-3999-08
Appendix A
Online Diagnostic Tests Fabric Tests
TestFabricSnakeForward
The TestFabricSnakeForward test consists of two test cases: the internal snake test and the external snake test. The internal snake test generates the test packets inside the fabric ASIC and the test data path is limited so that it stays inside the fabric ASIC. The external snake test generates the test packet using the supervisor engine inband port; the test data path involves the port ASIC, the rewrite engine ASIC inside the supervisor engine, and the fabric ASIC. Whether or not the supervisor engine local channel is synchronized to the fabric ASIC determines which test is used. If it is synchronized, the external snake test is used; if it is not, the internal snake test is used. For both tests, only the channels that are not synchronized to any modules are involved in the test. The Forward direction indicates that the snaking direction is from the low-numbered channel to the high-numbered channel.
Table 1-47 TestFabricSnakeForward Test Attributes
Description Nondisruptive. Run on-demand. This test can result in high CPU utilization. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. Supervisor engines crash to ROMMON; SFMs reset. Supervisor Engine 720 and SFM.
TestFabricSnakeBackward
The TestFabricSnakeBackward test consists of two test cases: the internal snake test and the external snake test. The internal snake test generates the test packets inside the fabric ASIC, and the test data path is limited so that it stays inside the fabric ASIC. The external snake test generates the test packet using the supervisor engine inband port and the test data path involves the port ASIC, the rewrite engine ASIC inside the supervisor engine, and the fabric ASIC. Whether or not the supervisor engine local channel is synchronized to the fabric ASIC determines which test is used. If it is synchronized, the external snake test is used; if it is not, internal snake test is used. For both tests, only the channels that are not synchronized to any modules are involved in the test. The backward direction indicates that the snaking direction is from the high-numbered channel to the low-numbered channel.
Table 1-48 TestFabricSnakeBackward Test Attributes
Description Nondisruptive. Run on-demand. This test can result in high CPU utilization. This test runs by default during bootup or after a reset or OIR. 12.1(13)E, 12.2(14)SX. Supervisor engines crash to ROMMON; SFMs reset. Supervisor Engine 720 and SFM.
A-27
Appendix A Fabric Tests
TestSynchedFabChannel
The TestSynchedFabChannel test periodically checks the fabric synchronization status for both the module and the fabric. This test is available only for fabric-enabled modules. This test is not a packet-switching test so it does not involve the data path. This test sends an SCP control message to the module and fabric to query the synchronization status.
Table 1-49 TestSynchedFabChannel Test Attributes
Description Nondisruptive. Do not turn this test off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. The module resets after five consecutive failures. Three consecutive reset cycles results in the module powering down. A fabric switchover may be triggered, depending on the type of failure. All fabric-enabled modules.
TestFabricCh0Health
The TestFabricCh0Health test constantly monitors the health of the ingress and egress data paths for fabric channel 0 on 10-gigabit modules. The test runs every five seconds. Ten consecutive failures are treated as fatal and the module resets; three consecutive reset cycles may result in a fabric switchover.
Table 1-50 TestFabricSCh0Health Test Attributes
Description Nondisruptive. Do not turn this test off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. The module resets after 10 consecutive failures. Three consecutive resets powers down the module. WS-X6704-10GE and WS-6702-10GE.
TestFabricCh1Health
The TestFabricCh1Health test constantly monitors the health of the ingress and egress data paths for fabric channel 1 on 10-gigabit modules. The test runs every five seconds. Ten consecutive failures are treated as fatal and the module resets; three consecutive reset cycles may result in a fabric switchover.
A-28
OL-3999-08
Appendix A
Online Diagnostic Tests Exhaustive Memory Tests
Table 1-51
TestFabricCh1Health Test Attributes
Description Nondisruptive. Do not turn this test off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. The module resets after 10 consecutive failures. Three consecutive failures resets powers down the module. WS-X6704-10GE module.
Exhaustive Memory Tests

The exhaustive memory tests include the following tests: TestFibTcamSSRAM, page A-29 TestAsicMemory, page A-30 TestAclQosTcam, page A-30 TestNetflowTcam, page A-31 TestQoSTcam, page A-31
Note
Because the supervisor engine must be rebooted after running memory tests, run memory tests on the other modules before running them on the supervisor engine. For more information about running on-demand online diagnostic tests see the Configuring On-Demand Online Diagnostics section on page 55-3.
TestFibTcamSSRAM
The TestFibTcamSSRAM test checks the FIB TCAM and Layer 3 Adjacency SSRAM memory.
Table 1-52 TestFibTcamSSRAM Test Attributes
Description Disruptive. Disruption is several hours. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.1(20)E, 12.2(14)SX, 12.2(17a)SX.
Recommendation Default Release
A-29
Appendix A Exhaustive Memory Tests
Table 1-52
TestFibTcamSSRAM Test Attributes (continued)
Not applicable. All modules including supervisor engines.
TestAsicMemory
The TestAsicMemory test uses an algorithm to test the memory on a module.
Table 1-53 TestAsicMemory Test Attributes
Description Disruptive. Disruption is approximately one hour. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(17a)SX. Not applicable. All modules including supervisor engines.
TestAclQosTcam
The TestAclQosTcam test tests all the bits and checks the location of both ACL and QOS TCAMs on the PFC3BXL and PFC3B. It is not supported on the PFC3A.
Table 1-54 TestAclQosTcam Test Attributes
Description Disruptive. Disruption is approximately one hour. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(18)SXD. Not applicable. All modules including supervisor engines.
A-30
OL-3999-08
Appendix A
Online Diagnostic Tests Exhaustive Memory Tests
TestNetflowTcam
The TestNetflowTcam test tests all the bits and checks the location of the Netflow TCAM.
Table 1-55 TestNetflowTcam Test Attributes
Attribute
Description Disruptive. Disruption is several minutes and can vary depending on whether you are testing the PFC3A, PFC3BXL, or PFC3B. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(18)SXD. Not applicable. All modules including supervisor engines.
TestQoSTcam
The TestQoSTcam test performs exhaustive memory tests for QoS TCAM devices.
Table 1-56 TestQoSTcam Test Attributes
Attribute
Description Disruptive. Disruption is several minutes and can vary depending on whether you are testing the PFC3A, PFC3BXL, or PFC3B. Use this test only if you suspect a problem with the hardware or before putting the hardware into a live network. Do not run any traffic in the background on the module that you are testing. The supervisor engine must be rebooted after running this test. Off. 12.2(18)SXD. Not applicable. All modules including supervisor engines.
A-31
Appendix A IPSEC Services Modules Tests
IPSEC Services Modules Tests

The IPSEC Services Modules Tests include the following tests: TestIPSecClearPkt, page A-32 TestHapiEchoPkt, page A-32 TestIPSecEncryptDecryptPkt, page A-33
TestIPSecClearPkt
The TestIPSecClearPkt test sends a packet through the switch fabric or bus from the supervisor engine inband port through to the crypto engine. The packet is sent back without encryption from the crypto engine to the supervisor engine in-band port. The packet is checked to verify that the encryption is not done and that the packet data fields are reserved. The Layer 2 lookup drives the packet between the supervisor in-band port and the crypto engine.
Table 1-57 TestIPSecClearPkt Test Attributes
Description Nondisruptive. Run this test on-demand. This test runs by default during bootup or after a reset or OIR. 12.2(18)SXE2.2. None. See the system message guide for more information. VPN service module.
TestHapiEchoPkt
The TestHapiEchoPkt test sends a Hapi Echo packet to the crypto engine using the control path. After the Hapi Echo packet is sent to the crypto engine, it is echoed back from the crypto engine. The packet is sent from the supervisor engine inband port to the crypto engine using index-direct and is sent back using broadcast to a diagnostic VLAN.
Table 1-58 TestHapiEchoPkt Test Attributes
Description Disruptive. Run this test on-demand. This test cannot be run from on-demand CLI. On. 12.2(18)SXE2. None. See the system message guide for more information. VPN service module.
A-32
OL-3999-08
Appendix A
Online Diagnostic Tests Stress Tests
TestIPSecEncryptDecryptPkt
The TestIPSecEncryptDecryptPkt test checks the encryption functionality by exchanging a packet between the supervisor engine in-band port and the crypto engine of the IPSec services modules (WS-SVC-IPSEC, SPA-IPSEC) using the switch fabric or bus (whichever is applicable). After several exchanges, the packet is checked to verify that the original data is preserved after the encryption and decryption process performed by the crypto engine. The Layer 2 lookup drives the packet between the supervisor in-band port and the crypto engine.
Table 1-59 TestIPSecEncryptDecryptPkt Test Attributes
Description Nondisruptive. Test runs every minute by default. This test can only be run at bootup. This test runs by default during bootup or after a reset or OIR. 12.2(18)SXE2.2. None. See the system message guide for more information. VPN services module.
Stress Tests
The stress tests consist of the following tests: TestTrafficStress, page A-33 TestEobcStressPing, page A-34
TestTrafficStress
The TestTrafficStress test stress tests the switch and the installed modules by configuring all of the ports on the modules into pairs, which then pass packets between each other. After allowing the packets to pass through the switch for a predetermined period, the test verifies that the packets are not dropped.
Table 1-60 TestTrafficStress Test Attributes
Description Disruptive. Disruption is several minutes. Use this test to qualify hardware before installing it in your network. Off. 12.2(18)SXF. Not applicable. Supervisor Engine 720 and Supervisor Engine 32.
A-33
Appendix A Critical Recovery Tests
TestEobcStressPing
The TestEobcStressPing test stress tests a modules EOBC link with the supervisor engine. The test is started when the supervisor engine initiates a number of sweep-ping processes (the default is one). The sweep-ping process pings the module with 20,000 SCP-ping packets. The test passes if all 20,000 packets respond before each packet-ping timeout, which is two seconds. If unsuccessful, the test allows five retries to account for traffic bursts on the EOBC bus during the test.
Table 1-61 TestEobcStressPing Test Attributes
Description Disruptive. Disruption is several minutes. Use this test to qualify hardware before installing it in your network. Off. 12.2(18)SXD. Not applicable. Supervisor Engine 720 and Supervisor Engine 32.
Critical Recovery Tests

The critical recovery tests consist of the following tests:

TestL3HealthMonitoring, page A-34 TestTxPathMonitoring, page A-35 TestSynchedFabChannel, page A-35
The TestFabricCh0Health and TestFabricCh1Health tests are also considered critical recovery tests. See the Fabric Tests section on page A-26 for a description of these tests.
TestL3HealthMonitoring
The TestL3HealthMonitoring test triggers a set of diagnostic tests involving IPv4 and IPv6 packet switching on a local DFC whenever the system tries to self-recover from a detected hardware fault. The tests shut down the front panel port (usually port 1) for testing purposes. If the diagnostic tests are not passing, it is an indication that the hardware fault cannot be fixed and a self-recovery sequence will be applied again
Table 1-62 TestL3HealthMonitoring Test Attributes
Attribute
Description Disruptive. Disruption is typically less than one second. Duration of the disruption depends on the configuration of looped-back port (for example, Spanning Tree Protocol). Forwarding and port functions are disrupted during the test.
A-34
OL-3999-08
Appendix A
Online Diagnostic Tests Critical Recovery Tests
Table 1-62
TestL3HealthMonitoring Test Attributes (continued)
Do not disable. On. 12.2(14)SX. Not applicable. DFC-equipped modules
TestTxPathMonitoring
The TestTxPathMonitoring test sends index-directed packets periodically to each port on the Supervisor Engine 720 and WS-X67xx series modules to verify ASIC synchronization and correct any related problems. The test runs every two seconds.
Table 1-63 TestTxPathMonitoring Test Attributes
Description Nondisruptive. Do not change the default settings. On. 12.2(14)SX. Not applicable (self-recovering). Supervisor Engine 720 and WS-67xx series modules.
TestSynchedFabChannel
The TestSynchedFabChannel test periodically checks the fabric synchronization status for both the module and the fabric. This test is available only for fabric-enabled modules. This test is not a packet-switching test so it does not involve the data path. This test sends an SCP control message to the module and fabric to query the synchronization status.
Table 1-64 TestSynchedFabChannel Test Attributes
Description Nondisruptive. Do not turn off. Use as a health-monitoring test. On. 12.1(13)E, 12.2(14)SX. None. See the system message guide for more information. All fabric-enabled modules.
A-35
Appendix A General Tests
General Tests
The general tests consist of the following tests: ScheduleSwitchover, page A-36 TestFirmwareDiagStatus, page A-36
ScheduleSwitchover
The ScheduleSwitchover test allows you to trigger a switchover at any time using the online diagnostics scheduling capability.
Table 1-65 ScheduleSwitchover Test Attributes
Description Disruptive. Schedule this test during downtime to test the ability of the standby supervisor engine to take over after a switchover. Off. 12.2(17B)SXA None Supervisor engines only.
TestFirmwareDiagStatus
The TestFirmwareDiagStatus test displays the results of the power-on diagnostic tests run by the firmware during the module bootup.
Table 1-66 TestFirmwareDiagStatus Test Attributes
Description Nondisruptive. This test can only be run at bootup. This test runs by default during bootup or after a reset or OIR 12.2(18)SXD None. See the system message guide. All modules, including supervisor engines.
A-36
OL-3999-08
Appendix A
Online Diagnostic Tests General Tests
Tip
A-37
Appendix A General Tests
A-38
OL-3999-08
A P P E N D I X
Acronyms
Tip
Table B-1 defines the acronyms used in this publication.

Table B-1 List of Acronyms
Acronym AAL ACE ACL AFI Agport ALPS AMP APaRT ARP ATA ATM AV BDD BECN BGP BPDU BRF BSC
Expansion ATM adaptation layer access control entry access control list authority and format identifier aggregation port Airline Protocol Support Active Monitor Present Automated Packet Recognition and Translation Address Resolution Protocol Analog Telephone Adaptor Asynchronous Transfer Mode attribute value binary decision diagrams backward explicit congestion notification Border Gateway Protocol bridge protocol data unit bridge relay function Bisync
B-1
Appendix B
Acronyms
Table B-1
List of Acronyms (continued)
Acronym BSTUN BUS BVI CAM CAR CCA CDP CEF CHAP CIR CIST CLI CLNS CMNS COPS COPS-DS CoS CPLD CRC CRF CST CUDD DCC dCEF DDR DE DEC DFC DFI DFP DISL DLC DLSw DMP DNS DoD
Expansion Block Serial Tunnel broadcast and unknown server bridge-group virtual interface content-addressable memory committed access rate circuit card assembly Cisco Discovery Protocol Cisco Express Forwarding Challenge Handshake Authentication Protocol committed information rate Common and internal spanning tree command-line interface Connection-Less Network Service Connection-Mode Network Service Common Open Policy Server Common Open Policy Server Differentiated Services class of service Complex Programmable Logic Device cyclic redundancy check concentrator relay function Common Spanning Tree University of Colorado Decision Diagram Data Country Code distributed Cisco Express Forwarding dial-on-demand routing discard eligibility Digital Equipment Corporation Distributed Forwarding Card Domain-Specific Part Format Identifier Dynamic Feedback Protocol Dynamic Inter-Switch Link Data Link Control Data Link Switching data movement processor Domain Name System Department of Defense
B-2
OL-3999-08
Appendix B
Acronyms
Table B-1
Acronym DOS dot1q DRAM DRiP DSAP DSCP DSPU DTP DTR DXI EAP EARL EEPROM EHSA EIA ELAN EOBC EOF ESI FAT FECN FM FRU fsck FSM GARP GMRP GVRP HSRP ICC ICD ICMP IDB IDP IDSM IFS
Expansion denial of service 802.1Q dynamic RAM Dual Ring Protocol destination service access point differentiated services code point downstream SNA Physical Units Dynamic Trunking Protocol data terminal ready data exchange interface Extensible Authentication Protocol Enhanced Address Recognition Logic electrically erasable programmable read-only memory enhanced high system availability Electronic Industries Association Emulated Local Area Network Ethernet out-of-band channel end of file end-system identifier File Allocation Table forward explicit congestion notification feature manager field replaceable unit file system consistency check feasible successor metrics General Attribute Registration Protocol GARP Multicast Registration Protocol GARP VLAN Registration Protocol Hot Standby Routing Protocol Inter-card Communication International Code Designator Internet Control Message Protocol interface descriptor block initial domain part or Internet Datagram Protocol Intrusion Detection System Module IOS File System
B-3
Appendix B
Acronyms
Table B-1
Acronym IGMP IGRP ILMI IP IPC IPX IS-IS ISL ISO ISR IST LAN LANE LAPB LCP LDA LEC LECS LEM LER LES LLC LTL MAC MD5 MFD MSFC MIB MII MLS MLSE MOP MOTD MLSE MRM
Expansion Internet Group Management Protocol Interior Gateway Routing Protocol Integrated Local Management Interface Internet Protocol interprocessor communication Internetwork Packet Exchange Intermediate System-to-Intermediate System Intradomain Routing Protocol Inter-Switch Link International Organization of Standardization Integrated SONET router Internal spanning tree local area network LAN Emulation Link Access Procedure, Balanced Link Control Protocol Local Director Acceleration LAN Emulation Client LAN Emulation Configuration Server link error monitor link error rate LAN Emulation Server Logical Link Control Local Target Logic Media Access Control Message Digest 5 multicast fast drop Multilayer Switch Feature Card Management Information Base media-independent interface Multilayer Switching maintenance loop signaling entity Maintenance Operation Protocol message-of-the-day maintenance loops signaling entity multicast routing monitor
B-4
OL-3999-08
Appendix B
Acronyms
Table B-1
Acronym MSDP MSFC MSM MST MTU MVAP NAM NBP NCIA NDE NET NetBIOS NFFC NMP NSAP NSF NTP NVRAM OAM ODM OSI OSM OSPF PAE PAgP PBD PC PCM PCR PDP PDU PEP PFC PGM PHY PIB
Expansion Multicast Source Discovery Protocol Multilayer Switching Feature Card Multilayer Switch Module multiple spanning tree maximum transmission unit multiple VLAN access port Network Analysis Module Name Binding Protocol Native Client Interface Architecture NetFlow Data Export network entity title Network Basic Input/Output System NetFlow Feature Card Network Management Processor network service access point Nonstop Forwarding Network Time Protocol nonvolatile RAM Operation, Administration, and Maintenance order dependent merge Open System Interconnection Optical Services Module open shortest path first port access entity Port Aggregation Protocol packet buffer daughterboard Personal Computer (formerly PCMCIA) pulse code modulation peak cell rate policy decision point protocol data unit policy enforcement point Policy Feature Card Pragmatic General Multicast physical sublayer policy information base
B-5
Appendix B
Acronyms
Table B-1
Acronym PIM PPP PRID PVST+ QDM QM QoS RACL RADIUS RAM RCP RGMP RIB RIF RMON ROM ROMMON RP RPC RPF RPR RPR+ RSPAN RST RSVP SAID SAP SCM SCP SDLC SGBP SIMM SLB SLCP SLIP SMDS
Expansion protocol independent multicast Point-to-Point Protocol Policy Rule Identifiers Per VLAN Spanning Tree+ QoS device manager QoS manager quality of service router interface access control list Remote Access Dial-In User Service random-access memory Remote Copy Protocol Router-Ports Group Management Protocol routing information base Routing Information Field remote network monitor read-only memory ROM monitor route processor or rendezvous point remote procedure call reverse path forwarding route processor redundancy route processor redundancy plus remote SPAN reset ReSerVation Protocol Security Association Identifier service access point service connection manager Switch-Module Configuration Protocol Synchronous Data Link Control Stack Group Bidding Protocol single in-line memory module server load balancing Supervisor Line-Card Processor Serial Line Internet Protocol Software Management and Delivery Systems
B-6
OL-3999-08
Appendix B
Acronyms
Table B-1
Acronym SMF SMP SMRP SMT SNAP SNMP SRM SSO SPAN SREC SSTP STP SVC SVI TACACS+ TARP TCAM TCL TCP/IP TFTP TIA TopN TOS TLV TTL TVX UDLD UDP UNI UTC VACL VCC VCI VCR VINES VLAN
Expansion software MAC filter Standby Monitor Present Simple Multicast Routing Protocol Station Management Subnetwork Access Protocol Simple Network Management Protocol single router mode stateful switchover Switched Port Analyzer S-Record format, Motorola defined format for ROM contents Cisco Shared Spanning Tree Spanning Tree Protocol switched virtual circuit switched virtual interface Terminal Access Controller Access Control System Plus Target Identifier Address Resolution Protocol Ternary Content Addressable Memory table contention level Transmission Control Protocol/Internet Protocol Trivial File Transfer Protocol Telecommunications Industry Association Utility that allows the user to analyze port traffic by reports type of service type-length-value Time To Live valid transmission UniDirectional Link Detection Protocol User Datagram Protocol User-Network Interface Coordinated Universal Time VLAN access control list virtual channel circuit virtual circuit identifier Virtual Configuration Register Virtual Network System virtual LAN
B-7
Appendix B
Acronyms
Table B-1
Acronym VMPS VPN VRF VTP VVID WAN WCCP WFQ WRED WRR XNS
Expansion VLAN Membership Policy Server virtual private network VPN routing and forwarding VLAN Trunking Protocol voice VLAN ID wide area network Web Cache Communications Protocol weighted fair queueing weighted random early detection weighted round-robin Xerox Network System
Tip
B-8
OL-3999-08
I N D EX
Numerics
4K VLANs (support for 4,096 VLANs) 802.10 SAID (default) 802.1Q encapsulation
3 6 2
access port, configuring ACEs and ACLs acronyms, list of addresses IP, see IP addresses
1 1
14
MAC, see MAC addresses advertisements, VTP aggregate label

2, 4 3
Layer 2 protocol tunneling See Layer 2 protocol tunneling mapping to ISL VLANs trunks
3 5 13, 16
aggregate policing see QoS policing aging time accelerated
restrictions tunneling
configuration guidelines configuring tunnel ports overview

1
3 6
for MSTP maximum for MSTP aging-time
25
26
802.1Q Ethertype specifying custom 802.1s See MST 802.1w See MST 802.1X See port-based authentication 802.3ad See LACP 802.3x Flow Control
13 15
IP MLS alarms major minor

12 12
Allow DHCP Option 82 on Untrusted Port configuring understanding

10 3 13 16
any transport over MPLS (AToM) Ethernet over MPLS ARP ACL
70 1 16
compatibility with previous releases of AToM
A
AAA
1 5 1 2
ARP spoofing AToM audience

13 30
abbreviating commands
authentication See also port-based authentication Authentication, Authorization, and Accounting
access control entries and lists
access-enable host timeout (not supported)
IN-1
Index
See AAA Authentication, Authorization, and Accounting (AAA) authorized ports with 802.1X auto-sync command auxiliary VLAN See voice VLAN
6 4 1
C
cautions for passwords encrypting TACACS+ CDP configuration task lists
2 3 3 17 17
B
BackboneFast See STP BackboneFast backup interfaces See Flex Links binding database, DHCP snooping See DHCP snooping binding database binding table, DHCP snooping See DHCP snooping binding database blocking floods
1 8 26
enabling on an interface overview CEF

1 1 3
monitoring and maintaining cdp enable command configuring MSFC2 examples

5 5
supervisor engine
3 2
Layer 3 switching packet rewrite CEF for PFC2 See CEF CGMP
8 2
blocking state, STP boot command

22
boot bootldr command boot config command boot system command BPDU RSTP format BPDU guard See STP BPDU guard bridge groups bridge ID See STP bridge ID bridge priority, STP see BPDUs bridging
2 30 2 13
26 21, 26 22
channel-group group command checking configuration, system Cisco Discovery Protocol See CDP Cisco Emergency Responder Cisco Express Forwarding See CGMP Cisco IOS Unicast Reverse Path Forwarding CiscoView CIST
15 2 2 3 4 10 8, 12 9
boot system flash command
command example
Cisco Group Management Protocol
bridge protocol data units
broadcast storms see traffic-storm control
CIST regional root See MSTP CIST root See MSTP

OL-3999-08
IN-2
Index
class command
75 66 71 3
configuration
21 to 24 22
class-map command
settings at startup configuration example EoMPLS port mode
class map configuration clear cdp table command clear counters command clear interface command
clear cdp counters command

3 18 18
17, 20 17
EoMPLS VLAN mode listing value

27 24 23 9
configuration register boot field modification tasks configure command configuring

74
clear mls ip multicast statistics command clears IP MMLS statistics CLI accessing
2 5 5
configure terminal command global parameters procedure interfaces

5 3 5 5
23, 2
backing out one level
console configuration mode getting list of commands global configuration mode history substitution
4
sample configuration
8 to 9
3 to 8
using configuration mode console configuration mode control plane policing See CoPP CoPP
3 5 3 5
10 5
interface configuration mode privileged EXEC mode ROM monitor software basics
7 4
command line processing commands, getting list of
applying QoS service policy to control plane configuring ACLs to match traffic enabling MLS QoS service-policy map entering
30 30 30 30
30
Committed Access Rate (CAR), not supported Common and Internal Spanning Tree See also CIST See CST
15 3 2, 3 2 15
packet classification criteria

30
Common Spanning Tree community ports
control plane configuration mode displaying dynamic information rate information

23 10 31 30 31 31
community VLANs
Concurrent routing and bridging (CRB) CONFIG_FILE environment variable description

25
number of conforming bytes and packets entering control plane configuration mode monitoring statistics overview
28 31 31
config-register command config terminal command configuration file, saving interfaces register changing settings
23 11 8 to 10
packet classification guidelines traffic classification defining guidelines

32 34
IN-3
Index
overview
32 34 32 11
description command
16 3 3
sample ACLs sample classes copy system
destination-ip flow mask DHCP binding database
destination-source-ip flow mask
copy running-config startup-config command running-config nvram startup-config command CoS override priority counters clearing interface CSCsr62404 CSCtc21076 CSCte40004 CST
15 18 14 5 5 18 7, 8 26
See DHCP snooping binding database DHCP binding table See DHCP snooping binding database DHCP option 82 circuit ID suboption overview
3 5
packet format, suboption circuit ID remote ID

5 5 5 10
remote ID suboption DHCP snooping binding database
DHCP option 82 allow on untrusted port
common spanning tree
D
dCEF
4, 5
See DHCP snooping binding database configuration guidelines configuring

9 6 18 6
debug commands IP MMLS

27 2
default configuration enabling
displaying binding tables

9, 10, 11, 12, 13, 14
DEC spanning-tree protocol default configuration 802.1X

6 5
enabling the database agent message exchange process option 82 data insertion overview
1 5 3 4
14
dynamic ARP inspection Flex Links IP MMLS MSTP UDLD VTP

5 16 2 2 7
Snooping database agent described entries

5 2 2
DHCP snooping binding database
supervisor engine
3
voice VLAN
DHCP snooping binding table See DHCP snooping binding database

12 10
default gateway, configuring default NDE configuration default VLAN

10
DHCP Snooping Database Agent adding to the database (example) enabling (example)
15 18
deficit weighted round robin denial of service protection See DoS protection
109
overview
5 17 7, 15
reading from a TFTP file (example)
DHCP snooping increased bindings limit
IN-4
Index
differentiated services codepoint See QoS DSCP DiffServ configuring short pipe mode configuring uniform mode short pipe mode uniform mode
33 4 6 32 40 35
multicast FIB miss rate limiters network under SYN attack QoS ACLs
12 11 6, 13 13 16 13
20 10, 19
multicast IGMP snooping rate limiters
security ACLs TCP intercept
traffic storm control uRPF check

12
DiffServ tunneling modes
TTL failure rate limiter uRPF failure rate limiters VACL log rate limiters
Disabling PIM Snooping Designated Router Flooding distributed Cisco Express Forwarding See dCEF documentation, related DoS protection monitoring packet drop statistics using VACL capture Supervisor Engine 2 ARP throttling FIB rate limiting QoS ACLs
3 2 5 23 26 7 25 30
16 10, 18
Supervisor Engine 720Layer 3 security features rate limiters 9, 18 understanding how it works DSCP See QoS DSCP DSCP-based queue mapping duplex command duplex mode configuring interface DWRR
109 7 8, 9 100 2
using monitor session commands
configuration guidelines and restrictions

4
recommendations security ACLs

2
dynamic ARP inspection ARP cache poisoning

5 10 22 8, 15 2 2
traffic storm control Supervisor Engine 720 default configurations FIB glean rate limiters
ARP requests, described ARP spoofing attack clearing log buffer statistics configuring
17 8, 15 16 16 2
egress ACL bridget packet rate limiters

17 9, 17 18
FIB receive rate limiters
configuration guidelines log buffer

13, 14
ICMP redirect rate limiters
IGMP unreachable rate limiters IP errors rate limiters

10, 20
ingress ACL bridget packet rate limiters IPv4 multicast rate limiters IPv6 multicast rate limiters Layer 2 PDU rate limiters MTU failure rate limiters
10, 20 21 10, 19
logging system messages default configuration described

1 5
14 4, 9
rate limit for incoming ARP packets denial-of-service attacks, preventing DHCP snooping binding database displaying
20 3 9
Layer 2 protocol tunneling rate limiters

19
10, 19
multicast directyly connected rate limiters
ARP ACLs
15
IN-5
Index
configuration and operating state log buffer statistics

16 16 15
15
on router interfaces encapsulation

3
11
enhanced interface range command environmental monitoring

4
trust state and rate limit function of log buffer clearing displaying
16 13, 14 16 2 3
error-disabled state for exceeding rate limit interface trust states
LED indications SNMP traps

12
12
supervisor engine and switching modules Syslog messages

12 10
12
using CLI commands environment variables CONFIG_FILE

5 25
configuring
logging of dropped packets, described logging system messages configuring

14 2
controlling viewing EoMPLS

3 4 26 14
26
man-in-the middle attack, described
configuring
16 16 14
network security issues and interface trust states priority of ARP ACLs and DHCP snooping entries rate limiting of ARP packets configuring described statistics clearing displaying
16 16 11 4 4 9
configuring VLAN mode guidelines and restrictions port mode

16
port mode configuration guidelines VLAN mode

16
20
error-disabled state
erase startup-config command configuration files cleared with ERSPAN

1 14
EtherChannel channel-group group command

8, 12 9 5
validation checks, performing See DHCP snooping
Dynamic Host Configuration Protocol snooping
command example configuring Layer 2

15 62 14 8 7
configuration guidelines
E
Egress ACL support for remarked DSCP egress ACL support for remarked DSCP Embedded CiscoView enable command enable mode enabling IP MMLS
5 10 10, 23 2
configuring (tasks)
DFC restriction, see CSCdt27074 in the Release Notes interface port-channel command example lacp system-priority command example Layer 2 configuring
8 10 8 7
egress replication performance improvement
interface port-channel (command)
enable sticky secure MAC address
IN-6
Index
load balancing configuring understanding modes PAgP Understanding

3 5 3 11 5
fall-back bridging fastethernet FIB TCAM filters, NDE

2
fiber-optic, detecting unidirectional links

3
destination host filter, specifying protocol

18
17 17
port-channel interfaces command STP

5 10, 11 11
destination TCP/UDP port, specifying
port-channel load-balance command example
source host and destination TCP/UDP port Flash memory configuration process
6 25 25
17
switchport trunk encapsulation dot1q understanding

1
configuring router to boot from loading system image from security precautions write protection Flex Links
1 2 25 25 24
EtherChannel Guard See STP EtherChannel Guard EtherChannel Min-Links Ethernet setting port duplex EoMPLS port mode examples configuration interface
8 to 9 21 to 24 15 12
configuration guidelines configuring description

17 3 2
Ethernet over MPLS (EoMPLS) configuration

20
default configuration
1 4 1 13
EoMPLS VLAN mode
monitoring flood blocking flow control flow masks IP MLS

3
software configuration register configuring global parameters EXP mutation See VLANs extended system ID MSTP
19 4 2
destination-ip
3 3 3
destination-source-ip ip-full minimum

1 3 3
extended range VLANs
interface-destination-source-ip ip-interface-full
7 3
Extensible Authentication Protocol over LAN
overview flows IP MMLS
F
fabric switching mode See switch fabric module fabric switching-mode allow dcef-only command on Supervisor Engine 720 2
completely and partially switched forward-delay time MSTP

25 32
forward-delay time, STP frame distribution
IN-7
Index
See EtherChannel load balancing
See RSTP IEEE 802.3ad See LACP IEEE 802.3x Flow Control
13
G
gateway, configuring
12 1 5 3
IEEE bridging protocol IGMP
generic online diagnostics global configuration mode GOLD

1
configuration guidelines enabling

10
8, 7
global parameters, configuring
Internet Group Management Protocol join messages

2
H
hardware Layer 3 switching guidelines hello time MSTP
24 31 4 4
leave processing enabling queries

3 12
query interval configuring snooping fast leave

5 2 4 11
hello time, STP history CLI

4
High Capacity Power Supply Support
joining multicast group leaving multicast group understanding snooping querier enabling IGMPv3
10 10 11, 19, 58, 76 7 9 2 2
host ports kinds of http //www-tac.cisco.com/Teams/ks/c3/xmlkwery.php?srId= 612293409 6

3
understanding IGMP v3lite
ignore port trust
I
I-BPDU
16 1 6
IGRP, configuring interface command

10
Integrated routing and bridging (IRB)
ICMP unreachable messages IEEE 802.10 SAID (default) IEEE 802.1Q See 802.1Q IEEE 802.1Q Ethertype specifying custom IEEE 802.1s See MST IEEE 802.1w See MST
15
configuration Layer 2 modes number

2
8 to 9 5
configuration mode
4
parameters, configuring interface port-channel command example

8
8 3
interface-destination-source-ip flow mask
interface port-channel (command)
IN-8
Index
interfaces configuring
2 7
aging-time flow masks
configuring, duplex mode configuring, speed counters, clearing

7 2
destination-ip
3 3 3
destination-source-ip ip-full
16 17 3 3
configururing, overview
18
interface-destination-source-ip ip-interface-full minimum overview IP MMLS cache, overview

2 8 7 3
descriptive name, adding maintaining monitoring naming range of restarting task

19 2 16 4 19 17 17
displaying information about
configuration guideline debug commands enabling on router interfaces

4 6 27 7
shutting down interfaces command
11
interfaces range command
flows completely and partially switched Layer 3 MLS cache overview router enabling globally
10 11 21 2 3 2 4
interfaces range macro command Interior Gateway Routing Protocol See IGRP, configuring Internal Sub Tree Protocol See ISTP See IGMP IP default gateway, configuring static routes IP addresses assigned by BOOTP protocol set to default IP CEF topology (figure)
4 14 12 9 12 15
packet rewrite
Internet Group Management Protocol
enabling on interfaces PIM, enabling switch statistics, clearing unsupported features

14 27 9 10
multicast routing table, displaying
IP accounting, IP MMLS and
IP multicast IGMP snooping and MLDv2 snooping and overview

14 2 9 10
ip flow-export destination command ip flow-export source command ip-full flow mask ip http server IP MLS
1 3 3
IP multicast MLS See IP MMLS ip multicast-routing command enabling IP multicast IP phone configuring
6 10
12, 13, 15, 3, 4
ip-interface-full flow mask
IN-9
Index
ip pim command enabling IP PIM IPsec

2 2 5 11
understanding trunks understanding VLAN
IP unnumbered
IPv4 Multicast over Point-to-Point GRE Tunnels IPv4 Multicast VPN IPv6 QoS ISL trunks isolated port ISTP
15 53 3 1
interface assignment Layer 2 Interfaces

1
12
IPv6 Multicast PFC3 and DFC3 Layer 3 Switching ISL encapsulation

3 3 2, 3
configuring
Layer 2 protocol tunneling configuring Layer 2 tunnels overview

1 18 1 2
Layer 2 remarking Layer 2 Traceroute Layer 2 traceroute and ARP

2 2 1
isolated VLANs
J
join messages, IGMP jumbo frames
10 2
and CDP described
IP addresses and subnets multicast traffic

2
2 2
MAC addresses and VLANs multiple devices on a port

2
K
keyboard shortcuts
3
unicast traffic Layer 3
1 2
usage guidelines
IP MMLS and MLS cache
L
label edge router label switched path label switch router LACP system ID Layer 2 configuring interfaces access port trunk defaults
8 5 4 12, 13, 7, 12 14 6 4 2 16 2, 4
Layer 3 switched packet rewrite CEF CEF

2
Layer 3 switching
2 8
Layer 4 port operations (ACLs) leave processing, IGMP enabling enabling LERs
2, 6, 7 12
leave processing, MLDv2

13
Link Failure detecting unidirectional link negotiation link redundancy See Flex Links
interface modes show interfaces switching
OL-3999-08
IN-10
Index
Load Balancing load balancing
8 15 14
queries snooping
Local Egress Replication logical operation unit See LOU loop guard See STP loop guard LOU description LSRs
2, 7 8
fast leave
7 4 6
joining multicast group leaving multicast group understanding snooping querier enabling
8 9 2 1 2
understanding MLDv2 Snooping MLS
determining maximum number of
configuring threshold
15
M
MAC address adding to BOOTP configuration file MAC address-based blocking MAC move (port security) main-cpu command markdown see QoS markdown match protocol MSTP
26 32 26 53 6 13, 16 2 2 14
MSFC threshold
15
mls aging command configuring IP MLS mls flow command configuring IP MLS enabling IP MMLS mls nde flow command configuring a host and port filter configuring a host flow filter configuring a port filter mls nde sender command monitoring Flex Links MPLS
2 2 13 4 17 17 18 17 17 7, 9, 12 8
mls ip multicast command

12, 13, 14, 16, 17, 18, 23, 24
mapping 802.1Q VLANs to ISL VLANs
maximum aging time maximum aging time, STP maximum hop count, MSTP microflow policing rule see QoS policing Min-Links MLD report
4 12
configuring a protocol flow filter

11
private VLANs aggregate label
any transport over MPLS basic configuration core

12 4 8
MLD snooping query interval configuring MLDv2

1 10
DiffServ Tunneling Modes egress

4 3
32
enabling enabling
experimental field ingress

3
leave processing
13
guidelines and restrictions
IN-11
Index
IP to MPLS path labels

2
configuration configuring
8
18 33
Layer 2 VPN load balancing MPLS to IP path nonaggregate lable VPN

12 4 4 2 15
edge ports enabling hop count instances
20 34 20 18 16 16
MPLS to MPLS path
QoS default configuration
interoperability
11 16
interoperability with PVST+ link type master regions

2 20 20 20
VPN guidelines and restrictions mpls l2 transport route command MPLS QoS Classification Class of Service commands
16 20 23 2
message age
18, 19
MSTP boundary ports configuration guidelines described

29 31 2 6 3 4 16
configuring a class map configuring a policy map
configuring egress EXP mutation configuring EXP Value Maps displaying a policy map E-LSP EXP bits features QoS Tags
3 2 2 18 28
CIST, described CIST root configuring

5
CIST regional root
Differentiated Services Code Point
configuration guidelines forward-delay time hello time

24 25
16
enabling QoS globally

2
link type for rapid convergence maximum aging time maximum hop count
19 26 26 2
26
IP Precedence
queueing-only mode
MST region neighbor type

20
17 27
MPLS QoS configuration class map to classify MPLS packets MPLS VPN limitations and restrictions MQC
1 11
path cost root switch
22 21 19 20
port priority
secondary root switch switch priority CST

3 23 3
not supported CAR queuing supported policy maps MST

15 19 3
defined
3 4
operations between regions default configuration displaying status enabling the mode
28 17 16
boundary ports
IN-12
Index
extended system ID effects on root switch unexpected behavior IEEE 802.1s implementation terminology described IST defined master
3 4 4 17 9 28 5 7 7 19 20
RGMP
2 21
multicast, displaying routing table
effects on secondary root switch

19
Multicast enhancement - egress replication performance improvement 14 Multicast Enhancement - Replication Mode Detection multicast flood blocking multicast groups joining leaving joining
2 6, 4 1 12
port role naming change
interoperability with IEEE 802.1D restarting migration process
multicast groups, IPv6

4
Multicast Listener Discovery version 2 See MLDv2 multicast multilayer switching See IPv4 MMLS Multicast Replication Mode Detection enhancement multicast RPF multicast storms see traffic-storm control
17 2 6 2 12
operations within a region M-record CIST

3 16
mapping VLANs to MST instance MST region configuring described IST M-tree overview root switch configuring
19 19 3
Multilayer MAC ACL QoS Filtering multilayer switch feature card see MSFC multiple forwarding paths
3 15 2
67
hop-count mechanism
supported spanning-tree instances

16 1
multiple path RPF check Multiple Spanning Tree See MST
Multiple Spanning Tree Protocol See MSTP

15
effects of extended system ID unexpected behavior status, displaying MTU size (default) multicast IGMP snooping and MLDv2 snooping and NetFlow statistics non-RPF overview
5 2 4 10 9 10 28 6 19
N
NAC non-responsive hosts native VLAN NBAR NDE configuration, displaying displaying configuration enabling
10 18 18 1, 53 10 5
PIM snooping
IN-13
Index
filters destination host, specifying protocol, specifying

18 17 17
configuring memory tests overview

1
2 10
destination TCP/UDP port, specifying
running tests understanding
5 1 1 1
source host and destination TCP/UDP port, specifying 17 multicast specifying destination host filters protocol filters NDE version 8
3 14 18 10 17 17 10
test descriptions
online diagnostic tests See OIR operating system image See system image out of profile see QoS out of profile
3
online insertion and removal
destination TCP/UDP port filters NDE configuration, default
Netflow Multiple Export Destinations NetFlow version 9 See NAC Network Admission Control (NAC) network fault tolerance network management configuring
1 2, 4 5 15 1
Network Admission Control
P
packet burst
1 16 15
packet recirculation packet rewrite CEF packets multicast PAgP understanding passwords configuring enable password enable secret line password
1 15 3 4 2 3
Network-Based Application Recognition
IP MMLS and
nonaggregate label non-RPF multicast Nonstop Forwarding See NSF
nonvolatile random-access memory See NVRAM normal-range VLANs See VLANs NSF
1
15
16 15
static enable password TACACS+ encrypting (caution)

17 17 16
NSF with SSO does not support IPv6 multicast traffic. NVRAM saving settings
11
TACACS+ (caution)
17
O
OIR
16
recovering lost enable passwords path cost MSTP PBR

4 22
19
online diagnostics
IN-14
Index
PFC2 NetFlow table, displaying entries PFC3BXL hardware features

5 7 6
manual reauthentication of a client quiet period

12 10
11
RADIUS server
RADIUS server parameters on the switch
MPLS guidelines and restrictions MPLS label switching recirculation

4 5 1 7
switch-to-authentication-server retransmission time 14 switch-to-client EAP-request frame retransmission time 13 switch-to-client frame-retransmission number switch-to-client retransmission time default configuration described device roles
1 2 16 3 3 3 6 12 14
MPLS supported commands supported Cisco IOS features VPN supported commands VPN switching PIM snooping designated router flooding enabling globally overview
4 5 5 6 10 10
11
PIM, IP MMLS and
displaying statistics EAPOL-start frame
EAP-request/identity frame EAP-response/identity frame enabling 802.1X authentication

4 7, 9
enabling in a VLAN
platform ipv4 pbr optimize tcam command police command policing See QoS policing policy
66 78
periodic reauthentication encapsulation method lists ports

7 3
10
initiation and message exchange
policy-based routing See PBR policy enforcement policy map

74 81 6
authorization state and dot1x port-control command 4 authorized and unauthorized resetting to default values switch as proxy
2 2 5 67, 75 15 4
attaching to an interface policy-map command see PAgP port-based authentication authentication server defined
2 3, 2
Port Aggregation Protocol
RADIUS client
topologies, supported port-based QoS features see QoS port channel
RADIUS server client, defined configuring

2
switchport trunk encapsulation dot1q port-channel

6
see EtherChannel port-channel load-balance

11
initializing authentication of a client
command
10, 11
IN-15
Index
command example port cost, STP disabling displaying enabling PortFast See STP PortFast
15 15 15 28
10, 11
private VLANs and SVIs benefits of

6 2
1 5
across multiple switches
port debounce timer
community VLANs configuring host ports

11 14
2, 3 7, 9, 11
PortFast BPDU filtering See STP PortFast BPDU filtering port mode port priority MSTP ports setting the debounce timer port security aging
12, 13 4 3 15 21 26 16 8
pomiscuous ports
15 13 12
routing secondary VLAN ingress traffic secondary VLANs with primary VLANs VLANs as private end station access to IP addressing monitoring ports community isolated
3 3 2 2 3 9 17 4 2, 3 11 4
port negotiation
port priority, STP
isolated VLANs
configuration guidelines promiscuous primary VLANs secondary VLANs

10
configuring described displaying

2
13
enable sticky secure MAC address sticky MAC address violations

2 3
subdomains traffic in
6
privileged EXEC mode

3, 4, 5, 9, 11
Port Security is supported on trunks port security MAC move

2 3
privileges changing default configuring

3 18
port security on PVLAN ports power management
Port Security with Sticky Secure MAC Addresses enabling/disabling redundancy overview
1 4 5 2
multiple levels privilege level exiting procedures

19 18
17 18
logging in
powering modules up or down primary links priority overriding CoS

7, 8 1 2
system power requirements, nine-slot chassis primary VLANs
global parameters, configuring interfaces, configuring promiscuous ports protocol tunneling

3 8 to 9 10
3 to 8
using configuration mode
IN-16
Index
See Layer 2 protocol tunneling pruning, VTP See VTP, pruning PVLANs See private VLANs PVRST See Rapid-PVST
14
QoS labels (definition) QoS mapping
124
CoS values to DSCP values DSCP markdown values DSCP mutation

83, 30
85, 88
30, 89, 16
DSCP values to CoS values QoS markdown

23
90 88
IP precedence values to DSCP values QoS marking definition

124 17 17
Q
QoS IPv6
53 123
trusted ports untrusted ports QoS MSFC marking

20
QoS classification (definition) QoS congestion avoidance definition QoS CoS

123
QoS multilayer switch feature card QoS OSM egress port

14 14
20
and ToS final L3 Switching Engine values definition

123 93 113, 2
feature summary QoS out of profile QoS policing definition

124
16 23
and ToS final values from L3 Switching Engine port value, configuring QoS default configuration QoS DSCP definition
123 12 87
microflow, enabling for nonrouted traffic QoS policing rule aggregate creating microflow QoS port trust state
91 61 20 65 20
60
internal values
maps, configuring thresholds configuring scheduling

113
QoS dual transmit queue

93, 98
QoS port-based or VLAN-based QoS queues
QoS Ethernet egress port scheduling, congestion avoidance, and marking QoS Ethernet ingress port classification, marking, scheduling, and congestion avoidance 8 QoS final L3 Switching Engine CoS and ToS values QoS internal DSCP values QoS L3 Switching Engine classification, marking, and policing feature summary
19 11 12 14 14, 16
transmit, allocating bandwidth between QoS receive queue drop thresholds

10, 104, 107 25 124
109
QoS scheduling (definition) configuring configuring

99 1
QoS single-receive, dual-transmit queue ports QoS statistics data export

2 8
configuring destination host configuring time interval

7, 9
IN-17
Index
QoS ToS and CoS final values from L3 Switching Engine definition
123 4 14
BGP CEF IS-IS OSPF

26, 101, 103, 105, 106
14 13 19 16 15 13
EIGRP
QoS traffic flow through QoS features QoS transmit queue size ratio QoS trust-cos port keyword QoS trust-dscp port keyword QoS trust-ipprec port keyword
17, 18 17, 18 13, 61 17, 18 17, 19 111, 112
configuring multicast NSF with SSO configuring supervisor engine routing protocols redundancy (RPR+) configuring
6 5 4 1 10
QoS transmit queues
configuring supervisor engine redundancy command redundancy (SSO) redundancy command

12 30 6
displaying supervisor engine configuration route processor redundancy plus

3
QoS untrusted port keyword queries, IGMP queries, MLDv2

3 5
QoS VLAN-based or port-based
related documentation reload command

23
R
range command macro
6 4 11 4
Remote source-route bridging (RSRB) Replication Mode Detection report, MLD See VLANs rewrite, packet CEF RGMP
2 3 4 12
reserved-range VLANs
of interfaces Rapid-PVST enabling overview See RSTP See RSTP

33 14
rapid convergence
IP MMLS
1
overview
2 2 17
Rapid Spanning Tree

13
packet types
RIF cache monitoring rommon command ROM monitor

15 24
Rapid Spanning Tree Protocol rapid spanning tree protocol receive queues see QoS receive queues recirculation
4, 15 2
boot process and CLI

7 24
20
root bridge, STP root guard
reduced MAC address redundancy (NSF) configuring

1
See STP root guard root switch MSTP

19
IN-18
Index
route processor redundancy See redundancy (RPR+) router-port group management protocol See RGMP routing table, multicast RPF failure
5 2 5 21
S
SAID
6 2 to 10
sample configuration Sampled NetFlow description scheduling see QoS secondary VLANs security
1 2 8
saving the configuration file
11
multicast unicast RPR+

2
non-RPF multicast
Secure MAC Address Aging Type configuring security, port

10 1 2
12
See redundancy (RPR+) RPR and RPR+ support IPv6 multicast traffic RSTP
15
active topology BPDU format

13 14
security precautions with Flash memory card serial interfaces clearing

18
25
processing
synchronous
10 10
designated port, defined designated switch, defined described

9
maintaining
18 67 62, 81, 84, 87, 30 2 2
service-policy command
interoperability with IEEE 802.1D restarting migration process topology changes overview port roles described port states
9 13 10 12 15 28
service-policy input command
service-provider network, MSTP and RSTP setup command short pipe mode configuring
35 26 2 109
set power redundancy enable/disable command shaped round robin
synchronized
14
show boot command show cdp command
show catalyst6000 chassis-mac-address command

11 2, 3 3 3 3
proposal-agreement handshake process rapid convergence described

11 11
show cdp entry command
show cdp interface command show cdp neighbors command show cdp traffic command
3
edge ports and Port Fast point-to-point links root ports

11 10
11, 26
show ciscoview package command show ciscoview version command show configuration command show debugging command show eobc command
17 3 16
3 3
root port, defined See also MSTP
IN-19
Index
show hardware command show history command show ibc command

17 4
shutdown interfaces result

19
Single Spanning Tree

2, 12, 13, 16, 17, 7, 12 18 2 9
show interfaces command
See SST SNMP
15 2
clearing interface counters
slot number, description
displaying, interface type numbers displaying, speed and duplex mode show ip flow export command
support and documentation snooping See IGMP snooping See MLDv2 snooping
displaying NDE export flow IP address and UDP port 15 show ip interface command displaying IP MMLS interfaces show ip mroute command displaying IP multicast routing table show ip pim interface command displaying IP MMLS router configuration show mls aging command show mls entry command
9 6 19 21 19
software configuration register functions source-only-ip flow mask

3
21 to 24
source specific multicast with IGMPv3, IGMP v3lite, and URD 10 SPAN configuration guidelines configuring sources
14 15, 17, 18, 19, 22 24 6
show mls ip multicast group command displaying IP MMLS group

22, 25
VLAN filtering overview

1
show mls ip multicast interface command displaying IP MMLS interface displaying IP MMLS source displaying IP MMLS statistics show mls ip multicast summary displaying IP MMLS configuration show mls nde command show mls rp command displaying IP MLS configuration show module command show protocols command show rif command
17 10, 16, 17 11 7 17 8 18 15 22, 25 22, 25
SPAN Destination Port Permit Lists spanning-tree backbonefast command

13, 14 14
14
show mls ip multicast source command

22, 25
command example spanning-tree cost command

28
show mls ip multicast statistics command

22, 25
command example spanning-tree portfast command

8, 9
29
displaying NDE flow IP address
command example command command

12
spanning-tree portfast bpdu-guard spanning-tree port-priority

27 2
spanning-tree protocol for bridging spanning-tree uplinkfast command

13 13
show running-config command show startup-config command show version command shutdown command
19
9, 23, 24, 17
command example spanning-tree vlan
IN-20
Index
command
22, 24, 25, 26, 15 23, 24, 26
bridge priority enabling hello time port cost

22, 24
30
command example spanning-tree vlan cost command command

28
forward-delay time
31
32
spanning-tree vlan forward-time

32 32
maximum aging time

28 26 24
32
command example command

31
port priority root bridge defaults

21
spanning-tree vlan hello-time command example command

32 32 31
secondary root switch EtherChannel understanding

5 2 12 8
26
spanning-tree vlan max-age command example command

27 28
802.1Q Trunks Blocking State BPDUs

4
spanning-tree vlan port-priority command example command speed configuring interface speed command SRR SST
109 15 16 1 2, 8 7 30 30
disabled state learning state listening state overview port states

2 6
12 11
spanning-tree vlan priority command example
forwarding state
10 9
protocol timers topology and MST configuring figure

12 5
5 4
root bridge election STP BackboneFast

16 13
interoperability standby link standby links statistics 802.1X Sticky ARP sticky ARP
16 35 35 1 1
Standard-Compliant IEEE 802.1s MST
static route, configuring
adding a switch command understanding

13, 14
spanning-tree backbonefast command example

4 3 10, 11 14
sticky MAC address storm control
STP BPDU Guard and MST configuring command

16 12
Sticky secure MAC addresses see traffic-storm control STP configuring

22
spanning-tree portfast bpdu-guard

12 2
understanding
IN-21
Index
STP bridge ID STP loop guard and MST configuring overview STP PortFast and MST
16 7 16
2 6
supervisor engine redundancy configuring

10, 5
STP EtherChannel guard
supervisor engines displaying redundancy configuration

15 7
Switched Port Analyzer See SPAN switch fabric functionality configuring monitoring
10 2 4 4 1 2
BPDU filter configuring BPDU filtering configuring command understanding and MST and MST and MST configuring command understanding supervisor engine configuring
1 2 16 7, 14 8
switch fabric module configuring monitoring slot locations switchport

9 3 5 2
spanning-tree portfast
8, 9
command example
2
configuring example
13
14
STP Portfast BPDU filtering STP root guard

16
show interfaces example example

14
12, 13, 7, 12 10, 14
switchport access vlan switchport mode access

14
4, 14
STP UplinkFast
16 12
switchport mode dynamic
9 4 4
switchport mode dynamic auto default

13 5 13 4, 9 4
spanning-tree uplinkfast
13
switchport mode dynamic desirable example

2
command example
3
switchport mode trunk switchport nonegotiate
subdomains, private VLAN
switchport trunk allowed vlan switchport trunk encapsulation

12 10
11 8 4
default configuration default gateways redundancy ROM monitor static routes

12 1 20
switchport trunk encapsulation dot1q example

13 4
environmental monitoring
switchport trunk encapsulation isl default

5 10 12
switchport trunk encapsulation negotiate

20
startup configuration
switchport trunk native vlan switchport trunk pruning vlan

20, 7
synchronizing configurations Supervisor Engine 32

1
switch priority MSTP

23
IN-22
OL-3999-08
Index
switch TopN reports foreground execution overview running viewing system configuration register configuration
21 to 24 22 3 to 8 2 2 1 2
traffic flood blocking traffic-storm control command broadcast described monitoring thresholds
1 5 1 4
traffic suppression see traffic-storm control translational bridge numbers (defaults) transmit queues see QoS transmit queues
22 6 5
settings at startup
configuring global parameters System Hardware Capacity system image determining if and how to load loading from Flash
24
trunks
3 5
802.1Q Restrictions allowed VLANs

11
T
TACACS+ TDR checking cable connectivity enabling and disabling test guidelines Telnet accessing CLI See TDR TopN reports See switch TopN reports traceroute, Layer 2 and ARP and CDP described
2 2 1 2 2 2 19 19 19 1 2
configuring
8 7
default interface configuration default VLAN encapsulation native VLAN

10 3
TCP Intercept
different VTP domains

3 10 4
to non-DTP device trust-dscp see QoS trust-dscp trust-ipprec see QoS trust-ipprec tunneling
4, 32
VLAN 1 minimization
11
Time Domain Reflectometer
tunneling, 802.1Q See 802.1Q

1
U
UDE
1 4
IP addresses and subnets multicast traffic unicast traffic

1 2 2
MAC addresses and VLANs multiple devices on a port usage guidelines

2
configuration overview UDLD

2
UDE and UDLR
IN-23
Index
enabling globally on ports overview UDLR

1 2 6 1 4 4, 5
user EXEC mode UUFB

1
V
VACLs
2 4 9 8 7
back channel configuration tunnel (example)
configuring examples
7 3
Layer 3 VLAN interfaces Layer 4 port operations logging configuration example configuring
4 1 11 11 5
ARP and NHRP See UDLR UMFB

1
UDLR (unidirectional link routing)
11
unauthorized ports with 802.1X unicast flood blocking unicast RPF unicast storms see traffic-storm control Unidirectional Ethernet see UDE unidirectional ethernet example of setting see UDLD uniform mode configuring See UMFB unknown unicast flood blocking See UUFB untrusted see QoS trust-cos see QoS untrusted upgrade guidelines UplinkFast See STP UplinkFast URD
10 22, 79 16 40 5 2 1
restrictions
Unicast and Multicast Flood Blocking
MAC address based multicast packets overview SVIs

8 2 2 4
WAN interfaces virtual LAN See VLANs vlan command
10, 12, 13, 16 11 68 2
UniDirectional Link Detection Protocol
command example
VLAN-based QoS filtering vlan database command example command VLAN mode VLANs allowed on trunk
11 10, 12, 13, 16 11
VLAN-bridge spanning-tree protocol
unknown multicast flood blocking
vlan mapping dot1q

15, 16 17
command example
16
configuration guidelines configuration options
global configuration mode VLAN database mode

9
User-Based Rate Limiting
IN-24
OL-3999-08
Index
configuring defaults
6
1 9
default configuration disabling domains

2 9 2 3
configuring (tasks) extended range ID (default)

6
VLANs modes
12
interface assignment name (default) normal range private See private VLANs reserved range token ring trunks understanding understanding VTP domain
3 1 3 3 2 2 6
client server
2 2 2 10 1
transparent monitoring overview pruning

2
support for 4,096 VLANs
configuration configuring overview statistics

10 4 7
12
server, configuring
11
VLAN 1 minimization VLAN translation command example See VTP voice VLAN
transparent mode, configuring version 2 enabling

8 3
15, 16
overview
VLAN Trunking Protocol
W
2
Cisco 7960 phone, port connections configuration guidelines

5
web browser interface weighted round robin WRR

109
1 109
configuring IP phone for data traffic override CoS of incoming frame configuring ports for voice traffic in 802.1Q frames
6 6 7, 8
X
xconnect command
16 5
connecting to an IP phone default configuration overview VPN configuration example VTP advertisements
3 9 5 12 1
guidelines and restrictions
11
client, configuring
IN-25

Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide Release 12.2 (18) SXF

Uploaded by

Copyright:

Available Formats

Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide Release 12.2 (18) SXF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide Release 12.2 (18) SXF

Uploaded by

Copyright:

Available Formats

Catalyst 6500 Series Switch Cisco IOS Software Configuration Guide

Release 12.2(18)SXF and Rebuilds and Earlier Releases

Text Part Number: OL-3999-08

Product Overview User Interfaces

Supported Hardware and Software

Flash Memory on a Supervisor Engine 32

Understanding How the Switch Fabric Module Works

Understanding Interface Configuration Using the Interface Command

Configuring a Range of Interfaces

Defining and Using Interface-Range Macros

Configuring LAN Ports for Layer 2 Switching

Understanding Flex Links

Understanding Port Channel Interfaces Understanding Load Balancing 5

EtherChannel Feature Configuration Guidelines and Restrictions

VLAN Configuration Guidelines and Restrictions

Configuring Cisco IP Phone Support

Cisco IP Phone Support Configuration Guidelines and Restrictions

Understanding How 802.1Q Tunneling Works

STP and MST Configuration Guidelines and Restrictions

Understanding How BPDU Guard Works Understanding How UplinkFast Works

Understanding How EtherChannel Guard Works

Enabling EtherChannel Guard

Configuring Layer 3 Interfaces

Configuring AppleTalk Routing, Cable Ranges, and Zones

Displaying Hardware Layer 3 Switching Statistics

Default IPv4 Multicast Layer 3 Switching Configuration

Understanding How PIM Snooping Works Default PIM Snooping Configuration

Understanding How RGMP Works Default RGMP Configuration

Configuring MAC Address-Based Traffic Blocking

Cisco IOS ACL Configuration Guidelines and Restrictions

CoPP Configuration Guidelines and Restrictions

Configuring DHCP Snooping

DAI Configuration Guidelines and Restrictions

Understanding Traffic Storm Control

Default Traffic Storm Control Configuration Enabling Traffic Storm Control

Configuring PFC3BXL or PFC3B Mode MPLS QoS Terminology

PFC3BXL or PFC3B Mode MPLS QoS Restrictions and Guidelines

PFC QoS Statistics Data Export Default Configuration

802.1X Port-Based Authentication Guidelines and Restrictions

Port Security Guidelines and Restrictions

Understanding How CDP Works

Understanding How Online Diagnostics Work

Online Diagnostic Tests

Global Health-Monitoring Tests TestSPRPInbandPing 2 TestScratchRegister 3 TestMacNotification 3

For information about MIBs, go to this URL: http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml

Notes use the following conventions:

Obtaining Documentation and Submitting a Service Request

Supported Hardware and Software

Chapter 1 Configuring Embedded CiscoView Support

Configuring Embedded CiscoView Support

Understanding Embedded CiscoView

Installing and Configuring Embedded CiscoView

Step 2 Step 3 Step 4

Step 6 Step 7 Step 8 Step 9

Displaying Embedded CiscoView Information

Software Features Supported in Hardware by the PFC and DFC

in software on the MSFC

Idle timeout is processed in software on the MSFC.

Chapter 1 Software Features Supported in Hardware by the PFC and DFC