Cisco IOS Software Configuration Guide

Cisco IOS Software Configuration Guide
Release 12.2(33)SXH and Later Releases
Americas 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 527-0883
Text Part Number: OL-13013-06
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 of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Cisco IOS Software Configuration Guide, Release 12.2SX 20072009, Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
xxxix xxxix xxxix
Audience Conventions
Related Documentation
xxxix
Obtaining Documentation, Obtaining Support, and Security Guidelines

1
xl
CHAPTER
Product Overview
1-1
Supported Hardware and Software 1-1 Understanding Supervisor Engine 720-10GE Memory Devices and Ports Understanding Supervisor Engine 720 Memory Devices and Ports 1-2 Understanding Supervisor Engine 32 Memory Devices and Ports 1-4 Understanding ME6500 Flash Memory Devices and Ports 1-5 User Interfaces
1-5 1-6
1-1
Software Features Supported in Hardware by the PFC and DFC

1
PART
Configuration Fundamentals
2
CHAPTER
Command-Line Interfaces
2-1
Accessing the CLI 2-2 Accessing the CLI through the EIA/TIA-232 Console Interface Accessing the CLI through Telnet 2-2 Performing Command Line Processing Performing History Substitution Cisco IOS Command Modes Securing the CLI
2-6 2-7 2-4 2-5 2-4 2-3
2-2
Displaying a List of Cisco IOS Commands and Syntax ROM-Monitor Command-Line Interface
3
CHAPTER
Configuring Smart Port Macros
3-1
Understanding Smart Port Macros 3-1 Understanding Cisco-Provided Smart Port Macros 3-1 Understanding User-Created Smart Port Macros 3-2 Configuring Smart Port Macros
3-2
Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06
iii
Contents
Smart Port Macro Default Configuration 3-2 Smart Port Macro Configuration Guidelines 3-3 Applying the Cisco-Provided Smart Port Macros 3-4 Configuring User-Created Smart Port Macros 3-13 Displaying Smart Port Macros
4
3-16
CHAPTER
Configuring Virtual Switching Systems Understanding Virtual Switching Systems VSS Overview 4-2 VSS Redundancy 4-11 Multichassis EtherChannels 4-14 Packet Handling 4-16 System Monitoring 4-20 Dual-Active Detection 4-22 VSS Initialization 4-25
4-1 4-1
VSS Configuration Guidelines and Restrictions 4-29 General VSS Restrictions and Guidelines 4-29 VSL Restrictions and Guidelines 4-29 Multichassis EtherChannel Restrictions and Guidelines 4-29 Dual-Active Detection Restrictions and Guidelines 4-30 Service Module Restrictions and Guidelines 4-30 Configuring a VSS 4-30 Converting to a VSS 4-31 Displaying VSS Information 4-37 Converting a VSS to Standalone Chassis 4-37 Configuring VSS Parameters 4-39 Configuring Multichassis EtherChannels 4-45 Configuring Dual-Active Detection 4-46 Configuring Service Modules in a VSS 4-52 Viewing Chassis Status and Module Information in a VSS Upgrading a VSS 4-55 Performing a Fast Software Upgrade of a VSS 4-55 Performing an Enhanced Fast Software Upgrade of a VSS
2
4-54
4-56
PART
High Availability
5
CHAPTER
Performing an Enhanced Fast Software Upgrade eFSU Overview 5-1 eFSU Operation 5-2
Cisco IOS Software Configuration Guide, Release 12.2SX
5-1
iv
OL-13013-06
Contents
Outage Time and Support Considerations Reserving Module Memory 5-3 Error Handling for eFSU Preload 5-4 eFSU Guidelines and Limitations
5-4
5-3
Performing an Enhanced Fast Software Upgrade 5-5 Software Upgrade Process Summary For a Switch 5-5 Preparing for the Upgrade 5-6 Copying the New Software Image 5-8 Loading the New Software onto the Standby Supervisor Engine 5-8 Displaying the Maximum Outage Time for Installed Modules (Optional) 5-10 Forcing a Switchover from Active to Standby 5-10 Accepting the New Software Version and Stopping the Rollback Process (Optional) Committing the New Software to the Standby 5-12 Verifying the Software Installation 5-12 Aborting the Upgrade Process 5-13 Performing an eFSU Upgrade on an Installed Modular Image 5-14 Upgrading an Installed Modular Image 5-14 Example an eFSU Upgrade on an Installed Modular Image 5-15 Upgrading a Non-eFSU Image to an eFSU Image
6
5-16
5-11
CHAPTER
Configuring NSF with SSO Supervisor Engine Redundancy
6-1
Understanding NSF with SSO Supervisor Engine Redundancy 6-1 NSF with SSO Supervisor Engine Redundancy Overview 6-2 SSO Operation 6-2 NSF Operation 6-3 Cisco Express Forwarding 6-3 Multicast MLS NSF with SSO 6-4 Routing Protocols 6-4 NSF Benefits and Restrictions 6-8 Supervisor Engine Configuration Synchronization 6-9 Supervisor Engine Redundancy Guidelines and Restrictions 6-9 Redundancy Configuration Guidelines and Restrictions 6-9 Hardware Configuration Guidelines and Restrictions 6-10 Configuration Mode Restrictions 6-11 NSF Configuration Tasks 6-11 Configuring SSO 6-11 Verifying the Redundancy States 6-12 Configuring Multicast MLS NSF with SSO Verifying Multicast NSF with SSO 6-13
6-13
Contents
Configuring CEF NSF 6-13 Verifying CEF NSF 6-14 Configuring BGP NSF 6-14 Verifying BGP NSF 6-14 Configuring OSPF NSF 6-15 Verifying OSPF NSF 6-16 Configuring IS-IS NSF 6-17 Verifying IS-IS NSF 6-17 Configuring EIGRP NSF 6-19 Verifying EIGRP NSF 6-19 Synchronizing the Supervisor Engine Configurations Copying Files to the Redundant Supervisor Engine
7
6-20
6-20
CHAPTER
Configuring RPR Supervisor Engine Redundancy
7-1
Understanding RPR 7-1 Supervisor Engine Redundancy Overview 7-2 RPR Operation 7-2 Supervisor Engine Configuration Synchronization
7-3
Supervisor Engine Redundancy Guidelines and Restrictions 7-3 Redundancy Guidelines and Restrictions 7-3 Hardware Configuration Guidelines and Restrictions 7-3 Configuration Mode Restrictions 7-4 Configuring Supervisor Engine Redundancy 7-4 Configuring Redundancy 7-4 Synchronizing the Supervisor Engine Configurations Displaying the Redundancy States 7-5 Performing a Fast Software Upgrade Copying Files to the RP
3
7-7 7-6
7-5
PART
Interface and Hardware Components

8
CHAPTER
Configuring and Monitoring the Switch Fabric Functionality Understanding the Switch Fabric Functionality 8-1 Switch Fabric Functionality Overview 8-2 Forwarding Decisions for Layer 3-Switched Traffic Switching Modes 8-2 Configuring the Switch Fabric Functionality Monitoring the Switch Fabric Functionality
8-3 8-4
8-1
8-2
vi
OL-13013-06
Contents
Displaying the Switch Fabric Redundancy Status 8-4 Displaying Fabric Channel Switching Modes 8-4 Displaying the Fabric Status 8-5 Displaying the Fabric Utilization 8-5 Displaying Fabric Errors 8-6
9
CHAPTER
Configuring Interfaces
9-1 9-2
Understanding Interface Configuration Using the Interface Command

9-2 9-4
Configuring a Range of Interfaces
Defining and Using Interface-Range Macros
9-6
Configuring Optional Interface Features 9-6 Configuring Ethernet Interface Speed and Duplex Mode Configuring Jumbo Frame Support 9-10 Configuring IEEE 802.3x Flow Control 9-13 Configuring the Port Debounce Timer 9-15 Adding a Description for an Interface 9-16 Understanding Online Insertion and Removal Monitoring and Maintaining Interfaces 9-17 Monitoring Interface Status 9-17 Clearing Counters on an Interface 9-18 Resetting an Interface 9-18 Shutting Down and Restarting an Interface Checking the Cable Status Using the TDR
10
9-19 9-16
9-7
9-19
CHAPTER
Configuring UDLD
10-1
Understanding UDLD 10-1 UDLD Overview 10-2 UDLD Aggressive Mode Fast UDLD 10-4 Default UDLD Configuration
10-3
10-4
Configuring UDLD 10-5 Enabling UDLD Globally 10-5 Enabling UDLD on LAN Ports 10-5 Disabling UDLD on Fiber-Optic LAN Ports 10-6 Configuring the Global UDLD Probe Message Interval Configuring Fast UDLD 10-6 Resetting Disabled LAN Interfaces 10-7
10-6
vii
Contents
CHAPTER
11
Power Management and Environmental Monitoring Understanding Power Management 11-1 Enabling or Disabling Power Redundancy 11-2 Powering Modules Off and On 11-3 Viewing System Power Status 11-4 Power Cycling Modules 11-5 Determining System Power Requirements 11-5 Determining System Hardware Capacity 11-5 Determining Sensor Temperature Threshold 11-9
11-1
Understanding Environmental Monitoring 11-10 Overview 11-10 Monitoring System Environmental Status 11-10 Understanding LED Environmental Indications 11-12
12
CHAPTER
Configuring EnergyWise
12-1
CHAPTER
13
Configuring Onboard Failure Logging Understanding OBFL 13-1 Overview of OBFL 13-2 Data Collected by OBFL 13-2 Restrictions for OBFL Enabling OBFL
13-9 13-9
13-1
Configuration Examples for OBFL 13-10 Enabling OBFL Message Logging: Example 13-10 OBFL Message Log: Example 13-10 OBFL Component Uptime Report: Example 13-10 OBFL Report for a Specific Time: Example 13-11
14
CHAPTER
Configuring Online Diagnostics
14-1 14-1
Understanding Online Diagnostics
Configuring Online Diagnostics 14-2 Setting Bootup Online Diagnostics Level 14-2 Configuring On-Demand Online Diagnostics 14-3 Scheduling Online Diagnostics 14-4 Configuring Health-Monitoring Diagnostics 14-5 Running Online Diagnostic Tests 14-5 Starting and Stopping Online Diagnostic Tests Running All Online Diagnostic Tests 14-7
14-6
viii
OL-13013-06
Contents
Displaying Online Diagnostic Tests and Test Results Performing Memory Tests
15
14-12
14-7
CHAPTER
Configuring Cisco IP Phone Support
15-1
Understanding Cisco IP Phone Support 15-1 Cisco IP Phone Connections 15-2 Cisco IP Phone Voice Traffic 15-2 Cisco IP Phone Data Traffic 15-3 IP Phone Power Configurations 15-3 Other Cisco IP Phone Features 15-6 Default Cisco IP Phone Support Configuration Configuring Cisco IP Phone Support 15-7 Configuring Voice Traffic Support 15-8 Configuring Data Traffic Support 15-9 Configuring Inline Power Support 15-10
2
15-6 15-7
Cisco IP Phone Support Configuration Guidelines and Restrictions
PART
LAN Switching
16
CHAPTER
Configuring LAN Ports for Layer 2 Switching Understanding Layer 2 Switching 16-1 Understanding Layer 2 Ethernet Switching Understanding VLAN Trunks 16-3 Layer 2 LAN Port Modes 16-4 Default Layer 2 LAN Interface Configuration
16-1
16-1
16-5 16-5
Layer 2 LAN Interface Configuration Guidelines and Restrictions
Configuring LAN Interfaces for Layer 2 Switching 16-6 Configuring a LAN Port for Layer 2 Switching 16-7 Enabling Out-of-Band MAC Address Table Synchronization 16-8 Configuring MAC Address Table Notification 16-8 Configuring a Layer 2 Switching Port as a Trunk 16-10 Configuring a LAN Interface as a Layer 2 Access Port 16-16 Configuring an IEEE 802.1Q Custom EtherType Field Value 16-18
17
CHAPTER
Configuring Flex Links
17-1 17-1
Understanding Flex Links
Configuring Flex Links 17-2 Flex Links Default Configuration
17-2
ix
Contents
Flex Links Configuration Guidelines and Restrictions Configuring Flex Links 17-3 Monitoring Flex Links
18
17-4
17-2
CHAPTER
Configuring EtherChannels
18-1
Understanding EtherChannels 18-1 EtherChannel Feature Overview 18-2 Understanding EtherChannel Configuration 18-2 Understanding LACP 1:1 Redundancy 18-5 Understanding Port Channel Interfaces 18-5 Understanding Load Balancing 18-5 EtherChannel Feature Configuration Guidelines and Restrictions
18-6
Configuring EtherChannels 18-7 Configuring Port Channel Logical Interfaces for Layer 3 EtherChannels 18-7 Configuring Channel Groups 18-8 Configuring the LACP System Priority and System ID 18-11 Configuring EtherChannel Load Balancing 18-11 Configuring EtherChannel Hash-Distribution Algorithm 18-12 Configuring the EtherChannel Min-Links Feature 18-13 Configuring LACP 1:1 Redundancy 18-14 Configuring Auto Interleaved Port Priority For LACP Port Channels 18-15
19
CHAPTER
Configuring mLACP for Server Access
19-1
Understanding mLACP for Server Access 19-1 Overview of mLACP for Server Access 19-2 Understanding mLACP Operation 19-2 Failure Protection Scenarios 19-6 mLACP Failover 19-6 mLACP for Server Access Guidelines and Restrictions
19-9
Configuring mLACP for Server Access 19-10 Summary of mLACP PoA Configuration Values 19-11 Configuring mLACP Global Options 19-11 Configuring the Interchassis Communication Channel 19-12 Configuring Interchassis Redundancy Groups 19-13 Forcing a PoA Failover 19-18 Troubleshooting mLACP 19-18 Verifying an Active PoA 19-18 Verifying a Standby PoA 19-22
OL-13013-06
Contents
CHAPTER
20
Configuring IEEE 802.1ak MVRP and MRP
20-1
Understanding IEEE 802.1ak MVRP and MRP 20-1 Overview 20-1 Dynamic VLAN Creation 20-3 MVRP Interoperability with VTP 20-3 MVRP Interoperation with Non-Cisco Devices 20-5 MVRP Interoperability with Other Software Features and Protocols IEEE 802.1ak MVRP and MRP Guidelines and Restrictions Configuring IEEE 802.1ak MVRP and MRP 20-8 Enabling MVRP 20-8 Enabling Automatic Detection of MAC Addresses Enabling MVRP Dynamic VLAN Creation 20-9 Changing the MVRP Registrar State 20-9 Troubleshooting the MVRP Configuration
20-10 20-7
20-5
20-8
Configuration Examples for IEEE 802.1ak MVRP and MRP 20-11 Enabling MVRP 20-11 Enabling MVRP Automatic Detection of MAC Addresses 20-11 Enabling Dynamic VLAN Creation 20-11 Changing the MVRP Registrar State 20-11
21
CHAPTER
Configuring VTP
21-1
Understanding VTP 21-1 Understanding the VTP Domain 21-2 Understanding VTP Modes 21-3 Understanding VTP Advertisements 21-3 Understanding VTP Authentication 21-4 Understanding VTP Version 2 21-4 Understanding VTP Version 3 21-5 Understanding VTP Pruning 21-6 VLAN Interaction 21-8 Interaction Between VTP Version 3 and VTP Version 2 Devices Interaction Between VTP Version 3 and VTP Version 1 Devices VTP Default Configuration
21-8 21-9 21-8 21-8
VTP Configuration Guidelines and Restrictions
Configuring VTP 21-10 Configuring VTP Global Parameters 21-10 Configuring the VTP Mode 21-15 Configuring VTP Mode on a Per-Port Basis 21-17
xi
Contents
Displaying VTP Statistics

22
21-18
CHAPTER
Configuring VLANs
22-1
Understanding VLANs 22-1 VLAN Overview 22-2 VLAN Ranges 22-2 VLAN Configuration Guidelines and Restrictions
22-3
Configuring VLANs 22-3 Configurable VLAN Parameters 22-4 Ethernet VLAN Default Parameters 22-4 VLAN Locking 22-4 Creating or Modifying an Ethernet VLAN 22-5 Assigning a Layer 2 LAN Interface to a VLAN 22-6 Configuring the Internal VLAN Allocation Policy 22-7 Configuring VLAN Translation 22-7 Mapping 802.1Q VLANs to ISL VLANs 22-10 Saving VLAN Information 22-11
23
CHAPTER
Configuring Private VLANs
23-1
Understanding Private VLANs 23-1 Private VLAN Domains 23-2 Private VLAN Ports 23-3 Primary, Isolated, and Community VLANs 23-3 Private VLAN Port Isolation 23-4 IP Addressing Scheme with Private VLANs 23-4 Private VLANs Across Multiple Switches 23-5 Private VLAN Interaction with Other Features 23-5 Private VLAN Configuration Guidelines and Restrictions Secondary and Primary VLAN Configuration 23-7 Private VLAN Port Configuration 23-9 Limitations with Other Features 23-9
23-6
Configuring Private VLANs 23-11 Configuring a VLAN as a Private VLAN 23-11 Associating Secondary VLANs with a Primary VLAN 23-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 23-15 Configuring a Layer 2 Interface as a Private VLAN Promiscuous Port 23-16 Monitoring Private VLANs
23-17
23-13
xii
OL-13013-06
Contents
CHAPTER
24
Configuring Private Hosts
24-1
Understanding Private Hosts 24-1 Isolating Hosts in a VLAN 24-2 Restricting Traffic Flow (Using Private Hosts Port Mode and PACLs) Port ACLs 24-5 Configuration Guidelines and Limitations 24-5 ACL Guidelines 24-6 VLANs on the Trunk Port 24-6 Interaction with Other Features 24-6 Spoofing Protection 24-7 Multicast Operation 24-7 Configuring Private Hosts 24-7 Configuration Summary 24-8 Detailed Configuration Steps 24-9 Configuration Examples 24-10
25
24-3
CHAPTER
Configuring IEEE 802.1Q Tunneling Understanding 802.1Q Tunneling
25-1 25-1 25-3
802.1Q Tunneling Configuration Guidelines and Restrictions Configuring 802.1Q Tunneling 25-6 Configuring 802.1Q Tunnel Ports 25-6 Configuring the Switch to Tag Native VLAN Traffic
26
25-7
CHAPTER
Configuring Layer 2 Protocol Tunneling Understanding Layer 2 Protocol Tunneling
26-1 26-1 26-2
Configuring Support for Layer 2 Protocol Tunneling

27
CHAPTER
Configuring STP and MST
27-1
Understanding STP 27-1 STP Overview 27-2 Understanding the Bridge ID 27-2 Understanding Bridge Protocol Data Units 27-3 Election of the Root Bridge 27-4 STP Protocol Timers 27-4 Creating the Spanning Tree Topology 27-5 STP Port States 27-5 STP and IEEE 802.1Q Trunks 27-12 Understanding IEEE 802.1w RSTP
27-13
xiii
Contents
Port Roles and the Active Topology 27-13 Rapid Convergence 27-14 Synchronization of Port Roles 27-15 Bridge Protocol Data Unit Format and Processing Topology Changes 27-17 Rapid-PVST 27-18 Understanding MST 27-18 MST Overview 27-19 MST Regions 27-19 IST, CIST, and CST 27-20 Hop Count 27-23 Boundary Ports 27-23 Standard-Compliant MST Implementation 27-24 Interoperability with IEEE 802.1D-1998 STP 27-26
27-16
Configuring STP 27-26 Default STP Configuration 27-27 Enabling STP 27-28 Enabling the Extended System ID 27-29 Configuring the Root Bridge 27-30 Configuring a Secondary Root Bridge 27-31 Configuring STP Port Priority 27-32 Configuring STP Port Cost 27-33 Configuring the Bridge Priority of a VLAN 27-35 Configuring the Hello Time 27-36 Configuring the Forward-Delay Time for a VLAN 27-36 Configuring the Maximum Aging Time for a VLAN 27-37 Enabling Rapid-PVST 27-37 Configuring MST 27-38 Default MST Configuration 27-39 MST Configuration Guidelines and Restrictions 27-39 Specifying the MST Region Configuration and Enabling MST Configuring the Root Bridge 27-41 Configuring a Secondary Root Bridge 27-43 Configuring Port Priority 27-43 Configuring Path Cost 27-44 Configuring the Switch Priority 27-45 Configuring the Hello Time 27-46 Configuring the Forwarding-Delay Time 27-47 Configuring the Transmit Hold Count 27-47
27-40
xiv
OL-13013-06
Contents
Configuring the Maximum-Aging Time 27-48 Configuring the Maximum-Hop Count 27-48 Specifying the Link Type to Ensure Rapid Transitions Designating the Neighbor Type 27-49 Restarting the Protocol Migration Process 27-50 Displaying the MST Configuration and Status
28
27-50
27-48
CHAPTER
Configuring Optional STP Features
28-1
Understanding the Optional STP Features 28-1 Understanding STP Port Types 28-2 Understanding PortFast 28-2 Understanding Bridge Assurance 28-3 Understanding BPDU Guard 28-5 Understanding PortFast BPDU Filtering 28-5 Understanding UplinkFast 28-6 Understanding BackboneFast 28-7 Understanding EtherChannel Guard 28-9 Understanding Root Guard 28-10 Understanding Loop Guard 28-10 Understanding PVST Simulation 28-11 Configuring the Optional STP Features 28-12 Enabling PortFast 28-12 Enabling Bridge Assurance 28-14 Enabling PortFast BPDU Filtering 28-15 Enabling BPDU Guard 28-16 Enabling UplinkFast 28-18 Enabling BackboneFast 28-19 Enabling EtherChannel Guard 28-20 Enabling Root Guard 28-20 Enabling Loop Guard 28-21 Configuring PVST Simulation 28-22 Verifying the Optional STP Features 28-23 Using the show spanning-tree Commands 28-23 Examples in Release 12.2(33)SXI and Later Releases 28-23 Examples in Releases Earlier Than Release 12.2(33)SXI 28-26
3
PART
IP Routing Protocols
xv
Contents
CHAPTER
29
Configuring Layer 3 Interfaces
29-1 29-2
Layer 3 Interface Configuration Guidelines and Restrictions Configuring Subinterfaces on Layer 3 Interfaces Configuring IPv4 Routing and Addresses
29-4 29-7 29-2
Configuring IPX Routing and Network Numbers Configuring Other Protocols on Layer 3 Interfaces
30
Configuring AppleTalk Routing, Cable Ranges, and Zones

29-9
29-8
CHAPTER
Configuring UDE and UDLR
30-1
Understanding UDE and UDLR 30-1 UDE and UDLR Overview 30-1 Supported Hardware 30-2 Understanding UDE 30-2 Understanding UDLR 30-3 Configuring UDE and UDLR 30-3 Configuring UDE 30-3 Configuring UDLR 30-6
4
PART
Multiprotocol Label Switching

31
CHAPTER
Configuring Multiprotocol Label Switching
31-1
MPLS 31-1 Understanding MPLS 31-2 Hardware-Supported MPLS Functions 31-4 Supported Cisco IOS Features 31-5 MPLS Guidelines and Restrictions 31-7 Supported MPLS Commands 31-7 Configuring MPLS 31-8 MPLS Per-Label Load Balancing 31-8 MPLS Configuration Examples 31-8 DE/CLP and EXP Mapping on FR/ATMoMPLS VC Match on ATM CLP Bit 31-10 Set on ATM CLP Bit 31-12 VPN Switching 31-13 VPN Switching Operation 31-13 MPLS VPN Guidelines and Restrictions 31-14 MPLS VPN Supported Commands 31-14 Configuring MPLS VPN 31-15
31-10
xvi
OL-13013-06
Contents
MPLS VPN Sample Configuration
31-15
Any Transport over MPLS 31-17 AToM Load Balancing 31-17 Understanding EoMPLS 31-17 EoMPLS Guidelines and Restrictions 31-18 Configuring EoMPLS 31-19 Configuring MUX-UNI Support on LAN Cards
5
31-26
PART
IP Switching
32
CHAPTER
Configuring IP Unicast Layer 3 Switching
32-1
Understanding Layer 3 Switching 32-2 Understanding Hardware Layer 3 Switching 32-2 Understanding Layer 3-Switched Packet Rewrite 32-2 Default Hardware Layer 3 Switching Configuration Configuration Guidelines and Restrictions Configuring Hardware Layer 3 Switching
32-4 32-5 32-6 32-4
Displaying Hardware Layer 3 Switching Statistics

6
PART
IPv6
33
CHAPTER
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching Features that Support IPv6 Multicast
33-1 33-2 33-3 33-3
33-1
IPv6 Multicast Guidelines and Restrictions New or Changed IPv6 Multicast Commands Configuring IPv6 Multicast Layer 3 Switching
Using show Commands to Verify IPv6 Multicast Layer 3 Switching 33-3 Verifying MFIB Clients 33-4 Displaying the Switching Capability 33-4 Verifying the (S,G) Forwarding Capability 33-5 Verifying the (*,G) Forwarding Capability 33-5 Verifying the Subnet Entry Support Status 33-5 Verifying the Current Replication Mode 33-5 Displaying the Replication Mode Auto-Detection Status 33-5 Displaying the Replication Mode Capabilities 33-5 Displaying Subnet Entries 33-6 Displaying the IPv6 Multicast Summary 33-6 Displaying the NetFlow Hardware Forwarding Count 33-6
xvii
Contents
Displaying the FIB Hardware Bridging and Drop Counts 33-7 Displaying the Shared and Well-Known Hardware Adjacency Counters
34
33-7
CHAPTER
Configuring MLD Snooping for IPv6 Multicast Traffic Understanding MLD Snooping 34-2 MLD Snooping Overview 34-2 MLD Messages 34-3 Source-Based Filtering 34-3 Explicit Host Tracking 34-3 MLD Snooping Proxy Reporting 34-4 Joining an IPv6 Multicast Group 34-4 Leaving a Multicast Group 34-6 Understanding the MLD Snooping Querier Default MLD Snooping Configuration
34-8
34-1
34-7
MLD Snooping Configuration Guidelines and Restrictions Enabling the MLD Snooping Querier
34-9
34-8 34-9
MLD Snooping Querier Configuration Guidelines and Restrictions Configuring MLD Snooping 34-10 Enabling MLD Snooping 34-10 Configuring a Static Connection to a Multicast Receiver Configuring a Multicast Router Port Statically 34-11 Configuring the MLD Snooping Query Interval 34-12 Enabling Fast-Leave Processing 34-12 Enabling SSM Safe Reporting 34-13 Configuring Explicit Host Tracking 34-13 Configuring Report Suppression 34-14 Displaying MLD Snooping Information 34-14
7
34-11
PART
IP Multicast
35
CHAPTER
Configuring IPv4 Multicast Layer 3 Switching
35-1
Understanding IPv4 Multicast Layer 3 Switching 35-1 IPv4 Multicast Layer 3 Switching Overview 35-2 Multicast Layer 3 Switching Cache 35-2 Layer 3-Switched Multicast Packet Rewrite 35-3 Partially and Completely Switched Flows 35-4 Non-RPF Traffic Processing 35-5 Multicast Boundary 35-8
xviii
OL-13013-06
Contents
Understanding IPv4 Bidirectional PIM
35-9 35-9 35-10
Default IPv4 Multicast Layer 3 Switching Configuration
IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions Restrictions 35-10 Unsupported Features 35-10 Configuring IPv4 Multicast Layer 3 Switching 35-11 Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD 35-11 Enabling IPv4 Multicast Routing Globally 35-11 Enabling IPv4 PIM on Layer 3 Interfaces 35-12 Enabling IP Multicast Layer 3 Switching Globally 35-12 Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces 35-13 Configuring the Replication Mode 35-13 Enabling Local Egress Replication 35-15 Configuring the Layer 3 Switching Global Threshold 35-16 Enabling Installation of Directly Connected Subnets 35-17 Specifying the Flow Statistics Message Interval 35-17 Enabling Shortcut-Consistency Checking 35-17 Configuring ACL-Based Filtering of RPF Failures 35-18 Displaying RPF Failure Rate-Limiting Information 35-18 Configuring Multicast Boundary 35-19 Displaying IPv4 Multicast Layer 3 Hardware Switching Summary 35-19 Displaying the IPv4 Multicast Routing Table 35-22 Displaying IPv4 Multicast Layer 3 Switching Statistics 35-23 Configuring IPv4 Bidirectional PIM 35-24 Enabling IPv4 Bidirectional PIM Globally 35-24 Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups Setting the IPv4 Bidirectional PIM Scan Interval 35-25 Displaying IPv4 Bidirectional PIM Information 35-26 Using IPv4 Debug Commands 35-28 Clearing IPv4 Multicast Layer 3 Switching Statistics 35-28 Redundancy for Multicast Traffic 35-29
36
35-25
CHAPTER
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Understanding IGMP Snooping 36-2 IGMP Snooping Overview 36-2 Joining a Multicast Group 36-2 Leaving a Multicast Group 36-4 Understanding the IGMP Snooping Querier 36-5 Understanding IGMP Version 3 Support 36-5
36-1
xix
Contents
Default IGMP Snooping Configuration
36-7 36-8 36-8
IGMP Snooping Configuration Guidelines and Restrictions Enabling the IGMP Snooping Querier
36-9
IGMP Snooping Querier Configuration Guidelines and Restrictions Configuring IGMP Snooping 36-9 Enabling IGMP Snooping 36-10 Configuring a Static Connection to a Multicast Receiver Configuring a Multicast Router Port Statically 36-11 Configuring the IGMP Snooping Query Interval 36-11 Enabling IGMP Fast-Leave Processing 36-12 Configuring Source-Specific Multicast Mapping 36-12 CGMP Automatic Detection 36-13 Configuring IGMPv3 Explicit Host Tracking 36-13 Displaying IGMP Snooping Information 36-14 Understanding MVR 36-16 Using MVR in a Multicast Television Application Configuring MVR 36-19 Default MVR Configuration 36-19 MVR Configuration Guidelines and Limitations Configuring MVR Global Parameters 36-20 Configuring MVR Interfaces 36-21 Displaying MVR Information Clearing MVR Counters
37
36-23 36-24 36-17
36-11
36-20
CHAPTER
Configuring IPv4 IGMP Filtering and Router Guard Understanding IGMP Filtering 37-1 IGMP Filtering Overview 37-2 IGMP Filters 37-2 IGMP Filter Precedence 37-4 Filter Hierarchy Example 37-4 Displaying IGMP Filtering 37-5 Clearing IGMP Filtering Statistics
37-1
37-7
Understanding Router Guard 37-7 Router Guard Overview 37-8 Configuring Router Guard 37-8 Displaying Router Guard Configurations 37-9 Displaying Router Guard Interfaces 37-10 Clearing Router Guard Statistics 37-11
xx
OL-13013-06
Contents
CHAPTER
38
Configuring PIM Snooping
38-1 38-1 38-4 38-4
Understanding PIM Snooping
Default PIM Snooping Configuration
PIM Snooping Configuration Guidelines and Restrictions Configuring PIM Snooping 38-5 Enabling PIM Snooping Globally 38-5 Enabling PIM Snooping in a VLAN 38-5 Disabling PIM Snooping Designated-Router Flooding
39
38-6
CHAPTER
Configuring IPv4 Multicast VPN Support
39-1
Understanding MVPN 39-1 MVPN Overview 39-2 Multicast Routing and Forwarding and Multicast Domains Multicast Distribution Trees 39-2 Multicast Tunnel Interfaces 39-5 PE Router Routing Table Support for MVPN 39-6 Multicast Distributed Switching Support 39-6 Hardware-Assisted IPv4 Multicast 39-6 MVPN Configuration Guidelines and Restrictions
39-7
39-2
Configuring MVPN 39-8 Forcing Ingress Multicast Replication Mode (Optional) 39-8 Configuring a Multicast VPN Routing and Forwarding Instance Configuring Multicast VRF Routing 39-15 Configuring Interfaces for Multicast Routing to Support MVPN Sample Configurations for MVPN 39-21 MVPN Configuration with Default MDTs Only 39-21 MVPN Configuration with Default and Data MDTs 39-23
8
39-9
39-19
PART
Quality of Service
40
CHAPTER
Configuring PFC QoS
40-1
Understanding PFC QoS 40-2 Port Types Supported by PFC QoS 40-2 Overview 40-2 Component Overview 40-5 Understanding Classification and Marking 40-14 Policers 40-17 Understanding Port-Based Queue Types 40-20
xxi
Contents
PFC QoS Default Configuration 40-27 PFC QoS Global Settings 40-27 Default Values with PFC QoS Enabled 40-28 Default Values with PFC QoS Disabled 40-50 PFC QoS Configuration Guidelines and Restrictions 40-50 General Guidelines 40-51 Class Map Command Restrictions 40-54 Policy Map Command Restrictions 40-54 Policy Map Class Command Restrictions 40-54 Supported Granularity for CIR and PIR Rate Values 40-54 Supported Granularity for CIR and PIR Token Bucket Sizes 40-55 IP Precedence and DSCP Values 40-56 Configuring PFC QoS 40-56 Enabling PFC QoS Globally 40-57 Enabling Ignore Port Trust 40-58 Configuring DSCP Transparency 40-59 Enabling Queueing-Only Mode 40-59 Enabling Microflow Policing of Bridged Traffic 40-60 Enabling VLAN-Based PFC QoS on Layer 2 LAN Ports 40-61 Enabling Egress ACL Support for Remarked DSCP 40-61 Creating Named Aggregate Policers 40-62 Configuring a PFC QoS Policy 40-65 Configuring Egress DSCP Mutation 40-82 Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports 40-84 Configuring DSCP Value Maps 40-86 Configuring the Trust State of Ethernet LAN Ports 40-90 Configuring Trusted Boundary with Cisco Device Verification 40-91 Configuring the Ingress LAN Port CoS Value 40-92 Configuring Standard-Queue Drop Threshold Percentages 40-93 Mapping QoS Labels to Queues and Drop Thresholds 40-98 Allocating Bandwidth Between Standard Transmit Queues 40-107 Setting the Receive-Queue Size Ratio 40-109 Configuring the Transmit-Queue Size Ratio 40-110 Common QoS Scenarios 40-111 Sample Network Design Overview 40-111 Classifying Traffic from PCs and IP Phones in the Access Layer 40-112 Accepting the Traffic Priority Value on Interswitch Links 40-115 Prioritizing Traffic on Interswitch Links 40-116 Using Policers to Limit the Amount of Traffic from a PC 40-119
xxii
OL-13013-06
Contents
PFC QoS Glossary

41
40-120
CHAPTER
Using AutoQoS
41-1
Understanding AutoQoS 41-1 AutoQoS Support for a Cisco IP Phone 41-2 AutoQoS Support for Cisco IP Communicator 41-2 AutoQoS Support for Marked Traffic 41-2 Using AutoQoS 41-3 AutoQoS Configuration Guidelines and Restrictions Configuring AutoQoS 41-4
42
41-3
CHAPTER
Configuring MPLS QoS Terminology

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

43-2
PART
Security
44
CHAPTER
Configuring Network Security Configuring TCP Intercept
44-1 44-2
Configuring MAC Address-Based Traffic Blocking

44-2
Configuring Unicast Reverse Path Forwarding Check 44-2 Understanding PFC3 Unicast RPF Check Support 44-2 Unicast RPF Check Guidelines and Restrictions 44-3 Configuring Unicast RPF Check 44-4
45
CHAPTER
Using AutoSecure
45-1
Understanding AutoSecure 45-1 Benefits of AutoSecure 45-2 Securing the Management Plane
45-2
xxiv
OL-13013-06
Contents
Securing the Forwarding Plane 45-5 AutoSecure Guidelines and Restrictions Configuring AutoSecure 45-6 Using the AutoSecure Command 45-7 Configuring Additional Security 45-8 Verifying AutoSecure 45-8 AutoSecure Configuration Example
46
45-9
45-6
CHAPTER
Understanding Cisco IOS ACL Support ACL Support in Hardware and Software Policy-Based ACLs 46-3 Understanding PBACLs 46-3 PBACL Guidelines and Restrictions Configuring PBACL 46-4 Configuring IPv6 Address Compression Optimized ACL Logging 46-8 Understanding OAL 46-8 OAL Guidelines and Restrictions Configuring OAL 46-8
46-1 46-1 46-3
Cisco IOS ACL Configuration Guidelines and Restrictions
46-4
46-6
46-8
Guidelines and Restrictions for Using Layer 4 Operators in ACLs Determining Layer 4 Operation Usage 46-10 Determining Logical Operation Unit Usage 46-11
47
46-10
CHAPTER
Configuring Cisco TrustSec 47-1 Hardware Supported 47-3 Configuring Port ACLs and VLAN ACLs Understanding ACLs 48-1 Understanding ACLs 48-2 Understanding VACLs 48-2 Understanding Port ACLs 48-3 PACL and VACL Interactions 48-4 Configuring PACLs 48-7 PACL Configuration Guidelines 48-8 Configuring IP and MAC ACLs on a Layer 2 Interface 48-8 Configuring Access-group Mode on Layer 2 Interface 48-9 Applying ACLs to a Layer 2 Interface 48-9
48-1
CHAPTER
48
xxv
Contents
Applying ACLs to a Port Channel 48-10 Displaying an ACL Configuration on a Layer 2 Interface
48-10
Configuring VACLs 48-11 VACL Configuration Guidelines 48-11 Defining a VLAN Access Map 48-13 Configuring a Match Clause in a VLAN Access Map Sequence 48-13 Configuring an Action Clause in a VLAN Access Map Sequence 48-14 Applying a VLAN Access Map 48-15 Verifying VLAN Access Map Configuration 48-15 VLAN Access Map Configuration and Verification Examples 48-15 Configuring a Capture Port 48-16 Configuring MAC PBF 48-17 Configuring VACL Logging
49
48-19
CHAPTER
Configuring Denial of Service Protection Understanding DoS Protection

49-2
49-1
DoS Protection Default Configuration
49-13 49-14
DoS Protection Configuration Guidelines and Restrictions Monitoring Packet Drop Statistics 49-15 Displaying Rate-Limiter Information 49-17 Configuring Sticky ARP
50
49-18
CHAPTER
Configuring Control Plane Policing Understanding Control Plane Policing CoPP Default Configuration Configuring CoPP Monitoring CoPP
50-3 50-4 50-2
50-1 50-1
CoPP Configuration Guidelines and Restrictions
50-2
Defining Traffic Classification 50-5 Traffic Classification Overview 50-6 Traffic Classification Guidelines 50-7 Sample Basic ACLs for CoPP Traffic Classification
51
50-7
CHAPTER
Configuring DHCP Snooping
51-1
Understanding DHCP Snooping 51-1 Overview of DHCP Snooping 51-2 Trusted and Untrusted Sources 51-2 DHCP Snooping Binding Database 51-3
xxvi
OL-13013-06
Contents
Packet Validation 51-3 DHCP Snooping Option-82 Data Insertion 51-3 Overview of the DHCP Snooping Database Agent Default Configuration for DHCP Snooping
51-6
51-5
DHCP Snooping Configuration Restrictions and Guidelines DHCP Snooping Configuration Restrictions 51-7 DHCP Snooping Configuration Guidelines 51-7 Minimum DHCP Snooping Configuration 51-8
51-7
Configuring DHCP Snooping 51-9 Enabling DHCP Snooping Globally 51-9 Enabling DHCP Option-82 Data Insertion 51-10 Enabling the DHCP Option-82 on Untrusted Port Feature 51-10 Enabling DHCP Snooping MAC Address Verification 51-11 Enabling DHCP Snooping on VLANs 51-11 Configuring the DHCP Trust State on Layer 2 LAN Interfaces 51-12 Configuring Spurious DHCP Server Detection 51-13 Configuring DHCP Snooping Rate Limiting on Layer 2 LAN Interfaces Configuring the DHCP Snooping Database Agent 51-14 Configuration Examples for the Database Agent 51-14 Displaying a Binding Table 51-18
52
51-13
CHAPTER
Configuring IP Source Guard
52-1
Overview of IP Source Guard 52-1 IP Source Guard Interaction with VLAN-Based Features Channel Ports 52-2 Trunk Ports 52-2 Layer 2 and Layer 3 Port Conversion 52-2 IP Source Guard and Voice VLAN 52-2 IP Source Guard and Web-Based Authentication 52-2 IP Source Guard Restrictions 52-3 Configuring IP Source Guard on the Switch Displaying IP Source Guard Information Displaying IP Source Binding Information
53
52-3 52-4 52-6
52-2
CHAPTER
Configuring Dynamic ARP Inspection
53-1
Understanding DAI 53-1 Understanding ARP 53-2 Understanding ARP Spoofing Attacks 53-2 Understanding DAI and ARP Spoofing Attacks
53-2
xxvii
Contents
Interface Trust States and Network Security 53-3 Rate Limiting of ARP Packets 53-4 Relative Priority of ARP ACLs and DHCP Snooping Entries Logging of Dropped Packets 53-5 Default DAI Configuration
53-5 53-6
53-4
DAI Configuration Guidelines and Restrictions
Configuring DAI 53-6 Enabling DAI on VLANs 53-7 Configuring the DAI Interface Trust State 53-8 Applying ARP ACLs for DAI Filtering 53-8 Configuring ARP Packet Rate Limiting 53-9 Enabling DAI Error-Disabled Recovery 53-10 Enabling Additional Validation 53-11 Configuring DAI Logging 53-12 Displaying DAI Information 53-14 DAI Configuration Samples 53-15 Sample One: Two Switches Support DAI 53-16 Sample Two: One Switch Supports DAI 53-20
54
CHAPTER
Configuring Traffic Storm Control
54-1 54-1 54-3 54-3
Understanding Traffic Storm Control
Default Traffic Storm Control Configuration Configuration Guidelines and Restrictions
Configuring Traffic Storm Control 54-4 Enabling Traffic Storm Control 54-4 Configuring the Traffic Storm Control Shutdown Mode Configuring Traffic Storm Control SNMP Traps 54-6 Displaying Traffic Storm Control Settings
55
54-7
54-6
CHAPTER
Configuring Unknown Unicast and Multicast Flood Control Understanding Unknown Traffic Flood Control Configuring UUFB or UMFB Configuring UUFRL
55-2 55-2 55-1
55-1
CHAPTER
56
Configuring Network Admission Control Understanding NAC 56-1 NAC Overview 56-2 NAC Device Roles 56-3
56-1
xxviii
OL-13013-06
Contents
AAA Down Policy 56-4 NAC IP Validation 56-4 NAC and Switchover 56-12 Configuring NAC 56-12 Default NAC Configuration 56-12 NAC IP Guidelines, Limitations, and Restrictions Configuring NAC IP Validation 56-14 Configuring EAPoUDP 56-18 Configuring Identity Profiles and Policies 56-18 Configuring NAC High Availability 56-19 Configuring a NAC AAA Down Policy 56-20 Monitoring and Maintaining NAC 56-23 Clearing Table Entries 56-23 Displaying NAC Information 56-23
57
56-12
CHAPTER
Configuring IEEE 802.1X Port-Based Authentication
57-1
Understanding 802.1X Port-Based Authentication 57-1 Understanding 802.1X Device Roles 57-2 Understanding the Port-based Authentication Process 57-3 Authentication Initiation and Message Exchange 57-6 Ports in Authorized and Unauthorized States 57-8 802.1X Host Modes 57-9 Using 802.1X Authentication with DHCP Snooping 57-11 Understanding 802.1X Accounting 57-12 Using 802.1X Authentication with VLAN Assignment 57-13 Using Multiple VLANs and VLAN User Distribution with VLAN Assignment 57-14 Using 802.1X Authentication with Guest VLAN 57-15 Using 802.1X Authentication with Restricted VLAN 57-16 Using 802.1X Authentication with Inaccessible Authentication Bypass 57-17 Using 802.1X Authentication with Voice VLAN Ports 57-18 Using 802.1X Authentication with Port Security 57-19 Using 802.1X Authentication with ACL Assignments and Redirect URLs 57-19 Using 802.1X Authentication with Port Descriptors 57-22 Using 802.1X Authentication with MAC Authentication Bypass 57-22 Using Network Admission Control Layer 2 IEEE 802.1X Validation 57-23 Using RADIUS Change of Authorization 57-24 Using 802.1X Authentication with Wake-on-LAN 57-25 Understanding MAC Move 57-25 Understanding MAC Replace 57-26
xxix
Contents
Understanding 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT) 57-26 802.1X Authentication Feature Configuration Guidelines 57-28 802.1X Authentication 57-28 802.1X Host Mode 57-29 VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass MAC Authentication Bypass 57-31 Web-Based Authentication 57-32 Configuring 802.1X Port-Based Authentication 57-32 Default 802.1X Port-Based Authentication Configuration 57-33 Enabling 802.1X Authentication 57-34 Configuring Switch-to-RADIUS-Server Communication 57-36 Configuring 802.1X Authenticator Host Mode 57-37 Enabling Fallback Authentication 57-39 Enabling Periodic Reauthentication 57-41 Manually Reauthenticating the Client Connected to a Port 57-42 Initializing Authentication for the Client Connected to a Port 57-42 Removing 802.1X Client Information 57-43 Clearing Authentication Sessions 57-43 Changing 802.1X Timeouts 57-43 Setting the Switch-to-Client Frame Retransmission Number 57-45 Setting the Reauthentication Number 57-46 Configuring IEEE 802.1X Accounting 57-46 Configuring VLAN User Distribution 57-47 Configuring a Guest VLAN 57-48 Configuring a Restricted VLAN 57-49 Configuring the Inaccessible Authentication Bypass Feature 57-51 Configuring MAC Authentication Bypass 57-54 Configuring NAC Layer 2 IEEE 802.1X Validation 57-55 Configuring NAC Agentless Audit Support 57-56 Configuring the Switch for DACLs or Redirect URLs 57-57 Configuring a Port to Ignore CoA Commands 57-58 Configuring 802.1X Authentication with WoL 57-58 Disabling 802.1X Authentication on the Port 57-59 Resetting the 802.1X Configuration to the Default Values 57-59 Configuring an Authenticator and a Supplicant Switch with NEAT 57-60 Displaying Authentication Status and Information 57-61 Displaying 802.1X Status 57-62 Displaying Authentication Methods and Status 57-63 Displaying MAC Authentication Bypass Status 57-66
57-30
xxx
OL-13013-06
Contents
Enabling MAC Move 57-67 Enabling MAC Replace 57-67

58
CHAPTER
Configuring Web-Based Authentication
58-1
Understanding Web-Based Authentication 58-1 Device Roles 58-2 Host Detection 58-3 Session Creation 58-3 Authentication Process 58-3 AAA Fail Policy 58-4 Customization of the Authentication Proxy Web Pages 58-4 Web-based Authentication Interactions with Other Features 58-5 Configuring Web-Based Authentication 58-6 Default Web-Based Authentication Configuration 58-7 Web-based Authentication Configuration Guidelines and Restrictions Web-based Authentication Configuration Task List 58-8 Configuring the Authentication Rule and Interfaces 58-8 Configuring AAA Authentication 58-9 Configuring Switch-to-RADIUS-Server Communication 58-9 Configuring the HTTP Server 58-11 Configuring an AAA Fail Policy 58-13 Configuring the Web-based Authentication Parameters 58-14 Removing Web-based Authentication Cache Entries 58-15 Displaying Web-Based Authentication Status
59
58-15
58-7
CHAPTER
Configuring Port Security
59-1
Understanding Port Security 59-1 Port Security with Dynamically Learned and Static MAC Addresses Port Security with Sticky MAC Addresses 59-2 Port Security with IP Phones 59-3 Default Port Security Configuration
59-3 59-3
59-2
Port Security Guidelines and Restrictions
Configuring Port Security 59-5 Enabling Port Security 59-5 Configuring the Port Security Violation Mode on a Port 59-6 Configuring the Port Security Rate Limiter 59-7 Configuring the Maximum Number of Secure MAC Addresses on a Port Enabling Port Security with Sticky MAC Addresses on a Port 59-9 Configuring a Static Secure MAC Address on a Port 59-10
59-9
xxxi
Contents
Configuring Secure MAC Address Aging on a Port Displaying Port Security Settings
10
59-12
59-11
PART
NetFlow
60
CHAPTER
Configuring NetFlow
60-1 60-1 60-2 60-2 60-4 60-4 60-5 60-6
Understanding NetFlow NetFlow Overview NetFlow on the PFC NetFlow on the RP NetFlow Features
Default NetFlow Configuration
NetFlow Configuration Guidelines and Restrictions Configuring NetFlow 60-6 Configuring NetFlow on the PFC 60-7 Configuring NetFlow Features 60-10
61
CHAPTER
Configuring NDE
61-1
Understanding NDE 61-2 NDE Overview 61-2 NDE on the RP 61-2 NDE on the PFC 61-2 Default NDE Configuration
61-10 61-10
NDE Configuration Guidelines and Restrictions
Configuring NDE 61-10 Configuring NDE on the PFC 61-11 Configuring NDE on the RP 61-13 Enabling NDE for Ingress-Bridged IP Traffic 61-14 Displaying the NDE Address and Port Configuration Configuring NDE Flow Filters 61-16 Displaying the NDE Configuration 61-17
11
61-15
PART
Network Management
62
CHAPTER
Configuring Call Home
62-1 62-2 62-3
Understanding Call Home Obtaining Smart Call Home Default Settings

62-3
xxxii
OL-13013-06
Contents
Configuring Call Home 62-3 Configuration Overview 62-4 Configuring Customer Contact Information 62-4 Configuring Destination Profiles 62-5 Subscribing to Alert Groups 62-13 Enabling Call Home 62-16 Testing Call Home Communications 62-16 Configuring and Enabling Smart Call Home 62-19 Configuring the Smart Call Home Service 62-20 Enabling the Smart Call Home Service 62-20 Declare and Authenticate a CA Trustpoint 62-21 Start Smart Call Home Registration 62-22 Displaying Call Home Configuration Information Alert Group Trigger Events and Commands
62-26 62-23
Message Contents 62-33 Sample Syslog Alert Notification in Long-Text Format 62-37 Sample Syslog Alert Notification in XML Format 62-37
63
CHAPTER
Using the System Event Archive
63-1 63-1
Understanding the System Event Archive Displaying the SEA Logging System Copying the SEA To Another Device
64
63-2 63-3
CHAPTER
Backplane Traffic Monitoring Default Configuration

64-2
64-1 64-1
Understanding Traffic Monitoring
Configuration Guidelines and Restrictions Configuring Backplane Traffic Monitoring

65
64-2 64-2
CHAPTER
Configuring Local SPAN, RSPAN, and ERSPAN
65-1
Understanding Local SPAN, RSPAN, and ERSPAN 65-1 Local SPAN, RSPAN, and ERSPAN Overview 65-2 Local SPAN, RSPAN, and ERSPAN Sources 65-5 Local SPAN, RSPAN, and ERSPAN Destinations 65-7 Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions General Guidelines and Restrictions 65-8 Feature Incompatibilities 65-8 Local SPAN, RSPAN, and ERSPAN Session Limits 65-10
65-7
xxxiii
Contents
Local SPAN, RSPAN, and ERSPAN Interface Limits 65-10 Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions 65-10 VSPAN Guidelines and Restrictions 65-11 RSPAN Guidelines and Restrictions 65-12 ERSPAN Guidelines and Restrictions 65-13 Distributed Egress SPAN Mode Guidelines and Restrictions 65-14 Configuring Local SPAN, RSPAN, and ERSPAN 65-14 Local SPAN, RSPAN, and ERSPAN Default Configuration 65-15 Configuring a Destination as an Unconditional Trunk (Optional) 65-15 Configuring Destination Trunk VLAN Filtering (Optional) 65-16 Configuring Destination Port Permit Lists (Optional) 65-17 Configuring the Egress SPAN Mode (Optional) 65-18 Configuring Local SPAN 65-19 Configuring RSPAN 65-23 Configuring ERSPAN 65-29 Configuring Source VLAN Filtering in Global Configuration Mode 65-33 Verifying the Configuration 65-34 Configuration Examples 65-34
66
CHAPTER
Configuring SNMP IfIndex Persistence Understanding SNMP IfIndex Persistence
66-1 66-1
Configuring SNMP IfIndex Persistence 66-2 Enabling SNMP IfIndex Persistence Globally 66-2 Disabling SNMP IfIndex Persistence Globally 66-2 Enabling and Disabling SNMP IfIndex Persistence on Specific Interfaces 66-3 Clearing SNMP IfIndex Persistence Configuration from a Specific Interface 66-3
67
CHAPTER
Using Top-N Reports
67-1
Understanding Top-N Reports 67-1 Top-N Reports Overview 67-1 Understanding Top-N Reports Operation Using Top-N Reports 67-2 Enabling Top-N Reports Creation Displaying Top-N Reports 67-3 Clearing Top-N Reports 67-4
68
67-3
67-2
CHAPTER
Using the Layer 2 Traceroute Utility Usage Guidelines

68-2
68-1 68-1
Understanding the Layer 2 Traceroute Utility
xxxiv
OL-13013-06
Contents
Using the Layer 2 Traceroute Utility

69
68-3
CHAPTER
Using the Mini Protocol Analyzer
69-1 69-1
Understanding How the Mini Protocol Analyzer Works Configuring the Mini Protocol Analyzer 69-2 Filtering the Packets to be Captured 69-3 Starting and Stopping a Capture
69-4 69-6
Displaying and Exporting the Capture Buffer
Mini Protocol Analyzer Configuration, Operation, and Display Examples General Configuration Examples 69-7 Filtering Configuration Examples 69-8 Operation Examples 69-9 Display Examples 69-9
12
69-7
PART
Appendixes
A
APPENDIX
Online Diagnostic Tests
A-1
Global Health-Monitoring Tests A-2 TestEARLInternalTables A-2 TestSPRPInbandPing A-3 TestScratchRegister A-3 TestMacNotification A-4 TestErrorCounterMonitor A-4 TestLtlFpoeMemoryConsistency A-5 TestMgmtPortsLoopback A-5 TestDataPortLoopback A-6 Per-Port Tests A-6 TestNonDisruptiveLoopback A-7 TestLoopback A-7 TestActiveToStandbyLoopback A-8 TestUnusedPortLoopback A-8 TestTransceiverIntegrity A-9 TestNetflowInlineRewrite A-9 TestPortTxMonitoring A-10 TestSnrMonitoring A-10 TestDCPLoopback A-11 TestCCPLoopback A-11 TestNPLoopback A-12 TestMediaLoopback A-13
xxxv
Contents
PFC Layer 2 Forwarding Engine Tests A-13 TestNewIndexLearn A-13 TestDontConditionalLearn A-14 TestBadBpduTrap A-14 TestMatchCapture A-15 TestStaticEntry A-15 DFC Layer 2 Forwarding Engine Tests A-16 TestDontLearn A-16 TestNewLearn A-16 TestIndexLearn A-17 TestConditionalLearn A-18 TestTrap A-18 TestBadBpdu A-19 TestProtocolMatchChannel A-19 TestCapture A-20 TestStaticEntry A-20 PFC Layer 3 Forwarding Engine Tests TestFibDevices A-21 TestIPv4FibShortcut A-22 TestIPv6FibShortcut A-22 TestMPLSFibShortcut A-23 TestNATFibShortcut A-23 TestL3Capture2 A-24 TestAclPermit A-24 TestAclDeny A-25 TestNetflowShortcut A-25 TestQoS A-26 DFC Layer 3 Forwarding Engine Tests TestFibDevices A-26 TestIPv4FibShortcut A-27 TestIPv6FibShortcut A-28 TestMPLSFibShortcut A-28 TestNATFibShortcut A-29 TestL3Capture2 A-29 TestAclPermit A-30 TestAclDeny A-30 TestQoS A-31 TestNetflowShortcut A-31 TestAclFpgaMonitor A-32
A-21
A-26
xxxvi
OL-13013-06
Contents
Replication Engine Tests A-32 TestL3VlanMet A-32 TestIngressSpan A-33 TestEgressSpan A-33 Fabric Tests A-34 TestFabricSnakeForward A-34 TestFabricSnakeBackward A-34 TestSynchedFabChannel A-35 TestFabricCh0Health A-36 TestFabricCh1Health A-36 Exhaustive Memory Tests A-36 TestFibTcamSSRAM A-37 TestAsicMemory A-37 TestAclQosTcam A-38 TestNetflowTcam A-38 TestQoSTcam A-39 IPSEC Services Modules Tests A-39 TestIPSecClearPkt A-39 TestHapiEchoPkt A-40 TestIPSecEncryptDecryptPkt A-40 Stress Tests A-41 TestTrafficStress A-41 TestEobcStressPing A-41 TestMicroburst A-42 Critical Recovery Tests A-42 TestL3HealthMonitoring A-42 TestTxPathMonitoring A-43 TestSynchedFabChannel A-43 General Tests A-44 ScheduleSwitchover A-44 TestFirmwareDiagStatus A-44 TestCFRW A-45
B
APPENDIX
Acronyms
B-1
INDEX
xxxvii
Contents
xxxviii
OL-13013-06
Preface
This preface describes who should read the Cisco IOS Software Configuration Guide, Release 12.2SX , and its document conventions.
Audience
This guide is for experienced network administrators who are responsible for configuring and maintaining the switches supported in Cisco IOS Release 12.2SX.
Related Documentation
The following publications are available for Cisco IOS Release 12.2SX:

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.2SX Cisco IOS Configuration Guides and Command References: http://www.cisco.com/en/US/products/hw/switches/ps708/tsd_products_support_series_home.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 Description Commands, command options, and keywords are in boldface. Arguments for which you supply values are in italics.
xxxix
Preface
Convention [ ] {x|y|z} [x|y|z] string

screen
Description 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 font. Arguments for which you supply values are in italic screen font.
This pointer highlights an important line of text in an example.
boldface screen
font
italic screen
font
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, Obtaining Support, and Security Guidelines

For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, 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
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
xl
OL-13013-06
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-5 Software Features Supported in Hardware by the PFC and DFC, page 1-6
Tip
Supported Hardware and Software

For complete information about the chassis, modules, and software features supported by Cisco IOS Release 12.2SX, see the Release Notes for Cisco IOS Release 12.2SX: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/ol_14271.html These sections describe the ports and flash memory devices on the supervisor engines:

Understanding Supervisor Engine 720-10GE Memory Devices and Ports, page 1-1 Understanding Supervisor Engine 720 Memory Devices and Ports, page 1-2 Understanding Supervisor Engine 32 Memory Devices and Ports, page 1-4 Understanding ME6500 Flash Memory Devices and Ports, page 1-5
Understanding Supervisor Engine 720-10GE Memory Devices and Ports

These sections describe the Supervisor Engine 720-10GE memory devices and ports:

Supervisor Engine 720-10GE Flash Memory Devices, page 1-2 Supervisor Engine 720-10GE Ports, page 1-2
1-1
Chapter 1 Supported Hardware and Software
Product Overview
Supervisor Engine 720-10GE Flash Memory Devices

The Supervisor Engine 720-10GE has these flash memory devices:
disk0: (active) and slavedisk0: (standby):

External CompactFlash Type II slots For CompactFlash Type II flash PC cards sold by Cisco Systems, Inc.
sup-bootdisk: (active) and slavesup-bootdisk: (standby):

Switch processor (SP) 1-GB internal CompactFlash flash memory From SP ROMMON, it is bootdisk: Not accessible from route processor (RP) ROMMON
bootflash: (active) and slave-bootflash: (standby):

RP 64-MB internal flash memory Not accessible from SP ROMMON
Supervisor Engine 720-10GE Ports

The Supervisor Engine 720-10GE has these ports:

Console portEIA/TIA-232 (RS-232) port Ports 1 and 2

Gigabit Ethernet SFP (fiber or 10/100/1000 Mbps RJ-45) Fast Ethernet SFP
Port 310/100/1000 Mbps RJ-45 Ports 4 and 510-Gigabit Ethernet X2
Note
The 1-Gigabit Ethernet ports and the 10-Gigabit Ethernet ports have the same QoS port architecture (2q4t/1p3q4t) unless you disable the 1-Gigabit Ethernet ports with the mls qos 10g-only global configuration command. With the 1-Gigabit Ethernet ports disabled, the QoS port architecture of the 10-Gigabit Ethernet ports is 8q4t/1p7q4t. See the Configuring Optional Interface Features section on page 9-6 for information about configuring the ports.
Understanding Supervisor Engine 720 Memory Devices and Ports

These sections describe the Supervisor Engine 720 memory devices and ports:

Supervisor Engine 720 Flash Memory Devices, page 1-3 Configuring Supervisor Engine 720 Ports, page 1-3
1-2
OL-13013-06
Chapter 1
Product Overview Supported Hardware and Software
Supervisor Engine 720 Flash Memory Devices

The Supervisor Engine 720 has these flash memory devices:
disk0: and disk1: (active) and slavedisk0: and slavedisk1: (standby):

sup-bootflash: (active) and slavesup-bootflash: (standby):

Switch processor (SP) 64-MB internal flash memory From SP ROMMON, it is bootflash: Not accessible from route processor (RP) ROMMON
With WS-CF-UPG=, sup-bootdisk: (active) and slavesup-bootflash: (standby):

SP 512-MB internal CompactFlash flash memory From SP ROMMON, it is bootdisk: Not accessible from RP ROMMON See this publication for more information:
http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/hardware/Config_Notes/78_1727 7.html

Configuring Supervisor Engine 720 Ports

The Supervisor Engine 720 has these ports:

Port 1Small form-factor pluggable (SFP); no unique configuration options. Port 2 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}
Purpose Selects the Ethernet port to be configured. Selects the connector to use.
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
See the Configuring Optional Interface Features section on page 9-6 for more information about configuring the ports.
1-3
Chapter 1 Supported Hardware and Software
Product Overview
Understanding Supervisor Engine 32 Memory Devices and Ports

These sections describe the Supervisor Engine 32 memory devices and ports:

Supervisor Engine 32 Flash Memory Devices, page 1-4 Supervisor Engine 32 Ports, page 1-4
Note
Supervisor Engine 32 does not support switch fabric connectivity.
Supervisor Engine 32 Flash Memory Devices

The Supervisor Engine 32 has these flash memory devices:
disk0: (active) and slavedisk0: (standby):

sup-bootdisk: (active) and slavesup-bootflash: (standby):

Switch processor (SP) 256-MB internal CompactFlash flash memory From SP ROMMON, it is bootdisk: Not accessible from route processor (RP) ROMMON

Supervisor Engine 32 Ports

The Supervisor Engine 32 has these ports:

Console portEIA/TIA-232 (RS-232) port Two Universal Serial Bus (USB) 2.0 portsNot currently enabled WS-SUP32-GE-3B:
Ports 1 through 8Small form-factor pluggable (SFP) Port 910/100/1000 Mbps RJ-45
WS-SUP32-10GE:
Ports 1 and 210-Gigabit Ethernet XENPAK Port 310/100/1000 Mbps RJ-45
See the Configuring Optional Interface Features section on page 9-6 for information about configuring the ports.
1-4
OL-13013-06
Chapter 1
Product Overview User Interfaces
Understanding ME6500 Flash Memory Devices and Ports

These sections describe the Cisco ME6500 series Ethernet switch memory devices and ports:

ME6500 Flash Memory Devices, page 1-5 ME6500 Ports, page 1-5
ME6500 Flash Memory Devices

The ME6500 has these flash memory devices:
disk0:
One external CompactFlash Type II slot Supports CompactFlash Type II flash PC cards
sup-bootflash:
Switch processor (SP) 128 MB internal CompactFlash flash memory From SP ROMMON, it is bootflash: Not accessible from route processor (RP) ROMMON
bootflash:
ME6500 Ports
The ME6500 has these ports:
ME-C6524GS-8S and ME-C6524GT-8S

Ports 2532: Gigabit Ethernet SFP Requires Gigabit Ethernet SFPs
ME-C6524GS-8S
Ports 124: Gigabit Ethernet SFP Requires Gigabit Ethernet SFPs
ME-C6524GT-8SPorts 124: 10/100/1000 Mbps RJ-45 Ethernet ports
User Interfaces
Release 12.2SX supports configuration using the following interfaces:

CLISee Chapter 2, Command-Line Interfaces. SNMPSee 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
1-5
Chapter 1 Software Features Supported in Hardware by the PFC and DFC
Product Overview
Cisco IOS web browser interfaceSee 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
Software Features Supported in Hardware by the PFC and DFC

The PFC3 and DFC3 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 route processor (RP).
Except on MPLS interfaces, reflexive ACL flows after the first packet in a session is processed
in software on the RP
Dynamic ACL flows
Note
Idle timeout is processed in software on the RP.
For more information about PFC and DFC support for ACLs, see Chapter 46, Understanding Cisco IOS ACL Support. For complete information about configuring 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/12_2/security/configuration/guide/scfacls.html

Bidirectional Protocol Independent Multicast (PIM) in hardwareSee Understanding IPv4 Bidirectional PIM section on page 35-9. IPv4 Multicast over point-to-point generic route encapsulation (GRE) TunnelsSee the publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/interface/configuration/guide/icflogin.html Multiple-path Unicast Reverse Path Forwarding (RPF) CheckTo configure Unicast RPF Check, see the Configuring Unicast Reverse Path Forwarding Check section on page 44-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 not supported in PFC3A 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 RP to be processed in software. (CSCdz51590) To configure NAT, see 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-6
OL-13013-06
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 RP, 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)
NetFlow AggregationSee this URL: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/netfl ow.html#NetFlow_Aggregation
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, see 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 RP address falls within the range of a PBR ACL, traffic addressed to the RP is policy routed in hardware instead of being forwarded to the RP. To prevent policy routing of traffic addressed to the RP, configure PBR ACLs to deny traffic addressed to the RP.
Except on MPLS interfaces, TCP interceptTo configure TCP intercept, see the Configuring TCP Intercept section on page 44-2.
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 RP. 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, see 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
1-7
Chapter 1 Software Features Supported in Hardware by the PFC and DFC
Product Overview
To configure the tunnel tos and tunnel ttl commands, see this publication for more information: http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/12s_tos.html 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. Failure to use unique source addresses may result in control plane failures when software path congestion occurs. (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. Other PFC versions support PFC QoS features on tunnel interfaces. The RP 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, and encryption.
VLAN ACLs (VACLs)To configure VACLs, see Chapter 48, Configuring Port ACLs and VLAN ACLs.
1-8
OL-13013-06
PA R T
Configuration Fundamentals
C H A P T E R
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/122sxmcl/12_2sx_mcl_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
Tip

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
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
Step 1 Step 2 Step 3 Step 4
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 29-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-13013-06
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.
Step 3 Step 4 Step 5
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-13013-06
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.
Router(config)#
Interface configuration
Router(config-if)#
Console configuration
From global configuration mode, Router(config-line)# enter the line console 0 command.
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?
2-5
Chapter 2 Securing the CLI
collect
configure
connect
copy
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
2-6
OL-13013-06
Chapter 2
Command-Line Interfaces ROM-Monitor Command-Line Interface
Configuring a secure connection with SSH or HTTPS 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/sec_user_services/configuration/guide/sec_cfg_secure_shell _ps6017_TSD_Products_Configuration_Guide_Chapter.html 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/12_2t/12_2t15/feature/guide/ftsslsht.html 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/sec_user_services/configuration/guide/sec_secure_copy_ps 6017_TSD_Products_Configuration_Guide_Chapter.html
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/sec_user_services/configuration/guide/12_2sx/sec_securing_use r_services_12.2sx_book.html
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-13013-06
C H A P T E R

This chapter describes how to configure and apply smart port macros. Release 12.2(33)SXH and later releases support smart port macros.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html
Tip

Understanding Smart Port Macros, page 3-1 Configuring Smart Port Macros, page 3-2 Displaying Smart Port Macros, page 3-16
Understanding Smart Port Macros

These sections describe smart port macros:

Understanding Cisco-Provided Smart Port Macros, page 3-1 Understanding User-Created Smart Port Macros, page 3-2
Understanding Cisco-Provided Smart Port Macros

There are Cisco-provided smart port macros embedded in the switch software (see Table 3-1). You can display these macros and the commands they contain by using the show parser macro user EXEC command.
3-1
Chapter 3 Configuring Smart Port Macros
Table 3-1
Cisco-Provided Smart Port Macros
Macro Name cisco-global cisco-desktop cisco-phone
Description Use this global configuration macro to enable load balancing across VLANs, provide rapid convergence of spanning-tree instances and to enable port error recovery. Use this interface configuration macro for increased network security and reliability when connecting a desktop device, such as a PC, to a switch port. Use this interface configuration macro when connecting a desktop device such as a PC with a Cisco IP phone to a switch port. This macro is an extension of the cisco-desktop macro and provides the same security and resiliency features, but with the addition of dedicated voice VLANs to ensure proper treatment of delay-sensitive voice traffic. Use this interface configuration macro for Layer 2 connections between devices like switches and routers. Use this interface configuration macro for Layer 3 connections between devices like switches and routers.
cisco-switch cisco-router
Cisco also provides a collection of pretested, Cisco-recommended baseline configuration templates for Catalyst switches. The online reference guide templates provide the CLI commands that you can use to create smart port macros based on the usage of the port. You can use the configuration templates to create smart port macros to build and deploy Cisco-recommended network designs and configurations.
Understanding User-Created Smart Port Macros

Smart port macros provide a convenient way to save and share common configurations. You can use smart port macros to enable features and settings based on the location of a switch in the network and for mass configuration deployments across the network. Each smart port macro is a user-defined set of Cisco IOS CLI commands. When you apply a smart port macro on an interface, the CLI commands within the macro are configured on the interface. When the macro is applied to an interface, the existing interface configurations are not lost. The new commands are added to the interface and are saved in the running configuration file.

Smart Port Macro Default Configuration, page 3-2 Smart Port Macro Configuration Guidelines, page 3-3 Applying the Cisco-Provided Smart Port Macros, page 3-4 Configuring User-Created Smart Port Macros, page 3-13
Smart Port Macro Default Configuration

This example shows how to list the Cisco-provided smart port macros:
Router# show parser macro brief | include default default global : cisco-global
3-2
OL-13013-06
Chapter 3
Configuring Smart Port Macros Configuring Smart Port Macros
default default default default
interface: interface: interface: interface:
cisco-desktop cisco-phone cisco-switch cisco-router
There are no smart port macros applied to any interfaces.
Smart Port Macro Configuration Guidelines

These section describe the smart port macro configuration guidelines:
You can display all of the macros on the switch by using the show parser macro user EXEC command. Display the contents of a specific macro by using the show parser macro name macro-name user EXEC command. A macro cannot be edited. If the name following the macro name command is an existing macros name, that macro is replaced by the new macro. If a description already exists for a macro, the macro description command appends any description that you enter to the existing description; it does not replace it. The entered descriptions are separated by the pipe (|) character. The maximum macro description length is 256 characters. When the description string becomes longer than 256 characters, the oldest descriptions are deleted to make room for new ones. User-created recursive macros are not supported. You cannot define a macro that calls another macro. Each user-created macro can have up to three keyword-value pairs. A macro definition can contain up to 3,000 characters. Line endings count as two characters. When creating a macro, do not use the exit or end commands or change the command mode by using interface interface-id. This could cause commands that follow exit, end, or interface interface-id to execute in a different command mode. When creating a macro, all CLI commands should be in the same configuration mode. When creating a macro that requires the assignment of unique values, use the parameter value keywords to designate values specific to the interface. Keyword matching is case sensitive. All matching occurrences of the keyword are replaced with the corresponding value. Any full match of a keyword, even if it is part of a larger string, is considered a match and is replaced by the corresponding value. Macro names are case sensitive. For example, the commands macro name Sample-Macro and macro name sample-macro will result in two separate macros. Some macros might contain keywords that require a parameter value. You can use the macro global apply macro-name ? global configuration command or the macro apply macro-name ? interface configuration command to display a list of any required values in the macro. If you apply a macro without entering the keyword values, the commands are invalid and are not applied. When a macro is applied globally to a switch or to a switch interface, the existing configuration on the interface is retained. This is helpful when applying an incremental configuration. If you modify a macro definition by adding or deleting commands, the changes are not reflected on the interface where the original macro was applied. You need to reapply the updated macro on the interface to apply the new or changed commands.
3-3
You can use the macro global trace macro-name global configuration command or the macro trace macro-name interface configuration command to apply and debug a macro to find any syntax or configuration errors. If a command fails because of a syntax error or a configuration error, the macro continues to apply the remaining commands. Some CLI commands are specific to certain interface types. If a macro is applied to an interface that does not accept the configuration, the macro will fail the syntax check or the configuration check, and the switch will return an error message. Applying a macro to an interface range is the same as applying a macro to a single interface. When you use an interface range, the macro is applied sequentially to each interface within the range. If a macro command fails on one interface, it is still applied to the remaining interfaces. When you apply a macro to a switch or a switch interface, the macro name is automatically added to the switch or interface. You can display the applied commands and macro names by using the show running-config user EXEC command.
Applying the Cisco-Provided Smart Port Macros

These sections describe how to apply the Cisco-provided smart port macros:

Using the cisco-global Smart Port Macro, page 3-4 Using the cisco-desktop Smart Port Macro, page 3-5 Using the cisco-phone Smart Port Macro, page 3-7 Using the cisco-switch Smart Port Macro, page 3-9 Using the cisco-router Smart Port Macro, page 3-11
Using the cisco-global Smart Port Macro

These sections describe how to apply the cisco-global smart port macro:

Displaying the Contents of the cisco-global Smart Port Macro, page 3-4 Applying the cisco-global Smart Port Macro, page 3-5
Displaying the Contents of the cisco-global Smart Port Macro

This example shows how to display the contents of the cisco-global smart port macro:
Router# show parser macro name cisco-global Macro name : cisco-global Macro type : default global # Enable dynamic port error recovery for link state # failures errdisable recovery cause link-flap errdisable recovery interval 60 # VTP requires Transparent mode for future 802.1x Guest VLAN # and current Best Practice vtp domain [smartports] vtp mode transparent # Config Cos to DSCP mappings mls qos map cos-dscp 0 8 16 26 32 46 48 56 # Enable aggressive mode UDLD on all fiber uplinks udld aggressive
3-4
OL-13013-06
Chapter 3
# Enable Rapid PVST+ and Loopguard spanning-tree mode rapid-pvst spanning-tree loopguard default spanning-tree extend system-id
Applying the cisco-global Smart Port Macro

To apply the cisco-global smart port macro, perform this task: Command
Router# configure terminal Router(config)# macro global apply cisco-global Router(config)# end Router# show parser macro description
Purpose Enters global configuration mode. Applies the cisco-global smart port macro. Returns to privileged EXEC mode. Displays the macros that have been applied.
This example shows how to apply the cisco-global smart port macro and display the name of the applied macro:
Router# configure terminal Router(config)# macro global apply cisco-global Changing VTP domain name from previous_domain_name to [smartports] Setting device to VTP TRANSPARENT mode. Router(config)# end Router# show parser macro description Global Macro(s): cisco-global Interface Macro Description(s) --------------------------------------------------------------------------------------------------------------------------Router#
Using the cisco-desktop Smart Port Macro

These sections describe how to apply the cisco-desktop smart port macro:

Displaying the Contents of the cisco-desktop Smart Port Macro, page 3-5 Applying the cisco-desktop Smart Port Macro, page 3-6
Displaying the Contents of the cisco-desktop Smart Port Macro

This example shows how to display the contents of the cisco-desktop smart port macro:
Router# show parser macro name cisco-desktop Macro name : cisco-desktop Macro type : default interface # macro keywords $AVID # Basic interface - Enable data VLAN only # Recommended value for access vlan (AVID) should not be 1 switchport switchport access vlan $AVID switchport mode access # Enable port security limiting port to a single # MAC address -- that of desktop switchport port-security
3-5
switchport port-security maximum 1 # Ensure port-security age is greater than one minute # and use inactivity timer switchport port-security violation restrict switchport port-security aging time 2 # Configure port as an edge network port spanning-tree portfast spanning-tree portfast edge bpduguard default
Applying the cisco-desktop Smart Port Macro

To apply the cisco-desktop smart port macro, perform this task: Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6
Router# configure terminal Router(config)# interface type
1
Purpose Enters global configuration mode.

slot/port
Selects the interface to configure. Applies the cisco-desktop smart port macro. The recommended range for access_vlan_ID is 24094. Returns to privileged EXEC mode. Displays the macros that have been applied. Displays all of the commands configured on the interface.
Router(config-if)# macro apply cisco-desktop $AVID access_vlan_ID Router(config-if)# end Router# show parser macro description interface type1 slot/port Router# show running-config interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to apply the cisco-desktop smart port macro to Gigabit Ethernet port 1/1 with VLAN 2 specified as the access VLAN and how to verify the result:
Router# configure terminal Router(config)# interface gigabitethernet 1/1 Router(config-if)# macro apply cisco-desktop $AVID 2 %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 %Portfast has been configured on GigabitEthernet1/1 but will only have effect when the interface is in a non-trunking mode. Router(config)# end Router# show parser macro description interface gigabitethernet 1/1 Global Macro(s): cisco-global Interface Macro Description(s) -------------------------------------------------------------Gi1/1 cisco-desktop -------------------------------------------------------------Router# show running-config interface gigabitethernet 1/1 Building configuration... Current configuration : 307 bytes ! interface GigabitEthernet1/1 switchport switchport access vlan 2 switchport mode access
3-6
OL-13013-06
Chapter 3
switchport port-security switchport port-security aging time 2 switchport port-security violation restrict shutdown macro description cisco-desktop spanning-tree portfast spanning-tree bpduguard enable end Router#
Using the cisco-phone Smart Port Macro

These sections describe how to apply the cisco-phone smart port macro:

Displaying the Contents of the cisco-phone Smart Port Macro, page 3-7 Applying the cisco-phone Smart Port Macro, page 3-8
Displaying the Contents of the cisco-phone Smart Port Macro

This example shows how to display the contents of the cisco-phone smart port macro:
Router# show parser macro name cisco-phone Macro name : cisco-phone Macro type : default interface # macro keywords $AVID $VVID # VoIP enabled interface - Enable data VLAN # and voice VLAN (VVID) # Recommended value for access vlan (AVID) should not be 1 switchport switchport access vlan $AVID switchport mode access # Update the Voice VLAN (VVID) value which should be # different from data VLAN # Recommended value for voice vlan (VVID) should not be 1 switchport voice vlan $VVID # Enable port security limiting port to a 3 MAC # addressess -- One for desktop and two for phone switchport port-security switchport port-security maximum 3 # Ensure port-security age is greater than one minute # and use inactivity timer switchport port-security violation restrict switchport port-security aging time 2 # Enable auto-qos to extend trust to attached Cisco phone auto qos voip cisco-phone # Configure port as an edge network port spanning-tree portfast spanning-tree portfast edge bpduguard default
3-7
Applying the cisco-phone Smart Port Macro

To apply the cisco-phone smart port macro, perform this task: Command
1

slot/port
Selects the interface to configure. Applies the cisco-phone smart port macro. The recommended range for access_vlan_ID is 24094. The recommended range for voice_vlan_ID is 24094. Returns to privileged EXEC mode. Displays the macros that have been applied. Displays all of the commands configured on the interface.
Router(config-if)# macro apply cisco-phone $AVID access_vlan_ID $VVID voice_vlan_ID
Router(config-if)# end Router# show parser macro description interface type1 slot/port Router# show running-config interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
When applying the cisco-phone smart port macro, note the following information:
Some of the generated commands are in the category of PFC QoS commands that are applied to all ports controlled by a port ASIC. When one of these generated commands is applied, PFC QoS displays the messages caused by application of the command to all the ports controlled by the port ASIC. Depending on the module, these commands are applied to as many as 48 ports. See the Number of port groups and Port ranges per port group listed for each module in the Release Notes for Cisco IOS Release 12.2SX. You might see messages that instruct you to configure other ports to trust CoS. You must do so to enable the generated QoS commands. You might not be able to apply the cisco-phone smart port macro and other macros on ports that are controlled by the same port ASIC because of conflicting port trust state requirements.
This example shows how to apply the cisco-phone smart port macro to Gigabit Ethernet port 2/2 with VLAN 2 specified as the access VLAN and how to verify the result:
Router# configure terminal Router(config)# interface gigabitethernet 2/2 Router(config-if)# macro apply cisco-phone $AVID 2 $VVID 3 Hardware QoS is enabled Propagating cos-map to inband port Propagating cos-map configuration to: [port list not shown]
[Output for other ports controlled by the same port ASIC omitted]
Warning: rcv cosmap will not be applied in hardware. To modify rcv cosmap in hardware, all of the interfaces below must be put into 'trust cos' state:
[port list not shown]

%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 %Portfast has been configured on GigabitEthernet1/2 but will only have effect when the interface is in a non-trunking mode. Router(config)# end
3-8
OL-13013-06
Chapter 3
Router# show parser macro description interface gigabitethernet 2/2 Global Macro(s): cisco-global Interface Macro Description(s) -------------------------------------------------------------Gi2/2 cisco-phone -------------------------------------------------------------Router# show running-config interface gigabitethernet 2/2 Building configuration... Building configuration... Current configuration : 307 bytes ! interface GigabitEthernet1/2 Building configuration... Current configuration : 1336 bytes ! interface GigabitEthernet2/2 switchport switchport access vlan 2 switchport mode access switchport voice vlan 3 switchport port-security switchport port-security maximum 3 switchport port-security aging time 2 switchport port-security violation restrict shutdown
[QoS queuing commands omitted: these vary according to port type]

mls qos trust cos auto qos voip cisco-phone macro description cisco-phone spanning-tree portfast spanning-tree bpduguard enable end Router#
Using the cisco-switch Smart Port Macro

These sections describe how to apply the cisco-switch smart port macro:

Displaying the Contents of the cisco-switch Smart Port Macro, page 3-9 Applying the cisco-switch Smart Port Macro, page 3-10
Displaying the Contents of the cisco-switch Smart Port Macro

This example shows how to display the contents of the cisco-switch smart port macro:
Router# show parser macro name cisco-switch Macro name : cisco-switch Macro type : default interface # macro keywords $NVID # Do not apply to EtherChannel/Port Group # Access Uplink to Distribution # Define unique Native VLAN on trunk ports # Recommended value for native vlan (NVID) should not be 1
3-9
switchport switchport trunk native vlan $NVID # Update the allowed VLAN range (VRANGE) such that it # includes data, voice and native VLANs # switchport trunk allowed vlan VRANGE # Hardcode # speed up switchport switchport switchport trunk and disable negotiation to convergence trunk encapsulation dot1q mode trunk nonegotiate
# 802.1w defines the link as pt-pt for rapid convergence spanning-tree link-type point-to-point Router#
Applying the cisco-switch Smart Port Macro

To apply the cisco-switch smart port macro, perform this task: Command
1

slot/port
Selects the interface to configure. Applies the cisco-switch smart port macro. The recommended range for native_vlan_ID is 24094. Returns to privileged EXEC mode. Displays the macros that have been applied. Displays all of the commands configured on the interface.
Router(config-if)# macro apply cisco-switch $NVID native_vlan_ID Router(config-if)# end Router# show parser macro description interface type1 slot/port Router# show running-config interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to apply the cisco-switch smart port macro to Gigabit Ethernet port 1/4 with VLAN 4 specified as the native VLAN and how to verify the result:
Router# configure terminal Router(config)# interface gigabitethernet 1/4 Router(config-if)# macro apply cisco-switch $NVID 4 Router(config-if)# end Router# show parser macro description interface gigabitethernet 1/4 Interface Macro Description(s) -------------------------------------------------------------Gi1/4 cisco-switch -------------------------------------------------------------Router# show running-config interface gigabitethernet 1/4 Building configuration... Current configuration : 247 bytes ! interface GigabitEthernet1/4 switchport switchport trunk encapsulation dot1q switchport trunk native vlan 4 switchport mode trunk
3-10
OL-13013-06
Chapter 3
switchport nonegotiate shutdown macro description cisco-switch spanning-tree link-type point-to-point end Router#
Using the cisco-router Smart Port Macro

These sections describe how to apply the cisco-router smart port macro:

Displaying the Contents of the cisco-router Smart Port Macro, page 3-11 Applying the cisco-router Smart Port Macro, page 3-12
Displaying the Contents of the cisco-router Smart Port Macro

This example shows how to display the contents of the cisco-router smart port macro:
Router# show parser macro name cisco-router Macro name : cisco-router Macro type : default interface # macro keywords $NVID # Do not apply to EtherChannel/Port Group # Access Uplink to Distribution switchport # Define unique Native VLAN on trunk ports # Recommended value for native vlan (NVID) should not be 1 switchport trunk native vlan $NVID # Update the allowed VLAN range (VRANGE) such that it # includes data, voice and native VLANs # switchport trunk allowed vlan VRANGE # Hardcode # speed up switchport switchport switchport trunk and disable negotiation to convergence trunk encapsulation dot1q mode trunk nonegotiate
# Configure qos to trust this interface auto qos voip trust mls qos trust dscp # Ensure fast # Ensure that spanning-tree spanning-tree Router# access to the network when enabling the interface. switch devices cannot become active on the interface. portfast portfast edge bpduguard default
3-11
Applying the cisco-router Smart Port Macro

To apply the cisco-router smart port macro, perform this task: Command
1

slot/port
Selects the interface to configure. Applies the cisco-router smart port macro. The recommended range for native_vlan_ID is 24094. Returns to privileged EXEC mode. Displays the macros that have been applied. Displays all of the commands configured on the interface.
Router(config-if)# macro apply cisco-router $NVID native_vlan_ID Router(config-if)# end Router# show parser macro description interface type1 slot/port Router# show running-config interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Note
The cisco-router smart port macro includes the auto qos voip trust command. When entered on a port configured with the switchport command, the auto qos voip trust command generates and applies the mls qos trust cos command to the port, but the cisco-router smart port macro changes the port trust state to trust DSCP with the mls qos trust dscp command. When you apply the cisco-router smart port macro, ignore messages that instruct you to enter the mls qos trust cos command on other ports controlled by the port ASIC. This example shows how to apply the cisco-router smart port macro to Gigabit Ethernet port 1/5 and how to verify the result:
Router# configure terminal Router(config)# interface gigabitethernet 1/5 Router(config-if)# macro apply cisco-router $NVID 5 Hardware QoS is enabled Propagating cos-map to inband port Propagating cos-map configuration to: [port list not shown]
[Output for other ports controlled by the same port ASIC omitted] [Output from temporarily applied trust CoS command omitted]
%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 %Portfast has been configured on GigabitEthernet1/5 but will only have effect when the interface is in a non-trunking mode. Router(config-if)# end Router# show parser macro description interface gigabitethernet 1/5 Interface Macro Description(s) -------------------------------------------------------------Gi1/5 cisco-router -------------------------------------------------------------Router# show running-config interface gigabitethernet 1/5 Building configuration... Current configuration : 1228 bytes
3-12
OL-13013-06
Chapter 3
! interface GigabitEthernet1/5 switchport switchport trunk encapsulation dot1q switchport trunk native vlan 5 switchport mode trunk switchport nonegotiate shutdown wrr-queue bandwidth 20 100 200
[QoS queuing commands omitted: these vary according to port type]

mls qos trust dscp auto qos voip trust macro description cisco-router spanning-tree portfast spanning-tree bpduguard enable end Router#
Configuring User-Created Smart Port Macros

These sections describe how to configure user-created smart port macros:

Creating Smart Port Macros, page 3-13 Applying Smart Port Macros, page 3-14
Creating Smart Port Macros

To create a smart port macro, perform this task:
3-13
Command
Step 1 Step 2
Router# configure terminal Router(config)# macro name macro-name
Purpose Enters global configuration mode. Creates a macro. Macro names are case sensitive. For example, the commands macro name Sample-Macro and macro name sample-macro will result in two separate macros. A macro definition can contain up to 3,000 characters. Line endings count as two characters. There is no prompt displayed in macro creation mode. Enter the macro commands on separate lines. Use the # character at the beginning of a line to enter a comment within the macro. Use the @ character to end the macro. Do not use the exit or end commands or change the command mode with the interface interface-id in a macro. This could cause any commands following exit, end, or interface interface-id to execute in a different command mode. For best results, all commands in a macro should be in the same configuration mode. Each user-created macro can have up to three keyword-value pairs.
Step 3
# macro keywords keyword1 keyword2 keyword3
(Optional) You can create a help string to describe the keywords that you define in the macro. You can enter up to three help string comments in a macro. Returns to privileged EXEC mode. Verifies that the macro was created.
Step 4 Step 5
end show parser macro name macro-name
Note
The no form of the macro name global configuration command only deletes the macro definition. It does not affect the configuration of those interfaces on which the macro is already applied. This example shows how to create a macro that defines the Layer 2 access VLAN and the number of secure MAC addresses and also includes two help string keywords by using # macro keywords:
Router(config)# macro name test #macro keywords $VLANID $MAX switchport access vlan $VLANID switchport port-security maximum $MAX @
Applying Smart Port Macros

To apply a smart port macro, perform this task:
3-14
OL-13013-06
Chapter 3
Command
Router# configure terminal Router(config)# default interface interface-id
Purpose Enters global configuration mode. (Optional) Clears all configuration from the specified interface. (Required for interface macros.) Specifies the interface on which to apply the macro and enters interface configuration mode. Applies or traces and applies each individual command defined in the macro. For global macros: To find any syntax or configuration errors, enter the macro global trace macro-name command to apply and debug the macro. To display a list of any keyword-value pairs defined in the macro, enter the macro global apply macro-name ? command. To find any syntax or configuration errors, enter the macro trace macro-name command to apply and debug the macro. To display a list of any keyword-value pairs defined in the macro, enter the macro apply macro-name ? command.
Router(config)# interface interface_id
Step 4
Router(config)# macro global {apply | trace} macro-name [keyword value] [keyword value] [keyword value]
Or
Router(config-if)# macro {apply | trace} macro-name [keyword value] [keyword value] [keyword value]
For interface macros:
To successfully apply the macro, you must enter any required keyword-value pairs. Keyword matching is case sensitive. In the commands that the macro applies, all matching occurrences of keywords are replaced with the corresponding values.
Step 5 Step 6
Router(config)# end Router# show parser macro description [interface interface_id]
Returns to privileged EXEC mode. Verifies that the macro is applied to the interface.
You can delete a global macro-applied configuration on a switch only by entering the no version of each command that is in the macro. You can delete all configurations on an interface by entering the default interface interface_id interface configuration command. This example shows how to apply the user-created macro called snmp, to set the host name address to test-server and to set the IP precedence value to 7:
Router(config)# macro global apply snmp ADDRESS test-server VALUE 7
This example shows how to debug the user-created macro called snmp by using the macro global trace global configuration command to find any syntax or configuration errors in the macro when it is applied to the switch:
Router(config)# macro global trace snmp VALUE 7 Applying command...snmp-server enable traps port-security
3-15
Chapter 3 Displaying Smart Port Macros
Applying command...snmp-server Applying command...snmp-server Applying command...snmp-server %Error Unknown error. Applying command...snmp-server
enable traps linkup enable traps linkdown host ip precedence 7
This example shows how to apply the user-created macro called desktop-config and to verify the configuration:
Router(config)# interface fastethernet1/2 Router(config-if)# macro apply desktop-config Router(config-if)# end Router# show parser macro description Interface Macro Description -------------------------------------------------------------Fa1/2 desktop-config --------------------------------------------------------------
This example shows how to apply the user-created macro called desktop-config and to replace all occurrences of vlan with VLAN ID 25:
Router(config-if)# macro apply desktop-config vlan 25
Displaying Smart Port Macros

To display the smart port macros, use one or more of the privileged EXEC commands in Table 3-2.
Table 3-2 Commands for Displaying Smartports Macros
Command
show parser macro show parser macro name macro-name show parser macro brief show parser macro description
Purpose Displays all configured macros. Displays a specific macro. Displays the configured macro names. [interface interface-id] Displays the macro description for all interfaces or for a specified interface.
Tip
3-16
OL-13013-06
C H A P T E R
Configuring Virtual Switching Systems

This chapter describes how to configure a virtual switching system (VSS) for the Catalyst 6500 series switch. Cisco IOS Release 12.2(33)SXH1 and later releases support VSS.
Note
The Cisco IOS Virtual Switch Command Reference at this URL: http://www.cisco.com/en/US/docs/ios/vswitch/command/reference/vs_book.html The Cisco IOS 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
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

Understanding Virtual Switching Systems, page 4-1 VSS Configuration Guidelines and Restrictions, page 4-29 Configuring a VSS, page 4-30 Upgrading a VSS, page 4-55
Understanding Virtual Switching Systems

These sections describe a VSS:

VSS Overview, page 4-2 VSS Redundancy, page 4-11 Multichassis EtherChannels, page 4-14
4-1
Chapter 4 Understanding Virtual Switching Systems
Packet Handling, page 4-16 System Monitoring, page 4-20 Dual-Active Detection, page 4-22 VSS Initialization, page 4-25 VSS Configuration Guidelines and Restrictions, page 4-29
VSS Overview
Network operators increase network reliability by configuring switches or SIP-400 CWAN line cards in redundant pairs and by provisioning links to the redundant pairs. Figure 4-1 shows a typical switch network configuration. Redundant network elements and redundant links can add complexity to network design and operation. Virtual switching simplifies the network by reducing the number of network elements and hiding the complexity of managing redundant switches and links. A VSS combines a pair of Catalyst 6500 series switches or SIP-400 CWAN line cards into a single network element. The VSS manages the redundant links, which externally act as a single port channel. The VSS simplifies network configuration and operation by reducing the number of Layer 3 routing neighbors and by providing a loop-free Layer 2 topology.
Figure 4-1
Access
Typical Switch Network Design
Distribution
Core
The following sections present an overview of the VSS. These topics are covered in detail in subsequent chapters:

Key Concepts, page 4-3 VSS Functionality, page 4-5 Hardware Requirements, page 4-8 Understanding VSL Topology, page 4-11
4-2
181320
OL-13013-06
Chapter 4
Configuring Virtual Switching Systems Understanding Virtual Switching Systems
Key Concepts
The VSS incorporates the following key concepts:

Virtual Switching System, page 4-3 VSS Active and VSS Standby Chassis, page 4-3 Virtual Switch Link, page 4-3 Multichassis EtherChannel, page 4-5
Virtual Switching System

A VSS combines a pair of switches into a single network element. For example, a VSS in the distribution layer of the network interacts with the access and core networks as if it were a single switch. See Figure 4-2. An access switch connects to both chassis of the VSS using one logical port channel. The VSS manages redundancy and load balancing on the port channel. This capability enables a loop-free Layer 2 network topology. The VSS also simplifies the Layer 3 network topology because the VSS reduces the number of routing peers in the network.
Figure 4-2 VSS in the Distribution Network
Physical view Virtual Distribution Switch
Logical view Virtual Distribution Switch
Access
Access
VSS Active and VSS Standby Chassis

When you create or restart a VSS, the peer chassis negotiate their roles. One chassis becomes the VSS active chassis, and the other chassis becomes the VSS standby. The VSS active chassis controls the VSS. It runs the Layer 2 and Layer 3 control protocols for the switching modules on both chassis. The VSS active chassis also provides management functions for the VSS, such as module online insertion and removal (OIR) and the console interface. The VSS active and VSS standby chassis perform packet forwarding for ingress data traffic on their locally hosted interfaces. However, the VSS standby chassis sends all control traffic to the VSS active chassis for processing.
Virtual Switch Link

For the two chassis of the VSS to act as one network element, they need to share control information and data traffic.
4-3
181321
The virtual switch link (VSL) is a special link that carries control and data traffic between the two chassis of a VSS, as shown in Figure 4-3. The VSL is implemented as an EtherChannel with up to eight links. The VSL gives control traffic higher priority than data traffic so that control messages are never discarded. Data traffic is load balanced among the VSL links by the EtherChannel load-balancing algorithm.
Figure 4-3 Virtual Switch Link
Virtual switch
Chassis 1
Chassis 2
Virtual switch link (VSL)
When you configure VSL all existing configurations are removed from the interface except for specific allowed commands. When you configure VSL, the system puts the interface into a restricted mode. When an interface is in restricted mode, only specific configuration commands can be configured on the interface. The following VSL configuration commands are not removed from the interface when it becomes restricted:

mls qos trust cos mls qos channel-consistency description logging event load-interval vslp port-channel port
When in VSL restricted mode, only these configuration commands are available:

channel-group default description exit load-interval logging mls mls ip mls ipx mls netflow mls rp
4-4
181322
OL-13013-06
Chapter 4
mls switching no shutdown
Note
The mls qos command is not available when a port is in VSL restricted mode.
Multichassis EtherChannel
An EtherChannel (also known as a port channel) is a collection of two or more physical links that combine to form one logical link. Layer 2 protocols operate on the EtherChannel as a single logical entity. A multichassis EtherChannel (MEC) is a port channel that spans the two chassis of a VSS. The access switch views the MEC as a standard port channel. See Figure 4-4. The VSS supports a maximum of 512 EtherChannels. This limit applies to the combined total of regular EtherChannels and MECs. Because VSL requires two EtherChannel numbers (one for each chassis), there are 510 user-configurable EtherChannels. If an installed service module uses an internal EtherChannel, that EtherChannel will be included in the total.
Note
For releases earlier than Cisco IOS Release 12.2(33)SXI, the maximum number of EtherChannels is 128, allowing 126 user-configurable EtherChannels.
Figure 4-4 VSS with MEC
VSL Chassis 1 Chassis 2
MEC
181323
VSS Functionality
The following sections describe the main functionality of a VSS:

Redundancy and High Availability, page 4-6 Packet Handling, page 4-6 System Management, page 4-6 Quad-Supervisor Uplink Forwarding on In-chassis Standby Supervisor Engines, page 4-6 Interface Naming Convention, page 4-8 Software Features, page 4-8
4-5
Redundancy and High Availability

In a VSS, supervisor engine redundancy operates between the VSS active and VSS standby chassis, using stateful switchover (SSO) and nonstop forwarding (NSF). The peer chassis exchange configuration and state information across the VSL and the VSS standby supervisor engine runs in hot VSS standby mode. The VSS standby chassis monitors the VSS active chassis using the VSL. If it detects failure, the VSS standby chassis initiates a switchover and takes on the VSS active role. When the failed chassis recovers, it takes on the VSS standby role. If the VSL fails completely, the VSS standby chassis assumes that the VSS active chassis has failed, and initiates a switchover. After the switchover, if both chassis are VSS active, the dual-active detection feature detects this condition and initiates recovery action. For additional information about dual-active detection, see the Dual-Active Detection section on page 4-22.
Packet Handling
The VSS active supervisor engine runs the Layer 2 and Layer 3 protocols and features for the VSS and manages the DFC modules for both chassis. The VSS uses VSL to communicate protocol and system information between the peer chassis and to carry data traffic between the chassis when required. Both chassis perform packet forwarding for ingress traffic on their interfaces. If possible, ingress traffic is forwarded to an outgoing interface on the same chassis to minimize data traffic that must traverse the VSL. Because the VSS standby chassis is actively forwarding traffic, the VSS active supervisor engine distributes updates to the VSS standby supervisor engine PFC and all VSS standby chassis DFCs.
System Management
The VSS active supervisor engine acts as a single point of control for the VSS. For example, the VSS active supervisor engine handles OIR of switching modules on both chassis. The VSS active supervisor engine uses VSL to send messages to and from local ports on the VSS standby chassis. The command console on the VSS active supervisor engine is used to control both chassis. In virtual switch mode, the command console on the VSS standby supervisor engine blocks attempts to enter configuration mode. The VSS standby chassis runs a subset of system management tasks. For example, the VSS standby chassis handles its own power management.
Quad-Supervisor Uplink Forwarding on In-chassis Standby Supervisor Engines

When you use VSS quad-supervisor uplink forwarding, the in-chassis standby (ICS) supervisor engine acts as a DFC line card. Only one processor, the SP processor, acts as the DFC line card; the RP processor is reset to ROMMON. During the bootup, once the chassis level role is resolved, the ICS downloads the image from the in-chassis active (ICA) supervisor engine. Once the supervisor engine is booted with the image, it will function in the same way as a DFC line card. All applications running in virtual switch (VS) view the in-chassis standby as a DFC line card. See Figure 4-6 for the various roles that supervisor engines can assume within a quad-supervisor VSS system.
4-6
OL-13013-06
Chapter 4
Figure 4-5
Typical VSS Quad-Supervisor Configuration
VSL Active Supervisor

Supervisor 1: active, ICA
Standby Supervisor
Supervisor 2: standby, ICA
Supervisor 3 ICS Linecard 1 Linecard 2
Supervisor 4 ICS Linecard 1 Linecard 2
Linecard N Active chassis
Linecard N Standby chassis
If your supervisor engine is:

in-chassis active, it can be VSS active or VSS standby. in-chassis standby, it can only be an ICS. VSS active, it can only be ICA. VSS standby, it can only be ICA. eFSU upgrades You can upgrade or downgrade your VSS system using ISSU. See Upgrading a VSS section on page 4-55 for more information about eFSU upgrades. Image version mismatchBefore the bootup, the ICS completes a version check. If there is a version mismatch, the ICS is set to ROMMON. If you want to boot different images on the ICS and ICA. You need to configure the no switch virtual in-chassis standby bootup version mismatch-check command. This command is only valid once all four supervisors are running software that supports Quad-supervisor uplink forwarding. If one supervisor is running software that does not support Quad-supervisor uplink forwarding the command will have no effect. EARL mode mismatchIf the supervisor engine EARL modes do not match then the supervisor engine is reset to ROMMON. It is recommended that all four supervisor engines run the same EARL Lite or EARL Heavy version. VSS RPR switchoverOn RPR switchover the ICS will be reset. For more information regarding RPR see RPR and SSO Redundancy section on page 4-12. In-chassis RPR switchoverICS supervisor engines in the supervisor engine 1 and supervisor engine 2 positions boot up as RPR-Warm. RPR-Warm is when a supervisor engine acts as a DFC. When a VSS stateful switchover occurs, the supervisor engine is reset to ROMMON and boot ups with the supervisor engine image. You can verify the switchover mode of the supervisor engines by entering the show module command. VSS stateful switchoverWhen the in-chassis active supervisor engine crashes, a switchover occurs and the whole chassis reloads (including the ICS) during which the standby supervisor engine takes over as the in-chassis active supervisor engine. A z-switchover operates exactly like a switchover except that the ICS supervisor engine takes priority and is assigned the in-chassis standby supervisor engine. You can initiate a z-switchover by entering the redundancy force switchover command on the in-chassis active supervisor engine. You can verify the switchover mode of the supervisor engines by entering the show module command.
Quad-supervisor uplink forwarding provides these key features:

197277
4-7
If you insert a supervisor engine from another system (VS or standalone) in the supervisor engine 1 or supervisor engine 2 position of your existing two supervisor engine VSS system, the supervisor engine does a reset to update the supervisor engine number, and then reboots before going online as a DFC.
Interface Naming Convention

In VSS mode, interfaces are specified using the switch number (in addition to slot and port), because the same slot numbers are used on both chassis. For example, the interface 1/5/4 command specifies port 4 of the switching module in slot 5 of switch 1. The interface 2/5/4 command specifies port 4 on the switching module in slot 5 of switch 2.
Software Features
With some exceptions, the VSS has feature parity with the standalone Catalyst 6500 series switch. Major exceptions include:

In software releases earlier than Cisco IOS Release 12.2(33)SXI2, the VSS does not support IPv6 unicast or MPLS. In software releases earlier than Cisco IOS Release 12.2(33)SXI, port-based QoS and port ACLs (PACLs) are supported only on Layer 2 single-chassis or multichassis EtherChannel (MEC) links. Beginning with Cisco IOS Release 12.2(33)SXI, port-based QoS and PACLs can be applied to any physical port in the VSS, excluding ports in the VSL. PACLs can be applied to no more than 2046 ports in the VSS. In software releases earlier than Cisco IOS Release 12.2(33)SXI4, the VSS does not support supervisor engine redundancy within a chassis. Starting in Cisco IOS Release 12.2(33)SXI4, the VSS does support supervisor engine redundancy within a chassis. The VSS does not support Lawful Intercept.
Hardware Requirements
The following sections describe the hardware requirements of a VSS:

Chassis and Modules, page 4-8 VSL Hardware Requirements, page 4-9 PFC, DFC, and CFC Requirements, page 4-10 Multichassis EtherChannel Requirements, page 4-10 Service Module Support, page 4-10 WAN Module Support, page 4-10
Chassis and Modules

Table 4-1 describes the hardware requirements for the VSS chassis and modules.
4-8
OL-13013-06
Chapter 4
Table 4-1
VSS Hardware Requirements
Hardware Chassis
Count Requirements 2 The VSS is available on chassis that support VS-S720-10G supervisor engines and WS-X6708-10GE switching modules.
Note
The two chassis need not be identical.
Supervisor Engines
The VSS requires Supervisor Engine 720 with 10-Gigabit Ethernet ports. You must use either two VS-S720-10G-3C or two VS-S720-10G-3CXL supervisor engine modules. The two supervisor engines must match exactly. The VSS requires 67xx series switching modules. The VSS does not support classic, CEF256, or dCEF256 switching modules. In virtual switch mode, unsupported switching modules remain powered off.
Switching Modules
2+
VSL Hardware Requirements

The VSL EtherChannel supports only 10-Gigabit Ethernet ports. The 10-Gigabit Ethernet port can be located on the supervisor engine module or on one of the following switching modules:

WS-X6708-10GE-3C or WS-X6708-10GE-3CXL WS-X6716-10GE-3C or WS-X6716-10GE-3CXL WS-X6716-10T-3C or WS-X6716-10T-3CXL
Note
Using the 10-Gigabit Ethernet ports on a WS-X6716-10GE switching module in the VSL EtherChannel requires Cisco IOS Release 12.2(33)SXI or a later release.
Note
Using the 10-Gigabit Ethernet ports on a WS-X6716-10T switching module in the VSL EtherChannel requires Cisco IOS Release 12.2(33)SXI4 or a later release. We recommend that you use both of the 10-Gigabit Ethernet ports on the supervisor engines to create the VSL between the two chassis. You can add additional physical links to the VSL EtherChannel by using the 10-Gigabit Ethernet ports on WS-X6708-10GE, WS-X6716-10GE, or WS-X6716-10T switching modules.
Note
When using the 10-Gigabit Ethernet ports on the WS-X6716-10GE or WS-X6716-10T switching module as VSL links, you must operate the ports in performance, not oversubscription, mode. Enter the no hw-module switch x slot y oversubscription port-group num command when configuring the switching module. It is important to understand, if you configure oversubscription using the hw-module switch x slot y oversubscription command only ports 1, 5, 9, and 13 will be configurable, all other ports within the port-group will be disabled.
4-9
Note
Port-groups are independent of each other and one, or more, port-groups can operate in non-oversubscribed (1:1) mode (e.g. for VSL) with the 3 unused ports administratively shutdown, while the others can still operate in oversubscribed (4:1) mode.
PFC, DFC, and CFC Requirements

The VSS supports any 67xx series switching module with CFC hardware. The VSS supports DFC3C or DFC3CXL hardware and does not support DFC3A/3B/3BXL hardware. If any switching module in the VSS is provisioned with DFC3C, the whole VSS must operate in PFC3C mode. If a 67xx series switching module with a DFC3A/3B/3BXL is inserted in the chassis of a VSS, the module will remain unpowered, because VSS supports only DFC3C and DFC3CXL. If the supervisor engines are provisioned with PFC3C, the VSS will automatically operate in 3C mode, even if some of the modules are 3CXL. However, if the supervisor engines are provisioned with PFC3CXL, but some of the modules are 3C, you need to configure the VSS to operate in 3C mode. The platform hardware vsl pfc mode pfc3c configuration command sets the system to operate in 3C mode after the next restart. See the SSO Dependencies section on page 4-27 for further details about this command.
Multichassis EtherChannel Requirements

Physical links from any 67xx series switching module can be used to implement a Multichassis EtherChannel (MEC).
Service Module Support

Using the indicated minimum software releases, the following service modules are supported in a VSS: Minimum Cisco IOS Release 12.2(33)SXH1 Minimum Module Release 3.6(1a) A2(1.3) 6.0(2)E1 3.2.171.6 4.0.4
Service Module Network Analysis Module (NAM-1 and NAM-2) (WS-SVC-NAM-1 and WS-SVC-NAM-2)
Application Control Engine (ACE10 and ACE20) (ACE10-6500-K9 12.2(33)SXI and ACE20-MOD-K9) Intrusion Detection System Services Module (IDSM-2) (WS-SVC-IDSM2-K9) Wireless Services Module (WiSM) (WS-SVC-WISM-1-K9 Firewall Services Module (FWSM) (WS-SVC-FWM-1-K9) 12.2(33)SXI 12.2(33)SXI 12.2(33)SXI
Note
Before deploying a service module in VSS mode, upgrade the module to the minimum supported release in standalone mode.
WAN Module Support

No WAN modules are currently supported in virtual switch mode.
4-10
OL-13013-06
Chapter 4
Understanding VSL Topology

A VSS contains two chassis that communicate using the VSL, which is a special port group. We recommend that you configure both of the 10-Gigabit Ethernet ports on the supervisor engines as VSL ports. Optionally, you can also configure the VSL port group to contain switching module 10-Gigabit Ethernet ports. This configuration provides additional VSL capacity. See Figure 4-6 for an example topology.
Figure 4-6 VSL Topology Example
VSL Active Supervisor Standby Supervisor
Linecard 1 Linecard 2
VSS Redundancy
The following sections describe how redundancy in a VSS supports network high availability:

Overview, page 4-11 RPR and SSO Redundancy, page 4-12 Failed Chassis Recovery, page 4-13 VSL Failure, page 4-13 User Actions, page 4-14
Overview
A VSS operates stateful switchover (SSO) between the VSS active and VSS standby supervisor engines. Compared to standalone mode, a VSS has the following important differences in its redundancy model:

The VSS active and VSS standby supervisor engines are hosted in separate chassis and use the VSL to exchange information. The VSS active supervisor engine controls both chassis of the VSS. The VSS active supervisor engine runs the Layer 2 and Layer 3 control protocols and manages the switching modules on both chassis. The VSS active and VSS standby chassis both perform data traffic forwarding.
If the VSS active supervisor engine fails, the VSS standby supervisor engine initiates a switchover and assumes the VSS active role.
181326
4-11
RPR and SSO Redundancy

A VSS operates with stateful switchover (SSO) redundancy if it meets the following requirements:

Both supervisor engines must be running the same software version. VSL-related configuration in the two chassis must match. PFC mode must match. SSO and nonstop forwarding (NSF) must be configured on each chassis.
See the SSO Dependencies section on page 4-27 for additional details about the requirements for SSO redundancy on a VSS. See Chapter 6, Configuring NSF with SSO Supervisor Engine Redundancy for information about configuring SSO and NSF. With SSO redundancy, the VSS standby supervisor engine is always ready to assume control following a fault on the VSS active supervisor engine. Configuration, forwarding, and state information are synchronized from the VSS active supervisor engine to the redundant supervisor engine at startup and whenever changes to the VSS active supervisor engine configuration occur. If a switchover occurs, traffic disruption is minimized. If a VSS does not meet the requirements for SSO redundancy, the VSS will use route processor redundancy (RPR). With RPR redundancy, the VSS active supervisor engine does not synchronize configuration changes or state information with the VSS standby. The VSS standby supervisor engine is only partially initialized and the switching modules on the VSS standby supervisor are not powered up. If a switchover occurs, the VSS standby supervisor engine completes its initialization and powers up the switching modules. Traffic is disrupted for the normal reboot time of the chassis. The VSS normally runs stateful switchover (SSO) between the VSS active and VSS standby supervisor engines (see Figure 4-7). The VSS determines the role of each supervisor engine during initialization. The supervisor engine in the VSS standby chassis runs in hot standby state. The VSS uses the VSL link to synchronize configuration data from the VSS active to the VSS standby supervisor engine. Also, protocols and features that support high availability synchronize their events and state information to the VSS standby supervisor engine.
Figure 4-7 Chassis Roles in a VSS
VSL Active Supervisor Standby Supervisor
4-12
181326
OL-13013-06
Chapter 4
Failed Chassis Recovery

If the VSS active chassis or supervisor engine fails, the VSS initiates a stateful switchover (SSO) and the former VSS standby supervisor engine assumes the VSS active role. The failed chassis performs recovery action by reloading the supervisor engine. If the VSS standby chassis or supervisor engine fails, no switchover is required. The failed chassis performs recovery action by reloading the supervisor engine. The VSL links are unavailable while the failed chassis recovers. After the chassis reloads, it becomes the new VSS standby chassis and the VSS reinitializes the VSL links between the two chassis. The switching modules on the failed chassis are unavailable during recovery, so the VSS operates only with the MEC links that terminate on the VSS active chassis. The bandwidth of the VSS is reduced until the failed chassis has completed its recovery and become operational again. Any devices that are connected only to the failed chassis experience an outage.
Note
The VSS may experience a brief data path disruption when the switching modules in the VSS standby chassis become operational after the SSO. After the SSO, much of the processing power of the VSS active supervisor engine is consumed in bringing up a large number of ports simultaneously in the VSS standby chassis. As a result, some links might be brought up before the supervisor engine has configured forwarding for the links, causing traffic to those links to be lost until the configuration is complete. This condition is especially disruptive if the link is an MEC link. Two methods are available to reduce data disruption following an SSO:
Beginning in Cisco IOS Release 12.2(33)SXH2, you can configure the VSS to activate non-VSL ports in smaller groups over a period of time rather than all ports simultaneously. For information about deferring activation of the ports, see the Configuring Deferred Port Activation During VSS Standby Recovery section on page 4-45. You can defer the load sharing of the peer switchs MEC member ports during reestablishment of the port connections. See the Failed Chassis MEC Recovery section on page 4-16 for details about load share deferral.
VSL Failure
To ensure fast recovery from VSL failures, fast link notification is enabled in virtual switch mode on all port channel members (including VSL ports) whose hardware supports fast link notification.
Note
Fast link notification is not compatible with link debounce mechanisms. In virtual switch mode, link debounce is disabled on all port channel members. If a single VSL physical link goes down, the VSS adjusts the port group so that the failed link is not selected. If the VSS standby chassis detects complete VSL link failure, it initiates a stateful switchover (SSO). If the VSS active chassis has failed (causing the VSL links to go down), the scenario is chassis failure, as described in the previous section. If only the VSL has failed and the VSS active chassis is still operational, this is a dual-active scenario. The VSS detects that both chassis are operating in VSS active mode and performs recovery action. See the Dual-Active Detection section on page 4-22 for additional details about the dual-active scenario.
4-13
User Actions
From the VSS active chassis command console, you can initiate a VSS switchover or a reload. If you enter the reload command from the command console, the entire VSS performs a reload. To reload only the VSS standby chassis, use redundancy reload peer command. To force a switchover from the VSS active to the VSS standby supervisor engine, use the redundancy force-switchover command. To reset the VSS standby PRE module or to reset both the VSS active and VSS standby PRE modules, use the redundancy reload shelf command.
Multichassis EtherChannels
These sections describe multichassis EtherChannels (MECs):

Overview, page 4-14 MEC Failure Scenarios, page 4-15
Overview
A multichassis EtherChannel is an EtherChannel with ports that terminate on both chassis of the VSS (see Figure 4-8). A VSS MEC can connect to any network element that supports EtherChannel (such as a host, server, router, or switch). At the VSS, an MEC is an EtherChannel with additional capability: the VSS balances the load across ports in each chassis independently. For example, if traffic enters the VSS active chassis, the VSS will select an MEC link from the VSS active chassis. This MEC capability ensures that data traffic does not unnecessarily traverse the VSL. Each MEC can optionally be configured to support either PAgP or LACP. These protocols run only on the VSS active chassis. PAgP or LACP control packets destined for an MEC link on the VSS standby chassis are sent across VSL. An MEC can support up to eight VSS active physical links, which can be distributed in any proportion between the VSS active and VSS standby chassis.
4-14
OL-13013-06
Chapter 4
Figure 4-8
MEC Topology
Router, switch or server
Virtual switch Supervisor engine
MEC Supervisor engine
Active chassis
Standby chassis
MEC Failure Scenarios

We recommend that you configure the MEC with at least one link to each chassis. This configuration conserves VSL bandwidth (traffic egress link is on the same chassis as the ingress link), and increases network reliability (if one VSS supervisor engine fails, the MEC is still operational). The following sections describe possible failures and the resulting impacts:

Single MEC Link Failure, page 4-15 All MEC Links to the VSS Active Chassis Fail, page 4-15 All MEC Links to the VSS Standby Chassis Fail, page 4-16 All MEC Links Fail, page 4-16 VSS Standby Chassis Failure, page 4-16 VSS Active Chassis Failure, page 4-16 Failed Chassis MEC Recovery, page 4-16
Single MEC Link Failure

If a link within the MEC fails (and other links in the MEC are still operational), the MEC redistributes the load among the operational links, as in a regular port.
All MEC Links to the VSS Active Chassis Fail

If all links to the VSS active chassis fail, the MEC becomes a regular EtherChannel with operational links to the VSS standby chassis. Data traffic terminating on the VSS active chassis reaches the MEC by crossing the VSL to the VSS standby chassis. Control protocols continue to run in the VSS active chassis. Protocol messages reach the MEC by crossing the VSL.
181327
4-15
All MEC Links to the VSS Standby Chassis Fail

If all links fail to the VSS standby chassis, the MEC becomes a regular EtherChannel with operational links to the VSS active chassis. Control protocols continue to run in the VSS active chassis. All control and data traffic from the VSS standby chassis reaches the MEC by crossing the VSL to the VSS active chassis.
All MEC Links Fail

If all links in an MEC fail, the logical interface for the EtherChannel is set to unavailable. Layer 2 control protocols perform the same corrective action as for a link-down event on a regular EtherChannel. On adjacent switches, routing protocols and Spanning Tree Protocol (STP) perform the same corrective action as for a regular EtherChannel.
VSS Standby Chassis Failure

If the VSS standby chassis fails, the MEC becomes a regular EtherChannel with operational links on the VSS active chassis. Connected peer switches detect the link failures, and adjust their load-balancing algorithms to use only the links to the VSS active chassis.
VSS Active Chassis Failure

VSS active chassis failure results in a stateful switchover (SSO). See the VSS Redundancy section on page 4-11 for details about SSO on a VSS. After the switchover, the MEC is operational on the new VSS active chassis. Connected peer switches detect the link failures (to the failed chassis), and adjust their load-balancing algorithms to use only the links to the new VSS active chassis.
Failed Chassis MEC Recovery

When a failed chassis returns to service as the new VSS standby chassis, protocol messages reestablish the MEC links between the recovered chassis and connected peer switches. Although the recovered chassis MEC links are immediately ready to receive unicast traffic from the peer switch, received multicast traffic may be lost for a period of several seconds to several minutes. To reduce this loss, you can configure the port load share deferral feature on MEC port channels of the peer switch. When load share deferral is configured, the peers deferred MEC port channels will establish with an initial load share of 0. During the configured deferral interval, the peers deferred port channels are capable of receiving data and control traffic, and of sending control traffic, but are unable to forward data traffic to the VSS. See the Configuring Port Load Share Deferral on the Peer Switch section on page 4-46 for details about configuring port load share deferral.
Packet Handling
In a VSS, the VSS active supervisor engine runs the Layer 2 and Layer 3 protocols and features for the VSS and manages the DFC modules for both chassis. The VSS uses the VSL to communicate system and protocol information between the peer chassis and to carry data traffic between the two chassis. Both chassis perform packet forwarding for ingress traffic on their local interfaces. The VSS minimizes the amount of data traffic that must traverse the VSL.
4-16
OL-13013-06
Chapter 4
The following sections describe packet handling in a VSS:

Traffic on the VSL, page 4-17 Layer 2 Protocols, page 4-17 Layer 3 Protocols, page 4-18 SPAN, page 4-20
Traffic on the VSL

The VSL carries data traffic and in-band control traffic between the two chassis. All frames forwarded over the VSL link are encapsulated with a special 32-byte header, which provides information for the VSS to forward the packet on the peer chassis. The VSL transports control messages between the two chassis. Messages include protocol messages that are processed by the VSS active supervisor engine, but received or transmitted by interfaces on the VSS standby chassis. Control traffic also includes module programming between the VSS active supervisor engine and switching modules on the VSS standby chassis. The VSS needs to transmit data traffic over the VSL under the following circumstances:

Layer 2 traffic flooded over a VLAN (even for dual-homed links). Packets processed by software on the VSS active supervisor engine where the ingress interface is on the VSS standby chassis. The packet destination is on the peer chassis, such as the following examples:
Traffic within a VLAN where the known destination interface is on the peer chassis. Traffic that is replicated for a multicast group and the multicast receivers are on the peer chassis. The known unicast destination MAC address is on the peer chassis. The packet is a MAC notification frame destined for a port on the peer chassis.
VSL also transports system data, such as NetFlow export data and SNMP data, from the VSS standby chassis to the VSS active supervisor engine. To preserve the VSL bandwidth for critical functions, the VSS uses strategies to minimize user data traffic that must traverse the VSL. For example, if an access switch is dual-homed (attached with an MEC terminating on both VSS chassis), the VSS transmits packets to the access switch using a link on the same chassis as the ingress link. Traffic on the VSL is load-balanced with the same global hashing algorithms available for EtherChannels (the default algorithm is source-destination IP).
Layer 2 Protocols
The VSS active supervisor engine runs the Layer 2 protocols (such as STP and VTP) for the switching modules on both chassis. Protocol messages that are transmitted and received on the VSS standby chassis switching modules must traverse the VSL to reach the VSS active supervisor engine. The following sections describe Layer 2 protocols for a VSS:

Spanning Tree Protocol, page 4-18 Virtual Trunk Protocol, page 4-18 EtherChannel Control Protocols, page 4-18 Multicast Protocols, page 4-18
4-17
Spanning Tree Protocol

The VSS active chassis runs Spanning Tree Protocol (STP). The VSS standby chassis redirects STP BPDUs across the VSL to the VSS active chassis. The STP bridge ID is commonly derived from the chassis MAC address. To ensure that the bridge ID does not change after a switchover, the VSS continues to use the original chassis MAC address for the STP Bridge ID.
Virtual Trunk Protocol

Virtual Trunk Protocol (VTP) uses the IP address of the switch and local current time for version control in advertisements. After a switchover, VTP uses the IP address of the newly VSS active chassis.
EtherChannel Control Protocols

Link Aggregation Control Protocol (LACP) and Port Aggregation Protocol (PAgP) packets contain a device identifier. The VSS defines a common device identifier for both chassis to use. A new PAgP enhancement has been defined for assisting with dual-active scenario detection. For additional information, see the Dual-Active Detection section on page 4-22.
Multicast Protocols
Fast-redirect optimization makes multicast traffic redirection between inter-chassis or intra-chassis line cards faster for Layer 2 trunk multichassis EtherChannel or distributed EtherChannel in case of member port link failure and recovery. This operation occurs mainly when a member port link goes down (port leaves the EtherChannel) and when the member port link goes up (port joins or rejoins the EtherChannel). Fast-redirect does not take effect when you add or remove a member port due to a configuration change or during system boot up.
Layer 3 Protocols
The MSFC on the VSS active supervisor engine runs the Layer 3 protocols and features for the VSS. Both chassis perform packet forwarding for ingress traffic on their interfaces. If possible, ingress traffic is forwarded to an outgoing interface on the same chassis, to minimize data traffic that must traverse the VSL. Because the VSS standby chassis is actively forwarding traffic, the VSS active supervisor engine distributes updates to the VSS standby supervisor engine PFC and all VSS standby chassis DFCs. The following sections describe Layer 3 protocols for a VSS:

IPv4, page 4-18 IPv6 and MPLS, page 4-19 IPv4 Multicast, page 4-19 Software Features, page 4-20
IPv4
The supervisor engine on the VSS active chassis runs the IPv4 routing protocols and performs any required software forwarding. Routing updates received on the VSS standby chassis are redirected to the VSS active chassis across the VSL.
4-18
OL-13013-06
Chapter 4
Hardware forwarding is distributed across all DFCs on the VSS. The supervisor engine on the VSS active chassis sends FIB updates to all local DFCs, remote DFCs, and the VSS standby supervisor engine PFC. All hardware routing uses the router MAC address assigned by the VSS active supervisor engine. After a switchover, the original MAC address is still used. The supervisor engine on the VSS active chassis performs all software forwarding (for protocols such as IPX) and feature processing (such as fragmentation and TTL exceed). If a switchover occurs, software forwarding is disrupted until the new VSS active supervisor engine obtains the latest CEF and other forwarding information. In virtual switch mode, the requirements to support non-stop forwarding (NSF) are the same as in standalone mode. For additional information about NSF requirements, refer to the Catalyst 6500 Series Switch Cisco IOS Configuration Guide, Release 12.2SX. From a routing peer perspective, EtherChannels remain operational during a switchover (only the links to the failed chassis are down, so the routing adjacencies remains valid). The VSS implements path filtering by storing only local paths (paths that do not traverse the VSL) in the FIB entries. Therefore, IP forwarding performs load sharing among the local paths. If no local paths to a given destination are available, the VSS updates the FIB entry to include remote paths (reachable by traversing the VSL).
IPv6 and MPLS

In Cisco IOS Release 12.2(33)SXI2 and later releases, the VSS supports IPv6 unicast and MPLS.
IPv4 Multicast
The IPv4 multicast protocols run on the VSS active supervisor engine. Internet Group Management Protocol (IGMP) and Protocol Independent Multicast (PIM) protocol packets received on the VSS standby supervisor engine are transmitted across VSL to the VSS active chassis. The VSS active supervisor engine sends IGMP and PIM protocol packets to the VSS standby supervisor engine in order to maintain Layer 2 information for stateful switchover (SSO). The VSS active supervisor engine distributes multicast FIB and adjacency table updates to the VSS standby supervisor engine and switching module DFCs. For Layer 3 multicast in the VSS, learned multicast routes are stored in hardware in the VSS standby supervisor engine. After a switchover, multicast forwarding continues, using the existing hardware entries.
Note
To avoid multicast route changes as a result of the switchover, we recommend that all links carrying multicast traffic be configured as MEC rather than Equal Cost Multipath (ECMP). In virtual switch mode, the VSS active chassis does not program the multicast expansion table (MET) on the VSS standby chassis. The VSS standby supervisor engine programs the outgoing interface hardware entries for all local multicast receivers If all switching modules on the VSS active chassis and VSS standby chassis are egress capable, the multicast replication mode is set to egress mode; otherwise, the mode is set to ingress mode. In egress mode, replication is distributed to DFCs that have ports in outgoing VLANs for a particular flow. In ingress mode, replication for all outgoing VLANs is done on the ingress DFC. For packets traversing VSL, all Layer 3 multicast replication occurs on the ingress chassis. If there are multiple receivers on the egress chassis, replicated packets are forwarded over the VSL.
4-19
Software Features
Software features run only on the VSS active supervisor engine. Incoming packets to the VSS standby chassis that require software processing are sent across the VSL. For features supported in hardware, the ACL configuration is sent to the TCAM manager on the VSS active supervisor engine, the VSS standby supervisor engine, and all DFCs.
SPAN
The VSS supports all SPAN features for non-VSL interfaces. The VSS supports SPAN features on VSL interfaces with the following limitations:

If the VSL is configured as a local SPAN source, the SPAN destination interface must be on the same chassis as the source interface. VSL cannot be configured as a SPAN destination. VSL cannot be configured as a traffic source of RSPAN, ERSPAN, or egress-only SPAN.
The number of SPAN sessions available to a VSS is the same as for a single chassis running in standalone mode.
System Monitoring
The following sections describe system monitoring and system management for a VSS:

Power Management, page 4-20 Environmental Monitoring, page 4-20 File System Access, page 4-21 Diagnostics, page 4-21 Service Modules, page 4-21 Network Management, page 4-22
Power Management
From the VSS active chassis, you can control power-related functions for the VSS standby chassis. For example, use the power enable switch command to control power to the modules and slots on the VSS standby chassis. Use the show power switch command to see the current power settings and status.
Environmental Monitoring
Environmental monitoring runs on both supervisor engines. The VSS standby chassis reports notifications to the VSS active supervisor engine. The VSS active chassis gathers log messages for both chassis. The VSS active chassis synchronizes the calendar and system clock to the VSS standby chassis.
4-20
OL-13013-06
Chapter 4
File System Access

You can access file systems of both chassis from the VSS active chassis. Prefix the device name with the switch number and slot number to access directories on the VSS standby chassis. For example, the command dir sw2-slot6-disk0: lists the contents of disk0 on the VSS standby chassis (assuming switch 2 is the VSS standby chassis). You can access the VSS standby chassis file system only when VSL is operational.
Diagnostics
You can use the diagnostic schedule and diagnostic start commands on a VSS. In virtual switch mode, these commands require an additional parameter, which specifies the chassis to apply the command. When you configure a VSL port on a switching module or a supervisor engine module, the diagnostics suite incorporates additional tests for the VSL ports. Use the show diagnostic content command to display the diagnostics test suite for a module.
VSL Diagnostics
The following VSL-specific diagnostics tests are available on WS-X6708-10GE switching modules with VSL ports. These tests are disruptive:

TestVslBridgeLink TestVslLocalLoopback
The following VSL-specific diagnostics tests are available on a Supervisor Engine 720-10GE with VSL ports. These tests are disruptive:

TestVSActiveToStandbyLoopback TestVslBridgeLink TestVslLocalLoopback
The following VSL-specific diagnostics test is available for VSL ports on the switching module or the supervisor engine. This test is not disruptive:
TestVslStatus
Service Modules
The following system monitoring and system management guidelines apply to service modules supported by the VSS:
The supervisor engine in the same chassis as the service module controls the powering up of the service module. After the service module is online, you initiate a session from the VSS active supervisor engine to configure and maintain the service module. Use the session command to connect to the service module. If the service module is in the VSS standby chassis, the session runs over the VSL. The VSS active chassis performs the graceful shutdown of the service module, even if the service module is in the VSS standby chassis.
4-21
Network Management
The following sections describe network management for a VSS:

Telnet over SSH Sessions and the Web Browser User Interface, page 4-22 SNMP, page 4-22 Command Console, page 4-22
Telnet over SSH Sessions and the Web Browser User Interface
A VSS supports remote access using Telnet over SSH sessions and the Cisco web browser user interface. All remote access is directed to the VSS active supervisor engine, which manages the whole VSS. If the VSS performs a switchover, Telnet over SSH sessions and web browser sessions are disconnected.
SNMP
The SNMP agent runs on the VSS active supervisor engine. CISCO-VIRTUAL-SWITCH-MIB is a new MIB for virtual switch mode and contains the following main components:

cvsGlobalObjects Domain #, Switch #, Switch Mode cvsCoreSwitchConfig Switch Priority cvsChassisTable Chassis Role and Uptime cvsVSLConnectionTable VSL Port Count, Operational State cvsVSLStatsTable Total Packets, Total Error Packets cvsVSLPortStatsTable TX/RX Good, Bad, Bi-dir and Uni-dir Packets
Command Console
Connect console cables to both supervisor engine console ports. You can only use configuration mode in the console for the VSS active supervisor engine. The console on the VSS standby chassis will indicate that chassis is operating in VSS standby mode by adding the characters -stdby to the command line prompt. You cannot enter configuration mode on the VSS standby chassis console. The following example shows the prompt on the VSS standby console:
Router-stdby> show switch virtual Switch mode : Virtual switch domain number : Local switch number : Local switch operational role: Peer switch number : Peer switch operational role : Virtual Switch 100 1 Virtual Switch Standby 2 Virtual Switch Active
Dual-Active Detection
If the VSL fails, the VSS standby chassis cannot determine the state of the VSS active chassis. To ensure that switchover occurs without delay, the VSS standby chassis assumes the VSS active chassis has failed and initiates switchover to take over the VSS active role.
4-22
OL-13013-06
Chapter 4
If the original VSS active chassis is still operational, both chassis are now VSS active. This situation is called a dual-active scenario. A dual-active scenario can have adverse affects on network stability, because both chassis use the same IP addresses, SSH keys, and STP bridge ID. The VSS must detect a dual-active scenario and take recovery action. The VSS supports these three methods for detecting a dual-active scenario:
Enhanced PAgPUses PAgP messaging over the MEC links to communicate between the two chassis through a neighbor switch. Enhanced PAgP is faster than IP BFD, but requires a neighbor switch that supports the PAgP enhancements. IP Bidirectional Forwarding Detection (BFD)Uses BFD messaging over a backup Ethernet connection. IP BFD uses a direct connection between the two chassis and does not require support from a neighbor switch. dual-active fast-helloUses special hello messages over a backup Ethernet connection. Dual-active fast-hello is faster than IP BFD and does not require support from a neighbor switch. This method is available only in Cisco IOS Release 12.2(33)SXI and later releases,
You can configure all three detection methods to be VSS active at the same time. For line redundancy, we recommend dedicating at least two ports per switch for dual-active detection. For module redundancy, the two ports can be on different switching modules in each chassis, and should be on different modules than the VSL links, if feasible. The dual-active detection and recovery methods are described in the following sections:

Dual-Active Detection Using Enhanced PAgP, page 4-23 Dual-Active Detection Using IP BFD, page 4-24 Dual-Active Detection Using Dual-Active Fast Hello Packets, page 4-24 Recovery Actions, page 4-25
Dual-Active Detection Using Enhanced PAgP

Port aggregation protocol (PAgP) is a Cisco-proprietary protocol for managing EtherChannels. If a VSS MEC terminates to a Cisco switch, you can run PAgP protocol on the MEC. If PAgP is running on the MECs between the VSS and an upstream or downstream switch, the VSS can use PAgP to detect a dual-active scenario. The MEC must have at least one port on each chassis of the VSS. In virtual switch mode, PAgP messages include a new type length value (TLV) which contains the ID of the VSS active switch. Only switches in virtual switch mode send the new TLV. For dual-active detection to operate successfully, one or more of the connected switches must be able to process the new TLV. Catalyst 6500 series switches with Supervisor Engine 32 and Supervisor Engine 720 have this capability if they are running Cisco IOS Release 12.2(33)SXH1 or later. For a list of other Cisco products that support enhanced PAgP, refer to Release Notes for Cisco IOS Release 12.2SX at this URL: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/ol_14271.html When the VSS standby chassis detects VSL failure, it initiates SSO and becomes VSS active. Subsequent PAgP messages to the connected switch from the newly VSS active chassis contain the new VSS active ID. The connected switch sends PAgP messages with the new VSS active ID to both VSS chassis. If the formerly VSS active chassis is still operational, it detects the dual-active scenario because the VSS active ID in the PAgP messages changes. This chassis initiates recovery actions as described in the Recovery Actions section on page 4-25.
4-23
Dual-Active Detection Using IP BFD

To use the IP BFD detection method, you must provision a direct Ethernet connection between the two switches. Regular Layer 3 ping will not function correctly on this connection, as both chassis have the same IP address. The VSS instead uses the Bidirectional Forwarding Detection (BFD) protocol. If the VSL fails, both chassis create BFD neighbors, and try to establish adjacency. If the original VSS active chassis receives an adjacency message, it realizes that this is a dual-active scenario, and initiates recovery actions as described in the Recovery Actions section on page 4-25.
Note
If Flex Links are configured on the VSS, we recommend using the PAgP detection method. Do not configure Flex Links and BFD dual-active detection on the same VSS.
Dual-Active Detection Using Dual-Active Fast Hello Packets

Cisco IOS Release 12.2(33)SXI and later releases support the dual-active fast hello method. To use the dual-active fast hello packet detection method, you must provision a direct Ethernet connection between the two switches. You can dedicate up to four non-VSL links for this purpose. The two chassis periodically exchange special Layer 2 dual-active hello messages containing information about the switch state. If the VSL fails and a dual-active scenario occurs, each switch recognizes from the peers messages that there is a dual-active scenario and initiates recovery actions as described in the Recovery Actions section on page 4-25. If a switch does not receive an expected dual-active fast hello message from the peer before the timer expires, the switch assumes that the link is no longer capable of dual-active detection. When you configure dual-active fast hello mode, all existing configurations are removed automatically from the interface except for the specific commands. When you configure dual-active fast hello mode, the system puts the interface into a restricted mode. When an interface is in restricted mode, only specific configuration commands can be entered on the interface. The following fast hello configuration commands are not removed from the interface when it becomes restricted:

description logging event load-interval rcv-queue cos-map rcv-queue queue-limit rcv-queue random-detect rcv-queue threshold wrr-queue bandwidth wrr-queue cos-map wrr-queue queue-limit wrr-queue random-detect wrr-queue threshold priority-queue cos-map
When in dual-active fast hello restricted mode, these configuration commands are available:
4-24
OL-13013-06
Chapter 4
default description dual-active exit load-interval logging no shutdown
Note
ASIC-specific QoS commands are not configurable on the fast hello ports directly, but are allowed to remain on the fast hello port if the commands were configured on another non-fast hello port in that same ASIC group. For a list of these commands, see the Configuring PFC QoS - General Guidelines Section at: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/configuration/guide/qos.html #wp1583195
Recovery Actions
An VSS active chassis that detects a dual-active condition shuts down all of its non-VSL interfaces (except interfaces configured to be excluded from shutdown) to remove itself from the network, and waits in recovery mode until the VSL links have recovered. You might need to intervene directly to fix the VSL failure. When the shut down chassis detects that VSL is operational again, the chassis reloads and returns to service as the VSS standby chassis. Loopback interfaces are also shut down in recovery mode. We do not recommend configuring loopback interfaces at this time (while in recovery mode), because any new loopback interfaces configured in recovery mode will not be shut down.
Note
If the running configuration of the chassis in recovery mode has been changed without saving, the chassis will not automatically reload. In this situation, you must write the configuration to memory and then reload manually.
VSS Initialization
A VSS is formed when the two chassis and the VSL link between them become operational. The peer chassis communicate over the VSL to negotiate the chassis roles. If only one chassis becomes operational, it assumes the VSS active role. The VSS forms when the second chassis becomes operational and both chassis bring up their VSL interfaces. VSS initialization is described in the following sections:

Virtual Switch Link Protocol, page 4-26 SSO Dependencies, page 4-27 Initialization Procedure, page 4-28
4-25
Virtual Switch Link Protocol

The Virtual Switch Link Protocol (VSLP) consists of several protocols that contribute to virtual switch initialization. The VSLP includes the following protocols:
Role Resolution Protocol The peer chassis use Role Resolution Protocol (RRP) to negotiate the role (VSS active or VSS standby) for each chassis.
Link Management Protocol The Link Management Protocol (LMP) runs on all VSL links, and exchanges information required to establish communication between the two chassis. LMP identifies and rejects any unidirectional links. If LMP flags a unidirectional link, the chassis that detects the condition brings the link down and up to restart the VSLP negotiation. VSL moves the control traffic to another port if necessary.
4-26
OL-13013-06
Chapter 4
SSO Dependencies
For the VSS to operate with SSO redundancy, the VSS must meet the following conditions:
Identical software versions Both supervisor engine modules on the VSS must be running the identical software version. VSL configuration consistency During the startup sequence, the VSS standby chassis sends virtual switch information from the startup-config file to the VSS active chassis. The VSS active chassis ensures that the following information matches correctly on both chassis:
Switch virtual domain Switch virtual node Switch priority VSL port channel: switch virtual link identifier VSL ports: channel-group number, shutdown, total number of VSL ports Power redundancy-mode Power enable on VSL modules
If the VSS detects a mismatch, it prints out an error message on the VSS active chassis console and the VSS standby chassis comes up in RPR mode. After you correct the configuration file, save the file by entering the copy running-config startup-config command on the VSS active chassis, and then restart the VSS standby chassis.
PFC mode check If both supervisor engines are provisioned with PFC3C, the VSS will automatically operate in PFC3C mode, even if some of the switching modules are equipped with 3CXL daughter feature cards (DFCs). However, if the supervisor engines are provisioned with PFC3CXL and there is a mixture of DFC3C and DFC3CXL switching modules, the system PFC mode will depend on how the 3C and 3CXL switching modules are distributed between the two chassis. Each chassis in the VSS determines its system PFC mode. If the supervisor engine of a given chassis is provisioned with PFC3CXL and all the switching modules in the chassis are provisioned with DFC3CXL, the PFC mode for the chassis is PFC3CXL. However, if any of the switching modules is provisioned with DFC3C, the chassis PFC mode will be set to PFC3C. If there is a mismatch between the PFC modes of two chassis, the VSS will come up in RPR mode instead of SSO mode. You can prevent this situation by using the platform hardware vsl pfc mode pfc3c command to force the VSS to operate in PFC3C mode after the next reload.
SSO and NSF enabled SSO and NSF must be configured and enabled on both chassis. For detailed information on configuring and verifying SSO and NSF, see Chapter 6, Configuring NSF with SSO Supervisor Engine Redundancy.
If these conditions are not met, the VSS operates in RPR redundancy mode. For a description of SSO and RPR, see the VSS Redundancy section on page 4-11.
4-27
Initialization Procedure
The following sections describe the VSS initialization procedure:

VSL Initialization, page 4-28 System Initialization, page 4-28 VSL Down, page 4-28
VSL Initialization
A VSS is formed when the two chassis and the VSL link between them become operational. Because both chassis need to be assigned their role (VSS active or VSS standby) before completing initialization, VSL is brought online before the rest of the system is initialized. The initialization sequence is as follows:
1. 2. 3. 4. 5.
The VSS initializes all cards with VSL ports, and then initializes the VSL ports. The two chassis communicate over VSL to negotiate their roles (VSS active or VSS standby). The VSS active chassis completes the boot sequence, including the consistency check described in the SSO Dependencies section on page 4-27. If the consistency check completed successfully, the VSS standby chassis comes up in SSO VSS standby mode. If the consistency check failed, the VSS standby chassis comes up in RPR mode. The VSS active chassis synchronizes configuration and application data to the VSS standby chassis.
System Initialization
If you boot both chassis simultaneously, the VSL ports become VSS active, and the chassis will come up as VSS active and VSS standby. If priority is configured, the higher priority switch becomes inactive. If you boot up only one chassis, the VSL ports remain inVSS active, and the chassis comes up as VSS active. When you subsequently boot up the other chassis, the VSL links become active, and the new chassis comes up as VSS standby.
VSL Down
If the VSL is down when both chassis try to boot up, the situation is similar to a dual-active scenario. One of the chassis becomes VSS active and the other chassis initiates recovery from the dual-active scenario. For further information, see the Configuring Dual-Active Detection section on page 4-46.
4-28
OL-13013-06
Chapter 4
Configuring Virtual Switching Systems VSS Configuration Guidelines and Restrictions
VSS Configuration Guidelines and Restrictions

The following sections describe restrictions and guidelines for VSS configuration:

General VSS Restrictions and Guidelines, page 4-29 VSL Restrictions and Guidelines, page 4-29 Multichassis EtherChannel Restrictions and Guidelines, page 4-29 Dual-Active Detection Restrictions and Guidelines, page 4-30 Service Module Restrictions and Guidelines, page 4-30 Configuring a VSS, page 4-30
General VSS Restrictions and Guidelines

When configuring the VSS, note the following guidelines and restrictions:

The VSS configurations in the startup-config file must match on both chassis. We recommend enabling out-of-band MAC address table synchronization among DFC-equipped switching modules by entering the mac-address-table synchronize command.
VSL Restrictions and Guidelines

When configuring the VSL, note the following guidelines and restrictions:

For line redundancy, we recommend configuring at least two ports per switch for the VSL. For module redundancy, the two ports can be on different switching modules in each chassis. The no mls qos channel-consistency command is automatically applied when you configure the VSL. Do not remove this command. Monitor capture sessions cannot be started if a source is the VSL on the port channel of the standby switch. You can specify multiple sources for the monitor capture, but you will need to remove the VSL as a source. The following message is displayed when a remote VSL port channel on the standby switch is specified and you attempt to start the monitor capture:
% remote VSL port is not allowed as capture source
The following message is displayed when a scheduled monitor capture start fails because a source is a remote VSL port channel:
Packet capture session 1 failed to start. A source port is a remote VSL.
Multichassis EtherChannel Restrictions and Guidelines

When configuring MECs, note the following guidelines and restrictions:

All links in an MEC must terminate locally on the VSS active or VSS standby chassis of the same virtual domain. For an MEC using LACP control protocol, minlinks defines the minimum number of physical links in each chassis for the MEC to be operational.
4-29
Chapter 4 Configuring a VSS
For an MEC using LACP control protocol, maxbundle defines the maximum number of links in the MEC across the whole VSS. MEC supports LACP 1:1 redundancy. For additional information about LACP 1:1 redundancy, refer to the Understanding LACP 1:1 Redundancy section on page 18-5. An MEC can be connected to another MEC on a different VSS domain.
Dual-Active Detection Restrictions and Guidelines

When configuring dual-active detection, note the following guidelines and restrictions:

If Flex Links are configured on the VSS, we recommend using the PAgP detection method. Do not configure Flex Links and BFD dual-active detection on the same VSS. For line redundancy, we recommend configuring at least two ports per switch for dual-active detection. For module redundancy, the two ports can be on different switching modules in each chassis, and should be on different modules than the VSL, if feasible.
Service Module Restrictions and Guidelines

When configuring service modules in a VSS, note the following guidelines and restrictions:
When configuring and attaching VLAN groups to a service module interface in a VSS, use the switch {1 | 2} command keyword. For example, the firewall vlan-group command becomes the firewall switch num slot slot vlan-group command. When upgrading the software image of a service module in a VSS, use the switch {1 | 2} command keyword. EtherChannel load balancing (ECLB) is not supported between an IDSM-2 in the VSS active chassis and an IDSM-2 in the VSS standby chassis. A switchover between two service modules in separate chassis of a VSS is considered an intrachassis switchover.
Note
For detailed instructions, restrictions, and guidelines for a service module in a VSS, see the configuration guide and command reference for the service module.
Configuring a VSS
These sections describe how to configure a VSS:

Converting to a VSS, page 4-31 Displaying VSS Information, page 4-37 Converting a VSS to Standalone Chassis, page 4-37 Configuring VSS Parameters, page 4-39 Configuring Multichassis EtherChannels, page 4-45 Configuring Dual-Active Detection, page 4-46 Configuring Service Modules in a VSS, page 4-52
4-30
OL-13013-06
Chapter 4
Configuring Virtual Switching Systems Configuring a VSS
Viewing Chassis Status and Module Information in a VSS, page 4-54 Upgrading a VSS, page 4-55
Converting to a VSS
By default, the Catalyst 6500 series switch is configured to operate in standalone mode (the switch is a single chassis). The VSS combines two standalone switches into one virtual switch, operating in virtual switch mode.
Note
When you convert two standalone switches into one VSS, all non-VSL configuration settings on the VSS standby chassis will revert to the default configuration. To convert two standalone chassis into a VSS, you perform the following major activities:

Save the standalone configuration files. Configure SSO and NSF on each chassis. Configure each chassis as a VSS. Convert to a VSS. Configure the peer VSL information.
In virtual switch mode, both chassis use the same configuration file. When you make configuration changes on the VSS active chassis, these changes are automatically propagated to the VSS standby chassis. The tasks required to convert the standalone chassis to a VSS are detailed in the following sections:

Backing Up the Standalone Configuration, page 4-32 Configuring SSO and NSF, page 4-32 Assigning Virtual Switch Domain and Switch Numbers, page 4-33 Configuring VSL Port Channel and Ports, page 4-34 Converting the Chassis to Virtual Switch Mode, page 4-35 (Optional) Configuring VSS Standby Chassis Modules, page 4-36
In the procedures that follow, the example commands assume the configuration shown in Figure 4-9.
Figure 4-9 Example VSS
Chassis A (Switch 1)
T 5/1
T 5/2
Chassis B (Switch 2)
Virtual switch link (VSL)
Two chassis, A and B, are converted into a VSS with virtual switch domain 100. Interface 10-Gigabit Ethernet 5/1 on Switch 1 is connected to interface 10-Gigabit Ethernet 5/2 on Switch 2 to form the VSL.
181325
4-31
Backing Up the Standalone Configuration

Save the configuration files for both chassis operating in standalone mode. You need these files to revert to standalone mode from virtual switch mode. On Switch 1, perform this task: Command
Step 1 Step 2
Switch-1# copy running-config startup-config
Purpose (Optional) Saves the running configuration to startup configuration. Copies the startup configuration to a backup file.
Switch-1# copy startup-config disk0:old-startup-config
Perform the following task on Switch 2: Command

Step 1 Step 2
Purpose (Optional) Saves the running configuration to the startup configuration file. Copies the startup configuration to a backup file.
Switch-2# copy startup-config disk0:old-startup-config
Configuring SSO and NSF

SSO and NSF must be configured and enabled on both chassis. On Switch 1, perform this task: Command
Step 1 Step 2
Switch-1(config)# redundancy Switch-1(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. Exits redundancy configuration mode. Enables an OSPF routing process, which places the router in router configuration mode. Enables NSF operations for OSPF. Exits to privileged EXEC mode. Verifies that SSO and NSF are configured and enabled. Displays the operating redundancy mode.
Switch-1(config-red)# exit Switch-1(config)# router ospf processID
Switch-1(config-router)# nsf Switch-1(config-router)# end Switch-1# show running-config
Switch-1# show redundancy states

Step 1 Step 2
Switch-2(config)# redundancy Switch-2(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.
4-32
OL-13013-06
Chapter 4
Command
Switch-2(config-red)# exit Switch-2(config)# router ospf processID
Purpose Exits redundancy configuration mode. Enables an OSPF routing process, which places the router in router configuration mode. Enables NSF operations for OSPF. Exits to privileged EXEC mode. Verifies that SSO and NSF are configured and enabled. Displays the operating redundancy mode.
Switch-2(config-router)# nsf Switch-2(config-router)# end Switch-2# show running-config
Switch-2# show redundancy states
For detailed information on configuring and verifying SSO and NSF, see Chapter 6, Configuring NSF with SSO Supervisor Engine Redundancy.
Assigning Virtual Switch Domain and Switch Numbers

You must configure the same virtual switch domain number on both chassis of the VSS. The virtual switch domain is a number between 1 and 255, and must be unique for each VSS in your network (the domain number is incorporated into various identifiers to ensure that these identifiers are unique across the network). Within the VSS, you must configure one chassis to be switch number 1 and the other chassis to be switch number 2. To configure the virtual switch domain and switch number on both chassis, perform this task on Switch 1: Command
Switch-1(config)# switch virtual domain 100 Switch-1(config-vs-domain)# switch 1 Switch-1(config-vs-domain)# exit
Purpose Configures the virtual switch domain on Chassis A. Configures Chassis A as virtual switch number 1. Exits config-vs-domain.

Switch-2(config)# switch virtual domain 100 Switch-2(config-vs-domain)# switch 2 Switch-2(config-vs-domain)# exit
Purpose Configures the virtual switch domain on Chassis B. Configures Chassis B as virtual switch number 2. Exits config-vs-domain.
Note
The switch number is not stored in the startup or running configuration, because both chassis use the same configuration file (but must not have the same switch number).
4-33
Configuring VSL Port Channel and Ports

The VSL is configured with a unique port channel on each chassis. During the conversion, the VSS configures both port channels on the VSS active chassis. If the VSS standby chassis VSL port channel number has been configured for another use, the VSS comes up in RPR mode. To avoid this situation, check that both port channel numbers are available on both of the chassis. Check the port channel number by using the show running-config interface port-channel command. The command displays an error message if the port channel is available for VSL. For example, the following command shows that port channel 20 is available on Switch 1:
Switch-1 # show running-config interface port-channel 20 % Invalid input detected at '^' marker.
To configure the VSL port channels, perform this task on Switch 1: Command
Switch-1(config)# interface port-channel 10 Switch-1(config-if)# switch virtual link 1 Switch-1(config-if)# no shutdown Switch-1(config-if)# exit
Purpose Configures port channel 10 on Switch 1. Associates Switch 1 as owner of port channel 10. Activates the port channel. Exits interface configuration.

Switch-2(config)# interface port-channel 20 Switch-2(config-if)# switch virtual link 2 Switch-2(config-if)# no shutdown Switch-2(config-if)# exit
Purpose Configures port channel 20 on Switch 2. Associates Switch 2 as owner of port channel 20. Activates the port channel. Exits interface configuration mode.
You must add the VSL physical ports to the port channel. In the following example, interfaces 10-Gigabit Ethernet 3/1 and 3/2 on Switch 1 are connected to interfaces 10-Gigabit Ethernet 5/2 and 5/3 on Switch 2.
Tip
For line redundancy, we recommend configuring at least two ports per switch for the VSL. For module redundancy, the two ports can be on different switching modules in each chassis. To configure the VSL ports, perform this task on Switch 1:
Command
Switch-1(config)# interface range tengigabitethernet 3/1-2 Switch-1(config-if)# channel-group 10 mode on witch-1(config-if)# no shutdown
Purpose Enters configuration mode for interface range tengigabitethernet 3/1-2 on Switch 1. Adds this interface to channel group 10. Activates the port.
4-34
OL-13013-06
Chapter 4

Switch-2(config)# interface range tengigabitethernet 5/2-3 Switch-2(config-if)# channel-group 20 mode on Switch-2(config-if)# no shutdown
Purpose Enters configuration mode for interface range tengigabitethernet 5/2-3 on Switch 2. Adds this interface to channel group 20. Activates the port.
Converting the Chassis to Virtual Switch Mode

Conversion to virtual switch mode requires a restart for both chassis. After the reboot, commands that specify interfaces with module/port now include the switch number. For example, a port on a switching module is specified by switch/module/port. Prior to the restart, the VSS converts the startup configuration to use the switch/module/port convention. A backup copy of the startup configuration file is saved on the RP. This file is assigned a default name, but you are also prompted to override the default name if you want to change it. Prior to the conversion, ensure that the PFC operating mode matches on both chassis. If they do not match, VSS comes up in RPR redundancy mode. Enter the show platform hardware pfc mode command on each chassis to display the current PFC mode. If only one of the chassis is in PFC3CXL mode, you can configure it to use PFC3C mode with the platform hardware vsl pfc mode pfc3c command. To verify the PFC operating mode, perform this task: Command
Step 1
Switch-1# show platform hardware pfc mode
Purpose Ensures that the PFC operating mode matches on both chassis, to ensure that the VSS comes up in SSO redundancy mode. Ensures that the PFC operating mode matches on both chassis, to ensure that the VSS comes up in SSO redundancy mode. (Optional) Sets the PFC operating mode to PFC3C on Chassis A. (Optional) Sets the PFC operating mode to PFC3C on Chassis B.
Step 2
Switch-2# show platform hardware pfc mode
Step 3 Step 4
Switch-1(config)# platform hardware vsl pfc mode pfc3c Switch-2(config)# platform hardware vsl pfc mode pfc3c
To convert Chassis 1 to virtual switch mode, perform this task: Command

Switch-1# switch convert mode virtual
Purpose Converts Switch 1 to virtual switch mode. After you enter the command, you are prompted to confirm the action. Enter yes. The system creates a converted configuration file, and saves the file to the RP bootflash.
4-35
To convert Chassis 2 to virtual switch mode, perform this task on Switch 2: Command
Switch-2# switch convert mode virtual
Purpose Converts Switch 2 to virtual switch mode. After you enter the command, you are prompted to confirm the action. Enter yes. The system creates a converted configuration file, and saves the file to the RP bootflash.
Note
After you confirm the command (by entering yes at the prompt), the running configuration is automatically saved as the startup configuration and the chassis reboots. After the reboot, the chassis is in virtual switch mode, so you must specify interfaces with three identifiers (switch/module/port).
(Optional) Configuring VSS Standby Chassis Modules

After the reboot, each chassis contains the module provisioning for its own slots. In addition, the modules from the VSS standby chassis have been automatically provisioned on the VSS active chassis with default configuration. Configurations for the VSS standby chassis modules are restored to their default settings (for example, no IP addresses). You can view the module provisioning information in the configuration file, by entering the show startup-config command (after you have saved the configuration).
Note
Do not delete or modify this section of the configuration file. In Cisco IOS Release 12.2(33)SXI and later releases, you can no longer add module provisioning entries using the module provision CLI command. When a module is not present, the provisioning entry for that module can be cleared using the no slot command with the module provision CLI command. Note that the VSS setup does not support the module clear-config command. The following example shows the module provisioning information from a configuration file:
module provision switch 1 slot 1 slot-type 148 port-type 60 number 4 virtual-slot 17 slot 2 slot-type 137 port-type 31 number 16 virtual-slot 18 slot 3 slot-type 227 port-type 60 number 8 virtual-slot 19 slot 4 slot-type 225 port-type 61 number 48 virtual-slot 20 slot 5 slot-type 82 port-type 31 number 2 virtual-slot 21 module provision switch 2 slot 1 slot-type 148 port-type 60 number 4 virtual-slot 33 slot 2 slot-type 227 port-type 60 number 8 virtual-slot 34 slot 3 slot-type 137 port-type 31 number 16 virtual-slot 35 slot 4 slot-type 225 port-type 61 number 48 virtual-slot 36 slot 5 slot-type 82 port-type 31 number 2 virtual-slot 37
4-36
OL-13013-06
Chapter 4
Displaying VSS Information

To display basic information about the VSS, perform one of these tasks: Command
Router# show switch virtual
Purpose Displays the virtual switch domain number, and the switch number and role for each of the chassis. Displays the role, switch number, and priority for each of the chassis in the VSS. Displays the status of the VSL.
Router# show switch virtual role
Router# show switch virtual link
The following example shows the information output from these commands:
Router# show switch virtual Switch mode : Virtual switch domain number : Local switch number : Local switch operational role: Peer switch number : Peer switch operational role : Virtual Switch 100 1 Virtual Switch Active 2 Virtual Switch Standby
Router# show switch virtual role Switch Switch Status Preempt Priority Role Session ID Number Oper(Conf) Oper(Conf) Local Remote -----------------------------------------------------------------LOCAL 1 UP FALSE(N) 100(100) ACTIVE 0 0 REMOTE 2 UP FALSE(N) 100(100) STANDBY 8158 1991 In dual-active recovery mode: No Router# show switch virtual link VSL Status: UP VSL Uptime: 4 hours, 26 minutes VSL SCP Ping: Pass OK VSL ICC (Ping): Pass VSL Control Link: Te 1/5/1
Converting a VSS to Standalone Chassis

To convert a VSS into two standalone chassis, you perform the following major steps:

Copying the VSS Configuration to a Backup File, page 4-38 Converting the VSS Active Chassis to Standalone, page 4-38 Converting the Peer Chassis to Standalone, page 4-38
4-37
Copying the VSS Configuration to a Backup File

Save the configuration file from the VSS active chassis. You may need this file if you convert to virtual switch mode again. You only need to save the file from the VSS active chassis, because the configuration file on the VSS standby chassis is identical to the file on the VSS active chassis. Command
Step 1
Purpose (Optional) Saves the running configuration to startup configuration. This step is only required if there are unsaved changes in the running configuration that you want to preserve. Copies the startup configuration to a backup file.
Step 2
Switch-1# copy startup-config disk0:vs-startup-config
Converting the VSS Active Chassis to Standalone

When you convert the VSS active chassis to standalone mode, the VSS active chassis removes the provisioning and configuration information related to VSL links and the peer chassis modules, saves the configuration file, and performs a reload. The chassis comes up in standalone mode with only the provisioning and configuration data relevant to the standalone system. The VSS standby chassis of the VSS becomes VSS active. VSL links on this chassis are down because the peer is no longer available. To convert the VSS active chassis to standalone mode, perform this task on the VSS active chassis: Command
Switch-1# switch convert mode stand-alone
Purpose Converts Switch 1 to standalone mode. After you enter the command, you are prompted to confirm the action. Enter yes.
Converting the Peer Chassis to Standalone

When you convert the new VSS active chassis to standalone mode, the chassis removes the provisioning and configuration information related to VSL links and the peer chassis modules, saves the configuration file and performs a reload. The chassis comes up in standalone mode with only its own provisioning and configuration data. To convert the peer chassis to standalone, perform this task on the VSS standby chassis: Command
Switch-2# switch convert mode stand-alone
Purpose Converts Switch 2 to standalone mode. After you enter the command, you are prompted to confirm the action. Enter yes.
4-38
OL-13013-06
Chapter 4
Configuring VSS Parameters

These sections describe how to configure VSS parameters:

Configuring VSL Switch Priority, page 4-39 Configuring PFC Mode, page 4-40 Configuring PFC Mode, page 4-40 Configuring a VSL, page 4-41 Displaying VSL Information, page 4-41 Configuring VSL QoS, page 4-42 Subcommands for VSL Port Channels, page 4-43 Subcommands for VSL Ports, page 4-43 Configuring the Router MAC Address Assignment, page 4-44
Configuring VSL Switch Priority

To configure the switch priority, perform this task: Command
Step 1 Step 2
Router(config)# switch virtual domain 100
Purpose Enters configuration mode for the virtual switch domain. Configures the priority for the chassis. The switch with the higher priority assumes the VSS active role. The range is 1 (lowest priority) to 255 (highest priority); the default is 100.
Note
Router(config-vs-domain)# switch [1 | 2] priority [priority_num]
The new priority value only takes effect after you save the configuration and perform a reload of the VSS. If the higher priority switch is currently in VSS standby state, you can make it the VSS active switch by initiating a switchover. Enter the redundancy force-switchover command. The show switch virtual role command displays the operating priority and the configured priority for each switch in the VSS. The no form of the command resets the priority value to the default priority value of 100. The new value takes effect after you save the configuration and perform a reload.
Step 3
Router# show switch virtual role
Displays the current priority.
4-39
Note
If you make configuration changes to the switch priority, the changes only take effect after you save the running configuration to the startup configuration file and perform a reload. The show switch virtual role command shows the operating and priority values. You can manually set the VSS standby switch to VSS active using the redundancy force-switchover command. This example shows how to configure virtual switch priority:
Router(config)# switch virtual domain 100 Router(config-vs-domain)# switch 1 priority 200 Router(config-vs-domain)# exit
This example shows how to display priority information for the VSS:
Router# show switch virtual role Switch Switch Status Preempt Priority Role Session ID Number Oper(Conf) Oper(Conf) Local Remote -----------------------------------------------------------------LOCAL 1 UP FALSE(N) 100(200) ACTIVE 0 0 REMOTE 2 UP FALSE(N) 100(100) STANDBY 8158 1991 In dual-active recovery mode: No
Configuring PFC Mode

If you have a mixture of DFC3C and DFC3CXL switching modules in the VSS, set the PFC mode by performing this task: Command
Router(config)# platform hardware vsl pfc mode pfc3c
Purpose Sets the PFC configuration mode for the VSS to PFC3C.
Note
This command requires a system reload before it takes effect.
Router# show platform hardware pfc mode
Displays the current settings for the PFC mode.
This example shows how to set the PFC configuration mode for the VSS to PFC3C. You can wait until the next maintenance window to perform the reload command.
Router(config)# platform hardware vsl pfc mode pfc3c Router(config)# end Router# reload
If all the supervisor engines and switching modules in the VSS are 3CXL, the following warning is displayed if you set the PFC mode to PFC3C:
Router(config)# platform hardware vsl pfc mode pfc3c PFC Preferred Mode: PFC3CXL. The discrepancy between Operating Mode and Preferred Mode could be due to PFC mode config. Your System has all PFC3XL modules. Remove ' platform hardware vsl pfc mode pfc3c ' from global config.
This example shows how to display the operating and configured PFC modes:
Router# show platform hardware pfc mode PFC operating mode : PFC3C Configured PFC operating mode : PFC3C
4-40
OL-13013-06
Chapter 4
Configuring a VSL
To configure a port channel to be a VSL, perform this task: Command
Step 1 Step 2
Router(config)# interface port-channel channel_num
Purpose Enters configuration mode for the specified port channel. Assigns the port channel to the virtual link for the specified switch.
Router(config-if)# switch virtual link switch_num
Note
We recommend that you configure the VSL prior to converting the chassis into a VSS. This example shows how to configure the VSL:
Switch-1(config)# interface port-channel 10 Switch-1(config-if)# switch virtual link 1 Switch-1(config-if)# no shutdown Switch-1(config)# interface tenGigabitEthernet 5/1 Switch-1(config-if)# channel-group 10 mode on Switch-1(config-if)# no shutdown Switch-2(config)# interface port-channel 25 Switch-2(config-if)# switch virtual link 2 Switch-2(config-if)# no shutdown Switch-2(config-if)# interface tenGigabitEthernet 5/2 Switch-2(config-if)# channel-group 25 mode on Switch-2(config-if)# no shutdown
Displaying VSL Information

To display information about the VSL, perform one of these tasks: Command
Router# show switch virtual link Router# show switch virtual link port-channel Router# show switch virtual link port
Purpose Displays information about the VSL. Displays information about the VSL port channel. Displays information about the VSL ports.
This example shows how to display VSL information:

Router# show switch virtual link VSL Status : UP VSL Uptime : 1 day, 3 hours, 39 minutes VSL SCP Ping : Pass VSL ICC Ping : Pass VSL Control Link : Gi1/4/2 Router# show switch virtual link port-channel VSL Port Channel Information Flags: D - down P - bundled in port-channel I - stand-alone s - suspended H - Hot-standby (LACP only)
4-41
R - Layer3 S - Layer2 U - in use N - not in use, no aggregation f - failed to allocate aggregator M m u w not in use, no aggregation due to minimum links not met not in use, port not aggregated due to minimum links not met unsuitable for bundling waiting to be aggregated
Group Port-channel Protocol Ports ------+-------------+-----------+--------------------------------------------10 Po10(RU) Te1/5/4(P) Te1/5/5(P) 20 Po20(RU) Te2/5/4(P) Te2/5/5(P) Router# show switch virtual link port VSL Link Info : Configured: 2 Operational: 1
Peer Peer Peer Interface State MAC Switch Interface ----------------------------------------------------------------------Te1/5/4 operational 0013.5fcb.1480 2 Te2/5/4 Te1/5/5 link_down Last operational Current packet Last Diag Time since Interface Failure state State Result Last Diag ------------------------------------------------------------------------------Te1/5/4 No failure Hello bidir Never ran 7M:51S Te1/5/5 No failure No failure Never ran 7M:51S
Hello Tx (T4) ms Hello Rx (T5*) ms Interface State Cfg Cur Rem Cfg Cur Rem ---------------------------------------------------------------------Te1/5/4 operational 500 500 404 5000 5000 4916 Te1/5/5 link_down 500 500000 Te2/5/4 operational 500 500 404 500000 500000 499916 Te2/5/5 link_down 500 500000 *T5 = min_rx * multiplier
Configuring VSL QoS

The VSS automatically configures VSL ports for trust CoS, using default CoS mappings (you cannot change the mappings on VSL ports). For switching modules that support per-ASIC configuration, the VSL configuration applies to all ports on the same ASIC (including any non-VSL ports). The VSS disables the QoS commands on VSL ports (and any non-VSL ports on the same ASIC). For example, you cannot use QoS queuing or map commands on VSL ports. To ensure that all eight QoS receive queues are enabled for the 10-Gigabit Ethernet ports on the supervisor engine, enter the mls qos 10g-only global configuration command. In Cisco IOS Release 12.2(33)SXI and later releases, when the mls qos 10g-only command is entered and only one of the two 10-Gigabit Ethernet ports on the supervisor engine is a VSL port, the non-VSL 10-Gigabit Ethernet port can be configured for QoS.
4-42
OL-13013-06
Chapter 4
Subcommands for VSL Port Channels

On a VSL port channel, only a subset of interface subcommands are available in the command console. Table 4-2 describes the available interface subcommands.
Table 4-2 Interface Subcommands for VSL Port Channels
Subcommand default description exit load-interval logging mls no shutdown switch virtual link vslp
Description Sets a command to its defaults. Enters a text description for the interface. Exits from interface configuration mode. Specifies interval for load calculation for an interface. Configures logging for interface. Specifies multilayer switching subcommands. Disables a command, or sets the command defaults. Shuts down the selected interface. Specifies the switch associated with this port channel. Specifies VSLP interface configuration commands.
Subcommands for VSL Ports

If a port is included in a VSL port channel, only a subset of interface subcommands are available in the command console. Table 4-3 describes the available interface subcommands.
Table 4-3 Interface Subcommands for VSL Ports
Subcommand channel-group default description exit load-interval logging no shutdown
Description Adds the interface to the specified channel group. Sets a command to its defaults. Adds a description to the interface. Exits from interface configuration mode. Specifies interval for load calculation for an interface. Configures logging for the interface. Disables a command, or sets the command defaults. Shuts down the selected interface.
4-43
Configuring the Router MAC Address Assignment

When the VSS is started for the first time, the initial VSS active supervisor engine assigns a router MAC address for the VSS. By default, the supervisor engine assigns a MAC address from its own chassis. After a switchover to the second chassis, the VSS continues to use the MAC address from the previously VSS active chassis as the router MAC address. In the rare case where both chassis later become inactive, and then they start up with the second supervisor engine becoming the initial VSS active supervisor engine, the VSS will start up with a router MAC address from the second chassis. Other Layer 2 hosts that do not respond to GARP and are not directly connected to the VSS will retain the earlier router MAC address of the VSS, and will not be able to communicate with the VSS. To avoid this possibility, you can configure the VSS to assign a router MAC address from a reserved pool of addresses with the domain ID encoded in the last octet of the MAC address, or you can specify a MAC address.
Note
If you change the router MAC address, you must reload the virtual switch for the new router MAC address to take effect. To specify that the router MAC address is assigned from a reserved pool of domain-based addresses, perform this task:
Command
Step 1 Step 2
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# mac-address use-virtual
Purpose Enters VSS configuration mode. The router MAC address is assigned from a reserved pool of domain-based addresses.
Note
The no form of this command reverts to the default setting, using a MAC address from the backplane of the initial VSS active chassis.
To specify a router MAC address, perform this task: Command

Step 1 Step 2
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# mac-address mac-address
Purpose Enters VSS configuration mode. The router MAC address is specified in three 2-byte hexadecimal numbers.
This example shows how to configure router MAC address assignment from a reserved pool of domain-based addresses:
Router(config)# switch virtual domain 255 Router(config-vs-domain)# mac-address use-virtual
The following example shows how to specify the router MAC address in hexadecimal format:
Router(config)# switch virtual domain 255 Router(config-vs-domain)# mac-address 0123.4567.89ab
4-44
OL-13013-06
Chapter 4
Configuring Deferred Port Activation During VSS Standby Recovery

Instead of allowing all ports to be activated simultaneously when a failed chassis is restarted as the VSS standby chassis, you can configure the system to defer activation of non-VSL ports and then activate the ports in groups over a period of time. To specify deferred port activation, perform this task: Command
Step 1 Step 2
Router(config)# switch virtual domain 1 Router(config-vs-domain)# standby port delay delay-time
Purpose Enters VSS configuration mode. Specifies that the port activation will be initially deferred and then performed in cycles. For delay-time, specify the period in seconds before port activation will begin. The range is 30 to 3600.
Step 3
Router(config-vs-domain)# standby port bringup number cycle-time
Specifies the number of ports to be activated per cycle and the waiting time between cycles. For number, specify the number of ports to be activated per cycle. The range is 1 to 100. The default value is 1 port. For cycle-time, specify the period in seconds between cycles. The range is 1 to 10. The default value is 1 second.
This example shows how to configure port activation to be deferred by 120 seconds, then activated in groups of 20 ports every 5 seconds:
Router(config)# switch virtual domain 1 Router(config-vs-domain)# standby port delay 120 Router(config-vs-domain)# standby port bringup 20 5
Configuring Multichassis EtherChannels

Configure multichassis EtherChannels (MECs) as you would for a regular EtherChannel. The VSS will recognize that the EtherChannel is an MEC when ports from both chassis are added to the EtherChannel. You can verify the MEC configuration by entering the show etherchannel command. One VSS supports a maximum of 512 port channels.
Note
Releases earlier than Cisco IOS Release 12.2(33)SXI support a maximum of 128 port channels.
4-45
The Configuring Port Load Share Deferral on the Peer Switch section provides additional details about MECs:
Configuring Port Load Share Deferral on the Peer Switch

To configure the load share deferral feature for a port channel, perform this task on the switch that is an MEC peer to the VSS: Command
Step 1
Router(config)# port-channel load-defer seconds
Purpose (Optional) Configures the port load share deferral interval for all port channels.
secondsThe time interval during which load sharing is initially 0 for deferred port channels. The range is 1 to 1800 seconds; the default is 120 seconds.
Step 2 Step 3
Router(config)# interface port-channel channel-num Router(config-if)# port-channel port load-defer
Enters interface configuration mode for the port channel. Enables port load share deferral on the port channel.
This example shows how to configure the load share deferral feature on port channel 10 of the switch that is an MEC peer to the VSS:
Router(config)# port-channel load-defer 60 Router(config)# interface port-channel 10 Router(config-if)# port-channel port load-defer This will enable the load share deferral feature on this port-channel. Do you wish to proceed? [yes/no]: yes
Configuring Dual-Active Detection

The following sections describe how to configure dual-active detection:

Configuring Enhanced PAgP Dual-Active Detection, page 4-46 Configuring BFD Dual-Active Detection, page 4-48 Configuring Fast Hello Dual-Active Detection, page 4-49 Configuring the Exclusion List, page 4-50 Displaying Dual-Active Detection, page 4-50
Configuring Enhanced PAgP Dual-Active Detection

If enhanced PAgP is running on the MECs between the VSS and its access switches, the VSS can use enhanced PAgP messaging to detect a dual-active scenario. By default, PAgP dual-active detection is enabled. However, the enhanced messages are only sent on port channels with trust mode enabled (see the trust mode description in the note).
4-46
OL-13013-06
Chapter 4
Note
Before changing PAgP dual-active detection configuration, ensure that all port channels with trust mode enabled are in administrative down state. Use the shutdown command in interface configuration mode for the port channel. Remember to use the no shutdown command to reactivate the port channel when you are finished configuring dual-active detection. To enable or disable PAgP dual-active detection, perform this task:
Command
Step 1 Step 2
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# dual-active detection pagp
Purpose Enters virtual switch submode. Enables sending of the enhanced PAgP messages.
You must configure trust mode on the port channels that will detect PAgP dual-active detection. By default, trust mode is disabled.
Note
If PAgP dual-active detection is enabled, you must place the port channel in administrative down state before changing the trust mode. Use the shutdown command in interface configuration mode for the port channel. Remember to use the no shutdown command to reactivate the port channels when you are finished configuring trust mode on the port channel. To configure trust mode on a port channel, perform this task:
Command
Step 1 Step 2
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# dual-active detection pagp trust channel-group group_number
Purpose Enters virtual switch submode. Enables trust mode for the specified port channel.
This example shows how to enable PAgP dual-active detection:

Router(config)# interface port-channel 20 Router(config-if)# shutdown Router(config-if)# exit Router(config)# switch virtual domain 100 Router(config-vs-domain)# dual-active detection pagp Router(config-vs-domain)# dual-active detection pagp trust channel-group 20 Router(config-vs-domain)# exit Router(config)# interface port-channel 20 Router(config-if)# no shutdown Router(config-if)# exit
This example shows the error message if you try to enable PAgP dual-active detection when a trusted port channel is not shut down first:
Router(config)# switch virtual domain 100 Router(config-vs-domain)# dual-active detection pagp Trusted port-channel 20 is not administratively down. To change the pagp dual-active configuration, shutdown these port-channels first. Remember to no shutdown these port-channels afterwards.
This example shows the error message if you try to configure trust mode for a port channel that is not shut down first:
Router(config)# switch virtual domain 100
4-47
Router(config-vs-domain)# dual-active detection pagp trust channel-group 20 Trusted port-channel 20 is not administratively down. To change the pagp dual-active trust configuration, shutdown the port-channel first. Remember to no shutdown the port-channel afterwards.
Configuring BFD Dual-Active Detection

For the BFD dual-active detection, you must configure dual-active interface pairs that will act as BFD messaging links. By default, BFD detection is enabled. To configure BFD dual-active detection, perform this task: Command
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# dual-active detection bfd
Purpose Enters virtual switch submode. Enables BFD dual-active detection method. By default, BFD detection is enabled. Configures the dual-active pair of interfaces. The interfaces int_1 and int_2 are of the form
type1 switch/slot/port.
Router(config-vs-domain)# dual-active pair interface int_1 interface int_2 bfd
The interfaces must be directly connected (a single Layer 3 hop).

1. type = fastethernet, gigabitethernet, or tengigabitethernet
When you configure the dual-active interface pairs, note the following information:

The individual ports must be configured first with both an IP address and BFD configuration. The configuration is validated when you add the dual-active interface pair. The IP addresses assigned to the dual-active pair must be from two different networks or subnetworks. The BFD timers must be configured with the same values on the ports at both ends of the link to ensure proper operation of Layer 3 BFD dual-active detection. The MAC address cannot be specified on the interface.
Note
We recommend that you configure a short BFD interval and small multiplier value (such as 50 to 100 ms for the interval and 3 as the multiplier value). If the interval and multiplier values are large, there is a long delay before the system initiates dual-active mode recovery. This condition can cause network instability and poor convergence. This example shows how to configure interfaces for BFD dual-active detection:
Router Router Router Router Router Router Router Router Router Router Router Router (config)# interface gigabitethernet 1/9/48 (config-if)# no switchport (config-if)# ip address 200.230.230.231 255.255.255.0 (config-if)# bfd interval 100 min_rx 100 multiplier 3 (config-if)# no shutdown (config-if)# interface gigabitethernet 2/1/48 (config-if)# no switchport (config-if)# ip address 201.230.230.231 255.255.255.0 (config-if)# bfd interval 100 min_rx 100 multiplier 3 (config-if)# no shutdown (config-if)# exit (config)# switch virtual domain 100
4-48
OL-13013-06
Chapter 4
Router (config-vs-domain)# dual-active detection bfd Router (config-vs-domain)# dual-active pair interface g 1/9/48 interface g 2/1/48 bfd adding a static route 200.230.230.0 255.255.255.0 Gi2/1/48 for this dual-active pair adding a static route 201.230.230.0 255.255.255.0 Gi1/9/48 for this dual-active pair Router(config-vs-domain)# exit Router(config)# exit Router# show switch virtual dual-active bfd Bfd dual-active detection enabled: Yes Bfd dual-active interface pairs configured: interface1 Gi1/9/48 interface2 Gi2/1/48
Configuring Fast Hello Dual-Active Detection

Fast hello dual-active detection is enabled by default; however, you must configure dual-active interface pairs to act as fast hello dual-active messaging links. To configure fast hello dual-active detection, perform this task: Command
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# dual-active detection fast-hello Router(config-vs-domain)# exit Router(config)# interface type
1
Purpose Enters the virtual switch submode. Enables the fast hello dual-active detection method. Fast hello dual-active detection is enabled by default. Exits virtual switch submode.
switch/slot/port
Selects the interface to configure. This interface must be directly connected to the other chassis and must not be a VSL link. Enables fast hello dual-active detection on the interface, automatically removes all other configuration from the interface, and restricts the interface to dual-active configuration commands. Activates the interface.
Step 5
Router(config-if)# dual-active fast-hello
Step 6
Router(config-if)# no shutdown 1. type = fastethernet, gigabitethernet, or tengigabitethernet
When you configure fast hello dual-active interface pairs, note the following information:

You can configure a maximum of four interfaces on each chassis to connect with the other chassis in dual-active interface pairs. Each interface must be directly connected to the other chassis and must not be a VSL link. We recommend using links from a switching module not used by the VSL. Each interface must be a physical port. Logical ports such as an SVI are not supported. Configuring fast hello dual-active mode will automatically remove all existing configuration from the interface and will restrict the interface to fast hello dual-active configuration commands. Unidirectional link detection (UDLD) will be disabled on fast hello dual-active interface pairs.
This example shows how to configure an interface for fast hello dual-active detection:
Router(config)# switch virtual domain 255 Router(config-vs-domain)# dual-active detection fast-hello Router(config-vs-domain)# exit Router(config)# interface fastethernet 1/2/40
4-49
Router(config-if)# dual-active fast-hello WARNING: Interface FastEthernet1/2/40 placed in restricted config mode. All extraneous configs removed! Router(config-if)# no shutdown Router(config-if)# exit Router(config)# exit Router# show run interface fastethernet 1/2/40 interface FastEthernet1/2/40 no switchport no ip address dual-active fast-hello end
Configuring the Exclusion List

When a dual-active scenario is detected, part of the recovery action is for the chassis to shut down all of its non-VSL interfaces. You can specify one or more interfaces to be excluded from this action (for example, to exclude the interface you use for remote access to the chassis). To specify interfaces that are not to be shut down by dual-active recovery, perform this task: Command
Step 1 Step 2
Router(config)# switch virtual domain domain_id Router(config-vs-domain)# dual-active exclude interface type1 switch/slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Enters virtual switch submode. Specifies an interface to exclude from shutting down in dual-active recovery.
When you configure the exclusion list, note the following information:

The interface must be a physical port configured with an IP address. The interface must not be a VSL port. The interface must not be in use for IP BFD dual-active detection. The interface must not be in use for fast hello dual-active detection.
This example shows how to configure an interface as an exclusion:

Router(config)# switch virtual domain 100 Router (config-vs-domain)# dual-active exclude interface gigabitethernet 1/5/5
Displaying Dual-Active Detection

To display information about dual-active detection, perform this task: Command
Router# show switch virtual dual-active [bfd | pagp | fast-hello | summary]
Purpose Displays information about dual-active detection configuration and status.
This example shows how to display the summary status for dual-active detection:
Router# show switch virtual dual-active summary Pagp dual-active detection enabled: Yes
4-50
OL-13013-06
Chapter 4
Bfd dual-active detection enabled: Yes Fast-hello dual-active detection enabled: Yes No interfaces excluded from shutdown in recovery mode In dual-active recovery mode: No
This example shows how to display information for BFD dual-active detection:
Router# show switch virtual dual-active bfd Bfd dual-active detection enabled: Yes Bfd dual-active interface pairs configured: interface1 Gi1/9/48 interface2 Gi2/1/48
This example shows how to display information for fast-hello dual-active detection:
Router# show switch virtual dual-active fast-hello Fast-hello dual-active detection enabled: Yes Fast-hello dual-active interfaces: Port State (local only) ----------------------------Gi1/4/47 Link dn Gi2/4/47 -
This example shows how to display PAgP status and the channel groups with trust mode enabled:
Router# show pagp dual-active PAgP dual-active detection enabled: Yes PAgP dual-active version: 1.1 Channel group 3 dual-active detect capability w/nbrs Dual-Active trusted group: No Dual-Active Partner Partner Partner Port Detect Capable Name Port Version Fa1/2/33 No None None N/A Channel group 4 Dual-Active trusted group: Yes No interfaces configured in the channel group Channel group 5 Dual-Active trusted group: Yes Channel group 5 is not participating in PAGP Channel group 10 dual-active detect capability w/nbrs Dual-Active trusted group: Yes Dual-Active Partner Partner Partner Port Detect Capable Name Port Version Gi1/6/1 Yes partner-1 Gi1/5/1 1.1 Gi2/5/1 Yes partner-1 Gi1/5/2 1.1 Channel group 11 dual-active detect capability w/nbrs Dual-Active trusted group: No Dual-Active Partner Partner Partner Port Detect Capable Name Port Version Gi1/6/2 Yes partner-1 Gi1/3/1 1.1 Gi2/5/2 Yes partner-1 Gi1/3/2 1.1 Channel group 12 dual-active detect capability w/nbrs Dual-Active trusted group: Yes Dual-Active Partner Partner Partner Port Detect Capable Name Port Version Fa1/2/13 Yes partner-1 Fa1/2/13 1.1 Fa1/2/14 Yes partner-1 Fa1/2/14 1.1 Gi2/1/15 Yes partner-1 Fa1/2/15 1.1 Gi2/1/16 Yes partner-1 Fa1/2/16 1.1
4-51
Note
The show switch virtual dual-active pagp command displays the same output as the show pagp dual-active command.
Configuring Service Modules in a VSS

To configure a service module in a VSS, you must add the switch number to many of the configuration commands, as described in this section.
Note
For detailed instructions on configuring a service module in a VSS, see the configuration guide and command reference for the service module. The following sections provide examples of how to configure a service module in a VSS:

Opening a Session with a Service Module in a VSS, page 4-52 Assigning a VLAN Group to a Firewall Service Module in a VSS, page 4-53 Assigning a VLAN Group to an ACE Service Module in a VSS, page 4-53 Verifying Injected Routes in a Service Module in a VSS, page 4-54
Opening a Session with a Service Module in a VSS

To configure service modules that require opening a session, perform this task: Command
Router# session switch num slot slot processor processor-id
Purpose Opens a session with the specified module.

numSpecifies the switch to access; valid values are 1 and 2. slotSpecifies the slot number of the module. processor-idSpecifies the processor ID number. Range: 0 to 9.
This example shows how to open a session to a Firewall Service Module in a VSS:
Router# session switch 1 slot 4 processor 1 The default escape character is Ctrl-^, then x. You can also type 'exit' at the remote prompt to end the session Trying 127.0.0.41 ... Open
4-52
OL-13013-06
Chapter 4
Assigning a VLAN Group to a Firewall Service Module in a VSS

To assign a VLAN group to a FWSM, perform this task: Command
Router(config)# firewall switch num slot slot vlan-group [vlan_group | vlan_range]
Purpose Assigns VLANs to a firewall group in the specified module.

numSpecifies the switch to access; valid values are 1 and 2. slotSpecifies the slot number of the module. vlan_groupSpecifies the group ID as an integer. vlan_rangeSpecifies the VLANs assigned to the group.
This example shows how to assign a VLAN group to a Firewall Service Module in a VSS:
Router(config)# firewall switch 1 slot 4 vlan-group 100,200
Assigning a VLAN Group to an ACE Service Module in a VSS

To assign a VLAN group to an ACE, perform this task: Command
Step 1 Step 2
Router(config)# svclc multiple-vlan-interfaces
Purpose Enables multiple VLAN interfaces mode for service modules. Assign VLANs to a firewall group in the specified module.

Router(config)# svclc switch num slot slot vlan-group [vlan_group | vlan_range]
numSpecifies the switch to access; valid values are 1 and 2. slotSpecifies the slot number of the module. vlan_groupSpecifies the group ID as an integer. vlan_rangeSpecifies the VLANs assigned to the group.
This example shows how to assign multiple VLAN groups to an ACE service module in a VSS:
Router(config)# svclc multiple-vlan-interfaces Router(config)# svclc switch 1 slot 4 vlan-group 100,200
4-53
Verifying Injected Routes in a Service Module in a VSS

To view route health injection (RHI) routes, perform this task: Command
Router# show svclc rhi-routes switch num slot slot
Purpose Displays injected RHI routes in the specified service module.

numSpecifies the switch to access; valid values are 1 and 2. slotSpecifies the slot number of the module.
This example shows how to view injected routes in a service module in a VSS:
Router# show svclc rhi-routes switch 1 slot 4 RHI routes added by slot 34 ip mask nexthop vlan weight tableid
--------------- --------------- --------------- ------ ------ ------A 23.1.1.4 255.255.255.252 20.1.1.1 20 1 0
Viewing Chassis Status and Module Information in a VSS

To view chassis status and information about modules installed in either or both chassis of a VSS, perform the following task: Command
Router# show module switch { 1 | 2 | all }
Purpose Displays information about modules in the specified chassis (1 or 2), or in both chassis (all).
This example shows how to view the chassis status and module information for chassis number 1 of a VSS:
Router# show module switch 1 Switch Number: 1 Role: Virtual Switch Active
---------------------Mod Ports Card Type
----------------------------Model Serial No.
--- ----- -------------------------------------- ------------------ ----------1 2 3 . . . 48 8 1 CEF720 48 port 10/100/1000mb Ethernet CEF720 8 port 10GE with DFC Application Control Engine Module WS-X6748-GE-TX WS-X6708-10GE ACE20-MOD-K9 SAL1215M2YA SAL1215M55F SAD120603SU
4-54
OL-13013-06
Chapter 4
Configuring Virtual Switching Systems Upgrading a VSS
Upgrading a VSS
Cisco IOS Rel ease 12.2(33)SXH supports a fast software upgrade (FSU) of the VSS using RPR. Cisco IOS Release 12.2(33)SXI and later releases support an enhanced fast software upgrade (eFSU) of the VSS using SSO. This section describes both types of VSS upgrade:

Performing a Fast Software Upgrade of a VSS, page 4-55 Performing an Enhanced Fast Software Upgrade of a VSS, page 4-56
Performing a Fast Software Upgrade of a VSS

The FSU of a VSS is similar to the RPR-based standalone chassis FSU described in the Performing a Fast Software Upgrade section on page 7-6. While the standalone chassis upgrade is initiated by reloading the VSS standby supervisor engine, the VSS upgrade is initiated by reloading the VSS standby chassis. During the FSU procedure, a software version mismatch between the VSS active and the VSS standby chassis causes the system to boot in RPR redundancy mode, which is stateless and causes a hard reset of the all modules. As a result, the FSU procedure requires system downtime corresponding to the RPR switchover time.
Note
VSS mode supports only one supervisor engine in each chassis. If another supervisor engine resides in the chassis it will act as the DFC. To perform an FSU of a VSS, perform this task:
Command
Step 1
Router# copy tftp disk_name
Purpose Uses TFTP to copy the new software image to flash memory on the VSS active and VSS standby chassis (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image. Enters global configuration mode. Removes any previously assigned boot variables. Sets the configuration register. Configures the chassis to boot the new image. Returns to privileged EXEC mode. Saves the configuration.
Router# config terminal Router(config)# no boot system Router(config)# config-register 0x2102 Router(config)# boot system flash device:file_name Router(config)# end Router# copy running-config startup-config
4-55
Chapter 4 Upgrading a VSS
Command
Step 8
Router# redundancy reload peer
Purpose Reloads the VSS standby chassis and brings it back online running the new version of the Cisco IOS software. Due to the software version mismatch between the two chassis, the VSS standby chassis will be in RPR redundancy mode.
Note
Before reloading the VSS standby chassis, make sure you wait long enough to ensure that all configuration synchronization changes have completed.
Step 9
Router# redundancy force-switchover
Forces the VSS standby chassis to assume the role of the VSS active chassis running the new Cisco IOS image. The modules are reloaded and the module software is downloaded from the new VSS active chassis. The old VSS active chassis reboots with the new image and becomes the VSS standby chassis.
This example shows how to perform an FSU:

Router# config terminal Router(config)# no boot system Router(config)# config-register 0x2102 Router(config)# boot system flash disk0:image_name Router(config)# end Router# copy running-config startup-config Router# redundancy reload peer Router# redundancy force-switchover
Performing an Enhanced Fast Software Upgrade of a VSS

An eFSU uses the same commands and software infrastructure as an in-service software upgrade (ISSU). The eFSU differs from an ISSU in that it resets the modules, which results in a brief traffic interruption. The eFSU sequence for a VSS follows the same logical steps as the single-chassis eFSU described in the Performing an Enhanced Fast Software Upgrade section on page 5-5, but the procedure applies to the VSS active and VSS standby supervisor engine in each chassis, instead of two supervisor engines in one chassis. During an eFSU, the VSS standby chassis, including the supervisor engine and modules, is upgraded and brought up in a stateful switchover (SSO) mode. The eFSU process then forces a switchover and performs the same upgrade on the other chassis, which becomes the new VSS standby.
Note
VSS mode supports only one supervisor engine in each chassis. If another supervisor resides in the chassis it will act as the DFC. This section contains the following topics:

eFSU Restrictions and Guidelines, page 4-57 eFSU Stages for a VSS Upgrade, page 4-57 Configuring and Performing an eFSU Upgrade, page 4-59 eFSU Upgrade Example, page 4-67
4-56
OL-13013-06
Chapter 4
eFSU Restrictions and Guidelines

When performing an eFSU, note the following guidelines and restrictions:
An eFSU can install a full image upgrade or a patch upgrade. Any patch upgrade will be installed by the same process as a full image upgrade, regardless of whether the patch requires a reload or a process restart. The new image file must reside in the file system of the supervisor engine in each chassis before the eFSU can be initiated. The issu commands will accept only global file system names (for example, disk0: or sup-bootdisk:). The issu commands will not accept switch number-specific file system names (for example, sw1-slot5-disk0:). When preparing for the eFSU, do not change the boot variable. Although a boot variable change is required in the FSU (RPR) procedure, changing the boot variable in the eFSU procedure will cause the CurrentVersion variable to be inconsistent, preventing execution of the eFSU. The issu commands for a VSS eFSU upgrade are similar to those for a single-chassis (standalone) eFSU, as described in the Performing an Enhanced Fast Software Upgrade section on page 5-5, with the following differences:
Where the standalone issu commands accept an argument of slot number, the VSS issu
commands accept a switch and slot number, in the format of switch/slot (for example, 1/5 refers to switch 1, slot 5).
For a normal VSS eFSU, it is not necessary to specify a switch or slot number when entering
the VSS issu commands.

You cannot change the rollback timer period during the eFSU process. During the eFSU process, do not perform any manual switchover other than those caused by the issu commands. During the eFSU process, do not perform an online insertion or removal (OIR) of any module. During an eFSU downgrade, if the process is aborted (either due to an MCL error or by entering the abortversion command) just after executing the loadversion command, the SSO VSS standby is reloaded with the original image but the SSO VSS standbys ICS is not because the bootvar of the SSO VSS standbys ICS is not modified during an abort executed after the loadversion command.
eFSU Stages for a VSS Upgrade

The eFSU sequence consists of several stages, each explicitly initiated by entering a specific issu command in the CLI. At each stage, you can verify the system status or roll back the upgrade before moving to the next stage.
4-57
The following sections describe the eFSU stages for a VSS upgrade:

Preparation, page 4-58 Loadversion Stage, page 4-58 Runversion Stage, page 4-58 Acceptversion Stage (Optional), page 4-58 Commitversion Stage, page 4-59 Abortversion (Optional), page 4-59
Preparation
Before you can initiate the eFSU process, the upgrade image must reside in the file system of the supervisor engine in each chassis; otherwise, the initial command will be rejected. The VSS must be in a stable operating state with one chassis in the VSS active state and the other chassis in the hot VSS standby state.
Loadversion Stage
The eFSU process begins when you enter the issu loadversion command specifying the location in memory of the new upgrade images on the VSS active and VSS standby chassis. Although the issu loadversion command allows you to specify the switch and slot number of the VSS active and VSS standby chassis, it is not necessary to do so. When you enter the issu loadversion command, the entire VSS standby chassis, including the supervisor engine and modules, is reloaded with the new upgrade image. Because the VSS standby chassis modules are unavailable while reloading, the throughput of the VSS is temporarily reduced by 50 percent during this stage. After reloading, the VSS standby chassis boots with the new image and initializes in SSO mode, restoring traffic throughput. In this state, the VSS standby chassis runs a different software version than the VSS active chassis, which requires the VSS active chassis to communicate with modules running different image versions between the two chassis.
Runversion Stage
When the VSS standby chassis is successfully running the new image in SSO mode, you can enter the issu runversion command. This command forces a switchover in which the upgraded VSS standby chassis takes over as the new VSS active chassis. The formerly VSS active chassis reloads and initializes as the new VSS standby chassis in SSO mode, running the old image. As in the loadversion stage, the throughput of the VSS is temporarily reduced during the VSS standby chassis reload, and the VSS standby chassis runs a different software version than the VSS active chassis.
Acceptversion Stage (Optional)

When you enter the issu runversion command, a switchover to the chassis running the new image occurs, which starts an automatic rollback timer as a safeguard to ensure that the upgrade process does not cause the VSS to be nonoperational. Before the rollback timer expires, you must either accept or commit the new software image. If the timer expires, the upgraded chassis reloads and reverts to the previous software version. To stop the rollback timer, enter the issu acceptversion command. Prior to starting the eFSU process, you can disable the rollback timer or configure it to a value up to two hours (the default is 45 minutes). Operating with an upgraded VSS active chassis, this stage allows you to examine the functionality of the new software image. When you are satisfied that the new image is acceptable, enter the issu commitversion command to complete the upgrade process.
4-58
OL-13013-06
Chapter 4
Commitversion Stage
To apply the upgrade image to the second chassis, completing the eFSU, enter the issu commitversion command. The VSS standby chassis is reloaded and booted with the new upgrade image, initializing again as the VSS standby chassis. As in the loadversion stage, the throughput of the VSS is temporarily reduced while the modules are reloaded and initialized. After the successful reload and reboot of the VSS standby chassis, the VSS upgrade process is complete.
Abortversion (Optional)
At any time before you enter the issu commitversion command, you can roll back the upgrade by entering the issu abortversion command. The upgrade process also aborts automatically if the software detects a failure. The rollback process depends on the current state. If the eFSU is aborted before you enter the issu runversion command, the VSS standby chassis is reloaded with the old image. If the eFSU is aborted after the issu runversion command, a switchover is executed. The VSS standby chassis, running the old image, becomes the VSS active chassis. The formerly VSS active chassis is then reloaded with the old image, completing the rollback.
Configuring and Performing an eFSU Upgrade

The following sections describe how to configure and perform an eFSU upgrade:

Changing the eFSU Rollback Timer, page 4-60 Performing an eFSU Upgrade, page 4-60 Performing an eFSU Upgrade from Previous Cisco IOS Releases to Cisco IOS Release 12.2(33)SXI4, page 4-61 Performing an eFSU Upgrade from Cisco IOS Release 12.2(33)SXI4 to Future Cisco IOS Releases, page 4-62 Performing an eFSU Downgrade from Cisco IOS Release 12.2(33)SXI4 to Earlier Cisco IOS Releases, page 4-63 Performing an eFSU Downgrade from a Future Cisco IOS Release to Cisco IOS Release 12.2(33)SXI4, page 4-65 Performing an eFSU Upgrade on an Installed Modular Image, page 4-66 Aborting an eFSU Upgrade, page 4-67
4-59
Changing the eFSU Rollback Timer

To view or change the eFSU rollback timer, perform the following task before beginning an upgrade: Command
Step 1 Step 2
Router# config terminal Router(config)# issu set rollback-timer {seconds | hh:mm:ss}
Purpose Enters configuration mode. (Optional) Sets the rollback timer to ensure that the upgrade process does not leave the VSS nonoperational. If the timer expires, the software image reverts to the previous software image. To stop the timer, you must either accept or commit the new software image. The timer duration can be set with one number (seconds), indicating the number of seconds, or as hours, minutes, and seconds with a colon as the delimiter (hh:mm:ss). The range is 0 to 7200 seconds (2 hours); the default is 2700 seconds (45 minutes). A setting of 0 disables the rollback timer.
Step 3 Step 4
Router(config)# exit Router# show issu rollback timer
Returns to privileged EXEC mode. Displays the current rollback timer value.
This example shows how to set the eFSU rollback timer to one hour using both command formats:
Router# config terminal Router(config)# issu set rollback-timer 3600 % Rollback timer value set to [ 3600 ] seconds Router(config)# issu set rollback-timer 01:00:00 % Rollback timer value set to [ 3600 ] seconds Router(config)#
Performing an eFSU Upgrade

To perform an eFSU upgrade (or downgrade) of a VSS, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to flash memory on the VSS active and VSS standby chassis (disk0: and slavedisk0:) and to the ICSs, if they exist. Answer the prompts to identify the name and location of the new software image. (Optional) Verifies that the VSS is ready to run the eFSU.
Note
Step 2
Router# show issu state [switch/slot] [detail]
You can use the show issu state command at any stage of the upgrade to verify the progress and status of the upgrade.
Step 3
Router# issu loadversion [active_switch/slot] active-image [standby_switch/slot] standby-image
Starts the upgrade process by loading the new software image onto the VSS standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the VSS standby chassis to transition to SSO mode.
4-60
OL-13013-06
Chapter 4
Command
Step 4
Router# issu runversion
Purpose Forces a switchover, causing the VSS standby chassis to become VSS active and begin running the new software. The previously VSS active chassis becomes VSS standby and boots with the old image. (Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process. Loads the new software image onto the VSS standby chassis. Verifies the status of the upgrade process. If the upgrade was successful, both the VSS active and VSS standby chassis are running the new software version.
Step 5
Router# issu acceptversion
Step 6 Step 7
Router# issu commitversion
Router# show issu state [switch/slot][detail]
For an example of the eFSU upgrade sequence, see the eFSU Upgrade Example section on page 4-67.
Performing an eFSU Upgrade from Previous Cisco IOS Releases to Cisco IOS Release 12.2(33)SXI4
With previous Cisco IOS releases if you have a second ICS in your chassis, it will be forced to ROMMON. To perform an eFSU upgrade of a VSS from Cisco IOS Release 12.2(33)SXI to Cisco IOS Release 12.(33)SXI4, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to flash memory on the active and standby chassis (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image. (Optional) Verifies that the VSS is ready to run the eFSU.
Note
Step 2
Step 3
Starts the upgrade process by loading the new software image onto the standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.
Step 4
Forces a switchover, causing the standby chassis to become active and begin running the new software. The previously active chassis becomes standby and boots with the old image. (Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process.
Step 5
4-61
Command
Step 6 Step 7
Router# issu commitversion Router# show issu state [switch/slot][detail]
Purpose Loads the new software image onto the standby chassis. Verifies the status of the upgrade process. If the upgrade was successful, both the active and standby chassis are running the new software version.
If you intend to bring up the ICS supervisor engine with Cisco IOS Release 12.2(33)SXI4, you will need to manually boot up the ICS supervisor engine after the eFSU cycle is complete.
Performing an eFSU Upgrade from Cisco IOS Release 12.2(33)SXI4 to Future Cisco IOS Releases
To perform an eFSU upgrade of a VSS from Cisco IOS Release 12.2(33)SXI4 to a future Cisco IOS Release, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to flash memory on the active and standby chassis (disk0: and slavedisk0:) and to the ICSs, if they exist. Answer the prompts to identify the name and location of the new software image. (Optional) Verifies that the VSS is ready to run the eFSU.
Note
Step 2
Step 3
Router# switch virtual in-chassis standby switch [disable | enable]
(Optional) Includes or removes the ICS, from the eFSU cycle. This command must be executed before the start of the eFSU cycle even if the ICS is in ROMMON. Starts the upgrade process by loading the new software image onto the standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.
Step 4
Note
This command is not extended for the ICS. The file system mentioned for the ICA is used for the respective ICS. For example, if the issu loadversion disk0:image_name slavesup-bootdisk:image_name command is executed the loadversion command is accepted. The presence of the image is checked in the disk0: for the active supervisor engine (both the ICA and ICS) and the SPs bootdisk for the SSO standby (both the ICA and ICS).
4-62
OL-13013-06
Chapter 4
Command
Step 5
Purpose Forces a switchover, causing the standby engine chassis to become active and begin running the new software. The previously active chassis becomes standby and boots with the old image.
Note
If there are two supervisor engines in the active chassis, an in-chassis role reversal will occur if the upgrade cycle starts with both supervisor engines in the active chassis unless you have configured a supervisor engine to not participate in the upgrade.
Step 6
(Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process. Loads the new software image onto the standby chassis. Verifies the status of the upgrade process. If the upgrade was successful, both the active and standby chassis are running the new software version. The ICS is forced to ROMMON.
Step 7 Step 8
If the ICS is participating in the eFSU upgrade, you must ensure that the ICS is up and running before performing each ISSU step. If the ICS is not up and running, you need to wait until it is online. You can verify that the ICS is online by entering the show module command.
Performing an eFSU Downgrade from Cisco IOS Release 12.2(33)SXI4 to Earlier Cisco IOS Releases
To perform an eFSU downgrade of a VSS from Cisco IOS Release 12.2(33)SXI4 to an earlier Cisco IOS release, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to flash memory on the active and standby chassis (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image. (Optional) Verifies that the VSS is ready to run the eFSU.
Note
Step 2
Step 3
(Optional) Includes or removes the ICS from the eFSU cycle. This command must be executed before the start of the eFSU cycle even if the ICS is in ROMMON.
4-63
Command
Step 4
Purpose Starts the downgrade process by loading the new software image onto the standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.
Note
If the active ICS is online when you enter the issu loadversion command, then an error message is displayed when the standby supervisor engine is booting up with the pre-12.2(33)SXI4 image, which prompts you to disable the active ICS. Once you disable the active ICS, the cycle will proceed. If you do not disable the active ICS and enter the issu runversion command, the command is not accepted. You will have to either abort the downgrade process or disable the active ICS to proceed with the downgrade. If the standby ICS is online when you enter the issu loadversion command, the pre-12.2(33)SXI4 image that comes up on the SSO standby forces the standby ICS to ROMMON.
Step 5
Forces a switchover, causing the standby chassis to become active and begin running the new software. The previously active chassis becomes standby and boots with the old image. (Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process. Loads the new software image onto the standby chassis. Verifies the status of the downgrade process. If the downgrade was successful, both the active and standby chassis are running the new software version.
Step 6
Step 7 Step 8
4-64
OL-13013-06
Chapter 4
Performing an eFSU Downgrade from a Future Cisco IOS Release to Cisco IOS Release 12.2(33)SXI4
To perform an eFSU downgrade of a VSS from a future Cisco IOS Release to Cisco IOS Release 12.2(33)SXI4, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to the ICSs and flash memory on the active and standby chassis (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image. (Optional) Verifies that the VSS is ready to run the eFSU.
Note
Step 2
Step 3
(Optional) Includes or removes the ICS from the eFSU cycle. This command must be executed before the start of the eFSU cycle even if the ICS is in ROMMON.
Note
If you did not remove the ICS from the downgrade using the switch virtual disable command the loadversion cycle is aborted, the SSO standby reloads with the initial image.
Step 4
Starts the downgrade process by loading the new software image onto the standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.
Note
This command is not extended for the ICS. The file system mentioned for the ICA is used for the respective ICS. For example, if the issu loadversion disk0:image_name slavesup-bootdisk:image_name command is executed the loadversion command is accepted. The presence of the image is checked in the disk0: for the active supervisor engine (both the ICA and ICS) and the SPs bootdisk for the SSO standby (both the ICA and ICS).
Step 5
Forces a switchover, causing the standby chassis to become active and begin running the new software. The previously active chassis becomes standby and boots with the old image. (Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process.
Step 6
4-65
Command
Step 7 Step 8
Purpose Loads the new software image onto the standby chassis. Verifies the status of the downgrade process. If the downgrade was successful, both the active and standby chassis are running the new software version.
If the ICS is participating in the eFSU upgrade, you must ensure that the ICS is up and running before performing each ISSU step. If the ICS is not up and running you need to wait until it is online. You can verify that the ICS is online by entering the show module command.
Performing an eFSU Upgrade on an Installed Modular Image

To perform an eFSU upgrade (or downgrade) of an ION VSS, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to flash memory on the active and VSS standby chassis (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image.
Note
You should have a console on both the active and VSS standby supervisor engines because you will go back and forth between them.
Router# install file bootdisk:filename bootdisk:/location Router# show issu state [switch/slot][detail]
Installs the modular image on to both the active and VSS standby supervisor engines. Verifies the status of the upgrade process; status should display Init. Starts the upgrade process by loading the installed software image onto the active and VSS standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the VSS standby chassis to transition to SSO mode.
Router# issu loadversion new-image
Note
This command will cause the VSS standby chassis to reload.
Step 5 Step 6
Verifies the status of the upgrade process; status should display Load Version. Forces a switchover, causing the VSS standby chassis to become active and begin running the new software. The previously active chassis becomes VSS standby and boots with the old image. Verifies the status of the upgrade process; status should display Run Version.
Step 7
4-66
OL-13013-06
Chapter 4
Command
Step 8
Purpose Loads the new software image onto the VSS standby chassis.
Note
This command will cause the VSS standby chassis to reload.
Step 9 Step 10
Verifies the status of the upgrade process; status should display Init. (Optional) Forces the VSS standby Route Processor (RP) to assume the role of the active RP.
For an example of the eFSU upgrade on an Installed Modular Image sequence, see the eFSU Upgrade on an Installed Modular Image Example section on page 4-68.
Aborting an eFSU Upgrade

To manually abort the eFSU and roll back the upgrade, perform this task: Command
Router# issu abortversion
Purpose Stops the upgrade process and forces a rollback to the previous software image.
This example shows how to abort an eFSU upgrade for a VSS:

Router# issu abortversion
eFSU Upgrade Example

This example shows how to perform and verify an eFSU upgrade for a VSS.
Verify the System Readiness

After copying the new image files into the file systems of the active and VSS standby chassis, enter the show issu state detail command and the show redundancy status command to check that the VSS is ready to perform the eFSU. One chassis must be in the active state and the other chassis in the hot VSS standby state. Both chassis should be in the ISSU Init state and in SSO redundancy state. In the example, both chassis are running an oldversion image.
Router# show issu state detail Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version Variable Store = = = = = = = = = 1/2 Active Init disk0:s72033-oldversion.v1,12; sso N/A N/A disk0:s72033-oldversion.v1 PrstVbl
Slot = 2/7 RP State = Standby ISSU State = Init
4-67
Boot Variable Operating Mode Primary Version Secondary Version Current Version
= = = = =
disk0:s72033-oldversion.v1,12; sso N/A N/A disk0:s72033-oldversion.v1
Router# show redundancy status my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Secondary Unit ID = 18 Redundancy Mode (Operational) = sso Redundancy Mode (Configured) = sso Redundancy State = sso Maintenance Mode = Disabled Communications = Up client count = 132 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
30000 milliseconds 9000 milliseconds 0 18 0x0
eFSU Upgrade on an Installed Modular Image Example

This example shows how to perform an an eFSU upgrade on an installed modular image:
Router# copy ftp://172.18.108.26/s72033-advipservicesk9_wan-vz.122-33.SXI2 sup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin Router# copy ftp://172.18.108.26/s72033-advipservicesk9_wan-vz.122-33.SXI2 slavesup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin Router# install file sup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin sup-bootdisk:/newsys Router# install file slavesup-bootdisk:s72033-advipservicesk9_wan-vz.122-33.SXI2.bin slavesup-bootdisk:/newsys Router# show issu state Slot = 1/6 RP State = Active ISSU State = Init Boot Variable = bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Slot = 2/6 RP State = Standby ISSU State = Init Boot Variable = bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Router# issu loadversion sup-bootdisk:/newsys/s72033/base/s72033-advipservicesk9_wan-vm %issu loadversion executed successfully, Standby is being reloaded Router# show issu state Slot = 1/6 RP State = Active ISSU State = Load Version Boot Variable = bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Slot = RP State = ISSU State = Boot Variable = Router# issu runversion This command will reload the Router# show issu state Slot = 2/6 Standby Load Version bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Active unit. Proceed ? [confirm] 2/6
4-68
OL-13013-06
Chapter 4
RP State = Active ISSU State = Run Version Boot Variable = bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Slot = RP State = ISSU State = Boot Variable = Router# issu commitversion %issu commitversion executed Router# show issu state Slot = RP State = ISSU State = Boot Variable = 1/6 Standby Run Version bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; successfully 2/6 Active Init bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12;
Slot = 1/6 RP State = Standby ISSU State = Init Boot Variable = bootdisk:/sys/s72033/base/s72033-advipservicesk9_wan-vm,12; Router# redundancy force-switchover
Load the New Image to the VSS Standby Chassis

Enter the issu loadversion command to start the upgrade process. In this step, the VSS standby chassis reboots, reloads with the new image, and initializes as the VSS standby chassis in SSO redundancy mode, running the new image. This step is complete when the chassis configuration is synchronized, as indicated by the Bulk sync succeeded message.
Router# issu loadversion disk0:s72033-newversion.v2 000133: Aug 6 16:17:44.486 PST: TenGigabitEthernet1/2/4, changed 000134: Aug 6 16:17:43.507 PST: TenGigabitEthernet2/7/4, changed 000135: Aug 6 16:17:43.563 PST: changed state to down 000136: Aug 6 16:17:44.919 PST: changed state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface state to down %LINK-3-UPDOWN: Interface TenGigabitEthernet2/7/4, %LINK-3-UPDOWN: Interface TenGigabitEthernet1/2/4,
(Deleted many interface and protocol down messages)

%issu loadversion executed successfully, Standby is being reloaded
(Deleted many interface and protocol down messages, then interface and protocol up messages)
0000148: Aug 6 16:27:54.154 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/2/5, changed state to up 000149: Aug 6 16:27:54.174 PST: %LINK-3-UPDOWN: Interface TenGigabitEthernet2/7/5, changed state to up 000150: Aug 6 16:27:54.186 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet2/7/5, changed state to up 000151: Aug 6 16:32:58.030 PST: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
4-69
Verify the New Image on the VSS Standby Chassis

You can now enter the show issu state detail command and the show redundancy command to check that both chassis are in the ISSU Load Version state and SSO redundancy state. In this example, the VSS standby chassis is now running the newversion image.
Router# show issu state detail Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version Variable Store = = = = = = = = = 1/2 Active Load Version disk0:s72033-oldversion.v1,12 sso disk0:s72033-oldversion.v1 disk0:s72033-newversion.v2 disk0:s72033-oldversion.v1 PrstVbl
Slot = 2/7 RP State = Standby ISSU State = Load Version Boot Variable = disk0:s72033-newversion.v2,12;disk0:s72033-oldversion.v1,12 Operating Mode = sso Primary Version = disk0:s72033-oldversion.v1 Secondary Version = disk0:s72033-newversion.v2 Current Version = disk0:s72033-newversion.v2 Router# show redundancy status my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Secondary Unit ID = 18 Redundancy Mode (Operational) = sso Redundancy Mode (Configured) = sso Redundancy State = sso Maintenance Mode = Disabled Communications = Up client count = 132 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
Execute a Switchover to the New Image

When the VSS standby chassis is successfully running the new image in SSO redundancy state, enter the issu runversion command to force a switchover. The upgraded VSS standby chassis takes over as the new active chassis, running the new image. The formerly active chassis reloads and initializes as the new VSS standby chassis in SSO mode, running the old image (in case the software upgrade needs to be aborted and the old image restored). This step is complete when the chassis configuration is synchronized, as indicated by the Bulk sync succeeded message.
Router# issu runversion This command will reload the Active unit. Proceed ? [confirm] System Bootstrap, Version 12.2(17r)S4, RELEASE SOFTWARE (fc1) Technical Support: http://www.cisco.com/techsupport Copyright (c) 2005 by cisco Systems, Inc.
4-70
OL-13013-06
Chapter 4
Cat6k-Sup720/RP platform with 1048576 Kbytes of main memory Download Start !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
(Deleted many lines)

!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Download Completed! Booting the image. Self decompressing the image : ##########################################################################################

################################################################################ [OK] running startup....

000147: Aug succeeded 6 16:53:43.199 PST: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync
Verify the Switchover

You can now enter the show issu state detail command and the show redundancy command to check that both chassis are in the ISSU Run Version state and SSO redundancy state. In this example, the active chassis is now running the newversion image.
Router# show issu state detail Slot = 2/7 RP State = Active ISSU State = Run Version Boot Variable = disk0:s72033-newversion.v2,12;disk0:s72033-oldversion.v1,12 Operating Mode = sso Primary Version = disk0:s72033-newversion.v2 Secondary Version = disk0:s72033-oldversion.v1 Current Version = disk0:s72033-newversion.v2 Variable Store = PrstVbl Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version = = = = = = = = 1/2 Standby Run Version disk0:s72033-oldversion.v1,12 sso disk0:s72033-newversion.v2 disk0:s72033-oldversion.v1 disk0:s72033-oldversion.v1
Router# show redundancy status my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Primary Unit ID = 39 Redundancy Mode (Operational) = sso Redundancy Mode (Configured) = sso Redundancy State = sso Maintenance Mode = Disabled Communications = Up client count = 134 client_notification_TMR = 30000 milliseconds keep_alive TMR = 9000 milliseconds
4-71
keep_alive count = 1 keep_alive threshold = 18 RF debug mask = 0x0
Commit the New Image to the VSS Standby Chassis

When the active chassis is successfully running the new image in the SSO redundancy state, you can enter either the issu acceptversion command to stop the rollback timer and hold this state indefinitely, or the issu commitversion command to continue with the eFSU. To continue, enter the issu commitversion command to upgrade the VSS standby chassis and complete the eFSU sequence. The VSS standby chassis reboots, reloads with the new image, and initializes as the VSS standby chassis in the SSO redundancy state, running the new image. This step is complete when the chassis configuration is synchronized, as indicated by the Bulk sync succeeded message.
Router# issu commitversion Building configuration... [OK] 000148: Aug 6 17:17:28.267 PST: TenGigabitEthernet2/7/4, changed 000149: Aug 6 17:17:28.287 PST: TenGigabitEthernet1/2/4, changed
%LINEPROTO-5-UPDOWN: Line protocol on Interface state to down %LINEPROTO-5-UPDOWN: Line protocol on Interface state to down
(Deleted many interface and protocol down messages)

%issu commitversion executed successfully
(Deleted many interface and protocol down messages, then interface and protocol up messages)
000181: Aug 6 17:41:51.086 PST: %LINEPROTO-5-UPDOWN: Line protocol on Interface TenGigabitEthernet1/2/5, changed state to up 000182: Aug 6 17:42:52.290 PST: %HA_CONFIG_SYNC-6-BULK_CFGSYNC_SUCCEED: Bulk Sync succeeded
Verify That the Upgrade is Complete

You can now enter the show issu state detail command and the show redundancy command to check the results of the eFSU. In this example, both chassis are now running the newversion image, indicating that the eFSU was successful. Because the eFSU has completed, the two chassis will be once again in the ISSU Init Version state, as they were before the eFSU was initiated.
Router# show issu state detail Slot = 2/7 RP State = Active ISSU State = Init Boot Variable = disk0:s72033-newversion.v2,12;disk0:s72033-oldversion.v1,12 Operating Mode = sso Primary Version = N/A Secondary Version = N/A Current Version = disk0:s72033-newversion.v2 Variable Store = PrstVbl Slot = 1/2 RP State = Standby ISSU State = Init Boot Variable = disk0:s72033-newversion.v2,12;disk0:s72033-oldversion.v1,12
4-72
OL-13013-06
Chapter 4
Operating Mode Primary Version Secondary Version Current Version
= = = =
sso N/A N/A disk0:s72033-newversion.v2
Router# show redundancy status my state = 13 -ACTIVE peer state = 8 -STANDBY HOT Mode = Duplex Unit = Primary Unit ID = 39 Redundancy Mode (Operational) = sso Redundancy Mode (Configured) = sso Redundancy State = sso Maintenance Mode = Disabled Communications = Up client count = 134 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
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
4-73
4-74
OL-13013-06
PA R T
High Availability
CH A P T E R
Performing an Enhanced Fast Software Upgrade

This chapter provides information about how to perform a software upgrade using the Enhanced Fast Software Upgrade (eFSU) feature.
Note
Tip
This chapter contains the following sections:

eFSU Overview, page 5-1 eFSU Guidelines and Limitations, page 5-4 Performing an Enhanced Fast Software Upgrade, page 5-5 Performing an eFSU Upgrade on an Installed Modular Image, page 5-14 Upgrading a Non-eFSU Image to an eFSU Image, page 5-16
eFSU Overview
The following sections provide an overview of how eFSU works:

eFSU Operation, page 5-2 Outage Time and Support Considerations, page 5-3 Reserving Module Memory, page 5-3 Error Handling for eFSU Preload, page 5-4
5-1
Chapter 5 eFSU Overview
Note
eFSU is supported in VSS mode. See the VSS Configuration Guidelines and Restrictions section on page 4-29 for more information.
eFSU Operation
eFSU is an enhanced software upgrade procedure. Cisco IOS Release 12.2(33)SXI and later releases support eFSU. Non-eFSU (FSU) software upgrades require system downtime, because a software version mismatch between the active and the standby supervisor engines forces the system to boot in RPR redundancy mode, which is stateless and causes a hard reset of the all modules. eFSU enables an increase in network availability by reducing the downtime caused by software upgrades. eFSU does this by:
Bringing up the standby supervisor engine in SSO mode even when the active and the standby supervisor engines have different software versions, or with VSS configured, when the supervisor engines in the two chassis have different software versions. During an eFSU, new software is loaded onto the standby supervisor engine while the active supervisor engine continues to operate using the previous software. As part of the upgrade, the standby processor reaches the SSO Standby Hot stage, a switchover occurs, and the standby becomes active, running the new software. In previous releases Supervisor Engines running different software versions ran in the Route Processor Redundancy Mode. You can continue with the upgrade to load the new software onto the other processor, or you can abort the upgrade and resume operation with the old software.
Preloading new module software into memory on supported modules to avoid a hard reset. If the new software release contains new module software, eFSU preloads the new module software onto any modules in the switch that support eFSU preload. When the switchover occurs between the active and standby supervisor engines, the modules are restarted with the new software image. The following modules support eFSU preload:
WS-X67xx modules SIP-400 and SIP-600
All other modules undergo a hard reset at switchover, and the software image loads after the module restarts. During a software upgrade, the switch performs the following steps automatically on modules that support eFSU preload:
Reserves the necessary memory for the new Cisco IOS software image on each module. Preloads a new software image onto the modules as part of the issu loadversion command. Restarts the modules with the new software image when a switchover occurs (issu runversion). During the restart, the software features and routing protocols are not available. If a rollback or abort occurs, to minimize disruption, the switch preloads the original software
version onto the module. Once the rollback or abort is completed, the module is restarted with the original software version.
5-2
OL-13013-06
Chapter 5
Performing an Enhanced Fast Software Upgrade eFSU Overview
Note
All modules that support eFSU preload must have at least 512 MB of memory, with enough memory free to hold the new software image. If there is insufficient free memory, eFSU does not attempt the preload, but instead resets the modules during the switchover.
Outage Time and Support Considerations

During an eFSU upgrade, modules are restarted or reset after the switchover that occurs between the supervisor engines. Because the modules are restarted or reset, any links attached to the modules go up and down and traffic processing is disrupted until protocols and software features are brought back online. The length of time that module processing is disrupted (outage time) depends on whether the eFSU process was able to preload a new software image onto the module.

For modules that support eFSU preload, the outage time for an eFSU module warm reload is faster than an RPR mode module reload. For modules that do not support eFSU preload, the outage time for module reload is similar to an RPR mode module reload.
Once the new software is loaded (issu loadversion), you can use the show issu outage slot all command to display the maximum outage time for installed modules. See the Displaying the Maximum Outage Time for Installed Modules (Optional) section on page 5-10 for a command example.
Reserving Module Memory

On modules that support eFSU, the supervisor engine automatically reserves memory on the module to store the new software image (decompressed format). The amount of memory needed varies according to the module type. Although we do not recommend it, you can enter the following command to keep the switch from reserving memory for the software preload (where slot-num specifies which slot the module is installed in):
no mdr download reserve memory image slot slot-num
Note
All modules that support eFSU preload must have at least 512 MB of memory, with enough memory free to hold the new software image. If there is insufficient free memory, eFSU does not attempt the preload, but instead resets the modules during the switchover. To display whether or not the memory reservation was successful on a module, use the show issu outage slot all command See the Displaying the Maximum Outage Time for Installed Modules (Optional) section on page 5-10 for a command example.
5-3
Chapter 5 eFSU Guidelines and Limitations
Error Handling for eFSU Preload

If problems occur during eFSU preload, the switch takes the following actions:

Module crash during loadversionThe module is reset when a switchover occurs. Module not active when eFSU startedNo power is provided to the module during the software upgrade, and the module is reset when the process ends. The same action is applied to a module that is inserted into the switch after the software upgrade process has begun. Module crash during run version or during rollbackThe module boots with the software image version that corresponds to the software image that is present on the active supervisor engine.
eFSU Guidelines and Limitations

When performing an eFSU, follow these guidelines and restrictions:

eFSU requires two supervisor engines, one active and one standby. Both the active and standby supervisor engines must have enough flash memory to store both the old and new software images prior to the upgrade process. Images from different features sets, regardless of release, fail the eFSU compatibility check. When downgrading with eFSU to an earlier version of Cisco IOS Software, the configuration files fail to synchronize and the standby supervisor engine reloads unless you disable any features or functions that are not supported in the earlier version before you start the process. Remove any configuration commands that are not available in the earlier version. During an eFSU upgrade, the modules are restarted. The switch examines the old and new software images and automatically performs the appropriate process (eFSU) to upgrade the software image:
For a patch upgrade, if the module software is the same in both the old and the new software
images, because no module software upgfrade is required, the eFSU upgrades only the supervisor engine software. The system downtime is from 0 to 3 seconds.
If the module software in the images is different, the modules are restarted or reset during the
upgrade process. System downtime depends on whether the modules support eFSU (see the Outage Time and Support Considerations section on page 5-3 for more information).
The eFSU upgrade feature works with NSF/SSO. Software features that do not support NSF/SSO stop operating until they come back online after the switchover that occurs during the software upgrade. All modules that support eFSU preload must have at least 512 MB of memory, with enough memory free to hold the new software image. If there is insufficient free memory, eFSU does not attempt the preload, but instead resets the modules during the switchover. Online insertion and replacement (OIR) is not supported during an eFSU. If you attempt to insert a new module in the switch while the upgrade is active, the switch does not provide power for the module. When the upgrade ends, the switch resets the newly inserted module. Do not perform a manual switchover between supervisor engines during the upgrade. Make sure that the configuration register is set to allow autoboot (the lowest byte of the register should be set to 2). Before you enter the issu abortversion command (to abort a software upgrade), make sure that the standby supervisor engine is Up (STANDBY HOT [in SSO] or COLD [in RPR]).
5-4
OL-13013-06
Chapter 5
Performing an Enhanced Fast Software Upgrade Performing an Enhanced Fast Software Upgrade
The Fast Software Upgrade (FSU) process supports upgrade from earlier releases to Release 12.2(33)SXI or later releases. During this process, the module software image is also upgraded on those modules that support eFSU. The enhanced Fast Software Upgrade (eFSU) process supports upgrades from Release 12.2(33)SXI and rebuilds to Release 12.2(33)SXJ. During this process, the module software image is also upgraded on those modules that support eFSU.

The following sections describe the process for performing an enhanced fast software upgrade (eFSU) on the Catalyst 6500 series switch:

Software Upgrade Process Summary For a Switch, page 5-5 Preparing for the Upgrade, page 5-6 Copying the New Software Image, page 5-8 Loading the New Software onto the Standby Supervisor Engine, page 5-8 Displaying the Maximum Outage Time for Installed Modules (Optional), page 5-10 Forcing a Switchover from Active to Standby, page 5-10 Accepting the New Software Version and Stopping the Rollback Process (Optional), page 5-11 Committing the New Software to the Standby, page 5-12 Verifying the Software Installation, page 5-12 Aborting the Upgrade Process, page 5-13
Each section briefly describes a particular step in the upgrade process and provides command examples. In the command examples, important fields in the command output are shown in bold. Check these fields to verify the status of the command.
Software Upgrade Process Summary For a Switch

The following sections provide examples of the software upgrade process. To upgrade the software, perform the following tasks: Command
Step 1 Step 2
Router> enable
Purpose Enables privileged EXEC mode. Enter your password if prompted. Uses TFTP to copy the new software image to flash memory on the active and standby supervisor engines (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image.
5-5
Chapter 5 Performing an Enhanced Fast Software Upgrade
Command
Step 3
Router# show version | in image Router# show bootvar
Purpose These show commands verify that the switch is ready to run eFSU. The show version and show bootvar commands verify the boot image settings. The show redundancy and show issu state commands verify that redundancy mode is enabled and that SSO and NSF are configured.
Note
Router# show redundancy Router# show issu state [detail]
Use the show redundancy and show issu state commands throughout the upgrade to verify the status of the upgrade.
Step 4
Router# issu loadversion active-slot active-image standby-slot standby-image
Starts the upgrade process and loads the new software image onto the standby supervisor engine. It may take several seconds for the new image to load and for the standby supervisor engine to transition to SSO mode. (Optional) Displays the maximum outage time for installed modules. Enter the command on the switch processor of the supervisor engine. Forces a switchover, which causes the standby supervisor engine to become active and begin running the new software. The previously active processor becomes standby and boots with the old image. (Optional) Halts the rollback timer to ensure that the new software image is not automatically aborted during the upgrade process. Loads the new software image onto the standby supervisor engine in the specified slot. Verifies the status of the upgrade process. If the upgrade was successful, both the active and standby supervisor engines are running the new software version.
Step 5
Router# show issu outage slot all
Step 6
Step 7
Step 8 Step 9
Router# show redundancy Router# show issu state [detail]
Preparing for the Upgrade

Before attempting to perform a software upgrade, be sure to review the eFSU Guidelines and Limitations section on page 5-4. To prepare for eFSU, perform the tasks in the following sections:

Verifying the Boot Image Version and Boot Variable, page 5-6 Verifying Redundancy Mode, page 5-7 Verifying eFSU State, page 5-8
Verifying the Boot Image Version and Boot Variable

Before starting, enter the show version and show bootvar commands to verify the boot image version and BOOT environment variable, as shown in the following examples:
Router# show version | in image BOOT variable = disk0:image_name; CONFIG_FILE variable = BOOTLDR variable = Cisco IOS Software Configuration Guide, Release 12.2SX
5-6
OL-13013-06
Chapter 5
Configuration register is 0x2002 Standby is up Standby has 1048576K/65536K bytes of memory. Standby BOOT variable = disk0:image_name; Standby CONFIG_FILE variable = Standby BOOTLDR variable =
Verifying Redundancy Mode

Verify that redundancy mode is enabled and that NSF and SSO are configured. The following command example shows how to verify redundancy:
Router# show redundancy Redundant System Information : -----------------------------Available system uptime Switchovers system experienced Standby failures Last switchover reason Hardware Mode Configured Redundancy Mode Operating Redundancy Mode Maintenance Mode Communications
= = = = = = = = =
45 minutes 0 0 none Duplex sso sso Disabled Up
Current Processor Information : ------------------------------Active Location = slot 6 Current Software state = ACTIVE Uptime in current state = 44 minutes Image Version = Cisco IOS Software, image_details Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Wed 18-Feb-09 12:48 by kchristi BOOT = disk0:image_name; CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Peer Processor Information : ---------------------------Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 28 minutes Image Version = Cisco IOS Software, image_details Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled image_details BOOT = disk0:image_name ; CONFIG_FILE = BOOTLDR = Configuration register = 0x2002
5-7
Verifying eFSU State

Verify that the the ISSU state is Init, rather than an intermediate eFSU upgrade state. Enter this command:
Router# show issu state detail Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version Variable Store ROMMON CV Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version = = = = = = = = = = = = = = = = = = 6 Active Load Version disk0:image_name sso disk0:sierra.0217 disk0:sierra.0217 disk0:sierra.0217 PrstVbl [disk0:image_name] 5 Standby Load Version disk0:image_name sso disk0:image_name disk0:image_name disk0:image_name
Copying the New Software Image

Before starting the eFSU process, copy the new software image to flash memory (disk0: and slavedisk0:) on the active and standby supervisor engines.
Loading the New Software onto the Standby Supervisor Engine

Enter the issu loadversion command to start the upgrade process. This command reboots the standby supervisor engine and loads the new software image onto the standby supervisor engine. When the download is complete, you are prompted to enter the runversion command.
Note
Do not automatically disable the features that are not common to both images. During the standby initialization, after you enter the issu loadversion command, if there are any enabled features that are not supported on the standby supervisor engine, a message is displayed that states that the standby supervisor engine cannot initialize while this feature is enabled, and the standby supervisor engine is forced to RPR (in the load-version state).
Router# issu loadversion device:filename %issu loadversion executed successfully, Standby is being reloaded
When execution of the issu loadversion command completes, the standby supervisor engine is loaded with the new software image and the supervisor engine is in SSO mode. The issu loadversion command might take several seconds to complete. If you enter the show commands too soon, you might not see the information that you need.
5-8
OL-13013-06
Chapter 5
These examples show how to check the status of the upgrade using the show redundancy and show issu state detail commands:
= = = = = = = = =
1 hour, 0 minutes 0 1 none Duplex sso sso Disabled Up
Current Processor Information : ------------------------------Active Location = slot 6 Current Software state = ACTIVE Uptime in current state = 59 minutes Image Version = Cisco IOS Software, image_details Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled ... BOOT = disk0:image_name CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Peer Processor Information : ---------------------------Standby Location = slot 5 Current Software state = STANDBY HOT Uptime in current state = 3 minutes Image Version = Cisco IOS Software, image_name Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled ... BOOT = disk0:image_name CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Router# show issu state detail Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version Variable Store ROMMON CV Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version
= = = = = = = = = = = = = = = = = =
6 Active Load Version disk0:image_name sso disk0:image_name disk0:image_name disk0:image_name PrstVbl [disk0:image_name] 5 Standby Load Version disk0:image_name sso disk0:image_name disk0:image_name disk0:image_name Cisco IOS Software Configuration Guide, Release 12.2SX
OL-13013-06
5-9
Displaying the Maximum Outage Time for Installed Modules (Optional)

Once the new software is downloaded, you can enter the show issu outage slot all command on the switch processor to display the maximum outage time for the installed modules:
Router# show issu outage slot all Slot # Card Type ------ ------------------------------------------1 CEF720 8 port 10GE with DFC 2 96-port 10/100 Mbps RJ45 4 CEF720 48 port 1000mb SFP MDR Mode Max Outage Time ----------- --------------WARM_RELOAD 300 secs RELOAD 360 secs RELOAD 360 secs
Slot # Reason Error Number ------ ------------------------------------------- -----------1 PLATFORM_INIT 3 2 PLATFORM_INIT 3 4 PREDOWNLOAD_LC_MIMIMUM_MEMORY_FAILURE 5 Router#
Forcing a Switchover from Active to Standby

Enter the issu runversion command to force a switchover between the active and standby supervisor engines. The standby supervisor engine, which has the new software image loaded, becomes active. The previously active supervisor engine becomes the standby and boots with the old software image (in case the software upgrade needs to be aborted and the old image restored).
Router# issu runversion This command will reload the Active unit. Proceed ? [confirm] y
A switchover between the supervisor engines occurs now. The previous standby supervisor engine becomes active and is running the new software version. The previous active supervisor engine, now the standby supervisor engine, boots with the old software.
Note
At this point, the new active supervisor engine is running the new software image and the standby is running the old software image. You should verify the state of the active and standby supervisor engines as shown in the following examples (show redundancy and show issu state detail).
Router# show redundancy -----------------------------Available system uptime Switchovers system experienced Standby failures Last switchover reason Hardware Mode Configured Redundancy Mode Operating Redundancy Mode Maintenance Mode Communications
= = = = = = = = =
1 hour, 9 minutes 1 0 user forced Duplex sso sso Disabled Up
Current Processor Information : ------------------------------Active Location = Current Software state = Uptime in current state = Image Version =
slot 5 ACTIVE 7 minutes Cisco IOS Software, image_details
5-10
OL-13013-06
Chapter 5
Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled ... BOOT = disk0:image_name CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Peer Processor Information : ---------------------------Standby Location = slot 6 Current Software state = STANDBY HOT Uptime in current state = 0 minutes Image Version = Cisco IOS Software, image_details Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled Wed 18-Feb-09 12:48 by kchristi BOOT = disk0:image_name CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Router# show issu state detail Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version Variable Store ROMMON CV Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version
= = = = = = = = = = = = = = = = = =
5 Active Run Version disk0:image_name sso disk0:image_name disk0:image_name disk0:image_name PrstVbl [disk0:image_name] 6 Standby Run Version disk0:image_name sso disk0:image_name disk0:image_name disk0:image_name
Note
To complete the upgrade process, enter the issu acceptversion (optional) and issu commitversion commands (as described in the following sections).
Accepting the New Software Version and Stopping the Rollback Process (Optional)
You must either accept or commit the new software image, or the rollback timer will expire and stop the upgrade process. If that occurs, the software image reverts to the previous software version. The rollback timer is a safeguard to ensure that the upgrade process does not leave the switch nonoperational.
Note
New features that are not supported by the previous image are allowed to be enabled only after you enter the issu commitversion command.
5-11
The following command sequence shows how the issu acceptversion command stops the rollback timer to enable you to examine the functionality of the new software image. When you are satisfied that the new image is acceptable, enter the issu commitversion command to end the upgrade process.
Router# show issu rollback-timer Rollback Process State = In progress Configured Rollback Time = 00:45:00 Automatic Rollback Time = 00:37:28 Router# issu acceptversion % Rollback timer stopped. Please issue the commitversion command.
View the rollback timer to see that the rollback process has been stopped:
Router# show issu rollback-timer Rollback Process State = Not in progress Configured Rollback Time = 00:45:00
Committing the New Software to the Standby

Enter the issu commitversion command to load the new software image onto the standby supervisor engine and complete the software upgrade process. In the following example, the new image is loaded onto the standby supervisor engine in slot 5:
Router# issu commitversion Building configuration... [OK] %issu commitversion executed successfully
Note
The software upgrade process is now complete. Both the active and standby supervisor engines are running the new software version.
Verifying the Software Installation

You should verify the status of the software upgrade. If the upgrade was successful, both the active and standby supervisor engines are running the new software version.
= = = = = = = = =
1 hour, 17 minutes 1 1 user forced Duplex sso sso Disabled Up
Current Processor Information : ------------------------------Active Location = Current Software state = Uptime in current state = Image Version =
slot 5 ACTIVE 15 minutes Cisco IOS Software, image_name
5-12
OL-13013-06
Chapter 5
Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled ... BOOT = disk0:image_name CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Peer Processor Information : ---------------------------Standby Location = slot 6 Current Software state = STANDBY HOT Uptime in current state = 0 minutes Image Version = Cisco IOS Software, image_details Technical Support: http://www.cisco.com/techsupport Copyright (c) 1986-2009 by Cisco Systems, Inc. Compiled ... BOOT = disk0:image_name CONFIG_FILE = BOOTLDR = Configuration register = 0x2002 Router# show issu state detail Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version Variable Store ROMMON CV Slot RP State ISSU State Boot Variable Operating Mode Primary Version Secondary Version Current Version = = = = = = = = = = = = = = = = = = 5 Active Init disk0:image_name sso N/A N/A disk0:image_name PrstVbl [disk0:simage_name ] 6 Standby Init disk0:image_name sso N/A N/A disk0:image_name
Aborting the Upgrade Process

You can manually abort the software upgrade at any stage by entering the issu abortversion command. The upgrade process also aborts on its own if the software detects a failure. If you abort the process after you enter the issu loadversion command, the standby supervisor engine is reset and reloaded with the original software. The following is an example of the issu abortversion slot image command that shows how to abort the software upgrade process:
Router# issu abortversion 6 c7600s72033
Note
Before you enter the issu abortversion command, make sure that the standby supervisor engine is Up (STANDBY HOT [in SSO] or COLD [in RPR]).
5-13
Chapter 5 Performing an eFSU Upgrade on an Installed Modular Image
Performing an eFSU Upgrade on an Installed Modular Image

The following sections describe the process for performing an enhanced fast software upgrade (eFSU) on an Installed Modular Image (ION):

Upgrading an Installed Modular Image, page 5-14 Example an eFSU Upgrade on an Installed Modular Image, page 5-15
Upgrading an Installed Modular Image

To perform an eFSU upgrade (or downgrade) of an ION VSS, perform this task: Command
Step 1
Purpose Uses TFTP to copy the new software image to flash memory on the active and standby chassis (disk0: and slavedisk0:). Answer the prompts to identify the name and location of the new software image.
Note
It is best to have a console on both the active and standby supervisor engines as you will go back and forth between them.
Router# install file bootdisk:filename bootdisk:/location Router# show issu state [switch/slot][detail]
Installs the modular image onto both the active and standby supervisor engines. Verifies the status of the upgrade process; status should display Init. Starts the upgrade process by loading the installed software image onto the active and standby chassis. The image name includes the path of the target image to be loaded, in the format devicename:filename. It may take several seconds for the new image to load and for the standby chassis to transition to SSO mode.
Router# issu loadversion new-image
Note
This command will cause the standby chassis to reload.
Step 5 Step 6
Verifies the status of the upgrade process; status should display Load Version. Forces a switchover, causing the standby chassis to become active, and begins running the new software. The previously active chassis becomes standby and boots with the old image. Verifies the status of the upgrade process; status should display Run Version.
Step 7
5-14
OL-13013-06
Chapter 5
Performing an Enhanced Fast Software Upgrade Performing an eFSU Upgrade on an Installed Modular Image
Command
Step 8
Purpose Loads the new software image onto the standby chassis.
Note
This command will cause the standby chassis to reload.
Step 9 Step 10
Verifies the status of the upgrade process; status should display Init. (Optional) Forces the standby Route Processor (RP) to assume the role of the active RP.
For an example of the eFSU upgrade on an Installed Modular Image sequence, see the Example an eFSU Upgrade on an Installed Modular Image section on page 5-15.
Example an eFSU Upgrade on an Installed Modular Image

This example shows how to perform an an eFSU upgrade on an Installed Modular Image.
Router# Router# Router# Router# Router# copy ftp://172.18.108.26/image_name sup-bootdisk:simage_name copy ftp://172.18.108.26/image_name slavesup-bootdisk:image_name install file sup-bootdisk:image_name sup-bootdisk:/newsys install file slavesup-bootdisk:image_name slavesup-bootdisk:/newsys show issu state Slot = 1/6 RP State = Active ISSU State = Init Boot Variable = bootdisk:/sys/s72033/base/image_name ,12;
Slot = 2/6 RP State = Standby ISSU State = Init Boot Variable = bootdisk:/sys/s72033/base/image_name ,12; Router# issu loadversion sup-bootdisk:/newsys/s72033/base/image_name %issu loadversion executed successfully, Standby is being reloaded Router# show issu state Slot = 1/6 RP State = Active ISSU State = Load Version Boot Variable = bootdisk:/sys/s72033/base/image_name ,12; Slot = RP State = ISSU State = Boot Variable = Router# issu runversion This command will reload the Router# show issu state Slot = RP State = ISSU State = Boot Variable = Slot RP State ISSU State Boot Variable = = = = 2/6 Standby Load Version bootdisk:/sys/s72033/base/image_name ,12; Active unit. Proceed ? [confirm] 2/6 Active Run Version bootdisk:/sys/s72033/base/image_name,12; 1/6 Standby Run Version bootdisk:/sys/s72033/base/image_name,12;
5-15
Chapter 5 Upgrading a Non-eFSU Image to an eFSU Image
Router# issu commitversion %issu commitversion executed Router# show issu state Slot = RP State = ISSU State = Boot Variable =
successfully 2/6 Active Init bootdisk:/sys/s72033/base/image_name,12;
Slot = 1/6 RP State = Standby ISSU State = Init Boot Variable = bootdisk:/sys/s72033/base/image_name,12; Router# redundancy force-switchover
Upgrading a Non-eFSU Image to an eFSU Image

If the new Cisco IOS software image does not support eFSU, you must manually upgrade the software image. To do so, you must upgrade the software image on the standby supervisor engine and then perform a manual switchover so that the standby takes over processing with the new image. You can then upgrade the software image on the previously active, and now standby, supervisor engine. For more information, see the Software Upgrade Process Summary For a Switch section on page 5-5.
Tip
5-16
OL-13013-06
C H A P T E R

This chapter describes how to configure supervisor engine redundancy using Cisco nonstop forwarding (NSF) with stateful switchover (SSO) on Catalyst 6500 series switches.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html Cisco ME 6500 Series Ethernet switches do not support redundancy. NSF with SSO does not support IPv6 multicast traffic.
Tip

Understanding NSF with SSO Supervisor Engine Redundancy, page 6-1 Supervisor Engine Configuration Synchronization, page 6-9 NSF Configuration Tasks, page 6-11 Copying Files to the Redundant Supervisor Engine, page 6-20
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 6-2 SSO Operation, page 6-2 NSF Operation, page 6-3 Cisco Express Forwarding, page 6-3
6-1
Chapter 6 Understanding NSF with SSO Supervisor Engine Redundancy
Multicast MLS NSF with SSO, page 6-4 Routing Protocols, page 6-4 NSF Benefits and Restrictions, page 6-8
NSF with SSO Supervisor Engine Redundancy Overview

Note
The two Gigabit Ethernet interfaces on the redundant supervisor engine are always active unless you enter the fabric switching-mode allow dcef-only command. With a Supervisor Engine 720, 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)
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) for redundancy. For information about these redundancy modes, see Chapter 7, Configuring 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
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.
6-2
OL-13013-06
Chapter 6
Configuring NSF with SSO Supervisor Engine Redundancy Understanding NSF with SSO Supervisor Engine Redundancy
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, EIGRP, 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 modules 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. For platforms with intelligent modules, the modules 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 modules 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 modules 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.
6-3
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 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 route processor (RP) 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 RP of the active supervisor engine, and they receive routing updates from their neighbor routers. Routing protocols do not run on the RP 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
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.
6-4
OL-13013-06
Chapter 6
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
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.
6-5
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. 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 checkpointed data, and can quickly rebuild its routing tables.
6-6
OL-13013-06
Chapter 6
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. 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.
6-7
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 availabilityNSF continues forwarding network traffic and application state information so that user session information is maintained after a switchover. Overall network stabilityNetwork 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 flapBecause 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 flapsBecause SSO continues forwarding network traffic in the event of a switchover, routing flaps are avoided. No loss of user sessionsUser sessions established before the switchover are maintained. For NSF operation, you must have SSO configured on the device. NSF with SSO supports IP Version 4 traffic and protocols only. 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 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. NSF with SSO does not support L2VPN. Except in VSS mode, Release 12.2(33)SXH and later releases support IPv4 Multiprotocol Label Switching (MPLS) with Cisco NSF with SSO. In VSS mode, Release 12.2(33)SXI2 and later releases support IPv4 MPLS with Cisco NSF with SSO. For additional information about supported MPLS features, search for MPLS in the Release Notes for Cisco IOS Release 12.2(33)SXH and Later Releases: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/features.html
Cisco NSF with SSO has these restrictions:

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.
6-8
OL-13013-06
Chapter 6
Configuring NSF with SSO Supervisor Engine Redundancy Supervisor Engine Configuration Synchronization
Supervisor Engine Configuration Synchronization

These sections describe supervisor engine configuration synchronization:

Supervisor Engine Redundancy Guidelines and Restrictions, page 6-9 Redundancy Configuration Guidelines and Restrictions, page 6-9
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.
Supervisor Engine Redundancy Guidelines and Restrictions

These sections describe supervisor engine redundancy guidelines and restrictions:

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

These guidelines and restrictions apply to all redundancy modes:
Because the Supervisor Engine 720 and Supervisor Engine 720-10GE integrate the switch fabric functionality on the supervisor engine, a supervisor engine switchover will force a fabric switchover as well. During the fabric switchover, data will be lost for a period of between 0.5 seconds and 1.5 seconds. When a Supervisor Engine 720 or Supervisor Engine 720-10GE is installed in a Catalyst 6500 series switch E series chassis (such as the WS-C6509-E), Release 12.2(33)SXH incorporates a fast fabric switchover mechanism, called enhanced hot-standby fabric switchover time, to reduce the data loss to a period of between 50 milliseconds and 0.5 seconds for feature-capable cards. When a redundant supervisor engine is in standby mode, the two Gigabit Ethernet interfaces on the redundant supervisor engine are always active unless you enter the fabric switching-mode allow dcef-only command. With a Supervisor Engine 720, 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.
6-9
Chapter 6 Supervisor Engine Configuration Synchronization
Using the supervisor engine Ethernet ports as routed ports or EtherChannel ports will significantly increase the switchover time.
Note
In Cisco IOS Release 12.2(33)SXI2 and later releases, the switchover recovery time is greatly improved for EtherChannels containing the Ethernet ports of both the active and standby supervisor engines. This improvement, which reduces the data disruption period from up to 4 seconds to less than one second, applies only to Supervisor Engine 720 and Supervisor Engine 32, and applies only when the EtherChannel contains no ports other than those of the supervisor engines.
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. 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 SP and the RP supports redundant configurations where the supervisor engines are identical. If they are not identical, one will boot first and become active and hold the other supervisor engine 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. Both supervisor engines must have the same system image (see the Copying Files to the Redundant Supervisor Engine section on page 6-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.
6-10
OL-13013-06
Chapter 6
Configuring NSF with SSO Supervisor Engine Redundancy NSF Configuration Tasks
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 6-11 Verifying the Redundancy States, page 6-12 Configuring Multicast MLS NSF with SSO, page 6-13 Verifying Multicast NSF with SSO, page 6-13 Configuring CEF NSF, page 6-13 Verifying CEF NSF, page 6-14 Configuring BGP NSF, page 6-14 Verifying BGP NSF, page 6-14 Configuring OSPF NSF, page 6-15 Verifying OSPF NSF, page 6-16 Configuring IS-IS NSF, page 6-17 Verifying IS-IS NSF, page 6-17
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.
6-11
Chapter 6 NSF Configuration Tasks
Command
Step 3 Step 4
Router# show running-config Router# show redundancy states
Purpose Verifies that SSO is enabled. Displays the operating redundancy mode.
This example shows how to configure the system for SSO:

Router> enable Router# configure terminal Enter configuration commands, one per line. Router(config)# redundancy Router(config-red)# mode sso Router(config-red)# end
End with CNTL/Z.
Verifying the Redundancy States

To verify the redundancy states, enter the show redundancy states command:
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
client count = 29 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
In this example, the system cannot enter the redundancy state because the second supervisor engine is disabled or missing:
Router# show redundancy states my state = 13 -ACTIVE peer state = 1 -DISABLED Mode = Simplex Unit = Primary Unit ID = 1 Redundancy Mode (Operational) = sso Redundancy Mode (Configured) = sso Redundancy State = Non Redundant Maintenance Mode = Disabled Communications = Down Reason: Simplex mode client count = 11 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
6-12
OL-13013-06
Chapter 6
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. 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 multicast 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.
6-13
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 Default dCEF switching: yes Update HWIDB counters: no Drop multicast packets: no . . . CEF NSF capable: yes IPC delayed func on SSO: no RRP state: I am standby RRP: no My logical slot: 0 RF PeerComm: 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:
6-14
OL-13013-06
Chapter 6
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 . . . 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
Step 1
Router# configure terminal
6-15
Command
Step 2 Step 3
Router(config)# router ospf processID
Purpose 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:
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
6-16
OL-13013-06
Chapter 6
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. (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 5
Router(config-router)# nsf t3 {manual [seconds] | adjacency}
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...>
6-17
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
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
6-18
OL-13013-06
Chapter 6
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
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
6-19
Chapter 6 Copying Files to the Redundant Supervisor Engine
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
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 RP:
Router# copy source_device:source_filename slavebootflash:target_filename
Tip
6-20
OL-13013-06
C H A P T E R

This chapter describes how to configure supervisor engine redundancy using route processor redundancy (RPR).
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html Cisco ME 6500 Series Ethernet switches do not support redundancy. In RPR redundancy mode, the ports on a Supervisor Engine 720-10GE in standby mode are disabled. RPR supports IPv6 multicast traffic. Release 12.2(33)SXH and later releases do not support Route Processor Redundancy Plus (RPR+).
Tip

Understanding RPR, page 7-1 Supervisor Engine Redundancy Guidelines and Restrictions, page 7-3 Configuring Supervisor Engine Redundancy, page 7-4 Performing a Fast Software Upgrade, page 7-6 Copying Files to the RP, page 7-7
Understanding RPR
These sections describe RPR supervisor engine redundancy:

Supervisor Engine Redundancy Overview, page 7-2 RPR Operation, page 7-2
7-1
Chapter 7 Understanding RPR
Supervisor Engine Configuration Synchronization, page 7-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. RPR supports a switchover time of 2 or more minutes. The following events cause a switchover:

A hardware failure on the active supervisor engine Clock synchronization failure between supervisor engines A manual 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 7-6.)
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 route processor (RP) 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 RP (including Layer 2 and Layer 3 protocols) are brought up Access control lists (ACLs) are reprogrammed into supervisor engine hardware
Note
In a switchover, there is a disruption of traffic because some address states are lost and then restored after they are dynamically redetermined.
7-2
OL-13013-06
Chapter 7
Configuring RPR Supervisor Engine Redundancy Supervisor Engine Redundancy Guidelines and Restrictions
Supervisor Engine Configuration Synchronization

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. 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.
Supervisor Engine Redundancy Guidelines and Restrictions

These sections describe supervisor engine redundancy guidelines and restrictions:

Redundancy Guidelines and Restrictions, page 7-3 Hardware Configuration Guidelines and Restrictions, page 7-3 Configuration Mode Restrictions, page 7-4
Redundancy Guidelines and Restrictions

These guidelines and restrictions apply to RPR:

When a redundant supervisor engine is in standby mode, 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. 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.
Hardware Configuration Guidelines and Restrictions

For redundant operation, the following guidelines and restrictions must be met:
Cisco IOS running on the SP and RP supports redundant configurations where the supervisor engines are identical. If they are not identical, one will boot first and become active and hold the other supervisor engine 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.
7-3
Chapter 7 Configuring Supervisor Engine Redundancy
Except during an FSU, both supervisor engines must have the same system image (see the Copying Files to the RP section on page 7-7).
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 must be set to 0x2102 ( config-register 0x2102).
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.
Configuring Supervisor Engine Redundancy

These sections describe how to configure supervisor engine redundancy:

Configuring Redundancy, page 7-4 Synchronizing the Supervisor Engine Configurations, page 7-5 Displaying the Redundancy States, page 7-5
Configuring Redundancy
To configure redundancy, perform this task: Command
Step 1 Step 2
Router(config)# redundancy Router(config-red)# mode rpr
Purpose Enters redundancy configuration mode. Configures RPR. When this command is entered, the redundant supervisor engine is reloaded and begins to work in RPR mode. Verifies that RPR is enabled. Displays the operating redundancy mode.
Step 3 Step 4
Router# show running-config Router# show redundancy states
This example shows how to configure the system for RPR:
7-4
OL-13013-06
Chapter 7
Configuring RPR Supervisor Engine Redundancy Configuring Supervisor Engine Redundancy
Router> enable Router# configure terminal Enter configuration commands, one per line. Router(config)# redundancy Router(config-red)# mode rpr Router(config-red)# end
End with CNTL/Z.
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 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 (Configured) = Route Processor Redundancy = Disabled = Enabled = Up
client count = 11 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
In this example, the system cannot enter the redundancy state because the second supervisor engine is disabled or missing:
Router# show redundancy states my state = 13 -ACTIVE peer state = 1 -DISABLED Mode = Simplex Unit = Primary Unit ID = 1
7-5
Chapter 7 Performing a Fast Software Upgrade
Redundancy Mode (Operational) = rpr Redundancy Mode (Configured) = rpr Redundancy State = Non Redundant Maintenance Mode = Disabled Communications = Down Reason: Simplex mode client count = 11 client_notification_TMR keep_alive TMR keep_alive count keep_alive threshold RF debug mask
= = = = =
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. FSU from an IOS image to a modular IOS image is not supported. FSU from a modular IOS image to an IOS image is not supported. (CSCsb07831)
To perform an FSU, perform this task: Command

Step 1
Router# copy source_device:source_filename {disk0 | disk1}:target_filename Or: Router# copy source_device:source_filename sup-bootflash:target_filename Or: Router# copy source_device:source_filename {slavedisk0 | slavedisk1}:target_filename Or: Router# copy source_device:source_filename slavesup-bootflash: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. Saves the configuration.
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
7-6
OL-13013-06
Chapter 7
Configuring RPR Supervisor Engine Redundancy Copying Files to the RP
Command
Step 4
Router# hw-module {module num} reset
Purpose Reloads the redundant supervisor engine and brings it back online (running the new version of the Cisco IOS software).
Note
Before reloading the redundant supervisor engine, make sure you wait long enough to ensure that all configuration synchronization changes have completed.
Step 5
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
Copying Files to the RP

Use the following command to copy a file to the bootflash: device on an active RP:
Router# copy source_device:source_filename bootflash:target_filename
Use the following command to copy a file to the bootflash: device on a redundant RP:
Router# copy source_device:source_filename slavebootflash:target_filename
Tip
7-7
Chapter 7 Copying Files to the RP
7-8
OL-13013-06
PA R T
Interface and Hardware Components
C H A P T E R
Configuring and Monitoring the Switch Fabric Functionality

This chapter describes how to configure the switching mode and monitor the switch fabric functionality that is included on the Supervisor Engine 720-10GE and the Supervisor Engine 720:

Understanding the Switch Fabric Functionality, page 8-1 Configuring the Switch Fabric Functionality, page 8-3 Monitoring the Switch Fabric Functionality, page 8-4
Note
Tip
Understanding the Switch Fabric Functionality

These sections describe how the switch fabric functionality works:

Switch Fabric Functionality Overview, page 8-2 Forwarding Decisions for Layer 3-Switched Traffic, page 8-2 Switching Modes, page 8-2
8-1
Chapter 8 Understanding the Switch Fabric Functionality
Switch Fabric Functionality Overview

The switch fabric functionality is built into the supervisor engine 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. The supervisor engine 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-10GE or 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 8-1 shows the switching modes used with fabric-enabled and nonfabric-enabled modules installed.
8-2
OL-13013-06
Chapter 8
Configuring and Monitoring the Switch Fabric Functionality Configuring the Switch Fabric Functionality
Table 8-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.
8-3
Chapter 8 Monitoring the Switch Fabric Functionality
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. These sections describe how to monitor the switch fabric functionality:

Displaying the Switch Fabric Redundancy Status, page 8-4 Displaying Fabric Channel Switching Modes, page 8-4 Displaying the Fabric Status, page 8-5 Displaying the Fabric Utilization, page 8-5 Displaying Fabric Errors, page 8-6
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 all modules:
Router# show fabric switching-mode module all Module Slot Switching Mode 3 Bus 5 Bus Router#
8-4
OL-13013-06
Chapter 8
Configuring and Monitoring the Switch Fabric Functionality Monitoring the Switch Fabric Functionality
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 module status 1 0 20G OK 1 1 20G OK 2 0 20G OK 2 1 20G OK 3 0 20G OK 4 0 20G OK 4 1 20G OK Router# fabric status OK OK OK OK OK OK OK hotStandby Standby support module N/A N/A Y(not-hot) Y(not-hot) Y(not-hot) Y(not-hot) Y(not-hot) Standby fabric
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 speed Ingress % 1 0 20G 0 1 1 20G 0 2 0 20G 0 2 1 20G 0 3 0 20G 48 4 0 20G 0 4 1 20G 0 Router# Egress % 0 0 24 24 0 0 0
8-5
Chapter 8 Monitoring the Switch Fabric Functionality
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
8-6
OL-13013-06
C H A P T E R
This chapter describes how to configure interfaces in Cisco IOS Release 12.2SX.
Note
Tip

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
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:
Fast Ethernet (use the fastethernet keyword) Gigabit Ethernet (use the gigabitethernet keyword) 10-Gigabit Ethernet (use the tengigabitethernet keyword)
Note
For WAN interfaces, see the configuration note for the WAN module.
Slot numberThe slot in which the module is installed. On switches supported by Cisco IOS Release 12.2SX, slots are numbered starting with 1 from top to bottom. Port numberThe physical port number on the module. On switches supported by Cisco IOS Release 12.2SX, 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)#
9-2
OL-13013-06
Chapter 9
Configuring Interfaces Using the Interface Command
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 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
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
9-3
Chapter 9 Configuring a Range of Interfaces
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.
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 = 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. You do not need to add a space between the interface numbers and the dash when using the interface range command.
9-4
OL-13013-06
Chapter 9
Configuring Interfaces Configuring a Range of Interfaces
The no interface range command supports VLAN interfaces. 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}] 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Defines the interface-range macro and save it in NVRAM.
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 Configuring IEEE 802.3x Flow Control, page 9-13
9-6
OL-13013-06
Chapter 9
Configuring Interfaces Configuring Optional Interface Features
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 ports to negotiate the speed and duplex mode. 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
A LAN port 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. 10-Gigabit Ethernet ports do not support autonegotiation.
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]]}}
Purpose Selects the Ethernet port to be configured. Configures the speed of the Ethernet interface.
When configuring the port speed for a 10/100/1000-Mbps Ethernet port, 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]
Purpose Selects the Ethernet port to be configured. Sets the duplex mode of the Ethernet port.
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. 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).
9-8
OL-13013-06
Chapter 9
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
Purpose Selects the port to be configured. Disables link negotiation.
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 properties]
1
Purpose
slot/port [transceiver
Displays the speed and duplex mode configuration. To display autonegotiation status for speed and duplex, add the transceiver properties option.
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 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
9-9
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#
This example shows how to display the speed and duplex autonegotiation status for Gigabit Ethernet port 3/1:
Router# show interfaces GigabitEthernet 3/1 transceiver properties Name : Gi3/1 Admin Speed Nego : Enable , Admin Duplex Nego : Enable 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 8092 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-11 Ethernet Ports, page 9-11 VLAN Interfaces, page 9-12
9-10
OL-13013-06
Chapter 9
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.
Note
Jumbo frame support fragments routed traffic in software on the route processor (RP). 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 RP 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-12 Layer 3 Ethernet Ports, page 9-12 Layer 2 Ethernet Ports, page 9-12
9-11
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. 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
Purpose Selects the interface to configure.
Step 2
Configures the MTU size.
9-12
OL-13013-06
Chapter 9
Command
Step 3 Step 4
Router(config-if)# end Router# show running-config interface [{gigabitethernet | tengigabitethernet} slot/port] 1.
Purpose Exits configuration mode. Displays the running configuration.
type = fastethernet, gigabitethernet, tengigabitethernet, or ge-wan
When configuring the MTU size, note the following information:

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 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 can be configured to transmit an IEEE 802.3x pause frame that requests the remote port to delay sending frames for a specified time. All Ethernet ports can can be configured to respond to IEEE 802.3x pause frames from other devices.
9-13
To configure flow control on an Ethernet port, perform this task: Command

Router(config)# interface type1 slot/port Router(config-if)# flowcontrol {receive | send} {desired | off | on} Router# show interfaces [type1 slot/port] flowcontrol 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Selects the port to configure. Configures a port to send or respond to pause frames. Displays the flow-control configuration for all ports.
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-13013-06
Chapter 9
Configuring the Port Debounce Timer

The port debounce timer delays notification of a link change. Delayed notification of a link changecan decrease traffic loss due to network reconfiguration. If the status of a link changes quickly from up to down and then back to up, the port debounce timer suppresses the link status notification. If the link transitions from up to down, but does not come back up, the port debounce timer delays the link status notification. Delayed link status notification allows a quick port status change and recovery to occur without triggering any of the changes that are necessary when a port stays down. The normal operation of DWDM links sometimes includes quick port status changes and recoveries. Delayed link status notification can also be used to mitigate link flaps because of bad cabling. 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
Router(config)# interface type
1
Purpose
slot/port
Selects the port to configure. Configures the debounce timer.

Note
Router(config-if)# link debounce [time debounce_time]
The default port debounce timer values provide appropriate link change notification delay on DWDM links.
Step 3
Router# show interfaces debounce 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Verifies the configuration.
When configuring the debounce timer on a port, note the following information:
The time keyword is supported only on fiber Gigabit Ethernet ports. With the time keyword, 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. The debounce timer recognizes 10-Gbps copper media and detects media-only changes.
Table 9-2 lists the time delay that occurs before notification of a link change.
Table 9-2 Default Port Debounce Timer Delay Times
Port Type Ports operating at 10 Mpbs or 100 Mbps: Ports operating at 1000 Mpbs Copper media ports: Fiber media ports:
Debounce Timer Disabled Debounce Timer Enabled 300 milliseconds 300 milliseconds 10 milliseconds 3100 milliseconds 3100 milliseconds 100 milliseconds
9-15
Chapter 9 Understanding Online Insertion and Removal
Table 9-2
Default Port Debounce Timer Delay Times
Port Type Ports operating at 10 Gbps:

Note
Debounce Timer Disabled Debounce Timer Enabled
The show interfaces debounce command does not display the default value for 10-GigabitEthernet ports when the port debounce timer is disabled. Except WS-X6502-10GE ports: WS-X6502-10GE ports: 10 milliseconds 1000 milliseconds 1000 milliseconds 3100 milliseconds
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
Purpose Adds a description for 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.
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, see the Catalyst 6500 Series Switch Installation Guide.
9-16
OL-13013-06
Chapter 9
Configuring Interfaces Monitoring and Maintaining Interfaces
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. Displays the current contents of the routing information field (RIF) cache.
Router# show running-config Router# show rif
9-17
Chapter 9 Monitoring and Maintaining Interfaces
Command
Router# show protocols [type slot/port]
Purpose 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 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 = 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.
Note
The clear counters command clears counters displayed with the EXEC show interfaces command, not counters retrieved using SNMP.
Resetting an Interface
To reset an interface, perform this task: Command
Router# clear interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Resets an interface.
This example shows how to reset Fast Ethernet port 5/5:

Router# clear interface fastethernet 5/5 Router#
9-18
OL-13013-06
Chapter 9
Configuring Interfaces Checking the Cable Status Using the TDR
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. type = fastethernet, gigabitethernet, or tengigabitethernet
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.
9-19
Chapter 9 Checking the Cable Status Using the TDR
Note
TDR can test cables up to a maximum length of 115 meters. For information about which modules support the TDR, see this document: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/ol_14271.ht ml
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-13013-06
C H A P T E R
10
Configuring UDLD
This chapter describes how to configure the UniDirectional Link Detection (UDLD) protocol. Release 12.2(33)SXI4 and later releases support fast UDLD, which provides faster detection times.
Note
Tip

Understanding UDLD, page 10-1 Default UDLD Configuration, page 10-4 Configuring UDLD, page 10-5
Understanding UDLD
Normal-mode UDLD classifies a link as unidirectional if the received UDLD packets do not contain information that is correct for the neighbor device. In addition to the functionality of normal mode UDLD, aggressive-mode UDLD puts ports into the errdisabled state if the relationship between two previously synchronized neighbors cannot be reestablished. These sections describe how UDLD works:

UDLD Overview, page 10-2 UDLD Aggressive Mode, page 10-3 Fast UDLD, page 10-4
10-1
Chapter 10 Understanding UDLD
Configuring UDLD
UDLD Overview
The Cisco-proprietary UDLD protocol monitors the physical configuration of the links between devices and ports that support UDLD. UDLD detects the existence of unidirectional links. When a unidirectional link is detected, UDLD puts the affected port into the errdisabled state and alerts the user. UDLD can operate in either normal or aggressive mode. For example, UDLD can help prevent these problems:

Spanning tree topology loops caused by unidirectional links Incorrect cabling of unbundled fiber strands Transceiver or link hardware malfunction Incorrect or excessive flooding of packets Loss of traffic without notice (also known as black holing)
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. 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. LAN ports with UDLD enabled periodically transmit UDLD packets to neighbor devices. If the packets are echoed back within a specific time frame (the message detection time is 3 times as long as the message interval, plus a timeout period) 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 disabled on nonfiber LAN ports to avoid sending unnecessary control traffic on this type of media because it is often used for access ports. Figure 10-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.
10-2
OL-13013-06
Chapter 10
Configuring UDLD Understanding UDLD
Figure 10-1
Unidirectional Link
Switch A TX RX
TX
RX
18720
Switch B
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, the default nonaggressive UDLD 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.
10-3
Chapter 10 Default UDLD Configuration
Configuring UDLD
Fast UDLD
Release 12.2(33)SXI4 and later releases support fast UDLD. Fast UDLD is a per-port configuration option that supports UDLD message time intervals between 200 and 1000 milliseconds. Fast UDLD can be configured to provide subsecond unidirectional link detection. (Without fast UDLD, the message time intervals are 7 through 90 seconds). When configuring fast UDLD, note the following guidelines and restrictions:

Cisco IOS Software Modularity images do not support fast UDLD. Fast UDLD is disabled by default. Normal and aggressive mode both support fast UDLD. Fast UDLD ports do not support the link debounce command. Fast UDLD supports only point-to-point links between network devices that support fast UDLD. Configure fast UDLD on at least two links between each connected network device. Fast UDLD does not support single-link connections to neighbor devices. Fast UDLD does not report a unidirectional link if the same error occurs simultaneously on more than one link to the same neighbor device. Fast UDLD cannot detect unidirectional links when the CPU utilization exceeds 60 percent. Fast UDLD is supported on a limited number of ports:
60 ports with a Supervisor Engine 720 10 ports with a Supervisor Engine 32 10 ports with a Cisco ME 6500 Series Ethernet Switch (ME6524)
Default UDLD Configuration

Table 10-1 shows the default UDLD configuration.
Table 10-1 UDLD Default Configuration
Feature UDLD global enable state UDLD aggressive mode Fast UDLD Fast UDLD error reporting UDLD per-port enable state for fiber-optic media UDLD per-port enable state for twisted-pair (copper) media
Default Value Globally disabled. Disabled. Disabled. Disabled. Enabled on all Ethernet fiber-optic LAN ports. Disabled on all Ethernet 10/100 and 1000BASE-TX LAN ports.
10-4
OL-13013-06
Chapter 10
Configuring UDLD Configuring UDLD
Configuring UDLD
These sections describe how to configure UDLD:

Enabling UDLD Globally, page 10-5 Enabling UDLD on LAN Ports, page 10-5 Disabling UDLD on Fiber-Optic LAN Ports, page 10-6 Configuring the Global UDLD Probe Message Interval, page 10-6 Configuring Fast UDLD, page 10-6 Resetting Disabled LAN Interfaces, page 10-7
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.
Enabling UDLD on LAN Ports

By default, UDLD is disabled on nonfiber-optic LAN ports. To enable UDLD on a LAN port, 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 a fiber-optic LAN port, 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. type = fastethernet, gigabitethernet, or tengigabitethernet
10-5
Chapter 10 Configuring UDLD
Configuring UDLD
Disabling UDLD on Fiber-Optic LAN Ports

By default, UDLD is enabled on fiber-optic LAN ports. To disable UDLD on a fiber-optic LAN port, 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.
Note
Router(config-if)# udld port disable
The no form of this command, which reverts the port to the udld enable global configuration command setting, is only supported on fiber-optic LAN ports.
Step 3
Configuring the Global UDLD Probe Message Interval

To configure the time between UDLD probe messages globally on all 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. Verifies the configuration.
Step 2
Configuring Fast UDLD

Release 12.2(33)SXI4 and later releases support fast UDLD. These sections describe how to configure fast UDLD:

Configuring Fast UDLD on a Port, page 10-7 Enabling Fast UDLD Error Reporting, page 10-7
Note
You can configure fast UDLD on ports where UDLD is not enabled, but fast UDLD is active only when UDLD is enabled on the port.
10-6
OL-13013-06
Chapter 10
Configuring UDLD Configuring UDLD
Configuring Fast UDLD on a Port

To configure fast UDLD on a port, perform this task: Command
Step 1
Router(config-if)# udld fast-hello interval
Purpose Configures the fast UDLD probe message interval on a port.

Note
See the guidelines and restrictions in the Fast UDLD section on page 10-4. When selecting the value, follow these guidelines:
Valid values are from 200 to 1000 milliseconds. Adjust the fast UDLD probe message interval to
the longest interval possible that will provide the desired link failure detection time. A shorter message interval increases the likelihood that UDLD will falsely report link failures under stressful conditions.
Step 2 Step 3
Router# show udld fast-hello Router# show udld fast-hello type
1
Displays fast UDLD configuration and operational state.

slot/number
Verifies the per-port fast UDLD configuration and operational state.
1.
type = fastethernet, gigabitethernet, or tengigabitethernet
Enabling Fast UDLD Error Reporting

By default, fast UDLD error-disables ports with unidirectional links. You can globally enable fast UDLD to report unidirectional links with a message displayed on the console instead of error-disabling ports with unidirectional links.
Note
When fast UDLD error reporting is enabled, you must manually take the action appropriate for the state of the link. To globally enable fast UDLD error reporting, perform this task:
Command
Router(config)# udld fast-hello error-reporting
Purpose Enables fast UDLD error reporting.
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.
10-7
Chapter 10 Configuring UDLD
Configuring UDLD
Tip
10-8
OL-13013-06
C H A P T E R
11
Power Management and Environmental Monitoring

This chapter describes the power management and environmental monitoring features in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Power Management, page 11-1 Understanding Environmental Monitoring, page 11-10
Understanding Power Management

These sections describe power management:

Enabling or Disabling Power Redundancy, page 11-2 Powering Modules Off and On, page 11-3 Viewing System Power Status, page 11-4 Power Cycling Modules, page 11-5 Determining System Power Requirements, page 11-5 Determining System Hardware Capacity, page 11-5 Determining Sensor Temperature Threshold, page 11-9
11-1
Chapter 11 Understanding Power Management
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, see 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 11-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 11-4). Table 11-1 describes how the system responds to changes in the power supply configuration.
Table 11-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)
11-2
OL-13013-06
Chapter 11
Power Management and Environmental Monitoring Understanding Power Management
Table 11-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
Powering Modules Off and On

To power modules off and on from the CLI, perform this task: Command
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.
11-3
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
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
11-4
OL-13013-06
Chapter 11
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

For information about power consumption, see the Release Notes for Cisco IOS Release 12.2SX publication at this URL: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/ol_14271.html
Determining System Hardware Capacity

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 a switching module:
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 1 RP 1 SP 7 8 I/O memory: Module 1 RP 1 SP 7 8 Router# Bytes: Total 176730048 192825092 195111584 195111584 Total 35651584 35651584 35651584 35651584
1 minute 1% 5% 69% 74% Used 51774704 51978936 35769704 35798632 Used 12226672 9747952 9616816 9616816
5 minutes 1% 4% 69% 74% %Used 29% 27% 18% 18% %Used 34% 27% 27% 27%
Bytes:
This example shows how to display EOBC-related statistics for the route processor, the switch processor, and the DFCs:
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 Dropped packets 0 0 0 0 0
11-5
8 Router#
Tx: Rx: Tx:
8 5 10
18543 12130 20317
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 FIB TCAM usage: Total 72 bits (IPv4, MPLS, EoM) 196608 144 bits (IP mcast, IPv6) 32768 detail: Protocol IPv4 MPLS EoM IPv6 IPv4 mcast IPv6 mcast Adjacency usage: Total 1048576
Used 11 Used 0 Used 36 7 Used 36 0 0 4 3 0 Used 175
%Used 1% %Used 0% %Used 1% 1% %Used 1% 0% 0% 1% 1% 0% %Used 1%
Forwarding engine load: Module 6 Netflow Resources
pps 8
peak-pps 1972
peak-time 02:02:17 UTC Thu Apr 21 2005
11-6
OL-13013-06
Chapter 11
TCAM utilization: ICAM utilization:
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 5 Router#
Rx 48
Bytes:
Tx buffer 12345 12345
Rx buffer 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#
11-7
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 PFC and DFC:
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 5 WS-SUP720-BASE supervisor CEF 9 WS-X6548-RJ-45 CEF256 CEF Router#
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#
11-8
OL-13013-06
Chapter 11
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 threshold #1 for module 5 power-output-fail: (sensor value != 0) is system major alarm module 5 outlet temperature: 26C threshold #1 for module 5 outlet temperature: (sensor value > 60) is system minor alarm threshold #2 for module 5 outlet temperature: (sensor value > 75) is system major alarm module 5 inlet temperature: 23C threshold #1 for module 5 inlet temperature: (sensor value > 50) is system minor alarm threshold #2 for module 5 inlet temperature: (sensor value > 65) is system major alarm EARL 1 outlet temperature: N/O
11-9
Chapter 11 Understanding Environmental Monitoring
threshold (sensor threshold (sensor threshold (sensor threshold (sensor
#1 for EARL value > 60) #2 for EARL value > 75) #1 for EARL value > 50) #2 for EARL value > 65)
1 outlet temperature: is system minor alarm 1 outlet temperature: is system major alarm EARL 1 inlet temperature: N/O 1 inlet temperature: is system minor alarm 1 inlet temperature: is system major alarm
Understanding Environmental Monitoring

These sections describe environmental monitoring:

Overview, page 11-10 Monitoring System Environmental Status, page 11-10 Understanding LED Environmental Indications, page 11-12
Overview
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.
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 Router# show environment alarm environmental alarms: no alarms Router# show environment cooling fan-tray 1: fan-tray 1 fan-fail: failed fan-tray 2:
11-10
OL-13013-06
Chapter 11
Power Management and Environmental Monitoring Understanding Environmental Monitoring
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 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
11-11
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

All modules have an LED labeled STATUS. There are LEDs on power supplies and fan trays that indicate problems. A nongreen LED indicates a problem. Supervisor engines have an LED labeled SYSTEM that indicates alarms. The alarm can be on a supervisor engine, module, power supply, fan tray, or backplane. In non-VSS mode, the SYSTEM LED indicates the following:

With one supervisor engine, the SYSTEM LED on the active supervisor engine indicates the alarm status for the chassis. With two supervisor engines, the SYSTEM LED on the standby supervisor engine indicates the alarm status of the standby supervisor engine. With one supervisor engine in each chassis, the SYSTEM LED on the active chassis supervisor engine indicates the alarm status for both chassis. The SYSTEM LED on the standby chassis supervisor engine indicates the alarm status of the standby chassis. With two supervisor engines in each chassis, the SYSTEM LED on the active-chassis, in-chassis active supervisor engine indicates system status for both chassis. With two supervisor engines in each chassis, the SYSTEM LED on the standby-chassis in-chassis active supervisor engine indicates the alarm status of the standby chassis. With two supervisor engines in each chassis, the SYSTEM LEDs on in-chassis standby supervisor engines are turned off.
In VSS mode, the SYSTEM LED indicates the following:
The SYSTEM LED 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, alerting you to a problem that could turn critical if corrective action is not taken. Temperature sensors monitor key components. The temperature sensors are polled every 30 seconds. If the sensed temperature falls below the alarm threshold, the alarm is immediately cancelled. For major alarms, there is a delay before any automatic actions occur to protect the switch. The delay is 5 minutes for a major alarm from a board sensor, and a 1 minute for a major alarm from an ASIC sensor. Table 11-2 lists the environmental indicators for the supervisor engine and switching modules.
Note
See the Catalyst 6500 Series Switch Supervisor Engine Guide for additional information on LEDs, including the supervisor engine STATUS LED.
11-12
OL-13013-06
Chapter 11
Power Management and Environmental Monitoring Understanding Environmental Monitoring
Table 11-2
Environmental Monitoring for Supervisor Engine and Switching Modules
Component VSS mode supervisor engine temperature sensor exceeds major threshold
Alarm Type Major
SYSTEM LED Color Red
Action Generates syslog message and an SNMP trap. After the time delay, these actions happen:
With a redundant supervisor engine in the same chassis, the peer chassis becomes active and the previously active supervisor engine drops to ROMMON. With Release 12.2(33)SXI4 and later releases, if the fan tray is faulty or absent, the chassis with fault shuts down. The peer chassis continues operating. With a single supervisor engine in the chassis, the supervisor engine drops to ROMMON and the peer chassis becomes active. With Release 12.2(33)SXI4 and later releases, if the fan tray is faulty or absent, the faulty chassis shuts down.
Non-VSS mode supervisor engine temperature sensor exceeds major threshold
Major
Red
Generates syslog message and an SNMP trap. After the time delay, these actions happen:
With a redundant supervisor engine in the same chassis, the redundant supervisor engine becomes active and the previously active supervisor engine drops to ROMMON. With Release 12.2(33)SXI4 and later releases, if the fan tray is faulty or absent, the chassis shuts down. With a single supervisor engine, the supervisor engine drops to ROMMON. With Release 12.2(33)SXI4 and later releases, if the fan tray is faulty or absent, the chassis shuts down.
Supervisor engine temperature sensor exceeds minor threshold Redundant supervisor engine temperature sensor exceeds major or minor threshold
Minor
Orange
Generates syslog message and an SNMP trap. Monitors the condition.
Major
Red
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.
Minor Switching module temperature sensor exceeds major threshold Switching module temperature sensor exceeds minor threshold Major
Orange Red
Monitors the condition if a minor alarm is generated. Generates syslog message and SNMP. Powers down the module (see the Understanding Power Management section on page 11-1).
Minor
Orange
Generates syslog message and an SNMP trap. Monitors the condition.
Tip
11-13
11-14
OL-13013-06
CH A P T E R
12
Configuring EnergyWise
EnergyWise is a Cisco energy management architecture that provides a common approach to configuring, reporting and managing the power consumed by Cisco switches and attached devices. With Cisco EnergyWise, power can be managed on a network, sub-network or network element level. Release 12.2(33)SXI4 Feature Modification EnergyWise Phase2 introduced on Catalyst 6500 Series
EnergyWise configuration procedures for the Catalyst 6500 Series are documented in the Cisco EnergyWise Configuration Guide, EnergyWise Phase 2 located at the following URL: http://www.cisco.com/en/US/docs/switches/lan/energywise/phase2/ios/configuration/guide/ew_v2.html Additional Cisco EnergyWise documents, such as White Papers, Data Sheets, FAQs, andare located at the following URL: http://www.cisco.com/en/US/products/ps10195/ Cisco EnergyWise Orchestrator configuration guides are located at the following URL: http://www.cisco.com/en/US/products/ps10195/products_installation_and_configuration_guides_list.h tml
12-1
OL-13013-06
CH A P T E R
13
Configuring Onboard Failure Logging

This chapter describes how to configure Onboard Failure Logging (OBFL) in Cisco IOS Release 12.2SX. Release 12.2(33)SXH and later releases support OBFL.
Note
Tip

Understanding OBFL, page 13-1 Restrictions for OBFL, page 13-9 Enabling OBFL, page 13-9 Configuration Examples for OBFL, page 13-10
Understanding OBFL
These sections describe OBFL:

Overview of OBFL, page 13-2 Data Collected by OBFL, page 13-2
13-1
Chapter 13 Understanding OBFL
Overview of OBFL
The Onboard Failure Logging (OBFL) feature collects data such as operating temperatures, hardware uptime, interrupts, and other important events and messages from system hardware installed in a Cisco router or switch. The data is stored in nonvolatile memory and helps technical personnel diagnose hardware problems.
Data Collected by OBFL

The OBFL feature records operating temperatures, hardware uptime, interrupts, and other important events and messages that can assist with diagnosing problems with hardware cards (or modules) installed in a Cisco router or switch. Data is logged to files stored in nonvolatile memory. When the onboard hardware is started up, a first record is made for each area monitored and becomes a base value for subsequent records. The OBFL feature provides a circular updating scheme for collecting continuous records and archiving older (historical) records, ensuring accurate data about the system. Data is recorded in one of two formats: continuous information that displays a snapshot of measurements and samples in a continuous file, and summary information that provides details about the data being collected. The data is displayed using the show logging onboard command. The message No historical data to display is seen when historical data is not available. The following sections describe the type of data collected:

Temperature, page 13-2 Operational Uptime, page 13-4 Interrupts, page 13-7 Message Logging, page 13-8
Temperature
Temperatures surrounding hardware modules can exceed recommended safe operating ranges and cause system problems such as packet drops. Higher than recommended operating temperatures can also accelerate component degradation and affect device reliability. Monitoring temperatures is important for maintaining environmental control and system reliability. Once a temperature sample is logged, the sample becomes the base value for the next record. From that point on, temperatures are recorded either when there are changes from the previous record or if the maximum storage time is exceeded. Temperatures are measured and recorded in degrees Celsius.
Temperature Example
-------------------------------------------------------------------------------TEMPERATURE SUMMARY INFORMATION -------------------------------------------------------------------------------Number of sensors : 12 Sampling frequency : 5 minutes Maximum time of storage : 120 minutes -------------------------------------------------------------------------------Sensor | ID | Maximum Temperature 0C -------------------------------------------------------------------------------MB-Out 980201 43 MB-In 980202 28 MB 980203 29 MB 980204 38 EARL-Out 910201 0 EARL-In 910202 0
13-2
OL-13013-06
Chapter 13
Configuring Onboard Failure Logging Understanding OBFL
SSA 1 980301 38 SSA 2 980302 36 JANUS 1 980303 36 JANUS 2 980304 35 GEMINI 1 980305 0 GEMINI 2 980306 0 --------------------------------------------------------------Temp Sensor ID 0C 1 2 3 4 5 6 7 8 9 10 11 12 --------------------------------------------------------------No historical data to display ---------------------------------------------------------------------------------------------------------------------------------------------TEMPERATURE CONTINUOUS INFORMATION -------------------------------------------------------------------------------Sensor | ID | -------------------------------------------------------------------------------MB-Out 980201 MB-In 980202 MB 980203 MB 980204 EARL-Out 910201 EARL-In 910202 SSA 1 980301 SSA 2 980302 JANUS 1 980303 JANUS 2 980304 GEMINI 1 980305 GEMINI 2 980306 ------------------------------------------------------------------------------Time Stamp |Sensor Temperature 0C MM/DD/YYYY HH:MM:SS | 1 2 3 4 5 6 7 8 9 10 11 12 ------------------------------------------------------------------------------03/06/2007 22:32:51 31 26 27 27 NA NA 33 32 30 29 NA NA 03/06/2007 22:37:51 43 28 29 38 NA NA 38 36 36 35 NA NA -------------------------------------------------------------------------------
To interpret this data:

Number of sensors is the total number of temperature sensors that will be recorded. A column for each sensor is displayed with temperatures listed under the number of each sensor, as available. Sampling frequency is the time between measurements. Maximum time of storage determines the maximum amount of time, in minutes, that can pass when the temperature remains unchanged and the data is not saved to storage media. After this time, a temperature record will be saved even if the temperature has not changed. The Sensor column lists the name of the sensor. The ID column lists an assigned identifier for the sensor. Maximum Temperature 0C shows the highest recorded temperature per sensor. Temp indicates a recorded temperature in degrees Celsius in the historical record. Columns following show the total time each sensor has recorded that temperature. Sensor ID is an assigned number, so that temperatures for the same sensor can be stored together.
13-3
Operational Uptime
The operational uptime tracking begins when the module is powered on, and information is retained for the life of the module.
Operational Uptime Example
-------------------------------------------------------------------------------UPTIME SUMMARY INFORMATION -------------------------------------------------------------------------------First customer power on : 03/06/2007 22:32:51 Total uptime : 0 years 0 weeks 2 days 18 hours 10 minutes Total downtime : 0 years 0 weeks 0 days 8 hours 7 minutes Number of resets : 130 Number of slot changes : 16 Current reset reason : 0xA1 Current reset timestamp : 03/07/2007 13:29:07 Current slot : 2 Current uptime : 0 years 0 weeks 1 days 7 hours 0 minutes -------------------------------------------------------------------------------Reset | | Reason | Count | -------------------------------------------------------------------------------0x5 64 0x6 62 0xA1 4 --------------------------------------------------------------------------------------------------------------------------------------------------------------UPTIME CONTINUOUS INFORMATION -------------------------------------------------------------------------------Time Stamp | Reset | Uptime MM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes -------------------------------------------------------------------------------03/06/2007 22:32:51 0xA1 0 0 0 0 0 --------------------------------------------------------------------------------
The operational uptime application tracks the following events:

Date and time the customer first powered on a component. Total uptime and downtime for the component in years, weeks, days, hours, and minutes. Total number of component resets. Total number of slot (module) changes. Current reset timestamp to include the date and time. Current slot (module) number of the component. Current uptime in years, weeks, days, hours, and minutes. Reset reason; see Table 13-1 to translate the numbers displayed. Count is the number of resets that have occurred for each reset reason.
Reset Reason Codes and Explanations
Table 13-1
Reset Reason Code (in hex) 0x01 0x02
Component/Explanation Chassis on Line card hot plug in
13-4
OL-13013-06
Chapter 13
Table 13-1
Reset Reason Code (in hex) 0x03 0x04 0x05 0x06 0x07 0x08 0x09 0x0A 0x0B 0x0C 0x0D 0x0E 0x0F 0x10 0x11 0x12 0x13 0x14 0x15 0x16 0x17 0x18 0x19 0x1A 0x1B 0x21 0x22 0x23 0x24 0x25 0x26 0x27 0x28 0x29 0x2A
Component/Explanation Supervisor requests line card off or on Supervisor requests hard reset on line card Line card requests Supervisor off or on Line card requests hard reset on Supervisor Line card self reset using the internal system register Momentary power interruption on the line card Off or on after Supervisor non-maskable interrupts (NMI) Hard reset after Supervisor NMI Soft reset after Supervisor NMI Off or on after line card asks Supervisor NMI Hard reset after line card asks Supervisor NMI Soft reset after line card asks Supervisor NMI Off or on after line card self NMI Hard reset after line card self NMI Soft reset after line card self NMI Off or on after spurious NMI Hard reset after spurious NMI Soft reset after spurious NMI Off or on after watchdog NMI Hard reset after watchdog NMI Soft reset after watchdog NMI Off or on after parity NMI Hard reset after parity NMI
13-5
Table 13-1
Reset Reason Code (in hex) 0x2B 0x31 0x32 0x33 0x34 0x35 0x36 0x37 0x38 0x39 0x3A 0x3B 0x41 0x42 0x43 0xA1
Component/Explanation Soft reset after parity NMI Off or on after system fatal interrupt Hard reset after system fatal interrupt Soft reset after system fatal interrupt Off or on after application-specific integrated circuit (ASIC) interrupt Hard reset after ASIC interrupt Soft reset after ASIC interrupt Off or on after unknown interrupt Hard reset after unknown interrupt Soft reset after unknown interrupt Off or on after CPU exception Hard reset after CPU exception Soft reset after CPU exception Reset data converted to generic data
13-6
OL-13013-06
Chapter 13
Interrupts
Interrupts are generated by system components that require attention from the CPU such as ASICs and NMIs. Interrupts are generally related to hardware limit conditions or errors that need to be corrected. The continuous format records each time a component is interrupted, and this record is stored and used as base information for subsequent records. Each time the list is saved, a timestamp is added. Time differences from the previous interrupt are counted, so that technical personnel can gain a complete record of the components operational history when an error occurs.
Interrupts Example
-------------------------------------------------------------------------------INTERRUPT SUMMARY INFORMATION -------------------------------------------------------------------------------Name | ID | Offset | Bit | Count -------------------------------------------------------------------------------No historical data to display --------------------------------------------------------------------------------------------------------------------------------------------------------------CONTINUOUS INTERRUPT INFORMATION -------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS mmm | Name | ID | Offset | Bit -------------------------------------------------------------------------------03/06/2007 22:33:06 450 Port-ASIC #2 9 0x00E7 6 --------------------------------------------------------------------------------

Name is a description of the component including its position in the device. ID is an assigned field for data storage. Offset is the register offset from a component registers base address. Bit is the interrupt bit number recorded from the components internal register. The timestamp shows the date and time that an interrupt occurred down to the millisecond.
13-7
Message Logging
The OBFL feature logs standard system messages. Instead of displaying the message to a terminal, the message is written to and stored in a file, so the message can be accessed and read at a later time. System messages range from level 1 alerts to level 7 debug messages, and these levels can be specified in the hw module logging onboard command.
Error Message Log Example
-------------------------------------------------------------------------------ERROR MESSAGE SUMMARY INFORMATION -------------------------------------------------------------------------------Facility-Sev-Name | Count | Persistence Flag MM/DD/YYYY HH:MM:SS -------------------------------------------------------------------------------No historical data to display --------------------------------------------------------------------------------------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION -------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name -------------------------------------------------------------------------------03/06/2007 22:33:35 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testing

A timestamp shows the date and time the message was logged. Facility-Sev-Name is a coded naming scheme for a system message, as follows:
The Facility code consists of two or more uppercase letters that indicate the hardware device
(facility) to which the message refers.

Sev is a single-digit code from 1 to 7 that reflects the severity of the message. Name is one or two code names separated by a hyphen that describe the part of the system from
where the message is coming.

The error message follows the Facility-Sev-Name codes. For more information about system messages, see the Cisco IOS System and Error Messages guide. Count indicates the number of instances of this message that is allowed in the history file. Once that number of instances has been recorded, the oldest instance will be removed from the history file to make room for new ones. The Persistence Flag gives a message priority over others that do not have the flag set.
13-8
OL-13013-06
Chapter 13
Configuring Onboard Failure Logging Restrictions for OBFL
Restrictions for OBFL
Software RestrictionsIf a device (router or switch) intends to use linear flash memory as its OBFL storage media, Cisco IOS software must reserve a minimum of two physical sectors (or physical blocks) for the OBFL feature. Because an erase operation for a linear flash device is done on per-sector (or per-block) basis, one extra physical sector is needed. Otherwise, the minimum amount of space reserved for the OBFL feature on any device must be at least 8 KB. Firmware RestrictionsIf a line card or port adapter runs an operating system or firmware that is different from the Cisco IOS operating system, the line card or port adapter must provide device driver level support or an interprocess communications (IPC) layer that allows the OBFL file system to communicate to the line card or port adapter. This requirement is enforced to allow OBFL data to be recorded on a storage device attached to the line card or port adapter. Hardware RestrictionsTo support the OBFL feature, a device must have at least 8 KB of nonvolatile memory space reserved for OBFL data logging.
Enabling OBFL
Note
The OBFL feature is enabled by default. Because of the valuable information this feature offers technical personnel, it should not be disabled. If you find the feature has been disabled, use the following steps to reenable it. To enable OBFL, perform this task:
Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Enables OBFL on the specified hardware module.
Note
Router# configure terminal Router(config)# hw-module switch switch-number module module-number logging onboard [message level {1-7}]
By default, all system messages sent to a device are logged by the OBFL feature. You can define a specific message level (only level 1 messages, as an example) to be logged using the message level keywords.
Step 4
Router(config)# end
Ends global configuration mode.
13-9
Chapter 13 Configuration Examples for OBFL
Configuration Examples for OBFL

The important OBFL feature is the information that is displayed by the show logging onboard module privileged EXEC command. This section provides the following examples of how to enable and display OBFL records.

Enabling OBFL Message Logging: Example OBFL Message Log: Example OBFL Component Uptime Report: Example OBFL Report for a Specific Time: Example
Enabling OBFL Message Logging: Example

The following example shows how to configure OBFL message logging at level 3:
Router(config)# hw-module switch 2 module 1 logging onboard message level 3
OBFL Message Log: Example

The following example shows how to display the system messages that are being logged for module 2:
Router# show logging onboard module 2 message continuous -------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION -------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name -------------------------------------------------------------------------------03/06/2007 22:33:35 %SWITCH_IF-3-CAMERR : [chars], for VCI [dec] VPI [dec] in stdby data path check, status: [dec] --------------------------------------------------------------------------------
OBFL Component Uptime Report: Example

The following example shows how to display a summary report for component uptimes for module 2:
Router# show logging onboard module 2 uptime -------------------------------------------------------------------------------UPTIME SUMMARY INFORMATION -------------------------------------------------------------------------------First customer power on : 03/06/2007 22:32:51 Total uptime : 0 years 0 weeks 0 days 0 hours 35 minutes Total downtime : 0 years 0 weeks 0 days 0 hours 0 minutes Number of resets : 1 Number of slot changes : 0 Current reset reason : 0xA1 Current reset timestamp : 03/06/2007 22:31:34 Current slot : 2 Current uptime : 0 years 0 weeks 0 days 0 hours 35 minutes -------------------------------------------------------------------------------Reset | | Reason | Count | -------------------------------------------------------------------------------No historical data to display --------------------------------------------------------------------------------
13-10
OL-13013-06
Chapter 13
Configuring Onboard Failure Logging Configuration Examples for OBFL
OBFL Report for a Specific Time: Example

The following example shows how to display continuous reports for all components during a specific time period:
Router# show logging onboard module 3 continuous start 15:01:57 1 Mar 2007 end 15:04:57 3 Mar 2007 PID: WS-X6748-GE-TX , VID: , SN: SAL09063B85
-------------------------------------------------------------------------------UPTIME CONTINUOUS INFORMATION -------------------------------------------------------------------------------Time Stamp | Reset | Uptime MM/DD/YYYY HH:MM:SS | Reason | years weeks days hours minutes -------------------------------------------------------------------------------03/01/2007 15:01:57 0xA1 0 0 0 10 0 03/03/2007 02:29:29 0xA1 0 0 0 5 0 --------------------------------------------------------------------------------------------------------------------------------------------------------------TEMPERATURE CONTINUOUS INFORMATION -------------------------------------------------------------------------------Sensor | ID | -------------------------------------------------------------------------------MB-Out 930201 MB-In 930202 MB 930203 MB 930204 EARL-Out 910201 EARL-In 910202 SSA 1 930301 SSA 2 930302 JANUS 1 930303 JANUS 2 930304 GEMINI 1 930305 GEMINI 2 930306 ------------------------------------------------------------------------------Time Stamp |Sensor Temperature 0C MM/DD/YYYY HH:MM:SS | 1 2 3 4 5 6 7 8 9 10 11 12 ------------------------------------------------------------------------------03/01/2007 15:01:57 26 26 NA NA NA NA 0 0 0 0 0 0 03/01/2007 15:06:57 39 27 NA NA NA NA 39 37 36 29 32 32 03/01/2007 15:11:02 40 27 NA NA NA NA 40 38 37 30 32 32 03/01/2007 17:06:06 40 27 NA NA NA NA 40 38 37 30 32 32 03/01/2007 19:01:09 40 27 NA NA NA NA 40 38 37 30 32 32 03/03/2007 02:29:30 25 26 NA NA NA NA 0 0 0 0 0 0 03/03/2007 02:34:30 38 26 NA NA NA NA 39 37 36 29 31 31 03/03/2007 04:29:33 40 27 NA NA NA NA 40 38 36 30 32 32 03/03/2007 06:24:37 40 27 NA NA NA NA 40 38 36 29 32 32 03/03/2007 08:19:40 40 27 NA NA NA NA 40 38 36 29 32 32 03/03/2007 10:14:44 40 27 NA NA NA NA 40 38 36 30 32 32 03/03/2007 12:09:47 40 27 NA NA NA NA 40 38 36 30 32 32 03/03/2007 14:04:51 40 27 NA NA NA NA 40 38 36 30 32 32 -------------------------------------------------------------------------------------------------------------------------------------------------------------CONTINUOUS INTERRUPT INFORMATION -------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS mmm | Name | ID | Offset | Bit -------------------------------------------------------------------------------03/01/2007 15:01:59 350 Port-ASIC #0 7 0x00E7 6 03/03/2007 02:29:34 650 Port-ASIC #0 7 0x00E7 6 --------------------------------------------------------------------------------
13-11
Chapter 13 Configuration Examples for OBFL
-------------------------------------------------------------------------------ERROR MESSAGE CONTINUOUS INFORMATION -------------------------------------------------------------------------------MM/DD/YYYY HH:MM:SS Facility-Sev-Name -------------------------------------------------------------------------------03/01/2007 15:02:15 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testing 03/03/2007 02:29:51 %GOLD_OBFL-3-GOLD : Diagnostic OBFL: Diagnostic OBFL testing --------------------------------------------------------------------------------
13-12
OL-13013-06
C H A P T E R
14

This chapter describes how to configure the online diagnostics in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Online Diagnostics, page 14-1 Configuring Online Diagnostics, page 14-2 Running Online Diagnostic Tests, page 14-5 Performing Memory Tests, page 14-12
Understanding Online Diagnostics

With online diagnostics, you can test and verify the hardware functionality of the 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, module online insertion and removal (OIR), and system reset. The nondisruptive online diagnostic tests run as part of background health monitoring. Either disruptive or nondisruptive tests can be run at the users request (on-demand). The online diagnostics detect problems in the following areas:

Hardware components Interfaces (GBICs, Ethernet ports, and so forth)
14-1
Chapter 14 Configuring Online Diagnostics
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, schedule, 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.

These sections describe how to configure online diagnostics:

Setting Bootup Online Diagnostics Level, page 14-2 Configuring On-Demand Online Diagnostics, page 14-3 Scheduling Online Diagnostics, page 14-4
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 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)#
14-2
OL-13013-06
Chapter 14
Configuring 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 nondisruptive 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 nondisruptive tests. To display the available tests and their attributes, and determine which commands are in the nondisruptive 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 number 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 number test all command. The EOBC connection is disrupted during this test and will cause the health-monitoring tests to fail and take recovery action.
Step 5
Run the exhaustive-memory tests.
14-3
Chapter 14 Configuring Online Diagnostics
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 number 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 number 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 number 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 on the specified module for a specific date and time, how many times to run (iterations), and what action to take when errors are found.
14-4
OL-13013-06
Chapter 14
Configuring Online Diagnostics Running Online Diagnostic Tests
This example shows how to schedule diagnostic testing on a specific date and time for a specific port on module 1:
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, the generation of a system message upon test failure, or the enabling or disabling 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 number test {test_id | test_id_range | all} [hour hh] [min mm] [second ss] [millisec ms] [day day] Router(config)#[no] diagnostic monitor module number test {test_id | test_id_range | all} Router# show diagnostic health
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. Displays the output for the health checks performed.
Step 2 Step 3
This example shows how to configure the specified test to run every two minutes on module 1:
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 14-6
14-5
Chapter 14 Running Online Diagnostic Tests
Running All Online Diagnostic Tests, page 14-7 Displaying Online Diagnostic Tests and Test Results, page 14-7
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 the console. When disruptive tests are complete, a warning message on the console recommends that you reload the system to return to normal operation. Strictly follow this warning. While tests are running, all ports are shut down because a stress test is being performed with ports configured to loop internally; external traffic might alter the test results. The switch must be rebooted to bring the switch to normal operation. When you issue 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 switching module, rather than the supervisor engine, after the test is initiated and complete, you must reset the switching 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
Router# diagnostic start module number test {test_id | test_id_range | minimal | complete | basic | per-port | non-disruptive | all} [port {num | port#_range | all}] Router# diagnostic stop module number
Purpose Starts a diagnostic test on a port or range of ports on the specified module. Stops a diagnostic test on the specified module.
This example shows how to start a diagnostic test on module 1:

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#
14-6
OL-13013-06
Chapter 14
Running All Online Diagnostic Tests

You can run all diagnostic tests, disruptive and nondisruptive, at once with a single command. In this case, all test dependencies will be handled automatically.
Note
Running all online diagnostic tests will disrupt normal system operation. Reset the system after the diagnostic start system test all command has completed. Do not insert, remove, or power down modules or the supervisor while the system test is running. Do not issue any diagnostic command other than the diagnostic stop system test all command while the system test is running. Make sure no traffic is running in background.
To start or stop all online diagnostic tests, perform one of these tasks: Command
Router# diagnostic start system test all Router# diagnostic stop system test all
Purpose Executes all online diagnostic tests. Stops the execution of all online diagnostic tests.
This example shows how to start all online diagnostic tests:

Router# diagnostic start system test all ************************************************************************* * WARNING: * * 'diagnostic start system test all' will disrupt normal system * * operation. The system requires RESET after the command * * 'diagnostic start system test all' has completed prior to * * normal use. * * * * IMPORTANT: * * 1. DO NOT INSERT, OIR, or POWER DOWN Linecards or * * Supervisor while system test is running. * * * * 2. DO NOT ISSUE ANY DIAGNOSTIC COMMAND except * * "diagnostic stop system test all" while system test * * is running. * * * * 3. PLEASE MAKE SURE no traffic is running in background. * ************************************************************************* Do you want to continue? [no]:
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 following show commands:

show diagnostic content show diagnostic health
14-7
To display the diagnostic tests that are configured, perform this task: Command show diagnostic {bootup level | content [module num] | events [module num] [event-type event-type] | health | ondemand settings | result [module num] [detail] | schedule [module num]} Purpose Displays the test results of online diagnostics and lists supported test suites.
This example shows how to display the online diagnostics that are configured on module 1:
Router# show diagnostic content module 1 Module 1: Supervisor Engine 32 8GE (Active) 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 reload supervisor / NA K/* - Require resetting the line card after the test has completed / NA T/* - Shut down all ports and need reload supervisor / NA Test Interval day hh:mm:ss.ms =============== 000 00:00:30.00 000 00:00:15.00 not configured not configured not configured 000 00:00:02.00 000 00:00:15.00 000 00:00:15.00 not configured not configured not configured 000 00:00:15.00 000 00:00:15.00 000 00:00:15.00 000 00:00:15.00 000 00:00:15.00 000 00:00:15.00 000 00:00:15.00 not configured not configured 000 00:00:15.00 000 00:00:15.00 not configured not configured not configured not configured not configured not configured not configured not configured Threshold ===== 5 10 n/a n/a n/a 10 10 10 n/a n/a n/a 10 10 10 10 10 10 10 n/a n/a 10 10 n/a n/a n/a n/a n/a n/a n/a n/a
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) 29) 30)
Test Name ================================== TestScratchRegister -------------> TestSPRPInbandPing --------------> TestTransceiverIntegrity --------> TestActiveToStandbyLoopback -----> TestLoopback --------------------> TestTxPathMonitoring ------------> TestNewIndexLearn ---------------> TestDontConditionalLearn --------> TestBadBpduTrap -----------------> TestMatchCapture ----------------> TestProtocolMatchChannel --------> TestFibDevices ------------------> TestIPv4FibShortcut -------------> TestL3Capture2 ------------------> TestIPv6FibShortcut -------------> TestMPLSFibShortcut -------------> TestNATFibShortcut --------------> TestAclPermit -------------------> TestAclDeny ---------------------> TestQoSTcam ---------------------> TestL3VlanMet -------------------> TestIngressSpan -----------------> TestEgressSpan ------------------> TestNetflowInlineRewrite --------> TestTrafficStress ---------------> TestFibTcamSSRAM ----------------> TestAsicMemory ------------------> TestAclQosTcam ------------------> TestNetflowTcam -----------------> ScheduleSwitchover -------------->
Attributes ============ ***N****A*** ***N****A*** **PD****I*** M*PDSX**I*** M*PD*X**I*** M**N****A*** M**N****I*** M**N****I*** M**D*X**I*** M**D*X**I*** M**D*X**I*** M**N****I*** M**N****I*** M**N****I*** M**N****I*** M**N****I*** M**N****I*** M**N****I*** M**D*X**I*** M**D*X**I*** M**N****I*** M**N****I*** M**D*X**I*** C*PD*X**I*** ***D*X**I**T ***D*X**IR** ***D*X**IR** ***D*X**IR** ***D*X**IR** ***D*X**I***
14-8
OL-13013-06
Chapter 14
31) 32) 33) 34) 35) 36) 37) Router#
TestFirmwareDiagStatus ----------> TestAsicSync --------------------> TestUnusedPortLoopback ----------> TestErrorCounterMonitor ---------> TestPortTxMonitoring ------------> TestL3HealthMonitoring ----------> TestCFRW ------------------------>
M**N****I*** ***N****A*** **PN****A*** ***N****A*** **PN****A*** ***N**FEA*** M*VN*X**I***
000 000 000 000 000 000 not
00:00:15.00 00:00:15.00 00:01:00.00 00:00:30.00 00:01:15.00 00:00:05.00 configured
10 10 10 10 5 10 n/a
This example shows how to display the online diagnostic results for module 1:
Router# show diagnostic result module 1 Current bootup diagnostic level: bypass Module 1: Cisco ME 6524 Ethernet Switch SerialNo : CAT103956WS
Overall Diagnostic Result for Module 1 : MINOR ERROR Diagnostic level at card bootup: bypass Test results: (. = Pass, F = Fail, U = Untested) 1) TestSPRPInbandPing --------------> . 2) TestTransceiverIntegrity: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------U U U U U U U U U U U U U U U U U U U U U U U U Port 25 26 27 28 29 30 31 32 ---------------------------. . U U U U U .
3) TestScratchRegister -------------> . 4) TestNonDisruptiveLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------. . . . . . . . . . . . . . . . . . . . . . . . Port 25 26 27 28 29 30 31 32 ---------------------------U U U U U U U U
5) TestLoopback: Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------. F . . . . . . . . . . . . . . . . . . . . . . Port 25 26 27 28 29 30 31 32 ---------------------------. . . . . . . .
6) 7) 8) 9) 10) 11) 12)
TestNewIndexLearn ---------------> TestDontConditionalLearn --------> TestBadBpduTrap -----------------> TestMatchCapture ----------------> TestProtocolMatchChannel --------> TestFibDevices ------------------> TestIPv4FibShortcut ------------->
. . . . . . .
14-9
13) 14) 15) 16) 17) 18) 19) 20) 21) 22) 23)
TestL3Capture2 ------------------> TestIPv6FibShortcut -------------> TestMPLSFibShortcut -------------> TestNATFibShortcut --------------> TestAclPermit -------------------> TestAclDeny ---------------------> TestQoSTcam ---------------------> TestL3VlanMet -------------------> TestIngressSpan -----------------> TestEgressSpan ------------------> TestNetflowInlineRewrite:
. . . . . . . . . .
Port 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 ---------------------------------------------------------------------------U U U U U U U U U U U U U U U U U U U U U U U U Port 25 26 27 28 29 30 31 32 ---------------------------U U U U U U U U
24) 25) 26) 27) 28) 29) 30) 31) 32)
TestTrafficStress ---------------> TestFibTcamSSRAM ----------------> TestAsicMemory ------------------> TestLtlFpoeMemoryConsistency ----> TestAclQosTcam ------------------> TestNetflowTcam -----------------> FirmwareDiagStatus --------------> TestL3HealthMonitoring ----------> TestCFRW: Device 1 --------.
U U U . U U . .
33) TestRwEngineOverSubscription ----> U
Router#
This example shows how to display the detailed online diagnostic results for module 1:
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 ------------------> 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) 330 May 12 2003 14:49:36 n/a n/a May 12 2003 14:49:36 0
14-10
OL-13013-06
Chapter 14
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 ------------------> 0 (DIAG_SUCCESS) Total run count -------------> 0 Last test execution time ----> n/a First test failure time -----> n/a Last test failure time ------> n/a Last test pass time ---------> n/a Total failure count ---------> 0 Consecutive failure count ---> 0 ________________________________________________________________________ . . . Router#
This example shows how to display the output for the health checks performed:
Router# show diagnostic health CPU utilization for the past 5 mins is greater than 70% five minutes: 81% EARL reset history: Module 5: WS-SUP720-BASE EARL patch log Num. of times patch applied : 0 Num. of times patch requested : 0 Non-zero port counters for 1/8 13. linkChange = 159810 Non-zero port counters for 1/9 0. rxCRCAlignErrors = 5 3. rxFragmentPkts = 9 6. ifInErrors = 46 13. linkChange = 1 Current bootup diagnostic level: minimal Test results: (. = Pass, F = Fail, U = Untested) 36) TestErrorCounterMonitor ---------> F Error code ------------------> 1 (DIAG_FAILURE) Total run count -------------> 29 Last test execution time ----> Mar 16 2007 19:04:02 First test failure time -----> Mar 16 2007 19:03:21 Last test failure time ------> Mar 16 2007 19:04:02 Last test pass time ---------> Mar 16 2007 19:03:19 Total failure count ---------> 4 Consecutive failure count ---> 4
14-11
Chapter 14 Performing Memory Tests
Error Records as following. ID -- Asic Identification IN -- Asic Instance PO -- Asic Port Number RE -- Register Identification RM -- Register Identification More EG -- Error Group DV -- Delta Value CF -- Consecutive Failure TF -- Total Failure ID IN PO RE RM DV EG CF TF --------------------------------------------------------------26 0 0 338 255 256 2 13 13 26 0 0 344 255 256 2 13 13 26 0 0 358 255 256 2 13 13 System Memory: 524288K total, 353225K used, 171063K free, 1000K kernel reserved Lowest(b) : 171020288 Process kernel, type POSIX, PID = 1 0K total, 0K text, 0K data, 0K stack, 0K dynamic Process sbin/chkptd.proc, type POSIX, PID = 16386 2296K total, 1988K text, 120K data, 12K stack, 176K dynamic 65536 heapsize, 55356 allocated, 8084 free 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 number test all command.
Tip
14-12
OL-13013-06
C H A P T E R
15

This chapter describes how to configure support for Cisco IP phones on the Catalyst 6500 series switches. This information may be helpful in configuring support for non-Cisco IP phones, but we recommend that you see the manufacturers documentation for those devices.
Note
Cisco ME 6500 Series Ethernet switches are not typically used to support Cisco IP phones. For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html
Tip

Understanding Cisco IP Phone Support, page 15-1 Default Cisco IP Phone Support Configuration, page 15-6 Cisco IP Phone Support Configuration Guidelines and Restrictions, page 15-7 Configuring Cisco IP Phone Support, page 15-7
Understanding Cisco IP Phone Support

These sections describe Cisco IP phone support:

Cisco IP Phone Connections, page 15-2 Cisco IP Phone Voice Traffic, page 15-2 Cisco IP Phone Data Traffic, page 15-3 IP Phone Power Configurations, page 15-3 Other Cisco IP Phone Features, page 15-6
15-1
Chapter 15 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 15-1 shows a Cisco IP phone connected between a switch and a PC.
Figure 15-1 Cisco IP Phone Connected to a Switch
Cisco IP Phone
Phone ASIC
P2 P1 Catalyst switch 3-port switch P3 Access port Workstation/PC

192734
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. You can configure Layer 2 access ports on the switch to send Cisco Discovery Protocol (CDP) packets that configure 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 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). To provide more predictable voice traffic flow, you can configure QoS on the switch to trust the Layer 3 IP precedence or Layer 2 CoS value in the received traffic (see Chapter 40, Configuring PFC QoS).
15-2
OL-13013-06
Chapter 15
Configuring Cisco IP Phone Support Understanding Cisco IP Phone Support
Release 12.2(33)SXI1 and later releases support the trusted boundary device verification feature, which can configure ports on the switch to apply configured QoS port trust commands only when the Cisco Discovery Protocol (CDP) verifies that the device attached to the port is a Cisco IP phone. See the Configuring Trusted Boundary with Cisco Device Verification section on page 40-91. 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.
Cisco IP Phone Data Traffic

Note
The ability to either trust or mark tagged data traffic from the device attached to the access port on the Cisco IP phone is called the trusted boundary (extended trust for CDP devices) feature. 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. Untagged data 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 15-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.
Most IP phones have no ability to notify the switch of link state changes on the IP phones access port. When a device attached to the access port is disconnected or disabled administratively, the switch is unaware of the change. Some Cisco IP phones can send a CDP message containing a host presence type length value (TLV) indicating the changed state of the access port link. To recognize the host presence TLV, the switch must be running Cisco IOS Release 12.2(33)SXI or a later release.
IP Phone Power Configurations

These sections describe IP phone power configurations:

Locally Powered IP Phones, page 15-3 Inline-Powered IP Phones, page 15-4 Inline Power Management, page 15-4
Locally Powered IP Phones

There are two sources of local power:

From a power supply connected to the IP phone From a power supply through a patch panel over the twisted-pair Ethernet cable to the IP phone
15-3
Chapter 15 Understanding Cisco IP Phone Support
When a locally powered IP phone is present on a switching module port, the switching module cannot detect its presence. The supervisor engine can discover a locally powered Cisco IP phone through CDP messaging with the Cisco IP phone. If a locally powered IP phone loses local power, the switching module can discover and supply inline power to the IP phone if the inline power mode is set to auto.
Inline-Powered IP Phones
Switching modules that support an inline power daughtercard can supply power over the twisted-pair Ethernet cable to external devices such as IP phones, IP cameras, and wireless access points. Cisco inline power modules are available to support one or both of the two most common implementations of Power over Ethernet (PoE):

Cisco Prestandard Inline Power IEEE 802.3af standard
With an inline power card installed, a switching module can automatically detect and provision a powered device that adheres to a PoE implementation supported by the card. The switching module can supply power to devices supporting other PoE implementations only through manual configuration. Only one device can be powered per port, and the device must be connected directly to the switch port. For example, if a second IP phone is daisy-chained off a phone that is connected to the switch port, the second phone cannot be powered by the switch.
Note
For information about switching modules that support inline power, see the Release Notes for Cisco IOS Release 12.2SX publication at this URL: http://www.cisco.com/en/US/docs/switches/lan/catalyst6500/ios/12.2SX/release/notes/ol_14271.html
Inline Power Management

Each inline-powered device, such as an IP phone or a wireless access point, requires power to be allocated from the chassis power budget. Because each powered device can have unique power requirements, more devices can be supported if the systems power management software can intelligently allocate the necessary power on a per-port basis. With Release 12.2(33)SXH and later releases, you can configure the switching module to allocate and apply inline power to individual ports:

When an attached inline-powered device is discovered, at a power level based on information sensed from the device or at a default or specified maximum power level (auto mode) At a fixed default or specified level, whether or not an inline-powered device is present on the port (static mode)
The Cisco Prestandard PoE implementation defines a method to sense an attached inline-powered device and to apply an initial power level. After activation, a Cisco Prestandard device that supports CDP can negotiate a lower or higher power allocation using CDP messaging.
15-4
OL-13013-06
Chapter 15
Configuring Cisco IP Phone Support Understanding Cisco IP Phone Support
The IEEE 802.3af PoE standard defines a method to sense an attached device and to immediately classify the devices power requirement into these power ranges:

Class 0: Up to 15.4 W per port (default classification) Class 1: Up to 4 W per port Class 2: Up to 7 W per port Class 3: Up to 15.4 W per port
The IEEE 802.3af standard contains no provision for subsequent readjustment of a devices power allocation. Newer inline power daughtercards (such as the WS-F6K-48-AF) add the ability to accurately measure the power provided by the port to the powered device, and to enable power policing on a port. With power measurement and policing, you can safely override the IEEE 802.3af power classification of a device that requires a power level at the lower end of its IEEE power classification range. Cisco inline-powered devices that support 802.3af power classification and CDP can use CDP to override the IEEE 802.3af power classification. A switching module whose inline power card supports both PoE implementations will attempt both detection methods in parallel. If the attached device responds to both detection methods, the module will consider the device to be an IEEE 802.3af device.
Caution
When an 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 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.
Example: Cisco Prestandard IP Phone

When a switching module port detects an unpowered Cisco Prestandard IP phone, the switching module reports to the supervisor engine that an unpowered Cisco IP phone is present and indicates which module and port the phone is on. If the port is configured in auto mode, the supervisor engine determines whether there is enough system power available to power up the Cisco IP phone. The power allocation will be the lower of the default power or the configured port maximum if a maximum has been specified. If there is sufficient power available, the supervisor engine removes the allocated power 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. Unless a lower maximum power level has been configured for the port, 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.
15-5
Chapter 15 Default Cisco IP Phone Support Configuration
Example: IEEE 802.3af IP Phone

When a switching module port detects an unpowered IEEE 802.3af-compliant IP phone, the module detects the phones IEEE 802.3af power classification and notifies the supervisor engine of the phones location and power requirement. If there is sufficient system power available, the supervisor engine allocates the power level indicated by the IEEE class and sends a message to the switching module approving power to the port. If there is not enough available power for the IP phone, the supervisor engine sends a message to the switching module indicating that power is denied to the port. For example, an IEEE 802.3af-compliant IP phone consuming 7.1 W is plugged into a port. The switching module detects the phone and determines that its IEEE power classification is Class 3, which requires between 7.0 W and 15.4 W. The switching module notifies the supervisor engine of the port location and the IEEE classification of the phone. If there is sufficient power available, the supervisor engine removes 15.4 W from the system power and approves power to the port. For this phone, the system is required to reserve an unnecessary 8.3 W due to the broad ranges of the IEEE classification system. If the auto mode is selected for this port with a maximum power level lower than 15.4 W, the Class 3 phone will be denied power. By using a newer inline power card (WS-F6K-48-AF and later) that supports power measurement and policing, the situation described in this example can be managed with greater efficiency. By enabling power policing, you can safely set a lower maximum power allocation for the port because the module will monitor the power consumption of each port and will remove inline power to the port if the configured maximum power setting is exceeded. In this example, you can enable power policing and configure the port for a maximum of 7.5 W. When the Class 3 phone is connected to this port, the supervisor engine will allocate only 7.5 W from the system power rather than 15.4 W, which leaves more power available for other powered devices. The port power consumption will be monitored, and if the phone later draws more than 7.5 W, the supervisor engine will remove inline power to the port and generate a syslog error message.
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 57, 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
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.
15-6
OL-13013-06
Chapter 15
Configuring Cisco IP Phone Support Cisco IP Phone Support Configuration Guidelines and Restrictions
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 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 (see Chapter 59, 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).

These sections describe how to configure Cisco IP phone support:

Configuring Voice Traffic Support, page 15-8 Configuring Data Traffic Support, page 15-9 Configuring Inline Power Support, page 15-10
Note
Voice VLANs are referred to as auxiliary VLANs in the Catalyst software publications.
15-7
Chapter 15 Configuring Cisco IP Phone Support
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
Purpose Selects the port to configure. Configures the LAN port for Layer 2 switching.
Note
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)# switchport voice vlan {voice_vlan_ID | dot1p | none | untagged} Router(config)# end Router# show interfaces fastethernet slot/port switchport Router# show running-config interface fastethernet slot/port
Configures the way in which the Cisco IP phone transmits voice traffic. Exits configuration mode. Verifies the configuration.
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). See Chapter 40, Configuring PFC QoS, for information about how to configure QoS. See the Configuring a LAN Interface as a Layer 2 Access Port section on page 16-16 for information about how to configure the port as a Layer 2 access port and configure the access VLAN.
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
15-8
OL-13013-06
Chapter 15
Configuring Cisco IP Phone Support Configuring Cisco IP Phone Support
This example shows how to verify the configuration of Fast Ethernet port 5/1:
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

Note
The trusted boundary feature is implemented with the mls qos trust extend command. To configure the way in which an attached Cisco IP phone transmits data traffic, perform this task:
Command
Router(config)# interface fastethernet slot/port Router(config-if)# mls qos trust extend [cos cos_value] Router(config)# end Router# show interfaces fastethernet slot/port switchport Router# show running-config interface fastethernet slot/port
Purpose Selects the port to configure. Configures the way in which an attached Cisco IP phone transmits data traffic. Exits configuration mode. Verifies the configuration.
When configuring the way in which an attached Cisco IP phone transmits data traffic, note the following information:
To send CDP packets that configure an attached 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 an attached 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.
15-9
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 Step 3 Step 4 Step 5
1
Purpose
slot/port
Selects an interface to configure. Configures inline power support and optionally specifies a maximum inline power level in milliwatts for the port. Enables inline power policing, if supported.2 Exits configuration mode. Verifies the configuration.
Router(config-if)# power inline {auto | static | never}[max milliwatts] Router(config-if)# [no] power inline police Router(config)# end Router# show power inline {type slot/port | module slot}[detail] 1. 2. type = fastethernet or gigabitethernet
Requires a WS-F6K-48-AF or other inline power daughtercard that supports power monitoring and policing.
When configuring inline power support with the power inline command, note the following information:

To configure auto-detection of an inline-powered device and auto-allocation of port inline power, enter the auto keyword. To configure auto-detection of an inline-powered device but reserve a fixed inline power allocation, enter the static keyword. To specify the maximum power to allocate to a port, enter either the auto or static keyword followed by the max keyword and the power level in milliwatts. When the auto keyword is entered and CDP is enabled on the port, an inline-powered device that supports CDP can negotiate a different power level. To disable auto-detection of an inline-powered device, enter the never keyword. The following information applies to WS-F6K-48-AF and WS-F6K-GE48-AF inline power cards:
15-10
OL-13013-06
Chapter 15
Configuring Cisco IP Phone Support Configuring Cisco IP Phone Support
In Cisco IOS Release 12.2(33)SXH2 and later releases, the configurable range of maximum
power using the max keyword is 4000 to 16800 milliwatts. For earlier releases, the configurable range for maximum power is 4000 to 15400 milliwatts. For all releases, if no maximum power level is configured, the default maximum power is 15400 milliwatts.
Note
To support a large number of inline-powered ports using power levels above 15400 milliwatts on an inline power card, we recommend using the static keyword so that the power budget is deterministic.
In Cisco IOS Release 12.2(33)SXH2 and later releases, when the auto keyword is entered and
CDP is enabled on the port, an inline-powered device that supports CDP can negotiate a power level up to 16800 milliwatts unless a lower maximum power level is configured. For earlier releases, the inline-powered device can negotiate a power level up to 15400 milliwatts or the configured maximum power level, if lower. 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 Router#
This example shows how to verify the inline power configuration on GigabitEthernet port 1/9 when the module includes an inline power daughtercard that supports power monitoring and policing:
Router# show power inline GigabitEthernet 1/9 Interface Admin Oper Power (Watts) Device Class From PS To Device ------------ ---- ------- --------- ------- ----Gi1/9 auto on 17.3 15.4 Ieee PD 3 Interface --------Gi1/9 Router# AdminPowerMax (Watts) Police --------------------- -----15.4 on ActualConsumption ----------------5.7
This example shows how to verify the detailed inline power configuration on GigabitEthernet port 1/9 when the module includes an inline power daughtercard that supports power monitoring and policing:
Router# show power inline GigabitEthernet 1/9 detail Interface: Gi1/9 Inline Power Mode: auto Operational status: on Device Detected: yes Device Type: Cisco IP Phone 7970 IEEE Class: 3
15-11
Discovery mechanism used/configured: Ieee and Cisco Police: on Power Admin Power Power Allocated Value: 15.3 drawn from the source: 11.5 available to the device: 10.2
Actual consumption Measured at the port: 6.3 Maximum Power drawn by the device since powered on: 6.7 Absent Counter: 0 Over Current Counter: 0 Short Current Counter: 0 Invalid Signature Counter: 0 Power Denied Counter: 0 Router#
Tip
15-12
OL-13013-06
PA R T
LAN Switching
C H A P T E R
16
Configuring LAN Ports for Layer 2 Switching

This chapter describes how to use the command-line interface (CLI) to configure Fast Ethernet, Gigabit Ethernet, and 10-Gigabit Ethernet LAN ports for Layer 2 switching in Cisco IOS Release 12.2SX. The configuration tasks in this chapter apply to LAN ports on switching modules and to the LAN ports on the supervisor engine and Cisco ME 6500 Series Ethernet switches.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html To configure Layer 3 interfaces, see Chapter 29, Configuring Layer 3 Interfaces.

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

These sections describe how Layer 2 switching works in Cisco IOS Release 12.2SX:

Understanding Layer 2 Ethernet Switching, page 16-1 Understanding VLAN Trunks, page 16-3 Layer 2 LAN Port Modes, page 16-4
Understanding Layer 2 Ethernet Switching

These sections describe Layer 2 Ethernet switching:

Layer 2 Ethernet Switching Overview, page 16-2 Switching Frames Between Segments, page 16-2 Building the Address Table, page 16-2
16-1
Chapter 16 Understanding Layer 2 Switching
Layer 2 Ethernet Switching Overview

Layer 2 Ethernet ports on Cisco 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. Cisco switches that support Layer 2 Ethernet ports 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 Layer 2 Ethernet port 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

The address table is built 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.
Synchronization and Sharing of the Address Table

With distributed switching, each DFC-equipped switching module learns MAC addresses, maintains an address table, and ages table entries. By enabling MAC address table synchronization over the Ethernet Out of Band Channel (EOBC), you can configure the switch to allow sharing and synchronization of the address tables among all DFCs and supervisor engines in the switch, eliminating the need for flooding
16-2
OL-13013-06
Chapter 16
Configuring LAN Ports for Layer 2 Switching Understanding Layer 2 Switching
by a DFC for an address that is active on another DFC. When a WS-6708-10G switching module is present in the system, MAC synchronization is automatically enabled. Otherwise, MAC synchronization must be enabled manually by entering the mac-address-table synchronize command.
Notification of Address Table Changes

You can configure the switch to maintain a history of dynamic additions and removals of address table entries associated with a particular LAN port. The change history can be sent as an SNMP trap notification or it can be read manually from the SNMP MIB.
Understanding VLAN Trunks

These sections describe VLAN trunks in Cisco IOS Release 12.2SX:

Trunking Overview, page 16-3 Encapsulation Types, page 16-4
Trunking Overview
Note
For information about VLANs, see Chapter 22, 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.
Note
The following switching modules do not support ISL encapsulation: 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 18, Configuring EtherChannels. Ethernet trunk ports support several trunking modes (see Table 16-2 on page 16-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. 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 21, Configuring VTP.
16-3
Encapsulation Types
Table 16-1 lists the Ethernet trunk encapsulation types.
Table 16-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 16-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 16-2 lists the Layer 2 LAN port modes and describes how they function on LAN ports.
Table 16-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
16-4
OL-13013-06
Chapter 16
Configuring LAN Ports for Layer 2 Switching Default Layer 2 LAN Interface Configuration
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.
Default Layer 2 LAN Interface Configuration

Table 16-3 shows the Layer 2 LAN port default configuration.
Table 16-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 22-1 on page 22-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:

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
16-5
Chapter 16 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 (the Mono
Spanning Tree, or MST) 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 in Cisco IOS Release 12.2SX:

Configuring a LAN Port for Layer 2 Switching, page 16-7 Enabling Out-of-Band MAC Address Table Synchronization, page 16-8 Configuring MAC Address Table Notification, page 16-8 Configuring a Layer 2 Switching Port as a Trunk, page 16-10 Configuring a LAN Interface as a Layer 2 Access Port, page 16-16 Configuring an IEEE 802.1Q Custom EtherType Field Value, page 16-18
16-6
OL-13013-06
Chapter 16
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
Router(config-if)# no shutdown
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.
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. type = fastethernet, gigabitethernet, or tengigabitethernet
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.
16-7
Enabling Out-of-Band MAC Address Table Synchronization

With Release 12.2(33)SXF and later releases, to enable the out-of-band MAC address table synchronization feature, perform this task: Command
Step 1
Router(config)# [no] mac-address-table synchronize [activity-time seconds]
Purpose Enables out-of-band synchronization of MAC address tables among DFC-equipped switching modules.
activity-time seconds(Optional) Specifies the activity timer interval.
Step 2
Router# show mac-address-table synchronize statistics
Displays MAC address table synchronization statistics.
When configuring out-of-band MAC address table synchronization, note the following information:

By default, out-of-band MAC address table synchronization is disabled. Out-of-band MAC address table synchronization is enabled automatically if any of the following conditions are met:
A WS-6708-10G switching module is installed in the switch. The switch is part of a virtual switch system (VSS) running Cisco IOS Release 12.2(33)SXI4
or a later release.
The activity timer interval can be configured as 160, 320, and 640 seconds. The default is 160 seconds.
This example shows how to enable out-of-band MAC address table synchronization:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mac-address-table synchronize activity-time 320
Configuring MAC Address Table Notification

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 16-7 before performing the tasks in this section. To send SNMP trap notifications using this feature, you must also enable the global MAC trap flag, using the snmp-server enable mac-notification change command.
16-8
OL-13013-06
Chapter 16
With Release 12.2(33)SXH and later releases, to configure the MAC address table notification feature, perform this task: Command
Step 1
Router(config)# mac-address-table notification change [interval value] [history size]
Purpose Enables sending notification of dynamic changes to MAC address table. (Optional) Sets the minimum change-sending interval in seconds. (Optional) Sets the number of entries in the history buffer.
Note
The no form of the command reverts to the default without sending any change information.
Step 2 Step 3
Router(config)# interface type1 slot/port Router(config-if)# snmp trap mac-notification change [added | removed]
Selects the LAN port to configure. For MAC addresses that are associated with this LAN port, enable SNMP trap notification when MAC addresses are added to or removed from the address table. (Optional) To notify only when a MAC address is added to the table, use the added option. To notify only when a MAC address is removed, use the removed option.
Step 4 Step 5
Router(config-if)# end Router# show mac-address-table notification
Exits interface configuration mode. Displays whether this feature is enabled, the notification interval, and the history table maximum size. Displays history table contents. Displays the interface-specific flags for the specified interface. If slot and port are not specified, the flags for all interfaces will be displayed.
Step 6
Router# show mac-address-table notification [type slot/port]
1.
When configuring the notification parameters, note the following information:

The interval value parameter can be configured from 0 seconds (immediate) to 2,147,483,647 seconds. The default is 1 second. The history size parameter can be configured from 0 entries to 500 entries. The default is 1 entry.
This example shows how to configure the SNMP notification of dynamic additions to the MAC address table of addresses on the Fast Ethernet ports 5/7 and 5/8. Notifications of changes will be sent no more frequently than 5 seconds, and up to 25 changes can be stored and sent in that interval:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# mac-address-table notification change interval 5 history 25 Router(config)# interface fastethernet 5/7 Router(config-if)# snmp trap mac-notification change added Router(config-if)# end Router(config)# interface fastethernet 5/8 Router(config-if)# snmp trap mac-notification change added Router(config-if)# end Router# exit
16-9
Configuring a Layer 2 Switching Port as a Trunk

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

Configuring the Layer 2 Switching Port as an ISL or 802.1Q Trunk, page 16-10 Configuring the Layer 2 Trunk to Use DTP, page 16-11 Configuring the Layer 2 Trunk Not to Use DTP, page 16-11 Configuring the Access VLAN, page 16-12 Configuring the 802.1Q Native VLAN, page 16-13 Configuring the List of VLANs Allowed on a Trunk, page 16-13 Configuring the List of Prune-Eligible VLANs, page 16-14 Completing Trunk Configuration, page 16-15 Verifying Layer 2 Trunk Configuration, page 16-15 Configuration and Verification Examples, page 16-15
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 16-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}
Purpose (Optional) Configures the encapsulation, which configures the Layer 2 switching port as either an ISL or 802.1Q trunk.
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 16-11) 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:
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
16-10
OL-13013-06
Chapter 16
Note
Complete the steps in the Completing Trunk Configuration section on page 16-15 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 16-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}
Purpose (Optional) Configures the trunk to use DTP.

Note
The no form of the command 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 16-2 on page 16-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 16-7 before performing the tasks in this section. To configure the Layer 2 trunk not to use DTP, perform this task:
Command
Step 1 Step 2
Router(config-if)# switchport mode trunk Router(config-if)# switchport nonegotiate
Purpose (Optional) Configures the port to trunk unconditionally. (Optional) Configures the trunk not to use DTP.
Note
The no form of the command enables DTP on the port.
16-11
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 16-10). To support the switchport nonegotiate command, you must enter the switchport mode trunk command. Enter the switchport mode dynamic trunk command. See Table 16-2 on page 16-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 16-10) 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 16-11).
Note
Configuring the Access VLAN

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 16-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 22-1 on page 22-2).
Note
If VLAN locking is enabled, enter the VLAN name instead of the VLAN number. For more information, see the VLAN Locking section on page 22-4. The no form of the command reverts to the default VLAN (VLAN 1).
Note
16-12
OL-13013-06
Chapter 16
Configuring the 802.1Q Native VLAN

Note
Complete the steps in the Configuring a LAN Port for Layer 2 Switching section on page 16-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
Purpose (Optional) Configures the 802.1Q native VLAN.

Note
If VLAN locking is enabled, enter the VLAN name instead of the VLAN number. For more information, see the VLAN Locking section on page 22-4.
When configuring the native VLAN, note the following information:

The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 22-1 on page 22-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 16-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[,...]]
Purpose (Optional) Configures the list of VLANs allowed on the trunk.

Note
If VLAN locking is enabled, enter VLAN names instead of VLAN numbers. For more information, see the VLAN Locking section on page 22-4. The no form of the command reverts to the default value (all VLANs allowed).
16-13
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. If VLAN locking is enabled, enter VLAN names instead of VLAN numbers. When entering a range of VLAN names, you must leave spaces between the VLAN names and the dash. 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 16-7 before performing the tasks in this section. 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[,...]]}}
Purpose (Optional) Configures the list of prune-eligible VLANs on the trunk (see the Understanding VTP Pruning section on page 21-6).
Note
The no form of the command 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 22-1 on page 22-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 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
16-14
OL-13013-06
Chapter 16
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. type = fastethernet, gigabitethernet, or tengigabitethernet
1
Purpose Displays the running configuration of the interface. Displays the switch port configuration of the interface. Displays the trunk configuration of the interface.
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
16-15
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#
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 22-5). 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
Step 4 Step 5
Router(config-if)# switchport mode access Router(config-if)# switchport access vlan vlan_ID
Configures the LAN port as a Layer 2 access port. Places the LAN port in a VLAN. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 22-1 on page 22-2).
Note
16-16
OL-13013-06
Chapter 16
Command
Purpose 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.
Router(config-if)# end Router# show running-config interface [type1 slot/port] Router# show interfaces [type1 slot/port] switchport 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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

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#
16-17
Configuring an IEEE 802.1Q Custom EtherType Field Value

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
Purpose Configures the 802.1Q EtherType field value for the port.
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.
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.2SX 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)#
16-18
OL-13013-06
C H A P T E R
17

This chapter describes how to configure Flex Links in Cisco IOS Release 12.2SX.
Note
Tip
The chapter consists of these sections:

Understanding Flex Links, page 17-1 Configuring Flex Links, page 17-2 Monitoring Flex Links, page 17-4
Understanding Flex Links

Flex Links are a pair of a Layer 2 interfaces (ports 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. In Figure 17-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
17-1
Chapter 17 Configuring Flex Links
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 17-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 17-2 Flex Links Configuration Guidelines and Restrictions, page 17-2 Configuring Flex Links, page 17-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. 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.
17-2
OL-13013-06
Chapter 17
Configuring Flex Links Configuring Flex Links
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
Flex Links and port security are not compatible with each other.

To configure Flex Links, perform this task: Command
Router# configure terminal Router(conf)# interface {{type {port-channel number}}
1

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.
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 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
17-3
Chapter 17 Monitoring Flex Links
Monitoring Flex Links

To monitor the Flex Links configuration, perform this task: 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
17-4
OL-13013-06
C H A P T E R
18
This chapter describes how to configure EtherChannels on Layer 2 or Layer 3 LAN ports in Cisco IOS Release 12.2SX.
Note
Tip

Understanding EtherChannels, page 18-1 EtherChannel Feature Configuration Guidelines and Restrictions, page 18-6 Configuring EtherChannels, page 18-7
Understanding EtherChannels
These sections describe how EtherChannels work:

EtherChannel Feature Overview, page 18-2 Understanding EtherChannel Configuration, page 18-2 Understanding Port Channel Interfaces, page 18-5 Understanding LACP 1:1 Redundancy, page 18-5 Understanding Load Balancing, page 18-5
18-1
Chapter 18 Understanding EtherChannels
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. Cisco IOS Release 12.2SX supports a maximum of 128 EtherChannels. You can form an EtherChannel with up to eight compatibly configured LAN ports on any switching module. 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 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 EtherChannel Configuration

These sections describe how EtherChannels are configured:

EtherChannel Configuration Overview, page 18-2 Understanding Manual EtherChannel Configuration, page 18-3 Understanding PAgP EtherChannel Configuration, page 18-3 Understanding IEEE 802.3ad LACP EtherChannel Configuration, page 18-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 18-1 lists the user-configurable EtherChannel modes.
18-2
OL-13013-06
Chapter 18
Configuring EtherChannels Understanding EtherChannels
Table 18-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.
18-3
Chapter 18 Understanding EtherChannels
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 18-11). 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 18-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 auto interleaved port priorityYou can configure LACP auto interleaved port priority to create an effective distribution of bundled and hot standby ports across different slots that are part of the same port channel, either Distributed EtherChannel (DEC) or Multichassis EtherChannel (MEC). To configure auto interleaved port priority use the lacp active-port distribution automatic command. The bundled port distribution can be configured through the CLI (see the Configuring Channel Groups section on page 18-8). Once the auto interleaved port priority feature is enabled, it automatically distributes bundled ports based on the position of when a port link comes up and is effective only if you configure it on the system that has the higher LACP system priority. You need to perform a shutdown and no shutdown on the interface port channel to enable the auto interleaved port priority feature on all ports. 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
18-4
OL-13013-06
Chapter 18
Configuring EtherChannels Understanding EtherChannels
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).
Understanding LACP 1:1 Redundancy

With Release 12.2(33)SXH and later releases, the LACP 1:1 redundancy feature provides an EtherChannel configuration with one active link and fast switchover to a hot standby link. To use LACP 1:1 redundancy, you configure an LACP EtherChannel with two ports (one active and one standby). If the active link goes down, the EtherChannel stays up and the system performs fast switchover to the hot standby link. When the failed link becomes operational again, the EtherChannel performs another fast switchover to revert to the original active link. For the LACP 1:1 redundancy feature to work correctly, especially the fast switchover capability, the feature needs to be enabled at both ends of the link.
Understanding Port Channel Interfaces

Each EtherChannel has a numbered port channel interface. You can configure a maximum of 128 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 information in the frame header to a numerical value that selects one of the links in the channel. You can configure which header information will be used to derive the numerical value for link selection. The EtherChannel load balancing method can use MAC addresses, IP addresses, or Layer 4 port numbers, and you can configure whether the information will be from the 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 also use MPLS Layer 2 information. If PFC3C/CXL hardware is installed, EtherChannel load balancing will additionally consider VLAN information by default. 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.
18-5
Chapter 18 EtherChannel Feature Configuration Guidelines and Restrictions
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 Layer 2 Ethernet ports, including the ports on the supervisor engine and a redundant supervisor engine. The WS-X6148-GE-TX and WS-X6148V-GE-TX switching modules do not support more than 1 Gbps of traffic per EtherChannel. 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 Layer 2 Ethernet 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. Enable all 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.
18-6
OL-13013-06
Chapter 18
Configuring EtherChannels Configuring EtherChannels
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 different queue structures, for example, 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. 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 18-7 Configuring Channel Groups, page 18-8 Configuring EtherChannel Load Balancing, page 18-11 Configuring EtherChannel Hash-Distribution Algorithm, page 18-12 Configuring the EtherChannel Min-Links Feature, page 18-13 Configuring LACP 1:1 Redundancy, page 18-14 Configuring Auto Interleaved Port Priority For LACP Port Channels, page 18-15
Note
Make sure that the LAN ports are configured correctly (see the EtherChannel Feature Configuration Guidelines and Restrictions section on page 18-6).
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 18-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 18-8).
18-7
Chapter 18 Configuring EtherChannels
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
Router(config)# interface port-channel group_number Router(config-if)# ip address ip_address mask
Purpose Creates the port channel interface. Assigns an IP address and subnet mask to the EtherChannel. Exits configuration mode. Verifies the configuration.
Router(config-if)# end Router# show running-config interface port-channel group_number
The group_number can be 1 through 256, up to a maximum of 128 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 18-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.
18-8
OL-13013-06
Chapter 18
To configure channel groups, perform this task for each LAN port: Command
Router(config)# interface type1 slot/port Router(config-if)# no ip address
Purpose 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. Configures the LAN port in a port channel and specifies the mode (see Table 18-1 on page 18-3). PAgP supports only the auto and desirable modes. LACP supports only the active and passive modes. (Optional for LACP) Valid values are 1 through 65535. Higher numbers have lower priority. The default is 32768. Disables the interface. Enables the interface. Exits configuration mode. Verifies the configuration.
Router(config-if)# channel-protocol (lacp | pagp}
Step 4
Router(config-if)# channel-group group_number mode {active | auto | desirable | on | passive}
Step 5
Router(config-if)# lacp port-priority priority_value
Router(config-if)# shutdown Router(config-if)# no shutdown Router(config-if)# end Router# show running-config interface type1 slot/port Router# show interfaces type1 slot/port etherchannel 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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)# shutdown Router(config-if)# no shutdown 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#
18-9
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 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#
18-10
OL-13013-06
Chapter 18
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
Purpose (Optional for LACP) Valid values are 1 through 65535. Higher numbers have lower priority. The default is 32768. 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 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 Step 2
Router(config)# port-channel per-module load-balance 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} [module slot] Router(config)# no port-channel load-balance
Purpose (Optional) Enables the ability to specify the load-balancing method on a per-module basis. Configures the EtherChannel load-balancing method. The method is globally applied to all port channels. Optionally, you can configure the load-balancing method for a specific module. The default method is src-dst-ip. Reverts to default EtherChannel load balancing. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config)# end Router# show etherchannel load-balance
The load-balancing method keywords indicate the following information:

dst-ipDestination IP addresses dst-macDestination MAC addresses dst-portDestination Layer 4 port
18-11
mplsLoad balancing for MPLS packets src-dst-ip(Default) Source 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
The optional module keyword allows you to specify the load-balancing method for a specific module. This capability is supported only on DFC-equipped switching modules. You must enable per-module load balancing globally before configuring the feature on a module. 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 EtherChannel Load-Balancing Configuration: src-dst-ip enhanced mpls label-ip EtherChannel Load-Balancing Addresses Used Per-Protocol: Non-IP: Source XOR Destination MAC address IPv4: Source XOR Destination IP address IPv6: Source XOR Destination IP address MPLS: Label or IP Router#
Note
In this example, the enhanced keyword indicates that PFC3C/CXL hardware is installed and, as a result, VLAN information will also be included in the load-balancing method.
Configuring EtherChannel Hash-Distribution Algorithm

Releases earlier than 12.2(33)SXH support a load-distribution algorithm called the fixed algorithm. When you add a port to the EtherChannel or delete a port from the EtherChannel, the switch updates the port ASIC for each port in the EtherChannel, which causes a short outage on each port. Release 12.2(33)SXH and later releases support an additional algorithm called the adaptive algorithm. The adaptive algorithm does not need to update the port ASIC for existing member ports. The fixed algorithm is the default algorithm. You can configure a global value for the adaptive algorithm. You can also specify the algorithm for individual port channels. When you change the algorithm, the change is applied at the next member link event (link down, link up, addition, deletion, no shutdown, and shutdown). When you enter the command to change the algorithm, the command console issues a warning that the command does not take effect until the next member link event.
18-12
OL-13013-06
Chapter 18
Note
Some external devices require the fixed algorithm. For example, the service control engine (SCE) requires incoming and outgoing packets to use the same port.
Note
If you change the load-balancing method, EtherChannel ports on DFC-equipped switching modules or on an active supervisor engine in a dual supervisor engine configuration will flap.
Configuring the Hash-Distribution Algorithm Globally

To configure the load-sharing algorithm globally, perform this task: Command
Step 1 Step 2
Router(config)# port-channel hash-distribution {adaptive | fixed} Router(config)# end
Purpose Sets the hash distribution algorithm to adaptive or fixed. Exits configuration mode.
This example shows how to globally set the hash distribution to adaptive:
Router(config)# port-channel hash-distribution adaptive
Configuring the Hash-Distribution Algorithm for a Port Channel

To configure the hash-distribution algorithm for a specific port channel, perform this task: Command
Router(config)# interface port-channel channel-num Router(config-if)# port-channel port hash-distribution {adaptive | fixed} Router(config-if)# end
Purpose Enters interface configuration mode for the port channel. Sets the hash distribution algorithm for this interface Exits interface configuration mode.
This example shows how to set the hash distribution algorithm to adaptive on port channel 10:
Router (config)# interface port-channel 10 Router (config-if)# port-channel port hash-distribution adaptive
Configuring 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. In addition, when LACP max-bundle values are specified in conjunction with min-links, the configuration is verified and an error message is returned if the min-links value is not compatible with (equal to or less than) the max-bundle value.
18-13
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. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show running-config interface port-channel group_number Router# show interfaces type1 slot/port etherchannel 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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 two 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
Configuring LACP 1:1 Redundancy

For the LACP 1:1 redundancy feature, the LACP EtherChannel must contain exactly two links, of which only one is active. The link with the lower port priority number (and therefore a higher priority) will be the active link, and the other link will be in a hot standby state. The LACP max-bundle must be set to 1. To configure the LACP 1:1 redundancy feature, perform this task: Command
Router(config)# interface port-channel group_number Router(config-if)# lacp fast-switchover
Purpose Selects an LACP port channel interface. Enables the fast switchover feature for this EtherChannel. Sets the maximum number of active member ports to be one. Exits configuration mode. Verifies the configuration.
Router(config-if)# lacp max-bundle 1
Router(config-if)# end Router# show running-config interface port-channel group_number Router# show interfaces type1 slot/port etherchannel 1. type = fastethernet, gigabitethernet, or tengigabitethernet
18-14
OL-13013-06
Chapter 18
Note
For the LACP 1:1 redundancy feature to work correctly, especially the fast switchover capability, the feature needs to be enabled at both ends of the EtherChannel. This example shows how to configure an LACP EtherChannel with 1:1 redundancy. Because Fast Ethernet port 5/6 is configured with a higher port priority number (and therefore a lower priority) than the default of 32768, it will be the standby port.
Router# configure terminal Router(config)# lacp system-priority 33000 Router(config)# interface range fastethernet 5/6 -7 Router(config-if)# channel-protocol lacp Router(config-if)# channel-group 1 mode active Router(config)# interface fastethernet 5/6 Router(config-if)# lacp port-priority 33000 Router(config)# interface port-channel 1 Router(config-if)# lacp fast-switchover Router(config-if)# lacp max-bundle 1 Router(config-if)# end
Tip
Configuring Auto Interleaved Port Priority For LACP Port Channels

To configure auto interleaved port priority for LACP on a port channel, perform this task on the port channel interface: Command
Step 1 Step 2
Router(config)# interface port-channel channel-group Router(config-if)# lacp active-port distribution automatic
Purpose Selects a port channel interface to configure. Configures the port channel to use interleaved port priority.
Note
You need to perform a shutdown and no shutdown for interleaved port priority to be enabled.
Router(config-if)# shutdown Router(config-if)# no shutdown Router(config-if)# end Router# show etherchannel channel-group port-channel Router# show etherchannel channel-group summary
Disables the interface. Enables the interface. Exits configuration mode. Verifies the configuration.
18-15
This example shows how to configure auto interleaved port priority on a port channel:
Router(config)# interface port-channel23 Router(config-if)# lacp active-port distribution automatic Please shut/no shut the port-channel for configuration to take effect immediately. Router(config-if)# shutdown Router(config-if)# no shutdown Router(config-if)# end
This example shows how to verify the configuration of port channel interface 23:
Router# show running interfaces port-channel23 Building configuration... Current configuration : 81 bytes ! interface Port-channel23 no switchport no ip address lacp max-bundle 4 lacp active-port distribution automatic end
This example shows how to verify the configuration of EtherChannel 23:

Router# show etherchannel 23 summary Flags: D I H R U f M m u d down P - bundled in port-channel stand-alone s - suspended Hot-standby (LACP only) Layer3 S - Layer2 in use N - not in use, no aggregation failed to allocate aggregator not in use, no aggregation due to minimum links not met not in use, port not aggregated due to minimum links not met unsuitable for bundling default port
w - waiting to be aggregated Number of channel-groups in use: 9 Number of aggregators: 9 Group Port-channel Protocol Ports ------+-------------+-----------+--------------------------------------23 Po23(RU) LACP Gi1/1/21(P) Gi1/1/22(P) Gi1/1/23(H) Gi1/1/24(H) Gi2/1/17(P) Gi2/1/18(P) Gi2/1/19(H) Gi2/1/20(H) Last applied Hash Distribution Algorithm: Fixed
Note
The above example shows that the four bundled ports are distributed 2 per chassis/slot.
18-16
OL-13013-06
CH A P T E R
19

This chapter describes how to configure the multichassis LACP (mLACP) for server access feature. Release 12.2(33)SXJ and later releases support the mLACP for server access feature. This chapter includes these sections:

Understanding mLACP for Server Access, page 19-1 mLACP for Server Access Guidelines and Restrictions, page 19-9 Configuring mLACP for Server Access, page 19-10
Note
For information about Etherchannels, see Chapter 18, Configuring EtherChannels. For information about the IEEE 802.3ad link aggregation control protocol (LACP), see the Understanding IEEE 802.3ad LACP EtherChannel Configuration section on page 18-4.
Understanding mLACP for Server Access

These sections describe mLACP for server access:

Overview of mLACP for Server Access, page 19-2 Understanding mLACP Operation, page 19-2 Failure Protection Scenarios, page 19-6 mLACP Failover, page 19-6
19-1
Chapter 19 Understanding mLACP for Server Access
Overview of mLACP for Server Access

The mLACP for server access feature supports single redundant Layer 2 LACP links from a pair of Catalyst 6500 switches to a server. Figure 19-1 illustrates switches connected to a server.
Figure 19-1 mLACP for Server Access Topology
Network Point of Attachment (PoA) Catalyst 6500 Switch A Backbone Interfaces

Interchassis Communication Channel (ICC) Dual-Link Layer 2 mLACP EtherChannel
Point of Attachment (PoA) Catalyst 6500 Switch B
Active Link
Dual-Link LACP EtherChannel
Standby Link
237465
Dual Homed Device (DHD) Server
In the mLACP for server access topology, the server is a dual-homed device connected through two Layer 2 links. On the server, the links attach to ports that are configured as members of a Layer 2 LACP EtherChannel. The links function in active-standby redundancy mode, with only one link active at any time, which prevents Layer 2 loops and imposes no Spanning Tree Protocol (STP) requirements. Each link connects to a switch that functions as a point-of-attachment (PoA). On the switches, the links attach to ports that are configured as members of a Layer 2 Multichassis EtherChannel (MCEC). An MCEC uses the Interchassis Communication Protocol (ICCP) over the interchassis communication channel (ICC) to synchronize states between the PoAs.
Note
A switch configured as a PoA cannot form mLACP peer relationships with more than one other switch. The switch-to-server connection is a connection between an mLACP port-channel interface on the PoAs and an LACP port-channel interface on the server.
Understanding mLACP Operation

These sections describe mLACP operation:

mLACP for Server Access Feature Components, page 19-3 mLACP System ID, page 19-5 mLACP Port Identifier, page 19-5 Port-Channel ID, page 19-5
19-2
OL-13013-06
Chapter 19
Configuring mLACP for Server Access Understanding mLACP for Server Access
mLACP for Server Access Feature Components

This table describes the feature components that must be configured compatibly on the PoAs. Active PoA (Switch A)
Component:
Standby PoA (Switch B)
Interchassis communication channel (ICC)

Definition:
A link that connects the PoAs to carry only ICCP traffic.

Note:
The ICC supports only Interchassis Communication Protocol (ICCP) traffic. On switch A, the ip address interface command configures an On switch B, the ip address interface command configures an IP address on the switch A end of the ICC link. IP address on the switch B end of the ICC link.
Component:
mLACP Redundancy Group

Definition:
Two PoAs that form a virtual LACP peer.

Note:

One mLACP redundancy group can support multiple mLACP port-channel interfaces. An mLACP redundancy group has the same mLACP interchassis group ID on both PoAs. The mLACP interchassis group ID configured on port-channel interfaces configures them as members of the mLACP redundancy group. On switch B, the member ip redundancy group command points to the ICC-link IP address on switch A. On switch B, the mlacp system-priority redundancy group command configures the switch B mLACP system priority value used on this PoA in this redundancy group as part of the mLACP system ID value. On switch B, the mlacp system-mac redundancy group command configures the switch B mLACP system priority value used on this PoA in this redundancy group as part of the mLACP system ID value. On switch B, the mlacp node-id redundancy group command configures the switch B mLACP port number value used on this PoA in this redundancy group as part of the mLACP port identifier value. On switch B, the backbone interface redundancy group command configures mLACP link-status monitoring on the switch B physical ports that carry server traffic to and from the network.
On switch A, the member ip redundancy group command points to the ICC-link IP address on switch B. On switch A, the mlacp system-priority redundancy group command configures the switch A mLACP system priority value used on this PoA in this redundancy group as part of the mLACP system ID value. On switch A, the mlacp system-mac redundancy group command configures the switch A mLACP system priority value used on this PoA in this redundancy group as part of the mLACP system ID value. On switch A, the mlacp node-id redundancy group command configures the switch A mLACP port number value used on this PoA in this redundancy group as part of the mLACP port identifier value. On switch A, the backbone interface redundancy group command configures mLACP link-status monitoring on the switch A physical ports that carry server traffic to and from the network.
19-3
Active PoA (Switch A)

Component:
Port-channel interfaces
Definition:
Port-channel interface commands that configure DHD connection links.

Note:

Each port-channel interface supports one Layer 2 link to a server. Port-channel interfaces must be configured with matching interface port-channel port-channel interface command ID values on both PoAs. Use the mLACP interchassis group ID as the mlacp interchassis group port-channel interface command ID value on both PoAs. On switch B, the mlacp lag-priority port-channel interface command configures the switch B mLACP port priority value used on this PoA in this redundancy group as part of the mLACP port identifier value.
On switch A, the mlacp lag-priority port-channel interface command configures the switch A mLACP port priority value used on this PoA in this redundancy group as part of the mLACP port identifier value.
Component:
Port interfaces
Definition:
Interface commands that configure Layer 2 DHD connection links as members of the mLACP port-channel interfaces.
Note:
The channel-group interface command configured with the mLACP port-channel ID value makes the port a member of an mLACP port-channel interface.
19-4
OL-13013-06
Chapter 19
mLACP System ID
In each mLACP redundancy group, the PoA with the lowest mLACP system ID value is the link selection PoA. The link selection PoA controls selection of the link that will be active. Comparisons of mLACP system IDs are numeric comparisons of the unsigned integer values of the mLACP system ID values. mLACP uses the two-byte mLACP system priority value as the most significant two octets and the configured mLACP system MAC address value as the least significant octets of the 8-byte mLACP system ID value.
Note
The mLACP for server access feature does not support DHD control of active link selection. Configure the LACP instance on the DHD to have a numerically higher LACP system ID value than the PoA mLACP system ID values.
mLACP System Priority
The mlacp system-priority redundancy group command sets the mLACP system priority value. A lower value contributes to selection of the PoA as the link selection PoA.
mLACP System MAC Address
The mlacp system-mac redundancy group command sets the mLACP system MAC address. A lower value contributes to selection of the PoA as the link selection PoA.
Note
The mLACP system MAC value is only used in the LACP PDUs sent between the PoAs and DHD.
mLACP Port Identifier

In each redundancy group, for each port-channel interface in the redundancy group, the link selection PoA selects the link with the lowest mLACP port identifier value to be active. Comparisons of mLACP port identifiers are numeric comparisons of the unsigned integer values of the mLACP port identifier values. mLACP uses the two-byte mLACP port priority value as the most significant two octets and the configured mLACP port number as the least significant two octets of the four-byte mLACP port identifier value.
mLACP Port Priority
The mlacp lag-priority port-channel interface command configures the mLACP port priority value. A lower value contributes to selection of a link to be active.
mLACP Port Number
The mlacp node-id redundancy group command configures the mLACP port number. A lower value contributes to selection of a link to be active.
Port-Channel ID
You create the port-channel ID with the port-channel id_number command and associate physical ports to it with the channel-group id_number interface configuration mode command. The port-channel ID on the two PoAs in an mLACP redundancy group must match. The port-channel ID on the DHD can be different from the value configured on the PoAs.
19-5
Failure Protection Scenarios

The mLACP for server access feature provides network resiliency by protecting against port, link, and PoA failures. These failures can be categorized into five types. Figure 19-2 shows the failure points in a network, denoted by the letters A through E.

AFailure of the port on the server BFailure of the server-connection link CFailure of the server-connection port on the active PoA DFailure of the active PoA EFailure of the backbone interfaces
mLACP for Server Access Protected Failure Points
Figure 19-2
Network
Point of Attachment (PoA)

D
Backbone Interfaces
Interchassis Communication Channel (ICC)
Point of Attachment (PoA)
Active Link
Standby Link Dual Homed Device (DHD)
Server
When any of these faults occur, mLACP triggers a switchover from the active PoA to the standby PoA.
mLACP Failover
These sections describe mLACP failover:

Overview, page 19-7 Dynamic Port Priority, page 19-7 Revertive and Nonrevertive Modes, page 19-7 Peer Monitoring with Interchassis Redundancy Manager, page 19-7
19-6
237490
OL-13013-06
Chapter 19
Overview
mLACP forces failover in these situations:
If the active PoA loses communication with the server (failure points A, B, or C) or if all backbone interfaces on the active PoA fail (failure point E), mLACP fails over to the link on the standby PoA. (PoA failover does not occur.) If ICRM notifies the standby PoA that the active PoA has failed, the standby PoA becomes active.
Note
The DHD does not participate in failover determination.
Dynamic Port Priority

The default failover method uses dynamic port priority changes on the local member links to force the LACP selection logic to move the required standby link to the SELECTED and Collecting_Distributing state. This state change occurs when the LACP actor port priority values for all affected member links on the currently active PoA are changed to a higher numeric value than the standby PoAs port priority (which gives the standby PoA ports a higher claim to bundle links). Changing the actor port priority triggers the transmission of an mLACP Port Config Type-Length-Value (TLV) message to all peers in the redundancy group. These messages also serve as notification to the standby PoA that the currently active PoA is attempting to relinquish its role. The LACP then transitions the standby link to the SELECTED state and moves all the currently active links to STANDBY. Dynamic port priority changes are not automatically written back to the running configuration or to the NVRAM configuration. If you want the system to use the current priorities when the it reloads, configure the mlacp lag-priority command and save the configuration.
Revertive and Nonrevertive Modes

The mLACP feature uses the dynamic port priority functionality for both revertive mode and nonrevertive mode. The default operation is revertive, which is the default in single chassis LACP. Nonrevertive mode can be enabled on a per port-channel basis by using the lacp failover non-revertive command in interface configuration mode, which is supported only for mLACP. Nonrevertive mode limits failover and possible traffic loss. Dynamic port priority changes are utilized to ensure that the newly activated PoA remains active after the failed PoA recovers. Revertive mode operation forces the configured primary PoA to return to active state after it recovers from a failure. Dynamic port priority changes are uses when necessary to allow the recovering PoA to resume its active role.
Peer Monitoring with Interchassis Redundancy Manager

The interchassis redundancy manager (ICRM) can monitor a peer with these methods:

Routewatch (RW)This method is the default. Bidirectional Forwarding Detection (BFD)You must configure the redundancy group with the monitor peer bfd command.
19-7
Note
For stateful switchover (SSO) deployments with redundant supervisor engines, configure BFD monitoring and a static route for the ICCP connection to prevent both PoAs from being active after an SSO failover. Routewatch does not support SSO. There is a monitoring adjacency for each peer (designated by a member IP address) in each redundancy group. If there are two peers with the same IP address, the adjacency is shared regardless of the monitoring mode. For example, if redundancy groups 1 and 2 have a peer relationship with member IP address 10.10.10.10, there is only one adjacency to 10.10.10.10, which is shared in both redundancy groups. Redundancy groups can use different monitoring methods.
Note
BFD is completely dependent on routewatch; there must be a route to the peer for ICRM to initiate BFD monitoring. BFD implies routewatch. Sometimes the status of the adjacency might seem misleading but is accurately representing the state. Also, if the route to the peer PoA is not through the directly connected (back-to-back) link between the systems, BFD can give misleading results. This is an example of output from the show redundancy interface command:
Router# show redundancy interface Redundancy Group 1 (0x1) Applications connected: mLACP Monitor mode: Route-watch member ip: 201.0.0.1 mlacp-201, CONNECTED Route-watch for 201.0.0.1 is UP mLACP state: CONNECTED ICRM fast-failure detection neighbor table IP Address Status Type Next-hop IP ========== ====== ==== =========== 201.0.0.1 UP RW
Interface =========
Table 19-1 explains the adjacency status displayed by the show redundancy interchassis command.
Table 19-1 Status Information from the show redundancy interchassis command
Adjacency Type RW RW
Adjacency Status DOWN UP
Meaning Routewatch or BFD is configured, but there is no route for the given IP address. Routewatch or BFD is configured. Routewatch is up, which indicates that there is a valid route to the peer. If BFD is configured and the adjacency status is UP, BFD is probably not configured on the interface of the routes adjacency. BFD is configured. A route exists and the routes adjacency is to an interface that has BFD enabled. BFD is started but the peer is down. The DOWN status can be because the peer is not present or BFD is not configured on the peers interface. BFD is configured and operational.
BFD
DOWN
BFD
Note
UP
If the adjacency type is BFD, routewatch is UP regardless of the BFD status.
19-8
OL-13013-06
Chapter 19
Configuring mLACP for Server Access mLACP for Server Access Guidelines and Restrictions
mLACP for Server Access Guidelines and Restrictions

When configuring mLACP for Server Access, follow these guidelines and restrictions:

PFC3A mode does not support the mLACP for server access feature. VSS mode does not support the mLACP for server access feature. No more than 100 VLANs can be active on a switch configured as a PoA. Switches configured with the mLACP for server access feature cannot support the Wireless Services Module (WiSM; WS-SVC-WISM-1-K9) or Wireless Services Module 2 (WiSM2; WS-SVC-WISM2-K9). Do not install WiSM modules in switches configured with the mLACP for server access feature. Do not configure the mLACP for server access feature in switches where any WiSM modules are installed. (CSCtn90999) The mLACP for server access feature supports the following:
Pairs of Catalyst 6500 switches with Supervisor Engine 720 or with
Supervisor Engine 720-10GE configured as points of attachment (PoAs).
Note
A switch configured as a PoA cannot form an mLACP peer relationship with more than one other switch.
Servers with fully compliant IEEE 802.3ad LACP support, configured as dual-homed devices
(DHDs).
Note
The CLI does not enforce this restriction, but servers that support IEEE 802.3ad LACP are the only tested and supported DHDs.
One Layer 2 access link from each PoA to each DHD.
Note
The CLI does not enforce this restriction, but one Layer 2 access link from each PoA to each DHD is the only tested and supported configuration.
mLACP Layer 2 port-channel interfaces on a pair of switches with one Layer 2 access port per
mLACP port-channel interface on each PoA.
Note
The CLI does not enforce this restriction, but one Layer 2 access port per mLACP port-channel interface on each PoA is the only tested and supported configuration.
The mLACP for server access feature has an mLACP extended mode.
The mLACP extended mode is disabled by default. A reload is required to enable the mLACP extended mode after you enter the port-channel
mode mlacp-extended command.

When the mLACP extended mode is not enabled, the switch supports 128 PaGP, LACP, or
mLACP port-channel interfaces, numbered between 1 and 256. These port channel interfaces support QoS and ACLs.
19-9
Chapter 19 Configuring mLACP for Server Access
When the mLACP extended mode is enabled, the switch supports the following:
128 PaGP, LACP, or mLACP port-channel interfaces, numbered 1 through 256. These port-channel interfaces support QoS and ACLs. An additional 128 mLACP port-channel interfaces, numbered 257 through 512. These port-channel interfaces do not support QoS and ACLs.

Configure PoA network access so that each PoA can fully support all of the server traffic. Do not include one PoA in the network access path of the other PoA. Ensure that there is no server traffic on any links between the PoAs. Configure the Interchassis Communication Channel (ICC) as a point-to-point connection between the PoAs. Configure the ICC so that it carries only ICCP traffic.
Note
Traffic volume on the ICC will be relatively low.
mLACP operation is only supported when the ICC is functioning correctly. If possible, configure the ICC as a redundant connection. For example, you can configure the ICC as a two-link EtherChannel if there is available port-channel capacity. mLACP does not support half-duplex links. mLACP does not support multiple neighbors. Converting a port channel to mLACP can cause a service disruption. The DHD system priority must be lower (higher numerically) than the PoA system priority.

These sections describe how to configure mLACP for server access:

Summary of mLACP PoA Configuration Values, page 19-11 Configuring mLACP Global Options, page 19-11 Configuring the Interchassis Communication Channel, page 19-12 Configuring Interchassis Redundancy Groups, page 19-13 Forcing a PoA Failover, page 19-18 Troubleshooting mLACP, page 19-18 Verifying an Active PoA, page 19-18 Verifying a Standby PoA, page 19-22
19-10
OL-13013-06
Chapter 19
Configuring mLACP for Server Access Configuring mLACP for Server Access
Summary of mLACP PoA Configuration Values

Table 19-2 provides a list of the values that need to be coordinated on the PoA switches.
Table 19-2 Coordinated mLACP Configuration Values
Active PoA (Switch A)

interface type slot/port description connected to switch B ip address 10.0.0.1 255.255.255.255 ip route 200.0.0.1 255.255.255.255 icc_port_A interface loopback 0 description Supports routing to switch B ip address 100.0.0.1 255.255.255.255 mpls ldp router-id loopback 0 force redundancy interchassis group 10 member ip 10.0.0.2 mlacp system-priority 1 mlacp system-mac 0001.0001.0001 mlacp node-id 1 interface port-channel 50 mlacp interchassis group 10 mlacp lag-priority 1 interface type slot/port description connected to DHD channel-group 50 mode passive

interface type slot/port description connected to switch A ip address 10.0.0.2 255.255.255.255 ip route 100.0.0.1 255.255.255.255 icc_port_B interface loopback 0 description Supports routing to switch A ip address 200.0.0.1 255.255.255.255 mpls ldp router-id loopback 0 force redundancy interchassis group 10 member ip 10.0.0.1 mlacp system-priority 2 mlacp system-mac 0002.0002.0002 mlacp node-id 2 interface port-channel 50 mlacp interchassis group 10 mlacp lag-priority 2 interface type slot/port description connected to DHD channel-group 50 mode passive
Note
This summary section does not list all of the commands required to configure the mLACP for server access feature. See the following sections for complete configuration procedures.
Configuring mLACP Global Options

To configure mLACP global options, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. (Optional) Enables the mLACP extended mode, which supports configuration of an additional 128 mLACP port-channel interfaces.
Note
Router# configure terminal Router(config)# port-channel mode mlacp-extended
A reload is required to enable the mLACP extended mode after you enter the port-channel mode mlacp-extended command.
19-11
Step 4 Step 5
Router(config)# errdisable recovery cause mlacp-minlink
Enables automatic recovery from a failover state of the port channel. Returns to privileged EXEC mode.
Router(config)# end
Configuring the Interchassis Communication Channel

These sections describe how to configure the Interchassis Communication Channel (ICC):

Configuring the ICC Port, page 19-12 Configuring ICCP Routing, page 19-13
Configuring the ICC Port

To configure the ICC port, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode.
1
Router# configure terminal Router(config-if)# interface type slot/port
Selects the ICC port. Describes the ICC port that connects to the other PoA. Configures an IP address on the ICC port.
Note
Router(config-if)# description peer_description
Router(config-if)# ip address ip_address mask
This address is used as the member IP address on the other PoA.
Router(config-if)# mpls ip Router(config-if)# bfd interval 600 min_rx 600 multiplier 6
Enables MPLS on the interface. Configures BFD to support Interchassis Redundancy Manager (ICRM) traffic. Disables the interface. Enables the interface. Exits interface configuration mode. Returns to privileged EXEC mode.
Router(config-if)# shutdown Router(config-if)# no shutdown
Step 10 Router(config-if)# exit Step 11 Router(config)# end

This example shows how to configure the port that connects to the other PoA switch:
Router> enable Router# configure terminal Router(config-if)# interface fastethernet 1/1 Router(config-if)# description Connected to switch B Router(config-if)# ip address 10.0.0.1 255.255.255.255 Router(config-if)# bfd interval 600 min_rx 600 multiplier 6 Router(config-if)# shutdown Router(config-if)# no shutdown Router(config-if)# exit Router(config)# end
19-12
OL-13013-06
Chapter 19
Configuring ICCP Routing

To configure ICCP routing, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Configures a static route that points to the IP address of the loopback interface on the other PoA through the ICC port. Configures a loopback interface to support ICCP routing. (You can use an existing loopback interface.) Describes the loopback interface. Configures an IP address on the ICC port. Exits interface configuration mode. Configures MPLS LDP to use the loopback interface created in Step 4. Returns to privileged EXEC mode.
Router# configure terminal Router(config)# ip route ip_address mask icc_port
Step 4
Router(config)# interface loopback_interface
Router(config-if)# description loopback_description Router(config-if)# ip address ip_address mask Router(config-if)# exit Router(config)# mpls ldp router-id loopback_interface force
Router(config)# end
This example shows how to configure the port that connects to the other PoA switch:
Router> enable Router# configure terminal Router(config)# ip route 200.0.0.2 255.255.255.255 fastethernet 1/1 Router(config-if)# interface loopback 0 Router(config-if)# description Supports routing to switch B Router(config-if)# ip address 100.0.0.1 255.255.255.255 Router(config-if)# exit Router(config)# mpls ldp router-id 0 force Router(config)# end
Configuring Interchassis Redundancy Groups

These sections describe how to configure interchassis redundancy groups:

Configuring an Interchassis Redundancy Group, page 19-14 Configuring an mLACP Port-Channel Interface, page 19-15 Configuring the mLACP Member Port, page 19-17
19-13
Configuring an Interchassis Redundancy Group

To configure an interchassis redundancy group, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Enters redundancy configuration mode. Creates an interchassis group and enters interchassis redundancy mode.
Note
Router# configure terminal Router(config)# redundancy Router(config-red)# interchassis group group_id
Use the same interchassis group ID on the other PoA for the other link in the redundancy group.
Step 5
Router(config-r-ic)# member ip ip_address
Configures the IP address of the mLACP peer member group. Use the IP address configured on ICC port on the other PoA (Configuring the Interchassis Communication Channel, Step 5). Defines the mLACP system MAC address value that is part of the mLACP system ID value that selects the PoA that selects the active link.

Step 6
Router(config-r-ic)# mlacp system-mac {0001.0001.0001 | 0002.0002.0002}
Configure the active PoA with 0001.0001.0001. Configure the standby PoA with 0002.0002.0002.
Step 7
Router(config-r-ic)# mlacp system-priority {1 | 2}
Defines the mLACP system priority value that is part of the mLACP system ID value that selects the PoA that selects the active link.

Configure the active PoA with priority 1. Configure the standby PoA with priority 2.
Step 8
Router(config-r-ic)# mlacp node-id {1 | 2}
Defines the mLACP port number value used as part of the mLACP port identifier value that is used to select the active link.

Configure node ID 1 on the PoA that will have the active link. Configure node ID 2 on the PoA that will have the standby link.
Step 9
Router(config-r-ic)# backbone interface type slot/port
Configures mLACP link-status monitoring on the physical ports that carry server traffic to and from the network.
Note
Enter a backbone interface command for each port that carries server traffic between the PoA and the network.
Step 10 Router(config-r-ic)# monitor peer bfd
Configures the BFD option to monitor the state of the peer. The default option is route-watch.
19-14
OL-13013-06
Chapter 19
This example shows how to configure an interchassis redundancy group that configures a switch as the active PoA:
Router> enable Router# configure terminal Router(config)# redundancy Router(config-red)# interchassis group 10 Router(config-r-ic)# member ip 10.0.0.2 Router(config-r-ic)# mlacp node-id 1 Router(config-r-ic)# mlacp system-mac 0001.0001.0001 Router(config-r-ic)# mlacp system-priority 1 Router(config-r-ic)# monitor peer bfd
Configuring an mLACP Port-Channel Interface

To configure an mLACP port-channel interface, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Configures the port channel and enters interface configuration mode.

Router# configure terminal Router(config)# interface port-channel port_channel_id
The port_channel_id value can be from 1 through 256. In mLACP extended mode, the value can be from 1 through 512.
You can configure 128 PaGP, LACP, or
mLACP port-channel interfaces, numbered 1 through 256. These port channel interfaces support QoS and ACLs.
You can configure an additional 128
mLACP port-channel interfaces, numbered 257 through 512. These port channel interfaces do not support QoS and ACLs.
You must configure the same port-channel ID on the other PoA for the port-channel interface of other link in the mLACP redundancy group.
Configures the port-channel interface for Layer 2 switching. Configures the port-channel interface as an access port. Enables the interface. Associates the port-channel interface with the mLACP redundancy group. Use the group_id configured in Configuring Interchassis Redundancy Groups section on page 19-13, Step 4.
Router(config-if)# switchport access
Router(config-if)# no shutdown Router(config-if)# mlacp interchassis group group_id
19-15
Command or Action
Step 8
Router(config-r-ic)# mlacp node-id {1|2}
Purpose Defines the the mLACP port number value used as part of the mLACP port identifier value that is used to select the active link.

Configure the PoA with the active link with priority 1. Configure the PoA with the standby link with priority 2. The CLI does not enforce 1 as the only value, but it is the only tested and supported value.
Step 9
Router(config-if)# lacp max-bundle 1
Sets maximum number of active member ports.

Note
Step 10 Router(config-if)# port-channel min-links 1
Sets the minimum number of member ports.

Note
The CLI does not enforce 1 as the only value, but it is the only tested and supported value. The other link in the EtherChannel is on the other PoA.
Step 11 Router(config-if)# lacp failover non-revertive
(Optional) Sets the mLACP switchover to nonrevertive. The revertive mode is the default, with a 180-second delay.
Note
Although present in the CLI, the lacp failover brute-force command is not supported.
This example shows how to configure an mLACP port-channel interface:

Router> enable Router# configure terminal Router(config)# interface port-channel 50 Router(config-if)# switchport Router(config-if)# switchport access Router(config-if)# no shutdown Router(config-if)# mlacp lag-priority 1 Router(config-if)# mlacp interchassis group 10 Router(config-if)# lacp max-bundle 1 Router(config-if)# port-channel min-links 1
19-16
OL-13013-06
Chapter 19
Configuring the mLACP Member Port

To configure the mLACP member port, perform this task: Command or Action
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode.
1
Router# configure terminal Router(config-if)# interface type Router(config-if)# no ip address slot/port
Selects a LAN port to configure. Ensures that there is no IP address assigned to the LAN port. Configures the LAN port for Layer 2 switching. Configures the LAN port as an access port. Configures the LAN port as a member of a VLAN. Enables the LACP EtherChannel protocol. Configures the LAN port as a member of an mLACP port-channel interface and specifies the mode. Use the port_channel_id value configured on the appropriate mLACP port-channel interface. Defines the the mLACP port priority value used as part of the mLACP port identifier value that is used to select the active link.

Router(config-if)# switchport Router(config-if)# switchport mode access Router(config-if)# switchport access vlan vlan_id Router(config-if)# channel-protocol lacp Router(config-if)# channel-group port_channel_id mode {active | passive}
Step 10 Router(config-if)# mlacp lag-priority {1|2}
Configure the active link with priority 1. Configure the standby link with priority 2.
Step 11 Router(config-if)# shutdown Step 12 Router(config-if)# no shutdown

Disables the interface. Enables the interface.
This example shows how to configure an mLACP member port as the active link:
Router> enable Router# configure terminal Router(config-if)# interface gigabitethernet 1/1 Router(config-if)# no ip address Router(config-if)# switchport Router(config-if)# switchport mode access Router(config-if)# switchport access vlan 10 Router(config-if)# channel-protocol lacp Router(config-if)# channel-group 10 mode passive Router(config-if)# mlacp lag-priority 1 Router(config-if)# no shutdown
19-17
Forcing a PoA Failover

The mlacp lag-priority command also can be used to force a PoA failover in the following two ways:
Set the active PoAs LAG priority to a value greater than the LAG priority on the standby PoA. This setting results in the quickest failover because it requires the fewest LACP link state transitions on the standby links before they turn active. Set the standby PoAs LAG priority to a value numerically less than the LAG priority on the active PoA. This setting results in a slightly longer failover time because standby links have to signal OUT_OF_SYNC to the DHD before the links can be brought up and go active.
In some cases, the operational priority and the configured priority might differ when using dynamic port priority management to force failovers. In this case, the configured version is not changed unless the port channel is operating in nonrevertive mode. Enter the show lacp multichassis port-channel command to view the current operational priorities. Use the show running-config command to display the configured priority values.
Troubleshooting mLACP
Use these debug commands to troubleshoot mLACP: Command or Action
Step 1 Step 2
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enables debugging of the interchassis redundancy manager. Enables debugging of the InterChassis Control Protocol (ICCP). Enables debugging of LACP activity.
Router# debug redundancy interchassis {all | application | error | event | monitor} Router# debug mpls ldp iccp
Step 3 Step 4
Router# debug lacp [all | event | fsm | misc | multi-chassis [all | database | lacp-mgr | redundancy-group | user-interface] | packet]
Verifying an Active PoA

The following show commands can be used to display statistics and configuration parameters to verify the operation of the mLACP feature on an active PoA:

show lacp multi-chassis group, page 19-19 show lacp multi-chassis port-channel, page 19-20 show etherchannel summary, page 19-21 show etherchannel channel_id port-channel, page 19-21 show lacp internal, page 19-22 show lacp neighbor, page 19-22
19-18
OL-13013-06
Chapter 19
show lacp multi-chassis group

Use the show lacp multi-chassis group command to display the LACP parameters, local configuration, status of the backbone uplink, peer information, node ID, channel, state, priority active, and inactive links.
DC35-5# show lacp multi-chassis group 100 Interchassis Redundancy Group 10 Operational LACP Parameters: RG State: Synchronized System-Id: 1.0001.0001.0001 ICCP Version: 0 Backbone Uplink Status: Connected Local Configuration: Node-id: 1 System-Id: 1.0001.0001.0001 Peer Information: State: Node-id: System-Id: ICCP Version: State Flags: Active Standby Down AdminDown Standby Reverting Unknown mLACP Channel-groups Channel State Priority Group Local/Peer Local/Peer 50 A/S 1/2
Up 2 2.0002.0002.0002 0 A S D AD SR U
Active Links Local/Peer 1/1
Inactive Links Local/Peer 0/0
19-19
show lacp multi-chassis port-channel

Use the show lacp multi-chassis port-channel command to display the interface port-channel value channel group, LAG state, priority, inactive links peer configuration, and standby links.
DC35-5# show lacp multi-chassis port-channel1 Interface Port-channel50 Local Configuration: Address: 00d0.d32e.d23f Channel Group: 50 State: Active LAG State: Up Priority: 1 Inactive Links: 0 Total Active Links: 1 Bundled: 1 Selected: 1 Standby: 0 Unselected: 0 Peer Configuration: Interface: Port-channel50 Address: 0002.fcbd.cee5 Channel Group: 50 State: Standby LAG State: Up Priority: 2 Inactive Links: 0 Total Active Links: 1 Bundled: 0 Selected: 0 Standby: 1 Unselected: 0
19-20
OL-13013-06
Chapter 19
show etherchannel summary

Use the show etherchannel summary command to display the status and identity of the mLACP member links.
DC35-5# show etherchannel summary Flags: D - down P - bundled in port-channel I - stand-alone s - suspended H - Hot-standby (LACP only) R - Layer3 S - Layer2 U - in use N - not in use, no aggregation f - failed to allocate aggregator M m u d not in use, no aggregation due to minimum links not met not in use, port not aggregated due to minimum links not met unsuitable for bundling default port
w - waiting to be aggregated Number of channel-groups in use: 1 Number of aggregators: 1 Group Port-channel Protocol Ports ------+-------------+-----------+----------------------------------------------50 Po50(SU) LACP Fa1/44(P)
show etherchannel channel_id port-channel

Use the show etherchannel channel_id port-channel command to display the status and identity of the EtherChannel and and port channel.
DC35-5# show etherchannel 50 port-channel Port-channels in the group: ---------------------Port-channel: Po50 -----------Age of the Port-channel = 0d:01h:15m:10s Logical slot/port = 14/5 Number of ports = 1 HotStandBy port = null Port state = Port-channel Ag-Inuse Protocol = LACP Fast-switchover = disabled (Primary Aggregator)
Load share deferral = disabled Ports in the Port-channel: Index Load Port EC state No of bits ------+------+------------+------------------+----------0 FF Fa1/44 mLACP-active 8 Time since last port bundled: 0d:00h:14m:18s Time since last port Un-bundled: 0d:00h:14m:20s Last applied Hash Distribution Algorithm: Adaptive Fa1/44 Fa1/44
19-21
show lacp internal

Use the show lacp internal command to display the device, port, and member-link information.
DC35-5# show lacp internal Flags: S - Device is requesting Slow LACPDUs F - Device is requesting Fast LACPDUs A - Device is in Active mode P - Device is in Passive mode Channel group 50 Port Fa1/44 Flags SA State bndl-act LACP port Priority 1 Admin Key 0x32 Oper Key 0x32 Port Number 0x912D Port State 0x3D
Peer (DC35-6) mLACP member links
show lacp neighbor

Use the show lacp neighbor command to display the neighbor device, port, and member-link information.
DC35-5# show lacp neighbor Flags: S - Device is requesting Slow LACPDUs F - Device is requesting Fast LACPDUs A - Device is in Active mode P - Device is in Passive mode Channel group 50 neighbors Partner's information: Partner Partner Flags State SA bndl-act LACP Partner Partner Partner Partner Partner Port Priority Admin Key Oper Key Port Number Port State 32768 0x0 0xAC 0x62D 0x3D
Port Fa1/44
Verifying a Standby PoA

The following show commands can be used to display statistics and configuration parameters to verify the operation of the mLACP feature on a standby PoA:

show lacp multi-chassis group, page 19-23 show lacp multi-chassis portchannel, page 19-24 show etherchannel summary, page 19-25 show lacp internal, page 19-26
19-22
OL-13013-06
Chapter 19
show lacp multi-chassis group

Use the show lacp multi-chassis group command to display the LACP parameters, local configuration, status of the backbone uplink, peer information, node ID, channel, state, priority active, and inactive links.
DC35-6# show lacp multi-chassis group Interchassis Redundancy Group 10 Operational LACP Parameters: RG State: Synchronized System-Id: 1.0001.0001.0001 ICCP Version: 0 Backbone Uplink Status: Connected Local Configuration: Node-id: 2 System-Id: 2.0002.0002.0002 Peer Information: State: Node-id: System-Id: ICCP Version: State Flags: Active Standby Down AdminDown Standby Reverting Unknown mLACP Channel-groups Channel State Priority Group Local/Peer Local/Peer 50 S/A 2/1
Up 1 1.0001.0001.0001 0 A S D AD SR U
Active Links Local/Peer 1/1
Inactive Links Local/Peer 0/0
19-23
show lacp multi-chassis portchannel

Use the show lacp multi-chassis portchannel command to display the interface port-channel value channel group, LAG state, priority, inactive links peer configuration, and standby links.
DC35-6# show lacp multi-chassis port-channel Interface Port-channel50 Local Configuration: Address: 0002.fcbd.cee5 Channel Group: 50 State: Standby LAG State: Up Priority: 2 Inactive Links: 0 Total Active Links: 1 Bundled: 0 Selected: 0 Standby: 1 Unselected: 0 Peer Configuration: Interface: Port-channel50 Address: 00d0.d32e.d23f Channel Group: 50 State: Active LAG State: Up Priority: 1 Inactive Links: 0 Total Active Links: 1 Bundled: 1 Selected: 1 Standby: 0 Unselected: 0
19-24
OL-13013-06
Chapter 19
show etherchannel summary

Use the show etherchannel summary command to display the status and identity of the mLACP member links.
DC35-6# show etherchannel summary Flags: D - down P - bundled in port-channel I - stand-alone s - suspended H - Hot-standby (LACP only) R - Layer3 S - Layer2 U - in use N - not in use, no aggregation f - failed to allocate aggregator M m u d not in use, no aggregation due to minimum links not met not in use, port not aggregated due to minimum links not met unsuitable for bundling default port
w - waiting to be aggregated Number of channel-groups in use: 1 Number of aggregators: 1 Group Port-channel Protocol Ports ------+-------------+-----------+----------------------------------------------50 Po50(SU) LACP Fa3/44(P)
show etherchannel channel_id port-channel

Use the show etherchannel channel_id port-channel command to display the status and identity of the EtherChannel and port channel.
DC35-6# show etherchannel 50 port-channel Port-channels in the group: ---------------------Port-channel: Po50 -----------Age of the Port-channel = 0d:01h:17m:40s Logical slot/port = 14/5 Number of ports = 1 HotStandBy port = null Port state = Port-channel Ag-Inuse Protocol = LACP Fast-switchover = disabled (Primary Aggregator)
Load share deferral = disabled Ports in the Port-channel: Index Load Port EC state No of bits ------+------+------------+------------------+----------0 FF Fa3/44 mLACP-stdby 8 Time since last port bundled: 0d:00h:16m:59s Time since last port Un-bundled: 0d:00h:17m:00s Last applied Hash Distribution Algorithm: Adaptive Fa3/44 Fa3/44
19-25
show lacp internal

Use the show lacp internal command to display the device, port, and member-link information.
DC35-6# show lacp internal Flags: S - Device is requesting Slow LACPDUs F - Device is requesting Fast LACPDUs A - Device is in Active mode P - Device is in Passive mode Channel group 50 Port Fa3/44 Flags SA State bndl-sby LACP port Priority 2 Admin Key 0x32 Oper Key 0x32 Port Number 0xA32D Port State 0x5
Peer (DC35-5^C^C) mLACP member links
show lacp neighbor

Use the show lacp neighbor command to display the neighbor device, port, and member-link information.
DC35-6# show lacp neighbor Flags: S - Device is requesting Slow LACPDUs F - Device is requesting Fast LACPDUs A - Device is in Active mode P - Device is in Passive mode Channel group 50 neighbors Partner's information: Partner Partner Flags State FA bndl-sby LACP Partner Partner Partner Partner Partner Port Priority Admin Key Oper Key Port Number Port State 32768 0x0 0xAC 0x32D 0xF
Port Fa3/44
19-26
OL-13013-06
CH A P T E R
20

This chapter describes how to configure the IEEE 802.1ak Multiple VLAN Registration Protocol (MVRP) and Multiple Registration Protocol (MRP) as implemented in accordance with the IEEE 802.1ak standard.

Understanding IEEE 802.1ak MVRP and MRP, page 20-1 IEEE 802.1ak MVRP and MRP Guidelines and Restrictions, page 20-7 Configuring IEEE 802.1ak MVRP and MRP, page 20-8 Troubleshooting the MVRP Configuration, page 20-10 Configuration Examples for IEEE 802.1ak MVRP and MRP, page 20-11
Note
This feature appears in Cisco Feature navigator as IEEE 802.1ak - MVRP and MRP.
Understanding IEEE 802.1ak MVRP and MRP

These sctions describe IEEE 802.1ak MVRP and MRP:

Overview, page 20-1 Dynamic VLAN Creation, page 20-3 MVRP Interoperability with VTP, page 20-3 MVRP Interoperation with Non-Cisco Devices, page 20-5 MVRP Interoperability with Other Software Features and Protocols, page 20-5
Overview
MVRP supports dynamic registration and deregistration of VLANs on ports in a VLAN bridged network. IEEE 802.1ak uses more efficient Protocol Data Units (PDUs) and protocol design to provide better performance than the Generic VLAN Registration Protocol (GARP) VLAN Registration Protocol (GVRP) and GARP Multicast Registration Protocol (GMRP) protocols. A VLAN-bridged network usually restricts unknown unicast, multicast, and broadcast traffic to those links that the traffic uses to access the appropriate network devices. In a large network, localized topology changes can affect the service over a much larger portion of the network. IEEE 802.1ak replaces GARP with MRP, which provides improved resource utilization and bandwidth conservation.
20-1
Chapter 20 Understanding IEEE 802.1ak MVRP and MRP
With the 802.1ak MRP attribute encoding scheme, MVRP only needs to send one PDU that includes the state of all 4094 VLANs on a port. MVRP also transmits Topology Change Notifications (TCNs) for individual VLANs. This is an important feature for service providers because it allows them to localize topology changes. Figure 20-1 illustrates MVRP deployed in a provider network on provider and customer bridges.
Figure 20-1 MVRP Deployed on Provider and Customer Bridges
CB-3 MVRP H1 PB-2 MVRP
H2 CB-1 MVRP H5
CB-1 MVRP
PB-1 MVRP PB-3 MVRP
PB-4 MVRP
CB-2 MVRP H3 H4 MVRP runs on Customer Bridges MVRP runs on Provider Bridges H6
CB-2 MVRP H7
274481
Because most providers do not wish to filter traffic by destination MAC addresses, a pruning protocol like MVRP is important in a Metro Ethernet provider network, which often uses thousands of VLANs.
20-2
OL-13013-06
Chapter 20
Configuring IEEE 802.1ak MVRP and MRP Understanding IEEE 802.1ak MVRP and MRP
Figure 20-2 dispalys redundant links that are configured between the access switch and two distribution switches on the cloud. When the link with VLAN 104 fails over, MVRP needs to send only one TCN for VLAN 104. Without MVRP, an STP TCN would need to be sent out for the whole MST region (VLANs1-1000), which could cause unnecessary network interruption. STP sets the tcDetected variable to signal MVRP that MVRP must decide whether to send an MVRP TCN. MVRP can flush filtering database entries rapidly on a per-VLAN basis following a topology change because when a port receives an attribute declaration marked as new, any entries in the filtering database for that port and for that VLAN are removed.
Figure 20-2 MVRP TCN Application
MST1 V1-1000
MST2 V2001-3000
V1050 V104
V104
MVRP Applicant
Redundant links MVRP TCN for v104
Dynamic VLAN Creation

Virtual Trunking Protocol (VTP) is a Cisco proprietary protocol that distributes VLAN configuration information across multiple devices within a VTP domain. When VTP is running on MVRP-aware devices, all of the VLANs allowed on the Cisco bridged LAN segments are determined by VTP. Only the VTP transparent mode supports MVRP dynamic VLAN creation. When dynamic VLAN creation is disabled, the MVRP trunk ports can register and propagate the VLAN messages only for existing VLANs. MVRP PDUs and MVRP messages for the nonexistant VLANs are discarded. For a switch to be configured in full compliance with the MVRP standard, the switch VTP mode must be transparent and MVRP dynamic VLAN creation must be enabled.
MVRP Interoperability with VTP

These sections describe MVRP and VTP:

Overview, page 20-4 VTP in Transparent or Off Mode, page 20-4
274480
20-3
VTP in Server or Client Mode and VTP Pruning is Disabled, page 20-4 VTP in Server or Client Mode and VTP Pruning is Enabled, page 20-4
Overview
The VLAN Trunking Protocol (VTP) is a Cisco proprietary protocol that distributes VLAN configuration information across multiple devices within a VTP domain. VTP pruning is an extension of VTP. It has its own Join message that can be exchanged with VTP PDUs. VTP PDUs can be transmitted on both 802.1Q trunks and ISL trunks. A VTP-capable device is in one of the VTP modes: server, client, transparent, or off. When VTP Pruning and MVRP are both enabled globally, MVRP runs on trunks where it is enabled and VTP Pruning runs on other trunks. MVRP or VTP pruning can be enabled on a trunk, but not both.
VTP in Transparent or Off Mode

When VTP is in transparent or off mode, VTP pruning is not supported and VTP PDUs are not processed. When a port receives an MVRP join message for a VLAN, the port transmits broadcast, multicast, and unknown unicast frames in that VLAN and adds the traffic definition to the MRP Attribute Propagation (MAP) port configured for that VLAN. The mapping is removed when the VLAN is no longer registered on the port. For each interface that is forwarding in each VLAN, MVRP issues a join request to each MRP Attribute Declaration (MAD) instance and an MVRP Join message is sent out on each corresponding MVRP port. MVRP dynamic VLAN creation can be enabled in VTP transparent or off mode. If it is enabled and the VLAN registered by a join message does not exist in the VLAN database in the device, then the VLAN will be created.
VTP in Server or Client Mode and VTP Pruning is Disabled

MVRP functions like VTP in transparent or off mode, except that MVRP dynamic VLAN creation is not allowed.
VTP in Server or Client Mode and VTP Pruning is Enabled

MVRP and VTP with pruning disabled can be supported on the same port and these two protocols need to communicate and exchange pruning information. When VTP receives a VTP join message on a VTP trunk, MVRP is notified so that join request can be posted to the MVRP port MAD instances, and MVRP join messages are out on the MVRP ports to the MVRP network. When VTP pruning removes a VLAN from a VTP trunk, MVRP sends a leave request to all the MAD instances and the MAD instances send a leave or empty message from the MVRP ports to indicate that the VLAN is not configured on the device. When an MVRP port received an MVRP join message, MVRP propagates the event to other MVRP ports in the same MAP context, and notifies VTP so that VTP pruning can send a VTP join message from the VTP trunk ports. If MVRP learns that a VLAN is no longer declared by the neighboring devices, MVRP sends a withdrawal event to VTP and then VTP pruning verifies that it should continue sending VTP join messages.
20-4
OL-13013-06
Chapter 20
Configuring IEEE 802.1ak MVRP and MRP Understanding IEEE 802.1ak MVRP and MRP
For VLANs that are configured as VTP pruning non-eligible on the VTP trunks, the VTP pruning state variables are set to joined for the VLANs. MVRP join requests are sent to those VLANs through the MVRP ports.
MVRP Interoperation with Non-Cisco Devices

Non-Cisco devices can interoperate with a Cisco device only through 802.1q trunks.
MVRP Interoperability with Other Software Features and Protocols

These sections describes MVRP interoperability with these protocols:

802.1x and Port Security, page 20-5 DTP, page 20-5 EtherChannel, page 20-6 Flex Links, page 20-6 High Availability, page 20-6 ISSU and eFSU, page 20-6 L2PT, page 20-6 SPAN, page 20-6 Unknown Unicast and Multicast Flood Control, page 20-6 STP, page 20-6 UDLR, page 20-6 VLANs with MVRP, page 20-7
802.1x and Port Security

802.1x authenticates and authorizes a port after it transitions to the link-up state, but before DTP negotiation occurs and MVRP runs on a port. Port security works independently of MVRP.
Note
When MVRP is globally enabled, the MVRP MAC address auto detect and provision feature is disabled by default (mvrp mac-learning auto). In some situations, MVRP MAC address auto detect and provision can disable MAC address learning and prevent correct port security operation. For example, on ports where port security is configured, when the number of streams exceeds the configured maximum number of MAC addresses, no port security violation occurs because MAC address learning is disabled, which prevents updates to port security about the streams coming into the port. To avoid incorrect port security operation, use caution when enabling the MVRP MAC address auto detect and provision feature on ports where port security is configured.
DTP
DTP negotiation occurs after ports transition to the link-up state and before transition to the forwarding state. If MVRP is administratively enabled globally and enabled on a port, it becomes operational when the port starts trunking.
20-5
EtherChannel
An EtherChannel port-channel interface can be configured as an MVRP participant. The EtherChannel member ports cannot be MVRP participants. MVRP learns the STP state of EtherChannel port-channel interfaces. The MAP context applies to the EtherChannel port-channel interfaces, but not to the EtherChannel member ports.
Flex Links
MVRP declares VLANs on STP forwarding ports but not on ports in the blocking state. On flex links ports, MVRP declares VLANs on the active ports but not on the standby ports. when a standby port takes over and an active port transitions to the link-down state, MVRP declares the VLANs on the newly active port.
High Availability
State Switchover (SSO) and ISSU supports MVRP.
ISSU and eFSU

Enhanced Fast Software Upgrade (EFSU) is an enhanced software upgrade procedure. MVRP is serviced by the ISSU client identified as ISSU_MVRP_CLIENT_ID.
L2PT
Layer 2 Protocol Tunneling (L2PT) does not support MVRP PDUs on 802.1Q tunnel ports.
SPAN
MVRP ports can be configured as either Switched Port Analyzer (SPAN) sources or destinations.
Unknown Unicast and Multicast Flood Control

MVRP and the Unknown Unicast and Multicast Flood Control feature, configured with the switchport block command, cannot be configured on the same port.
STP
An STP mode change causes forwarding ports to leave the forwarding state until STP reconverges in the newly configured mode. The reconvergence might cause an MVRP topology change because join messages might be received on different forwarding ports, and leave timers might expire on other ports.
UDLR
MVRP and unidirectional link routing (UDLR) cannot be configured on the same port.
20-6
OL-13013-06
Chapter 20
Configuring IEEE 802.1ak MVRP and MRP IEEE 802.1ak MVRP and MRP Guidelines and Restrictions
VLANs with MVRP

This sections decribe interactions between VLANs and MVRP:

VLAN Translation, page 20-7 802.1Q Native VLAN Tagging, page 20-7 Private VLANs, page 20-7
VLAN Translation
VLAN translation and MVRP cannot be configured on the same port.
802.1Q Native VLAN Tagging

Other MVRP participants might not be able to accept tagged MVRP PDUs in the 802.1Q native VLAN. Compatibility between MVRP and 802.1Q native VLAN tagging depends on the specific network configuration.
Private VLANs
Private VLAN ports cannot support MVRP.
IEEE 802.1ak MVRP and MRP Guidelines and Restrictions

When configuring IEEE 802.1ak MVRP and MRP, follow these guidelines and restrictions:

A non-Cisco device can interoperate with a Cisco device only through 802.1Q trunks. MVRP runs on ports where it is enabled. VTP pruning can run on ports where MVRP is not enabled. MVRP can be configured on both physical interfaces and EtherChannel interfaces, but is not supported on EtherChannel member ports. MVRP dynamic VLAN creation is not supported when the device is running in VTP server or client mode. MVRP and Connectivity Fault Management (CFM) can coexist but if the module does not have enough MAC address match registers to support both protocols, the MVRP ports on those modules are put in the error-disabled state. To use the ports that have been shut down, disable MVRP on the ports, and then enter shutdown and no shutdown commands. 802.1X authentication and authorization takes place after the port becomes active and before the Dynamic Trunking Protocol (DTP) negotiations start prior to MVRP running on the port. Do not enable MVRP automatic MAC address learning on edge switches that are configured with access ports. Enable MVRP automatic MAC address learning only on core switches where all the trunk interfaces are running MVRP. MVRP is supported only on Layer 2 trunks. MVRP is not supported on subinterfaces.
20-7
Chapter 20 Configuring IEEE 802.1ak MVRP and MRP

These sections describe how to configure IEEE 802.1ak MVRP and MRP:

Enabling MVRP, page 20-8 Enabling Automatic Detection of MAC Addresses, page 20-8 Enabling MVRP Dynamic VLAN Creation, page 20-9 Changing the MVRP Registrar State, page 20-9
Enabling MVRP
MVRP must be enabled globally and on trunk ports. To enable MVRP, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Globally enables MVRP. Specifies and interface and enters interface configuration mode. Enables MVRP on the interface.
Note
Router# configure terminal Router(config)# mvrp global Router(config)# interface type number
Router(config-if)# mvrp
If MVRP is not successfully enabled on the port, the port is put in the errdisabled state. Enter the shutdown and no shutdown commands to clear the errdisabled state.
This example shows how to enable MVRP globally and on an interface:

Router> enable Router# configure terminal Router(config)# mvrp global Router(config)# interface FastEthernet 2/1 Router(config-if)# mvrp
Enabling Automatic Detection of MAC Addresses

MVRP automatic detection of MAC addresses is disabled by default. To enable MVRP automatic detection of MAC addresses on VLANs, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Enables MAC address learning.
Router# configure terminal Router(config)# mvrp mac-learning auto
20-8
OL-13013-06
Chapter 20
Configuring IEEE 802.1ak MVRP and MRP Configuring IEEE 802.1ak MVRP and MRP
This example shows how to enable automatic MAC address learning:

Router> enable Router# configure terminal Router(config)# mvrp mac-learning auto
Enabling MVRP Dynamic VLAN Creation

To enable MVRP dynamic VLAN creation, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Sets VTP mode to transparent.
Note
Router# configure terminal Router(config)# vtp mode transparent
Required for MVRP dynamic VLAN creation.
Step 4
Router(config)# mvrp vlan creation
Enables MRVP dynamic VLAN creation.
This example shows how to enable MVRP dynamic VLAN creation:

Router> enable Router# configure terminal Router(config)# vtp mode transparent Router(config)# mvrp vlan create
Changing the MVRP Registrar State

The MRP protocol allows one participant per application in an end station, and one per application per port in a bridge. To set the MVRP registrar state, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Enters global configuration mode. Specifies and interface and enters interface configuration mode. Registers MVRP with the MAD instance.
Router# configure terminal Router(config)# interface type number
Router(config-if)# mvrp registration [normal | fixed | forbidden]
This example shows how to set the MVRP registrar state to normal:
Router> enable Router# configure terminal Router(config)# interface FastEthernet 2/1 Router(config-if)# mvrp registration normal
20-9
Chapter 20 Troubleshooting the MVRP Configuration
Troubleshooting the MVRP Configuration

Use the show mvrp summary and show mvrp interface commands to display configuration information and interface states, and the debug mvrp command to enable all or a limited set of output messages related to an interface. To troubleshoot the MVRP configuration, perform this task: Command or Action
Router> enable
Purpose Enables privileged EXEC mode (enter your password if prompted). Displays the MVRP configuration. Displays the MVRP interface states for the specified interface. Displays MVRP debugging information. Clears MVRP statistics on all interfaces.
Router# show mvrp summary Router# show mvrp interface interface-type port/slot Router# debug mvrp Router# clear mvrp statistics
The following is sample output from the show mvrp summary command. This command can be used to display the MVRP configuration at the device level.
Router# show mvrp summary MVRP global state MVRP VLAN creation VLANs created via MVRP Learning disabled on VLANs : : : : enabled disabled 20-45, 3001-3050 none
The following is sample output from the show mvrp interface command. This command can be used to display MVRP interface details of the administrative and operational MVRP states of all or one particular trunk port in the device.
Router# show mvrp interface Port Fa3/1 Port Fa3/1 Port Fa3/1 Port Fa3/1 Port Fa3/1 Status off Registrar State normal Leave Timeout 700 Leaveall Timeout 1000
Join Timeout 201 600 Vlans Declared none
Vlans Registered none Vlans Registered and in Spanning Tree Forwarding State none
20-10
OL-13013-06
Chapter 20
Configuring IEEE 802.1ak MVRP and MRP Configuration Examples for IEEE 802.1ak MVRP and MRP
Configuration Examples for IEEE 802.1ak MVRP and MRP

This section provides the following configuration examples:

Enabling MVRP, page 20-11 Enabling MVRP Automatic Detection of MAC Addresses, page 20-11 Enabling Dynamic VLAN Creation, page 20-11 Changing the MVRP Registrar State, page 20-11
Enabling MVRP
The following example shows how to enable MVRP:
Router> enable Router# configure terminal Router(config)# mvrp global Router(config)# interface fastethernet2/1 Router(config-if)# mvrp
Enabling MVRP Automatic Detection of MAC Addresses

The following example shows how to enable MAC address learning:
Router> enable Router# configure terminal Router(config)# mvrp mac-learning auto
Enabling Dynamic VLAN Creation

The following example shows how to enable dynamic VLAN creation:
Router> enable Router# configure terminal Router(config)# vtp mode transparent Router(config)# mvrp vlan create
Changing the MVRP Registrar State

The following example shows how to change the MVRP registrar state:
Router> enable Router# configure terminal Router(config)# mvrp registration normal
20-11
Chapter 20 Configuration Examples for IEEE 802.1ak MVRP and MRP
20-12
OL-13013-06
C H A P T E R
21
Configuring VTP
This chapter describes how to configure the VLAN Trunking Protocol (VTP) in Cisco IOS Release 12.2SX.
Note
Tip

Understanding VTP, page 21-1 VLAN Interaction, page 21-8 VTP Default Configuration, page 21-8 VTP Configuration Guidelines and Restrictions, page 21-9 Configuring VTP, page 21-10
Understanding VTP
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.
21-1
Chapter 21 Understanding VTP
Configuring VTP
Note
For complete information on configuring VLANs, see Chapter 22, Configuring VLANs. These sections describe how VTP works:

Understanding the VTP Domain, page 21-2 Understanding VTP Modes, page 21-3 Understanding VTP Advertisements, page 21-3 Understanding VTP Authentication, page 21-4 Understanding VTP Version 2, page 21-4 Understanding VTP Version 3, page 21-5 Understanding VTP Pruning, page 21-6
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). VTP server mode is the default and the switch is in the no-management domain state until it 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. The valid VLAN ranges are as follows:

VTP version 1 and version 2 support VLANs 1 to 1000 only. In Cisco IOS Release 12.2(33)SXI and later releases, VTP version 3 is supported. In VTP version 3, the entire VLAN range is supported (VLANs 1 to 4094). The pruning of VLANs still applies to VLANs 1 to 1000 only. Extended-range VLANs are supported only in VTP version 3. If converting from VTP version 3 to VTP version 2, VLANs in the range 1006 to 4094 are removed from VTP control.
By default, all devices come up as secondary servers. You can enter the vtp primary privileged EXEC mode command to specify a primary server. In Cisco IOS releases prior to Release 12.2(33)SXI, when using VTP version 1 and version 2, a VTP server is used to back up the database to the NVRAM and allows you to change the database information. In Cisco IOS Release 12.2(33)SXI and later releases, VTP version 3 is supported. In VTP version 3, there is a VTP-primary server and a VTP-secondary server. A primary server allows you to alter the database information and the database updates sent out are honored by all the devices in the system. A secondary server can only back up the updated VTP configuration received from the primary server in the NVRAMs. The status of the primary and secondary servers is a runtime status and is not configurable. VTP maps VLANs dynamically across multiple LAN types with unique names and internal index associations. Mapping eliminates excessive device administration required from network administrators.
21-2
OL-13013-06
Chapter 21
Configuring VTP Understanding VTP
Understanding VTP Modes

You can configure 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, a transparent network device will forward received VTP advertisements from its trunking LAN ports. In VTP version 3, a transparent network device is specific to an instance. OffIn VTP off mode, a network device functions in the same manner as a VTP transparent device except that it does not forward VTP advertisements.
Note
The VTP server mode automatically changes 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 version 1 and version 2 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 the maximum transmission unit (MTU) size for each VLAN. Frame format.
In VTP version 3, the information distributed in VTP version 1 and version 2 advertisements are supported, as well as the following information:

A primary server ID. An instance number. A start index.
21-3
Configuring VTP
An advertisement request is sent by a Client or a Server in these situations:

On a trunk coming up on a switch with an invalid database. On all trunks when the database of a switch becomes invalid as a result of a configuration
change or a takeover message.

On a specific trunk where a superior database has been advertised.
VTP version 3 adds the following fields to the subset advertisement request:
A primary server ID. An instance number. A window size. A start index.
Understanding VTP Authentication

In releases prior to Cisco IOS Release 12.2(33)SXI, the secret that is used to validate the received VTP updates is visible in plain text in the show commands and the NVRAM file, const_nvram:vlan.dat. In the event that a device in a VTP domain is compromised, the administrator had to change the VTP secret across all the devices in the VTP domain. In Cisco IOS Release 12.2(33)SXI and later releases, VTP version 3 is supported. In VTP version 3, you can configure the authentication password to be hidden using the vtp password command. When you configure the authentication password to be hidden, it does not appear in plain text in the configuration. Instead, the secret associated with the password is saved in hexadecimal format in the running configuration. The password-string argument is an ASCII string from 1 to 64 characters identifying the administrative domain for the device.
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 VLANs section on page 22-1. Unrecognized Type-Length-Value (TLV) SupportA VTP server or client propagates configuration changes to its other trunks, even for TLVs that 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, VTP version 2 forwards VTP messages in transparent mode without checking the version.
21-4
OL-13013-06
Chapter 21
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.
Understanding VTP Version 3

Note
If you are using VTP in a Token Ring environment, you must use version 2. In Cisco IOS Release 12.2(33)SXI and later releases, VTP version 3 is supported. VTP version 3 supports all the features in version 1 and version 2. VTP version 3 also supports the following features not supported in version 1 and version 2:
Enhanced authenticationIn VTP version 3, you can configure the authentication password to be hidden using the vtp password command. When you configure the authentication password to be hidden, it does not appear in plain text in the configuration. Instead, the secret associated with the password is saved in hexadecimal format in the running configuration. The password-string argument is an ASCII string from 1 to 64 characters identifying the administrative domain for the device. The hidden and secret keywords for VTP password are supported only in VTP version 3. If converting to VTP version 2 from VTP version 3, you must remove the hidden or secret keyword prior to the conversion. These keywords are supported on the Catalyst 6500 series switch only.
Support for extended range VLAN database propagationVTP version 1 and version 2 support VLANs 1 to 1000 only. In VTP version 3, the entire VLAN range is supported (VLANs 1 to 4094). The pruning of VLANs still applies to VLANs 1 to 1000 only. Extended-range VLANs are supported in VTP version 3 only. Private VLANs are supported in VTP version 3. If you convert from VTP version 3 to VTP version 2, the VLANs in the range 1006 to 4094 are removed from VTP control. VLANs 1002 to 1005 are reserved VLANs in VTP version 1, version 2, and version 3. Support for propagation of any database in a domainIn VTP version 1 and version 2, a VTP server is used to back up the database to the NVRAM and allows you to change the database information.
Note
In Cisco IOS Release 12.2(33)SXI and later releases, VTP version 3 supports Multiple Spanning Tree (802.1s) (MST) database propagation separate from the VLAN database only. In the MST database propagation, there is a VTP primary server and a VTP econdary server. A primary server allows you to alter the database information, and the database updates sent out are honored by all the devices in the system. A secondary server can only back up the updated VTP configuration received from the primary server in the NVRAMs. The status of the primary and secondary servers is a runtime status and is not configurable. By default, all devices come up as secondary servers. You can enter the vtp primary privileged EXEC mode command to specify a primary server. The primary-server status is needed only when database changes have to be performed and is obtained when the administrator issues a takeover message in the domain. The primary-server status is lost when you reload, switch over, or the domain parameters change. The secondary servers back up the configuration and continue to propagate the database. You can have a working VTP domain without any primary servers. Primary and secondary servers may exist on an instance in the domain.
21-5
Configuring VTP
In VTP version 3, there is no longer a restriction to propagate only VLAN database information. You can use VTP version 3 to propagate any database information across the VTP domain. A separate instance of the protocol is running for each application that uses VTP. Two VTP version 3 regions can only communicate over a VTP version 1 or VTP version 2 region in transparent mode.
CLI to turn off/on VTP on a per-trunk basisYou can enable VTP on a per-trunk basis using the vtp interface configuration mode command. You can disable VTP on a per-trunk basis using the no form of this command. When you disable VTP on the trunking port, all the VTP instances for that port are disabled. You will not be provided with the option of setting VTP to OFF for the MST database and ON for the VLAN database.
VTP on a global basisWhen you set VTP mode to OFF globally, this applies to all the trunking ports in the system. Unlike the per-port configuration, you can specify the OFF option on a per-VTP instance basis. For example, the system could be configured as VTP-server for the VLAN database and as VTP-off for the MST database. In this case, VLAN databases are propagated by VTP, MST updates are sent out on the trunk ports in the system, and the MST updates received by the system are discarded.
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. In VTP versions 1 and 2, when you enable or disable pruning, it is propagated to the entire domain and accepted by all the devices in that domain. In VTP version 3, the domain administrator must manually enable or disable VTP pruning explicitly on each device. 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 21-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 switch (see the Enabling VTP Pruning section on page 21-13). You configure pruning on Layer 2 trunking LAN ports (see the Configuring a Layer 2 Switching Port as a Trunk section on page 16-10).
21-6
OL-13013-06
Chapter 21
Figure 21-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 21-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).
Figure 21-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 16-10). 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.
21-7
Chapter 21 VLAN Interaction
Configuring VTP
VLAN Interaction
This section describes the VLAN interaction between devices with different VTP versions:

Interaction Between VTP Version 3 and VTP Version 2 Devices, page 21-8 Interaction Between VTP Version 3 and VTP Version 1 Devices, page 21-8
Interaction Between VTP Version 3 and VTP Version 2 Devices

When a VTP version 3 device on a trunk port receives messages from a VTP version 2 device, the VTP version 3 device sends a scaled-down version of the VLAN database on that particular trunk in a VTP version 2 format. A VTP version 3 device does not send out VTP version 2-formatted packets on a trunk port unless it first receives VTP version 2 packets on that trunk. If the VTP version 3 device does not receive VTP version 2 packets for an interval of time on the trunk port, the VTP version 3 device stops transmitting VTP version 2 packets on that trunk port. Even when a VTP version 3 device detects a VTP version 2 device on a trunk port, the VTP version 3 device continues to send VTP version 3 packets in addition to VTP version 3 device 2 packets, to allow two kinds of neighbors to coexist on the trunk. VTP version 3 sends VTP version 3 and VTP version 2 updates on VTP version 2-detected trunks. A VTP version 3 device does not accept configuration from a VTP version 2 (or VTP version 1) device. Unlike in VTP version 2, when you configure the VTP version to be version 3, version 3 does not configure all the VTP version 3-capable devices in the domain to start behaving as VTP version 3 systems.
Interaction Between VTP Version 3 and VTP Version 1 Devices

When a VTP version 1 device that is capable of VTP version 2 or VTP version 3 receives a VTP version 3 packet, it will be configured as a VTP version 2 device if VTP version 2 conflicts do not exist. VTP version 1-only capable devices cannot interoperate with VTP version 3 devices.
VTP Default Configuration

Table 21-1 shows the default VTP configuration.
Table 21-1 VTP Default Configuration
Feature VTP domain name VTP version 1 and version 2 mode VTP version 3 mode
Default Value Null Server The VTP version 3 VLAN database mode is the same as the VLAN database mode in VTP version 1 or 2 after the conversion from VTP version 1 or 2 to VTP version 3. For example, the VTP version 1 or 2 VLAN database mode is carried over to VTP version 3 VLAN database mode. Transparent
MST database mode
21-8
OL-13013-06
Chapter 21
Configuring VTP VTP Configuration Guidelines and Restrictions
Table 21-1
VTP Default Configuration (continued)
Feature VTP version 3 server type VTP version 2 state VTP password VTP pruning
Default Value Secondary 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 filenames 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. 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 VTP in secure mode, 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 that runs VTP version 1 if 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. VTP version 1 and VTP version 2 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. VTP version 3 supports extended-range VLANs (VLAN numbers 1006 to 4094). If you convert from VTP version 3 to VTP version 2, the VLANs in the range 1006 to 4094 are removed from VTP control. VTP version 3 supports propagation of any database in a domain by allowing you to configure a primary and secondary server.
21-9
Chapter 21 Configuring VTP
Configuring VTP
In Cisco IOS Release 12.2(33)SXI and later releases, the network administrator has to manually configure VTP version 3 on the switches that need to run VTP version 3. Prior to configuring VTP version 3, you must ensure that the spanning-tree extend system-id command has been enabled. 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 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 16-14.
Configuring VTP
These sections describe how to configure VTP:

Configuring VTP Global Parameters, page 21-10 Configuring the VTP Mode, page 21-15 Configuring VTP Mode on a Per-Port Basis, page 21-17 Displaying VTP Statistics, page 21-18
Configuring VTP Global Parameters

These sections describe configuring the VTP global parameters:

Configuring VTP Version 1 and Version 2 Passwords, page 21-10 Configuring VTP Version 3 Password, page 21-11 Enabling VTP Pruning, page 21-13 Enabling VTP Version 2, page 21-13 Enabling VTP Version 3, page 21-14
Note
You can enter the VTP global parameters in either global configuration mode or in EXEC mode.
Configuring VTP Version 1 and Version 2 Passwords

To configure the VTP version 1 and version 2 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:
21-10
OL-13013-06
Chapter 21
Configuring VTP Configuring VTP
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.
Configuring VTP Version 3 Password

To configure the VTP version 3 password, perform this task: Command
Router(config)# vtp password password-string [hidden | secret]
Purpose Configures a password, which can be from 1 to 64 characters long or in 32-digit hexadecimal format, for the VTP domain.
Note
When entering the secret keyword, the password-string must be entered in 32-digit hexadecimal format.
Router(config)# no vtp password
Clears the 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 VTP database password to water. Router#
Note
If you configure a VTP password in EXEC mode, the password is not stored in the running-config file. This example shows one way to configure the password with a hidden key saved in hexadecimal format in the running configuration:
Router# configure terminal Router(config)# vtp password 82214640C5D90868B6A0D8103657A721 hidden Setting device VTP password Router#
This example shows how you configure the password secret key in hexadecimal format:
Router# configure terminal Router(config)# vtp password 300F060A2B0601035301020107010201 secret Setting device VTP password Router#
21-11
Configuring VTP
Configuring VTP Version 3 Server Type

To specify a primary server, perform this task: Command
Step 1 Step 2
Router# vtp primary [vlan | mst] [force] Router# show vtp status
Purpose Configure this device as the primary server. Verifies the configuration.
The vtp primary command does not have a no form. To return to the secondary server status, one of the following conditions must be met:

System reload. Switchover between redundant supervisors. Takeover from another server. Change in the mode configuration. Any domain configuration change (version, domain name, domain password).
This example shows how to configure this device as the primary server if the password feature is disabled:
Router# vtp primary This system is becoming primary server for feature vlan No conflicting VTP version 3 devices found. Do you want to continue? [confirm]y Router#
This example shows how to configure this device as the primary server for the VTP VLAN feature if the password feature is disabled:
Router# vtp primary vlan This system is becoming primary server for feature vlan No conflicting VTP version 3 devices found. Do you want to continue? [confirm]y Router#
This example shows how to force this device to be the primary server for the VTP MST feature if the password feature is disabled:
Router# vtp primary mst force This system is becoming primary server for feature MST No conflicting VTP version 3 devices found. Do you want to continue? [confirm]y Router#
This example shows how to force this device to be the primary server for the VTP MST feature when the domain VTP password is set with the hidden or secret keyword:
Router# vtp primary mst force Enter VTP password: water1 This switch is becoming Primary server for mst feature in the VTP domain VTP Database Conf Switch ID Primary Server Revision System Name ------------ ---- -------------- -------------- -------- -------------------VLANDB Yes 00d0.00b8.1400=00d0.00b8.1400 1 stp7 Do you want to continue (y/n) [n]? y Router#
21-12
OL-13013-06
Chapter 21
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#
For information about configuring prune eligibility, see the Configuring the List of Prune-Eligible VLANs section on page 16-14.
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
21-13
Configuring VTP
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#
Enabling VTP Version 3

VTP version 3 is disabled by default. You can enable version 3 in global configuration mode only. In Cisco IOS Release 12.2(33)SXI and later releases, the network administrator has to manually configure VTP version 3 on the switches that need to run VTP version 3.
Note
Prior to configuring VTP version 3, you must ensure that the spanning-tree extend system-id command has been enabled.
Caution
In VTP version 3, both the primary and secondary servers may exist on an instance in the domain. To enable VTP version 3, perform this task:
Command
Step 1
Router(config)# vtp version 3 Router(config)# no vtp version
Purpose Enables VTP version 3. Reverts to the default (VTP version 1). Verifies the configuration.
Step 2
This example shows one way to enable VTP version 3:

Router# configure terminal Router(config)# vtp version 3 Router(config)#

Router# show vtp status VTP Version capable VTP version running VTP Domain Name VTP Pruning Mode VTP Traps Generation Device ID Feature VLAN: -------------: : : : : : 1 to 3 3 lab_switch Disabled Disabled 0015.c724.0040
21-14
OL-13013-06
Chapter 21
VTP Operating Mode : Server Number of existing VLANs : 6 Number of existing extended VLANs : 0 Configuration Revision : 0 Primary ID : 0000.0000.0000 Primary Description : MD5 digest : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00
Feature MST: -------------VTP Operating Mode
: Transparent
Feature UNKNOWN: -------------VTP Operating Mode Router#
: Transparent
Configuring the VTP Mode

To configure the VTP mode, perform this task: Command
Step 1 Step 2
Router(config)# vtp mode {client | server | transparent | off} {vlan | mst | unknown} Router(config)# vtp domain domain-name
Purpose Configures the VTP mode. (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
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
When VTP is disabled, you can enter VLAN configuration commands in configuration mode instead of the VLAN database mode and 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#
This example shows how to configure the switch as a VTP client:

Router# configuration terminal Router(config)# vtp mode client
21-15
Configuring VTP
Setting device to VTP CLIENT mode. Router(config)# exit 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#
This example shows how to disable VTP on the switch and to disable VTP advertisement forwarding:
Router# config terminal Enter configuration commands, one per line. Router(config)# vtp mode off Setting device to VTP OFF mode. Router(config)# exit Router# End with CNTL/Z.

Router# show vtp status VTP Version capable VTP version running VTP Domain Name VTP Pruning Mode VTP Traps Generation Device ID : : : : : : 1 to 3 3 lab_network Disabled Disabled 0015.c724.0040
Feature VLAN: -------------VTP Operating Mode : Server Number of existing VLANs : 6 Number of existing extended VLANs : 0 Configuration Revision : 0 Primary ID : 0000.0000.0000 Primary Description : MD5 digest : 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 0x00 Feature MST: -------------VTP Operating Mode Feature UNKNOWN: -------------VTP Operating Mode Router#
: Transparent
: Transparent
21-16
OL-13013-06
Chapter 21
Configuring VTP Mode on a Per-Port Basis

With Release 12.2(33)SXH and later releases, you can configure VTP mode on a per-port basis. The VTP enable value will be applied only when a port becomes switched port in trunk mode. Incoming and outgoing vtp pdus are blocked; not forwarded. With Release 12.2(33)SXI and later releases, in VTP version 3, you can also configure VTP mode on a per-trunk basis. To configure VTP mode, perform this task: Command
Router(config)# interface type Router(config-if)# vtp Router(config-if)# end Router# show running-config interface type slot/port Router# show vtp interface 1. type = fastethernet, gigabitethernet, or tengigabitethernet
1
Purpose
slot/port
Selects an interface to configure. Enables VTP on the specified port. Exits interface configuration mode. Verifies the change to the port. Verifies the configuration.
This example shows how to configure VTP mode on a port:

Router# config terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 3/5 Router(config-if)# vtp Router(config-if)# end Router#
This example shows how to disable VTP mode on a port:

Router# config terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 3/5 Router(config-if)# no vtp Router(config-if)# end Router#
This example shows how to verify the configuration change:

Router# show vtp interface gigabitethernet 3/5 Interface VTP Status -----------------------------------GigabitEthernet3/5 disabled Router#
This example shows how to verify the interface:

Router# show vtp interface Interface VTP Status -----------------------------------GigabitEthernet3/1 enabled GigabitEthernet3/2 enabled GigabitEthernet3/3 enabled GigabitEthernet3/4 enabled GigabitEthernet3/5 disabled GigabitEthernet3/6 enabled ...
21-17
Configuring VTP
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 Number of config digest errors Number of V1 summary errors VTP pruning statistics: Trunk Summary advts received from non-pruning-capable device ---------------- ---------------- ---------------- --------------------------Fa5/8 43071 42766 5 Join Transmitted Join Received
: : : : : : : : :
7 5 0 997 13 3 0 0 0
Tip
21-18
OL-13013-06
C H A P T E R
22
Configuring VLANs
This chapter describes how to configure VLANs in Cisco IOS Release 12.2SX.
Note
Tip

Understanding VLANs, page 22-1 VLAN Configuration Guidelines and Restrictions, page 22-3 Configuring VLANs, page 22-3
Understanding VLANs
The following sections describe how VLANs work:

VLAN Overview, page 22-2 VLAN Ranges, page 22-2
22-1
Chapter 22 Understanding VLANs
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 27-2). Cisco IOS Release 12.2SX supports 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 22-1 describes the VLAN ranges.
Table 22-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 27-2).
22-2
OL-13013-06
Chapter 22
Configuring VLANs VLAN Configuration Guidelines and Restrictions
VLAN Configuration Guidelines and Restrictions

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

VLANs support a number of parameters that are not discussed in detail in this section. For complete information, see the Cisco IOS Master Command List, Release 12.2SX publication. If the switch is in VTP server or transparent mode (see the Configuring VTP section on page 21-10), 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 files. To display the VLAN configuration, enter the show vlan command. If the switch is in VLAN transparent mode, 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.
When the switch boots, if the VTP domain name and the VTP mode in the startup-config file 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. 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. Before you can create a VLAN, the switch must be in VTP server mode or VTP transparent mode. For information on configuring VTP, see Chapter 21, 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.
Configuring VLANs
These sections describe how to configure VLANs:

Configurable VLAN Parameters, page 22-4 Ethernet VLAN Default Parameters, page 22-4 VLAN Locking, page 22-4 Creating or Modifying an Ethernet VLAN, page 22-5 Assigning a Layer 2 LAN Interface to a VLAN, page 22-6 Configuring the Internal VLAN Allocation Policy, page 22-7 Configuring VLAN Translation, page 22-7 Mapping 802.1Q VLANs to ISL VLANs, page 22-10 Saving VLAN Information, page 22-11
22-3
Chapter 22 Configuring VLANs
Configuring VLANs
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
Ethernet VLAN Default Parameters

VLAN ID: 1; range: 14094 VLAN name:

VLAN 1: default Other VLANs: VLANvlan_ID
802.10 SAID: 10vlan_ID; range: 100001104094 MTU size: 1500; range: 150018190 Translational bridge 1: 0; range: 01005 Translational bridge 2: 0; range: 01005 VLAN state: active: active, suspend Pruning eligibility:
VLANs 21001 are pruning eligible VLANs 10064094 are not pruning eligible
VLAN Locking
Release 12.2(33)SXH and later releases support the VLAN locking feature, which provides an extra level of verification to ensure that you have configured the intended VLAN. When VLAN locking is enabled, you need to specify the VLAN name when you change a port from one VLAN to another. This feature affects switchport commands (in interface configuration mode) that specify the VLANs or private VLANs for access and trunk ports.
22-4
OL-13013-06
Chapter 22
Configuring VLANs Configuring VLANs
For additional information about how to configure access and trunk ports with VLAN locking enabled, see the Configuring LAN Interfaces for Layer 2 Switching section on page 16-6. For additional information about how to configure ports in private VLANs with VLAN locking enabled, see the Configuring Private VLANs section on page 23-11. By default, the VLAN locking is disabled. To enable VLAN locking, perform this task: Command
Step 1 Step 2
Router(config)# vlan port provisioning Router# show vlan port provisioning
Purpose Enables VLAN locking. Verifies the VLAN locking status (enabled or disabled).
Creating or Modifying an Ethernet VLAN

User-configured VLANs have unique IDs from 1 to 4094, except for reserved VLANs (see Table 22-1 on page 22-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 Ethernet VLAN Default Parameters section on page 22-4 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
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
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).
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
When you create or modify an Ethernet VLAN, note the following information:

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.
22-5
Configuring VLANs
When deleting VLANs, note the following information:

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.
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#
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 16-6.
22-6
OL-13013-06
Chapter 22
Configuring the Internal VLAN Allocation Policy

For more information about VLAN allocation, see the VLAN Ranges section on page 22-2.
Note
The internal VLAN allocation policy is applied only following a reload. To configure the internal VLAN allocation policy, perform this task:
Command
Router(config)# vlan internal allocation policy {ascending | descending} Router(config)# end Router# reload
Purpose Configures the internal VLAN allocation policy. Exits configuration mode. Applies the new internal VLAN allocation policy.
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
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 22-8 Configuring VLAN Translation on a Trunk Port, page 22-9 Enabling VLAN Translation on Other Ports in a Port Group, page 22-10
Note
To avoid spanning tree loops, be careful not to misconfigure the VLAN translation feature.
22-7
Configuring VLANs
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. For the modules that support VLAN translation, Table 22-2 lists:
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
Table 22-2
Module Support for VLAN Translation
Product Number WS-SUP720-3BXL WS-SUP720-3B WS-SUP720 WS-SUP32-10GE WS-SUP32-GE WS-X6K-S2U-MSFC2 WS-X6K-S2-MSFC2 WS-X6502-10GE WS-X6704-10GE WS-X6708-10GE WS-X6716-10GE WS-X6724-SFP WS-X6816-GBIC WS-X6516A-GBIC WS-X6516-GBIC
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
3 9 2 1 4 8 16 24 16 16 16
2 1 1 1 4 8 16 2 2 2 2
1, 23 19 12 1 port in 1 group 1 port in each group 1 port in each group 1 port in each group 112 1324 18 916 18 916 18 916
16 16 32 32 128 16 16 128 32 32 32
ISL 802.1Q ISL 802.1Q 802.1Q 802.1Q ISL 802.1Q ISL 802.1Q 802.1Q ISL 802.1Q 802.1Q 802.1Q 802.1Q
22-8
OL-13013-06
Chapter 22
Table 22-2
Module Support for VLAN Translation (continued)
Product Number WS-X6748-GE-SFP
Port Ranges Number of Number of per Ports Port Groups Port Group 48 4 123, odd 224, even 2547, odd 2648, even 112 1324 2536 3748 18 916 124 148 148
Translations per VLAN Translation Port Group Trunk-Type Support 128 ISL 802.1Q
WS-X6748-GE-TX
48
128
ISL 802.1Q
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 16-10.
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
Step 4 Step 5
Router(config-if)# end Router# show interface type1 slot/port vlan mapping
Exits configuration mode. Verifies the VLAN mapping.
22-9
Configuring VLANs
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
1
Purpose
slot/port
Selects the LAN port to configure. Enables VLAN translation. Exits configuration mode. Verifies the VLAN mapping.
Router(config-if)# switchport vlan mapping enable Router(config-if)# end Router# show interface type slot/port vlan mapping 1. type = fastethernet, gigabitethernet, or tengigabitethernet
1
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. 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.
22-10
OL-13013-06
Chapter 22
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 switch. Make sure that 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. Exits configuration mode. Verifies the VLAN mapping.
Step 2 Step 3
Router(config)# end Router# show vlan
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
22-11
Configuring VLANs
22-12
OL-13013-06
C H A P T E R
23

This chapter describes how to configure private VLANs in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Private VLANs, page 23-1 Private VLAN Configuration Guidelines and Restrictions, page 23-6 Configuring Private VLANs, page 23-11 Monitoring Private VLANs, page 23-17
Understanding Private VLANs

These sections describe how private VLANs work:

Private VLAN Domains, page 23-2 Private VLAN Ports, page 23-3 Primary, Isolated, and Community VLANs, page 23-3 Private VLAN Port Isolation, page 23-4 IP Addressing Scheme with Private VLANs, page 23-4 Private VLANs Across Multiple Switches, page 23-5 Private VLAN Interaction with Other Features, page 23-5
23-1
Chapter 23 Understanding Private VLANs
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 23-1).
Figure 23-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.
23-2
116083
OL-13013-06
Chapter 23
Configuring Private VLANs Understanding Private VLANs
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.
23-3
Chapter 23 Understanding Private VLANs
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.
23-4
OL-13013-06
Chapter 23
Configuring Private VLANs Understanding Private VLANs
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 23-2.)
Figure 23-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 versions 1 and 2 do 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. VTP version 3 does support private VLANs, so you do not need to manually configure private VLANs on all switches in the Layer 2 network.
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 23-6 Private VLANs and SVIs, page 23-6
See also the Private VLAN Configuration Guidelines and Restrictions section on page 23-6.
23-5
Chapter 23 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 23-7 Private VLAN Port Configuration, page 23-9 Limitations with Other Features, page 23-9
23-6
OL-13013-06
Chapter 23
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 21, 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 Configurable VLAN Parameters section on page 22-4. 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. In VTP versions 1 and 2, VTP does not propagate a private VLAN configuration and you must configure private VLANs on each device where you want private VLAN ports. In VTP version 3, VTP does propagate private VLAN configurations automatically. You cannot configure VLAN 1 or VLANs 1002 to 1005 as primary or secondary VLANs. Extended VLANs (VLAN IDs 1006 to 4094) cannot 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 48, Configuring Port ACLs and 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 40, Configuring PFC QoS.)
23-7
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 49-18. 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. You can configure sticky ARP on a per-interface basis. For information about configuring sticky ARP, see the Configuring Sticky ARP section on page 49-18. 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 48-15.) 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 44, 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.
23-8
OL-13013-06
Chapter 23
Configuring Private VLANs Private VLAN Configuration Guidelines and Restrictions
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 65, Configuring Local SPAN, RSPAN, and
ERSPAN.
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 28, 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
23-9
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. Do not configure a remote SPAN (RSPAN) VLAN as a private VLAN primary or secondary VLAN. For more information about SPAN, see Chapter 65, 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. 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. When you enter the shutdown or the no shutdown command on the primary VLAN, the corresponding secondary VLANs also are shutdown or brought up. These restrictions apply when you configure groups of 12 ports as secondary ports: 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. 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.
23-10
OL-13013-06
Chapter 23
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 23-11 Associating Secondary VLANs with a Primary VLAN, page 23-12 Mapping Secondary VLANs to the Layer 3 VLAN Interface of a Primary VLAN, page 23-13 Configuring a Layer 2 Interface as a Private VLAN Host Port, page 23-15 Configuring a Layer 2 Interface as a Private VLAN Promiscuous Port, page 23-16
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.
23-11
Chapter 23 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.
Router(config-vlan)# private-vlan association {secondary_vlan_list | add secondary_vlan_list | remove secondary_vlan_list} Router(config-vlan)# no private-vlan association
23-12
OL-13013-06
Chapter 23
Command
Step 3 Step 4
Router(config-vlan)# end Router# show vlan private-vlan [type]
Purpose Exits VLAN configuration mode. Verifies the configuration.
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:
23-13
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. Exits configuration mode. Verifies the configuration.
Router(config-if)# private-vlan mapping {secondary_vlan_list | add secondary_vlan_list | remove secondary_vlan_list} Router(config-if)# [no] private-vlan mapping
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#
23-14
OL-13013-06
Chapter 23
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.
Step 3 Step 4
Router(config-if)# switchport mode private-vlan {host | promiscuous} Router(config-if)# switchport private-vlan host-association primary_vlan_ID secondary_vlan_ID
Configures the Layer 2 port as a private VLAN host port. Associates the Layer 2 port with a private VLAN.
Note
Router(config-if)# no switchport private-vlan host-association
Clears the association. Exits configuration mode.
Step 5 Step 6
Router(config-if)# end Router# show interfaces [type switchport 1.

1
slot/port]
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
23-15
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.
Step 3 Step 4
Router(config-if)# switchport mode private-vlan {host | promiscuous} Router(config-if)# switchport private-vlan mapping primary_vlan_ID {secondary_vlan_list | add secondary_vlan_list | remove secondary_vlan_list}
Configures the Layer 2 port as a private VLAN promiscuous port. Maps the private VLAN promiscuous port to a primary VLAN and to selected secondary VLANs.
Note
Router(config-if)# no switchport private-vlan mapping
Clears all mapping between the private VLAN promiscuous port and the primary VLAN and any secondary VLANs. Exits configuration mode. Verifies the configuration.
Step 5 Step 6
Router(config-if)# end Router# show interfaces [type switchport 1.

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. If VLAN locking is enabled, enter VLAN names instead of VLAN numbers in the secondary_vlan_list. When entering a range of VLAN names, you must leave spaces between the VLAN names and the dash. 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.
23-16
OL-13013-06
Chapter 23
Configuring Private VLANs Monitoring Private VLANs
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
Monitoring Private VLANs

Table 23-1 shows the privileged EXEC commands for monitoring private VLAN activity.
Table 23-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/0/1, Gi3/0/1, Gi3/0/2 10 502 community Fa2/0/11, Gi3/0/1, Gi3/0/4 10 503 non-operational
23-17
Chapter 23 Monitoring Private VLANs
Tip
23-18
OL-13013-06
C H A P T E R
24

This chapter describes how to configure the private hosts feature in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Private Hosts, page 24-1 Configuration Guidelines and Limitations, page 24-5 Configuring Private Hosts, page 24-7
Understanding Private Hosts

Service providers typically deliver triple-play services (voice, video, and data) using three different VLANs over a single physical interface for each end user. The service infrastructure would be simpler and more scalable if the service provider could deploy a single set of VLANs to multiple end users for the same set of services, but the service provider must be able to isolate traffic between the users (hosts) at Layer 2. The private hosts feature provides this isolation, allowing VLAN sharing among multiple end users. The private hosts feature provides these key benefits:

Isolates traffic among hosts (subscribers) that share the same VLAN ID. Reuses VLAN IDs across different subscribers, which improves VLAN scalability by making better use of the 4096 VLANs allowed. Prevents media access control (MAC) address spoofing to prevent denial of service (DOS) attacks.
24-1
Chapter 24 Understanding Private Hosts
The private hosts feature uses protocol-independent port-based access control lists (PACLs) to provide Layer 2 isolation between hosts on trusted ports within a strictly Layer 2 domain. The PACLs isolate the hosts by imposing Layer 2 forwarding constraints on the switch ports. The sections that follow provide more detail about the following private hosts concepts:

Isolating Hosts in a VLAN, page 24-2 Restricting Traffic Flow (Using Private Hosts Port Mode and PACLs), page 24-3 Port ACLs, page 24-5
Isolating Hosts in a VLAN

By isolating the hosts, a service provider can use a single set of VLANs to deliver the same set of broadband or metro Ethernet services to multiple end users while ensuring that none of the hosts in the VLAN can communicate directly with each other. For example, VLAN 10 can be used for voice traffic, VLAN 20 for video traffic, and VLAN 30 for data traffic. When the switch is used as a Digital Subscriber Line Access Multiplexer (DSLAM) gigabit Ethernet aggregator, the DSLAM is connected to the switch through a trunk port that can carry data for multiple VLANs. The service provider uses a single physical port and a single set of VLANs to deliver the same set of services to different end users (isolated hosts). A separate VLAN is used for each service (voice, video, and data). Figure 24-1 shows an example of triple-play services being delivered from the switch to multiple end users attached to a DSLAM. In the figure, note the following:

A single trunk link between the switch and the DSLAM carries traffic for all three VLANs. Virtual circuits (VCs) deliver the VLAN traffic from the DSLAM to individual end users.
VC to VLAN Mapping
Figure 24-1
Cisco 6500 Switch
Trunk
1 2 3
DSLAM
Host Host
Host Host
Host Host
PC
24-2
182527
TV
Phone
OL-13013-06
Chapter 24
Configuring Private Hosts Understanding Private Hosts
The trunk link carries:

2 3
One voice VLAN One video VLAN One data VLAN
The DSLAM maps voice, video, and data traffic between VLANs and VCs. Individual VCs carry voice, video, and data traffic between the DSLAM and each host.
Restricting Traffic Flow (Using Private Hosts Port Mode and PACLs)
The private hosts feature uses PACLs to restrict the type of traffic that is allowed to flow through each of the ports configured for private hosts. A ports mode (specified when you enable private hosts on the port) determines what type of PACL is applied to the port. Each type of PACL restricts the traffic flow for a different type of traffic (for example, from content servers to isolated hosts, from isolated hosts to servers, and traffic between isolated hosts). The following list describes the port modes used by the private hosts feature (see Figure 24-2):
IsolatedPorts connected to the DSLAMs that the end users (isolated hosts) are connected to. The hosts on the VLANs on these ports need to be isolated from each other. Hosts connected through these ports are allowed to pass unicast traffic to upstream devices only. PromiscuousPorts that face the core network or the Broadband Remote Access Server (BRAS) devices and multicast servers that are providing the broadband services. MixedPorts that interconnect switches. These ports can function as either isolated ports or promiscuous ports, depending on Spanning Tree Protocol (STP) topology changes. These ports allow unicast traffic to upstream devices (such as a BRAS or multicast server) only. Broadcast traffic at the ingress of the service provider network is redirected to BRAS and multicast servers (such as video servers). All unicast traffic between access switches (switches connected to each other) is blocked except for traffic directed toward a BRAS or a multicast server. The unknown unicast flood blocking (UUFB) feature is used to block unknown unicast traffic on DSLAM-facing ports.
The private hosts feature restricts traffic flow in these ways:

Figure 24-2 shows the different types of port modes (isolated, promiscuous, and mixed) used in a private hosts configuration.
24-3
Chapter 24 Understanding Private Hosts
Figure 24-2
Private Hosts Port Types (Modes)
Video servers
Video servers
BRAS
Access router (network edge)
1 2
Cisco 6500 Switch Cisco 6500 Switch
3
DSLAM DSLAM
Host Host
Host Host
Host Host
Host Host
1 2
Promiscuous ports Mixed ports
Permit all traffic from a BRAS to hosts. Permit broadcast traffic from a BRAS. Redirect broadcast traffic from hosts to promiscuous and mixed-mode ports. Permit traffic from a BRAS to hosts and from hosts to a BRAS. Deny all other host to host traffic.
Isolated ports
Permit unicast traffic from host to a BRAS only; block unicast traffic between ports. Redirect all broadcast traffic from host to a BRAS. Deny traffic from a BRAS (to prevent spoofing). Permit multicast traffic (IPv4 and IPv6).
Note
In this description of port types, the term BRAS represents an upstream devices such as a BRAS, a multicast server (such as a video server), or a core network device that provides access to these devices.
24-4
182528
OL-13013-06
Chapter 24
Configuring Private Hosts Configuration Guidelines and Limitations
Port ACLs
The private hosts feature creates several types of port ACLs (PACLs) to impose Layer 2 forwarding constraints on switch ports. The software creates PACLs for the different types of private hosts ports based on the MAC addresses of the content servers providing broadband services and the VLAN IDs of the isolated hosts to deliver those services to. You specify the mode in which each private hosts port is to operate and the software applies the appropriate PACL to the port based on the ports mode (isolated, promiscuous, or mixed). The following are examples of the different types of PACLs that are used by the private hosts feature.
Isolated Hosts PACL
This example shows a PACL for isolated ports:

deny host BRAS_MAC any permit any host BRAS_MAC redirect any host FFFF.FFFF.FFFF to LTLIndex 6 permit any 0100.5E00.0000/0000.007F.FFFF permit any 3333.0000.0000/000.FFFF.FFFF deny any any
Promiscuous Port PACL
This example shows a PACL for promiscuous ports:

permit host BRAS_MAC any deny any any
Mixed Port PACL
This example shows a PACL for mixed ports:

permit host BRAS_MAC ffff.ffff.ffff redirect any host FFFF.FFFF.FFFF to LTLIndex 6 permit host BRAS_MAC any permit any host BRAS_MAC deny any any
Configuration Guidelines and Limitations

When you configure the private hosts feature, observe the following guidelines and limitations:

The SIP-400 and Enhanced FlexWAN modules do not support private hosts. Private hosts and private VLANs cannot both be configured on the same port (interface). Both features can coexist on the switch, but each feature must be configured on different ports. Private hosts is an end-to-end feature. You must enable the feature on all of the switches between the DSLAMs and an upstream device such as a BRAS or a multicast server. Only trusted ports currently can be configured as isolated ports. The private hosts feature is supported on Layer 2 interfaces that are configured as switch ports (802.1Q or ISL trunk ports). The private hosts feature is supported on port-channel interfaces (EtherChannel, Fast EtherChannel, and Gigabit EtherChannel). You must enable private hosts on the port-channel interface; you cannot enable the feature on member ports. DAI and DHCP snooping cannot be enabled on a private hosts port unless all of the VLANs on the port are configured for snooping.
24-5
Chapter 24 Configuration Guidelines and Limitations
ACL Guidelines
The following configuration guidelines and limitations apply to access control lists (ACLs):
This release of the private hosts feature uses protocol-independent MAC ACLs. Do not apply IP-based ACLs to any port configured for private hosts or you will defeat the private hosts feature (because the switch will not be able to apply a private hosts MAC ACL to the port).
You can configure the following interface types for protocol-independent MAC ACL filtering:
VLAN interfaces with no IP address Physical LAN ports that support EoMPLS Logical LAN subinterfaces that support EoMPLS
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). Ingress traffic that is permitted or denied by a protocol-independent MAC ACL is processed by egress interfaces as MAC-layer traffic. You cannot apply egress IP ACLs to traffic permitted or denied by a MAC ACL on an interface configured for protocol-independent MAC ACL filtering. 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 PFC3. Protocol-independent MAC ACL filtering supports microflow policing when the permitted traffic is routed in software by the route processor (RP). Do not apply any VACLs or RACLs to a port configured for private hosts. To prevent any existing VLAN ACLs (VACLs) and routing ACLs (RACLs) from interfering with a PACL, configure the access-group mode prefer port command on the port.
VLANs on the Trunk Port

The following guidelines and limitations apply to VLANs:

You can enable IGMP snooping on VLANs that use trunk ports configured for private hosts. You cannot enable IP multicast on a VLAN that uses a trunk port that is configured for private hosts. Because PACLs operate in override mode on trunk ports, you cannot apply VLAN-based features to switch ports. The Multicast VLAN Registration (MVR) feature can coexist with private hosts as long as the multicast source exists on a promiscuous port.
Interaction with Other Features

The private hosts feature interacts with other features that are configured on the switch as follows:
Private hosts do not affect Layer 2-based services such as MAC limiting, unicast flood protection (UFP), or unknown unicast flood blocking (UUFB).
24-6
OL-13013-06
Chapter 24
Configuring Private Hosts Configuring Private Hosts
The private hosts features does not affect IGMP snooping. However, if IGMP snooping is globally disabled, IGMP control packets will be subject to ACL checks. To permit IGMP control packets, the private hosts software adds a multicast permit statement to the PACLs for isolated hosts. This operation occurs automatically and no user intervention is required. Port security can be enabled on isolated ports to provide added security to those ports. When enabled on promiscuous or mixed-mode ports, the port security feature may restrict a change in source port for an upstream device (such as a BRAS or a multicast server). When enabled on an access port, 802.1X is not affected by the private hosts feature.
Spoofing Protection
The private hosts feature prevents MAC address spoofing but does not validate the customer MAC or IP address. To prevent MAC address spoofing, the private hosts feature does the following:

Uses a static MAC address for a BRAS or a multicast server. Disables learning in the Layer 2 forwarding table. Alerts the switch software when a BRAS or multicast server moves from one source port to another. The software then validates the move and updates the Layer 2 forwarding table.
Multicast Operation
Multicast traffic that originates from an upstream device (such as a BRAS or a multicast server) is always permitted. In addition, the private hosts PACLs are not applied to multicast control packets (such as IGMP query and join requests). This operation allows isolated hosts to participate in multicast groups, respond to IGMP queries, and receive traffic from any groups of interest. Multicast traffic that originates from a host is dropped by the private hosts PACLs. However, if other hosts need to receive multicast traffic originating from a host, the private hosts feature adds a multicast permit entry to the PACLs.

The following sections provide information about configuring the private hosts feature in Cisco IOS Release 12.2SX:

Configuration Summary, page 24-8 Detailed Configuration Steps, page 24-9 Configuration Examples, page 24-10
24-7
Chapter 24 Configuring Private Hosts
Configuration Summary
The following is a summary of the steps to configure the private hosts feature. Detailed configuration instructions are provided in the next section.
1.
Determine which switch ports (interfaces) to use for the private hosts feature.
You can configure the feature on switch ports (802.1Q or ISL trunk ports) You can configure the feature on port-channel interfaces. Private hosts must be enabled on the
port-channel interface; you cannot enable the feature on member ports.

2. 3. 4.
Configure each port (interface) for normal, non-private hosts service. Configure the access-group mode prefer port command on the port. You can configure the VLANs at this step or later. Determine which VLAN or set of VLANs will be used to deliver broadband services to end users. The private hosts feature will provide Layer 2 isolation among the hosts in these VLANs. Identify the MAC addresses of all of the BRASs and multicast servers that are being used to provide broadband services to end users (isolated hosts).
Note
If a server is not connected directly to the switch, determine the MAC address of the core network device that provides access to the server. (Optional) If you plan to offer different types of broadband service to different sets of isolated hosts, create multiple MAC and VLAN lists.
Each MAC address list identifies a server or set of servers providing a particular type of service. Each VLAN list identifies the isolated hosts to deliver that service to.
5.
6.
Configure promiscuous ports and specify a MAC and VLAN list to identify the server and receiving hosts for a particular type of service.
Note
You can specify multiple MAC and VLAN combinations to allow different types of services to be delivered to different sets of hosts. For example, the BRAS at xxxx.xxxx.xxxx could be used to deliver a basic set of services over VLANs 20, 25, and 30, and the BRAS at yyyy.yyyy.yyyy could be used to deliver a premium set of services over VLANs 5, 10, and 15. Globally enable private hosts. Enable private hosts on individual ports (interfaces) and specify the mode in which the port is to operate. To determine port mode, you need to know if the port faces upstream (toward content servers or core network), faces downstream (toward DSLAM and isolated hosts), or is connected to another switch (typically, in a ring topology). See the Restricting Traffic Flow (Using Private Hosts Port Mode and PACLs) section on page 24-3.
7. 8.
After you enable the feature on individual ports, the switch is ready to run the private hosts feature. The private hosts software uses the MAC and VLAN lists you defined to create the isolated, promiscuous, and mixed-mode PACLs for your configuration. The software then applies the appropriate PACL to each private hosts port based on the ports mode.
24-8
OL-13013-06
Chapter 24
Detailed Configuration Steps

To configure the private hosts feature, perform the following steps. These steps assume that you have already configured the Layer 2 interfaces that you plan for private hosts.
Note
You can configure private hosts only on switch ports (802.1Q or ISL trunk ports) or EtherChannel ports. In addition, you must enable private hosts on all of the switches between the DSLAMs and upstream devices.
Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# private-hosts mac-list mac-list-name mac-address [remark device-name | comment]
Purpose Enters global configuration mode. Creates a list of MAC addresses that identify the BRAS and multicast servers providing broadband services.

mac-list-name specifies a name to assign to this list of content servers. mac-address identifies the BRAS or multicast server (or set of servers) providing a particular broadband service or set of services. remark allows you to specify an optional device name or comment to assign to this MAC list.
Specify the MAC address of every content server being used to deliver services. If you plan to offer different types of services to different sets of hosts, create a separate MAC list for each server or set of servers providing a particular service.
Note
If a server is not directly connected to the switch, specify the MAC address of the core network device that provides access to the server.
Step 3
Router(config)# private-hosts vlan-list vlan-IDs
Creates a list of the VLANs (vlan-IDs) whose hosts need to be isolated so that the hosts can receive broadband services. Create separate VLAN lists if you plan to offer particular services to different sets of hosts. Otherwise, all of the broadband services will be delivered to all isolated hosts.
24-9
Command or Action
Step 4
Router(config)# private-hosts promiscuous mac-list-name [vlan-list vlan-IDs]
Purpose Identifies the content servers for broadband services and the end users (isolated hosts) to which to deliver the services.
mac-list-name specifies the name of the MAC address lists that identifies the BRAS or multicast server (or set of servers) providing a particular type of broadband service or set of services. vlan-IDs identifies the VLAN or set of VLANs whose hosts are to receive services from the above servers. If no VLAN list is specified, the software uses the global VLAN list (configured in Step 3). You can enter this command multiple times to configure multiple MAC and VLAN combinations, each defining the server and receiving hosts for a particular type of service.
Note
Router(config)# private-hosts Router(config)# interface interface
Globally enables private hosts on the switch. Selects the switch port (802.1Q or ISL trunk port) or EtherChannel port to enable for private hosts. Specifies that any existing VACLs or RACLs on the port will be ignored. Enables private hosts on the port. Use one of the following keywords to define the mode that the port is to operate in:
Router(config-if)# access-group mode prefer port Router(config-if)# private-hosts mode {promiscuous | isolated | mixed}
promiscuousUpstream-facing ports that connect to broadband servers (BRAS, multicast, or video) or to core network devices providing access to the servers. isolatedPorts that connect to DSLAMs. mixedPorts that connect to other switches, typically in a ring topology. You must perform this step on each port being used for private hosts.
Note Step 9
Router(config-if)# end
Exits interface and global configuration modes and returns to privileged EXEC mode. Private Hosts configuration is complete.
Configuration Examples
The following example creates a MAC address list and a VLAN list and isolates the hosts in VLANs 10, 12, 15, and 200 through 300. The BRAS-facing port is made promiscuous and two host-connected ports are made isolated:
Router# configure terminal Router(config)# private-hosts mac-list BRAS_list 0000.1111.1111 remark BRAS_SanJose Router(config)# private-hosts vlan-list 10,12,15,200-300 Router(config)# private-hosts promiscuous BRAS_list vlan-list 10,12,15,200-300 Router(config)# private-hosts Router(config)# interface gig 4/2 Router(config-if)# private-hosts mode promiscuous Router(config-if)# exit
24-10
OL-13013-06
Chapter 24
Router(config)# interface gig 5/2 Router(config-if)# private-hosts mode isolated Router(config-if)# exit Router(config)# interface gig 5/3 Router(config-if)# private-hosts mode isolated Router(config-if)# end Router#
The following example shows the interface configuration of a private hosts isolated port:
Router# show run interface gig 5/2 Building configuration... Current configuration : 200 bytes ! interface GigabitEthernet5/2 switchport switchport trunk encapsulation dot1q switchport mode trunk access-group mode prefer port private-hosts mode isolated end
The following example shows the interface configuration of a private hosts promiscuous port:
Router# show run interface gig 4/2 Building configuration... Current configuration : 189 bytes ! interface GigabitEthernet4/2 switchport switchport access vlan 200 switchport mode access private-hosts mode promiscuous end private-hosts private-hosts vlan-list 200 private-hosts promiscuous bras-list private-hosts mac-list bras-list 0000.1111.1111 remark BRAS-SERVER
Tip
24-11
24-12
OL-13013-06
C H A P T E R
25
Configuring IEEE 802.1Q Tunneling

This chapter describes how to configure IEEE 802.1Q tunneling in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_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.
Tip

Understanding 802.1Q Tunneling, page 25-1 802.1Q Tunneling Configuration Guidelines and Restrictions, page 25-3 Configuring 802.1Q Tunneling, page 25-6
Understanding 802.1Q Tunneling

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.
25-1
Chapter 25 Understanding 802.1Q Tunneling
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 25-1 on page 25-2 and Figure 25-2 on page 25-3.
Figure 25-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 trunk port 802.1Q trunk 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
25-2
OL-13013-06
Chapter 25
Configuring IEEE 802.1Q Tunneling 802.1Q Tunneling Configuration Guidelines and Restrictions
Figure 25-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.
25-3
79831
Chapter 25 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)
25-4
OL-13013-06
Chapter 25
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 26, 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. 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
The following configuration guidelines are required for your Layer 2 protocol tunneling configuration:
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
25-5
Chapter 25 Configuring 802.1Q Tunneling
Configuring 802.1Q Tunneling

These sections describe 802.1Q tunneling configuration:

Configuring 802.1Q Tunnel Ports, page 25-6 Configuring the Switch to Tag Native VLAN Traffic, page 25-7
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

Router(config-if)# switchport mode dot1q-tunnel Router(config-if)# end Router# show dot1q-tunnel [{interface type interface-number}] 1.
1
Configures the Layer 2 port as a tunnel port. Exits configuration mode. Verifies the configuration.
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
25-6
OL-13013-06
Chapter 25
Configuring IEEE 802.1Q Tunneling Configuring 802.1Q Tunneling
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. On ports where you enter the no switchport trunk native vlan tag interface command, the function of the vlan dot1q tag native global command is disabled. These sections describe how to configure the switch to tag native VLAN traffic:

Configuring the Switch to Tag Native VLAN Traffic Globally, page 25-7 Configuring Ports Not to Tag Native VLAN Traffic, page 25-7
Configuring the Switch to Tag Native VLAN Traffic Globally

With Release 12.2(33)SXH and later releases, to configure the switch to tag traffic in the native VLAN globally, perform this task: Command
Router(config)# vlan dot1q tag native
Purpose Configures the switch to tag native VLAN traffic globally. Exits configuration mode. Verifies the configuration.
Router(config)# end Router# show vlan dot1q tag native | include globally
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 | include globally dot1q native vlan tagging is enabled globally Router(config)#
Configuring Ports Not to Tag Native VLAN Traffic

When the switch is configured to tag native VLAN traffic globally, you can disable native VLAN tagging on a per-port basis. To configure a port not to tag traffic in the native VLAN, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
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 port.
25-7
Chapter 25 Configuring 802.1Q Tunneling
Command
Router(config-if)# no switchport trunk native vlan tag Router(config-if)# end Router# show interface type1 interface-number | include tagging 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Configures the Layer 2 port not to tag native VLAN traffic. Exits configuration mode. Verifies the configuration.
Note
The switchport trunk native vlan tag interface command does not enable native VLAN tagging unless the switch is configured to tag native VLAN traffic globally. This example shows how to configure Gigabit Ethernet port 1/4 to tag traffic in the native VLAN and verify the configuration:
Router# configure terminal Router(config)# interface gigabitethernet 1/4 Router(config-if)# switchport trunk native vlan tag Router(config-if)# end Router# show interface gigabitethernet 1/4 switchport | include tagging Administrative Native VLAN tagging: enabled Operational Native VLAN tagging: disabled Router#
Tip
25-8
OL-13013-06
C H A P T E R
26
Configuring Layer 2 Protocol Tunneling

This chapter describes how to configure Layer 2 protocol tunneling in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_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 Layer 2 protocol tunneling.
Tip

Understanding Layer 2 Protocol Tunneling, page 26-1 Configuring Support for Layer 2 Protocol Tunneling, page 26-2
Understanding Layer 2 Protocol Tunneling

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 26-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.
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 26-1) builds a spanning tree
26-1
Chapter 26 Configuring Support for Layer 2 Protocol Tunneling
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 26-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 disabled 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.
26-2
OL-13013-06
Chapter 26
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 | lldp | stp | vtp] Router(config-if)# l2protocol-tunnel drop-threshold {[cdp | lldp | stp | vtp] packets}
Configures the Layer 2 port as a Layer 2 protocol tunnel port for all protocols or only the specified protocol. (Optional) Configures the port as a Layer 2 protocol tunnel port and sets a drop threshold for all protocols or only the specified protocol. (Optional) Configures the port as a Layer 2 protocol tunnel port and sets a shutdown threshold for all protocols or only the specified protocol. Exits configuration mode. Verifies the configuration.
Router(config-if)# l2protocol-tunnel shutdown-threshold {[cdp | lldp | stp | vtp] packets}
Step 4 Step 5
Router(config)# end Router# show l2protocol-tunnel [interface type1 slot/port|summary] 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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 one-second period. If a drop threshold is not specified, the value is 0 (drop 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). If you specify both a drop threshold and a shutdown threshold for the port, packets exceeding the drop threshold will not be forwarded but will be counted toward the shutdown threshold.
Note
See 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
This example shows how to configure Layer 2 protocol tunneling and drop and shu tdown thresholds on port 5/1 for CDP, STP, and VTP, and verify the configuration:
26-3
Chapter 26 Configuring Support for Layer 2 Protocol Tunneling
Router(config)# interface fastethernet 5/1 Router(config-if)# switchport Router(config-if)# l2protocol-tunnel shutdown-threshold Router(config-if)# l2protocol-tunnel shutdown-threshold Router(config-if)# l2protocol-tunnel shutdown-threshold Router(config-if)# l2protocol-tunnel drop-threshold vtp Router(config-if)# end Router# show l2protocol-tunnel summary COS for Encapsulated Packets: 5 Drop Threshold for Encapsulated Packets: 0 Port Shutdown Threshold (cdp/lldp/stp/vtp) -------- ------------ ------------------Fa5/1 -- -- -- --- 400/----/ 400/ 400 Router# Protocol
cdp 400 stp 400 vtp 400 200
Drop Status Threshold (cdp/lldp/stp/vtp) -------------------- -------------/----/----/ 200 down(trunk)
This example shows how to display counter information for port 5/1:
Router# show l2protocol-tunnel interface fastethernet 5/1 COS for Encapsulated Packets: 5 Port Protocol Thresholds Counters Shutdown Drop Encap Decap Drop ----------- -------- --------- --------- --------- --------- --------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 Router(config-if)# no l2protocol-tunnel shutdown-threshold Router(config-if)# no l2protocol-tunnel shutdown-threshold Router(config-if)# no l2protocol-tunnel drop-threshold vtp 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 COS for Encapsulated Packets: 5 Drop Threshold for Encapsulated Packets: 0 Port Shutdown Threshold (cdp/lldp/stp/vtp) -------- ------------ ------------------Router# Protocol cdp 400 stp 400 vtp 400 200
Drop Status Threshold (cdp/lldp/stp/vtp) -------------------- ----------
This example shows how to clear Layer 2 protocol tunneling port counters:
Router# clear l2protocol-tunnel counters Router#
Tip
26-4
OL-13013-06
C H A P T E R
27

This chapter describes how to configure the Spanning Tree Protocol (STP) and Multiple Spanning Tree (MST) protocol in Cisco IOS Release 12.2SX.
Note
Tip

Understanding STP, page 27-1 Understanding IEEE 802.1w RSTP, page 27-13 Understanding MST, page 27-18 Configuring STP, page 27-26 Configuring MST, page 27-38 Displaying the MST Configuration and Status, page 27-50
Note
For information on configuring the PortFast, UplinkFast, and BackboneFast STP enhancements, see Chapter 28, Configuring Optional STP Features.
Understanding STP
These sections describe how STP works:

STP Overview, page 27-2 Understanding the Bridge ID, page 27-2
27-1
Chapter 27 Understanding STP
Understanding Bridge Protocol Data Units, page 27-3 Election of the Root Bridge, page 27-4 STP Protocol Timers, page 27-4 Creating the Spanning Tree Topology, page 27-5 STP Port States, page 27-5 STP and IEEE 802.1Q Trunks, page 27-12
STP Overview
STP, the IEEE 802.1D bridge protocol, 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. In an extension known as per-VLAN spanning tree (PVST), Layer 2 Ethernet ports can use STP 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 27-3 Extended System ID, page 27-3 STP MAC Address Allocation, page 27-3
27-2
OL-13013-06
Chapter 27
Configuring STP and MST Understanding STP
Bridge Priority Value

The bridge priority is a 4-bit value when the extended system ID is enabled (see Table 27-1 on page 27-3 and the Configuring the Bridge Priority of a VLAN section on page 27-35).
Extended System ID
A 12-bit extended system ID field is part of the bridge ID (see Table 27-1 on page 27-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 27-29.
Table 27-1 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.
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
27-3
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.
STP Protocol Timers

Table 27-2 describes the STP protocol timers that affect STP performance.
27-4
OL-13013-06
Chapter 27
Table 27-2
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 27-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 27-1
DP DP DP RP B A DP RP D DP DP
Spanning Tree Topology
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.
STP Port States

These sections describe the STP port states:

STP Port State Overview, page 27-6 Blocking State, page 27-7
27-5
Listening State, page 27-8 Learning State, page 27-9 Forwarding State, page 27-10 Disabled State, page 27-11
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 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. 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
A Layer 2 LAN port moves through these five states as follows:

Figure 27-2 illustrates how a Layer 2 LAN port moves through the five states.
27-6
OL-13013-06
Chapter 27
Figure 27-2
Boot-up initialization
STP Layer 2 LAN Interface States
Blocking state
Listening state
Disabled state
Learning state
When you enable STP, every port, 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.
Blocking State
A Layer 2 LAN port in the blocking state does not participate in frame forwarding, as shown in Figure 27-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.
S5691
Forwarding state
27-7
Figure 27-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.
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 27-4 shows a Layer 2 LAN port in the listening state.
27-8
OL-13013-06
Chapter 27
Figure 27-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.
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 27-5 shows a Layer 2 LAN port in the learning state.
27-9
Figure 27-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.
Forwarding State
A Layer 2 LAN port in the forwarding state forwards frames, as shown in Figure 27-6. The Layer 2 LAN port enters the forwarding state from the learning state.
27-10
OL-13013-06
Chapter 27
Figure 27-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.
Disabled State
A Layer 2 LAN port in the disabled state does not participate in frame forwarding or STP, as shown in Figure 27-7. A Layer 2 LAN port in the disabled state is virtually nonoperational.
27-11
Figure 27-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. Interoperability with non-Cisco 802.1Q network devices is an extension of PVST known as PVST+. For more information on 802.1Q trunks, see Chapter 16, Configuring LAN Ports for Layer 2 Switching.
27-12
OL-13013-06
Chapter 27
Configuring STP and MST Understanding IEEE 802.1w RSTP
Understanding IEEE 802.1w RSTP

The 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 27-13 Rapid Convergence, page 27-14 Synchronization of Port Roles, page 27-15 Bridge Protocol Data Unit Format and Processing, page 27-16 Topology Changes, page 27-17 Rapid-PVST, page 27-18
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 27-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 27-3 provides a comparison of 802.1D and RSTP port states.
Table 27-3 Port State Comparison
Operational Status Enabled Enabled Enabled
STP Port State (IEEE 802.1D) Blocking Listening Learning
RSTP Port State Discarding Discarding Learning
Is Port Included in the Active Topology? No No Yes
27-13
Chapter 27 Understanding IEEE 802.1w RSTP
Table 27-3
Port State Comparison (continued)
Operational Status Enabled Disabled
STP Port State (IEEE 802.1D) Forwarding Disabled
RSTP Port State Forwarding Discarding
Is Port Included in the Active Topology? 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.
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 27-8, 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.
27-14
OL-13013-06
Chapter 27
Figure 27-8
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 27-9.
88760
27-15
Chapter 27 Understanding IEEE 802.1w RSTP
Figure 27-9
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 27-16 Processing Superior BPDU Information, page 27-17 Processing Inferior BPDU Information, page 27-17
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 27-4 describes the RSTP flag fields.
Table 27-4 RSTP BPDU Flags
Bit 0 1 23: 00 01 10 11 4
Function Topology change (TC) Proposal Port role: Unknown Alternate port or backup port Root port Designated port Learning
27-16
OL-13013-06
Chapter 27
Table 27-4
RSTP BPDU Flags (continued)
Bit 5 6 7
Function Forwarding 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.
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).
27-17
Chapter 27 Understanding MST
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.
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. In Cisco IOS Release 12.2(33)SXI and later releases, Rapid-PVST mode supports unidirectional link failure detection as described in the Detecting Unidirectional Link Failure section on page 27-25.
Understanding MST
These sections describe MST:

MST Overview, page 27-19 MST Regions, page 27-19 IST, CIST, and CST, page 27-20 Hop Count, page 27-23 Boundary Ports, page 27-23
27-18
OL-13013-06
Chapter 27
Configuring STP and MST Understanding MST
Standard-Compliant MST Implementation, page 27-24 Interoperability with IEEE 802.1D-1998 STP, page 27-26
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 the preceding sections in this chapter. For information about other spanning tree features such as Port Fast, UplinkFast, and root guard, see Chapter 28, 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 27-10 on page 27-22. 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. 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.
27-19
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 27-20 Spanning Tree Operation Within an MST Region, page 27-20 Spanning Tree Operations Between MST Regions, page 27-21 IEEE 802.1s Terminology, page 27-22
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 27-20 and the Spanning Tree Operations Between MST Regions section on page 27-21.
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 27-10 on page 27-22. 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.
27-20
OL-13013-06
Chapter 27
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 27-10 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.
27-21
Figure 27-10
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 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.
27-22
OL-13013-06
92720
MST Region 2
MST Region 3
Chapter 27
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 27-5 compares the IEEE standard and the Cisco prestandard terminology.
Table 27-5 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
27-23
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 27-24 Spanning Tree Interoperation Between Legacy and Standard-Compliant Switches, page 27-25 Detecting Unidirectional Link Failure, page 27-25
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.
27-24
OL-13013-06
Chapter 27
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 27-11 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 27-11 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

Using the dispute mechanism included in the IEEE 802.1D-2004 RSTP standard, the switch 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 (blocking) state because disrupting connectivity in case of inconsistency is preferable to opening a bridging loop. Figure 27-12 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.
92721
27-25
Chapter 27 Configuring STP
Figure 27-12
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.
Configuring STP
These sections describe how to configure STP on VLANs:

Default STP Configuration, page 27-27 Enabling STP, page 27-28 Enabling the Extended System ID, page 27-29 Configuring the Root Bridge, page 27-30 Configuring a Secondary Root Bridge, page 27-31 Configuring STP Port Priority, page 27-32 Configuring STP Port Cost, page 27-33 Configuring the Bridge Priority of a VLAN, page 27-35 Configuring the Hello Time, page 27-36 Configuring the Forward-Delay Time for a VLAN, page 27-36 Configuring the Maximum Aging Time for a VLAN, page 27-37
27-26
92722
OL-13013-06
Chapter 27
Configuring STP and MST Configuring STP
Enabling Rapid-PVST, page 27-37
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.
Default STP Configuration

Table 27-6 shows the default STP configuration.
Table 27-6 STP Default Configuration
Feature Enable state Mode Bridge priority
Default Value STP enabled for all VLANs PVST 32768
STP port priority (configurable on a per-port basisused on LAN ports 128 configured as Layer 2 access ports) STP port cost (configurable on a per-port basisused on LAN ports configured as Layer 2 access ports) 10-Gigabit Ethernet: Gigabit Ethernet: Fast Ethernet: Ethernet: STP VLAN port priority (configurable on a per-VLAN basisused on LAN ports configured as Layer 2 trunk ports) 128 2 4 19 100 2 4 19 100
STP VLAN port cost (configurable on a per-VLAN basisused on LAN 10-Gigabit Ethernet: ports configured as Layer 2 trunk ports) Gigabit Ethernet: Fast Ethernet: Ethernet: Hello time Forward delay time Maximum aging time 2 seconds 15 seconds 20 seconds
27-27
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 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 27-6 on page 27-27). 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. Exits configuration mode. Verifies that STP is enabled.
Router(config)# default spanning-tree vlan vlan_ID Router(config)# no spanning-tree vlan vlan_ID
Step 2 Step 3
Router(config)# end Router# show spanning-tree vlan vlan_ID
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
27-28
OL-13013-06
Chapter 27
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 ---------------Gi1/4 Gi1/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.
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 27-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 Table 27-6STP Default Configuration section on page 27-27).
Step 2 Step 3
Router(config)# end Router# show spanning-tree vlan vlan_ID
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#
27-29

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

The switches supported by Cisco IOS Release 12.2SX 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 lowest 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. With the extended system ID 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. With the extended system ID enabled, 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 27-1 on page 27-3.)
Note
The spanning-tree vlan vlan_ID root command fails if the value required to be the root bridge is less than 1. With the extended system ID enabled, 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 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 switch as the root bridge.
27-30
OL-13013-06
Chapter 27
To configure the 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 the switch as the root bridge. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 27-6 on page 27-27). Clears the root bridge configuration. Exits configuration mode.
Router(config)# no spanning-tree vlan vlan_ID root
Step 2
Router(config)# end
This example shows how to configure the 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 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). With the extended system ID is enabled, STP sets the bridge priority to 28672. You can run this command on more than one 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 the 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 the switch as the secondary root bridge. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 22-1 on page 22-2). Clears the root bridge configuring. Exits configuration mode.
Step 2
Router(config)# end
This example shows how to configure the 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#
27-31
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. Cisco IOS uses the port priority value when the LAN port is configured as an access port and uses VLAN port priority values when the LAN port is configured as a trunk port. To configure the STP port priority of a Layer 2 LAN interface, perform this task: Command
Step 1
Router(config)# interface {{gigabitethernet 1/port} | {port-channel port_channel_number}} Router(config-if)# spanning-tree port-priority port_priority
Purpose Selects an interface to configure.
Step 2
Configures the port priority for the LAN interface. The port_priority value can be from 1 to 252 in increments of 4. Reverts to the default port priority value. Configures the VLAN port priority for the LAN interface. The port_priority value can be from 1 to 252 in increments of 4. The vlan_ID value can be 1 through 4094, except reserved VLANs (see Table 22-1 on page 22-2). Reverts to the default VLAN port priority value. Exits configuration mode. Verifies the configuration.
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 {gigabitethernet 1/port} | {port-channel port_channel_number} Router# show spanning-tree vlan vlan_ID
This example shows how to configure the STP port priority of Gigabit Ethernet port 1/4:
Router# configure terminal Router(config)# interface gigabitethernet 1/4 Router(config-if)# spanning-tree port-priority 160 Router(config-if)# end Router#
This example shows how to verify the configuration of Gigabit Ethernet port 1/4:
Router# show spanning-tree interface gigabitethernet 1/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#
27-32
OL-13013-06
Chapter 27
Gigabit Ethernet port 1/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. This example shows how to configure the VLAN port priority of Gigabit Ethernet port 1/4:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/4 Router(config-if)# spanning-tree vlan 200 port-priority 64 Router(config-if)# end 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 gigabitethernet 1/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 gigabitethernet 1/4 Interface Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------Gi1/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.
27-33
To configure the STP port cost of a Layer 2 LAN interface, perform this task: Command
Step 1
Router(config)# interface {{gigabitethernet 1/port} | {port-channel port_channel_number}} Router(config-if)# spanning-tree cost port_cost
Step 2
Configures the port cost for the LAN interface. The port_cost value can be from 1 to 200000000. 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 22-1 on page 22-2). Reverts to the default VLAN port cost. Exits configuration mode. Verifies the configuration.
Router(config-if)# no spanning-tree cost
Step 3
Router(config-if)# spanning-tree vlan vlan_ID cost port_cost
Router(config-if)# no spanning-tree vlan vlan_ID cost
Step 4 Step 5
Router(config-if)# end Router# show spanning-tree interface {gigabitethernet 1/port} | {port-channel port_channel_number} show spanning-tree vlan vlan_ID
This example shows how to change the STP port cost of Gigabit Ethernet port 1/4:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/4 Router(config-if)# spanning-tree cost 1000 Router(config-if)# end Router#

Router# show spanning-tree interface gigabitethernet 1/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 gigabitethernet 1/4 Router(config-if)# spanning-tree vlan 200 cost 2000 Router(config-if)# end Router#

Router# show spanning-tree vlan 200 interface gigabitethernet 1/4 Interface Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------Gi1/4 Desg FWD 2000 64.196 P2p
27-34
OL-13013-06
Chapter 27
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 gigabitethernet 1/4 Interface Role Sts Cost Prio.Nbr Status ---------------- ---- --- --------- -------- -------------------------------Gi1/4 Back BLK 1000 160.196 P2p Router#
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, perform this task:
Command
Step 1
Router(config)# 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 22-1 on page 22-2). Reverts to the default bridge priority value. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show spanning-tree vlan vlan_ID bridge [detail]
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 32768 Router(config)# end Router#

Router# show spanning-tree vlan 200 bridge Hello Max Fwd Vlan Bridge ID Time Age Delay ---------------- -------------------- ---- ---- ----VLAN200 32768 0050.3e8d.64c8 2 20 15 Router#
Protocol -------ieee
27-35
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 22-1 on page 22-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#

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 22-1 on page 22-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
27-36
OL-13013-06
Chapter 27
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 22-1 on page 22-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#

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 27-26.
27-37
Chapter 27 Configuring MST
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 MST
These sections describe how to configure MST:

Default MST Configuration, page 27-39 MST Configuration Guidelines and Restrictions, page 27-39 Specifying the MST Region Configuration and Enabling MST, page 27-40 (required) Configuring the Root Bridge, page 27-41 (optional) Configuring a Secondary Root Bridge, page 27-31 (optional) Configuring STP Port Priority, page 27-32 (optional) Configuring Path Cost, page 27-44 (optional) Configuring the Switch Priority, page 27-45 (optional) Configuring the Hello Time, page 27-46 (optional) Configuring the Transmit Hold Count, page 27-47 (optional) Configuring the Maximum-Aging Time, page 27-48 (optional) Configuring the Maximum-Hop Count, page 27-48 (optional) Specifying the Link Type to Ensure Rapid Transitions, page 27-48 (optional) Designating the Neighbor Type, page 27-49 (optional) Restarting the Protocol Migration Process, page 27-50 (optional)
27-38
OL-13013-06
Chapter 27
Configuring STP and MST Configuring MST
Default MST Configuration

Table 27-7 shows the default MST configuration.
Table 27-7 Default MST Configuration
Feature Spanning tree mode Switch priority (configurable on a per-CIST port basis) Spanning tree port priority (configurable on a per-MST port basis) Spanning tree port cost (configurable on a per-MST instance port basis)
Default Setting PVST+ (Rapid PVST+ and MST are disabled) 32768 128 10-Gigabit Ethernet: Gigabit Ethernet: Fast Ethernet: Ethernet: 2,000 20,000 200,000 2,000,000
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. 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.
27-39
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. Enables MST and RSTP.
Router(config-mst)# revision version
Router(config-mst)# show pending
Router(config)# exit
Router(config)# spanning-tree mode mst
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.
Step 9
Router(config)# end
Returns to privileged EXEC mode.
27-40
OL-13013-06
Chapter 27
Command
Step 10 Step 11
Router# show running-config Router# copy running-config startup-config
Purpose 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)#
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 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 27-1 on page 27-3.)
27-41
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. 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
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 instance_id root global configuration command.
27-42
OL-13013-06
Chapter 27
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. 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 27-41.
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.
27-43
To configure the MST port priority of an interface, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# interface {{gigabitethernet 1/port} | {port-channel number}} Router(config-if)# spanning-tree mst instance_id port-priority priority
Purpose Enters global configuration mode. (Optional) Specifies an interface to configure, and enters interface configuration mode. Configures the port priority.
Step 3
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
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.
27-44
OL-13013-06
Chapter 27
To configure the MST cost of an interface, perform this task: Command

Step 1 Step 2
Router# configure terminal Router(config)# interface {{gigabitethernet 1/port} | {port-channel number}} Router(config-if)# spanning-tree mst instance_id cost cost
Purpose Enters global configuration mode. (Optional) Specifies an interface to configure, and enters interface configuration mode. 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.
Step 3
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
or
Router# show spanning-tree mst instance_id
Step 6
Router# copy running-config startup-config
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.
27-45
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
Router(config)# end
27-46
OL-13013-06
Chapter 27
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.
27-47
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 27-14.
27-48
OL-13013-06
Chapter 27
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
Step 1 Step 2
Router# configure terminal Router(config)# interface {{gigabitethernet 1/port} | {port-channel number}} 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
Purpose Enters global configuration mode. (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.
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
Step 1 Step 2
Router# configure terminal Router(config)# interface {{gigabitethernet 1/port} | {port-channel number}} Router(config)# spanning-tree mst pre-standard Router(config)# end Router# show spanning-tree mst interface interface_id Router# copy running-config startup-config
Purpose Enters global configuration mode. (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.
To return the port to its default setting, use the no spanning-tree mst prestandard interface configuration command.
27-49
Chapter 27 Displaying the MST Configuration and Status
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 27-8.
Table 27-8 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
27-50
OL-13013-06
C H A P T E R
28

This chapter describes how to configure optional STP features.
Note
Tip

Understanding the Optional STP Features, page 28-1 Configuring the Optional STP Features, page 28-12 Verifying the Optional STP Features, page 28-23
Note
For information on configuring the Spanning Tree Protocol (STP), see Chapter 27, Configuring STP and MST.
Understanding the Optional STP Features

The optional features of the Spanning Tree Protocol (STP) enhance loop prevention, protect against some possible user misconfigurations, and provide better control over the protocol parameters. Although similar functionality may be incorporated into the IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) standard, we recommend using these extensions. With the exception of PVST Simulation, all of these extensions can be used with both Rapid PVST+ and MST. PVST Simulation operates only with MST. These sections describe the optional features:

Understanding STP Port Types, page 28-2 Understanding PortFast, page 28-2
28-1
Chapter 28 Understanding the Optional STP Features
Understanding Bridge Assurance, page 28-3 Understanding BPDU Guard, page 28-5 Understanding PortFast BPDU Filtering, page 28-5 Understanding UplinkFast, page 28-6 Understanding BackboneFast, page 28-7 Understanding EtherChannel Guard, page 28-9 Understanding Root Guard, page 28-10 Understanding Loop Guard, page 28-10 Understanding PVST Simulation, page 28-11
Understanding STP Port Types

Beginning with Cisco IOS Release 12.2(33)SXI, you can specifically configure a spanning tree port as either an edge port, a network port, or a normal port. The port type determines the behavior of the port with respect to STP extensions. An edge port, which is connected to a Layer 2 host, can be either an access port or a trunk port.
Note
If you configure a port connected to a Layer 2 switch or bridge as an edge port, you might create a bridging loop. A network port is connected only to a Layer 2 switch or bridge.
Note
If you mistakenly configure a port that is connected to a Layer 2 host as a spanning tree network port, the port will automatically move into the blocking state. The default spanning tree port type is normal, meaning only that its topology is not specified. In releases earlier than Cisco IOS Release 12.2(33)SXI, configuring a port with PortFast implies that the port is an edge port; otherwise, the port is considered to be a normal port.
Understanding PortFast
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.
Note
Beginning with Cisco IOS Release 12.2(33)SXI, PortFast options are edge and normal. There is no difference between edge ports and PortFast ports.
28-2
OL-13013-06
Chapter 28
Configuring Optional STP Features Understanding the Optional STP Features
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 (edge) ports. If you enable PortFast on a port connected to a switch (a network port), you might create a temporary bridging loop.
Understanding Bridge Assurance

With Cisco IOS Release 12.2(33)SXI and later releases, you can use Bridge Assurance to protect against certain problems that can cause bridging loops in the network. Specifically, you use Bridge Assurance to protect against a unidirectional link failure or other software failure and a device that continues to forward data traffic when it is no longer running the spanning tree algorithm.
Note
Bridge Assurance is supported only by Rapid PVST+ and MST. Bridge Assurance is enabled by default and can only be disabled globally. Also, Bridge Assurance is enabled only on spanning tree network ports that are point-to-point links. Finally, both ends of the link must have Bridge Assurance enabled. If the device on one side of the link has Bridge Assurance enabled and the device on the other side either does not support Bridge Assurance or does not have this feature enabled, the connecting port is blocked. With Bridge Assurance enabled, BPDUs are sent out on all operational network ports, including alternate and backup ports, for each hello time period. If the port does not receive a BPDU for a specified period, the port moves into an inconsistent state (blocking). and is not used in the root port calculation. Once that port receives a BPDU, it resumes the normal spanning tree transitions. Figure 28-1 shows a normal STP topology, and Figure 28-2 demonstrates a potential network problem when the device fails and you are not running Bridge Assurance.
Figure 28-1 Network with Normal STP Topology
Root
Network
Network
Network Blocked
Edge
186525
28-3
Figure 28-2
Network Problem without Running Bridge Assurance
Root
Loop
Malfunctioning switch
X
BPDUs Edge
186410
Figure 28-3 shows the network with Bridge Assurance enabled, and the STP topology progressing normally with bidirectional BPDUs issuing from every STP network port. Figure 28-4 shows how the potential network problem shown in Figure 28-2 does not happen when you have Bridge Assurance enabled on your network.
Figure 28-3 Network STP Topology Running Bridge Assurance
Root
Network
Network
Network Blocked
Edge
28-4
186526
OL-13013-06
Chapter 28
Figure 28-4
Network Problem Averted with Bridge Assurance Enabled

Stopped receiving BPDUs
Br1dge assurance inconsistent Network Root BPDUs Network
X
Network
Malfunctioning switch
Bridge assurance inconsistent

Stopped receiving BPDUs
Edge
When using Bridge Assurance, follow these guidelines:

Bridge Assurance runs only on point-to-point spanning tree network ports. You must configure each side of the link for this feature. We recommend that you enable Bridge Assurance throughout your network.
Understanding BPDU Guard

BPDU Guard complements the functionality of PortFast. On PortFast-enabled ports, BPDU Guard provides the protection against Layer 2 loops that STP cannot provide when STP PortFast is enabled. In a valid configuration, PortFast Layer 2 LAN interfaces (edge ports) do not receive BPDUs. 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 (edge) state. 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 (edge) state.
Understanding PortFast BPDU Filtering

PortFast BPDU filtering allows the administrator to prevent the system from sending or even receiving BPDUs on specified ports.
186411
%STP-2-BRIDGE_ASSURANCE_BLOCK: Bridge Assurance blocking port Ethernet2/48 VLAN0700. switch# sh spanning vl 700 | in -i bkn Eth2/48 Altn BKN*4 128.304 Network P2p *BA_Inc switch#
28-5
Note
Beginning with Cisco IOS Release 12.2(33)SXI, PortFast BPDU Filtering is known as PortFast Edge BPDU Filtering. When configured globally, PortFast BPDU filtering applies to all operational PortFast (edge) ports. Ports in an operational PortFast state are supposed to be connected to hosts, which typically drop BPDUs. If an operational PortFast port receives a BPDU, it immediately loses its operational PortFast status and becomes a normal port. In that case, PortFast BPDU filtering is disabled on this port and STP resumes sending BPDUs on this port. 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
Explicitly configuring PortFast BPDU filtering on a port that is not connected to a host can result in bridging loops, as the port will ignore any BPDU it receives and will go to a forwarding state. 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 28-15), 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 28-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 28-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 UplinkFast
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.
28-6
OL-13013-06
Chapter 28
Figure 28-5 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.
Figure 28-5 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 28-6. This switchover takes approximately one to five seconds.
Figure 28-6 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 BackboneFast
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
28-7
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. 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 28-7 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 28-7 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 28-8 shows how BackboneFast reconfigures the topology to account for the failure of link L1.
28-8
OL-13013-06
Chapter 28
Figure 28-8
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 28-9, 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 28-9 Adding a Network Device in a Shared-Medium Topology
Switch A (Root)
Switch C
Blocked port
Switch B (Designated Bridge)
Added switch
11245
Understanding EtherChannel Guard

EtherChannel guard detects a misconfigured EtherChannel when interfaces on the switch are configured as an EtherChannel while interfaces on the other device are not or when 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 switch into the errdisabled state.
11244
BackboneFast transitions port through listening and learning states to forwarding state
28-9
Understanding Root Guard

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 Loop Guard

Loop guard helps prevent bridging loops that could occur because of a unidirectional 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 28-10 shows loop guard in a triangle switch configuration.
Figure 28-10 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 28-10 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:
28-10
OL-13013-06
Chapter 28
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.
Understanding PVST Simulation

MST interoperates with Rapid PVST+ with no need for user configuration. The PVST simulation feature enables this seamless interoperability.
Note
PVST simulation is enabled by default when you enable MST. That is, by default, all interfaces on the device interoperate between MST and Rapid PVST+. The ability to disable PVST simulation is introduced in Cisco IOS Release 12.2(33)SXI. You may want to control the connection between MST and Rapid PVST+ to protect against accidentally connecting an MST-enabled port to a port enabled to run Rapid PVST+. Because Rapid PVST+ is the default STP mode, you may encounter many Rapid PVST+ connections.
28-11
Chapter 28 Configuring the Optional STP Features
Disabling Rapid PVST+ simulation, which can be done per port or globally for the entire device, moves the MST-enabled port to the PVST peer inconsistent (blocking) state once it detects it is connected to a Rapid PVST+-enabled port. This port remains in the inconsistent state until the port stops receiving Shared Spanning Tree Protocol (SSTP) BPDUs, and then the port resumes the normal STP transition process. The root bridge for all STP instances must all be in either the MST region or the Rapid PVST+ side. If the root bridge for all STP instances are not on one side or the other, the software moves the port into a PVST simulation-inconsistent state.
Note
We recommend that you put the root bridge for all STP instances in the MST region.
Configuring the Optional STP Features

This section includes the following topics:

Enabling PortFast, page 28-12 Enabling Bridge Assurance, page 28-14 Enabling PortFast BPDU Filtering, page 28-15 Enabling BPDU Guard, page 28-16 Enabling UplinkFast, page 28-18 Enabling BackboneFast, page 28-19 Enabling EtherChannel Guard, page 28-20 Enabling Root Guard, page 28-20 Enabling Loop Guard, page 28-21 Configuring PVST Simulation, page 28-22
Enabling PortFast
Caution
Use the PortFast feature only when connecting a single end station to a Layer 2 port. Otherwise, you might create a network loop.
Enabling PortFast on a Layer 2 Port

To enable PortFast on a Layer 2 port, perform this task: Command
Step 1
Router(config)# interface {type slot/port} | {port-channel port_channel_number}
1
Purpose Selects a port to configure.
28-12
OL-13013-06
Chapter 28
Configuring Optional STP Features Configuring the Optional STP Features
Command
Step 2
Router(config-if)# no spanning-tree portfast
Purpose Configures the port as a normal port. Enables edge behavior on a Layer 2 access port connected to a single workstation or server. The trunk keyword enables edge behavior on a trunk port. Configures the port as a network port. Bridge Assurance, if enabled globally, will be enabled on the port. Disables edge behavior on the port.
Cisco IOS Release 12.2(33)SXI and later releases:

Router(config-if)# spanning-tree portfast edge [trunk] Router(config-if)# spanning-tree portfast network
Router(config-if)# spanning-tree portfast edge disable
Earlier releases:
Router(config-if)# spanning-tree portfast [trunk] Router(config-if)# spanning-tree portfast disable
Enables PortFast on a Layer 2 access port connected to a single workstation or server. Disables edge behavior on the port. Port will behave as a normal port. Exits configuration mode. Verifies the configuration.
Step 3 Step 4
Router(config-if)# end Router# show running interface {type slot/port} | {port-channel port_channel_number} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
1
This example shows how to enable and verify PortFast on Fast Ethernet interface 5/8 in Cisco IOS Release 12.2(33)SXI and later releases:
Router# configure terminal Router(config)# interface fastethernet 5/8 Router(config-if)# spanning-tree portfast edge 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 edge end Router#
This example shows how to enable and verify PortFast on Fast Ethernet interface 5/8 in releases earlier than Cisco IOS Release 12.2(33)SXI:
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
28-13
switchport switchport access vlan 200 switchport mode access spanning-tree portfast end Router#
Configuring the PortFast Default State

To set and verify the default PortFast configuration, perform this task: Command Cisco IOS Release 12.2(33)SXI and later releases:
Router(config)# spanning-tree portfast [edge | network | normal] default
Purpose Configures the default state for all switch access ports to be edge, network, or normal. Bridge Assurance will be enabled on all network access ports by default. Configures the default state for all switch access ports to be edge. Use the no prefix to configure the default state to be normal. Exits configuration mode. Verifies the global configuration.
1
Step 1
Earlier releases:
Router(config)# [no] spanning-tree portfast default
Router(config-if)# end Router# show spanning-tree summary totals Router# show spanning-tree interface {type slot/port} detail 1.
Verifies the effect on a specific port.
This example shows how to configure the default switch access port state to be edge in Cisco IOS Release 12.2(33)SXI and later releases:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# spanning-tree portfast edge default Router(config)# ^Z
This example shows how to configure the default switch access port state to be edge in releases earlier than Cisco IOS Release 12.2(33)SXI:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# spanning-tree portfast default Router(config)# ^Z
Enabling Bridge Assurance

Release 12.2(33)SXI and later releases support Bridge Assurance. By default, Bridge Assurance is enabled on all network ports on the switch. Disabling Bridge Assurance causes all configured network ports to behave as normal spanning tree ports. To enable or disable Bridge Assurance globally, perform this task: Command
Router(config)# spanning-tree bridge assurance
Purpose Enables Bridge Assurance on all network ports on the switch.
28-14
OL-13013-06
Chapter 28
This example shows how to enable PortFast Bridge Assurance on all network ports on the switch, and how to configure a network port:
Router(config)# spanning-tree bridge assurance Router(config)# interface fastethernet 5/8 Router(config-if)# spanning-tree portfast network Router(config-if)# ^Z
Enabling PortFast BPDU Filtering

These sections describe how to configure PortFast BPDU filtering.
Enabling PortFast BPDU Filtering Globally

To enable PortFast BPDU filtering globally, perform this task: Command Cisco IOS Release 12.2(33)SXI and later releases:
Router(config)# spanning-tree portfast edge bpdufilter default
Purpose Enables BPDU filtering globally by default on all edge ports of the switch. Use the no prefix to disable BPDU filtering by default on all edge ports of the switch.
Step 1
Earlier releases:
Router(config)# spanning-tree portfast bpdufilter default
Step 2 Step 3
Router(config)# end Router# show spanning-tree summary totals
BPDU filtering is set to default on each edge port. This example shows how to enable PortFast BPDU filtering on the port and verify the configuration in PVST+ mode:
Router(config)# spanning-tree portfast edge bpdufilter default Router(config)# ^Z Router# show spanning-tree summary totals Root bridge for: Bridge VLAN0025 EtherChannel misconfiguration guard is enabled Extended system ID is enabled PortFast Edge BPDU Guard Default is disabled Portfast Edge BPDU Filter Default is enabled Portfast Default is edge Bridge Assurance is enabled Loopguard is disabled 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#
28-15
Enabling PortFast BPDU Filtering on a Nontrunking Port

To enable or disable PortFast BPDU filtering on a nontrunking port, perform this task: Command
Router(config)# interface {type
1
Purpose
slot/port}
Selects the interface to configure. Enables or disables BPDU filtering on the port. Exits configuration mode. Verifies the configuration.
Router(config-if)# spanning-tree bpdufilter [enable | disable] Router(config-if)# end Router# show spanning-tree interface {type slot/port} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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 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#
Enabling BPDU Guard

These sections describe how to enable BPDU Guard:

Enabling BPDU Guard Globally, page 28-17 Enabling BPDU Guard on a Port, page 28-18
28-16
OL-13013-06
Chapter 28
Enabling BPDU Guard Globally

To enable BPDU Guard globally, perform this task: Command
Step 1
Purpose Enables BPDU Guard globally by default on all edge ports of the switch.
Cisco IOS Release 12.2(33)SXI and later releases:

Router(config)# spanning-tree portfast edge bpduguard default
Earlier releases:
Router(config)# spanning-tree portfast bpduguard default
Step 2 Step 3
Router(config)# end Router# show spanning-tree summary totals
This example shows how to enable BPDU Guard:

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

Router# show spanning-tree summary totals Root bridge for: Bridge VLAN0025 EtherChannel misconfiguration guard is enabled Extended system ID is enabled PortFast Edge BPDU Guard Default is enabled Portfast Edge BPDU Filter Default is disabled Portfast Default is edge Bridge Assurance is enabled Loopguard is disabled 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#
28-17
Enabling BPDU Guard on a Port

To enable BPDU Guard on a port, perform this task: Command
Router(config)# interface {type slot/port} | {port-channel port_channel_number} Router(config-if)# spanning-tree bpduguard enable Router(config-if)# end Router# show spanning-tree Router# show running interface {type1 slot/port} | {port-channel port_channel_number} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
1
Purpose Selects a port to configure. Enables BPDU Guard on the port. Exits configuration mode. Verifies the configuration.
This example shows how to enable BPDU Guard:

Router# configure terminal Router(config)# spanning-tree portfast edge bpduguard default Router(config)# end Router#
Enabling UplinkFast
UplinkFast increases the bridge priority to 49152 and adds 3000 to the STP port cost of all Layer 2 LAN ports on the 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 switch. You cannot configure UplinkFast on an individual VLAN. To enable UplinkFast, perform this task:
Command
Step 1
Router(config)# spanning-tree uplinkfast Router(config)# spanning-tree uplinkfast [max-update-rate max_update_rate] Router(config)# end Router# show spanning-tree vlan vlan_ID
Purpose Enables UplinkFast. Enables UplinkFast with an update rate in seconds. 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:
28-18
OL-13013-06
Chapter 28
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
Router(config)# spanning-tree backbonefast Router(config)# end Router# show spanning-tree vlan vlan_ID
Purpose Enables BackboneFast. Exits configuration mode. Verifies that BackboneFast is enabled.
This example shows how to enable BackboneFast:

Router# configure terminal 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
28-19
Enabling EtherChannel Guard

To enable EtherChannel guard, perform this task: Command
Router(config)# spanning-tree etherchannel guard misconfig Router(config)# end Router# show spanning-tree summary | include EtherChannel
Purpose Enables EtherChannel guard. Exits configuration mode. Verifies that EtherChannel guard is enabled.
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: Command
Router(config)# interface {type slot/port} | {port-channel port_channel_number} Router(config-if)# spanning-tree guard root Router(config-if)# end Router# show spanning-tree Router# show running interface {type1 slot/port} | {port-channel port_channel_number} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
1
Purpose Selects a port to configure. Enables root guard. Exits configuration mode. Verifies the configuration.
To display ports that are in the root-inconsistent state, enter the show spanning-tree inconsistentports command.
28-20
OL-13013-06
Chapter 28
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 {type slot/port} detail 1.
1
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: 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 {type slot/port} detail 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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.
28-21

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#
Configuring PVST Simulation

Note
PVST simulation is enabled by default so that all interfaces on the device interoperate between MST and Rapid PVST+. The ability to disable PVST simulation is introduced in Cisco IOS Release 12.2(33)SXI. To prevent an accidental connection to a device that does not run MST as the default STP mode, you can disable PVST simulation. If you disable PVST simulation, the MST-enabled port moves to the blocking state once it detects it is connected to a Rapid PVST+-enabled port. This port remains in the inconsistent state until the port stops receiving BPDUs, and then the port resumes the normal STP transition process. To enable or disable PVST simulation globally, enter the command using the global keyword, as shown in the following task:
Command
Router(config)# spanning-tree mst simulate pvst global
Purpose Enables all ports to automatically interoperate with a connected device that is running in Rapid PVST+ mode. The default is enabled; all interfaces will operate seamlessly between Rapid PVST+ and MST.
To override the global PVST simulation setting for a port, enter the command in the interface command mode, as shown in the following task: Command
Step 1 Step 2
Router(config)# interface {type
1
Purpose
slot/port}
Selects a port to configure. Enables this interface to automatically interoperate with a connected device that is running in Rapid PVST+ mode.
Router(config-if)# spanning-tree mst simulate pvst 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to prevent the switch from automatically interoperating with a connecting device that is running Rapid PVST+:
Router(config)# no spanning-tree mst simulate pvst global
28-22
OL-13013-06
Chapter 28
Configuring Optional STP Features Verifying the Optional STP Features
This example shows how to prevent a port from automatically interoperating with a connecting device that is running Rapid PVST+:
Router(config)# interface gi3/13 Router(config-if)# spanning-tree mst simulate pvst disable
Verifying the Optional STP Features

This section includes the following topics:

Using the show spanning-tree Commands, page 28-23 Examples in Release 12.2(33)SXI and Later Releases, page 28-23 Examples in Releases Earlier Than Release 12.2(33)SXI, page 28-26
Using the show spanning-tree Commands

You can view spanning tree status and configuration information, both global and port-level, using the show spanning-tree commands described in this section. To view spanning tree status and configuration information, perform one of the following tasks: Command
Router# show spanning-tree
Purpose Displays information about the spanning tree, including protocol type and port types. Displays a summary of the spanning tree feature settings and the spanning tree states of the VLANs. Displays a summary of the spanning tree feature settings and totals of the VLAN states. Displays the spanning tree status details of an interface. Displays the spanning tree portfast edge interface operational state for all the instances. In releases earlier than Cisco IOS Release 12.2(33)SXI, the edge keyword is not used.
Router# show spanning-tree summary
Router# show spanning-tree summary totals
Router# show spanning-tree interface {type1 slot/port} detail Router# show spanning-tree interface {type1 slot/port} portfast edge
1.
Examples in Release 12.2(33)SXI and Later Releases

Note
The output of the show spanning-tree commands in releases earlier than Release 12.2(33)SXI differs from the output in Release 12.2(33)SXI and later releases. The differences are shown in bold in the examples in this section. This example displays the spanning-tree status with Bridge Assurance enabled but in the inconsistent state:
28-23
Chapter 28 Verifying the Optional STP Features
Router# show spanning-tree VLAN0010 Spanning tree enabled protocol rstp Root ID Priority 32778 Address 0002.172c.f400 This bridge is the root Hello Time 2 sec Max Age 20 sec Bridge ID
Priority 32778 (priority 32768 sys-id-ext 10) Address 0002.172c.f400 Hello Time 2 sec Max Age 20 sec Forward Delay 15 sec Aging Time 300
Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------Gi3/14 Desg BKN*4 128.270 Network, P2p *BA_Inc Router#
The following inconsistency messages can be appended to the Type field:

*BA_IncIndicates that Bridge Assurance is in the inconsistent state. *PVST_Peer_IncIndicates that the port is in a peer type Inconsistent state. DisputeIndicates that a dispute condition is detected.
This example shows the spanning-tree configuration summary:

Router# show spanning-tree summary Switch is in rapid-pvst mode Root bridge for: Bridge VLAN0025 EtherChannel misconfiguration guard Extended system ID PortFast Edge BPDU Guard Default Portfast Edge BPDU Filter Default Portfast Default Bridge Assurance Loopguard UplinkFast BackboneFast Pathcost method used is short PVST Simulation Default
is is is is is is is is is
enabled enabled disabled disabled edge enabled disabled disabled disabled
is enabled
Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------VLAN0025 0 0 0 1 1 VLAN0030 0 0 0 2 2 ---------------------- -------- --------- -------- ---------- ---------2 vlans 0 0 0 3 3 Router#
Possible states for the Bridge Assurance field are as follows:

is enabled is disabled is enabled but not active in the PVST mode
This example shows the spanning tree summary when PVST simulation is disabled in any STP mode:
Router# show spanning-tree summary
28-24
OL-13013-06
Chapter 28
Switch is in mst mode (IEEE Standard) Root bridge for: MST0 EtherChannel misconfig guard is enabled Extended system ID is enabled Portfast Default is disabled PortFast BPDU Guard Default is disabled Portfast BPDU Filter Default is disabled Loopguard Default is disabled UplinkFast is disabled BackboneFast is disabled Pathcost method used is long PVST Simulation Default is disabled Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------MST0 2 0 0 0 2 ---------------------- -------- --------- -------- ---------- ---------1 mst 2 0 0 0 2
Possible states for the PVST Simulation Default field are as follows:

is enabled is disabled is enabled but not active in rapid-PVST mode
This example shows the spanning tree summary totals:

Router# show spanning-tree summary totals Root bridge for: Bridge VLAN0025 EtherChannel misconfiguration guard is enabled Extended system ID is enabled PortFast Edge BPDU Guard Default is enabled Portfast Edge BPDU Filter Default is disabled Portfast Default is edge Bridge Assurance is enabled Loopguard is disabled 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#
This example shows the spanning-tree configuration details of an edge port:

Router# show spanning-tree interface gi3/13 detail Port 269 (GigabitEthernet3/13) of VLAN0002 is forwarding Port path cost 4, Port priority 128, Port Identifier 128.269. Designated root has priority 32770, address 0002.172c.f400 Designated bridge has priority 32770, address 0002.172c.f400 Designated port id is 128.269, designated path cost 0 Timers: message age 0, forward delay 0, hold 0 Number of transitions to forwarding state: 1 Link type is point-to-point by default Loop guard is enabled by default on the port The port is in the portfast edge mode by default BPDU: sent 2183, received 0
This example shows the spanning-tree configuration details of a trunk port:

Router(config-if)# spanning-tree portfast edge trunk %Warning:portfast should only be enabled on ports connected to a single
28-25
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 gi3/13 detail Port 269 (GigabitEthernet3/13) of VLAN0002 is forwarding Port path cost 4, Port priority 128, Port Identifier 128.269. Designated root has priority 32770, address 0002.172c.f400 Designated bridge has priority 32770, address 0002.172c.f400 Designated port id is 128.269, designated path cost 0 Timers: message age 0, forward delay 0, hold 0 Number of transitions to forwarding state: 1 Link type is point-to-point by default Loop guard is enabled by default on the port The port is in the portfast edge trunk mode BPDU: sent 2183, received 0 Router#
This example shows the spanning-tree configuration details of an edge port when a dispute condition has been detected:
Router# show spanning-tree interface gi3/13 detail Port 269 (GigabitEthernet3/13) of VLAN0002 is designated blocking (dispute) Port path cost 4, Port priority 128, Port Identifier 128.297. Designated root has priority 32769, address 0013.5f20.01c0 Designated bridge has priority 32769, address 0013.5f20.01c0 Designated port id is 128.297, designated path cost 0 Timers: message age 0, forward delay 0, hold 0 Number of transitions to forwarding state: 1 Link type is point-to-point by default BPDU: sent 132, received 1 Router#
This example shows the spanning tree portfast edge interface operational state for all the instances:
Router# show spanning-tree interface gi3/1 portfast edge MST0 disabled MST1 disabled
Examples in Releases Earlier Than Release 12.2(33)SXI

Note
The output of the show spanning-tree commands in releases earlier than Release 12.2(33)SXI differs from the output in Release 12.2(33)SXI and later releases. The differences are shown in bold in the examples in this section. This example displays the spanning-tree status:
Router# show spanning-tree VLAN0010 Spanning tree enabled protocol rstp Root ID Priority 32778 Address 0002.172c.f400 This bridge is the root Hello Time 2 sec Max Age 20 sec Bridge ID Priority 32778
(priority 32768 sys-id-ext 10)
28-26
OL-13013-06
Chapter 28
Address 0002.172c.f400 Hello Time 2 sec Max Age 20 sec Aging Time 300
Interface Role Sts Cost Prio.Nbr Type ---------------- ---- --- --------- -------- -------------------------------Gi3/14 Desg FWD 4 128.270 Edge, P2p Router#
This example shows the spanning-tree configuration summary:

Router# show spanning-tree summary Switch is in rapid-pvst mode 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 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#
This example shows the spanning-tree configuration summary totals:

Router# show spanning-tree summary totals Switch is in rapid-pvst mode 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 Name Blocking Listening Learning Forwarding STP Active ---------------------- -------- --------- -------- ---------- ---------2 vlans 0 0 0 3 3 Router#
This example shows the spanning-tree configuration details of an edge port:

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
28-27
Link type is point-to-point by default BPDU:sent 10, received 0
This example shows the spanning-tree configuration details of a trunk port:

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#
This example shows the spanning tree portfast interface operational state for all the instances:
Router# show spanning-tree interface gi3/1 portfast MST0 disabled MST1 disabled
Tip
28-28
OL-13013-06
PA R T
IP Routing Protocols
C H A P T E R
29

This chapter contains information about how to configure Layer 3 interfaces in Cisco IOS Release 12.2SX.
Note
Tip

Layer 3 Interface Configuration Guidelines and Restrictions, page 29-2 Configuring Subinterfaces on Layer 3 Interfaces, page 29-2 Configuring IPv4 Routing and Addresses, page 29-4 Configuring IPX Routing and Network Numbers, page 29-7 Configuring AppleTalk Routing, Cable Ranges, and Zones, page 29-8 Configuring Other Protocols on Layer 3 Interfaces, page 29-9
29-1
Chapter 29 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. The ip unnumbered command is supported on Layer 3 VLAN interfaces. To support VLAN interfaces, create and configure VLANs and assign VLAN membership to Layer 2 LAN ports. For more information, see Chapter 22, Configuring VLANs and Chapter 21, Configuring VTP. Cisco IOS Release 12.2SX does 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 route processor (RP). Cisco IOS Release 12.2SX does 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:
The PFC3 supports 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 PIMv1, PIMv2 SSM IGMPv3lite and URD Stub IP multicast routing
29-2
OL-13013-06
Chapter 29
Configuring Layer 3 Interfaces Configuring Subinterfaces on Layer 3 Interfaces
IGMP join IGMP static group Multicast routing monitor (MRM) Multicast source discovery protocol (MSDP) SSM IPv4 Ping IPv6 Ping
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.
With any VTP version, 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}} Router(config-subif)# encapsulation dot1q vlan_ID [native] Router(config-if)# exit 1.
Purpose Enters privileged EXEC mode. Enters global configuration mode. Selects an interface and enters subinterface configuration mode. Configures 802.1Q encapsulation for the subinterface. Returns to global configuration mode.
Step 4 Step 5
type = fastethernet, gigabitethernet, tengigabitethernet, or ge-wan
29-3
Chapter 29 Configuring IPv4 Routing and Addresses
Configuring IPv4 Routing and Addresses

For complete information and procedures, see 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:

See the command reference for information about the maximum-paths command. 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 RP address falls within the range of a PBR ACL, traffic addressed to the RP is policy
routed in hardware instead of being forwarded to the RP. To prevent policy routing of traffic addressed to the RP, configure PBR ACLs to deny traffic addressed to the RP.
Any options in Cisco IOS ACLs that provide filtering in a PBR route-map that would cause
flows to be sent to the RP 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 RP.

In Cisco IOS Release 12.2(33)SXH4 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. To configure PBR, see 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_Product s_Configuration_Guide_Chapter.html
29-4
OL-13013-06
Chapter 29
Configuring Layer 3 Interfaces 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. type = fastethernet, gigabitethernet, or tengigabitethernet
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 Keepalive set (10 sec)
29-5
Chapter 29 Configuring IPv4 Routing and Addresses
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#
29-6
OL-13013-06
Chapter 29
Configuring Layer 3 Interfaces 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 RP supports IPX with fast switching. For complete information and procedures, see 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}]
29-7
Chapter 29 Configuring AppleTalk Routing, Cable Ranges, and Zones
1.
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

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. type = fastethernet, gigabitethernet, or tengigabitethernet
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.
This example shows how to enable AppleTalk routing and assign an AppleTalk cable-range and zone name to interface VLAN 100:
29-8
OL-13013-06
Chapter 29
Configuring Layer 3 Interfaces 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

See 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
29-9
Chapter 29 Configuring Other Protocols on Layer 3 Interfaces
29-10
OL-13013-06
C H A P T E R
30

This chapter describes how to configure unidirectional Ethernet (UDE) and unidirectional link routing (UDLR).
Note
Cisco ME 6500 Series Ethernet switches do not support UDE and UDLR. For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html
Tip
These sections describe UDE and UDLR:

Understanding UDE and UDLR, page 30-1 Configuring UDE and UDLR, page 30-3
Understanding UDE and UDLR

These sections describe UDE and UDLR:

UDE and UDLR Overview, page 30-1 Supported Hardware, page 30-2 Understanding UDE, page 30-2 Understanding UDLR, page 30-3
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.
30-1
Chapter 30 Understanding UDE and UDLR
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 30-2 Understanding Hardware-Based UDE, page 30-2 Understanding Software-Based UDE, page 30-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
See the Supported Hardware section on page 30-2 for a list of the module with interfaces that support hardware-based UDE and software-based UDE.
Understanding Hardware-Based UDE

You can create a unidirectional link by using a unidirectional transceiver. Unidirectional transceivers are less expensive than bidirectional transceivers. These are the supported unidirectional transceivers:
Receive-only WDM GBIC (WDM-GBIC-REC=)
30-2
OL-13013-06
Chapter 30
Configuring UDE and UDLR Configuring UDE and UDLR
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 30-3 Configuring UDLR, page 30-6
Note
This caveat is open in releases that support UDLR: Neighboring ISIS routers are not seen through a UDLR topology. (CSCee56596)
Configuring UDE
These sections describe how to configure UDE:

UDE Configuration Guidelines, page 30-4 Configuring Hardware-Based UDE, page 30-4 Configuring Software-Based UDE, page 30-5
30-3
Chapter 30 Configuring UDE and UDLR
UDE Configuration Guidelines

When configuring UDE, follow these guidelines:

UDE is supported on the Supervisor Engine 720. 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. 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.
30-4
OL-13013-06
Chapter 30
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.
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.
30-5
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 30-6 Configuring a Receive-Only Tunnel Interface for a UDE Send-Only Port, page 30-7 Configuring a Send-Only Tunnel Interface for a UDE Receive-Only Port, page 30-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 route processor (RP) 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. UDLR back-channel tunnels do not support IPv6 or MPLS.
30-6
OL-13013-06
Chapter 30
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.
30-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
30-8
OL-13013-06
PA R T
Multiprotocol Label Switching
C H A P T E R
31

This chapter describes how to configure Multiprotocol Label Switching (MPLS) in Cisco IOS Release 12.2SX.
Note
MPLS is not supported in PFC3A mode. 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/122sxmcl/12_2sx_mcl_book.html
The Release 12.2 publications at this URL:
http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_installation_and_configu ration_guides_list.html
Tip

MPLS, page 31-1 DE/CLP and EXP Mapping on FR/ATMoMPLS VC, page 31-10 VPN Switching, page 31-13 Any Transport over MPLS, page 31-17
MPLS
These sections describe MPLS:

Understanding MPLS, page 31-2 Hardware-Supported MPLS Functions, page 31-4
31-1
Chapter 31 MPLS
Supported Cisco IOS Features, page 31-5 MPLS Guidelines and Restrictions, page 31-7 Configuring MPLS, page 31-8 MPLS Per-Label Load Balancing, page 31-8 MPLS Configuration Examples, page 31-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 31-1 shows an MPLS network of a service provider that connects two sites of a customer network.
Figure 31-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/mpls/configuration/guide/12_2sx/mp_12_2sx_book.html Cisco IOS Release 12.2SX 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. The route processor (RP) performs Layer 3 control-plane functions, including address resolution and routing protocols. The RP processes information from the Routing and Label Distribution Protocols and builds the IP forwarding (FIB) table and the label forwarding (LFIB) table. The RP distributes the information in both tables to the PFC3.
31-2
OL-13013-06
119118
Chapter 31
Configuring Multiprotocol Label Switching MPLS
The PFC3 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 31-2 shows the various functional blocks that support MPLS. 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 31-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 PFC 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 PFC 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 31-8.
MPLS to MPLS
At the core of an MPLS network, the PFC 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.
31-3
Chapter 31 MPLS
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 PFC 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 PFC 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 PFC 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 PFC looks up the top label in the FIB TCAM and recirculates the packet. Then the PFC 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 PFC 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 PFC for additional processing.
Hardware-Supported MPLS Functions

The PFC supports the following MPLS functions in hardware:

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.
31-4
OL-13013-06
Chapter 31
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 PFC provides the capability to recirculate the packets. See the Recirculation section on page 31-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:
Multi-VPN Routing and Forwarding (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 for more information: http://www.cisco.com/en/US/products/hw/routers/ps259/prod_bulletin09186a00800921d7.html VRF Lite is supported with the following features:
IPv4 forwarding between VRFs interfaces IPv4 ACLs IPv4 HSRP
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 for more information: http://www.cisco.com/en/US/docs/ios/12_0st/12_0st21/feature/guide/fs_rtr.html
31-5
Chapter 31 MPLS
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/mpls/configuration/guide/12_2sx/mp_12_2sx_book.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 for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_diffserv_aw_ps6017_TSD _Products_Configuration_Guide_Chapter.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/mpls/configuration/guide/mp_te_fwd_adjacency_ps6017_T SD_Products_Configuration_Guide_Chapter.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 for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_te_interarea_tun_ps6017_TS D_Products_Configuration_Guide_Chapter.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 for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/12_2sx/mp_12_2sx_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 for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_carrier_ldp_igp_ps6017_TSD _Products_Configuration_Guide_Chapter.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 for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_carrier_bgp_ps6017_TSD_Pr oducts_Configuration_Guide_Chapter.html
MPLS VPN Interautonomous System (InterAS) Support This feature allows an MPLS VPN to span service providers and autonomous systems. See this publication for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpn_interauto_ps6017_TSD_ Products_Configuration_Guide_Chapter.html
31-6
OL-13013-06
Chapter 31
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 for more information: http://www.cisco.com/en/US/docs/ios/mpls/configuration/guide/mp_vpn_connect_ipv4_ps6017_T SD_Products_Configuration_Guide_Chapter.html
HSRP Support for MPLS VPNsThis 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 for more information: http://www.cisco.com/en/US/docs/ios/ipapp/configuration/guide/ipapp_hsrp_ps6017_TSD_Produc ts_Configuration_Guide_Chapter.html#HSRP_Support_for_MPLS_VPNs
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 for more information: http://www.cisco.com/en/US/docs/ios/12_2t/12_2t8/feature/guide/ospfshmk.html Any Transport over MPLS (AToM)Transports Layer 2 packets over an MPLS backbone. See the Any Transport over MPLS section on page 31-17.
MPLS Guidelines and Restrictions

When configuring MPLS, follow these guidelines and restrictions:

The PFC3 and DFC3s support up to 16 load-shared paths (Cisco IOS releases for other platforms support only 8 load-shared paths). MTU size checking is supported in hardware. Fragmentation is supported in software, including traffic that ingresses as IP and egresses as MPLS. To prevent excessive CPU utilization, you can rate-limit the traffic being sent to the RP for fragmentation with the mls rate-limit all mtu-failure command.
Note
For information on other limitations and restrictions, see the MPLS VPN Guidelines and Restrictions section on page 31-14 and the EoMPLS Guidelines and Restrictions section on page 31-18.
Supported MPLS Commands

Release 12.2SX supports these MPLS 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
31-7
Chapter 31 MPLS
For information about these commands, see this publication: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html
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.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 PFC forwards MPLS labeled packets without explicit configuration. If the packet has three labels or less and the underlying packet is IPv4, then the PFC uses the source and destination IPv4 address. If the underlying packet is not IPv4, or if more than three labels are present, the PFC 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 31-8.
MPLS Configuration Examples

The following is an example of a basic MPLS configuration:
***** Basic MPLS *****
IP ingress interface:
31-8
OL-13013-06
Chapter 31
Router# mpls label protocol ldp interface GigabitEthernet6/2 ip address 75.0.77.1 255.255.255.0 media-type rj45 speed 1000 end 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# show ip routing 88.0.0.0 Routing entry for 88.0.0.0/24, 1 known subnets O E2 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
31-9
Chapter 31 DE/CLP and EXP Mapping on FR/ATMoMPLS VC
DE/CLP and EXP Mapping on FR/ATMoMPLS VC

Note
Cisco IOS Release 12.2(33)SXH and later releases do not support any Frame Relay interfaces. The DE/CLP and EXP Mapping on FR/ATMoMPLS VC feature allows you to map the ATM Congestion Loss Priority (CLP) bit to the MPLS EXP value at the ingress to an MPLS AToM network and to map the MPLS EXP value to the ATM CLP bit at the egress of an MPLS AToM network. The ATM CLP bit indicates whether the cell may be discarded if it encounters extreme congestion as it moves through the network. In the figure below, the PE1 tags the incoming packet with the MPLS EXP value and sends the packet to the next hop. At each hop, matching is on the EXP value. At the PE2 egress, however, the packet is no longer MPLS but IP, so matching cannot occur on the EXP value. Internally, the OSM preserves the EXP value in the QoS group so matching on the QoS group at the PE2 egress provides the same effect as matching on the EXP value.
Figure 31-3 CLP and EXP Mapping
CE1
PE1
PE2
CE2
See the following sections:

Match on ATM CLP Bit, page 31-10 Set on ATM CLP Bit, page 31-12
Match on ATM CLP Bit

Use Match on ATM CLP Bit at the ingress to an MPLS AToM network to map the ATM cell loss priority (CLP) of the packet arriving at an interface to the EXP value, and then apply the desired QoS functionality and actions (for example, traffic policing) to those packets.
Restrictions for Match on ATM CLP Bit

This feature is supported on policy maps attached to ATM permanent virtual circuits (PVCs) only.
31-10
59525
OL-13013-06
Chapter 31
Configuring Multiprotocol Label Switching DE/CLP and EXP Mapping on FR/ATMoMPLS VC
Configuring Match on ATM CLP Bit for Ingress Policy

Perform the following steps to configure Match on ATM CLP Bit for the ingress policy: Command or Action
Router# enable
Purpose Enables privileged EXEC mode. Enter your password if prompted. Enters global configuration mode. Specifies the user-defined name of the traffic class. Enables packet matching on the basis of the ATM CLP bit set to 1. Specifies the name of the traffic policy to configure. Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy. Designates the value to which the MPLS bits are set if the packets match the specified policy map. Enters interface configuration mode. Entesr ATM virtual circuit configuration mode. Attaches a traffic policy to an interface.
Router(config)# configure terminal Router(config)# class-map class-name Router(config-cmap)# match atm clp
Router(config-cmap)# policy-map policy-name Router(config-pmap)# class class-name
Router(config-pmap-c)# set mpls experimental value Router(config)# interface atm interface-number Router(config-if)# pvc [name] vpi/vci [l2transport] Router(config-if)# service-policy input policy-name
The following is an example of a Match on ATM CLP Bit configuration:

Router# conf t Enter configuration commands, one per line. End with CNTL/Z. Router(config)#class-map CLP Router(config-cmap)#match atm clp Router(config-cmap)#exit Router(config)#policy-map CLP2EXP Router(config-pmap)#class CLP Router(config-pmap-c)#set mpls experimental 1 Router(config-pmap-c)#exit Router(config-pmap)#interface ATM3/0 Router(config-if)#pvc 1/100 Router(cfg-if-atm-l2trans-pvc)#service-policy input CLP2EXP Router(cfg-if-atm-l2trans-pvc)#end Router#
Use the show policy-map interface command to verify the Match on ATM CLP bit as in the following example:
CFLOW_PE1# show policy-map interface a3/0 ATM3/0/0: VC 1/100 Service-policy input: CLP2EXP Class-map: CLP (match-all) 200 packets, 22400 bytes 5 minute offered rate 2000 bps, drop rate 0 bps Match: atm clp QoS Set mpls experimental imposition 1
31-11
Chapter 31 DE/CLP and EXP Mapping on FR/ATMoMPLS VC
Packets marked 200 Class-map: class-default (match-any) 0 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: any CFLOW_PE1#
Set on ATM CLP Bit

Use Set on ATM CLP Bit at the egress of an MPLS AToM network to map the EXP value to the ATM CLP bit.
Restrictions for Set on ATM CLP Bit

This feature is supported on policy maps attached to ATM permanent virtual circuits (PVCs) only.
Configuring Set on ATM CLP Bit for Egress Policy

Perform the following steps to configure Set on ATM CLP Bit for the ingress policy: Command or Action
Router# enable
Purpose Enables privileged EXEC mode. Enter your password if prompted. Enters global configuration mode. Specifies the user-defined name of the traffic class. Identifies a specific quality of service (QoS) group value as a match criterion. The QoS group value has no mathematical significance.
Note
Router(config)# configure terminal Router(config)# class-map class-name Router(config-cmap)# match qos-group qos-group-value
The QoS group concept is directly derived from the incoming MPLS EXP value and is valid only with AToM. You cannot use MQC to set QoS group value.
Step 5 Step 6
Router(config-cmap)# policy-map policy-name Router(config-pmap)# class class-name
Specifies the name of the traffic policy to configure. Specifies the name of a predefined traffic class, which was configured with the class-map command, used to classify traffic to the traffic policy. Sets the cell loss priority (CLP) bit when a policy map is configured. Enters the interface and enters interface configuration mode. Attaches a traffic policy to an interface.
Router(config-pmap-c)# set atm-clp
Router(config)# interface slot/port
Router(config-if)# service-policy input policy-name
The following shows how to configure Set on ATM CLP Bit:

arthos# show policy-map qg2clp
31-12
OL-13013-06
Chapter 31
Configuring Multiprotocol Label Switching VPN Switching
Policy Map qg2clp Class qg1 set atm-clp arthos# show class-map qg1 Class Map match-all qg1 (id 23) Match qos-group 1 arthos# show run int a9/1 interface ATM9/1 no ip address atm clock INTERNAL atm mtu-reject-call mls qos trust dscp pvc 1/100 l2transport encapsulation aal5 mpls l2transport route 101.101.101.101 1000 service-policy out qg2clp
Verify the configuration with the show policy-map interface command.

arthos# show policy interface ATM9/1 ATM9/1: VC 1/100 Service-policy output: qg2clp Class-map: qg1 (match-all) 1000 packets, 0 bytes 5 minute offered rate 0 bps, drop rate 0 bps Match: qos-group 1 QoS Set atm-clp Packets marked 1000
VPN Switching
These sections describe VPN switching:

VPN Switching Operation, page 31-13 MPLS VPN Guidelines and Restrictions, page 31-14 MPLS VPN Supported Commands, page 31-14 MPLS VPN Sample Configuration, page 31-15
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. See 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 31-4.
31-13
Chapter 31 VPN Switching
Figure 31-4
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 PFC makes a forwarding decision based on the packet headers. The PFC contains a table that maps VLANs to VPNs. In the switch architecture, all physical ingress interfaces in the system are associated with a specific VPN. The PFC 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 module 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 PFC 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 PFC 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, note that VPNs are recirculated when the number of VPNs is over 511.
MPLS VPN Supported Commands

MPLS VPN supports these commands:
31-14
OL-13013-06
Chapter 31
Configuring Multiprotocol Label Switching VPN Switching
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 this publication: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html
Configuring MPLS VPN

For information on configuring MPLS VPN, see 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#Configuring_MPLS_Virtual_Private_Networks
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 and FlexWAN CE-facing interfaces. MPLS switching configuration in Cisco IOS Release 12.2SX is identical to configuration in other releases.
!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 !
31-15
Chapter 31 VPN Switching
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 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 !
31-16
OL-13013-06
Chapter 31
Configuring Multiprotocol Label Switching Any Transport over MPLS
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 Cisco IOS Release 12.2SX:

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.
Cisco IOS Release 12.2SX supports both PFC-accelerated EoMPLS as well as 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 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 31-17 Understanding EoMPLS, page 31-17 EoMPLS Guidelines and Restrictions, page 31-18 Configuring EoMPLS, page 31-19 Configuring MUX-UNI Support on LAN Cards, page 31-26
AToM Load Balancing

EoMPLS in Cisco IOS Release 12.2SX 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.
31-17
Chapter 31 Any Transport over MPLS
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 FlexWAN-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 a FlexWAN module. 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. 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. Cisco IOS Release 12.2SX 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.
The no mls qos rewrite ip dscp command is not compatible with the MPLS and MPLS VPN
features. See Chapter 40, Configuring PFC QoS.

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 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 not directed to the EoMPLS cloud.
The native VLAN of a trunk must not be configured as an EoMPLS VLAN.
In Cisco IOS Release 12.2SX, 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.
31-18
OL-13013-06
Chapter 31
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 PFC 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 FlexWAN modules as uplinks. 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 31-19 Configuring VLAN-Based EoMPLS, page 31-20 Configuring Port-Based EoMPLS, page 31-23
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 Cisco IOS Release 12.2SX:
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, EoMPLS in Cisco IOS Release 12.2SX does not allow local switching of packets between interfaces unless you use loopback ports.
31-19
A system can have both FlexWAN configuration and PFC configuration enabled at the same time. Cisco supports this configuration but does not recommend it. Unless the uplinks to the MPLS core are through FlexWAN interfaces, FlexWAN-based EoMPLS connections will not be active; this causes packets for FlexWAN-based EoMPLS arriving on non-WAN interfaces to be dropped. For information on FlexWAN 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
In Cisco IOS Release 12.2SX, LAN ports can receive Layer 2 traffic, impose labels, and switch the frames into the MPLS core without using a FlexWAN module. With Cisco IOS Release 12.2SX, you can configure a FlexWAN module to face the core of MPLS network and use either the FlexWAN configuration or the PFC 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 VLAN-Based EoMPLS

When configuring 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 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 VLAN-based EoMPLS configuration sample:

! interface GigabitEthernet7/4.2 encapsulation dot1Q 3 xconnect 13.13.13.13 3 encapsulation mpls no shut
31-20
OL-13013-06
Chapter 31
Note
The IP address is configured on subinterfaces of the CE devices.
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
31-21
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.
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
31-22
OL-13013-06
Chapter 31
MTU: local 1500, remote 1500 Remote interface description: Sequencing: receive disabled, send disabled VC statistics: packet totals: receive 1406, send 1414 byte totals: receive 185497, send 191917 packet drops: receive 0, send 0
Configuring Port-Based EoMPLS

When configuring port-based EoMPLS in Cisco IOS Release 12.2SX, 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 Cisco IOS Release 12.2SX, 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
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:
31-23
router# show run interface g7/11 Building configuration... 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 !
31-24
OL-13013-06
Chapter 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 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 Bytes tag switched \ Outgoing interface Next Hop
31-25
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
0 55146580 0 0 0
Gi2/1 Vl2 GE3/3 GE3/3 GE3/3
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. 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
Configuring MUX-UNI Support on LAN Cards

A User Network Interface (UNI) is the point where the customer edge (CE) equipment connects to the ingress PE and an attachment VLAN is a VLAN on a UNI port. The MUX-UNI support on LAN cards feature provides the ability to partition a physical port on an attachment VLAN to provide multiple Layer 2 and Layer 3 services over a single UNI. When configuring MUX-UNI support on LAN cards, follow these guidelines and restrictions:

Encapsulation on main interface has to be dot1Q and not ISL. With dot1q encapsulation on the main interface, you cannot configure ISL on the subinterfaces; Layer 3 interfaces are unaffected.
To configure MUX-UNI support on LAN cards, perform this task on the provider edge (PE) routers. Command
Router# configure terminal Router(config)# interface type number
Purpose Enters global configuration mode. Selects an interface to configure and enters interface configuration mode; valid only for Ethernet ports. Puts an interface that is in Layer 3 mode into Layer 2 mode for Layer 2 configuration. Configures the port to support 802.1Q encapsulation. You must configure each end of the link with the same encapsulation type.
Note
Router(config-if)# switchport trunk encapsulation {isl | dot1q}
The valid choice for MUX-UNI support is dot1Q.
Step 5
Router(config-if)# switchport mode trunk
Configures the port as a VLAN trunk.
31-26
OL-13013-06
Chapter 31
Step 6
Router(config-if)# switchport trunk allowed vlan vlan-list
By default, all VLANs are allowed. Use this command to explicitly allow VLANs; valid values for vlan-list are from 1 to 4094.
Note
Avoid overlapping VLAN assignments between main and subinterfaces. VLAN assignments between the main interface and subinterfaces must be mutually exclusive.
Router(config-if)# exit Router(config)# interface type slot/port.subinterface-number Router(config-if)# encapsulation dot1q vlan_id
Exits interface configuration mode. Selects a subinterface to configure and enters interface configuration mode; valid only for Ethernet ports. 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 10
Binds the attachment circuit to a pseudowire VC. The syntax for this command is the same as for all other Layer 2 transports.
This example shows a physical trunk port used as UNI:

Router(config)# interface Fastethernet3/1 Router(config-if)# switchport Router(config-if)# switchport encapsulation dot1q Router(config-if)# switchport mode trunk Router(config-if)# switchport trunk allowed VLAN 200-250 Router(config-if)# exit Router(config)# interface Fastethernet3/1.10 Router(config-if)# encap dot1q 3000 Router(config-if)# xconnect 10.0.0.1 3000 encapsulation mpls Router(config-if)# exit
This example shows a Layer 2 port channel used as UNI:

Router(config)# interface Port-channel100 Router(config-if)# switchport Router(config-if)# switchport trunk encapsulation dot1q Router(config-if)# switchport trunk allowed VLAN 100-200 Router(config-if)# switchport mode trunk Router(config-if)# no ip address Router(config-if)# exit Router(config)# interface Port-channel100.1 Router(config-if)# encapsulation dot1Q 3100 Router(config-if)# xconnect 10.0.0.30 100 encapsulation mpls Router(config-if)# exit
This example shows Layer 3 termination and VRF for muxed UNI ports:
Router(config)# vlan 200, 300, 400 Router(config)# interface Fastethernet3/1 Router(config-if)# switchport
31-27
Router(config-if)# Router(config-if)# Router(config-if)# Router(config-if)#
switchport encapsulation dot1q switchport mode trunk switchport trunk allowed VLAN 200-500 exit
Router(config)# interface Fastethernet3/1.10 Router(config-if)# encap dot1q 3000 Router(config-if)# xconnect 10.0.0.1 3000 encapsulation mpls Router(config-if)# exit Router(config)# interface Vlan 200 Router(config-if)# ip address 1.1.1.3 Router(config-if)# exit Router(config)# interface Vlan 300 Router(config-if)# ip vpn VRF A Router(config-if)# ip address 3.3.3.1 Router(config-if)# exit Router(config)# interface Vlan 400 Router(config-if)# ip address 4.4.4.1 Router(config-if)# ip ospf network broadcast Router(config-if)# mpls label protocol ldp Router(config-if)# mpls ip Router(config-if)# exit
Tip
31-28
OL-13013-06
PA R T
IP Switching
C H A P T E R
32

This chapter describes how to configure IP unicast Layer 3 switching in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Layer 3 Switching, page 32-2 Default Hardware Layer 3 Switching Configuration, page 32-4 Configuration Guidelines and Restrictions, page 32-4 Configuring Hardware Layer 3 Switching, page 32-5 Displaying Hardware Layer 3 Switching Statistics, page 32-6
Note
IPX traffic is fast switched on the route proccessor (RP). For more information, see 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 35, Configuring IPv4 Multicast Layer 3 Switching.
32-1
Understanding Layer 3 Switching

These sections describe Layer 3 switching:

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

Hardware Layer 3 switching allows the PFC and DFCs, instead of the RP, 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 RP. Hardware Layer 3 switching requires minimal support from the RP. The RP routes any traffic that cannot be hardware Layer 3 switched. Hardware Layer 3 switching supports the routing protocols configured on the RP. Hardware Layer 3 switching does not replace the routing protocols configured on the RP. 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 flow-based switching for TCP intercept and 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 RP 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 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 61, 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 switch performs a packet rewrite at the egress port based on information learned from the RP so that the packets appear to have been routed by the RP. 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.
32-2
OL-13013-06
Chapter 32
Configuring IP Unicast Layer 3 Switching Understanding Layer 3 Switching
If Source A and Destination B are in different subnets and Source A sends a packet to the RP to be routed to Destination B, the switch recognizes that the packet was sent to the Layer 2 (MAC) address of the RP. 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 RP. 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 RP 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 RP 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 32-1 on page 32-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.
32-3
Chapter 32 Default Hardware Layer 3 Switching Configuration
Figure 32-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 32-1 shows the default hardware Layer 3 switching configuration.
Table 32-1 Default Hardware Layer 3 Switching Configuration
Feature Hardware Layer 3 switching enable state Cisco IOS CEF enable state on RP Cisco IOS dCEF enable state on RP
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)
32-4
44610
Host C 171.59.2.2 Data 171.59.1.2:171.59.2.2 Dd:Cc
OL-13013-06
Chapter 32
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 RP, see Chapter 29, 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 = 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 RP apply only to traffic that is CEF-switched in software on the RP. 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 RP, see 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
32-5
Chapter 32 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
32-6
OL-13013-06
PA R T
IPv6
C H A P T E R
33
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching

The PFC3 and DFC3 provide hardware support for IPv6 multicast traffic. Use these publications to configure IPv6 multicast in Cisco IOS Release 12.2SX:
The Cisco IOS IPv6 Configuration Library, Implementing IPv6 Multicast: http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/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
Tip
These sections provide additional information about IPv6 multicast support in Cisco IOS Release 12.2SX:

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

These features support IPv6 multicast:

RPR redundancy modeSee Chapter 7, Configuring RPR Supervisor Engine Redundancy. Multicast Listener Discovery version 2 (MLDv2) snoopingSee Chapter 34, Configuring MLD Snooping for IPv6 Multicast Traffic.
Note
MLDv1 snooping is not supported.
33-1
Chapter 33 IPv6 Multicast Guidelines and Restrictions
IPv6 Multicast rate limitersSee Chapter 49, Configuring Denial of Service Protection. IPv6 Multicast: Bootstrap Router (BSR)See the BSR information in the Cisco IOS IPv6 Configuration Library and the Cisco IOS IPv6 Command Reference. IPv6 Access ServicesSee DHCPv6 Prefix DelegationSee this publication for more information: http://www.cisco.com/en/US/docs/ios/12_2t/ipv6/ipv6_vgf.html SSM mapping for IPv6See this publication for more information: http://www.cisco.com/en/US/docs/ios/12_2t/ipv6/ipv6_vgf.html
IPv6 Multicast Guidelines and Restrictions

These guidelines and restrictions apply to IPv6 multicast support in Cisco IOS Release 12.2SX:
The PFC3 and DFC3 provide hardware support for the following:
Completely switched IPv6 multicast flows IPv6 PIM-Sparse Mode (PIM-SM) (S,G) and (*,G) forwarding
Note
Release 12.2(33)SXH provides initial support for IPv6 PIM-SM (*,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 redundancy mode (see Chapter 7, Configuring RPR Supervisor Engine Redundancy) Ingress and egress PFC QoS (see Chapter 40, Configuring PFC QoS) Input and output Cisco access-control lists (ACLs)
The PFC3 and DFC3 do not provide hardware support for the following:
Partially switched IPv6 multicast flows 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
33-2
OL-13013-06
Chapter 33
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching New or Changed IPv6 Multicast Commands
IPv6-in-IPv6 PIM register tunnels IPv6 multicast basic ISATAP tunnels ISATAP tunnels with embedded 6to4 tunnels
New or Changed IPv6 Multicast Commands

See the Cisco IOS Master Command List, Release 12.2SX for information about these IPv6 multicast commands:

ipv6 mfib hardware-switching mls rate-limit multicast ipv6 (see Chapter 49, Configuring Denial of Service Protection) show ipv6 mfib show mls rate-limit (see Chapter 49, Configuring Denial of Service Protection) show platform software ipv6-multicast show tcam interface

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 33-4 Displaying the Switching Capability, page 33-4 Verifying the (S,G) Forwarding Capability, page 33-5 Verifying the (*,G) Forwarding Capability, page 33-5 Verifying the Subnet Entry Support Status, page 33-5 Verifying the Current Replication Mode, page 33-5 Displaying the Replication Mode Auto-Detection Status, page 33-5 Displaying the Replication Mode Capabilities, page 33-5 Displaying Subnet Entries, page 33-6 Displaying the IPv6 Multicast Summary, page 33-6
33-3
Chapter 33 Using show Commands to Verify IPv6 Multicast Layer 3 Switching
Displaying the NetFlow Hardware Forwarding Count, page 33-6 Displaying the FIB Hardware Bridging and Drop Counts, page 33-7 Displaying the Shared and Well-Known Hardware Adjacency Counters, page 33-7
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 route processor (RP):
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)
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
33-4
OL-13013-06
Chapter 33
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching Using show Commands to Verify IPv6 Multicast Layer 3 Switching
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.
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
33-5
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 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...>
33-6
OL-13013-06
Chapter 33
Configuring IPv6 Multicast PFC3 and DFC3 Layer 3 Switching Using show Commands to Verify IPv6 Multicast Layer 3 Switching
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 RP.
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.
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] ---Index Packets Bytes ------ ------------- -----------------0x7F802 0 0 0x7 0 0 0x8 0 0 0x9 0 0 0xA 0 0 0xB 0 0 0xC 0 0
33-7
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
Tip
33-8
OL-13013-06
C H A P T E R
34
Configuring MLD Snooping for IPv6 Multicast Traffic

This chapter describes how to configure Multicast Listener Discovery (MLD) snooping for IPv6 multicast traffic in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html To constrain IPv4 multicast traffic, see Chapter 36, Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic. PFC3C and PFC3CXL modes support MLD version 1 (MLDv1) and MLD version 2 (MLDv2). These modes support only MLD version 2 (MLDv2):
PFC3A PFC3B PFC3BXL
Tip

Understanding MLD Snooping, page 34-2 Default MLD Snooping Configuration, page 34-8 MLD Snooping Configuration Guidelines and Restrictions, page 34-8 MLD Snooping Querier Configuration Guidelines and Restrictions, page 34-9 Enabling the MLD Snooping Querier, page 34-9 Configuring MLD Snooping, page 34-10
34-1
Chapter 34 Understanding MLD Snooping
Understanding MLD Snooping

These sections describe MLD snooping:

MLD Snooping Overview, page 34-2 MLD Messages, page 34-3 Source-Based Filtering, page 34-3 Explicit Host Tracking, page 34-3 MLD Snooping Proxy Reporting, page 34-4 Joining an IPv6 Multicast Group, page 34-4 Leaving a Multicast Group, page 34-6 Understanding the MLD Snooping Querier, page 34-7
MLD Snooping Overview

MLD snooping allows the switch to examine MLD packets and make forwarding decisions based on their content. You can configure the switch to use MLD snooping in subnets that receive MLD queries from either MLD or the MLD snooping querier. MLD 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. MLD, which runs at Layer 3 on a multicast router, generates Layer 3 MLD queries in subnets where the multicast traffic needs to be routed. For information about MLD, see this publication: http://www.cisco.com/en/US/docs/ios/ipv6/configuration/guide/12_2sx/ipv6_12_2sx_book.html You can configure the MLD snooping querier on the switch to support MLD snooping in subnets that do not have any multicast router interfaces. For more information about the MLD snooping querier, see the Enabling the MLD Snooping Querier section on page 34-9. MLD (on a multicast router) or, locally, the MLD snooping querier, sends out periodic general MLD queries that the switch forwards through all ports in the VLAN, and to which hosts respond. MLD snooping monitors the Layer 3 MLD traffic.
Note
PFC/DFC 3C/3CXL supports source-only Layer 2 entries, but 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, MLD snooping constrains the multicast traffic to only the multicast router ports.
34-2
OL-13013-06
Chapter 34
Configuring MLD Snooping for IPv6 Multicast Traffic Understanding MLD Snooping
MLD Messages
These are the MLD 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
MLD 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 MLD messages:

Source lists INCLUDE or EXCLUDE mode
Because the Layer 2 table is (MAC-group, VLAN) based, with MLD 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

MLD 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 MLD snooping software processes the MLD 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
34-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.
MLD Snooping Proxy Reporting

Because MLD 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, MLD 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 MLD report or by sending an MLD 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 MLD 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 MLD 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 MLD report. MLD 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 34-1). Layer 2 multicast groups learned through MLD 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 MLD snooping learning. Multicast group membership lists can consist of both static and MLD snooping-learned settings.
34-4
OL-13013-06
Chapter 34
Figure 34-1
Initial MLD 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 MLD 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 MLD report to the group with the equivalent MAC destination address of 0x0100.5E01.0203. When the switch snoops the MLD report multicast by Host 1, the switch uses the information in the MLD report to create a forwarding-table entry. Table 34-1 shows the forwarding table, which includes the port numbers of Host 1, the multicast router, and the switch.
Table 34-1 MLD Snooping Forwarding Table
Destination MAC Address 0100.5exx.xxxx 0100.5e01.0203
Type of Packet MLD !MLD
Ports 0 1, 2
The switch hardware can distinguish MLD information packets from other packets for the multicast group. The first entry in the table indicates that only MLD packets should be sent to the CPU, which prevents the switch from becoming overloaded with multicast frames. The second entry indicates that frames addressed to the 0x0100.5E01.0203 multicast MAC address that are not MLD packets (!MLD) should be sent to the multicast router and to the host that has joined the group. If another host (for example, Host 4) sends an unsolicited MLD report for the same group (Figure 34-2), the switch snoops that message and adds the port number of Host 4 to the forwarding table as shown in Table 34-2. Because the forwarding table directs MLD 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
34-5
Figure 34-2
Second Host Joining a Multicast Group
Router A
1 VLAN
PFC CPU 0
Host 1
Host 2
Host 3
Host 4
Table 34-2
Updated MLD Snooping Forwarding Table
Destination MAC Address 0100.5exx.xxxx 0100.5e01.0203
Type of Packet MLD !MLD
Leaving a Multicast Group

These sections describe leaving a multicast group:

Normal Leave Processing, page 34-6 Fast-Leave Processing, page 34-7
Normal Leave Processing

Interested hosts must continue to respond to the periodic MLD general queries. As long as at least one host in the VLAN responds to the periodic MLD 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 MLD general queries (called a silent leave), or they can send an MLD filter mode change record. When MLD snooping receives a filter mode change record from a host that configures the EXCLUDE mode for a group, MLD 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 MLD snooping does not receive an MLD report in response to the general query, MLD snooping assumes that no other hosts connected to the interface are interested in receiving traffic for the specified multicast group, and MLD snooping removes the interface from its Layer 2 forwarding table entry for the specified multicast group.
34-6
45751
Forwarding table
Ports 0 1, 2, 5
OL-13013-06
Chapter 34
If the filter mode change record was from the only remaining interface with hosts interested in the group, and MLD snooping does not receive an MLD report in response to the general query, MLD snooping removes the group entry and relays the MLD 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 MLD 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 MLD Snooping Querier

Use the MLD snooping querier to support MLD snooping in a VLAN where PIM and MLD 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 MLD 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 MLD querier so that it can send queries. When enabled, the MLD snooping querier sends out periodic MLD queries that trigger MLD report messages from the switch that wants to receive IP multicast traffic. MLD snooping listens to these MLD reports to establish appropriate forwarding. You can enable the MLD snooping querier on all the switches in the VLAN, but for each VLAN that is connected to switches that use MLD to report interest in IP multicast traffic, you must configure at least one switch as the MLD snooping querier. You can configure a switch to generate MLD queries on a VLAN regardless of whether or not IP multicast routing is enabled.
34-7
Chapter 34 Default MLD Snooping Configuration
Default MLD Snooping Configuration

Table 34-3 shows the default MLD snooping configuration.
Table 34-3 MLD Snooping Default Configuration
Feature MLD snooping querier MLD snooping Multicast routers MLD report suppression MLD snooping router learning method Fast-Leave Processing MLD Explicit Host Tracking
Default Values Disabled Enabled None configured Enabled Learned automatically through PIM or MLD packets Enabled Enabled
MLD Snooping Configuration Guidelines and Restrictions

When configuring MLD snooping, follow these guidelines and restrictions:

Only PFC3C and PFC3CXL modes support MLD version 1 (MLDv1) and MLD version 2 (MLDv2). These modes support only MLD version 2 (MLDv2):
PFC3A PFC3B PFC3BXL
MLD is derived from Internet Group Management Protocol version 3 (IGMPv3). MLD 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-.02.txt for detailed information on MLD protocol. MLD protocol messages are Internet Control Message Protocol version 6 (ICMPv6) messages. MLD 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. MLD snooping supports private VLANs. Private VLANs do not impose any restrictions on MLD snooping. MLD snooping constrains traffic in MAC multicast groups 0100.5e00.0001 to 0100.5eff.ffff. MLD snooping does not constrain Layer 2 multicasts generated by routing protocols.
34-8
OL-13013-06
Chapter 34
Configuring MLD Snooping for IPv6 Multicast Traffic MLD Snooping Querier Configuration Guidelines and Restrictions
MLD Snooping Querier Configuration Guidelines and Restrictions

When configuring the MLD snooping querier, follow these guidelines and restrictions:

Configure the VLAN in global configuration mode (see Chapter 22, Configuring VLANs). Configure an IPv6 address on the VLAN interface (see Chapter 29, Configuring Layer 3 Interfaces). When enabled, the MLD snooping querier uses the IPv6 address as the query source address. If there is no IPv6 address configured on the VLAN interface, the MLD snooping querier does not start. The MLD snooping querier disables itself if the IPv6 address is cleared. When enabled, the MLD snooping querier restarts if you configure an IPv6 address. When enabled, the MLD snooping querier does not start if it detects MLD traffic from an IPv6 multicast router. When enabled, the MLD snooping querier starts after 60 seconds with no MLD traffic detected from an IPv6 multicast router. When enabled, the MLD snooping querier disables itself if it detects MLD traffic from an IPv6 multicast router. QoS does not support MLD packets when MLD snooping is enabled. You can enable the MLD snooping querier on all the switches in the VLAN that support it. One switch is elected as the querier.
Enabling the MLD Snooping Querier

Use the MLD snooping querier to support MLD snooping in a VLAN where PIM and MLD are not configured because the multicast traffic does not need to be routed. To enable the MLD 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 MLD snooping querier. Disables the MLD 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 MLD 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
34-9
Chapter 34 Configuring MLD Snooping
Configuring MLD Snooping

Note
To use MLD snooping, configure a Layer 3 interface in the subnet for IPv6 multicast routing or enable the MLD snooping querier in the subnet (see the Enabling the MLD Snooping Querier section on page 34-9). These sections describe how to configure MLD snooping:

Enabling MLD Snooping, page 34-10 Configuring a Static Connection to a Multicast Receiver, page 34-11 Enabling Fast-Leave Processing, page 34-12 Configuring Explicit Host Tracking, page 34-13 Configuring Report Suppression, page 34-14 Displaying MLD Snooping Information, page 34-14
Note
Except for the global enable command, all MLD snooping commands are supported only on VLAN interfaces.
Enabling MLD Snooping

To enable MLD snooping globally, perform this task: Command
Step 1
Router(config)# ipv6 mld snooping Router(config)# no ipv6 mld snooping
Purpose Enables MLD snooping. Disables MLD 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 MLD 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 MLD 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 MLD snooping. Disables MLD snooping.
34-10
OL-13013-06
Chapter 34
Configuring MLD Snooping for IPv6 Multicast Traffic Configuring MLD 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 MLD 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-if)# end Router# show mac-address-table address mac_addr 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Configures a static connection to a multicast receiver.
Step 2 Step 3
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)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping mrouter interface type1 slot/port Router(config-if)# end Router# show ipv6 mld snooping mrouter
Purpose Selects the VLAN interface. Configures a static connection to a multicast router. Exits configuration mode. Verifies the configuration.
34-11
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. Verifies the configuration.
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
Enabling Fast-Leave Processing

To enable fast-leave processing in a VLAN, perform this task: Command
Router(config)# interface vlan vlan_ID Router(config-if)# ipv6 mld snooping fast-leave Router# show ipv6 mld interface vlan vlan_ID | include fast-leave
Purpose Selects a VLAN interface. Enables fast-leave processing in the VLAN. Verifies the configuration.
34-12
OL-13013-06
Chapter 34
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
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 ------------------------------------------------------------------------
34-13
10.1.1.1/226.2.2.2 10.2.2.2/226.2.2.2
Vl25:1/2 Vl25:1/2
16.27.2.3 16.27.2.3
INCLUDE 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
Displaying MLD Snooping Information

These sections describe displaying MLD snooping information:

Displaying Multicast Router Interfaces, page 34-14 Displaying MAC Address Multicast Entries, page 34-15 Displaying MLD Snooping Information for a VLAN Interface, page 34-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 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#
34-14
OL-13013-06
Chapter 34
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
Displaying MLD Snooping Information for a VLAN Interface

Note
When you apply the ipv6 mld snooping command and associated commands on any VLAN interface, the commands continue to function even if the VLAN interface is in shutdown state. To display MLD 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 MLD 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
34-15
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
34-16
OL-13013-06
PA R T
IP Multicast
C H A P T E R
35

This chapter describes how to configure IPv4 multicast Layer 3 switching in Cisco IOS Release 12.2SX.
Note
Tip

Understanding IPv4 Multicast Layer 3 Switching, page 35-1 Understanding IPv4 Bidirectional PIM, page 35-9 Default IPv4 Multicast Layer 3 Switching Configuration, page 35-9 IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions, page 35-10 Configuring IPv4 Multicast Layer 3 Switching, page 35-11 Configuring IPv4 Bidirectional PIM, page 35-24
Understanding IPv4 Multicast Layer 3 Switching

These sections describe how IPv4 multicast Layer 3 switching works:

IPv4 Multicast Layer 3 Switching Overview, page 35-2 Multicast Layer 3 Switching Cache, page 35-2
35-1
Chapter 35 Understanding IPv4 Multicast Layer 3 Switching
Layer 3-Switched Multicast Packet Rewrite, page 35-3 Partially and Completely Switched Flows, page 35-4 Non-RPF Traffic Processing, page 35-5 Multicast Boundary, page 35-8 Understanding IPv4 Bidirectional PIM, page 35-9
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 36, Configuring IGMP Snooping and MVR 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. In the event of a forwarding information database (FIB) fatal error, the default error action is for the system to reset and the FIB to reload. The route processor (RP) 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 RP ages out, the RP 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. 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.
35-2
OL-13013-06
Chapter 35
Configuring IPv4 Multicast Layer 3 Switching Understanding IPv4 Multicast Layer 3 Switching
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 RP 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 RP 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 RP 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 RP (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 RP MAC IP Header Destination Group G1 IP Source Source A IP TTL n1 Checksum calculation2 Data FCS
35-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 RP 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 35-4 Completely Switched Flows, page 35-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. 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:

(*,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.
35-4
OL-13013-06
Chapter 35
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 RP interface in that VLAN, freeing the RP 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 RP. The RP 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 35-5 Filtering of RPF Failures for Stub Networks, page 35-8 Rate Limiting of RPF Failure Traffic, page 35-8
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 35-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 PFC hardware processes non-RPF traffic by filtering (dropping) or rate limiting the non-RPF traffic.
35-5
Figure 35-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
The conflicting requirements for the non-RPF traffic in the PFC3 prevent the majority of traffic from reaching the RP. However, leaking some packets to the RP ensures that correct protocol operations are met by using the hardware NetFlow table on the PFC3. By default, the NetFlow non-RPF traffic handling is enabled on the Supervisor Engine 720, and it cannot be disabled. When the first non-RPF packet for an existing multicast FIB table entry is received, a matching (S,G) FIB TCAM entry for the packet is found; however, the RPF check is mismatched so a non-RPF NetFlow entry for the multicast entry is created in the NetFlow table. The packet is then bridged to the non-RPF VLAN and the RP for further processing. The NetFlow search engine removes all of the non-RPF NetFlow entries from the hardware every 20 seconds. The next non-RPF packet received for a FIB TCAM entry triggers the creation of a non-RPF NetFlow entry while bridging the packet to the RP CPU. This operation results in only a single packet for each non-RPF NetFlow entry which will be bridged to the RP CPU approximately every 20 seconds, regardless of the rate of the various multicast traffic flows passing through the system.
Note
The non-RPF NetFlow entries are created only for PIM-SM, PIM-DM, and SSM multicast FIB entries. Because the Bidir PIM does not use the PIM assert mechanism, non-RPF NetFlow entries are never created for Bidir PIM FIB entries. In addition to the 20-second periodic timer, any non-RPF NetFlow entries that remain unused for more than 2 seconds are automatically purged to conserve NetFlow table resources. To view details of the multicast non-RPF entries in the NetFlow table, use the show mls netflow ip multicast rpf-fail command from the SP console. This example shows how to display RPF fail information:
Router (config)# mls netflow ip multicast rpf-fail Source Destination RPF #packets #bytes Type +---------+---------------+--------+-----------+--------+--------------------------10.14.1.60 225.0.0.158 Vl19 2 92 NRPF 10.14.1.68 225.0.1.110 Vl19 2 92 NRPF 10.14.1.60 225.0.1.102 Vl19 2 92 NRPF 10.14.1.137 225.0.0.235 Vl19 121 5566 NRPF 10.14.1.135 225.0.0.233 Vl19 122 5612 NRPF 10.14.1.127 225.0.0.225 Vl19 122 5612 NRPF 10.14.1.124 225.0.0.222 Vl19 122 5612 NRPF 10.14.1.81 225.0.1.123 Vl19 2 92 NRPF 10.14.1.67 225.0.1.109 Vl19 2 92 NRPF
35-6
55645
OL-13013-06
Chapter 35
10.14.1.41
225.0.1.83
Vl19
92
NRPF
If the NetFlow table is full when the system attempts to create a new non-RPF NetFlow entry, the packet is bridged in the VLAN and is also forwarded to a reserved adjacency that punts the packet to the RP CPU. By default, the traffic sent to this adjacency entry is not rate limited. To protect the RP CPU from excess non-RPF packets, rate limit the traffic sent to this adjacency by using the mls rate limit multicast non-rpf rate burst command. You can check whether the NetFlow table is full by using the show mls netflow table contention summary command.
35-7
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 35-18.
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 RP 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 RP. To support the PIM assert mechanism, the PFC periodically forwards a percentage of the non-RPF flow packets to the RP. The first packets for directly connected sources in PIM sparse mode are also rate-limited and are processed by the CPU. By default, rate limiting of RPF failures is disabled . The non-RPF hardware rate limiter offers an alternative method for handling the non-RPF multicast traffic. You can enable the traffic-handling method by using the mls rate-limit multicast non-rpf command. The configured rate represents the aggregate of all non-RPF traffic punted to the RP CPU. We recommend that you enable the rate limiter when the NetFlow table is full. By default, the rate limiter is disabled.
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.
35-8
OL-13013-06
Chapter 35
Configuring IPv4 Multicast Layer 3 Switching Understanding IPv4 Bidirectional PIM
Multicast boundary ACLs can be processed in hardware by the Policy Feature Card (PFC), a Distributed Forwarding Card (DFC), or in software by the RP. 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 IPv4 Bidirectional PIM

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 switch accepts packets from the RPF and from the DF interfaces. When the switch 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 35-24.
Default IPv4 Multicast Layer 3 Switching Configuration

Table 35-1 shows the default IP multicast Layer 3 switching configuration.
Table 35-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
35-9
Chapter 35 IPv4 Multicast Layer 3 Switching Configuration Guidelines and Restrictions
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 36, Configuring IGMP Snooping and MVR 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 35-10 Unsupported Features, page 35-10
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. 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. 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.
35-10
OL-13013-06
Chapter 35
Configuring IPv4 Multicast Layer 3 Switching Configuring IPv4 Multicast Layer 3 Switching

These sections describe how to configure IP multicast Layer 3 switching:

Source-Specific Multicast with IGMPv3, IGMP v3lite, and URD, page 35-11 Enabling IPv4 Multicast Routing Globally, page 35-11 Enabling IPv4 PIM on Layer 3 Interfaces, page 35-12 Enabling IP Multicast Layer 3 Switching on Layer 3 Interfaces, page 35-13 Configuring the Replication Mode, page 35-13 Enabling Local Egress Replication, page 35-15 Configuring the Layer 3 Switching Global Threshold, page 35-16 Enabling Installation of Directly Connected Subnets, page 35-17 Specifying the Flow Statistics Message Interval, page 35-17 Configuring IPv4 Bidirectional PIM, page 35-24 Setting the IPv4 Bidirectional PIM Scan Interval, page 35-25 Enabling Shortcut-Consistency Checking, page 35-17 Configuring ACL-Based Filtering of RPF Failures, page 35-18 Displaying RPF Failure Rate-Limiting Information, page 35-18 Configuring Multicast Boundary, page 35-19 Displaying IPv4 Multicast Layer 3 Hardware Switching Summary, page 35-19 Displaying the IPv4 Multicast Routing Table, page 35-22 Displaying IPv4 Multicast Layer 3 Switching Statistics, page 35-23 Displaying IPv4 Bidirectional PIM Information, page 35-26 Using IPv4 Debug Commands, page 35-28 Clearing IPv4 Multicast Layer 3 Switching Statistics, page 35-28 Redundancy for Multicast Traffic, page 35-29
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), see 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.
35-11
Chapter 35 Configuring IPv4 Multicast Layer 3 Switching
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
Purpose Enables 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. 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} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Selects an interface to configure. Enables 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
This example shows how to enable PIM sparse mode on an interface:

Router(config-if)# ip pim sparse-mode
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.
35-12
OL-13013-06
Chapter 35
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 35-12. 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. Returns you to global configuration mode.
2
Router(config-if)# exit Router # [no] mls ip multicast syslog
(Optional) Enables display of multicast related syslog messages on console.
1. 2.
type = fastethernet, gigabitethernet, or tengigabitethernet This command is only available in IOS Software Release 12.2SXI and later, and is disabled by default.
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 the Cisco ME 6500 Series Ethernet switches support only ingress replication mode. The Supervisor Engine 720 and Supervisor Engine 720-10GE 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, the switch automatically detects the replication mode based on the switching modules installed in the system. If all switching modules are capable of egress replication, the switch uses egress-replication mode. If the switch detects switching modules that are not capable of egress
35-13
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 switch continues to work in egress-replication mode even if there are fabric-enabled modules installed that do not support egress replication. You can also configure the switch to operate only in ingress-replication mode. If the switch is functioning in automatic detection mode, and you install a switching module that cannot perform egress replication, the following occurs:

The switch reverts to ingress mode A system log is generated A system reload occurs to revert to the old configuration
If the switch 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 switch 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. Egress mode is not compatible with QoS or SPAN. When QoS is configured, egress replication can result in the incorrect COS or DSCP marking. 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

Router(config)# mls ip multicast replication-mode [egress | ingress] Router# show mls ip multicast capability Router# show mls ip multicast summary
Purpose Specifies the replication mode. 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 Multicast replication capability Egress Egress Ingress Egress
35-14
OL-13013-06
Chapter 35
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)#
Enabling Local Egress Replication

Note
Supervisor Engine 32 and the Cisco ME 6500 Series Ethernet switches support only ingress replication mode. With a Supervisor Engine 720 or Supervisor Engine 720-10GE, you can 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. When local egress replication mode is not enabled, both replication engines have the complete outgoing interface list for all modules, and the replication engines process and then drop traffic for nonlocal interfaces. Local egress replication mode limits the outgoing interface list to only the local interfaces that each replication engine supports, which prevents unnecessary processing of multicast traffic. Local egress replication is supported with the following software configuration and hardware:

IPv4 egress replication mode. Dual fabric-connection DFC-equipped modules. All releases can provide local egress replication on Layer 3-routed interfaces and subinterfaces that are not members of an EtherChannel. Releases earlier than Release 12.2(33)SXI cannot provide local egress replication on members of Layer 3 EtherChannels or on VLAN interfaces. Release 12.2(33)SXI and later releases add local egress replication support for members of Layer 3 EtherChannels and VLAN interfaces. 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:

35-15
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.
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 RP. 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
Purpose Configures the 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)#
35-16
OL-13013-06
Chapter 35
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: Command
Router(config)# mls ip multicast connected
Purpose Enables 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 switch processor (SP) forwards flow statistics messages to the route processor (RP) 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 RP. To specify how often flow statistics messages forwarded from the SP to the RP, perform this task: Command
Router(config)# mls ip multicast flow-stat-timer num
Purpose Specifies how the SP forwards flow statistics messages to the RP.
This example shows how to configure the SP to forward flow statistics messages to the RP 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:
35-17
Command
Router(config)# mls ip multicast consistency-check
Purpose Enables shortcut-consistency checking.
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.
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#
35-18
OL-13013-06
Chapter 35
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.
1.
Note
In releases earlier than 12.2(33)SXI, the switch creates an empty ACL (with implicit deny any any) even though the ACL is not preconfigured. However, from 12.2(33)SXI or later releases, if the ACL is not preconfigured, the ip multicast boundary command will not create an empty ACL (with implicit deny any any).
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.
35-19
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 RP 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
35-20
OL-13013-06
Chapter 35
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#
35-21
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.
35-22
OL-13013-06
Chapter 35
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 = 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
35-23
Chapter 35 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 35-24 Configuring the Rendezvous Point for IPv4 Bidirectional PIM Groups, page 35-25 Setting the IPv4 Bidirectional PIM Scan Interval, page 35-25 Displaying IPv4 Bidirectional PIM Information, page 35-26
Enabling IPv4 Bidirectional PIM Globally

To enable IPv4 bidirectional PIM, perform this task: Command
Router(config)# ip pim bidir-enable
Purpose Enables 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)#
35-24
OL-13013-06
Chapter 35
Configuring IPv4 Multicast Layer 3 Switching 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.
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)#
35-25
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
35-26
OL-13013-06
Chapter 35
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
35-27
Using IPv4 Debug Commands

Table 35-2 describes IPv4 multicast Layer 3 switching debug commands that you can use to troubleshoot IP multicast Layer 3 switching problems.
Table 35-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 RP, 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 35-23.
35-28
OL-13013-06
Chapter 35
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
35-29
35-30
OL-13013-06
C H A P T E R
36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic

This chapter describes how to configure Internet Group Management Protocol (IGMP) snooping, including an application of local IGMP snooping, Multicast VLAN Registration (MVR) for IPv4 multicast traffic in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html To constrain IPv6 Multicast traffic, see Chapter 34, Configuring MLD Snooping for IPv6 Multicast Traffic.
Tip

Understanding IGMP Snooping, page 36-2 Default IGMP Snooping Configuration, page 36-7 IGMP Snooping Configuration Guidelines and Restrictions, page 36-8 IGMP Snooping Querier Configuration Guidelines and Restrictions, page 36-8 Enabling the IGMP Snooping Querier, page 36-9 Configuring IGMP Snooping, page 36-9 Understanding MVR, page 36-16 Configuring MVR, page 36-19 Displaying MVR Information, page 36-23
36-1
Chapter 36 Understanding IGMP Snooping
Understanding IGMP Snooping

These sections describe IGMP snooping:

IGMP Snooping Overview, page 36-2 Joining a Multicast Group, page 36-2 Leaving a Multicast Group, page 36-4 Understanding the IGMP Snooping Querier, page 36-5 Understanding IGMP Version 3 Support, page 36-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 35, 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 36-9. IGMP (on a multicast router) or, locally, the IGMP snooping querier, 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 36-1).
36-2
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Understanding IGMP Snooping
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 36-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 36-1, that includes the port numbers of Host 1, the multicast router, and the switch internal CPU.
Table 36-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 36-2), the CPU receives that message and adds the port number of Host 4 to the forwarding table as shown in Table 36-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
36-3
Figure 36-2
Second Host Joining a Multicast Group
Router A
1 VLAN
PFC CPU 0
Host 1
Host 2
Host 3
Host 4
Table 36-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 36-4 Fast-Leave Processing, page 36-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
36-4
45751
Forwarding table
Ports 0 1, 2, 5
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Understanding IGMP Snooping
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 IGMPv3 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 36-6 IGMPv3 Fast-Leave Processing, page 36-6
36-5
Proxy Reporting, page 36-6 Explicit Host Tracking, page 36-7
IGMP Version 3 Support Overview

IGMP snooping supports IGMP version 3 (IGMPv3). IGMPv3 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 IGMPv3 snooping, the switch maintains IGMPv3 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 IGMPv3 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

IGMPv3 fast-leave processing is active if explicit-host tracking is enabled. The ip igmp snooping fast-leave command that enables IGMP version 2 fast-leave processing does not affect IGMPv3 fast-leave processing. 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 active, 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 receives 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 receives 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
36-6
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Default IGMP Snooping Configuration
routers is 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.
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 36-3 shows the default IGMP snooping configuration.
Table 36-3 IGMP Snooping Default Configuration
Feature IGMP snooping querier IGMP snooping Multicast routers IGMPv3 proxy reporting IGMP snooping router learning method Fast-Leave Processing
Default Values Disabled Enabled None configured Enabled Learned automatically through PIM or IGMP packets Disabled
36-7
Chapter 36 IGMP Snooping Configuration Guidelines and Restrictions
Table 36-3
IGMP Snooping Default Configuration (continued)
Feature CGMP Automatic Detection IGMPv3 Explicit Host Tracking
Default Values Enabled Enabled
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 route processor (RP) as a CGMP server. See 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, see 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 22, Configuring VLANs). Configure an IP address on the VLAN interface (see Chapter 29, 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 sends IGMPv3 querier messages. Although the IGMP version of the querier messages is not configurable, the querier is compatible with IGMPv2 hosts. When enabled, the IGMP snooping querier starts after 60 seconds with no IGMP traffic detected from a multicast router. If IGMP traffic from a multicast router, or from another IGMP snooping querier in the VLAN, is detected after the IGMP snooping querier has started, the querier will disable itself. QoS does not support IGMP packets when IGMP snooping is enabled.
36-8
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR 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)# end Router# show ip igmp interface vlan vlan_ID | include querier
Purpose Selects the VLAN interface. Configures the IP address and IP subnet. Enables the IGMP snooping querier. Exits configuration mode. Verifies the configuration.
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 35, 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 36-9). IGMP snooping allows 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 36-10 Configuring a Static Connection to a Multicast Receiver, page 36-11 Configuring a Multicast Router Port Statically, page 36-11 Configuring the IGMP Snooping Query Interval, page 36-11 Enabling IGMP Fast-Leave Processing, page 36-12 Configuring Source-Specific Multicast Mapping, page 36-12 CGMP Automatic Detection, page 36-13 CGMP Automatic Detection, page 36-13 Displaying IGMP Snooping Information, page 36-14
36-9
Chapter 36 Configuring IGMP Snooping
Note
Except for the ip igmp snooping command, all IGMP snooping commands are supported only on VLAN interfaces.
Enabling IGMP Snooping

To enable IGMP snooping globally, perform this task: Command
Router(config)# ip igmp snooping Router(config)# end Router# show ip igmp interface vlan vlan_ID | include globally
Purpose Enables IGMP snooping. Exits configuration mode. Verifies the configuration.
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

Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping Router(config-if)# end Router# show ip igmp interface vlan vlan_ID | include snooping
Purpose Selects a VLAN interface. Enables IGMP snooping. Exits configuration mode. Verifies the configuration.
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#
36-10
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR 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-if)# end Router# show mac-address-table address mac_addr 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Configures a static connection to a multicast receiver.
Step 2 Step 3
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. type = fastethernet, gigabitethernet, or tengigabitethernet
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
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.
36-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.
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

Fast-leave configuration applies to IGMP version 2 hosts only. To enable IGMP fast-leave processing in a VLAN, perform this task: Command
Router(config)# interface vlan vlan_ID Router(config-if)# ip igmp snooping
Purpose Selects a VLAN interface. Enables IGMP snooping. This step is only necessary if IGMP snooping is not already enabled on this VLAN. Enables IGMP fast-leave processing in the VLAN.
Router(config-if)# ip igmp snooping fast-leave
This example shows how to enable IGMP fast-leave processing for IGMP version 2 hosts on the VLAN 200 interface, and how to verify the configuration:
Router# interface vlan 200 Router(config-if)# ip igmp snooping 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
Configuring Source-Specific Multicast Mapping

Note
Do not configure SSM mapping in a VLAN that supports IGMPv3 multicast receivers. To configure source-specific multicast (SSM) mapping, see this publication: http://www.cisco.com/en/US/docs/ios/12_3t/12_3t2/feature/guide/gtssmma.html
36-12
OL-13013-06
Chapter 36
CGMP Automatic Detection

By default, the switch will detect Cisco group management protocol (CGMP) packets using the CGMP automatic detection feature. CGMP automatic detection operates as follows:

When CGMP traffic is detected on a VLAN, IGMP report suppression is disabled on that VLAN for a period of five minutes. Any new CGMP traffic on the VLAN will begin a new five-minute period. When no new CGMP traffic has been detected on the VLAN for five minutes, the IGMP report suppression will revert to the configured status.
The CGMP automatic detection feature has no access to VTP information and causes the switch to send CGMP traffic to VLANs that VTP has pruned from trunks. To avoid this situation, you can disable the CGMP automatic detection feature by entering the no ip igmp snooping cgmp auto-detect global configuration command. Disabling CGMP automatic detection restricts CGMP traffic to Layer 2. When CGMP automatic detection is disabled, IGMP report suppression must be disabled manually for any VLAN that will use CGMP. To disable CGMP automatic detection, perform this task: Command
Router(config)# no ip igmp snooping cgmp auto-detect Router(config)# interface vlan vlan_ID Router(config-if)# no ip igmp snooping report-suppression Router(config-if)# ip cgmp
Purpose Disables the CGMP auto-detect mode globally. Selects a VLAN interface. Disables IGMP snooping report suppression so that CGMP receives all the report messages on this VLAN. Enables CGMP mode on this VLAN.
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
36-13
-----------------------------------------------------------------------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
Displaying IGMP Snooping Information

These sections describe displaying IGMP snooping information:

Displaying Multicast Router Interfaces, page 36-14 Displaying MAC Address Multicast Entries, page 36-14 Displaying IGMP Snooping Information for a VLAN Interface, page 36-15 Displaying IGMP Snooping Statistics, page 36-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#
36-14
OL-13013-06
Chapter 36
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
Displaying IGMP Snooping Information for a VLAN Interface

Note
When you apply the ip igmp snooping command and associated commands on any VLAN interface, the commands continue to function even if the VLAN interface is in shutdown state. 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
36-15
Chapter 36 Understanding MVR
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.
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 -
Understanding MVR
Release 12.2(33)SXH and later releases support Multicast VLAN Registration (MVR). MVR is designed for applications that use wide-scale deployment of multicast traffic across an Ethernet ring-based service-provider network (for example, the broadcast of multiple television channels over a service-provider network). MVR allows a subscriber on a port to subscribe and unsubscribe to a multicast stream on the network-wide multicast VLAN. It allows the single multicast VLAN to be shared in the network while subscribers remain in separate VLANs. MVR provides the ability to continuously send multicast streams in the multicast VLAN, but to isolate the streams from the subscriber VLANs for bandwidth and security reasons. MVR assumes that subscriber ports subscribe and unsubscribe (join and leave) these multicast streams by sending out IGMP join and leave messages. These messages can originate from an IGMP Version-2-compatible host with an Ethernet connection. Although MVR operates on the underlying mechanism of IGMP snooping, the two features operate independently of each other. One feature can be enabled or disabled without affecting the operation of the other feature. However, if IGMP snooping and MVR are both enabled, MVR reacts only to join and leave messages from multicast groups configured under MVR. Join and leave messages from all other multicast groups are managed by IGMP snooping. MVR does the following:

Identifies the MVR IP multicast streams and their associated IP multicast group in the Layer 2 forwarding table. Intercepts the IGMP messages. Modifies the Layer 2 forwarding table to include or remove the subscriber as a receiver of the multicast stream, even though the receivers might be in a different VLAN from the source.
This forwarding behavior selectively allows traffic to cross between different VLANs.
36-16
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Understanding MVR
The switch will forward multicast data for MVR IP multicast streams only to MVR ports on which hosts have joined, either by IGMP reports or by MVR static configuration. The switch will forward IGMP reports received from MVR hosts only to the source (uplink) port. This eliminates using unnecessary bandwidth on MVR data port links. Only Layer 2 ports participate in MVR. You must configure ports as MVR receiver ports. Only one MVR multicast VLAN per switch.
Using MVR in a Multicast Television Application

In a multicast television application, a PC or a television with a set-top box can receive the multicast stream. Multiple set-top boxes or PCs can be connected to one subscriber port, which is a switch port configured as an MVR receiver port. Figure 36-3 is an example configuration. DHCP assigns an IP address to the set-top box or the PC. When a subscriber selects a channel, the set-top box or PC sends an IGMP report to Switch A to join the appropriate multicast. If the IGMP report matches one of the configured IP multicast group addresses, the SP CPU modifies the hardware address table to include this receiver port and VLAN as a forwarding destination of the specified multicast stream when it is received from the multicast VLAN. Uplink ports that send and receive multicast data to and from the multicast VLAN are called MVR source ports.
36-17
Chapter 36 Understanding MVR
Figure 36-3
Multicast VLAN Registration Example
Multicast VLAN
Cisco router
Switch B SP
SP SP
Multicast server
SP SP SP1 Multicast data Switch A RP1 RP2 RP3 RP4 RP5 RP6 RP7 Customer premises IGMP join Set-top box TV data PC Set-top box Hub SP2
SP
Multicast data
TV RP = Receiver Port SP = Source Port
TV Note: All source ports belong to the multicast VLAN.
When a subscriber changes channels or turns off the television, the set-top box sends an IGMP leave message for the multicast stream. The SP CPU sends a MAC-based general query through the receiver port VLAN. If there is another set-top box in the VLAN still subscribing to this group, that set-top box must respond within the maximum response time specified in the query. If the CPU does not receive a response, it eliminates the receiver port as a forwarding destination for this group. Unless the Immediate Leave feature is enabled, when the switch receives an IGMP leave message from a subscriber on a receiver port, it sends out an IGMP query on that port and waits for IGMP group membership reports. If no reports are received in a configured time period, the receiver port is removed from multicast group membership. With the Immediate Leave feature enabled, an IGMP query is not sent from the receiver port on which the IGMP leave was received. As soon as the leave message is received, the receiver port is removed from multicast group membership, which speeds up leave latency. Enable the Immediate Leave feature only on receiver ports to which a single receiver device is connected. MVR eliminates the need to duplicate television-channel multicast traffic for subscribers in each VLAN. Multicast traffic for all channels is only sent around the VLAN trunk onceonly on the multicast VLAN. The IGMP leave and join messages are in the VLAN to which the subscriber port is assigned.
36-18
101364
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Configuring MVR
These messages dynamically register for streams of multicast traffic in the multicast VLAN on the Layer 3 device, Switch B. The access layer switch, Switch A, modifies the forwarding behavior to allow the traffic to be forwarded from the multicast VLAN to the subscriber port in a different VLAN, selectively allowing traffic to cross between two VLANs. IGMP reports are sent to the same IP multicast group address as the multicast data. The Switch A CPU must capture all IGMP join and leave messages from receiver ports and forward them to the multicast VLAN of the source (uplink) port.
Configuring MVR
These sections contain this configuration information:

Default MVR Configuration, page 36-19 MVR Configuration Guidelines and Limitations, page 36-20 Configuring MVR Global Parameters, page 36-20 Configuring MVR Interfaces, page 36-21 Displaying MVR Information, page 36-23 Clearing MVR Counters, page 36-24
Default MVR Configuration

Table 36-4 shows the default MVR configuration.
Table 36-4 Default MVR Configuration
Feature MVR Multicast addresses Query response time Multicast VLAN Interface (per port) default Immediate Leave
Default Setting Disabled globally and per interface None configured 1 second VLAN 1 Neither a receiver nor a source port Disabled on all ports
36-19
Chapter 36 Configuring MVR
MVR Configuration Guidelines and Limitations

When configuring MVR, follow these guidelines:

Only one MVR VLAN can be present in a switch, and you should configure the same VLAN as the MVR VLAN for all the switches in the same network. Source ports must be in the MVR VLAN. Receiver ports on a switch can be in different VLANs, but must not be in the MVR VLAN. Receiver ports can only be access ports; they cannot be trunk ports. When using private VLANs, you cannot configure a secondary VLAN as the MVR VLAN. Do not connect a multicast router to a receiver port. The MVR VLAN must not be a reverse path forwarding (RPF) interface for any multicast route. MVR data received on an MVR receiver port is not forwarded to MVR source ports. The maximum number of multicast entries (MVR group addresses) that can be configured on a switch (that is, the maximum number of television channels that can be received) is 8000. MVR is available only on native systems. VTP pruning should be disabled if the MVR VLAN number is between 1 and 1000. MVR can coexist with IGMP snooping on a switch. MVR supports IGMPv3 messages.
Configuring MVR Global Parameters

You do not need to set the optional MVR parameters if you choose to use the default settings. Before changing the default parameters (except for the MVR VLAN), you must first enable MVR.
Note
For complete syntax and usage information for the commands used in this section, see the Cisco IOS Master Command List, Release 12.2SX. To configure the MVR global parameters, perform this task:
Command
Router# configure terminal Router(config)# mvr Router(config)# mvr max-groups max-groups
Purpose Enters global configuration mode. Enables MVR on the switch. Specifies the maximum number of MVR groups. The range is 1 to 8000. The default is 1000. Configures an IP multicast address on the switch or uses the count parameter to configure a contiguous series of MVR group addresses (the range for count is 1 to 256; the default is 1). Any multicast data sent to this address is sent to all source ports on the switch and all receiver ports that have elected to receive data on that multicast address. Each multicast address would correspond to one television channel.
Router(config)# mvr group ip-address [count]
36-20
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Configuring MVR
Command
Step 5
Router(config)# mvr querytime value
Purpose (Optional) Defines the maximum time to wait for IGMP report memberships on a receiver port before removing the port from multicast group membership. The value is in units of tenths of a second. The range is 1 to 100, and the default is 10 tenths or one second. (Optional) Specifies the VLAN in which multicast data is received; all source ports must belong to this VLAN. The VLAN range is 1 to 1001 and 1006 to 4094. The default is VLAN 1. Returns to privileged EXEC mode. Verifies the configuration.
Step 6
Router(config)# mvr vlan vlan-id
Step 7 Step 8
Router(config)# end Router# show mvr
To return the switch to its default settings, use the no mvr [group ip-address | querytime | vlan] global configuration command. This example shows how to enable MVR, configure the group address, set the query time to 1 second (10 tenths), and specify the MVR multicast VLAN as VLAN 22:
Router(config)# Router(config)# Router(config)# Router(config)# Router(config)# mvr mvr group 228.1.23.4 mvr querytime 10 mvr vlan 22 end
You can use the show mvr groups privileged EXEC command to verify the MVR multicast group addresses on the switch.
Configuring MVR Interfaces

To configure Layer 2 MVR interfaces, perform this task: Command
Router# configure terminal Router(config)# mvr Router(config)# interface interface-id
Purpose Enters global configuration mode. Enables MVR on the switch. Specifies the Layer 2 port to configure, and enters interface configuration mode.
36-21
Chapter 36 Configuring MVR
Command
Step 4
Router(config-if)# mvr type {source | receiver}
Purpose Configures an MVR port as one of these types of ports:
sourceConfigures uplink ports that receive and send multicast data as source ports. Subscribers cannot be directly connected to source ports. All source ports on a switch belong to the single multicast VLAN. receiverConfigures a port as a receiver port if it is a subscriber port and should only receive multicast data. It does not receive data unless it becomes a member of the multicast group, either statically or by using IGMP leave and join messages. Receiver ports cannot belong to the multicast VLAN.
If you attempt to configure a non-MVR port with MVR characteristics, the operation fails. The default configuration is as a non-MVR port.
Step 5
Router(config-if)# mvr immediate
(Optional) Enables the Immediate Leave feature of MVR on the port. The Immediate Leave feature is disabled by default.
Note
This command applies to only receiver ports and should only be enabled on receiver ports to which a single receiver device is connected.
Step 6 Step 7
Router(config-if)# end Router# show mvr
Returns to privileged EXEC mode. Verifies the configuration.
To return the interface to its default settings, use the no mvr [type | immediate] interface configuration commands. This example shows how to configure a source port and a receiver port and to configure Immediate Leave on the receiver port:
Router(config)# mvr Router(config)# interface gigabitethernet Router(config-if)# switchport Router(config-if)# switchport access vlan Router(config-if)# mvr type source Router(config-if)# exit Router(config)# interface gigabitethernet Router(config-if)# switchport Router(config-if)# switchport access vlan Router(config-if)# mvr type receiver Router(config-if)# mvr immediate Router(config-if)# exit Router(config)# 3/48 22
3/47 30
36-22
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Displaying MVR Information
Displaying MVR Information

You can display MVR information for the switch or for a specified interface. To display MVR configurations, perform one or more of these tasks: Command
Router# show mvr
Purpose Displays MVR status and these values for the switch: whether MVR is enabled or disabled, the multicast VLAN, the configured maximum and current number of multicast groups, and the query response time. Displays the MVR group configuration. Displays all MVR interfaces and their MVR configurations. When a specific interface is entered, displays this information:

Router# show mvr groups Router# show mvr interface [type module/port]
TypeReceiver or Source StatusOne of these:

ActiveAt least one IGMP join has been received
for an MVR group on the port.

InactiveThe port is not participating in any MVR
groups.
Up/DownThe port is forwarding (Up) or
nonforwarding (Down).
Router# show mvr members [[vlan vlan-id] | [type module/port]] Router# show mvr members [[vlan vlan-id] | [type module/port]] count Router# show mvr {receiver-ports | source-ports} [type module/port]
Immediate LeaveEnabled or Disabled
Displays details of all MVR members or MVR members on a specified VLAN or port. Displays number of MVR members in all active MVR groups. or on a specified VLAN or port. Displays all receiver or source ports that are members of any IP multicast group or those on the specified interface port.
This example displays MVR status and values for the switch:
Router# show mvr MVR Running: TRUE MVR multicast vlan: 22 MVR Max Multicast Groups: 1000 MVR Current multicast groups: 256 MVR Global query response time: 10 (tenths of sec)
This example displays the MVR group configuration:

Router# show mvr groups MVR max Multicast Groups allowed: 8000 MVR current multicast groups: 8000 MVR groups: Group start Group end --------------- --------------225.0.7.226 225.0.7.226 225.0.7.227 225.0.7.227 225.0.7.228 225.0.7.228
Type ----count count count
Count/Mask --------------1 1 1
36-23
Chapter 36 Displaying MVR Information
225.0.7.229 225.0.7.230 225.0.7.231 236.8.7.0 237.8.7.0 237.8.8.0
225.0.7.229 225.0.7.230 225.0.7.231 236.8.7.255 237.8.7.255 237.8.8.255
count count count mask mask mask
1 1 1 255.255.255.0 255.255.255.0 255.255.255.0
This example displays all MVR interfaces and their MVR configurations:
Router# show mvr interface Port VLAN Type Status ------- --------Gi1/20 2 RECEIVER ACTIVE/UP Gi1/21 2 SOURCE ACTIVE/UP Immediate Leave --------------DISABLED DISABLED
This example displays all MVR members on VLAN 2:

Router# show mvr MVR Group IP -----------224.000.001.001 224.000.001.002 members vlan 2 Status Members -----------ACTIVE Gi1/20(u),Gi1/21(u) ACTIVE Fa3/2(d),Gi1/12(u)
This example displays the number of MVR members on all MVR VLANs:
Router# show mvr members count Count of Vlan Vlan Vlan Vlan active MVR groups: 490: 400 600: 400 700: 0 950: 0
This example displays all receiver ports that are members of any IP multicast group:
Router# show mvr receiver-ports Joins: v1,v2,v3 counter shows total IGMP joins v3 counter shows IGMP joins received with both MVR and non-MVR groups Port VLAN Status Immediate Joins Leave (v1,v2,v3) (v3) ------- ------------- ------------------- ----------Gi1/7 202 INACTIVE/UP ENABLED 305336 0 Gi1/8 202 ACTIVE/UP DISABLED 4005 0 Gi1/9 203 INACTIVE/DOWN DISABLED 53007 0 Gi1/10 203 ACTIVE/UP DISABLED 6204 0 Gi1/11 204 ACTIVE/UP DISABLED 0 940 Gi1/12 205 INACTIVE/UP ENABLED 8623 0
Clearing MVR Counters

You can clear MVR join counters for the switch, for source or receiver ports, or for a specified interface. To clear MVR counters, perform this task: Command
Router# clear mvr counters [[receiver-ports | source-ports] [type module/port]]
Purpose Clears the join counters of all the MVR ports, or source or receiver ports, or of a specified MVR interface port.
36-24
OL-13013-06
Chapter 36
Configuring IGMP Snooping and MVR for IPv4 Multicast Traffic Displaying MVR Information
This example clears the join counters for the receiver port on GigabitEthernet port 1/7:
Router# clear mvr receiver-ports GigabitEthernet 1/7 Router# show mvr receiver-ports GigabitEthernet 1/7 Joins: v1,v2,v3 counter shows total IGMP joins v3 counter shows IGMP joins received with both MVR and non-MVR groups Port VLAN Status Immediate Joins Leave (v1,v2,v3) (v3) ------- ------------- ------------------- ----------Gi1/7 202 INACTIVE/UP ENABLED 0 0
Tip
36-25
Chapter 36 Displaying MVR Information
36-26
OL-13013-06
C H A P T E R
37
Configuring IPv4 IGMP Filtering and Router Guard

This chapter describes how IGMP traffic filtering and Router Guard are used to control the access of a port to IGMP traffic. Release 12.2(33)SXH and later releases support IGMP traffic filtering and Router Guard.
Note
Tip
The following sections describe IGMP filtering and Router Guard features for multicast hosts (receivers):

Understanding IGMP Filtering, page 37-1 Understanding Router Guard, page 37-7
Understanding IGMP Filtering

These sections describe IGMP filtering:

IGMP Filtering Overview, page 37-2 IGMP Filters, page 37-2 IGMP Filter Precedence, page 37-4 Displaying IGMP Filtering, page 37-5 Clearing IGMP Filtering Statistics, page 37-7
37-1
Chapter 37 Understanding IGMP Filtering
IGMP Filtering Overview

IGMP snooping is a protocol that learns and maintains multicast group membership at the Layer 2 level. IGMP snooping looks at IGMP traffic to decide which ports should be allowed to receive multicast traffic from certain sources and for certain groups. This information is used to forward multicast traffic to only interested ports. The main benefit of IGMP snooping is to reduce flooding of packets. For information about IGMP snooping, see Understanding IGMP Filtering section on page 37-1. IGMP filtering allows users to configure filters on a switch virtual interface (SVI), a per-port, or a per-port per-VLAN basis to control the propagation of IGMP traffic through the network. By managing the IGMP traffic, IGMP filtering provides the capability to manage IGMP snooping, which in turn controls the forwarding of multicast traffic. When an IGMP packet is received, IGMP filtering uses the filters configured by the user to determine whether the IGMP packet should be discarded or allowed to be processed by the existing IGMP snooping code. With a IGMP version 1 or version 2 packet, the entire packet is discarded. With a IGMPv3 packet, the packet is rewritten to remove message elements that were denied by the filters. The IGMP filtering feature is SSO compliant. IGMP traffic filters control the access of a port to multicast traffic. Access can be restricted based on the following:

Which multicast groups or channels can be joined on a port. Channels are joined by IGMPv3 hosts that specify both the group and the source of the multicast traffic. Maximum number of groups or channels allowed on a specific port or interface (regardless of the number of hosts requesting service). IGMP protocol versions (for example, disallow all IGMPv1 messages).
When you enter an IGMP filtering command, a user policy is applied to a Layer 3 SVI interface, a Layer 2 port, or a particular VLAN on a Layer 2 trunk port. The Layer 2 port may be an access port or a trunk port. The IGMP filtering features will work only if IGMP snooping is enabled (either on the interface or globally). IGMP filtering is typically used in access switches connected to end-user devices in Ethernet-to-home deployment scenarios.
Note
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 35, Understanding IPv4 Multicast Layer 3 Switching.
IGMP Filters
There are three different types of IGMP filters: IGMP group and channel access control, several IGMP groups and channels limit, and an IGMP minimum version. These filters are configurable and operate differently on different types of ports:

Per SVI Per port Per VLAN basis on a trunk port
In the case of trunk ports, filters may also be configured separately for each of the different VLANs passing through that trunk port.
37-2
OL-13013-06
Chapter 37
Configuring IPv4 IGMP Filtering and Router Guard Understanding IGMP Filtering
The following sections describe each type of filter in more detail:

IGMP Group and Channel Access Control, page 37-3 Number of IGMP Groups and Channels Limit, page 37-3 IGMP Minimum Version, page 37-4
IGMP Group and Channel Access Control

Filtering on the IGMP group or channel allows the user to control which IGMP groups or channels can be joined on a port or on a per VLAN basis on a trunk port. To configure filtering on the IGMP group or channel use the following CLI command: ip igmp snooping access-group acl [vlan vlan_id] To allow or deny several groups or channels, you must configure multiple access control entries in the access control list. Depending on whether the ACL is configured as permit or deny, the corresponding group or channel is allowed or denied. The ACL specified may be either a simple or extended ACL. Filtering by IGMP group or channel is configurable on a Layer 3 SVI as a default filter for all ports in access mode under that SVI and for the corresponding VLAN on all trunk ports carrying that VLAN. This filter is also configurable on a Layer 2 port. If the port is in access mode, this filter will override any default SVI filter. If the port is in trunk mode, this filter will act as a default for all VLANs on that trunk and will override the SVI filter for each corresponding VLAN. The vlan keyword can apply the filter only to IGMP packets arriving on the specified Layer 2 VLAN if the port is a trunk port. This per-VLAN filter (configured using the vlan keyword) will override any interface level filter and any SVI filter for the same VLAN.
Number of IGMP Groups and Channels Limit

Limiting the number of IGMP groups or channels allows you to control how many IGMP groups or channels can be joined on a port or on a per-VLAN basis on a trunk port. To limit the number of IGMP groups or channels, use the following interface command CLI: ip igmp snooping limit n [except acl] [vlan vlan_id] A maximum of n groups or channels are allowed on the port or interface. The except keyword allows you to specify groups or channels that are exempt from the configured limit. The ACL used with the except keyword may be either a simple or extended ACL. If joins are received for (*,G1) and (S1,G1) on the same interface, these are counted as two separate joins. If the limit on an interface has been set to 2, and joins are received for (*,G1) and (S1,G1), all other joins (for groups or channels different from these two) will then be discarded. This filter is configurable on a Layer 3 SVI as a default filter for all ports in access mode under that SVI and for the corresponding VLAN on all trunk ports carrying that VLAN. This filter is also configurable on a Layer 2 port. If the Layer 2 port is in access mode, this filter will override any default SVI filter. If the Layer 2 switch port is in trunk mode, this filter will act as a default for all VLANs on that trunk and will override the SVI filter for each corresponding VLAN. The vlan keyword allows the user to apply the filter only to IGMP packets arriving on the specified Layer 2 VLAN if the Layer 2 switch port is a trunk port. This per-VLAN filter, configured using the vlan keyword, will override any interface level filter and any SVI filter for the same VLAN.
37-3
IGMP Minimum Version

Filtering on the IGMP protocol allows you to configure the minimum version of IGMP hosts allowed on the SVI. For example, you may want to disallow all IGMPv1 hosts (such as, allow a minimum IGMP version of 2) or all IGMPv1 and IGMPv2 hosts (such as, allow a minimum IGMP version of 3). This filtering applies only to membership reports. To configure filtering on the IGMP protocol, use the following CLI command: ip igmp snooping minimum-version 2 | 3 This filter is only configurable on a Layer 3 SVI as a default filter for all ports in access mode under that SVI and for the corresponding VLAN on all trunk ports.
IGMP Filter Precedence

These sections describe the hierarchy of the different filters on various ports.
Access Mode
In access mode, filters can be configured on both the port and the SVI. When an IGMP packet is received on a port in access mode, the port filter is checked first. If the port filter exists, it is applied and the SVI filter is ignored. If no per-port filter exists, the SVI filter is used. This hierarchy is applied separately for each type of filter. For example, a limit filter configured on the port overrides the default limit filter on the SVI, but has no affect on any of the other filters.
Trunk Mode
With ports in trunk mode, a filter can be configured for an SVI corresponding to one of the VLANs on the trunk port, another filter configured on the trunk port itself, and a third filter configured on one of the Layer 2 VLANs passing through the trunk. When an IGMP packet is received, the trunk-per-VLAN specific filter will be checked first. If this filter exists, it is applied. The main trunk port filter and SVI filter will be ignored. If no trunk-per-VLAN filter exists, the main trunk port filter will be used. If neither of these filters exist, the SVI filter for the VLAN will be used as a final default for ports in trunk mode.
Filter Hierarchy Example

This example shows the filter hierarchy. The following configuration of SVI VLAN 100 contains three access ports g1/1, g1/2, and g1/3: VLAN 100:
Switch(config-if)# ip igmp snooping limit 20
Port g1/1:
Switch(config-if)# ip igmp snooping limit 35
Port g1/2:
Switch(config-if)# no limit filter
Port g1/3:
37-4
OL-13013-06
Chapter 37
Configuring IPv4 IGMP Filtering and Router Guard Understanding IGMP Filtering
Switch(config-if)# no limit filter
In this example, the limit value for g1/1 is 35, the limit value for g1/2 is 20, and the limit value for g1/3 is also 20.
Displaying IGMP Filtering

The following sections describe how to display IGMP filtering:

Displaying IGMP Filtering Configuration, page 37-5 Displaying IGMP Filtering Statistics, page 37-6
Displaying IGMP Filtering Configuration

To display IGMP filtering rules, perform this task: Command
Switch(config-if)# show ip igmp snooping filter interface interface-name [details]
Purpose Displays the filters configured for the specified interface.
This example shows how to display the default filters configured on the SVI:
Router# show ip igmp snooping filter interface vlan 20 Access-Group: Channel1-Acl Groups/Channels Limit:100 (Exception List: Channel6-Acl) IGMP Minimum-Version:Not Configured
This example shows how to display the filters configured for all ports in access mode under this SVI and for all trunk ports carrying the corresponding VLAN:
Router# show ip igmp snooping filter interface g3/48 Access-Group: Channel4-Acl Groups/Channels Limit:10 (Exception List: Channel3-Acl)
This example shows how to display the filters configured for all ports in access mode under this SVI:
Router# show ip igmp snooping filter interface vlan 20 detail GigabitEthernet3/47 : Access-Group: Not Configured Groups/Channels Limit: Not Configured GigabitEthernet3/48 : Access-Group: Channel4-ACL Groups/Channels Limit: 10 (Exception-list: Channel3-Acl)
This example shows how to display the default trunk port filters:
Router# show ip igmp snooping filter interface g3/46 Access-Group: Channel1-Acl Groups/Channels Limit: 10 (Exception List: Channel3-Acl)
This example shows how to display the per-VLAN filters for all VLANs on this trunk:
Router# show ip igmp snooping filter interface g3/46 detail Vlan 10 :
37-5
Access-Group: Not Configured Groups/Channels Limit: Not Configured Vlan 20 : Access-Group: Not Configured Groups/Channels Limit: 8 (Exception List: Channel4-Acl)
This example shows how to display the per-VLAN filters for a specific VLAN on this trunk:
Router# show ip igmp snooping filter interface g3/46 vlan 20 Access-Group: Not Configured Groups/Channels Limit: 8 (Exception List: Channel4-Acl)
Note
If the port is in the shutdown state, filter status will not be displayed because it cannot be determined whether the port is in trunk mode or access mode. In this situation, you can use the show running-config interface xxxx command to view the configuration.
Displaying IGMP Filtering Statistics

Statistics are maintained on an interface basis for ports in access mode and on a per-VLAN basis for ports in trunk mode. To display IGMP filtering statistics, perform this task: Command
Switch(config-if)# show ip igmp snooping filter interface interface-name [statistics]
Purpose Displays the filtering statistic collected for the specified interface.
This example shows how to display statistics for each port in access mode under the SVI:
Router# show ip igmp snooping filter interface vlan 20 statistics GigabitEthernet3/47 : IGMP Filters are not configured GigabitEthernet3/48 : Access-group denied : 0 Limit denied : 2 Limit status : 0 active out of 2 max Minimum-version denied : 0
This example shows how to display statistics for a specific port in access mode:
Router# show ip igmp snooping filter interface g3/48 statistics Access-group denied : 0 Limit denied : 2 Limit status : 0 active out of 2 max Minimum-version denied : 0
This example shows how to display statistics for Gigabit Ethernet port 3/47 in access mode with no default SVI filter and no port filter:
Router# show ip igmp snooping filter interface g3/47 statistics IGMP Filters are not configured
This example shows how to display statistics for all VLANs under a trunk:
Router# show ip igmp snooping filter interface g3/46 statistics
37-6
OL-13013-06
Chapter 37
Configuring IPv4 IGMP Filtering and Router Guard Understanding Router Guard
Vlan 10 : IGMP Filters are not configured Vlan 20 : Access-group denied : 0 Limit denied : 0 Minimum-version denied : 0
This example shows how to display statistics for a specific VLAN under a trunk:
Router# show ip igmp snooping filter interface g3/46 vlan 20 statistics Access-group denied : 0 Limit denied : 0 Minimum-version denied : 0
This example shows how to display statistics for a specific VLAN under a trunk port with no trunk and no VLAN filter:
Router# show ip igmp snooping filter interface g3/46 vlan 10 statistics IGMP Filters are not configured
Note
If the port is in the shutdown state, filter statistics will not be displayed because it cannot be determined whether the port is in trunk mode or access mode.
Clearing IGMP Filtering Statistics

To clear IGMP filtering statistics, perform one of these tasks: Command
Router# clear ip igmp snooping filter statistics
Purpose Clears IGMP filtering statistics for all access ports and for all VLANs on all trunk ports. Clears statistics for one particular access port or for all VLANs on one particular trunk port. Clears statistics for one particular VLAN on a trunk port.
Router# clear ip igmp snooping filter statistics interface interface_name Router# clear ip igmp snooping filter statistics interface interface_name vlan vlan_ID
Understanding Router Guard

These sections describe Router Guard:

Router Guard Overview, page 37-8 Configuring Router Guard, page 37-8 Displaying Router Guard Configurations, page 37-9 Displaying Router Guard Interfaces, page 37-10
37-7
Chapter 37 Understanding Router Guard
Router Guard Overview

The Router Guard feature allows you to designate a specified port only as a multicast host port and not as a multicast router port. Multicast router control packets received on this port are dropped. Any port can become a multicast router port if the switch receives one of the multicast router control packets, such as IGMP general query, PIM hello, or CGMP hello. When a port becomes a multicast router port, all multicast traffic (both known and unknown source traffic) is sent to all multicast router ports. This cannot be prevented without Router Guard. When configured, the Router Guard feature makes the specified port a host port only. The port is prevented from becoming a router port, even if a multicast router control packets are received. In addition, any control packets normally received from multicast routers, such as IGMP queries and PIM joins, will also be discarded by this filter. A Router Guard command applies a user policy to a Layer 3 SVI interface, a Layer 2 port, or a particular VLAN on a Layer 2 trunk port. The Layer 2 port may be an access port or a trunk port. The Router Guard feature does not require IGMP snooping to be enabled. Router Guard is implemented only for IPv4. Router Guard is typically used in access switches connected to end-user boxes in Ethernet-to-home deployment scenarios. The IPv4 multicast Router Guard feature is SSO-compliant. The following packet types are discarded if they are received on a port that has Router Guard enabled:

IGMP query messages IPv4 PIMv2 messages IGMP PIM messages (PIMv1) IGMP DVMRP messages RGMP messages CGMP messages
When these packets are discarded, statistics are updated indicating that packets are being dropped due to Router Guard.
Configuring Router Guard

The Router Guard feature can be configured globally and per-interface. Typically, the global configuration initiates Router Guard for all Layer 2 ports in the system. The per-interface configuration can then be used to override Router Guard for specific ports, for example, the ports where multicast routers are actually connected. The following sections describe each type of configuration:

Enabling Router Guard Globally, page 37-9 Clearing Router Guard Statistics, page 37-9 Disabling Router Guard on Ports, page 37-9
37-8
OL-13013-06
Chapter 37
Enabling Router Guard Globally

To enable Router Guard globally, perform this task: Command
Router# router-guard ip multicast switchports
Purpose Enables Router Guard globally.
Clearing Router Guard Statistics

To clear Router Guard statistics, perform this task: Command
Step 1 Step 2
Router# clear ip igmp snooping filter statistics interface interface_name Router# clear ip igmp snooping filter statistics interface interface_name vlan vlan_id
Purpose Clears statistics for one particular access port or for all VLANs on one particular trunk port. Clears statistics for one particular VLAN on a trunk port.
Disabling Router Guard on Ports

To disable Router Guard on a Layer 2 port to which a multicast router is connected, perform this task: Command
Router(config-if)# no router-guard ip multicast [vlan vlan_id]
Purpose Disables Router Guard on a Layer 2 port.

Note
The vlan keyword is effective only if the port is in trunk mode. You can use this keyword to override Router Guard only for specific VLANs on the trunk port.
This example shows how to allow multicast router messages on trunk port Gigabit Ethernet 3/46, VLAN 20:
Router# configure terminal Router(config)# interface gigabitethernet 3/46 Router(config-if)# no router-guard ip multicast vlan 20
Displaying Router Guard Configurations

To display the global Router Guard configuration and the Router Guard configuration for a specific interface, perform these tasks: Command
Router# show router-guard Router# show router-guard interface interface_name
Purpose Displays the global Router Guard configuration. Displays the Router Guard configuration for a specific interface.
37-9
This example shows how to display the interface command output for a port in access mode with Router Guard not active:
Router# show router-guard interface g3/48 Router Guard for IP Multicast: Globally enabled for all switch ports Enabled on this interface Packets denied: IGMP Queries: PIMv2 Messages: PIMv1 Messages: DVMRP Messages: RGMP Messages: CGMP Messages:
This example shows how to display the interface command output for a port in trunk mode:
Router# show router-guard interface g3/48 Router Guard for IP Multicast: Globally enabled for all switch ports Disabled on this interface
This example shows how to verify that a trunk port is carrying VLANs 10 and 20:
Router# show router-guard interface g3/46 Router Guard for IP Multicast: Globally enabled for all switch ports Default: Enabled for all VLANs on this interface VLAN 10: Enabled on this VLAN Packets denied: IGMP Queries: PIMv2 Messages: PIMv1 Messages: DVMRP Messages: RGMP Messages: CGMP Messages: VLAN 20 : Disabled on this VLAN
Note
If the port is in the shutdown state, the status will not be displayed because it cannot be determined whether the port is in trunk mode or access mode. You can use the show running-config interface xxxx command to display the Router Guard configuration.
Displaying Router Guard Interfaces

To display a list of all interfaces for which Router Guard is disabled, perform this task: Command
Router# show router-guard interface Router Guard for IP Multicast: Globally enabled for all switchports Interfaces: Gi3/46: Disabled on this port for VLANS: ALL
Purpose Displays a list of all interfaces for which Router Guard is disabled.
37-10
OL-13013-06
Chapter 37
Clearing Router Guard Statistics

To clear Router Guard statistics, perform one of these tasks: Command
Router(config)# clear router-guard ip multicast statistics Router(config)# clear router-guard ip multicast statistics interface interface_name Router(config)# clear router-guard ip multicast statistics interface interface_name vlan v
Purpose Clears statistics for all access ports and for all VLANs on all trunk ports. Clears statistics for an access port and for all VLANs on a trunk port. Clears statistics for one particular VLAN on a trunk port.
This example shows how to clear statistics for one particular VLAN on a trunk port:
Router# clear router-guard ip multicast statistics interface interface_name vlan v
Tip
37-11
37-12
OL-13013-06
C H A P T E R
38

This chapter describes how to configure protocol independent multicast (PIM) snooping in Cisco IOS Release 12.2SX.
Note
Tip

Understanding PIM Snooping, page 38-1 Default PIM Snooping Configuration, page 38-4 PIM Snooping Configuration Guidelines and Restrictions, page 38-4 Configuring PIM Snooping, page 38-5
Understanding PIM Snooping

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.
38-1
Chapter 38 Understanding PIM Snooping
Note
To use PIM snooping, you must enable IGMP snooping on the 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 38-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 38-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 38-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).
38-2
OL-13013-06
Chapter 38
Configuring PIM Snooping Understanding PIM Snooping
Figure 38-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 38-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 38-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 38-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).
38-3
Chapter 38 Default PIM Snooping Configuration
Figure 38-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.
38-4
OL-13013-06
Chapter 38
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 38-5 Enabling PIM Snooping in a VLAN, page 38-5 Disabling PIM Snooping Designated-Router Flooding, page 38-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

Note
When you apply the ip pim snooping command and associated commands on any VLAN interface, the commands continue to function even if the VLAN interface is in shutdown state. To enable PIM snooping in a VLAN, perform this task:
38-5
Chapter 38 Configuring PIM Snooping
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. Exits configuration mode. Verifies the configuration.
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
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
38-6
OL-13013-06
Chapter 38
Configuring PIM Snooping Configuring PIM Snooping
Tip
38-7
Chapter 38 Configuring PIM Snooping
38-8
OL-13013-06
C H A P T E R
39

This chapter describes how to configure IPv4 Multicast Virtual Private Network (MVPN) support in Cisco IOS Release 12.2SX.
Note
PFC3A modes does not support MVPN. For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html
Tip
This chapter contains these sections:

Understanding MVPN, page 39-1 MVPN Configuration Guidelines and Restrictions, page 39-7 Configuring MVPN, page 39-8
Understanding MVPN
These sections describe MVPN:

MVPN Overview, page 39-2 Multicast Routing and Forwarding and Multicast Domains, page 39-2 Multicast Distribution Trees, page 39-2 Multicast Tunnel Interfaces, page 39-5 PE Router Routing Table Support for MVPN, page 39-6 Multicast Distributed Switching Support, page 39-6 Hardware-Assisted IPv4 Multicast, page 39-6
39-1
Chapter 39 Understanding MVPN
MVPN Overview
MVPN is a standards-based feature that transmits IPv4 multicast traffic across an MPLS VPN cloud. MVPN uses the IPv4 multicast traffic PFC hardware support 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.
39-2
OL-13013-06
Chapter 39
Configuring IPv4 Multicast VPN Support Understanding MVPN
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 39-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.
39-3
Figure 39-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 39-2 shows how the PE router forwards the request to the CE router associated with the multicast source (CE1a).
39-4
72756
Customer 2 Houston Site
Customer 1 Dallas Site
CE3
OL-13013-06
Chapter 39
Configuring IPv4 Multicast VPN Support Understanding MVPN
Figure 39-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
39-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

Cisco IOS Release 12.2SX supports hardware acceleration for IPv4 multicast over VPN traffic, which forwards multicast traffic to the appropriate VPNs at wire speed without increased RP CPU utilization. In a customer VRF, PFC hardware acceleration supports multicast traffic in PIM dense, PIM sparse, PIM bidirectional, and PIM Source Specific Multicast (SSM) modes.
39-6
OL-13013-06
Chapter 39
Configuring IPv4 Multicast VPN Support MVPN Configuration Guidelines and Restrictions
In the service provider core, PFC hardware acceleration supports multicast traffic in PIM sparse, PIM bidirectional, and PIM SSM modes. In the service provider core, PFC hardware acceleration does not support multicast traffic in PIM dense mode.
MVPN Configuration Guidelines and Restrictions

When configuring MVPN, follow these guidelines and restrictions:

PFC3A mode 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.
39-7
Chapter 39 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 redundancy modes. 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 39-8 Configuring a Multicast VPN Routing and Forwarding Instance, page 39-9 Configuring Multicast VRF Routing, page 39-15 Configuring Interfaces for Multicast Routing to Support MVPN, page 39-19
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. To avoid disrupting customer traffic, we recommend verifying that the switch is already in ingress multicast replication mode before configuring any MVRFs.
39-8
OL-13013-06
Chapter 39
Configuring IPv4 Multicast VPN Support Configuring MVPN
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). Verifies the configuration.
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 39-10 Configuring the Route Distinguisher, page 39-10 Configuring the Route-Target Extended Community, page 39-10 Configuring the Default MDT, page 39-11 Configuring Data MDTs (Optional), page 39-12 Enabling Data MDT Logging, page 39-12 Sample Configuration, page 39-12 Displaying VRF Information, page 39-13
39-9
Configuring a VRF Entry

To configure a VRF entry, perform this task: Command
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. Verifies the configuration.
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
Step 1 Step 2
Router(config-vrf)# rd route_distinguisher Router(config-vrf)# do show ip vrf vrf_name
Purpose Specifies the route distinguisher for a VPN IPv4 prefix. Verifies the configuration.
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
Configuring the Route-Target Extended Community

To configure the route-target extended community, perform this task: Command
Step 1 Step 2
Router(config-vrf)# route-target [import | export | both] route_target_ext_community Router(config-vrf)# do show ip vrf detail
Purpose Configures a route-target extended community for the VRF. Verifies the configuration.
39-10
OL-13013-06
Chapter 39
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. bothImports 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
Router(config-vrf)# mdt default group_address
Purpose Configures the default MDT.
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
39-11
Configuring Data MDTs (Optional)

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

group_address1Multicast 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_bitsWildcard bit mask 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
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.
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
39-12
OL-13013-06
Chapter 39
! 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
* * * *
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
VRF
MDT INFO
MDT Type
State
39-13
BIDIR01HWRP BIDIR01SWRP SPARSE01HWRP SPARSE01SWRP red red red red red Router#
1 2 3 4 5 5 5 5 5
(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)
default default default default default data (send) data (send) data (send) data (send)
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#
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#
39-14
OL-13013-06
Chapter 39
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 39-15 Enabling IPv4 Multicast VRF Routing, page 39-15 Configuring a PIM VRF Register Message Source Address, page 39-16 Specifying the PIM VRF RP Address, page 39-16 Configuring an MSDP Peer, page 39-17 Enabling IPv4 Multicast Header Storage, page 39-17 Configuring the Maximum Number of Multicast Routes, page 39-17 Sample Configuration, page 39-18 Displaying IPv4 Multicast VRF Routing Information, page 39-19
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.
Enabling IPv4 Multicast Routing Globally

To enable IPv4 multicast routing globally, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# ip multicast-routing
Purpose Enters global configuration mode. Enables 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
Router(config)# ip multicast-routing vrf vrf_name [distributed]
Purpose Enables IPv4 multicast VRF routing.
39-15
When enabling IPv4 multicast VRF routing, note the following information:
vrf_nameSpecifies a particular VRF for multicast routing. The vrf_name should see a VRF that has been previously created, as specified in the Configuring a Multicast VPN Routing and Forwarding Instance section on page 39-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
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.
This example show how to configure a PIM VRF register message source address:
Router(config)# ip pim vrf blue register-source loopback 3
Specifying the PIM VRF RP Address

To specify the PIM VRF rendezvous point (RP) address, perform this task: Command
Router(config)# ip pim vrf vrf_name rp-address rp_address [access_list] [override] [bidir]
Purpose Specifies the PIM RP IPv4 address for a (required for sparse PIM networks):
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
39-16
OL-13013-06
Chapter 39
Configuring an MSDP Peer

To configure a multicast source discovery protocol (MSDP) peer, perform this task: Command
Router(config)# 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.
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.
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
Router(config)# ip multicast vrf vrf_name cache-headers [rtp]
Purpose (Optional) Enables a circular buffer to store IPv4 multicast packet headers.
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
Router(config)# 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.
39-17
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
Configuring IPv4 Multicast Route Filtering

To configure IPV4 multicast route filtering, perform this task: Command
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.
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
39-18
OL-13013-06
Chapter 39
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 39-19 Configuring PIM on an Interface, page 39-20 Configuring an Interface for IPv4 VRF Forwarding, page 39-20 Sample Configuration, page 39-21
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.
39-19
Configuring PIM on an Interface

To configure PIM on an interface, perform this task: Command
Router# configure terminal Router(config)# interface type {slot/port | number} Router(config-if)# ip pim {dense-mode | sparse-mode | sparse-dense-mode}
Purpose Enters global configuration mode. Enters interface configuration mode for the specified interface. Enables PIM on the interface.
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 Router(config)# 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
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.
39-20
OL-13013-06
Chapter 39
Configuring IPv4 Multicast VPN Support Sample Configurations for MVPN
This example shows how to configure the interface for VRF blue forwarding:
Router(config-if)# ip vrf forwarding blue
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 39-21 MVPN Configuration with Default and Data MDTs, page 39-23
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 !
39-21
Chapter 39 Sample Configurations for MVPN
! no ip domain-lookup ip host tftp 223.255.254.238 ! 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 !
39-22
OL-13013-06
Chapter 39
interface Loopback11 ip vrf forwarding mvpn-cus1 ip address 210.111.255.14 255.255.255.255 ip pim sparse-dense-mode ! 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
39-23
mdt default 226.3.3.1 mdt data 226.3.3.128 0.0.0.7 ! ip vrf v4 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
39-24
OL-13013-06
Chapter 39
ip address 1.1.1.1 255.255.255.252 ip pim sparse-dense-mode ip ospf network point-to-point ! 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
39-25
network 155.255.255.33 0.0.0.0 area 155 ! router ospf 1 log-adjacency-changes 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
39-26
OL-13013-06
Chapter 39
permit 1.1.1.1 ip access-list standard MCAST.BOUNDARY.VRF.v1 deny 226.192.1.1 permit any 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
39-27
39-28
OL-13013-06
PA R T
Quality of Service
C H A P T E R
40
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) in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html For information about Auto-QoS, see Chapter 41, Using AutoQoS. For information about QoS and MPLS, see Chapter 42, Configuring MPLS QoS. QoS in Cisco IOS Release 12.2SX (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).
Tip

Understanding PFC QoS, page 40-2 PFC QoS Default Configuration, page 40-27 PFC QoS Configuration Guidelines and Restrictions, page 40-50 Configuring PFC QoS, page 40-56 Common QoS Scenarios, page 40-111 PFC QoS Glossary, page 40-120
40-1
Chapter 40 Understanding PFC QoS
Configuring PFC QoS
Understanding PFC QoS

The term PFC QoS refers to QoS in Cisco IOS Release 12.2SX. 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 40-2 Overview, page 40-2 Component Overview, page 40-5 Understanding Classification and Marking, page 40-14 Understanding Port-Based Queue Types, page 40-20
Port Types Supported by PFC QoS

The PFC does not provide QoS for FlexWAN module ports. See 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.
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. 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
Cisco IOS Release 12.2SX does 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, Cisco IOS Release 12.2SX does not support MQC-configured queuing. Figure 40-1 shows an overview of QoS processing in a switch supported by Cisco IOS Release 12.2SX.
40-2
OL-13013-06
Chapter 40
Configuring PFC QoS Understanding PFC QoS
Figure 40-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 one of three types of received QoS values: 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.
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, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-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) 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 (optional) Layer 2 CoS marking mapped from the final internal DSCP
120559
40-3
Configuring PFC QoS
Layer 2 CoS-based and Layer 3 DSCP-based congestion avoidance. (Layer 3 DSCP-based
queue mapping is available only on WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE ports.) These figures provide more detail about the relationship between QoS and the switch components:

Figure 40-2, Traffic Flow and PFC QoS Features with a PFC3 Figure 40-3, PFC QoS Features and Component Overview
Figure 40-2 shows traffic flow and PFC QoS features with a PFC3.
Figure 40-2 Traffic Flow and PFC QoS Features with a PFC3
FlexWAN ingress port and QoS features Multilayer Switch Feature Card (MSFC) FlexWAN egress port and QoS features Transmit FlexWAN traffic
FlexWAN traffic enters switch
CoS = IP precedence for all traffic (not configurable)
Figure 40-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 route
processor (RP).
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. Ingress LAN port traffic can be Layer 2- or Layer 3-switched by the PFC3 or routed in software
by the RP.
Egress PFC QoS and egress LAN port QoS can be applied to LAN port egress traffic.
40-4
OL-13013-06
184403
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
Chapter 40
Figure 40-3
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 40-5 PFC and DFC QoS Features, page 40-7 PFC QoS Egress Port Features, page 40-11
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 40-6 Port Trust, page 40-7 Ingress Congestion Avoidance, page 40-7
40-5
137031
Configuring PFC QoS
Flowchart of Ingress LAN Port PFC QoS Features

Figure 40-4 shows how traffic flows through the ingress LAN port PFC QoS features.
Figure 40-4 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. DSCP-based queue mapping is supported only on WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE ports.
40-6
OL-13013-06
Chapter 40
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. You can configure WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-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 40-15 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 40-8 Supported Distributed Forwarding Cards, page 40-8 PFC and DFC QoS Feature List and Flowchart, page 40-8 Internal DSCP Values, page 40-10 Port-Based PFC QoS and VLAN-Based PFC QoS, page 40-11 Session-Based PFC QoS, page 40-11
40-7
Configuring PFC QoS
Supported Policy Feature Cards

The policy feature card (PFC) is a daughter card on the supervisor engine. The PFC provides QoS in addition to other functionality. The following PFCs are supported in Cisco IOS Release 12.2SX:

PFC3A on the Supervisor Engine 720 PFC3B on the Supervisor Engine 720 and Supervisor Engine 32 PFC3BXL on the Supervisor Engine 720 PFC3C on the Cisco ME 6500 Series Ethernet switches and the Supervisor Engine 720-10GE PFC3CXL on the Supervisor Engine 720-10GE
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. These DFCs are supported on the Catalyst 6500 series switches:
For use on dCEF256 and CEF256 modules with a Supervisor Engine 720:
WS-F6K-DFC3A WS-F6K-DFC3B WS-F6K-DFC3BXL
For use on CEF720 modules with a Supervisor Engine 720:

WS-F6700-DFC3A WS-F6700-DFC3B WS-F6700-DFC3BXL
For use on CEF720 modules with Supervisor Engine 720 and Supervisor Engine 720-10GE:
WS-F6700-DFC3CXL WS-F6700-DFC3C
PFC and DFC QoS Feature List and Flowchart

Table 40-1 lists the QoS features supported on the different versions of PFCs and DFCs.
Table 40-1 QoS Features Supported on PFCs and DFCs
Feature Support for DFCs Flow granularity QoS ACLs DSCP transparency
Note
PFC3A and DFC3A Yes Source Destination IP, MAC Optional
PFC3B and DFC3B Yes Source Destination IP, MAC Optional
PFC3BXL and DFC3BXL Yes Source Destination IP, MAC Optional
PFC3C and DFC3C Yes Source Destination IP, MAC Optional
PFC3CXL and DFC3CXL Yes Source Destination IP, MAC Optional
Enabling DSCP transparency disables egress ToS rewrite. Optional Optional Optional Optional Optional
Egress ToS rewrite
40-8
OL-13013-06
Chapter 40
Table 40-1
QoS Features Supported on PFCs and DFCs (continued)
Feature 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
PFC3A and DFC3A Yes Yes 1023 configurable 64 rates 64,000 Bytes
PFC3B and DFC3B Yes Yes 1023 configurable 64 rates 110,000 Bytes
PFC3BXL and DFC3BXL Yes Yes 1023 configurable 64 rates 240,000 Bytes
PFC3C and DFC3C Yes Yes 1023 configurable 64 rates 110,000 Bytes
PFC3CXL and DFC3CXL Yes Yes 1023 configurable 64 rates 240,000 Bytes
Layer 2 length Layer 2 length Layer 2 length Layer 2 length Layer 2 length
Figure 40-5 shows how traffic flows through the QoS features on the PFC and DFCs.
Figure 40-5 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)
40-9
154644
Configuring PFC QoS
Note
The DSCP transparency feature makes writing the egress DSCP value into the Layer 3 ToS byte optional.
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.
40-10
OL-13013-06
Chapter 40
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.
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.
Session-Based PFC QoS

In Cisco IOS Software Release 12.2(33)SXI and later releases, you can configure the dynamic delivery of a policy map to an interface by the AAA server when a user authenticates on that interface. This feature allows per-user or per-session QoS at the interface level, so that a user who connects by different interfaces at different times will always receive the same QoS treatment. For each user of session-based QoS, you must set these attribute-value (AV) pairs on the AAA server by using RADIUS cisco-av-pair vendor-specific attributes (VSAs):

cisco-avpair = ip:sub-policy-In=in_policy_name cisco-avpair = ip:sub-policy-Out=out_policy_name
The in_policy_name and out_policy_name arguments are the names of the ingress and egress QoS policy maps to be applied to an interface when a user authenticates on that interface. The policy maps will be removed from the interface when the user logs off and the session is terminated. For session-based QoS configuration information, see the Configuring Dynamic Per-Session Attachment of a Policy Map section on page 40-81.
PFC QoS Egress Port Features

These sections describe PFC QoS egress port features:

Flowchart of PFC QoS Egress LAN Port Features, page 40-12 Egress CoS Values, page 40-12 Egress DSCP Mutation, page 40-13 Egress ToS Byte, page 40-13 Egress PFC QoS Interfaces, page 40-13 Egress ACL Support for Remarked DSCP, page 40-13
40-11
Configuring PFC QoS
Flowchart of PFC QoS Egress LAN Port Features

Figure 40-6 shows how traffic flows through the QoS features on egress LAN ports.
Figure 40-6 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
You can configure WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-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 40-99).
40-12
OL-13013-06
144806
Chapter 40
Egress DSCP Mutation

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 on which PFC QoS supports egress QoS.
Note
If you configure egress DSCP mutation, PFC QoS does not derive the egress CoS value from the mutated DSCP value.
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 40-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. 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. The PFC3 supports 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).
40-13
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.
Understanding Classification and Marking

The following sections describe where and how classification and marking occur in Cisco IOS Release 12.2SX:

Classification and Marking at Trusted and Untrusted Ingress Ports, page 40-14 Classification and Marking on the PFC Using Service Policies and Policy Maps, page 40-16 Classification and Marking on the RP, page 40-17
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
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. You can configure WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-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 40-99). Ingress LAN port classification, marking, and congestion avoidance on other ports use Layer 2 CoS values only.
40-14
OL-13013-06
Chapter 40
The following sections describe classification and marking at trusted and untrusted ingress ports:

Classification and Marking at Untrusted Ingress Ports, page 40-15 Ingress Classification and Marking at Trusted Ports, page 40-15
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. These sections describe classification and marking at trusted ingress ports:

Ingress Classification and Marking at Trust CoS LAN Ports, page 40-15 Ingress Classification and Marking at Trust IP Precedence Ports, page 40-15 Ingress Classification and Marking at Trust DSCP Ports, page 40-15
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 40-20 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.
40-15
Configuring PFC QoS
You can enable DSCP-based ingress queues and thresholds on WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE ports to provide congestion avoidance (see the Configuring DSCP-Based Queue Mapping section on page 40-99). The ingress port queues and thresholds on other ports use only Layer 2 CoS. 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 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
Note
With releases earlier than Release 12.2(33)SXI, VSS mode does not support ingress service policies on Layer 2 ports. With Release 12.2(33)SXI and later releases, VSS mode supports ingress service policies on Layer 2 ports.
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 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 40-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.
Policy-map classes specify actions with the following optional commands:
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.
40-16
OL-13013-06
Chapter 40
Classification and Marking on the RP

PFC QoS sends IP traffic to the RP with the final internal DSCP values. CoS is equal to IP precedence in all traffic sent from the RP to egress ports.
Figure 40-7 RP Marking
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 RP and retains the CoS value assigned by the PFC.
Policers
These sections describe policers:

Overview of Policers, page 40-17 Aggregate Policers, page 40-18 Microflow Policers, page 40-19
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.)
40-17
Configuring PFC QoS
The PFC3 supports ingress and egress PFC QoS, which includes ingress and egress policing. Traffic shaping is supported on some WAN modules.
Note
Policers can act on ingress traffic per-port or per-VLAN. 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.
40-18
OL-13013-06
Chapter 40
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. You can configure MAC ACLs to filter IPX traffic.
Note
With Release 12.2(33)SXI4 and later releases, when appropriate for the configuration of the policer, microflow policers use the interface-full flow mask, which can reduce flowmask conflicts. Releases earlier than Release 12.2(33)SXI4 use the full flow mask. By default, microflow policers only affect traffic routed by the RP. To enable microflow policing of other traffic, including traffic in bridge groups, enter the mls qos bridged command. 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.
40-19
Configuring PFC QoS
Policing uses the Layer 2 frame 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 LAN switching modules:

Ingress and Egress Buffers and Layer 2 CoS-Based Queues, page 40-20 Ingress Queue Types, page 40-22 Egress Queue Types, page 40-23 Module to Queue Type Mappings, page 40-24
Ingress and Egress Buffers and Layer 2 CoS-Based Queues

The Ethernet 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 Ethernet ports support the following types of queues:

Standard queues Strict-priority queues
40-20
OL-13013-06
Chapter 40
The Ethernet ports 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. 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.
The Ethernet ports provide congestion avoidance with these types of thresholds within a queue:
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
You can enable DSCP-based queues and thresholds on WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE ports (see the Configuring DSCP-Based Queue Mapping section on page 40-99). The combination of multiple queues and the scheduling algorithms associated with each queue allows the switch to provide congestion avoidance. Figure 40-8 illustrates the drop thresholds for a 1q4t ingress LAN port. Drop thresholds in other configurations function similarly.
40-21
Configuring PFC QoS
Figure 40-8
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.
40-22
OL-13013-06
Chapter 40
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 nonconfigurable (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 nonconfigurable (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 two thresholds, each threshold configurable as either

One strict-priority queue Seven standard queues, each with four thresholds, each threshold configurable as either
40-23
Configuring PFC QoS

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:
Table 40-2
Table 40-2Supervisor Engine Module QoS Queue Structures Table 40-3Ethernet and Fast Ethernet Module Queue Structures Table 40-4Gigabit and 10/100/1000 Ethernet Modules Table 40-510-Gigabit Ethernet Modules
Supervisor Engine Module QoS Queue Structures
Supervisor Engines VS-S720-10G-3CXL VS-S720-10G-3C With Gigabit Ethernet ports enabled With Gigabit Ethernet ports disabled WS-SUP720 WS-SUP720-3B WS-SUP720-3BXL WS-SUP32-10GE 10-Gigabit Ethernet ports Gigabit Ethernet port WS-SUP32-GE
Ingress Queue and Ingress Drop Queue Thresholds Scheduler
Egress Queue and Egress Total Drop Queue Buffer Thresholds Scheduler Size
Ingress Buffer Size
Egress Buffer Size
2q4t 8q4t 1p1q4t
WRR
1p3q4t 1p7q4t 1p2q2t
DWRR or SRR WRR 512 KB
128 MB 112 MB 73 KB 439 KB
2q8t
WRR
1p3q8t
DWRR or SRR 193 MB
105 MB 88 MB 8.1 MB 8.1 MB
17.7 MB 9.6 MB 17.7 MB 9.6 MB
Note
To disable the Supervisor Engine 720-10GE Gigabit Ethernet ports, enter shutdown interface configuration mode commands for the Supervisor Engine 720-10GE Gigabit Ethernet ports, and then enter the mls qos 10g-only global configuration command, which disables the Gigabit Ethernet ports on the Supervisor Engine 720-10GE.
40-24
OL-13013-06
Chapter 40
Table 40-3
Ethernet and Fast Ethernet Module Queue Structures
Modules WS-X6524-100FX-MM WS-X6548-RJ-21 WS-X6548-RJ-45 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-X6148X2-RJ-45 WS-X6148X2-45AF WS-X6024-10FL-MT
Ingress Queue and Drop Thresholds 1p1q0t
Ingress Queue Scheduler
Egress Queue and Drop Thresholds 1p3q1t
Egress Queue Scheduler DWRR
Total Buffer Ingress Size Buffer Size 1,116 KB 28 KB
Egress Buffer Size 1,088 KB
1q4t
2q2t
WRR
128 KB
16 KB
112 KB
64 KB
8 KB
56 KB
128 KB
16 KB
112 KB
1p1q0t 1q4t
1p3q1t 2q2t
DWRR WRR
1,116 KB 64 KB
28 KB 8 KB
1,088 KB 56 KB
Table 40-4
Gigabit and 10/100/1000 Ethernet Modules
Modules WS-X6816-GBIC
Ingress Queue and Drop Thresholds 1p1q4t
Ingress Queue Scheduler
Egress Queue Scheduler WRR
Total Buffer Ingress Size Buffer Size 512 KB 73 KB
Egress Buffer Size 439 KB
40-25
Configuring PFC QoS
Table 40-4
Gigabit and 10/100/1000 Ethernet Modules (continued)
Modules WS-X6748-GE-TX with DFC3 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
Ingress Queue and Drop Thresholds 2q8t
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 CFC 1q8t 2q8t 1q8t 2q8t 1q8t 1q2t
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
Table 40-5
10-Gigabit Ethernet Modules
Modules WS-X6716-10GE Performance mode Oversubscription mode WS-X6708-10GE
Ingress Queue and Drop Thresholds 8q4t 1p7q2t 8q4t
Ingress Queue Scheduler DWRR
Egress Queue Scheduler DWRR SRR
Total Buffer Ingress Size Buffer Size 198 MB 91 MB 108 MB per port 90 MB per port 108 MB
Egress Buffer Size 90 MB per port 1 MB per port group 90 MB
DWRR
1p7q4t
DWRR SRR
200 MB
40-26
OL-13013-06
Chapter 40
Configuring PFC QoS PFC QoS Default Configuration
Table 40-5
10-Gigabit Ethernet Modules (continued)
Modules WS-X6704-10GE with DFC3 WS-X6704-10GE with CFC WS-X6502-10GE WS-X6501-10GEX4
Ingress Queue and Drop Thresholds 8q8t 1q8t 1p1q8t
Ingress Queue Scheduler WRR
Egress Queue and Drop Thresholds 1p7q8t 1p2q1t
Egress Queue Scheduler DWRR DWRR
Total Buffer Ingress Size Buffer Size 16 MB 64.2 MB 2 MB 256 KB
Egress Buffer Size 14 MB 64 MB
PFC QoS Default Configuration

These sections describe the PFC QoS default configuration:

PFC QoS Global Settings, page 40-27 Default Values with PFC QoS Enabled, page 40-28 Default Values with PFC QoS Disabled, page 40-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
40-27
Chapter 40 PFC QoS Default Configuration
Configuring PFC QoS
Feature
Default Value
Received IP precedence to initial internal DSCP map IP precedence 0 = DSCP 0 (initial internal DSCP set from received IP IP precedence 1 = DSCP 8 precedence values) 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 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 None Disabled Disabled
Marked-down DSCP from DSCP map Policers Policy maps Protocol-independent MAC ACL filtering VLAN-based MAC ACL QoS filtering
Default Values with PFC QoS Enabled

These sections list the default values that apply when PFC QoS is enabled:

Receive-Queue Limits, page 40-28 Transmit-Queue Limits, page 40-29 Bandwidth Allocation Ratios, page 40-30 Default Drop-Threshold Percentages and CoS Value Mappings, page 40-30
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%
40-28
OL-13013-06
Chapter 40
Feature 8q8t
Default Value Lowest priority: 80% Intermediate queues: 0% Highest priority: 20%
Transmit-Queue Limits
Feature 2q2t 1p2q2t Default Value Low priority: 80% High priority: 20% Low priority: 70% High priority: 15% Strict priority 15% 1p2q1t Low priority: 70% High priority: 15% Strict priority 15% 1p3q8t Low priority: 50% Medium priority: 20% High priority: 15% Strict priority 15% 1p7q2t Standard queue 1 (lowest priority): 50% Standard queue 2: 20% Standard queue 3: 15% Standard queues 4 through 7: 0% 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%
40-29
Configuring PFC QoS
Bandwidth Allocation Ratios

Feature 2q8t 8q4t 8q8t 1p3q8t 1p7q2t 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 5:255 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 40-31 1q4t Receive Queues, page 40-31 1p1q4t Receive Queues, page 40-32 1p1q0t Receive Queues, page 40-32 1p1q8t Receive Queues, page 40-33 1q8t Receive Queues, page 40-34 2q8t Receive Queues, page 40-35 8q4t Receive Queues, page 40-36 8q8t Receive Queues, page 40-40 2q2t Transmit Queues, page 40-40 1p2q2t Transmit Queues, page 40-41 1p3q8t Transmit Queues, page 40-42 1p7q2t Receive Queues, page 40-43 1p7q4t Transmit Queues, page 40-45 1p7q8t Transmit Queues, page 40-48 1p3q1t Transmit Queues, page 40-49 1p2q1t Transmit Queues, page 40-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.
40-30
OL-13013-06
Chapter 40
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
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%
40-31
Configuring PFC QoS
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)
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)
40-32
OL-13013-06
Chapter 40
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
40-33
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%
40-34
OL-13013-06
Chapter 40
2q8t Receive Queues
Feature Standard receive queue 1 (low 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 queue 2 (high priority) Threshold 1 CoS Tail-drop Thresholds 28 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%
40-35
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
40-36
OL-13013-06
Chapter 40
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%
40-37
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%
40-38
OL-13013-06
Chapter 40
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%
40-39
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%
40-40
OL-13013-06
Chapter 40
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
40-41
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)
40-42
OL-13013-06
Chapter 40
Feature Standard receive queue 1 (lowest priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Standard receive queue 2 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Standard receive queue 3 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Standard receive queue 4 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop
Default Value 0 09, 11, 13, 1517, 19, 21, 23, 25, 27, 29, 31, 33, 39, 4145, 47 Disabled; 70% 1 None Disabled; 100% 2 14 Disabled; 70% 3 and 4 10 and 12 Disabled; 100% 6 and 7 22 Disabled; 100% None 18 and 20 Disabled; 100% None 24 and 30 Enabled; 100% None 26 and 28 Enabled; 100%
40-43
Configuring PFC QoS
Feature (continued) Standard receive queue 5 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Standard receive queue 6 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Standard receive queue 7 (intermediate priority) Threshold 1 CoS DSCP Tail-drop Threshold 2 CoS DSCP Tail-drop Strict-priority transmit queue CoS DSCP Tail-drop
Default Value None 32, 3438 Enabled; 100% None None Enabled; 100% None 4863 Enabled; 100% None None Enabled; 100% None None Enabled; 100% None None Enabled; 100% 5 40 and 46 100% (nonconfigurable)
40-44
OL-13013-06
Chapter 40
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%
40-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%
40-46
OL-13013-06
Chapter 40
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%
40-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%
40-48
OL-13013-06
Chapter 40
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)
40-49
Chapter 40 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 40-51 Class Map Command Restrictions, page 40-54 Policy Map Command Restrictions, page 40-54 Policy Map Class Command Restrictions, page 40-54 Supported Granularity for CIR and PIR Rate Values, page 40-54 Supported Granularity for CIR and PIR Token Bucket Sizes, page 40-55 IP Precedence and DSCP Values, page 40-56
40-50
OL-13013-06
Chapter 40
Configuring PFC QoS PFC QoS Configuration Guidelines and Restrictions
General Guidelines

PFC QoS cannot be applied to IGMP, MLD, or PIM traffic. Configure the same trust mode on all ports supported by an ASIC. Mismatched trust modes cause inconsistent bandwidth and queue-limit ratios. With a Supervisor Engine 720-10GE that is using 10G mode, only one port per-ASIC is available because the 1-Gigabit uplinks are shutdown, making the behavior similar to that of WS-X6708-10GE. When you configure a port on a Supervisor Engine 720-10GE as a member of the VSL, the mls qos trust cos command is automatically added to the port configuration. The match ip precedence and match ip dscp commands filter only IPv4 traffic. The match precedence and match dscp commands filter IPv4 and IPv6 traffic. The set ip dscp and set ip precedence commands are saved in the configuration file as set dscp and set precedence commands. 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.
40-51
Configuring PFC QoS
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. 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
40-52
OL-13013-06
Chapter 40
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.

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. 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.

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 Network Address Translation (NAT)
You cannot apply microflow policing to ARP traffic. The PFC3 does not apply egress policing to traffic that is being bridged to the RP. The PFC3 does not apply egress policing or egress DSCP mutation to multicast traffic from the RP. With a PFC3A, PFC QoS does not rewrite the ToS byte in bridged multicast traffic. The PFC3 supports up to 1023 configurable 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.
40-53
Configuring PFC QoS
Class Map Command Restrictions

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
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) Granularity 32768 (32 Kb) 65536 (64 Kb) 131072 (128 Kb)
40-54
OL-13013-06
Chapter 40
CIR and PIR Rate Value Range 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 Gbs) 1073741825 to 2147483648 (2 Gbs) 2147483649 to 4294967296 (4 Gbs) 4294967296 to 8589934592 (8 Gbs) 8589934593 to 17179869184 (16 Gbs)
Granularity 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) 268435456 (256 Mb)
17179869185 to 34359738368 (32 Gbs) 536870912 (512 Mb) 34359738369 to 68719476736 (64 Gbs) 1073741824 (1024 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)
Within each range, PFC QoS programs the PFC with token bucket sizes that are multiples of the granularity values.
40-55
Chapter 40 Configuring PFC QoS
Configuring PFC QoS
IP Precedence and DSCP Values

3-bit IP Precedence 6 MSb1 of ToS 8 7 6 6-bit 5 4 3 DSCP 3-bit IP Precedence 6 MSb1 of ToS 8 7 6 6-bit DSCP 5 4 3
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 in Cisco IOS Release 12.2SX:

Enabling PFC QoS Globally, page 40-57 Enabling Ignore Port Trust, page 40-58 Configuring DSCP Transparency, page 40-59 Enabling Queueing-Only Mode, page 40-59
40-56
OL-13013-06
Chapter 40
Configuring PFC QoS Configuring PFC QoS
Enabling Microflow Policing of Bridged Traffic, page 40-60 Enabling VLAN-Based PFC QoS on Layer 2 LAN Ports, page 40-61 Enabling Egress ACL Support for Remarked DSCP, page 40-61 Creating Named Aggregate Policers, page 40-62 Configuring a PFC QoS Policy, page 40-65 Configuring Egress DSCP Mutation, page 40-82 Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports, page 40-84 Configuring DSCP Value Maps, page 40-86 Configuring the Trust State of Ethernet LAN Ports, page 40-90 Configuring Trusted Boundary with Cisco Device Verification, page 40-91 Configuring the Ingress LAN Port CoS Value, page 40-92 Configuring Standard-Queue Drop Threshold Percentages, page 40-93 Mapping QoS Labels to Queues and Drop Thresholds, page 40-98 Allocating Bandwidth Between Standard Transmit Queues, page 40-107 Setting the Receive-Queue Size Ratio, page 40-109 Configuring the Transmit-Queue Size Ratio, page 40-110
Note
PFC QoS processes both unicast and multicast traffic.
Enabling PFC QoS Globally

To enable PFC QoS globally, perform this task: Command
Router(config)# mls qos Router(config)# end Router# show mls qos [ipv6]
Purpose Enables PFC QoS globally on the switch. Exits configuration mode. Verifies the configuration.
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 IP shortcut packets: 1410 Packets dropped by policing: 0
40-57
Configuring PFC QoS
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

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
Router(config)# mls qos marking ignore port-trust Router(config)# end Router# show mls qos | include ignores
Purpose Enables ignore port trust globally on the switch. Exits configuration mode. Verifies the configuration.
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#
40-58
OL-13013-06
Chapter 40
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
Router(config)# no mls qos rewrite ip dscp Router(config)# end Router# show mls qos | include rewrite
Purpose Disables egress ToS byte rewrite globally on the switch. Exits configuration mode. Verifies the configuration.
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#
Enabling Queueing-Only Mode

To enable queueing-only mode on the switch, perform this task: Command
Router(config)# mls qos queueing-only Router(config)# end Router# show mls qos
Purpose Enables queueing-only mode on the switch. Exits configuration mode. Verifies the configuration.
40-59
Configuring PFC 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

By default, microflow policers affect only routed traffic. To enable microflow policing of bridged traffic on specified VLANs, perform this task: Command
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. Exits configuration mode. Verifies the configuration.
Router(config-if)# end Router# show mls qos 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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#
40-60
OL-13013-06
Chapter 40
Enabling VLAN-Based PFC QoS on Layer 2 LAN Ports

Note
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
Router(config)# interface {{type {port-channel number}}
1
Purpose
slot/port} |
Selects the interface to configure. Enables VLAN-based PFC QoS on a Layer 2 LAN port or a Layer 2 EtherChannel. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos vlan-based
Router(config-if)# end Router# show mls qos 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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.

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]
Purpose Selects the ingress interface to configure. Enables egress ACL support for remarked DSCP on the ingress interface.
40-61
Configuring PFC QoS
Command
Step 3 Step 4
Router(config-if)# end Router# show running-config interface ({type1 slot/port} | {port-channel number}} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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
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}]
Purpose Creates 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:
egress policing decisions at the ingress interface, on the PFC or ingress DFC.
40-62
OL-13013-06
Chapter 40
Policers affected by this restriction deliver an aggregate rate that is the sum of all the independent policing rates.

You can apply aggregate policers to IPv6 traffic. Policing uses the Layer 2 frame size. See the PFC QoS Configuration Guidelines and Restrictions section on page 40-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(33)SXH1 and earlier10 gigabits per second, entered as
10000000000
Maximum with Release 12.2(33)SXH2 and later64 gigabits per second, entered as
64000000000

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:
Because the token bucket must be large enough to hold at least one frame, configure the token
bucket size to be 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 maximum_burst_bytes parameter must be set larger than the normal_burst_bytes parameter To sustain a specific rate, set the token bucket size to be at least the rate value divided by 2000.
Note
To provide compatibility with QoS as implemented in the Catalyst operating system, Release 12.2(33)SXI and later releases support 1 byte as the minimum token bucket size, entered as 1.
With Release 12.2(33)SXI and later releases, the minimum token bucket size is 1 byte, entered
as 1.
With releases earlier than Release 12.2(33)SXI, the minimum token bucket size is 1000 bytes,
entered as 1000.
The maximum token bucket size is 512 megabytes, entered as 512000000.
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(33)SXH1 and earlier10 gigabits per second, entered as
10000000000
64000000000
(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.
40-63
Configuring PFC QoS
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.
(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#
40-64
OL-13013-06
Chapter 40

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 40-65 Configuring MAC ACLs, page 40-66 Configuring ARP ACLs for QoS Filtering, page 40-70 Configuring a Class Map, page 40-70 Verifying Class Map Configuration, page 40-72 Configuring a Policy Map, page 40-73 Verifying Policy Map Configuration, page 40-79 Attaching a Policy Map to an Interface, page 40-79 Configuring Dynamic Per-Session Attachment of a Policy Map, page 40-81
Note
PFC QoS policies process both unicast and multicast traffic.
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
Extended ACLs Yes: 100 to 199 2000 to 2699 Yes (named)
Named ACLs Yes
IPv6
Yes
40-65
Configuring PFC QoS
Protocol MAC Layer ARP
Numbered ACLs No No
Extended ACLs No No
Named ACLs Yes Yes
The PFC3 supports IPv6 named extended ACLs and named standard ACLs. The PFC3 supports ARP ACLs.
Note
The PFC3 does not apply IP ACLs to ARP traffic. 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.
PFC QoS supports time-based Cisco IOS ACLs. Except for MAC ACLs and ARP 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/12_2/security/configuration/guide/scfacls.html

See Chapter 44, Configuring Network Security, for additional information about ACLs in
Cisco IOS Release 12.2SX.

class-map (optional)Enter the class-map command to define one or more traffic classes by specifying the criteria by which traffic is classified. policy-mapEnter 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 40-66 Enabling VLAN-Based MAC QoS Filtering, page 40-68 Configuring MAC ACLs, page 40-68
Note
You can use MAC ACLs with VLAN ACLs (VACLs). For more information, see Chapter 48, Configuring Port ACLs and VLAN ACLs.
Configuring Protocol-Independent MAC ACL Filtering
Note
PFC3A mode does not support protocol-independent MAC ACL filtering.
40-66
OL-13013-06
Chapter 40
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.
1.
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 PFC. Protocol-independent MAC ACL filtering supports microflow policing when the permitted traffic is routed in software by the RP.
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
40-67
Configuring PFC QoS
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

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.
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. You can configure MAC ACLs that do VLAN-based filtering or CoS-based filtering or both. 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
Router(config)# mac host name mac_addr Router(config)# mac access-list extended list_name Router(config-ext-macl)# {permit | deny} {src_mac_mask | {host name src_mac_name} | any} {dest_mac_mask | {host name dst_mac_name} | any} [{protocol_keyword | {ethertype_number ethertype_mask}} [vlan vlan_ID] [cos cos_value]]
Purpose (Optional) Assigns a name to a MAC address. Configures a MAC ACL. Configures an access control entry (ACE) in a MAC ACL. The source and destination MAC addresses can be specified by MAC address masks or by names created with the mac host command.
40-68
OL-13013-06
Chapter 40
When configuring an entry in a MAC-Layer ACL, note the following information:

The PFC3 supports the ipx-arpa and ipx-non-arpa keywords. Cisco IOS Release 12.2SX supports the vlan and cos keywords. The vlan and cos keywords are not supported in MAC ACLs used for VACL filtering. 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. 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)
40-69
Configuring PFC QoS
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 PFC3 does not apply IP ACLs to ARP traffic. You cannot apply microflow policing to ARP traffic.
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 Step 2
Router(config)# arp access-list list_name Router(config-arp-nacl)# {permit | deny} {ip {any | host sender_ip | sender_ip sender_ip_wildcardmask} mac any
Purpose Configures an ARP ACL for QoS filtering. Configures an access control entry (ACE) in an ARP ACL for QoS filtering.
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 40-71 Class Map Filtering Guidelines and Restrictions, page 40-71 Configuring Filtering in a Class Map, page 40-72
40-70
OL-13013-06
Chapter 40
Creating a Class Map

To create a class map, perform this task: Command
Router(config)# class-map class_name
Purpose Creates a class map.
Class Map Filtering Guidelines and Restrictions

When configuring class map filtering, follow these guidelines and restrictions:

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 ip any any entry, all match criteria after the deny ip any any 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 ip any any 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 ip any any entry into different class maps.
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.

PFC QoS supports the match protocol ip command for IPv4 traffic. 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. Cisco IOS Release 12.2SX does not detect the use of unsupported commands until you attach a policy map to an interface. 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:
40-71
Configuring PFC QoS
Configuring MAC ACLs, page 40-66 Configuring ARP ACLs for QoS Filtering, page 40-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 40-65.
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)# match protocol ipv6
Purpose (Optional) Configures the class map to filter using an ACL. (Optionalfor IPv6 traffic) Configures the class map to filter IPv6 traffic. (Optionalfor IPv4 or IPv6 traffic) Configures the class map to filter based on up to eight IP precedence values.
Note
Router (config-cmap)# match precedence ipp_value1 [ipp_value2 [ipp_valueN]]
Does not support source-based or destination-based microflow policing.
Router (config-cmap)# match dscp dscp_value1 [dscp_value2 [dscp_valueN]]
(Optionalfor IPv4 or IPv6 traffic only) Configures the class map to filter based on up to eight DSCP values.
Note
Router (config-cmap)# match ip precedence ipp_value1 [ipp_value2 [ipp_valueN]]
(Optionalfor IPv4 traffic) Configures the class map to filter based on up to eight IP precedence values.
Note
Router (config-cmap)# match ip dscp dscp_value1 [dscp_value2 [dscp_valueN]]
(Optionalfor IPv4 traffic) Configures the class map to filter based on up to eight DSCP values.
Note
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 End with CNTL/Z.
40-72
OL-13013-06
Chapter 40
Router(config-cmap)# match ip precedence 5 Router(config-cmap)# end

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 40-73 Policy Map Class Configuration Guidelines and Restrictions, page 40-73 Creating a Policy Map Class and Configuring Filtering, page 40-74 Configuring Policy Map Class Actions, page 40-74
Creating a Policy Map

To create a policy map, perform this task: Command
Router(config)# policy-map policy_name
Purpose Creates a policy map.
Policy Map Class Configuration Guidelines and Restrictions

When you configuring policy map classes, follow the guidelines and restrictions:
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. 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.
40-73
Configuring PFC QoS
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.
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. 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.
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.
The set ip dscp and set ip precedence commands are saved in the configuration file as set dscp
and set precedence commands.

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 40-75
40-74
OL-13013-06
Chapter 40
Configuring the Policy Map Class Trust State, page 40-75 Configuring Policy Map Class Policing, page 40-75
Configuring Policy Map Class Marking
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}
Purpose Configures the policy map class to mark matched untrusted traffic with the configured DSCP or IP precedence value.
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.
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. Using a Named Aggregate Policer, page 40-76 Configuring a Per-Interface Policer, page 40-76
These sections describe configuration of policy map class policing:

40-75
Configuring PFC QoS
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
Purpose Configures the policy map class to use a previously defined named aggregate policer.
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}]
Purpose Creates a per-interface policer and configures the policy-map class to use it.
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:
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. You can apply aggregate and microflow policers to IPv6 traffic. Policing uses the Layer 2 frame size. See the PFC QoS Configuration Guidelines and Restrictions section on page 40-50 for information about rate and burst size granularity.
40-76
OL-13013-06
Chapter 40
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:
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. PFC QoS supports the mask src-only keywords for both IP traffic and MAC traffic.
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. PFC QoS supports the mask dest-only keywords for both IP traffic and MAC 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.
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(33)SXH1 and earlier10 gigabits per second, entered as
10000000000
64000000000

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:
Because the token bucket must be large enough to hold at least one frame, configure the token
bucket size to be 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 maximum_burst_bytes parameter must be set larger than the normal_burst_bytes parameter. To sustain a specific rate, set the token bucket size to be at least the rate value divided by 2000.
Note
To provide compatibility with QoS as implemented in the Catalyst operating system, Release 12.2(33)SXI and later releases support 1 byte as the minimum token bucket size, entered as 1.
With Release 12.2(33)SXI and later releases, the minimum token bucket size is 1 byte, entered
as 1.
With releases earlier than Release 12.2(33)SXI, the minimum token bucket size is 1000 bytes,
entered as 1000.
40-77
Configuring PFC QoS
The maximum token bucket size is 512 megabytes, entered as 512000000.
The valid range of values for the pir bits_per_second parameter (not supported with the flow keyword) 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(33)SXH1 and earlier10 gigabits per second, entered as
10000000000
64000000000
(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.
40-78
OL-13013-06
Chapter 40
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)# end Router# show policy-map interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}
Attaches a policy map to the interface. Exits configuration mode. Verifies the configuration.
40-79
Configuring PFC QoS
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. PFC QoS supports the output keyword only on Layer 3 interfaces (either LAN ports configured as Layer 3 interfaces or VLAN interfaces).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:
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

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
40-80
OL-13013-06
Chapter 40
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 Dynamic Per-Session Attachment of a Policy Map

To configure and enable per-session QoS, perform these steps:
Define the ingress and egress QoS policy maps to be assigned when users are authenticated. Configure identity policies to specify the policy maps to be assigned. In the user profiles on the RADIUS server, configure the Cisco vendor-specific attributes (VSAs) to specify which ingress and egress QoS policy maps will be assigned to each user.
To define the policy maps and associate them with an identity policy, follow these steps: Command
Router(config)# policy-map in_policy_name Router(config-pmap)# class class_map_name ... Router(config-pmap-c)# exit Router(config)# policy-map out_policy_name Router(config-pmap)# class class_map_name ... Router(config-pmap-c)# exit Router(config)# identity policy policy1
Purpose Configures an ingress QoS policy map. Configures policy map class. Exits policy map class configuration submode. Configures an egress QoS policy map. Configures policy map class. Exits policy map class configuration submode. Creates an identity policy, and enters identity policy configuration submode. Associates the ingress QoS policy map with this identity. Associates the egress QoS policy map with this identity. Exits identity policy configuration submode and returns to privileged EXEC mode. Verifies the configuration when a session is active on the interface.
Router(config-identity-policy)# service-policy type qos input in_policy_name Router(config-identity-policy)# service-policy type qos output out_policy_name
Step 10 Router(config-identity-policy)# end Step 11 Router# show epm session [summary | ip ip_addr |
mac mac_addr]
To remove the identity policy from the switch, use the no identity policy policy_name command. After the policy maps have been defined on the switch, configure the Cisco AV pair attributes in each user profile on the RADIUS server using the policy map names:
cisco-avpair = ip:sub-policy-In=in_policy_name
40-81
Configuring PFC QoS
cisco-avpair = ip:sub-policy-Out=out_policy_name
To set the Cisco AV pair attributes on the RADIUS server, perform the following task: Command or Action
sub-policy-In=in_policy_name sub-policy-Out=out_policy_name
Purpose Enters the two Cisco AV pairs for service policy on the RADIUS server in the user file. When the switch requests the policy name, this information in the user file is supplied. A RADIUS user file contains an entry for each user that the RADIUS server will authenticate. Each entry, which is also referred to as a user profile, establishes an attribute the user can access. In this example, you have configured a service policy that attaches a QoS policy map to the interface and specifies the direction (inbound for data packets traveling into the interface or outbound for data packets leaving the interface). The policy map applied in the inbound direction is example_in_qos and the outbound policy map is example_out_qos. This example shows the configuration in the user file on the RADIUS server:
userid Password ="cisco" Service-Type = Framed, Framed-Protocol = PPP, cisco-avpair = "sub-policy-In=example_in_qos", cisco-avpair = "sub-policy-Out=example_out_qos"
This example shows the output of the show epm session summary command when a session is active:
Router# show epm session summary EPM Session Information ----------------------Total sessions seen so far : 5 Total active sessions : 1 Session IP Address : 192.0.2.1 -------------------
This example shows the output of the show epm session ip ip_addr command when a session is active on the interface with IP address 192.0.2.1:
Router# show epm session ip 192.0.2.1 Admission feature AAA Policies Input Service Policy Output Service Policy : AUTHPROXY : : in_policy_name : out_policy_name
Configuring Egress DSCP Mutation

These sections describe how to configure egress DSCP mutation:

Configuring Named DSCP Mutation Maps, page 40-83 Attaching an Egress DSCP Mutation Map to an Interface, page 40-84
40-82
OL-13013-06
Chapter 40
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)# end Router# show mls qos maps
Purpose Configures a named DSCP mutation map.
Step 2 Step 3
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.
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.
40-83
Configuring PFC QoS
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)# end Router# show running-config interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Attaches an egress DSCP mutation map to the interface. Exits configuration mode. Verifies the configuration.
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
Configuring Ingress CoS Mutation on IEEE 802.1Q Tunnel Ports

IEEE 802.1Q tunnel ports configured to trust received CoS support ingress CoS mutation (see the Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports section on page 40-86 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 40-84 Configuring Ingress CoS Mutation Maps, page 40-85 Applying Ingress CoS Mutation Maps to IEEE 802.1Q Tunnel Ports, page 40-86
Ingress CoS Mutation Configuration Guidelines and Restrictions

When configuring ingress CoS mutation, follow these guidelines and restrictions:

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. The WS-X6704-10GE, WS-X6748-SFP, WS-X6724-SFP, and WS-X6748-GE-TX switching modules support ingress CoS mutation.
40-84
OL-13013-06
Chapter 40
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 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)# end Router# show mls qos maps cos-mutation
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. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
40-85
Configuring PFC QoS
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#
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
1
Purpose
slot/port} |
Selects the interface to configure. Attaches an ingress CoS mutation map to the interface. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos cos-mutation mutation_map_name 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 40-87 Mapping Received IP Precedence Values to Internal DSCP Values, page 40-87
40-86
OL-13013-06
Chapter 40
Configuring DSCP Markdown Values, page 40-88 Mapping Internal DSCP Values to Egress CoS Values, page 40-89
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. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
Router(config)# end Router# show mls qos maps
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. Exits configuration mode. Verifies the configuration.
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
40-87
Configuring PFC QoS

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)# end Router# show mls qos maps
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. 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#
40-88
OL-13013-06
Chapter 40

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)# end Router# show mls qos maps
Purpose Configures the internal DSCP to egress CoS map.
Step 2 Step 3
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
40-89
Configuring PFC QoS
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 Ports

By default, all ports are untrusted. You can configure the port trust state on all Ethernet LAN ports.
Note
On non-Gigabit Ethernet 1q4t/2q2t ports, you must repeat the trust configuration in a class map. To configure the trust state of a port, perform this task:
Command
1
Purpose
slot/port} |
Selects the interface to configure. Configures the trust state of the port. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos trust [dscp | ip-precedence | cos2] Router(config-if)# end Router# show queueing interface type1 slot/port | include Trust state 1. 2. type = fastethernet, gigabitethernet, or tengigabitethernet. Not supported for serial, pos or atm interface types.
When configuring the trust state of a port, note the following information:

To apply a non-default trust configuration only when a Cisco IP phone is attached to the port, see the Configuring Trusted Boundary with Cisco Device Verification section on page 40-91. To configure QoS on an attached IP phone, see the Configuring Cisco IP Phone Support section on page 15-7. With no other keywords, the mls qos trust command is equivalent to mls qos trust dscp.
40-90
OL-13013-06
Chapter 40
You can use the mls qos trust dscp command to enable DSCP-based receive-queue drop thresholds on WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE ports (see the Configuring DSCP-Based Queue Mapping section on page 40-99). 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. 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 40-84). 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#
Configuring Trusted Boundary with Cisco Device Verification

Release 12.2(33)SXI1 and later releases support the trusted boundary with Cisco device verification feature, which configures Ethernet LAN ports to use CDP to detect whether or not a Cisco IP phone is attached to the port.

If CDP detects a Cisco IP phone, QoS applies a configured mls qos trust dscp, mls qos trust ip-precedence, or mls qos trust cos interface command. If CDP does not detect a Cisco IP phone, QoS ignores any configured nondefault trust state.
To configure trusted boundary with Cisco device verification, perform this task: Command
Router(config)# interface {{type1 slot/port} | {port-channel number}} Router(config-if)# mls qos trust device cisco-phone Router(config-if)# end Router# show queueing interface type include [Tt]rust 1.
1
Purpose Selects the interface to configure. Configures trusted boundary with Cisco device verification. Exits configuration mode.
slot/port |
type = fastethernet, gigabitethernet, tengigabitethernet.
40-91
Configuring PFC QoS
When configuring trusted boundary with Cisco device verification, note the following information:

CDP must be enabled on the port to use trusted boundary with Cisco device verification. To configure QoS on an attached IP phone, see the Configuring Cisco IP Phone Support section on page 15-7.
This example shows how to configure trusted boundary with Cisco device verification 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)# mls qos trust device cisco-phone Router(config-if)# end Router#
This example shows how to verify the configuration on a port configured to trust CoS, but that does not have a Cisco IP phone attached:
Router# show queueing interface gigabitethernet 1/1 | include [Tt]rust Trust boundary enabled Port is untrusted Extend trust state: not trusted [COS = 0] Router#
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
Router(config)# interface {{type1 slot/port} | {port-channel number}} Router(config-if)# mls qos cos port_cos Router(config-if)# end Router# show queuing interface {ethernet | fastethernet | gigabitethernet} slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Selects the interface to configure. Configures the ingress LAN port CoS value. Exits configuration mode. Verifies the configuration.
40-92
OL-13013-06
Chapter 40
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 40-94 Configuring a WRED-Drop Transmit Queue, page 40-95 Configuring a WRED-Drop and Tail-Drop Receive Queue, page 40-95 Configuring a WRED-Drop and Tail-Drop Transmit Queue, page 40-96 Configuring 1q4t/2q2t Tail-Drop Threshold Percentages, page 40-97
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), 1p7q2t (receive), 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.
When you configure multiple-threshold standard queues, note the following information:

40-93
Configuring PFC QoS
When configuring the WRED-drop thresholds, note the following information:

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.
Configuring a Tail-Drop Receive Queue

These port types have only tail-drop thresholds in their receive-queues:

1q2t 1p1q4t 2q8t 1q8t
To configure the drop thresholds, perform this task: Command

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)# end Router# show queueing interface {fastethernet | gigabitethernet} slot/port
Purpose Selects the interface to configure. Configures the receive-queue tail-drop threshold percentages. Exits configuration mode. Verifies the configuration.
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]
40-94
OL-13013-06
Chapter 40
<...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
Router(config)# interface type slot/port Router(config-if)# wrr-queue random-detect min-threshold queue_id thr1% [thr2%] Router(config-if)# wrr-queue random-detect max-threshold queue_id thr1% [thr2%] Router(config-if)# end Router# show queueing interface type 1.
1
Selects the interface to configure. Configures the low WRED-drop thresholds. Configures the high WRED-drop thresholds. Exits configuration mode.
slot/port
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) 1p7q2t (receive) 1p1q8t (receive)

1
Purpose
slot/port
Selects the interface to configure. Configures the 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)# rcv-queue random-detect min-threshold queue_id thr1% thr2% thr3% thr4% thr5% thr6% thr7% thr8% Router(config-if)# rcv-queue random-detect max-threshold queue_id thr1% thr2% thr3% thr4% thr5% thr6% thr7% thr8% Router(config-if)# rcv-queue random-detect queue_id Router(config-if)# end Router# show queueing interface type 1.
1
Step 4
Configures the high WRED-drop thresholds.
Enables WRED-drop thresholds. Exits configuration mode.
slot/port
40-95
Configuring PFC QoS
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) 1p7q8t (transmit)

1
Purpose
slot/port
Selects the interface to configure. Configures the 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)# wrr-queue random-detect min-threshold queue_id thr1% [thr2% thr3% thr4% thr5% thr6% thr7% thr8%] Router(config-if)# wrr-queue random-detect max-threshold queue_id thr1% [thr2% thr3% thr4% thr5% thr6% thr7% thr8%] Router(config-if)# wrr-queue random-detect queue_id Router(config-if)# end Router# show queueing interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Step 4
Configures the high WRED-drop thresholds.
Enables WRED-drop thresholds. Exits configuration mode. Verifies the configuration.
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#
40-96
OL-13013-06
Chapter 40
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
Router(config)# interface {ethernet | fastethernet | gigabitethernet} slot/port Router(config-if)# wrr-queue threshold queue_id thr1% thr2% Router(config-if)# end Router# show queueing interface {ethernet | fastethernet | gigabitethernet} slot/port
Purpose Selects the interface to configure. Configures the receive- and transmit-queue tail-drop thresholds. Exits configuration mode. Verifies the configuration.
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] <...Output Truncated...> Receive queues [type = 1q4t]:
40-97
Configuring PFC QoS
<...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 40-98 Configuring DSCP-Based Queue Mapping, page 40-99 Configuring CoS-Based Queue Mapping, page 40-103
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)
40-98
OL-13013-06
Chapter 40
Configuring DSCP-Based Queue Mapping

These sections describe how to configure DSCP-based queue mapping:

Configuring Ingress DSCP-Based Queue Mapping, page 40-99 Mapping DSCP Values to Standard Transmit-Queue Thresholds, page 40-101 Mapping DSCP Values to the Transmit Strict-Priority Queue, page 40-103
Note
DSCP-based queue mapping is supported on WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE ports. To configure DSCP-based queue mapping on Supervisor Engine 720-10GE ports, you must enter shutdown interface configuration mode commands for the Supervisor Engine 720-10GE Gigabit Ethernet ports, and then enter the mls qos 10g-only global configuration command, which disables the Gigabit Ethernet ports on the Supervisor Engine 720-10GE.
Enabling DSCP-Based Queue Mapping

To enable DSCP-based queue mapping, perform this task: Command
Router(config)# interface tengigabitethernet slot/port Router(config-if)# mls qos queue-mode mode-dscp Router(config-if)# end Router# show queueing interface tengigabitethernet slot/port | include Queueing Mode
Purpose Selects the interface to configure. Enables DSCP-based queue mapping. Exits configuration mode. Verifies the configuration.
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 40-99 Mapping DSCP Values to Standard Receive-Queue Thresholds, page 40-100
40-99
Configuring PFC QoS
Configuring the Port to Trust DSCP
To configure the port to trust DSCP perform this task: Command

Router(config)# interface tengigabitethernet slot/port Router(config-if)# mls qos trust dscp Router(config-if)# end Router# show queueing interface tengigabitethernet slot/port | include Trust state
Purpose Selects the interface to configure. Configures the port to trust received DSCP values. Exits configuration mode. Verifies the configuration.
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)# end Router# show queueing interface tengigabitethernet slot/port
Purpose Selects the interface to configure. Maps DSCP values to the standard receive queue thresholds. 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 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#
40-100
OL-13013-06
Chapter 40
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#
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]]]]]]]
Purpose Selects the interface to configure. Maps DSCP values to a standard transmit-queue threshold.
40-101
Configuring PFC QoS
Command
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.
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#
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
40-102
OL-13013-06
Chapter 40
<...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. 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 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 40-104 Mapping CoS Values to Standard Transmit-Queue Thresholds, page 40-104 Mapping CoS Values to Strict-Priority Queues, page 40-105
40-103
Configuring PFC QoS
Mapping CoS Values to Tail-Drop Thresholds on 1q4t/2q2t LAN Ports, page 40-106
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)# end Router# show queueing interface type 1.
1
Purpose Selects the interface to configure. Maps CoS values to the standard receive queue thresholds. Exits configuration mode.
slot/port
Step 3 Step 4
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)# end Router# show queueing interface type 1.
1
Purpose Selects the interface to configure. Maps CoS values to a standard transmit-queue threshold.
Step 3 Step 4

slot/port
40-104
OL-13013-06
Chapter 40
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#
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. Exits configuration mode.
Router(config-if)# priority-queue cos-map queue_# cos1 [cos2 [cos3 [cos4 [cos5 [cos6 [cos7 [cos8]]]]]]] Router(config-if)# end Router# show queueing interface type 1.
1
Step 3 Step 4
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
40-105
Configuring PFC QoS
--------------------------------------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#
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
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)# end Router# show queueing interface type1 slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Selects the interface to configure. Maps CoS values to a tail-drop threshold.
Step 3 Step 4
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.
40-106
OL-13013-06
Chapter 40
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#
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 the queues as they are serviced sequentially:

Shaped round robin (SRR)SRR allows a queue to use only the allocated bandwidth. Supported as an option on 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. See the Module to Queue Type Mappings section on page 40-24 for information about the modules that support these algorithms.
You can enter percentages or 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.
40-107
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 40-98). Percentages should add up to 100. You must enter percentages for all the standard transmit queues on the port. 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
Step 3 Step 4
Router(config-if)# end Router# show queueing interface type 1.

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#
40-108
OL-13013-06
Chapter 40
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
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#
40-109
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. type = fastethernet, gigabitethernet, or tengigabitethernet
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:
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 (1p7q8t) WS-SUP32-10GE-3B (1p3q8t) WS-SUP32-GE-3B (1p3q8t) WS-X6708-10GE, WS-X6716-10GE, WS-X6716-10T, and Supervisor Engine 720-10GE (1p7q4t)

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.
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
40-110
OL-13013-06
Chapter 40
Configuring PFC QoS Common QoS Scenarios
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 40-111. 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 40-111 Classifying Traffic from PCs and IP Phones in the Access Layer, page 40-112 Accepting the Traffic Priority Value on Interswitch Links, page 40-115 Prioritizing Traffic on Interswitch Links, page 40-116 Using Policers to Limit the Amount of Traffic from a PC, page 40-119
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
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.
40-111
Chapter 40 Common QoS Scenarios
Configuring PFC QoS
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, see 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. 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)
40-112
OL-13013-06
Chapter 40
This classification strategy provides a way to support three different classes of service on the network:

High priority for voice traffic Medium priority for voice signaling and important application traffic Low priority for the remaining traffic
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
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
40-113
Configuring PFC QoS
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 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
40-114
OL-13013-06
Chapter 40
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. 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
40-115
Configuring PFC QoS
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 40-112 and the Accepting the Traffic Priority Value on Interswitch Links section on page 40-115 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 Ethernet ports 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)
The Ethernet ports 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. 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 40-112) or to trust the packets incoming DSCP value (as in the Accepting the Traffic Priority Value on Interswitch Links section on page 40-115). 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 (dscp= d1d2)
40-116
OL-13013-06
Chapter 40
4 : 5 : 6 : Router#
05 05 05 05 05 05 05 05 06 06 06 06 06 06 06 06 07 07 07 07 07 07 07 07
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 3 5 3 6 3 7 3 8 4 1 5 <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.
40-117
Configuring PFC QoS
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 DSCP-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 40-104. 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. The scheduling algorithms used on the Ethernet ports 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. 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 40-107).
40-118
OL-13013-06
Chapter 40
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 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 40-112 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
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
40-119
Chapter 40 PFC QoS Glossary
Configuring PFC QoS
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 50-Mbps 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 PFC3 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
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.
40-120
OL-13013-06
Chapter 40
Configuring PFC QoS PFC QoS Glossary
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. 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. ThresholdPercentage 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.
40-121
Chapter 40 PFC QoS Glossary
Configuring PFC QoS
Tip
40-122
OL-13013-06
C H A P T E R
41
Using AutoQoS
This chapter describes how to use the automatic quality of service (QoS) configuration feature. Release 12.2(33)SXH and later releases support the automatic quality of service (QoS) configuration feature.
Note
Tip

Understanding AutoQoS, page 41-1 Using AutoQoS, page 41-3
Understanding AutoQoS
AutoQoS is a macro that applies the recommended Architecture for Voice, Video, and Integrated Data (AVVID) QoS settings to a port. These sections describe how autoQoS works:

AutoQoS Support for a Cisco IP Phone, page 41-2 AutoQoS Support for Cisco IP Communicator, page 41-2 AutoQoS Support for Marked Traffic, page 41-2
41-1
Chapter 41 Understanding AutoQoS
Using AutoQoS
AutoQoS Support for a Cisco IP Phone

Cisco IP phones are usually connected directly to ports. Optionally, you can attach a PC to the phone and use the phone as a hop to the switch. The traffic that comes from the phone can be marked with an 802.1Q or 802.1p tag. The tag contains a VLAN ID and CoS value. When you configure the port to trust the CoS value that comes from the phone, the switch uses the CoS value to prioritize the phone traffic. There is a three-port switch built into Cisco IP phones that forwards the traffic that comes from the PC, the phone, and the switch port. Cisco IP phones have trust and classification capabilities that you need to configure (see the Configuring Cisco IP Phone Support section on page 15-7). AutoQoS supports Cisco IP phones with the auto qos voip cisco-phone interface configuration command. When you enter the auto qos voip cisco-phone interface configuration command on a port that is configured to support an IP phone and to which an IP phone is connected, the autoQoS feature does the following:

If QoS was not already enabled, enables QoS globally. If VLAN-based QoS was configured for the port, reverts to the default port-based QoS (done for all ports on switching modules with 1p1q0t/1p3q1t ports). Sets the port trust state to trust CoS. Creates and applies a trust-CoS QoS policy to ports on switching modules with non-Gigabit Ethernet 1q4t/2q2t ports, which do not support port trust.
AutoQoS Support for Cisco IP Communicator

The Cisco IP Communicator program runs on a PC and emulates a Cisco IP phone. The Cisco IP Communicator marks its voice traffic with a DSCP value instead of a CoS value. When you configure the port to trust the DSCP value that comes from the Cisco IP Communicator, the switch uses the DSCP value to prioritize the Cisco IP Communicator traffic. AutoQoS supports the Cisco IP Communicator program with the auto qos voip cisco-softphone interface configuration command. When you enter the auto qos voip cisco-softphone interface configuration command on a port that is connected to a device running the Cisco IP Communicator program, the autoQoS feature does the following:

If QoS was not already enabled, enables QoS globally. If VLAN-based QoS was configured for the port, reverts to the default port-based QoS (done for all ports on switching modules with 1p1q0t/1p3q1t ports). If a trust state was configured for the port, reverts to the default untrusted state. Creates and applies ingress policers to trust DSCP 46 and remark DSCP 26 packets to DSCP 24. Packets with other DSCP values or out-of-profile packets are remarked with DSCP 0.
AutoQoS Support for Marked Traffic

Ports that connect to the interior of your network might receive traffic that has already been marked with QoS labels that are consistent with your network QoS policies, and which do not need to be changed. You can use the QoS trust feature to process the marked traffic using the received QoS values.
41-2
OL-13013-06
Chapter 41
Using AutoQoS Using AutoQoS
AutoQoS supports marked traffic with the auto qos voip trust interface configuration command. When you enter the auto qos voip trust interface configuration command, the autoQoS feature does the following:

If QoS was not already enabled, enables QoS globally. If VLAN-based QoS was configured for the port, reverts to the default port-based QoS (done for all ports on switching modules with 1p1q0t/1p3q1t ports). If the port is configured with the switchport command, sets the port trust state to trust CoS. If the port is not configured with the switchport command, sets the port trust state to trust DSCP. Creates and applies a trust-CoS or trust-DSCP QoS policy to ports on switching modules with non-Gigabit Ethernet 1q4t/2q2t ports, which do not support port trust.
Using AutoQoS
These sections describe how to use autoQoS:

AutoQoS Configuration Guidelines and Restrictions, page 41-3 Configuring AutoQoS, page 41-4
AutoQoS Configuration Guidelines and Restrictions

These sections provide the configuration guidelines and restrictions for autoQoS:

AutoQoS generates commands for the port and adds the generated commands to the running configuration. The generated QoS commands are applied as if you were entering them from the CLI. An existing configuration might cause the application of the generated commands to fail or an existing configuration might be overridden by the generated commands. These actions occur without warning. If the generated commands are successfully applied, any configuration that was not overridden remains in the running configuration. Any commands that were overridden might still exist in the startup-config file. Some of the generated commands are the type of PFC QoS commands that are applied to all ports controlled by a port ASIC. When one of these commands is applied, PFC QoS displays the messages caused by application of the command to all the ports controlled by the port ASIC. Depending on the module, these commands are applied to as many as 48 ports. See the Number of port groups and Port ranges per port group listed for each module in the Release Notes for Cisco IOS Release 12.2SX. You might not be able to configure support for Cisco IP phones and the other autoQoS options on ports that are controlled by the same port ASIC because of conflicting port trust state requirements. If application of the generated commands fails, the previous running configuration is restored. Enable autoQoS before you configure other QoS commands. If necessary, you can modify the QoS configuration after the autoQoS configuration completes. AutoQoS cannot attach a policy map to an interface if there is already a policy map attached. Do not modify a policy map or class map that includes AUTOQOS in its name. You cannot configure autoQoS on the following:
Port-channel interfaces
41-3
Chapter 41 Using AutoQoS
Using AutoQoS
VLAN interfaces (also known as switch virtual interfaces or SVIs) Tunnel interfaces Loopback interfaces Subinterfaces on any type of interface
Configuring AutoQoS
AutoQoS generates commands that are appropriate for the QoS port architecture of the port on which you enter an auto qos voip command. For each of the different auto qos voip commands, autoQoS generates different QoS commands for each of these QoS port architectures:

1p1q0t/1p3q1t 1p1q4t/1p2q2t 1p1q4t/1p3q8t 1p1q8t/1p2q1t 1q2t/1p2q2t 1q2t/1p3q8t 1q4t/2q2t 1q8t/1p3q8t 1q8t/1p7q8t 2q8t/1p3q8t 8q4t/1p7q4t 8q8t/1p7q8t
The procedures in the following sections include the commands that you need to enter to display the generated commands, but the specific commands that autoQoS generates are not listed in this document. These sections describe how to configure autoQoS:

Configuring AutoQoS Support for a Cisco IP Phone, page 41-4 Configuring AutoQoS Support for Cisco IP Communicator, page 41-5 Configuring AutoQoS Support for Marked Traffic, page 41-6
Configuring AutoQoS Support for a Cisco IP Phone

Note
Complete the configuration procedures in the Configuring Cisco IP Phone Support section on page 15-7 before you configure autoQoS for a Cisco IP phone. To configure autoQoS for a Cisco IP phone, perform this task:
Command
Step 1 Step 2
1

slot/port
Selects the interface to configure.
41-4
OL-13013-06
Chapter 41
Command
Router(config-if)# auto qos voip cisco-phone Router(config-if)# end Router# show auto qos interface type1 slot/port Router# show running-config | include mls qos map cos-dscp Router# show running-config interface type1 slot/port 1. type = fastethernet or gigabitethernet
Purpose Configures autoQoS for a Cisco IP phone. Returns to privileged EXEC mode. Displays the configured autoQoS commands. Displays the generated received CoS to internal DSCP map. Displays all of the commands configured on the interface.
When configuring autoQoS for a Cisco IP phone, note the following information:
To disable autoQoS on an interface, use the no auto qos voip interface configuration command.
Note
The no auto qos voip interface configuration command does not disable QoS globally or delete the received CoS to internal DSCP map created by autoQoS.
You might see messages that instruct you to configure other ports to trust CoS. You must do so to enable the autoQoS generated commands.
This example shows how to enable autoQoS on Fast Ethernet interface 1/1:
Router(config)# interface fastethernet 1/1 Router(config-if)# auto qos voip cisco-phone
Configuring AutoQoS Support for Cisco IP Communicator

To configure autoQoS for Cisco IP Communicator, perform this task: Command
1

slot/port
Selects the interface to configure. Configures autoQoS for Cisco IP Communicator. Returns to privileged EXEC mode. Displays the configured autoQoS commands. Displays the policy map and policers created by autoQoS. Displays the class maps created by autoQoS. Displays the DSCP markdown maps created by autoQoS. Displays all of the commands configured on the interface.
Router(config-if)# auto qos voip cisco-softphone Router(config-if)# end Router# show auto qos interface type
1
slot/port
Router# show policy-map AUTOQOS-CISCO-SOFT-PHONE
Router# show class-map AUTOQOS-CISCO-SOFTPHONE-SIGNAL Router# show class-map AUTOQOS-CISCO-SOFTPHONE-DATA Router# show running-config | include mls qos map policed-dscp Router# show running-config interface type1 slot/port
1.
41-5
Using AutoQoS
When configuring autoQoS for Cisco IP Communicator, note the following information:
Note
The no auto qos voip interface configuration command does not disable QoS globally or delete the policy, class, and DSCP markdown maps created by autoQoS.
You cannot configure support for Cisco IP Communicator on ports that are configured with the switchport keyword. PFC QoS supports 1023 aggregate policers and each use of the auto qos voip cisco-softphone command on a port uses two aggregate policers.
Router(config)# interface fastethernet 1/1 Router(config-if)# auto qos voip cisco-softphone
Configuring AutoQoS Support for Marked Traffic

To configure autoQoS for marked traffic, perform this task: Command
Router# configure terminal Router(config)# interface type1 slot/port Router(config-if)# auto qos voip trust Router(config-if)# end Router# show auto qos interface type
1
Purpose Enters global configuration mode. Selects the interface to configure. Configures autoQoS for marked traffic. Returns to privileged EXEC mode.
slot/port
Displays the configured autoQoS commands. For ports configured with the switchport command, displays the generated received CoS to internal DSCP map. Displays all of the commands configured on the interface.
Router# show running-config | include mls qos map cos-dscp
Step 7
Router# show running-config interface type1 slot/port
1.
When configuring autoQoS to trust marked traffic, note the following information:
Note
The no auto qos voip interface configuration command does not disable QoS globally or delete the received CoS to internal DSCP map created by autoQoS.
For ports configured with the switchport command, you might see messages that instruct you to configure other ports to trust CoS. You must do so to enable the autoQoS generated commands.
Router(config)# interface fastethernet 1/1 Router(config-if)# auto qos voip trust
41-6
OL-13013-06
Chapter 41
Tip
41-7
Using AutoQoS
41-8
OL-13013-06
C H A P T E R
42
Configuring MPLS QoS

This chapter describes how to configure Multiprotocol Label Switching (MPLS) quality of service (QoS) in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html MPLS QoS extends to MPLS traffic the PFC QoS features described in Chapter 40, Configuring PFC QoS. This chapter provides supplemental information on MPLS QoS features. Be sure that you understand the PFC QoS features before you read this chapter. All policing and marking available for 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
Tip

Terminology, page 42-2 MPLS QoS Features, page 42-3 MPLS QoS Overview, page 42-4 MPLS QoS, page 42-5 Understanding MPLS QoS, page 42-7 MPLS QoS Default Configuration, page 42-15 MPLS QoS Commands, page 42-16
42-1
Chapter 42 Terminology
MPLS QoS Restrictions and Guidelines, page 42-17 Configuring MPLS QoS, page 42-17 MPLS DiffServ Tunneling Modes, page 42-30 Configuring Short Pipe Mode, page 42-34 Configuring Uniform Mode, page 42-39
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. 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.
42-2
OL-13013-06
Chapter 42
Configuring MPLS QoS MPLS QoS Features
Policing is limiting bandwidth used by a flow of traffic. Policing can mark or drop traffic.
MPLS QoS Features

QoS enables a network to provide improved service to selected network traffic. This section explains the following MPLS QoS features, which are supported in an MPLS network:

MPLS Experimental Field, page 42-3 Trust, page 42-3 Classification, page 42-3 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 an MPLS QoS policy.
Trust
For received Layer 3 MPLS packets, the PFC 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 PFC 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.
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 PFC makes 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.
42-3
Chapter 42 MPLS QoS Overview
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 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-22 for information.
Preserving IP ToS
The PFC 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:

LAN port subinterfaces Layer 3 VLAN interfaces Layer 3 LAN ports Layer 2 LAN ports (ports configured with the switchport command) FlexWAN ports or subinterfaces
You cannot attach EXP mutation maps to these interface types:

For configuration information, see theConfiguring MPLS QoS Egress EXP Mutation section on page 42-28.
MPLS DiffServ Tunneling Modes

The PFC 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-30 for information.
MPLS QoS Overview

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.
42-4
OL-13013-06
Chapter 42
Configuring MPLS QoS MPLS QoS
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-30.
MPLS QoS
This section describes how 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 PE2service provider egress LER CE2Customer equipment 2
Note
PE1 and PE2 are at the boundaries between the MPLS network and the IP network.
41867
42-5
Chapter 42 MPLS QoS
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-6 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 or a port adapter on a FlexWAN or Enhanced FlexWAN module. This section is for LAN ports. 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 PFC 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 PFC 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 PFC forwards the labeled packets to the appropriate output interface for processing. The PFC 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.
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.
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 PFC receives the traffic from the input interface and uses the EXP bits to perform classification, marking, and policing. The PFC3 performs a table lookup to determine the next-hop LSR.
42-6
OL-13013-06
Chapter 42
Configuring MPLS QoS Understanding MPLS QoS
4. 5. 6. 7. 8.
An appropriate label is placed (swapped) into the packet and the MPLS EXP bits are copied into the label header. The PFC forwards the labeled packets to the appropriate output interface for processing. The PFC 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 PFC 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 PFC performs a lookup on the IP address to determine the packets destination; the PFC 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 PFC 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.
Understanding MPLS QoS

MPLS QoS supports IP QoS. For MPLS packets, the EXP value is mapped into an internal DSCP so that the PFC can apply non-MPLS QoS marking and policing. For both the ingress and egress policies, MPLS QoS marking and policing decisions are made on a per-interface basis at an ingress PFC. 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.
42-7
Chapter 42 Understanding MPLS QoS
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 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 see QoS features for LAN ports and FlexWAN ports. For details about how the different features work, see 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.
Ethernet to MPLS
For Ethernet to MPLS, the ingress interface, 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 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, 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).
42-8
OL-13013-06
Chapter 42
For more information, see these sections:

Classification for MPLS-to-IP, page 42-11 Classification for MPLS-to-IP MPLS QoS, page 42-11 Classification at MPLS-to-IP Ingress Port, page 42-11 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 PFC 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 PFC 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 PFC 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. After the PFC applies the port trust and QoS policies, it assigns the internal DSCP. The PFC 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 PFC preserves the original IP ToS when the MPLS labels are imposed. The PFC 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.
42-9
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 PFC 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 PFC will map the internal DSCP to the imposed EXP value. A PFC 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 PFC will map the internal DSCP to the imposed EXP value.
Classification for IP-to-MPLS Mode MPLS QoS

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
MPLS QoS at the egress of PE1 supports the match 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. 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. 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 copy the egress CoS into the egress 802.1Q field.
MPLS to IP
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.
42-10
OL-13013-06
Chapter 42
Classification for MPLS-to-IP

The PFC assigns the internal DSCP (internal priority that the PFC 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 PFC classifies the packet based on MPLS EXP ingress or egress policy. The PFC 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 PFC 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 PFC 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 31-4. For incoming MPLS packets on the PE-to-CE ingress, the PFC 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.
Classification for MPLS-to-IP MPLS QoS

MPLS QoS at the ingress to PE2 supports matching on the EXP value and the police command. 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. 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.
42-11
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 FlexWAN interfaces classify traffic on information in the transmitted IP header. If the egress port is a trunk, the LAN 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 PFC. 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.
Note
For information on recirculation, see the Recirculation section on page 31-4. The PFC 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)
42-12
OL-13013-06
Chapter 42
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 PFC 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
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 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 PFC ignores the port trust state, the ingress CoS, and any policy-map trust commands. Instead, the PFC trusts the EXP value in the topmost label.
Note
The 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. MPLS QoS maps the EXP value to the internal DSCP using the EXP-to-DSCP global map. What the PFC does next depends on whether it is swapping labels, imposing a new label, or popping a label:
Swapping labelsWhen swapping labels, the PFC preserves the EXP value in the received topmost label and copies it to the EXP value in the outgoing topmost label. The PFC 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 PFC 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 PFC is performing a markdown, it uses the internal DSCP as an index into the internal DSCP markdown map. The PFC maps the result of the internal DSCP markdown to an EXP value using the internal DSCP-to-EXP global map. The PFC 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 PFC 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.
42-13
Imposing an additional labelWhen imposing a new label onto an existing label stack, the PFC 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 PFC 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 PFC can mark in-profile and mark down out-of-profile traffic. After it marks the internal DSCP, the PFC uses the internal DSCP-to-EXP global map to map the internal DSCP to the EXP value in the newly imposed label. The PFC then copies the EXP in the imposed label to the underlying swapped label. The PFC 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 PFC preserves the EXP value in the exposed label. The PFC 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 PFC maps the internal DSCP to the EXP value in the exposed label using the DSCP-to-EXP global map. The PFC 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 MPLS QoS

MPLS QoS at the ingress to P1 or P2 supports the following:

Matching with the match mpls experimental topmost command The set mpls experimental imposition, police, and police with set imposition commands
MPLS QoS at the egress of P1 or P2 supports matching with the match mpls experimental topmost command.
Classification at MPLS-to-MPLS Ingress Port

LAN port classification is based on the egress CoS from the PFC. 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 PFC. 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 copy the egress CoS into the egress 802.1Q field.
42-14
OL-13013-06
Chapter 42
Configuring MPLS QoS MPLS QoS Default Configuration
MPLS QoS Default Configuration

This section describes the MPLS QoS default configuration. The following global 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.
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
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
42-15
Chapter 42 MPLS QoS Commands
Feature Marked-down DSCP from DSCP map EXP mutation map Policers Policy maps MPLS flow mask in NetFlow table MPLS core QoS
Default Value 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:

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

MPLS QoS supports the following MPLS QoS commands:

match mpls experimental topmost set mpls experimental imposition 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 40-56.
42-16
OL-13013-06
Chapter 42
Configuring MPLS QoS MPLS QoS Restrictions and Guidelines
The following commands are not supported:

set qos-group set discard-class
MPLS QoS Restrictions and Guidelines

When configuring 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. 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 PFC to assign the correct EXP value for the labels that it imposes. 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 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
42-17
Chapter 42 Configuring MPLS QoS
Configuring a Policy Map, page 42-22 Displaying a Policy Map, page 42-27 Configuring MPLS QoS Egress EXP Mutation, page 42-28 Configuring EXP Value Maps, page 42-29
Enabling QoS Globally

Before you can configure QoS on the PFC, 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 PFC 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
Router(config)# end Router# show mls qos
This example shows how to enable QoS globally:

Router(config)# mls qos Router(config)# end Router#

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
42-18
OL-13013-06
Chapter 42
Configuring MPLS QoS Configuring MPLS QoS
Enabling Queueing-Only Mode

To enable queueing-only mode, perform this task: Command
Router(config)# mls qos queueing-only Router(config)# end Router# show mls qos
Purpose Enables queueing-only mode. Exits configuration mode. Verifies the configuration.
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#
Restrictions and Usage Guidelines

If QoS is disabled (no mls qos) for the PFC, 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.
42-19
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
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.
42-20
OL-13013-06
Chapter 42
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 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 3466140423 0 Int Mod Dir Class-map DSCP

The following restrictions and guidelines apply when classifying MPLS packets:
42-21
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. 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. Exits interface configuration mode. Verifies the configuration.
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. MPLS QoS does not attempt to apply commands from more than one policy map class to matched traffic.
42-22
OL-13013-06
Chapter 42
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.
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
42-23
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 Router# 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 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 Int Mod Dir 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.
42-24
OL-13013-06
Chapter 42
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. 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 PFC, 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 PFC hardware that provides the ability to rate limit a particular traffic class to a specific rate. The PFC 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 40-17. 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
Creates an ingress flow policer. (Not supported in egress policy.) Exits class-map configuration mode.
Step 6
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-25
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-26
OL-13013-06
Chapter 42

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 40-73. 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 PFC, 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 PFC does not mark in-profile traffic; when marking down out-of-profile traffic, the PFC marks the outgoing topmost label. The PFC 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 40-73. 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 PFC, 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 PFC 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 an MPLS QoS Policy Map Class Summary

To display an MPLS QoS policy map class summary, perform this task: Command
Router# show mls qos mpls [{interface interface_type interface_number} | {module slot}
Purpose Displays an MPLS QoS policy map class summary.
This example shows how to display an 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-27
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 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 MPLS QoS EXP mutation:

Configuring Named EXP Mutation Maps, page 42-29 Attaching a Named EXP Mutation Map to an Egress Interface, page 42-29
42-28
OL-13013-06
Chapter 42
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 map_name mutated_exp1 mutated_exp2 mutated_exp3 mutated_exp4 mutated_exp5 mutated_exp6 mutated_exp7 mutated_exp8 Router(config)# end Router# show mls qos maps
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 a Named EXP Mutation Map to an Egress Interface

To attach an EXP mutation map to an egress 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)# end Router# show running-config interface {{vlan vlan_ID} | {type slot/port} | {port-channel number}} 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Attaches an egress EXP mutation map to the interface. Exits configuration mode. Verifies the configuration.
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
Configuring EXP Value Maps

These sections describe how EXP values are mapped to other values:

Configuring the Ingress-EXP to Internal-DSCP Map, page 42-30 Configuring the Egress-DSCP to Egress-EXP Map, page 42-30
42-29
Chapter 42 MPLS DiffServ Tunneling Modes
Configuring the Ingress-EXP to Internal-DSCP Map

To configure the ingress-EXP to internal-DSCP map, perform this task: Command
Step 1
Router(config)# mls qos map exp-dscp 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. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to configure the 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 the Egress-DSCP to Egress-EXP Map

To configure the 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 the 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. Exits configuration mode. Verifies the configuration.
Step 2 Step 3
This example shows how to configure the egress-DSCP to egress-EXP map:

Router(config)# mls qos map dscp-exp 20 25 to 3 Router(config)#
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 PFC, there are two ways to forward packets through a network:
42-30
OL-13013-06
Chapter 42
Configuring MPLS QoS MPLS DiffServ Tunneling Modes
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-31. For the configuration information, see the Configuring Short Pipe Mode section on page 42-34. 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-32. For the configuration procedure, see the Configuring Uniform Mode section on page 42-39.
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/12_2t/12_2t13/feature/guide/ftdtmode.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-31
Chapter 42 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/12_2t/12_2t13/feature/guide/ftdtmode.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 propagation is performed by a router only when a PHB is added or exposed due to label imposition or
42-32
119121
OL-13013-06
Chapter 42
Configuring MPLS QoS MPLS DiffServ Tunneling Modes
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. 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.
4. 5.
The following is an example when there are IP precedence bit markings:

1. 2. 3.
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.
119209
IP dscp 3
MPLS exp 3
MPLS exp 0
IP dscp 0
42-33
Chapter 42 Configuring Short Pipe Mode
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-34 Configuring Ingress PE RouterP Facing Interface, page 42-35 Configuring the P RouterOutput Interface, page 42-37 Configuring the Egress PE RouterCustomer Facing Interface, page 42-38
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.
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 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).
42-34
OL-13013-06
Chapter 42
Configuring MPLS QoS Configuring Short Pipe Mode
For MPLS and VPN, the ingress PE supports all ingress PFC IP policies. For information about the classification for PFC IP policies based on IP ACL/DSCP/precedence, see Chapter 40, Configuring PFC QoS. To configure a policy map to set the MPLS EXP field in the imposed label entries, perform this task: Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7
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 PFC QoS globally. 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
Configuring Ingress PE RouterP Facing Interface

This procedure classifies packets based on their MPLS EXP field and provides appropriate discard and scheduling treatments.
42-35
Note
QoS features shown here are available only with 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 PFC QoS globally. 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 Router(config)# interface pos 4/1 Router(config-if)# service-policy output output-qos
42-36
OL-13013-06
Chapter 42
Configuring MPLS QoS Configuring Short Pipe Mode
Configuring the P RouterOutput Interface

Note
QoS features shown here are available only with 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 PFC QoS globally. 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
42-37
Configuring the Egress PE RouterCustomer Facing Interface

Note
QoS features shown here are available only with 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 PFC QoS globally. 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 Router(config)# interface GE-WAN 3/2.32 Router(config-if)# service-policy output output-qos
42-38
OL-13013-06
Chapter 42
Configuring MPLS QoS Configuring Uniform Mode
Configuring Uniform Mode

This section describes how to configure the following:

Configuring the Ingress PE RouterCustomer Facing Interface, page 42-39 Configuring the Ingress PE RouterP Facing Interface, page 42-40 Configuring the Egress PE RouterCustomer Facing Interface, page 42-41
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 PFC to copy the IP PHB into the MPLS PHB.
Note
This description applies to PFC QoS for LAN 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 PFC QoS globally. 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.
Router(config)# interface type slot/port Router(config-if)# mls qos trust dscp
Selects an interface to configure. 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
42-39
Chapter 42 Configuring Uniform Mode
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 PFC QoS globally. 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.
Note
42-40
OL-13013-06
Chapter 42
Configuring MPLS QoS Configuring Uniform Mode
Configuring the Egress PE RouterCustomer Facing Interface

To configure the egress PE router at the customer-facing interface, perform this task: Command
Purpose Enables PFC QoS globally. 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
Note
42-41
Chapter 42 Configuring Uniform Mode
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-42
OL-13013-06
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 in Cisco IOS Release 12.2SX.
Note
Tip

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
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 configured aggregate policers.
Note
The PFC QoS statistics data export feature is completely separate from NetFlow Data Export and does not interact with it.
43-1
Chapter 43 PFC QoS Statistics Data Export Default Configuration
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 Per class map policer PFC QoS data export PFC QoS data export time interval Export destination PFC QoS data export field delimiter
Default Value Disabled Disabled Disabled 300 seconds Not configured Pipe character ( | )
Per named aggregate policer PFC QoS data export Disabled

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-6 Configuring PFC QoS Statistics Data Export Destination Host and UDP Port, page 43-7 Setting the PFC QoS Statistics Data Export Field Delimiter, page 43-8
Enabling PFC QoS Statistics Data Export Globally

To enable PFC QoS statistics data export globally, perform this task: Command
Router(config)# mls qos statistics-export Router(config)# end Router# show mls qos statistics-export info
Purpose Enables PFC QoS statistics data export globally. Exits configuration mode. Verifies the configuration.
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
43-2
OL-13013-06
Chapter 43
Configuring PFC QoS Statistics Data Export Configuring PFC QoS Statistics Data Export
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
1
Purpose
slot/port
Selects the interface to configure. Enables PFC QoS statistics data export for the port. Exits configuration mode. Verifies the configuration.
Router(config-if)# mls qos statistics-export Router(config)# end Router# show mls qos statistics-export info 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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 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
43-3
Chapter 43 Configuring PFC QoS Statistics Data Export
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
Router(config)# mls qos statistics-export aggregate-policer aggregate_policer_name Router(config)# end Router# show mls qos statistics-export info
Purpose Enables PFC QoS statistics data export for a named aggregate policer. Exits configuration mode. Verifies the configuration.
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) 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
43-4
OL-13013-06
Chapter 43
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
Router(config)# mls qos statistics-export class-map classmap_name Router(config)# end Router# show mls qos statistics-export info
Purpose Enables PFC QoS statistics data export for a class map. Exits configuration mode. Verifies the configuration.
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) 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
43-5
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
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.
Step 2 Step 3
Router(config)# end Router# show mls qos statistics-export info
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
43-6
OL-13013-06
Chapter 43
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#
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
Router(config)# end Router# show mls qos statistics-export info
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.
43-7
Table 43-3
Supported PFC QoS Data Export Severity Parameter Values
Severity Parameter Name emerg alert crit err notice info debug Number Definition 0 1 2 3 5 6 7 system is unusable action must be taken immediately critical conditions error conditions warning conditions normal but significant condition informational debug-level messages
warning 4
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
Router(config)# mls qos statistics-export delimiter delimiter_character Router(config)# end Router# show mls qos statistics-export info
Purpose Sets the PFC QoS statistics data export field delimiter. Exits configuration mode. Verifies the configuration.
43-8
OL-13013-06
Chapter 43
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 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-9
43-10
OL-13013-06
PA R T
Security
C H A P T E R
44
Configuring Network Security

This chapter contains network security information unique to Cisco IOS Release 12.2SX, 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
Tip

Configuring MAC Address-Based Traffic Blocking, page 44-2 Configuring TCP Intercept, page 44-2 Configuring Unicast Reverse Path Forwarding Check, page 44-2
44-1
Chapter 44 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, see 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 unicast reverse path forwarding check (unicast RPF check):

Understanding PFC3 Unicast RPF Check Support, page 44-2 Unicast RPF Check Guidelines and Restrictions, page 44-3 Configuring Unicast RPF Check, page 44-4
Understanding PFC3 Unicast RPF Check Support

The unicast RPF check verifies that the source address of received IP packets is reachable. The unicast RPF check discards IP packets that lack a verifiable IP source prefix (route), which helps mitigate problems that are caused by traffic with malformed or forged (spoofed) IP source addresses. For unicast RPF check without ACL filtering, the PFC3 provides hardware support for the RPF check of traffic from multiple interfaces. For unicast RPF check with ACL filtering, the PFC determines whether or not traffic matches the ACL. The PFC sends the traffic denied by the RPF ACL to the route processor (RP) for the unicast RPF check. Packets permitted by the ACL are forwarded in hardware without a unicast RPF check.
44-2
OL-13013-06
Chapter 44
Configuring Network Security Configuring Unicast Reverse Path Forwarding Check
Unicast RPF Check Guidelines and Restrictions

These sections describe the unicast RPF check guidelines and restrictions:

General Unicast RPF Check Guidelines and Restrictions, page 44-3 Unicast RPF Check Configuration Guidelines and Restrictions, page 44-3
General Unicast RPF Check Guidelines and Restrictions

When configuring unicast RPF check, follow these guidelines and restrictions:

The PFC does not provide hardware support for the unicast RPF check for policy-based routing (PBR) traffic. (CSCea53554) Unicast RPF does not provide complete protection against spoofing. Spoofed packets can enter a network through unicast RPF-enabled interfaces if an appropriate return route to the source IP address exists. The switch applies the same unicast RPF mode to all interfaces where unicast RPF check is configured. Any change that you make in the unicast RPF mode on any interfaces is applied to all interfaces where the unicast RPF check is configured. The allow default options of the unicast RPF modes do not offer significant protection against spoofing.
Strict unicast RPF Check with Allow DefaultReceived IP traffic that is sourced from a prefix
that exists in the routing table passes the unicast RPF check if the prefix is reachable through the input interface. If a default route is configured, any IP packet with a source prefix that is not in the routing table passes the unicast RPF check if the ingress interface is a reverse path for the default route.
Loose unicast RPF Check with Allow DefaultIf a default route is configured, any IP packet
passes the unicast RPF check.
Avoid configurations that overload the route processor with unicast RPF checks.
Do not configure unicast RPF to filter with an ACL. Do not configure the global unicast RPF punt check mode.
Unicast RPF Check Configuration Guidelines and Restrictions

Although the software supports up to 16 reverse-path interfaces, implement these limits in your configuration:
Unicast RPF Strict ModeThe unicast RPF strict mode provides the greatest security against spoofed traffic. If, on all unicast RPF-check enabled interfaces, the switch receives valid IP traffic through interfaces that are reverse paths for the traffic, then strict mode is an option in these circumstances:
If, on a maximum of 24 interfaces, divided into four groups of six interfaces each, the switch
receives valid IP packets that have up to six reverse-path interfaces per source prefix, configure the unicast RPF strict mode with the mls ip cef rpf multipath interface-group command. This option requires you to identify the source prefixes and the interfaces that serve as reverse paths for the source prefixes and to configure interface groups for those reverse path interfaces. All of the reverse-path interfaces for each source prefix must be in the same interface group.
44-3
Chapter 44 Configuring Unicast Reverse Path Forwarding Check
You can configure four interface groups, with each group containing up to six reverse-path interfaces. There is no limit on the number of source prefixes that an interface group can support. To ensure that no more than six reverse-path interfaces exist in the routing table for each prefix, enter the maximum-paths 6 command in config-router mode when configuring OSPF, EIGRP, or BGP. IP traffic with one or two reverse-path interfaces that is received on uPPF-check enabled interfaces outside the interface groups passes the unicast RPF check if the ingress interface and at most one other interface are reverse paths. With maximum paths set to six, IP traffic with more than two reverse-path interfaces that is received on uPPF-check enabled interfaces outside the interface groups always pass the unicast RPF check.
If, on any number of interfaces, the switch receives valid IP packets that have one or two reverse
path interfaces per source prefix, configure the unicast RPF strict mode with the mls ip cef rpf multipath pass command. To ensure that no more than two reverse-path interfaces exist in the routing table for each prefix, enter the maximum-paths 2 command in config-router mode when configuring OSPF, EIGRP, or BGP.
Unicast RPF Loose Mode with the Pass Global ModeThe unicast RPF loose mode provides less protection than strict mode, but it is an option on switches that receive valid IP traffic on interfaces that are not reverse paths for the traffic. The unicast RPF loose mode verifies that received traffic is sourced from a prefix that exists in the routing table, regardless of the interface on which the traffic arrives.
Configuring Unicast RPF Check

These sections describe how to configure unicast RPF check:

Configuring the Unicast RPF Check Mode, page 44-4 Configuring the Multiple-Path Unicast RPF Check Mode, page 44-6 Enabling Self-Pinging, page 44-7
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. 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.
44-4
OL-13013-06
Chapter 44
To configure unicast RPF check mode, perform this task: Command

Step 1
Router(config)# interface {{vlan vlan_ID} | {type1 slot/port} | {port-channel number}}

Note
Based on the input port, unicast RPF check verifies the best return path before forwarding the packet on to the next destination.
Router(config-if)# ip verify unicast source reachable-via {rx | any} [allow-default] [list] Router(config-if)# exit Router# show mls cef ip rpf 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Configures the unicast RPF check mode. Exits interface configuration mode. Verifies the configuration.
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#

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
44-5
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

To configure the multiple-path unicast RPF check mode, perform this task: Command
Router(config)# mls ip cef rpf mpath {punt | pass | interface-group} Router(config)# end Router# show mls cef ip rpf
Purpose Configures the multiple path RPF check mode. Exits configuration mode. Verifies the configuration.
When configuring multiple path RPF check, note the following information:
punt mode (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 RP for unicast RPF check in software. pass modeThe 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 modeThe 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 punt as the multiple path RPF check mode:
Router(config)# mls ip cef rpf mpath punt
Configuring Multiple-Path Interface Groups

To configure multiple-path unicast RPF interface groups, 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
Purpose Configures a multiple path RPF interface group.
Step 2
Removes an interface group.
44-6
OL-13013-06
Chapter 44
Command
Step 3 Step 4
Router(config)# end Router# show mls cef ip rpf
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
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)# exit 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Selects the interface to configure. Enables the switch to ping itself or a secondary address. Exits interface configuration mode.
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
44-7
44-8
OL-13013-06
C H A P T E R
45
Using AutoSecure
This chapter describes how to use the AutoSecure function. Release 12.2(33)SXH and later releases support the AutoSecure function.
Note
Tip

Understanding AutoSecure, page 45-1 Configuring AutoSecure, page 45-6 AutoSecure Configuration Example, page 45-9
Understanding AutoSecure
You can easily secure the switch without understanding all the security capabilities of the switch by using the AutoSecure feature. AutoSecure is a simple security configuration process that disables nonessential system services and enables a basic set of recommended security policies to ensure secure networking services.
Caution
Although AutoSecure helps to secure a switch, it does not guarantee the complete security of the switch. The following sections describe how AutoSecure works:

Benefits of AutoSecure, page 45-2 Securing the Management Plane, page 45-2
45-1
Chapter 45 Understanding AutoSecure
Using AutoSecure
Securing the Forwarding Plane, page 45-5 AutoSecure Guidelines and Restrictions, page 45-6
Benefits of AutoSecure
AutoSecure provides a variety of mechanisms to enhance security of the switch.
Simplified Switch Security Configuration

AutoSecure automates a thorough configuration of security features of the switch. AutoSecure disables certain features that are enabled by default that could be exploited for security holes. You can execute AutoSecure in either of two modes, depending on your individual needs:

Interactive modePrompts with options to enable and disable services and other security features, suggesting a default setting for each option. Noninteractive modeAutomatically executes the recommended Cisco default settings.
Enhanced Password Security

AutoSecure provides the following mechanisms to improve the security of access to the switch:
You can specify a required minimum password length, which can eliminate weak passwords that are prevalent on most networks, such as lab and cisco. To configure a minimum password length, use the security passwords min-length command. You can cause a syslog message to be generated after the number of unsuccessful login attempts exceeds the configured threshold. To configure the number of allowable unsuccessful login attempts (the threshold rate), use the security authentication failure rate command.
System Logging Message Support

System logging messages capture any subsequent changes to the AutoSecure configuration that are applied on the running configuration. As a result, a more detailed audit trail is provided when AutoSecure is executed.
Securing the Management Plane

AutoSecure provides protection for the switch management interfaces (the management plane) and the data routing and switching functions (the forwarding plane, described in the Securing the Forwarding Plane section on page 45-5.) Securing the management plane is done by turning off certain global and interface services that can be potentially exploited for security attacks and turning on global services that help minimize the threat of attacks. Secure access and secure logging are also configured for the switch.
Caution
If your device is managed by a network management (NM) application, securing the management plane could turn off some services such as the HTTP server and disrupt the NM application support.
45-2
OL-13013-06
Chapter 45
Using AutoSecure Understanding AutoSecure
The following sections define how AutoSecure helps to secure the management plane:

Disables Global Services, page 45-3 Disables Per-Interface Services, page 45-3 Enables Global Services, page 45-4 Secures Access to the Switch, page 45-4 Enhances Logging for Security, page 45-5
Disables Global Services

AutoSecure will disable the following global services on the switch without prompting the user:

FingerCollects information about the system (reconnaissance) before an attack. PADEnables all packet assembler and disassembler (PAD) commands and connections between PAD devices and access servers. Small serversCauses TCP and User Datagram Protocol (UDP) diagnostic port attacks: a sender transmits a volume of fake requests for UDP diagnostic services on the switch, consuming all CPU resources. Bootp serverBootp is an insecure protocol that can be exploited for an attack. HTTP serverWithout secure-HTTP or authentication embedded in the HTTP server with an associated ACL, the HTTP server is insecure and can be exploited for an attack. (If you must enable the HTTP server, you will be prompted for the proper authentication or access list.)
Note
If you are using Security Device Manager (SDM), you must manually enable the HTTP server using the ip http server command. Identification serviceAn unsecure protocol (defined in RFC 1413) that allows an external host to query a TCP port for identification. An attacker can access private information about the user from the ID server. CDPIf a large number of Cisco Discovery Protocol (CDP) packets are sent to the switch, the available memory of the switch can be consumed, which causes the switch to crash.
Note
NM applications that use CDP to discover network topology will not be able to perform discovery. NTPWithout authentication or access control, Network Time Protocol (NTP) is insecure and can be used by an attacker to send NTP packets to crash or overload the switch. If you require NTP, you must configure NTP authentication using Message Digest 5 (MD5) and the ntp access-group command. If NTP is enabled globally, disable it on all interfaces on which it is not needed.
Source routingSource routing is provided only for debugging purposes, and should be disabled in all other cases. Otherwise, packets may avoid some of the access control mechanisms of the switch.
Disables Per-Interface Services

AutoSecure will disable the following per-interface services on the switch without prompting the user:
45-3
Chapter 45 Understanding AutoSecure
Using AutoSecure
ICMP redirectsDisabled on all interfaces. Does not add a useful functionality to a correctly configured network, but could be used by attackers to exploit security holes. ICMP unreachablesDisabled on all interfaces. Internet Control Management Protocol (ICMP) unreachables are a known method for some ICMP-based denial of service (DoS) attacks. ICMP mask reply messagesDisabled on all interfaces. ICMP mask reply messages can give an attacker the subnet mask for a particular subnetwork in the internetwork. Proxy-arpDisabled on all interfaces. Proxy-arp requests are a known method for DoS attacks because the available bandwidth and resources of the switch can be consumed in an attempt to respond to the repeated requests sent by an attacker. Directed broadcastDisabled on all interfaces. Potential cause of SMURF attacks for DoS. Maintenance Operations Protocol (MOP) serviceDisabled on all interfaces.
Enables Global Services

AutoSecure will enable the following global services on the switch without prompting the user:

The service password-encryption commandPrevents passwords from being visible in the configuration. The service tcp-keepalives-in and service tcp-keepalives-out commandsEnsures that abnormally terminated TCP sessions are removed.
Secures Access to the Switch

Caution
If your device is managed by an NM application, securing access to the switch could turn off vital services and may disrupt the NM application support. AutoSecure will make the following options available for securing access to the switch:
If a text banner does not exist, you will be prompted to add a banner. This feature provides the following sample banner:
Authorized access only This system is the property of ABC Enterprise Disconnect IMMEDIATELY if you are not an authorized user! Contact abc@example.com +1 408 5551212 for help.
The login and password (preferably a secret password, if supported) are configured on the console, AUX, vty, and tty lines. The transport input and transport output commands are also configured on all of these lines. (Telnet and secure shell (SSH) are the only valid transport methods.) The exec-timeout command is configured on the console and AUX as 10. When the image on the device is a crypto image, AutoSecure enables SSH and secure copy (SCP) for access and file transfer to and from the switch. The timeout seconds and authentication-retries integer options for the ip ssh command are configured to a minimum number. (Telnet and FTP are not affected by this operation and remain operational.) If the user specifies that the switch does not use Simple Network Management Protocol (SNMP), one of the following functionalities will occur:
In interactive mode, the user is asked whether to disable SNMP regardless of the values of the
community strings, which act like passwords to regulate access to the agent on the switch.
In noninteractive mode, SNMP will be disabled if the community string is public or private.
45-4
OL-13013-06
Chapter 45
Using AutoSecure Understanding AutoSecure
Note
After AutoSecure has been enabled, tools that use SNMP to monitor or configure a device will be unable to communicate with the device using SNMP. If authentication, authorization, and accounting (AAA) is not configured, AutoSecure configures local AAA. AutoSecure will prompt the user to configure a local username and password on the switch.
Enhances Logging for Security

AutoSecure provides the following logging options, which allow you to identify and respond to security incidents:

Sequence numbers and time stamps for all debug and log messages. This option is useful when auditing logging messages. Logging messages for login-related events. For example, the message Blocking Period when Login Attack Detected will be displayed when a login attack is detected and the switch enters quiet mode. (Quiet mode means that the switch will not allow any login attempts using Telnet, HTTP, or SSH.) The logging console critical command, which sends system logging (syslog) messages to all available TTY lines and limits messages based on severity. The logging buffered command, which copies logging messages to an internal buffer and limits messages logged to the buffer based on severity. The logging trap debugging command, which allows all commands with a severity higher than debugging to be sent to the logging server.
Securing the Forwarding Plane

To minimize the risk of attacks on the switch forwarding plane, AutoSecure provides the following functions:
Cisco Express Forwarding (CEF)AutoSecure enables CEF or distributed CEF (dCEF) on the switch whenever possible. Because there is no need to build cache entries when traffic starts arriving for new destinations, CEF operates more predictably than other modes when presented with large volumes of traffic addressed to many destinations. Switches configured for CEF perform better under SYN attacks than switches using the traditional cache.
Note
CEF consumes more memory than a traditional cache. If strict Unicast Reverse Path Forwarding (uRPF) is available, it can be configured on the switch to help mitigate problems that are caused by the introduction of forged (spoofed) IP source addresses. uRPF discards IP packets that lack a verifiable IP source address. Hardware rate limitingAutoSecure will enable hardware rate-limiting of the following types of traffic without prompting the user:
IP errors RPF failures ICMP no-route messages ICMP acl-drop messages
45-5
Chapter 45 Configuring AutoSecure
Using AutoSecure
IPv4 multicast FIB miss messages IPv4 multicast partially switch flow messages
AutoSecure will provide the option for hardware rate-limiting of the following types of traffic:
ICMP redirects TTL failures MTU failures IP unicast options IP multicast options Ingress and egress ACL bridged packets
Note
Rate-limiting of ingress and egress ACL bridged packets can interfere with ACL logging and can increase session setup rates for hardware accelerated features such as NAT, Layer 3 WCCP, and TCP intercept.
AutoSecure Guidelines and Restrictions

When configuring AutoSecure, follow these guidelines and restrictions:

Because there is no command to undo configuration changes made by AutoSecure, always save your running configuration before configuring AutoSecure. The AutoSecure configuration can be configured at run time or setup time. If any related configuration is modified after AutoSecure has been enabled, the AutoSecure configuration may not be fully effective. After AutoSecure has been enabled, tools that use SNMP to monitor or configure a device will be unable to communicate with the device using SNMP. If your device is managed by a network management (NM) application, securing the management plane could turn off some services such as HTTP server and disrupt the NM application support. If you are using Security Device Manager (SDM), you must manually enable the HTTP server using the ip http server command. NM applications that use CDP to discover network topology will not be able to perform discovery.
Configuring AutoSecure
These sections describe how to configure AutoSecure:

Using the AutoSecure Command, page 45-7 Configuring Additional Security, page 45-8 Verifying AutoSecure, page 45-8
45-6
OL-13013-06
Chapter 45
Using AutoSecure Configuring AutoSecure
Using the AutoSecure Command

The auto secure command guides you through a semi-interactive session (also known as the AutoSecure session) to secure the management and forwarding planes. You can use this command to secure just the management plane or the forwarding plane; if neither option is selected in the command line, you can choose to configure one or both planes during the session. This command also allows you to go through all noninteractive configuration portions of the session before the interactive portions. The noninteractive portions of the session can be enabled by selecting the optional no-interact keyword. The AutoSecure session will request the following information from you:

Is the device going to be connected to the Internet? How many interfaces are connected to the Internet? What are the names of the interfaces connected to the Internet? What will be your local username and password? What will be the switch hostname and domain name?
At any prompt you may enter a question mark (?) for help or Ctrl-C to abort the session. In interactive mode, you will be asked at the end of the session whether to commit the generated configuration to the running configuration of the switch. In noninteractive mode, the changes will be automatically applied to the running configuration.
Note
There is no undo command for configuration changes made by AutoSecure. You should always save the running configuration before executing the auto secure command. To execute the AutoSecure configuration process, beginning in privileged EXEC mode, perform this task:
Command
Router# auto secure [management | forwarding] [no-interact | full]
Purpose Executes the AutoSecure session for configuring one or both planes of the switch.

managementOnly the management plane will be secured. forwardingOnly the forwarding plane will be secured. no-interactThe user will not be prompted for any interactive configurations. fullThe user will be prompted for all interactive questions. This is the default.
For an example of the AutoSecure session, see the AutoSecure Configuration Example section on page 45-9.
45-7
Chapter 45 Configuring AutoSecure
Using AutoSecure
Configuring Additional Security

After completing the AutoSecure configuration, you can further enhance the security of management access to your switch by performing this task: Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# security passwords min-length length
Purpose Enters global configuration mode. Ensures that all configured passwords are at least a specified length.
lengthMinimum length of a configured password. The range is 0 to 16 characters.
Step 3
Router(config)# enable password {password | [encryption-type] password}
Sets a local password to control access to various privilege levels.
encryption-typeA value of 0 indicates that an unencrypted password follows. A value of 7 indicates that a hidden password follows. You usually will not enter an encryption type unless you enter a password that has already been encrypted by a Cisco router or switch.
Note
Step 4
Router(config)# security authentication failure rate threshold-rate log
Configures the number of allowable unsuccessful login attempts.

threshold-rateNumber of allowable unsuccessful login attempts. The range is 1 to 1024. logSyslog authentication failures if the number of failures in one minute exceeds the threshold.
The following example shows how to configure the switch for a minimum password length of 10 characters and a threshold of 3 password failures in one minute. The example also shows how to set a hidden local password.
Router# configure terminal Router(config)# security passwords min-length 10 Router(config)# security authentication failure rate 3 Router(config)# enable password 7 elephant123
Verifying AutoSecure
To verify that the AutoSecure feature has executed successfully, perform this task: Command
Router# show auto secure config
Purpose Displays all configuration commands that have been added as part of the AutoSecure configuration. The output is the same as the configuration generated output
45-8
OL-13013-06
Chapter 45
Using AutoSecure AutoSecure Configuration Example
AutoSecure Configuration Example

The following example is a sample AutoSecure session. After you execute the auto secure command, the feature will automatically prompt you with a similar response unless you enable the no-interact keyword. (For information on which features are disabled and which features are enabled, see the Securing the Management Plane section on page 45-2 and the Securing the Forwarding Plane section on page 45-5.)
Router# auto secure --- AutoSecure Configuration --*** AutoSecure configuration enhances the security of the router, but it will not make it absolutely resistant to all security attacks *** AutoSecure will modify the configuration of your device. All the configuration changes will be shown. For a detailed explanation of how the configuration changes enhance security and any possible side effects, please refer to Cisco.com for AutoSecure documentation. At any prompt you may enter '?' for help. Use ctrl-c to abort this session at any prompt. If this device is being managed by a network management station, AutoSecure configuration may block network management traffic. Continue with AutoSecure? [no]: y Gathering information about the router for AutoSecure Is this router connected to internet? [no]: y Enter the number of interfaces facing the internet [1]: 1 Interface IP-Address OK? Method Status Protocol Vlan1 unassigned YES NVRAM administratively down down Vlan77 77.1.1.4 YES NVRAM down down GigabitEthernet6/1 unassigned YES NVRAM administratively down down GigabitEthernet6/2 21.30.30.1 YES NVRAM up up Loopback0 3.3.3.3 YES NVRAM up up Tunnel1 unassigned YES NVRAM up up Enter the interface name that is facing the internet: Vlan77 Securing Management plane services... Disabling service finger Disabling service pad Disabling udp & tcp small servers Enabling service password encryption Enabling service tcp-keepalives-in Enabling service tcp-keepalives-out Disabling the cdp protocol Disabling Disabling Disabling Disabling Disabling the bootp server the http server the finger service source routing gratuitous arp
Here is a sample Security Banner to be shown at every access to device. Modify it to suit your enterprise requirements. Authorized Access only
45-9
Chapter 45 AutoSecure Configuration Example
Using AutoSecure
This system is the property of <Name of Enterprise>. UNAUTHORIZED ACCESS TO THIS DEVICE IS PROHIBITED. You must have explicit permission to access this device. All activities performed on this device are logged. Any violations of access policy will result in disciplinary action. Enter the security banner {Put the banner between k and k, where k is any character}: k banner k Enter the new enable secret: Confirm the enable secret : Enable password is not configured or its length is less than minimum no. of charactersconfigured Enter the new enable password: Confirm the enable password: Configuration of local user database Enter the username: cisco Enter the password: Confirm the password: Configuring AAA local authentication Configuring Console, Aux and VTY lines for local authentication, exec-timeout, and transport Securing device against Login Attacks Configure the following parameters Blocking Period when Login Attack detected (in seconds): 5 Maximum Login failures with the device: 3 Maximum time period for crossing the failed login attempts (in seconds): ? % A decimal number between 1 and 32767. Maximum time period for crossing the failed login attempts (in seconds): 5 Configure SSH server? [yes]: no Configuring interface specific AutoSecure services Disabling mop on Ethernet interfaces Securing Forwarding plane services... Enabling unicast rpf on all interfaces connected to internet The following rate-limiters are enabled by default: mls rate-limit unicast ip errors 100 10 mls rate-limit unicast ip rpf-failure 100 10 mls rate-limit unicast ip icmp unreachable no-route 100 10 mls rate-limit unicast ip icmp unreachable acl-drop 100 10 mls rate-limit multicast ipv4 fib-miss 100000 100 mls rate-limit multicast ipv4 partial 100000 100 Would you like mls rate-limit mls rate-limit mls rate-limit mls rate-limit mls rate-limit to enable the following rate-limiters also? unicast ip icmp redirect 100 10 all ttl-failure 100 10 all mtu-failure 100 10 unicast ip options 100 10 multicast ipv4 ip-options 100 10
Enable the above rate-limiters also? [yes/no]: yes
45-10
OL-13013-06
Chapter 45
Using AutoSecure AutoSecure Configuration Example
Would you like to enable the rate-limiters for Ingress/EgressACL bridged packets also? NOTE: Enabling the ACL in/out rate-limiters can affect ACL logging and session setup rate for hardware accelerated features such as NAT, Layer 3 WCCP and TCP Intercept mls rate-limit unicast acl input 100 10 mls rate-limit unicast acl output 100 10 Enable the ACL in/out rate-limiters also? [yes/no]: no This is the configuration generated: no service finger no service pad no service udp-small-servers no service tcp-small-servers service password-encryption service tcp-keepalives-in service tcp-keepalives-out no cdp run no ip bootp server no ip http server no ip finger no ip source-route no ip gratuitous-arps no ip identd banner k banner k security passwords min-length 6 security authentication failure rate 10 log enable secret 5 $1$30kP$f.KDndYPz/Hv/.yTlJStN/ enable password 7 08204E4D0D48574446 username cisco password 7 08204E4D0D48574446 aaa new-model aaa authentication login local_auth local line console 0 login authentication local_auth exec-timeout 5 0 transport output telnet line vty 0 15 login authentication local_auth transport input telnet login block-for 5 attempts 3 within 5 service timestamps debug datetime msec localtime show-timezone service timestamps log datetime msec localtime show-timezone logging facility local2 logging trap debugging service sequence-numbers logging console critical logging buffered int Vlan1 no ip redirects no ip proxy-arp no ip unreachables no ip directed-broadcast no ip mask-reply no mop enabled int Vlan77 no ip redirects no ip proxy-arp no ip unreachables no ip directed-broadcast no ip mask-reply
45-11
Chapter 45 AutoSecure Configuration Example
Using AutoSecure
no mop enabled int GigabitEthernet6/1 no ip redirects no ip proxy-arp no ip unreachables no ip directed-broadcast no ip mask-reply no mop enabled int GigabitEthernet6/2 no ip redirects no ip proxy-arp no ip unreachables no ip directed-broadcast no ip mask-reply no mop enabled interface Vlan77 ip verify unicast source reachable-via rx mls rate-limit unicast ip icmp redirect 100 10 mls rate-limit all ttl-failure 100 10 mls rate-limit all mtu-failure 100 10 mls rate-limit unicast ip options 100 10 mls rate-limit multicast ipv4 ip-options 100 10 ! end
Apply this configuration to running-config? [yes]: yes Applying the config generated to running-config Router#
Tip
45-12
OL-13013-06
C H A P T E R
46
Understanding Cisco IOS ACL Support

This chapter describes Cisco IOS access control list (ACL) support in Cisco IOS Release 12.2SX:

ACL Support in Hardware and Software, page 46-1 Cisco IOS ACL Configuration Guidelines and Restrictions, page 46-3 Policy-Based ACLs, page 46-3 Configuring IPv6 Address Compression, page 46-6 Optimized ACL Logging, page 46-8 Guidelines and Restrictions for Using Layer 4 Operators in ACLs, page 46-10
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/sec_data_plane/configuration/guide/sec_accs_list_rmap_ps6017 _TSD_Products_Configuration_Guide_Chapter.html
Tip
ACL Support in Hardware and Software

ACLs can be processed in hardware by the Policy Feature Card (PFC), a Distributed Forwarding Card (DFC), or in software by the route processor (RP):

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.
46-1
Chapter 46 ACL Support in Hardware and Software
VLAN ACL (VACL) and port ACL (PACL) flows are processed in hardware. If a field that is specified in a VACL or PACL is not supported by hardware processing, then that field is ignored (for example, the log keyword in an ACL), or the whole configuration is rejected (for example, a VACL containing IPX ACL parameters). 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. Cisco IOS Release 12.2SX does 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 RP 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 RP. Extended name-based MAC address ACLs are supported in hardware. 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 section on page 46-8). 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. Hardware-supported counters for hardware-supported ACLs, displayed by the show tcam interface command (not supported in PFC3A mode). See this publication: http://www.cisco.com/en/US/docs/ios/interface/command/reference/ir_s6.html#show_tcam_interfa ce 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.
46-2
OL-13013-06
Chapter 46
Understanding Cisco IOS ACL Support Cisco IOS ACL Configuration Guidelines and Restrictions
Cisco IOS ACL Configuration Guidelines and Restrictions

The following guidelines and restrictions apply to Cisco IOS ACLs configured for use with any feature:

You can apply Cisco IOS ACLs directly to Layer 3 ports and to VLAN interfaces. You can apply VLAN ACLs and port ACLs to Layer 2 interfaces (see Chapter 48, Configuring Port ACLs and 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 route processor (RP). By default, the RP sends Internet Control Message Protocol (ICMP) unreachable messages when a packet is denied by an access group. With the ip unreachables command enabled (which is the default), the switch processor (SP) drops most of the denied packets in hardware and sends only a small number of packets to the RP to be dropped (10 packets per second, maximum), which generates ICMP-unreachable messages. To eliminate the load imposed on the RP 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 or a PACL. Use named ACLs (instead of numbered ACLs) because this causes less 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.
Policy-Based ACLs
Release 12.2(33)SXH and later releases support policy-based ACLs (PBACLs). The following sections describe PBACLs:

Understanding PBACLs, page 46-3 PBACL Guidelines and Restrictions, page 46-4 Configuring PBACL, page 46-4
Understanding PBACLs
PBACLs provide the capability to apply access control policies across object groups. An object group is a group of users or servers. You define an object group as a group of IP addresses or as a group of protocol ports. You then create access control entries (ACEs) that apply a policy (such as permit or deny) to the object group. For example, a policy-based ACE can permit a group of users to access a group of servers.
46-3
Chapter 46 Policy-Based ACLs
An ACE defined using a group name is equivalent to multiple ACEs (one applied to each entry in the object group). The system expands the PBACL ACE into multiple Cisco IOS ACEs (one ACE for each entry in the group) and populates the ACEs in the TCAM. Therefore, the PBACL feature reduces the number of entries you need to configure but does not reduce TCAM usage. If you make changes in group membership, or change the contents of an ACE that uses an access group, the system updates the ACEs in the TCAM. The following types of changes trigger the update:

Adding a member to a group Deleting a member from a group Modifying the policy statements in an ACE that uses an access group
You configure a PBACL using extended Cisco IOS ACL configuration commands. As with regular ACEs, you can associate the same access policy with one or more interfaces. When you configure an ACE, you can use an object group to define the source, the destination, or both.
PBACL Guidelines and Restrictions

When configuring PBACLs, note the following guidelines and restrictions:

PBACLs are supported on Layer 3 interfaces (such as routed interfaces and VLAN interfaces). The PBACL feature only supports IPv4 ACEs. The PBACL feature supports only Cisco IOS ACLs. It is not supported with any other features. The keywords reflexive and evaluate are not supported. The PBACL feature supports only named Cisco IOS ACLs. It does not support numbered ACLs. Feature interactions for policy-based ACLs are the same as for Cisco IOS ACLs.
Configuring PBACL
Configure PBACLs using the following tasks:

Configuring a PBACL IP Address Object Group, page 46-4 Configuring a PBACL Protocol Port Object Group, page 46-5 Configuring ACLs with PBACL Object Groups, page 46-5 Configuring PBACL on an Interface, page 46-6
Configuring a PBACL IP Address Object Group

To create or modify a PBACL IP address object group, perform this task:
Command
Step 1 Step 2
Router(config)# object-group ip address object_group_name Router(config-ipaddr-ogroup)# {ip_address mask} | {host {name | ip_address} }
Purpose Defines object group name and enters IP-address object-group configuration mode. Configures a member of the group. The member is either a network address plus mask or a host (identified by host name or IP address).
46-4
OL-13013-06
Chapter 46
Understanding Cisco IOS ACL Support Policy-Based ACLs
Command
Step 3
Router(config-ipaddr-ogroup)# {end} | {exit}
Purpose To leave the configuration mode, enter the end command. To leave the IP-address object-group configuration mode, enter the exit command.
Step 4
Router# show object-group [object_group_name]
Displays the object-group configuration for the named group (or for all groups if no name is entered).
The following example creates an object group with three hosts and a network address:
Router(config)# object-group ip address myAG Router(config-ipaddr-pgroup)# host 10.20.20.1 Router(config-ipaddr-pgroup)# host 10.20.20.5 Router(config-ipaddr-pgroup)# 10.30.0.0 255.255.0.0
Configuring a PBACL Protocol Port Object Group

To create or modify a PBACL protocol port object group, perform this task: Command
Step 1 Step 2
Router(config)# object-group ip port object_group_name Router(config-port-ogroup)# {eq number} | {gt number} | {lt number} | {neq number} | {range number number}
Purpose Defines object group name and enters port object-group configuration mode. Configures a member of the group. The member is either equal to or not equal to a port number, less than or greater than a port number, or a range of port numbers. To leave the configuration mode, enter the end command. To leave the port object-group configuration mode, enter the exit command.
Step 3
Router(config-port-ogroup)# end | exit
Step 4
Router# show object-group [object_group_name]
Displays the object-group configuration for the named group (or for all groups if no name is entered).
The following example creates a port object group that matches protocol port 100 and any port greater than 200, except 300:
Router(config)# object-group ip port myPG Router(config-port-pgroup)# eq 100 Router(config-port-pgroup)# gt 200 Router(config-port-pgroup)# neq 300
Configuring ACLs with PBACL Object Groups

To configure an ACL to use a PBACL object group, perform this task:
46-5
Chapter 46 Configuring IPv6 Address Compression
Command
Step 1 Step 2
Router(config)# ip access-list extended acl_name
Purpose Defines an extended ACL with the specified name and enters extended-ACL configuration mode. Configures an ACE for TCP traffic using IP address object group as the source policy and an object group as the destination policy. Exits extended ACL configuration mode. Displays the object-group configuration for the named group (or for all groups if no name is entered).
Router(config-ext-nacl)# permit tcp addrgroup object_group_name addrgroup object_group_name
Step 3 Step 4
Router(config-ext-nacl)# exit Router# show access-lists [acl_name]
The following example creates an access list that permits packets from the users in myAG if the protocol ports match the ports specified in myPG:
Router(config)# ip access-list extended my-pbacl-policy Router(config-ext-nacl)# permit tcp addrgroup myAG portgroup myPG any Router(config-ext-nacl)# deny tcp any any Router(config-ext-nacl)# exit Router(config)# exit Router# show ip access-list my-pbacl-policy Extended IP access list my-pbacl-policy 10 permit tcp addrgroup AG portgroup PG any 20 permit tcp any any Router# show ip access-list my-pbacl-policy expand Extended IP access list my-pbacl-policy expanded 20 permit tcp host 10.20.20.1 eq 100 any 20 permit tcp host 10.20.20.1 gt 200 any 20 permit tcp host 10.20.20.1 neq 300 any 20 permit tcp host 10.20.20.5 eq 100 any 20 permit tcp host 10.20.20.5 gt 200 any 20 permit tcp host 10.20.20.5 neq 300 any 20 permit tcp 10.30.0.0 255.255.0.0 eq 100 any 20 permit tcp 10.30.0.0 255.255.0.0 gt 200 any 20 permit tcp 10.30.0.0 255.255.0.0 neq 300 any
Configuring PBACL on an Interface

To configure a PBACL on an interface, use the ip access-group command. The command syntax and usage is the same as for Cisco IOS ACLs. For additional information, see the Cisco IOS ACL Configuration Guidelines and Restrictions section on page 46-3. The following example shows how to associate access list my-pbacl-policy with VLAN 100:
Router(config)# int vlan 100 Router(config-if)# ip access-group mp-pbacl-policy in
Configuring IPv6 Address Compression

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.
46-6
OL-13013-06
Chapter 46
Understanding Cisco IOS ACL Support Configuring IPv6 Address Compression
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 46-1 for details about the compression methods. 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 46-1.
Table 46-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)#
46-7
Chapter 46 Optimized ACL Logging
Optimized ACL Logging

These sections describe optimized ACL logging (OAL):

Understanding OAL, page 46-8 OAL Guidelines and Restrictions, page 46-8 Configuring OAL, page 46-8
Understanding OAL
OAL provides hardware support for ACL logging. Unless you configure OAL, packets that require logging are processed completely in software on the RP. OAL permits or drops packets in hardware on the PFC3 and uses an optimized routine to send information to the RP 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 RP 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.
Configuring OAL
These sections describe how to configure OAL:

Configuring OAL Global Parameters, page 46-9 Configuring OAL on an Interface, page 46-10
46-8
OL-13013-06
Chapter 46
Understanding Cisco IOS ACL Support Optimized ACL Logging
Displaying OAL Information, page 46-10 Clearing Cached OAL Entries, page 46-10
Note
For complete syntax and usage information for the commands used in this section, see 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}}
Purpose Sets OAL global parameters.
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).
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).
46-9
Chapter 46 Guidelines and Restrictions for Using Layer 4 Operators in ACLs
Configuring OAL on an Interface

To configure OAL on an interface, perform this task: Command
Router(config)# interface {{type
1
Purpose
slot/port}
Specifies the interface to configure. Enables OAL for ingress traffic on the interface. Enables OAL for egress traffic on the interface.
Router(config-if)# logging ip access-list cache in Router(config-if)# logging ip access-list cache out 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 46-10 Determining Logical Operation Unit Usage, page 46-11
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)
46-10
OL-13013-06
Chapter 46
Understanding Cisco IOS ACL Support Guidelines and Restrictions for Using Layer 4 Operators in ACLs
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 46-11 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
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
46-11
Chapter 46 Guidelines and Restrictions for Using Layer 4 Operators in ACLs
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
46-12
OL-13013-06
CH A P T E R
47
Configuring Cisco TrustSec

Cisco TrustSec is an umbrella term for security improvements to Cisco network devices based on the capability to strongly identify users, hosts and network devices within a network. TrustSec provides topology independent and scalable access controls by uniquely classifying data traffic for a particular role. TrustSec ensures data confidentiality and integrity by establishing trust among authenticated peer and encrypting links with those peers. To configure Cisco Trustsec on the Cisco Catalyst 6500 Series switches, see the publication, Cisco TrustSec Switch Configuration Guide at the following URL: http://www.cisco.com/en/US/docs/switches/lan/trustsec/configuration/guide/trustsec.html Release Notes for Cisco TrustSec 1.0 General Availability 2010 Release are at the following URL: http://www.cisco.com/en/US/docs/switches/lan/trustsec/release/notes/rn_cts_xplat.html Additional information on the Cisco TrustSec Solution, including overviews, datasheets, and case studies, is available at: http://www.cisco.com/en/US/netsol/ns1051/index.html Table 1 lists the TrustSec features to be eventually implemented on TrustSec-enabled network devices. Successive general availability releases of TrustSec will expand the number of network devices supported and the number of TrustSec features supported per device. See the section, Hardware Supported for information on which TrustSec features are implemented.
47-1
Chapter 47
Table 1
Cisco TrustSec Key FeaturesTrustSec 1.0 General Availability 2010 Release
Cisco TrustSec Feature 802.1AE Tagging (MACSec)
Description Protocol for IEEE 802.1AE-based wire-rate hop-to-hop layer 2 encryption. Between MACSec-capable devices, packets are encrypted on egress from the transmitting device, decrypted on ingress to the receiving device, and in the clear within the devices. This feature is only available between TrustSec hardware-capable devices.
Endpoint Admission Control (EAC)
EAC is an authentication process for an endpoint user or a device connecting to the TrustSec domain. Usually EAC takes place at the access level switch. Successful authentication and authorization in the EAC process results in Security Group Tag assignment for the user or device. Currently EAC can be 802.1X, MAC Authentication Bypass (MAB), and Web Authentication Proxy (WebAuth). NDAC is an authentication process where each network device in the TrustSec domain can verify the credentials and trustworthiness of its peer device. NDAC utilizes an authentication framework based on IEEE 802.1X port-based authentication and uses EAP-FAST as its EAP method. Successful authentication and authorization in NDAC process results in Security Association Protocol negotiation for IEEE 802.1AE encryption. A Security Group Access Control List (SGACL) associates a Security Group Tag with a policy. The policy is enforced upon SGT-tagged traffic egressing the TrustSec domain. After NDAC authentication, the Security Association Protocol (SAP) automatically negotiates keys and the cipher suite for subsequent MACSec link encryption between TrustSec peers. SAP is defined in IEEE 802.11i. An SGT is a 16-bit single label indicating the security classification of a source in the TrustSec domain. It is appended to an Ethernet frame or an IP packet. Security Group Tag Exchange Protocol (SXP). Devices that are not TrustSec-hardware capable can, with SXP, receive from the Cisco ACS, SGT attributes for authenticated users or devices then forward the sourceIP-to-SGT binding to a TrustSec-hardware capable device for tagging and SGACL enforcement.
Network Device Admission Control (NDAC)
Security Group Access Control List (SGACL) Security Association Protocol (SAP)
Security Group Tag (SGT) SGT Exchange Protocol (SXP)
47-2
OL-13013-06
Chapter 47
Hardware Supported
Table 2 lists the TrustSec features supported by platform on the release date of Cisco IOS 12.2(33) SXI4.
Table 2
Feature and Platform supportTrustSec 1.0 General Availability 2010 Release Software Release Cisco IOS 12.2 (53) SE Cisco IOS 12.2 (53) SE Cisco IOS 12.2 (50) SG5 Cisco IOS 12.2(33) SXI3 Cisco NX-OS 4.2.1
1
Hardware Catalyst 3560 Series Catalyst 3750 Series Catalyst 4500 Series Catalyst 6500 Series Nexus 7000 Series
TrustSec Feature Introduced EAC; SXP EAC; SXP EAC; SXP EAC; SXP; NDAC (no SAP) EAC; SXP; NDAC; SGACL; MACSec
1. Cisco TrustSec was implemented on the Catalyst 6500 Series in SXI3, but announced as generally available in SXI4.
47-3
Chapter 47
47-4
OL-13013-06
C H A P T E R
48
Configuring Port ACLs and VLAN ACLs

This chapter describes how to configure port ACLs (PACLs) and VLAN ACLs (VACLs) in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html Optimized ACL logging (OAL) and VACL capture are incompatible. Do not configure both features on the switch. With OAL configured (see the Optimized ACL Logging section on page 46-8), use SPAN to capture traffic. Port ACLs do not support the access-list keywords log or reflexive. These keywords in the access list are ignored. OAL does not support PACLs. PACLs are not supported on private VLANs.
Tip

Understanding ACLs, page 48-1 Configuring PACLs, page 48-7 Configuring VACLs, page 48-11 Configuring VACL Logging, page 48-19
Understanding ACLs
The following sections describe ACLs in Cisco IOS Release 12.2SX:

Understanding ACLs, page 48-2 Understanding VACLs, page 48-2
48-1
Chapter 48 Understanding ACLs
Understanding Port ACLs, page 48-3 PACL and VACL Interactions, page 48-4
Understanding ACLs
Access control lists (ACLs) provide the ability to filter ingress and egress traffic based on conditions specified in the ACL. Cisco IOS Release 12.2SX supports the following types of ACLs:
Cisco IOS ACLs are applied to Layer 3 interfaces. They filter traffic routed between VLANs. For more information about Cisco IOS ACLs, see Chapter 46, Understanding Cisco IOS ACL Support. VACLs control access to the VLAN of all packets (bridged and routed). Packets can either enter the VLAN through a Layer 2 port or through a Layer 3 port after being routed. You can also use VACLs to filter traffic between devices in the same VLAN. Port ACLs perform access control on all traffic entering the specified Layer 2 port.
PACLs and VACLs can provide access control based on the Layer 3 addresses (for IP protocols) or Layer 2 MAC addresses (for non-IP protocols). You can apply only one IP access list and one MAC access list to a Layer 2 interface.
Understanding VACLs
VLAN ACLs (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 Cisco IOS ACLs that 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 the ACL TCAM hardware. VACLs ignore any Cisco IOS ACL fields that are not supported in hardware. You can configure VACLs for IP and MAC-layer traffic. VACLs applied to WAN interfaces support only IP traffic for VACL capture. If a VACL is configured for a packet type, and a packet of that type does not match the VACL, the default action is to deny the packet.
Note
IGMP packets are not checked against VACLs.
MAC Policy-Based Forwarding

Cisco IOS Release 12.2(33)SXI and later releases support MAC Policy-Based Forwarding (PBF), a type of MAC-based VACL by which packets can be bridged between VLANs. MAC PBF forwards packets based solely on the source and destination MAC addresses, ignoring any information above Layer 2. Unlike other VACLs, which are processed in the ACL TCAM hardware, MAC PBF is performed in software, with optional rate limiters to control CPU usage. Also, PBF is applied only to incoming packets.
Note
Layer 2 port ACLs (PACLs) take precedence over MAC PBF.
48-2
OL-13013-06
Chapter 48
Configuring Port ACLs and VLAN ACLs Understanding ACLs
Understanding Port ACLs

The port ACL (PACL) feature provides the ability to perform access control on specific Layer 2 ports. A Layer 2 port is a physical LAN or trunk port that belongs to a VLAN. Port ACLs are applied only on the ingress traffic. The port ACL feature is supported only in hardware (port ACLs are not applied to any packets routed in software). When you create a port ACL, an entry is created in the ACL TCAM. You can use the show tcam counts command to see how much TCAM space is available. The PACL feature does not affect Layer 2 control packets received on the port. You can use the access-group mode command to change the way that PACLs interact with other ACLs. PACLs use the following modes:
Prefer port modeIf a PACL is configured on a Layer 2 interface, the PACL takes effect and overwrites the effect of other ACLs (Cisco IOS ACL and VACL). If no PACL feature is configured on the Layer 2 interface, other features applicable to the interface are merged and are applied on the interface. Merge modeIn this mode, the PACL, VACL, and Cisco IOS ACLs are merged in the ingress direction following the logical serial model shown in Figure 48-2. This is the default access group mode.
You configure the access-group mode command on each interface. The default is merge mode.
Note
A PACL can be configured on a trunk port only after prefer port mode has been selected. Trunk ports do not support merge mode. To illustrate access group mode, assume a physical port belongs to VLAN100, and the following ACLs are configured:

Cisco IOS ACL R1 is applied on routed interface VLAN100. VACL (VLAN filter) V1 is applied on VLAN100. PACL P1 is applied on the physical port. In prefer port mode, Cisco IOS ACL R1 and VACL V1 are ignored. In merge mode, Cisco IOS ACL R1, VACL V1 and PACL P1 are merged and applied on the port.
In this situation, the following ACL interactions occur:

Note
The CLI syntax for creating a PACL is identical to the syntax for creating a Cisco IOS ACL. An instance of an ACL that is mapped to a Layer 2 port is called a PACL. An instance of an ACL that is mapped to a Layer 3 interface is called a Cisco IOS ACL. The same ACL can be mapped to both a Layer 2 port and a Layer 3 interface. The PACL feature supports MAC ACLs and IPv4 ACLs. The PACL feature does not support ACLs for IPV6, ARP, or Multiprotocol Label Switching (MPLS) traffic. PACLs are explained in more detail in the following sections:

EtherChannel and PACL Interactions, page 48-4 Dynamic ACLs (Applies to Merge Mode Only), page 48-4 Trunk Ports, page 48-4 Layer 2 to Layer 3 Port Conversion, page 48-4
48-3
Port-VLAN Association Changes, page 48-4
EtherChannel and PACL Interactions

This section describes the guidelines for the EtherChannel and PACL interactions:
PACLs are supported on the main Layer 2 channel interface but not on the port members. A port that has a PACL configured on it may not be configured as an EtherChannel member port. The EtherChannel configuration commands are unavailable on ports that are configured with a PACL. Changing the configuration on the logical port affects all the ports in the channel. When an ACL is mapped to the logical port belonging to a channel, it is mapped to all ports in the channel.
Dynamic ACLs (Applies to Merge Mode Only)

Dynamic ACLs are VLAN-based and are used by GWIP. The merge mode does not support the merging of the dynamic ACLs with the PACLs. In merge mode, the following configurations are not allowed:

Attempting to apply a PACL on a port where its corresponding VLAN has a dynamic ACL mapped. In this case, the PACL is not applied to traffic on the port. Configuring a dynamic ACL on a VLAN where one of its constituent ports has a PACL installed. In this case, the dynamic ACL is not applied.
Trunk Ports
To configure a PACL on a trunk port, you must first configure port prefer mode. The configuration commands to apply a PACL on a trunk or dynamic port will not be available until you configure the port in port prefer mode by entering the access-group mode prefer port interface command. Trunk ports do not support merge mode.
Layer 2 to Layer 3 Port Conversion

If you reconfigure a port from Layer 2 to Layer 3, any PACL configured on the port becomes inactive but remains in the configuration. If you subsequently configure the port as Layer 2, any PACL configured on the port becomes active again.
Port-VLAN Association Changes

You can enter port configuration commands that alter the port-VLAN association, which triggers an ACL remerge. Unmapping and then mapping a PACL, VACL, or Cisco IOS ACL automatically triggers a remerge. In merge mode, online insertion or removal of a switching module also triggers a remerge, if ports on the module have PACLs configured.
PACL and VACL Interactions

The following sections describe interactions between the different types of ACL:
48-4
OL-13013-06
Chapter 48
Configuring Port ACLs and VLAN ACLs Understanding ACLs
PACL Interaction with VACLs and Cisco IOS ACLs, page 48-5 Bridged Packets, page 48-5 Routed Packets, page 48-6 Multicast Packets, page 48-6
PACL Interaction with VACLs and Cisco IOS ACLs

This section describes the guidelines for the PACL interaction with the VACLs and Cisco IOS ACLs. For an incoming packet on a physical port, the PACL is applied first. If the packet is permitted by the PACL, the VACL on the ingress VLAN is applied next. If the packet is Layer 3 forwarded and is permitted by the VACL, it is filtered by the Cisco IOS ACL on the same VLAN. The same process happens in reverse in the egress direction. However, there is currently no hardware support for output PACLs. The PACLs override both the VACLs and Cisco IOS ACLs when the port is configured in prefer port mode. The one exception to this rule is when the packets are forwarded in the software by the route processor (RP). The RP applies the ingress Cisco IOS ACL regardless of the PACL mode. Two examples where the packets are forwarded in the software are as follows:

Packets that are egress bridged (due to logging or features such as NAT) Packets with IP options
Bridged Packets
Figure 48-1 shows a PACL and a VACL applied to bridged packets. In merge mode, the ACLs are applied in the following order:
1. 2. 3.
PACL for the ingress port VACL for the ingress VLAN VACL for the egress VLAN
Applying ACLs on Bridged Packets
Figure 48-1
VACL
MSFC
VACL
Host A
VLAN 10 PACL
Supervisor Engine
Host B
In prefer port mode, only the PACL is applied to the ingress packets (the input VACL is not applied).
182042
48-5
Routed Packets
Figure 48-2 shows how ACLs are applied on routed and Layer 3-switched packets. In merge mode, the ACLs are applied in the following order:
1. 2. 3. 4. 5.
PACL for the ingress port VACL for the ingress VLAN Input Cisco IOS ACL Output Cisco IOS ACL VACL for the egress VLAN
In prefer port mode, only the PACL is applied to the ingress packets (the input VACL and Cisco IOS ACL are not applied).
Figure 48-2 Applying ACLs on Routed Packets
Routed
Input IOS ACL Bridged VACL
Output IOS ACL MSFC VACL Bridged
Supervisor Engine
182043
Host A (VLAN 10)
PACL
Host B (VLAN 20)
Multicast Packets
Figure 48-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. PACL for the ingress port b. VACL for the ingress VLAN c. Input Cisco IOS ACL
2.
Packets after multicast expansion:

a. Output Cisco IOS ACL b. VACL for the egress VLAN
3.
Packets originating from router:

a. Output Cisco IOS ACL
48-6
OL-13013-06
Chapter 48
Configuring Port ACLs and VLAN ACLs Configuring PACLs
b. VACL for the egress VLAN
In prefer port mode, only the PACL is applied to the ingress packets (the input VACL and Cisco IOS ACL are not applied).
Figure 48-3 Applying ACLs on Multicast Packets
IOS ACL for output VLAN for packets originating from router Routed Input IOS ACL Bridged PACL VACL Supervisor Engine Host B (VLAN 20)
182044
MSFC
Output IOS ACL VACL
Host A (VLAN 10)
Bridged Host D (VLAN 20)
Host C (VLAN 10)
Configuring PACLs
Cisco IOS Release 12.2(33)SXH and later releases support PACLs. This section describes how to configure PACLs. PACLs filter incoming traffic on Layer 2 interfaces, using Layer 3 information, Layer 4 header information, or non-IP Layer 2 information. The PACL feature uses existing Cisco IOS access-list commands to create the standard or extended IP ACLs or named MAC-extended ACLs that you want to apply to the port. Use the ip access-group or mac access-group interface command to apply an IP ACL or MAC ACL to one or more Layer 2 interfaces.
Note
PACLs cannot filter Physical Link Protocols and Logical Link Protocols, such as CDP, VTP, DTP, PAgP, UDLD, and STP, because the protocols are redirected to the switch processor (SP) before the ACL takes effect. This section contains the following topics:

PACL Configuration Guidelines, page 48-8 Configuring IP and MAC ACLs on a Layer 2 Interface, page 48-8 Configuring Access-group Mode on Layer 2 Interface, page 48-9
48-7
Chapter 48 Configuring PACLs
Applying ACLs to a Layer 2 Interface, page 48-9 Applying ACLs to a Port Channel, page 48-10 Displaying an ACL Configuration on a Layer 2 Interface, page 48-10
PACL Configuration Guidelines

Consider the following guidelines when configuring PACLs:

There can be at most one IP access list and one MAC access list applied to the same Layer 2 interface per direction. PACLs are not applied to IPv6, MPLS, or ARP messages. An IP access list filters only IPv4 packets, For IP access lists, you can define a standard, extended, or named access-list. A MAC access list filters ingress packets that are of an unsupported type (not IP, IPv6, ARP, or MPLS packets) based on the fields of the Ethernet datagram. A MAC access list is not applied to IP, IPv6, MPLS, or ARP messages. You can define only named MAC access lists. The number of ACLs and ACEs that can be configured as part of a PACL are bounded by the hardware resources on the switch. Those hardware resources are shared by various ACL features (such as VACLs) that are configured on the system. If there are insufficient hardware resources to program a PACL in hardware, the PACL is not applied. PACL does not support the access-list log and reflect/evaluate keywords. These keywords are ignored if you add them to the access list for a PACL. OAL does not support PACLs. The access group mode can change the way PACLs interact with other ACLs. To maintain consistent behavior across Cisco platforms, use the default access group mode (merge mode).
Configuring IP and MAC ACLs on a Layer 2 Interface

IP and MAC ACLs can be applied to Layer 2 physical interfaces. Standard (numbered, named) and Extended (numbered, named) IP ACLs, and Extended Named MAC ACLs are supported. To apply IP or MAC ACLs on a Layer 2 interface, perform this task: Command
Switch# configure terminal Switch(config)# interface interface Switch(config-if)# {ip | mac} access-group {name | number | in | out} Switch(config)# show running-config
Purpose Enters global configuration mode. Enters interface configuration mode for a Layer 2 port. Applies a numbered or named ACL to the Layer 2 interface. Displays the access list configuration.
This example shows how to configure the Extended Named IP ACL simple-ip-acl to permit all TCP traffic and implicitly deny all other IP traffic:
Switch(config)# ip access-list extended simple-ip-acl Switch(config-ext-nacl)# permit tcp any any Switch(config-ext-nacl)# end
48-8
OL-13013-06
Chapter 48
Configuring Port ACLs and VLAN ACLs Configuring PACLs
This example shows how to configure the Extended Named MAC ACL simple-mac-acl to permit source host 000.000.011 to any destination host:
Switch(config)# mac access-list extended simple-mac-acl Switch(config-ext-macl)# permit host 000.000.011 any Switch(config-ext-macl)# end
Configuring Access-group Mode on Layer 2 Interface

To configure the access mode on a Layer 2 interface, perform this task: Command
Switch# configure terminal Switch(config)# interface interface Switch(config-if)# [no] access-group mode {prefer port | merge} Switch(config)# show running-config
Purpose Enters global configuration mode. Enters interface configuration mode for a Layer 2 port. Sets the mode for this Layer 2 interface. The no prefix sets the mode to the default value (which is merge). Displays the access list configuration.
This example shows how to configure an interface to use prefer port mode:
Switch# configure terminal Switch(config)# interface gigabitEthernet 6/1 Switch(config-if)# access-group mode prefer port
This example shows how to configure an interface to use merge mode:

Switch# configure terminal Switch(config)# interface gigabitEthernet 6/1 Switch(config-if)# access-group mode merge
Applying ACLs to a Layer 2 Interface

To apply IP and MAC ACLs to a Layer 2 interface, perform one of these tasks: Command
Switch(config-if)# ip access-group ip-acl in Switch(config-if)# mac access-group mac-acl in
Purpose Applies an IP ACL to the Layer 2 interface. Applies a MAC ACL to the Layer 2 interface.
This example applies the extended named IP ACL simple-ip-acl to interface GigabitEthernet 6/1 ingress traffic:
Switch# configure t Switch(config)# interface gigabitEthernet 6/1 Switch(config-if)# ip access-group simple-ip-acl in
This example applies the extended named MAC ACL simple-mac-acl to interface GigabitEthernet 6/1 ingress traffic:
Switch# configure t Switch(config)# interface gigabitEthernet 6/1 Switch(config-if)# mac access-group simple-mac-acl in
48-9
Chapter 48 Configuring PACLs
Applying ACLs to a Port Channel

To apply IP and MAC ACLs to a port channel logical interface, perform this task: Command
Switch(config-if)# interface port-channel number Switch(config-if)# ip access-group ip-acl {in | out} Switch(config-if)# mac access-group mac-acl {in | out}
Purpose Enters configuration mode for the port channel. Applies an IP ACL to the port channel interface. Applies a MAC ACL to the port channel interface.
This example applies the extended named IP ACL simple-ip-acl to port channel 3 ingress traffic:
Switch# configure t Switch(config)# interface port-channel 3 Switch(config-if)# ip access-group simple-ip-acl in
Displaying an ACL Configuration on a Layer 2 Interface

To display information about an ACL configuration on Layer 2 interfaces, perform one of these tasks: Command
Switch# show ip access-lists [interface interface-name] Switch# show mac access-group [interface interface-name]
Purpose Shows the IP access group configuration on the interface. Shows the MAC access group configuration on the interface. Shows the access group mode configuration on the interface.
Switch# show access-group mode [interface interface-name]
This example shows that the IP access group simple-ip-acl is configured on the inbound direction of interface fa6/1:
Switch# show ip interface fast 6/1 FastEthernet6/1 is up, line protocol is up Inbound access list is simple-ip-acl Outgoing access list is not set
This example shows that MAC access group simple-mac-acl is configured on the inbound direction of interface fa6/1:
Switch# show mac access-group interface fast 6/1 Interface FastEthernet6/1: Inbound access-list is simple-mac-acl Outbound access-list is not set
This example shows that access group merge is configured on interface fa6/1:
Switch# show access-group mode interface fast 6/1 Interface FastEthernet6/1: Access group mode is: merge
48-10
OL-13013-06
Chapter 48
Configuring Port ACLs and VLAN ACLs Configuring VACLs
Configuring VACLs
These sections describe how to configure VACLs:

VACL Configuration Guidelines, page 48-11 Defining a VLAN Access Map, page 48-13 Configuring a Match Clause in a VLAN Access Map Sequence, page 48-13 Configuring an Action Clause in a VLAN Access Map Sequence, page 48-14 Applying a VLAN Access Map, page 48-15 Verifying VLAN Access Map Configuration, page 48-15 VLAN Access Map Configuration and Verification Examples, page 48-15 Configuring a Capture Port, page 48-16 Configuring MAC PBF, page 48-17
VACL Configuration Guidelines

Consider the following guidelines when configuring VACLs:

VACLs use standard and extended Cisco IOS IP and MAC layer-named ACLs (see the Configuring MAC ACLs section on page 40-66) 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 has a match clause and an action clause. The match clause specifies IP 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 apply access control to 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 apply access control to both the ingress and egress routed traffic. You can define a VACL to apply access control to 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.
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. When VACL capture is configured on an egress interface together with another egress feature that requires software processing of the traffic, packets of the overlapping traffic may be captured twice.
48-11
Chapter 48 Configuring VACLs
By default, software-switched WAN packets are not subjected to ACL lookup in the ACL TCAM and are therefore not affected by hardware-only features. As a result, VACL capture will fail for software-switched WAN packets. In Cisco IOS Release 12.2(33)SXI2 and later releases, you can allow ACLs to be applied to egress or ingress software-switched WAN packets by entering the platform cwan acl software-switched {egress | ingress} command in global configuration mode. To verify whether ACLs will be applied to software-switched WAN packets, enter the show platform acl software-switched command as shown in this example:
Router (config)# platform cwan acl software-switched ingress Router (config)# exit Router# show platform acl software-switched CWAN: ACL treatment for software switched in INGRESS is enabled CWAN: ACL treatment for software switched in EGRESS is disabled
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. VACLs cannot be applied to IGMP, MLD, or PIM traffic. When the WAN logical interface (Multilink or Multilink Frame Relay) is removed, the corresponding VACL filter applied to the WAN logical interface is also removed and the error message VACL-4-VLANFILTER_CWAN_DELETE appears. The following example displays an illustration of this behavior:
Router (config)# do show vlan filter VLAN Map capture_all: Configured on VLANs: 100 Active on VLANs: 100 Configured on Interfaces: Active on Interfaces: Multilink100
Router (config)# no interface multilink 100 % Please 'shutdown' this interface before trying to delete it Router (config)# interface multilink 100 Router (config-if)# show Router (config-if)# exit Router (config)# no interface multilink 100 Router (config)# %VACL-4-VLANFILTER_CWAN_DELETE: VLAN ACCESS-MAP capture_all applied on Multilink100 will be removed. Router (config)# do show vlan filter VLAN Map capture_all: Configured on VLANs: 100 Active on VLANs: 100 Router (config)#
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.
48-12
OL-13013-06
Chapter 48
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. Deletes a map sequence from the VLAN access map. Deletes the VLAN access map.
Router(config)# no vlan access-map map_name 0-65535 Router(config)# no vlan access-map map_name
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 48-15.
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} | {mac address acl_name}} Router(config-access-map)# no match {ip address {1-199 | 1300-2699 | 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, see the Configuring MAC ACLs section on page 40-66. For information about Cisco IOS ACLs, see the Traffic Filtering and Firewalls section of the 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
48-13
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 | vlan vlan_ID]} | {redirect {{ethernet | fastethernet | gigabitethernet | tengigabitethernet} slot/port} | {port-channel channel_id}} Router(config-access-map)# no action {drop [log]} | {forward [capture | vlan vlan_ID]} | {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 48-16. The forward vlan action implements Policy-Based Forwarding (PBF), bridging between VLANs. 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. If a VACL is redirecting traffic to an egress SPAN source port, SPAN does not copy 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.
48-14
OL-13013-06
Chapter 48
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
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
48-15
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 16-10 and the Configuring the Layer 2 Trunk Not to Use DTP section on page 16-11). To configure a capture port, perform this task:
Command
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. Configures the port to capture VACL-filtered traffic.
Router(config-if)# switchport capture allowed vlan {add | all | except | remove} vlan_list Router(config-if)# switchport capture 1. type = fastethernet, gigabitethernet, or tengigabitethernet
48-16
OL-13013-06
Chapter 48
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 16-10) 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 16-16) 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 mymap Vlan access-map "mymap" 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
Configuring MAC PBF

To configure MAC policy-based forwarding (PBF), perform this task on each source VLAN: Command
Router(config)# mac host my_host mac_addr
Purpose (Optional) Assigns a name to the MAC address of the source host. Configures a MAC ACL. Configures an access control entry (ACE) to permit traffic from the named host to any other address. Hosts can be specified by a name or by a MAC address. Configures an ACE to permit traffic from the named host to one other host. Exits ACL configuration.
Router(config)# mac access-list extended macl_name Router(config-ext-macl)# permit host my_host any
Router(config-ext-macl)# permit host my_host host other_host
Step 4
Router(config-ext-macl)# exit
48-17
Command
Router(config)# vlan access-map map_name Router(config-access-map)# match mac address macl_name Router(config-access-map)# action forward vlan other_vlan_ID [local]
Purpose Defines a VLAN access map. Applies the MAC ACL to this VLAN access map. Forwards matching traffic to the other VLAN.
Note
By default, PBF-specified devices on the same VLAN cannot communicate with each other. To allow local communication by the host, use the local keyword.
Step 8 Step 9
Router(config-access-map)# exit Router(config)# vlan filter map_name vlan-list my_vlan_ID
Exits access map configuration. Applies the VLAN access map to the specified VLAN. Enters interface configuration mode for the VLAN. Classifies incoming or outgoing Layer 3 packets on this VLAN as Layer 2 packets. Exits interface configuration. (Optional) Sets a rate limit on PBF packets.

Step 10 Router(config)# interface vlan my_vlan_ID Step 11 Router(config-if)# mac packet-classify Step 12 Router(config-if)# exit Step 13 Router(config)# mls rate-limit unicast acl mac-pbf pps [burst_size]
ppsMaximum number of packets per second. The range is 10 to 1000000 packets per second. burst_sizeMaximum number of packets in a burst. The range is 1 to 255 packets.
Step 14 Router(config)# exit Step 15 Router# show vlan mac-pbf config Step 16 Router# clear vlan mac-pbf counters
Exits global configuration mode. Displays MAC PBF configuration and statistics. (Optional) Clears MAC PBF packet counters.
When configuring MAC PBF, note the following information:

To allow traffic in both directions between two VLANs, you must configure MAC PBF in both VLANs. You can configure MAC PBF between hosts in different switches. By default, MAC PBF hosts in the same VLAN cannot communicate with each other. To allow local communication, use the local keyword. When configuring the vlan filter command, specify only one VLAN after the vlan-list keyword. If you specify more than one VLAN, MAC PBF will ignore all but the last VLAN in the list. The output of the show vlan mac-pbf config command displays the following fields for configured PBF paths:
Rcv Vlan The number of the VLAN to which packets are forwarded by PBF. Snd Vlan The number of the VLAN which will forward packets by PBF. DMAC The MAC address of the destination host on the receiving VLAN. SMAC The MAC address of the source host on the sending VLAN. (Local) Displays 1 if the local keyword is configured in the action forward vlan command
on the sending VLAN; displays 0 if the local keyword is not configured.

(Packet counter) The number of packets that have been forwarded from the sending VLAN
to the receiving VLAN. To clear this counter, enter the clear vlan mac-pbf counters command.
48-18
OL-13013-06
Chapter 48
Configuring Port ACLs and VLAN ACLs Configuring VACL Logging
Pkts dropped The number of packets that have been dropped by the sending VLAN. To clear
this counter, enter the clear vlan mac-pbf counters command.
If the sending VLAN is shut down, MAC PBF will still function. Shutting down a VLAN disables Layer 3 functionality, but MAC PBF is a Layer 2 function.
This example shows how to configure and display MAC PBF to allow two hosts in separate VLANs (red VLAN 100 and blue VLAN 200) on the same switch to exchange packets:
Router(config)# mac host host_red3 0001.0002.0003 Router(config)# mac access-list extended macl_red Router(config-ext-macl)# permit host host_red host host_blue Router(config-ext-macl)# exit Router(config)# vlan access-map red_to_blue Router(config-access-map)# match mac address macl_red Router(config-access-map)# action forward vlan 200 local Router(config-access-map)# exit Router(config)# vlan filter red_to_blue vlan-list 100 Router(config)# interface vlan 100 Router(config-if)# mac packet-classify Router(config-if)# exit Router(config)# Router(config)# mac host host_blue5 0001.0002.0005 Router(config)# mac access-list extended macl_blue Router(config-ext-macl)# permit host host_blue host host_red Router(config-ext-macl)# exit Router(config)# vlan access-map blue_to_red Router(config-access-map)# match mac address macl_blue Router(config-access-map)# action forward vlan 100 Router(config-access-map)# exit Router(config)# vlan filter blue_to_red vlan-list 200 Router(config)# interface vlan 200 Router(config-if)# mac packet-classify Router(config-if)# exit Router# Router# show vlan mac-pbf config Rcv Vlan 100, Snd Vlan 200, DMAC 0001.0002.0003, SMAC 0001.0002.0005 1 15 Rcv Vlan 200, Snd Vlan 100, DMAC 0001.0002.0005, SMAC 0001.0002.0003 0 23 Pkts Dropped 0 Router#
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.
48-19
Chapter 48 Configuring VACL Logging
To configure VACL logging, use the action drop log command action in VLAN access map submode (see the Configuring PACLs section on page 48-7 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
Tip
48-20
OL-13013-06
C H A P T E R
49
Configuring Denial of Service Protection

This chapter contains information on how to protect your switch against Denial of Service (DoS) attacks. The information covered in this chapter is unique to Cisco IOS Release 12.2SX, 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
Tip

Understanding DoS Protection, page 49-2 DoS Protection Default Configuration, page 49-13 DoS Protection Configuration Guidelines and Restrictions, page 49-14 Configuring Sticky ARP, page 49-18
49-1
Chapter 49 Understanding DoS Protection
Understanding DoS Protection

This section contains information about the available methods to counteract DoS attacks 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 Chapter 50, Configuring Control Plane Policing. Security ACLs and VACLs, page 49-2 QoS Rate Limiting, page 49-3 uRPF Check, page 49-4 Traffic Storm Control, page 49-4 Network Under SYN Attack, page 49-5 ARP Policing, page 49-5 Recommended Rate-Limiter Configuration, page 49-6 Hardware-Based Rate Limiters on the PFC3, page 49-6
Ingress-Egress ACL Bridged Packets (Unicast Only), page 49-7 uRPF Check Failure, page 49-8 TTL Failure, page 49-8 ICMP Unreachable (Unicast Only), page 49-8 FIB (CEF) Receive Cases (Unicast Only), page 49-9 FIB Glean (Unicast Only), page 49-9 Layer 3 Security Features (Unicast Only), page 49-9 ICMP Redirect (Unicast Only), page 49-10 VACL Log (Unicast Only), page 49-10 MTU Failure, page 49-10 Layer 2 PDU, page 49-10 Layer 2 Protocol Tunneling, page 49-11 IP Errors, page 49-11 Layer 2 Multicast IGMP Snooping, page 49-10 IPv4 Multicast, page 49-11 IPv6 Multicast, page 49-12
These sections describe DoS protection:

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.
49-2
OL-13013-06
Chapter 49
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 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.
QoS Rate Limiting

QoS ACLs limit the amount of a particular type of traffic that is processed by the RP. If a DoS attack is initiated against the RP, QoS ACLs can prevent the DoS traffic from reaching the RP 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 RP. 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 RP 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
49-3
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 switch processor (SP) FIB tables. 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 is supported in hardware. However, all packets that fail the uRPF check, and are forwarded because of an applied ACL, can be sent and rate limited to the RP 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).
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 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.
49-4
OL-13013-06
Chapter 49
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 RP 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.
Note
When both thresholds fall below the configured low value, the aggressive behavior ceases (default value is 900 in both factors).
TCP flows are hardware assisted on the PFC3.
ARP Policing
During an attack, malicious users may try to overwhelm the RP 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 RP 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
49-5
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. Disable 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)
49-6
OL-13013-06
Chapter 49
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 RP 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 RP. 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. 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:
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:
Router(config)# mls rate-limit unicast acl output 40000 50
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
49-7
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 RP 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 RP. The uRPF check rate limiters allow you to rate limit the packets per second that are bridged to the RP CPU when a uRPF check failure occurs. This example shows how to rate limit the uRPF check failure packets sent to the RP 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 RP 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
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 RP). The ICMP unreachable rate limiter allows you to rate limit the packets that are sent to the RP containing unreachable addresses. This example shows how to rate limit the packets that are sent to the RP 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
49-8
OL-13013-06
Chapter 49
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 RP 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 RP. This situation occurs when traffic enters a port and contains the destination of a host on a subnet that is locally connected to the RP, 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 RP 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 RP 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 RP. For these security features, you need to rate limit the number of these packets being sent to the RP 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 RP may be overwhelmed. Rate limiting would be advantageous in this situation. IPsec and inspection are also done by the RP 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 RP to 100000 pps with a burst of 10 packets:
Router(config)# mls rate-limit unicast ip features 100000 10
49-9
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 RP sends ICMP-redirect messages to the host to correct its sending path. If this traffic occurs continuously, and is not rate limited, the RP 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 RP 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 RP 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
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 RP CPU. This might cause the RP to be overwhelmed. This example shows how to rate limit packets failing the MTU failures from being sent to the RP 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 SP. IGMP snooping listens to IGMP messages between the hosts and the switch. You cannot enable the Layer 2 PDU rate limiter if the 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. In releases earlier than Cisco IOS Release 12.2(33)SXH, the IGMP snooping rate limiter also rate limits PIM messages. In Cisco IOS Release 12.2(33)SXH and later releases, the IGMP snooping rate limiter does not rate limit PIM messages. 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 SP and not the RP CPU. You cannot enable the Layer 2 PDU rate limiter if the 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:
49-10
OL-13013-06
Chapter 49
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 SP. 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 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
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 RP 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 RP 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 RP 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 RP. For this reason, it may be desirable to rate limit the flow destined to the RP 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 not supported in PFC3A mode. 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
49-11
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
IPv6 Multicast
This rate limiter limits the IPv6 multicast packets. Table 49-1 lists the IPv6 rate limiters and the class of traffic that each rate limiter serves.
Table 49-1 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.
49-12
OL-13013-06
Chapter 49
Configuring Denial of Service Protection DoS Protection Default Configuration
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
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 49-2 shows the DoS protection default configuration for the PFC3 hardware-based rate limiters.
Table 49-2 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
Default Status (ON/OFF) OFF ON OFF OFF OFF OFF ON ON OFF OFF OFF OFF ON OFF ON 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
49-13
Chapter 49 DoS Protection Configuration Guidelines and Restrictions
Table 49-2
PFC3 Hardware-based Rate Limiter Default Setting (continued)
Rate Limiter Multicast Directly Connected Multicast Non-RPF Multicast IPv6
Default Status (ON/OFF) OFF OFF ON
Default Value
If the packets-in-burst is not set, a default of 100 is programmed for multicast cases.
DoS Protection Configuration Guidelines and Restrictions

When configuring DoS protection, 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 50-2.
Do not use these rate limiters if multicast is enabled in systems configured with a PFC3A:
TTL failure MTU failure
These rate limiters are not supported in PFC3A 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.
49-14
OL-13013-06
Chapter 49
Configuring Denial of Service Protection DoS Protection Configuration Guidelines and Restrictions
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.
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

All modes except PFC3A mode support 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)
49-15
Chapter 49 DoS Protection Configuration Guidelines and Restrictions
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 M 36836 0.0.0.0 R rslt: L3_DENY_RESULT (*) Router#
0.0.0.0 P=0 P=0 0.0.0.0 0 0 rtr_rslt: L3_DENY_RESULT (*)
------
0 ---- 0 0 ---- 0
0 -- --- 0-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.
49-16
OL-13013-06
Chapter 49
Configuring Denial of Service Protection DoS Protection Configuration Guidelines and Restrictions
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. 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 Status ---------Off On Off Off Off Off On Off Off On On Off On On Off Off Off Off Off Off Packets/s --------100000 2000 100000 100 100 100 Burst ----100 1 100 10 10 10 Sharing ------Not sharing Not sharing Not sharing Group:0 S Group:0 S Group:0 S -
49-17
Chapter 49 Configuring Sticky ARP
IP ERRORS CAPTURE PKT MCAST IGMP MCAST IPv6 DIRECT CON MCAST IPv6 *G M BRIDG MCAST IPv6 *G BRIDGE MCAST IPv6 SG BRIDGE MCAST IPv6 ROUTE CNTL MCAST IPv6 DFLT DROP MCAST IPv6 SECOND. DR Router#
On Off Off Off Off Off Off Off Off Off
100 -
10 -
Group:0 S -
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 -
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 switches. 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, see 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
49-18
OL-13013-06
Chapter 49
Configuring Denial of Service Protection Configuring Sticky ARP
To configure sticky ARP on a Layer 3 interface, perform this 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. type = fastethernet, gigabitethernet, or tengigabitethernet
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
49-19
Chapter 49 Configuring Sticky ARP
49-20
OL-13013-06
C H A P T E R
50
Configuring Control Plane Policing

This chapter describes how to configure control plane policing (CoPP) with Cisco IOS Release 12.2SX.
Note
Tip

Understanding Control Plane Policing, page 50-1 CoPP Default Configuration, page 50-2 CoPP Configuration Guidelines and Restrictions, page 50-2 Configuring CoPP, page 50-3 Monitoring CoPP, page 50-4 Defining Traffic Classification, page 50-5
Understanding Control Plane Policing

The traffic managed by the RP is divided into three functional components or planes:

Data plane Management plane Control plane
The control plane policing (CoPP) feature increases security on the switch by protecting the RP 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.
50-1
Chapter 50 CoPP Default Configuration
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 majority of traffic managed by the RP 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:

CoPP is not be enabled in hardware unless you have enabled PFC QoS globally with the mls qos command. If you do not enter the mls qos command, CoPP is not hardware-accelerated. CoPP is supported in software for the following:
Multicast traffic. Broadcast traffic.
Note
The combination of ACLs, traffic storm control, and CoPP software protection provides protection against broadcast DoS attacks.
CoPP-policy ACLs configured with the log keyword. To avoid software-supported CoPP
processing, do not use the log keyword in CoPP-policy ACLs.

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. Enter the show tcam utilization command to verify the TCAM utilization.
CoPP policies configured with the match protocol arp command. Release 12.2(33)SXI4 and later releases support CoPP policies configured with the
match access-group arp_acl command.

CoPP does not support ARP policies. ARP policing mechanisms provide protection against
ARP storms.

CoPP is performed on a per-forwarding-engine basis and software CoPP is performed on an aggregate basis. CoPP does not support MAC ACLs. 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.
50-2
OL-13013-06
Chapter 50
Configuring Control Plane Policing Configuring CoPP
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. 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. 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). 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.
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, see the Defining Traffic Classification section on page 50-5. 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.
50-3
Chapter 50 Monitoring CoPP
Command
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]
Purpose 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 Step 5
Router(config)# control-plane Router(config-cp)# Router(config-cp)# service-policy input service-policy-name
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. The supported QoS ACLs 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.
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)
50-4
OL-13013-06
Chapter 50
Configuring Control Plane Policing Defining Traffic Classification
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 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 50-6 Traffic Classification Guidelines, page 50-7 Sample Basic ACLs for CoPP Traffic Classification, page 50-7
50-5
Chapter 50 Defining Traffic Classification
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. 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 be 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 RP 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 RP. 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 RP 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 RP. 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.
50-6
OL-13013-06
Chapter 50
Configuring Control Plane Policing Defining Traffic Classification
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 50-7.
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 RP) 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
50-7
Chapter 50 Defining Traffic Classification
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:
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
Tip
50-8
OL-13013-06
C H A P T E R
51

This chapter describes how to configure Dynamic Host Configuration Protocol (DHCP) snooping in Cisco IOS Release 12.2SX.
Note
Tip

Understanding DHCP Snooping, page 51-1 Default Configuration for DHCP Snooping, page 51-6 DHCP Snooping Configuration Restrictions and Guidelines, page 51-7 Configuring DHCP Snooping, page 51-9
Understanding DHCP Snooping

These sections describe the DHCP snooping feature:

Overview of DHCP Snooping, page 51-2 Trusted and Untrusted Sources, page 51-2 DHCP Snooping Binding Database, page 51-3 Packet Validation, page 51-3 DHCP Snooping Option-82 Data Insertion, page 51-3 Overview of the DHCP Snooping Database Agent, page 51-5
51-1
Chapter 51 Understanding DHCP Snooping
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 route processor (RP). Therefore, all DHCP messages for enabled VLANs are intercepted in the PFC and directed to the RP 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 and unknown DHCP servers are generally treated as untrusted sources. A DHCP server that is on your network without your knowledge on an untrusted port is called a spurious DHCP server. A spurious DHCP server is any piece of equipment that is loaded with DHCP server enabled. Some examples are desktop systems and laptop systems that are loaded with DHCP server enabled, or wireless access points honoring DHCP requests on the wired side of your network. If spurious DHCP servers remain undetected, you will have difficulties troubleshooting a network outage. You can detect spurious DHCP servers by sending dummy DHCPDISCOVER packets out to all of the DHCP servers so that a response is sent back to the switch. 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 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.
51-2
OL-13013-06
Chapter 51
Configuring DHCP Snooping Understanding DHCP Snooping
DHCP Snooping Binding Database

The DHCP snooping binding database is also referred to as the DHCP snooping binding table. 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.
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.
51-3
Chapter 51 Understanding DHCP Snooping
Figure 51-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 51-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 IEEE 802.1X port-based authentication is enabled, the switch will also add the hosts 802.1X authenticated user identity information (the RADIUS attributes suboption) to the packet. See the Using 802.1X Authentication with DHCP Snooping section on page 57-11. 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 51-2 do not change:
Circuit ID suboption fields

Suboption type Length of the suboption type
51-4
OL-13013-06
Chapter 51
Configuring DHCP Snooping Understanding DHCP Snooping
Circuit ID type Length of the circuit ID type
Remote ID suboption fields

Suboption type Length of the suboption type Remote ID type Length of the circuit ID type
Figure 51-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 51-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

Suboption Remote type ID 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>
51-5
Chapter 51 Default Configuration for DHCP Snooping
<entry-2> <checksum-1-2> ... ... <entry-n> <checksum-1-2-..-n> 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 51-1 shows all the default configuration values for each DHCP snooping option.
Table 51-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
Default Value/State Disabled Enabled Disabled None Untrusted
51-6
OL-13013-06
Chapter 51
Configuring DHCP Snooping DHCP Snooping Configuration Restrictions and Guidelines
Table 51-1
Default Configuration Values for DHCP Snooping
Option DHCP snooping vlan DHCP snooping spurious server detection DHCP snooping detect spurious interval
Default Value/State Disabled Disabled 30 minutes
DHCP Snooping Configuration Restrictions and Guidelines

These sections provide DHCP snooping configuration restrictions and guidelines:

DHCP Snooping Configuration Restrictions, page 51-7 DHCP Snooping Configuration Guidelines, page 51-7 Minimum DHCP Snooping Configuration, page 51-8
DHCP Snooping Configuration Restrictions

When configuring DHCP snooping, note these restrictions:

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, see 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.
51-7
Chapter 51 DHCP Snooping Configuration Restrictions and Guidelines
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. 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, see 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. See the Enabling DHCP Snooping on VLANs section on page 51-11
2.
3.
Ensure that DHCP server is connected through a trusted interface. By default, the trust state of all interfaces is untrusted. See the Configuring the DHCP Trust State on Layer 2 LAN Interfaces section on page 51-12
4.
Configure the DHCP snooping database agent. This step ensures that database entries are restored after a restart or switchover. See the Configuring the DHCP Snooping Database Agent section on page 51-14
5.
Enable DHCP snooping globally. The feature is not active until you complete this step. See the Enabling DHCP Snooping Globally section on page 51-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. See the Enabling the DHCP Option-82 on Untrusted Port Feature section on page 51-10
51-8
OL-13013-06
Chapter 51
Configuring DHCP Snooping Configuring DHCP Snooping

These sections describe how to configure DHCP snooping:

Enabling DHCP Snooping Globally, page 51-9 Enabling DHCP Option-82 Data Insertion, page 51-10 Enabling the DHCP Option-82 on Untrusted Port Feature, page 51-10 Enabling DHCP Snooping MAC Address Verification, page 51-11 Enabling DHCP Snooping on VLANs, page 51-11 Configuring the DHCP Trust State on Layer 2 LAN Interfaces, page 51-12 Configuring Spurious DHCP Server Detection, page 51-13 Configuring DHCP Snooping Rate Limiting on Layer 2 LAN Interfaces, page 51-13 Configuring the DHCP Snooping Database Agent, page 51-14 Configuration Examples for the Database Agent, page 51-14 Displaying a Binding Table, page 51-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 Step 2
Router(config)# ip dhcp snooping Router(config)# do show ip dhcp snooping | include Switch
Purpose Enables DHCP snooping globally. Verifies the configuration.
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.
51-9
Chapter 51 Configuring DHCP Snooping
Enabling DHCP Option-82 Data Insertion

To enable DHCP option-82 data insertion, perform this task: Command
Step 1 Step 2
Router(config)# ip dhcp snooping information option Router(config)# do show ip dhcp snooping | include 82
Purpose Enables DHCP option-82 data insertion. Verifies the configuration.
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. 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. Verifies the configuration.
Step 2
Router(config)# do show ip dhcp snooping
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)#
51-10
OL-13013-06
Chapter 51
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 Step 2
Router(config)# ip dhcp snooping verify mac-address Router(config)# do show ip dhcp snooping | include hwaddr
Purpose Enables DHCP snooping MAC address verification. Verifies the configuration.
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)#
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 RP. The DHCP snooping feature is implemented in software on the RP. To enable DHCP snooping on VLANs, perform this task: Command
Step 1 Step 2
Router(config)# ip dhcp snooping vlan {{vlan_ID [vlan_ID]} | {vlan_range} Router(config)# do show ip dhcp snooping
Purpose Enables DHCP snooping on a VLAN or VLAN range. Verifies the configuration.
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.
51-11
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 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 {type1 slot/port | port-channel number}

Note
Select only LAN ports configured with the switchport command or Layer 2 port-channel interfaces.
Step 2 Step 3
Router(config-if)# ip dhcp snooping trust Router(config-if)# do show ip dhcp snooping | begin pps 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Configures the interface as trusted. Verifies the configuration.
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)
51-12
OL-13013-06
Chapter 51
-----------------------FastEthernet5/12 Router#
------yes
---------------unlimited
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#
Configuring Spurious DHCP Server Detection

To detect and locate spurious DHCP servers, perform this task: Command
Router(config)# ip dhcp snooping detect spurious vlan range Router(config)# ip dhcp snooping detect spurious interval time Router# show ip dhcp snooping detect spurious
Purpose Enables detection of spurious DHCP servers on a specified VLAN range. Sets the interval time, the default is 30 minutes. Verifies spurious DHCP server detection.
This example shows how to configure DHCP spurious server detection on VLANs 20 to 25 and set the interval to 50 minutes:
Router# configure terminal Router(config)# ip dhcp snooping detect spurious vlan 20-25 Router(config)# ip dhcp snooping detect spurious interval 50 Router# do show ip dhcp snooping detect spurious Spurious DHCP server detection is enabled. Detection VLAN list : 20-25 Detection interval : 50 minutes Router#
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.
Step 2 Step 3
Router(config-if)# ip dhcp snooping limit rate rate Router(config-if)# do show ip dhcp snooping | begin pps
Configures DHCP packet rate limiting. Verifies the configuration.
51-13
1.
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# show ip dhcp snooping database [detail]
Purpose Configures a URL for the database agent (or file) and the related timeout values. Displays the current operating state of the database agent and statistics associated with the transfers. Clears the statistics associated with the database agent. Requests the read entries from a file at the given URL. Adds bindings to the snooping database.
Router# clear ip dhcp snooping database statistics 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
When configuring the DHCP snooping database agent, note the following information:

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:
51-14
OL-13013-06
Chapter 51
Example 1: Enabling the Database Agent, page 51-15 Example 2: Reading Binding Entries from a TFTP File, page 51-16 Example 3: Adding Information to the DHCP Snooping Database, page 51-17
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 Succeeded Time : None Last Failed Time : 17:14:25 UTC Sat Jul 7 2001 Last Failed Reason : Unable to access URL. Total Attempts Successful Transfers Successful Reads Successful Writes Media Failures : : : : : 21 0 0 0 0 Startup Failures Failed Transfers Failed Reads Failed Writes : : : : 0 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).
51-15
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.
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 Succeeded 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.
51-16
OL-13013-06
Chapter 51
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 Succeeded Time : 15:24:34 UTC Sun Jul 8 2001 Last Failed Time : None Last Failed Reason : No failure recorded. Total Attempts : 1 Startup Failures : 0 Successful Transfers : 1 Failed Transfers : 0 Successful Reads : 1 Failed Reads : 0 Successful Writes : 0 Failed Writes : 0 Media Failures : 0 Router# Router# show ip dhcp snoop bind MacAddress IpAddress Lease(sec) Type ------------------ --------------- ---------- ------------00:01:00:01:00:05 1.1.1.1 49810 dhcp-snooping 00:01:00:01:00:02 1.1.1.1 49810 dhcp-snooping 00:01:00:01:00:04 1.1.1.1 49810 dhcp-snooping 00:01:00:01:00:03 1.1.1.1 49810 dhcp-snooping 00:01:00:01:00:01 1.1.1.1 49810 dhcp-snooping Router# clear ip dhcp snoop bind Router# show ip dhcp snoop bind MacAddress IpAddress Lease(sec) Type ------------------ --------------- ---------- ------------Router#
VLAN ---512 512 1536 1024 1
Interface -------------------GigabitEthernet1/1 GigabitEthernet1/1 GigabitEthernet1/1 GigabitEthernet1/1 GigabitEthernet1/1
VLAN ----
Interface --------------------
Example 3: Adding Information to the DHCP Snooping Database

To manually add a binding to the DHCP snooping database, perform this 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) ------------------ --------------- ----------
Type -------------
VLAN ----
Interface --------------------
51-17
00:01:00:01:00:01 Router#
1.1.1.1
992
dhcp-snooping
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 51-2 describes the fields in the show ip dhcp snooping binding command output.
Table 51-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
51-18
OL-13013-06
C H A P T E R
52

This chapter describes how to configure IP Source Guard. Cisco IOS Release 12.2(33)SXH and later releases support IP Source Guard.
Note
Tip

Overview of IP Source Guard, page 52-1 Configuring IP Source Guard on the Switch, page 52-3 Displaying IP Source Guard Information, page 52-4 Displaying IP Source Binding Information, page 52-6
Overview of IP Source Guard

IP Source Guard provides source IP address filtering on a Layer 2 port to prevent a malicious host from impersonating a legitimate host by assuming the legitimate hosts IP address. The feature uses dynamic DHCP snooping and static IP source binding to match IP addresses to hosts on untrusted Layer 2 access ports. Initially, all IP traffic on the protected port is blocked except for DHCP packets. After a client receives an IP address from the DHCP server, or after static IP source binding is configured by the administrator, all traffic with that IP source address is permitted from that client. Traffic from other hosts is denied. This filtering limits a hosts ability to attack the network by claiming a neighbor hosts IP address. IP Source Guard is a port-based feature that automatically creates an implicit port access control list (PACL).
52-1
Chapter 52 Overview of IP Source Guard
IP Source Guard Interaction with VLAN-Based Features

Use the access-group mode command to specify how IP Source Guard interacts with VLAN-based features (such as VACL and Cisco IOS ACL and RACL). In prefer port mode, if IP Source Guard is configured on an interface, IP Source Guard overrides other VLAN-based features. If IP Source Guard is not configured on the interface, other VLAN-based features are merged in the ingress direction and applied on the interface. In merge mode, IP Source Guard and VLAN-based features are merged in the ingress direction and applied on the interface. This is the default access-group mode.
Channel Ports
IP Source Guard is supported on the main Layer 2 channel interface but not on the port members. When IP Source Guard is applied on the main Layer 2 channel interface, it is applied to all the member ports in the channel.
Trunk Ports
IP Source Guard is not supported on trunk ports.
Layer 2 and Layer 3 Port Conversion

When an IP Source Guard policy is applied to a Layer 2 port, and then you change that port to be a Layer 3 port, the IP Source Guard policy no longer functions but is still present in the configuration. When the port is changed back to a Layer 2 port, IP Source Guard policy becomes effective again.
IP Source Guard and Voice VLAN

IP Source Guard is supported on a Layer 2 port that belongs to a voice VLAN. To configure the voice VLAN for the Layer 2 port, use the switchport voice vlan command. For IP Source Guard to be active on the voice VLAN, DHCP snooping must be enabled on the voice VLAN. In merge mode, the IP Source Guard feature is merged with VACL and Cisco IOS ACL configured on the access VLAN.
IP Source Guard and Web-Based Authentication

In releases earlier than Cisco IOS Release 12.2(33)SXI2, configuring IP Source Guard and web-based authentication on the same interface is not supported. In Cisco IOS Release 12.2(33)SXI2 and later releases, you can configure IP Source Guard and web-based authentication on the same interface. If DHCP snooping is also enabled on the access VLAN, you must enter the mls acl tcam override dynamic dhcp-snooping command in global configuration mode to avoid conflicts between the two features. Other VLAN-based features are not supported when IP Source Guard and web-based authentication are combined.
52-2
OL-13013-06
Chapter 52
Configuring IP Source Guard Configuring IP Source Guard on the Switch
IP Source Guard Restrictions

Because the IP Source Guard feature is supported only in hardware, IP Source Guard is not applied if there are insufficient hardware resources available. These hardware resources are shared by various other ACL features that are configured on the system. The following restrictions apply to IP Source Guard:

Only supported on ingress Layer 2 ports. Only supported in hardware. Not applied to any traffic that is processed in software. Does not support filtering of traffic based on MAC address. Is not supported on private VLANs.
Configuring IP Source Guard on the Switch

To enable IP Source Guard, perform this task: Command
Step 1
Router(config)# ip dhcp snooping
Purpose Enables DHCP snooping globally. You can use the no keyword to disable DHCP snooping. Enables DHCP snooping on your VLANs. Selects the interface to be configured. Use the no keyword to configure the interface as untrusted. Enables IP Source Guard, source IP address filtering on the port. The following are the command parameters:
Router(config)# ip dhcp snooping vlan number [number] Router(config)# interface interface-name Router(config-if)# no ip dhcp snooping trust
Router(config-if)# ip verify source vlan dhcp-snooping [port-security]
vlan applies the feature to only specific VLANs on the interface. The dhcp-snooping option applies the feature to all VLANs on the interface that have DHCP snooping enabled. port-security enables MAC address filtering. This feature is currently not supported.

Router(config-if)# exit Router(config)# ip source binding mac-address vlan vlan-id ip-address interface interface-name Router(config)# end Router# show ip verify source [interface interface-name]
Returns to global configuration mode. (Optional) Configures a static IP binding on the port. Exits configuration mode. Verifies the configuration.
52-3
Chapter 52 Displaying IP Source Guard Information
Note
The static IP source binding can only be configured on a Layer 2 port. If you enter the ip source binding vlan interface command on a Layer 3 port, you receive this error message:
Static IP source binding can only be configured on switch port.
The no keyword deletes the corresponding IP source binding entry. This command requires an exact match of all the required parameters in order for the deletion to be successful.
This example shows how to enable per-Layer 2 port IP Source Guard on VLANs 10 through 20:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# ip dhcp snooping Router(config)# ip dhcp snooping vlan 10 20 Router(config)# interface fa6/1 Router(config-if)# switchport mode access Router(config-if)# switchport access vlan 10 Router(config-if)# no ip dhcp snooping trust Router(config-if)# ip verify source vlan dhcp-snooping Router(config-if)# end Router# show ip verify source interface f6/1 Interface Filter-type Filter-mode IP-address Mac-address --------- ----------- ----------- --------------- ----------------Fa6/1 ip active 10.0.0.1 Fa6/1 ip active deny-all Router#
Vlan ---------10 11-20
The output shows that there is one valid DHCP binding to VLAN 10. This example shows how to configure an interface to use prefer port mode:
Router# configure terminal Router(config)# interface gigabitEthernet 6/1 Router(config-if)# access-group mode prefer port
This example shows how to configure an interface to use merge mode:

Router# configure terminal Router(config)# interface gigabitEthernet 6/1 Router(config-if)# access-group mode merge
Displaying IP Source Guard Information

To display IP Source Guard PACL information for all interfaces on a switch, perform this task: Command
Router# show ip verify source [interface interface-name]
Purpose Displays IP Source Guard PACL information for all interfaces on a switch or for a specified interface.
This example shows that DHCP snooping is enabled on VLAN 10 through 20, interface fa6/1 is configured for IP filtering, and there is an existing IP address binding 10.0.01 on VLAN 10:
Router# show ip verify source interface fa6/1 Interface Filter-type Filter-mode IP-address --------- ----------- ----------- --------------fa6/1 ip active 10.0.0.1 Mac-address -------------Vlan --------10
52-4
OL-13013-06
Chapter 52
Configuring IP Source Guard Displaying IP Source Guard Information
fa6/1
ip
active
deny-all
11-20
Note
The second entry shows that a default PACL (deny all IP traffic) is installed on the port for those snooping-enabled VLANs that do not have a valid IP source binding. This example shows the displayed PACL information for a trusted port:
Interface --------fa6/2 Filter-type ----------ip Filter-mode IP-address ----------- --------------inactive-trust-port Mac-address -------------Vlan ---------
This example shows the displayed PACL information for a port in a VLAN not configured for DHCP snooping:
Interface --------fa6/3 Filter-type ----------ip Filter-mode IP-address ----------- --------------inactive-no-snooping-vlan Mac-address -------------Vlan ---------
This example shows the displayed PACL information for a port with multiple bindings configured for an IP/MAC filtering:
Interface --------fa6/4 fa6/4 fa6/4 Filter-type ----------ip ip ip Filter-mode ----------active active active IP-address --------------10.0.0.2 11.0.0.1 deny-all Mac-address -------------aaaa.bbbb.cccc aaaa.bbbb.cccd deny-all Vlan --------10 11 12-20
This example shows the displayed PACL information for a port configured for IP/MAC filtering but not for port security:
Interface --------fa6/5 fa6/5 Filter-type ----------ip ip Filter-mode ----------active active IP-address --------------10.0.0.3 deny-all Mac-address -------------permit-all permit-all Vlan --------10 11-20
Note
The MAC address filter shows permit-all because port security is not enabled, so the MAC filter cannot apply to the port/VLAN and is effectively disabled. Always enable port security first. This example shows an error message when you enter the show ip verify source command on a port that does not have an IP source filter mode configured:
Router# show ip verify source interface fa6/6 IP Source Guard is not configured on the interface fa6/6.
This example shows how to display all interfaces on the switch that have IP Source Guard enabled:
Router# show ip verify source Interface Filter-type Filter-mode IP-address --------- ----------- ----------- --------------fa6/1 ip active 10.0.0.1 fa6/1 ip active deny-all fa6/2 ip inactive-trust-port fa6/3 ip inactive-no-snooping-vlan fa6/4 ip active 10.0.0.2 fa6/4 ip active 11.0.0.1 fa6/4 ip active deny-all fa6/5 ip active 10.0.0.3 fa6/5 ip active deny-all Mac-address -------------Vlan --------10 11-20
aaaa.bbbb.cccc aaaa.bbbb.cccd deny-all permit-all permit-all
10 11 12-20 10 11-20
52-5
Chapter 52 Displaying IP Source Binding Information
Displaying IP Source Binding Information

To display all IP source bindings configured on all interfaces on a switch, perform this task: Command
Router# show ip source binding [ip-address] [mac-address] [dhcp-snooping | static] [vlan vlan-id] [interface interface-name]
Purpose Displays IP source bindings using the optional specified display filters. The dhcp-snooping filter displays all VLANs on the interface that have DHCP snooping enabled. This example shows how to display all IP source bindings configured on all interfaces on the switch.
Router# show ip source binding MacAddress IpAddress ------------------ --------------00:02:B3:3F:3B:99 55.5.5.2 00:00:00:0A:00:0B 11.0.0.1 Router# Lease(sec) ---------6522 infinite Type ------------dhcp-snooping static VLAN ---10 10 Interface -------------------FastEthernet6/10 FastEthernet6/10
Table 52-1 describes the fields in the show ip source binding command output.
Table 52-1 show ip source 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; static bindings configured from CLI to dynamic binding learned from DHCP snooping VLAN number of the client interface Interface that connects to the DHCP client host
Tip
52-6
OL-13013-06
C H A P T E R
53

This chapter describes how to configure dynamic Address Resolution Protocol (ARP) inspection (DAI) in Cisco IOS Release 12.2SX.
Note
Tip

Understanding DAI, page 53-1 Default DAI Configuration, page 53-5 DAI Configuration Guidelines and Restrictions, page 53-6 Configuring DAI, page 53-6 DAI Configuration Samples, page 53-15
Understanding DAI
These sections describe how DAI helps prevent ARP spoofing attacks:

Understanding ARP, page 53-2 Understanding ARP Spoofing Attacks, page 53-2 Understanding DAI and ARP Spoofing Attacks, page 53-2
53-1
Chapter 53 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 53-1 shows an example of ARP cache poisoning.
Figure 53-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 for 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.
53-2
111750
OL-13013-06
Chapter 53
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 53-8). The switch logs dropped packets (see the Logging of Dropped Packets section on page 53-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 53-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 53-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.
53-3
Chapter 53 Understanding DAI
Figure 53-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 53-20.
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 53-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.
53-4
130194
OL-13013-06
Chapter 53
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 53-12.
Default DAI Configuration

Table 53-1 shows the default DAI configuration.
Table 53-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.
53-5
Chapter 53 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 51, 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 53-7 Configuring the DAI Interface Trust State, page 53-8 Applying ARP ACLs for DAI Filtering, page 53-8
53-6
OL-13013-06
Chapter 53
Configuring Dynamic ARP Inspection Configuring DAI
Configuring ARP Packet Rate Limiting, page 53-9 Enabling DAI Error-Disabled Recovery, page 53-10 Enabling Additional Validation, page 53-11 Configuring DAI Logging, page 53-12 Displaying DAI Information, page 53-14
Enabling DAI on VLANs

To enable DAI on VLANs, perform this task: Command
Router# configure terminal Router(config)# ip arp inspection vlan {vlan_ID | vlan_range} Router(config-if)# do show ip arp inspection vlan {vlan_ID | vlan_range} | begin Vlan
Purpose Enters global configuration mode. Enables DAI on VLANs. Verifies the configuration.
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 Vlan ---10 11 12 15 ACL Logging ----------Deny Deny Deny Deny DHCP Logging -----------Deny Deny Deny Deny
53-7
Chapter 53 Configuring DAI
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 53-12. To configure the DAI interface trust state, perform this task: Command
Router# configure terminal Router(config)# interface {type1 slot/port | port-channel number} Router(config-if)# ip arp inspection trust Router(config-if)# do show ip arp inspection interfaces 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Purpose Enters global configuration mode. Specifies the interface connected to another switch, and enter interface configuration mode. Configures the connection between switches as trusted. Verifies the DAI configuration.
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 command reference for information about the arp access-list command. 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.
53-8
OL-13013-06
Chapter 53
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 ACL Logging DHCP Logging ------------------------10 Deny Deny 11 Deny Deny 12 Deny Deny 15 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. 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. Verifies the configuration.
Router(config-if)# ip arp inspection limit {rate pps [burst interval seconds] | none} Router(config-if)# do show ip arp inspection interfaces 1. type = fastethernet, gigabitethernet, or tengigabitethernet
53-9
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 53-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
Enabling DAI Error-Disabled Recovery

To enable DAI error-disabled recovery, perform this task: Command
Router# configure terminal Router(config)# errdisable recovery cause arp-inspection Router(config)# do show errdisable recovery | include Reason|---|arp-
Purpose Enters global configuration mode. (Optional) Enables DAI error-disabled recovery. Verifies the configuration.
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
53-10
OL-13013-06
Chapter 53
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
Router# configure terminal Router(config)# ip arp inspection validate {[dst-mac] [ip] [src-mac]} Router(config)# do show ip arp inspection | include abled$
Purpose Enters global configuration mode. (Optional) Enables additional validation. Verifies the configuration.
The additional validations do the following:
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. 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-mac and dst-mac validations, and a second ip arp inspection validate command enables IP validation only, the src-mac and dst-mac validations are disabled as a result of the second command.
When enabling additional validation, note the following information:

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
53-11
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
Configuring DAI Logging

These sections describe DAI logging:

DAI Logging Overview, page 53-12 Configuring the DAI Logging Buffer Size, page 53-13 Configuring the DAI Logging System Messages, page 53-13 Configuring DAI Log Filtering, page 53-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.
53-12
OL-13013-06
Chapter 53
Configuring the DAI Logging Buffer Size

To configure the DAI logging buffer size, perform this task: Command
Router# configure terminal Router(config)# ip arp inspection log-buffer entries number Router(config)# do show ip arp inspection log | include Size
Purpose Enters global configuration mode. Configures the DAI logging buffer size (range is 0 to 1024). Verifies the configuration.
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
Configuring the DAI Logging System Messages

To configure the DAI logging system messages, perform this task: Command
Router# configure terminal Router(config)# ip arp inspection log-buffer logs number_of_messages interval length_in_seconds Router(config)# do show ip arp inspection log
Purpose Enters global configuration mode. Configures the DAI logging buffer. Verifies the configuration.
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.
53-13
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
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 permitLogs 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 53-2.
Table 53-2 Commands for Displaying DAI Information
Command show arp access-list [acl_name]
Description Displays detailed information about ARP ACLs.
53-14
OL-13013-06
Chapter 53
Configuring Dynamic ARP Inspection DAI Configuration Samples
Table 53-2
Commands for Displaying DAI Information (continued)
Command
Description
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).
To clear or display DAI statistics, use the privileged EXEC commands in Table 53-3.
Table 53-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 53-4:
Table 53-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 53-16 Sample Two: One Switch Supports DAI, page 53-20
53-15
Chapter 53 DAI Configuration Samples
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 53-2 on page 53-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 51, Configuring DHCP Snooping. This configuration does not work if the DHCP server is moved from Switch A to a different location. 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
53-16
OL-13013-06
Chapter 53
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
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 Forwarded Dropped DHCP Drops ACL Drops
53-17
---1 Vlan ---1
--------2 DHCP Permits -----------2
------2 ACL Permits ----------0
---------2
---------0
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
Rate (pps) ---------15
53-18
OL-13013-06
Chapter 53
Gi1/2 Gi3/1 Gi3/2 Fa3/3 Fa3/4 Fa3/5 Fa3/6 Fa3/7 <output truncated> SwitchB#
Untrusted Untrusted Untrusted Trusted Untrusted Untrusted Untrusted Untrusted
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) ------------------ --------------- ---------00:01:00:01:00:01 1.1.1.1 4995 SwitchB# Type ------------dhcp-snooping VLAN ---1 Interface -------------------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:
SwitchB# show ip arp inspection statistics vlan 1 Vlan ---1 Vlan ---1 Forwarded --------1 DHCP Permits -----------1 Dropped ------0 ACL Permits ----------0 DHCP Drops ---------0 ACL Drops ---------0
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:

SwitchB# show ip arp inspection statistics vlan 1
53-19
Vlan ---1 Vlan ---1
Forwarded --------1 DHCP Permits -----------1
Dropped ------1 ACL Permits ----------0
DHCP Drops ---------1
ACL Drops ---------0
Sample Two: One Switch Supports DAI

This procedure shows how to configure DAI when Switch B shown in Figure 53-2 on page 53-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 ---Configuration ------------Operation --------ACL Match --------Static ACL ----------
53-20
OL-13013-06
Chapter 53
1 Vlan ---1 SwitchA#
Enabled ACL Logging ----------Deny
Active DHCP Logging -----------Deny
H2
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 --------------Fa6/3 Switch# Trust State ----------Untrusted Rate (pps) ---------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
53-21
53-22
OL-13013-06
C H A P T E R
54

This chapter describes how to configure the traffic storm control feature in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Traffic Storm Control, page 54-1 Default Traffic Storm Control Configuration, page 54-3 Configuration Guidelines and Restrictions, page 54-3 Configuring Traffic Storm Control, page 54-4
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 it 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). Traffic storm control monitors the level of each traffic type for which you enable traffic storm control in 1-second traffic storm control intervals.
54-1
Chapter 54 Understanding Traffic Storm Control
In all releases, and by default in Release 12.2(33)SXJ and later releases, 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. Release 12.2(33)SXJ and later releases support these configurable traffic storm control optional actions:
ShutdownWhen a traffic storm occurs, traffic storm control puts the port into the error-disabled state. To reenable ports, use the error-disable detection and recovery feature or the shutdown and no shutdown commands. TrapWhen a traffic storm occurs, traffic storm control generates an SNMP trap.
Figure 54-1 shows the broadcast traffic patterns on a LAN interface over a specific 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 54-1 Broadcast Suppression
Total number of broadcast packets or bytes
Threshold
T1
T2
T3
T4
T5
Time
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 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 the threshold is reached, traffic storm control 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.
54-2
S5706
OL-13013-06
Chapter 54
Configuring Traffic Storm Control Default Traffic Storm Control Configuration
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.
Default Traffic Storm Control Configuration

Traffic storm control is disabled by default.

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
54-3
Chapter 54 Configuring Traffic Storm Control
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.

These sections describe how to configure traffic storm control:

Enabling Traffic Storm Control, page 54-4 Configuring the Traffic Storm Control Shutdown Mode, page 54-6 Configuring Traffic Storm Control SNMP Traps, page 54-6
Enabling Traffic Storm Control

To enable traffic storm control on an interface, perform this task: Command
Step 1 Step 2
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. 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.
Router(config-if)# storm-control broadcast level level[.level]
Step 3
Router(config-if)# storm-control multicast level level[.level]
Note
The storm-control multicast command is supported only on Gigabit and 10-Gigabit Ethernet interfaces.
Step 4
Router(config-if)# storm-control unicast level level[.level]
Note
The storm-control unicast command is supported only on Gigabit and 10-Gigabit Ethernet interfaces.
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.
Step 5 Step 6
Router(config-if)# end Router# show running-config interface 1.
type = fastethernet, fastethernet, gigabitethernet, or tengigabitethernet
When configuring the traffic storm control level, note the following information:

You can configure traffic storm control on the port channel interface of an EtherChannel. 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.
54-4
OL-13013-06
Chapter 54
Configuring Traffic Storm Control Configuring Traffic Storm Control
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 WS-X6748-GE-TX 100Mbps ports: 0.03 percent or less WS-X6716-10G-3C, WS-X6716-10G-3CXL Oversubscription Mode: 0.29 percent or less WS-X6716-10T-3C, WS-X6716-10T-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. All routers in a VLAN see copies of all broadcast traffic. To avoid high RP CPU utilization caused by a high volume of broadcast traffic, the threshold typically is set to a very low value; for example, less than 1 percent on a Gigabit Ethernet port. You can use the Top N feature to periodically measure the peak broadcast traffic levels of the selected ports. If you have a specific required broadcast traffic level (for example, from an application), you can use that requirement as the basis of the threshold. Base the suppression threshold on your data, plus some additional capacity. For example, if the peak broadcast traffic that is acceptable for a port is 1 percent, a threshold of 1.5 percent might be appropriate. The faster the port speed, the less additional capacity is required. Use the show interfaces counters storm-control command to monitor the effect of the values that you configure, and increase the configured threshold if the TotalSuppDiscards column shows nonzero values. 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 0.5 percent:
Router# configure terminal Router(config)# interface gigabitethernet 3/16 Router(config-if)# storm-control multicast level 0.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 0.5 storm-control multicast level 0.5 spanning-tree portfast edge end
54-5
Chapter 54 Configuring Traffic Storm Control
Router# configure terminal Router(config)# interface gigabitethernet 4/10 Router(config-if)# storm-control unicast level 0.7 Router(config-if)# end Router# show interfaces gig4/10 counters storm-control Port Gi4/10 Router# UcastSupp % 00.70 McastSupp % 00.70 BcastSupp % 00.70 TotalSuppDiscards 0
Configuring the Traffic Storm Control Shutdown Mode

To configure the traffic storm control shutdown mode on an interface, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port} |
Selects an interface to configure. (Optional) Configures traffic storm control to error-disable ports when a traffic storm occurs.

Router(config-if)# storm-control action shutdown
Enter the no storm-control action shutdown command to revert to the default action (drop). Use the error disable detection and recovery feature, or the shutdown and no shutdown commands to reenable ports.
Step 3 Step 4
Router(config-if)# end Router# show running-config interface 1.
type = fastethernet, fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to configure the traffic storm control shutdown mode on Gigabit Ethernet interface 3/16:
Router# configure terminal Router(config)# interface gigabitethernet 3/16 Router(config-if)# storm-control action shutdown Router(config-if)# end
Configuring Traffic Storm Control SNMP Traps

To configure traffic storm control SNMP traps, perform this task: Command
1
Purpose
slot/port} |
Selects an interface to configure. Configures traffic storm control to generate an SNMP trap when a storm is detected on the port. Exits interface configuration mode.
Router(config-if)# storm-control action trap
Router(config-if)# exit
54-6
OL-13013-06
Chapter 54
Configuring Traffic Storm Control Displaying Traffic Storm Control Settings
Command
Step 4
Router(config)# snmp-server enable traps storm-control trap-rate value
Purpose Configures the maximum number of storm-control traps sent per minute. The range is 0 to 1000; the default is 0 (no limit is imposed; a trap is sent at every occurrence). Exits configuration mode. Verifies the interface configuration.
Step 5 Step 6
Router(config)# end Router# show running-config interface 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to configure Gigabit Ethernet interface 3/16 to send an SNMP trap when a traffic storm is detected on the port and how to revert traffic storm control trap rate limiting to the default value:
Router# configure terminal Router(config)# interface gigabitethernet 3/16 Router(config-if)# storm-control action trap Router(config-if)# exit Router(config)# snmp-server enable traps storm-control trap-rate 0 Router(config)# end
Displaying Traffic Storm Control Settings

To display traffic storm control information, use the commands described in Table 54-1.
Table 54-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. type = fastethernet, gigabitethernet, or tengigabitethernet
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.
Note
The show interfaces [{interface_type slot/port} | {port-channel number}] counters command does not display the discard count. You must the storm-control keyword to display the discard count.
Tip
54-7
Chapter 54 Displaying Traffic Storm Control Settings
54-8
OL-13013-06
C H A P T E R
55
Configuring Unknown Unicast and Multicast Flood Control

This chapter describes how to configure the unknown unicast flood blocking (UUFB), unknown multicast flood blocking (UMFB), and unknown unicast flood rate-limiting (UUFRL) features in Cisco IOS Release 12.2SX.
Note
Tip
Understanding Unknown Traffic Flood Control

By default, unknown unicast and multicast traffic is flooded to all Layer 2 ports in a VLAN. You can use the UUFB, UMFB, and UUFRL 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. The UUFRL feature applies a rate limit globally to unknown unicast traffic on all VLANs.
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.
55-1
Chapter 55 Configuring UUFB or UMFB
Configuring UUFB or UMFB

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 = 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
Configuring UUFRL
Note
The UUFRL feature is available only with the Supervisor Engine 720-10GE. To configure UUFRL, perform this task:
Command
Step 1 Step 2
Router# configure terminal Router(config)# mls rate-limit layer2 unknown rate-in-pps [burst-size] Router(config)# exit
Purpose Enters global configuration mode. Enables UUFRL and sets the maximum packet rate. (Optional) Specify a burst size limit. Exits configuration mode.
Step 3
When you configure UUFRL, note the following information:
When unknown unicast flood rate-limiting (UUFRL) is enabled, per-VLAN learning must be enabled on all the Layer 3 routed ports, otherwise, any unicast flooded packet coming into a routed port will also be rate-limited by UUFRL. For the rate-in-pps value:
The range is 10 through 1,000,000 (entered as 1000000). There is no default value.
55-2
OL-13013-06
Chapter 55
Configuring Unknown Unicast and Multicast Flood Control Configuring UUFRL
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 UUFRL with a rate limit of 1000 pps with a burst of 20 packets:
Router# configure terminal Router(config)# mls rate-limit layer2 unknown 1000 20 Router(config)# exit
Tip
55-3
Chapter 55 Configuring UUFRL
55-4
OL-13013-06
C H A P T E R
56
Configuring Network Admission Control

This chapter describes how to configure Network Admission Control (NAC) in Cisco IOS Release 12.2SX.
Note
Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html The Network Admission Control feature module at this URL: http://www.cisco.com/en/US/docs/ios/12_3t/12_3t8/feature/guide/gt_nac.html The Cisco IOS Security Command Reference, Release 12.3 at this URL: http://www.cisco.com/en/US/docs/ios/12_3/security/command/reference/secur_r.html
Tip

Understanding NAC, page 56-1 Configuring NAC, page 56-12 Monitoring and Maintaining NAC, page 56-23
Understanding NAC
These sections describe NAC:

NAC Overview, page 56-2 NAC Device Roles, page 56-3 AAA Down Policy, page 56-4
56-1
Chapter 56 Understanding NAC
NAC IP Validation, page 56-4 NAC and Switchover, page 56-12
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. Release 12.2(18)SXF2 and later releases supports NAC Layer 2 IP validation. Release 12.2(33)SXH and rebuilds support NAC Layer 3 IP validation. Release 12.2(33)SXI and later releases do not support NAC Layer 3 IP validation. NAC Layer 2 IP (also known as LAN Port IP) operates on Layer 2 ports on edge switches. NAC Layer 2 IP validation 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 additional information about IEEE 802.1x, see Chapter 57, Configuring IEEE 802.1X Port-Based Authentication. For a complete list of devices that support NAC, see the Release Notes for Network Admission Control, Release 2.1, at this URL: http://www.cisco.com/en/US/docs/security/nac/2.1/release_notes/NAC21RN.html NAC Layer 3 IP (also known as NAC Gateway IP) operates on Layer 3 interfaces on distribution layer switches. An advantage of NAC Layer 3 IP is that access layer switches do not require any changes to use the NAC feature.
Note
The NAC feature applies access controls only to IPv4 traffic. NAC does not restrict Layer 2-bridged traffic. NAC provides posture validation for routed traffic. 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.
56-2
OL-13013-06
Chapter 56
Configuring Network Admission Control Understanding NAC
NAC Device Roles

The devices in the network have specific roles when you use NAC as shown in Figure 56-1.
Figure 56-1 Posture Validation Devices
PC
Workstation
Switch
Cisco Secure ACS
Server
Network Access Device
Authentication Server (RADIUS)
Clients running the Cisco Trust Agent software
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. The host, which is running the Cisco Trust Agent (CTA) 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.
For NAC Layer 2 IP, the device is connected to an access port through a direct connection, an
IP phone, or a wireless access point.

For NAC Layer 3 IP, the device is one or more Layer 3 hops away from the switch.
The CTA software is also referred to as the posture agent or the antivirus client.
SwitchThis is a network access device, which provides validation services and policy enforcement.
Edge switchThis is the network access device that provides NAC Layer 2 IP 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.
Distribution switchThis is the NAC gateway, which provides validation services and policy
enforcement at the Layer 3 network edge and controls access to the Layer 3 network based on the access policy of the client. 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. The switch relays Extensible Authentication Protocol (EAP) messages between the endpoints and the authentication server.
92734
56-3
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. 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. When the AAA policy is applied, the session state is maintained as AAA DOWN.
NAC IP Validation
The following sections describe NAC IP validation:

NAC Layer 2 IP Validation, page 56-4 NAC Layer 3 IP Validation, page 56-5 Posture Validation, page 56-6 Cisco Secure ACS and AV Pairs, page 56-7 Audit Servers, page 56-8 ACLs, page 56-9 NAC Timers, page 56-9
NAC Layer 2 IP Validation

You can use NAC Layer 2 IP on the access port of 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 access port through a direct connection, an IP phone, or a wireless access point, as shown in Figure 56-2.
56-4
OL-13013-06
Chapter 56
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 56-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
NAC Layer 2 IP supports the posture validation of multiple hosts on the same Layer 2 port, as shown in Figure 56-2. When you enable NAC Layer 2 IP validation on a Layer 2 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.
NAC Layer 3 IP Validation

The gateway IP feature supports two types of posture validation (PV) triggers:

Intercept ACLs ARP-based triggers (SVI interfaces only)
Intercept ACLs are configured to intercept inbound traffic from the clients and initiate PV if the traffic matches the ACL. If the IP admission rule configured on an interface does not have an associated intercept ACL, the gateway uses ARP or DHCP events to trigger posture validation on the interface. When the gateway learns a new client in its ARP cache, it initiates PV with the client. Using the ARP-based triggers reduces ACL TCAM usage, but it is only valid for clients that are one Layer 3 hop away from the gateway. Therefore, you can configure only SVIs (and not router ports) to have IP admission rules without an intercept ACL.
92735
56-5
Posture Validation
If only dynamic ARP inspection is enabled on the access VLAN assigned to a Layer 2 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.
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.
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 CTA. 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 CTA, 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
56-6
OL-13013-06
Chapter 56
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 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 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 Layer 2 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.
Cisco Secure ACS and AV Pairs

When NAC 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.
56-7
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 = 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 traffic but not for both at the same time. This situation occurs because the Cisco IOS software 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 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 56-3 shows how audit servers fit into the typical topology.
Figure 56-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
56-8
OL-13013-06
Chapter 56
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 occurs 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 server 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 IP validation on an interface, you must also configure a default security ACL on the same interface. The default ACL is applied 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 Layer 2 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. If there is no default ACL configured, the traffic is permitted. If the Cisco Secure ACS sends the switch a downloadable ACL that specifies a redirect URL as a policy-map action, this ACL takes precedence over the default ACL already configured on the Layer 2 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 56-9 Idle Timer, page 56-10 Retransmission Timer, page 56-11 Revalidation Timer, page 56-11 Status-Query Timer, page 56-11
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.
56-9
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 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 or Layer 3 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 a 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 active entries in the IP device tracking table but limits the number of inactive entries. When the table reaches the table size limit, the switch removes the inactive 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. The table size limit is 2048.
56-10
OL-13013-06
Chapter 56
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 applied 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.
56-11
Chapter 56 Configuring NAC
NAC and Switchover

When RPR mode redundancy is configured, a switchover causes the loss of all information about currently postured hosts. All sessions will be revalidated. Users will be unvalidated and may see service disruption. With Release 12.2(33)SXH and later releases, if you are using SSO mode redundancy, you can enter the ip admission ha command to enable host session table synchronization to the standby supervisor engine. When the high availability feature is enabled, established postured hosts do not need to be revalidated when a switchover occurs, because they will not see any disruption from the switchover. Posture sessions that were not yet established prior to the SSO will need to be revalidated after the switchover.
Configuring NAC
The following sections describe how to configure NAC:

Default NAC Configuration, page 56-12 NAC IP Guidelines, Limitations, and Restrictions, page 56-12 Configuring NAC IP Validation, page 56-14 Configuring EAPoUDP, page 56-18 Configuring Identity Profiles and Policies, page 56-18 Configuring NAC High Availability, page 56-19 Configuring a NAC AAA Down Policy, page 56-20
Default NAC Configuration

By default, NAC IP validation is disabled.
NAC IP Guidelines, Limitations, and Restrictions

The NAC feature applies access controls only to IPv4 traffic. NAC does not restrict Layer 2 bridged traffic. IPv6 traffic does not trigger posture validation and NAC IP does not apply access policies to IPv6 traffic. Default ACLs must permit EAPoUDP traffic for NAC IP to function. DHCP traffic must be permitted in the interface default ACL and the host policy for DHCP snooping to function. If you want to forward 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.
56-12
OL-13013-06
Chapter 56
Configuring Network Admission Control Configuring NAC
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. Layer 2 IP is not allowed if the parent VLAN of the port has VACL capture 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 Layer 2 port to which hosts are connected. NAC Layer 2 IP is not supported if the Layer 2 port 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 Layer 2 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 Layer 2 port with ACEs permitting DNS packets. If NAC Layer 2 IP validation is configured on a Layer 2 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. If dynamic ARP inspection is enabled on the ingress VLAN, the switch initiates posture validation only after the ARP packets are validated. 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 Layer 2 access VLAN. This configuration allows you to bypass the redirection of the HTTP traffic destined for the remediation servers.
56-13
NAC Layer 3 IP Guidelines, Limitations, and Restrictions

When configuring NAC Layer 3 IP validation, follow these guidelines, limitations, and restrictions:

Only Release 12.2(33)SXH and rebuilds support NAC Layer 3 IP validation. Release 12.2(33)SXI and later releases do not support NAC Layer 3 IP validation. NAC Gateway feature is supported on Supervisor Engine 720 and Supervisor Engine 32-8GE. For ARP-based trigger, the GWIP detects host presence using the ARP probing mechanism. When you enable NAC Gateway IP validation on an interface, you must also configure a default Cisco IOS ACL on the interface. 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 Cisco IOS ACL on the interface. 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 Layer 2 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 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
Router(config)# mls rate-limit layer 2 ip ip-admission pps (burst) or Router(config)# mls rate-limit unicast ip features pps (burst)
For a Layer 2 port, enables the rate limiting of the IP admission traffic to the CPU. For a Layer 3 port, enables the rate limiting of the IP admission traffic to the CPU.
56-14
OL-13013-06
Chapter 56
Command
Step 4
Router(config)# access-list access_list_number {deny | permit} source [source_wildcard] [log]
Purpose 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.
Router(config)# interface interface_id Router(config)# ip access-group {access_list_number | name} in Router(config)# 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 name 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.
56-15
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
Router(config)# radius-server host {hostname | ip_address} key string
(Optional) Configures the RADIUS server parameters. For the hostname or 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.

Step 14
Router(config)# radius-server attribute 8 include-in-access-req
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.
Step 17 Step 18
Router(config)# eou logging Router(config)# end
(Optional) Enables EAPoUDP system logging events. Returns to privileged EXEC mode.
56-16
OL-13013-06
Chapter 56
Command
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
Purpose 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.
When configuring NAC IP validation, note the following guidelines:
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. If IEEE 802.1x authentication in single-host mode and NAC Layer 2 IP validation are configured on a Layer 2 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.
This example shows how to configure NAC Layer 2 IP validation on a switch interface:
Router# configure terminal Router(config)# ip admission name 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 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
56-17
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
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.
Router(config-identity-policy)# access-group access_group Router(config)# identity profile eapoudp
56-18
OL-13013-06
Chapter 56
Command
Step 5
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
Purpose 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# 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 NAC High Availability

To configure IP admission high availability, perform this task: Command
Router# configure terminal Router(config)# ip admission ha Router(config)# ip admission ha update update_interval
Purpose Enters global configuration mode. Enables IP admission high availability. Defines how often the active supervisor engine sends synchronization updates to the standby. The interval has a range of 30 to 60 seconds. Displays the statistics related to session synchronization. (Optional) Clears the statistics related to session synchronization.
Step 4 Step 5
Router# show ip admission ha stats Router# clear ip admission ha stats
Note
You cannot enable the IP admission high availability feature if there are active Webauth or Posture sessions. To disable IP admission high availability from the switch, use the no ip admission ha configuration command.
56-19
This example shows how to configure IP admission high availability:

Router# configure terminal Router(config)# ip admission ha Router(config)# ip admission ha update 50 Router(config)# end Router(config)# clear ip admission ha stats Router(config-identity-prof)# show ip admission ha stats
Configuring a NAC AAA Down Policy

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 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 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.
Step 7 Step 8
Router(config)# exit Router(config)# aaa new-model
Returns to global configuration mode. Enables AAA.
56-20
OL-13013-06
Chapter 56
Command
Step 9
Router(config)# aaa authentication eou default group radius
Purpose 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.
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} 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
(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.
Step 15
Router(config)# radius-server vsa send authentication
Configures the network access server to recognize and use vendor-specific attributes.
56-21
Command
Step 16 Step 17
Router(config)# radius-server dead-criteria {tries | time} value Router(config)# eou logging
Purpose 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.
Router(config)# end Router# show ip admission {[cache] [configuration] [eapoudp]} Router# show ip device tracking {all | interface interface-id | ip ip-address | mac mac-address} Router(# copy running-config startup-config
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.
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
56-22
OL-13013-06
Chapter 56
Configuring Network Admission Control Monitoring and Maintaining NAC
! 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 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
Monitoring and Maintaining NAC

You can perform the tasks in these sections to monitor and maintain NAC:

Clearing Table Entries, page 56-23 Displaying NAC Information, page 56-23
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.
56-23
Chapter 56 Monitoring and Maintaining NAC
Tip
56-24
OL-13013-06
CH A P T E R
57

This chapter describes how to configure IEEE 802.1X port-based authentication in Cisco IOS Release 12.2SX to prevent unauthorized devices (clients) from gaining access to the network.
Note

Understanding 802.1X Port-Based Authentication, page 57-1 802.1X Authentication Feature Configuration Guidelines, page 57-28 Configuring 802.1X Port-Based Authentication, page 57-32 Displaying Authentication Status and Information, page 57-61
Understanding 802.1X Port-Based Authentication

The IEEE 802.1X standard defines a client and 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 the role of 802.1X port-based authentication as a part of a system of authentication, authorization, and accounting (AAA):

Understanding 802.1X Device Roles, page 57-2 Understanding the Port-based Authentication Process, page 57-3 Authentication Initiation and Message Exchange, page 57-6 Ports in Authorized and Unauthorized States, page 57-8
57-1
Chapter 57 Understanding 802.1X Port-Based Authentication
802.1X Host Modes, page 57-9 Using 802.1X Authentication with DHCP Snooping, page 57-11 Understanding 802.1X Accounting, page 57-12 Using 802.1X Authentication with VLAN Assignment, page 57-13 Using Multiple VLANs and VLAN User Distribution with VLAN Assignment, page 57-14 Using 802.1X Authentication with Guest VLAN, page 57-15 Using 802.1X Authentication with Restricted VLAN, page 57-16 Using 802.1X Authentication with Inaccessible Authentication Bypass, page 57-17 Using 802.1X Authentication with Voice VLAN Ports, page 57-18 Using 802.1X Authentication with Port Security, page 57-19 Using 802.1X Authentication with ACL Assignments and Redirect URLs, page 57-19 Using RADIUS Change of Authorization, page 57-24 Using 802.1X Authentication with Port Descriptors, page 57-22 Using 802.1X Authentication with MAC Authentication Bypass, page 57-22 Using Network Admission Control Layer 2 IEEE 802.1X Validation, page 57-23 Using 802.1X Authentication with Wake-on-LAN, page 57-25 Understanding MAC Move, page 57-25 Understanding MAC Replace, page 57-26 Understanding 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT), page 57-26
Understanding 802.1X Device Roles

With 802.1X port-based authentication, the devices in the network have specific roles as shown in Figure 57-1.
Figure 57-1 802.1X Device Roles
Catalyst switch or Cisco Router Workstations (clients)
Authentication server (RADIUS)
57-2
79549
OL-13013-06
Chapter 57
Configuring IEEE 802.1X Port-Based Authentication Understanding 802.1X Port-Based Authentication
The specific roles shown in Figure 57-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 (ACS), 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)With Release 12.2(33)SXH and later releases, 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. 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.
Understanding the Port-based Authentication Process

When 802.1X port-based authentication is enabled, these events occur:

If the client supports 802.1X-compliant client software and the clients identity is valid, the 802.1X authentication succeeds and the switch grants the client access to the network. If 802.1X authentication times out while waiting for an EAPOL message exchange, the switch can use a fallback authentication method, such as MAC authentication bypass (MAB) or web-based authentication (webauth), if either or both are enabled:
If MAC authentication bypass is enabled, the switch relays the clients MAC address to the
AAA server for authorization. If the clients MAC address is valid, the authorization succeeds and the switch grants the client access to the network.
If web-based authentication is enabled, the switch sends an HTTP login page to the client. The
switch relays the clients username and password to the AAA server for authorization. If the login succeeds, the switch grants the client access to the network.
57-3
Note
The default order for authentication methods is 802.1X, and then MAB, then web-based authentication. You can change the order, and you can disable any of these methods. If fallback authentication methods are not enabled or are not successful, and if a guest VLAN is configured, the switch assigns the client to a guest VLAN that provides limited services. If the switch receives an invalid identity from an 802.1X-capable client and a restricted VLAN is specified, the switch can assign the client to a restricted VLAN that provides limited services. If the RADIUS authentication server is unavailable (down) and inaccessible authentication bypass is enabled, the switch grants the client access to the network by putting the port in the critical-authentication state in the user-specified critical VLAN.
Note
Inaccessible authentication bypass is also referred to as critical authentication or the AAA fail policy.
57-4
OL-13013-06
Chapter 57
Figure 57-2 shows the authentication process.

Figure 57-2 Authentication Flowchart
Start
Is the client IEEE 802.1x capable? Yes
No
IEEE 802.1x authentication process times out.
Is MAC authentication bypass enabled? 1 Yes No
The switch gets an EAPOL message, and the EAPOL message exchange begins. Start IEEE 802.1x port-based authentication. Client identity is invalid Client identity is valid
Use MAC authentication bypass. 1 Client MAC address identity is valid. Client MAC address identity is invalid. Is web-based authentication enabled? 1 Yes No
Assign the port to a restricted VLAN.
Assign the port to a VLAN.
Done All authentication servers are down
Done
Use web-based authentication.1 All authentication servers are down Login passed Login failed
Use inaccessible authentication bypass (critical authentication) to assign the critical port to a VLAN.
Assign the port to a VLAN.
Assign the port to a guest VLAN. 1

280232
Done
Done
Done
1 = This occurs if the switch does not detect EAPOL packets from the client.
The switch reauthenticates a client when one of these situations occurs:
Periodic reauthentication is enabled, and the reauthentication timer expires. You can configure the reauthentication timer to use a switch-specific value or to be based on values from the RADIUS server. After 802.1X authentication using a RADIUS server is configured, the switch uses timers based on the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute [29]). The Session-Timeout RADIUS attribute (Attribute[27]) specifies the time after which reauthentication occurs.
57-5
The Termination-Action RADIUS attribute (Attribute [29]) specifies the action to take during reauthentication. The actions are Initialize and ReAuthenticate. When the Initialize action is set (the attribute value is DEFAULT), the 802.1X session ends, and connectivity is lost during reauthentication. When the ReAuthenticate action is set (the attribute value is RADIUS-Request), the session is not affected during reauthentication.
You manually reauthenticate the client by entering the dot1x re-authenticate interface type slot/port privileged EXEC command (Cisco IOS Release 12.2(33)SXH and earlier releases).
Authentication Initiation and Message Exchange

The switch or the client can initiate authentication. If you enable authentication on a port by using the dot1x pae authenticator and authentication port-control auto interface configuration commands (dot1x port-control auto command in Cisco IOS Release 12.2(33)SXH and earlier releases), 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 57-8. 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 port becomes authorized. If the authentication fails, authentication can be retried, the port might be assigned to a VLAN that provides limited services, or network access is not granted. For more information, see the Ports in Authorized and Unauthorized States section on page 57-8.
57-6
OL-13013-06
Chapter 57
The specific exchange of EAP frames depends on the authentication method being used. Figure 57-3 shows a message exchange initiated by the client using the One-Time-Password (OTP) authentication method with a RADIUS server.
Figure 57-3 Message Exchange
Client
Catalyst switch or Cisco Router
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
If 802.1X authentication times out while waiting for an EAPOL message exchange, and MAC authentication bypass is enabled, the switch can authorize the client when the switch detects an Ethernet packet from the client. The switch uses the MAC address of the client as its identity and includes this information in the RADIUS-access/request frame that is sent to the RADIUS server. After the server sends the switch the RADIUS-access/accept frame (authorization is successful), the port becomes authorized. If MAB authorization fails and a guest VLAN is specified, the switch assigns the port to the guest VLAN. If the switch detects an EAPOL packet while waiting for an Ethernet packet, the switch stops the MAC authentication bypass process and starts 802.1X authentication.
57-7
Figure 57-4 shows the message exchange during MAC authentication bypass.
Figure 57-4 Message Exchange During MAC Authentication Bypass
Client
Switch
EAPOL Request/Identity EAPOL Request/Identity EAPOL Request/Identity Ethernet packet RADIUS Access/Request
141681
RADIUS Access/Accept
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 authentication connects 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 authentication port-control interface configuration command (dot1x port-control auto command in Cisco IOS Release 12.2(33)SXH and earlier releases) 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. autoEnables 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 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.
57-8
OL-13013-06
Chapter 57
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.
802.1X Host Modes

The 802.1X ports host mode determines whether more than one client can be authenticated on the port and how authentication will be enforced. You can configure an 802.1X port to use any of the four host modes described in the following sections. In addition, each mode may be modified to allow pre-authentication open access.

Single-Host Mode, page 57-9 Multiple-Hosts Mode, page 57-9 Multidomain Authentication Mode, page 57-10 Multiauthentication Mode, page 57-10 Pre-Authentication Open Access, page 57-11
Single-Host Mode
In single-host mode (see Figure 57-1 on page 57-2), only one client can be connected to the 802.1X-enabled port. The switch detects the client by sending an EAPOL frame 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.
Multiple-Hosts Mode
In multiple-hosts mode, you can attach multiple hosts to a single 802.1X-enabled port. Figure 57-5 shows 802.1X port-based authentication in a wireless LAN. In this mode, only one of the attached clients must be authorized for all clients to be granted network access. If the port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received), the switch denies network access to all of the attached clients. In this topology, the wireless access point is responsible for authenticating the clients attached to it, and it also acts as a client to the switch. With the multiple-hosts mode enabled, you can use 802.1X authentication to authenticate the port and you can use port security to manage network access for all MAC addresses, including the clients MAC address.
57-9
Figure 57-5
Multiple Host Mode Example
Access point Wireless clients
Multidomain Authentication Mode

Supported in Cisco IOS Release 12.2(33)SXI and later releases, multidomain authentication (MDA) mode allows an IP phone (Cisco or third-party) and a single host behind the IP phone to authenticate independently, using 802.1X, MAC authentication bypass (MAB), or (for the host only) web-based authentication. In this application, multidomain refers to two domains, data and voice, and only two MAC addresses are allowed per port. The switch can place the host in the data VLAN and the IP phone in the voice VLAN, though they appear on the same switch port. The data VLAN assignment can be obtained from the vendor-specific attributes (VSAs) received from the authentication, authorization, and accounting (AAA) server during authentication. Figure 57-6 shows a typical MDA application with a single host behind an IP phone connected to the 802.1X-enabled port. Because the client is not directly connected to the switch, the switch cannot detect a loss of port link if the client is disconnected. To prevent the possibility of another device using the established authentication of the disconnected client, later Cisco IP phones send a Cisco Discovery Protocol (CDP) host presence type length value (TLV) to notify the switch of changes in the attached clients port link state.
Figure 57-6 Multidomain Authentication Mode Example
Client
IP phone IP
Switch

187640
Multiauthentication Mode
Available in Cisco IOS Release 12.2(33)SXI and later releases, multiauthentication (multiauth) mode allows one 802.1X/MAB client on the voice VLAN and multiple authenticated 802.1X/MAB/webauth clients on the data VLAN. When a hub or access point is connected to an 802.1X port (as shown in Figure 57-5), multiauth mode provides enhanced security over the multiple-hosts mode by requiring authentication of each connected client. For non-802.1X devices, MAB or web-based authentication can be used as the fallback method for individual host authentications, which allows different hosts to be authenticated through different methods on a single port. Multiauth also supports MDA functionality on the voice VLAN by assigning authenticated devices to either a data or voice VLAN depending on the data that the VSAs received from the authentication server.
57-10
101227
OL-13013-06
Chapter 57
Release 12.2(33)SXJ and later releases support the assignment of a RADIUS server-supplied VLAN in multiauth mode, by using the existing commands and when these conditions occur:

The host is the first host authorized on the port, and the RADIUS server supplies VLAN information. Subsequent hosts are authorized with a VLAN that matches the operational VLAN. A host is authorized on the port with no VLAN assignment, and subsequent hosts either have no VLAN assignment, or their VLAN information matches the operational VLAN. The first host authorized on the port has a group VLAN assignment, and subsequent hosts either have no VLAN assignment, or their group VLAN matches the group VLAN on the port. Subsequent hosts must use the same VLAN from the VLAN group as the first host. If a VLAN list is used, all hosts are subject to the conditions specified in the VLAN list. After a VLAN is assigned to a host on the port, subsequent hosts must have matching VLAN information or be denied access to the port. The behavior of the critical-auth VLAN is not changed for multiauth mode. When a host tries to authenticate and the server is not reachable, all authorized hosts are reinitialized in the configured VLAN.
Note
Only one voice VLAN is supported on a multiauth port. You cannot configure a guest VLAN or an auth-fail VLAN in multiauth mode.
Pre-Authentication Open Access

With Cisco IOS Release 12.2(33)SXI and later releases, any of the four host modes may be additionally configured to allow a device to gain network access before authentication. This pre-authentication open access is useful in an application such as the Pre-boot eXecution Environment (PXE), where a device must access the network to download a bootable image containing an authentication client. Pre-authentication open access is enabled by entering the authentication open command after host mode configuration, and acts as an extension to the configured host mode. For example, if pre-authentication open access is enabled with single-host mode, then the port will allow only one MAC address. When pre-authentication open access is enabled, initial traffic on the port is restricted only by whatever other access restriction, independent of 802.1X, is configured on the port. If no access restriction other than 802.1X is configured on the port, then a client device will have full access on the configured VLAN.
Using 802.1X Authentication with DHCP Snooping

With Cisco IOS Release 12.2(33)SXH and later releases, when the Dynamic Host Configuration Protocol (DHCP) snooping option-82 with data insertion feature is enabled, the switch can insert a clients 802.1X authenticated user identity information into the DHCP discovery process, allowing the DHCP server to assign IP addresses from different IP address pools to different classes of end users. This feature allows you to secure the IP addresses given to the end users for accounting purposes and to allow services based on Layer 3 criteria. After a successful 802.1X authentication between a supplicant and the RADIUS server, the switch puts the port in the forwarding state and stores the attributes that it receives from the RADIUS server. While performing DHCP snooping, the switch acts as a DHCP relay agent, receiving DHCP messages and regenerating those messages for transmission on another interface. When a client, after 802.1X
57-11
authentication, sends a DHCP discovery message, the switch receives the packet. The switch adds to the packet a RADIUS attributes suboption section containing the stored RADIUS attributes of the client. The switch then submits the discovery broadcast again. The DHCP server receives the modified DHCP discovery packet and can, if configured to do so, use the authenticated user identity information when creating the IP address lease. The mapping of user-to-IP address can be on a one-to-one, one-to-many, or many-to-many basis. The one-to-many mapping allows the same user to authenticate through the 802.1X hosts on multiple ports. The switch will automatically insert the authenticated user identity information when 802.1X authentication and DHCP snooping option-82 with data insertion features are enabled. To configure DHCP snooping option-82 with data insertion, see the DHCP Snooping Option-82 Data Insertion section on page 51-3. For information about the data inserted in the RADIUS attributes suboption, see RFC 4014, Remote Authentication Dial-In User Service (RADIUS) Attributes Suboption for the Dynamic Host Configuration Protocol (DHCP) Relay Agent Information Option.
Understanding 802.1X Accounting

The IEEE 802.1X standard defines how users are authorized and authenticated for network access but does not keep track of network usage. IEEE 802.1X accounting is disabled by default. With Release 12.2(33)SXH and later releases, you can enable 802.1X accounting to monitor the following activities on 802.1X-enabled ports:

User successfully authenticates. User logs off. Link-down occurs. Reauthentication successfully occurs. Reauthentication fails.
The switch does not log IEEE 802.1X accounting information. Instead, it sends this information to the RADIUS server, which must be configured to log accounting messages.
802.1X Accounting Attribute-Value Pairs

The information sent to the RADIUS server is represented in the form of Attribute-Value (AV) pairs. These AV pairs provide data for different applications. (For example, a billing application might require information that is in the Acct-Input-Octets or the Acct-Output-Octets attributes of a RADIUS packet.) AV pairs are automatically sent by a switch that is configured for 802.1X accounting. Three types of RADIUS accounting packets are sent by a switch:

STARTSent when a new user session starts. INTERIMSent during an existing session for updates. STOPSent when a session terminates.
57-12
OL-13013-06
Chapter 57
Table 57-1 lists the AV pairs and indicates when they are sent are sent by the switch.
Table 57-1 Accounting AV Pairs
Attribute Number Attribute[1] Attribute[4] Attribute[5] Attribute[8] Attribute[25] Attribute[26] Attribute[30] Attribute[31] Attribute[40] Attribute[41] Attribute[42] Attribute[43] Attribute[44] Attribute[45] Attribute[46] Attribute[49] Attribute[61]
AV Pair Name User-Name NAS-IP-Address NAS-Port Framed-IP-Address Class Vendor-Specific

2
START Always Always Always Never Always Always Always Always Always Never Never Always Always Never Never Always
INTERIM Always Always Always Sometimes Always Always Always Always Always Never Never Always Always Never Never Always
1
STOP Always Always Always Sometimes1 Always Always Always Always Always Always Always Always Always Always Always Always
Called-Station-ID Calling-Station-ID Acct-Status-Type Acct-Delay-Time Acct-Input-Octets Acct-Output-Octets Acct-Session-ID Acct-Authentic Acct-Session-Time Acct-Terminate-Cause NAS-Port-Type
1. The Framed-IP-Address AV pair is sent only if a valid DHCP binding exists for the host in the DHCP snooping bindings table. 2. Vendor-specific attributes (VSAs) are used by other 802.1X features.
You can view the AV pairs that are being sent by the switch by entering the debug radius accounting privileged EXEC command. For more information about this command, see the Cisco IOS Debug Command Reference, Release 12.2 at this URL: http://www.cisco.com/en/US/docs/ios/12_2/debug/command/reference/122debug.html For more information about AV pairs, see RFC 3580, IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines.
Using 802.1X Authentication with VLAN Assignment

After successful 802.1X authentication of a port, the RADIUS server sends the VLAN assignment to configure the port. The RADIUS server database maintains the username-to-VLAN mappings, assigning the VLAN based on the username of the client connected to the port. You can use this feature to limit network access for certain users. When configured on the switch and the RADIUS server, 802.1X authentication with VLAN assignment has these characteristics:
If 802.1X authentication is enabled on a port, and if all information from the RADIUS server is valid, the port is placed in the RADIUS server-assigned VLAN after authentication.
57-13
If the multiple-hosts mode is enabled on an 802.1X port, all hosts on the port are placed in the same RADIUS server-assigned VLAN as the first authenticated host. If the multiauth mode is enabled on an 802.1X port, the VLAN assignment will be ignored. If no VLAN number is supplied by the RADIUS server, the port is configured in its access VLAN after successful authentication. An access VLAN is a VLAN assigned to an access port. All packets sent from or received on this port belong to this VLAN. If 802.1X authentication is enabled but the VLAN information from the RADIUS server is not valid, the port returns to the unauthorized state and remains in the configured access VLAN. This prevents ports from appearing unexpectedly in an inappropriate VLAN because of a configuration error. Configuration errors could include specifying a VLAN for a routed port, a malformed VLAN ID, a nonexistent or internal (routed port) VLAN ID, or an attempted assignment to a voice VLAN ID.
If 802.1X authentication is disabled on the port, the port is returned to the configured access VLAN.
When the port is in the force-authorized, force-unauthorized, unauthorized, or shutdown state, the port is put into the configured access VLAN. If an 802.1X port is authenticated and put in the RADIUS server-assigned VLAN, any change to the port access VLAN configuration does not take effect. The 802.1X authentication with VLAN assignment feature is not supported on trunk ports, dynamic ports, or with dynamic-access port assignment through a VLAN Membership Policy Server (VMPS). To configure VLAN assignment, perform this task:
Enable AAA authorization by using the network keyword to allow interface configuration from the RADIUS server. Enable 802.1X authentication. The VLAN assignment feature is automatically enabled when you configure 802.1X authentication on an access port. Assign vendor-specific tunnel attributes in the RADIUS server. The RADIUS server must return these attributes to the switch:

[64] Tunnel-Type = VLAN [65] Tunnel-Medium-Type = 802 [81] Tunnel-Private-Group-ID = VLAN name or VLAN ID
Attribute [64] must contain the value VLAN (type 13). Attribute [65] must contain the value 802 (type 6). Attribute [81] specifies the VLAN name or VLAN ID assigned to the 802.1X-authenticated user.
Using Multiple VLANs and VLAN User Distribution with VLAN Assignment
In Cisco IOS Release 12.2(33)SXI1 and later releases, the RADIUS-supplied VLAN assignment can provide load balancing by distributing 802.1X-authenticated users among multiple VLANs. In earlier releases, the RADIUS server can supply a single VLAN name or ID for the assignment of an authenticating user. In Cisco IOS Release 12.2(33)SXI1 and later releases, the RADIUS server can supply multiple VLAN names and IDs or the name of a VLAN group that contains multiple VLANs. Use either of the following two methods to load balance the users between the different VLANs:
57-14
OL-13013-06
Chapter 57
Configure the RADIUS server to send more than one VLAN ID or VLAN name as part of the response to the authenticating user. The 802.1X VLAN user group feature tracks the users in a particular VLAN and achieves load balancing by placing newly authenticated users in the least populated VLAN of the RADIUS-supplied VLAN IDs. Perform the steps shown in the Using 802.1X Authentication with VLAN Assignment section on page 57-13 with the following exception: Attribute [81] Tunnel-Private-Group-ID specifies multiple VLAN names or VLAN IDs Define a VLAN group that contains multiple VLANs. Configure the RADIUS server to supply the VLAN group name instead of a VLAN ID as part of the response to the authenticating user. If the supplied VLAN group name is found among the VLAN group names that you have defined, the newly authenticated user is placed in the least populated VLAN within the VLAN group. Perform the steps shown in the Using 802.1X Authentication with VLAN Assignment section on page 57-13 with the following exception: Attribute [81] Tunnel-Private-Group-ID specifies a defined VLAN group name
For more information, see the Configuring VLAN User Distribution section on page 57-47.
Using 802.1X Authentication with Guest VLAN

With Release 12.2(33)SXH and later releases, you can configure a guest VLAN for each 802.1X port on the switch to provide limited services to non-802.1X-compliant clients, such as for downloading the 802.1X client software. These clients might be upgrading their system for 802.1X authentication, and some hosts, such as Windows 98 systems, might not be 802.1X-capable. When you enable a guest VLAN on an 802.1X port, the switch assigns clients to a guest VLAN when the switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not sent by the client and no fallback authentication methods are enabled. In addition, the switch maintains the EAPOL packet history. If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines that the device connected to that interface is an 802.1X-capable supplicant, and the interface will not change to the guest VLAN state. The EAPOL packet history is cleared if the interface link status goes down. Use the dot1x guest-vlan supplicant global configuration command to allow an interface to change to the guest VLAN state regardless of the EAPOL packet history. That is, a host that is not 802.1X-capable will be assigned to the guest VLAN even if a previous host on that interface was 802.1X-capable.
Note
If an EAPOL packet is detected after the interface has changed to the guest VLAN, the interface reverts to an unauthorized state, and 802.1X authentication restarts. Any number of 802.1X-incapable clients are allowed access when the port is moved to the guest VLAN. If an 802.1X-capable client joins the same port on which the guest VLAN is configured, the port is put into the unauthorized state in the user-configured access VLAN, and authentication is restarted. When operating as an 802.1X guest VLAN, a port functions in multiple-hosts mode regardless of the configured host mode of the port. You can configure any active VLAN except an RSPAN VLAN, a private primary PVLAN, or a voice VLAN as an 802.1X guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
57-15
The switch supports MAC authentication bypass in Release 12.2(33)SXH and later releases. When MAC authentication bypass is enabled on an 802.1X port, the switch can authorize clients based on the client MAC address when 802.1X authentication times out while waiting for an EAPOL message exchange. After detecting a client on an 802.1X port, the switch waits for an Ethernet packet from the client. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address. If authorization succeeds, the switch grants the client access to the network. If authorization fails, the switch assigns the port to the guest VLAN if one is specified. For more information, see the Using 802.1X Authentication with MAC Authentication Bypass section on page 57-22 and the Configuring a Guest VLAN section on page 57-48.
Using 802.1X Authentication with Restricted VLAN

You can configure a restricted VLAN (also referred to as an authentication failed VLAN) for each 802.1X port on a switch to provide limited services to clients that failed authentication and cannot access the guest VLAN. These clients are 802.1X-compliant and cannot access another VLAN because they fail the authentication process. A restricted VLAN allows users without valid credentials in an authentication server (typically, visitors to an enterprise) to access a limited set of services. The administrator can control the services available to the restricted VLAN.
Note
You can configure a VLAN to be both the guest VLAN and the restricted VLAN if you want to provide the same services to both types of users. Without this feature, the client attempts and fails authentication indefinitely, and the port remains in the spanning-tree blocking state. With this feature, you can configure the port to be in the restricted VLAN after a specified number of authentication attempts. The authenticator counts the failed authentication attempts for the client. The failed attempt count increments when the RADIUS server replies with either an Access-Reject EAP failure or an empty response without an EAP packet. When this count exceeds the configured maximum number of authentication attempts, the port moves to the restricted VLAN, the failed attempt counter resets, and subsequent EAPOL-start messages from the failed client are ignored. Users who fail authentication remain in the restricted VLAN until the next switch-initiated reauthentication attempt. A port in the restricted VLAN tries to reauthenticate at configured intervals (the default is 60 seconds). If reauthentication fails, the port remains in the restricted VLAN. If reauthentication is successful, the port moves either to the configured VLAN or to a VLAN sent by the RADIUS server. You can disable reauthentication. If you do this, the only way to restart the authentication process is for the port to receive a link down or EAP logoff event. We recommend that you keep reauthentication enabled if a client might connect through a hub. When a client disconnects from the hub, the port might not receive the link down or EAP logoff event. When operating as an 802.1X restricted VLAN, a port functions in single-host mode regardless of the configured host mode of the port. Only the client that failed authentication is allowed access on the port. An exception is that a port configured in MDA mode can still authenticate a voice supplicant from the restricted VLAN. You can configure any active VLAN except an RSPAN VLAN or a voice VLAN as an 802.1X restricted VLAN. The restricted VLAN feature is not supported on routed or trunk ports; it is supported only on access ports. This feature works with port security. As soon as the port is authorized, a MAC address is provided to port security. If port security does not permit the MAC address or if the maximum secure address count is reached, the port becomes unauthorized and error disabled.
57-16
OL-13013-06
Chapter 57
Other port security features such as dynamic ARP Inspection, DHCP snooping, and IP source guard can be configured independently on a restricted VLAN. For more information, see the Configuring a Restricted VLAN section on page 57-49.
Using 802.1X Authentication with Inaccessible Authentication Bypass

With Release 12.2(33)SXH and later releases, when the switch cannot reach the configured RADIUS servers and hosts cannot be authenticated, you can configure the switch to allow network access to the hosts connected to critical ports. A critical port is enabled for the inaccessible authentication bypass feature, also referred to as critical authentication or the AAA fail policy. When this feature is enabled, the switch checks the status of the configured RADIUS servers whenever the switch tries to authenticate a host connected to a critical port. If a server is available, the switch can authenticate the host. However, if all the RADIUS servers are unavailable, the switch grants network access to the host and puts the port in the critical-authentication state, which is a special case of the authentication state. The behavior of the inaccessible authentication bypass feature depends on the authorization state of the port:
If the port is unauthorized when a host connected to a critical port tries to authenticate and all servers are unavailable, the switch puts the port in the critical-authentication state in the user-specified critical VLAN. If the port is already authorized and reauthentication occurs, the switch puts the critical port in the critical-authentication state in the current VLAN, which might be the one previously assigned by the RADIUS server. If the RADIUS server becomes unavailable during an authentication exchange, the current exchanges times out, and the switch puts the critical port in the critical-authentication state during the next authentication attempt.
When a RADIUS server that can authenticate the host is available, all critical ports in the critical-authentication state are automatically reauthenticated. Inaccessible authentication bypass interacts with these features:
Guest VLANInaccessible authentication bypass is compatible with guest VLAN. When a guest VLAN is enabled on 8021.x port, the features interact as follows:
If at least one RADIUS server is available, the switch assigns a client to a guest VLAN when
the switch does not receive a response to its EAP request/identity frame or when EAPOL packets are not sent by the client.
If all the RADIUS servers are not available and the client is connected to a critical port, the
switch authenticates the client and puts the critical port in the critical-authentication state in the user-specified critical VLAN.
If all the RADIUS servers are not available and the client is not connected to a critical port, the
switch might not assign clients to the guest VLAN if one is configured.
If all the RADIUS servers are not available and if a client is connected to a critical port and was
previously assigned to a guest VLAN, the switch keeps the port in the guest VLAN.
57-17
Restricted VLANIf the port is already authorized in a restricted VLAN and the RADIUS servers are unavailable, the switch puts the critical port in the critical-authentication state in the restricted VLAN. 802.1X accountingAccounting is not affected if the RADIUS servers are unavailable. Private VLANYou can configure inaccessible authentication bypass on a private VLAN host port. The access VLAN must be a secondary private VLAN. Voice VLANInaccessible authentication bypass is compatible with voice VLAN, but the RADIUS-configured or user-specified access VLAN and the voice VLAN must be different. Remote Switched Port Analyzer (RSPAN)Do not configure an RSPAN VLAN as the RADIUS-configured or user-specified access VLAN for inaccessible authentication bypass.
Using 802.1X Authentication with Voice VLAN Ports

A Multi-VLAN Access Port (MVAP) is a port that belong to two VLANs. A voice VLAN port is an MVAP that allows separating a ports voice traffic and data traffic on different VLANs. A voice VLAN port is associated with two VLAN identifiers:

Voice VLAN identifier (VVID) to carry voice traffic to and from the IP phone. The VVID is used to configure the IP phone connected to the port. Port VLAN identifier (PVID) to carry the data traffic to and from the workstation connected to the switch through the IP phone. The PVID is the native VLAN of the port.
In releases earlier than Release 12.2(33)SXH, a switch in single-host mode accepted traffic from a single host, and voice traffic was not allowed. In multiple-hosts mode, the switch did not accept voice traffic until the client was authenticated on the primary VLAN, which makes the IP phone inoperable until the user logged in. With Release 12.2(33)SXH and later releases, the IP phone uses the VVID for its voice traffic, regardless of the authorization state of the port. This allows the phone to work independently of 802.1X authentication. In single-host mode, only the IP phone is allowed on the voice VLAN. In multiple-hosts mode, additional clients can send traffic on the voice VLAN after a supplicant is authenticated on the PVID. When multiple-hosts mode is enabled, the supplicant authentication affects both the PVID and the VVID. In order to recognize an IP phone, the switch will allow CDP traffic on a port regardless of the authorization state of the port. A voice VLAN port becomes active when there is a link, and the device MAC address appears after the first CDP message from the IP phone. Cisco IP phones do not relay CDP messages from other devices. As a result, if several IP phones are connected in series, the switch recognizes only the one directly connected to it. When 802.1X authentication is enabled on a voice VLAN port, the switch drops packets from unrecognized IP phones more than one hop away. When 802.1X authentication is enabled on a port, you cannot configure a port VLAN that is equal to a voice VLAN.
Note
If you enable 802.1X authentication on an access port on which a voice VLAN is configured and to which a Cisco IP phone is connected, the Cisco IP phone loses connectivity to the switch for up to 30 seconds. For voice VLAN configuration information, see Chapter 15, Configuring Cisco IP Phone Support.
57-18
OL-13013-06
Chapter 57
Using 802.1X Authentication with Port Security

With Release 12.2(33)SXH and later releases, you can configure an 802.1X port with port security in either single-host or multiple-hosts mode. (You also must configure port security on the port by using the switchport port-security interface configuration command.) When you enable port security and 802.1X authentication on a port, 802.1X authentication authenticates the port, and port security manages network access for all MAC addresses, including that of the client. You can then limit the number or group of clients that can access the network through an 802.1X port. These are some examples of the interaction between 802.1X authentication and port security on the switch:
When a client is authenticated, and the port security table is not full, the client MAC address is added to the port security list of secure hosts. The port then proceeds to come up normally. When a client is authenticated and manually configured for port security, it is guaranteed an entry in the secure host table. A security violation occurs if the client is authenticated, but the port security table is full. This can happen if the maximum number of secure hosts has been statically configured or if the client ages out of the secure host table. If the client address is aged, its place in the secure host table can be taken by another host. If a security violation is caused by any host, the port becomes error-disabled and immediately shuts down. The port security violation modes determine the action for security violations. For more information, see the Configuring the Port Security Violation Mode on a Port section on page 59-6.
When you manually remove an 802.1X client address from the port security table by using the no switchport port-security mac-address mac-address interface configuration command, you should reauthenticate the 802.1X client by using the dot1x re-authenticate interface type slot/port privileged EXEC command. When an 802.1X client logs off, the port changes to an unauthenticated state, and all dynamic entries in the secure host table are cleared, including the entry for the client. Normal authentication then takes place. If the port is administratively shut down, the port becomes unauthenticated, and all dynamic entries are removed from the secure host table. Port security and a voice VLAN can be configured simultaneously on an 802.1X port that is in either single-host or multiple-hosts mode. Port security applies to both the voice VLAN identifier (VVID) and the port VLAN identifier (PVID).
For more information about enabling port security on your switch, see the Configuring Port Security section on page 59-5.
Using 802.1X Authentication with ACL Assignments and Redirect URLs

With Cisco IOS Release 12.2(33)SXI and later releases, per-host policies such as ACLs and redirect URLs can be downloaded to the switch from the authentication server (AS) in a RADIUS Access-Accept packet at the end of an 802.1X, MAB, or web-based authentication exchange. Per-host policies are activated during authentication as follows:
Downloadable ACLs (DACLs) are defined in the Cisco Secure ACS and downloaded from the ACS to the switch using VSAs.
57-19
Filter-ID ACLs are defined on the switch, and only the ACL name is downloaded from the AS to the switch using the RADIUS Filter-ID attribute. Filter-ID ACLs are supported in Cisco IOS Release 12.2(33)SXI2 and later releases. A redirection URL and an ACL name are downloaded from the ACS to the switch using VSAs. The redirection ACL is defined on the switch.
For information about configuring per-host policies, see the Configuring the Switch for DACLs or Redirect URLs section on page 57-57.
Downloadable ACLs Using the Cisco Secure ACS

Following a successful host authentication, the Cisco Secure ACS can use a VSA to download an ACL to the switch. The switch combines the DACL with the default ACL on the port to which the host has connected. Because the DACL definition resides on the authentication server, this feature allows for centralized policy management. Two methods are provided in the Cisco Secure ACS for configuring DACLs:
Downloadable IP ACL Downloading of the DACL is enabled by selecting Assign IP ACL in the ACS configuration, and the DACL is defined in the Downloadable IP ACL Content menu of the ACS. There is no restriction on the size of the DACL.
Per-user ACL In Cisco IOS Release 12.2(33)SXI2 and later releases, the ACS can use the CiscoSecure-Defined-ACL [009\001 cisco-av-pair] VSAs to deliver the DACL. Because the entire DACL is delivered in a single RADIUS packet, the maximum size is limited by the 4096-byte maximum size for a RADIUS packet. The DACL must be defined on the ACS using the following format: protocol:inacl#sequence_number=ace as shown in this example:
ip:inacl#10=permit ip any 67.2.2.0 0.0.0.255
These guidelines apply when using DACLs:

The source address for all ACEs must be defined as ANY. When the 802.1X host mode of the port is MDA or multiauth, the DACL will be modified to use the authenticated hosts IP address as the source address. When the host mode is either single-host or multiple-host, the source address will be configured as ANY, and the downloaded ACLs or redirects will apply to all devices on the port. If no DACLs are provided during the authentication of a host, the static default ACL configured on the port will be applied to the host. On a voice VLAN port, only the static default ACL of the port will be applied to the phone.
Filter-ID ACLs
In Cisco IOS Release 12.2(33)SXI2 and later releases, following a successful host authentication, the authentication server can use the RADIUS Filter-ID attribute (Attribute[11]) rather than a VSA to deliver only the name of an extended ACL to the switch in the following format: acl_name.in The suffix .in indicates that the ACL should be applied in the inbound direction.
57-20
OL-13013-06
Chapter 57
In this method, the ACL must be already defined on the switch. The switch matches the Filter-ID attribute value to a locally configured ACL that has the same name or number as the Filter-ID (for example, Filter-ID=101.in will match the extended numbered ACL 101, and Filter-ID= guest.in will match the extended named ACL guest). The specified ACL is then applied to the port. Because the ACL definition resides on the switch, this feature allows for local variation in a policy. These guidelines apply when using Filter-ID ACLs:

The guidelines for using DACLs also apply to Filter-ID ACLs. The Filter-ID attribute may be a number (100 to 199, or 2000 to 2699) or a name.
Redirect URLs
Following a successful host authentication, the Cisco Secure ACS can use a VSA to download information to the switch for intercepting and redirecting HTTP or HTTPS requests from the authenticated host. The ACS downloads a redirection ACL and URL. When an HTTP or HTTPS request from the host matches the downloaded ACL, the hosts web browser is redirected to the downloaded redirection URL. The ACS uses these cisco-av-pair VSAs to configure the redirection:
url-redirect-acl This 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, and the source address must be defined as ANY. Traffic that matches a permit entry in the redirect ACL will be redirected.
url-redirect This AV pair contains the HTTP or HTTPS URL to which the web browser will be redirected.
Static Sharing of ACLs

When a number of interfaces have the same PACL and VLAN-based features, you can use the mls acl tcam share-acl global configuration command to enable the static sharing feature. With static sharing, only one copy of the PACL and inherited VLAN-based feature ACLs is stored in the TCAM for all ports using the same ACL set, freeing TCAM space for more ACLs. With static sharing enabled, the switch will automatically evaluate all configured or enabled interfaces for static sharing when any of these events occur:

When the mls acl tcam share-acl command is entered. When an interface is configured. When a state change occurs on an interface. Static sharing is not supported for interfaces enabled with IPv6. Static sharing is not supported with PFC3A-based supervisor engines or earlier, or in systems running in PFC3A mode or lower. Static sharing is supported only on switch ports in access mode with NAC or 802.1X DACL features configured. Static sharing is not supported on switch ports enabled with QOS, with the exception of VLAN-based QoS.
When enabling static sharing, consider the following guidelines and restrictions:

57-21
When 802.1X is used with DACL, we recommend entering the platform hardware acl dynamic setup static command to avoid triggering a static sharing evaluation when the port is dynamically configured by the authentication server response. The static sharing evaluation may adversely affect the port/host linkup time. 802.1X interfaces with fallback authentication as active cannot form a static sharing group with interfaces on which fallback is not enabled or is not active.
Using 802.1X Authentication with Port Descriptors

With Release 12.2(33)SXI and later releases, you can associate descriptive text with an 802.1X clients authentication information by configuring the Cisco vendor-specific attribute (VSA) aaa:supplicant-name on the RADIUS server. During a successful 802.1X authentication of the client on the port, the switch will receive the descriptive information from the RADIUS server as part of the Access-Accept packet and will display the information when the show interface users command is entered for the port. If the port is in a mode supporting multiple authenticated hosts, identity information for all the authenticated hosts will be displayed with the port description.
Using 802.1X Authentication with MAC Authentication Bypass

With Release 12.2(33)SXH and later releases, you can configure the switch to authorize clients based on the client MAC address (see Figure 57-4 on page 57-8) by using the MAC authentication bypass feature. For example, you can enable this feature on 802.1X ports connected to devices such as printers. If 802.1X authentication times out while waiting for an EAPOL response from the client, the switch tries to authorize the client by using MAC authentication bypass. When the MAC authentication bypass feature is enabled on an 802.1X port, the switch uses the MAC address as the client identity. The authentication server has a database of client MAC addresses that are allowed network access. After detecting a client on an 802.1X port, the switch waits for an Ethernet packet from the client. The switch sends the authentication server a RADIUS-access/request frame with a username and password based on the MAC address. If authorization succeeds, the switch grants the client access to the network. If authorization fails, the switch assigns the port to the guest VLAN if one is configured. If an EAPOL packet is detected on the interface during the lifetime of the link, the switch determines that the device connected to that interface is an 802.1X-capable supplicant and uses 802.1X authentication (not MAC authentication bypass) to authorize the interface. EAPOL history is cleared if the interface link status goes down. If the switch already authorized a port by using MAC authentication bypass and detects an 802.1X supplicant, the switch does not unauthorize the client connected to the port. When reauthentication occurs, the switch uses 802.1X authentication as the preferred reauthentication process if the previous session ended because the Termination-Action RADIUS attribute value is DEFAULT. Clients that were authorized with MAC authentication bypass can be reauthenticated. The reauthentication process is the same as that for clients that were authenticated with 802.1X. During reauthentication, the port remains in the previously assigned VLAN. If reauthentication is successful, the switch keeps the port in the same VLAN. If reauthentication fails, the switch assigns the port to the guest VLAN, if one is configured. If reauthentication is based on the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute [29]) and if the Termination-Action RADIUS attribute (Attribute [29]) action is Initialize, (the attribute value is DEFAULT), the MAC authentication bypass session ends, and connectivity is lost during reauthentication. If MAC authentication bypass is enabled
57-22
OL-13013-06
Chapter 57
and the 802.1X authentication times out, the switch uses the MAC authentication bypass feature to initiate reauthorization. For more information about these AV pairs, see RFC 3580, IEEE 802.1X Remote Authentication Dial In User Service (RADIUS) Usage Guidelines. MAC authentication bypass interacts with the features:

802.1X authenticationYou can enable MAC authentication bypass only if 802.1X authentication is enabled on the port. Guest VLANIf a client has an invalid MAC address identity, the switch assigns the client to a guest VLAN if one is configured. Restricted VLANThis feature is not supported when the client connected to an 802.lx port is authenticated with MAC authentication bypass. Port securitySee the Using 802.1X Authentication with Port Security section on page 57-19. Voice VLANSee the Using 802.1X Authentication with Voice VLAN Ports section on page 57-18. VLAN Membership Policy Server (VMPS) 802.1X and VMPS are mutually exclusive. Private VLANYou can assign a client to a private VLAN. Network admission control (NAC) Layer 2 IP validationThis feature takes effect after an 802.1X port is authenticated with MAC authentication bypass, including hosts in the exception list.
Using Network Admission Control Layer 2 IEEE 802.1X Validation

Cisco IOS Release 12.2(33)SXH and later releases support Network Admission Control (NAC) Layer 2 IEEE 802.1X validation, which checks the antivirus condition or posture of endpoint systems or clients before granting the devices network access. NAC Layer 2 IEEE 802.1X validation performs policy enforcement by assigning the authenticated port into a specified VLAN, which provides segmentation and quarantine of poorly postured hosts at Layer 2. Configuring NAC Layer 2 IEEE 802.1X validation is similar to configuring 802.1X port-based authentication except that you must configure a posture token on the RADIUS server. You can view the NAC posture token, which shows the posture of the client, by using the show dot1x privileged EXEC command. For information about configuring NAC Layer 2 IEEE 802.1X validation, see the Configuring NAC Layer 2 IEEE 802.1X Validation section on page 57-55. For more information about NAC, see the Network Admission Control Software Configuration Guide.
NAC Agentless Audit Support

With Cisco IOS Release 12.2(33)SXI and later releases, MAB support is added for the Cisco NAC Audit Architecture, which uses an external audit server to check the antivirus posture of clients that do not run a Cisco Trust Agent (CTA) and cannot respond to NAC queries. To audit and report an agentless clients antivirus posture, the NAC audit server must possess the clients IP address and a unique session identifier for the clients connection to the switch. To support the NAC audit architecture for agentless clients, the switch must snoop the clients IP address, create and assign a unique session identifier for the agentless client, and pass this information to the RADIUS server for sharing with the NAC audit server. Because MAB operates at Layer 2, the MAB authenticator does not normally know the IP address of the supplicant, and the supplicant might not have an IP address when it first contacts the authenticator. A supplicant that requires a DHCP-assigned IP address must be allowed access to a DHCP server before authentication. You must enable ARP and DHCP snooping on the switch to allow the MAB authenticator
57-23
to learn the IP address of the supplicant. To allow the IP address and unique session identifier information to be shared with the NAC audit server, you must enable the sending of certain RADIUS attributes. See the Configuring NAC Agentless Audit Support section on page 57-56. The client IP address and unique session identifier are shared in RADIUS Access-Requests and Access-Accepts using the following RADIUS cisco-av-pair vendor-specific attributes (VSAs):
Cisco-AVPair=identity-request=ip-address ip-address is the client IP address obtained by the switch through ARP or DHCP snooping. Cisco-AVPair=audit-session-id=audit session id string audit session id string is a UTF-8 encoding of a unique 96-bit identifier derived by the switch from the network access server (NAS) IP address, a session count, and the session start timestamp.
Using RADIUS Change of Authorization

With Cisco IOS Release 12.2(33)SXI4 and later releases, the switch can accept and execute unsolicited Change of Authorization (CoA) messages from the authentication server (AS). CoA is an extension to the RADIUS protocol that allows the AS to make dynamic and unsolicited changes to the authorization information of an active session hosted by a network access device, such as a switch. For more information about CoA, see RFC 5176. The Catalyst 6500 series switch supports per-session and per-policy CoA commands relating to 802.1X, MAB, and web-based authentication sessions.
Per-Session CoA
Using per-session CoA commands, the AS can cause the switch to terminate a session or to force a reauthentication of the session. To terminate a session, the AS can instruct the switch to perform one of the following actions:

End the sessionThe AS sends a CoA Disconnect-Request (see RFC 5176), causing the switch to delete all state information about the session. Shut down the portThe AS sends the following VSA to force an administrative shutdown of the port: Cisco-AVPair=subscriber:command=disable-host-port Bounce the portThe AS sends the following VSA to force the switch link to be taken down, then up again: Cisco-AVPair=subscriber:command=bounce-host-port
By default, the switch accepts and executes per-session CoA commands, but you can configure the switch to ignore CoA shutdown or bounce commands directed at specific ports. The AS sends the following VSA to force a reauthentication of the session: Cisco-AVPair=subscriber:command=re-authenticate
Per-Policy CoA
Using per-policy CoA commands, the AS can instruct the switch to update the contents of a DACL or a Filter-ID ACL, and apply the updated policy information to all sessions that currently have the affected ACL applied.
57-24
OL-13013-06
Chapter 57
Using 802.1X Authentication with Wake-on-LAN

With Release 12.2(33)SXH and later releases, the 802.1X authentication with wake-on-LAN (WoL) feature allows dormant PCs to be powered up when the switch receives a specific Ethernet frame, known as the magic packet. You can use this feature in environments where administrators need to connect to systems that have been powered down. When a host that uses WoL is attached through an 802.1X port and the host powers off, the 802.1X port becomes unauthorized. The port can only receive and send EAPOL packets, and WoL magic packets cannot reach the host. When the PC is powered off, it is not authorized, and the switch port is not opened. When the switch uses 802.1X authentication with WoL, the switch forwards traffic to unauthorized 802.1X ports, including magic packets. While the port is unauthorized, the switch continues to block ingress traffic other than EAPOL packets. The host can receive packets but cannot send packets to other devices in the network.
Note
If PortFast is not enabled on the port, the port is forced to the bidirectional state. When you configure a port as unidirectional by using the authentication control-direction in interface configuration command (dot1x control-direction in command in Cisco IOS Release 12.2(33)SXH and earlier releases), the port changes to the spanning-tree forwarding state. The port can send packets to the host but cannot receive packets from the host. When you configure a port as bidirectional by using the authentication control-direction both interface configuration command (dot1x control-direction both command in Cisco IOS Release 12.2(33)SXH and earlier releases), the port is access-controlled in both directions. The port does not receive packets from or send packets to the host.
Understanding MAC Move

Release 12.2(33)SXI4 and later releases support the Mac move feature. When a MAC address is authenticated on one switch port, that address is not allowed on another authentication manager-enabled port of the switch. If the switch detects that same MAC address on another authentication manager-enabled port, the address is not allowed. There are situations where a MAC address might need to move from one port to another on the same switch. For example, when there is another device (for example a hub or an IP phone) between an authenticated host and a switch port, you might want to disconnect the host from the device and connect it directly to another port on the same switch. You can globally enable MAC move so the device is reauthenticated on the new port. When a host moves to a second port, the session on the first port is deleted, and the host is reauthenticated on the new port. When a MAC address moves from one port to another, the switch terminates the authenticated session on the original port and initiates a new authentication sequence on the new port. Port security behavior remains the same when you configure MAC move.
Note
MAC move is supported in all host modes. (The authenticated host can move to any port on the switch, no matter which host mode is enabled on the that port.) MAC move is supported with port security. The MAC move feature applies to both voice and data hosts.
57-25
In open authentication mode, a MAC address is immediately moved from the original port to the new port, with no requirement for authorization on the new port.
For more information see the Enabling MAC Move section on page 57-67.
Understanding MAC Replace

Release 12.2(33)SXI4 and later releases support the Mac replace feature. The MAC replace feature can be configured to address the violation that occurs when a host attempts to connect to a port where another host was previously authenticated.
Note
The Mac replace feature is not supported on ports in multiauth mode, because violations are not triggered in that mode. The Mac replace feature is not supported on ports in multiple host mode, because in that mode, only the first host requires authentication.
If you configure the authentication violation interface configuration command with the replace keyword, the authentication process on a port in multi-domain mode is:

A new MAC address is received on a port with an existing authenticated MAC address. The authentication manager replaces the MAC address of the current data host on the port with the new MAC address. The authentication manager initiates the authentication process for the new MAC address. If the authentication manager determines that the new host is a voice host, the original voice host is removed.
If a port is in open authentication mode, any new MAC address is immediately added to the MAC address table. For more information see the Enabling MAC Replace section on page 57-67.
Understanding 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT)
Release 12.2(33)SXJ and later releases support the Network Edge Access Topology (NEAT) feature. NEAT extends identity to areas outside the wiring closet (such as conference rooms). This allows any type of device to authenticate on the port.
802.1x switch supplicant: You can configure a switch to act as a supplicant to another switch by using the 802.1x supplicant feature. This configuration is helpful in a scenario, where, for example, a switch is outside a wiring closet and is connected to an upstream switch through a trunk port. A switch configured with the 802.1x switch supplicant feature authenticates with the upstream switch for secure connectivity. Once the supplicant switch authenticates successfully the port mode changes from access to trunk. If the access VLAN is configured on the authenticator switch, it becomes the native VLAN for the trunk port after successful authentication.
57-26
OL-13013-06
Chapter 57
You can enable MDA or multiauth mode on the authenticator switch interface that connects to one more supplicant switches. On the authenticator switch interface, multihost mode is not supported and in MDA mode voice client is not supported. Use the dot1x supplicant force-multicast global configuration command on the supplicant switch for Network Edge Access Topology (NEAT) to work in all host modes.
Host Authorization: Ensures that only traffic from authorized hosts (connecting to the switch with supplicant) is allowed on the network. The switches use Client Information Signalling Protocol (CISP) to send the MAC addresses connecting to the supplicant switch to the authenticator switch, as shown in Figure 57-7. Auto enablement: Automatically enables trunk configuration on the authenticator switch, allowing user traffic from multiple VLANs coming from supplicant switches. Configure the cisco-av-pair as device-traffic-class=switch at the ACS. (You can configure this under the group or the user settings.)
Authenticator and Supplicant Switch using CISP
Figure 57-7
1 5
205718
1 3 5
Workstations (clients) Authenticator switch Trunk port
2 4
Supplicant switch (outside wiring closet) Access control server (ACS)
When configuring NEAT and CISP, follow these guidelines and restrictions:
You can configure NEAT ports with the same configurations as the other authentication ports. When the supplicant switch authenticates, the port mode is changed from access to trunk based on the switch vendor-specific attributes (VSAs). (device-traffic-class=switch). The VSA changes the authenticator switch port mode from access to trunk and enables 802.1x trunk encapsulation and the access VLAN if any would be converted to a native trunk VLAN. VSA does not change any of the port configurations on the supplicant
For more information, see the Configuring an Authenticator and a Supplicant Switch with NEAT section on page 57-60.
57-27
Chapter 57 802.1X Authentication Feature Configuration Guidelines
802.1X Authentication Feature Configuration Guidelines

This section has configuration guidelines for these features:

802.1X Authentication, page 57-28 802.1X Host Mode, page 57-29 VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass, page 57-30 MAC Authentication Bypass, page 57-31 Web-Based Authentication, page 57-32
802.1X Authentication
When configuring 802.1X authentication, note the following guidelines:
In releases where CSCtg01609 is not resolved, on ports with the authentication port-control auto command or the dot1x pae supplicant command configured, you cannot successfully enter the no switchport command. In releases where CSCtg01609 is resolved, on ports with any authentication, dot1x, or mab command configured, you cannot successfully enter the no switchport command.
Note
Enter the default interface type slot/port command to revert to the default port configuration.
When 802.1X authentication is enabled, ports are authenticated before any other Layer 2 or Layer 3 features are enabled. If you try to change the mode of an 802.1X-enabled port (for example, from access to trunk), an error message appears, and the port mode is not changed. With Cisco IOS Release 12.2(33)SXH and later releases, you can configure port security and 802.1X port-based authentication on the same port. We do not recommend configuring both together. If the VLAN to which an 802.1X-enabled port is assigned changes, this change is transparent and does not affect the switch. For example, this change occurs if a port is assigned to a RADIUS server-assigned VLAN and is then assigned to a different VLAN after reauthentication. If the VLAN to which an 802.1X port is assigned to shut down, disabled, or removed, the port becomes unauthorized. For example, the port is unauthorized after the access VLAN to which a port is assigned shuts down or is removed.
The 802.1X protocol is supported on Layer 2 static-access ports, voice VLAN ports, and Layer 3 routed ports, but it is not supported on these port types:
Trunk portIf you try to enable 802.1X authentication on a trunk port, an error message
appears, and 802.1X authentication is not enabled. If you try to change the mode of an 802.1X-enabled port to trunk, an error message appears, and the port mode is not changed.
Dynamic portsA port in dynamic mode can negotiate with its neighbor to become a trunk
port. If you try to enable 802.1X authentication on a dynamic port, an error message appears, and 802.1X authentication is not enabled. If you try to change the mode of an 802.1X-enabled port to dynamic, an error message appears, and the port mode is not changed.
57-28
OL-13013-06
Chapter 57
Configuring IEEE 802.1X Port-Based Authentication 802.1X Authentication Feature Configuration Guidelines
Dynamic-access portsIf you try to enable 802.1X authentication on a dynamic-access (VLAN
Query Protocol [VQP]) port, an error message appears, and 802.1X authentication is not enabled. If you try to change an 802.1X-enabled port to dynamic VLAN assignment, an error message appears, and the VLAN configuration is not changed.
EtherChannel portDo not configure a port that is an active or a not-yet-active member of an
EtherChannel as an 802.1X port. If you try to enable 802.1X authentication on an EtherChannel port, an error message appears, and 802.1X authentication is not enabled.
Note
In software releases earlier than Release 12.2(33)SXH, if 802.1X authentication is enabled on a not-yet active port of an EtherChannel, the port does not join the EtherChannel.
Switched Port Analyzer (SPAN) and Remote SPAN (RSPAN) destination portsYou can
enable 802.1X authentication on a port that is a SPAN or RSPAN destination port. However, 802.1X authentication is disabled until the port is removed as a SPAN or RSPAN destination port. You can enable 802.1X authentication on a SPAN or RSPAN source port.
Note
In software releases earlier than Release 12.2(33)SXH, 802.1X authentication is not supported on voice VLAN ports.
Before globally enabling 802.1X authentication on a switch by entering the dot1x system-auth-control global configuration command, remove the EtherChannel configuration from the interfaces on which 802.1X authentication and EtherChannel are configured. Because all traffic from unauthenticated hosts is forwarded to the switch processor, we recommend that you apply rate limiting to this traffic.
802.1X Host Mode

When configuring any host mode, note the following guidelines:
In most cases when the host mode is changed on a port, any existing 802.1X authentications on that port are deleted. Exceptions are when changing from the single-host mode to any other mode, and when changing from multidomain mode to multiauth mode. In these two cases, existing 802.1X authentications are retained. If you enter the authentication open interface configuration command in Cisco IOS Release 12.2(33)SXI and later releases, any new MAC address detected on the port will be allowed unrestricted Layer 2 access to the network even before any authentication has succeeded. If you use this command, you should use static default ACLs to restrict Layer 3 traffic. For additional details, see the Pre-Authentication Open Access section on page 57-11. If the multiple-hosts port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received), all attached clients are denied access to the network. A third-party IP phones MAC address will initially be assigned to the data VLAN. When tagged voice packets are observed, the device will be removed from the data VLAN and placed on the voice VLAN.
When configuring multiple-hosts mode, note the following guideline:
When configuring MDA host mode, note the following guideline:
57-29
Chapter 57 802.1X Authentication Feature Configuration Guidelines
When configuring multiauth host mode, note the following guidelines:
If one client on a multiauth port becomes unauthorized (reauthentication fails or an EAPOL-logoff message is received from that client), the authorization status of the other attached clients is not changed. RADIUS-assigned VLANs are not supported on multiauth ports, which can have only one data VLAN. If the authentication server sends VLAN-related attributes, the authentication will succeed but the VLAN assignment will be ignored. Although multiple hosts are allowed on the data VLAN, only one host is allowed on the voice VLAN. When one IP phone has been authenticated, further IP phones on the same port will be denied authentication. A multiauth port does not support a guest VLAN, authentication-fail VLAN, or a critical VLAN.
VLAN Assignment, Guest VLAN, Restricted VLAN, and Inaccessible Authentication Bypass
When configuring VLAN assignment, guest VLAN, restricted VLAN, and inaccessible authentication bypass, note the following guidelines:

When 802.1X authentication is enabled on a port, you cannot configure a port VLAN that is equal to a voice VLAN. The 802.1X authentication with VLAN assignment feature is not supported on trunk ports, dynamic ports, or with dynamic-access port assignment through a VMPS. You can configure any VLAN except an RSPAN VLAN, a private primary PVLAN, or a voice VLAN as an 802.1X guest VLAN. The guest VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports. After you configure a guest VLAN for an 802.1X port to which a DHCP client is connected, you might need to get a host IP address from a DHCP server. You can change the settings for restarting the 802.1X authentication process on the switch before the DHCP process on the client times out and tries to get a host IP address from the DHCP server. Decrease the settings for the 802.1X authentication process (dot1x timeout quiet-period and dot1x timeout tx-period interface configuration commands). The amount to decrease the settings depends on the connected 802.1X client type. When configuring the 802.1X VLAN user distribution feature, follow these guidelines:
A maximum of 100 VLAN groups can be configured, and a maximum of 4094 VLANs can be
mapped to a VLAN group.

A VLAN can be mapped to more than one VLAN group. A guest VLAN, a critical VLAN, or a restricted VLAN can be mapped to a VLAN group. A VLAN group name cannot be specified as a guest VLAN, a critical VLAN, or a restricted
VLAN.
You can modify a VLAN group by adding or removing a VLAN, but at least one VLAN must
be mapped to the VLAN group. If you remove the last VLAN from the VLAN group, the VLAN group is deleted.
Removing an existing VLAN from the VLAN group name does not revoke the authentication
status of the ports in the VLAN, but the mappings are removed from the existing VLAN group.
57-30
OL-13013-06
Chapter 57
Configuring IEEE 802.1X Port-Based Authentication 802.1X Authentication Feature Configuration Guidelines
Deleting an existing VLAN group name does not revoke the authentication status of the ports
in any VLAN within the group, but the VLAN mappings to the VLAN group are removed.
When configuring the inaccessible authentication bypass feature, follow these guidelines:
The inaccessible authentication bypass feature is supported on 802.1X ports in single-host
mode, multiple-hosts mode, and MDA mode.

If the client is running Windows XP and the port to which the client is connected is in the
critical-authentication state, Windows XP might report that the interface is not authenticated.
If the Windows XP client is configured for DHCP and has an IP address from the DHCP server,
receiving an EAP-Success message on a critical port might not reinitiate the DHCP configuration process.
You can configure the inaccessible authentication bypass feature and the critical VLAN on an
802.1X port. If the switch tries to reauthenticate a critical port in a critical VLAN and all the RADIUS servers are unavailable, the switch changes the port state to the critical authentication state and the port remains in the critical VLAN.
You can configure the inaccessible bypass feature and port security on the same port.
You can configure any VLAN except an RSPAN VLAN or a voice VLAN as an 802.1X restricted VLAN. The restricted VLAN feature is not supported on internal VLANs (routed ports) or trunk ports; it is supported only on access ports.
MAC Authentication Bypass

When configuring MAC authentication bypass, note the following guidelines:
Unless otherwise stated, the MAC authentication bypass guidelines are the same as the 802.1X authentication guidelines. For more information, see the 802.1X Authentication section on page 57-28. If you disable MAC authentication bypass from a port after the port has been authorized with its MAC address, the session will be removed. When MAC authentication bypass with EAP has been enabled on an interface, it is not disabled by a subsequent default interface command on the interface. If the port is in the unauthorized state and the client MAC address is not the authentication-server database, the port remains in the unauthorized state. However, if the client MAC address is added to the database, the switch can use MAC authentication bypass to reauthorize the port. If the port is in the authorized state, the port remains in this state until reauthorization occurs. To use MAC authentication bypass on a routed port, make sure that MAC address learning is enabled on the port. In Release 12.2(33)SXH and later releases, you can optionally configure a timeout period for hosts that are connected by MAC authentication bypass but are inactive. The range is 1 to 65535 seconds, but should be set to a value less than the reauthentication timeout. You must enable port security before configuring a timeout value. For more information, see the Configuring Port Security section on page 59-5.
57-31
Chapter 57 Configuring 802.1X Port-Based Authentication
Web-Based Authentication
When configuring web-based authentication, note the following guidelines:

Fallback to web-based authentication is configured on switch ports in access mode. Ports in trunk mode are not supported. Fallback to web-based authentication is not supported on EtherChannels or EtherChannel members. Although fallback to web-based authentication is an interface-specific configuration, the web-based authentication fallback behavior is defined in a global fallback profile. If the global fallback configuration changes, the new profile will not be used until the next instance of authentication fallback.
For detailed information on configuring web-based authentication, see Chapter 58, Configuring Web-Based Authentication.
Configuring 802.1X Port-Based Authentication

These sections describe how to configure 802.1X port-based authentication:

Default 802.1X Port-Based Authentication Configuration, page 57-33 802.1X Authentication Feature Configuration Guidelines, page 57-28 Enabling 802.1X Authentication, page 57-34 Configuring Switch-to-RADIUS-Server Communication, page 57-36 Configuring 802.1X Authenticator Host Mode, page 57-37 Enabling Fallback Authentication, page 57-39 Enabling Periodic Reauthentication, page 57-41 Manually Reauthenticating the Client Connected to a Port, page 57-42 Initializing Authentication for the Client Connected to a Port, page 57-42 Removing 802.1X Client Information, page 57-43 Clearing Authentication Sessions, page 57-43 Changing 802.1X Timeouts, page 57-43 Setting the Switch-to-Client Frame Retransmission Number, page 57-45 Setting the Reauthentication Number, page 57-46 Configuring IEEE 802.1X Accounting, page 57-46 Configuring a Guest VLAN, page 57-48 Configuring a Restricted VLAN, page 57-49 Configuring the Inaccessible Authentication Bypass Feature, page 57-51 Configuring MAC Authentication Bypass, page 57-54 Configuring NAC Layer 2 IEEE 802.1X Validation, page 57-55 Configuring NAC Agentless Audit Support, page 57-56 Configuring the Switch for DACLs or Redirect URLs, page 57-57 Configuring a Port to Ignore CoA Commands, page 57-58
57-32
OL-13013-06
Chapter 57
Configuring IEEE 802.1X Port-Based Authentication Configuring 802.1X Port-Based Authentication
Configuring 802.1X Authentication with WoL, page 57-58 Disabling 802.1X Authentication on the Port, page 57-59 Resetting the 802.1X Configuration to the Default Values, page 57-59 Displaying 802.1X Status, page 57-62 Displaying Authentication Methods and Status, page 57-63 Displaying MAC Authentication Bypass Status, page 57-66 Enabling MAC Move, page 57-67 Enabling MAC Replace, page 57-67 Configuring an Authenticator and a Supplicant Switch with NEAT, page 57-60
Default 802.1X Port-Based Authentication Configuration

Table 57-2 shows the default 802.1X configuration.
Table 57-2 Default 802.1X Configuration
Feature Switch 802.1X enable state Per-port 802.1X enable state
Default Setting Disabled. Disabled (force-authorized). The port sends and receives normal traffic without 802.1X-based authentication of the client.
AAA RADIUS server

Disabled.

IP address UDP authentication port Key
None specified. 1812. None specified.
Host mode Control direction Periodic reauthentication Number of seconds between reauthentication attempts Reauthentication number
Single-host mode. Bidirectional control. Disabled. 3600 seconds. 2 times (number of times that the switch restarts the authentication process before the port changes to the unauthorized state). 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).
Quiet period
Retransmission time
57-33
Table 57-2
Default 802.1X Configuration (continued)
Feature Maximum retransmission number
Default Setting 2 times (number of times that the switch will send an EAP-request/identity frame before restarting the authentication process). 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). Disabled. None specified. Disabled. None specified. None specified. Disabled.
Note
Client timeout period
Authentication server timeout period
Inactivity timeout Guest VLAN Inaccessible authentication bypass Restricted VLAN Authenticator (switch) mode MAC authentication bypass
When MAC authentication bypass with EAP has been enabled on an interface, it is not disabled by a subsequent default interface command on the interface.
Enabling 802.1X 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 allow VLAN assignment, you must enable AAA authorization to configure the switch for all network-related service requests. The 802.1X AAA process is as follows:
1. 2. 3. 4. 5.
A user connects to a port on the switch. Authentication is performed. VLAN assignment is enabled, as appropriate, based on the RADIUS server configuration. The switch sends a start message to an accounting server. Reauthentication is performed, as necessary.
57-34
OL-13013-06
Chapter 57
6. 7. 8.
The switch sends an interim accounting update to the accounting server that is based on the result of reauthentication. The user disconnects from the port. The switch sends a stop message to the accounting server.
To configure 802.1X port-based authentication, perform this task: Command

Step 1 Step 2
Router(config)# aaa new-model Router(config)# aaa authentication dot1x {default} method1 [method2...]
Purpose Enables AAA. Creates an 802.1X port-based authentication method list. To create a default list that is used when a named list is not specified in the aaa authentication command, use the default keyword followed by the method that is to be used in default situations. The default method list is automatically applied to all ports. For method1, enter the group radius keywords to use the list of all RADIUS servers for authentication. Though other keywords are visible in the command-line help string, only the group radius keywords are supported.
Step 3 Step 4
Router(config)# dot1x system-auth-control Router(config)# aaa authorization network {default} group radius
Globally enables 802.1X port-based authentication. (Optional) Configures the switch to use user-RADIUS authorization for all network-related service requests such as VLAN assignment. Specifies the IP address of the RADIUS server. Specifies the authentication and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. (Optional) Enables static sharing, which allows more efficient use of the TCAM when a number of interfaces have the same PACL and VLAN-based features. Enters interface configuration mode and specifies the interface to be enabled for 802.1X authentication. Sets the port to access mode only if you configured the RADIUS server in previous steps. Enables port-based authentication on the interface. The no form of the command disables port-based authentication on the interface. For feature interaction information, see the 802.1X Authentication Feature Configuration Guidelines section on page 57-28. Enables 802.1X authentication on the interface.
Step 5 Step 6
Router(config)# radius-server host ip-address Router(config)# radius-server key string
Step 7
Router(config)# mls acl tcam static-share
Step 8 Step 9
Router(config)# interface type1 slot/port
Router(config-if)# switchport mode access
Step 10 Cisco IOS Release 12.2(33)SXI or later releases:

Router(config-if)# authentication port-control auto
Cisco IOS Release 12.2(33)SXH or earlier releases:

Router(config-if)# dot1x port-control auto
Step 11 Router(config-if)# dot1x pae authenticator
57-35
Command
Step 12 Router(config)# end Step 13 Router# show dot1x all
Purpose 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.
1.
This example shows how to enable AAA and 802.1X on Fast Ethernet port 5/1:
Router(config)# aaa new-model Router(config)# aaa authentication dot1x default group radius Router(config)# dot1x system-auth-control Router(config)# mls acl tcam static-share Router(config)# interface fastethernet 5/1 Router(config-if)# authentication port-control auto Router(config-if)# dot1x pae authenticator Router(config-if)# end

Router# show dot1x all Sysauthcontrol Dot1x Protocol Version Enabled 2
Dot1x Info for GigabitEthernet1/7 ----------------------------------PAE = AUTHENTICATOR PortControl = AUTO ControlDirection = Both HostMode = SINGLE_HOST QuietPeriod = 60 ServerTimeout = 30 SuppTimeout = 30 ReAuthMax = 2 MaxReq = 2 TxPeriod = 30
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.
57-36
OL-13013-06
Chapter 57
To configure the RADIUS server parameters, perform this task: Command

Step 1 Step 2
Router(config)# ip radius source-interface interface_name Router(config)# radius-server host {hostname | ip_address}
Purpose Specifies that the RADIUS packets have the IP address of the 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 3
Router(config)# radius-server key string
Configures the authorization and encryption key used between the switch and the RADIUS daemon running on the RADIUS server.
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. 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, see the Cisco IOS Security Configuration Guide, Release 12.2, publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/configuration/guide/fsecur_c.html and the Cisco IOS Security Command Reference, Release 12.2, publication at this URL: http://www.cisco.com/en/US/docs/ios/12_2/security/command/reference/fsecur_r.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, see the RADIUS server documentation. This example shows how to configure the RADIUS server parameters on the switch:
Router(config)# ip radius source-interface Vlan80 Router(config)# radius-server host 172.l20.39.46 Router(config)# radius-server key rad123
Configuring 802.1X Authenticator Host Mode

An 802.1X-enabled port can grant access to a single client or multiple clients as described in the 802.1X Host Modes section on page 57-9.
57-37
To configure the host mode of an 802.1X-authorized port, perform this task: Command
Step 1 Step 2
Purpose Specifies the port to be configured, and enters interface configuration mode. Enables port-based authentication on the interface. The no form of the command disables port-based authentication on the interface. For feature interaction information, see the 802.1X Authentication Feature Configuration Guidelines section on page 57-28. Enables 802.1X authentication on the interface. Allows a single authenticated host (client) on an authorized port. Allows multiple clients on an authorized port when one client is authenticated. Allows a single IP phone and a single data client to independently authenticate on an authorized port. Allows a single IP phone and multiple data clients to independently authenticate on an authorized port.
Cisco IOS Release 12.2(33)SXI or later releases:


Step 3 Step 4
Router(config-if)# dot1x pae authenticator

Router(config-if)# authentication host-mode single-host Router(config-if)# authentication host-mode multi-host Router(config-if)# authentication host-mode multi-domain Router(config-if)# authentication host-mode multi-auth

Router(config-if)# dot1x host-mode {single-host | multi-host}
Router(config-if)# authentication open
(Optional) With Cisco IOS Release 12.2(33)SXI or later releases, enables pre-authentication open access. Returns to privileged EXEC mode. Verifies your entries.
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)# authentication port-control auto Router(config-if)# dot1x pae authenticator Router(config-if)# authentication host-mode multi-host

Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x port-control auto Router(config-if)# dot1x host-mode multi-host
57-38
OL-13013-06
Chapter 57
Enabling Fallback Authentication

On a port in multiauth mode, either or both of MAB and web-based authentication can be configured as fallback authentication methods for non-802.1X hosts (those that do not respond to EAPOL). You can configure the order and priority of the authentication methods. For detailed configuration information for MAB, see the Configuring MAC Authentication Bypass section on page 57-54. For detailed configuration information for web-based authentication, see Chapter 58, Configuring Web-Based Authentication. In Cisco IOS Release 12.2(33)SXI and later releases, to enable fallback authentication, perform this task: Command
Router(config)# ip admission name rule-name proxy http Router(config)# fallback profile profile-name Router(config-fallback-profile)# ip access-group rule-name in Router(config-fallback-profile)# ip admission name rule-name
Purpose Configures an authentication rule for web-based authentication. Creates a fallback profile for web-based authentication. Specifies the default ACL to apply to network traffic before web-based authentication. Associates an IP admission rule with the profile, and specifies that a client connecting by web-based authentication uses this rule. Returns to global configuration mode. Specifies the port to be configured, and enters interface configuration mode. Enables authentication on the port. (Optional) Specifies the fallback order of authentication methods to be used. The three values of method, in the default order, are dot1x, mab, and webauth. The specified order also determines the relative priority of the methods for reathentication, from highest to lowest. (Optional) Overrides the relative priority of authentication methods to be used. The three values of method, in the default order of priority, are dot1x, mab, and webauth. Specifies that the next configured authentication method will be used if authentication fails. Enables MAC authentication bypass. The optional eap keyword specifies that the EAP extension is used during RADIUS authentication. Enables web-based authentication using the specified profile.
Router(config-fallback-profile)# exit Router(config)# interface type

1
slot/port
Router(config-if)# authentication port-control auto Router(config-if)# authentication order method1 [method2] [method3]
Step 9
Router(config-if)# authentication priority method1 [method2] [method3]
Step 10 Router(config-if)# authentication event fail

action next-method
Step 11 Router(config-if)# mab [eap]
Step 12 Router(config-if)# authentication fallback

profile-name
57-39
Command
Step 13 Router(config-if)# authentication violation
[shutdown | restrict]
Purpose (Optional) Configures the disposition of the port if a security violation occurs. The default action is to shut down the port. If the restrict keyword is configured, the port will not be shutdown, but trap entries will be installed for the violating MAC address, and traffic from that MAC address will be dropped. (Optional) Configures the inactivity timeout value for MAB and 802.1X. By default, inactivity aging is disabled for a port.

Step 14 Router(config-if)# authentication timer

inactivity {seconds | server}
secondsSpecifies inactivity timeout period. The range is from 1 to 65535 seconds. serverSpecifies that the inactivity timeout period value will be obtained from the authentication server.
Step 15 Router(config-if)# authentication timer restart

seconds
(Optional) Specifies a period after which the authentication process will restart in an attempt to authenticate an unauthorized port.
secondsSpecifies the restart period. The range is from 1 to 65535 seconds.
Step 16 Router(config-if)# exit Step 17 Router(config)# ip device tracking Step 18 Router(config)# exit Step 19 Router# show dot1x interface type slot/port
1
Returns to global configuration mode. Enables the IP device tracking table, which is required for web-based authentication. Returns to privileged EXEC mode. Verifies your entries.
This example shows how to enable 802.1X fallback to MAB, and then to enable web-based authentication, on an 802.1X-enabled port:
Router(config)# ip admission name rule1 proxy http Router(config)# fallback profile fallback1 Router(config-fallback-profile)# ip access-group default-policy in Router(config-fallback-profile)# ip admission rule1 Router(config-fallback-profile)# exit Router(config)# interface gigabit1/1 Router(config-if)# switchport mode access Router(config-if)# authentication port-control auto Router(config-if)# dot1x pae authenticator Router(config-if)# authentication order dot1x mab webauth Router(config-if)# mab eap Router(config-if)# authentication fallback fallback1 Router(config-if)# exit Router(config)# ip device tracking Router(config)# exit
Cisco IOS Release 12.2(33)SXH:

Router(config)# ip admission name rule1 proxy http Router(config)# fallback profile fallback1 Router(config-fallback-profile)# ip access-group default-policy in
57-40
OL-13013-06
Chapter 57
Router(config-fallback-profile)# ip admission rule1 Router(config-fallback-profile)# exit Router(config)# interface gigabit1/1 Router(config-if)# switchport mode access Router(config-if)# dot1x port-control auto Router(config-if)# dot1x fallback fallback1 Router(config-if)# exit Router(config)# ip device tracking Router(config)# exit
Enabling Periodic Reauthentication

With Release 12.2(33)SXH and later releases, you can enable periodic 802.1X client reauthentication and specify how often it occurs. You can specify the reauthentication period manually or you can use the session-timeout period specified by the RADIUS server. If you enable reauthentication without specifying a time period, the number of seconds between reauthentication attempts is 3600. 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
Purpose Specifies the port to be configured, and enters interface configuration mode. Enables periodic reauthentication of the client, which is disabled by default.

Router(config-if)# authentication periodic

Router(config-if)# dot1x reauthentication
Step 3

Router(config-if)# authentication timer reauthenticate [seconds | server]
Specifies the number of seconds between reauthentication attempts using these keywords:

Router(config-if)# dot1x timeout reauth-period [seconds | server]
secondsSets the number of seconds from 1 to 65535; the default is 3600 seconds. serverSets the number of seconds based on the value of the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute [29]).
This command affects the operation of the switch only if periodic reauthentication is enabled.
Step 4 Step 5
Router(config-if)# end Router# show dot1x interface type slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to enable periodic reauthentication and set the number of seconds between reauthentication attempts to 4000:
Router(config)# interface fastethernet 5/1 Router(config-if)# authentication periodic
57-41
Router(config-if)# authentication timer reauthenticate 4000

Router(config)# interface fastethernet 5/1 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. type = fastethernet, gigabitethernet, or tengigabitethernet
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
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:
Command
Step 1 Step 2
Router# dot1x initialize interface type1 slot/port Router# show dot1x all 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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
57-42
OL-13013-06
Chapter 57
Removing 802.1X Client Information

To completely delete all existing supplicants from an interface or from all the interfaces on the switch, perform this task: Command
Step 1
Router# clear dot1x interface type
1
Purpose
slot/port
Removes 802.1X client information for the client connected to the specified port. Removes 802.1X client information for all clients connected to all ports. Verifies your entries.
Router# clear dot1x all
Step 2
Router# show dot1x all 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to remove 802.1X client information for the client connected to Fast Ethernet port 5/1:
Router# clear dot1x interface fastethernet 5/1
Clearing Authentication Sessions

To clear all or selected authentication sessions, perform this task: Command
Router# clear authentication sessions [handle handle] [interface interface] [mac mac] [method method]
Purpose Clears current authentication sessions. With no options specified, all current active sessions will be cleared. The keywords can be added and combined to clear specific sessions or subset of sessions.
This example shows how to clear all MAB authentication sessions connected to Fast Ethernet port 5/1:
Router# clear authentication sessions interface fastethernet 5/1 method mab
Changing 802.1X Timeouts

You can change several 802.1X timeout attributes using the dot1x timeout {attribute} seconds command form in the interface configuration mode. This section shows in detail how to change the quiet period timeout, followed by descriptions of how to change other 802.1X timeouts using the same command form.
Setting 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 dot1x timeout quiet-period interface configuration command controls the idle period. 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 number smaller than the default.
57-43
To change the quiet period, perform this task: Command

Step 1 Step 2
Purpose Specifies the port to be configured, and enters interface configuration mode. 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 privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x timeout quiet-period seconds
Step 3 Step 4
Router(config-if)# end Router# show dot1x all 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to set the quiet period on the switch to 30 seconds:
Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x timeout quiet-period 30
This example shows how to restore the default quiet period on the switch:
Router(config-if)# no dot1x timeout quiet-period
Setting 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 operational problems with certain clients and authentication servers. To change the amount of time that the switch switch waits for a response to an EAP-request/identity frame from the client before retransmitting the request, use the dot1x timeout tx-period seconds command in the interface configuration mode. The range is 1 to 65535 seconds; the default is 30. To return to the default retransmission time, use the no dot1x timeout tx-period command. 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)# interface fastethernet 5/1 Router(config-if)# 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. To set the amount of time that the switch waits for notification, use the dot1x timeout supp-timeout seconds command in the interface configuration mode. The range is 1 to 65535 seconds; the default is 30. To return to the default retransmission time, use the no dot1x supp-timeout command.
57-44
OL-13013-06
Chapter 57
This example shows how to set the switch-to-client retransmission time for the EAP-request frame to 25 seconds:
Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x timeout supp-timeout 25
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. To set the value for the retransmission of Layer 4 packets from the switch to the authentication server, use the dot1x timeout server-timeout seconds command in the interface configuration mode. The range is 1 to 65535 seconds; the default is 30. To return to the default retransmission time, use the no dot1x server-timeout command. This example shows how to set the switch-to-authentication-server retransmission time for Layer 4 packets to 25 seconds:
Router(config)# interface fastethernet 5/1 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 operational 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
Specifies the port to be configured, and enters interface configuration mode. 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 privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x max-req count
Step 3 Step 4
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)# interface fastethernet 5/1 Router(config-if)# dot1x max-req 5
57-45
Setting the Reauthentication Number

You can also change the number of times that the switch restarts the authentication process before the port changes to the unauthorized state.
Note
You should change the default value of this command only to adjust for unusual circumstances such as unreliable links or specific operational problems with certain clients and authentication servers. To set the reauthentication number, perform this task:
Command
Step 1 Step 2
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Sets the number of times that the switch restarts the authentication process before the port changes to the unauthorized state. The range is 0 to 10; the default is 2. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x max-reauth-req count
Step 3 Step 4
This example shows how to set 4 as the number of times that the switch restarts the authentication process before the port changes to the unauthorized state:
Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x max-reauth-req 4
Configuring IEEE 802.1X Accounting

Enabling AAA system accounting with 802.1X accounting allows system reload events to be sent to the accounting RADIUS server for logging. The server then can determine that all active 802.1X sessions are closed. Because RADIUS uses the unreliable UDP transport protocol, accounting messages might be lost due to poor network conditions. If the switch does not receive the accounting response message from the RADIUS server after a configurable number of retransmissions of an accounting request, this system message appears:
Accounting message %s for session %s failed to receive Accounting Response.
When the stop message is not sent successfully, this message appears:
00:09:55: %RADIUS-3-NOACCOUNTINGRESPONSE: Accounting message Start for session 172.20.50.145 sam 11/06/03 07:01:16 11000002 failed to receive Accounting Response.
Note
You must configure the RADIUS server to perform accounting tasks, such as logging start, stop, and interim-update messages and time stamps. To turn on these functions, enable logging of Update/Watchdog packets from this AAA client in your RADIUS server Network Configuration tab. Next, enable CVS RADIUS Accounting in your RADIUS server System Configuration tab.
57-46
OL-13013-06
Chapter 57
To configure 802.1X accounting after AAA is enabled on your switch, perform this task: Command
Step 1 Step 2
Router(config)# aaa accounting dot1x default start-stop group radius Router(config)# aaa accounting system default start-stop group radius
Purpose Enables 802.1X accounting using the list of all RADIUS servers. (Optional) Enables system accounting (using the list of all RADIUS servers) and generates system accounting reload event messages when the switch reloads. Returns to privileged EXEc mode. Verifies your entries.
Step 3 Step 4
Router(config)# end Router# show running-config
Use the show radius statistics privileged EXEC command to display the number of RADIUS messages that do not receive the accounting response message. This example shows how to configure 802.1X accounting. The first command configures the RADIUS server, specifying 1813 as the UDP port for accounting:
Router(config)# radius-server host 172.120.39.46 auth-port 1812 acct-port 1813 key rad123 Router(config)# aaa accounting dot1x default start-stop group radius Router(config)# aaa accounting system default start-stop group radius
Configuring VLAN User Distribution

With Cisco IOS Release 12.2(33)SXI1 and later releases, you can define a VLAN group that contains multiple VLANs. For VLAN load balancing, you can then configure the RADIUS server to supply a VLAN group name as part of the response to a user during 802.1X authentication. If the supplied VLAN group name is found among the VLAN group names that you have defined, the newly authenticated user is placed in the least populated VLAN within the VLAN group. To configure a VLAN group, perform this task: Command
Step 1
Router(config)# vlan group group-name vlan-list vlan-list
Purpose Creates a VLAN group or adds VLANs to an existing VLAN group.
group-nameThe name of the VLAN group. The name may contain up to 32 characters and must begin with a letter. vlan-list vlan-listThe VLANs that belong to the VLAN group. Group members can be specified as a single VLAN ID, a list of VLAN IDs, or a VLAN ID range. Multiple entries are separated by a hyphen (-) or a comma (,).
Step 2
Router(config)# no vlan group group-name vlan-list vlan-list
(Optional) Removes the members specified by vlan-list from a VLAN group.

Note
When no VLANs remain in the VLAN group, the VLAN group is deleted.
Step 3
Router# show vlan group [group-name group-name]
Displays the VLANs and VLAN ranges that are members of the specified VLAN group or of all VLAN groups.
57-47
This example shows how to map VLANs 7 through 9 and 11 to a VLAN group:
Router(config)# vlan group ganymede vlan-list 7-9,11
This example shows how to remove VLAN 7 from a VLAN group:

Router(config)# no vlan group ganymede vlan-list 7
Configuring a Guest VLAN

With Cisco IOS Release 12.2(33)SXH and later releases, when you configure a guest VLAN, clients that are not 802.1X-capable are put into the guest VLAN when the server does not receive a response to its EAP request/identity frame. Clients that are 802.1X-capable but that fail authentication are not granted network access. When operating as a guest VLAN, a port functions in multiple-hosts mode regardless of the configured host mode of the port. To configure a guest VLAN, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Sets the port to access mode. or Configures the port as a private VLAN host port. The guest VLAN is not supported on routed or trunk ports.
Router(config-if)# switchport mode access or Router(config-if)# switchport mode private-vlan host
Step 3

Enables authentication on the port.

Step 4

Router(config-if)# authentication event no-response action authorize vlan vlan-id
Specifies an active VLAN as a guest VLAN. The range is 1 to 4094. You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, a private primary PVLAN, or a voice VLAN as a guest VLAN. Specifies whether the port authentication method is 802.1X or MAC address bypass. In Cisco IOS Release 12.2(33)SXH and earlier releases, this command is not needed, and the method will be 802.1X. Returns to privileged EXEC mode. Verifies your entries.

Router(config-if)# dot1x guest-vlan vlan-id
Step 5

Router(config-if)# dot1x pae authenticator or Router(config-if)# mab
Step 6 Step 7
57-48
OL-13013-06
Chapter 57
This example shows how to enable VLAN 2 as an 802.1X guest VLAN:

Router(config)# interface fastethernet 5/1 Router(config-if)# authentication port-control auto Router(config-if)# authentication event no-response action authorize vlan 2 Router(config-if)# dot1x pae authenticator

Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x port-control auto Router(config-if)# dot1x guest-vlan 2
This example shows how to set 3 seconds as the client notification timeout on the switch, to set 15 as the number of seconds that the switch waits for a response to an EAP-request/identity frame from the client before resending the request, and to enable VLAN 2 as an 802.1X guest VLAN when an 802.1X port is connected to a DHCP client:
Router(config-if)# Router(config-if)# Router(config-if)# Router(config-if)# dot1x timeout supp-timeout 3 dot1x timeout tx-period 15 authentication event no-response action authorize vlan 2 dot1x pae authenticator

Router(config-if)# dot1x timeout supp-timeout 3 Router(config-if)# dot1x timeout tx-period 15 Router(config-if)# dot1x guest-vlan 2
Configuring a Restricted VLAN

When you configure a restricted VLAN on a switch, clients that are 802.1X-compliant are moved into the restricted VLAN when the authentication server does not receive a valid username and password. When operating as a restricted VLAN, a port functions in single-host mode regardless of the configured host mode of the port. To configure a restricted VLAN, perform this task: Command
Step 1 Step 2
Purpose Specifies the port to be configured, and enters interface configuration mode. Sets the port to access mode. or Configures the port as a private-VLAN host port.
Router(config-if)# switchport mode access or Router(config-if)# switchport mode private-vlan host
57-49
Command
Step 3
Purpose Enables port-based authentication on the port.


Step 4

Router(config-if)# authentication event fail [retry retries] action authorize vlan vlan-id
Specifies an active VLAN as a restricted VLAN. The range for vlan-id is 1 to 4094. (Optional) The retry keyword specifies a number of authentication attempts to allow before a port moves to the restricted VLAN. You can configure any active VLAN except an internal VLAN (routed port), an RSPAN VLAN, a private primary PVLAN, or a voice VLAN as a restricted VLAN. (Optional) The max-attempts keyword specifies a number of authentication attempts to allow before a port moves to the restricted VLAN. Returns to privileged EXEC mode. Verifies your entries.

Router(config-if)# dot1x auth-fail vlan vlan-id
Step 5

Router(config-if)# dot1x auth-fail max-attempts max-attempts
Step 6 Step 7
To disable and remove the restricted VLAN, use the no form of the authentication event fail command or the dot1x auth-fail command. The port returns to the unauthorized state. You can configure the maximum number of authentication attempts allowed before a user is assigned to the restricted VLAN.
In Cisco IOS Release 12.2(33)SXI and later releases, you can set the number of attempts by using the retry keyword in the authentication event fail [retry retries] action authorize vlan command. The range of retries (allowable authentication attempts) is 1 to 5. The default is 2 attempts. In Cisco IOS Release 12.2(33)SXH, you can set the number of attempts by using the dot1x auth-fail max-attempts max-attempts interface configuration command. The range of max-attempts (allowable authentication attempts) is 1 to 3. The default is 3 attempts.
This example shows how to enable VLAN 2 as a restricted VLAN, with assignment of a host after 3 failed attempts:
Router(config)# interface fastethernet 5/1 Router(config-if)# authentication port-control auto Router(config-if)# authentication event fail retry 3 action authorize vlan 2 Router(config-if)# dot1x pae authenticator

Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x port-control auto Router(config-if)# dot1x auth-fail vlan 2 Router(config-if)# dot1x auth-fail max-attempts 3
57-50
OL-13013-06
Chapter 57
Configuring the Inaccessible Authentication Bypass Feature

You can configure the inaccessible bypass feature, also referred to as critical authentication or the AAA fail policy. To configure the port as a critical port and enable the inaccessible authentication bypass feature, perform this task: Command
Step 1
Router(config)# radius-server dead-criteria time time tries tries
Purpose (Optional) Sets the conditions that are used to decide when a RADIUS server is considered unavailable or dead. The range for time is from 1 to 120 seconds. The switch dynamically determines the default seconds value that is 10 to 60 seconds. The range for tries is from 1 to 100. The switch dynamically determines the default tries parameter that is 10 to 100.
Step 2
Router(config)# radius-server deadtime minutes
(Optional) Sets the number of minutes that a RADIUS server is not sent requests. The range is from 0 to 1440 minutes (24 hours). The default is 0 minutes.
57-51
Command
Step 3
Router(config)# radius-server host ip-address [acct-port udp-port] [auth-port udp-port] [key string] [test username name [idle-time time] [ignore-acct-port] [ignore-auth-port]]
Purpose (Optional) Configures the RADIUS server parameters by using these keywords:
acct-port udp-portSpecifies the UDP port for the RADIUS accounting server. The range for the UDP port number is from 0 to 65536. The default is 1646. auth-port udp-portSpecifies the UDP port for the RADIUS authentication server. The range for the UDP port number is from 0 to 65536. The default is 1645. You should configure the UDP port for the RADIUS accounting server and the UDP port for the RADIUS authentication server to nondefault values. key stringSpecifies the authentication and encryption key for all RADIUS communication between the switch and the RADIUS daemon. You can also configure the authentication and encryption key by using the radius-server key {0 string | 7 string | string} global configuration command. test username nameEnables automated testing of the RADIUS server status, and specify the username to be used. idle-time timeSets the interval of time in minutes after which the switch sends test packets to the server. The range is from 1 to 35791 minutes. The default is 60 minutes (1 hour). ignore-acct-portDisables testing on the RADIUS server accounting port. ignore-auth-portDisables testing on the RADIUS server authentication port.
Note
Note
Step 4
Router(config)# dot1x critical eapol
(Optional) Specifies that the switch sends an EAPOL-Success message when the switch successfully authenticates the critical port. (Optional) Sets the recovery delay period during which the switch waits to reinitialize a critical port when a RADIUS server that was unavailable becomes available. The range is from 1 to 10000 milliseconds. The default is 1000 milliseconds (a port can be reinitialized every second). Specifies the port to be configured, and enters interface configuration mode.
Step 5

Router(config-if)# authentication critical recovery delay milliseconds

Router(config)# dot1x critical recovery delay milliseconds
Step 6
57-52
OL-13013-06
Chapter 57
Command
Step 7
Purpose Enables the inaccessible authentication bypass feature, authorizing ports on the specified VLAN when the AAA server is unreachable. If no VLAN is specified, the access VLAN will be used.
Note

Router(config-if)# authentication event server dead action authorize [vlan vlan-id]

Router(config-if)# dot1x critical [vlan vlan-id]
The vlan keyword is only available on a switch port.
Step 8

Router(config-if)# authentication event server alive action reinitialize

Router(config-if)# dot1x critical recovery action reinitialize
Configures the inaccessible authentication bypass recovery feature, specifying that the recovery action is to authenticate the port when an authentication server becomes available.
Step 9 Step 10
Router(config-if)# end Router# show dot1x [interface type slot/port] 1. type = fastethernet, gigabitethernet, or tengigabitethernet
To return to the RADIUS server default settings, use the no radius-server dead-criteria, the no radius-server deadtime, and the no radius-server host global configuration commands. To return to the default settings of inaccessible authentication bypass, use the no dot1x critical eapol global configuration command. To disable inaccessible authentication bypass, use the no authentication event server dead action authorize (or no dot1x critical) interface configuration command. This example shows how to configure the inaccessible authentication bypass feature:
Router(config)# radius-server dead-criteria time 30 tries 20 Router(config)# radius-server deadtime 60 Router(config)# radius-server host 1.1.1.2 acct-port 1550 auth-port 1560 key abc1234 test username user1 idle-time 30 Router(config)# dot1x critical eapol Router(config)# authentication critical recovery delay 2000 Router(config)# interface gigabitethernet 1/1 Router(config-if)# authentication event server dead action authorize vlan 123 Router(config-if)# authentication event server alive action reinitialize

Router(config)# radius-server dead-criteria time 30 tries 20 Router(config)# radius-server deadtime 60 Router(config)# radius-server host 1.1.1.2 acct-port 1550 auth-port 1560 key abc1234 test username user1 idle-time 30 Router(config)# dot1x critical eapol Router(config)# dot1x critical recovery delay 2000 Router(config)# interface gigabitethernet 1/1 Router(config-if)# dot1x critical vlan 123 Router(config-if)# dot1x critical recovery action reinitialize
57-53
Configuring MAC Authentication Bypass

To configure MAC authentication bypass on an interface, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Enables 802.1X authentication on the port. The keywords have these meanings:


Router(config-if)# authentication port-control {auto | force-authorized | force-unauthorized}

Router(config-if)# dot1x port-control {auto | force-authorized | force-unauthorized}
autoAllows only EAPOL traffic until successful authentication. force-authorizedAllows all traffic, requires no authentication. force-unauthorizedAllows no traffic.
Step 3

Router(config-if)# mab [eap]
Enables MAC authentication bypass on the interface. (Optional) Use the eap keyword to configure the switch to use EAP for authorization.

Router(config-if)# dot1x mac-auth-bypass [eap]
Step 4

Router(config-if)# no mab eap

Router(config-if)# no dot1x mac-auth-bypass eap
(Optional) Disables the use of EAP for authorization if EAP was previously configured using the mab eap or the dot1x mac-auth-bypass eap command.
Step 5

Router(config-if)# no mab
(Optional) Disables MAC authentication bypass on the interface.

Note

Router(config-if)# no dot1x mac-auth-bypass
When MAC authentication bypass with EAP has been enabled on an interface, it is not disabled by a subsequent default interface command on the interface.
Step 6 Step 7
Note
To use MAC authentication bypass on a routed port, make sure that MAC address learning is enabled on the port. This example shows how to enable MAC authentication bypass on a port:
Router(config)# interface fastethernet 5/1 Router(config-if)# authentication port-control auto Router(config-if)# mab
57-54
OL-13013-06
Chapter 57

Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x port-control auto Router(config-if)# dot1x mac-auth-bypass
Configuring NAC Layer 2 IEEE 802.1X Validation

With Cisco IOS Release 12.2(33)SXH and later releases, you can configure NAC Layer 2 IEEE 802.1X validation, which is also referred to as 802.1X authentication with a RADIUS server. NAC Layer 2 IEEE 802.1X configuration is the same as 802.1X configuration with the additional step of configuring the RADIUS server with a posture token and VLAN assignment. To configure NAC Layer 2 IEEE 802.1X validation, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Enables port-based authentication on the interface. The no form of the command disables port-based authentication on the interface. For feature interaction information, see the 802.1X Authentication Feature Configuration Guidelines section on page 57-28. Enables periodic reauthentication of the client, which is disabled by default.


Step 3

Router(config-if)# authentication periodic

Router(config-if)# dot1x reauthentication
Step 4

Router(config-if)# authentication timer reauthenticate [seconds | server]
Specifies the number of seconds between reauthentication attempts using these keywords:

Router(config-if)# dot1x timeout reauth-period [seconds | server]
secondsSets the number of seconds from 1 to 65535; the default is 3600 seconds. serverSets the number of seconds based on the value of the Session-Timeout RADIUS attribute (Attribute[27]) and the Termination-Action RADIUS attribute (Attribute [29]).
This command affects the operation of the switch only if periodic reauthentication is enabled.
Step 5 Step 6
Router(config-if)# end Router# show dot1x interface type slot/port
Returns to privileged EXEC mode. Verifies your 802.1X authentication configuration. Verify that a NAC posture token is displayed with the 802.1X authentication configuration.
1.
57-55
This example shows how to configure NAC Layer 2 IEEE 802.1X validation:
Router(config)# interface fastethernet 5/1 Router(config)# authentication port-control auto Router(config-if)# authentication periodic Router(config-if)# authentication timer reauthenticate server

Router(config)# interface fastethernet 5/1 Router(config)# dot1x port-control auto Router(config-if)# dot1x reauthentication Router(config-if)# dot1x timeout reauth-period server
Configuring NAC Agentless Audit Support

To support the NAC audit architecture for agentless clients, the switch must snoop an authenticating 802.1X clients IP address, create and assign a unique session identifier for the agentless client, and pass this information to the RADIUS server for sharing with the NAC audit server. To allow the switch to obtain and share this information, you must enable ARP and DHCP snooping on the switch and you must enable the sending of certain RADIUS attributes. To configure the RADIUS and tracking settings to support NAC agentless audit, perform this task: Command
Step 1
Purpose 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 (VSAs) (specifically audit-session-id) in RADIUS Access-Requests generated by the switch during the authentication phase. Allows VSAs to be included in subsequent RADIUS Accounting-Requests. Enables the IP device tracking table.
Step 2
Step 3 Step 4
Router(config)# radius-server vsa send accounting
Router(config)# ip device tracking
57-56
OL-13013-06
Chapter 57
Configuring the Switch for DACLs or Redirect URLs

To configure switch ports to accept DACLs or redirect URLs from the RADIUS server during authentication of an attached host, perform this task: Command
Step 1 Step 2
Router# config terminal Router(config)# radius-server vsa send authentication
Purpose Enters global configuration mode. Configures the network access server to recognize and use vendor-specific attributes (VSAs) in RADIUS Access-Requests generated by the switch during the authentication phase.
Note
This step is necessary only with redirect URLs or when DACLs are downloaded using VSAs rather than the Filter-ID attribute.
Step 3 Step 4
Router(config)# ip device tracking Router(config)# ip access-list extended dacl-name
Enables the IP device tracking table. Configures an ACL that will be referenced by the VSA or Filter-ID attribute.
Note
This step is not necessary for DACLs defined on the RADIUS server and downloaded using VSAs. The source address must be ANY.
Step 5
Router(config-std-nacl)# {permit | deny} ...
Defines the ACL.

Note
Router(config-std-nacl)# exit Router(config)# ip access-list extended acl-name Router(config-std-nacl)# {permit | deny} ... Router(config-std-nacl)# exit Router(config)# interface type
1
Returns to global configuration mode. Configures a default ACL for the ports. Defines the ACL. Returns to global configuration mode.
slot/port
Specifies the port to be configured, and enters interface configuration mode. Applies the default static ACL on the interface. Returns to global configuration mode.
Router(config-if)# ip access-group acl-name in Router(config-if)# exit 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to configure a switch for a downloadable policy:

Router# config terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# radius-server vsa send authentication Router(config)# ip device tracking Router(config)# ip access-list extended my_dacl Router(config-ext-nacl)# permit tcp any host 10.2.3.4 Router(config-ext-nacl)# exit Router(config)# ip access-list extended default_acl Router(config-ext-nacl)# permit ip any any Router(config-ext-nacl)# exit Router(config)# interface fastEthernet 2/13 Router(config-if)# ip access-group default_acl in Router(config-if)# exit
57-57
Configuring a Port to Ignore CoA Commands

To configure the switch to disregard a CoA command to shut down or bounce a specific port, perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Configures the switch to ignore any CoA command requesting that this port be administratively shut-down. Configures the switch to ignore any CoA command requesting that this port be held down for a period of time. Returns to global configuration mode.
Router(config-if)# [no] authentication command disable-port ignore Router(config-if)# [no] authentication command bounce-port ignore
Step 3
Router(config-if)# exit 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Configuring 802.1X Authentication with WoL

To enable 802.1X authentication with wake-on-LAN (WoL), perform this task: Command
Step 1 Step 2
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Enables 802.1X authentication with WoL on the port, and uses these keywords to configure the port as bidirectional or unidirectional.

Router(config-if)# authentication control-direction {both | in}

Router(config-if)# dot1x control-direction {both | in}
bothSets the port as bidirectional. The port cannot receive packets from or send packets to the host. By default, the port is bidirectional. inSets the port as unidirectional. The port can send packets to the host but cannot receive packets from the host.
Step 3 Step 4
To disable 802.1X authentication with WoL, use the no authentication control-direction (or the no dot1x control-direction) interface configuration command. This example shows how to enable 802.1X authentication with WoL and set the port as bidirectional:
Router(config)# interface fastethernet 5/1 Router(config-if)# authentication control-direction both
57-58
OL-13013-06
Chapter 57

Router(config)# interface fastethernet 5/1 Router(config-if)# dot1x control-direction both
Disabling 802.1X Authentication on the Port

You can disable 802.1X authentication on the port by using the no dot1x pae interface configuration command. To disable 802.1X authentication on the port, perform this task: Command
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Disables 802.1X authentication on the port. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# no dot1x pae authenticator Router(config-if)# end Router# show dot1x interface type slot/port 1. type = fastethernet, gigabitethernet, or tengigabitethernet
To configure the port as an 802.1X port access entity (PAE) authenticator, which enables 802.1X on the port but does not allow clients connected to the port to be authorized, use the dot1x pae authenticator interface configuration command. This example shows how to disable 802.1X authentication on the port:
Router(config)# interface fastethernet 5/1 Router(config-if)# no dot1x pae authenticator
Resetting the 802.1X Configuration to the Default Values

To reset the 802.1X configuration to the default values, perform this task: Command
1
Purpose
slot/port
Specifies the port to be configured, and enters interface configuration mode. Resets the configurable 802.1X parameters to the default values. Returns to privileged EXEC mode. Verifies your entries.
Router(config-if)# dot1x default
This example shows how to reset a ports 802.1X authentication settings to the default values:
Router(config)# interface gigabitethernet 3/27 Router(config-if)# dot1x default
57-59
Configuring an Authenticator and a Supplicant Switch with NEAT

Release 12.2(33)SXJ and later releases support Network Edge Access Topology (NEAT), which requires one switch to be configured as a supplicant and to be connected to an authenticator switch. For overview information, see the Understanding 802.1x Supplicant and Authenticator Switches with Network Edge Access Topology (NEAT) section on page 57-26.
Note
The cisco-av-pairs value must be configured as device-traffic-class=switch on the ACS, which sets the interface as a trunk after the supplicant is successfully authenticated. To configure a switch as an authenticator, perform this task:
Command
Step 1 Step 2 Step 3 Step 4 Step 5 Step 6 Step 7 Step 8 Step 9 Step 10
Router# configure terminal Router(config)# cisp enable Router(config)# interface interface-id
Purpose Enters global configuration mode. Enables CISP. Specifies the port to be configured, and enters interface configuration mode. Sets the port mode to access. Sets the port-authentication mode to auto. Configures the interface as a port access entity (PAE) authenticator. Enables PortFast on an access port connected to a single workstation or server. Returns to privileged EXEC mode. Verifies your configuration. (Optional) Saves your entries in the configuration file.
Router(config-if)# switchport mode access Router(config-if)# authentication port-control auto Router(config-if)# dot1x pae authenticator
Router(config-if)# spanning-tree portfast
Router(config-if)# end Router# show running-config interface interface-id Router# copy running-config startup-config
This example shows how to configure a switch as an 802.1x authenticator:

Router# configure terminal Router(config)# cisp enable Router(config)# interface gigabitethernet1/1 Router(config-if)# switchport mode access Router(config-if)# authentication port-control auto Router(config-if)# dot1x pae authenticator Router(config-if)# spanning-tree portfast trunk
To configure a switch as a supplicant, perform this task: Command

Router# configure terminal Router(config)# cisp enable Router(config)# dot1x credentials profile
Purpose Enters global configuration mode. Enables CISP. Creates 802.1x credentials profile. This must be attached to the port that is configured as supplicant. Creates a username.
Router(config)# username suppswitch
57-60
OL-13013-06
Chapter 57
Configuring IEEE 802.1X Port-Based Authentication Displaying Authentication Status and Information
Command
Step 5 Step 6
Router(config)# password password Router(config)# dot1x supplicant force-multicast
Purpose Creates a password for the new username. Forces the switch to send only multicast EAPOL packets when it receives either unicast or multicast packets, which allows NEAT to work on the supplicant switch in all host modes. Specifies the port to be configured, and enters interface configuration mode. Sets the port to trunk mode. Configures the interface as a VLAN trunk port. Configures the interface as a port access entity (PAE) supplicant. Attaches the 802.1x credentials profile to the interface. Returns to privileged EXEC mode. Verifies your configuration. (Optional) Saves your entries in the configuration file.
Step 7 Step 8 Step 9 Step 10 Step 11 Step 12 Step 13 Step 14
Router(config)# interface interface-id
Router(config-if)# switchport trunk encapsulation dot1q Router(config-if)# switchport mode trunk Router(config-if)# dot1x pae supplicant
Router(config-if)# dot1x credentials profile-name Router(config-if)# end Router# show running-config interface interface-id Router# copy running-config startup-config
This example shows how to configure a switch as a supplicant:

Router# configure terminal Router(config)# cisp enable Router(config)# dot1x credentials test Router(config)# username suppswitch Router(config)# password myswitch Router(config)# dot1x supplicant force-multicast Router(config)# interface gigabitethernet1/1 Router(config-if)# switchport trunk encapsulation dot1q Router(config-if)# switchport mode trunk Router(config-if)# dot1x pae supplicant Router(config-if)# dot1x credentials test Router(config-if)# end
Displaying Authentication Status and Information

This section describes the show commands used to display authentication status and information.

Displaying 802.1X Status, page 57-62 Displaying Authentication Methods and Status, page 57-63 Displaying MAC Authentication Bypass Status, page 57-66
For detailed information about the fields in these displays, see the Cisco IOS Master Command List, Release 12.2SX.
57-61
Chapter 57 Displaying Authentication Status and Information
Displaying 802.1X Status

To display the global 802.1X administrative and operational status for the switch or the 802.1X settings for individual ports, perform this task: Command
Router# show dot1x [all | interface type1 slot/port]
Purpose Displays the global 802.1X administrative and operational status for the switch. (Optional) Use the all keyword to display the global 802.1X status and the 802.1X settings for all interfaces using 802.1X authentication. (Optional) Use the interface keyword to display the 802.1X settings for a specific interface.
1.
This example shows how to view only the global 802.1X status:
Router# show dot1x Sysauthcontrol Dot1x Protocol Version Critical Recovery Delay Critical EAPOL Router#
Disabled 2 100 Disabled
This example shows how to view the global 802.1X status and the 802.1X settings for all interfaces using 802.1X authentication:
Router# show dot1x all Sysauthcontrol Dot1x Protocol Version Critical Recovery Delay Critical EAPOL
Disabled 2 100 Disabled
Dot1x Info for GigabitEthernet3/27 ----------------------------------PAE = AUTHENTICATOR PortControl = FORCE_AUTHORIZED ControlDirection = Both HostMode = SINGLE_HOST ReAuthentication = Disabled QuietPeriod = 60 ServerTimeout = 30 SuppTimeout = 30 ReAuthPeriod = 3600 (Locally configured) ReAuthMax = 2 MaxReq = 2 TxPeriod = 30 RateLimitPeriod = 0 Router#
57-62
OL-13013-06
Chapter 57
Displaying Authentication Methods and Status

To display the authentication methods and status, perform any of these tasks: Command
Router# show authentication registrations Router# show authentication interface interface
Purpose Displays details of all registered methods. Displays authentication information for a specific interface Lists current authentication sessions that were authorized using the specified method. Displays information about current authentication sessions. With no options specified, all current active sessions will be listed. The keywords can be added and combined to display detailed information about specific sessions or subset of sessions.
Router# show authentication method method
Router# show authentication sessions [handle handle] [interface interface] [mac mac] [method method] [session-id session-id]
Table 57-3 shows the possible states of the authentication session.

Table 57-3 Authentication Session States
State Idle Running No methods Authc Success Authc Failed Authz Success Authz Failed
Description The session has been initialized and no methods have run yet. A method is running for this session. No method has provided a result for this session. A method has provided a successful authentication result for the session. A method has provided a failed authentication result for the session. All features have been successfully applied for this session. A feature has failed to be applied for this session.
Table 57-4 shows the possible states of the authentication methods.

Table 57-4 Authentication Method States
State Not run Running Failed over
Description The method has not run for this session The method is running for this session. The method has failed and the next method is expected to provide a result.
57-63
Table 57-4
Authentication Method States (continued)
State Success Authc Failed
Description The method has provided a successful authentication result for the session. The method has provided a failed authentication result for the session.
This example shows how to display the registered authentication methods:

Router# show authentication registrations Auth Methods registered with the Auth Manager: Handle Priority Name 3 0 dot1x 2 1 mab 1 2 webauth
This example shows how to display the authentication details for a given interface:
Router# show authentication interface g1/23 Client list: MAC Address Domain Status Handle Interface 0123.4567.abcd DATA Authz Success 0xE0000000 GigabitEthernet1/23 Available methods list: Handle Priority Name 3 0 dot1x 2 1 mab Runnable methods list: Handle Priority Name 2 0 mab 3 1 dot1x
This example shows how to display all authentication sessions on the switch:
Router# show authentication sessions Interface Gi1/48 Gi1/5 Gi1/5 MAC Address 0015.63b0.f676 000f.23c4.a401 0014.bf5d.d26d Method dot1x mab dot1x Domain DATA DATA DATA Status Authz Success Authz Success Authz Success Session ID 0A3462B1000000102983C05C 0A3462B10000000D24F80B58 0A3462B10000000E29811B94
This example shows how to display sessions authorized using a specified authentication method:
Router# show authentication method dot1x Interface MAC Address Method Domain Gi1/48 0015.63b0.f676 dot1x DATA Gi1/5 0014.bf5d.d26d dot1x DATA Status Authz Success Authz Success Session ID 0A3462B1000000102983C05C 0A3462B10000000E29811B94
This example shows how to display all authentication sessions on an interface:

Router# show authentication sessions interface f1/47 Interface: FastEthernet1/47 MAC Address: Unknown IP Address: Unknown Status: Authz Success Domain: DATA Oper host mode: multi-host Oper control dir: both Authorized By: Guest Vlan Vlan Policy: 20
57-64
OL-13013-06
Chapter 57
Session timeout: Idle timeout: Common Session ID: Acct Session ID: Handle:
N/A N/A 0A3462C8000000000002763C 0x00000002 0x25000000
Runnable methods list: Method State mab Failed over dot1x Failed over ---------------------------------------Interface: MAC Address: IP Address: User-Name: Status: Domain: Oper host mode: Oper control dir: Authorized By: Session timeout: Idle timeout: Common Session ID: Acct Session ID: Handle: FastEthernet1/47 0005.5e7c.da05 Unknown 00055e7cda05 Authz Success VOICE multi-domain both Authentication Server N/A N/A 0A3462C8000000010002A238 0x00000003 0x91000001
Runnable methods list: Method State mab Authc Success dot1x Not run
This example shows how to display the authentication session for a specified session ID:
Router# show authentication sessions session-id 0B0101C70000004F2ED55218 Interface: MAC Address: IP Address: Username: Status: Domain: Oper host mode: Oper control dir: Authorized By: Vlan policy: Session timeout: Idle timeout: Common Session ID: Acct Session ID: Handle: GigabitEthernet9/2 0000.0000.0011 20.0.0.7 johndoe Authz Success DATA multi-host both Critical Auth N/A N/A N/A 0B0101C70000004F2ED55218 0x00000003 0x91000001
Runnable methods list: Method State mab Authc Success dot1x Not run
This example shows how to display all clients authorized by the specified authentication method:
Router# show authentication sessions method mab No Auth Manager contexts match supplied criteria
57-65
Router# show authentication sessions method dot1x Interface Gi9/2 MAC Address 0000.0000.0011 Domain DATA Status Authz Success Session ID 0B0101C70000004F2ED55218
Displaying MAC Authentication Bypass Status

To display the MAB status, perform this task: Command
Router# show mab {all | interface type [detail] 1.
1
Purpose
slot/port}
Displays MAB authentication details for all interfaces or for a specific interface.
Table 57-5 shows the possible states of the MAB authentication state machine.
Table 57-5 MAB States
State INITIALIZE ACQUIRING AUTHORIZING TERMINATE
Description The authorization session is initialized. The session is obtaining the client MAC address. The session is waiting for MAC-based authorization. The authorization session result has been obtained.
This example shows how to display the brief MAB status for a single interface:
Router# show mab interface fa1/1 MAB details for FastEthernet1/1 ------------------------------------Mac-Auth-Bypass = Enabled Inactivity Timeout = None
This example shows how to display the detailed MAB status for a single interface:
Router# show mab interface fa1/1 detail MAB details for FastEthernet1/1 ------------------------------------Mac-Auth-Bypass = Enabled Inactivity Timeout = None MAB Client List --------------Client MAC MAB SM state Auth Status
= 000f.23c4.a401 = TERMINATE = AUTHORIZED
57-66
OL-13013-06
Chapter 57
Enabling MAC Move

Release 12.2(33)SXI4 and later releases support the Mac move feature. To globally enable MAC move on the switch, perform this task: Command
Router# configure terminal Router(config)# authentication mac-move permit Router(config)# end Router# show running-config Router# copy running-config startup-config
Purpose Enters global configuration mode. Enables MAC move on the switch. Returns to privileged EXEC mode. (Optional) Verifies your entries. (Optional) Saves your entries in the configuration file.
This example shows how to globally enable MAC move on a switch:

Router(config)# authentication mac-move permit
Enabling MAC Replace

Release 12.2(33)SXI4 and later releases support the Mac replace feature. To enable MAC replace on an interface, perform this task: Command
Router# configure terminal Router(config)# interface interface-id
Purpose Enters global configuration mode. Specifies the port to be configured, and enter interface configuration mode. Uses the replace keyword to enable MAC replace on the interface. The port removes the current session and initiates authentication with the new host. The other keywords have these effects:
Router(config-if)# authentication violation {protect | replace | restrict | shutdown}
protect: the port drops packets with unexpected MAC addresses without generating a system message. restrict: violating packets are dropped by the CPU and a system message is generated. shutdown: the port is error disabled when it receives an unexpected MAC address.

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.
This example shows how to enable MAC replace on an interface:

Router(config)# interface gigabitethernet2/2 Router(config-if)# authentication violation replace
57-67
57-68
OL-13013-06
C H A P T E R
58

This chapter describes how to configure web-based authentication. Cisco IOS Release 12.2(33)SXH and later releases support web-based authentication.
Note
Tip

Understanding Web-Based Authentication, page 58-1 Configuring Web-Based Authentication, page 58-6 Displaying Web-Based Authentication Status, page 58-15
Understanding Web-Based Authentication

The web-based authentication feature implements web-based authentication, which is also known as Web Authentication Proxy. You can use the web-based authentication feature to authenticate end users on host systems that do not run the IEEE 802.1X supplicant. You can configure the web-based authentication feature on Layer 2 and Layer 3 interfaces. When a user initiates an HTTP session, the web-based authentication feature intercepts ingress HTTP packets from the host and sends an HTML login page to the user. The user keys in their credentials, which the web-based authentication feature sends to the AAA server for authentication. If the authentication succeeds, web-based authentication sends a Login-Successful HTML page to the host and applies the access policies returned by the AAA server.
58-1
Chapter 58 Understanding Web-Based Authentication
If the authentication fails, web-based authentication feature sends a Login-Fail HTML page to the user, which prompts the user to retry the login attempt. If the user exceeds the maximum number of failed login attempts, web-based authentication sends a Login-Expired HTML page to the host and the user is placed on a watch list for a waiting period. These sections describe the role of web-based authentication as a part of the authentication, authorization, and accounting (AAA) system:

Device Roles, page 58-2 Host Detection, page 58-3 Session Creation, page 58-3 Authentication Process, page 58-3 AAA Fail Policy, page 58-4 Customization of the Authentication Proxy Web Pages, page 58-4 Web-based Authentication Interactions with Other Features, page 58-5
Device Roles
With web-based authentication, the devices in the network have specific roles as shown in Figure 58-1.
Figure 58-1 Web-based Authentication Device Roles
Catalyst switch or Cisco Router Workstations (clients)
The specific roles shown in Figure 58-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 an HTML browser with Java Script enabled. 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. SwitchControls 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.
58-2
79549
OL-13013-06
Chapter 58
Configuring Web-Based Authentication Understanding Web-Based Authentication
Host Detection
The switch maintains an IP device tracking table to store information about detected hosts.
Note
By default, the IP device tracking feature is disabled on a switch. You must enable the IP device tracking feature to use web-based authentication. For Layer 3 interfaces, web-based authentication sets an HTTP intercept ACL when the feature is configured on the interface (or when the interface is put in service). For Layer 2 interfaces, web-based authentication detects IP hosts using the following mechanisms:

ARP based triggerARP redirect ACL allows web-based authentication to detect hosts with static IP address or dynamically acquired IP address. Dynamic ARP Inspection DHCP snoopingWeb-based authentication is notified when the switch creates a DHCP binding entry for the host.
Session Creation
When web-based authentication detects a new host, it creates a session as follows:
Checks the exception list If the host IP is included in the exception list, the policy from the exception list entry is applied, and the session is considered to be established.
Checks for Auth bypass If the host IP is not on the exception list, web-based authentication sends a nonresponsive host (NRH) request to the server. If the server response is Access Accepted, authorization is bypassed for this host. The session is considered to be established.
Sets up the HTTP Intercept ACL If the server response to the NRH request is Access Rejected, the HTTP intercept ACL is activated and the session waits for HTTP traffic from the host.
Authentication Process
When web-based authentication is enabled, the following events occur:

The user initiates an HTTP session. The HTTP traffic is intercepted, and authorization is initiated. The switch sends the login page to the user. The user enters a username and password on the login page, and the switch sends the entries to the authentication server. If the client identity is valid and the authentication succeeds, the switch downloads and activates the users access policy from the authentication server. The login success page is sent to the user. If the authentication fails, the switch sends the login fail page. The user retries the login, but if the maximum number of attempts fail, the switch sends the login expired page and the host is placed in a watch list. After a watch list timeout, the user can retry the authentication process.
58-3
Chapter 58 Understanding Web-Based Authentication
If the authentication server does not respond to the switch, and if an AAA fail policy is configured, the switch will apply the failure access policy to the host. The login success page is sent to the user. The AAA fail policy feature is available in Cisco IOS Release 12.2(33)SXI and later releases.
The switch reauthenticates a client when the host does not respond to an ARP probe on a Layer 2 interface, or the host does not send any traffic within the idle timeout on a Layer 3 interface.

The feature applies the downloaded timeout or the locally configured session timeout. If the terminate action is RADIUS, the feature sends a nonresponsive host (NRH) request to the server. The terminate action is included in the response from the server. If the terminate action is default, the session is dismantled and the applied policy is removed.
AAA Fail Policy

The AAA fail policy, supported in Cisco IOS Release 12.2(33)SXI and later releases, is a method for allowing a user to connect or to remain connected to the network if the AAA server is not available. If the AAA server cannot be reached when web-based authentication of a client is needed, instead of rejecting the user (that is, not providing the access to the network), an administrator can configure a default AAA fail policy that can be applied to the user. This policy is advantageous for the following reasons:

While AAA is unavailable, the user will still have connectivity to the network, although access may be restricted. When the AAA server is again available, a user can be revalidated, and the users normal access policies can be downloaded from the AAA server.
Note
When the AAA server is down, the AAA fail policy is applied only if there is no existing policy associated with the user. Typically, if the AAA server is unavailable when a user session requires reauthentication, the policies currently in effect for the user are retained. While the AAA fail policy is in effect, the session state is maintained as AAA Down.
Customization of the Authentication Proxy Web Pages

The switchs internal HTTP server hosts four HTML pages for delivery to an authenticating client during the web-based authentication process. The four pages allow the server to notify the user of the following four states of the authentication process:

LoginThe users credentials are requested SuccessThe login was successful FailThe login has failed ExpireThe login session has expired due to excessive login failures
In Cisco IOS Release 12.2(33)SXI and later releases, you can substitute your custom HTML pages for the four default internal HTML pages, or you can specify a URL to which the user will be redirected upon successful authentication, effectively replacing the internal Success page.
58-4
OL-13013-06
Chapter 58
Configuring Web-Based Authentication Understanding Web-Based Authentication
Web-based Authentication Interactions with Other Features

These sections describe web-based authentication interactions with these features:

Port Security, page 58-5 LAN Port IP, page 58-5 Gateway IP, page 58-5 ACLs, page 58-5 IP Source Guard, page 58-6 EtherChannel, page 58-6 Switchover, page 58-6
Port Security
You can configure web-based authentication and port security on the same port. (You configure port security on the port by using the switchport port-security interface configuration command.) When you enable port security and web-based authentication on a port, web-based authentication authenticates the port, and port security manages network access for all MAC addresses, including that of the client. You can then limit the number or group of clients that can access the network through the port. For more information about enabling port security, see the Configuring Port Security section on page 59-5.
LAN Port IP
You can configure LAN port IP (LPIP) and Layer 2 web-based authentication on the same port. The host is authenticated using web-based authentication first, and then LPIP posture validation takes place. The LPIP host policy overrides the web-based authentication host policy. If the web-based authentication idle timer expires, the NAC policy is removed. The host is authenticated and posture validated again.
Gateway IP
You cannot configure Gateway IP on a Layer 3 VLAN interface if web-based authentication is configured on any of the switch ports in the VLAN. You can configure web-based authentication on the same Layer 3 interface as Gateway IP. The host policies for both features are applied in software. The GWIP policy overrides the web-based authentication host policy.
ACLs
If you configure a VLAN ACL or Cisco IOS ACL on an interface, the ACL is applied to the host traffic only after the web-based authentication host policy is applied. For Layer 2 web-based authentication, you must configure a port ACL (PACL) as the default access policy for ingress traffic from hosts connected to the port. After authentication, the web-based authentication host policy overrides the PACL. You cannot configure a MAC ACL and web-based authentication on the same interface.
58-5
Chapter 58 Configuring Web-Based Authentication
You cannot configure web-based authentication on a port whose access VLAN has VACL capture configured.
IP Source Guard
In releases earlier than Cisco IOS Release 12.2(33)SXI2, configuring IP Source Guard and web-based authentication on the same interface is not supported. In Cisco IOS Release 12.2(33)SXI2 and later releases, you can configure IP Source Guard and web-based authentication on the same interface. If DHCP snooping is also enabled on the access VLAN, you must enter the mls acl tcam override dynamic dhcp-snooping command in global configuration mode to avoid conflict between the two features. Other VLAN-based features are not supported when IP Source Guard and web-based authentication are combined.
EtherChannel
You can configure web-based authentication on a Layer 2 EtherChannel interface. The web-based authentication configuration applies to all member channels.
Switchover
On Catalyst 6500 series switches with redundant supervisor engines in RPR mode redundancy, information about currently authenticated hosts is maintained during a switchover. Users will not need to reauthenticate.

These sections describe how to configure web-based authentication:

Default Web-Based Authentication Configuration, page 58-7 Web-based Authentication Configuration Guidelines and Restrictions, page 58-7 Web-based Authentication Configuration Task List, page 58-8 Configuring the Authentication Rule and Interfaces, page 58-8 Configuring AAA Authentication, page 58-9 Configuring Switch-to-RADIUS-Server Communication, page 58-9 Configuring the HTTP Server, page 58-11 Configuring the Web-based Authentication Parameters, page 58-14 Removing Web-based Authentication Cache Entries, page 58-15
58-6
OL-13013-06
Chapter 58
Configuring Web-Based Authentication Configuring Web-Based Authentication
Default Web-Based Authentication Configuration

Table 58-1 shows the default web-based authentication configuration.
Table 58-1 Default Web-based Authentication Configuration
Feature AAA RADIUS server

Default Setting Disabled

IP address UDP authentication port Key
None specified 1812 None specified
Default value of inactivity timeout Inactivity timeout
3600 seconds Enabled
Web-based Authentication Configuration Guidelines and Restrictions

These are the web-based authentication configuration guidelines:

Web-based authentication is an ingress-only feature. You can configure web-based authentication only on access ports. Web-based authentication is not supported on trunk ports, EtherChannel member ports, or dynamic trunk ports. You must configure the default ACL on the interface before configuring web-based authentication. Configure a port ACL for a Layer 2 interface, or a Cisco IOS ACL for a Layer 3 interface. On Layer 2 interfaces, you cannot authenticate hosts with static ARP cache assignment. These hosts are not detected by the web-based authentication feature, because they do not send ARP messages. By default, the IP device tracking feature is disabled on a switch. You must enable the IP device tracking feature to use web-based authentication. You must configure at least one IP address to run the HTTP server on the switch. You must also configure routes to reach each host IP address. The HTTP server sends the HTTP login page to the host. Hosts that are more than one hop away may experience traffic disruption if an STP topology change results in the host traffic arriving on a different port. This is because ARP and DHCP updates may not be sent after a Layer 2 (STP) topology change. Web-based authentication does not support VLAN assignment as a downloadable host policy. Cisco IOS Release 12.2(33)SXI and later releases support downloadable ACLs (DACLs) from the RADIUS server. Web-based authentication is not supported for IPv6 traffic.
58-7
Web-based Authentication Configuration Task List

To configure the web-based authentication feature, perform the following tasks:

Configuring the Authentication Rule and Interfaces, page 58-8 Configuring AAA Authentication, page 58-9 Configuring Switch-to-RADIUS-Server Communication, page 58-9 Configuring the HTTP Server, page 58-11 Configuring an AAA Fail Policy, page 58-13 Configuring the Web-based Authentication Parameters, page 58-14 Removing Web-based Authentication Cache Entries, page 58-15
Configuring the Authentication Rule and Interfaces

To configure web-based authentication, perform this task: Command
Step 1 Step 2
Router(config)# ip admission name name proxy http
Purpose Configures an authentication rule for web-based authorization. Enters interface configuration mode and specifies the ingress Layer 2 or Layer 3 interface to be enabled for web-based authentication. Applies the default ACL. Configures web-based authentication on the specified interface. (Optional) Specifies the fallback order of authentication methods to be used. The three values of method, in the default order, are dot1x, mab, and webauth. Omitting a method disables that method on the interface. Returns to configuration mode. Enables the IP device tracking table. Returns to privileged EXEC mode. Displays the configuration.
Router(config-if)# ip access-group name Router(config-if)# ip admission name
Router(config-if)# authentication order method1 [method2] [method3]
Router(config-if)# exit Router(config)# ip device tracking Router(config)# end Router# show ip admission configuration 1. type = fastethernet, gigabitethernet, or tengigabitethernet
This example shows how to enable web-based authentication, while disabling 802.1X or MAB authentication, on Fast Ethernet port 5/1:
Router(config)# ip admission name webauth1 proxy http Router(config)# interface fastethernet 5/1 Router(config-if)# ip admission webauth1 Router(config-if)# authentication order webauth Router(config-if)# exit Router(config)# ip device tracking
58-8
OL-13013-06
Chapter 58

Router# show ip admission configuration Authentication Proxy Banner not configured Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes Authentication global init state time is 2 minutes Authentication Proxy Watch-list is disabled Authentication Proxy Rule Configuration Auth-proxy name webauth1 http list not specified inactivity-time 60 minutes Authentication Proxy Auditing is disabled Max Login attempts per user is 5
Configuring AAA Authentication

To enable web-based authentication, you must enable AAA and specify the authentication method. perform this task: Command
Router(config)# aaa new-model Router(config)# aaa authentication login default group {tacacs+ | radius} Router(config)# aaa authorization auth-proxy default group {tacacs+ | radius} Router(config)# tacacs-server host {hostname | ip_address}
Purpose Enables AAA functionality. Defines the list of authentication methods at login. Creates an authorization method list for web-based authorization. Specifies an AAA server. For Radius servers, see the section Configuring Switch-to-RADIUS-Server Communication section on page 58-9. Configures the authorization and encryption key used between the switch and the TACACS server.
Step 5
Router(config)# tacacs-server key {key-data}
This example shows how to enable AAA:

Router(config)# aaa new-model Router(config)# aaa authentication login default group tacacs+ Router(config)# aaa authorization auth-proxy default group tacacs+
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
58-9
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 that is configured functions as the failover backup to the first one. The RADIUS host entries are chosen in the order that they were configured. To configure the RADIUS server parameters, perform this task: Command
Step 1 Step 2
Router(config)# ip radius source-interface interface_name Router(config)# radius-server host {hostname | ip-address} test username username
Purpose Specifies that the RADIUS packets have the IP address of the indicated interface. Specifies the host name or IP address of the remote RADIUS server. The test username username option enables automated testing of the RADIUS server connection. The specified username does not need to be a valid user name. The key option specifies an authentication and encryption key to be used between the switch and the RADIUS server. To use multiple RADIUS servers, reenter this command.
Step 3
Router(config)# radius-server key string
Configures the authorization and encryption key used between the switch and the RADIUS daemon running on the RADIUS server. Enables downloading of an ACL from the RADIUS server. This feature is supported in Cisco IOS Release 12.2(33)SXI and later releases. Specifies the number of unanswered transmits to a RADIUS server before considering the server to be dead. The range of num-tries is 1 to 100.
Step 4
Step 5
Router(config)# radius-server dead-criteria tries num-tries
When you configure the RADIUS server parameters, note the following information:

Specify the key string on a separate command line. 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, see 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/docs/ios/12_2/security/command/reference/fsecur_r.html Cisco IOS Release 12.2(33)SXI and later releases support downloadable ACLs (DACLs) from the RADIUS server.
58-10
OL-13013-06
Chapter 58
Note
You also need to configure some settings on the RADIUS server. These settings include the IP address of the switch, the key string to be shared by both the server and the switch, and the downloadable ACL. For more information, see the RADIUS server documentation. This example shows how to configure the RADIUS server parameters on the switch:
Router(config)# Router(config)# Router(config)# Router(config)# ip radius source-interface Vlan80 radius-server host 172.l20.39.46 test username user1 radius-server key rad123 radius-server dead-criteria tries 2
Configuring the HTTP Server

To use web-based authentication, you must enable the HTTP server within the switch. You can enable the server for either HTTP or HTTPS. To enable the server, perform one of these tasks in global configuration mode: Command
Router(config)# ip http server
Purpose Enables the HTTP server. The web-based authentication feature uses the HTTP server to communicate with the hosts for user authentication. Enables HTTPS.
Router(config)# ip http secure-server
With Cisco IOS Release 12.2(33)SXI and later releases, you can optionally configure custom authentication proxy web pages or specify a redirection URL for successful login, as described in the following sections:

Customizing the Authentication Proxy Web Pages Specifying a Redirection URL for Successful Login
Customizing the Authentication Proxy Web Pages

With Cisco IOS Release 12.2(33)SXI and later releases, you have the option to provide four substitute HTML pages to be displayed to the user in place of the switchs internal default HTML pages during web-based authentication. To specify the use of your custom authentication proxy web pages, first store your custom HTML files on the switchs internal disk or flash memory, then perform this task in global configuration mode: Command
Step 1
Router(config)# ip admission proxy http login page file device:login-filename
Purpose Specifies the location in the switch memory file system of the custom HTML file to be used in place of the default login page. The device: is either disk or flash memory, such as disk0:. Specifies the location of the custom HTML file to be used in place of the default login success page.
Step 2
Router(config)# ip admission proxy http success page file device:success-filename
58-11
Command
Step 3 Step 4
Router(config)# ip admission proxy http failure page file device:fail-filename Router(config)# ip admission proxy http login expired page file device:expired-filename
Purpose Specifies the location of the custom HTML file to be used in place of the default login failure page. Specifies the location of the custom HTML file to be used in place of the default login expired page.
When configuring the use of customized authentication proxy web pages, consider the following guidelines:

To enable the custom web pages feature, you must specify all four custom HTML files. If fewer than four files are specified, the internal default HTML pages will be used. The four custom HTML files must be present on the disk or flash of the switch. An image file has a size limit of 256 KB. All image files must have a filename that begins with web_auth_ (like web_auth_logo.jpg instead of logo.jpg). All image file names must be less than 33 characters. Any images on the custom pages must be located on an accessible HTTP server. An intercept ACL must be configured within the admission rule to allow access to the HTTP server. Any external link from a custom page will require configuration of an intercept ACL within the admission rule. Any name resolution required for external links or images will require configuration of an intercept ACL within the admission rule to access a valid DNS server. If the custom web pages feature is enabled, a configured auth-proxy-banner will not be used. If the custom web pages feature is enabled, the redirection URL for successful login feature will not be available. To remove the specification of a custom file, use the no form of the command. The login form must accept user input for the username and password and must POST the data as uname and pwd. The custom login page should follow best practices for a web form, such as page timeout, hidden password, and prevention of redundant submissions.
Because the custom login page is a public web form, consider the following guidelines for this page:

The following example shows how to configure custom authentication proxy web pages:
Router(config)# Router(config)# Router(config)# Router(config)# ip ip ip ip admission admission admission admission proxy proxy proxy proxy http http http http login page file disk1:login.htm success page file disk1:success.htm fail page file disk1:fail.htm login expired page file disk1:expired.htm
The following example shows how to verify the configuration of custom authentication proxy web pages:
Router# show ip admission configuration Authentication proxy webpage Login page : disk1:login.htm Success page : disk1:success.htm Fail Page : disk1:fail.htm Login expired Page : disk1:expired.htm Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes
58-12
OL-13013-06
Chapter 58
Authentication global init state time is 2 minutes Authentication Proxy Session ratelimit is 100 Authentication Proxy Watch-list is disabled Authentication Proxy Auditing is disabled Max Login attempts per user is 5
Specifying a Redirection URL for Successful Login

With Cisco IOS Release 12.2(33)SXI and later releases, you have the option to specify a URL to which the user will be redirected upon successful authentication, effectively replacing the internal Success HTML page. To specify a redirection URL for successful login, perform this task in global configuration mode: Command
Router(config)# ip admission proxy http success redirect url-string
Purpose Specifies a URL for redirection of the user in place of the default login success page.
When configuring a redirection URL for successful login, consider the following guidelines:
If the custom authentication proxy web pages feature is enabled, the redirection URL feature is disabled and will not be available in the CLI. You can perform redirection in the custom login success page. If the redirection URL feature is enabled, a configured auth-proxy-banner will not be used. To remove the specification of a redirection URL, use the no form of the command.
The following example shows how to configure a redirection URL for successful login:
Router(config)# ip admission proxy http success redirect www.cisco.com
The following example shows how to verify the redirection URL for successful login:
Router# show ip admission configuration Authentication Proxy Banner not configured Customizable Authentication Proxy webpage not configured HTTP Authentication success redirect to URL: http://www.cisco.com Authentication global cache time is 60 minutes Authentication global absolute time is 0 minutes Authentication global init state time is 2 minutes Authentication Proxy Watch-list is disabled Authentication Proxy Max HTTP process is 7 Authentication Proxy Auditing is disabled Max Login attempts per user is 5
Configuring an AAA Fail Policy

The AAA fail policy for web-based authentication is supported in Cisco IOS Release 12.2(33)SXI and later releases.
58-13
To configure an AAA fail policy, perform this task in global configuration mode: Command
Step 1
Router(config)# ip admission name rule-name proxy http event timeout aaa policy identity identity_policy_name
Purpose Creates an AAA fail 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 proxy http event timeout aaa policy identity global configuration command. (Optional) To avoid flooding the AAA server when it returns to service, you can rate limit the authentication attempts from hosts in the AAA Down state.
Step 2
Router(config)# ip admission ratelimit aaa-down number_of_sessions
The following example shows how to apply an AAA fail policy:

Router(config)# ip admission name AAA_FAIL_POLICY proxy http event timeout aaa policy identity GLOBAL_POLICY1
The following example shows how to determine whether any hosts are connected in the AAA Down state:
Router# show ip admission cache Authentication Proxy Cache Client IP 209.165.201.11 Port 0, timeout 60, state ESTAB (AAA Down)
The following example shows how to view detailed information about a particular session based on the host IP address:
Router# show ip admission cache 209.165.201.11 Address : 209.165.201.11 MAC Address : 0000.0000.0000 Interface : Vlan333 Port : 3999 Timeout : 60 Age : 1 State : AAA Down AAA Down policy : AAA_FAIL_POLICY
Configuring the Web-based Authentication Parameters

You can configure the maximum number of failed login attempts before the client is placed in a watch list for a waiting period. To configure the web-based authentication parameters, perform this task: Command
Router(config)# ip admission max-login-attempts number Router(config)# end Router# show ip admission configuration Router# show ip admission cache
Purpose Sets the maximum number of failed login attempts. The range is 1 to 2147483647 attempts; the default is 5. Returns to privileged EXEC mode. Displays the authentication proxy configuration. Displays the list of authentication entries.
58-14
OL-13013-06
Chapter 58
Configuring Web-Based Authentication Displaying Web-Based Authentication Status
This example shows how to set the maximum number of failed login attempts to 10:
Router(config)# ip admission max-login-attempts 10
Removing Web-based Authentication Cache Entries

To delete existing session entries, perform either of these tasks: Command
Router# clear ip auth-proxy cache {* | host ip address}
Purpose Deletes authentication proxy entries. Use an asterisk to delete all cache entries. Enter a specific IP address to delete the entry for a single host. Deletes authentication proxy entries. Use an asterisk to delete all cache entries. Enter a specific IP address to delete the entry for a single host.
Router# clear ip admission cache {* | host ip address}
This example shows how to remove the web-based authentication session for the client at a specific IP address:
Router# clear ip auth-proxy cache 209.165.201.1
Displaying Web-Based Authentication Status

To display the web-based authentication settings for all interfaces or for specific ports, perform this task: Command
Step 1
Router# show fm ip-admission l2http [all | interface type1 slot/port]
Purpose Displays the web-based authentication settings. (Optional) Use the all keyword to display the settings for all interfaces using web-based authentication. (Optional) Use the interface keyword to display the web-based authentication settings for a specific interface.
1.
This example shows how to view only the global web-based authentication status:
Router# show fm ip-admission l2http all
This example shows how to view the web-based authentication settings for interface GigabitEthernet 3/27:
Router# show fm ip-admission l2http interface gigabitethernet 3/27
For detailed information about the fields in these displays, see the Cisco IOS Master Command List, Release 12.2SX.
58-15
Chapter 58 Displaying Web-Based Authentication Status
Tip
58-16
OL-13013-06
C H A P T E R
59

This chapter describes how to configure the port security feature.
Note
Tip

Understanding Port Security, page 59-1 Default Port Security Configuration, page 59-3 Port Security Guidelines and Restrictions, page 59-3 Configuring Port Security, page 59-5 Displaying Port Security Settings, page 59-12
Understanding Port Security

These sections describe port security:

Port Security with Dynamically Learned and Static MAC Addresses, page 59-2 Port Security with Sticky MAC Addresses, page 59-2 Port Security with IP Phones, page 59-3
59-1
Chapter 59 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, applies the configured 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 59-6 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 59-5. 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.
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.
59-2
OL-13013-06
Chapter 59
Configuring Port Security Default Port Security Configuration
Port Security with IP Phones

Figure 59-1 shows an application in which a device connects to the switch through the data port of an IP phone.
Figure 59-1 Device Connected Through IP Phone
Client
IP phone IP
Switch
188919
Because the device is not directly connected to the switch, the switch cannot physically detect a loss of port link if the device is disconnected. Later Cisco IP phones send a Cisco Discovery Protocol (CDP) host presence type length value (TLV) to notify the switch of changes in the attached devices port link state. With Cisco IOS Release 12.2(33)SXI and later releases, the switch recognizes the host presence TLV. Upon receiving a host presence TLV notification of a link down on the IP phones data port, port security removes from the address table all static, sticky, and dynamically learned MAC addresses. The removed addresses are added again only when the addresses are learned dynamically or configured.
Default Port Security Configuration

Table 59-1 shows the default port security configuration for an interface.
Table 59-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 the port 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.
59-3
Chapter 59 Port Security Guidelines and Restrictions
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. Port security supports private VLAN (PVLAN) ports. Port security supports 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 Cisco IOS Release 12.2(33)SXH and later releases, you can configure port security and 802.1X port-based authentication on the same port. With releases earlier than Cisco IOS Release 12.2(33)SXH:
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.
Port security supports nonnegotiating trunks.

Port security only supports trunks configured with these commands:
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.
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. Flex Links and port security are not compatible with each other.
59-4
OL-13013-06
Chapter 59
Configuring Port Security Configuring Port Security

These sections describe how to configure port security:

Enabling Port Security, page 59-5 Configuring the Port Security Violation Mode on a Port, page 59-6 Configuring the Port Security Rate Limiter, page 59-7 Configuring the Maximum Number of Secure MAC Addresses on a Port, page 59-9 Enabling Port Security with Sticky MAC Addresses on a Port, page 59-9 Configuring a Static Secure MAC Address on a Port, page 59-10 Configuring Secure MAC Address Aging on a Port, page 59-11
Enabling Port Security

These sections describe how to enable port security:

Enabling Port Security on a Trunk, page 59-5 Enabling Port Security on an Access Port, page 59-6
Enabling Port Security on a Trunk

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 59-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)# do show port-security interface type1 slot/port | include Port Security 1. type = fastethernet, gigabitethernet, or tengigabitethernet
1
Purpose
slot/port
Selects the LAN port to configure. Configures the port as a Layer 2 port. 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. Verifies the configuration.
59-5
Chapter 59 Configuring Port Security
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
Enabling Port Security on an Access Port

To enable port security on an access port, perform this task: Command
Step 1
Purpose Selects the LAN port to configure.

Note
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 port. 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 Step 5
Router(config-if)# switchport port-security Router(config-if)# do show port-security interface type1 slot/port | include Port Security 1. type = fastethernet, gigabitethernet, or tengigabitethernet
Enables port security on the port. Verifies the configuration.
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
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
1
Purpose
slot/port
Selects the LAN port to configure.
59-6
OL-13013-06
Chapter 59
Command
Step 2 Step 3
Router(config-if)# switchport port-security violation {protect | restrict | shutdown} Router(config-if)# do show port-security interface type1 slot/port | include violation_mode2 1. 2. type = fastethernet, gigabitethernet, or tengigabitethernet violation_mode = protect, restrict, or shutdown
Purpose (Optional) Sets the violation mode and the action to be taken when a security violation is detected. Verifies the configuration.
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. shutdownPuts 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 59-7).
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
Configuring the Port Security Rate Limiter

Note
The truncated switching mode does not support the port security rate limiter.
59-7
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 Step 2
Router(config)# mls rate-limit layer2 port-security rate_in_pps [burst_size] Router(config)# do show mls rate-limit | include PORTSEC
Purpose Configures the port security rate limiter. Verifies the configuration.
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
59-8
OL-13013-06
Chapter 59
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.
Step 3
Router(config-if)# do show port-security interface type1 slot/port | include Maximum 1. type = fastethernet, gigabitethernet, or tengigabitethernet
When configuring the maximum number of secure MAC addresses on a port, note the following information:

The range for number_of_addresses is 1 to 4,097. 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
Enabling Port Security with Sticky MAC Addresses on a Port

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.
Router(config-if)# switchport port-security mac-address sticky 1. type = fastethernet, gigabitethernet, or tengigabitethernet
59-9
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
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
Router(config)# interface type1 slot/port Router(config-if)# switchport port-security mac-address [sticky] mac_address [vlan vlan_ID]
Purpose Selects the LAN port to configure. Configures a static MAC address as secure on the port.
Note
Per-VLAN configuration is supported only on trunks.
Step 3 Step 4
Router(config-if)# end Router# show port-security address 1. type = fastethernet, gigabitethernet, or tengigabitethernet
When configuring a static secure MAC address on a port, note the following information:
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 59-9). 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. Port security is supported on trunks.
On a trunk, you can configure a static secure MAC address in a VLAN.
59-10
OL-13013-06
Chapter 59
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
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 59-11 Configuring Secure MAC Address Aging Time on a Port, page 59-12
Configuring the Secure MAC Address Aging Type on a Port

You can configure the secure MAC address aging type on a port. To configure the secure MAC address aging type on a port, perform this task: Command
1
Purpose
slot/port
Selects the LAN port to configure. Configures the secure MAC address aging type on the port (default is absolute). Verifies the configuration.
Router(config-if)# switchport port-security aging type {absolute | inactivity} Router(config-if)# do show port-security interface type1 slot/port | include Time 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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
59-11
Chapter 59 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). Verifies the configuration.
Router(config-if)# switchport port-security aging time aging_time
Step 3
Router(config-if)# do show port-security interface type1 slot/port | include Time 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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. type = fastethernet, gigabitethernet, or tengigabitethernet
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.
This example displays output from the show port-security command when you do not enter an interface:
Router# show port-security Secure Port MaxSecureAddr Action (Count) CurrentAddr (Count) SecurityViolation (Count) Security
59-12
OL-13013-06
Chapter 59
Configuring Port Security Displaying Port Security Settings
---------------------------------------------------------------------------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
59-13
Chapter 59 Displaying Port Security Settings
59-14
OL-13013-06
PA R T
10
NetFlow
C H A P T E R
60
Configuring NetFlow
This chapter describes how to configure NetFlow statistics collection in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see these publications: http://www.cisco.com/en/US/docs/ios/netflow/command/reference/nf_book.html
Tip

Understanding NetFlow, page 60-1 Default NetFlow Configuration, page 60-5 NetFlow Configuration Guidelines and Restrictions, page 60-6 Configuring NetFlow, page 60-6
Understanding NetFlow
The NetFlow feature collects traffic statistics about the packets that flow through the switch and stores the statistics in the NetFlow table. Several features use the statistics in the NetFlow table, and the statistics can be exported using the NetFlow Data Export (NDE) feature. These sections provide additional information about NetFlow:

NetFlow Overview, page 60-2 NetFlow on the PFC, page 60-2 NetFlow on the RP, page 60-4 NetFlow Features, page 60-4
60-1
Chapter 60 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 route processor (RP) 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 other PFCs, you can configure NetFlow to collect statistics for both routed and bridged traffic. Collecting and exporting a large volume of statistics can significantly impact switch processor (SP) and route processor (RP) CPU 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. Per-interface NetFlow allows you to enable or disable NetFlow data collection on Layer 3 interfaces. NetFlow Flow Sampling exports data for a subset of traffic in a flow, which can greatly reduce the volume of statistics exported. NetFlow Flow Sampling 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. NetFlow aggregation increases SP 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 clear table space for new entries.
NetFlow on the PFC

The NetFlow table on the PFC captures statistics for flows routed in hardware. These sections describe NetFlow on the PFC in more detail:

Flow Masks, page 60-2 Flow Mask Conflicts, page 60-3 Default NetFlow Configuration, page 60-5
Flow Masks
A flow is a unidirectional stream of packets between a source and a destination. The flow mask specifies the fields in the incoming packet that NetFlow uses to match (or create) a NetFlow table entry. All flow masks include the ingress interface in their definition. Therefore, NetFlow always collects statistics on a per-interface basis. You can also enable or disable NetFlow per-interface.
60-2
OL-13013-06
Chapter 60
Configuring NetFlow Understanding NetFlow
The PFC supports the following flow masks:

interface-sourceA less-specific flow mask. Statistics for all ingress flows on an interface from each source IP address aggregate into one entry. interface-destinationA less-specific flow mask. Statistics for all ingress flows on an interface to each destination IP address aggregate into one entry. interface-destination-sourceA more-specific flow mask. Statistics for all ingress flows on an interface between the same source IP address and destination IP address aggregate into one entry. interface-fullThe most-specific flow mask. The PFC creates and maintains a separate table entry for each IP flow on an interface. An interface-full entry includes the source IP address, destination IP address, protocol, and protocol ports.
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 interface-source, the NetFlow table contains one entry per source IP address. (Assume that NetFlow is enabled on only one interface). The statistics for all flows from each source are accumulated in the one entry. However, if the flow mask is configured as interface-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 60-6 for information about NetFlow table capacity.
Flow Mask Conflicts

Several features use the NetFlow table. Table 60-1 lists the flow mask requirements for each feature.
Table 60-1 Feature Requirements for Flow Masks
Feature Reflexive ACL TCP Intercept Web Cache Redirect (WCCP) Server Load Balancing (SLB) Network Address Translation (NAT) NetFlow Data Export (NDE) NetFlow Sampling NetFlow Aggregation
X X X X X X X X X X X X X X X X X X X
Non-interface Full
Interface Destination
Interface Destination Source
Interface Source
Interface Full
Full
60-3
Chapter 60 Understanding NetFlow
Configuring NetFlow
Because of the variety of feature requirements, potential flow mask conflicts can occur. Note the following flow mask constraints:

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 RP is responsible for resolving feature conflicts. The Feature Managers main purpose 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 RP. 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. To avoid problems with feature conflicts, follow these guidelines:

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. 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. NetFlow Flow Sampling requires the full-interface flow mask. 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 translated correctly by NAT if NAT is configured for overload. Except in PFC3A mode, you can use the mls ip nat netflow-frag-l4-zero command to ensure that NAT functions correctly in this configuration.
Note the following specific feature conflicts:
NetFlow on the RP
The NetFlow feature on the RP captures statistics for flows routed in software. For additional information about configuring NetFlow on the RP, see the Cisco IOS NetFlow Configuration Guide, Release 12.2SX.
NetFlow Features
NetFlow supports the following features:

Per Interface NetFlow, page 60-5 NetFlow Aggregation, page 60-5 NetFlow for Multicast IP, page 60-5
60-4
OL-13013-06
Chapter 60
Configuring NetFlow Default NetFlow Configuration
Per Interface NetFlow

Cisco IOS Release 12.2(33)SXH and later releases support per-interface NetFlow, which enables PFC NetFlow data collection on a per-interface basis. With releases earlier than Release 12.2(33)SXH, NetFlow on the PFC could be only be enabled and disabled globally. When you upgrade to a software release that supports the per-interface NetFlow feature, the system automatically enables per-interface NetFlow and configures the ip flow ingress command on every Layer 3 interface. This one-time action takes place on the first reload after the upgrade and maintains backward compatibility with the global NetFlow enable command. After the reload, you can configure the no ip flow ingress command on Layer 3 interfaces to selectively disable PFC and RP NetFlow data collection. The per-interface NetFlow feature only applies to IPv4 unicast flows on Layer 3 interfaces. Flows for non-IPv4 protocols (such as IPv6 and MPLS) are not controlled by this feature.
NetFlow Aggregation
NetFlow supports aggregation for packets forwarded in hardware (PFC) or software (RP). See the Cisco IOS NetFlow Configuration Guide, Release 12.2SX for information about these features:

NetFlow aggregation schemes Configuring NetFlow aggregation ToS-based router aggregation, which is supported by NetFlow on the RP
NetFlow for Multicast IP

NetFlow is supported for multicast IP packets forwarded in hardware (PFC) or software (RP). NetFlow multicast provides ingress accounting and egress accounting. With ingress accounting, NetFlow creates one flow per source and includes information about how many packet replications occur. With egress accounting, NetFlow creates one flow for each outgoing interface. Optionally, NetFlow multicast keeps statistics for multicast packets that fail the reverse path fail (RPF) check.
Note
Disabling the mls netflow command globally will cause non-RPF multicast traffic to be dropped in software, as new non-RPF Netflow entries will not be created.
Default NetFlow Configuration

Table 60-2 shows the default NetFlow configuration.
Table 60-2 Default NetFlow Configuration
Feature NetFlow NetFlow of routed IP traffic
Default Value Enabled Disabled
NetFlow of ingress bridged IP traffic Disabled
60-5
Chapter 60 NetFlow Configuration Guidelines and Restrictions
Configuring NetFlow
Table 60-2
Default NetFlow Configuration (continued)
Feature NetFlow Sampling NetFlow Aggregation Per-interface NDE Exclude ACL-denied traffic
Default Value Disabled Disabled Enabled Disabled (NetFlow creates entries for ACL-denied traffic)
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. Except in PFC3A mode, NetFlow supports bridged IP traffic. PFC3A mode does not support NetFlow bridged IP traffic. NetFlow supports multicast IP traffic.
Note
When you configure NAT on an interface, the PFC sends all fragmented packets to the RP to be processed in software. (CSCdz51590)

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 60-3 lists the recommended maximum utilization levels.
NetFlow Table Utilization
Table 60-3
PFC PFC3CXL PFC3C PFC3BXL PFC3B PFC3A
Recommended NetFlow Table Utilization 235,520 (230 K) entries 117,760 (115 K) entries 235,520 (230 K) entries 117,760 (115 K) entries 65,536 (64 K) entries
Total NetFlow Table Capacity 262,144 (256 K) entries 131,072 (128 K) entries 262,144 (256 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 60-7 Configuring NetFlow Features, page 60-10
60-6
OL-13013-06
Chapter 60
Configuring NetFlow Configuring NetFlow
Configuring NetFlow on the PFC

These sections describe how to configure NetFlow statistics collection on the PFC:

NetFlow PFC Commands Summary, page 60-7 Enabling NetFlow on the PFC, page 60-7 Setting the Minimum IP MLS Flow Mask, page 60-7 Configuring the MLS Aging Time, page 60-8 Displaying PFC NetFlow Information, page 60-10
NetFlow PFC Commands Summary

Table 60-4 shows a summary of the NetFlow commands available on the PFC.
Table 60-4 Summary of PFC NetFlow Commands
Command mls netflow mls flow ip mls aging mls exclude acl-deny show mls netflow {...} show mls netflow aggregation flowmask
Purpose Enables NetFlow on the PFC. Sets the minimum flow mask. Sets the configurable aging parameters. Disables the creation of flows for ACL-denied traffic. Displays NetFlow PFC information for unicast and multicast traffic. Displays the NetFlow aggregation flow mask.
Enabling NetFlow on the PFC

To enable NetFlow statistics collection globally on the PFC, perform this task: Command
Router(config)# mls netflow
Purpose Enables 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 command, if other configured features need a more specific flow mask (see the Flow Mask Conflicts section on page 60-3).
60-7
Chapter 60 Configuring NetFlow
Configuring NetFlow
To set the minimum IPv4 flow mask, perform this task: Command
Router(config)# mls flow ip {interface-source | interface-destination | interface-destination-source | interface-full}
Purpose Sets the minimum flow mask for IPv4 packets.
This example shows how to set the minimum flow mask:

Router(config)# mls flow ip interface-destination
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: if-dst 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 60-6), 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.
60-8
OL-13013-06
Chapter 60
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.
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 Exclude ACL-deny

By default, NetFlow table entries are created for ACL-denied flows. These flows can cause the NetFlow table to overflow. With Release 12.2(33)SXH and later releases, to exclude ACL-denied flows from the NetFlow table, perform this task: Command
Router# mls exclude acl-deny
Purpose Excludes ACL-denied flows from the NetFlow table.
This example shows how to exclude ACL-denied flows from the NetFlow table:
Router(config)# mls exclude acl-deny
60-9
Configuring NetFlow
Displaying PFC NetFlow Information

To display information about NetFlow on the PFC, perform this task: 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 Features

NetFlow features generally apply to packets forwarded in hardware (PFC) and software (RP). For the features to apply to PFC, you need to enable NetFlow on the PFC. These sections describe how to configure NetFlow features:

Configuring NetFlow on Layer 3 Interfaces, page 60-10 Enabling NetFlow for Ingress-Bridged IP Traffic, page 60-11 Configuring NetFlow Aggregation, page 60-11 Configuring NetFlow for Multicast IP Traffic, page 60-12
Configuring NetFlow on Layer 3 Interfaces

The per-interface NDE feature allows you to enable or disable NetFlow collection on a per-interface basis for packets forwarded in hardware (PFC) or software (RP). This feature is automatically enabled in Release 12.2(33)SXH and later releases. To enable or disable NetFlow for a Layer 3 interface, 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
Purpose Selects a Layer 3 interface to configure.
Step 2
Enables NetFlow for the specified interface. NetFlow will collect statistics for packets forwarded in hardware (PFC) or software (RP). Disables NetFlow for the specified interface. NetFlow will stop collecting statistics for packets forwarded in hardware (PFC) or software (RP).
Step 3
Router(config-if)# no ip flow ingress
When you upgrade for the first time to a software image that supports per-interface NetFlow on the PFC, the system automatically configures each Layer 3 interface to enable NetFlow (this ensures backward compatibility with the global mls netflow command). This one-time action occurs during the first system restart after the upgrade. After this action, you can configure Layer 3 interfaces to disable or enable NetFlow data collection.
60-10
OL-13013-06
Chapter 60
Enabling NetFlow for Ingress-Bridged IP Traffic

Except in PFC3A mode, 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 NetFlow Flow Sampling feature (see the NetFlow Sampling section on page 61-7). To enable NetFlow for bridged IP traffic on a VLAN, you must create a corresponding VLAN interface and enter the no shutdown command. The no shutdown command can be followed, if necessary, by the shutdown command. For Layer 3 VLANs, enabling NetFlow for ingress-bridged IP traffic also enables NetFlow for Layer 3 flows on the specified VLANs. The exported bridged flows will have ingress and egress VLAN information and not the physical port information.
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.
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
Configuring NetFlow Aggregation

To configure NetFlow aggregation, use the procedures in the Cisco IOS NetFlow Configuration Guide, Release 12.2SX.
Note
When you configure NetFlow aggregation, it is configured automatically for packets forwarded in hardware (PFC) or software (RP). The PFC and DFCs do not support NetFlow ToS-based router aggregation.
60-11
Configuring NetFlow
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.
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 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
Configuring NetFlow for Multicast IP Traffic

To configure NetFlow for multicast IP traffic, perform this task: Command
Step 1 Step 2
Router(config)# ip multicast netflow output-counters Router(config)# ip multicast netflow rpf-failure
Purpose (Optional) Enables the calculation of output bytes/packets for an ingress flow. (Optional) Enables NetFlow for multicast data that fails the RPF check.
60-12
OL-13013-06
Chapter 60
Command
Step 3
Router(config)# interface {vlan vlan_ID} | {type slot/port} | {port-channel port_channel_number} Router(config-if)# ip flow {ingress | egress}
Purpose Selects a Layer 3 interface to configure.
Step 4
Enables NetFlow multicast traffic on the specified interface (for RP and PFC).

Specify ingress to enable NetFlow multicast ingress accounting. Specify egress to enable NetFlow multicast egress accounting.
For additional information about configuring NetFlow for multicast traffic, see the Configuring NetFlow Multicast Accounting section of the Cisco IOS NetFlow Configuration Guide, Release 12.2SX. The Configuring NetFlow Multicast Accounting section specifies as a prerequisite that you need to configure multicast fast switching or multicast distributed fast switching (MDFS), but this prerequisite does not apply when configuring NetFlow multicast support with 12.2SX releases.
Note
The Configuring NetFlow Multicast Accounting document describes new configuration commands for Cisco IOS Release 12.2(4) and newer releases. The 12.2SX releases support the new commands.
Tip
60-13
Configuring NetFlow
60-14
OL-13013-06
C H A P T E R
61
Configuring NDE
This chapter describes how to configure NetFlow Data Export (NDE).
Note
The Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/netflow/command/reference/nf_book.html The Cisco IOS NetFlow Configuration Guide, Release 12.2SX , which provides information about NetFlow version 9.
Tip

Understanding NDE, page 61-2 Default NDE Configuration, page 61-10 NDE Configuration Guidelines and Restrictions, page 61-10 Configuring NDE, page 61-10
61-1
Chapter 61 Understanding NDE
Configuring NDE
Understanding NDE
These sections describe how NetFlow Data Export (NDE) works:

NDE Overview, page 61-2 NDE on the RP, page 61-2
NDE Overview
NetFlow collects traffic statistics by monitoring the packets that flow through the switch and storing the statistics in the NetFlow table. For more information about NetFlow, see Chapter 60, Configuring NetFlow. 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 modes other than PFC3A, you can configure NDE to export statistics for both routed and bridged traffic. 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. 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.
NDE on the RP
The RP supports these features, which are documented in the Cisco IOS NetFlow Configuration Guide, Release 12.2SX:

NDE for flows routed in software NetFlow aggregation NetFlow ToS-based router aggregation NetFlow flow sampling NetFlow version 9 export
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 61-3 NDE Versions, page 61-3 Exporting NetFlow Data, page 61-7 NetFlow Sampling, page 61-7
61-2
OL-13013-06
Chapter 61
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, see Chapter 60, 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. These fields are empty when you use the show command to display the hardware NetFlow table.
NDE Versions
NetFlow version 9 is described in this publication: http://www.cisco.com/en/US/docs/ios/12_3/feature/gde/nfv9expf.html NDE exports statistics for NetFlow aggregation flows using NDE version 8. The following document describes the version 8 header format: http://www.cisco.com/univercd/cc/td/doc/product/software/ios122/122cgcr/fswtch_c/swprt2/xcfnf ov.htm#wp1001212
With 12.2SX releases, 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 61-1Version 5 header format Table 61-2Version 7 header format Table 61-3Version 5 flow record format Table 61-4Version 7 flow record format
61-3
Configuring NDE
Table 61-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 61-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
61-4
OL-13013-06
Chapter 61
Table 61-3
NDE Version 5 Flow Record Format
Flow masks: X=Populated A=Additional field (see the Populating Additional NDE Fields section on page 61-11) Destination Source Interface Destination Destination Source 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 address

1
X 0 0 0 0 X X
0 X A 0 A X X X X 0 0 0 0 0 X6 0 X 0 X 0
2 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
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
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. Except in PFC3A mode, for ICMP traffic, contains the ICMP code and type values. 5. Always zero for hardware-switched flows. 6. Not populated in PFC3A mode.
Full
61-5
Configuring NDE
Table 61-4
NDE Version 7 Flow Record Format
Flow masks: X=Populated A=Additional field (see the Populating Additional NDE Fields section on page 61-11) Destination Source Interface Destination Destination Source Full Interface
X X A X A X X X X X4 X X 0 X X6 X X X X 0 X
Source
Bytes 03 47 811
Content srcaddr dstaddr nexthop
Description Source IP address Destination IP address Next hop routers IP address

1
X 0 0 0 0 X X
0 X A 0 A X X X X 0 0 X 0 0 X6 0 X 0 X 0 X
2 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
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
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. Except in PFC3A mode, for ICMP traffic, contains the ICMP code and type values. 5. Always zero for hardware-switched flows. 6. Not populated in PFC3A mode.
61-6
Full
OL-13013-06
Chapter 61
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 61-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 61-7 NetFlow Flow Sampling, page 61-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
61-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. 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].
61-8
OL-13013-06
Chapter 61
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/8th2/8th 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 61-5 lists the sampling rates and export intervals for time-based NetFlow flow sampling.
Table 61-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
61-9
Chapter 61 Default NDE Configuration
Configuring NDE
Default NDE Configuration

Table 61-6 shows the default NDE configuration.
Table 61-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:

You must enable NetFlow on the PFC to export data for packets forwarded in hardware. When you configure NAT and NDE on an interface, the PFC sends all fragmented packets to the RP to be processed in software. (CSCdz51590) NDE supports IP multicast traffic only with NetFlow version 9. NetFlow aggregation must use NDE version 8 or version 9. Except in PFC3A mode, 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. Aggregation support (ip flow-aggregation cache command) Export of Layer 2 switched IPv6 flows Netflow and NDE sampling NDE filter support
The following IPv4 Netflow and NDE options are not available for IPv6 flows:

Configuring NDE
These sections describe how to configure NDE:

Configuring NDE on the PFC, page 61-11 Configuring NDE on the RP, page 61-13 Enabling NDE for Ingress-Bridged IP Traffic, page 61-14 Displaying the NDE Address and Port Configuration, page 61-15 Configuring NDE Flow Filters, page 61-16 Displaying the NDE Configuration, page 61-17
61-10
OL-13013-06
Chapter 61
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 61-11 Populating Additional NDE Fields, page 61-11 Configuring NetFlow Flow Sampling, page 61-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, WX-X6716-10GE, or WX-X6716-10T 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.
1. The ip flow-export version 9 command was integrated into 12.2(18)SXF.
Note
NDE from the PFC uses the source interface configured for the RP (see the Configuring the RP NDE Source Layer 3 Interface section on page 61-13). NetFlow version 9 is described at this URL: http://www.cisco.com/en/US/docs/ios/12_3/feature/gde/nfv9expf.html
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
Populating Additional NDE Fields

You can configure NDE to populate the following additional fields in the NDE packets:
61-11
Chapter 61 Configuring NDE
Configuring NDE
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 61-3 for additional information. To populate the additional fields in NDE packets, perform this task: Command
Router(config)# mls nde interface
Purpose Populates additional fields in NDE packets.
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 61-12 Configuring NetFlow Flow Sampling on a Layer 3 Interface, page 61-12
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 NetFlow flow sampling and configures the rate. For packet-based sampling, optionally configures the export interval. Exits configuration mode.
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. To export any data, you must also configure NetFlow flow sampling on a Layer 3 interface.
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.
61-12
OL-13013-06
Chapter 61
To configure NetFlow flow sampling on a Layer 3 interface, perform this task: Command
Router(config)# interface {vlan vlan_ID | type slot/port} Router(config-if)# mls netflow sampling Router(config)# end
Purpose Selects a Layer 3 interface to configure. Enables NetFlow flow sampling on the Layer 3 interface. Exits configuration mode.
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 RP

These sections describe how to configure NDE on the RP:

Configuring the RP NDE Source Layer 3 Interface, page 61-13 Configuring the NDE Destination, page 61-14 Configuring NetFlow Sampling, page 61-14
Configuring the RP NDE Source Layer 3 Interface

To configure the Layer 3 interface used as the source of the NDE packets containing statistics from the RP, perform this task: Command
Router(config)# ip flow-export source {{vlan vlan_ID} | {type slot/port} | {port-channel number} | {loopback number}}
Purpose Configures the interface used as the source of the NDE packets containing statistics from the RP.
When configuring the RP NDE source Layer 3 interface, note the following information:

You must select an interface configured with an IP address. 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)#
61-13
Configuring NDE
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 [vrf vrf_name]
Purpose Configures the NDE destination IP address and UDP port. (Optional) Specify a VPN routing/forwarding table name.
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. 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 Sampling

The RP supports NetFlow sampling for software-routed traffic. For additional information, see the Cisco IOS NetFlow Configuration Guide.
Enabling NDE for Ingress-Bridged IP Traffic

Except in PFC3A mode, NDE supports ingress-bridged IP traffic. PFC3A mode does not support NDE for bridged IP traffic. NDE is enabled by default when you enable NetFlow on the VLAN. For additional information, see Configuring NetFlow on Layer 3 Interfaces section on page 60-10. 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.
61-14
OL-13013-06
Chapter 61
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 NDE information for hardware flows including the NDE export flow IP address, UDP port, and the NDE source interface configuration. Displays NDE information for software flows including 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: 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
61-15
Configuring NDE
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 61-16 Configuring a Port Flow Filter, page 61-16 Configuring a Host and Port Filter, page 61-16 Configuring a Host Flow Filter, page 61-17 Configuring a Protocol Flow Filter, page 61-17
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 61-17.
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}
Purpose Configures a port flow filter for an NDE flow.
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}}
Purpose Configures a host and port flow filter for an NDE flow.
61-16
OL-13013-06
Chapter 61
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}}
Purpose Configures a host flow filter for an NDE flow.
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)#
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}}
Purpose Configures a protocol flow filter for an NDE flow.
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 61-17.
Displaying the NDE Configuration

To display the NDE configuration, perform this task: Command
Purpose Displays the NDE configuration.
This example shows how to display the NDE configuration:

61-17
Configuring 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 Router#
Tip
61-18
OL-13013-06
PA R T
11
Network Management
C H A P T E R
62

This chapter describes how to configure the Call Home feature in Cisco IOS Release 12.2SX. Release 12.2(33)SXH and later releases support the Call Home feature.
Note
Tip
This chapter includes the following sections:

Understanding Call Home, page 62-2 Obtaining Smart Call Home, page 62-3 Default Settings, page 62-3 Configuring Call Home, page 62-3 Configuring the Smart Call Home Service, page 62-20 Displaying Call Home Configuration Information, page 62-23 Alert Group Trigger Events and Commands, page 62-26 Message Contents, page 62-33
62-1
Chapter 62 Understanding Call Home
Understanding Call Home

Call Home provides email-based and web-based notification of critical system events. A versatile range of message formats are available for optimal compatibility with pager services, standard email, or XML-based automated parsing applications. Common uses of this feature may include direct paging of a network support engineer, email notification to a Network Operations Center, XML delivery to a support website, and utilization of Cisco Smart Call Home services for direct case generation with the Cisco Systems Technical Assistance Center (TAC). The Call Home feature can deliver alert messages containing information on configuration, diagnostics, environmental conditions, inventory, and syslog events. The Call Home feature can deliver alerts to multiple recipients, referred to as Call Home destination profiles, each with configurable message formats and content categories. A predefined destination profile (CiscoTAC-1) is provided, and you also can define your own destination profiles. The CiscoTAC-1 profile is used to send alerts to the backend server of the Smart Call Home service, which can be used to create service requests to the Cisco TAC (depending on the Smart Call Home service support in place for your device and the severity of the alert). Flexible message delivery and format options make it easy to integrate specific support requirements. If multiple destination profiles are configured, and one fails, the system will try every configured profile before sending a failure message. The Call Home feature provides these functions:
Multiple message-format options:

Short TextSuitable for pagers or printed reports. Plain TextFull formatted message information suitable for human reading. XMLMachine readable format using Extensible Markup Language (XML) and Adaptive
Markup Language (AML) document type definitions (DTDs). The XML format enables communication with the Cisco Smart Call Home server.

Multiple concurrent message destinations. Multiple message categories including configuration, diagnostics, environmental conditions, inventory, and syslog events. Filtering of messages by severity and pattern matching. Scheduling of periodic message sending. Continuous device health monitoring and real-time diagnostics alerts. Analysis of Call Home messages from your device and, where supported, Automatic Service Request generation, routed to the appropriate TAC team, including detailed diagnostic information to speed problem resolution. Secure message transport directly from your device or through a downloadable Transport Gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices may not be connected directly to the Internet. Web-based access to Call Home messages and recommendations, inventory and configuration information for all Call Home devices that provides access to associated Field Notices, Security Advisories and End-of-Life Information.
62-2
OL-13013-06
Chapter 62
Configuring Call Home Obtaining Smart Call Home
Obtaining Smart Call Home

If you have a service contract directly with Cisco Systems, you can register your Call Home devices for the Cisco Smart Call Home service. Smart Call Home provides fast resolution of system problems by analyzing Call Home messages sent from your devices and providing background information and recommendations. For issues that can be identified as known, particularly GOLD diagnostics failures, depending on the Smart Call Home service support in place for your device and the severity of the alert, Automatic Service Requests will be generated with the Cisco TAC. You need the following items to register:

The SMARTnet contract number for your switch. Your email address Your Cisco.com ID
For detailed information on Smart Call Home, see the Smart Call Home page at this location: http://www.cisco.com/en/US/products/ps7334/serv_home.html
Default Settings
Table 62-1 lists the default Call Home settings.
Table 62-1 Default Call Home Settings
Parameters Call Home feature status User-defined profile status Predefined Cisco TAC profile status Transport method Message format type Alert group status Call Home message severity threshold Message rate limit for messages per minute
Default Disabled Active Inactive Email XML Enabled 0 (debugging) 20
Destination message size for a message sent in long text, short text, or XML format 3,145,728

These sections provide an overview of Call Home configuration:

Configuration Overview, page 62-4 Configuring Customer Contact Information, page 62-4 Configuring Destination Profiles, page 62-5 Subscribing to Alert Groups, page 62-13 Enabling Call Home, page 62-16
62-3
Chapter 62 Configuring Call Home
Testing Call Home Communications, page 62-16 Configuring and Enabling Smart Call Home, page 62-19
Configuration Overview
Consider these items before you configure Call Home:

Obtain customer email, phone, and street address information for the Call Home contact to be configured so that the receiver can determine the origin of messages received. If using email message delivery, identify the name or IPv4 address of a primary Simple Mail Transfer Protocol (SMTP) server and any backup servers. If using secure HTTP (HTTPS) message delivery, configure a trustpoint certificate authority (CA) . For example, this procedure is required if you are using the HTTPS server for Cisco Smart Call Home Service in the CiscoTAC-1 profile for Call Home. Verify IP connectivity from the router to the email server(s) or the destination HTTP server. If servers are specified by name, the switch must have IP connectivity to a domain name server. If using Cisco Smart Call Home, verify that an active service contract exists for the device being configured.
Tip
From the Smart Call Home web application, you can download a basic configuration script to assist you in the configuration of the Call Home feature for use with Smart Call Home and the Cisco TAC. The script will also assist in configuring the trustpoint CA for secure communications with the Smart Call Home service. The script, provided on an as-is basis, can be downloaded from this URL: http://www.cisco.com/en/US/products/ps7334/serv_home.html
Configuring Customer Contact Information

These are customer contact information items:

Email address (required) Phone number (optional) Street address (optional) Contract ID (optional) Customer ID (optional) Site ID (optional)
To configure the customer contact information, perform this task: Command

Step 1 Router# configure terminal Step 2 Router(config)# call-home Step 3 Router(cfg-call-home)# contact-email-addr
email-address
Purpose Enters configuration mode. Enters Call Home configuration mode. Assigns the customers email address. Enter up to 200 characters in email address format with no spaces.
62-4
OL-13013-06
Chapter 62
Configuring Call Home Configuring Call Home
Command
Step 4 Router(cfg-call-home)# phone-number +phone-number
Purpose (Optional) Assigns the customers phone number.

Note
The number must begin with a plus (+) prefix, and may contain only dashes (-) and numbers. Enter up to 16 characters. If you include spaces, you must enclose your entry in quotes ().
Step 5 Router(cfg-call-home)# street-address

street-address
(Optional) Assigns the customers street address where RMA equipment can be shipped. Enter up to 200 characters. If you include spaces, you must enclose your entry in quotes (). (Optional) Identifies the customer ID. Enter up to 64 characters. If you include spaces, you must enclose your entry in quotes (). (Optional) Identifies the customer site ID. Enter up to 200 characters. If you include spaces, you must enclose your entry in quotes (). (Optional) Identifies the customers contract ID for the switch. Enter up to 64 characters. If you include spaces, you must enclose your entry in quotes ().
Step 6 Router(cfg-call-home)# customer-id text
Step 7 Router(cfg-call-home)# site-id text
Step 8 Router(cfg-call-home)# contract-id text
This example shows the configuration of contact information:

Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# call-home Router(cfg-call-home)# contact-email-addr username@example.com Router(cfg-call-home)# phone-number +1-800-555-4567 Router(cfg-call-home)# street-address "1234 Picaboo Street, Any city, Any state, 12345" Router(cfg-call-home)# customer-id Customer1234 Router(cfg-call-home)# site-id Site1ManhattanNY Router(cfg-call-home)# contract-id Company1234 Router(cfg-call-home)# exit Router(config)#
Configuring Destination Profiles

These sections describe destination profiles:

Destination Profile Overview, page 62-6 Configuring Call Home to Use VRF, page 62-6 Configuring a Destination Profile to Send Email Messages, page 62-7 Configuring a Destination Profile to Send HTTP Messages, page 62-9 Configuring Call Home Traffic Rate Limiting, page 62-11 Destination Profile Management, page 62-11
62-5
Destination Profile Overview

A destination profile contains the required delivery information for an alert notification. At least one destination profile is required. You can configure multiple destination profiles of one or more types. You can use the predefined destination profile or define a desired profile. If you define a new destination profile, you must assign a profile name. You can configure the following attributes for a destination profile:

Profile nameA string that uniquely identifies each user-defined destination profile. The profile name is limited to 31 characters and is not case-sensitive. You cannot use all as a profile name. Transport methodThe transport mechanism, either email or HTTP (including HTTPS), for delivery of alerts.
For user-defined destination profiles, email is the default, and you can enable either or both
transport mechanisms. If you disable both methods, email will be enabled.

For the predefined Cisco TAC profile, you can enable either transport mechanism, but not both.
Destination addressThe actual address related to the transport method to which the alert should be sent. Message formattingThe message format used for sending the alert.
For user-defined destination profiles, the format options are long-text, short-text, or XML. The
default is XML.
For the predefined Cisco TAC profile, only XML is allowed.
Message sizeThe maximum destination message size. The valid range is 50 to 3,145,728 bytes and the default is 3,145,728 bytes.
Note
The Call Home feature provides a predefined profile named CiscoTAC-1 that is inactive by default. The CiscoTAC-1 profile is intended for use with the Smart Call Home service, which requires certain additional configuration steps to enable the service with the Call Home feature. For more information about this profile, see the Using the Predefined CiscoTAC-1 Destination Profile section on page 62-13. If you use the Cisco Smart Call Home service, the destination profile must use the XML message format.
Configuring Call Home to Use VRF

To configure Call Home to use a VRF interface for Call Home email or for HTTP messages, perform this task: Command or Action
Router# configure terminal Router(config)# interface type Router(config-if)# ip address ip_address mask
Purpose Enters configuration mode. Selects an interface to configure. Assigns an IP address and subnet mask to the interface.
62-6
OL-13013-06
Chapter 62
Command or Action
Step 3 Step 4
Router(config-if)# vrf forwarding call_home_vrf_name Router(config-if)# exit
Purpose Associates the call_home_vrf_name VRF with the interface. Exits interface configuration mode.
This example shows how to configure Call Home to use a VRF interface:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# interface gigabitethernet 1/1 Router(config-if)# ip address 10.10.10.10 0.0.0.0 Router(config-if)# vrf forwarding call_home_vrf Router(config-if)# exit Router(config)#
Configuring a Destination Profile to Send Email Messages

To configure Call Home to send email messages, complete the following tasks:

Configuring Call Home to Use VRF for Email Messages, page 62-7 (optional) Configuring the Mail Server, page 62-8 (required) Configuring a Destination Profile for Email, page 62-8 (required) Configuring Other Email Options, page 62-9 (optional)
Note
To send Call Home email messages through a VRF interface, configure Call Home to use VRF (see Configuring Call Home to Use VRF section on page 62-6).
Configuring Call Home to Use VRF for Email Messages

To configure Call Home to use a VRF instance for Call Home email messages, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(cfg-call-home)# vrf call_home_vrf_name
Purpose Enters configuration mode. Enters Call Home configuration submode. Specifies the VRF instance to use for Call Home email messages.
Note
Release 12.2(33)SXI1 and later releases support VRF configuration for Call Home email messages.
This example shows how to configure Call Home to use a VRF interface:
Router# configure terminal Enter configuration commands, one per line. Router(config)# call-home Router(cfg-call-home)# vrf call_home_vrf Router(cfg-call-home)# exit Router(config)# End with CNTL/Z.
62-7
Configuring the Mail Server

To use the email message transport, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(cfg-call-home)# mail-server {ipv4-address | name} priority number
Purpose Enters global configuration mode. Enters call home configuration mode. Specifies an email server and its relative priority among configured email servers, where:

ipv4-addressSpecifies the IPv4 address of the mail server. nameSpecifies the mail servers fully qualified domain name (FQDN) of 64 characters or less. numberAssigns a number between 1 (highest priority) and 100 (lowest priority). Higher priority (lower priority numbers) are tried first. Repeat to define backup email servers (maximum four backup email servers, for a total of five email servers.
The following example shows the configuration of a primary mail server (named smtp.example.com) and secondary mail server at IP address 192.168.0.1:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# call-home Router(cfg-call-home)# mail-server smtp.example.com priority 1 Router(cfg-call-home)# mail-server 192.168.0.1 priority 2 Router(cfg-call-home)# exit Router(config)#
Configuring a Destination Profile for Email

To configure a destination profile for email transport, complete this task: Command or Action
Router# configure terminal Router(config)# call-home Router(config-call-home)# profile name
Purpose Enters global configuration mode. Enters call home configuration mode. Enters call home destination profile configuration mode for the specified destination profile name. If the specified destination profile does not exist, it is created. Configures the message transport method for email. (This is the default.) Configures the destination email address to which Call Home messages are sent. (Optional) Configures a preferred message format. The default is XML.
Router(cfg-call-home-profile)# destination transport-method email Router(cfg-call-home-profile)# destination address email email_address Router(cfg-call-home-profile)# destination preferred-msg-format {long-text | short-text | xml}
62-8
OL-13013-06
Chapter 62
Command or Action
Step 7
Router(cfg-call-home-profile)# destination message-size bytes
Purpose (Optional) Configures a maximum destination message size (from 50 to 3145728 bytes) for the destination profile. The default is 3145728 bytes. (Optional) Enables the destination profile. By default, a user-defined profile is enabled when it is created. Exits call home destination profile configuration mode and returns to call home configuration mode. Returns to privileged EXEC mode.
Router(cfg-call-home-profile)# active
Router(cfg-call-home-profile)# exit
Router(cfg-call-home)# end
Configuring Other Email Options

To configure other email options, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(cfg-call-home)# sender from email-address
Purpose Enters global configuration mode. Enters call home configuration mode. (Optional) Assigns the email address that will appear in the from field in Call Home email messages. If no address is specified, the contact email address is used. (Optional) Assigns the email address that will appear in the reply-to field in Call Home email messages. (Optional; supported in Release 12.2(33)SXI and later releases) Assigns the source IP address that will be used for Call Home email messages.
Step 4 Step 5
Router(cfg-call-home)# sender reply-to email-address Router(cfg-call-home)# source-ip-address ip_address
This example shows how to configure the email options:

Router(cfg-call-home)# sender from username@example.com Router(cfg-call-home)# sender reply-to username@example.com Router(cfg-call-home)# source-ip-address 10.10.10.10
Configuring a Destination Profile to Send HTTP Messages

To configure Call Home to send HTTP (or HTTPS) messages, complete the following tasks:

Configuring the HTTP Source Interface, page 62-10 Configuring a Destination Profile for HTTP, page 62-10 Configuring a Trustpoint Certificate Authority, page 62-11 (required for HTTPS)
62-9
Configuring the HTTP Source Interface

To configure an HTTP client source interface, perform this task: Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# ip http client source-interface type number
Purpose Enters global configuration mode. Configures the source interface for the HTTP client. If the interface is associated with a VRF instance, the HTTP messages use the VRF instance.
Configuring a Destination Profile for HTTP

To configure a destination profile for HTTP transport, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(config-call-home)# profile name
Purpose Enters global configuration mode. Enters call home configuration mode. Enters call home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created. Enables the HTTP message transport method. Configures the destination URL to which Call Home messages are sent.
Note
Step 4 Step 5
Router(cfg-call-home-profile)# destination transport-method http Router(cfg-call-home-profile)# destination address http url
When entering a destination URL, include either http:// or https://, depending on whether the server is a secure server. If the destination is a secure server, you must also configure a trustpoint CA.
Step 6
Router(cfg-call-home-profile)# destination preferred-msg-format {long-text | short-text | xml} Router(cfg-call-home-profile)# destination message-size bytes Router(cfg-call-home-profile)# active
(Optional) Configures a preferred message format. The default is XML. (Optional) Configures a maximum destination message size for the destination profile. Enables the destination profile. By default, a profile is enabled when it is created. Exits call home destination profile configuration mode and returns to call home configuration mode. Returns to privileged EXEC mode.
Router(cfg-call-home)# end
This example shows how to configure a destination profile for HTTP transport:
Router# configure terminal Router(config)# call-home Router(config-call-home)# profile test Router(cfg-call-home-profile)# destination Router(cfg-call-home-profile)# destination Router(cfg-call-home-profile)# destination Router(cfg-call-home-profile)# destination Router(cfg-call-home-profile)# active
transport-method http address http https://example.url.com preferred-msg-format xml message-size 3,145,728
62-10
OL-13013-06
Chapter 62
Router(cfg-call-home-profile)# exit Router(cfg-call-home)# end
Configuring a Trustpoint Certificate Authority

If you are using the HTTP transport method and specifying an HTTPS destination URL, then you will also need to configure a trustpoint certificate authority (CA). See the Declare and Authenticate a CA Trustpoint section on page 62-21.
Configuring Call Home Traffic Rate Limiting

To configure Call Home traffic rate limiting, perform this task: Command
Step 1 Router# configure terminal Step 2 Router(config)# call-home Step 3 Router(cfg-call-home)# rate-limit number
Purpose Enters configuration mode. Enters Call Home configuration submode. (Optional) Specifies a limit on the number of messages sent per minute, from 1 to 60. The default is 20.
This example shows how to configure Call Home traffic rate limiting:
Router# configure terminal Router(config)# call-home Router(config-call-home)# profile test Router(cfg-call-home-profile)# rate-limit 20
Destination Profile Management

These sections describe destination profile management:

Activating and Deactivating a Destination Profile, page 62-11 Copying a Destination Profile, page 62-12 Renaming a Destination Profile, page 62-13 Using the Predefined CiscoTAC-1 Destination Profile, page 62-13 Verifying the Call Home Profile Configuration, page 62-13
Activating and Deactivating a Destination Profile

Except for the predefined CiscoTAC-1 profile, all Call Home destination profiles are automatically activated when you create them. If you do not want to use a profile right way, you can deactivate the profile. The CiscoTAC-1 profile is inactive by default and must be activated to be used. To activate or deactivate a destination profile, perform this task: Command or Action
Step 1 Step 2
Router# configure terminal Router(config)# call-home
Purpose Enters global configuration mode. Enters call home configuration mode.
62-11
Command or Action
Step 3
Router(config-call-home)# profile name
Purpose Enters call home destination profile configuration mode for the specified destination profile. If the specified destination profile does not exist, it is created. Enables the destination profile. By default, a new profile is enabled when it is created. Disables the destination profile. Exits call home destination profile configuration mode and returns to privileged EXEC mode.
Router(cfg-call-home-profile)# active
Router(cfg-call-home-profile)# no active Router(cfg-call-home)# end
This example shows how to activate a destination profile:

Router# configure terminal Router(config)# call-home Router(config-call-home)# profile test Router(cfg-call-home-profile)# active Router(cfg-call-home)# end
This example shows how to deactivate a destination profile:

Router# configure terminal Router(config)# call-home Router(config-call-home)# profile test Router(cfg-call-home-profile)# no active Router(cfg-call-home)# end
Copying a Destination Profile

To create a new destination profile by copying an existing profile, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(cfg-call-home)# copy profile source_profile target_profile
Purpose Enters global configuration mode. Enters call home configuration mode. Creates a new destination profile with the same configuration settings as the existing destination profile, where:

source_profileSpecifies the existing name of the profile. target_profileSpecifies a name for the new copy of the profile.

Router# configure terminal Router(config)# call-home Router(config-call-home)# profile test Router(cfg-call-home-profile)# copy profile profile1 profile2
62-12
OL-13013-06
Chapter 62
Renaming a Destination Profile

To change the name of an existing profile, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(cfg-call-home)# rename profile source_profile target_profile
Purpose Enters global configuration mode. Enters call home configuration mode. Renames an existing source file, where:

source_profileSpecifies the existing name of the profile. target_profileSpecifies a new name for the existing profile.

Router# configure terminal Router(config)# call-home Router(config-call-home)# profile test Router(cfg-call-home-profile)# rename profile profile1 profile2
Using the Predefined CiscoTAC-1 Destination Profile

The CiscoTAC-1 profile is automatically configured in the Call Home feature for your use with the Cisco Smart Call Home service. This profile includes certain information, such as the destination email address and HTTPS URL, and default alert groups for communication with the Smart Call Home service. Some of these attributes, such as the destination email address, HTTPS URL, and message format cannot be modified. You can use either email or http transport to communicate with the Smart Call Home service backend server. By default, the CiscoTAC-1 profile is inactive and uses email as the default transport method. To use email transport, you only need to enable the profile. However, to use this profile with the Cisco Smart Call Home service secure server (via HTTPS), you not only must enable the profile, but you must also change the transport method to HTTP as shown in the following example:
Router# configure terminal Router(config)# call-home Router(config-call-home)# profile CiscoTAC-1 Router(cfg-call-home-profile)# destination transport-method http Router(cfg-call-home-profile)# active
For more information about additional requirements for Configuring the Smart Call Home service, see the Configuring and Enabling Smart Call Home section on page 62-19.
Verifying the Call Home Profile Configuration

To verify the profile configuration for Call Home, use the show call-home profile command. See the Displaying Call Home Configuration Information section on page 62-23 for more information and examples.
Subscribing to Alert Groups

These sections describe subscribing to alert groups:
62-13
Overview of Alert Group Subscription, page 62-14 Configuring Alert Group Subscription, page 62-14 Configuring Periodic Notification, page 62-15 Configuring Message Severity Threshold, page 62-15 Configuring Syslog Pattern Matching, page 62-16
Overview of Alert Group Subscription

An alert group is a predefined subset of Call Home alerts supported in all switches. Different types of Call Home alerts are grouped into different alert groups depending on their type. These alert groups are available: Configuration Diagnostic

Environment Inventory Syslog
The triggering events for each alert group are listed in the Alert Group Trigger Events and Commands section on page 62-26, and the contents of the alert group messages are listed in the Message Contents section on page 62-33. You can select one or more alert groups to be received by a destination profile.
Note
A Call Home alert is only sent to destination profiles that have subscribed to the alert group containing that Call Home alert. In addition, the alert group must be enabled.
Configuring Alert Group Subscription

To subscribe a destination profile to an alert group, perform this task: Command
Router# configure terminal Router(config)# call-home Router(cfg-call-home)# alert-group {all | configuration | diagnostic | environment | inventory | syslog} Router(cfg-call-home)# profile name
Purpose Enters configuration mode. Enters Call Home configuration submode. Enables the specified alert group. Use the keyword all to enable all alert groups. By default, all alert groups are enabled. Enters the Call Home destination profile configuration submode for the specified destination profile. Subscribes this destination profile to the Configuration alert group. The Configuration alert group can be configured for periodic notification, as described in the Configuring Periodic Notification section on page 62-15. Subscribes to all available alert groups.
Step 4 Step 5
Router(cfg-call-home-profile)# subscribe-to-alert-group configuration [periodic {daily hh:mm | monthly date hh:mm | weekly day hh:mm}] Router(cfg-call-home-profile)# subscribe-to-alert-group all
Step 6
62-14
OL-13013-06
Chapter 62
Command
Step 7
Router(cfg-call-home-profile)# subscribe-to-alert-group diagnostic [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}] Router(cfg-call-home-profile)# subscribe-to-alert-group environment [severity {catastrophic | critical | debugging | disaster | fatal | major | minor | normal | notification | warning}] Router(cfg-call-home-profile)# subscribe-to-alert-group inventory [periodic {daily hh:mm | monthly date hh:mm | weekly day hh:mm}]
Purpose Subscribes this destination profile to the Diagnostic alert group. The Diagnostic alert group can be configured to filter messages based on severity, as described in the Configuring Message Severity Threshold section on page 62-15. Subscribes this destination profile to the Environment alert group. The Environment alert group can be configured to filter messages based on severity, as described in the Configuring Message Severity Threshold section on page 62-15. Subscribes this destination profile to the Inventory alert group. The Inventory alert group can be configured for periodic notification, as described in the Configuring Periodic Notification section on page 62-15. Subscribes this destination profile to the Syslog alert group. The Syslog alert group can be configured to filter messages based on severity, as described in the Configuring Message Severity Threshold section on page 62-15. You can specify a pattern to be matched in the syslog message, as described in the Configuring Syslog Pattern Matching section on page 62-16. If the pattern contains spaces, you must enclose it in quotes (). Exits the Call Home destination profile configuration submode.
Step 8
Step 9
Step 10 Router(cfg-call-home-profile)#
subscribe-to-alert-group syslog [severity {catastrophic | disaster | fatal | critical | major | minor | warning | notification | normal | debugging} [pattern string]]
Step 11 Router(cfg-call-home-profile)# exit
Configuring Periodic Notification

When you subscribe a destination profile to either the Configuration or the Inventory alert group (see the Configuring Alert Group Subscription section on page 62-14), you can choose to receive the alert group messages asynchronously or periodically at a specified time. The sending period can be one of the following:

DailySpecify the time of day to send, using an hour:minute format hh:mm, with a 24-hour clock (for example, 14:30). WeeklySpecify the day of the week and time of day in the format day hh:mm, where the day of the week is spelled out (for example, monday). MonthlySpecify the numeric date, from 1 to 31, and the time of day, in the format date hh:mm.
Configuring Message Severity Threshold

When you subscribe a destination profile to the Diagnostic, Environment, or Syslog alert group (see the Configuring Alert Group Subscription section on page 62-14), you can set a threshold for the sending of alert group messages based on the messages level of severity. Any message with a value lower than the destination profiles specified threshold is not sent to the destination. The severity threshold is configured using the keywords in Table 62-2, and ranges from catastrophic (level 9, highest level of urgency) to debugging (level 0, lowest level of urgency). If no severity threshold is configured, the default is debugging (level 0).
62-15
Note
Call Home severity levels are not the same as system message logging severity levels.
Table 62-2 Severity and Syslog Level Mapping
Level 9 8 7 6 5 4 3 2 1 0
Keyword catastrophic disaster fatal critical major minor warning notification normal debugging
Syslog Level N/A N/A Emergency (0) Alert (1) Critical (2) Error (3) Warning (4) Notice (5) Information (6) Debug (7)
Description Network-wide catastrophic failure. Significant network impact. System is unusable. Critical conditions, immediate attention needed. Major conditions. Minor conditions. Warning conditions. Basic notification and informational messages. Possibly independently insignificant. Normal event signifying return to normal state. Debugging messages.
Configuring Syslog Pattern Matching

When you subscribe a destination profile to the Syslog alert group (see the Configuring Alert Group Subscription section on page 62-14), you can optionally specify a text pattern to be matched within each syslog message. If you configure a pattern, a Syslog alert group message will be sent only if it contains the specified pattern and meets the severity threshold. If the pattern contains spaces, you must enclose it in quotes () when configuring it. You can specify up to five patterns for each destination profile.
Enabling Call Home

To enable or disable the Call Home feature, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# service call-home
Purpose Enters configuration mode. Enables the Call Home feature.
Testing Call Home Communications

You can test Call Home communications by sending messages manually using two command types. To send a user-defined Call Home test message, use the call-home test command. To send a specific alert group message, use the call-home send command. These sections describe Call Home communication:

Sending a Call Home Test Message Manually, page 62-17 Sending a Call Home Alert Group Message Manually, page 62-17
62-16
OL-13013-06
Chapter 62
Sending a Request for an Analysis and Report, page 62-18 Sending the Output of a Command, page 62-19
Sending a Call Home Test Message Manually

To manually send a Call Home test message, perform this task: Command
Router# call-home test ["test-message"] profile name
Purpose Sends a test message to the specified destination profile. The user-defined test message text is optional, but must be enclosed in quotes () if it contains spaces. If no user-defined message is configured, a default message will be sent.
Sending a Call Home Alert Group Message Manually

To manually trigger a Call Home alert group message, perform this task: Command
Step 1 Router# call-home send alert-group configuration [profile name]
Purpose Sends a configuration alert group message to one destination profile if specified, or to all subscribed destination profiles. Sends a diagnostic alert group message to the configured destination profile if specified, or to all subscribed destination profiles. You must specify the module or port whose diagnostic information should be sent. If a virtual switching system (VSS) is used, you must specify the switch and module. Sends an inventory alert group message to one destination profile if specified, or to all subscribed destination profiles.
Step 2 Router# call-home send alert-group diagnostic

{module number | slot/subslot | slot/bay_number | switch x module number} [profile name]
Step 3 Router# call-home send alert-group inventory

[profile name]
When manually sending Call Home alert group messages, note the following guidelines:

Only the configuration, diagnostic, and inventory alert groups can be sent manually. When you manually trigger a configuration, diagnostic, or inventory alert group message and you specify a destination profile name, a message is sent to the destination profile regardless of the profiles active status, subscription status, or severity setting. When you manually trigger a configuration or inventory alert group message and do not specify a destination profile name, a message is sent to all active profiles that have either a normal or periodic subscription to the specified alert group. When you manually trigger a diagnostic alert group message and do not specify a destination profile name, the command will cause the following actions:
For any active profile that subscribes to diagnostic events with a severity level of less than
minor, a message is sent regardless of whether the module or interface has observed a diagnostic event.
62-17
For any active profile that subscribes to diagnostic events with a severity level of minor or
higher, a message is sent only if the specified module or interface has observed a diagnostic event of at least the subscribed severity level; otherwise, no diagnostic message is sent to the destination profile.
Sending a Request for an Analysis and Report

Release 12.2(33)SXI and later releases support Call Home requests. You can use the call-home request command to submit information about your system to Cisco in order to receive helpful information specific to your system. You can request a variety of reports, including security alerts, known bugs, best practices, and command references. To submit a request for report and analysis information from the Cisco Output Interpreter tool, perform this task: Command
Step 1 Router# call-home request output-analysis "show-command" [profile name] [ccoid user-id]
Purpose Sends the output of the specified show command for analysis. The show command must be contained in quotes (). Sends the output of a predetermined set of commands such as the show running-config all, show version, and show module (standalone) or show module switch all (VS system) commands, for analysis. Specifies the type of report requested.
Step 2 Router# call-home request {config-sanity |

bugs-list | command-reference | product-advisory} [profile name] [ccoid user-id]
When manually sending a Call Home report and analysis request, note the following guidelines:
If a profile name is specified, the request will be sent to the profile. If no profile is specified, the request will be sent to the Cisco TAC profile. The recipient profile does not need to be enabled for the call-home request. The profile should specify the email address where the transport gateway is configured so that the request message can be forwarded to the Cisco TAC and the user can receive the reply from the Smart Call Home service. The ccoid user-id is the registered identifier of the Smart Call Home user. If the user-id is specified, the response will be sent to the email address of the registered user. If no user-id is specified, the response will be sent to the contact email address of the device. Based on the keyword specifying the type of report requested, the following information will be returned:
config-sanityInformation on best practices as related to the current running configuration. bugs-listKnown bugs in the running version and in the currently applied features. command-referenceReference links to all commands in the running configuration. product-advisoryProduct Security Incident Response Team (PSIRT) notices, End of Life
(EOL) or End of Sales (EOS) notices, or field notices (FN) that may affect devices in your network. This example shows a request for analysis of a user-specified show command:
Router# call-home request output-analysis "show diagnostic result module all" profile TG
62-18
OL-13013-06
Chapter 62
Sending the Output of a Command

You can use the call-home send command to execute a CLI command and email the command output to Cisco or to an email address that you specify. To execute a CLI command and email the command output, perform this task: Command
Router# call-home send "command" [email email-addr] [tac-service-request SR]
Purpose Executes the specified CLI command and emails the output.
When sending the output of a command, note the following guidelines:

The specified CLI command can be any run command, including commands for all modules. The command must be contained in quotes (). If an email address is specified, the command output will be sent to that address. If no email address is specified, the output will be sent to the Cisco TAC (attach@cisco.com). The email will be sent in long text format with the service number, if specified, in the subject line. The service number is required only if no email address is specified, or if a Cisco TAC email address is specified.
This example shows how to send the output of a CLI command to a user-specified email address:
Router# call-home send "show diagnostic result module all" email support@example.com
Configuring and Enabling Smart Call Home

For application and configuration information of the Cisco Smart Call Home service, see the Quick Start for Smart Call Home section in Chapter 1 of the Smart Call Home User Guide: http://www.cisco.com/en/US/docs/switches/lan/smart_call_home/book.html The user guide includes configuration examples for sending Smart Call Home messages directly from your device or through a transport gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices may not be connected directly to the Internet. Because the Smart Call Home service uses HTTPS as the transport method, you must also configure its CA as a trustpoint, as described in the Smart Call Home User Guide.
62-19
Chapter 62 Configuring the Smart Call Home Service
Configuring the Smart Call Home Service

Tip
From the Smart Call Home website, you can download a basic configuration script to assist you in the configuration of the Call Home feature for use with Smart Call Home service and the Cisco TAC. The script also assists in configuring the trustpoint CA for secure communications with the Smart Call Home service. The script, provided on an as-is basis, can be downloaded from a link under the Smart Call Home Resources heading at: http://www.cisco.com/en/US/products/ps7334/serv_home.html This section provides an overview of the minimum steps required to configure the Call Home feature on a Cisco device, and other required supporting configuration to communicate securely with the Smart Call Home service using HTTPS:

Enabling the Smart Call Home Service, page 62-20 Declare and Authenticate a CA Trustpoint, page 62-21 Start Smart Call Home Registration, page 62-22
Enabling the Smart Call Home Service

Note
Before you start to configure the Smart Call Home Service, be sure that you have completed the following prerequisites:

Verify that you have an active Cisco Systems service contract for the device being configured. Verify that you have IP connectivity to the Cisco HTTPS server. Obtain the latest Cisco Systems server security certificate.
The CiscoTAC-1 profile is predefined in the Call Home feature to communicate using email to the backend server for the Smart Call Home service. The URL to the Cisco HTTPS backend server is also predefined. This profile is inactive by default. Unlike other profiles that you can configure in Call Home to support both transport methods, the CiscoTAC-1 profile can only use one transport method at a time. To use this profile with the Cisco Smart Call Home HTTPS server, you must change the transport method from email to HTTP and enable the profile. In addition, you must minimally specify a contact email address and enable the Call Home feature. To enable the Smart Call Home service, perform this task: Command or Action
Router# configure terminal Router(config)# call-home Router(config-call-home)# profile CiscoTAC-1
Purpose Enters global configuration mode. Enters call home configuration mode. Enters call home destination profile configuration mode for the CiscoTAC-1 destination profile. (Required for HTTPS) Configures the message transport method for http. Enables the destination profile.
Router(cfg-call-home-profile)# destination transport-method http Router(cfg-call-home-profile)# active
62-20
OL-13013-06
Chapter 62
Configuring Call Home Configuring the Smart Call Home Service
Command or Action
Purpose Exits call home destination profile configuration mode and returns to call home configuration mode. Assigns the customers email address. Enter up to 200 characters in email address format with no spaces. Exits call home configuration mode and returns to global configuration mode. Enables the Call Home feature. Exits global configuration mode and returns to privileged EXEC mode. Saves the configuration.
Router(cfg-call-home)# contact-email-addr customer_email_address Router(cfg-call-home)# exit
Router(config)# service call-home Router(config)# exit
This example shows how to enable the Smart Call Home service:
Router(cfg-call-home-profile)# destination transport-method http Router(cfg-call-home-profile)# active Router(cfg-call-home-profile)# exit Router(cfg-call-home)# contact-email-addr username@example.com Router(cfg-call-home)# exit Router(config)# service call-home Router(config)# exit Router# copy running-config startup-config
Declare and Authenticate a CA Trustpoint

To declare and authenticate the Cisco server security certificate and establish communication with the Cisco HTTPS server for Smart Call Home service, perform this task: Command or Action
Router# configure terminal Router(config)# crypto pki trustpoint trustpoint_name Router(ca-trustpoint)# enrollment terminal
Purpose Enters global configuration mode. Declares a CA trustpoint on your router and enters CA trustpoint configuration mode. Specifies a manual cut-and-paste method of certificate enrollment. Exits CA trustpoint configuration mode and returns to global configuration mode. Authenticates the named CA. The CA name should match the trustpoint_name specified in the crypto pki trustpoint command. At the prompt, paste the security certificate text. Specifies the end of the security certificate text. Confirms acceptance of the entered security certificate. Exits global configuration mode and returns to privileged EXEC mode. Saves the configuration.
Router(ca-trustpoint)# exit
Router(config)# crypto pki authenticate trustpoint_name Enter the base 64 encoded CA certificate. End with a blank line or the word "quit" on a line by itself quit % Do you accept this certificate? [yes/no]: yes Router(config)# end
62-21
Chapter 62 Configuring the Smart Call Home Service
The example shows how to declare and authenticate the Cisco server security certificate and establish communication with the Cisco HTTPS server for Smart Call Home service:
Router# configure terminal Router(config)# crypto pki trustpoint cisco Router(ca-trustpoint)# enrollment terminal Router(ca-trustpoint)# exit Router(config)# crypto pki authenticate cisco Enter the base 64 encoded CA certificate. End with a blank line or the word "quit" on a line by itself
(CA certificate text not shown)

quit Certificate has the following attributes: Fingerprint MD5: A2339B4C 747873D4 6CE7C1F3 8DCB5CE9 Fingerprint SHA1: 85371CA6 E550143D CE280347 1BDE3A09 E8F8770F % Do you accept this certificate? [yes/no]: yes Trustpoint CA certificate accepted. % Certificate successfully imported Router(config)# end Router# copy running-config startup-config
Start Smart Call Home Registration

To start the Smart Call Home registration process, perform this task: Command or Action
Router# call-home send alert-group inventory profile CiscoTAC-1
Purpose Manually sends an inventory alert group message to the CiscoTAC-1 destination profile.
After the Smart Call Home service is registered, you will receive an email from Cisco Systems. Follow the instructions in the email. The instructions include these procedures:
To complete the device registration, launch the Smart Call Home web application at the following URL: http://tools.cisco.com/sch/ Accept the Legal Agreement. Confirm device registration for Call Home devices with pending registration.
For more information about using the Smart Call Home web application, see the Smart Call Home User Guide. This user guide also includes configuration examples for sending Smart Call Home messages directly from your device or through a transport gateway (TG) aggregation point. You can use a TG aggregation point in cases requiring support for multiple devices or in cases where security requirements mandate that your devices must not be connected directly to the Internet.
62-22
OL-13013-06
Chapter 62
Configuring Call Home Displaying Call Home Configuration Information
Displaying Call Home Configuration Information

To display the configured Call Home information, perform these tasks: Command
Router# show call-home Router# show call-home detail Router# show call-home alert-group Router# show call-home mail-server status
Purpose Displays the Call Home configuration in summary. Displays the Call Home configuration in detail. Displays the available alert groups and their status. Checks and displays the availability of the configured email server(s). Displays the configuration of the specified destination profile. Use the keyword all to display the configuration of all destination profiles. Displays the statistics of Call Home events.
Router# show call-home profile {all | name}
Router# show call-home statistics
Examples 62-1 to 62-7 show the results when using different options of the show call-home command.
Example 62-1 Configured Call Home Information
Router# show call-home Current call home settings: call home feature : disable call home message's from address: switch@example.com call home message's reply-to address: support@example.com contact person's email address: technical@example.com contact person's phone number: +1-408-555-1234 street address: 1234 Picaboo Street, Any city, Any state, 12345 customer ID: ExampleCorp contract ID: X123456789 site ID: SantaClara Mail-server[1]: Address: smtp.example.com Priority: 1 Mail-server[2]: Address: 192.168.0.1 Priority: 2 Rate-limit: 20 message(s) per minute Available alert groups: Keyword -----------------------configuration diagnostic environment inventory syslog Profiles: Profile Name: campus-noc Profile Name: CiscoTAC-1 Router#
State ------Disable Disable Disable Enable Disable
Description ------------------------------configuration info diagnostic info environmental info inventory info syslog info
62-23
Chapter 62 Displaying Call Home Configuration Information
Example 62-2 Configured Call Home Information in Detail

Router# show call-home detail Current call home settings: call home feature : disable call home message's from address: switch@example.com call home message's reply-to address: support@example.com contact person's email address: technical@example.com contact person's phone number: +1-408-555-1234 street address: 1234 Picaboo Street, Any city, Any state, 12345 customer ID: ExampleCorp contract ID: X123456789 site ID: SantaClara Mail-server[1]: Address: smtp.example.com Priority: 1 Mail-server[2]: Address: 192.168.0.1 Priority: 2 Rate-limit: 20 message(s) per minute Available alert groups: Keyword -----------------------configuration diagnostic environment inventory syslog Profiles: Profile Name: campus-noc Profile status: ACTIVE Preferred Message Format: long-text Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): noc@example.com HTTP address(es): Not yet set up Alert-group -----------------------inventory Syslog-Pattern -----------------------N/A Severity -----------normal Severity -----------N/A
State ------Disable Disable Disable Enable Disable
Profile Name: CiscoTAC-1 Profile status: ACTIVE Preferred Message Format: xml Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): callhome@cisco.com HTTP address(es): https://tools.cisco.com/its/service/oddce/services/DDCEService Periodic configuration info message is scheduled every 1 day of the month at 09:27 Periodic inventory info message is scheduled every 1 day of the month at 09: 12 Alert-group -----------------------diagnostic environment Syslog-Pattern -----------------------.* Router# Severity -----------minor minor Severity -----------major
62-24
OL-13013-06
Chapter 62
Configuring Call Home Displaying Call Home Configuration Information
Example 62-3 Available Call Home Alert Groups

Router# show call-home alert-group Available alert groups: Keyword State ------------------------ ------configuration Disable diagnostic Disable environment Disable inventory Enable syslog Disable Router#
Example 62-4 Email Server Status Information

Router# show call-home mail-server status Please wait. Checking for mail server status ... Translating "smtp.example.com" Mail-server[1]: Address: smtp.example.com Priority: 1 [Not Available] Mail-server[2]: Address: 192.168.0.1 Priority: 2 [Not Available] Router#
Example 62-5 Information for All Destination Profiles (Predefined and User-Defined)
Router# show call-home profile all Profile Name: campus-noc Profile status: ACTIVE Preferred Message Format: long-text Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): noc@example.com HTTP address(es): Not yet set up Alert-group -----------------------inventory Syslog-Pattern -----------------------N/A Severity -----------normal Severity -----------N/A
Profile Name: CiscoTAC-1 Profile status: ACTIVE Preferred Message Format: xml Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): callhome@cisco.com HTTP address(es): https://tools.cisco.com/its/service/oddce/services/DDCEService Periodic configuration info message is scheduled every 1 day of the month at 09:27 Periodic inventory info message is scheduled every 1 day of the month at 09:12 Alert-group -----------------------diagnostic environment Syslog-Pattern -----------------------.* Router# Severity -----------minor minor Severity -----------major
62-25
Chapter 62 Alert Group Trigger Events and Commands
Example 62-6 Information for a User-Defined Destination Profile

Router# show call-home profile campus-noc Profile Name: campus-noc Profile status: ACTIVE Preferred Message Format: long-text Message Size Limit: 3145728 Bytes Transport Method: email Email address(es): noc@example.com HTTP address(es): Not yet set up Alert-group -----------------------inventory Syslog-Pattern -----------------------N/A Router# Severity -----------normal Severity -----------N/A
Example 62-7 Call Home Statistics

Router# show call-home statistics Successful Call-Home Events: 1 Dropped Call-Home Events due to Rate Limiting: 0 Last call-home message sent time: 2007-04-25 11:07:04 GMT+00:00
Alert Group Trigger Events and Commands

Call Home trigger events are grouped into alert groups, with each alert group assigned CLI commands to execute when an event occurs. The CLI command output is included in the transmitted message. These tables list the trigger events included in each alert group, including the severity level of each event and the executed CLI commands for the alert group:

Call Home Syslog Alert Group Events and Actions, Table 62-3 on page 62-27 Call Home Environmental Alert Group Events and Actions, Table 62-4 on page 62-27 Call Home Inventory Alert Group Events and Actions, Table 62-5 on page 62-30 Call Home Diagnostic Failure Alert Group Events and Actions, Table 62-6 on page 62-31 Call Home Test Alert Group Events and Actions, Table 62-7 on page 62-32 Call Home License Alert Group Events and Actions, Table 62-8 on page 62-32 Call Home Configuration Alert Group Events and Actions, Table 62-9 on page 62-33
62-26
OL-13013-06
Chapter 62
Configuring Call Home Alert Group Trigger Events and Commands
Table 62-3
Call Home Syslog Alert Group Events and Actions
Alert Group Description: Send to TAC: Executed Commands: Call Home Trigger Event SYSLOG
Event logged to syslog No show logging, show inventory Syslog Event LOG_EMERG LOG_ALERT LOG_CRIT LOG_ERR LOG_WARNING LOG_NOTICE LOG_INFO LOG_DEBUG Sev 0 1 2 3 4 5 6 7 Description system is unusable action must be taken immediately critical conditions error conditions warning conditions normal but signification condition informational debug-level messages
Table 62-4
Call Home Environmental Alert Group Events and Actions
Alert Group Description: Send to TAC: Executed Commands: Call Home Trigger Event FAN_FAILURE
Events related to power, fan and environment sensing elements such as temperature alarms Yes show module, show environment, show logging, show inventory, show power Syslog Event FANPSINCOMPAT ALARMCLR FANHIOUTPUT FANLOOUTPUT FANVERCHK FANTRAYFAILED FANTRAYOK FANCOUNTFAILED FANCOUNTOK PSFANFAIL PSFANOK Sev Description 4 4 4 4 4 4 4 4 4 4 4 Fan tray and power supply %d are incompatible The specified alarm condition has been cleared, and shutdown has been cancelled. Version %d high-output fan-tray is in effect Version %d low-output fan-tray is in effect Power-supply %d inserted is only compatible with Version %d fan-tray. fan tray failed fan tray OK Required number of fan trays is not present Required number of fan trays is present the fan in power supply has failed the fan in power supply is OK
62-27
Table 62-4
Call Home Environmental Alert Group Events and Actions (continued)
Alert Group Description: Send to TAC: Executed Commands: Call Home Trigger Event TEMPERATURE_ALARM
Events related to power, fan and environment sensing elements such as temperature alarms Yes show module, show environment, show logging, show inventory, show power Syslog Event MAJORTEMPALARM MAJORTEMPALARMRECOVER MINORTEMPALARM MINORTEMPALARMRECOVER Sev Description 2 4 4 4 4 4 0 2 4 4 0 2 2 It has exceeded allowed operating temperature range. It has returned to allowed operating temperature range. It has exceeded normal operating temperature range. It has returned to normal operating temperature range. VTT %d failed. VTT %d operational. Too many VTT failures to continue system operation. Enough VTTs operational to continue system operation. clock failed clock operational too many clocks failed to continue system operation enough clocks operational to continue system operation shutdown for %s scheduled in %d seconds Major sensor alarm for %s is ignored, %s will not be shutdown shutdown for cancelled shutdown %s now because of %s need to shutdown %s now but shutdown action is disabled! System reset scheduled in seconds changing system switching clock cannot detect clock A in the system cannot detect clock B in the system system is using the redundant clock (clock B). power to module in slot %d set on power to module in slot %d set %s power supply %d turned on.
VTT_FAILED
VTTFAILED VTTOK VTTMAJFAILED VTTMAJRECOVERED
CLOCK_FAILED
CLOCKFAILED CLOCKOK CLOCKMAJFAILED CLOCKMAJRECOVERED SHUTDOWN-SCHEDULED
SHUTDOWN_NOT_SCHEDULED 2 SHUTDOWN-CANCELLED SHUTDOWN SHUTDOWN-DISABLED RESET_SCHEDULED CLOCK_SWITCHOVER CLOCK_A_MISSING CLOCK_B_MISSING USE_RED_CLOCK ENABLED DISABLED PSOK 2 2 1 2 2 4 4 4 4 4 4
62-28
OL-13013-06
Chapter 62
Table 62-4
Call Home Environmental Alert Group Events and Actions (continued)
Alert Group Description: Send to TAC: Executed Commands: Call Home Trigger Event
Events related to power, fan and environment sensing elements such as temperature alarms Yes show module, show environment, show logging, show inventory, show power Syslog Event PSREDUNDANTMODE PSCOMBINEDMODE PSREDUNDANTMISMATCH PSMISMATCH PSNOREDUNDANCY PSOCPSHUTDOWN PSREDUNDANTONESUPPLY PSREDUNDANTBOTHSUPPLY UNDERPOWERED COULDNOTREPOWER POWERDENIED UNSUPPORTED INSUFFICIENTPOWER INPUTCHANGE PSINPUTDROP Sev Description 4 4 4 4 4 4 2 4 4 4 4 4 4 2 4 4 power supply %d output failed. power supplies set to redundant mode. power supplies set to combined mode. power supplies rated outputs do not match. power supplies rated outputs do not match. Power supplies are not in full redundancy, power usage exceed lower capacity supply Power usage exceeds power supply %d allowable capacity. in power-redundancy mode, system is operating on one power supply in power-redundancy mode, system is operating on both power supplies insufficient power to operate all FRUs in system. wanted to re-power FRU (slot %d) but could not. insufficient power, module in slot %d power denied. unsupported module in slot %d, power not allowed: %s. Powering down all linecards as there is not enough power to operate all critical cards Power supply %d input has changed. Power capacity adjusted to %sW Power supply %d input has droppe
POWER_SUPPLY_FAILURE PSFAIL
62-29
Table 62-5
Call Home Inventory Alert Group Events and Actions
Alert Group Description:
Inventory status should be provided whenever a unit is cold-booted, or when FRUs are inserted or removed. This is considered a non-critical event, and the information is used for status and entitlement. Yes show module, show version, show install running (software modularity images only), show inventory oid, show idprom all, remote command switch show version, show diagbus, show power Syslog Event INSPS REMPS REMCARD STDBY_REMCARD Sev Description 6 6 6 6 Power supply inserted in slot %d Power supply removed from slot %d Card removed from slot %d, interfaces disabled The OIR facility on Standby Supervior was notifed by the Active that a processor from slot[n] has been removed Card inserted in slot %d, interfaces are now online Standby was notified, card online in slot %d SCP seq mismatch for card in slot %d : %s Unknown card in slot %d, card is being disabled Standby was notified, Unknown card in slot %d Card in slot %d is unsupported. %s Card in module %d, is being power-cycled %s Standby was notified, Card in module %d is being power-cycled %s Changing console ownership to %s processor During switchover, the OIR facility is unable to clean up running-config processor. Supervisor attempting to come up as secondary in EHSA mode, will not be allowed Fan %d removed Fan %d inserted power supply inserted in slot %d.
Send to TAC: Executed Commands:
Call Home Trigger Event HARDWARE_INSERTION HARDWARE_REMOVAL
HARDWARE_INSERTION
INSCAR STDBY_INSCARD SEQ_MISMATCH
6 6 6 3 3 3 3 3 6 6 6 6 6 4
HARDWARE_REMOVAL
UNKNOWN STDBY_UNKNOWN UNSUPPORTED PWRCYCLE STDBY_PWRCYCLE CONSOLE RUNNING_CONFIG DISALLOW REMFAN
HARDWARE_INSERTION
INSFAN PSINSERTED
62-30
OL-13013-06
Chapter 62
Table 62-6
Call Home Diagnostic Failure Alert Group Events and Actions
Alert Group Description: Send to TAC: Executed Commands:
Events related to standard or intelligent line cards Yes show module, show diagnostic result Module <#> detail, show version, show install running (software modularity images only), show inventory, show buffers, show logging, show diagnostic result module all, remote command switch show version, show logging system last 100 DIAGNOSTICS_FAILURE Sev Description 2 2 2 2 2 2 4 6 6 3 3 3 6 The constellation 2 plus module in slot %d has no forwarding daughter board. Power denied Module %d DFC incompatible with Supervisor DFC. Power denied Module %d not at an appropriate hardware revision level to support DFC. Power denied WARNING: Module %d not at an appropriate hardware revision level to support DFC3 Module %d not at an appropriate hardware revision level to coexist with PFC3 system. Power denied Module %d not supported without fan upgrade Module %d cannot be adequately cooled Module %d does not meet the provisioning requirements, power denied Module %d is being disabled due to power convertor failure Module %d has Major online diagnostic failure, %s Module %d is being hard reset as a part of swichover error recovery Module %d is being soft reset as a part of swichover error recovery Fabric capable module %d not at an appropriate hardware revision level, and can only run in flowthrough mode
Call Home Trigger Event:
Syslog Event C2PLUSWITHNODB DFCMISMATCH BADFLOWCTRL BADFLOWCTRL_WARN BADPINN1 FANUPGREQ INSUFFCOO PROVISION PWRFAILURE LC_FAILURE HARD_RESET SOFT_RESET DOWNGRADE DIAG_OK DIAG_BYPASS DIAG_ERROR DIAG_MINOR_ERROR DIAG_MAJOR_ERROR DIAG_LINE_CARD_NOT_PRESENT DIAG_LINE_CARD_REMOVED DIAG_INVALID_TEST_ID_RANGE DIAG_INVALID_PORT_RANGE DIAG_IS_BUSY DIAG_IS_IDLE DIAG_NO_SCHEDULE DIAG_SCHEDULE_EXIST
62-31
Table 62-6
Call Home Diagnostic Failure Alert Group Events and Actions (continued)
Alert Group Description: Send to TAC: Executed Commands:
Events related to standard or intelligent line cards Yes show module, show diagnostic result Module <#> detail, show version, show install running (software modularity images only), show inventory, show buffers, show logging, show diagnostic result module all, remote command switch show version, show logging system last 100 DIAGNOSTICS_FAILURE Sev Description
Call Home Trigger Event:
Syslog Event DIAG_NO_TEST DIAG_UNKNOWN DIAG_NOT_AVAILABLE DIAG_EXIT_ON_ERROR DIAG_EXIT_ON_FAIL_LIMIT_REACHED DIAG_INVALID_SCHEDULE DIAG_PF_DIAG_NOT_SUPORTED DIAG_IS_STOPPED DIAG_INVALID_DEVICE_RANGE
Table 62-7
Call Home Test Alert Group Events and Actions
Alert Group Description: Send to TAC: Executed Commands: Call Home Trigger Event:
Yes show version, show module, show inventory, test message Sev Description 2 User-generated test message.
Syslog Event TEST
Table 62-8
Call Home License Alert Group Events and Actions
For future use. Yes show license all, show running-config Sev Description Events related to unlicensed use of licensed features, or inconsistent license information.
Syslog Event
62-32
OL-13013-06
Chapter 62
Configuring Call Home Message Contents
Table 62-9
Call Home Configuration Alert Group Events and Actions
User generated request for configuration. Yes show module, show version, show install running (software modularity images only), show running-config all, show startup-config, show inventory, remote command switch show version Sev Description
Syslog Event
Message Contents
The following tables display the content formats of alert group messages:

Table 62-10 describes the content fields of a short text message. Table 62-11 describes the content fields that are common to all long text and XML messages. The fields specific to a particular alert group message are inserted after the common fields. Table 62-12 describes the content fields for reactive messages (system failures that require a TAC case) and proactive messages (issues that might result in degraded system performance). Table 62-13 describes the content fields for an inventory message.
Format for a Short Text Message
Table 62-10
Data Item Device identification Date/time stamp Error isolation message Alarm urgency level
Description Configured device name Time stamp of the triggering event Plain English description of triggering event Error level such as that applied to a system message
Table 62-11
Common Fields for All Long Text and XML Messages
Data Item Description (Plain Text and XML) (Plain Text and XML) Time stamp Date and time stamp of event in ISO time notation: YYYY-MM-DDTHH:MM:SS Message name
XML Tag (XML Only) CallHome/EventTime
Name of message. Specific event names (for short text message only) are listed in the Alert Group Trigger Events and Commands section on page 62-26. Specifically Call Home. CallHome/Event/Type Specific type of message: full, delta, or CallHome/Event/SubType test.
Message type Message subtype
62-33
Chapter 62 Message Contents
Table 62-11
Common Fields for All Long Text and XML Messages (continued)
Data Item Description (Plain Text and XML) (Plain Text and XML) Message group Severity level Source ID Device ID Specifically reactive or proactive. Severity level of message (see Table 62-2 on page 62-16). Product type for routing. Specifically Catalyst 6500. Unique device identifier (UDI) for end device generating message. This field should be empty if the message is nonspecific to a fabric switch. The format is type@Sid@serial.

XML Tag (XML Only) (for long text message only) Body/Block/Severity (for long text message only) CallHome/CustomerData/ContractData/DeviceId
type is the product model number from backplane IDPROM. @ is a separator character. Sid is C, identifying the serial ID as a chassis serial number serial is the number identified by the Sid field. CallHome/CustomerData/ContractData/CustomerId
Example: WS-C6509@C@12345678 Customer ID Optional user-configurable field used for contract information or other ID by any support service. Optional user-configurable field used for contract information or other ID by any support service.
Contract ID
CallHome/CustomerData/ContractData/ContractId
Site ID
Optional user-configurable field used CallHome/CustomerData/ContractData/SiteId for Cisco-supplied site ID or other data meaningful to alternate support service. If the message is generated from the fabric switch, this is the unique device identifier (UDI) of the switch. The format is type@Sid@serial.

Server ID
(for long text message only)
type is the product model number from backplane IDPROM. @ is a separator character. Sid is C, identifying the serial ID as a chassis serial number serial is the number identified by the Sid field. CallHome/MessageDescription
Example: WS-C6509@C@12345678 Message description Short text describing the error.
62-34
OL-13013-06
Chapter 62
Table 62-11
Common Fields for All Long Text and XML Messages (continued)
Data Item Description (Plain Text and XML) (Plain Text and XML) Device name Contact name
XML Tag (XML Only)
Node that experienced the event. This is CallHome/CustomerData/SystemInfo/Name the host name of the device. Name of person to contact for issues associated with the node experiencing the event. Email address of person identified as contact for this unit. Phone number of the person identified as the contact for this unit. CallHome/CustomerData/SystemInfo/Contact
Contact email Contact phone number Street address
CallHome/CustomerData/SystemInfo/ContactEmail CallHome/CustomerData/SystemInfo/ContactPhoneNumber
Optional field containing street address CallHome/CustomerData/SystemInfo/StreetAddress for RMA part shipments associated with this unit. Model name of the switch. This is the specific model as part of a product family name. Chassis serial number of the unit. CallHome/Device/Cisco_Chassis/Model
Model name
Serial number
CallHome/Device/Cisco_Chassis/SerialNumber CallHome/Device/Cisco_Chassis/AdditionalInformation/ AD@name="PartNumber"/ CallHome/Device/Cisco_Chassis/AdditionalInformation/ AD@name="sysObjectID" CallHome/Device/Cisco_Chassis/AdditionalInformation/ AD@name="sysDescr" /aml/Attachments/Attachment/Name /aml/Attachments/Attachment@type /aml/attachments/attachment/Data@encoding /aml/attachments/attachment/atdata
Chassis part number Top assembly number of the chassis. System Object ID SysDesc The System ObjectID that uniquely identifies the system. System description for the managed element.
The following fields may be repeated if multiple CLI commands are executed for this alert group. Command output name Attachment type MIME type Command output text The exact name of the issued CLI command. Type (usually inline). Normally text/plain or encoding type. Output of command automatically executed (see the Alert Group Trigger Events and Commands section on page 62-26).
Table 62-12
Fields for a Reactive or Proactive Event Message
Data Item Description (Plain Text and XML) (Plain Text and XML) Chassis hardware version Supervisor module software version Hardware version of chassis. Top-level software version.
XML Tag (XML Only) CallHome/Device/Cisco_Chassis/HardwareVersion CallHome/Device/Cisco_Chassis/AdditionalInformation/ AD@name="SoftwareVersion"
62-35
Table 62-12
Fields for a Reactive or Proactive Event Message (continued)
Data Item Description (Plain Text and XML) (Plain Text and XML) Affected FRU name Name of the affected FRU generating the event message. Affected FRU serial Serial number of number affected FRU. Affected FRU part number FRU slot Part number of affected FRU. Slot number of FRU generating the event message. Hardware version of affected FRU. Software version(s) running on affected FRU. Name of process. Unique process ID. State of process (for example, running or halted). Exception or reason code.
XML Tag (XML Only) CallHome/Device/Cisco_Chassis/Cisco_Card/Model
CallHome/Device/Cisco_Chassis/Cisco_Card/SerialNumber CallHome/Device/Cisco_Chassis/Cisco_Card/PartNumber CallHome/Device/Cisco_Chassis/Cisco_Card/ LocationWithinContainer CallHome/Device/Cisco_Chassis/Cisco_Card/HardwareVersion CallHome/Device/Cisco_Chassis/Cisco_Card/SoftwareIdentity/VersionString
FRU hardware version FRU software version Process name Process ID Process state
/aml/body/process/name /aml/body/process/id /aml/body/process/processState
Process exception
/aml/body/process/exception
Table 62-13
Fields for an Inventory Event Message
Data Item Description XML Tag (Plain Text and XML) (Plain Text and XML) (XML Only) Chassis hardware version Supervisor module software version FRU name Hardware version of CallHome/Device/Cisco_Chassis/HardwareVersion chassis. Top-level software version. CallHome/Device/Cisco_Chassis/AdditionalInformation/AD@name="Softwar eVersion"
Name of the affected CallHome/Device/Cisco_Chassis/Cisco_Card/Model FRU generating the event message. Serial number of FRU. CallHome/Device/Cisco_Chassis/Cisco_Card/SerialNumber
FRU s/n FRU part number FRU slot
Part number of FRU. CallHome/Device/Cisco_Chassis/Cisco_Card/PartNumber Slot number of FRU. CallHome/Device/Cisco_Chassis/Cisco_Card/LocationWithinContainer
62-36
OL-13013-06
Chapter 62
Table 62-13
Fields for an Inventory Event Message (continued)
Data Item Description XML Tag (Plain Text and XML) (Plain Text and XML) (XML Only) FRU hardware version FRU software version Hardware version of CallHome/Device/Cisco_Chassis/Cisco_Card/HardwareVersion FRU. Software version(s) running on FRU. CallHome/Device/Cisco_Chassis/Cisco_Card/SoftwareIdentity/VersionString
Sample Syslog Alert Notification in Long-Text Format

source:MDS9000 Switch Priority:7 Device Id:WS-C6509@C@FG@07120011 Customer Id:Example.com Contract Id:123 Site Id:San Jose Server Id:WS-C6509@C@FG@07120011 Time of Event:2004-10-08T11:10:44 Message Name:SYSLOG_ALERT Message Type:Syslog Severity Level:2 System Name:10.76.100.177 Contact Name:User Name Contact Email:admin@yourcompany.com Contact Phone:+1 408 555-1212 Street Address:#1234 Picaboo Street, Any city, Any state, 12345 Event Description:2006 Oct 8 11:10:44 10.76.100.177 %PORT-5-IF_TRUNK_UP: %$VSAN 1%$ Interface fc2/5, vsan 1 is up syslog_facility:PORT start chassis information: Affected Chassis:WS-C6509 Affected Chassis Serial Number:FG@07120011 Affected Chassis Hardware Version:0.104 Affected Chassis Software Version:3.1(1) Affected Chassis Part No:73-8607-01 end chassis information:
Sample Syslog Alert Notification in XML Format

From: example Sent: Wednesday, April 25, 2007 7:20 AM To: User (user) Subject: System Notification From Router - syslog - 2007-04-25 14:19:55 GMT+00:00 <?xml version="1.0" encoding="UTF-8"?> <soap-env:Envelope xmlns:soap-env="http://www.w3.org/2003/05/soap-envelope"> <soap-env:Header> <aml-session:Session xmlns:aml-session="http://www.example.com/2004/01/aml-session" soap-env:mustUnderstand="true" soap-env:role="http://www.w3.org/2003/05/soap-envelope/role/next"> <aml-session:To>http://tools.example.com/services/DDCEService</aml-session:To> <aml-session:Path> <aml-session:Via>http://www.example.com/appliance/uri</aml-session:Via>
62-37
</aml-session:Path> <aml-session:From>http://www.example.com/appliance/uri</aml-session:From> <aml-session:MessageId>M2:69000101:C9D9E20B</aml-session:MessageId> </aml-session:Session> </soap-env:Header> <soap-env:Body> <aml-block:Block xmlns:aml-block="http://www.example.com/2004/01/aml-block"> <aml-block:Header> <aml-block:Type>http://www.example.com/2005/05/callhome/syslog</aml-block:Type> <aml-block:CreationDate>2007-04-25 14:19:55 GMT+00:00</aml-block:CreationDate> <aml-block:Builder> <aml-block:Name>Cat6500</aml-block:Name> <aml-block:Version>2.0</aml-block:Version> </aml-block:Builder> <aml-block:BlockGroup> <aml-block:GroupId>G3:69000101:C9F9E20C</aml-block:GroupId> <aml-block:Number>0</aml-block:Number> <aml-block:IsLast>true</aml-block:IsLast> <aml-block:IsPrimary>true</aml-block:IsPrimary> <aml-block:WaitForPrimary>false</aml-block:WaitForPrimary> </aml-block:BlockGroup> <aml-block:Severity>2</aml-block:Severity> </aml-block:Header> <aml-block:Content> <ch:CallHome xmlns:ch="http://www.example.com/2005/05/callhome" version="1.0"> <ch:EventTime>2007-04-25 14:19:55 GMT+00:00</ch:EventTime> <ch:MessageDescription>03:29:29: %CLEAR-5-COUNTERS: Clear counter on all interfaces by console</ch:MessageDescription> <ch:Event> <ch:Type>syslog</ch:Type> <ch:SubType></ch:SubType> <ch:Brand>Cisco Systems</ch:Brand> <ch:Series>Catalyst 6500 Series Switches</ch:Series> </ch:Event> <ch:CustomerData> <ch:UserData> <ch:Email>user@example.com</ch:Email> </ch:UserData> <ch:ContractData> <ch:CustomerId>12345</ch:CustomerId> <ch:SiteId>building 1</ch:SiteId> <ch:ContractId>abcdefg12345</ch:ContractId> <ch:DeviceId>WS-C6509@C@69000101</ch:DeviceId> </ch:ContractData> <ch:SystemInfo> <ch:Name>Router</ch:Name> <ch:Contact></ch:Contact> <ch:ContactEmail>user@example.com</ch:ContactEmail> <ch:ContactPhoneNumber>+1 408 555-1212</ch:ContactPhoneNumber> <ch:StreetAddress>270 E. Tasman Drive, San Jose, CA</ch:StreetAddress> </ch:SystemInfo> </ch:CustomerData> <ch:Device> <rme:Chassis xmlns:rme="http://www.example.com/rme/4.0"> <rme:Model>WS-C6509</rme:Model> <rme:HardwareVersion>1.0</rme:HardwareVersion> <rme:SerialNumber>69000101</rme:SerialNumber> <rme:AdditionalInformation> <rme:AD name="PartNumber" value="73-3438-03 01" /> <rme:AD name="SoftwareVersion" value="12.2(20070421:012711)" /> </rme:AdditionalInformation> </rme:Chassis> </ch:Device> </ch:CallHome>
62-38
OL-13013-06
Chapter 62
</aml-block:Content> <aml-block:Attachments> <aml-block:Attachment type="inline"> <aml-block:Name>show logging</aml-block:Name> <aml-block:Data encoding="plain"> <![CDATA[ Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes, 0 overruns, xml disabled, filtering disabled) Console logging: level debugging, 53 messages logged, xml disabled, filtering disabled Monitor logging: level debugging, 0 messages logged, xml disabled, filtering disabled Buffer logging: level debugging, 53 messages logged, xml disabled, filtering disabled Exception Logging: size (4096 bytes) Count and timestamp logging messages: disabled Trap logging: level informational, 72 message lines logged Log Buffer (8192 bytes): 00:00:54: curr is 0x20000 00:00:54: RP: Currently running ROMMON from F2 region 00:01:05: %SYS-5-CONFIG_I: Configured from memory by console 00:01:09: %SYS-5-RESTART: System restarted -Cisco IOS Software, s72033_rp Software (s72033_rp-ADVENTERPRISEK9_DBG-VM), Experimental Version 12.2(20070421:012711) Copyright (c) 1986-2007 by Cisco Systems, Inc. Compiled Thu 26-Apr-07 15:54 by xxx Firmware compiled 11-Apr-07 03:34 by integ Build [100]
00:01:01: %PFREDUN-6-ACTIVE: Initializing as ACTIVE processor for this switch 00:01:01: %SYS-3-LOGGER_FLUSHED: System was paused for 00:00:00 to ensure console debugging output. 00:03:00: SP: SP: Currently running ROMMON from F1 region 00:03:07: %C6K_PLATFORM-SP-4-CONFREG_BREAK_ENABLED: The default factory setting for config register is 0x2102.It is advisable to retain 1 in 0x2102 as it prevents returning to ROMMON when break is issued. 00:03:18: %SYS-SP-5-RESTART: System restarted -Cisco IOS Software, s72033_sp Software (s72033_sp-ADVENTERPRISEK9_DBG-VM), Experimental Version 12.2(20070421:012711) Copyright (c) 1986-2007 by Cisco Systems, Inc. Compiled Thu 26-Apr-07 18:00 by xxx 00:03:18: %SYS-SP-6-BOOTTIME: Time taken to reboot after reload = 339 seconds 00:03:18: %OIR-SP-6-INSPS: Power supply inserted in slot 1 00:03:18: %C6KPWR-SP-4-PSOK: power supply 1 turned on. 00:03:18: %OIR-SP-6-INSPS: Power supply inserted in slot 2 00:01:09: %SSH-5-ENABLED: SSH 1.99 has been enabled 00:03:18: %C6KPWR-SP-4-PSOK: power supply 2 turned on. 00:03:18: %C6KPWR-SP-4-PSREDUNDANTMISMATCH: power supplies rated outputs do not match. 00:03:18: %C6KPWR-SP-4-PSREDUNDANTBOTHSUPPLY: in power-redundancy mode, system is operating on both power supplies. 00:01:10: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF 00:01:10: %CRYPTO-6-ISAKMP_ON_OFF: ISAKMP is OFF 00:03:20: %C6KENV-SP-4-FANHIOUTPUT: Version 2 high-output fan-tray is in effect 00:03:22: %C6KPWR-SP-4-PSNOREDUNDANCY: Power supplies are not in full redundancy, power usage exceeds lower capacity supply 00:03:26: %FABRIC-SP-5-FABRIC_MODULE_ACTIVE: The Switch Fabric Module in slot 6 became active.
62-39
00:03:28: %DIAG-SP-6-RUN_MINIMUM: Module 6: Running Minimal Diagnostics... 00:03:50: %DIAG-SP-6-DIAG_OK: Module 6: Passed Online Diagnostics 00:03:50: %OIR-SP-6-INSCARD: Card inserted in slot 6, interfaces are now online 00:03:51: %DIAG-SP-6-RUN_MINIMUM: Module 3: Running Minimal Diagnostics... 00:03:51: %DIAG-SP-6-RUN_MINIMUM: Module 7: Running Minimal Diagnostics... 00:03:51: %DIAG-SP-6-RUN_MINIMUM: Module 9: Running Minimal Diagnostics... 00:01:51: %MFIB_CONST_RP-6-REPLICATION_MODE_CHANGE: Replication Mode Change Detected. Current system replication mode is Ingress 00:04:01: %DIAG-SP-6-DIAG_OK: Module 3: Passed Online Diagnostics 00:04:01: %OIR-SP-6-DOWNGRADE: Fabric capable module 3 not at an appropriate hardware revision level, and can only run in flowthrough mode 00:04:02: %OIR-SP-6-INSCARD: Card inserted in slot 3, interfaces are now online 00:04:11: %DIAG-SP-6-DIAG_OK: Module 7: Passed Online Diagnostics 00:04:14: %OIR-SP-6-INSCARD: Card inserted in slot 7, interfaces are now online 00:04:35: %DIAG-SP-6-DIAG_OK: Module 9: Passed Online Diagnostics 00:04:37: %OIR-SP-6-INSCARD: Card inserted in slot 9, interfaces are now online 00:00:09: DaughterBoard (Distributed Forwarding Card 3) Firmware compiled 11-Apr-07 03:34 by integ Build [100]
00:00:22: %SYS-DFC4-5-RESTART: System restarted -Cisco IOS Software, c6lc2 Software (c6lc2-SPDBG-VM), Experimental Version 12.2(20070421:012711) Copyright (c) 1986-2007 by Cisco Systems, Inc. Compiled Thu 26-Apr-07 17:20 by xxx 00:00:23: DFC4: Currently running ROMMON from F2 region 00:00:25: %SYS-DFC2-5-RESTART: System restarted -Cisco IOS Software, c6slc Software (c6slc-SPDBG-VM), Experimental Version 12.2(20070421:012711) Copyright (c) 1986-2007 by Cisco Systems, Inc. Compiled Thu 26-Apr-07 16:40 by username1 00:00:26: DFC2: Currently running ROMMON from F2 region 00:04:56: %DIAG-SP-6-RUN_MINIMUM: Module 4: Running Minimal Diagnostics... 00:00:09: DaughterBoard (Distributed Forwarding Card 3) Firmware compiled 11-Apr-07 03:34 by integ Build [100] slot_id is 8 00:00:31: %FLASHFS_HES-DFC8-3-BADCARD: /bootflash:: The flash card seems to be corrupted 00:00:31: %SYS-DFC8-5-RESTART: System restarted -Cisco IOS Software, c6lc2 Software (c6lc2-SPDBG-VM), Experimental Version 12.2(20070421:012711) Copyright (c) 1986-2007 by Cisco Systems, Inc. Compiled Thu 26-Apr-07 17:20 by username1 00:00:31: DFC8: Currently running ROMMON from S (Gold) region 00:04:59: %DIAG-SP-6-RUN_MINIMUM: Module 2: Running Minimal Diagnostics... 00:05:12: %DIAG-SP-6-RUN_MINIMUM: Module 8: Running Minimal Diagnostics... 00:05:13: %DIAG-SP-6-RUN_MINIMUM: Module 1: Running Minimal Diagnostics... 00:00:24: %SYS-DFC1-5-RESTART: System restarted -Cisco IOS Software, c6slc Software (c6slc-SPDBG-VM), Experimental Version 12.2(20070421:012711) Copyright (c) 1986-2007 by Cisco Systems, Inc. Compiled Thu 26-Apr-07 16:40 by username1 00:00:25: DFC1: Currently running ROMMON from F2 region 00:05:30: %DIAG-SP-6-DIAG_OK: Module 4: Passed Online Diagnostics 00:05:31: %SPAN-SP-6-SPAN_EGRESS_REPLICATION_MODE_CHANGE: Span Egress HW Replication Mode Change Detected. Current replication mode for unused asic session 0 is Centralized 00:05:31: %SPAN-SP-6-SPAN_EGRESS_REPLICATION_MODE_CHANGE: Span Egress HW Replication Mode Change Detected. Current replication mode for unused asic session 1 is Centralized 00:05:31: %OIR-SP-6-INSCARD: Card inserted in slot 4, interfaces are now online 00:06:02: %DIAG-SP-6-DIAG_OK: Module 1: Passed Online Diagnostics 00:06:03: %OIR-SP-6-INSCARD: Card inserted in slot 1, interfaces are now online
62-40
OL-13013-06
Chapter 62
00:06:31: %DIAG-SP-6-DIAG_OK: Module 2: Passed Online Diagnostics 00:06:33: %OIR-SP-6-INSCARD: Card inserted in slot 2, interfaces are now online 00:04:30: %XDR-6-XDRIPCNOTIFY: Message not sent to slot 4/0 (4) because of IPC error timeout. Disabling linecard. (Expected during linecard OIR) 00:06:59: %DIAG-SP-6-DIAG_OK: Module 8: Passed Online Diagnostics 00:06:59: %OIR-SP-6-DOWNGRADE_EARL: Module 8 DFC installed is not identical to system PFC and will perform at current system operating mode. 00:07:06: %OIR-SP-6-INSCARD: Card inserted in slot 8, interfaces are now online Router#]]></aml-block:Data> </aml-block:Attachment> </aml-block:Attachments> </aml-block:Block> </soap-env:Body> </soap-env:Envelope>
Tip
62-41
62-42
OL-13013-06
C H A P T E R
63

This chapter describes how to use the System Event Archive (SEA). Release 12.2(33)SXH and later releases support the SEA.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html SEA is supported with Supervisor Engine 32, Supervisor Engine 720-10GE, and Supervisor Engine 720 with a CompactFlash adapter and a CompactFlash card (WS-CF-UPG=).
Tip

Understanding the System Event Archive, page 63-1 Displaying the SEA Logging System, page 63-2 Copying the SEA To Another Device, page 63-3
Understanding the System Event Archive

The primary method of discovering the cause of system failure is system messages. When system messages do not provide the information needed to determine the cause of a failure, you can enable debug traces and attempt to recreate the failure. However, there are several situations in which neither of the above methods provides an optimum solution:

Reviewing a large number of system messages can be an inefficient method of determing the cause of a failure. Debug trace is usually not configured by default. You cannot recreate the failure while using debug trace.
63-1
Chapter 63 Displaying the SEA Logging System
Using debug trace is not an option if the switch on which the failure has occurred is part of your critical network.
The SEA enables each of the CPUs on a switch to report events to the management processor using an out-of-band interface. Each event is logged in nonvolatile memory with a time stamp. You can retrieve the event log by accessing the bootflash on the device, or you can copy the log to another location such as a removable storage device. The SEA maintains two files in the bootdisk, using up to 32 MB. These files contain the most recent messages recorded to the log:

sea_log.datApplications store the most recent system events in this file. sea_console.datThe most recent console messages are stored in this file.
These files are for system use and should not be removed.
Displaying the SEA Logging System

To display the SEA logging system, perform this task: Command
Router# show logging system [disk | size]
Purpose Displays the contents of the SEA. (Optional) Use the keyword disk to display the location where the SEA is stored. Use the keyword size to display the current size of the SEA.
Router# clear logging system
Removes the event records stored in the SEA.
The following example shows how to display the SEA:

Router# show logging system SEQ: MM/DD/YY HH:MM:SS MOD/SUB: SEV, COMP, MESSAGE ===================================================== 1: 01/24/07 15:38:40 2: 01/24/07 15:38:40 3: 01/24/07 15:38:40 4: 01/24/07 15:38:40 5: 01/24/07 15:38:40 6: 01/24/07 15:38:40 7: 01/24/07 15:38:39 6/-1 : MAJ, GOLD, syndiagSyncPinnacle failed in slot 6 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1 6/-1 : MAJ, GOLD, queryHyperionSynched[6]: Hyperion out of sync in sw_mode 1
The following example shows how to display the SEA logging system disk:
Router# show logging system disk SEA log disk: sup-bootdisk:
The following example shows how to display the current size of the SEA:
Router# show logging system size SEA log size: 33554432 bytes
63-2
OL-13013-06
Chapter 63
Using the System Event Archive Copying the SEA To Another Device
The following example shows how to clear the SEA:

Router# clear logging system Clear logging system operation will take a while. Do you want to continue? [no]: yes Router#
Copying the SEA To Another Device

To copy the SEA to another device, such as a removeable memory device, perform this task: Command
Router# copy logging system file_system
Purpose Copies the contents of the SEA to the specified destination file system or process.
The valid values for file_system are:

bootflash: disk0: disk1: ftp: http: https: rcp: slavebootflash: slavedisk0: slavedisk1: slavesup-bootdisk: slavesup-bootflash: sup-bootdisk: sup-bootflash: tftp:
The following example shows how to copy the SEA to the disk0 file system:
Router# copy logging system disk0: Destination filename [sea_log.dat]? Copy in progress...CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC 33554432 bytes copied in 112.540 secs (298156 bytes/sec)
63-3
Chapter 63 Copying the SEA To Another Device
The following example shows how to copy the SEA using the remote file copy function (rcp):
Router# copy logging system rcp: Address or name of remote host []? 192.0.2.1 Destination username [Router]? username1 Destination filename [sea_log.dat]? /auto/tftpboot-users/username1/sea_log.dat !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 33554432 bytes copied in 48.172 secs (696555 bytes/sec)
Tip
63-4
OL-13013-06
CH A P T E R
64
Backplane Traffic Monitoring

This chapter describes how to configure the Backplane Traffic Monitoring feature in Cisco IOS Software Release 12.2SX. Cisco IOS Release 12.2(33)SXI and later releases support the Backplane Traffic Monitoring feature.
Note
Tip

Understanding Traffic Monitoring, page 64-1 Default Configuration, page 64-2 Configuration Guidelines and Restrictions, page 64-2 Configuring Backplane Traffic Monitoring, page 64-2
Understanding Traffic Monitoring

Backplane Traffic Monitoring can monitor the backplane and fabric-channel traffic utilization at a configured interval and threshold. Traffic monitoring allows the switch to monitor the backplane and fabric channel traffic utilization at a configured interval and threshold. Syslog messages are generated when the traffic utilization is above or below the configured threshold. The following examples show several types of syslog messages:

00:08:03: %TRAFFIC_UTIL-SP-4-MONITOR_BACKPLANE_REACH_THR: Backplane traffic utilization is 26%, reached threshold(20%) within 10 second interval 00:08:13: %TRAFFIC_UTIL-SP-4-MONITOR_BACKPLANE_BELOW_THR: Backplane traffic utilization is 18%, below threshold(20%) within 10 second interval
64-1
Chapter 64 Default Configuration
00:08:44: %TRAFFIC_UTIL-SP-4-MONITOR_FABRIC_IG_REACH_THR: Module 1, Channel 0 ingress traffic utilization is 5%, reached threshold(3%) within 30 second interval 00:08:44: %TRAFFIC_UTIL-SP-4-MONITOR_FABRIC_EG_REACH_THR: Module 1, Channel 0 egress traffic utilization is 5%, reached threshold(3%) within 30 second interval 00:09:14: %TRAFFIC_UTIL-SP-4-MONITOR_FABRIC_IG_BELOW_THR: Module 1, Channel 0 ingress traffic utilization is 1%, below threshold(3%) within 30 second interval 00:09:14: %TRAFFIC_UTIL-SP-4-MONITOR_FABRIC_EG_BELOW_THR: Module 1, Channel 0 egress traffic utilization is 1%, below threshold(3%) within 30 second interval
Default Configuration

The default threshold is 80 percent. Traffic monitor is off by default.

The syslog message buffer is limited in size. To reduce false alarms and the number of syslog messages, use the following guidelines:
Traffic can occur in bursts. If a small amount of bursts occur in a monitoring interval, it does not represent a capacity overload issue for the system; the hardware buffers are able to absorb the effects and not cause packet drops. For an example, if you set a monitoring interval to 10 seconds and the threshold to 80 percent, there are a total of 10 traffic utilization readings. Assume only 2 of the readings reached 90 percent and the other 8 readings are 20 percent. If the peak threshold of 90 percent is used to compare with the threshold, an unwanted warning syslog message is generated. It is better to use the average 34 percent of the 10 readings to compare with the threshold and not generate warning messages in this case. If the peak value comparison is really needed, you can set the interval to 1 second. Setting the interval to 1 second compares the reading directly with the threshold.
The number of syslog messages that generate syslog messages are from below the threshold and above the threshold.
Configuring Backplane Traffic Monitoring

To configure the Backplane Traffic Monitoring feature, perform one or more of the following tasks: Command
Router(config)# monitor traffic-util backplane interval interval threshold percentage Router(config)# monitor traffic-util fabric module {mod-num | all} {channel {0|1|both}} {direction {egress | ingress | both}} [interval interval threshold percentage]
Purpose Configures the backplane utilization traffic monitoring. Configures the fabric channel utilization traffic monitoring.
64-2
OL-13013-06
Chapter 64
Backplane Traffic Monitoring Configuring Backplane Traffic Monitoring
Command
Router(config)# monitor traffic-util fabric logging interval second
Purpose Configures the fabric channel utilization traffic monitor SYSLOG interval when the traffic utilization is in the crossed state. Configures the traffic monitor backplane SYSLOG interval when the traffic utilization is in the crossed state. Displays the percentage of the backplane (shared bus) utilization and traffic monitor status information.
Router(config)# monitor traffic-util backplane logging interval second Router# show catalyst6000 traffic-meter
When configuring a range of interfaces, you can enter the mod-num as a list or a range. Separate each entry with a comma and each range with a hyphen (-). For example, 1,3,5-9,12. The following example shows how to enable backplane traffic utilization monitoring:
Router(config)# monitor traffic-util backplane logging interval 50 threshold 100
The following example shows how to disable backplane traffic utilization monitoring:
Router(config)# no monitor traffic-util backplane
The following example shows how to specify the fabric channel traffic utilization monitor interval and threshold for a fabric channel on a specific module:
Router(config)# monitor traffic-util fabric module 8 channel both direction both interval 50 threshold 60
The following example shows how to specify the fabric channel traffic utilization monitor threshold for a specific fabric channel and for egress traffic only:
Router(config)# monitor traffic-util fabric module 6 channel 0 direction egress interval 100 threshold 90
Tip
64-3
Chapter 64 Configuring Backplane Traffic Monitoring
64-4
OL-13013-06
C H A P T E R
65

This chapter describes how to configure local Switched Port Analyzer (SPAN), remote SPAN (RSPAN), and Encapsulated RSPAN (ERSPAN) in Cisco IOS Release 12.2SX.
Note
For complete syntax and usage information for the commands used in this chapter, see the Cisco IOS Master Command List, Release 12.2SX, at this URL: http://www.cisco.com/en/US/docs/ios/mcl/122sxmcl/12_2sx_mcl_book.html SPA ports and FlexWAN ports do not support SPAN, RSPAN, or ERSPAN.
Tip

Understanding Local SPAN, RSPAN, and ERSPAN, page 65-1 Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions, page 65-7 Configuring Local SPAN, RSPAN, and ERSPAN, page 65-14
Understanding Local SPAN, RSPAN, and ERSPAN

These sections describe how local SPAN, RSPAN, and ERSPAN work:

Local SPAN, RSPAN, and ERSPAN Overview, page 65-2 Local SPAN, RSPAN, and ERSPAN Sources, page 65-5 Local SPAN, RSPAN, and ERSPAN Destinations, page 65-7
65-1
Chapter 65 Understanding Local SPAN, RSPAN, and ERSPAN
Local SPAN, RSPAN, and ERSPAN Overview

SPAN copies traffic from one or more CPUs, one or more ports, one or more EtherChannels, or one or more VLANs, and sends the copied traffic to one or more destinations for analysis by a network analyzer such as a SwitchProbe device or other Remote Monitoring (RMON) probe. Traffic can also be sent to the processor for packet capture by the Mini Protocol Analyzer, as described in Chapter 69, Using the Mini Protocol Analyzer. SPAN does not affect the switching of traffic on sources. You must dedicate the destination for SPAN use. The SPAN-generated copies of traffic compete with user traffic for switch resources. These sections provide an overview of local SPAN, RSPAN, and ERSPAN:

Local SPAN Overview, page 65-2 RSPAN Overview, page 65-3 ERSPAN Overview, page 65-4 Understanding the Traffic Monitored at SPAN Sources, page 65-4
Local SPAN Overview

A local SPAN session is an association of source ports and source VLANs with one or more destinations. 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 for analysis (see Figure 65-1). For example, as shown in Figure 65-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 65-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
65-2
S6884
OL-13013-06
Chapter 65
Configuring Local SPAN, RSPAN, and ERSPAN Understanding Local SPAN, RSPAN, and ERSPAN
RSPAN Overview
RSPAN supports source ports, source VLANs, and destinations on different switches, which provides remote monitoring of multiple switches across your network (see Figure 65-2). RSPAN uses a Layer 2 VLAN to carry SPAN traffic between switches. 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 destinations 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 destinations.
Figure 65-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)
65-3
ERSPAN Overview
ERSPAN supports source ports, source VLANs, and destinations on different switches, which provides remote monitoring of multiple switches across your network (see Figure 65-3). ERSPAN uses a GRE tunnel to carry traffic between switches. 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 destinations 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 destinations.
Figure 65-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
Understanding the Traffic Monitored at SPAN Sources

These sections describe the traffic that local SPAN, RSPAN, and ERSPAN sources can monitor:

Monitored Traffic Direction, page 65-5 Monitored Traffic Type, page 65-5 Duplicate Traffic, page 65-5
65-4
OL-13013-06
Chapter 65
Configuring Local SPAN, RSPAN, and ERSPAN Understanding Local SPAN, RSPAN, and ERSPAN
Monitored Traffic Direction

You can configure local SPAN sessions, RSPAN source sessions, and ERSPAN source sessions to monitor the following traffic:
Ingress traffic
Called ingress SPAN. Copies traffic received by the sources (ingress traffic). Ingress traffic is sent to the supervisor engine SPAN ASIC to be copied.
Egress traffic
Called egress SPAN. Copies traffic transmitted from the sources (egress traffic). Distributed egress SPAN modeWith Release 12.2(33)SXH and later releases, on some
fabric-enabled switching modules, egress traffic can be copied locally by the switching module SPAN ASIC and then sent to the SPAN destinations. See the Distributed Egress SPAN Mode Guidelines and Restrictions section on page 65-14 for information about switching modules that support distributed egress SPAN mode.
Centralized egress SPAN modeOn all other switching modules, egress traffic is sent to the
supervisor engine SPAN ASIC to be copied and is then sent to the SPAN destinations.
Both
Copies both the received traffic and the transmitted traffic (ingress and egress traffic). Both ingress traffic and egress traffic is sent to the supervisor engine SPAN ASIC to be copied.
Monitored Traffic Type

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. 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, 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 CPUs, page 65-6 Source Ports and EtherChannels, page 65-6 Source VLANs, page 65-6
65-5
Source CPUs
A source CPU is a CPU monitored for traffic analysis. With Release 12.2(33)SXH and later releases, you can configure both the SP CPU and the RP CPU as SPAN sources. These are examples of what you can do with the data generated by CPU monitoring:

Develop baseline information about CPU traffic. Develop information to use when creating control plane policing (CoPP) policies. Troubleshoot CPU-related issues (for example, high CPU utilization).
Note
CPU SPAN monitors CPU traffic from the perspective of the ASICs that send and receive the CPU traffic, rather than from onboard the CPUs themselves. Traffic to and from the CPU is tagged with VLAN IDs. You can configure source VLAN filtering of the CPU traffic.
Source Ports and EtherChannels

A source port or EtherChannel is a port or EtherChannel monitored for traffic analysis. You can configure both Layer 2 and Layer 3 ports and EtherChannels as SPAN sources. SPAN can monitor one or more source ports or EtherChannels in a single SPAN session. You can configure ports or EtherChannels in any VLAN as SPAN sources. Trunk ports or EtherChannels can be configured as sources and mixed with nontrunk sources.
Note
SPAN does not copy the encapsulation from trunk sources. You can configure SPAN destinations as trunks to tag the monitored traffic before it is transmitted for analysis.
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 and EtherChannels in the source VLANs become sources of SPAN traffic.
Note
Layer 3 VLAN interfaces on source VLANs are not sources of SPAN traffic. Traffic that enters a VLAN through a Layer 3 VLAN interface is monitored when it is transmitted from the switch through an egress port or EtherChannel that is in the source VLAN.
65-6
OL-13013-06
Chapter 65
Configuring Local SPAN, RSPAN, and ERSPAN Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
Local SPAN, RSPAN, and ERSPAN Destinations

A SPAN destination is a Layer 2 or Layer 3 port or, with Release 12.2(33)SXH and later releases, an EtherChannel, to which local SPAN, RSPAN, or ERSPAN sends traffic for analysis. When you configure a port or EtherChannel as a SPAN destination, it is dedicated for use only by the SPAN feature. Destination EtherChannels do not support the Port Aggregation Control Protocol (PAgP) or Link Aggregation Control Protocol (LACP) EtherChannel protocols; only the on mode is supported, with all EtherChannel protocol support disabled. There is no requirement that the member links of a destination EtherChannel be connected to a device that supports EtherChannels. For example, you can connect the member links to separate network analyzers. See Chapter 18, Configuring EtherChannels, for more information about EtherChannel. Destinations, by default, cannot receive any traffic. With Release 12.2(33)SXH and later releases, you can configure Layer 2 destinations to receive traffic from any attached devices. Destinations, by default, do not transmit anything except SPAN traffic. Layer 2 destinations that you have configured to receive traffic can be configured to learn the Layer 2 address of any devices attached to the destination and transmit traffic that is addressed to the devices. You can configure trunks as destinations, which allows trunk destinations to transmit encapsulated traffic. You can use allowed VLAN lists to configure destination trunk VLAN filtering.
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 65-8 Feature Incompatibilities, page 65-8 Local SPAN, RSPAN, and ERSPAN Session Limits, page 65-10 Local SPAN, RSPAN, and ERSPAN Interface Limits, page 65-10 Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions, page 65-10 VSPAN Guidelines and Restrictions, page 65-11 RSPAN Guidelines and Restrictions, page 65-12 ERSPAN Guidelines and Restrictions, page 65-13 Distributed Egress SPAN Mode Guidelines and Restrictions, page 65-14
65-7
Chapter 65 Local SPAN, RSPAN, and ERSPAN Configuration Guidelines and Restrictions
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 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. Release 12.2(33)SXH and later releases support distributed egress SPAN, which reduces the load on the supervisor engine.
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 Incompatibilities
These feature incompatibilities exist with local SPAN, RSPAN, and ERSPAN:
In releases where CSCth62957 is not resolved, in PFC3B mode or PFC3BXL mode, the xconnect target_ip_address vc_value encapsulation mpls command might cause traffic to loop continuously with these SPAN configurations:
If the xconnect target_ip_address vc_value encapsulation mpls command is configured on a
physical interface, the CLI prevents configuration of that port as part of a SPAN session.
If a SPAN session is configured on a physical port and you attempt to configure the
xconnect target_ip_address vc_value encapsulation mpls command, the CLI prints a warning that recommends against the configuration.
65-8
OL-13013-06
Chapter 65
physical interface, you should not configure source cpu {rp | sp} in any SPAN session, but the CLI does not enforce any restriction.
If a SPAN session is configured with source cpu {rp | sp} and you attempt to configure the
xconnect target_ip_address vc_value encapsulation mpls command, the CLI does not enforce any restriction.
In releases where CSCth62957 is resolved, to avoid a configuration that might cause traffic to loop continuously, the CLI enforces these restrictions in PFC3B mode or PFC3BXL mode:
physical interface, the CLI prevents configuration of that port as part of a SPAN session.
If a SPAN session is configured on a physical port and you attempt to configure the the xconnect
target_ip_address vc_value encapsulation mpls command command on that port, the CLI prints a warning that recommends against the configuration.
If the the xconnect target_ip_address vc_value encapsulation mpls command command is
configured on a physical interface, you cannot configure source cpu {rp | sp} in any SPAN session.
If a SPAN session is configured with source cpu {rp | sp} and you attempt to configure the
xconnect target_ip_address vc_value encapsulation mpls command, the CLI prints a warning that recommends against the configuration.

Egress SPAN is not supported in egress multicast mode. (CSCsa95965) Unknown unicast flood blocking (UUFB) ports cannot be RSPAN or local SPAN egress-only destinations. (CSCsj27695) Except in PFC3C mode or PFC3CXL mode, Ethernet over MultiProtocol Label Switching (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. These features are incompatible with SPAN destinations:
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 destinations can participate in IEEE 802.3Z flow control. 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.
65-9
Local SPAN, RSPAN, and ERSPAN Session Limits

With Release 12.2(33)SXH and later releases, these are the PFC3 local SPAN, RSPAN, and ERSPAN session limits: Local and Source Sessions Local SPAN, RSPAN Source, ERSPAN Source Ingress or Egress or Both 2 Destination Sessions
Total Sessions 80
Local SPAN Egress-Only 14
RSPAN 64
ERSPAN 23
Local SPAN, RSPAN, and ERSPAN Interface Limits

With Release 12.2(33)SXH and later releases, these are the PFC3 local SPAN, RSPAN, and ERSPAN source and destination interface limits: In Each RSPAN Destination Session In Each ERSPAN Destination Session
In Each Local SPAN Session Egress or both sources Ingress sources RSPAN and ERSPAN destination session sources Destinations per session 128 128 64
In Each RSPAN Source Session 128 128
In Each ERSPAN Source Session 128 128
1 RSPAN VLAN 1 IP address 64 64
1 RSPAN VLAN 1 IP address
Local SPAN, RSPAN, and ERSPAN Guidelines and Restrictions

These guidelines and restrictions apply to local SPAN, RSPAN, and ERSPAN:
A SPAN destination that is copying traffic from a single egress SPAN source port sends only egress traffic to the network analyzer. 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. (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 destinations.
65-10
OL-13013-06
Chapter 65
Within a SPAN session, all of the SPAN destinations receive all of the traffic from all of the SPAN sources, except when source-VLAN filtering is configured on the SPAN source. You can configure destination trunk VLAN filtering to select which traffic is transmitted from the SPAN destination. 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. Within a session, you cannot configure both VLANs as SPAN sources and do source VLAN filtering. You can configure VLANs as SPAN sources or you can do source VLAN filtering of traffic from source ports and EtherChannels, but not both in the same session. You cannot configure source VLAN filtering for internal VLANs. 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 destinations as trunks to send locally tagged traffic to the traffic analyzer.
Note
A destination configured as a trunk tags traffic from a Layer 3 LAN source with the internal VLAN used by the Layer 3 LAN source.
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. Local SPAN sessions, RSPAN source sessions, and ERSPAN source sessions do not copy locally sourced ERSPAN GRE-encapsulated traffic from source ports. With Release 12.2(33)SXH and later, SPAN sessions can share destinations. SPAN destinations cannot be SPAN sources. Destinations never participate in any spanning tree instance. Local SPAN includes BPDUs in the monitored traffic, so any BPDUs seen on the destination are from the source. RSPAN does not support BPDU monitoring. All packets forwarded through the switch for transmission from a port that is configured as an egress SPAN source are copied to the SPAN destination, including packets that do not exit the switch through the egress port because STP has put the egress port into the blocking state, or on an egress 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.
65-11
These are VSPAN guidelines and restrictions:

VSPAN sessions do not support source VLAN filtering. For VSPAN sessions with both ingress and egress configured, two packets are forwarded from the destination to the analyzer 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:

All participating switches must be connected by Layer 2 trunks. 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. 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.
65-12
OL-13013-06
Chapter 65
ERSPAN Guidelines and Restrictions

These are ERSPAN guidelines and restrictions:
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
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 65-29). 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 65-31). 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 destinations. You configure the same address in both the source and destination sessions with the ip address command.
65-13
Chapter 65 Configuring Local SPAN, RSPAN, and ERSPAN
The ERSPAN ID differentiates the ERSPAN traffic arriving at the same destination IP address from various different ERSPAN source sessions.
Distributed Egress SPAN Mode Guidelines and Restrictions

These are distributed egress SPAN mode guidelines and restrictions:
These switching modules disable distributed egress SPAN mode:

WS-X6502-10GE WS-X6816-GBIC WS-X6516-GBIC WS-X6516-GE-TX WS-X6524-100FX-MM WS-X6548-RJ-45 WS-X6548-RJ-21
With any of these switching modules installed, the egress SPAN mode is centralized. Enter the show monitor session egress replication-mode | include Operational|slot command to display any switching modules that disable distributed egress SPAN mode. If there are no modules installed that disable distributed egress SPAN mode, the command displays only the egress SPAN operational mode.
Some switching modules have ASICs that do not support distributed egress SPAN mode for ERSPAN sources. Enter the show monitor session egress replication-mode | include Distributed.*Distributed.*Centralized command to display the slot number of any switching modules that do not support distributed egress SPAN mode for ERSPAN sources. Enter the show asic-version slot slot_number command to display the versions of the ASICs on the switching module in the slot where distributed egress SPAN mode is not supported for ERSPAN sources. Hyperion ASIC revision levels 5.0 and higher and all versions of the Metropolis ASIC support distributed egress SPAN mode for ERSPAN sources. Switching modules with Hyperion ASIC revision levels lower than 5.0 do not support distributed egress SPAN mode for ERSPAN sources.

These sections describe how to configure local SPAN, RSPAN, and ERSPAN:

Local SPAN, RSPAN, and ERSPAN Default Configuration, page 65-15 Configuring a Destination as an Unconditional Trunk (Optional), page 65-15 Configuring Destination Trunk VLAN Filtering (Optional), page 65-16 Configuring Destination Port Permit Lists (Optional), page 65-17 Configuring the Egress SPAN Mode (Optional), page 65-18 Configuring Local SPAN, page 65-19 Configuring RSPAN, page 65-23
65-14
OL-13013-06
Chapter 65
Configuring Local SPAN, RSPAN, and ERSPAN Configuring Local SPAN, RSPAN, and ERSPAN
Configuring ERSPAN, page 65-29 Configuring Source VLAN Filtering in Global Configuration Mode, page 65-33 Verifying the Configuration, page 65-34 Configuration Examples, page 65-34
Local SPAN, RSPAN, and ERSPAN Default Configuration

This section describes the local SPAN, RSPAN, and ERSPAN default configuration: Feature Local SPAN RSPAN ERSPAN Default operating mode for egress SPAN sessions: Releases earlier than Release 12.2(33)SXH: Centralized Release 12.2(33)SXH: Release 12.2(33)SXH1: Release 12.2(33)SXH2: Release 12.2(33)SXH2a: Distributed Distributed Distributed Centralized Default Value Disabled Disabled Disabled
Configuring a Destination as an Unconditional Trunk (Optional)

To tag the monitored traffic as it leaves a destination, configure the destination as a trunk before you configure it as a destination. To configure the destination as a trunk, perform this task: Command
Router# configure terminal Router(config)# interface {type port-channel number} Router(config-if)# switchport
1

slot/port |
Selects the interface to configure. Configures the interface for Layer 2 switching (required only if the interface is not already configured for Layer 2 switching). Configures the encapsulation, which configures the interface as either an ISL or 802.1Q trunk. Configures the interface to trunk unconditionally.
Step 4 Step 5
Router(config-if)# switchport trunk encapsulation {isl | dot1q} Router(config-if)# switchport mode trunk 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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
65-15
Router(config-if)# switchport mode trunk
Note
Releases earlier than Release 12.2(33)SXH required you to enter the switchport nonegotiate command when you configured a destination port as an unconditional trunk. This requirement has been removed in Release 12.2(33)SXH and later releases.
Configuring Destination Trunk VLAN Filtering (Optional)

Note
In addition to filtering VLANs on a trunk, you can also apply the allowed VLAN list to access ports. Destination trunk VLAN filtering is applied at the destination. Destination trunk VLAN filtering does not reduce the amount of traffic being sent from the SPAN sources to the SPAN destinations.
When a destination is a trunk, you can use the list of VLANs allowed on the trunk to filter the traffic transmitted from the destination. (CSCeb01318) Destination trunk VLAN filtering removes the restriction that, within a SPAN session, all destinations receive all the traffic from all the sources. Destination trunk VLAN filtering allows you to select, on a per-VLAN basis, the traffic that is transmitted from each destination trunk to the network analyzer. To configure destination trunk VLAN filtering on a destination trunk, perform this task: Command
1

slot/port
Selects the destination trunk port to configure. Configures the list of VLANs allowed on the trunk.
Router(config-if)# switchport trunk allowed vlan {add | except | none | remove} vlan [,vlan[,vlan[,...]] 1. type = fastethernet, gigabitethernet, or tengigabitethernet
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 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
65-16
OL-13013-06
Chapter 65
switchport trunk encapsulation dot1q switchport trunk allowed vlan 10 switchport mode trunk switchport nonegotiate ! 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
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)# 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. Configures a destination port permit list or adds to an existing destination port permit list. Verifies the configuration.
Step 4
This example shows how to configure a destination port permit list that includes Gigabit Ethernet ports 5/1 through 5/4 and 6/1:
65-17
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
Configuring the Egress SPAN Mode (Optional)

With Release 12.2(33)SXH, Release 12.2(33)SXH1, and Release 12.2(33)SXH2, distributed egress SPAN mode is the default if there are no switching modules installed that disable it. With Release 12.2(33)SXH2a and later releases, centralized egress SPAN mode is the default. See the Distributed Egress SPAN Mode Guidelines and Restrictions section on page 65-14 for information about switching modules that support distributed egress SPAN mode. With Release 12.2(33)SXH2a and later releases, to configure the egress SPAN mode, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session egress replication-mode distributed
Purpose Enters global configuration mode. Enables distributed egress SPAN mode.
Note
Enter the no monitor session egress replication-mode distributed command to enable centralized egress SPAN mode.
Step 3
Router(config)# end
This example shows how to enable distributed egress SPAN mode:

Router# configure terminal Router(config)# monitor session egress replication-mode distributed Router(config)# end
With Release 12.2(33)SXH, Release 12.2(33)SXH1, and Release 12.2(33)SXH2, to configure the egress SPAN mode, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session egress replication-mode centralized
Purpose Enters global configuration mode. Enables centralized egress SPAN mode.
Note
Enter the no monitor session egress replication-mode centralized command to enable distributed egress SPAN mode.
Step 3
Router(config)# end
This example shows how to disable distributed egress SPAN mode:

Router# configure terminal Router(config)# monitor session egress replication-mode centralized Router(config)# end
65-18
OL-13013-06
Chapter 65
This example shows how to display the configured egress SPAN mode:
Router# show monitor session egress replication-mode | include Configured Configured mode : Centralized
Configuring Local SPAN

These sections describe how to configure local SPAN sessions:

Configuring Local SPAN (SPAN Configuration Mode), page 65-19 Configuring Local SPAN (Global Configuration Mode), page 65-21
Configuring Local SPAN (SPAN Configuration Mode)

Note
To tag the monitored traffic as it leaves a destination, you must configure the destination to trunk unconditionally before you configure it as a destination (see the Configuring a Destination as an Unconditional Trunk (Optional) section on page 65-15). To configure a local SPAN session in SPAN configuration mode, perform this task:
Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session local_SPAN_session_number type [local | local-tx]
Purpose Enters global configuration mode. Configures a local SPAN session number and enters local SPAN session configuration mode.
Note
Enter the local keyword to configure ingress or egress or both SPAN sessions. Enter the local-tx keyword to configure egress-only SPAN sessions.
Step 3 Step 4
Router(config-mon-local)# description session_description Router(config-mon-local)# source {{cpu {rp | sp}} | single_interface | interface_list | interface_range | mixed_interface_list | single_vlan | vlan_list | vlan_range | mixed_vlan_list} [rx | tx | both]
(Optional) Describes the local SPAN session. Associates the local SPAN session number with the CPU, source ports, or VLANs, and selects the traffic direction to be monitored.
Note
When you enter the local-tx keyword, the rx and both keywords are not available and the tx keyword is required. To make best use of the available SPAN sessions, it is always preferable to configure local-tx sessions instead of local sessions with the tx keyword.
Step 5
Router(config-mon-local)# filter single_vlan | vlan_list | vlan_range | mixed_vlan_list
(Optional) Configures source VLAN filtering when the local SPAN source is a trunk port.
65-19
Command
Step 6
Router(config-mon-local)# destination {single_interface | interface_list | interface_range | mixed_interface_list} [ingress [learning]] Router(config-mon-local)# no shutdown
Purpose Associates the local SPAN session number with the destinations. Activates the local SPAN session.
Note
Step 7
The no shutdown command and shutdown commands are not supported for local-tx egress-only SPAN sessions.
Step 8
Router(config-mon-local)# end
When configuring monitor sessions, note the following information:
session_description can be up to 240 characters and cannot contain special characters; with Release 12.2(33)SXH and later releases, the description can contain spaces.
Note
You can enter 240 characters after the description command.
local_span_session_number can range from 1 to 80. cpu rp is the route processor (RP). cpu sp is the switch processor (SP). single_interface is as follows:
interface type slot/port; type is fastethernet, gigabitethernet, or tengigabitethernet. interface port-channel number
Note
Destination port channel interfaces must be configured with the channel-group group_num mode on command and the no channel-protocol command. See the Configuring EtherChannels section on page 18-7.
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 , ... Enter the ingress keyword to configure destinations to receive traffic from attached devices. Enter the learning keyword to enable MAC address learning from the destinations, which allows the switch to transmit traffic that is addressed to devices attached to the destinations. When configuring destinations with the ingress and learning keywords, note the following:
65-20
OL-13013-06
Chapter 65
Configure the destinations for Layer 2 switching. See the Configuring LAN Interfaces for
Layer 2 Switching section on page 16-6.

If the destination is a trunk and the attached device transmits tagged traffic back to the switch,
you can use either ISL or 802.1Q trunking.

If the destination is a trunk and the attached device transmits untagged traffic back to the switch,
use 802.1Q trunking with the native VLAN configured to accept the traffic from the attached device.
Do not configure the destinations with Layer 3 addresses. Use a VLAN interface to route traffic
to and from devices attached to destinations.

Destinations are held in the down state. To route the traffic to and from attached devices,
configure an additional active Layer 2 port in the VLAN to keep the VLAN interface up. This example shows how to configure session 1 to monitor ingress traffic from Gigabit Ethernet port 1/1 and configure Gigabit Ethernet port 1/2 as the destination:
Router(config)# monitor session 1 type local Router(config-mon-local)# source interface gigabitethernet 1/1 rx Router(config-mon-local)# destination interface gigabitethernet 1/2
For additional examples, see the Configuration Examples section on page 65-34.
Configuring Local SPAN (Global Configuration Mode)

Note
To tag the monitored traffic as it leaves a destination, you must configure the destination to trunk unconditionally before you configure it as a destination (see the Configuring a Destination as an Unconditional Trunk (Optional) section on page 65-15). You can configure up to two local SPAN sessions in global configuration mode. You can use SPAN configuration mode for all SPAN configuration tasks. You must use SPAN configuration mode to configure the supported maximum number of SPAN sessions.
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} [ingress [learning]]
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 destinations.
Step 3
65-21
When configuring local SPAN sessions, note the following information:

local_span_session_number can range from 1 to 66. single_interface is as follows:

Note
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 , ... Enter the ingress keyword to configure destinations to receive traffic from attached devices. Enter the learning keyword to enable MAC address learning from the destinations, which allows the switch to transmit traffic that is addressed to devices attached to the destinations. When configuring destinations with the ingress and learning keywords, note the following:



configure an additional active Layer 2 port in the VLAN to keep the VLAN interface up. 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
65-22
OL-13013-06
Chapter 65
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 65-23 Configuring RSPAN Sessions (SPAN Configuration Mode), page 65-23 Configuring RSPAN Sessions (Global Configuration Mode), page 65-26
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]
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. Updates the VLAN database and returns to privileged EXEC mode.
Step 3 Step 4
Router(config-vlan)# remote-span Router(config-vlan)# end
Configuring RSPAN Sessions (SPAN Configuration Mode)

These sections describe how to configure RSPAN sessions in SPAN configuration mode:

Configuring RSPAN Source Sessions in SPAN Configuration Mode, page 65-23 Configuring RSPAN Destination Sessions in SPAN Configuration Mode, page 65-25
Configuring RSPAN Source Sessions in SPAN Configuration Mode

To configure an RSPAN source session in SPAN configuration mode, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# monitor session RSPAN_source_session_number type rspan-source
Purpose Enters global configuration mode. Configures an RSPAN source session number and enters RSPAN source session configuration mode for the session. (Optional) Describes the RSPAN source session. Associates the RSPAN source session number with the CPU, source ports, or VLANs, and selects the traffic direction to be monitored.
Step 3 Step 4
Router(config-mon-rspan-src)# description session_description Router(config-mon-rspan-src)# source {{cpu {rp | sp}} | single_interface | interface_list | interface_range | mixed_interface_list | single_vlan | vlan_list | vlan_range | mixed_vlan_list} [rx | tx | both]
65-23
Command
Router(config-mon-rspan-src)# filter single_vlan | vlan_list | vlan_range | mixed_vlan_list Router(config-mon-rspan-src)# destination remote vlan rspan_vlan_ID Router(config-mon-rspan-src)# no shutdown Router(config-mon-rspan-src)# end
Purpose (Optional) Configures source VLAN filtering when the RSPAN source is a trunk port. Associates the RSPAN source session number session number with the RSPAN VLAN. Activates the RSPAN source session. Exits configuration mode.
When configuring RSPAN source sessions, note the following information:
Note
RSPAN_source_span_session_number can range from 1 to 80. cpu rp is the route processor (RP). cpu sp is the switch processor (SP). single_interface is as follows:
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 , ... See the Configuring RSPAN VLANs section on page 65-23 for information about the RSPAN VLAN ID.
This example shows how to configure session 1 to monitor bidirectional traffic from Gigabit Ethernet port 1/1:
Router(config)# monitor session 1 type rspan-source Router(config-mon-rspan-src)# source interface gigabitethernet 1/1 Router(config-mon-rspan-src)# destination remote vlan 2
65-24
OL-13013-06
Chapter 65
Configuring RSPAN Destination Sessions in SPAN Configuration Mode
Note
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 as an Unconditional Trunk (Optional) section on page 65-15). 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 type rspan-destination Router(config-mon-rspan-dst)# description session_description Router(config-mon-rspan-dst)# source remote vlan rspan_vlan_ID Router(config-mon-rspan-dst)# destination {single_interface | interface_list | interface_range | mixed_interface_list} [ingress [learning]] Router(config-mon-rspan-dst)# end
Purpose Enters global configuration mode. Configures an RSPAN destination session number and enters RSPAN destination session configuration mode for the session. (Optional) Describes the RSPAN destination session. Associates the RSPAN destination session number with the RSPAN VLAN. Associates the RSPAN destination session number with the destinations. Exits configuration mode.
Step 6
When configuring RSPAN destination sessions, note the following information:

RSPAN_destination_span_session_number can range from 1 to 80. single_interface is as follows:

Note
Note
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ...
65-25
Enter the ingress keyword to configure destinations to receive traffic from attached devices. Enter the learning keyword to enable MAC address learning from the destinations, which allows the switch to transmit traffic that is addressed to devices attached to the destinations. When configuring destinations with the ingress and learning keywords, note the following:



configure an additional active Layer 2 port in the VLAN to keep the VLAN interface up.
The no shutdown command and shutdown commands are not supported for RSPAN destination sessions.
This example shows how to configure RSPAN VLAN 2 as the source for session 1 and Gigabit Ethernet port 1/2 as the destination:
Router(config)# monitor session 1 type rspan-destination Router(config-rspan-dst)# source remote vlan 2 Router(config-rspan-dst)# destination interface gigabitethernet 1/2
Configuring RSPAN Sessions (Global Configuration Mode)

These sections describe how to configure RSPAN sessions in global configuration mode:

Configuring RSPAN Source Sessions in Global Configuration Mode, page 65-26 Configuring RSPAN Destination Sessions in Global Configuration Mode, page 65-27
Configuring RSPAN Source Sessions in Global Configuration Mode

To configure an RSPAN source session in global configuration mode, 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
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.
65-26
OL-13013-06
Chapter 65
When configuring RSPAN source sessions, note the following information:

To configure RSPAN VLANs, see the Configuring RSPAN VLANs section on page 65-23. RSPAN_source_span_session_number can range from 1 to 66. single_interface is as follows:
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 , ... See the Configuring RSPAN VLANs section on page 65-23 for information about the RSPAN VLAN ID.
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 in Global Configuration Mode
Note
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 as an Unconditional Trunk (Optional) section on page 65-15). You can configure an RSPAN destination session on the RSPAN source session switch to monitor RSPAN traffic locally.
65-27
To configure an RSPAN destination session in global configuration mode, 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} [ingress [learning]]
Purpose Enters global configuration mode. Associates the RSPAN destination session number with the RSPAN VLAN. Associates the RSPAN destination session number with the destinations.
Step 3

RSPAN_destination_span_session_number can range from 1 to 66. See the Configuring RSPAN VLANs section on page 65-23 for information about the RSPAN VLAN ID. single_interface is as follows:
Note
Note
interface_range is interface type slot/first_port - last_port. mixed_interface_list is, in any order, single_interface , interface_range , ... Enter the ingress keyword to configure destinations to receive traffic from attached devices. Enter the learning keyword to enable MAC address learning from the destinations, which allows the switch to transmit traffic that is addressed to devices attached to the destinations. When configuring destinations with the ingress and learning keywords, note the following:


65-28
OL-13013-06
Chapter 65

configure an additional active Layer 2 port in the VLAN to keep the VLAN interface up. 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 65-29 Configuring ERSPAN Destination Sessions, page 65-31
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. (Optional) Describes the ERSPAN source session. Associates the ERSPAN source session number with the CPU, 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 65-31, Step 6).
Step 3 Step 4
Router(config-mon-erspan-src)# description session_description Router(config-mon-erspan-src)# source {{{cpu {rp | sp}} | 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
Router(config-mon-erspan-src-dst)# ip address ip_address
65-29
Command
Step 8
Router(config-mon-erspan-src-dst)# erspan-id ERSPAN_flow_id
Purpose 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 65-31, Step 7). 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. Activates the ERSPAN source session. Exits configuration mode.
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)# no shutdown Router(config-mon-erspan-src-dst)# end
Note
ERSPAN_source_span_session_number can range from 1 to 66. cpu rp is the route processor (RP). cpu sp is the switch processor (SP). single_interface is as follows:
Note
Port channel interfaces must be configured with the channel-group group_num mode on command and the no channel-protocol command. See the Configuring EtherChannels section on page 18-7.
Note
interface_range is interface type slot/first_port - last_port.
65-30
OL-13013-06
Chapter 65
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.
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
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-mon-erspan-dst)# description session_description Router(config-mon-erspan-dst)# destination {single_interface | interface_list | interface_range | mixed_interface_list} [ingress [learning]] Router(config-mon-erspan-dst)# source
Purpose Enters global configuration mode. Configures an ERSPAN destination session number and enters ERSPAN destination session configuration mode for the session. (Optional) Describes the ERSPAN destination session. Associates the ERSPAN destination session number with the destinations. Enters ERSPAN destination session source configuration mode.
Step 3 Step 4
Step 5
65-31
Command
Step 6
Router(config-mon-erspan-dst-src)# ip address ip_address [force]
Purpose 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 65-29, Step 7. 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 65-29, Step 8. (Optional) Configures the VRF name used instead of the global routing table. Activates the ERSPAN destination session. Exits configuration mode.
Step 7
Router(config-mon-erspan-dst-src)# erspan-id ERSPAN_flow_id
Router(config-mon-erspan-dst-src)# vrf vrf_name
Router(config-mon-erspan-dst)# no shutdown Router(config-mon-erspan-dst-src)# end

ERSPAN_destination_span_session_number can range from 1 to 66. single_interface is as follows:

Note
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 65-29, Step 7).
ERSPAN_flow_id can range from 1 to 1023. Enter the ingress keyword to configure destinations to receive traffic from attached devices.
65-32
OL-13013-06
Chapter 65
Enter the learning keyword to enable MAC address learning from the destinations, which allows the switch to transmit traffic that is addressed to devices attached to the destinations. When configuring destinations with the ingress and learning keywords, note the following:



configure an additional active Layer 2 port in the VLAN to keep the VLAN interface up. 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
Configuring Source VLAN Filtering in Global Configuration Mode

Note
To configure source VLAN filtering in SPAN configuration mode, see the following sections:
Configuring Local SPAN (SPAN Configuration Mode), page 65-19 Configuring RSPAN Source Sessions in SPAN Configuration Mode, page 65-23 Configuring ERSPAN, page 65-29
Source VLAN filtering reduces the amount of traffic that is sent from SPAN sources to SPAN destinations.
Source VLAN filtering monitors specific VLANs when the source is a trunk port. 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
Purpose Enters global configuration mode. Configures source VLAN filtering when the local SPAN or RSPAN source is a trunk port.
65-33
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

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
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
65-34
OL-13013-06
Chapter 65
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 source 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 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
65-35
Tip
65-36
OL-13013-06
C H A P T E R
66
Configuring SNMP IfIndex Persistence

This chapter describes how to configure the SNMP ifIndex persistence feature in Cisco IOS Release 12.2SX.
Note
Tip

Understanding SNMP IfIndex Persistence, page 66-1 Configuring SNMP IfIndex Persistence, page 66-2
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.
66-1
Chapter 66 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 66-2 (Optional) Enabling and Disabling SNMP IfIndex Persistence on Specific Interfaces, page 66-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
66-2
OL-13013-06
Chapter 66
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
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. Enables SNMP ifIndex persistence on the specified interface. Exits interface configuration mode.
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
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
66-3
Chapter 66 Configuring SNMP IfIndex Persistence
Tip
66-4
OL-13013-06
C H A P T E R
67
Using Top-N Reports

This chapter describes how to use Top-N reports in Cisco IOS Release 12.2SX.
Note
Tip

Understanding Top-N Reports, page 67-1 Using Top-N Reports, page 67-2
Understanding Top-N Reports

These sections describe Top-N reports:

Top-N Reports Overview, page 67-1 Understanding Top-N Reports Operation, page 67-2
Top-N Reports Overview

Top-N reports allows you to collect and analyze data for each physical port on a switch. When Top-N reports start, they obtain statistics from the appropriate hardware counters and then go into sleep mode for a user-specified interval. When the interval ends, the reports obtain the current statistics from the same hardware counters, compare the current statistics from the earlier statistics, and store the difference. The statistics for each port are sorted by one of the statistic types that are listed in Table 67-1.
67-1
Chapter 67 Using Top-N Reports
Using Top-N Reports
Table 67-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, Top-N reports 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 Reports 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 reports notify 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. Only completed reports are displayed. For reports that are not completed, there is a short description of the process information. To terminate a Top-N reports process, enter the clear top counters interface report command. Pressing Ctrl-C does not terminate Top-N reports processes. The completed reports remain available for viewing until you remove them by entering the clear top counters interface report {all | report_num} command.
Using Top-N Reports

These sections describe how to use Top-N reports:

Enabling Top-N Reports Creation, page 67-3 Displaying Top-N Reports, page 67-3 Clearing Top-N Reports, page 67-4
67-2
OL-13013-06
Chapter 67
Using Top-N Reports Using Top-N Reports
Enabling Top-N Reports Creation

To enable Top-N reports creation, perform this task: Command
Router# collect top [number_of_ports] counters interface {type1 | all | layer-2 | layer-3} [sort-by statistic_type2] [interval seconds] 1. type = fastethernet, gigabitethernet, tengigabitethernet, port-channel 2. statistic_type = broadcast, bytes, errors, multicast, overflow, packets, utilization
Purpose Enables Top-N reports creation.
When enabling Top-N reports 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 reports 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 Top-N Reports

To display Top-N reports, perform this task: Command
Router# show top counters interface report [report_num]
Purpose Displays Top-N reports.

Note
To display information about all the reports, do not enter a report_num value.
Top-N reports 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.
This example shows how to display information about all the Top-N reports:
Router# show top counters interface report Id Start Time Int N Sort-By Status Owner
67-3
Chapter 67 Using Top-N Reports
Using Top-N Reports
-1 2 3 4
---------------------------08:18:25 UTC Tue Nov 23 2004 08:19:54 UTC Tue Nov 23 2004 08:21:34 UTC Tue Nov 23 2004 08:26:50 UTC Tue Nov 23 2004
--76 76 76 90
--20 20 20 20
--------util util util util
------done done done done
---------------------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 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 width (Tx + Rx) (Tx + Rx) (Tx + Rx) ------- ----- ---- ----------- ----------- ---------Fa2/5 100 50 726047564 11344488 11344487 Fa2/48 100 35 508018905 7937789 0 Fa2/46 100 25 362860697 5669693 0 Fa2/47 100 22 323852889 4762539 4762495
Multicast (Tx + Rx) ---------1 43 43 43
Inerr ---0 0 0 0
Bufovflw ----0 0 0 0
Clearing Top-N Reports

To clear Top-N reports, perform one of these tasks: Command
Router# clear top counters interface report Router# clear top counters interface report [report_num]
Purpose Clears all the Top-N reports that have a status of done. Clears Top-N report number report_num regardless of status.
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
Tip
67-4
OL-13013-06
C H A P T E R
68

This chapter describes how to use the Layer 2 traceroute utility.
Note
Tip

Understanding the Layer 2 Traceroute Utility, page 68-1 Usage Guidelines, page 68-2 Using the Layer 2 Traceroute Utility, page 68-3
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.
68-1
Chapter 68 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. 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. To verify the ping connectivity you need to use the IP address that the CDP advertises on its Layer 2 interfaces. 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.
68-2
OL-13013-06
Chapter 68
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.
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
68-3
Chapter 68 Using the Layer 2 Traceroute Utility
68-4
OL-13013-06
C H A P T E R
69

This chapter describes how to use the Mini Protocol Analyzer on the Catalyst 6500 series switches. Release 12.2(33)SXI and later releases support the Mini Protocol Analyzer feature.
Note
Tip

Understanding How the Mini Protocol Analyzer Works, page 69-1 Configuring the Mini Protocol Analyzer, page 69-2 Starting and Stopping a Capture, page 69-4 Displaying and Exporting the Capture Buffer, page 69-6 Mini Protocol Analyzer Configuration, Operation, and Display Examples, page 69-7
Understanding How the Mini Protocol Analyzer Works

The Mini Protocol Analyzer captures network traffic from a SPAN session and stores the captured packets in a local memory buffer. Using the provided filtering options, you can limit the captured packets to:

Packets from selected VLANs, ACLs, or MAC addresses. Packets of a specific EtherType. Packets of a specified packet size.
You can start and stop the capture using immediate commands, or you can schedule the capture to begin at a specified date and time.
69-1
Chapter 69 Configuring the Mini Protocol Analyzer
The captured data can be displayed on the console, stored to a local file system, or exported to an external server using normal file transfer protocols. The format of the captured file is libpcap, which is supported by many packet analysis and sniffer programs. Details of this format can be found at the following URL: http://www.tcpdump.org/ By default, only the first 68 bytes of each packet are captured.
Configuring the Mini Protocol Analyzer

To configure a capture session using the Mini Protocol Analyzer, perform this task: Command
Step 1 Step 2
Router# configure terminal Router(config)# [no] monitor session number type capture
Purpose Enters global configuration mode. Configures a SPAN session number with packets directed to the processor for capture. Enters capture session configuration mode. The session number range is 1 to 80. The no prefix removes the session. (Optional) Sets the size in KB of the capture buffer. The range is 32-65535 KB; the default is 2048 KB. (Optional) Describes the capture session. The description can be up to 240 characters and cannot contain special characters. If the description contains spaces, it must be enclosed in quotation marks(). (Optional) Sets a limit on the number of packets per second (pps) that can be captured. The range is 10-100000 packets per seconds; the default is 10000 packets per second. Associates the capture session with source ports or VLANs, and selects the traffic direction to be monitored. The default traffic direction is both. Exits the capture session configuration mode.
Step 3
Router(config-mon-capture)# buffer-size buf_size
Step 4
Router(config-mon-capture)# description session_description
Step 5
Router(config-mon-capture)# rate-limit pps
Step 6
Router(config-mon-capture)# source {{interface {single_interface | interface_list | interface_range | mixed_interface_list} | port-channel channel_id}} | {vlan {vlan_ID | vlan_list | vlan_range | mixed_vlan_list}}[rx | tx | both] Router(config-mon-capture)# exit
Step 7
When configuring a capture session, note the following information:

Only one capture session is supported; multiple simultaneous capture sessions cannot be configured. The source interface command argument is either a single interface, or a range of interfaces described by two interface numbers (the lesser one first, separated by a dash), or a comma-separated list of interfaces and ranges.
Note
When configuring a source interface list, you must enter a space before and after the comma. When configuring a source interface range, you must enter a space before and after the dash.
69-2
OL-13013-06
Chapter 69
Using the Mini Protocol Analyzer Configuring the Mini Protocol Analyzer
The source vlan command argument is either a single VLAN number from 1 through 4094 (except reserved VLANs), or a range of VLANs described by two VLAN numbers (the lesser one first, separated by a dash), or a list of VLANs and ranges.
Note
When configuring a source VLAN list, do not enter a space before or after the comma. When configuring a source VLAN range, do not enter a space before or after the dash. Note that this requirement differs from the requirement for source interface lists and ranges.
Data capture does not begin when the capture session is configured. The capture is started by the monitor capture start or monitor capture schedule command described in the Starting and Stopping a Capture section on page 69-4. Although the capture buffer is linear by default, it can be made circular as a run-time option in the monitor capture start or monitor capture schedule command. When no hardware rate limit registers are available, the capture session is disabled. When the fabric switching mode is truncated, with Release 12.2(33)SXI4 and later releases, you can enter an MPA configuration, but the default rate limiter and, if configured, the MPA rate limiter are not active while the fabric switching mode is truncated.
Note
Ignore the Rate-limiter is not configurable system message.
With releases earlier than Release 12.2(33)SXI4, because the truncated fabric switching mode does not support the MPA rate limiter, you cannot enter an MPA configuration when the fabric switching mode is truncated.
The source VLAN cannot be changed if a VLAN filter is configured. Remove any VLAN filters before changing the source VLAN.
Filtering the Packets to be Captured

Several options are provided for filtering the packets to be captured. Filtering by ACL and VLAN is performed in hardware before any rate-limiting is applied; all other filters are executed in software. Software filtering can decrease the capture rate. To filter the packets to be captured by the Mini Protocol Analyzer, perform this task in capture session configuration mode: Command
Router(config-mon-capture)# filter access-group {acl_number | acl_name} Router(config-mon-capture)# filter vlan {vlan_ID | vlan_list | vlan_range | mixed_vlan_list} Router(config-mon-capture)# filter ethertype type
Purpose (Optional) Captures only packets from the specified ACL. (Optional) Captures only packets from the specified source VLAN or VLANs. (Optional) Captures only packets of the specified EtherType. The type can be specified in decimal, hex, or octal.
69-3
Chapter 69 Starting and Stopping a Capture
Command
Step 4
Router(config-mon-capture)# filter length min_len [max_len]
Purpose (Optional) Captures only packets whose size is between min_len and max_len, inclusive. If max_len is not specified, only packets of exactly size min_len will be captured. The range for min_len is 0 to 9216 bytes and the range for max_len is 1 to 9216 bytes. (Optional) Captures only packets from the specified MAC address. Exits the configuration mode.
Step 5 Step 6
Router(config-mon-capture)# filter mac-address mac_addr
Router(config-mon-capture)# end
When configuring capture filtering, note the following information:
The filter vlan argument is either a single VLAN number from 1 through 4094 (except reserved VLANs), or a range of VLANs described by two VLAN numbers (the lesser one first, separated by a dash), or a list of VLANs and ranges.
Note
When configuring a filter VLAN list, you must enter a space before and after the comma. When configuring a filter VLAN range, you must enter a space before and after the dash. Note that this requirement differs from the requirement for source VLAN lists and ranges described in the preceding section.
To enter an EtherType as a decimal number, enter the number (1 to 65535) with no leading zero. To enter a hexadecimal number, precede four hexadecimal characters with the prefix 0x. To enter an octal number, enter numeric digits (0 to 7) with a leading zero. For example, the 802.1Q EtherType can be entered in decimal notation as 33024, in hexadecimal as 0x8100, or in octal as 0100400. Enter a MAC address as three 2-byte values in dotted hexadecimal format. An example is 0123.4567.89ab. The no keyword removes the filter.
Note
After removing a VLAN filter using the no keyword, you must exit configuration mode, reenter the capture configuration mode, and issue the source vlan command before making other capture configuration changes.
When you configure a VLAN filter, the capture source or destination must be a VLAN. When you configure a port filter, the capture source or destination must be a port.
Starting and Stopping a Capture

The commands to start and stop a capture are not stored as configuration settings. These commands are executed from the console in EXEC mode. You can start a capture immediately or you can set a future date and time for the capture to start. The capture ends when one of the following conditions occurs:

A stop or clear command is entered from the console. The capture buffer becomes full, unless it is configured as a circular buffer. The optionally specified number of seconds has elapsed.
69-4
OL-13013-06
Chapter 69
Using the Mini Protocol Analyzer Starting and Stopping a Capture
The optionally specified number of packets has been captured.
When the capture stops, the SPAN session is ended and no further capture session packets are forwarded to the processor. When starting a packet capture, you have the option to override some configured settings. To start, stop, or cancel a capture, perform this task: Command
Step 1
Router# monitor capture [buffer size buf_size][length cap_len][linear | circular][filter acl_number | acl_name] {start [for count (packets | seconds}] | schedule at time date}
Purpose Starts a capture with optional run-time configuration changes. The capture can start immediately or it can start at a specified time and date.

The buffer size option overrides the configured or default capture buffer size. The length option determines the number of bytes that will be captured from each packet. The range for cap_len is 0 to 9216 bytes; the default is 68 bytes. A value of 0 causes the entire packet to be captured. The circular option specifies that the capture buffer will overwrite earlier entries once it fills. The linear option specifies that the capture will stop when the buffer fills. The default is linear. The filter option applies the specified ACL. The for option specifies that the capture will end after the specified number of seconds has elapsed or the specified number of packets has been captured.
Step 2 Step 3
Router# monitor capture stop Router# monitor capture clear [filter]
Stops the capture. Clears any run-time configuration settings, clears any pending scheduled capture, and clears the capture buffer. The filter option clears only the run-time filter settings.
When using these commands, note the following information:
The format for time and date is hh:mm:ss dd mmm yyyy. The hour is specified in 24-hour notation, and the month is specified by a three-letter abbreviation. For example, to set a capture starting time of 7:30 pm on October 31, 2006, use the notation 19:30:00 31 oct 2006. The time zone is GMT. When you specify a capture filter ACL in the start command, the new ACL will not override any configured ACLs. The new ACL will execute in software.
69-5
Chapter 69 Displaying and Exporting the Capture Buffer
Displaying and Exporting the Capture Buffer

To display the captured packets or information about the capture session, or to export the captured packets for analysis, perform this task: Command
Router# show monitor capture Router# show monitor capture status
Purpose Displays the capture session configuration. Displays the capture session state, mode, and packet statistics. Displays the capture buffer contents.
Router# show monitor capture buffer [start [end]] [detail][dump [nowrap [dump_length]] [acl acl_number | acl_name]]
The start and end parameters specify packet number indices in the capture buffer. When a start index is specified with no end index, only the single packet at the start index is displayed. When both the start and end indices are specified, all packets between these indices are displayed. The range is 1 to 4294967295. The detail option adds expanded and formatted protocol and envelope information for each packet, including the packet arrival time. The dump option displays the hexadecimal contents of the packet. If nowrap is specified with dump_length, one line of hexadecimal packet content of dump_length characters will be displayed for each packet. If dump_length is not specified, a line of 72 characters will be displayed. The range of dump_length is 14 to 256. The acl option causes the display of only those packets that match the specified ACL.
Step 4 Step 5
Router# show monitor capture buffer [start [end]] brief [acl acl_number | acl_name] Router# monitor capture export buffer url
Displays only packet header information. Copies the contents of the capture buffer to the specified file system or file transfer mechanism.
69-6
OL-13013-06
Chapter 69
Using the Mini Protocol Analyzer Mini Protocol Analyzer Configuration, Operation, and Display Examples
Mini Protocol Analyzer Configuration, Operation, and Display Examples

This section provides examples for configuring the Mini Protocol Analyzer, for starting and stopping a capture session, and for displaying the results of a capture session.
General Configuration Examples

This example shows how to minimally configure the Mini Protocol Analyzer:
Router# Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# monitor session 1 type capture Router(config-mon-capture)# end Router# show mon cap Capture instance [1] : ====================== Capture Session ID : 1 Session status : up rate-limit value : 10000 redirect index : 0x807 buffer-size : 2097152 capture state : OFF capture mode : Linear capture length : 68 Router#
This example shows how to configure the buffer size, session description, and rate limit:
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# monitor session 1 type capture Router(config-mon-capture)# buffer-size 4096 Router(config-mon-capture)# description Capture from ports, no filtering. Router(config-mon-capture)# rate-limit 20000 Router(config-mon-capture)# end Router# Router# show monitor capture Capture instance [1] : ====================== Capture Session ID : 1 Session status : up rate-limit value : 20000 redirect index : 0x807 buffer-size : 4194304 capture state : OFF capture mode : Linear capture length : 68 Router#
This example shows how to configure the source as a mixed list of ports:
Router(config-mon-capture)# source interface gig 3/1 - 3 , gig 3/5
69-7
Chapter 69 Mini Protocol Analyzer Configuration, Operation, and Display Examples
This example shows how to configure the source as a mixed list of VLANs:
Router(config-mon-capture)# source vlan 123,234-245
Filtering Configuration Examples

This example shows how to configure for capturing packets with the following attributes:

The packets belong to VLANs 123 or 234 through 245 The packets are of 802.1Q EtherType (hexadecimal 0x8100, decimal 33024) The packet size is exactly 8192 bytes The source MAC address is 01:23:45:67:89:ab The packets conform to ACL number 99
Router# configure terminal Enter configuration commands, one per line. End with CNTL/Z. Router(config)# monitor session 1 type capture Router(config-mon-capture)# source vlan 123,234-245 Router(config-mon-capture)# filter ethertype 0x8100 Router(config-mon-capture)# filter length 8192 Router(config-mon-capture)# filter mac-address 0123.4567.89ab Router(config-mon-capture)# filter access-group 99 Router(config-mon-capture)# end Router# show monitor capture Capture instance [1] : ====================== Capture Session ID : 1 Session status : up rate-limit value : 20000 redirect index : 0x7E07 Capture vlan : 1019 buffer-size : 4194304 capture state : OFF capture mode : Linear capture length : 68 Sw Filters : ethertype : 33024 src mac : 0123.4567.89ab Hw acl : 99 Router# show monitor session 1 Session 1 --------Type : Capture Session Description : capture from ports Source VLANs : Both : 123,234-245 Capture buffer size : 4096 KB Capture rate-limit value : 20000 Capture filters : ethertype : 33024 src mac : 0123.4567.89ab acl : 99 Egress SPAN Replication State: Operational mode : Centralized Configured mode : Distributed (default)
69-8
OL-13013-06
Chapter 69
Router#
This example shows how to capture packets whose size is less than 128 bytes:
Router(config-mon-capture)# filter length 0 128
This example shows how to capture packets whose size is more than 256 bytes:
Router(config-mon-capture)# filter length 256 9216
Operation Examples
This example shows how to start and stop a capture:
Router# monitor capture start Router# monitor capture stop Router#
This example shows how to start a capture to end after 60 seconds:

Router# monitor capture start for 60 seconds Router#
This example shows how to start a capture at a future date and time:
Router# monitor capture schedule at 11:22:33 30 jun 2008 capture will start at : <11:22:33 UTC Mon Jun 30 2008> after 32465825 secs Router#
This example shows how to start a capture with options to override the buffer size and to change to a circular buffer:
Router# monitor capture buffer size 65535 circular start Router#
This example shows how to export the capture buffer to an external server and a local disk:
Router# monitor capture export buffer tftp://server/user/capture_file.cap Router# monitor capture export buffer disk1:capture_file.cap
Display Examples
These examples show how to display configuration information, session status, and capture buffer contents.
Displaying the Configuration

To display the capture session configuration, enter the show monitor capture command.
Router# show monitor capture Capture instance [1] : ====================== Capture Session ID : 1 Session status : up rate-limit value : 10000 redirect index : 0x807 buffer-size : 2097152
69-9
capture state capture mode capture length
: OFF : Linear : 68
This example shows how to display more details using the show monitor session n command:
Router# show monitor session 1 Session 1 --------Type : Capture Session Source Ports : Both : Gi3/1-3,Gi3/5 Capture buffer size : 32 KB Capture filters : None Egress SPAN Replication State: Operational mode : Centralized Configured mode : Distributed (default)
This example shows how to display the full details using the show monitor session n detail command:
Router# show monitor session 1 detail Session 1 --------Type : Capture Session Description : Source Ports : RX Only : None TX Only : None Both : Gi3/1-3,Gi3/5 Source VLANs : RX Only : None TX Only : None Both : None Source RSPAN VLAN : None Destination Ports : None Filter VLANs : None Dest RSPAN VLAN : None Source IP Address : None Source IP VRF : None Source ERSPAN ID : None Destination IP Address : None Destination IP VRF : None Destination ERSPAN ID : None Origin IP Address : None IP QOS PREC : 0 IP TTL : 255 Capture dst_cpu_id : 1 Capture vlan : 0 Capture buffer size : 32 KB Capture rate-limit value : 10000 Capture filters : None Egress SPAN Replication State: Operational mode : Centralized Configured mode : Distributed (default)
69-10
OL-13013-06
Chapter 69
Displaying the Capture Session Status

To display the capture session status, enter the show monitor capture status command.
Router# capture capture Number show monitor state : mode : of packets received : dropped : captured : capture status ON Linear 253 0 90
Displaying the Capture Buffer Contents

To display the capture session contents, enter the show monitor capture buffer command. These examples show the resulting display using several options of this command:
Router# show monitor capture buffer 1 IP: s=10.12.0.5 , d=224.0.0.10, len 60 2 346 0180.c200.000e 0012.44d8.5000 88CC 020707526F7 3 60 0180.c200.0000 0004.c099.06c5 0026 42420300000 4 60 ffff.ffff.ffff 0012.44d8.5000 0806 00010800060 5 IP: s=7.0.84.23 , d=224.0.0.5, len 116 6 IP: s=10.12.0.1 , d=224.0.0.10, len 60
Router# show monitor capture buffer detail 1 Arrival time : 09:44:30 UTC Fri Nov 17 2006 Packet Length : 74 , Capture Length : 68 Ethernet II : 0100.5e00.000a 0008.a4c8.c038 0800 IP: s=10.12.0.5 , d=224.0.0.10, len 60, proto=88 2 Arrival time : 09:44:31 UTC Fri Nov 17 2006 Packet Length : 346 , Capture Length : 68 346 0180.c200.000e 0012.44d8.5000 88CC 020707526F757463031
Router# show monitor capture buffer dump 1 IP: s=10.12.0.5 , d=224.0.0.10, len 60 08063810: 0100 5E00000A ..^... 08063820: 0008A4C8 C0380800 45C0003C 00000000 ..$H@8..E@.<.... 08063830: 0258CD8F 0A0C0005 E000000A 0205EE6A .XM.....`.....nj 08063840: 00000000 00000000 00000000 00000064 ...............d 08063850: 0001000C 01000100 0000000F 0004 .............. 2 346 0180.c200.000e 0012.44d8.5000 88CC 020707526F757465720415 3 60 0180.c200.0000 0004.c099.06c5 0026 4242030000000000800000 4 60 ffff.ffff.ffff 0012.44d8.5000 0806 0001080006040001001244 5 IP: s=7.0.84.23 , d=224.0.0.5, len 116 0806FCB0: 0100 5E000005 ..^... 0806FCC0: 0015C7D7 AC000800 45C00074 00000000 ..GW,...E@.t.... 0806FCD0: 01597D55 07005417 E0000005 0201002C .Y}U..T.`......, 0806FCE0: 04040404 00000000 00000002 00000010 ................ 0806FCF0: 455D8A10 FFFF0000 000A1201 0000 E]............
Router# show 1 74 2 346 3 60 4 60
monitor capture 0100.5e00.000a 0180.c200.000e 0180.c200.0000 ffff.ffff.ffff
buffer dump nowrap 0008.a4c8.c038 0800 0012.44d8.5000 88CC 0004.c099.06c5 0026 0012.44d8.5000 0806
45C0003C000000 020707526F7574 42420300000000 00010800060400
69-11
Tip
69-12
OL-13013-06
PA R T
12
Appendixes
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 see Chapter 14, Configuring 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 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 affect the test results. The switch must be rebooted to bring the switch to normal operation. When you issue 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 the switch processor (SP), after the test is initiated and complete, you must reload or power down and then power up the switch. If you are running the tests on other modules, after the test is initiated and complete, you must reset the module.
Tip
The online diagnostic tests are included in these categories:

Global Health-Monitoring Tests, page A-2 Per-Port Tests, page A-6 PFC Layer 2 Forwarding Engine Tests, page A-13 DFC Layer 2 Forwarding Engine Tests, page A-16 PFC Layer 3 Forwarding Engine Tests, page A-21
A-1
Appendix A Global Health-Monitoring Tests
DFC Layer 3 Forwarding Engine Tests, page A-26 Replication Engine Tests, page A-32 Fabric Tests, page A-34 Exhaustive Memory Tests, page A-36 IPSEC Services Modules Tests, page A-39 Stress Tests, page A-41 Critical Recovery Tests, page A-42 General Tests, page A-44
Global Health-Monitoring Tests

These are the global health monitoring tests:

TestEARLInternalTables, page A-2 TestSPRPInbandPing, page A-3 TestScratchRegister, page A-3 TestMacNotification, page A-4 TestErrorCounterMonitor, page A-4 TestLtlFpoeMemoryConsistency, page A-5 TestMgmtPortsLoopback, page A-5 TestDataPortLoopback, page A-6
TestEARLInternalTables
The TestEARLInternalTables test detects most PFC and DFC hardware table problems by running consistency checks on the PFC and DFC hardware tables. The test runs every 5 minutes. A failure of the test for the PFC results in one of these actions:

Failover to the redundant supervisor engine. If a redundant supervisor engine is not installed, shutdown of the supervisor engine. Up to two resets of the DFC-equipped switching module. Shutdown following a third failure.
A failure of the test for a test of a DFC results in one of these actions:

A CallHome message is generated if CallHome is configured on the system.

Table A-1 TestEARLInternalTables Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default
Description Nondisruptive. Do not disable. On.
A-2
OL-13013-06
Appendix A
Online Diagnostic Tests Global Health-Monitoring Tests
Table A-1
TestEARLInternalTables Test Attributes (continued)
Attribute Release Corrective action Hardware support
Description 12.2(33)SXI2. Reset the affected module. PFC and DFCs.
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 A-2 TestSPRPInbandPing Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default Release Corrective action Hardware support
Description Nondisruptive. Do not disable. This 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.
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 A-3 TestScratchRegister Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default Release
Description Nondisruptive. Do not disable. On. 12.2(14)SX.
A-3
Appendix A Global Health-Monitoring Tests
Table A-3
TestScratchRegister Test Attributes (continued)
Attribute Corrective action Hardware support
Description 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.
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 A-4 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.
TestErrorCounterMonitor
The TestErrorCounterMonitor test monitors the errors/interrupts that occur on each module in the system by periodically polling for the error counters maintained in the module. If the errors exceed a threshold value, a syslog message is displayed with detailed information including the error-counter identifier, port number, total failures, consecutive failures, and the severity of the error counter.
Table A-5 TestErrorCounterMonitor Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes to maintain accuracy. On. 12.2(33)SXH.
A-4
OL-13013-06
Appendix A
Online Diagnostic Tests Global Health-Monitoring Tests
Table A-5
TestErrorCounterMonitor Test Attributes (continued)
Description Display a syslog message indicating the error-counters detected on that port. All modules including the supervisor engines.
TestLtlFpoeMemoryConsistency
The TestLtlFpoeMemoryConsistency test verifies that the LTL and FPOE memories are working properly. The test runs every 15 seconds. Self-correction is applied if an error is detected. If self-correction fails, corrective action is triggered through GOLD which is used to reset the module. The module is powered-down on the third consecutive module reset. If self-correction passes, no action is taken. If too many self-corrections occur within a short period of time, the module is reset.
Table A-6 TestLtlFpoeMemoryConsistency Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXI2. Failure of this test causes the module to reset and power down after two resets. All modules including the supervisor engines.
TestMgmtPortsLoopback
The TestMgmtPortsLoopback test sends a packet from the inband port of the supervisor to the Firewall or NAM service module to verify the health of the backplane ports. The packet is looped back to the supervisor in hardware. If the packet does not return from the supervisor, the service application is queried for the status of the packet and depending on the action suggested by the service module, a syslog message is displayed and the card is reset. The TestMgmtPortsLoopback test runs every 30 seconds.
Table A-7 TestMgmtPortsLoopback Test Attributes
Attribute Disruptive/Nondisruptive Recommendation
Description Nondisruptive. Do not disable. If the failure is isolated to the firewall module, then a syslog is printed indicating which port failed the test. If the test fails due to any other datapath issue for 10 consecutive times, the linecard is reset. If the test fails persistently, the module is powered down. On.
Default
A-5
Appendix A Per-Port Tests
Table A-7
TestMgmtPortsLoopback Test Attributes
Description 12.2(33)SXJ. None. Bennu and NAM service modules.
TestDataPortLoopback
The TestDataPortLoopback test sends a packet from the inband port of the supervisor to the data port on the Firewall or NAM service module to verify the data packet path. The packet is looped back to the supervisor in hardware. If the packet does not return from the supervisor, hardware counters are polled to isolate the faulty path. The TestDataPortLoopback test runs every 45 seconds.
Table A-8 TestDataPortLoopback Test Attributes
Description Nondisruptive. Do not disable. If the test fails for 10 consecutive times, the linecard is reset. If the test fails persistently, the module is powered down. On. 12.2(33)SXJ. None. Bennu and NAM service modules.
Default Release Corrective action Hardware support
Per-Port Tests
The per-port tests consist of the following tests:

TestNonDisruptiveLoopback, page A-7 TestLoopback, page A-7 TestActiveToStandbyLoopback, page A-8 TestUnusedPortLoopback, page A-8 TestTransceiverIntegrity, page A-9 TestNetflowInlineRewrite, page A-9 TestPortTxMonitoring, page A-10 TestSnrMonitoring, page A-10 TestDCPLoopback, page A-11 TestCCPLoopback, page A-11 TestNPLoopback, page A-12 TestMediaLoopback, page A-13
A-6
OL-13013-06
Appendix A
Online Diagnostic Tests Per-Port Tests
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 A-9 TestNonDisruptiveLoopback Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default Release Corrective action
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.
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 A-10 TestLoopback Test Attributes
Attribute Disruptive/Nondisruptive
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. 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.
Recommendation Default Release Corrective action Hardware support
A-7
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 A-11 TestActiveToStandbyLoopback Test Attributes
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.
TestUnusedPortLoopback
The TestUnusedPortLoopback test verifies the data path between the supervisor engine and the network ports of a module in the runtime periodically. In this test, a Layer 2 packet is flooded onto the VLAN associated with the test port and the supervisor engine inband port only. The packet loops back in the port and returns to the supervisor engine on the same VLAN. It's similar to TestLoopback but only runs on unused (admin down) network ports and only one unused port per port ASIC. This test substitutes the lack of nondisruptive loopback test in current ASICs and runs every 60 seconds.
Table A-12 TestUnusedPortLoopback Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes to maintain accuracy. On. 12.2(33)SXH
A-8
OL-13013-06
Appendix A
Table A-12
TestUnusedPortLoopback Test Attributes (continued)
Attribute Corrective action
Description Display a syslog message indicating the port(s) that failed. For modules other than supervisor engines, if all port groups fail (for example, at least one port per port ASIC fails more than the failure threshold for all port ASICs), the default action is to reset the module and power down the module after two resets. All modules including supervisor engines.
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 A-13 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.
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 A-14 TestNetflowInlineRewrite Test Attributes
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.
Recommendation Default Release
A-9
Table A-14
TestNetflowInlineRewrite Test Attributes (continued)
Description None. See the system message guide for more information. All modules including supervisor engines.
TestPortTxMonitoring
The test polls the transmit counters on each port periodically and displays a syslog and error disables the port if no activity is seen for the configured time interval and failure threshold. You configure the time interval and threshold by entering the diagnostic monitor interval and diagnostic monitor threshold commands. The test does not source any packets, but leverages the CDP protocol that transmits packets periodically. If CDP is disabled, the polling for that port is skipped. The test runs every 75 seconds and the failure threshold is set to 5 by default.
Table A-15 TestPortTxMonitoring Test Attributes
Description Nondisruptive. Do not disable. This test is automatically disabled during CPU-usage spikes. On. 12.2(33)SXH. Display a syslog message indicating the port(s) that failed. Error disable the port(s) that failed. All modules including the supervisor engines.
TestSnrMonitoring
The TestSnrMonitoring test monitors the health of the WS-X6716-10GT-3C and WS-X6716-10GT-3CXL linecards. The test is added to the WS-X6716-10GT-3C and WS-X6716-10GT-3CXL linecards for standalone and VSS (Virtual Switching Systems) setups. The SNR (signal-to-noise ratio) margin for a port varies between 12.7 dB to +12.7 dB. The test uses the following two threshold levels to compare SNR:

Minor threshold at +1.0 dB Major threshold at 0.0 dB
When the SNR value drops below the minor threshold, the test logs a minor warning message. When the SNR value drops below the major threshold, the test logs a major warning message. Similarly, recovery messages are logged when SNR recovers the two threshold levels. The default interval for the test is 30 seconds and can be configured to as low as 10 seconds for faster monitoring. The TestSnrMonitoring is not a bootup test and cannot be run on demand.
A-10
OL-13013-06
Appendix A
Table A-16
TestSnrMonitoring Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXI4. None. WS-X6716-10T.
TestDCPLoopback
The TestDCPLoopback test checks the data plane data path. The TestDCPLoopback test sends an online diagnostics packet from the supervisor engine to data ports on the Wireless Services Module (WiSM2). The TestDCPLoopback test checks whether the test packet loops back. If the test fails, a syslog message is displayed to indicate the error. The TestDCPLoopback test also can be run as health monitoring, on-demand, and scheduled tests.
Table A-17 TestDCPLoopback Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXJ. A syslog message is displayed after five consecutive failures. WS-SVC-WISM2-K9.
TestCCPLoopback
The TestCCPLoopback test checks the control plane data path. The TestCCPLoopback test sends an online diagnostics packet from the supervisor engine to service or high availability port on the Wireless Services Module (WiSM2). The TestCCPLoopback checks whether the test packet loops back. If the test fails, a syslog message is displayed to indicate the error. The TestCCPLoopback test also can be run as health monitoring, on-demand, and scheduled tests.
Table A-18 TestCCPLoopback Test Attributes
Attribute Disruptive/Nondisruptive Recommendation Default
Description Nondisruptive. Do not disable. On.
A-11
Table A-18
TestCCPLoopback Test Attributes (continued)
Description 12.2(33)SXJ. A syslog message is displayed after five consecutive failures. WS-SVC-WISM2-K9.
TestNPLoopback
The TestNPLoopback test checks the data path of the ACE30 module for data path errors. The TestNPLoopback test runs at bootup, and the default configuration is a health-monitoring test that runs every 15 seconds. If TestNPLoopback fails, an SCP (Switch-module Configuration Protocol) message is sent to the ACE30 module indicating which network processors have failed. Upon receipt of the SCP message, ACE30 will take corrective action. If the TestNPLoopback test fails for ten consecutive times, the ACE30 module is reset.
Table A-19 TestNPLoopback Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXJ. A syslog message is displayed to inform the ACE30 about the port(s) that failed the test on the failure code. Depending on the failure code, the ACE30 decides whether to take corrective action or not. The suggested action for ACE30 is to collect core dumps from all network processors and reset the ACE30 module. ACE30-MOD-K9.
Hardware support
A-12
OL-13013-06
Appendix A
Online Diagnostic Tests PFC Layer 2 Forwarding Engine Tests
TestMediaLoopback
The TestMediaLoopback test verifies the data path of MediaNet-like traffic. Index direct UDP packets are sent out to the MediaNet interface under test. The packets are looped back and forwarded to the inband port of the linecard.
Table A-20 TestMediaLoopback Test Attributes
Description Disruptive. Do not disable. Off. 12.2(33)SXJ. None. See the system message guide for more information. All C5 linecards supporting MediaNet.
PFC Layer 2 Forwarding Engine Tests

The PFC Layer 2 Forwarding Engine tests consist of the following tests:

TestNewIndexLearn, page A-13 TestDontConditionalLearn, page A-14 TestBadBpduTrap, page A-14 TestMatchCapture, page A-15 TestStaticEntry, page A-15
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-16.
Table A-21 TestNewIndexLearn 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.
Default Release
A-13
Appendix A PFC Layer 2 Forwarding Engine Tests
Table A-21
TestNewIndexLearn Test Attributes (continued)
Description None. See the system message guide for more information. Supervisor engines only.
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-16.
Table A-22 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. 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-16.
Table A-23 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.
A-14
OL-13013-06
Appendix A
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-16.
Table A-24 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.
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 A-25 TestStaticEntry Test Attributes
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.
Recommendation
A-15
Appendix A DFC Layer 2 Forwarding Engine Tests
DFC Layer 2 Forwarding Engine Tests

These are the DFC Layer 2 Forwarding Engine tests:

TestDontLearn, page A-16 TestNewLearn, page A-16 TestIndexLearn, page A-17 TestConditionalLearn, page A-18 TestTrap, page A-18 TestBadBpdu, page A-19 TestProtocolMatchChannel, page A-19 TestCapture, page A-20 TestStaticEntry, page A-20
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.
Table A-26 TestDontLearn Test Attributes
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
A-16
OL-13013-06
Appendix A
Online Diagnostic Tests DFC Layer 2 Forwarding Engine Tests
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 A-27 TestNewLearn Test Attributes
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 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 A-28 TestIndexLearn Test Attributes
A-17
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 A-29 TestConditionalLearn Test Attributes
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 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 A-30 TestTrap Test Attributes
A-18
OL-13013-06
Appendix A
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 A-31 TestBadBpdu Test Attributes
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. The Match feature is verified during the diagnostic packet lookup by the Layer 2 forwarding engine.
Table A-32 TestProtocolMatchChannel Test Attributes
A-19
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 A-33 TestCapture Test Attributes
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.
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 A-34 TestStaticEntry Test Attributes
A-20
OL-13013-06
Appendix A
PFC Layer 3 Forwarding Engine Tests

These are the PFC Layer 3 Forwarding Engine tests:

TestFibDevices, page A-21 TestIPv4FibShortcut, page A-22 TestIPv6FibShortcut, page A-22 TestMPLSFibShortcut, page A-23 TestNATFibShortcut, page A-23 TestL3Capture2, page A-24 TestAclPermit, page A-24 TestAclDeny, page A-25 TestQoS, page A-26
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.
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 A-35
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.
A-21
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 A-36 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-22
OL-13013-06
Appendix A
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 A-38 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 A-39 TestNATFibShortcut Test Attributes
Description Nondisruptive. 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.
A-23
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 A-40 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 A-41 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-24
OL-13013-06
Appendix A
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 A-42 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 A-43 TestNetflowShortcut Test Attributes
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.
A-25
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 A-44 TestQoS Test Attributes
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

These are the DFC Layer 3 Forwarding Engine tests:

TestFibDevices, page A-26 TestIPv4FibShortcut, page A-27 TestIPv6FibShortcut, page A-28 TestMPLSFibShortcut, page A-28 TestNATFibShortcut, page A-29 TestL3Capture2, page A-29 TestAclPermit, page A-30 TestAclDeny, page A-30 TestQoS, page A-31 TestNetflowShortcut, page A-31 TestAclFpgaMonitor, page A-32
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-26
OL-13013-06
Appendix A
Table A-45
TestFibDevices Test Attributes
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.
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.
A-27
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.
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 A-48 TestMPLSFibShortcut Test Attributes
A-28
OL-13013-06
Appendix A
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.
Table A-49 TestNATFibShortcut Test Attributes
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 A-50 TestL3Capture2 Test Attributes
A-29
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.
Table A-51 TestACLPermit Test Attributes
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 A-52 TestACLDeny Test Attributes
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.
A-30
OL-13013-06
Appendix A
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 A-53 TestQoS Test Attributes
Description Disruptive for looped-back ports. The disruption is typically less than one second. 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 A-54 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.
A-31
Appendix A Replication Engine Tests
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-55 TestAclFpgaMonitor Test Attributes
Description NonDisruptive. Do not disable. On. 12.2(33)SXI4, 12.2(18)SXF17a. 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

These are the Replication Engine tests:

TestL3VlanMet, page A-32 TestIngressSpan, page A-33 TestEgressSpan, page A-33
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 A-56 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.
A-32
OL-13013-06
Appendix A
Online Diagnostic Tests Replication Engine Tests
Table A-56
TestL3VlanMet Test Attributes (continued)
Description 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.
Table A-57 TestIngressSpan Test Attributes
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 A-58 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.
A-33
Appendix A Fabric Tests
Fabric Tests
These are the Fabric tests:

TestFabricSnakeForward, page A-34 TestFabricSnakeBackward, page A-34 TestSynchedFabChannel, page A-35 TestFabricCh0Health, page A-36 TestFabricCh1Health, page A-36
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 A-59 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
A-34
OL-13013-06
Appendix A
Online Diagnostic Tests Fabric Tests
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 A-60 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.
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 A-61 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.
Hardware support
A-35
Appendix A Exhaustive Memory Tests
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 A-62 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.
Table A-63 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-37 TestAsicMemory, page A-37 TestAclQosTcam, page A-38
A-36
OL-13013-06
Appendix A
Online Diagnostic Tests Exhaustive Memory Tests
TestNetflowTcam, page A-38 TestQoSTcam, page A-39
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 14-3.
TestFibTcamSSRAM
The TestFibTcamSSRAM test checks the FIB TCAM and Layer 3 Adjacency SSRAM memory.
Table A-64 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. Not applicable. All modules including supervisor engines.
TestAsicMemory
The TestAsicMemory test uses an algorithm to test the memory on a module.
Table A-65 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.
A-37
Appendix A Exhaustive Memory Tests
TestAclQosTcam
The TestAclQosTcam test tests all the bits and checks the location of both ACL and QOS TCAMs on the PFC. It is not supported on the PFC3A.
Table A-66 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.
TestNetflowTcam
The TestNetflowTcam test tests all the bits and checks the location of the Netflow TCAM.
Table A-67 TestNetflowTcam Test Attributes
Description Disruptive. Disruption is several minutes and can vary depending on the version of the PFC. 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-38
OL-13013-06
Appendix A
Online Diagnostic Tests IPSEC Services Modules Tests
TestQoSTcam
The TestQoSTcam test performs exhaustive memory tests for QoS TCAM devices.
Table A-68 TestQoSTcam Test Attributes
Description Disruptive. Disruption is several minutes and can vary depending on the version of the PFC. 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.
IPSEC Services Modules Tests

The IPSEC Services Modules Tests include the following tests:

TestIPSecClearPkt, page A-39 TestHapiEchoPkt, page A-40 TestIPSecEncryptDecryptPkt, page A-40
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 A-69 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.
A-39
Appendix A IPSEC Services Modules Tests
Table A-69
TestIPSecClearPkt Test Attributes (continued)
Description 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 A-70 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.
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 A-71 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.
A-40
OL-13013-06
Appendix A
Online Diagnostic Tests Stress Tests
Stress Tests
The stress tests consist of the following tests:

TestTrafficStress, page A-41 TestEobcStressPing, page A-41 TestMicroburst, page A-42
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 A-72 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.
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 A-73 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.
A-41
Appendix A Critical Recovery Tests
TestMicroburst
The TestMicroburst test monitors packet microbursts in the port ASICs and logs them to SEA unless consecutive failures reach the threshold.
Table A-74 TestMicroburst Test Attributes
Description Nondisruptive. Do not disable. On. 12.2(33)SXJ. Not applicable. C5 linecards that support MediaNet.
Critical Recovery Tests

The critical recovery tests consist of the following tests:

TestL3HealthMonitoring, page A-42 TestTxPathMonitoring, page A-43 TestSynchedFabChannel, page A-43
The TestFabricCh0Health and TestFabricCh1Health tests are also considered critical recovery tests. See the Fabric Tests section on page A-34 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 A-75 TestL3HealthMonitoring Test Attributes
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. Do not disable. Off. 12.2(14)SX.
Recommendation Default Release
A-42
OL-13013-06
Appendix A
Online Diagnostic Tests Critical Recovery Tests
Table A-75
TestL3HealthMonitoring Test Attributes (continued)
Description 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 A-76 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 A-77 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-43
Appendix A General Tests
General Tests
The general tests consist of the following tests:

ScheduleSwitchover, page A-44 TestFirmwareDiagStatus, page A-44 TestCFRW, page A-45
ScheduleSwitchover
The ScheduleSwitchover test allows you to trigger a switchover at any time using the online diagnostics scheduling capability.
Table A-78 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 A-79 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-44
OL-13013-06
Appendix A
Online Diagnostic Tests General Tests
TestCFRW
The TestCFRW test verifies the CompactFlash disk or disks on the supervisor engine. This test is performed during system boot-up or whenever a disk is inserted. A 128-byte temporary file is written to each disk present in the slot and read back. The content read back is checked and the temporary file is deleted. You can also execute this test from the CLI.
Table A-80 TestCFRW Test Attributes
Description Nondisruptive. Do not disable. No traffic is affected. On. 12.2(33)SXH. Format or replace the failed CompactFlash. External CompactFlash on the active and the standby Supervisor Engine 720 and Supervisor Engine 32.
Tip
A-45
Appendix A General Tests
A-46
OL-13013-06
A P P E N D I X
Acronyms
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 BSTUN BUS BVI CAM CAR CCA CDP
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 Block Serial Tunnel broadcast and unknown server bridge-group virtual interface content-addressable memory committed access rate circuit card assembly Cisco Discovery Protocol
B-1
Appendix B
Acronyms
Table B-1
List of Acronyms (continued)
Acronym 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 DOS dot1q DRAM DRiP DSAP DSCP DSPU
Expansion 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 denial of service 802.1Q dynamic RAM Dual Ring Protocol destination service access point differentiated services code point downstream SNA Physical Units
B-2
OL-13013-06
Appendix B
Acronyms
Table B-1
Acronym DTP DTR DWRR 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 IGMP IGRP ILMI IP IPC IPX
Expansion Dynamic Trunking Protocol data terminal ready deficit weighted round robin 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 Internet Group Management Protocol Interior Gateway Routing Protocol Integrated Local Management Interface Internet Protocol interprocessor communication Internetwork Packet Exchange
B-3
Appendix B
Acronyms
Table B-1
Acronym IS-IS ISL ISO ISR IST LAN LANE LAPB LCP LDA LEC LECS LEM LER LES LLC LTL MAC MD5 MDS MDT MEC MFD MIB MII MLD MLS MLSE MLSE MOP MOTD MRM MSDP MSFC MSFC
Expansion 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 distributed switching multicast distribution tree multichassis EtherChannel multicast fast drop Management Information Base media-independent interface Multicast Listener Discovery Multilayer Switching maintenance loop signaling entity maintenance loops signaling entity Maintenance Operation Protocol message-of-the-day multicast routing monitor Multicast Source Discovery Protocol Multilayer Switch Feature Card Multilayer Switching Feature Card
B-4
OL-13013-06
Appendix B
Acronyms
Table B-1
Acronym MSM MST MTI MTU MVAP MVPN MVR MVRF NAC NAM NBAR NBP NCIA NDE NET NetBIOS NFFC NMP NSAP NSF NTP NVRAM OAM ODM OSI OSM OSPF PACL PAE PAgP PBD PC PCM PCR PDP PDU
Expansion Multilayer Switch Module multiple spanning tree multicast tunnel interface maximum transmission unit multiple VLAN access port multicast virtual private network mulitcast VLAN registration multicast VRF Network Admission Control Network Analysis Module Network-Based Application Recognition 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 control list 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
B-5
Appendix B
Acronyms
Table B-1
Acronym PEP PFC PGM PHY PIB PIM PPP PRID PVID 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
Expansion policy enforcement point Policy Feature Card Pragmatic General Multicast physical sublayer policy information base protocol independent multicast Point-to-Point Protocol Policy Rule Identifiers Port VLAN identifier 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
B-6
OL-13013-06
Appendix B
Acronyms
Table B-1
Acronym SDM SEA SGBP SIMM SLB SLCP SLIP SMDS SMF SMP SMRP SMT SNAP SNMP SPAN SREC SRM SRR SSM SSO SSTP STP SVC SVI TACACS+ TARP TCAM TCL TCP/IP TFTP TIA TLV TopN TOS TTL TVX
Expansion Secure Device Manager System Event Archive 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 software MAC filter Standby Monitor Present Simple Multicast Routing Protocol Station Management Subnetwork Access Protocol Simple Network Management Protocol Switched Port Analyzer S-Record format, Motorola defined format for ROM contents single router mode shaped round robin source-specific multicast stateful switchover 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 type-length-value Utility that allows the user to analyze port traffic by reports type of service Time To Live valid transmission
B-7
Appendix B
Acronyms
Table B-1
Acronym UDLD UDP UNI URD UTC UUFB UUFRL VACL VCC VCI VCR VINES VLAN VMPS VPN VRF VTP VVID WAN WCCP WFQ WoL WRED WRR XNS
Expansion UniDirectional Link Detection Protocol User Datagram Protocol User-Network Interface URL Rendezvous Directory Coordinated Universal Time unknown unicast flood blocking unknown unicast flood rate limiting VLAN access control list virtual channel circuit virtual circuit identifier Virtual Configuration Register Virtual Network System virtual LAN 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 wake-on LAN weighted random early detection weighted round-robin Xerox Network System
B-8
OL-13013-06
INDEX
Numerics
4K VLANs (support for 4,096 VLANs) 802.1AE Tagging 802.1Q encapsulation
16-4 47-2 22-2
abbreviating commands
2-5 44-1, 45-1, 46-1, 49-1, 50-1 46-2
access control entries and lists access port, configuring accounting with 802.1x ACEs and ACLs ACLs downloadable
16-5 58-7 57-46 57-12 16-16
access-enable host timeout (not supported)
Layer 2 protocol tunneling See Layer 2 protocol tunneling mapping to ISL VLANs trunks
16-3 22-7, 22-10
with IEEE 802.1x
44-1, 45-1, 46-1, 49-1
restrictions tunneling
downloadable (dACLs) Filter-ID

25-3 25-6 57-20 57-20
57-19
configuration guidelines configuring tunnel ports overview 802.1Q Ethertype specifying custom 802.1X See port-based authentication 802.1x accounting 802.3ad See LACP 802.3af. See PoE. 802.3x Flow Control
9-13 57-46 16-18 25-1
per-user port
defined redirect URL static sharing acronyms, list of aggregate label
48-2 57-21 57-21 A-1, B-1 21-3
advertisements, VTP aggregate policing see QoS policing aging time accelerated for MSTP
31-2, 31-4
27-47
A
AAA
44-1, 45-1, 46-1, 49-1, 50-1 57-4, 58-4
maximum for MSTP aging-time IP MLS alarms major minor

11-12 11-12 60-8 27-48
fail policy
AAA (authentication, authorization, and accounting). See also port-based authentication. 57-1, 58-2 aaa accounting dot1x command aaa accounting system command
57-47 57-47
Allow DHCP Option 82 on Untrusted Port
IN-1
Index
configuring understanding
51-10 51-3 31-17 31-19
binding database, DHCP snooping See DHCP snooping binding database binding table, DHCP snooping See DHCP snooping binding database blocking floods BPDU RSTP format BPDU guard See STP BPDU guard BPDUs Bridge Assurance Bridge Assurance description
28-3 to 28-5 28-3 28-3 28-3 28-12 27-16 55-1 27-7
any transport over MPLS (AToM) Ethernet over MPLS ARP ACL AToM audience
40-70 53-1 31-19
compatibility with previous releases of AToM
blocking state, STP
ARP spoofing
31-17
1-xxxix
Authentication, Authorization, and Accounting See AAA Authentication, Authorization, and Accounting (AAA) 49-1, 50-1 authentication control-direction command authentication event command authentication failed VLAN See restricted VLAN authentication open comand authentication password, VTP
57-11 21-4 57-41, 57-55 57-48 57-41 57-48 57-58
Shared Spanning Tree Protocol (SSTP)
inconsistent state bridge groups bridge ID See STP bridge ID bridge priority, STP see BPDUs bridging
41-3 29-2 29-2
supported protocols and link types
authentication periodic command
authentication port-control command authorized ports with 802.1X auto enablement automatic QoS
57-27 57-8
27-35
authentication timer reauthenticate command
bridge protocol data units
broadcast storms see traffic-storm control
configuration guidelines and restrictions macros overview AutoQoS

41-1 7-4 41-3 41-1
C
Call Home description messages
62-2 62-2
auto-sync command auxiliary VLAN See voice VLAN
message format options format options call home

62-1 62-13 62-4 62-2
B
BackboneFast See STP BackboneFast backup interfaces See Flex Links
alert groups
contact information default settings

62-3
destination profiles
62-5
IN-2
OL-13013-06
Index
displaying information pattern matching rate limit messages severity threshold SMTP server
62-4 62-16
62-23
command
18-9, 18-14, 18-15 18-9, 18-15
command example See CDP
periodic notification
62-15 62-11 62-15 62-3
Cisco Discovery Protocol Cisco Emergency Responder Cisco EnergyWise

12-1 31-3 15-6
smart call home feature testing communications call home alert groups configuring description subscribing
62-13 62-14 62-14
Cisco Express Forwarding

62-16
Cisco Group Management Protocol See CGMP Cisco IOS Unicast Reverse Path Forwarding CISP
57-27 44-2
CIST regional root See MSTP CIST root See MSTP class command
40-74 40-66 40-71 57-43 62-4
call home customer information entering information attributes description displaying

62-6 62-6 62-25
call home destination profiles
class-map command
class map configuration

62-37 62-37
call home notifications full-txt format for syslog XML format for syslog CDP host presence detection CEF
32-1 57-10, 59-3 15-2
clear authentication sessions command clear counters command clear dot1x command clear interface command
9-18 57-43 9-18
clear mls ip multicast statistics command clears IP MMLS statistics CLI accessing
2-2 2-5 2-5 35-28
to configure Cisco phones configuring RP examples

32-5 32-5
backing out one level
supervisor engine
32-3 32-2
console configuration mode getting list of commands global configuration mode history substitution
2-4 2-5
Layer 3 switching packet rewrite CEF for PFC2 See CEF

32-2
2-5
interface configuration mode privileged EXEC mode

62-4 2-5
2-5
certificate authority (CA) CGMP

36-8
ROM monitor software basics

36-13
2-7 2-4
disabling automatic detection Change of Authorization See CoA channel-group group
Client Information Signalling Protocol See CISP CoA description

57-24
IN-3
Index
command line processing commands class-map

31-11, 31-12
2-3
CoS override priority counters

15-9, 15-10
commands, getting list of community ports

23-3
2-5 40-2
clearing interface critical authentication CSCsr62404

29-2 9-14 46-8 40-51
9-18 57-4 57-51
Committed Access Rate (CAR), not supported community VLANs

23-2, 23-3
critical authentication, IEEE 802.1x CSCtc21076 CSCtd34068

31-20, 31-23 31-21 9-2
Concurrent routing and bridging (CRB) configuration example EoMPLS port mode EoMPLS VLAN mode configure terminal command configuring
40-73 2-5
CSCte40004 CSCte95941
40-51, 48-12 40-53
customer contact information entering for call home

62-4
console configuration mode control plane policing See CoPP CoPP

50-1
D
dACL
50-3
applying QoS service policy to control plane configuring ACLs to match traffic enabling MLS QoS service-policy map entering displaying dynamic information rate information monitoring statistics overview
50-1 50-4 50-4 50-4 50-3 50-3 50-3 50-3
See ACLs, downloadable dCEF

32-4, 32-5
57-19
debug commands IP MMLS

35-28 29-2
packet classification criteria

50-3
DEC spanning-tree protocol default configuration 802.1X

57-33, 58-7
control plane configuration mode
dynamic ARP inspection Flex Links IP MMLS

50-4 17-2 35-9
53-5
number of conforming bytes and packets entering control plane configuration mode
50-4
MSTP MVR UDLD VTP
27-39 36-19 10-4 15-6
50-3
voice VLAN
21-8
packet classification guidelines traffic classification defining guidelines overview

50-6 50-7 50-6 50-7 50-6
default NDE configuration default VLAN

16-12
61-10
deficit weighted round robin denial of service protection See DoS protection description command
9-16 60-3
40-107
sample ACLs sample classes
destination-ip flow mask
IN-4
OL-13013-06
Index
destination-source-ip flow mask device IDs call home format

62-33, 62-34
60-3
overview
51-5 51-16 51-7, 51-14
reading from a TFTP file (example) DHCP snooping increased bindings limit differentiated services codepoint See QoS DSCP DiffServ configuring short pipe mode configuring uniform mode
51-5 42-34 42-39
DHCP binding database See DHCP snooping binding database DHCP binding table See DHCP snooping binding database DHCP option 82 circuit ID suboption overview
51-3
short pipe mode uniform mode
42-31 42-32 42-4
packet format, suboption circuit ID remote ID

51-5 51-5 51-5 51-10
DiffServ tunneling modes
Disabling PIM Snooping Designated Router Flooding 38-6 distributed Cisco Express Forwarding See dCEF distributed egress SPAN
57-11 65-5, 65-18 1-xxxix
remote ID suboption DHCP snooping 802.1X data insertion binding database
DHCP option 82 allow on untrusted port
documentation, related DoS protection
See DHCP snooping binding database configuration guidelines configuring

51-9 51-6 51-13 51-18 51-6
configuration guidelines and restrictions default configurations FIB glean rate limiters FIB receive rate limiters
49-13
49-14
egress ACL bridget packet rate limiters

49-9 49-9 49-10 49-8
49-7
default configuration
detecting spurious servers displaying binding tables enabling enabling the database agent message exchange process monitoring overview
52-4, 52-6
ICMP redirect rate limiters
51-9, 51-10, 51-11, 51-12, 51-13 51-14 51-4
IGMP unreachable rate limiters IP errors rate limiters

49-11
ingress ACL bridget packet rate limiters IPv4 multicast rate limiters
49-11 49-12 49-10
49-7
option 82 data insertion

51-1
51-3
IPv6 multicast rate limiters Layer 2 PDU rate limiters
Snooping database agent described entries

51-3
51-5
Layer 2 protocol tunneling rate limiters Layer 3 security features rate limiters monitoring packet drop statistics using monitor session commands using VACL capture MTU failure rate limiters
49-16 49-10
49-11 49-9
DHCP snooping binding database

51-3
49-15
DHCP snooping binding table See DHCP snooping binding database DHCP Snooping Database Agent adding to the database (example) enabling (example)
51-15 51-17
multicast directyly connected rate limiters multicast FIB miss rate limiters
49-11
49-11
multicast IGMP snooping rate limiters

49-10
OL-13013-06
IN-5
Index
network under SYN attack QoS ACLs

49-3 49-2 49-5 49-4
49-5
log buffer
53-13, 53-14 53-13 53-4, 53-9
logging system messages default configuration

49-8 49-2 53-5
security ACLs TCP intercept
rate limit for incoming ARP packets denial-of-service attacks, preventing described displaying
49-8 49-10 57-50 53-1 53-3 53-9
traffic storm control
TTL failure rate limiter uRPF check

49-4
understanding how it works uRPF failure rate limiters VACL log rate limiters dot1x critical command
DHCP snooping binding database ARP ACLs log buffer statistics

53-14
configuration and operating state

53-15 53-15 53-15
53-15
dot1x auth-fail max-attempts command

57-53
dot1x initialize interface command dot1x mac-auth-bypass command dot1x max-reauth-req command dot1x max-req command
57-45
57-42 57-54
trust state and rate limit function of log buffer clearing

57-42 53-15 53-13, 53-14 53-15 53-2 53-3
error-disabled state for exceeding rate limit interface trust states
53-4
57-46
dot1x pae authenticator command dot1x port-control command

57-48
57-35
dot1x re-authenticate interface command dot1x reauthentication command

57-41
configuring displaying
dot1x timeout quiet-period command dot1x timeout reauth-period command DSCP See QoS DSCP DSCP-based queue mapping duplex command duplex mode autonegotiation status configuring interface DWRR
40-107 9-9 9-7 9-8, 9-9 40-99
57-44 57-41
logging of dropped packets, described logging system messages configuring

53-13
53-5
man-in-the middle attack, described
53-2 53-3
network security issues and interface trust states priority of ARP ACLs and DHCP snooping entries 53-4 rate limiting of ARP packets configuring described statistics clearing displaying
53-15 53-15 53-11 53-9 53-4 53-4
dynamic ARP inspection ARP cache poisoning ARP spoofing attack clearing log buffer statistics configuring
error-disabled state
53-2 53-2
ARP requests, described

53-2
validation checks, performing

53-15 53-15 53-6
Dynamic Host Configuration Protocol snooping See DHCP snooping
configuration guidelines
IN-6
OL-13013-06
Index
E
EAC eFSU for a virtual switching system
4-55 47-2 57-1
performing steps
5-5
5-5, 5-14
usage guidelines and limitations verifying redundancy mode environmental monitoring LED indications SNMP traps
11-12 11-12 5-7
5-4
EAPOL. See also port-based authentication.
eFSU, See Enhanced Fast Software Upgrade (eFSU) eFSU. See enhanced Fast Software Upgrade (eFSU) Egress ACL support for remarked DSCP egress ACL support for remarked DSCP egress SPAN
65-5 40-13 40-61 35-15
supervisor engine and switching modules Syslog messages EOBC for MAC address table synchronization EoMPLS
31-17 31-19 31-19 31-18 11-12 11-10
11-12
using CLI commands
egress replication performance improvement e-mail addresses assigning for call home e-mail notifications Call Home enable mode enabling IP MMLS on router interfaces encapsulation EnergyWise
16-4 47-2 35-13 62-2 2-5 59-9 62-4
16-2
configuring
configuring VLAN mode guidelines and restrictions port mode

31-19
enable sticky secure MAC address
port mode configuration guidelines VLAN mode ERSPAN

65-1 31-19
31-23
EtherChannel channel-group group command

18-9, 18-14, 18-15 18-9, 18-15 4-31, 18-6
Endpoint Admission Control (EAC)

12-1
command example configuration guidelines

5-13
enhanced Fast Software Upgrade (eFSU) aborting (issu abortversion command) accepting the new software version
5-11
configuring Layer 2
18-8, 18-15 4-30, 18-7
commiting the new software to standby RP (issu commitversion command) 5-12 displaying maximum outage time for module error handling
5-4 5-10 5-10
configuring (tasks)
DFC restriction, see CSCdt27074 in the Release Notes interface port-channel command example
18-8 18-8
forcing a switchover (issu runversion command) issu loadversion command

5-8 5-8
interface port-channel (command) lacp system-priority command example Layer 2

18-11
loading new software onto standby RP memory reservation on module OIR not supported operation
5-2 5-3 5-4 5-3
memory reservation on module, prohibiting
5-3
configuring load balancing configuring understanding
18-8, 18-15
18-11 18-5
outage times
IN-7
Index
Min-Links modes PAgP

18-3
18-13, 18-14
FIB TCAM filters, NDE
31-3
destination host filter, specifying

18-3 18-5
61-17 61-16
understanding
destination TCP/UDP port, specifying protocol Flex Links

18-12 61-17
port-channel interfaces command STP

18-5 18-11
port-channel load-balance command example
source host and destination TCP/UDP port

17-1 17-2
61-16
configuration guidelines configuring

18-6 17-3
switchport trunk encapsulation dot1q understanding EtherChannel Guard See STP EtherChannel Guard Ethernet setting port duplex EoMPLS port mode EXP mutation See VLANs extended system ID MSTP
27-41 42-4 22-2 9-15 4-1, 18-1
default configuration description monitoring flood blocking flow control flow masks IP MLS destination-ip ip-full minimum overview flows IP MMLS
60-3 60-7 60-2, 61-3 17-1 17-4 55-1 9-13
17-2
Ethernet over MPLS (EoMPLS) configuration

31-23 31-20
60-3 60-3
EoMPLS VLAN mode extended range VLANs
destination-source-ip
Extensible Authentication Protocol over LAN. See EAPOL.
completely and partially switched forward-delay time MSTP

27-47 27-36
35-4
F
fabric switching mode See switch fabric module fabric switching-mode allow dcef-only command on Supervisor Engine 720 6-2 fabric switchover fall-back bridging fastethernet
9-2 6-9 6-9 29-2
forward-delay time, STP frame distribution
See EtherChannel load balancing FSU for a virtual switching system

4-55
G
global configuration mode guest VLAN and 802.1x guidelines
10-1 24-5 2-5 57-15
fast fabric switchover fast link notification on VSL failure
4-13
fiber-optic, detecting unidirectional links
IN-8
OL-13013-06
Index
H
hardware Layer 3 switching guidelines hello time MSTP
27-46 27-36 11-4 32-4
network admission control Layer 2 validation port security interoperability voice VLAN IEEE 802.3ad See LACP IEEE 802.3af. See PoE. IEEE 802.3x Flow Control
2-4 9-13 57-18 57-25 57-19 57-41
57-23
RADIUS-supplied session timeout wake-on-LAN support
hello time, STP history CLI host mode
High Capacity Power Supply Support
IEEE bridging protocol IGMP
29-2
see port-based authentication host ports kinds of

23-3 15-3, 57-10 59-3
configuration guidelines enabling

36-10
34-8, 36-7
Internet Group Management Protocol join messages enabling

36-2
36-1
host presence CDP message host presence TLV message http
leave processing
36-12
//www-tac.cisco.com/Teams/ks/c3/xmlkwery.php?srI d=612293409 18-6
queries
36-3
query interval configuring

36-11
I
ICMP unreachable messages IDs serial IDs IEEE 802.1Q See 802.1Q IEEE 802.1Q Ethertype specifying custom IEEE 802.1w See RSTP IEEE 802.1x accounting critical ports guest VLAN
57-12, 57-46 57-16 16-18 25-7 62-34 46-3
snooping fast leave

36-5 36-2, 37-2 36-4, 37-4
joining multicast group leaving multicast group understanding snooping querier enabling IGMPv3
35-11 35-11 36-9 36-2, 37-2 36-2, 37-2
understanding IGMP v3lite
IEEE 802.1Q Tagging on a Per-Port Basis
ignore port trust ingress SPAN inline power
40-9, 40-16, 40-58, 40-75 57-17
inaccessible authentication bypass

65-5 15-4
authentication failed VLAN

57-17 57-11
inline-power policing and override interface configuration mode

2-5
15-5 29-2
Integrated routing and bridging (IRB)
DHCP snooping
57-15 57-22
MAC authentication bypass
Layer 2 modes
16-4
IN-9
Index
number
9-2
minimum overview
18-8 18-8
60-7 60-2, 61-3
interface port-channel command example interfaces configuring

9-2 9-7
IP MMLS cache, overview debug commands

35-2 35-10
interface port-channel (command)
configuration guideline
35-28
configuring, duplex mode configuring, speed counters, clearing

9-7
default configuration enabling
35-9
configururing, overview
9-18
9-2
on router interfaces flows
35-13
descriptive name, adding maintaining monitoring naming range of restarting task

9-4 9-19 9-16 9-17 9-17
9-16 9-17
completely and partially switched Layer 3 MLS cache overview router enabling globally
35-11 35-13 35-2 35-3 35-2
35-4
displaying information about
packet rewrite
enabling on interfaces PIM, enabling

9-2 9-4, 64-2 9-6 35-12
shutting down
9-19
multicast routing table, displaying switch statistics, clearing unsupported features IP multicast IGMP snooping and MLDv2 snooping and
35-10 36-9 34-10 35-28 35-10
35-22
interfaces command
interfaces range command internal VLANs See IGMP

22-2
interfaces range macro command
Internet Group Management Protocol IP accounting, IP MMLS and IP CEF topology (figure)
32-4 61-14
overview
36-2, 37-1, 37-7
IP multicast MLS See IP MMLS ip multicast-routing command enabling IP multicast IP phone

60-3 35-12 60-11, 61-13, 61-14, 67-3,
ip flow-export destination command ip flow-export source command

67-4
ip-full flow mask ip http server IP MLS aging-time flow masks

1-6
configuring ip pim command
15-7
enabling IP PIM
60-8
35-12
IP Source Guard configuring

60-3 60-3 52-3 52-4
destination-ip ip-full
60-3
configuring on private VLANs displaying overview

52-4, 52-6 52-1
destination-source-ip
IN-10
OL-13013-06
Index
IP unnumbered
29-2 1-6
interface assignment Layer 2 Interfaces configuring

33-1 16-1 39-1
22-6
IPv4 Multicast over Point-to-Point GRE Tunnels IPv4 Multicast VPN IPv6 QoS ISL trunks isolated port
40-53 16-4
IPv6 Multicast PFC3 and DFC3 Layer 3 Switching ISL encapsulation

16-3 23-3 23-2, 23-3
Layer 2 protocol tunneling configuring Layer 2 tunnels overview

26-1 40-15 68-1 26-2
Layer 2 remarking Layer 2 Traceroute Layer 2 traceroute and ARP

68-2 68-2 68-1
isolated VLANs
J
join messages, IGMP jumbo frames
9-10 36-2
and CDP described
IP addresses and subnets multicast traffic

68-2
68-2 68-2
MAC addresses and VLANs multiple devices on a port
68-2
K
keyboard shortcuts
2-3
unicast traffic Layer 3
68-1 68-2
usage guidelines
IP MMLS and MLS cache
35-2
L
label edge router label switched path label switch router LACP system ID Layer 2 configuring interfaces access port trunk defaults
16-10 16-5 16-4 9-12, 9-13, 16-7, 16-15 16-16 16-6 18-4 31-2 31-19 31-2, 31-3
Layer 3 switched packet rewrite CEF CEF

32-2
Layer 3 switching
32-2 46-10
Layer 4 port operations (ACLs) leave processing, IGMP enabling enabling LERs Link Failure detecting unidirectional link negotiation link redundancy
16-1 9-8 36-12
leave processing, MLDv2

34-12 42-2, 42-6, 42-7
interface modes show interfaces switching
27-25
understanding trunks understanding VLAN
See Flex Links Load Balancing

31-8 35-15
16-3
Local Egress Replication logical operation unit See LOU
IN-11
Index
loop guard See STP loop guard LOU description LSRs

42-2, 42-6 46-11 46-11
MLD snooping query interval configuring MLDv1 MLDv2

34-8 34-1 34-10 34-12
determining maximum number of
enabling
leave processing
M
mab command
57-48, 57-54 44-2 16-8 16-3
enabling queries snooping fast leave

34-5
34-12
MAC address-based blocking MAC address table notification
34-7 34-4 34-6
joining multicast group leaving multicast group understanding snooping querier enabling MLDv2 Snooping MLS
34-9 34-2 34-2
mac-address-table synchronize command
MAC authentication bypass. See also port-based authentication. 57-22 MAC move (port security) macros MACSec
3-1 59-2
understanding
34-1
See Smartports macros

47-2 57-25 7-4 22-7, 22-10
magic packet
configuring threshold RP threshold mls aging command configuring IP MLS mls flow command configuring IP MLS
27-37 27-48 35-16
35-16
main-cpu command markdown
mapping 802.1Q VLANs to ISL VLANs see QoS markdown maximum aging time MSTP
27-48
60-9
60-8, 60-12, 61-12
maximum aging time, STP maximum hop count, MSTP MEC configuration described failure
4-14 4-15 4-45
mls ip multicast command enabling IP MMLS mls nde flow command configuring a host and port filter configuring a host flow filter configuring a port filter
61-16 61-17 61-16 61-17 35-13 to 35-25
port load share deferral microflow policing rule see QoS policing Mini Protocol Analyzer Min-Links MLD report
34-4 18-13 69-1
4-16
configuring a protocol flow filter mls nde sender command monitoring Flex Links MVR MPLS
17-4 36-23, 36-24 23-17 61-11
private VLANs
31-1, 31-2
IN-12
OL-13013-06
Index
aggregate label
31-2 31-17
class map to classify MPLS packets MPLS VPN limitations and restrictions MQC
42-30 40-1 31-14 31-8
42-20
any transport over MPLS basic configuration core egress

31-3
DiffServ Tunneling Modes

31-4 42-3
not supported CAR

40-2 40-2
experimental field
queuing
31-7 31-4
guidelines and restrictions hardware-supported features ingress labels

31-3 31-3
supported policy maps MST interoperation with Rapid PVST+ root bridge
28-12 28-11 40-3
IP to MPLS path
31-2
Layer 2 VPN load balancing MPLS to IP path nonaggregate lable supported commands VPN
42-12 31-4 31-3 31-2
31-8
MSTP boundary ports configuration guidelines described

27-23 27-20 27-20 27-39
MPLS to MPLS path
QoS default configuration

31-7
42-15
CIST, described CIST root

31-14 27-22
CIST regional root
VPN guidelines and restrictions mpls l2 transport route command MPLS QoS Classification Class of Service commands
42-16 42-20 42-22 42-2 42-2
configuration guidelines configuring forward-delay time hello time

27-46
27-39
31-19
27-47
link type for rapid convergence maximum aging time maximum hop count MST region
42-28 27-40 27-49 27-48 27-48
27-48
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
42-2 42-18 42-27
neighbor type path cost

27-44
42-29 42-2
Differentiated Services Code Point
port priority root switch
27-43 27-41 27-43
secondary root switch switch priority CST defined

42-2 27-20 27-45
enabling QoS globally

42-2 42-3
IP Precedence
42-2
operations between regions default configuration

42-19 27-39
27-21
queueing-only mode MPLS QoS configuration
displaying status enabling the mode
27-50 27-40
IN-13
Index
extended system ID effects on root switch unexpected behavior IEEE 802.1s implementation terminology described IST defined master
27-20 27-20 27-20 27-40 27-24 27-24 27-41 27-43
multicast, displaying routing table
35-22
effects on secondary root switch

27-42
Multicast enhancement - egress replication performance improvement 35-15 Multicast Enhancement - Replication Mode Detection 35-13 multicast flood blocking multicast groups joining leaving joining
36-2, 37-2 34-6, 36-4 55-1
port role naming change

27-22
interoperability with IEEE 802.1D

27-26 27-50
multicast groups, IPv6

34-4
restarting migration process
Multicast Listener Discovery version 2 See MLDv2 multicast multilayer switching See IPv4 MMLS Multicast Replication Mode Detection enhancement 35-13 multicast RPF
35-2
operations within a region MST region CIST

27-20 27-40 27-19
mapping VLANs to MST instance
multicast storms see traffic-storm control multicast television application

27-23 36-17
configuring described IST overview root switch configuring

27-20
hop-count mechanism
multicast VLAN
27-19
36-16
Multicast VLAN Registration See MVR multicast VLAN registration (MVR) MVR
27-41 27-41 36-16
supported spanning-tree instances

27-18
multichassis EtherChannel see MEC

4-14 27-42
effects of extended system ID unexpected behavior status, displaying MTU size (default)
27-50 22-4
Multidomain Authentication (MDA). See also port-based authentication. 57-10 Multilayer MAC ACL QoS Filtering multilayer switch feature card see RP multiple path RPF check
44-2 40-67
multiauthentication (multiauth). See also port-based authentication. 57-10 multicast IGMP snooping and MLDv2 snooping and NetFlow statistics non-RPF overview
35-5 36-2, 37-1, 37-7 38-4 36-9 34-10
Multiple Spanning Tree See MST MUX-UNI Support MUX-UNI support

31-26 31-26
61-10
PIM snooping
MVAP (Multi-VLAN Access Port). See also port-based authentication. 57-18
IN-14
OL-13013-06
Index
MVR and IGMPv3

36-20 36-20 36-21 36-19
multicast specifying
61-10
configuration guidelines configuring interfaces default configuration described

36-16
destination host filters protocol filters NDE version 8 NEAT configuring

36-17 57-60 57-26 61-3 61-17
61-17 61-16
destination TCP/UDP port filters NDE configuration, default

61-10
example application in the switch stack monitoring
36-17 36-19
36-23, 36-24
multicast television application setting global parameters

36-20
overview NetFlow
table, displaying entries
32-6 61-14
N
NAC agentless audit support critical authentication for Layer 3 interfaces
57-23 57-17, 57-51 56-2, 56-14
Netflow Multiple Export Destinations NetFlow search engine NetFlow version 9 See NAC Network Admission Control (NAC)
56-14 57-55 61-3 35-6
Network Admission Control

56-1 56-2,
IEEE 802.1x authentication using a RADIUS server 57-55 IEEE 802.1x validation using RADIUS server inaccessible authentication bypass Layer 2 IEEE 802.1x validation Layer 2 IEEE802.1x validation non-responsive hosts SSO NBAR NDAC NDE configuration, displaying displaying configuration enabling filters destination host, specifying protocol, specifying
61-17 61-17 61-16 61-10 61-17 61-17 56-12 16-13 56-6 57-51 57-55 57-23
network admission control for Layer 3 interfaces Network-Based Application Recognition Network Edge Access Topology See NEAT network ports Bridge Assurance description
28-2 31-2, 31-4 35-5 28-3 40-1
Network Device Admission Control (NDAC)
47-2
native VLAN
40-1 47-2
nonaggregate label non-RPF multicast Nonstop Forwarding See NSF
normal-range VLANs See VLANs NSF

6-1
destination TCP/UDP port, specifying
NSF with SSO does not support IPv6 multicast traffic. 6-1
source host and destination TCP/UDP port, specifying 61-16
IN-15
Index
O
OIR
9-16
PBACLs PBF PBR

A-45
46-3
48-14 1-7, 29-4
online diagnostics CompactFlash disk verification configuring

14-2 A-8 A-10 A-4 A-4
peer inconsistent state in PVST simulation PFC recirculation PFC3

35-6 35-12 31-4 28-12 21-17
per-port VTP enable and disable
datapath verification egress datapath test error counter test memory tests overview
14-1 14-5 A-1 14-1
interrupt counter test

14-12
PIM, IP MMLS and PIM snooping
designated router flooding enabling globally overview

A-1 38-4 38-5 38-5
38-6
running tests understanding
test descriptions online diagnostic tests See OIR
enabling in a VLAN
platform cwan acl software-switched command platform ipv4 pbr optimize tcam command PoE Cisco Prestandard Inline Power IEEE 802.3af police command policing See QoS policing policing. See power management. policy
40-65 46-3 48-2 15-4, 15-6 40-76 15-4, 15-5 29-4
48-12
online insertion and removal out-f-band MAC address table synchronization configuring in a VSS out of profile see QoS out of profile
16-8 4-29
P
packet burst packet capture packet rewrite CEF packets multicast PAgP understanding path cost MSTP
27-44
policy-based ACLs (PBACLs)

49-7 69-1 40-13
policy-based forwarding (PBF) policy-based routing See PBR policy enforcement policy map
35-3 40-73 56-7
packet recirculation
32-2
IP MMLS and
48-6
attaching to an interface policy-map command port ACLs defined

48-2 48-1
40-79
40-66, 40-73
PACLs. See private hosts feature

18-3
port ACLs (PACLs) see PAgP
Port Aggregation Protocol port-based authentication
IN-16
OL-13013-06
Index
AAA authorization accounting

57-12
57-34
configuration guidelines described

57-15
57-15, 57-16
configuring defined
57-46
host mode
57-9
authentication server
57-3, 58-2 56-4, 57-3
inaccessible authentication bypass configuring described guidelines

57-28, 58-7 57-51 57-17 57-31 57-6
RADIUS server client, defined configuring guest VLAN
57-3, 58-2
57-48
initiation and message exchange MAC authentication bypass magic packet

57-51 57-42 57-42 57-25 57-34
57-22
inaccessible authentication bypass initializing authentication of a client manual reauthentication of a client RADIUS server
58-9 57-37, 58-11
method lists modes

57-9
multiauth mode, described

57-36,
57-10 57-10
multidomain authentication mode, described multiple-hosts mode, described ports

57-9
RADIUS server parameters on the switch restricted VLAN

57-49
switch-to-authentication-server retransmission time 57-45 switch-to-client EAP-request frame retransmission time 57-44 switch-to-client frame-retransmission number 57-45, 57-46 switch-to-client retransmission time user distribution default configuration described device roles
57-1 57-2, 58-2 57-11 51-4 57-47 57-47 57-44
authorization state and dot1x port-control command 57-8 authorized and unauthorized critical port security and voice VLAN described interactions
57-19 57-19 57-9 57-11, 57-38 57-19 57-17 57-18 57-8
voice VLAN
VLAN group assignment
57-33, 58-7
multiple-hosts mode resetting to default values supplicant, defined switch as proxy

57-3, 58-2 57-3 57-3
pre-authentication open access

57-59
DHCP snooping
DHCP snooping and insertion displaying statistics EAPOL-start frame

57-6
57-62, 58-15
RADIUS client
57-6 57-6
EAP-request/identity frame EAP-response/identity frame enabling 802.1X authentication encapsulation guest VLAN
57-3
switch supplicant configuring overview user distribution configuring described guidelines

57-47 57-14 57-30 57-60 57-26
57-34, 57-36, 58-9 57-41
periodic reauthentication
IN-17
Index
VLAN assignment AAA authorization characteristics described VLAN group guidelines voice VLAN described PVID VVID
57-18 57-18 57-18 57-25 57-30 57-13 57-13 57-14 57-34
port security aging

59-11, 59-12 59-5 59-3
configuring described displaying
configuration tasks
59-2 59-12
enable sticky secure MAC address sticky MAC address violations

59-2 59-2
59-9
Port Security is supported on trunks port security MAC move

59-2 59-4
59-4, 59-5, 59-9, 59-10
wake-on-LAN, described port-based QoS features see QoS port channel
port security on PVLAN ports power management
Port Security with Sticky Secure MAC Addresses enabling/disabling redundancy

18-6 11-2
59-2
switchport trunk encapsulation dot1q port-channel see EtherChannel port-channel load-balance command
18-11 18-11, 18-12 4-46
inline power overview
15-4 15-5, 15-6
inline power policing

11-1
powering modules up or down power policing

15-11
11-3
command example
system power requirements, nine-slot chassis Power over Ethernet. See PoE.
4-46
11-5
port-channel load-defer command port cost, STP disabling displaying enabling PortFast See STP PortFast PortFast BPDU filtering
27-33
port-channel port load-defer command port debounce timer

9-15 9-15 9-15
pre-authentication open access. See port-based authentication. primary links priority overriding CoS private hosts
24-1 15-9, 15-10 17-1 23-2
primary VLANs
private hosts feature configuration guidelines configuring (summary)

24-5 24-9
See STP PortFast BPDU filtering port mode port priority MSTP ports setting the debounce timer
9-15 27-43 27-32 31-19 9-8
configuring (detailed steps)

24-8
port negotiation
multicast operation overview port types

24-1
24-7
port ACLs (PACLs)

24-3
24-5
port priority, STP
protocol-independent MAC ACLs restricting traffic flow with PACLs
24-2 24-3
IN-18
OL-13013-06
Index
spoofing protection private VLANs and SVIs benefits of

23-1
24-7
description PVST simulation

23-5
27-12
across multiple switches

23-6 23-2
description root bridge
28-11 28-12
peer inconsistent state

28-12 23-2, 23-3 23-7, 23-9, 23-11
community VLANs configuring host ports

23-11 23-15
Q
QoS
pomiscuous ports
23-16 23-13 23-12
auto-QoS enabling for VoIP IPv6

40-53 41-1 40-120 41-4
routing secondary VLAN ingress traffic secondary VLANs with primary VLANs VLANs as private end station access to IP addressing monitoring ports community isolated
23-3 23-9 23-4 23-2, 23-3 23-11 23-4
See also automatic QoS QoS classification (definition) QoS congestion avoidance definition QoS CoS
40-121
isolated VLANs
23-17
and ToS final L3 Switching Engine values definition

40-120 40-92 40-111, 43-2
40-12 40-12
and ToS final values from L3 Switching Engine port value, configuring
23-3 23-3 23-2 23-2
promiscuous primary VLANs secondary VLANs subdomains traffic in

23-2 23-6
QoS default configuration QoS DSCP definition

40-121 40-10
internal values
2-5
maps, configuring QoS dual transmit queue thresholds configuring

26-1 23-3
40-86
privileged EXEC mode promiscuous ports protocol tunneling
40-93, 40-97
See Layer 2 protocol tunneling pruning, VTP See VTP, pruning PVLANs See private VLANs PVRST See Rapid-PVST PVST description PVST+
27-2 27-18
QoS Ethernet egress port scheduling

40-111 40-12
scheduling, congestion avoidance, and marking QoS Ethernet ingress port
classification, marking, scheduling, and congestion avoidance 40-6 QoS final L3 Switching Engine CoS and ToS values QoS internal DSCP values QoS L3 Switching Engine classification, marking, and policing
40-9 40-10 40-12
IN-19
Index
feature summary QoS labels (definition) QoS mapping
40-16 40-121
QoS ToS and CoS final values from L3 Switching Engine definition
40-84, 40-87 40-28, 40-88, 42-16 40-121 40-4 40-12
CoS values to DSCP values DSCP markdown values DSCP mutation

40-83, 42-29
QoS traffic flow through QoS features QoS transmit queue size ratio
40-109, 40-110
DSCP values to CoS values QoS markdown QoS marking definition

40-121 40-15 40-15 40-20
40-89 40-87
QoS transmit queues QoS trust-cos port keyword QoS trust-dscp port keyword QoS trust-ipprec port keyword
40-23, 40-100, 40-101, 40-104
IP precedence values to DSCP values
40-14
40-14
trusted ports untrusted ports QoS out of profile QoS policing definition
40-14 40-14 40-11, 40-61
QoS multilayer switch feature card

40-20
40-17
QoS untrusted port keyword quad-supervisor
QoS VLAN-based or port-based uplink forwarding

40-60 4-6
40-121
microflow, enabling for nonrouted traffic QoS policing rule aggregate creating microflow QoS port trust state QoS queues transmit, allocating bandwidth between QoS receive queue drop thresholds QoS RP marking
40-17 40-121 40-8, 40-103, 40-105 40-22 40-90, 40-91 40-61 40-17 40-65 40-17
queries, IGMP queries, MLDv2
36-3 34-5
R
RADIUS range command
40-107 9-4, 64-2 51-4 57-3
RADIUS. See also port-based authentication.
QoS port-based or VLAN-based
macro
9-6 9-4 27-14
of interfaces rapid convergence Rapid-PVST enabling overview Rapid PVST+
27-37 27-18
QoS scheduling (definition) QoS session-based configuring configuring

40-11
QoS single-receive, dual-transmit queue ports

40-98 43-1
interoperation with MST Rapid Spanning Tree See RSTP Rapid Spanning Tree Protocol
28-11
QoS statistics data export

43-2
configuring destination host configuring time interval
43-7
See RSTP receive queues
43-6, 43-8
IN-20
OL-13013-06
Index
see QoS receive queues recirculation redirect URLs described

57-21 27-2 31-4, 40-13
ROM monitor CLI MST

2-7
root bridge
28-12 28-12
reduced MAC address redundancy (NSF) configuring BGP CEF IS-IS OSPF EIGRP
6-14 6-13 6-19 6-17 6-15 6-1
PVST simulation root bridge, STP root guard See STP root guard root switch MSTP See RHI
6-13 27-41 27-30
route health injection route processor redundancy See redundancy (RPR) router guard RPF
7-3 7-5 37-1 35-22
configuring multicast NSF with SSO configuring supervisor engine routing protocols redundancy (RPR) configuring
7-1 7-4 6-4 6-10
routing table, multicast failure

35-5 35-2
configuring supervisor engine redundancy command redundancy (SSO) redundancy command related documentation
6-11 1-xxxix 7-4
displaying supervisor engine configuration
multicast unicast RPR
non-RPF multicast
44-2
35-5
See redundancy (RPR) RPR support IPv6 multicast traffic RSTP active topology BPDU format
27-16 27-17 27-13 27-13 27-13 7-1
Remote Authentication Dial-In User Service. See RADIUS. Remote source-route bridging (RSRB) Replication Mode Detection report, MLD
34-4 35-13 29-2
reserved-range VLANs See VLANs restricted VLAN configuring described rewrite, packet CEF RHI
4-54 9-17 32-2 35-3 57-49 57-16 57-16
processing
designated port, defined designated switch, defined described

27-26
interoperability with IEEE 802.1D restarting migration process topology changes overview port roles described
27-13 27-15 27-13 27-17 27-50
using with IEEE 802.1x
IP MMLS
RIF cache monitoring
synchronized
IN-21
Index
proposal-agreement handshake process rapid convergence described

27-14 27-14
27-14
SGT
47-2 40-107
shaped round robin short pipe mode configuring
edge ports and Port Fast point-to-point links root ports See also MSTP
27-14 27-13
42-34 57-63 27-3
27-14, 27-48
show authentication command show configuration command show dot1x interface command show eobc command
9-17 9-3 2-4
show catalyst6000 chassis-mac-address command

9-16 57-41
root port, defined
S
Sampled NetFlow description scheduling see QoS SEA See System Event Archive secondary VLANs security configuring security, port
44-1, 45-1, 46-1, 49-1, 50-1 59-2 47-2 47-2 23-2 59-11 61-8
show hardware command show history command show ibc command

16-15 9-17
show interfaces command
9-3, 9-12, 9-13, 9-16, 9-17, 16-7, 9-18 9-3 9-9
clearing interface counters
displaying, interface type numbers displaying, speed and duplex mode show ip flow export command
Secure MAC Address Aging Type
displaying NDE export flow IP address and UDP port 61-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 mab command
57-66 60-9 32-6 35-20 35-22 35-20
Security Exchange Protocol (SXP) Security Group Tag (SGT) serial IDs description serial interfaces clearing
9-18 62-34 47-2
Security Group Access Control List (SGACL)
show mls aging command show mls entry command
show mls ip multicast group command displaying IP MMLS group

9-18 35-23, 35-26
synchronous maintaining server IDs description

62-34 40-66 40-61, 40-79, 40-84, 40-86, 27-19 11-2
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
35-23, 35-26 35-23, 35-26
show mls ip multicast source command

35-23, 35-26
service-policy command
42-29
service-policy input command
show mls ip multicast statistics command

35-23, 35-26
service-provider network, MSTP and RSTP SGACL

47-2
set power redundancy enable/disable command
IN-22
OL-13013-06
Index
show mls nde command show mls rp command
61-17 61-15
See MLDv2 snooping software upgrading router

60-8 5-5, 5-14
displaying NDE flow IP address displaying IP MLS configuration show module command show protocols command show rif command
9-17 7-5
source IDs call home event format

48-12 62-34 60-3
show platform acl software-switched command

9-17
source-only-ip flow mask
source specific multicast with IGMPv3, IGMP v3lite, and URD 35-11
9-16, 9-17
show running-config command displaying ACLs show version command shutdown command shutdown interfaces result
9-19 9-2 48-8, 48-9
SPAN configuration guidelines

65-7
show svclc rhi-routes command

9-17 57-47
4-54
configuring sources
65-31
65-14 65-19, 65-21, 65-23, 65-25, 65-26, 65-28, 65-29, 65-33
show vlan group command

9-19
VLAN filtering CPU source
65-6, 65-19, 65-20, 65-23, 65-29 65-7, 65-22,
destination port support on EtherChannels

65-25, 65-27, 65-28, 65-32
slot number, description smart call home description

62-1 62-3
distributed egress
65-5, 65-18 65-14 65-14
modules that disable

62-6 62-3 62-4 62-2
modules that disable for ERSPAN input packets with dont learn option ERSPAN local SPAN RSPAN understanding
62-3 65-31, 65-32 65-20, 65-21, 65-22
destination profile (note) registration requirements
service contract requirements SMARTnet smart call home registration smart port macros Smartports macros
3-1 3-3
Transport Gateway (TG) aggregation point
65-25, 65-26, 65-28 65-7 65-10, 65-19
local SPAN egress session increase overview

65-1
SPAN Destination Port Permit Lists spanning-tree backbonefast

3-14
65-17
applying global parameter values applying macros creating defined tracing SNMP support and documentation snooping See IGMP snooping
1-5 3-13 3-2 3-14
command
28-19, 28-20 28-19, 28-20
command example spanning-tree cost command

27-34
3-2 3-16
command example spanning-tree portfast command
27-34
displaying
3-4
28-12, 28-14 28-13
command example command

28-17
spanning-tree portfast bpdu-guard spanning-tree port-priority

OL-13013-06
IN-23
Index
command
27-32 29-2
sticky MAC address storm control
59-2 59-9, 59-10
spanning-tree protocol for bridging spanning-tree uplinkfast command

28-18 28-18, 28-19
Sticky secure MAC addresses see traffic-storm control STP configuring

27-26 27-35
command example spanning-tree vlan command
27-28, 27-29, 27-31, 28-18, 28-20 27-28, 27-29, 27-31
bridge priority enabling hello time port cost
command example spanning-tree vlan cost command command

27-34
27-28, 27-29 27-36
forward-delay time
27-36
spanning-tree vlan forward-time

27-36 27-37
maximum aging time

27-33 27-32 27-30
27-37
command example command

27-36
port priority root bridge defaults edge ports

27-27 28-2
spanning-tree vlan hello-time command example command

27-37 27-37 27-36
secondary root switch
27-31
spanning-tree vlan max-age command example command

27-32 27-33
EtherChannel network ports normal ports PortFast

28-2
18-5 28-2 28-2
spanning-tree vlan port-priority command example command speed configuring interface speed command speed mode autonegotiation status SRR
40-107 56-12 9-9 1-3, 9-8 9-7 27-35 27-35
understanding
27-1 27-12 27-7
spanning-tree vlan priority command example
802.1Q Trunks Blocking State BPDUs

27-3
disabled state learning state listening state overview port states

17-1 27-2
27-11 27-10
forwarding state
27-9 27-8
27-5 27-4 27-4
SSO for network admission control standby links static sharing configuring description statistics 802.1X sticky ARP
57-62, 58-15 49-18 57-35 57-21
protocol timers topology STP BackboneFast configuring figure adding a switch

28-19 27-5
root bridge election
28-10
spanning-tree backbonefast
IN-24
OL-13013-06
Index
command understanding STP BPDU Guard configuring command understanding STP bridge ID STP extensions description STP loop guard configuring overview STP PortFast BPDU filter configuring BPDU filtering configuring command understanding STP port types description edge normal
28-2 28-2 28-2 27-2
28-19, 28-20 28-19, 28-20
redundancy
6-1, 7-1 6-20, 7-5
command example
28-7
synchronizing configurations Supervisor Engine 32 configuring

1-4, 1-5
supervisor engine redundancy

28-16 6-10, 7-3
spanning-tree portfast bpdu-guard

28-17 28-5
supervisor engines displaying redundancy configuration supplicant

57-3 4-53 7-5
svclc command
28-9
STP EtherChannel guard
Switched Port Analyzer See SPAN switch fabric functionality configuring

8-3 8-4 8-1
28-2 to 28-12
28-21 28-10
monitoring switchport configuring example
16-16
16-15 9-12, 9-13, 16-7, 16-15 16-8, 16-9, 16-12, 16-16
28-15 28-5
show interfaces example example

16-17
switchport access vlan switchport mode access

16-17 28-13
28-12
spanning-tree portfast
28-12, 28-14
16-4, 16-8, 16-9, 16-16
command example
28-2
switchport mode dynamic
16-11 16-4 16-4
switchport mode dynamic auto default example

16-5 16-15
switchport mode dynamic desirable

28-2
network
switchport mode trunk switchport nonegotiate
16-4, 16-11 16-4 16-13 16-9, 16-10 16-4
STP root guard STP UplinkFast configuring
28-10, 28-20
switchport trunk allowed vlan switchport trunk encapsulation
28-18
switchport trunk encapsulation dot1q example

28-18, 28-19 16-15
spanning-tree uplinkfast command understanding supervisor engine environmental monitoring

11-10 28-18
switchport trunk encapsulation isl default

23-2 16-5 16-13
16-4 16-4
command example
28-6
switchport trunk encapsulation negotiate switchport trunk native vlan switchport trunk pruning vlan switch priority
subdomains, private VLAN
16-14
IN-25
Index
MSTP
27-45
multicast unicast
67-2
54-4, 54-6 54-4, 54-6
switch TopN reports foreground execution running viewing SXP

47-2 63-1 63-1 67-2 67-2
described monitoring thresholds
54-1 54-7 54-1
traffic suppression see traffic-storm control transmit queues see QoS transmit queues trunks
16-3 16-5
system event archive (SEA) System Hardware Capacity
System Event Archive, configuring

11-5
T
TACACS+ TDR checking cable connectivity enabling and disabling test guidelines Telnet accessing CLI See TDR TLV host presence detection traceroute, Layer 2 and ARP and CDP described
68-2 68-2 68-1 68-2 68-2 15-3, 57-10, 59-3 2-2 9-19 9-19 9-19 44-1, 45-1, 46-1, 49-1, 50-1 44-2
802.1Q Restrictions allowed VLANs configuring

16-10
16-13
TCP Intercept
default interface configuration default VLAN encapsulation native VLAN

16-12 16-3
16-7
different VTP domains

16-4 16-13 16-5
to non-DTP device trust-dscp see QoS trust-dscp trusted boundary trust-ipprec see QoS trust-ipprec trustpoint tunneling
62-4 42-4, 42-30 15-9
VLAN 1 minimization
16-14
Time Domain Reflectometer
trusted boundary (extended trust for CDP devices)
15-3
IP addresses and subnets multicast traffic unicast traffic

68-2
tunneling, 802.1Q See 802.1Q type length value See TLV

25-1
MAC addresses and VLANs multiple devices on a port

68-1 68-2 55-1
68-2
usage guidelines traffic flood blocking traffic-storm control command
U
UDE
30-1 30-3
configuration
54-4, 54-6
action shutdown broadcast
overview
30-2 30-1
54-4, 54-6
UDE and UDLR
IN-26
OL-13013-06
Index
UDLD default configuration enabling globally on ports overview UDLR

30-1 30-1 30-6 10-5 10-5, 10-6 10-4
UplinkFast See STP UplinkFast uplink forwarding quad-supervisor URD

35-11 40-19, 40-77 4-6
10-1
User-Based Rate Limiting user EXEC mode UUFB UUFRL

55-1 55-1 2-5
back channel configuration tunnel (example)
30-7 30-3
ARP and NHRP See UDLR UMFB

55-1
V
VACLs
48-2 48-11 48-16 48-15 46-10
UDLR (unidirectional link routing)
configuring examples
57-8 55-1
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
42-39 30-5 44-2 55-1
Layer 3 VLAN interfaces Layer 4 port operations logging configuration example configuring restrictions multicast packets SVIs
48-15 48-2 48-19 48-19 48-11
Unicast and Multicast Flood Blocking
48-20
MAC address based
48-6
WAN interfaces virtual LAN See VLANs vlan command
UniDirectional Link Detection Protocol
22-5, 22-7, 61-12, 61-13, 65-23 22-6
unknown multicast flood blocking
command example See VACLs
VLAN Access Control Lists VLAN-based QoS filtering vlan database command example VLAN locking
22-5, 22-7, 61-12, 61-13, 65-23 22-6 57-47 40-68 29-2
unknown unicast flood rate-limiting See UUFRL untrusted see QoS trust-cos see QoS untrusted upgrade guidelines
31-19
VLAN-bridge spanning-tree protocol
vlan group command

22-4
IN-27
Index
vlan mapping dot1q command VLAN maps applying VLAN mode VLANs allowed on trunk configuring defaults
22-4 22-2 22-6 22-1 22-3 16-13 22-3 48-9 31-19 22-4 22-9, 22-10, 22-11 22-11
connecting to an IP phone default configuration overview VPN configuration example VPN supported commands VPN switching VSS dual-active detection
31-13 15-1 15-6
15-7
command example
voice VLAN. See also port-based authentication.

31-15 31-14
57-18
VLAN port provisioning verification
guidelines and restrictions
31-14
configuration guidelines configuring (tasks) extended range multicast

36-16 22-4 22-2
Enhanced PAgP, advantages Enhanced PAgP, description enhanced PAgP, description fast-hello, advantages fast hello, description IP BFD, advantages IP BFD, description IP BFG, configuration
4-23 4-24 4-23 4-24 4-48
4-23 4-23 4-46
interface assignment name (default) normal range private
See private VLANs reserved range token ring trunks understanding understanding VTP domain VLAN translation command example See VTP voice VLAN Cisco 7960 phone, port connections configuration guidelines
15-7 15-2 22-10 22-1 16-14 16-3 22-4 22-2 22-2
VSLP fast-hello, configuration VTP advertisements

21-3, 21-4 21-15 21-9
4-49
support for 4,096 VLANs
client, configuring
configuration guidelines default configuration disabling domains modes client server monitoring overview pruning
15-9, 15-10 21-3 21-3 21-3 21-15 21-2 22-4
21-8
VLAN 1 minimization
22-4
VLANs
VLAN Trunking Protocol
transparent
21-1
21-18
per-port enable and disable configuration configuring overview

21-6 16-14 21-13
21-17
configuring IP phone for data traffic override CoS of incoming frame configuring ports for voice traffic in 802.1Q frames
15-8
IN-28
OL-13013-06
Index
server, configuring statistics version 2 enabling overview version 3 enabling overview

21-14 21-5 21-13 21-4 21-18
21-15
transparent mode, configuring
21-15
server type, configuring
21-12
W
wake-on-LAN. See also port-based authentication. web-based authentication AAA fail policy description
58-1 1-6 40-107 58-4 57-25
web browser interface weighted round robin wireless access point inline power WRR
40-107 15-4
X
xconnect command
31-19
IN-29
Index
IN-30
OL-13013-06

Cisco IOS Software Configuration Guide

Uploaded by

Document Informationclick to expand document informationIPTV, Cisco IOS Software Configuration Guide

Document Informationclick to expand document information

Copyright:

Available Formats

Cisco IOS Software Configuration Guide

Uploaded by

Document Information

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

Cisco IOS Software Configuration Guide

Uploaded by

Copyright:

Available Formats

Cisco IOS Software Configuration Guide

Release 12.2(33)SXH and Later Releases

Text Part Number: OL-13013-06

Obtaining Documentation, Obtaining Support, and Security Guidelines

Software Features Supported in Hardware by the PFC and DFC

Configuring Smart Port Macros

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Configuring NSF with SSO Supervisor Engine Redundancy

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Configuring RPR Supervisor Engine Redundancy

Interface and Hardware Components

Cisco IOS Software Configuration Guide, Release 12.2SX

Understanding Interface Configuration Using the Interface Command

Configuring a Range of Interfaces

Defining and Using Interface-Range Macros

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Configuring Online Diagnostics

Understanding Online Diagnostics

Cisco IOS Software Configuration Guide, Release 12.2SX

Configuring Cisco IP Phone Support

Cisco IP Phone Support Configuration Guidelines and Restrictions

Layer 2 LAN Interface Configuration Guidelines and Restrictions

Configuring Flex Links

Understanding Flex Links

Configuring Flex Links 17-2 Flex Links Default Configuration

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Configuring mLACP for Server Access

Cisco IOS Software Configuration Guide, Release 12.2SX

Configuring IEEE 802.1ak MVRP and MRP

VTP Configuration Guidelines and Restrictions

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Displaying VTP Statistics

Configuring Private VLANs

Cisco IOS Software Configuration Guide, Release 12.2SX

Configuring Private Hosts

Configuring IEEE 802.1Q Tunneling Understanding 802.1Q Tunneling

25-1 25-1 25-3

Configuring Layer 2 Protocol Tunneling Understanding Layer 2 Protocol Tunneling

26-1 26-1 26-2

Configuring Support for Layer 2 Protocol Tunneling

Configuring STP and MST

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Cisco IOS Software Configuration Guide, Release 12.2SX

Configuring Optional STP Features

Cisco IOS Software Configuration Guide, Release 12.2SX OL-13013-06

Configuring Layer 3 Interfaces

Configuring AppleTalk Routing, Cable Ranges, and Zones

Configuring UDE and UDLR

Multiprotocol Label Switching

Configuring Multiprotocol Label Switching

MPLS VPN Sample Configuration

Configuring IP Unicast Layer 3 Switching

Displaying Hardware Layer 3 Switching Statistics

Configuring IPv4 Multicast Layer 3 Switching

Cisco IOS Software Configuration Guide, Release 12.2SX

Understanding IPv4 Bidirectional PIM

35-9 35-9 35-10

Default IPv4 Multicast Layer 3 Switching Configuration